OSM Map On Garmin/mtb map/old

From OpenStreetMap Wiki
Jump to navigation Jump to search

Progress

Using OSM Composer mtb maps can be easily created. In a few days I will post a nice howto on here including a fully configured osm_composer set. Maps don't include a DEM but contourlines (configurable). The text below will then be exchanged (not needed anymore), I will archive it under a different name as using osm_composer creating maps takes more time and tiles including contourlines can't cover nearly as big regions. (1°*1° are possible however (if it's not too mountaneous - this applies to the "Wiener Voralpen". As in the main alps contourlines take enourmos amounts of data (whole of Austria takes about 300MB in garmin .img format with ARC3" data - using ARC1 this will go up to probabely 3000MB - best would be to use contourlines from maps like Kompass, Amap, etc but their contourlines are in no way compatible to any open licence....), that's already quite large). I hope that providing a good and easy to use interface configuration here, many mountainbikers will get interested in OSM and start contributing their tracks to OSM. To be frank, until now it wasn't easy to get any sort of decent garmin mtb map out of OSM, this has changed so interest should potentiate.--Extremecarver 23:05, 28 October 2008 (UTC)

  • Therefore this page is now archive only

If you want to download readymade mtb maps lease go to [1]

Prerequisites

on Linux

  • Install the Perl modules IO::Uncompress::Bunzip2 from CPAN
    • IO::Uncompress::Bunzip2 depends on Compress::Raw::Bzip2 and IO::Compress::Base; Debian/Ubuntu users can build packages with e.g. dh-make-perl --build --cpan Compress::Raw::Bzip2
  • Download mkgmap and ungzip it
  • Download osmcut.*.jar from here, and put the .jar in the mkgmap directory
  • Download an .osm file from somewhere (e.g. one of these planet.osm extracts)
  • Download [[2]] cyclingmap_typfile.pl and save it to mkgmap directory
  • Download [[3]] cycling_map_features_typfile.csv and save it to "resources" directory in mkgmap directory
  • Download [[4]] 4011.typ and save it to the directory where you want to put your maps afterwards

on Windows

  • Install Active Perl, Additional Package Bundle-IO-Compress-Bzip2 is necessary (use the "Perl Package Manager" to installe the module)
  • Download mkgmap and ungzip it
  • Download osmcut.*.jar from here, and put the .jar in the mkgmap directory
  • Download an .osm file from somewhere (e.g. one of these planet.osm extracts)
  • Download [[5]] cyclingmap_typfile.pl and save it to mkgmap directory
  • Download [[6]] cycling_map_features_typfile.csv and save it to "resources" directory in mkgmap directory
  • Download [[7]] 4011.typ and save it to the directory where you want to put your maps afterwards

Running it

  • perl cyclingmap_typfile.pl yourosmfile.osm (or yourosmfile.osm.bz2)
  • Note Osmcut.jar is deactivated in mtbmap.pl (by # placed), you have to enable it for bigger country.osm files like Germany or Europe. You may try to render it, but I don't know whether it will render and I don't know whether the Unit will show it. Countries like Austria are fine though.
  • It will create a .img file, which you should copy across to your GPS with Mapsource or Sendmap or QLandkarte
    • Integrate the .TYP file into your map. If working with mapsource under "MS Winodws" this is done easily with Mapset Toolkit http://cypherman1.googlepages.com/ or otherwise you can use sendmap. Note: Without typfile this map will not show many details and look horrible. You can also write it manually to the registry. With linux only possibilitie is integration with sendmap. (please correct if possible otherways)

Outpout

Notice: you can see the ping/turquise cycleroutes even though the way they are using might also be tagged with other attributes that usually prevail. Blue Dotted is Cycleway and not Footway (red dotted)

  • If you want to edit your typfile you can either edit directly in text and then compile, use Maptk or the online editor

http://ati.land.cz/gps/typdecomp/editor.cgi which is easier for beginners.

  • Unsure wheter it displays Umlauts. Does not do Cycle Nodes yet. There are pecularities on mouseover - these are due to mtbmap.pl which is based on preprocess.pl by Richard as found on the "old" cyclemap. The implementation using a TYP file is cleaner, but a little bit more difficult than the old way. Typfiles are only used by Garmin Color PNAs, so Garmin Units with B/W display should use the "old" cyclemap procedure (however there shouldn't be many B/W users left and they can still use the old procedure).
  • Severe Limitations: It is very difficult (Perl Programming in the mtbmap.pl) right now to react to two different tags which are used to tag the same way in the database. This is done in mtbmap.pl - however this process has to be greatly overworked.

Polylines mkgmap limitation

  • At the moment, Polylines that are tagged (hexadecimal) between 0x2b and 0x3f will not be seen in Mapsource (as well as 0x17). They will show up on the units themselves however. Mkgmap doesn't yet support 3 byte definitions so polylines can only be integrated from 0x00 to 0x3f (hexadecimal).


To Do

  • Needed: Someone who can rewrite the cyclingmap_typfile.pl to include mtb trails and tracks (leave the cycletracks inside)

Tags are here:

See also

Retrieved from "https://wiki.openstreetmap.org/w/index.php?title=OSM_Map_On_Garmin/mtb_map/old&oldid=2041445"