millbj92/us-zip-codes-json

List of all US Zip codes in JSON format. Includes Latitude, Longitude, City, State, County, and of course, Zip Code.

US-Zip-Codes-JSON

List of all US Zip codes in JSON format. Includes Latitude, Longitude, City, State, County, and of course, Zip Code.

Feel free to fork and use in your own project :)

Bugs / extending / general QOL updates

As stated above, you're definitely more than welcome to fork and keep a copy on your own GH, all I ask is if you do find a bug, please let me know as it seems this repo tens to be the one people find first. I would also love to extend this at some point to include possibly some more general info about the location and/or possibly new JSON files for different countries. If you think of any cool ideas on how to extend this please make a comment in the discussions or submit a PR for the feature. There are a ton of ways extending this could further help people and

Extending

If you'd like to extend the data structure a bit to include some more helpful info, please just try and keep the general data structure the same. I.E. Don't add one or two properties to just YOUR specific area code and call it a day. You can, however, create the props for every object and give values to only your zip code.

Generally, I just want to make sure that if someone were to load this into an API, etc, that the client can always expect the same general structure.

Thanks for reading. And remember, I'm never NOT okay with it if you'd like to

us-zip-codes-json's Issues

Lat Long associated with 77035 is incorrect

If you do a lookup on the lat long of 77035, it actually gives you the zip code of 77018.
Lat: 29.83399
Long: -95.434241

Zip code list is missing latest updates

Looking through postal bulletins, there have been a few zip code updates since this data set was generated, with https://postalpro.usps.com/POB_22625 being the most significant I think, as it mentions two zip codes that don't exist in the data right now. As such, I'm thinking the data here needs to be regen'd.

Where is this data being sourced/what script was used to generate it, by the way?

A suggestion

Hey, it is a wonderful data source that you created. Thank you!
I was thinking it will be very handy if the json file also contains ne_lng, ne_lat, sw_lng, sw_lat fields describing the rectangular bounds of each zip.
I will definitley buy you a beer when you add them. Hahha!

ZIPs starting with zero omit first character due to storing as an INT

I noticed what I think is a bug. Storing ZIPs as INT will omit leading zeros. Here's an example of a ZIP in NJ:

{
      "zip_code": 7837,
      "latitude": 41.12831,
      "longitude": -74.678956,
      "city": "Glasser",
      "state": "NJ",
      "county": "Sussex"
    }

This causes data loss since the first character defines the geographical region for the ZIP.

Would you accept a PR to convert the data type to a STRING and correct all zip codes that begin with zero?

These are area codes not zip codes

An important distinction!