Tweet
Not 100% sure with the Skoda file structure. Only have successfully modified the VW one after many hours of trial and error and many failed attempts.
But I would hazard a guess and say "All Skoda" is equivalent to "All Categories" in the VW file structure.
If that's the case, then it's the master list in which the unit uses for all categories searching.
I have only needed to modify my V5 map to include my custom POIs onto the master list.
In other words, I suggest you only have to do this if you want to include custom POIs into "All Skoda" subfolder, if you want the unit to return custom POIs in a "search for anything nearby" query.
But I have attempted not to alter the name of the equivalent folder to "All Skoda". So not sure whether that would stuff up the search every POI or not. Best not to rename it on first trial, if you want to successfully build your modified map incrementally.
My other tip is to just load all your custom POIs via SD card under a completely separate PersonalPOI.db3 file and 'Personal' subfolder.
Certainly this is my tip if you're loading a ****load of POIs like I have done.
Refer to my post #21 within the Collection of POI's sticky for better picture and explanation of what I'm talking about.
Too lazy to explain and repeat here.
In terms of playing around with distances, I would advise against it based on the fact that it just adds more time and effort required for the process and for very little gain.
You have to remember that our units don't make any audible alerts with POIs. So adjusting distances is a bit pointless.
Also, shorter distances will mean more clutter on the map as more POIs will be shown as you zoom in.
Just stick to the default distance.
But I would hazard a guess and say "All Skoda" is equivalent to "All Categories" in the VW file structure.
If that's the case, then it's the master list in which the unit uses for all categories searching.
I have only needed to modify my V5 map to include my custom POIs onto the master list.
In other words, I suggest you only have to do this if you want to include custom POIs into "All Skoda" subfolder, if you want the unit to return custom POIs in a "search for anything nearby" query.
But I have attempted not to alter the name of the equivalent folder to "All Skoda". So not sure whether that would stuff up the search every POI or not. Best not to rename it on first trial, if you want to successfully build your modified map incrementally.
My other tip is to just load all your custom POIs via SD card under a completely separate PersonalPOI.db3 file and 'Personal' subfolder.
Certainly this is my tip if you're loading a ****load of POIs like I have done.
Refer to my post #21 within the Collection of POI's sticky for better picture and explanation of what I'm talking about.
Too lazy to explain and repeat here.
In terms of playing around with distances, I would advise against it based on the fact that it just adds more time and effort required for the process and for very little gain.
You have to remember that our units don't make any audible alerts with POIs. So adjusting distances is a bit pointless.
Also, shorter distances will mean more clutter on the map as more POIs will be shown as you zoom in.
Just stick to the default distance.
Comment