Process for Creating Contour Maps?

Does someone have wiki pages describing the best procedure to create contour maps for Garmins? It seems like a number of people are having some success but it doesn't seem to be very well documented. I'm working though trying to get groundtruth to generate .osm files with contours in them and then using mkgmap to create an .img file but mkgmap is segfaulting. In any case though, I'd like to get contour maps using better data than the STRM that groundtruth uses. My ultimate goal is to generate contour maps for a trip out to the Grand Canyon this summer. -- Jeff Ollie

Jeffrey Ollie schrieb:
Does someone have wiki pages describing the best procedure to create contour maps for Garmins? It seems like a number of people are having some success but it doesn't seem to be very well documented. I'm working though trying to get groundtruth to generate .osm files with contours in them and then using mkgmap to create an .img file but mkgmap is segfaulting. In any case though, I'd like to get contour maps using better data than the STRM that groundtruth uses. My ultimate goal is to generate contour maps for a trip out to the Grand Canyon this summer. Dear Jeffrey,
there are two different approaches: - Using srtm2osm to generate contour lines as osm files. - Using mkgmap to generate the contour lines directly. In both cases you'll need appropriate entries in your style file to determine which contour lines are mapped to major/medium/minor contours (0x22, 0x21, 0x20). I use # Contours take their name from the elevation setting. contour=elevation & ele ~ '\d*[02468]00' { name '${ele|conv:m=>ft}'; } [0x22 resolution 18] contour=elevation & ele ~ '\d+[05]0' { name '${ele|conv:m=>ft}'; } [0x21 resolution 21] contour=elevation { name '${ele|conv:m=>ft}'; } [0x20 resolution 23] for this purpose. Currently, the internal generation of contour lines can only cope with maps fitting into a single data tile. It can read SRTM geotiffs, ASTER geotiffs and HGT files. I use the following options: --contours --dem-type=ASTER --dem-increment=20 --dem-maxlevels=200 --dem-path=ASTER Hope that helps Christian

Christian Gawron wrote:
Dear Jeffrey,
# Contours take their name from the elevation setting. contour=elevation & ele ~ '\d*[02468]00' { name '${ele|conv:m=>ft}'; } [0x22 resolution 18] contour=elevation & ele ~ '\d+[05]0' { name '${ele|conv:m=>ft}'; } [0x21 resolution 21] contour=elevation { name '${ele|conv:m=>ft}'; } [0x20 resolution 23] for this purpose.
Hi Christain Could you expand on what this means please: ~ '\d*[02468]00' ~ '\d+[05]0' Cheers Dave F.

Christian Gawron schrieb:
there are two different approaches: - Using srtm2osm to generate contour lines as osm files. - Using mkgmap to generate the contour lines directly.
There is another one. Somebody has wirtten a little Python-tool to convert srtm files to osm - data files which can be processed with mkgmap. It is called Phyghtmap. http://wiki.openstreetmap.org/wiki/Phyghtmap It is much faster on a multicore processor than srtm2osm because it tries to use multiple threads. Best wishes Christoph

have done for srtm data for parts of US and viewfinder data in the alps started today to automate it for US based on NED 1 arc second data which is much better than SRTM. 1/3 arc second data is even better but requires to split most tiles and haven't done that yet. groundtruth didn't work at all for me and now it's all based on gdal* tools shp-2osm and mkgmap with some perl wrapping around. currently I use 25m contour lines and most tiles fit without splitting. Lars has all NED data and plans to start sharing at least 1 arc second data approx 60G, 1/3 arc second is approx 600G and can't be shared easily. We had some recent discussion on talk-us how this can be done. stay tuned On 21 Feb 2010, at 15:51 , Jeffrey Ollie wrote:
Does someone have wiki pages describing the best procedure to create contour maps for Garmins? It seems like a number of people are having some success but it doesn't seem to be very well documented. I'm working though trying to get groundtruth to generate .osm files with contours in them and then using mkgmap to create an .img file but mkgmap is segfaulting. In any case though, I'd like to get contour maps using better data than the STRM that groundtruth uses. My ultimate goal is to generate contour maps for a trip out to the Grand Canyon this summer.
-- Jeff Ollie _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (5)
-
Apollinaris Schoell
-
Christian Gawron
-
Christoph Wagner
-
Dave F.
-
Jeffrey Ollie