This namespace contains classes related to the "Bring Your Own Data" use case of the HERE Fleet Telematics API.
It enables creation, modification, fetching and rendering of the custom data layers.
Classes
Members
-
The access permissions types which can be granted to other
app_ids.- See:
Properties:
Name Description READWRITEEXPORT -
The storage type of a custom data layer.
- See:
Properties:
Name Description READONLYUPDATABLE
Type Definitions
-
An object that contains access permissions for a data layer that are granted for a specified
app_id.- See:
Properties:
Name Type Description grantedAppIdstring The ID of the Application for which the permissions are specified.
permissionsArray.<!H.service.extension.customLocation.Permission> The access rights that are granted. An empty list means no permissions are granted.
-
A
LayerConfigis an object that contains a configuration for a custom data layer.Properties:
Name Type Argument Description layerIdstring The unique ID of the layer.
rowFilterH.service.extension.RowFilter <optional>
An optional function to filter out rows from the tile response. If defined, it must be a pure function.
rowFilterContextObject <optional>
The JavaScript execution context of the
rowFilterfunction. Thethiswithin therowFilterwill be the specified object. For performance reasons it is recommended that this object contains only the necessary information. Functions are not allowed.columnsArray.<string> <optional>
An optional list of column names to keep for each row. By default all columns are kept.
-
An object that contains meta information of a data layer.
"GEOMETRY_ID"This column must be specified as the second last column if theMetaInfois used to create a new data layerH.service.extension.customLocation.Service#createLayerIt represents the ID of a record (a.k.a. row) within a data layer."WKT"This column must be specified as the last column if theMetaInfois used to create a new data layerH.service.extension.customLocation.Service#createLayerIt represents the geometry data of a data record and must be always the last column. The backend stores this data formatted as a Well-Known-Text (WKT) string but the client API converts it automatically into a specific implementation of theH.geo.AbstractGeometryand vice versa.
Properties:
Name Type Description layerIdstring The id of the data layer. It must conform to the naming rules
/^[A-Z][A-Z0-9_]*$/.columnNamesArray.<string> The ordered list of names for the data layer's attribute columns. Each column name must conform to the naming rules
/^[A-Z][A-Z0-9_]*$/. A data layer has two special intrinsic columns which must be always specified:levelundefined | number The level of detail. It specifies the level were the tiles stored in the backend. If not defined, the default level of the backend is used (see API Reference for more details.
storageundefined | H.service.extension.customLocation.Storage The storage type of the data layer. It can be only set if the
MetaInfois used to create a new data layer (seeH.service.extension.customLocation.Service#createLayer). If not defined, the default storage type of the backend is used.grantsundefined | !Array.<!H.service.extension.customLocation.Grant> The settings to grant other
app_ids access the data layer. See API Reference fore more details.lastUpdateTimestampundefined | number A read-only property that provide the timestamp in ms (since Jan 01 1970 UTC) when the data layer was modified on the backend.
Example
myMetaInfo = { layerId: "MY_LAYER", columnNames: ["NAME", "ADDRESS", "GEOMETRY_ID", "WKT"] }