Open codekrolik2 opened 2 years ago
Same here. Any update on this issue? It parses wrongly in some cases
I believe the latest Senzing alternative model handles that.
{"CITY":["LOS ANGELES"],"HOUSE_NUMBER":["777"],"LEVEL":["41ST FLOOR"],"POSTCODE":["90017"],"ROAD":["S FIGUEROA ST"],"STATE":["CA"]}
Hi!
I was checking out libpostal, and saw something that could be improved.
My country is
USA
Here's how I'm using libpostal
Parsing address components
Here's what I did
Tried to parse "777 S. Figueroa St, 41st Floor Los Angeles CA 90017"
Here's what I got
HOUSE_NUMBER: 777 ROAD: s. figueroa st 41st floor CITY: los angeles STATE: ca POSTCODE: 90017
Here's what I was expecting
HOUSE_NUMBER: 777 ROAD: s. figueroa st LEVEL: 41st floor CITY: los angeles STATE: ca POSTCODE: 90017
For parsing issues, please answer "yes" or "no" to all that apply.
Does the input address exist in OpenStreetMap? No
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? Yes, if you put the floor first: Components for: 41st Floor, 777 S. Figueroa St, Los Angeles CA 90017
LEVEL: 41st floor HOUSE_NUMBER: 777 ROAD: s. figueroa st CITY: los angeles STATE: ca POSTCODE: 90017
If the address does not contain city, region, etc., does adding those fields to the input improve the result? The address contains those fields
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? It works fine without floor info: Components for: 777 S. Figueroa St, Los Angeles CA 90017
HOUSE_NUMBER: 777 ROAD: s. figueroa st CITY: los angeles STATE: ca POSTCODE: 90017
Here's what I think could be improved
The addresses in which Floor information is specified in the same way can be found everywhere. It would be great to add parsing support for this format as well.