Corridor Polygon Search
Search for custom geometries within a buffer along a route specified by a sequence of coordinates.
The number of geometries in the response should not exceed 1000. Exceeding one of the limits results in an error response. If an application needs more results returned then please contact technical customer support to work on a solution to reduce this.
|app_id||Yes||A URL-safe encoded string obtained during the application registration. See Acquiring Credentials for information on getting credentials.|
|app_code||Yes||A URL-safe encoded string obtained during the application registration. See Acquiring Credentials for information on getting credentials.|
|layer_ids||Yes||Comma separated list of layer IDs to be searched. Layer names are not case sensitive. The maximum length of a layer name and the permitted characters can be lookup up in the service via |
|corridor||Either corridor or route_id|| |
The WGS84 degree coordinates of the polyline used as corridor center line.
latitude 1,longitude 1;latitude 2,longitude 2;...
|Either route_id or corridor||Yes|| |
A route_id obtained from a previous Router call. This route_id will be turned into a corridor polyline.
|radius||Yes||The buffer search radius in meters.All geometries overlapping the corridor polygon will be returned.|
|geom||No|| local, full or none. Specifies the geometry representation in the result. Default = local. |
Columns value for the geometry are available as defined variables.
When specified, only geometries where expression evaluates to true will be returned.
Example: filter=RATING > 3 && NAME != 'MyPlace23' && NAME.startsWith('Food')
Parameter value must be url encoded when using special characters.
This filter expression is applied after the spatial filtering, hence only to few geometries. Only for the
|callback||No||Specifies the function used to wrap the JSON response.|
To see an example of a corridor search response when you use coordinates, see Corridor Search for Custom Locations.