You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We usually get around this by calling the expand endpoint on libpostal for any abbrivations:
curl -v -X POST -H "Content-Type: application/json" -d '{"address":"CO"}' https://your_libpostal_server.com/expand
Response: ["co","colorado","county","company"]
And then calling the proper endpoint on Photon to feetch the data:
curl -X GET "https://your_server.com/api?q=Colorado"
which returns the needed items. I find that expanding common items first is easier. It's also helpful if you use something like pub 28 from the USPS to help normalize things as well before passing to the geocoder.
Not certain if that's something that should be specifically an issue w/ this project, as technically this project DOES work.
It looks like photon is looking for a place when characters are added after "New York."
I believe the second command should have resulted in the same output as the first.

The text was updated successfully, but these errors were encountered: