Crea teamAggiungi la tua APIDocumenti
Accedi
Iscriviti
Rapid account: Boundaries-io

Boundaries-io / VanitySoft

Our API Is trusted by Industry leaders: Over the last five years, we were able to amass over 600+ clients across the United States, Canada, and the United Kingdom. From startups to large companies that are industry leaders in marketing, emergency response, insurance, and transportation. These companies trust and rely on our robust API for their solutions.

    Discussioni

    49
    Title
    		Created at (Click to sort ascending)
    A
    2
    		 Good morning, Canada,United Kingdom, Germany and the United States are the only countries currently supported. Countries that are on the road map to implement from existing client requests are : India and South Africa. please send us an email with a list if European countries you would like to have postal code level boundaries for. thanks! support@boundaries-io.com lun 2:27 13/2/23
    A
    2
    		 Hello, Where did you see the date of 2015? We will update asap. Our latest polygon update comes from September 2021 ZCTA files. If desired you can download the shapefiles used from the Census website below: https://www2.census.gov/geo/tiger/TIGER2021/ZCTA520/ Please let em know if you have any other questions or concerns. Also, if you have feature requests, we will be happy to review to put on our roadmap. Looking forward to having you as a client. Thanks! Dawn support@boundaries-io.com mar 9:51 22/3/22
    A
    7
    		 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 sab 2:15 19/3/22
    A
    1
    		 Hello, Our data store for Neighborhood is from the Zilow 2017 Neightborhood boundaries data dump. Though this contains nearly 17,000 neighborhood boundaries in over 650 U.S. cities others may overlap in our 'place' endpoint: **/rest/v1/public/boundary/place/within** mer 1:43 16/2/22
    A
    1
    		 Hello, We follow the best practice with limiting URL Length, which means a URL should never be longer than 2,048 character. What is your latitude, and longitude parameter value used when you receive a HTTP 414 error? you should probably truncate the values to a significant digit for example: },"params":{ "longitude":"-92.3629", "latitude":"34.6937" } and not something like which may results in the 414 error of URL limit. },"params":{ "longitude":"-92.36290000000000", "latitude":"34.6937000000000000" } we don't have a 'batch' result API endpoint, but it seems you can use the API but make sure its not to long that breaks the 2048 URL limit constraint. -Dawn support@boundaries-io.com mer 1:14 5/1/22
    A
    1
    		 Hello, Please use this list to obtain DMA regions: https://gist.github.com/boundaries-io/3dae796461784df4b308075df725c44c ven 1:52 3/12/21