Look up FieldIDs for a given Point, Polygon or MultiPolygon.

This endpoint returns the fields intersecting input geometry, along with active BoundaryIDs.

It supports two types of inputs:

  1. Point

  2. Polygon (or MultiPolygon)

For #2 the ratio of overlap and the IoU score are added to the output.
Spatial search area limit is 25 km2.

GeoJSON input can be provided directly or encapsulated within the geometry of a GeoJSON Feature. Input must comply with ISO 19125.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
integer
≥ 0
Defaults to 0

Number of records to skip.

integer
1 to 100
Defaults to 50

Maximum number of records to return.

Body Params

GeoJSON object The coordinate reference system for all GeoJSON coordinates is a geographic coordinate reference system, using the World Geodetic System 1984 (WGS 84) datum, with longitude and latitude units of decimal degrees. This is equivalent to the coordinate reference system identified by the Open Geospatial Consortium (OGC) URN An OPTIONAL third-position element SHALL be the height in meters above or below the WGS 84 reference ellipsoid. In the absence of elevation values, applications sensitive to height or depth SHOULD interpret positions as being at local ground or sea level.

string
enum
required
Allowed:
coordinates
array of numbers
required
length between 2 and 3

Note: Global FieldID API allows 3 values to be provided but 3rd one is not used. GeoJSon fundamental geometry construct. A position is an array of numbers. There MUST be two or more elements. The first two elements are longitude and latitude, or easting and northing, precisely in that order and using decimal numbers. Altitude or elevation MAY be included as an optional third element. Implementations SHOULD NOT extend positions beyond three elements because the semantics of extra elements are unspecified and ambiguous. Historically, some implementations have used a fourth element to carry a linear referencing measure (sometimes denoted as "M") or a numerical timestamp, but in most situations a parser will not be able to properly interpret these values. The interpretation and meaning of additional elements is beyond the scope of this specification, and additional elements MAY be ignored by parsers.

coordinates*
Headers
string

Language and locale to return the response in

Responses

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json