1. Platform Data Extension PDE 1.5.1 Technical Training http://pde.api.here.com/

2. 22 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

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

4. 44 PDE Use Cases AttributeUse Case Street TypeFleet management customers need to know on which road types a vehicle is driving. Number of LanesFleet management companies need to know how many lanes the roads have that their vehicles use. Builtup AreasFleet management companies need to know if an asset is within or outside of an urban area for to risk management. Road ConditionRaise alerts if tracked vehicle leaves paved roads. SlopeEnables estimating fuel consumption and calculation of CO2 emission, for driver education or penalties. Traffic LightsEnables enhanced estimation of potential trip delays due to traffic signals. CurvatureAssessment of driver behavior for risk calculation and truck trip planning. Speed LimitsDriver behavior analysis for risk calculation and speed warning alerts during drive. Junction ViewsIntegration of junction views for improved directions or guidance. Toll CostMore accurate toll cost estimation for vehicle types based on toll roads and distances, on top of the info returned by the routing service.

5. 55 Access to PDE Product PDE Version 1.5.1 is available since August 31 th, 2015 Technical documentation on http://developer.here.com and http://pde.api.here.com/http://developer.here.comhttp://pde.api.here.com/ Product Manager: Dieter Wallmann Platform customers have to be white-listed to use PDE Examples provided by Technical Customer Support http://tcs.ext.here.com/examples/ http://tcs.ext.here.com/examples/ Submit bugs & feature requests to tcsplatform@here.com

6. 66 PDE is an HTTP REST API Example Layer Tile –http://pde.cit.api.here.com/1/tile.json? layer=ADAS_ATTRIB_FC1&level=9&tilex=534&tiley=387 &app_id= &app_cod e= http://pde.cit.api.here.com/1/tile.json? layer=ADAS_ATTRIB_FC1&level=9&tilex=534&tiley=387 &app_id= &app_cod e= –… tile.txt … Documentation of available maps/layers available here: –http://pde.api.here.com/ in HTML formathttp://pde.api.here.com/ –and in JSON format here:  http://pde.cit.api.here.com/1/doc/maps.json?app_id= &app_code= http://pde.cit.api.here.com/1/doc/maps.json?app_id= &app_code= <YOUR_APP_C ODE>  http://pde.cit.api.here.com/1/doc/layers.json?region=EU&release=2014Q1&app_id = &app_code= = http://pde.cit.api.here.com/1/doc/layers.json?region=EU&release=2014Q1&app_id = &app_code= =

7. 77 PDE 1.5.1 Data filtering Specifies the tile columns to be retained or removed from result. To have only certain columns in the resulting tile, value can be specified as semi-colon separated column names. As an example, the parameter value cols=LAT;LON will make the resulting tile include only LAT and LON columns tile.json / tile.txt –http://pde.cit.api.here.com/1/tile.json?layer=LINK_ATTRIBUTE_FC3&level=11&tilex=2 146&tiley=1594&meta=1&app_id= &app_code= &cols=LINK_ID;URBANhttp://pde.cit.api.here.com/1/tile.json?layer=LINK_ATTRIBUTE_FC3&level=11&tilex=2 146&tiley=1594&meta=1&app_id= &app_code=<YOUR_APP_COD E>&cols=LINK_ID;URBAN tiles.json / tiles.txt –http://pde.cit.api.here.com/1/tiles.json?layers=LINK_ATTRIBUTE_FC3,SPEED_LIMIT S_FC4&levels=11,12&tilexy=2146,1594,3686,2678&meta=1&app_id= &app_code= &cols=LINK_ID;URBAN,-SPEED_LIMIT_UNIThttp://pde.cit.api.here.com/1/tiles.json?layers=LINK_ATTRIBUTE_FC3,SPEED_LIMIT S_FC4&levels=11,12&tilexy=2146,1594,3686,2678&meta=1&app_id=<YOUR_APP_I D>&app_code= &cols=LINK_ID;URBAN,-SPEED_LIMIT_UNIT

