The CRC algorithm used to calculate the checksum for the partitions in this layers
Identifies whether the data is compressed.
The MIME type of the data is stored in this layer.
The name of the partitioning scheme for the layer.
The digest algorithm used to calculate the checksum for the partitions in this layer. If specified, you can assume that all partitions in the layer, at every version, were calculated using this algorithm. Note that it is the responsibility of the data publisher to use this algorithm to calculate partition checksums. The HERE platform does not verify that the specified algorithm was actually used.
The type of data availability that this layer provides.
The type of data availability that this layer provides
The layer creation timestamp.
A detailed description of the layer and what it contains. This information appears on the 'Overview' tab when you open a layer in the platform portal.
The HERE Resource Name (HRN) of the layer.
The ID to use when referring to this layer programmatically.
The display name for the layer.
A one-sentence summary of the layer. You can see this summary when you browse a list of layers on the platform portal.
The type of data availability that this layer provides
The name of the partitioning scheme for the layer.
The type of data availability that this layer provides.
Some keywords that help to find the layer when searching in the platform portal.
The expiry time in milliseconds for data in this layer. Data is automatically removed after the specified time limit has elapsed. For volatile layers the TTL value must be between 60000 (1 minute) and 604800000 (7 days). For stream layers the TTL value must be between 600000 (10 minutes) and 259200000 (72 hours).
The expiry time in hours for data in this layer. Data is automatically removed after the specified time limit has elapsed.
The type of data availability that this layer provides.
The type of data availability that this layer provides.
Checks whether a catalog with the specified HRN exists.
Creates a new catalog with the specified layers. The create catalog operation runs asynchronously. Once you've submitted the catalog for creation, you'll receive a randomly generated token that you can use to monitor the status of the operation.
Deletes a catalog and any layers within that catalog.
Deletes a layer of the catalog if it's of layerType 'index', 'volatile', or 'stream'. Other layerTypes
are currently not supported.
Disable automatic retired versions cleanup.
Gets the full catalog configuration for the requested catalog. The catalog configuration contains descriptive and structural information such as layer definitions and layer types.
Takes the randomly generated token that you receive when you submit a catalog for creation. You can use it to monitor the status of your request.
Lists all catalogs that your account has access to. To get access to a catalog, your administrator must associate this catalog in your HERE platform account. By default, the list provides summary data for each catalog such as the title, the configuration URL, and the resource type.
Modify some fields of the catalog. The existing HTTP PUT method only allows a complete replacement of a catalog configuration, HTTP PATCH method is used to modify some fields of existing catalog configuration. All fields are optional. Specify field value to modify it, not specified fields are ignored. To remove the field value use the null value. For more information, see RFC 7396 - JSON Merge Patch.
Modify some fields of the catalog layer. HTTP PATCH method is used to modify some fields of existing layer configuration. All fields are optional. Specify field value to modify it, not specified fields are ignored. To remove the field value use the null value. For more information see RFC 7396 - JSON Merge Patch.
Updates any descriptive and structural information in the catalog. To update a catalog, send a new version of your catalog configuration with the updated data and any required fields.
Generated using TypeDoc
List of billing tags a free-form tag which is used for grouping billing records together. If supplied, it must be between 4 - 16 characters, contain only alphanumeric ASCII characters [A-Za-z0-9].