Getting incorrect data when using the search boundaries

I wrote a long response initially as I'm not a fan of the v2 boundary service (It is the Bing Maps boundary service that has been brought over to Azure Maps and is less than ideal for your scenario).

First off, it's important to note that the geocoder and the boundary services are independent of each other. The v2 boundary service will retrieve any boundary that intersects with the coordinate provided. This is good for hierarchy type searches, but can be error prone if a "display coordinate" (center point) is used for an area that has an irregular shape and thus the display coordinate does not overlap the boundary. Normally I would recommend using the V1 services when searching for a specific boundary since each boundary in that version has a unique ID that is returned by the geocoder. However, if you go down that path you will find none of the zip codes you provided will return a boundary ID, which indicates that it's not a data issue. Digging into this I found that these zip codes are "non deliverable zip codes" like PO boxes which have no area (multiple zip codes can exist in the same spot). Around 30% of US zip codes are like this. For example, the building that has a PO box will have a street address and zip code that aligns with the wider area it is in, while it may contain one or more zip codes for its boxes. These zip codes are points, and have no area. In the case of 75265, it is within the zip code area of 75208. I used this tool to verify: https://www.unitedstateszipcodes.org/ You can also us some tools on the USPS site, but they are less intuitive. Good similar discussion on this can be found here: https://gis.stackexchange.com/questions/22324/where-can-i-find-a-list-of-non-deliverable-zip-codes

I haven't found a free list of all PO Box zip codes, however, zip code tabulation areas (ZTCA) used by the US census, is a list of all zip codes that have a population. So, nearly every zip code you come across that isn't in that list, is most likely a non-area zip code like a PO box. So, you could do a check to see if your input zip code is in that list before deciding to try and get its boundary or not. You can get the latest list of ZCTA here: https://www.census.gov/geographies/reference-files/time-series/geo/gazetteer-files.html

There is also this project that looks to categorize the zip code types: https://github.com/MacHu-GWU/uszipcode-project

All that said, if this is for a business intelligence type app, note that zip codes are not great for that type of analysis (at least in the US). Zip code boundaries are not well-defined areas and you will find that the shape/area varies between map provides. Zip codes area's as per the postal service is a set of delivery routes (roads), and the area between roads is a "gray" area where approximations are used to determine the boundary lines. There are a ton of articles that go into more details on this topic. Here are a couple:

• https://carto.com/blog/zip-codes-spatial-analysis
• https://sunlightfoundation.com/2012/01/19/dont-use-zipcodes/

When I work with customers who are focused on BI type scenarios in the US, I typically direct them towards census tracts.

Hi Nilesh,

For the postal Code issue, can I get you to try https://samples.azuremaps.com/?search=boundaries&sample=search-for-boundaries with the codes that are failing for you? Are these also incorrect?

For the Texas "75365" example "https://tools.usps.com/zip-code-lookup.htm?citybyzipcode" says that is not a valid Zip so you may have a typo but for the others that sample returns polygons for me. Can you confirm what is incorrect regarding those?

Sincere thanks,

IoTGirl