Administrative Boundaries v1 · Admin Bounds
Before calling these endpoints, use a Geoscape Hub application with access to this API product. Authenticate with your Consumer Key in the Authorization header. See Authentication, Error Handling, Rate Limiting, and Attribution for shared integration guidance.
Required response fields must be present when their containing object is returned. Supply the documented request parameters when calling the endpoint.
Find by point
Authentication: Use your Consumer Key in the
Authorizationheader.
Return boundaries that intersect the supplied point.
- Supply at least one layer
- A layer with no result contributes no feature and adds
Layer '{layer}' not found.tomessages. The response remains200, including when all layers have no result - Set
excludeGeometry=truefor attributes only. Geometry then containscoordinates: [null, null]
See Boundary Layers for values and identifier fields.
Code
query Parameters
latitudeLatitude of the search point. Use decimal degrees for the default GDA94 input CRS.
longitudeLongitude of the search point. Use decimal degrees for the default GDA94 input CRS.
layersOne or more case-sensitive layer names in a single comma-separated query value, for example layers=localities,localGovernmentAreas. See Boundary Layers for meanings and primary identifiers.
excludeGeometryDefaults to true: return attributes with sentinel geometry coordinates: [null, null]. Set false to request polygon coordinates. SEIFA has no polygon geometry.
Headers
accept-crsResponse CRS, expressed as an angle-bracketed CRS URI. Defaults to GDA94 (EPSG:4283). For multiple URIs, optional ;q= values set preference. See CRS & GDA2020, the OGC specification, and quality values.
Content-CrsInput coordinate reference system as an angle-bracketed CRS URI. Defaults to GDA94 (EPSG:4283). See CRS & GDA2020.
Find by point › Responses
Boundary FeatureCollection. Missing layers are reported in messages and can leave features empty.
typemessagesInformation about requested layers with no returned features.
requestTimeStampResponse time as Unix seconds.
requestDateTimeUTC response time.
Point lookup: [longitude, latitude] in the input CRS. Identifier lookup: the supplied identifier string.
attributionAttribution text to retain when using the data.
Find by identifier
Authentication: Use your Consumer Key in the
Authorizationheader.
Return boundaries matching a case-sensitive primary feature PID. Use the primary PID, not a polygon PID. A feature can return several polygons.
- Supply at least one layer
- A layer with no result contributes no feature and adds
Layer '{layer}' not found.tomessages. The response remains200, including when all layers have no result - Set
excludeGeometry=truefor attributes only. Geometry then containscoordinates: [null, null]
See Boundary Layers for values and identifier fields.
Code
query Parameters
layersOne or more case-sensitive layer names in a single comma-separated query value, for example layers=localities,localGovernmentAreas. See Boundary Layers for meanings and primary identifiers.
identifierCase-sensitive primary feature PID from a returned boundary. See Boundary Layers for the field for each layer.
excludeGeometryDefaults to true: return attributes with sentinel geometry coordinates: [null, null]. Set false to request polygon coordinates. SEIFA has no polygon geometry.
Headers
accept-crsResponse CRS, expressed as an angle-bracketed CRS URI. Defaults to GDA94 (EPSG:4283). For multiple URIs, optional ;q= values set preference. See CRS & GDA2020, the OGC specification, and quality values.
Find by identifier › Responses
Boundary FeatureCollection for the supplied primary feature PID. Missing layers are reported in messages.
typemessagesInformation about requested layers with no returned features.
requestTimeStampResponse time as Unix seconds.
requestDateTimeUTC response time.
Point lookup: [longitude, latitude] in the input CRS. Identifier lookup: the supplied identifier string.
attributionAttribution text to retain when using the data.