HERE Map Attributes API

HERE Map Attributes API — 23 operation(s) across 20 path(s), OpenAPI 3.0.2 version 8.3.3, harvested verbatim from the HERE developer documentation. Simple and fast access to the rich HERE Map content Note: Support for custom map data and custom routing is deprecated.

Operations 23

GET /v8/maps/attributes Simple and fast access to the rich HERE Map Content #
POST /v8/maps/attributes Simple and fast access to the rich HERE Map Content #
GET /v8/maps/attributes/segments Map Attributes for individual segments. #
POST /v8/maps/attributes/segments Map Attributes for individual segments (POST). #
POST /v8/maps/upload Import Geometries in a WKT or Shape File - deprecated, use HERE Geofencing API #
POST /v8/maps/modify Modify Geometries in Existing Layers - deprecated, use HERE Geofencing API #
GET /v8/maps/routeisoline Retrieve the POIs that are reachable within a certain time or distance from the main route #
GET /v8/maps/list List available map (public/private/both) regions/releases available to the app. #
GET /v8/maps/list.html List all maps (public/private/both) available to the app in HTML format. #
GET /v8/maps/layers/list List the available map layers (public/private/both) in JSON format. To see only the layers of a given map region, like Postal Code Boundaries or WEU, then specify it as map 'region #
GET /v8/maps/layers/list.html List the available map layers (public/private/both) in HTML format. To see only the layers of a given map region, like Postal Code Boundaries or WEU, then specify it as map 'region #
GET /v8/maps/layers/doc Show the layer documentation for a specific layer (public/private) in JSON format. Public layer documentation list the attributes and corresponding official attribute description, #
GET /v8/maps/layers/doc.html Show the layer documentation for a specific layer (public/private) in HTML format. Public layer documentation list the attributes and corresponding official attribute description, #
GET /v8/maps/layers/attributes List the layer attributes across all layers #
GET /v8/maps/layers/attributes.html List the layer attributes across all layers #
GET /v8/maps/indexes List available layer indexes #
GET /v8/maps/indexes.html List available layer indexes #
GET /v8/maps/index Tile IDs containing a given value #
GET /v8/maps/delete Delete some of my Geometry Layers. To delete complete maps and overlays, leave the layerNames field in parameter 'id' empty - deprecated, use HERE Geofencing API. #
GET /v8/maps/content.html Landing page for inline documentation #
GET /v8/maps/serviceconfiguration Service parameter boundary values #
GET /v8/maps/attributes/path Map Attributes along a route path. #
POST /v8/maps/attributes/path Map Attributes along a route path (POST). #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/here-map-attributes-v1"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

