logo separator

[mkgmap-dev] Multilayer Map in MapSource?

From charlie at cferrero.net charlie at cferrero.net on Fri Dec 18 10:17:09 GMT 2009

Quoting Fips <doktor.fips at 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




More information about the mkgmap-dev mailing list