Pelias fails to find address if city is added to query #1594
Comments
|
agh, funny, this is actually the issue I was planning to tackle today and I spent an hour figuring that out 😆 for now the workaround is to use a different form of the street name, any of the following work:
you can follow this issue for updates on a proper fix: pelias/model#144 |
|
Haha, i'm glad to hear that you are already working on it, since this is a pretty big issue for german street names, which are almost always written with the |
|
There is a PR open now, it still needs a bit more work before merging but seems to be much better at producing all permutations of German street names. The list of terms is fairly small for now, basically just Do you see a need to add any of these? |
|
This is a pretty good list IMO but lists the abbreviation for 'Platz' as '-pl' which seems wrong to me? Isn't it more commonly written |
|
Not sure if i'm the right person to answer this questions, but personally i haven't seen most of these abbreviations anywhere before. But that doesn't mean they aren't more commonly used in other parts of Germany or other German speaking countries. So if it doesn't add to the complexity of the implementation or otherwise mess with the matching of non abbreviated street names, i'd say just add them?! The list from libostal looks like the better one to me, and a quick google search seems to confirm the abbreviation of "Platz" is indeed "pl" 👍. |
|
there is a build up on dev right now which looks much better @fl0cke |
|
@missinglink excellent! Which package do i need to update for this to work on my machine? Edit: found it... |
|
I need to update three docker images (openstreetmap/openaddresses/polylines) & probably also csv-importer to make sure they are all bringing in the latest version of the |
|
okay the docker images have been updated, you should be able to run |
|
I just updated our server and everything seems to work as expected. Thanks! |
|
Hi! I have a CSV dataset with Spanish addresses that the API sometimes fails to provide when the city is included in the query. I.e. the CSV contains the next address: I expect that address to be returned with the query
|
I have observed some strange behaviour with search queries on my new Pelias setup. I have imported the dataset for germany and are trying to geocode the following address: Ackermannstr. 12a Frankfurt am Main
Executing the query
GET /v1/search?text=Ackermannstr. 12a Frankfurt am Main&sources=osm&size=1yields the following result:{ "geocoding": { "version": "0.2", "query": { "text": "Ackermannstr. 12a Frankfurt am Main", "size": 1, "sources": [ "openstreetmap" ], "private": false, "lang": { "name": "German", "iso6391": "de", "iso6393": "deu", "via": "header", "defaulted": false }, "querySize": 20, "parser": "libpostal", "parsed_text": { "street": "ackermannstr.", "housenumber": "12a", "city": "frankfurt am main" } }, "engine": { "name": "Pelias", "author": "Mapzen", "version": "1.0" }, "timestamp": 1641556303027 }, "type": "FeatureCollection", "features": [ { "type": "Feature", "geometry": { "type": "Point", "coordinates": [ 8.584764, 50.041821 ] }, "properties": { "id": "101913837", "gid": "whosonfirst:locality:101913837", "layer": "locality", "source": "whosonfirst", "source_id": "101913837", "country_code": "DE", "name": "Frankfurt am Main", "confidence": 0.6, "match_type": "fallback", "accuracy": "centroid", "country": "Deutschland", "country_gid": "whosonfirst:country:85633111", "country_a": "DEU", "region": "Hessen", "region_gid": "whosonfirst:region:85682531", "region_a": "HE", "macrocounty": "Darmstadt", "macrocounty_gid": "whosonfirst:macrocounty:404227581", "county": "Frankfurt", "county_gid": "whosonfirst:county:102063589", "county_a": "FA", "localadmin": "Frankfurt am Main", "localadmin_gid": "whosonfirst:localadmin:1377692799", "locality": "Frankfurt am Main", "locality_gid": "whosonfirst:locality:101913837", "continent": "Europa", "continent_gid": "whosonfirst:continent:102191581", "label": "Frankfurt am Main, HE, Deutschland" }, "bbox": [ 8.472633, 50.015574, 8.800535, 50.226257 ] } ], "bbox": [ 8.472633, 50.015574, 8.800535, 50.226257 ] }As you can see, the address is not found and instead Pelias falls back to returning the locality.
However, when i remove the city from the query (
GET /v1/search?text=Ackermannstr. 12a&sources=osm&size=1), it returns the correct result:{ "geocoding": { "version": "0.2", "query": { "text": "Ackermannstr. 12a", "size": 1, "sources": [ "openstreetmap" ], "private": false, "lang": { "name": "German", "iso6391": "de", "iso6393": "deu", "via": "header", "defaulted": false }, "querySize": 20, "parser": "pelias", "parsed_text": { "subject": "12a Ackermannstr.", "street": "Ackermannstr.", "housenumber": "12a" } }, "engine": { "name": "Pelias", "author": "Mapzen", "version": "1.0" }, "timestamp": 1641556309332 }, "type": "FeatureCollection", "features": [ { "type": "Feature", "geometry": { "type": "Point", "coordinates": [ 8.627754, 50.097648 ] }, "properties": { "id": "way/154520993", "gid": "openstreetmap:address:way/154520993", "layer": "address", "source": "openstreetmap", "source_id": "way/154520993", "country_code": "DE", "name": "Ackermannstraße 12", "housenumber": "12", "street": "Ackermannstraße", "postalcode": "60326", "confidence": 1, "match_type": "exact", "accuracy": "point", "country": "Deutschland", "country_gid": "whosonfirst:country:85633111", "country_a": "DEU", "region": "Hessen", "region_gid": "whosonfirst:region:85682531", "region_a": "HE", "macrocounty": "Darmstadt", "macrocounty_gid": "whosonfirst:macrocounty:404227581", "county": "Frankfurt", "county_gid": "whosonfirst:county:102063589", "county_a": "FA", "localadmin": "Frankfurt am Main", "localadmin_gid": "whosonfirst:localadmin:1377692799", "locality": "Frankfurt am Main", "locality_gid": "whosonfirst:locality:101913837", "neighbourhood": "Goldstein", "neighbourhood_gid": "whosonfirst:neighbourhood:85795343", "label": "Ackermannstraße 12, Frankfurt am Main, HE, Deutschland" } } ], "bbox": [ 8.627754, 50.097648, 8.627754, 50.097648 ] }The only difference i can spot is the parser that is used for extracting the address components from the query. But both produce correct components, so i'm not sure what's going on here. Do you have any idea?
The text was updated successfully, but these errors were encountered: