Edit (7th June 2018) [there is a solution see below and links] at the minute we have a handbrake turn at step 2 since VW have withdrawn the POI import page again - they have moved over to Carnet for the upload which isn't available with Seat and many VWs. I see others have nicked my text and published it elsewhere and it doesn't work now but haven't gone into the contingency testing as I outlined below if it happened again (which it has). I don't think it will come back this time so it's the contingency plan. I see the other boards aren't making progress 
.
However the contingency plan is now working for me see post 10 or read on further for a tail of wow.
The Car-net method VW have moved to doesn't do the beeps on Poi's so it wouldn't be any good for safety cameras. Skoda is moving to the same approach also no beep.
The VW have a record of ditching the POI import software, they did it with the RNS510 leaving people stranded. They have stranded their own Mib2 customers without car-net now.
Have tested the Skoda import method, very slow and problematic and didn't work on the Mib2 High and that's with and without the directory copy business explained below, so wasn't that. It might work with a standard unit but I think the Skoda site is being thrashed by VW people with files of 40,000 Poi's or so. Not so sure whether it was my impatience to the browser pop ups. But clearly on 40,000 Poi's it doesn't work once you try it in your car. It can only be a matter of time before that one is pulled one suspects given that Skoda is moving to a carnet approach (& that is no good for speed cameras, mib2.5 dimension as well where apparently you can specify by POI in the car for alarm sounds) so better to go with something independently installed on your own equipment than a webpage that may be pulled at any moment. Did that but currently doesn't work, have emailed the developer.
A better night after midnight with Germans tucked up in bed so you get the hardware more to your self. On the Skoda site you toggle off after each one paints to the screen since that saves the geographical processing of the data for the purposes of showing it on the screen. Exported out ok. Gpx I was using for the the cameras. ASC it's fussy about. I see thou nobody or few has any luck with getting the raw output into VW hardware and the directory trick covered below doesn't work either. Suggestion that Skoda is not computing the checksums correctly. Got to get back up to speed again to check that one out. Did that and yes they have the poi checksum and filesize wrong on the Poi directory as one German poster said on a German board. Then you recalc these plus the Metafilechecksum. A few tricks... got to test it in the car thou... there still might be a problem but incorrect checksums will hang it.
Breakthrough with POI Inspector see post 10 below - that's for the MIB2 High, the MIB2 standard should be be fine. Need release 6.4 or above for the MIB2High to work.
----
Main text when it was working via the VW site
This covers how to upload speed / safety cameras and other POIs to the Seat Ateca navigation and abridged step for the Seat Navigation Plus is currently required related to a bug introduced by VW in 2017 on their web based process.
Circa February 2017 the VW site that can be used to import speed camera databases (safety cameras) from third parties plus other POIs into the Ateca navigation system became broken for the MIB2High unit (Navigation Plus). Skoda vehicles as well as VW cars were effected, all the MIB2 High units. There is a metainfo2.txt file that is held in the main uploaded directory which is incompatible with the Discovery Pro MIB2 unit. There is a simple workaround. A similar fix was used for the standard MIB2 units previously when VW messed up the software. The standard unit POI files are held in the MIB2TSD files if this ever becomes an issue. If this issue appears on the standard unit as it has done in the past a variation to this fix can be used.
The issue was reported in a couple of threads
https://www.briskoda.net/forums/topic/385044-poi/?page=5
http://www.vwaudiforum.co.uk/forum/showthread.php/181365-Custom-POI-s
There are two workarounds one is to use an existing version of the metainfo2.txt file if you have one (i.e. you have done the process before and saved the files generated), the second is to open up the folder generated and to copy out from the "MIB2HIGH" as covered by CBEE in the thread above.
》
1) Create and download the POI files as normal using the VW Navigation Website
2) Open the zip file and you will see a folder called "PersonalPOI" and a file called "metainfo2.txt", open the folder called "PersonalPOI"
3) Inside the folder will be 3 other folders called "MIB2DE", "MIB2HIGH" and MIB2TSD", open the "MIB2HIGH" folder for the Discover Pro
4) Inside the folder you will see the same "PersonalPOI" and "metainfo2.txt" files, copy these to the root of your SD card.
5) Stick SD card in car and away you go
《
Both work in the Ateca Navigation. You can use either an SD card or USB to copy the files into the unit.
SETTING UP SPEED CAMERA / OTHER POI DATABASE
The process of uploading speed camera to the Ateca Navigation unit, you first need to select your database of speed cameras, I use the subscription Pocket GPS World, GPX format taking four files from the database, fixed and mobile, UK and Europe wide in the type Other. They call it "single file" select UK and then Euro downloading two zip files that contain the four GPX files and four bit maps. Other services which are free are available, Poiplaza is one. The choice is yours in terms of which you think is the most up to date.
After downloading the files which generally consist of the data file and the bit map picture of the camera graphic these are uploaded into the German VW website, in German. However this link provides an excellent step by step work through of the process. Step 1 is for Australia getting your POI files, substitute by the above, then follow the steps, then at the end we have the wrinkle in copying across onto an SD or USB stick the file and enabling the Ateca unit to show
Follow Primordial's first post
http://www.vwgolf.net.au/showthread.php?27941-MIB-II-Custom-POI-s-Speed-Cameras-etc
At step 2 you need the new VW link to call up the site that does the work (not the one that was shown in the original Primordial instruction which no longer works due to VW changing their site around)
http://rollout.volkswagen.de/content/de/brand/de/navigation/discover-pro/poi-listen-sammlung.html
Continue through the stages and repeat for additional speed cameras, make sure you click the "Annaherungs" to generate the sound for the cameras. Any other POIs can also be uploaded.
If using Pocket GPS World for the UK and European mainland for the fixed and mobile cameras the imported files within the VW software should look similar to this at the end of Step 5 with the sound marked up and the correct camera type showing:
Do Step 7 and stop
Step 8 is modified currently with the problematic VW website for those units effected.
New Step 8:
Extract the ZIP file to your SD Card or USB stick but with the modified procedure of CBEE mentioned above, extract onto a blank media. No other directories or files should be present on the SD card or stick else the import will not run.
A) Open the zip file and you will see a folder called "PersonalPOI" and a file called "metainfo2.txt", open the folder called "PersonalPOI"
B) Inside the folder will be 3 other folders called "MIB2DE", "MIB2HIGH" and MIB2TSD", open the "MIB2HIGH" folder for the Discover Pro
C) Inside the folder you will see the same "PersonalPOI" and "metainfo2.txt" files, copy these to the root of your SD card.
D) Stick SD card in car and away you go
The user POI database created by the VW site are imported onto the memory of the unit itself whether the maps are held on an SD card or SSD of the Plus unit.
As of June 2017, the situation is that the modified step is required for the Seat Navigation Plus unit which is "MIB2 High". The standard unit is currently un effected but as mentioned above previously the standard units were effected when the VW exported file site didn't work with the standard units. They seem to move this issue about possibly due to poor testing. Same fix would be required but on MIB2TSD directory. Worth noting.
Do Step 9, insert into unit.
Seat Step 10 as opposed to VW Discover System
A. Go into Navigation Setting, Manage Memory, with the SD / USB in the unit, tap Update My POIs (note no need to delete any previous users POIs they are always over-ridden during the update). Click Update my POIs. Next etc.
B. Under Navigation Announcement Settings, click "Note: My points of interest (POI)"
C. Map settings, Show POIs (click), Show Brand (Click), Select categories of POIs, click on the speed camera ones and any other users POIs so they display in the map
D. Test. The process can now be tested. Advanced settings, click Demo mode, enter start point of address to run the demo from, the other side of a known camera, now put in a destination that takes the unit in demo mode past the camera, you should see the camera on the screen and hear the audio warning. Stop route, top right of screen to exit, take off demo mode. Might also wish to do a long press on the left volume control for a reset to correct any zoom issue introduced by the demo mode.
Note steps 10 does not need to be repeated after any POI updates although (10D) can be done for checking.
Job done.
.However the contingency plan is now working for me see post 10 or read on further for a tail of wow.
The Car-net method VW have moved to doesn't do the beeps on Poi's so it wouldn't be any good for safety cameras. Skoda is moving to the same approach also no beep.
The VW have a record of ditching the POI import software, they did it with the RNS510 leaving people stranded. They have stranded their own Mib2 customers without car-net now.
Have tested the Skoda import method, very slow and problematic and didn't work on the Mib2 High and that's with and without the directory copy business explained below, so wasn't that. It might work with a standard unit but I think the Skoda site is being thrashed by VW people with files of 40,000 Poi's or so. Not so sure whether it was my impatience to the browser pop ups. But clearly on 40,000 Poi's it doesn't work once you try it in your car. It can only be a matter of time before that one is pulled one suspects given that Skoda is moving to a carnet approach (& that is no good for speed cameras, mib2.5 dimension as well where apparently you can specify by POI in the car for alarm sounds) so better to go with something independently installed on your own equipment than a webpage that may be pulled at any moment. Did that but currently doesn't work, have emailed the developer.
A better night after midnight with Germans tucked up in bed so you get the hardware more to your self. On the Skoda site you toggle off after each one paints to the screen since that saves the geographical processing of the data for the purposes of showing it on the screen. Exported out ok. Gpx I was using for the the cameras. ASC it's fussy about. I see thou nobody or few has any luck with getting the raw output into VW hardware and the directory trick covered below doesn't work either. Suggestion that Skoda is not computing the checksums correctly. Got to get back up to speed again to check that one out. Did that and yes they have the poi checksum and filesize wrong on the Poi directory as one German poster said on a German board. Then you recalc these plus the Metafilechecksum. A few tricks... got to test it in the car thou... there still might be a problem but incorrect checksums will hang it.
Breakthrough with POI Inspector see post 10 below - that's for the MIB2 High, the MIB2 standard should be be fine. Need release 6.4 or above for the MIB2High to work.
----
Main text when it was working via the VW site
This covers how to upload speed / safety cameras and other POIs to the Seat Ateca navigation and abridged step for the Seat Navigation Plus is currently required related to a bug introduced by VW in 2017 on their web based process.
Circa February 2017 the VW site that can be used to import speed camera databases (safety cameras) from third parties plus other POIs into the Ateca navigation system became broken for the MIB2High unit (Navigation Plus). Skoda vehicles as well as VW cars were effected, all the MIB2 High units. There is a metainfo2.txt file that is held in the main uploaded directory which is incompatible with the Discovery Pro MIB2 unit. There is a simple workaround. A similar fix was used for the standard MIB2 units previously when VW messed up the software. The standard unit POI files are held in the MIB2TSD files if this ever becomes an issue. If this issue appears on the standard unit as it has done in the past a variation to this fix can be used.
The issue was reported in a couple of threads
https://www.briskoda.net/forums/topic/385044-poi/?page=5
http://www.vwaudiforum.co.uk/forum/showthread.php/181365-Custom-POI-s
There are two workarounds one is to use an existing version of the metainfo2.txt file if you have one (i.e. you have done the process before and saved the files generated), the second is to open up the folder generated and to copy out from the "MIB2HIGH" as covered by CBEE in the thread above.
》
1) Create and download the POI files as normal using the VW Navigation Website
2) Open the zip file and you will see a folder called "PersonalPOI" and a file called "metainfo2.txt", open the folder called "PersonalPOI"
3) Inside the folder will be 3 other folders called "MIB2DE", "MIB2HIGH" and MIB2TSD", open the "MIB2HIGH" folder for the Discover Pro
4) Inside the folder you will see the same "PersonalPOI" and "metainfo2.txt" files, copy these to the root of your SD card.
5) Stick SD card in car and away you go
《
Both work in the Ateca Navigation. You can use either an SD card or USB to copy the files into the unit.
SETTING UP SPEED CAMERA / OTHER POI DATABASE
The process of uploading speed camera to the Ateca Navigation unit, you first need to select your database of speed cameras, I use the subscription Pocket GPS World, GPX format taking four files from the database, fixed and mobile, UK and Europe wide in the type Other. They call it "single file" select UK and then Euro downloading two zip files that contain the four GPX files and four bit maps. Other services which are free are available, Poiplaza is one. The choice is yours in terms of which you think is the most up to date.
After downloading the files which generally consist of the data file and the bit map picture of the camera graphic these are uploaded into the German VW website, in German. However this link provides an excellent step by step work through of the process. Step 1 is for Australia getting your POI files, substitute by the above, then follow the steps, then at the end we have the wrinkle in copying across onto an SD or USB stick the file and enabling the Ateca unit to show
Follow Primordial's first post
http://www.vwgolf.net.au/showthread.php?27941-MIB-II-Custom-POI-s-Speed-Cameras-etc
At step 2 you need the new VW link to call up the site that does the work (not the one that was shown in the original Primordial instruction which no longer works due to VW changing their site around)
http://rollout.volkswagen.de/content/de/brand/de/navigation/discover-pro/poi-listen-sammlung.html
Continue through the stages and repeat for additional speed cameras, make sure you click the "Annaherungs" to generate the sound for the cameras. Any other POIs can also be uploaded.
If using Pocket GPS World for the UK and European mainland for the fixed and mobile cameras the imported files within the VW software should look similar to this at the end of Step 5 with the sound marked up and the correct camera type showing:
Do Step 7 and stop
Step 8 is modified currently with the problematic VW website for those units effected.
New Step 8:
Extract the ZIP file to your SD Card or USB stick but with the modified procedure of CBEE mentioned above, extract onto a blank media. No other directories or files should be present on the SD card or stick else the import will not run.
A) Open the zip file and you will see a folder called "PersonalPOI" and a file called "metainfo2.txt", open the folder called "PersonalPOI"
B) Inside the folder will be 3 other folders called "MIB2DE", "MIB2HIGH" and MIB2TSD", open the "MIB2HIGH" folder for the Discover Pro
C) Inside the folder you will see the same "PersonalPOI" and "metainfo2.txt" files, copy these to the root of your SD card.
D) Stick SD card in car and away you go
The user POI database created by the VW site are imported onto the memory of the unit itself whether the maps are held on an SD card or SSD of the Plus unit.
As of June 2017, the situation is that the modified step is required for the Seat Navigation Plus unit which is "MIB2 High". The standard unit is currently un effected but as mentioned above previously the standard units were effected when the VW exported file site didn't work with the standard units. They seem to move this issue about possibly due to poor testing. Same fix would be required but on MIB2TSD directory. Worth noting.
Do Step 9, insert into unit.
Seat Step 10 as opposed to VW Discover System
A. Go into Navigation Setting, Manage Memory, with the SD / USB in the unit, tap Update My POIs (note no need to delete any previous users POIs they are always over-ridden during the update). Click Update my POIs. Next etc.
B. Under Navigation Announcement Settings, click "Note: My points of interest (POI)"
C. Map settings, Show POIs (click), Show Brand (Click), Select categories of POIs, click on the speed camera ones and any other users POIs so they display in the map
D. Test. The process can now be tested. Advanced settings, click Demo mode, enter start point of address to run the demo from, the other side of a known camera, now put in a destination that takes the unit in demo mode past the camera, you should see the camera on the screen and hear the audio warning. Stop route, top right of screen to exit, take off demo mode. Might also wish to do a long press on the left volume control for a reset to correct any zoom issue introduced by the demo mode.
Note steps 10 does not need to be repeated after any POI updates although (10D) can be done for checking.
Job done.
Last edited:
But I think that is a Garmin thing and nothing to do with the POI import. I need to spend a bit of time with a POI editor going through the GPX file to see what's in there.
)
.
