Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling of ambigious zipcodes #13

Open
klemmster opened this issue Apr 11, 2012 · 4 comments
Open

Handling of ambigious zipcodes #13

klemmster opened this issue Apr 11, 2012 · 4 comments
Assignees
Labels

Comments

@klemmster
Copy link

curl http://zip.elevenbasetwo.com?zip=10115

returns:

{"country": "US", "state": "NY", "city": "NEW YORK"}

however, it should indicate that this is also a match.

{"country": "DE", "state": "BERLIN", "city": "BERLIN"}

@ghost ghost assigned daspecster May 9, 2012
@daspecster
Copy link
Owner

Looks like this issue is getting bigger now that we added more!

@eostrom
Copy link

eostrom commented May 10, 2012

Related, 55416 is a zip code that includes portions of both Minneapolis and St. Louis Park, MN. It's not the case that city can always be determined from the zip (or even zip + country).

@yakatz
Copy link

yakatz commented Jul 29, 2013

Same issue with 20901: Most people use "Silver Spring, MD", but ziptastic returns "Takoma Park, MD".
According to the USPS website, the preffered result is Silver Spring.

@wguldin
Copy link

wguldin commented Jun 3, 2014

One possible way to handle this is something like the Checkout process of Crate & Barrel, which upon Zipcode submission, provides a dropdown of all valid cities within that zipcode. Don't know if it's possible to replicate this with ziptastic, but it'd be more user-friendly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants