libpostal
libpostal copied to clipboard
20 Boulevard St-Michel, Paris, France
Hi!
This is an interesting test case which produces different parses depending on how the street name is specified:
20 Boulevard St-Michel, Paris, France
My country is
France
Here's how I'm using libpostal
Pelias Geocoder
Here's what I did & what I got
> 20 Boulevard St-Michel, Paris, France
Result:
{
"house_number": "20",
"road": "boulevard st-michel",
"city": "paris",
"country": "france"
}
> 20 Boulevard St Michel, Paris, France
Result:
{
"house_number": "20",
"road": "boulevard",
"suburb": "st michel",
"city": "paris",
"country": "france"
}
> 20 Boulevard Saint Michel, Paris, France
Result:
{
"house_number": "20",
"road": "boulevard",
"suburb": "saint michel",
"city": "paris",
"country": "france"
}
Here's what I was expecting
"house_number": "20",
"road": "boulevard st-michel",
For parsing issues, please answer "yes" or "no" to all that apply.
- Does the input address exist in OpenStreetMap? https://www.openstreetmap.org/node/2553153336 https://www.openstreetmap.org/node/3172251267
- Do all the toponyms exist in OSM (city, state, region names, etc.)? yes
- If the address uses a rare/uncommon format, does changing the order of the fields yield the correct result? As shown above
- If the address does not contain city, region, etc., does adding those fields to the input improve the result? N/A
- If the address contains apartment/floor/sub-building information or uncommon formatting, does removing that help? Is there any minimum form of the address that gets the right parse? N/A
Here's what I think could be improved
The synonyms seem to be correct so I'm not sure what's going on...
A similar address which seems to have the same issue:
> 20 Boulevard St Martin, Paris, France
Result:
{
"house_number": "20",
"road": "boulevard st",
"suburb": "martin",
"city": "paris",
"country": "france"
}