Hello guys, I'm currently new to generating maps for my Garmin eTrex Legend HCx. What I did till now: I generated a map with one single layer with mkgmap and installed that into MapSource. Now I found out that there's also the possibility to create a map with multiple layers (contours, basemap and routing map). Does anyone has an instruction which commands and ids I have to use? I already tried some things but without success till now. Thanks in advance
On 12/16/2009 11:57 PM, Fips wrote:
What I did till now: I generated a map with one single layer with mkgmap and installed that into MapSource. Now I found out that there's also the possibility to create a map with multiple layers (contours, basemap and routing map).
Does anyone has an instruction which commands and ids I have to use? I already tried some things but without success till now.
For getting multiple map layers on the GPS unit you need more than one family ID. The lowest map must not be transparent, the upper ones need to be. The template.args might look like this: gmapsupp=yes family-id=1234 product-id=1 family-name=Map1 draw-priority=25 transparent=no mapname=10000001 input-file=1.osm mapname=10000002 input-file=2.osm family-id=5678 product-id=1 family-name=Map2 draw-priority=28 transparent=yes mapname=20000001 input-file=3.osm mapname=20000002 input-file=4.osm For Mapsource things are different. Mapsource does not care about the draw priority. It draws the maps in the order of the mapname. So the transparent layers above have: - a higher draw-priority for the GPS unit - a higher mapname number for Mapsource You can import only one family at a time into Mapsource. So the above example will create a gmapsupp.img which is fine on the GPS unit, but you cannot load both layers into Mapsource. For this you need a second template.args file. This one just creates the TDB file for Mapsource using the images create in the first step: gmapsupp=no tdbfile=yes family-id=1234 product-id=1 family-name=Map1 mapname=10000001 input-file=10000001.img mapname=10000002 input-file=10000002.img mapname=20000001 input-file=20000001.img mapname=20000002 input-file=20000001.img If you use TYP files you need two seperate TYPs for the GPS unit (for the two FIDs) and one TYP for the mapsource (because there is only one FID). The FID is not stored in the map tiles, only in in the TDB file. So you can use a different one if you like without recreating the map tiles.
I used your templates. This is the first one: gmapsupp=yes family-id=1234 product-id=1 family-name=Map1 draw-priority=25 transparent=no mapname=10000001 input-file=10000001-bayern\10000001.osm.gz mapname=10000002 input-file=10000001-bayern\10000002.osm.gz mapname=10000003 input-file=10000001-bayern\10000003.osm.gz mapname=10000004 input-file=10000001-bayern\10000004.osm.gz mapname=10000005 input-file=10000001-bayern\10000005.osm.gz mapname=10000006 input-file=10000001-bayern\10000006.osm.gz mapname=10000007 input-file=10000001-bayern\10000007.osm.gz family-id=5678 product-id=1 family-name=Map2 draw-priority=28 transparent=yes mapname=20000001 input-file=20000001-srtm\20000001.osm.gz The files were splitted before using the mkgmap splitter. This is my command line: java -Xmx3500M -jar ..\mkgmap\mkgmap-r1436\mkgmap.jar -c template.args The *.img files, gmapsupp.img and osmmap.img are created. Next step: gmapsupp=no tdbfile=yes family-id=1234 product-id=1 family-name=Map1 mapname=10000001 input-file=10000001.img mapname=10000002 input-file=10000002.img mapname=10000003 input-file=10000003.img mapname=10000004 input-file=10000004.img mapname=10000005 input-file=10000005.img mapname=10000006 input-file=10000006.img mapname=10000007 input-file=10000007.img mapname=20000001 input-file=20000001.img and the command line: java -Xmx3500M -jar ..\mkgmap\mkgmap-r1436\mkgmap.jar -c template-tdb.args After this being completed, I used MapSetToolKit to install the mapset into MapSource. This worked, but I can't see any contour lines. If I just render the 20000001-srtm\20000001.osm.gz and install this into MapSource, I can see them. My MapSource version is 6.15.7, if that's relevant. Ralf Kleineisel schrieb:
On 12/16/2009 11:57 PM, Fips wrote:
What I did till now: I generated a map with one single layer with mkgmap and installed that into MapSource. Now I found out that there's also the possibility to create a map with multiple layers (contours, basemap and routing map).
Does anyone has an instruction which commands and ids I have to use? I already tried some things but without success till now.
For getting multiple map layers on the GPS unit you need more than one family ID. The lowest map must not be transparent, the upper ones need to be. The template.args might look like this:
gmapsupp=yes family-id=1234 product-id=1 family-name=Map1 draw-priority=25 transparent=no mapname=10000001 input-file=1.osm mapname=10000002 input-file=2.osm family-id=5678 product-id=1 family-name=Map2 draw-priority=28 transparent=yes mapname=20000001 input-file=3.osm mapname=20000002 input-file=4.osm
For Mapsource things are different. Mapsource does not care about the draw priority. It draws the maps in the order of the mapname. So the transparent layers above have: - a higher draw-priority for the GPS unit - a higher mapname number for Mapsource
You can import only one family at a time into Mapsource. So the above example will create a gmapsupp.img which is fine on the GPS unit, but you cannot load both layers into Mapsource. For this you need a second template.args file. This one just creates the TDB file for Mapsource using the images create in the first step:
gmapsupp=no tdbfile=yes family-id=1234 product-id=1 family-name=Map1 mapname=10000001 input-file=10000001.img mapname=10000002 input-file=10000002.img mapname=20000001 input-file=20000001.img mapname=20000002 input-file=20000001.img
If you use TYP files you need two seperate TYPs for the GPS unit (for the two FIDs) and one TYP for the mapsource (because there is only one FID). The FID is not stored in the map tiles, only in in the TDB file. So you can use a different one if you like without recreating the map tiles.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 12/18/2009 12:03 AM, Fips wrote:
After this being completed, I used MapSetToolKit to install the mapset into MapSource. This worked, but I can't see any contour lines. If I just render the 20000001-srtm\20000001.osm.gz and install this into MapSource, I can see them.
Does the TYP files for FID 1234 contain line styles for the Garmin codes you use for the contours? Or don't you use a TYP at all? If you put the gmapsupp.img from step 1 onto a GPS unit, do you see the map + contours? Does the SRTM layer cover the correct area?
My MapSource version is 6.15.7, if that's relevant.
Yes, with 6.15.7 I often see the contour line numbers only, but not the lines. 6.13.7 works much better, although if you zoom and pan around a lot in Mapsource sometimes the upper layers disappear. After zooming out completely, restarting Mapsource and zooming in again everything is fine. Others have reported the same problems. I don't know if these are Mapsource bugs or map issues.
Ralf Kleineisel schrieb:
On 12/18/2009 12:03 AM, Fips wrote:
After this being completed, I used MapSetToolKit to install the mapset into MapSource. This worked, but I can't see any contour lines. If I just render the 20000001-srtm\20000001.osm.gz and install this into MapSource, I can see them.
Does the TYP files for FID 1234 contain line styles for the Garmin codes you use for the contours? Or don't you use a TYP at all?
I don't use any TYP file at all. I wanted to keep the process as simple as possible for my first steps.
If you put the gmapsupp.img from step 1 onto a GPS unit, do you see the map + contours?
I didn't try that yet. I will do that on the weekend or perhaps at the beginning of the next week.
Does the SRTM layer cover the correct area?
There's something strange going on. I downloaded the srtm data via srtm2osm. This is my command: Srtm2Osm.exe -bounds1 47.2 8.9 50.6 13.9 -large -corrxy 0.0005 0.0005 -step 20 -cat 400 200 -o bayern-srtm.osm (I tried wih corrxy and without) The Longs/Lats, I got from the bayern.osm. I opened it and looked at the bounds-tag. <bound box="47.26543,8.96835,50.57129,13.84947" origin="http://www.openstreetmap.org/api/0.6"/> The strange thing is that when I run the splitter on that osm-file, I get the following: Exact map coverage is (49.45424795150757,8.904247283935547) to (49.45590019226074,8.907573223114014) Trimmed and rounded map coverage is (49.4384765625,8.876953125) to (49.5263671875,8.96484375) But that doesn't fit with the coordinates I gave to srtm2osm. How can that be?
Quoting Fips <doktor.fips@web.de>:
Ralf Kleineisel schrieb:
On 12/18/2009 12:03 AM, Fips wrote:
After this being completed, I used MapSetToolKit to install the mapset into MapSource. This worked, but I can't see any contour lines. If I just render the 20000001-srtm\20000001.osm.gz and install this into MapSource, I can see them.
Does the TYP files for FID 1234 contain line styles for the Garmin codes you use for the contours? Or don't you use a TYP at all?
I don't use any TYP file at all. I wanted to keep the process as simple as possible for my first steps.
If you put the gmapsupp.img from step 1 onto a GPS unit, do you see the map + contours?
I didn't try that yet. I will do that on the weekend or perhaps at the beginning of the next week.
Does the SRTM layer cover the correct area?
There's something strange going on. I downloaded the srtm data via srtm2osm. This is my command: Srtm2Osm.exe -bounds1 47.2 8.9 50.6 13.9 -large -corrxy 0.0005 0.0005 -step 20 -cat 400 200 -o bayern-srtm.osm (I tried wih corrxy and without)
The Longs/Lats, I got from the bayern.osm. I opened it and looked at the bounds-tag. <bound box="47.26543,8.96835,50.57129,13.84947" origin="http://www.openstreetmap.org/api/0.6"/>
The strange thing is that when I run the splitter on that osm-file, I get the following: Exact map coverage is (49.45424795150757,8.904247283935547) to (49.45590019226074,8.907573223114014) Trimmed and rounded map coverage is (49.4384765625,8.876953125) to (49.5263671875,8.96484375)
But that doesn't fit with the coordinates I gave to srtm2osm. How can that be?
This may or may not be related, but when you split an SRTM file with splitter, you may need to use the --mixed switch. http://www.mail-archive.com/mkgmap-dev@lists.mkgmap.org.uk/msg02908.html -- Charlie
Hey charlie, thanks for the clue. That was the reason for the problem. So for everyone with the same problem: You have to use the mixed switch with the mkgmap splitter because otherwise it will only parse the osm-file until it finds the first way- or relation-tag. Now I need to optimize the process :) Thank you and happy holidays! charlie@cferrero.net schrieb:
Quoting Fips <doktor.fips@web.de>:
Ralf Kleineisel schrieb:
On 12/18/2009 12:03 AM, Fips wrote:
After this being completed, I used MapSetToolKit to install the mapset into MapSource. This worked, but I can't see any contour lines. If I just render the 20000001-srtm\20000001.osm.gz and install this into MapSource, I can see them.
Does the TYP files for FID 1234 contain line styles for the Garmin codes you use for the contours? Or don't you use a TYP at all?
I don't use any TYP file at all. I wanted to keep the process as simple as possible for my first steps.
If you put the gmapsupp.img from step 1 onto a GPS unit, do you see the map + contours?
I didn't try that yet. I will do that on the weekend or perhaps at the beginning of the next week.
Does the SRTM layer cover the correct area?
There's something strange going on. I downloaded the srtm data via srtm2osm. This is my command: Srtm2Osm.exe -bounds1 47.2 8.9 50.6 13.9 -large -corrxy 0.0005 0.0005 -step 20 -cat 400 200 -o bayern-srtm.osm (I tried wih corrxy and without)
The Longs/Lats, I got from the bayern.osm. I opened it and looked at the bounds-tag. <bound box="47.26543,8.96835,50.57129,13.84947" origin="http://www.openstreetmap.org/api/0.6"/>
The strange thing is that when I run the splitter on that osm-file, I get the following: Exact map coverage is (49.45424795150757,8.904247283935547) to (49.45590019226074,8.907573223114014) Trimmed and rounded map coverage is (49.4384765625,8.876953125) to (49.5263671875,8.96484375)
But that doesn't fit with the coordinates I gave to srtm2osm. How can that be?
This may or may not be related, but when you split an SRTM file with splitter, you may need to use the --mixed switch.
http://www.mail-archive.com/mkgmap-dev@lists.mkgmap.org.uk/msg02908.html
participants (3)
-
charlieï¼ cferrero.net -
Fips -
Ralf Kleineisel