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_muenc...@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-boun...@lists.mkgmap.org.uk > im Auftrag von 
>Vadim Karpov < bom...@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_muenc...@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-boun...@lists.mkgmap.org.uk< 
>/compose?To=mkgmap%2ddev%2dboun...@lists.mkgmap.org.uk >> im Auftrag von Vadim 
>Karpov <bom...@mail.ru< /compose?To=bom...@mail.ru >>
>Gesendet: Donnerstag, 2. März 2023 14:38
>An: mkgmap-dev@lists.mkgmap.org.uk< 
>/compose?To=mkgmap%2d...@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-mkg...@jagit.co.uk< 
>/compose?To=rwb%2dmkg...@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-boun...@lists.mkgmap.org.uk</compose?To=mkgmap%2ddev%2dboun...@lists.mkgmap.org.uk<
>>  
>> /compose?To=%2fcompose%3fto%3dmkgmap%252ddev%252dboun...@lists.mkgmap.org.uk 
>> >>> im Auftrag
>> von Vadim Karpov <bom...@mail.ru</compose?To=bom...@mail.ru< 
>> /compose?To=%2fcompose%3fto%3dbom...@mail.ru >>>
>> Gesendet: Mittwoch, 1. März 2023 13:00
>> An: 
>> mkgmap-dev@lists.mkgmap.org.uk</compose?To=mkgmap%2d...@lists.mkgmap.org.uk< 
>> /compose?To=%2fcompose%3fto%3dmkgmap%252d...@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@lists.mkgmap.org.uk</compose?To=mkgmap%2d...@lists.mkgmap.org.uk< 
>> /compose?To=%2fcompose%3fto%3dmkgmap%252d...@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
 
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Reply via email to