MAP&Guide next generation versus PTV Developer Routing API

[Bernd Welter]

Recently I's been asked by different parties how to ensure that MAP&GUIDE and our Routing APIs return equal results.
Well, the question has to be more precise... because there's multiple product versions avaiable:

Frontend	Backend
Map&Guide Desktop	PTV MapServer
MAP&GUIDE Internet "classic"	PTV xServer 1
n.a.	PTV xServer 2
MAP&GUIDE next generation	PTV Developer API

Sometimes users of one product need to compare the routing results with users who drive the same relations but who use a different product, e.g. large companies used an integrated xRoute1 solution while their subcontractors used the well known generic Map&Guide.

So the current technological architecture is based on

• • PTV Developer Geocoding and Places API for the determination of the underlying coordinates
  • PTV Developer Routing API for the routing and determination of distance, traveltime, detailed toll, emissions and more
  • PTV Developer Raster Maps API / PTV Developer Vector Maps API for the visualization of the result
• PTV MAP&GUIDE next generation

the demand is now to align these two solutions. The answer is: apply the following options in your Developer Routing API call

• Base profile, e.g. EUR_TRUCK_40T
• TrafficMode.AVERAGE
• RoutingMode.FAST

Here's my sample call

Code: Select all

{
  "waypoints": [
    "48.8571701049805,2.3413999080658;name=Paris",     "52.2355995178223,21.0103702545166;name=Warszawa",
    "50.0791397094727,14.4329900741577;name=Praha"
  ],
  "profile": "EUR_TRUCK_40T",
  "vehicle": {  },
  "options": {
    "trafficMode": "AVERAGE",    "routingMode": "FAST",    "language": "EN",    "currency": "EUR",    "speedFactor": 1.0
  },
  "monetaryCostOptions": {},
  "results": [    "POLYLINE",    "TOLL_COSTS",    "TOLL_EVENTS",    "TOLL_SECTIONS",    "TOLL_SYSTEMS"  ]
}

Here's some example output for a route from Paris via Warschau to Prague

MAP&GUIDE next generation. Standard profile "40T Truck" - no further options available at this time (9.4.2025)	Developer Routing API based result - EUR_TRUCK_40T profile with explicit overriding of RoutingMode.FAST and TrafficMode.AVERAGE

Bernd