It seems to be more difficult than I thought. The proposed simple change only works for render engine 2. With engine 1 and wetland order=4 or 5 the wetland polygon gets hidden behind the water polygon. 😬

render engine 1

wetland order=6 as it currently is, fairway hidden behind wetland (1) and cable area is hidden behide wetland (2) and seabed polygons are hidden behind wetland (X)

wetland order=5, it is better but cable area still behind wetland (3)

and when zoomed in, wetland polygon gets behind water polygon

wetland order=4, the wetland is not display at all

render engine 2

wetland order=4, it works as expected

I use diffrent colors for wetland and fairways, but this does not affect the z ordering issue.

rendering engine v1 is out of support for such complex issues, so it's relevant to be honest. On iOS version v1 was never supported

Fixed
Legacy engine:

OpenGL engine:

Thanks! But I do not consider this as fixed.

The no anchor area is still partially behind the wetland.

But this is maybe just a minor issue, like this it is definitely better than before, great improvement. Thanks.

Is the render.xml file actually updated when the app gets updated via the app store?

The order attribute was removed for sand_waves. But what about the other sea bed related keys/values?

Commit is attached osmandapp/OsmAnd-resources@8cc445a

I meant, in line https:/osmandapp/OsmAnd-resources/blob/master/rendering_styles/nautical.render.xml#L491 the order attribute was removed, but shouldn't it also be removed from the surrounding lines?

OsmAnd~ 4.6.0#710m, released: 2023-09-01
Latest Netherlands Frisia map downloaded
53.4582 6.1760

• as mentioned in comment above (objects rendered with wrong z order #17835 (comment)) the No anchor area is still partially covered by the wetland (middle left part of the picture attached)

This is because of sorting by area. Nothing to do in rendering style.

It does have to do with the rendering style, because the order is defined there. Transparent areas like seamark:type=cable_area should get a higher order. This won't hide anything since they are (semi)transparent and ensures that the auto order algorithm does not put them in the back. Danger areas already have a higher order assigned.

Some seamark:areas are matched by area=true others by cycle=true, some by both. cable_area is only in the area section.

Adding <case tag="seamark:type" value="cable_area" order="8"/> here would fix #17835 (comment)