Supported backends

This topic describes the backends that you can use with Kanzi Maps.

Mapbox backend

The Mapbox backend uses the HTTP Client provided by the generic Kanzi Maps backend library to access the Mapbox REST APIs.

A task in the IO execution context fetches data over HTTPS (if supported) from Mapbox servers. A task in the COMPUTE execution context takes the data and parses it.

Tile Fetcher and supported layers

Supported layers

Kanzi Maps supports these Mapbox layers:

Tile source	Supported layers and reference documentation
Mapbox Streets v8 mapbox.mapbox-streets-v8 (In map_settings.xml: <streets version="v8" />)	admin aeroway airport_label building housenum_label landuse landuse_overlay motorway_junction natural_label place_label poi_label road structure transit_stop_label water waterway https://docs.mapbox.com/data/tilesets/reference/mapbox-streets-v8/#layer-reference
Mapbox Streets v7 mapbox.mapbox-streets-v7 (In map_settings.xml: <streets version="v7" />)	admin aeroway airport_label barrier_line building country_label housenum_label landuse landuse_overlay marine_label motorway_junction mountain_peak_label place_label poi_label rail_station_label road road_label state_label water water_label waterway waterway_label https://docs.mapbox.com/data/tilesets/reference/legacy/mapbox-streets-v7/#layer-reference
Mapbox Terrain v2 mapbox.mapbox-terrain-v2	contour hillshade landcover https://docs.mapbox.com/data/tilesets/reference/mapbox-terrain-v2/#layer-reference
Mapbox Traffic v1 mapbox.mapbox-traffic-v1	traffic https://docs.mapbox.com/data/tilesets/reference/mapbox-traffic-v1/#layer-reference
mapbox.3d-buildings	building3d
Mapbox Terrain-RGB v1 mapbox.terrain-rgb	terrain3d raster (height map) layer https://docs.mapbox.com/data/tilesets/guides/access-elevation-data/#mapbox-terrain-rgb
Mapbox Satellite mapbox.satellite	satellite raster (texture) layer https://docs.mapbox.com/help/glossary/mapbox-satellite/

For information on the supported metadata, see the reference documentation linked to each list of layers.

Tiling scheme

The Mapbox backend uses TilingSchemeGoogle which is a Web Mercator based quad tree tiling scheme.

Router

Routing uses the Mapbox Directions REST API.

Geocoder

Reverse geocoding for Mapbox is implemented using the Mapbox Geocoding REST API.

Kanzi Maps makes a reverse geocoding query using a single WGS84 latitude-longitude coordinate, and parses the resulting GeoJSON response into a GeoFeature collection.

For more information see:

• Mapbox Geocoding API documentation

• Kanzi Maps GeoFeature API documentation

HERE OLP Edge backend

The HERE OLP Edge backend uses Here SDK for fetching OMV vector tile map data optimized for rendering. The vector tile format uses the same ProtoBuf binary format as that specified by Mapbox vector tile specification, but the layer and metadata names are different from those used by the Mapbox backend.

Tile fetcher

The tile fetcher uses the Hype library for fetching target data. The Hype library provides support for asynchronous operations, and a task in the IO execution context is used for waiting results from Hype.

Supported layers

Kanzi Maps supports these layers from the HERE Vector Tile API:

• boundaries

• buildings

• earth

• landuse

• places

• pois

• roads

• transit

• water

For more information see https://developer.here.com/documentation/vector-tile-api/dev_guide/topics/layers.html.

Tiling scheme

The HERE OLP Edge backend uses TilingSchemeGoogle which is a Web Mercator based quad tree tiling scheme.

Router

Here OLP Edge backend supports the HERE public REST API for routing. Functionally routing works the same as with Mapbox, but uses HERE-specific decoding for routing results. For more information, see https://developer.here.com/documentation/routing/topics/introduction.html.

Geocoder

Not available on the HERE backend.

TomTom backend

The TomTom backend uses the HTTP Client provided by the generic Kanzi Maps backend library to access the TomTom REST APIs.

A task in the IO execution context fetches data over HTTPS (if supported) from TomTom servers. A task in the COMPUTE execution context takes the data and parses it.

Tile fetcher

Supported layers

Kanzi Maps supports these TomTom layers:

Tile source	Supported layers and reference documentation
Vector service - Content	buildings boundaries carto_labels_lines carto_labels_points earth_cover land_cover land_use places poi_basic poi_extended roads water water_lines https://developer.tomtom.com/map-display-api/documentation/vector/content-v2
Raster service - Satellite Tile	satellite https://developer.tomtom.com/map-display-api/documentation/raster/satellite-tile
Traffic Flow service - Raster Flow Tiles	traffic_flow https://developer.tomtom.com/traffic-api/documentation/traffic-flow/raster-flow-tiles
Traffic Incidents service - Raster Incident Tiles	traffic_incidents https://developer.tomtom.com/traffic-api/documentation/traffic-incidents/raster-incident-tiles
Hill/Main	terrain3d

For information on the supported metadata, see the reference documentation linked to each list of layers.

Tiling scheme

The TomTom backend uses TilingSchemeGoogle which is a Web Mercator based quad tree tiling scheme.

Router

Routing uses the TomTom Routing REST API. See https://developer.tomtom.com/routing-api/documentation/routing/calculate-route.

Geocoder

Reverse geocoding for TomTom uses the TomTom Search REST API. See https://developer.tomtom.com/search-api/documentation/reverse-geocoding-service/reverse-geocode.