here-map-attributes-v1-openapi.json Raw ↑
{"openapi":"3.0.2","info":{"title":"Map Attributes API","description":"Simple and fast access to the rich HERE Map content<br><br/><strong>Note: Support for custom map data and custom routing is deprecated.</strong>","termsOfService":"https://developer.here.com/terms-conditions","license":{"name":"HERE Documentation License","url":"https://legal.here.com/en-gb/terms/documentation-license"},"version":"8.3.3"},"externalDocs":{"description":"The Developer guide and Release notes are available here.","url":"https://www.here.com/docs/category/map-attributes"},"servers":[{"url":"https://smap.hereapi.com","description":"Generated server url"}],"security":[{"apiKey":[]},{"bearerTokenAuth":[]}],"paths":{"/v8/maps/attributes":{"get":{"tags":["Map Attributes V8"],"summary":"Simple and fast access to the rich HERE Map Content","description":"Simple and fast access to the rich HERE Map Content","operationId":"Map Attributes API v8GetMapAttributes","parameters":[{"name":"app_id","in":"query","required":false,"schema":{"type":"string"}},{"name":"app_code","in":"query","required":false,"schema":{"type":"string"}},{"name":"mapName","in":"query","description":"map name. Optional for public HERE maps and for private BYOD maps. If not specified, the content of all maps containing the requested layer(s) is retrieved","required":false,"schema":{"type":"string"}},{"name":"layers","in":"query","description":"Comma separated list of layers to be searched. Layer names are not case sensitive. Both custom layers and Map Attribute core map layers are supported. Map Attribute layers divided by functional class, like ROAD_GEOM_FC1 ... FC5 can be selected by N, e.g. ROAD_GEOM_FCN. The maximum length of a layer name and the permitted characters can be looked up up in the service via v8/maps/serviceconfiguration. Via the attributes parameter only certain column attributes from a layer can be returned.","required":true,"schema":{"type":"string"}},{"name":"in","in":"query","description":"Spatial filtering. Supported are bbox, proximity, tile, corridor and all (full layer). \r\nThe format is &in=all or \r\n&in=bbox:{west longitude},{south latitude},{east longitude},{north latitude} or \r\n&in=proximity:latitude,longitude;r={radius} or \r\n&in=tile:{comma separated list of tile ids. The number of tile ids must match with the number of layers.} or \r\n&in=corridor:{comma separated WGS84 degree coordinates of corridor, for example:latitude 1,longitude 1,latitude 2,longitude 2 / encoded polyline string from Routing v8 response/ routeHandle string from Routing v8 response};r={radius}[;type=geoCoordinate(gc)/encodedPolyline(ep)/routeHandle(rh) }.\r\n When using routeHandle for corridor search an access token or apikey used for the router v8 service should be specified as Authorization header, else request will fail.","required":false,"schema":{"type":"string"}},{"name":"filter","in":"query","description":"A SQL expression being evaluated for each geometry being returned from the specified layer listing. Columns value for the geometry are available as defined variables. When specified, only geometries where expression evaluates to true will be returned. Supported SQL filter operators are: '=', '!=', '>', '<', 'AND', 'OR', 'LIKE'. Example: filter=RATING > 3 AND NAME != 'MyPlace23' AND NAME LIKE 'FOOD%'. Parameter value must be url encoded when using special characters. This filter expression is applied to all geometries, so it can become slow for big layers. To avoid service overload, filter expressions must not exceed 100 characters of text.\nNote:\n1. The filter expression is applied to all objects across all specified layers. Therefore, it is most likely to work as intended when a single layer is requested.\n2. The filter expression is not compatible with tile search. Tile search only allows filtering results based on attribute columns. Column filtering can be used to reduce response size.","required":false,"schema":{"type":"string","default":""}},{"name":"link2stabletopologyid","in":"query","description":"When set to 1 then stable topology ids are returned in the response. The default value is 1.","required":false,"schema":{"type":"string","default":"1"}},{"name":"release","in":"query","description":"Map release quarter, e.g. 2015Q4, 161J0, 16153 or LATEST (= default) for the latest available map release quarter. Specifying a map release is strongly discouraged, because there is no guarantee how long old map releases are available, hence applications that specify a release might stop working when the release gets retired. To choose a (nearest to) specific snapshot of the live traffic speed record or archived weather layer, a UNIX timestamp (number of milliseconds since 1970) or a url encoded date in 2017-12-01T17:30:00+01:00 format can be passed.","required":false,"schema":{"type":"string"}},{"name":"meta","in":"query","description":"When set to 1 then meta info is returned in the response. The default value is 1.","required":false,"schema":{"type":"string","default":"1"}},{"name":"attributes","in":"query","description":"Semicolon separated list of column names (in uppercase) to specify which attributes shall appear in the result. If the request specifies several layers, then pass this for each layer, as a comma separated list. Default = all. F.e. if layers=LINK_ATTRIBUTE2_FCn,LINK_ATTRIBUTE_FCn,ROAD_GEOM_FCn are requested, then the columns can be restricted to only following attributes=PARKING_LOT_ROAD;CARPOOL_ROAD,PAVED;PRIVATE,BRIDGE;TUNNEL. Parking lot and carpool road are from layer LINK_ATTRIBUTE2_FCn, paved and private from LINK_ATTRIBUTE_FCn and bridge, tunnel from ROAD_GEOM_FCn layer.","required":false,"schema":{"type":"string"}},{"name":"transportMode","in":"query","description":"Mode of transport to be used for the route calculation: car, truck, pedestrian. Required when routeHandle is used to retrieve attributes in corridor, please specify the same transportMode which was used to get the route handle from v8 Routing API.","required":false,"schema":{"type":"string"}},{"name":"count","in":"query","description":"The number of geometries in the response. If more geometries satisfy the search/filter criteria, they will be suppressed. It is undefined, which of the matching geometries are returned, unless this parameter is used together with offset, which sorts the results set by geometry id.\nParameter can be a single value that applies to all layers, or a comma separated list equal in number to the number of layers specified in layer_id parameter.\nThe maximum number of records supported within a single request can be looked up in the v8/maps/serviceconfiguration endpoint.\nThis parameter can only be used with &in=all filter to download either the custom layers or public static layers.","required":false,"schema":{"type":"string"}},{"name":"offset","in":"query","description":"To paginate huge responses, this parameter specifies the lowest geometry id to be returned. If geometry ids are not known, then retrieve the first page using zero, and to retrieve subsequent pages then request highest geometry of current page + 1 (it doesn't matter whether this geometry id actually exists or not). Use this parameter together with count.\nParameter can be a single value that applies to all layers, or a comma separated list equal in number to the number of layers specified in layer_id parameter.\nThis parameter can only be used with &in=all filter to download either the custom layers or public static layers.","required":false,"schema":{"type":"string"}},{"name":"acceptMissingLayers","in":"query","description":"Optional. If this parameter is set to true, user will get list of geometries from available layers, even if some of the requested layers are missing. If none of the requested layers are found, service returns empty list.","required":false,"schema":{"type":"string"}},{"name":"geom","in":"query","description":"local, full or none. Specifies the geometry representation in the result. Default = local. Local geometry is used for map display purposes, returning geometry pieces that cover the given search radius, bounding box or corridor polygon. Full geometry is used for interactive editing, where the original geometry is required. Full geometry can only be retrieved for custom layers, for map  None is used for applications like geofencing, which most of the time want to know only the ids of the geofence points/lines polygons they are in or near.","required":false,"schema":{"type":"string","default":"local"}},{"name":"ownerAppId","in":"query","description":"Owner app_id that was used to upload a layer. It is mandatory when a granted app_id is used to access the layer.","required":false,"schema":{"type":"string"}},{"name":"apiKey","in":"query","description":"A key generated specifically to authenticate API requests. For more information on how to get an API key, see https://developer.here.com/documentation/identity-access-management/dev_guide/index.html .\nOther authentication options are Bearer token, see https://developer.here.com/documentation/identity-access-management/dev_guide/index.html or app_id with app_code for backward compatibility.","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","content":{"application/json;charset=UTF-8":{"schema":{"$ref":"#/components/schemas/MapAttributesV8Response"}}}}}},"post":{"tags":["Map Attributes V8"],"summary":"Simple and fast access to the rich HERE Map Content","description":"Simple and fast access to the rich HERE Map Content","operationId":"Map Attributes API v8GetMapAttributes_1","parameters":[{"name":"app_id","in":"query","required":false,"schema":{"type":"string"}},{"name":"app_code","in":"query","required":false,"schema":{"type":"string"}},{"name":"mapName","in":"query","description":"map name. Optional for public HERE maps and for private BYOD maps. If not specified, the content of all maps containing the requested layer(s) is retrieved","required":false,"schema":{"type":"string"}},{"name":"layers","in":"query","description":"Comma separated list of layers to be searched. Layer names are not case sensitive. Both custom layers and Map Attribute core map layers are supported. Map Attribute layers divided by functional class, like ROAD_GEOM_FC1 ... FC5 can be selected by N, e.g. ROAD_GEOM_FCN. The maximum length of a layer name and the permitted characters can be looked up up in the service via v8/maps/serviceconfiguration. Via the attributes parameter only certain column attributes from a layer can be returned.","required":true,"schema":{"type":"string"}},{"name":"in","in":"query","description":"Spatial filtering. Supported are bbox, proximity, tile, corridor and all (full layer). \r\nThe format is &in=all or \r\n&in=bbox:{west longitude},{south latitude},{east longitude},{north latitude} or \r\n&in=proximity:latitude,longitude;r={radius} or \r\n&in=tile:{comma separated list of tile ids. The number of tile ids must match with the number of layers.} or \r\n&in=corridor:{comma separated WGS84 degree coordinates of corridor, for example:latitude 1,longitude 1,latitude 2,longitude 2 / encoded polyline string from Routing v8 response/ routeHandle string from Routing v8 response};r={radius}[;type=geoCoordinate(gc)/encodedPolyline(ep)/routeHandle(rh) }.\r\n When using routeHandle for corridor search an access token or apikey used for the router v8 service should be specified as Authorization header, else request will fail.","required":false,"schema":{"type":"string"}},{"name":"filter","in":"query","description":"A SQL expression being evaluated for each geometry being returned from the specified layer listing. Columns value for the geometry are available as defined variables. When specified, only geometries where expression evaluates to true will be returned. Supported SQL filter operators are: '=', '!=', '>', '<', 'AND', 'OR', 'LIKE'. Example: filter=RATING > 3 AND NAME != 'MyPlace23' AND NAME LIKE 'FOOD%'. Parameter value must be url encoded when using special characters. This filter expression is applied to all geometries, so it can become slow for big layers. To avoid service overload, filter expressions must not exceed 100 characters of text.\nNote:\n1. The filter expression is applied to all objects across all specified layers. Therefore, it is most likely to work as intended when a single layer is requested.\n2. The filter expression is not compatible with tile search. Tile search only allows filtering results based on attribute columns. Column filtering can be used to reduce response size.","required":false,"schema":{"type":"string","default":""}},{"name":"link2stabletopologyid","in":"query","description":"When set to 1 then stable topology ids are returned in the response. The default value is 1.","required":false,"schema":{"type":"string","default":"1"}},{"name":"release","in":"query","description":"Map release quarter, e.g. 2015Q4, 161J0, 16153 or LATEST (= default) for the latest available map release quarter. Specifying a map release is strongly discouraged, because there is no guarantee how long old map releases are available, hence applications that specify a release might stop working when the release gets retired. To choose a (nearest to) specific snapshot of the live traffic speed record or archived weather layer, a UNIX timestamp (number of milliseconds since 1970) or a url encoded date in 2017-12-01T17:30:00+01:00 format can be passed.","required":false,"schema":{"type":"string"}},{"name":"meta","in":"query","description":"When set to 1 then meta info is returned in the response. The default value is 1.","required":false,"schema":{"type":"string","default":"1"}},{"name":"attributes","in":"query","description":"Semicolon separated list of column names (in uppercase) to specify which attributes shall appear in the result. If the request specifies several layers, then pass this for each layer, as a comma separated list. Default = all. F.e. if layers=LINK_ATTRIBUTE2_FCn,LINK_ATTRIBUTE_FCn,ROAD_GEOM_FCn are requested, then the columns can be restricted to only following attributes=PARKING_LOT_ROAD;CARPOOL_ROAD,PAVED;PRIVATE,BRIDGE;TUNNEL. Parking lot and carpool road are from layer LINK_ATTRIBUTE2_FCn, paved and private from LINK_ATTRIBUTE_FCn and bridge, tunnel from ROAD_GEOM_FCn layer.","required":false,"schema":{"type":"string"}},{"name":"transportMode","in":"query","description":"Mode of transport to be used for the route calculation: car, truck, pedestrian. Required when routeHandle is used to retrieve attributes in corridor, please specify the same transportMode which was used to get the route handle from v8 Routing API.","required":false,"schema":{"type":"string"}},{"name":"count","in":"query","description":"The number of geometries in the response. If more geometries satisfy the search/filter criteria, they will be suppressed. It is undefined, which of the matching geometries are returned, unless this parameter is used together with offset, which sorts the results set by geometry id.\nParameter can be a single value that applies to all layers, or a comma separated list equal in number to the number of layers specified in layer_id parameter.\nThe maximum number of records supported within a single request can be looked up in the v8/maps/serviceconfiguration endpoint.\nThis parameter can only be used with &in=all filter to download either the custom layers or public static layers.","required":false,"schema":{"type":"string"}},{"name":"offset","in":"query","description":"To paginate huge responses, this parameter specifies the lowest geometry id to be returned. If geometry ids are not known, then retrieve the first page using zero, and to retrieve subsequent pages then request highest geometry of current page + 1 (it doesn't matter whether this geometry id actually exists or not). Use this parameter together with count.\nParameter can be a single value that applies to all layers, or a comma separated list equal in number to the number of layers specified in layer_id parameter.\nThis parameter can only be used with &in=all filter to download either the custom layers or public static layers.","required":false,"schema":{"type":"string"}},{"name":"acceptMissingLayers","in":"query","description":"Optional. If this parameter is set to true, user will get list of geometries from available layers, even if some of the requested layers are missing. If none of the requested layers are found, service returns empty list.","required":false,"schema":{"type":"string"}},{"name":"geom","in":"query","description":"local, full or none. Specifies the geometry representation in the result. Default = local. Local geometry is used for map display purposes, returning geometry pieces that cover the given search radius, bounding box or corridor polygon. Full geometry is used for interactive editing, where the original geometry is required. Full geometry can only be retrieved for custom layers, for map  None is used for applications like geofencing, which most of the time want to know only the ids of the geofence points/lines polygons they are in or near.","required":false,"schema":{"type":"string","default":"local"}},{"name":"ownerAppId","in":"query","description":"Owner app_id that was used to upload a layer. It is mandatory when a granted app_id is used to access the layer.","required":false,"schema":{"type":"string"}},{"name":"apiKey","in":"query","description":"A key generated specifically to authenticate API requests. For more information on how to get an API key, see https://developer.here.com/documentation/identity-access-management/dev_guide/index.html .\nOther authentication options are Bearer token, see https://developer.here.com/documentation/identity-access-management/dev_guide/index.html or app_id with app_code for backward compatibility.","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","content":{"application/json;charset=UTF-8":{"schema":{"$ref":"#/components/schemas/MapAttributesV8Response"}}}}}}},"/v8/maps/attributes/segments":{"get":{"tags":["Map Attributes V8"],"summary":"Map Attributes for individual segments.","description":"The segments endpoint can be used to enrich multiple unconnected segments with HERE Map content attributes.\n\nNote: We recommend using POST requests for large payloads, as GET requests may be constrained by request-line length limits imposed by load balancers.","operationId":"Map Attributes API v8GetMapAttributesForMultiSegment","parameters":[{"name":"app_id","in":"query","required":false,"schema":{"type":"string"}},{"name":"app_code","in":"query","required":false,"schema":{"type":"string"}},{"name":"mapName","in":"query","description":"Optional. Default: For public HERE maps all maps/regions containing the layer are returned, for private BYOD maps the layers from the DEFAULT map are returned","required":false,"schema":{"type":"string"}},{"name":"attributes","in":"query","description":"Comma separated list of PDE layer names, to get link attributes along the route. Only link attribute layers (roughly those ending in _FC1, _FC2 ... ) are supported. Specify FCn to get the layers of all functional classes. Behind each layer name attributes can be listed, or (*) to get all. Example: &attributes=ROAD_GEOM_FCn(TUNNEL), SPEED_LIMITS_FCn (FROM_REF_SPEED_LIMIT, TO_REF_SPEED_LIMIT), ADAS_ATTRIB_FCn (SLOPES). A maximum of 32 layers can be requested per request.","required":false,"schema":{"type":"string"}},{"name":"segmentRefs","in":"query","description":"Semicolon separated list of one or multiple disconnected topology segment references. Format of a SegmentRef is [Segment Identifier:]Segment Ref Id#Start Offset[..End Offset][,LAT,LON][,Remaining Time On Route,Functional Class]. Please use here:xs1:segment as the segment identifier for Japan segmentRefs and here:cm:segment for segmentRefs from rest of the world.  The input is typically retrieved from the Geocoding&Search (Reverse Geocoding) API. A maximum of 64 segment references can be requested per request.","required":false,"schema":{"type":"string"}},{"name":"apiKey","in":"query","description":"A key generated specifically to authenticate API requests. For more information on how to get an API key, see https://developer.here.com/documentation/identity-access-management/dev_guide/index.html .\nOther authentication options are Bearer token, see https://developer.here.com/documentation/identity-access-management/dev_guide/index.html or app_id with app_code for backward compatibility.","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","content":{"application/json;charset=UTF-8":{"schema":{"$ref":"#/components/schemas/MapAttributesAlongPathResponse"}}}}}},"post":{"tags":["Map Attributes V8"],"summary":"Map Attributes for individual segments (POST).","description":"The segments endpoint can be used to enrich multiple unconnected segments with HERE Map content attributes. For POST requests, send the segmentRefs parameter in an application/x-www-form-urlencoded request body instead of the query string. Authentication `apiKey` must - and basic configuration parameters can remain in the query string.","operationId":"Map Attributes API v8GetMapAttributesForMultiSegmentPost","parameters":[{"name":"app_id","in":"query","required":false,"schema":{"type":"string"}},{"name":"app_code","in":"query","required":false,"schema":{"type":"string"}},{"name":"mapName","in":"query","description":"Optional. Default: For public HERE maps all maps/regions containing the layer are returned, for private BYOD maps the layers from the DEFAULT map are returned","required":false,"schema":{"type":"string"}},{"name":"attributes","in":"query","description":"Comma separated list of PDE layer names, to get link attributes along the route. Only link attribute layers (roughly those ending in _FC1, _FC2 ... ) are supported. Specify FCn to get the layers of all functional classes. Behind each layer name attributes can be listed, or (*) to get all. Example: &attributes=ROAD_GEOM_FCn(TUNNEL), SPEED_LIMITS_FCn (FROM_REF_SPEED_LIMIT, TO_REF_SPEED_LIMIT), ADAS_ATTRIB_FCn (SLOPES). A maximum of 32 layers can be requested per request.","required":false,"schema":{"type":"string"}},{"name":"apiKey","in":"query","description":"A key generated specifically to authenticate API requests. For more information on how to get an API key, see https://developer.here.com/documentation/identity-access-management/dev_guide/index.html .\nOther authentication options are Bearer token, see https://developer.here.com/documentation/identity-access-management/dev_guide/index.html or app_id with app_code for backward compatibility.","schema":{"type":"string"}}],"requestBody":{"description":"Segment references sent as an application/x-www-form-urlencoded form field instead of a query parameter, to keep the request line within length limits.","content":{"application/x-www-form-urlencoded":{"schema":{"type":"object","properties":{"segmentRefs":{"type":"string","description":"Semicolon separated list of one or multiple disconnected topology segment references. Format of a SegmentRef is [Segment Identifier:]Segment Ref Id#Start Offset[..End Offset][,LAT,LON][,Remaining Time On Route,Functional Class]. Please use here:xs1:segment as the segment identifier for Japan segmentRefs and here:cm:segment for segmentRefs from rest of the world.  The input is typically retrieved from the Geocoding&Search (Reverse Geocoding) API. A maximum of 64 segment references can be requested per request."}}},"examples":{"segmentRefs":{"description":"segmentRefs","value":"segmentRefs=$1:87628529#0.725739..0.725739;$1:89921205#0..0.780687"}}}}},"responses":{"200":{"description":"OK","content":{"application/json;charset=UTF-8":{"schema":{"$ref":"#/components/schemas/MapAttributesAlongPathResponse"}}}}}}},"/v8/maps/upload":{"post":{"tags":["Map Attributes V8"],"summary":"Import Geometries in a WKT or Shape File - deprecated, use HERE Geofencing API","description":"Import polygons, polylines or points in WKT (Wellknown Text) or Shapefile format geometries using an HTTP POST request, or import WKT geometries using HTTP GET. A layer can contain only one geometry type - polygons, polylines or points, but not a mix of different types. After the response there is a delay of several seconds to compile, store and make the geometries available in the service. <br><br/> <strong> Note: The feature to import custom layers is deprecated. It will be only supported in self-hosting in maintenance mode. </strong>","operationId":"Map Attributes API v8UploadPost","parameters":[{"name":"layerId","in":"query","description":"Unique identifier for the layer in the format {app_id}.{mapName}.{layerName}. app_id: app_id of the project creating the layer; mapName: the map into which the layer is uploaded, default = upload the layer into the app_id's default map; layerName:  Name of layer to create/replace, the maximum length of a layer name and the permitted characters can be looked up up in the service via /serviceconfiguration.json.","required":true,"schema":{"type":"string"}},{"name":"level","in":"query","description":"Specify tile size for the database for performance optimization, if not specified default tile size of 12 is used.","required":false,"schema":{"type":"integer","format":"int32","default":12}},{"name":"storage","in":"query","description":"Either updatable or readonly. Default = updatable.","required":false,"schema":{"type":"string","default":"updatable"}},{"name":"wktQuote","in":"query","description":"Specify the quote character to use. Default = \" (double quotes). Specifying NONE disables quotes.","required":false,"schema":{"type":"string","default":"\""}},{"name":"indexColumns","in":"query","description":"Specify columns of the layer that should be indexed. Column name is followed by semi-colon(;) and indexing type. Supported indexing type are: order(o), text(t) or both order,text(o,t). Columns are separated by pipe(|). Example &indexColumns=POI_ID;order|CAT_ID;text|ADMIN_IDS;order,text","required":false,"schema":{"type":"string"}},{"name":"grantedAppIds","in":"query","description":"Comma separated list of app_ids which also have (per default read+export) access to this layer (specifying ownerAppId.mapName.layerName). Example &granted_app_ids=otherAppId1,otherAppId2","required":false,"schema":{"type":"string"}},{"name":"file","in":"query","description":"WKT file content","required":true,"style":"form","schema":{"type":"string","format":"binary"}},{"name":"apikey","in":"query","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"$ref":"#/components/schemas/LayerUploadResponse"}}}}}}},"/v8/maps/modify":{"post":{"tags":["Map Attributes V8"],"summary":"Modify Geometries in Existing Layers - deprecated, use HERE Geofencing API","description":"Modify geometries using an HTTP GET or POST request. After the response there is a delay of several seconds to compile, store and make the modified geometries available in the service.\r\n Note: The level (tile grid size) of the layer can only be changed by uploading the whole layer, not as a modification operation. <br><br/> <strong> Note: The feature to modify custom layers is deprecated. It will be only supported in self-hosting in maintenance mode. </strong>","operationId":"Map Attributes API v8ModifyPost","parameters":[{"name":"layerId","in":"query","description":"Unique identifier for the layer in the format {app_id}.{mapName}.{layerName}. app_id: app_id of the project modifying the layer; mapName: the map into which the layer is uploaded, default = upload the layer into the app_id's default map; layerName:  Name of layer to modify, the maximum length of a layer name and the permitted characters can be looked up up in the service via /serviceconfiguration.json.","required":true,"schema":{"type":"string"}},{"name":"action","in":"query","description":"append, update or delete. Geometries are identified by their geometry_id column value. For append, the geometries must not exist yet and will be added. For update, the geometries must exist and will be replaced. All column values must be specified, not only the changes. For update and delete, the columns must not change - names, sequence orders and type must be identical. For delete, the geometries must exist and will be replaced. Only the geometry_id column is required.","required":true,"schema":{"type":"string"}},{"name":"wktQuote","in":"query","description":"Specify the quote character to use. Default = \" (double quotes). Specifying NONE disables quotes.","required":false,"schema":{"type":"string","default":"\""}},{"name":"ownerAppId","in":"query","description":"Owner app_id that was used to upload a layer. It is mandatory when a granted app_id is used to access the layer.","required":false,"schema":{"type":"string"}},{"name":"file","in":"query","description":"WKT file content","required":true,"style":"form","schema":{"type":"string","format":"binary"}},{"name":"apikey","in":"query","schema":{"type":"string"}}],"requestBody":{"content":{"application/json":{"schema":{"type":"string","format":"byte"}}}},"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"$ref":"#/components/schemas/LayerModifyResponse"}}}},"409":{"description":"Modify Conflict","content":{"application/json":{"schema":{"$ref":"#/components/schemas/LayerModifyResponse"}}}}}}},"/v8/maps/routeisoline":{"get":{"tags":["Map Attributes V8"],"summary":"Retrieve the POIs that are reachable within a certain time or distance from the main route","description":"Retrieve the POIs that are reachable within a certain time or distance from the main route","operationId":"Map Attributes API searchRouteIsolineV8","parameters":[{"name":"app_id","in":"query","required":false,"schema":{"type":"string"}},{"name":"app_code","in":"query","required":false,"schema":{"type":"string"}},{"name":"layer_ids","in":"query","description":"Comma separated list of layer IDs to be searched. Layer names are not case sensitive. Both custom layers and PDE map layers are supported. PDE layers divided by functional class, like ROAD_GEOM_FC1 ... FC5 can be selected by N, e.g. ROAD_GEOM_FCN. Layers must have a LINK_ID column. If a customer doesn't have a LINK_ID column, customers can create it using the Geocoder, Reverse Geocoder or RME. The maximum length of a layer name and the permitted characters can be looked up up in the service via v8/maps/serviceconfiguration","required":false,"schema":{"type":"string"}},{"name":"attributes","in":"query","description":"List of comma separated column names to specify which attributes shall appear in the result. Column names are not case sensitive. Default = all.","required":false,"schema":{"type":"string"}},{"name":"geom","in":"query","description":"local, full or none. Specifies the geometry representation in the result. Default = local. Local geometry is used for map display purposes, returning geometry pieces that cover the given search radius, bounding box or corridor polygon. Full geometry is used for interactive editing, where the original geometry is required. None is used for applications like geofencing, which most of the time want to know only the ids of the geofence points/lines polygons they are in or near.","required":false,"schema":{"type":"string","default":"local","enum":["local","full","none"]}},{"name":"max_detour_distance","in":"query","description":"Either max_detour_distance or max_detour_time must be specified. Maximum travel distance in meter away from the route to reach the map object. This is one way, from the junction that leaves the route until to the map object. The distance to get back onto the route is not considered here.","required":false,"schema":{"type":"number","format":"double"}},{"name":"max_detour_time","in":"query","description":"Either max_detour_time or max_detour_distance\tMaximum travel time in seconds away from the route to reach the map object. This is one way, from the junction that leaves the route until to the map object. The time to get back onto the route is not considered here.","required":false,"schema":{"type":"number","format":"double"}},{"name":"storage","in":"query","description":"Optional, default searches in both. Specify 'updatable' or 'readonly', how you uploaded the layer.","required":false,"schema":{"type":"string","default":"updatable"}},{"name":"mapMatchRadius","in":"query","description":"Maximum adaptive map match search radius [meter]. Will be applied to each way point. If given it overrides waypoints' transitRadius values and the default maximum adaptive search radius. For routing, default 1600. Limit 5000.","required":false,"schema":{"type":"string"}},{"name":"trailerType","in":"query","description":"Trailer ty

# --- truncated at 32 KB (103 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/here/refs/heads/main/openapi/here-map-attributes-v1-openapi.json