This document introduces the Fleet Telematics Custom Locations and:
- explains key concepts
- provides examples
- documents resources and query parameters
- documents request and response structures and data types
For the terms and conditions covering this documentation, see the HERE Documentation License.
What Is the Fleet Telematics Custom Locations?
- CSV files using Wellknown Text (WKT) geometry
- Shapefile standard-compliant shapes
In addition to the REST service, the Fleet Telematics Custom Locations also provides a dashboard for users to manage their custom geometries: Custom Locations Admin (PRD). Custom Locations Admin (CIT).
Why Use the Fleet Telematics Custom Locations?
The table below lists the high level use cases for the Fleet Telematics Custom Locations.
|Store custom locations, lines and polygons||Store your own shapes and points of interest (POIs). In other words, you can create your own layer on top of the map. You can also use these shapes and POIs with other HERE Platform Extension APIs.|
|Find objects near a location||Search for custom or core map objects that are in air distance proximity a specific location.|
|Find objects within an area||Retrieve custom or core map objects within a given bounding box.|
|Find objects within a buffer along a route||Search for custom or map objects within a specified airline distance along a defined route.|
|Find objects reachable within a certain time or distance from a specific location||Search for custom or core map objects reachable within a limited driving time or driving distance from a given location. Create the required isoline polygons via HLP Router and store them in CLE.|
|Find objects reachable within a certain time or distance from the route||Search for all custom or core map objects that can be reached by departing from the route. Limit the detour time or distance from the route.|