[Tobias]

This is an old discussion which wasn’t finished. The tags are still in tag-mapping, but are not processed/transformed, so these tags are empty.
As mapsforge doesn’t support route relations out of the box Christian wrote some scripts that copy the relations values to the underlying ways, also in a hierarchical order if there are several relations on the same way. Only Christian can really give you the proper answers here.

Developer of Elevate mapstyle

[tartiflette74]

Thanks Tobias; another question: it seems that cycling and hiking routes have a „ref“ tag, but no „name“; however I would like to display the full name as a pathText, instead of the cryptic ref, at very high zoom levels. Would it be possible?
Out of curiosity, are the tags associated to a route duplicated in the map file, for each way associated to the route (and possibly each tile for each way)? This would be a reason for not including the full name that can be pretty long… But then maybe it could be optimized somehow.
Thanks!

Hike, Ride & Sight! theme
Live GPS Tracking for Locus Map

[Tobias]

tartiflette74 wrote:

Thanks Tobias; another question: it seems that cycling and hiking routes have a „ref“ tag, but no „name“; however I would like to display the full name as a pathText, instead of the cryptic ref, at very high zoom levels. Would it be possible?

No, as the tags from the relations are copied to the underlying ways, it’s only possible to have ONE name, and that is already occupied by the name of the underlying way (usually the street name). In mapsforge there are only a few variable fields available, for ways that’s name, ref and addr:housenumber, see here.

tartiflette74 wrote:

Out of curiosity, are the tags associated to a route duplicated in the map file, for each way associated to the route (and possibly each tile for each way)?

No, as written above, only processed and copied to the underlying way. It could also be possible to copy everyway for each relation, but this also has it’s disadvantages (see piste routes), and would mean no backward compatibility and other issues.

Developer of Elevate mapstyle

1 Teilnehmer(n) gefällt dieser Beitrag

tartiflette74

[tartiflette74]

Tobias wrote:

No, as the tags from the relations are copied to the underlying ways, it’s only possible to have ONE name

OK; would it be possible, when multiple routes of the same importance (e.g. network=nwn) share the same way, to concatenate the ref tags? I.e. for 392092977, ref=GR5 - GRV ? Edit: bad example, as one is iwn and the other nwn; I have not found yet an example with the same network level. Anyway, maybe the ref tag could also be concatenated for different levels…
Thanks !

Hike, Ride & Sight! theme
Live GPS Tracking for Locus Map

[Tobias]

tartiflette74 wrote:

Anyway, maybe the ref tag could also be concatenated for different levels…

There are already several refs combined for several routes – when cycling/mtb/hiking routes are on the same way.
And when tags for local/regional/national/international cycling/mtb/hiking routes including refs when there are several of the same level, we can get to so many refs that it doesn’t make sense.
Christian was also experimenting with different possibilities, see here for example, but stopped the effort:
https://www.openandromaps.org/oam-forums/topic/rwn-numbers-replaced-by-rcn
https://www.openandromaps.org/oam-forums/topic/v3-v4-v5

Developer of Elevate mapstyle

[tartiflette74]

Hi, I am still a bit confused with routes; it seems a single way can be associated to both a walking and a cycling network (e.g. here). But still not to both a cycling and mountain bike network (e.g. here): only the cycling network is shown in oam. Is this correct?
Thanks!

Hike, Ride & Sight! theme
Live GPS Tracking for Locus Map

[Tobias]

tartiflette74 wrote:

But still not to both a cycling and mountain bike network (e.g. here): only the cycling network is shown in oam. Is this correct?

No, that’s not correct. If you look at the tag-mapping, the routes have three different keys:

<!-- cycle_relations -->
<osm-tag key='network' value='icn' zoom-appear='7' />
<osm-tag key='network' value='ncn' zoom-appear='7' />
<osm-tag key='network' value='rcn' zoom-appear='10' />
<osm-tag key='network' value='lcn' zoom-appear='12' />
<osm-tag key='network' value='ucn' zoom-appear='12' />
<osm-tag key='network' value='hcw' zoom-appear='13' />
<osm-tag key='network' value='mtb' zoom-appear='11' />
<osm-tag key='network_mtb' value='lay_mtb' zoom-appear='11' />
<!-- hiking_relations -->
<osm-tag key='hknetwork' value='iwn' zoom-appear='7' />
<osm-tag key='hknetwork' value='nwn' zoom-appear='8' />
<osm-tag key='hknetwork' value='rwn' zoom-appear='12' />
<osm-tag key='hknetwork' value='lwn' zoom-appear='12' />
<osm-tag key='hknetwork' value='uwn' zoom-appear='12' />
<!-- mtb_relations -->
<osm-tag key='mtbnetwork' value='imn' zoom-appear='6' />
<osm-tag key='mtbnetwork' value='nmn' zoom-appear='6' />
<osm-tag key='mtbnetwork' value='rmn' zoom-appear='8' />
<osm-tag key='mtbnetwork' value='lmn' zoom-appear='10' />
<osm-tag key='mtbnetwork' value='umn' zoom-appear='10' />

