
And just remember that if you ever use that option, maps will be incompatible (meaning frequent BSOD) on all old Garmin GPS like Vista HCx and Co - just like the current poi-adresses option crashes the POI search (in comparison to it not being used) and often causes BSODs (for me like 0.5 times daily). Garmin GPS are not suited for POI overload like it is happening with such options. It's just a really really dirty hack, to implement something that was not intended to be shown. The NT map format does have possibilities for such information - problem is that we have absolutely no clues about it. So don't expect Garmin will remotely improve here, as they already have a format that would be suitable for such information. On 26.10.2011 17:37, Henning Scholland wrote:
Of course you're right. There should be more Nodes in a fix distance to each other like MapComposer did it.
My intention was, that the user should be able to control for which ways these nodes were created. E.g. if I just want to display maxspeed-signs, these nodes should only be created if the way has a maxspeed-tagg.
Henning
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev