Yes the thread is here with the documentation which has become the programmers official documentation:
https://forums.seatcupra.net/index....f-woe-vw-pulled-the-update-site-again.444799/
It's called "Tale of woe" but it isn't that title dates back to when VW pulled plug on the web based tool which took users POIs and created the VAG standard import for the infotainment systems in the range. You needed German then, so people posted up what to do, it was used world wide across VAG brands. There is a Skoda version but never worked so well so people used the VW site.
VW pulled that a few years back as VW connect import POIs but muted the ability to create a camera warble. A few people had been writing programs to do the process as side projects for interest. One is Poinspector also related to VW pulling the plug on the previous RNS equipment. Radas the programmer dusted the program down to work with the previous standard infotainment unit and the latest Mib2s standard and high (plus) work with mib1 as well. The fly in the ointment was when Seat produced the mib2 standard with WiFi that is only fitted to
Ateca and Leon My19 / My20 with the current version of firmware. They deleted the internal ability to import POI files.
So it's good for all VAG brands and models except those two identified above (You can do a test which is documented on the part number of the infotainment unit), works fine on the rest. Warbles as well. I use it to import destinations and speed cameras. Warble off for destinations
.
Back end of the thread gets a bit preoccupied with head banging on the
Ateca / Leon My19 / My20. Until Seat comes up with new hardware or firmware that issue will remain. The Spanish thread that identified the issue believes its hardware related, I think its firmware related. They were either short of memory in the unit so deleted the functionality from the spec or just deleted it or messed it up. The import file is a standard SQL database format which Poinspector creates with checksums and file signatures so the unit recognises the import. There is also an Excel script version(s) around to do it but the program works well allowing the POIs to be shown in Google Maps prior to import which script based solutions won't do I'm sure.
---
OK I will comment on Speedcamera databases being a bit of a GPS / Mapping expert. You have static cameras and mobile cameras. The latter being areas where the police do speed checks. Commercial databases can access public information of where the static cameras are. The mobile cameras require spotters, crowd sourcing. The program reads whatever database you have. I use the GPSworld ones which has a modest subscription, link provided in the thread. This is the one that Maypack refers to. The choice is yours. That one is updated monthly and you can add and delete cameras subject to validation.