[Taras D]

OSM’s Wiki indicates numeric values are valid for ladder, safety_rope, and rungs (length in metres or number of rungs). However, OAM’s tag-mapping for ladder, safety_rope, and rungs is restricted to a “yes” value and does not accept numeric values.

<!– tags_alpine –>
<osm-tag key=‘safety_rope’ value=‘sr_yes’ equivalent-values=’yes’ zoom-appear=’15’ />
<osm-tag key=‘ladder’ value=‘ld_yes’ equivalent-values=’yes’ zoom-appear=’15’ />
<osm-tag key=‘rungs’ value=‘rn_yes’ equivalent-values=’yes’ zoom-appear=’15’ />

As a consequence, all ladders with numeric values are excluded from OpenAndroMaps. Here’s one of several ladders (with numeric value) that I added to OSM: http://www.openstreetmap.org/node/5191411959

In addition, please modify the Elevate theme so that it can display ladders with numeric values.

OLD: <rule e=”any” k=”ladder” v=”ld_yes” zoom-min=”15″> <symbol src=”file:../ele_res/s_ladder.svg” symbol-width=”16dp” /> </rule>

NEW: <rule e=”any” k=”ladder” v=”*” zoom-min=”15″> <symbol src=”file:../ele_res/s_ladder.svg” symbol-width=”16dp” /> </rule>

This request is a result of a discussion about the Elevate (and Tiramisu) themes in the Locus Map forum:
http://forum.locusmap.eu/index.php?topic=5965.msg49633#msg49633

[ChristianK]

All I can do ist to tagtransform ladders with numeric values to ladder=ld_yes.
These ladders will be shown in the map.

Why?
I have to define exact tag/value pairs in Mapsforge TagMapping, I cant say ladder=* , this is impossible, except for same specials tags like ele, addr:housenumber, name,

	
<translation>
		<name>ladders with numeric values to yes</name>
		<description>ladders with numeric values to yes</description>
		<match mode="and">
			<tag k="ladder" v="(^[1-9].*)"/>
		</match>
		<output>
			<copy-all/>
			<tag k="ladder" v="yes"/>
		</output>
	</translation>

Well, December update is already running so this change will effect January maps.

Best regards
Christian

[Taras D]

Thank you for the explanation. I only have a superficial understanding of TagMapping rules. However, I understand your solution (transform numbers into “yes”). It is even better than what I proposed because there will be no need to modify the Elevate theme. Thank you!

[Emux]

Mapsforge maps v5 have now support for variable tag values!

Emux

[Tobias]

Emux wrote:

Mapsforge maps v5 have now support for variable tag values!
Emux

But it will take ages that certain apps will support it properly 🙁

Christian: I think the request was not just ladder, but safety_rope and rungs, too. Looking at the used values, there is some weird stuff, too:
https://taginfo.openstreetmap.org/keys/ladder#values
https://taginfo.openstreetmap.org/keys/safety_rope#values (especially sr_yes, I think someone took our values :-))
https://taginfo.openstreetmap.org/keys/rungs#values
I think it won’t make sense to support all, but at least values like “2.5” make sense by the definition. But anyway most values are yes, so we’re talking about a really tiny part, at least at the moment.

Developer of Elevate mapstyle

[ChristianK]

Tagtransform rule = include all values starting with numerics

	
<translation>
		<name>ladders with numeric values to yes</name>
		<description>ladders with numeric values to yes</description>
		<match>
			<tag k="ladder" v="(^[1-9].*)"/>
		</match>
		<output>
			<copy-all/>
			<tag k="ladder" v="yes"/>
		</output>
	</translation>
	<translation>
		<name>ropes with numeric values to yes</name>
		<description>ropes with numeric values to yes</description>
		<match>
			<tag k="safety_rope" v="(^[1-9].*)"/>
		</match>
		<output>
			<copy-all/>
			<tag k="safety_rope" v="yes"/>
		</output>
	</translation>	
	<translation>
		<name>rungs with numeric values to yes</name>
		<description>runges with numeric values to yes</description>
		<match>
			<tag k="rungs" v="(^[1-9].*)"/>
		</match>
		<output>
			<copy-all/>
			<tag k="rungs" v="yes"/>
		</output>
	</translation>		

Added “wire_rope,chain” as EQ to safety_rope

[Author]

Posts