[ninesevenoh]

Hi,

Areas tagged heath are displaying as blue hatched areas on Locus using the elevate/elements themes when zoomed in (not sure how to check the zoom level number). Both the map (Great Britain Locus May 24th) and themes (Locus zipped) are updated to the latest versions today. Locus 3.70.9

Thanks

[JohnPercy]

I believe the map being used is an OAM one, not a LoMap, as I am able to replicate the issue using OAM maps and Elevate theme. The issue does not occur with my Voluntary theme.
The hatching appears to be marking access permissions but I cannot find the mapping details for the area in question. Blue hatching in Elevate indicates access restricted to customers or similar. Not far from your screenshot is another area hatched orange which indicates some kind of restricted access.
If Tobias cares to look into this, the location is in Wales and the UK Ordnance Survey coordinates are in the screenshot.

Voluntary and Velocity themes - https://voluntary.nichesite.org

[Tobias]

This is a heath tagged with access=destination, which is very unusual:
https://www.openstreetmap.org/relation/13569216#map=12/53.0099/-4.0687&layers=D

This tag is usually used for e.g. parking lots., I have never seen it used like this.
There are other tags that can be used for limited access for nature reserves etc.

Developer of Elevate mapstyle

1 Teilnehmer(n) gefällt dieser Beitrag

JohnPercy

[JohnPercy]

There is a similar issue with orange hatching at N 53.03004°, W 004.04295°.

Voluntary and Velocity themes - https://voluntary.nichesite.org

[Tobias]

JohnPercy wrote:

There is a similar issue with orange hatching at N 53.03004°, W 004.04295°.

Do you have the OSM ID of the object? Probably also access restrictions also added to a non-highway area.
I might filter this, but this kind of tagging just doesn’t make sense, and filtering every senseless tagging doesn’t make sense, too 🙂

Developer of Elevate mapstyle

1 Teilnehmer(n) gefällt dieser Beitrag

ChristianK

[JohnPercy]

@Tobias
I don’t have the osm id as my usual method (OSM Query from Locus) doesn’t show landuse areas and similar.
Here is a screenshot however.

Voluntary and Velocity themes - https://voluntary.nichesite.org

[Tobias]

JohnPercy wrote:

@Tobias
I don’t have the osm id as my usual method (OSM Query from Locus) doesn’t show landuse areas and similar.
Here is a screenshot however.

Thanks; when I have a screenshot I usually search in OSM a probably unique name, this lead me to this:
https://www.openstreetmap.org/relation/13612326#map=17/53.03011/-4.05431
This time it’s access=private, same mapper.

I’m not sure if it is a good idea to render access tags for areas only on highway=* or similar. Pretty hard to research combinations as access=* is so widely used.

Developer of Elevate mapstyle

[JohnPercy]

I decided for Voluntary to render access restrictions only on highways and parking lots, plus gardens. And as you said earlier, protected areas have their own tags and rendering.

Voluntary and Velocity themes - https://voluntary.nichesite.org

1 Teilnehmer(n) gefällt dieser Beitrag

ChristianK

[ChristianK]

I could filter those access and destination tags from landuse and natural with ease …

2 Teilnehmer(n) gefällt dieser Beitrag

mbe57, JohnPercy

[Tobias]

ChristianK wrote:

I could filter those access and destination tags from landuse and natural with ease …

Good idea, although I’m still not sure if there might be a good reason to display access on landuse/natural. I think this became an issue now as we introduced based_on_rel=mp and I’m using it as an equivalent to area=yes. For natural/landuse this isn’t necessary, as those are never non-filled closed ways – so maybe not adding based_on_rel=mp to natural/landuse would also help here and maybe other (yet to come) issues?

Developer of Elevate mapstyle

[ChristianK]

I took a look at Overpass-Turbo and there are a lot of access tags on various kinds of landuse/nature – down to private gardens.
I will remove the bound_to_rel for natural/landuse for a quick solution.

<translation>
	<name>add tag to identify mp relations in mapsforge for theme</name>
        <description>add tag to identify mp relations in mapsforge for theme</description>
		<match type="relation" mode="and">
			<tag k="type" v="multipolygon"/>
			<notag k="natural|landuse" v=".*"/>
		</match>
	<output>
		<copy-all/>
		<tag k="based_on_rel" v="mp"/>
	</output>
</translation>

1 Teilnehmer(n) gefällt dieser Beitrag

Tobias

[Tobias]

ChristianK wrote:

I took a look at Overpass-Turbo and there are a lot of access tags on various kinds of landuse/nature – down to private gardens.
I will remove the bound_to_rel for natural/landuse for a quick solution.

<translation>
	<name>add tag to identify mp relations in mapsforge for theme</name>
        <description>add tag to identify mp relations in mapsforge for theme</description>
		<match type="relation" mode="and">
			<tag k="type" v="multipolygon"/>
			<notag k="natural|landuse" v=".*"/>
		</match>
	<output>
		<copy-all/>
		<tag k="based_on_rel" v="mp"/>
	</output>
</translation>

Thanks. I could have changed this in the theme, but as written above it’s unnecessary for landuse/natural.
I’m just hesitating to remove access=* from landuse/natural as it seems to make no sense from my/our perspective for the moment, but it might make sense in countries with other legal tradition.

Developer of Elevate mapstyle

1 Teilnehmer(n) gefällt dieser Beitrag

ChristianK

[Autor]

Beiträge