[Tobias]

ChristianK wrote:

Rendered Netherlands with variable keys for cycle/hike_nodes.
Result: Level 12 completely WHITE, level >12 single white tiles.
Cruiser says: Invalid Tag, don’t show the cycle/hike nodes

Next step: Rendering Netherlands V5 with standard V3 TagMapping.
.. slow approach to variable tags ..
However, regular June_Update is more important.

Oops, of course this had to happen. NL is one of the most complex maps already :-/
But as said above – no hurry, and yes, current update is more important, but probably less interesting 😉

ChristianK wrote:

This will kick in for shure when we take advantage of the variable tags for the ref/names of cycle/hike/mtb routes.
It would be perfect to have seperate ref/names.
Like
– ref_mtb_route, name_mtb_route
– ref_hike_route, name_hike_route
– ref_cycle_route, name_cycle_route
.. at least the refs would be fine.
However seperate refs allone will add 3 more Tags to ways, a close call…

Indeed, that would be a major improvement (also having fundamental things like elevation on ways and ref on nodes), but I think there has to be an additional change first to prevent running into the limit.
Would it be possible to copy every way which has route tags, and have only the route tags on this (and on the normal way the remaining highway, access etc. tags)?
That would at least work with the current way of having only one route of a kind (MTB, hiking, cycling), as this would be 9 tags max. Even better would be allowing to simultaneously show Int./Nat./Reg./Loc. or at least I+N/R+L routes, but this would demand even more doubled ways. And I totally forgot about OSMC, too… seems like there’s too much data 🙂

Developer of Elevate mapstyle

[ChristianK]

So, testing of the variable tag/key shows major problems with captions and some other quirks.
Im pretty shure that this could be sorted out with @EMUX over the next months.

@Tobias: Please change caption of hike_nodes to “ref” for the July update.
Netherlands and Belgium have _LOTS_ of combined hike/cycle nodes – we have to solve this issue ASAP, this is a real severe bug.

Best regards
Christian

[Tobias]

ChristianK wrote:

@tobias: Please change caption of hike_nodes to „ref“ for the July update.

Netherlands and Belgium have _LOTS_ of combined hike/cycle nodes – we have to solve this issue ASAP, this is a real severe bug.

I will, but the current map still has the old tag-mapping, right? BTW, could you change for all maps the zoom-appear of admin_level=4 to at least 6? Thanks.

Developer of Elevate mapstyle

[ChristianK]

Tobias wrote:

I will, but the current map still has the old tag-mapping, right

I’v rendered Netherlands and Belgium out of regular schedule. Those maps will be available from Sunday morning on for regular download.
All other European maps will be updated begin of July.

Currently Asia and Russia have to be rendered so unfortunately there is no free slot for an earlier update.

Tobias wrote:

admin_level=4 to at least 6

Done to Level 5, this should’nt cause any Problems

Thanks and best regards
Christian

[ChristianK]

ChristianK wrote:

I’v rendered Netherlands and Belgium out of regular schedule. Those maps will be available from Sunday morning on for regular download.
All other European maps will be updated begin of July.

Stopped it…
ref not working

to be continued

[ChristianK]

@tobias please help

I have a node (near Haarlem):

  <node id="46134508" version="1" timestamp="1970-01-01T00:00:01Z" changeset="1" lat="52.3125477" lon="4.5721922">
    <tag k="rcn_ref" v="17"/>
    <tag k="ref" v="59"/>
    <tag k="cycle_node" v="NLBE"/>
    <tag k="name" v="17"/>
    <tag k="hike_node" v="rwn"/>
    <tag k="layer" v="2"/>
    <tag k="rwn_ref" v="59"/>
  </node>

a render rule:

	<!-- hike nodes for rwn networks shown in both mapmodes -->       
	<rule e="node" k="hike_node" v="rwn">	
		<rule e="node" k="hike_node" v="*" zoom-min="12" zoom-max="14">	
			<circle r="12" fill="#ffffff" stroke="#fad55a" stroke-width="2.0" />
			<caption k="ref" dy="5" font-style="bold" font-size="15" fill="#5e5022" stroke="#ffffff" stroke-width="2.0" />
		</rule>
		<rule e="node" k="hike_node" v="*" zoom-min="15" zoom-max="17">	
			<circle r="17" fill="#ffffff" stroke="#fad55a" stroke-width="3.0" />
			<caption k="ref" dy="8" font-style="bold" font-size="21" fill="#5e5022" stroke="#ffffff" stroke-width="2.0" />
		</rule>
		<rule e="node" k="hike_node" v="*" zoom-min="18" zoom-max="21">	
			<circle r="22" fill="#ffffff" stroke="#fad55a" stroke-width="3.0" />
			<caption k="ref" dy="11" font-style="bold" font-size="28" fill="#5e5022" stroke="#ffffff" stroke-width="2.0" />
		</rule>
	</rule>

It does’nt work, the refs are not rendered in the circles.
If I replace it by “name” ist works

Please could you try to render the refs of the hike_node=* in the circles

Map: https://drive.google.com/open?id=1Ai2RnTjl8YsqqHOQ2_418gPbVEfbNYGh

Tested in Cruiser latest

THX

[Tobias]

ref is online possible for ways, not nodes with V3/4 maps.

Developer of Elevate mapstyle

[ChristianK]

Addr:housenumber ??

[Tobias]

ChristianK wrote:

Addr:housenumber ??

https://github.com/mapsforge/mapsforge/blob/master/docs/Specification-Binary-Map-File.md#poi-data
That should work

Developer of Elevate mapstyle

[ChristianK]

Thanks Tobias,

I re-uploaded Haarlem,map
https://drive.google.com/open?id=1Ai2RnTjl8YsqqHOQ2_418gPbVEfbNYGh

[Tobias]

ChristianK wrote:

I re-uploaded Haarlem,map

works as expected, just replacing name with addr:housenumber in the hiking-nodes section

Developer of Elevate mapstyle

2 users thanked author for this post.

R5O.nl, ChristianK

[ChristianK]

OK, took me 2 days to find out that the variable tag/keys are working like a charm on WAYS, but not on NODES.

I replaced the countless “ele” tags by ele=%f – working !! this means that appearence of ele pathtext now is driven by phyghtmap parameters only = on 10m countourline distance its possible to render pathtext each 50m without changing anything in tagmapping.
refs for routes are now stored in
cy_ref, hk_ref, mtb_ref
.. and this is working perfect fine

So there is a long ways to go to OAM/V5 cause a lot of preprozessing have to be completely rewritten to take full advantage out of V5.
However, I’m pretty shure that this will pay off.

… and I really hope that APPs will support curved pathtexts soon, this is a killer feature …

Best regards
Christian
.. still suffering from a MTB crash while sun is shining all day ..
🙁

2 users thanked author for this post.

Tobias, R5O.nl

[Tobias]

ChristianK wrote:

OK, took me 2 days to find out that the variable tag/keys are working like a charm on WAYS, but not on NODES.

Ouch… I don’t get why nodes and ways are always treated different in mapsforge, was probably okay at that time but now a bit of a design flaw.

ele=%f for ways is great, as it was only available on nodes. Lots of mountain huts are ways and contain elevation values, which couldn’t be shown, and we’ll find lot of other examples.

Best wishes for your recovery!

Developer of Elevate mapstyle

[R5O.nl]

I see this issue has been solved, using the July maps of NL and the latest Elevate Theme: great!
Many thanks guys!!!

2 users thanked author for this post.

ChristianK, Tobias

[Author]

Posts