Only one key per way is possible, so you can have one hiking, one cycling and one mtb route on the same way.

Developer of Elevate mapstyle

[tartiflette74]

Thanks Tobias; however, as I mention, this way (in latest Alps West) does not show the mtb route with the elevate mtb theme, even if I disable all ucn/icn/ncn/rcn/lcn rules to make sure they do not overlap. So I think there might be a problem in the route scripts?
Thanks!

Hike, Ride & Sight! theme
Live GPS Tracking for Locus Map

[Tobias]

Have you any older example? The planet file for the current maps is from 27.03.21, the latest changes in these routes are from 29.03.21

Developer of Elevate mapstyle

[tartiflette74]

I last added this way to mtb routes on March 24, even if the routes themselves have been modified afterwards for other ways.
Anyway, another older example: here (mtb and bike routes)

Hike, Ride & Sight! theme
Live GPS Tracking for Locus Map

[Tobias]

Sorry for not getting back earlier… in your second example, no route is shown on the roundabout which is also strange.
What might be the cause for the first problem – MTB-routes used to be network=mtb and therefore only could be on a way if there wasn’t another network=* (depending on the priorities in Christian’s scripts). It might be that network=lay_mtb is still using the same logic, but it shouldn’t need it anymore.
Only Christian can answer that, as those scripts aren’t public.

Developer of Elevate mapstyle

[ChristianK]

Hi,

There was a design flaw in the scripts.
mtbnetwork=* was in tagmapping but not in the scripts.
This will be resolved in update for May.

So: mtbnetwork=imn|nmn|rmn|lmn
will be added in the script = will be included in the maps.

In this way, it should also be possible in future to show the national/regional routes more clearly than the local mtb routes.

However, for preserving compatibility with the themes and for testing the new tags the
network=mtb will stay in the maps for one or two months.

@Tobias: do you really need the network_mtb=lay_mtb?

I will provide Austria/UK maps for testing

Best regards
Christian

2 Teilnehmer(n) gefällt dieser Beitrag

Tobias, tartiflette74

[Tobias]

ChristianK wrote:

@tobias: do you really need the network_mtb=lay_mtb?

Not after mtbnetwork=imn|nmn|rmn|lmn is working 🙂 network_mtb=lay_mtb was just the better alternative to network=mtb (although it didn’t work as expected, see above).

But shouldn’t mtbnetwork be like in tag-mapping?

<!-- mtb_relations -->
<osm-tag key="mtbnetwork" value="mtb_icn" zoom-appear="6"/>
<osm-tag key="mtbnetwork" value="mtb_ncn" zoom-appear="6"/>
<osm-tag key="mtbnetwork" value="mtb_rcn" zoom-appear="8"/>
<osm-tag key="mtbnetwork" value="mtb_lcn" zoom-appear="10"/>
<osm-tag key="mtbnetwork" value="mtb_ucn" zoom-appear="10"/>

Developer of Elevate mapstyle

[ChristianK]

Tobias wrote:

But shouldn’t mtbnetwork be like in tag-mapping?

I’v changed this to imn,etc cause this would follow the scheme of network/hknetwork.
If you don’t like it I will move back to mtb_###

[Tobias]

ChristianK wrote:

Tobias wrote:

But shouldn’t mtbnetwork be like in tag-mapping?

I’v changed this to imn,etc cause this would follow the scheme of network/hknetwork.
If you don’t like it I will move back to mtb_###

For me mtbnetwork=imn|nmn|rmn|lmn is fine and logical, probably no one has implemented the old, not working tag-mapping anyway.

Developer of Elevate mapstyle

1 Teilnehmer(n) gefällt dieser Beitrag

ChristianK

[Autor]

Beiträge