Missing locality in geocoding result
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 259
- Forks
- 169
- Avg merge
- 6h 15m
- Merged PRs (30d)
- 1
Description
Hey Everyone!
When I search for an address in some parts of Germany, e.g. eggeberger strasse, the results are missing a locality field.
"properties": {
"id": "polyline:2682317",
"gid": "openstreetmap:street:polyline:2682317",
"layer": "street",
"source": "openstreetmap",
"source_id": "polyline:2682317",
"name": "Eggeberger Straße",
"street": "Eggeberger Straße",
"confidence": 1,
"match_type": "exact",
"accuracy": "centroid",
"country": "Deutschland",
"country_gid": "whosonfirst:country:85633111",
"country_a": "DEU",
"region": "Nordrhein-Westfalen",
"region_gid": "whosonfirst:region:85682513",
"region_a": "NRW",
"macrocounty": "Regierungsbezirk Detmold",
"macrocounty_gid": "whosonfirst:macrocounty:404227571",
"county": "Gütersloh",
"county_gid": "whosonfirst:county:102063877",
"county_a": "GT",
"continent": "Europa",
"continent_gid": "whosonfirst:continent:102191581",
"label": "Eggeberger Straße, Deutschland"
}
However, the data should be available for the underlying source (OSM in this case).
Also, using Nominatim I can find the exact same place by typing eggebergerstrasse (missing the space), while Pelias gives no results for the same query.
Thanks for having a look!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Eggeberger Straße and eggebergerstrasse searches using the Pelias API comparison links, then trace how the OpenStreetMap result is assembled. Compare the response with the linked Nominatim details and search results; done means the locality is present and the no-space query returns the expected place.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100