[JohnPercy]

Is it the case that the maps can’t display both MTB routes and cycle routes that run together? If so, is that a function of the mapping data or of the OAM processes?
If it’s because of the OAM processes, would it be possible to allow MTB routes and cycle routes to coexist?
Example: https://www.openstreetmap.org/?mlat=52.81166&mlon=-3.89035#map=18/52.81166/-3.89035

[Tobias]

This is probably some processing relict from the time when both had the same key, there’s still some work to do, see also here.

Developer of Elevate mapstyle

1 user thanked author for this post.

JohnPercy

[ChristianK]

Hi John,

This issue is resolved.
When the new Rendermachine is built and runnig it will be part of a big update.

Best regards
Christian

2 users thanked author for this post.

tartiflette74, Tobias

[ChristianK]

Hi @JohnPercy,

Have you noticed that there is a change of Route-Prozessing that effects the Themes.

There will be seperate REF tags for highways (as ususal) and cycle/mtb/hike routes.
This will resolve most of the issues we were facing the last years.
Esp. the long distance MTB-Routes are now fine and overlaying mtb/cycle/hike routes are shown much more accurate.

https://www.openandromaps.org/map-basics-2/tag-mapping

There are maps for testing and a modified Theme here:
http://ftp5.gwdg.de/pub/misc/openstreetmap/openandromaps/mapsV5/

Best regards
Christian

[JohnPercy]

Ref_cycle is not working for me for ncns such as https://www.openstreetmap.org/relation/1620344
Using test GB map and test Elevate theme or my personal test theme.

[ChristianK]

Hi John,

Thanks for feedback.
Thats really strange.
The ways are tagged right – here an example:

https://www.openstreetmap.org/way/41726706#map=18/52.27123/-0.89316&layers=D

	
An preprozessed right:
<way id="41726706" version="1" timestamp="1970-01-01T00:59:59Z" changeset="1">
		<nd ref="513696313"/>
		<nd ref="513696314"/>
		<nd ref="8896847052"/>
		<nd ref="3523451572"/>
		<nd ref="8896847053"/>
		<nd ref="513696315"/>
		<nd ref="3523451573"/>
		<nd ref="513696316"/>
		<tag k="name" v="Whitfield Way"/>
		<tag k="highway" v="residential"/>
		<tag k="ref_cycle" v="539"/>
		<tag k="network" v="ncn"/>
	</way>

Oh, everythings clear to me…

There are two ways to define an Tag with arbitrary values in Mapsforge V5.
tag=%f – for values (leike nth-floor in buildings, height of buildings etc
tag=%s – for strings like street names and (of couse) refs =
ref_cycle=%s as definition for an arbitrary cycle-ref
So a ref=”EV12″ is OK, however it seems that ref=”539″ ist treated as a number in mapsforge V5 rather than a string=”539″ an skipped. In UK this is to be seen very clear as most NCN have numeric refs.

Thats not funny, however we will find a solution.

[ChristianK]

Problem solved.
I identify type of value in preprozessing and add a prefix “#” if value is numeric.
Works great….

Again:
Thanks for your valuable feedback !

1 user thanked author for this post.

Tobias

[JohnPercy]

Elegant solution, thanks. Could you make the revised map available for testing, please.
What I don’t understand though is that ref worked perfectly fine before with ncn numbers. That’s to say current maps and themes show ncn even if the value is a number.

[ChristianK]

JohnPercy wrote:

What I don’t understand though is that ref worked perfectly fine before with ncn

This was the “REF” Tag.
Means you have some tags with arbitrary values in Mapsforge – a few.

For Ways:
https://github.com/mapsforge/mapsforge/blob/master/docs/Specification-Binary-Map-File.md#way-properties
In Short:Name,Housenumber,ref

For Nodes:
https://github.com/mapsforge/mapsforge/blob/master/docs/Specification-Binary-Map-File.md#poi-data
In short: Name,Housenumber,elevation

So far this is Mapsforge V4, and this works fine
All other tag/value pairs have to be defined in TagMapping.V4

In Mapsforge V5 there is an extension you can define more tags with arbitrary values.
This can be done by setting a tag with the value %f or %s in TagMapping.
.. as I do with (eg) ref_cycle=%s MEANS : Store all values for ref_cycle while value is a string.

So Mapsforge has to store all possible ref_cycle tag/value pairs as strings (=%s)
And this extension is buggy.

1 user thanked author for this post.

JohnPercy

[JohnPercy]

@Christian
Of course. Maybe I should have known that.
A silly question, maybe, but I presume you can’t just prepend a space to the numeric string as in ” 537″?

[ChristianK]

JohnPercy wrote:

but I presume you can’t just prepend a space to the numeric string as in “ 537″?

Thats worth a try, however I have to take care cause there are a lot of ‘trimms’ in the scripts.
Actually I have troubles with RAM consumption of this extension – I hope EMUX finds a solution.

1 user thanked author for this post.

JohnPercy

[ChristianK]

JohnPercy wrote:

A silly question, maybe, but I presume you can’t just prepend a space to the numeric string as in “ 537″?

Hi John,

Its working

3 users thanked author for this post.

mbe57, JohnPercy, Tobias

[Author]

Posts