Garmin PNAs The maps are compatible with nearly all Garmin PNAs with a color screen (e.g. Legend/Vista HCx and Cx, 60/76CSx, Oregon, Colorado,Edge 705, Nuvi, Streetmap).
Garmin Mapsource 6.16.3 or higher (Windows based PC/Wine/ Mac) Mapsource compatible – If you have not yet installed Mapsource – here is how to do it: http://velomap.org/tutorials/install-mapsource/ You can have several Mapsource Versions installed – see here for a description (German only – I will translate too english later): http://www.naviuser.at/forum/showthread.php?t=826 Attention: Mapsource versions before 6.16.1 do not show the map correctly and miss a lot of ways and streets.
Garmin Basecamp – Perfectly compatible starting with v3.
Qlandkarte GT (since version 0.18.3) – Cross Platform www.qlandkarte.org – no autorouting support though. Comes with most Linux distributions, binaries for Windows available, other platforms need to compile. I recommend Qlandkarte 1.0 or higher (go latest version!)
PDA, Smartphone (Windows CE or ME) Also compatible with Garmin Mobile XT (installable to any Windows Smartphone) – Garmin Mobile XT does. If you don't want to buy Garmin Mobile XT there is also Glopus (as of version 2.02 beta or higher) and Qlandkarte M which you can try. Neither of the latter supports autorouting however. Some POI are not shown on Mobile XT. Areas and ways/roads/highways are all correctly shown.
Incompatibilities: Iphone, IQue 3600 (and others?), old Garmin handhelds without color screen and (micro)SD card. Any other program or PNA that doesn't support .TYP-files. (like TTQV, Compegps,….)
.
Hi
I am using your maps on a Mac and with an Edge 605. I don’t really end up with the colours etc. that you show in your screenshots – I have a basic yellow background and the roads are all nearly indistinguishable: various shares of brown and pink (some dotted). What could be wrong?
Second, it is clear that the routing algorithm is working a bit – some great cycle routes are shown in a broad red line on the Edge, but often it is only little segments of a longer track. Is it your algorithm that yields this result or something to do with the Edge? Can I change the tags a little to help?
HB
You messed up the installation and are missing the .TYP-file somehow.
Thanks – that made a big difference