Joined
·
2,739 Posts
Been spending a lot of time researching the VCard import which varies between VW models across the range, Seat and Skoda. The Ateca 8" screen with the SSD storage (called HD by Seat UK) and DVD Drive is the Discover Pro. In German
http://www.volkswagen.de/de/navigation/discover-pro.html
Whilst Skoda offer their own individual look up for other versions I believe the best one is for the Discover Pro, the VCard syntax is different on the others:
http://www.volkswagen.de/de/navigation/discover-pro/adressnavigation.html
Edit: Two ways of doing this via VCards working on the address or via the GEO code decimal positions. If you don't have the full address then you do it via the GEO code and POI import, then store each POI as a destinations and that's your destinations done - goto page 3. However if you have the full address can use the VCard method and if that fails the POI method... read on
.
To generate a VCard for the Discover you use the site above and put in the address under
Interesse (Interest) and Ort (Place)
Example is Legure Hotel Munsbach Luxembourg under Interesse hitting Suche Starten
That gives you what it's found listed and on the map, you select the one you want and hit Speichern to Save and Weiter. This generates a VCard which can be opened in the Notepad:
BEGIN:VCARD
VERSION:3.0
N;CHARSET=UTF-8:Légère Hotel Luxembourg;;;;;
FN;CHARSET=UTF-8:Légère Hotel Luxembourg
ADR;CHARSET=UTF-8:;;Rue Gabriel Lippmann 11;Schuttrange;;5365;LUXEMBURG
GEO:49.64023999999999;6.270546999999965
END:VCARD
The actual name that will be used in the satnav once imported is the one placed on the FN line. The GEO line is the traditional satnav reference. The Begin, End and Version code are all required. There is then variation with Skoda / Seat / VW and other look up programmes on how much else is required plus other layout. Working on the basis this is VW's spec for the headend this is the file profile to use.
Thus if you get the urge to get your destinations ready this is the target file structure you need and multiple VCards are just listed down as I understand it. Finding an import program to take existing destinations and writing these out on mass as VCards isn't something that you find online. GPSBabel VCard export is really for supporting the iPod to show coordinates for mapping and it's VCard structure isn't inline with that shown above. From what I can see you have to get out your destination and X, Y coordinates from your existing system then do your own processing to generate this file structure. Better still give the task over to the partner once you have unlocked the materiel from your GPS.
It's Co-Pilot where I was struggling to find a suitable program to get out the destination data. Co-Pilot say themselves it is not possible, they import but don't allow you to export. There was other misguided stuff elsewhere where a non existent solution given, but I did stumble on a piece of text which said that the TRP trip planning file was readable. On Android the destination file isn't in ASCII. The solution is you work down the list of destinations and make a planned journey to as many as possible. Save the planned journey that gives you a planned trip around your destinations as a TRP file. This contains a readable file but it's still in Co-Pilot ASCII with decimal places shifted on the coordinates and lots of other stuff.
ITN Convertor then comes to your rescue (shareware free) it reads Co-Pilot TRP files to generate GPX files for exporting elsewhere. Pick a CSV as output and you get the destination and the X, Y cordinates written out for each of your destinations. Do this as many times as you require. I had a library of 144 destinations hence I wasn't stumbling to put them in by hand. I had to plan three trips around my destinations to get them all out.
You then take you destinations and manipulate into the file structure above and get the car as well
. Navigation is one my interests. This solution may work with other Satnavs. ITN Convertor or GPSBabel may allow you to get out your destinations and traditional coordinates. If the partner doesn't sort out the final bit I will be forced to brush up my programming skills. Basically you have to post seven columns of information in a row going down as per that example above for each destination. My Légère Hotel will look like this, I fill the destination name into the two other fields:
BEGIN:VCARD
VERSION:3.0
N;CHARSET=UTF-8:LUXEMBOURG Legere Premium Hotel;;;;;
FN;CHARSET=UTF-8:LUXEMBOURG Legere Premium Hotel
ADR;CHARSET=UTF-8:;;LUXEMBOURG Legere Premium Hotel;;;;
GEO:49.6405;6.271
END:VCARD
Coordinates as per I had them in Co-Pilot which uses the same underlying maps based on Here. So I'm note expecting the issue of where the car won't go since that road already existed on my mapping system using the same maps.
Something that VW / Skoda / Seat owners can do for me. When I had the satnav shown to me in the Ateca I asked about putting in the coordinates so he brought the screen up. The example on the screen was in this form N49 38.430 E6 16.260 (Legere Hotel again). I did read that on some of the VW systems you had to enter the coordinates in non standard non decimal mode (e.g. standard is decimal degrees, WGS84). Any of you readers got the navigation that takes in the normal decimal degree method or are they all difficult. I can't see that the Discover Pro would be so difficult.
When hiking I take out the X, Y coordinates from my general hiking / navigation app finding the trail head from OSM maps or Google Earth photo then transfer them to car navigation. Clearly if the car doesn't take the normal coordinates when away from home I won't be wanting to do a conversion job on the codes although there are apps. I would like to resolve this one. Something to try out when you sit in an Ateca. 49.6405, 6.271 as a destination.
http://www.volkswagen.de/de/navigation/discover-pro.html
Whilst Skoda offer their own individual look up for other versions I believe the best one is for the Discover Pro, the VCard syntax is different on the others:
http://www.volkswagen.de/de/navigation/discover-pro/adressnavigation.html
Edit: Two ways of doing this via VCards working on the address or via the GEO code decimal positions. If you don't have the full address then you do it via the GEO code and POI import, then store each POI as a destinations and that's your destinations done - goto page 3. However if you have the full address can use the VCard method and if that fails the POI method... read on
To generate a VCard for the Discover you use the site above and put in the address under
Interesse (Interest) and Ort (Place)
Example is Legure Hotel Munsbach Luxembourg under Interesse hitting Suche Starten
That gives you what it's found listed and on the map, you select the one you want and hit Speichern to Save and Weiter. This generates a VCard which can be opened in the Notepad:
BEGIN:VCARD
VERSION:3.0
N;CHARSET=UTF-8:Légère Hotel Luxembourg;;;;;
FN;CHARSET=UTF-8:Légère Hotel Luxembourg
ADR;CHARSET=UTF-8:;;Rue Gabriel Lippmann 11;Schuttrange;;5365;LUXEMBURG
GEO:49.64023999999999;6.270546999999965
END:VCARD
The actual name that will be used in the satnav once imported is the one placed on the FN line. The GEO line is the traditional satnav reference. The Begin, End and Version code are all required. There is then variation with Skoda / Seat / VW and other look up programmes on how much else is required plus other layout. Working on the basis this is VW's spec for the headend this is the file profile to use.
Thus if you get the urge to get your destinations ready this is the target file structure you need and multiple VCards are just listed down as I understand it. Finding an import program to take existing destinations and writing these out on mass as VCards isn't something that you find online. GPSBabel VCard export is really for supporting the iPod to show coordinates for mapping and it's VCard structure isn't inline with that shown above. From what I can see you have to get out your destination and X, Y coordinates from your existing system then do your own processing to generate this file structure. Better still give the task over to the partner once you have unlocked the materiel from your GPS.
It's Co-Pilot where I was struggling to find a suitable program to get out the destination data. Co-Pilot say themselves it is not possible, they import but don't allow you to export. There was other misguided stuff elsewhere where a non existent solution given, but I did stumble on a piece of text which said that the TRP trip planning file was readable. On Android the destination file isn't in ASCII. The solution is you work down the list of destinations and make a planned journey to as many as possible. Save the planned journey that gives you a planned trip around your destinations as a TRP file. This contains a readable file but it's still in Co-Pilot ASCII with decimal places shifted on the coordinates and lots of other stuff.
ITN Convertor then comes to your rescue (shareware free) it reads Co-Pilot TRP files to generate GPX files for exporting elsewhere. Pick a CSV as output and you get the destination and the X, Y cordinates written out for each of your destinations. Do this as many times as you require. I had a library of 144 destinations hence I wasn't stumbling to put them in by hand. I had to plan three trips around my destinations to get them all out.
You then take you destinations and manipulate into the file structure above and get the car as well
BEGIN:VCARD
VERSION:3.0
N;CHARSET=UTF-8:LUXEMBOURG Legere Premium Hotel;;;;;
FN;CHARSET=UTF-8:LUXEMBOURG Legere Premium Hotel
ADR;CHARSET=UTF-8:;;LUXEMBOURG Legere Premium Hotel;;;;
GEO:49.6405;6.271
END:VCARD
Coordinates as per I had them in Co-Pilot which uses the same underlying maps based on Here. So I'm note expecting the issue of where the car won't go since that road already existed on my mapping system using the same maps.
Something that VW / Skoda / Seat owners can do for me. When I had the satnav shown to me in the Ateca I asked about putting in the coordinates so he brought the screen up. The example on the screen was in this form N49 38.430 E6 16.260 (Legere Hotel again). I did read that on some of the VW systems you had to enter the coordinates in non standard non decimal mode (e.g. standard is decimal degrees, WGS84). Any of you readers got the navigation that takes in the normal decimal degree method or are they all difficult. I can't see that the Discover Pro would be so difficult.
When hiking I take out the X, Y coordinates from my general hiking / navigation app finding the trail head from OSM maps or Google Earth photo then transfer them to car navigation. Clearly if the car doesn't take the normal coordinates when away from home I won't be wanting to do a conversion job on the codes although there are apps. I would like to resolve this one. Something to try out when you sit in an Ateca. 49.6405, 6.271 as a destination.