[mkgmap-dev] The "Elevation=M" in the header of the polish .MP files does not work
From Vadim Karpov bombur at mail.ru on Thu Mar 2 13:38:27 GMT 2023
Hi Yes. Types 0x23.0x24.0x25 are used to create bathymetric maps. Information from the MPCTypes.txt file ( TypViewer application): 0x02000=Contour Lines/MINOR_CONTOUR/Minor land-based contour line/Non NT 0x02100=Contour Lines/INT_CONTOUR/Intermediate contour (should be used for about every 5th contour line)/Non NT 0x02200=Contour Lines/MAJOR_CONTOUR/Major contour (should be used for about every 10th contour line)/Non NT 0x02300=Contour Lines/MINOR_BATHY_CONTOUR/Minor bathymetric, or depth, contour/Non NT 0x02400=Contour Lines/INT_BATHY_CONTOUR/Intermediate bathymetric, or depth, contour (should be used for about every 5th contour line)/Non NT 0x02500=Contour Lines/MAJOR_BATHY_CONTOUR/Major bathymetric, or depth, contour (should be used for about every 10th contour line)/Non NT >Четверг, 2 марта 2023, 12:01 +03:00 от Ticker Berkin <rwb-mkgmap at jagit.co.uk>: > >Hi > >My understanding of the default Garmin usage is that > 0x20..0x22 are land/height contours (Minor to Major) > 0x23..0x25 are sea/depth " " > >Ticker > >On Thu, 2023-03-02 at 08:52 +0000, Gerd Petermann wrote: >> Hi Vadim, >> >> I see code in mkgmap to handle the statement with Elevation=m or >> Elevation=M, but it is only used for the line types 0x20 .. 0x22. >> Do you have a good reason to use line type 0x25 instead? >> >> Gerd >> >> >> ________________________________________ >> Von: mkgmap-dev < mkgmap-dev-bounces at lists.mkgmap.org.uk > im Auftrag >> von Vadim Karpov < bombur at mail.ru > >> Gesendet: Mittwoch, 1. März 2023 13:00 >> An: mkgmap-dev at lists.mkgmap.org.uk >> Betreff: [mkgmap-dev] The "Elevation=M" in the header of the polish >> .MP files does not work >> >> Good afternoon ! >> >> I am using the latest version of MkGMap and trying to create a depth >> chart with isolines (types 0x24, 0x25). >> >> The problem is that the compiler interprets the depth specified in >> Meters as in Feet. >> The result is independent of the presence or value of the >> "Elevation=M" parameter. >> >> And I didn't find an alternative command line option. :( >> >> So how can I tell the compiler to treat all numerical depth and >> height values in an .MP file as meters and not feet? >> >> Thanks for the advice. >> >> PS: cGpsMapper works fine with "Elevation=M" of course. >> PPS: Example of polylyne defs: >> >> [POLYLINE] >> Type=0x02500 >> Label=21 >> EndLevel=3 >> Data0=(47.139263517000003,-122.560520313), ... >> [END] >> >> [POLYLINE] >> Type=0x02500 >> Label=12 >> EndLevel=3 >> Data0=(47.127846400000003,-122.562501059), ... >> [END] >> >> -- >> Vadim Karpov >> _______________________________________________ >> mkgmap-dev mailing list >> mkgmap-dev at lists.mkgmap.org.uk >> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- Vadim Karpov Отправлено из Почты Mail.ru -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20230302/8234bf55/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: 1635083738985.jpg Type: image/jpeg Size: 129784 bytes Desc: not available URL: <https://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20230302/8234bf55/attachment-0001.jpg>
- Previous message: [mkgmap-dev] The "Elevation=M" in the header of the polish .MP files does not work
- Next message: [mkgmap-dev] The "Elevation=M" in the header of the polish .MP files does not work
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list