as many of you probably know PTV offers both
- backend routing components (PTV xRoute)
- offline navigation (PTV Navigator)
and we also provide a mechanism called Guided Navigation which is based on a proprietary file format which is also supported by the xRoute engine (v2.x) itself.
Every once in a while I am getting asked for whether PTV routing can provide files that are ready to be used with non-PTV navigation products such as Google Maps (©) or Cygic(©). Of course each one of those players requires a proprietary file format so what PTV xRoute can offer is to return the info that is needed to create such a file, e.g. all the polygon points.
What we do not support at the moment (august 2020) is s a direct output you can forward to those other systems. You would need to assemble these strings manually but afaik the level of complexity is way less than rocket science
- simple workflow chart
Best regards,
Bernd
PS: here's a sample BCR file which demonstrates the structure of PTVs own "guided navigation" mechanism. This complete string is guiding the driver from Karlsruhe to Mannheim and is bassed on PTV_MERCATOR coordinates. Of course we also support formats such as WGS84 (Open Gis Geodecimal).
[CLIENT]
ROUTENAME=xServer 2 - guided navigation route export
MAP_VERSION=unknown
[COORDINATES]
STATION1=937170,6270123
STATION2=941462,6350704
[VISITED]
STATION1=0
STATION2=0
[Station2Segmentcenters]
Point1=937410,6270183,72
Point2=937513,6269952,164
Point3=937699,6268849,107
Point4=940219,6268889,45
Point5=944406,6276077,27
Point6=949109,6284042,27
Point7=951235,6291451,22
Point8=954888,6300524,24
Point9=956410,6309145,355
Point10=957865,6316105,307
Point11=953031,6322201,320
Point12=952211,6323471,333
Point13=950117,6331361,355
Point14=950184,6339869,340
Point15=948806,6346746,297
Point16=947195,6347465,212
Point17=947053,6347210,203
Point18=946327,6346535,300
Point19=943537,6348160,315
Point20=943093,6348610,90
