Not sure. I think the that the values for contourlines work like this. I'll experiment with the values later. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cdavilam@orangecorreo.es> Gesendet: Donnerstag, 2. Februar 2017 11:44:42 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Is height: filter working as described? I thought the special character was the comma that is added after the name. So there is some internal character that may affect displayed units, right? El 02/02/17 a las 11:31, Gerd Petermann escribió:
Hi Carlos,
I forgot to mention that the special separation character added by the height filter might tell Garmin softtware to convert the value (again). IIRC there is a flag in the img file which tells Garmin if values are in feet or metres, so you are probably right that the filter doesn't work as expected.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <GPetermann_muenchen@hotmail.com> Gesendet: Donnerstag, 2. Februar 2017 11:18:05 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Is height: filter working as described?
Hi Carlos,
this seems to be a problem in the documentation. I found this description for the height filter: "This is exactly the same as the conv filter, except that it prepends a special separation character before the value which is intended for elevations." ${ele|height:"m=>ft"}
This can be easily confused with the example for the conv filter: ${height|conv:"m=>ft"}
Looking at the source code the description for height seems okay. In your examples the rule doesn't place the argument in "", maybe that is the problem?
Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cdavilam@orangecorreo.es> Gesendet: Donnerstag, 2. Februar 2017 10:45:02 An: Development list for mkgmap Betreff: [mkgmap-dev] Is height: filter working as described?
According to style manual the rule natural=peak {name '${name|def:}${ele|height:m=>ft|def:}' } [0x6616 resolution 24] from default style should convert ele values from meters to feet, assuming ele is in meters, but this is what map shows for the following ele values: ele=500, map: ", 500 m" ele=500m, map: ", 500 m" ele=500ft, map: ", 152 m" So it seems to be doing right the opposite, converting from feet to meters. Also, with m=>ft rule, map should show ft units, not m. If I invert the rule from m=>ft to ft=>m this is what happens: ele=500, map: ", 46 m" ele=500m, map: ", 152 m" ele=500ft, map: ", 46 m" Now it seems when values are in feet conversion factor is applied twice. It seems when height: is used it always does a ft to m conversion first and then it applies what is specified in the rule. For the same examples, conv: filter gives the right values.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev