Platform Data Extension PDE Technical Training Version 1.3 http://tcs.it.here.com/http-proxy2/PlatformDataExtension/

What is PDE? Online access to core map data For Platform business customers All attribution (slopes, road type…) on top of the Platform attributes (speed, func.class) Thematic layers, geographically tiled, simple text or JSON format Platform customers don’t need to download + install RDF … don’t need to compile into a binary format … don’t need a hosting service / cloud … devices / browsers don’t need complex PSF access libraries

Filter by route link ids Application with PDE Application Filter by route link ids Request: ADAS attributes for map rectangles Request: Calculate Route from A to B Response: Text or JSON Response: route geometry & link ids LinkId Slope Curvature … 1234 1% 2.3% … 400m 180m 1256 1.5% 0.2% 430m 410m Routing Web Service PDE Web Service

PDE Use Cases Attribute Use Case Street Type Fleet management customers need to know on which road types a vehicle is driving. Number of Lanes Fleet management companies need to know how many lanes the roads have that their vehicles use. Builtup Areas Fleet management companies need to know if an asset is within or outside of an urban area for to risk management. Road Condition Raise alerts if tracked vehicle leaves paved roads. Slope Enables estimating fuel consumption and calculation of CO2 emission, for driver education or penalties. Traffic Lights Enables enhanced estimation of potential trip delays due to traffic signals. Curvature Assessment of driver behavior for risk calculation and truck trip planning. Speed Limits Driver behavior analysis for risk calculation and speed warning alerts during drive. Junction Views Integration of junction views for improved directions or guidance. Toll Cost More accurate toll cost estimation for vehicle types based on toll roads and distances, on top of the info returned by the routing service.

Access to PDE Product PDE Version 1.2.0 was released on October 1st, 2014 Technical documentation soon on http://developer.here.com, and on http://tcs.it.here.com/http-proxy2/PlatformDataExtension/ Product Manager: Dieter Wallmann Platform customers have to be white-listed to use PDE Examples provided by Technical Customer Support http://tcs.it.here.com/http-proxy2/Examples/ Submit bugs & feature requests to tcsplatform@here.com

PDE is an HTTP REST API Example Layer Tile PDE 1.2 &region parameter no longer mandatory Example Layer Tile http://pde.cit.api.here.com/1/tile.json?region=EU&release=2013Q3&layer=ADAS_ATTRIB_FC1&level=9&tilex=534&tiley=387&app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg … tile.txt … Documentation of available maps/layers available here: http://tcs.it.here.com/http-proxy2/PlatformDataExtension/ in HTML format and in JSON format here: http://pde.cit.api.here.com/1/doc/maps.json?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg http://pde.cit.api.here.com/1/doc/layers.json?region=EU&release=2014Q1&app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg

PDE Concepts Layers Thematically (driver alert, ADAS, road conditions, …) Potentially all core map content + additional content (Digital Terrain Model, …) Tiling & Levels NDS compatible, WGS84 (not QuadKey), Platform compatible Layers usually distributed into 5 levels (per functional class)  even for long routes need only load ~20 tiles IDs from Core Map (Link PVID, Carto PVID, Condition PVID…) All map releases available  fits to current Platform releases Binary content also available via file download e.g. Junction View images Level 0 y=0, x=0 0,1 Level 1 0,0 0,3 0,2 1,0 1,1 1,3 1,2 Level 2 2,0 2,1 2,3 2,2 3,0 3,1 3,3 3,2 0,4 0,5 0,7 0,6 1,4 1,5 1,7 1,6 2,4 2,5 2,7 2,6 3,4 3,5 3,7 3,6

PDE Tiling & Levels Applications have to request a layer content tile on the correct PDE level (the tile size) Specified in the layer documentation For road layers: PDE level = functional class + 8 New since version 1.1! Before, tiles could be requested on any level. Which tiles shall I request? Lookup the level from the layer documentation tile size = 180° / 2^level [degree] tileY = trunc((latitude + 90°) / tile size) tileX = trunc((longitude + 180°) / tile size)

Why Tiles Irrelevant data  just want data for the route links? Reduce number of REST requests Tile contains info for multiple links, no need to request info for each link separately Cache tiles during the session, avoids redundant requests Web Service performance & cost efficiency Tiles partially served out of Web caches  less load on Web service Long routes start/end on minor roads and then mainly use major roads PDE layers are split according to the road functional classes (highway, federal,…) Even for a long route, only ~20 tiles must be requested (highway tiles are huge) Serve multiple use cases Not only “link attributes along route” E.g. show info for the current map display area, or selected administrative areas

PDE 1.1: Toll Cost Layers Use Case: Retrieve the toll cost along a route Several types of tolls: Fixed cost (bridge, tunnel…) sections Cost per kilometer sections Cost between 2 tool booths sections Fixed cost per administrative area sections The vehicle type, main factor of toll cost variation, is looked up from its specifications (type, height, weight…) thanks to a static content PDE layer The toll cost returned can be variable according to multiple parameters (number of passengers, date / time…) Route Toll Cost Web service will launch in Q4/2014 Uses PDE toll cost layers, implements the complex specifications © 2014 HERE | PowerPoint template v3.0

PDE 1.1: Truck Speed Limit Layers Use case: How fast can I drive here with my 10 tons truck with trailer? Speed Limit layer: Sign posted + from country regulations - for passenger cars Conditional Speed Limit layer: Time and vehicle type dependent – only sign posted Variable Speed Limit layer: Locations of variable speed limit signs Truck Speed Limit layer: Time and vehicle type dependent – from country regulations Truck driver warning applications have to compute the minimum from the 3 layers © 2014 HERE | PowerPoint template v3.0

PDE 1.1: Truck Speed Limit Layers Car Speed Limits Truck Speed Limits © 2014 HERE | PowerPoint template v3.0

PDE 1.1: Traffic Pattern Layers For each link: Average speed driven on Mondays 0:00, 0:15, 0:30 … 23:45, Tuesdays… In the tiles, only Pattern IDs are listed Request a “static” (non tiled) table TRAFFIC_PATTERN from PDE JSON or Text The tables listes the speed values across the day for each Pattern ID © 2014 HERE | PowerPoint template v3.0

PDE 1.1: Traffic Sign Layers Demo application (by TCS) http://tcs.it.here.com/Examples/src/HLP3_PDETrafficSigns.html © 2014 HERE | PowerPoint template v3.0

PDE 1.1: Admin Polygon Layers Builtup, City, County, State, Country Created from core map polygons + boundary lines Tiled: Each tile contains Admin Place IDs and parts of their polygons Use case: Map display Lookup by Admin Place ID is supported by the Geocoder On demand, PDE can also offer an index Admin Place ID  tile IDs © 2014 HERE | PowerPoint template v3.0

PDE 1.1: Link Admin Layers For each road link, the left / right side administrative hierarchy is listed Builtup, Order 8, Order 2, Order 1, Country Postal Code Use case: Where am I on this link Geocoder offers the same function PDE is the “bulk” interface: Don’t call Geocoder for each of the 1000 links along the route, instead call PDE for each of the 30 tiles along the road © 2014 HERE | PowerPoint template v3.0

PDE 1.2: Direction Sign Layer Sign text and highway route numbers For text based guidance instructions © 2014 HERE | PowerPoint template v3.0

PDE 1.2: Static Content “Country” Country level information Applications load this file once per session http://pde.cit.api.here.com/1/static.json ?region=EU&release=2014Q2 &content=COUNTRY &app_id=RBvfUskZo9VHXO16qN0F&app_code=nurAvIabhmop7KOSfQd0bA © 2014 HERE | PowerPoint template v3.0

PDE 1.1: Link_ID Lookup Index Link_ID  set of tile IDs http://pde.cit.api.here.com/1/index.txt?region=EU&release=2013Q4&layer=ROAD_GEOM_FCn&attributes=LINK_ID&values=548294575,833539855,550088940,930893121&app_id=dIqjg3N5LuHG1QAwHbwD&app_code=rJbZNQB3EN3oB4NqHaFXTQ http://pde.cit.api.here.com/1/index.json?region=EU&release=2013Q4&layer=ROAD_GEOM_FCn&attributes=LINK_ID&values=548294575,833539855,550088940,930893121&app_id=dIqjg3N5LuHG1QAwHbwD&app_code=rJbZNQB3EN3oB4NqHaFXTQ http://pde.cit.api.here.com/1/indexes.html?region=EU&release=2013Q4&app_id=dIqjg3N5LuHG1QAwHbwD&app_code=rJbZNQB3EN3oB4NqHaFXTQ The tile IDs can be used for any link based layer (of the same Functional Class), e.g. LINK_ATTRIBUTE layer Example response: Layers: [ {layer: "ROAD_GEOM_FC1", level: 9, tileXYs: [534,397,536,398]}, {layer: "ROAD_GEOM_FC2", level: 10, tileXYs: [ ]}, {layer: "ROAD_GEOM_FC3", level: 11, tileXYs: [2139,1590]}, {layer: "ROAD_GEOM_FC4", level: 12, tileXYs: [ ]}, {layer: "ROAD_GEOM_FC5", level: 13, tileXYs: [8580,6376]} ] © 2014 HERE | PowerPoint template v3.0

Example Slopes in Rectangle http://tcs.navteq.com/http-proxy2/Examples/src2.5.4/HLP_SlopeInBoundingBox.html

Example Slopes along Route http://tcs.navteq.com/http-proxy2/Examples/src/HLP3_SlopeAlongRoute.html

Example Route Types & Urban along Route http://tcs.navteq.com/http-proxy2/Examples/src/HLP3_RouteTypesAlongRoute.html

Batch Example - Route Types / Urban / Speeding http://tcs.navteq.com/http-proxy2/Examples/src2.5.4/Trace_Match_Batch_Client2.zip Trace Match & Attribution Batch Program Visualizer Result Collected GPS traces in GPX or CSV format Map matched Points + matched Routes Route Types, Urban, Speeding colored HERE Platform Route Match Web Service HERE PDE Web Service