Hacker News new | past | comments | ask | show | jobs | submit login

* API client with batching and parallelization built in (100 queries in a single request, multiple requests run in parallel, etc.)

* robustness in the face of bad street suffixes (for example, in Burlington, VT, you may find data with "CR" meaning "CIRCLE" instead of the official USPS "CREEK")

* fuzzy street name matching (PAKCER -> PACKER)

* accurate geocoding in rural United States

* fuzzy international place matching (like "ST PANCRAS ST STATION" in London)




In your experience is the rural US geocoding problem a software problem or a lack of underlying data?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: