v1
latestOpenAPI 3.0.12026-07-24110189356.6 KBconfig
Gets the details of a catalog
Gets the full catalog configuration for the requested catalog. The catalog configuration contains descriptive and structural information such as layer definitions and layer types.
get/catalogs/{catalogHrn}
Path parameters
catalogHrnstring required
The HERE Resource Name (HRN) of the catalog
Query parameters
billingTagstring
The billingTag parameter is an optional free-form tag that you can use to group billing records together. If supplied, it must be between 4 - 16 characters, contain only alpha/numeric ASCII characters [A-Za-z0-9]. Grouping billing records by billing tag will be available in future releases.
Response
OK
Example response
{
"id": "olp-traffic",
"hrn": "hrn:here:data:::olp-traffic",
"name": "Traffic Data",
"summary": "This catalog provides traffic flow and incidents information.",
"description": "The catalog provides aggregated information about traffic incidents, including the type and location of each traffic incident, status, start and end time, and other relevant data. This data is useful to dynamically optimize route calculations. It also provides access to real-time traffic flow data in including information on speed and congestion for specific regions. The catalog also contains additional data such as the geometry of the road segments in relation to the flow.",
"coverage": {
"adminAreas": [
"DE"
]
},
"owner": {
"creator": {
"id": "Mejk6DMxAq7kKI5lt2T2"
},
"organisation": {
"id": "HERE"
}
},
"tags": [
"Traffic",
"Flow",
"Speed"
],
"billingTags": [
"Cost-Center_1",
"Cost-Center_2"
],
"created": "2017-08-04T17:19:03.853Z",
"automaticVersionDeletion": {
"numberOfVersionsToKeep": 1,
"ttlDays": 3
},
"layers": [
{
"id": "traffic-incidents",
"hrn": "hrn:here:data:::olp-traffic:traffic-incidents",
"name": "Traffic Incidents",
"summary": "This layer provides aggregated information about traffic incidents.",
"description": "This layer provides aggregated information about traffic incidents, including the type and location of each traffic incident, status, start and end time, and other relevant data. This data is useful to dynamically optimize route calculations.",
"coverage": {
"adminAreas": [
"DE"
]
},
"schema": {
"hrn": "hrn:here:schema:::com.here.schema.rib:topology-geometry_v2:2.2.0"
},
"partitioningScheme": "heretile",
"partitioning": {
"scheme": "heretile",
"tileLevels": [
12
]
},
"contentType": "application/json",
"contentEncoding": "gzip",
"tags": [
"Traffic",
"Flow",
"Speed",
"Real-Time",
"Current"
],
"billingTags": [
"Cost-Center_1",
"Cost-Center_2"
],
"digest": "SHA-1",
"crc": "CRC-32C",
"volume": {
"volumeType": "durable"
},
"created": "2019-02-07T15:24:39.437810Z",
"layerType": "versioned",
"secureHandles": true,
"subsetRestrictions": true,
"versionedLayerProperties": {
"encryptionType": "hereEncryption"
}
}
],
"areaScheme": "hrn:here:areascheme::olp-here:default-countries",
"subsetRestrictions": true,
"version": 1
}