March 2023 - mkgmap-dev - The mkgmap lists

Commit r4907: Accept elevation values given in m with decimals in polish (*.mp) format and use Math.round() for the result of the convertion to feet instead of always rounding down.
by svn commit 06 Mar '23

06 Mar '23

Version mkgmap-r4907 was committed by gerd on Mon, 06 Mar 2023 Accept elevation values given in m with decimals in polish (*.mp) format and use Math.round() for the result of the convertion to feet instead of always rounding down. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4907

1 0

Re: [mkgmap-dev] The "Elevation=M" in the header of the polish .MP files does not work
by Vadim Karpov 04 Mar '23

04 Mar '23

Hi Gerd, > BTW ... This is one of the options. But this is not always convenient. For example, if CUSTOMIZABLE_ and _CONTOUR types are simultaneously used to create depth maps: the values of CUSTOMIZABLE_ types are strings and they will remain in feet. In addition, often only the source file in meters is available. And thanks a lot for the patch. But unfortunately I'm not a Java programmer and I can't test it. :( -- Vadim >Суббота, 4 марта 2023, 11:52 +03:00 от Gerd Petermann <gpetermann_muenchen(a)hotmail.com>: > >Hi Vadim, > >the code in mkgmap to change metres to feet expects int values. The attached patch changes this. >If nobody complains I'll commit this on monday. >I am not sure what to do with the extended marine types. > >BTW: Since your input to mkgmap is generated, wouldn't it be better to tell the generator to output the values in feet instead? > >Gerd > >________________________________________ >Von: mkgmap-dev < mkgmap-dev-bounces(a)lists.mkgmap.org.uk > im Auftrag von Vadim Karpov < bombur(a)mail.ru > >Gesendet: Freitag, 3. März 2023 09:46 >An: Development list for mkgmap >Betreff: Re: [mkgmap-dev] The "Elevation=M" in the header of the polish .MP files does not work > >Hi all! > >Thanks for the new build (r4906) ! >But the problem is only partially solved. > >Integer values (22 or 12) are converted normally. >But fractional ones (for example: 25.5 or 26.25) are still perceived by the compiler as feet. :( > >All values of subtypes 0-5 of marine type 09 (0x10900 … 0x10905) are interpreted exclusively as feet... > >PS: I can't place an example .MP file in this mailing list. I will send it personally. >Четверг, 2 марта 2023, 18:01 +03:00 от Gerd Petermann < gpetermann_muenchen(a)hotmail.com >: > >Hi all, > >OK, I see no problems to change this method in GType.java: > public static boolean isContourLine(MapLine line) { > return line.getType() >= 0x20 && line.getType() <= 0x22 && !(line instanceof MapShape); > } > >All I have to do is to change 0x22 to 0x25, right? > >Gerd > >________________________________________ >Von: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk< /compose?To=mkgmap%2ddev%2dbounces(a)lists.mkgmap.org.uk >> im Auftrag von Vadim Karpov <bombur(a)mail.ru< /compose?To=bombur(a)mail.ru >> >Gesendet: Donnerstag, 2. März 2023 14:38 >An: mkgmap-dev(a)lists.mkgmap.org.uk< /compose?To=mkgmap%2ddev(a)lists.mkgmap.org.uk > >Betreff: Re: [mkgmap-dev] The "Elevation=M" in the header of the polish .MP files does not work > >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(a)jagit.co.uk< /compose?To=rwb%2dmkgmap(a)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(a)lists.mkgmap.org.uk</compose?To=mkgmap%2ddev%2dbounces(a)lists.mkgmap.org.uk< /compose?To=%2fcompose%3fTo%3dmkgmap%252ddev%252dbounces(a)lists.mkgmap.org.uk >>> im Auftrag >> von Vadim Karpov <bombur(a)mail.ru</compose?To=bombur(a)mail.ru< /compose?To=%2fcompose%3fTo%3dbombur(a)mail.ru >>> >> Gesendet: Mittwoch, 1. März 2023 13:00 >> An: mkgmap-dev(a)lists.mkgmap.org.uk</compose?To=mkgmap%2ddev(a)lists.mkgmap.org.uk< /compose?To=%2fcompose%3fTo%3dmkgmap%252ddev(a)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(a)lists.mkgmap.org.uk</compose?To=mkgmap%2ddev(a)lists.mkgmap.org.uk< /compose?To=%2fcompose%3fTo%3dmkgmap%252ddev(a)lists.mkgmap.org.uk >> >> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > >-- >Vadim Karpov >Отправлено из Почты Mail.ru<https://trk.mail.ru/c/zzm979> > >-- >Vadim Karpov

1 0

The "Elevation=M" in the header of the polish .MP files does not work
by Vadim Karpov 03 Mar '23

03 Mar '23

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

4 7

Commit r4906: Treat also line types 0x23..0x25 as contour lines in method isContourLine()
by svn commit 02 Mar '23

02 Mar '23

Version mkgmap-r4906 was committed by gerd on Thu, 02 Mar 2023 Treat also line types 0x23..0x25 as contour lines in method isContourLine() http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4906

1 0

Re: [mkgmap-dev] Remove accentiuation
by 7770 02 Mar '23

02 Mar '23

Hi. For some reason it seems i am not able to perform this type of change in the finalize section. I get: Error in style: Error: (points:427): Unrecognised command '=' The lines in points finalize style looks like: name=* {name '${name}'} # next line to remove ' from names. name=* {set name='${name|subst:"'=>"}'} include 'inc/address'; Is this how it is supposed to look? Regards Karl On söndag 1 januari 2023 19:34:19 CET you wrote: > You can try in stylefile this addidional line : {set name='${name > > |subst:'=>}'} . This action shoult remove the apostrophe. > > thomas > > Am 01.01.2023 um 18:37 schrieb 7770: > > Hi and with wishes of a Happy new year. > > > > When preparing maps i use the setting > > --latin1 (same as --code-page=1252) > > > > This is good most of the time, since most language specific characters are > > replaced with plain latin characters. Cyrillic is transliterated to latin. > > > > In Ukraininan there is a softening letter (ь), when this is present in a > > name, it is transliteradet to ' (apostrophe). > > > > For example the city Львів becomes L'viv. This in turn makes searches more > > difficult since one not familar with the language may not know where the > > accentuation is placed. As a forigner i would not know if it is Lviv or > > L'viv. > > > > Is there some better code page to use to start with (still performing > > transliteration) or some way to ask mkgmap to remove the apostrophe from > > the text? > > > > > > Regards > > Karl > > > > > > > > _______________________________________________ > > mkgmap-dev mailing list > > mkgmap-dev(a)lists.mkgmap.org.uk > > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

2 1