
Hi Stefan,
Personally, I think the search weirdness we are seeing would go away if we could implement the extra indexing stuff (MDR file?)
The reason I believe that is because I installed the complete NZ mapset (not produced by mkgmap) on my gps and the road search function worked just as you would hope. But then I installed a small portion of the map and the road search then behaved like it does on our maps. So, I think that the extra file(s) in the mapset alter how the road search works.
By 'complete NZ mapset', do you mean a commercial (and therefor encrypted) mapset? I'm far from understanding the garmin file formats, but if there are non-crypted examples of maps with working street search, couldn't there been extracted at least some knowledge?
As an example I have here some OSM maps generated with some unknown tool (I asked the developer but got no answer) with working street search. So at least some tool out there knows how to do it.
So is someone knows this tool, wouldn't it be possible to generate simplistic example maps (like with one or two streets) to study the format of the files?
So my question is: are there any known tools that can generate street search enabled maps? I obviously only use mkgmap so far. Does cgsmapper have this functionality?
I agree, to improve the search functionality of our maps we need to learn what's missing/wrong and looking at simple examples of working maps can be very informative. Cheers, Mark