Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Geocoding of locality-specific "plus codes" is broken when they contain a suffix with a space in it (i.e Colorado Springs, Colorado) #21967

Open
arkag opened this issue Feb 25, 2025 · 0 comments

Comments

@arkag
Copy link

arkag commented Feb 25, 2025

Description

Beat for beat the same report as #12809, but specifically with suffixes that have a space in them that also include a matching locality.

Example of working parsing:

Denver International Airport:

Stevens-Pagosa Springs Airfield:

Example of broken parsing:

Colorado Springs Airport:

Steps to reproduce

Search for the three short codes I mentioned above:

  1. Colorado Springs Airport: R73Q+FG Colorado Springs, Colorado
  2. Denver International Airport: V84F+GC Denver, Colorado
  3. Stevens-Pagosa Springs Airfield: 7WMV+J4 Pagosa Springs, Colorado

Actual result

  1. A location in Brazil (incorrect)
  2. A location in Colorado (correct)
  3. A location in Colorado (correct)

Expected result

  1. Should match 2 and 3
  2. No change
  3. No change

Your Environment (required)

WARNING Crash-Logs MAY contain information you deem sensitive.
Review this CAREFULLY before posting your issue!

Device : komodo
Brand : google
Manufacturer : Google
Model : Pixel 9 Pro XL
Product : komodo
Build : AP4A.250205.002.C1
Version : 15
App Version : OsmAnd~
Apk Version : 4.9.10 491003
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant