boundaries-io
9.9 / 10
361ms
100%
Zip Codes don't line up with google
Hey I was just looking into the boundary returned by a zipcode for the first time on query by zipcode for zipcode boundaries. The first zipcode I tested 22066 in VA did not match google’s result, there was a section in the boundaries-io result that covered a different area than google. After checking some locations within that area for their zipcode, the boundaries-io result seems to be wrong.
This is a minor blemish as I see it but a location marked with 22102 as its zip, appears in 22066 according to boundaries-io but appears correctly on google and on other services.
Can I reliably use this service if the first zipcode I tested is wrong? zipcodes are the whole reason I would use this service, please let me know, thanks
Únase a la conversación, añada un comentario a continuación:
If you encounter discrepancies between the data provided by a service like boundaries and other trusted heardle sources, it’s a good idea to contact the service provider. They may be able to investigate and address the issue or provide clarification on the accuracy of their data.
This is quite useful, so thank you! thank you so much for your reply. It’s strange that Google’s search results don’t match up with government data, unless the search engine is simply behind on updates.
geometry dash
thanks
Line items can have their number of impressions and clicks delivered dramatically decreased by targeting them to a limited geographic area or collection of postal codes.
Line items can have their number of impressions and clicks delivered dramatically decreased by targeting them to a limited geographic area or collection of postal codes.
So useful, thank you very much!
Thank you so much, this is very helpful! And that combine=true feature might be very helpful as well, really appreciate the response. Weird that google doesn’t align with official records, unless they are just behind on updating.
Hello,
Great questions! We have quite a few clients who are in the emergency response and communication industry, so In order to maintain accuracy of zipcode boundaries and data we must only pull from official sources without modification.
Our boundaries data comes directly from the the US census Cartographic boundaries files located in the below link which differs slightly from Google.
Cartographic Boundary Files - Shapefile (census.gov)
https://www.census.gov/geographies/mapping-files/time-series/geo/carto-boundary-file.html?msclkid=89b9cc75a72111ecbfe58b9cdb53320e
22066
https://gist.github.com/boundaries-io/3f7970aa988803796c9c9f0ff2361d3f
22102
https://gist.github.com/boundaries-io/0c91b2d333c246c4af073312152f44f4
We also include additional endpoints that allow merging of these boundaries into a single GeoJson Feature using the ‘combine=true’ query parameter, and querying for multiple zipcode boundaries with one API call.
If you have any other questions or concerns please do not hesitate to reach out to us via email support@boundaries-io.com