8. 88 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

9. 99 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 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)

10. 10 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

11. 11 PDE Indexes Link_ID  set of tile IDs http://pde.cit.api.here.com/1/ index.txt ?release=2014Q2& layer=ROAD_GEOM_FCn&attributes=LINK_ID&values =548294575,833539855,550088940,930893121 &app_id= &app_code= http://pde.cit.api.here.com/1/ index.json ?release=2014Q2& layer=ROAD_GEOM_FCn&attributes=LINK_ID&valu es=548294575,833539855,550088940,930893121 &app_id= &app_code= http://pde.cit.api.here.com/1/doc/ indexes.json ?region=EU&release=2014Q2 &app_id= &app_code= 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]} ] PDE 1.5 How many values can I request in a single call? http://pde.cit.api.here.com/pde/1/serviceconfiguration.json { Configuration: { multiTileRequestLimit: "100", indexRequestValueLimit: "100" }

12. 12 Available Layers ADAS Attributes (geometry, curvature, height, slope) Admin Places Admin Polygons Basic Height Census Entities City Center POIs Digital Terrain Model Distance Markers Junction Views 2D Lane Connectivity Link Attributes Link Connectivity TMC Road Admin Info Signpost Text Speed Limits (conditional, variable) Toll Cost Toll Booths Toll Links Traffic Pattern Traffic Signs Truck Restrictions Truck Speed Limits

13. 13 Demo – Digital Terrain Model http://tcs.it.here.com/Examples/src/HLP3_PDE_DigitalTerrainModel.html

14. 14 Demo – Distance Markers http://tcs.ext.here.com/examples/src/HLP3_PDEDistanceMarkers.html

15. 15 Demo – Junction Views 2D http://tcs.ext.here.com/examples/src/HLP3_PDEJunctionViewAlongRoute.htmlhttp://tcs.ext.here.com/examples/src/HLP3_PDEJunctionViewAlongRoute.html

16. 16 Demo – Postal Code Boundaries http://tcs.ext.here.com/examples/src/HLP3_PDEPostalBounds.htmlhttp://tcs.ext.here.com/examples/src/HLP3_PDEPostalBounds.html

17. 17 Demo - Route Types & Urban http://tcs.ext.here.com/examples/src/HLP3_RouteTypesAlongRoute.htmlhttp://tcs.ext.here.com/examples/src/HLP3_RouteTypesAlongRoute.html

18. 18 Demo - Slopes along Route http://tcs.ext.here.com/examples/src/HLP3_SlopeAlongRoute.htmlhttp://tcs.ext.here.com/examples/src/HLP3_SlopeAlongRoute.html

19. 19 Demo - Slopes in Rectangle http://tcs.ext.here.com/examples/src2.5.4/HLP_SlopeInBoundingBox.htmlhttp://tcs.ext.here.com/examples/src2.5.4/HLP_SlopeInBoundingBox.html

20. 20 Demo – Speed Limits http://tcs.ext.here.com/examples/src/HLP3_PDESpeedLimitsAlongRoute.htmlhttp://tcs.ext.here.com/examples/src/HLP3_PDESpeedLimitsAlongRoute.html

21. 21 Demo - Traffic Signs http://tcs.ext.here.com/examples/src/HLP3_PDETrafficSigns.htmlhttp://tcs.ext.here.com/examples/src/HLP3_PDETrafficSigns.html

22. 22 Batch Demo - Route Types / Urban / Speeding http://tcs.ext.here.com/examples/src/RME_PDE_Java_Example.ziphttp://tcs.ext.here.com/examples/src/RME_PDE_Java_Example.zip Collected GPS traces in GPX or CSV format HERE PDE Web Service HERE Platform Route Match Web Service Trace Match & Attribution Batch Program Map matched Points + matched Routes Route Types, Urban, Speeding colored Result Visualizer