The Geofence is intended to provide constraints for
API user accounts. An account with geofenced privileges
cannot execute services if input geographies fall outside of the user account
geofence constraints. Geofence limits the use of underlying datasets to specific
areas defined by the geofence constraints.
Geofence Rules and Limitations
- Geofences can be specified as a list of ZIP codes or a list of County FIPS codes. However, they can't be specified as both.
- If geographic areas are discontinuous then the geofence is applied as specified.
- Geofences specified by County FIPS are mapped to all ZIP codes that intersect the selected counties. Therefore, users might get a slightly larger area if a ZIP Code spans a county boundary.
- Analysis origins of simple and drive time rings are tested for intersection with the list of ZIP code areas before completing operations which take point geometries as input.
- The centroids of custom polygon areas are tested for intersection with the list of ZIP code areas before completing operations which take area geometries as input.
- The requested operation will not be completed if any ring analysis origin or custom polygon centroid falls outside of the geofenced ZIP Code areas associated with the user account.
- Geofence doesn't affect where you can map or geocode.
Below are geofence boundaries of an account with API geofenced to Douglas County, Kansas.
Geofence boundaries are enlarged in order to preserve the entire area of each ZIP code which intersects the geofenced area.
Listed below are ZIP Codes within the geofence boundaries.
These are Census Tracts within the geofence boundaries.