[Juanjo]

Hi,

on March 2026 maps, multipolygon relations with highway=pedestrian and place=square are not rendered.

This one is rendering: https://www.openstreetmap.org/relation/5662178
This one is not: https://www.openstreetmap.org/relation/16657232

Both are multipolygon pedestrian areas. The second one has place=square, the first one don’t.

Cheers

[JohnPercy]

I can confirm this. It is not theme-dependent.

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

[ChristianK]

Well, I made a map with both Relations in Question.
IMO both Relations are rendered.
Both ID with all tags exist in every evolution of the render_prozess.

Whats NOT to be seen are the outdoor_seatings and some other stuff = no Layer or lower layer value.

Maybe I’m wrong – but as I said: The IDS are in the map – for sure.

[ChristianK]

And its the same mess here on OSM Map:

https://www.openstreetmap.org/relation/5662178#map=19/40.415309/-3.707457

EG. The Stairway to the Garage is not to be seen as its tagged Layer=-1 while the Relation itself is on Layer=+1

• Diese Antwort wurde vor vor 1 Monat, 2 Wochen von ChristianK bearbeitet.

[Juanjo]

ChristianK wrote:

IMO both Relations are rendered.

This is not how they used to be rendered in the past.

If you look at ‚Plaza Mayor‘ you see the virtual pedestrian ways that are usually added to allow routing. Normally they are not visible because the pedestrian area covers them.
The other relation, ‚Plaza de San Miguel‘, also has such ways (look at the arrows going around the building). In this case they are correctly masked by the pedestrian area

If you happen to have an old map at hand (unfortunately, I don’t) you can check the difference.

[JohnPercy]

In the previous map, the square was shown as a pedestrian area. Earlier today, just before my previous post in this thread, I updated the map and the pedestrian area no longer appears.
I don’t have a previous version of the map either!

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

[JohnPercy]

Here are some comparisons:

Latest map, Elevate

Older map, Elevate

Latest map, Voluntary

Older map, Voluntary

The older maps are V4 maps I just downloaded but the appearance is the same as maps just before the latest one.

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

• Diese Antwort wurde vor vor 1 Monat, 2 Wochen von JohnPercy bearbeitet.

[ChristianK]

I’v checked this again.
The Relation (no change in the last months) exists in the final osm file with both outer and inner.
There was no change in tagmapping and tagtransform. (as said, the IDs are exct the same as in original planetfile).

The only thing different is the Version of the mapwriter, its the 0.26.1
I will update to 0.27 and look if this makes a difference.

EDIT: No its still the same
Usually I find these Quirks in a few minutes – unfortunately not here .
The pedestrian Area SHOULD render, no idea why it does’nt.

Ok, lets sleep one night over this issue…….

• Diese Antwort wurde vor vor 1 Monat, 2 Wochen von ChristianK bearbeitet.

3 Teilnehmer(n) gefällt dieser Beitrag

mbe57, Tobias, JohnPercy

[ChristianK]

I removed place=square from the relation and still the same

The k=“highway“ v=“pedestrian“
is rendered right when I add this tag to the outer member of the relation.
!!!

No idea why this happens, the ####

OK, finally got it.
Relations are only resolved by MapsForgeWriter when these are type=miltipolygone.
THIS relations lost this tag, I have to check why.

So tags are only inherited from relation to members when type=multipolygone is in the tagset.

Fine that I had the first Motorcycle Crash after 35 years yesterday (those old men on their irons), so now I have a week or so for such things 😉

So, if there is more to clear …..

• Diese Antwort wurde vor vor 1 Monat, 2 Wochen von ChristianK bearbeitet. Grund: Multiply is lost in toolchain

3 Teilnehmer(n) gefällt dieser Beitrag

Juanjo, Tobias, JohnPercy

[mbe57]

Hope only a small metal, but no human damage, Christian!

[ChristianK]

mbe57 wrote:

Hope only a small metal, but no human damage, Christian!

Left ankle is a bit angry about that old man driving fast motorcycles……..

2 Teilnehmer(n) gefällt dieser Beitrag

Tobias, mbe57

[ChristianK]

OK – forget all what I’v written…

Places as multipolygones are handled a bit different from other objects in OAM.
These numerous place-objects are converted to NODES (only the names are important, the areas covered are usually rendered with other objects) and the type=multipoly tag is skipped.
= the type=multipolygone is filtered out with places, thats an old rule – nothing new
This reduces the overload (oceans, islands, citys…) of rendering a lot.

Now there is place=square and this tag is often combined with other objects like highway=* or similar in citys.

Why this worked so far and now fails = no idea…

I modified the rule for removing the type=multipoly in a way that combined objects carrying more than place=.* and esp. place=square are not destroyed.
(I hope nobody will have the silly idea to add those add. tags to objects like place=ocean)

	<translation>
		<name>remove multipolys from place</name>
		<description>remove multipolys from place</description>
		<match mode="and" type="relation">
			<tag k="place" v=".*"/>
			<tag k="type" v="multipolygon"/>
			<notag k="highway" v=".*"/>
			<notag k="amenity" v=".*"/>
			<notag k="leisure" v=".*"/>
			<notag k="place" v="square"/>
		</match>
		<output>
			<copy-all/>
			<tag k="type" v="cleared_multip"/>
		</output>
	</translation>

Will take place with the next update.

4 Teilnehmer(n) gefällt dieser Beitrag

Tobias, Juanjo, mbe57, JohnPercy

[Autor]

Beiträge