Hi

You put a path cross buildings of half the village. Import? The edit set summary even warns i.e. before you uploaded.

Ciao

This example shows it in the simplest form grassland inside a forest. The grassland is a simple polygon, but if you couple this to a second grassland patch they together become a multipolygon (MP) where both are an outer member of their MP. When one is inside the forest, then only the 1 is made also an inner member of the Forest. Then you get the Forest being the outer in the MP relation and the grassland patch the inner

relation/282825#map=14/45.8261/6.6311

If you click on the outer way, only the forest is highlighted. If you click on the inner way, only the grassland is highlighted. You see it's in first order tagged as grassland, but then made an inner member of the forest MP.

In your case the ski zones are just being outlined on top of everything else so they're not defined as 'inner' to anything i.e. this relation/17261841 being a 3 part outer MP relation.

Nee het stoort mij voor geen meter, de process volgorde is wat stoort, een revert van de vorige wijziging(en), door mij, en dan het inlezen van de nieuwe. Daar wordt door Pascal Neis wekelijks een lijstje van gemaakt. Die van jouw: https://resultmaps.neis-one.org/hdyc-reverted-entities?uid=327477

De laatste node/2842289976, ook een BAG import revert en als je doorbladert lijkt het dat er behoorlijk mee gestrooit wordt in de Paesi Bassi.

Blijft, dat die gebouwen alle 6 recht of nagenoeg recht zijn maar door BAG kromgetrokken worden. Daarvoor was de Q functie toch gedacht om die beeldvervorming te corrigeren. Zou toch wel de zorg van de importeur moeten zijn, of?

ciao

All 3 have to have outer, outer outer roles

cheers.

PS Gebouw nr 6, echt recht, maar niet volgens de BAG import
way/281808532
Prullebak dat systeem.

Hi,

Da's interessant, jouw BAG updates veroorzaken bij mij node/object reverts op de lijst, 12 stuks in deze rondgang, vette thumbs down.

Over de vorm van die BAG gebouwen stel ik 'weer' vraagtekens. Zie hoekjes die met de beste wil van de wereld in geen enkele aerial zichtbaar is.

Helaas heb ik vanuit een buitenland IP geen toegang tot sommige beelden.

Recht is de boel ook niet bepaald, en volgens mij zijn bij dit grote gebouw de daken niet eens verbonden.

osm.org/edit?node=2857836931#map=20/52.89707/4.75372

Heb wel eens een draadje geopend over die BAG importen en de juistheid. Nog steed Quasi,

IIG 5 gebouwen op rij, 5x Q toets, 5x niet recht.

ciao

Also sorted members of vrs routes reporting gaps and disconnection. Refined lay of waterway area, move boundary to exclude farm tracks.

Buongiorno Piergiorgio.

This object way/1249999472 reports a self intersection in the OSM Inspector validation
https://tools.geofabrik.de/osmi/?view=areas&lon=7.64226&lat=45.10780&zoom=19&baselayer=Geofabrik%20Standard&opacity=0.50&overlays=duplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways%2Cduplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways

We've been discussing on the community forum what the meaning is of tags like height 76, layer 75.5 + min_height=0. Layers is a tag made for identifying if one object is higher or lower than another object, for instance a bridge is at layer=1 over ground.

Could you please fix the self intersection and give an understanding of this layer=75.5?

Many thanks and have a good day.

Rob

PS The Musical bridge in Rome has the multiple selfintersections reported in OSM Inspector. Please check and correct.

thx

Hi,

Repaired woodland relation in changeset/147759181

Why did you tag the woodland outline with man_made=cutline, separating it from the wood multipolygon relation? These are cutline-breaks in forest/wood area for special purposes. See wiki man_made=cutline

ciao

Apologies to all, if you're missing all the bright green in the Park Nat. d'Abruzzo and see all these grand white voids... someone last year, lets say, inadvertently, put the natural=grassland tag on this 496km square park area when substantially no grassland was mapped at all. It's parts prateria, scree, bare rock, farmland, scrub, wood, heath and whatever not yet identified. Very Very WIP, and oddly, in no Carto Standard zoom level the park name is seen rendering, but search does find the area/name.

Correct comment: Naz.Parco d'Abruzzo natural landcover, ways, outline refinements on prior mapped wood. man made rock heaps (pietro secco).

Hi,

v.v. liking trees showing on scree or bare rock, have I got news for you... Carto Standard does it one way and other data consumers do it their way. Look at e.g. F4Map and then zoom in to get the 3D rendition.
https://demo.f4map.com/#lat=45.9313011&lon=10.8752743&zoom=15&camera.theta=0.9

Enjoy

PS Consider trying out JOSM. Superior large multipolygon handling and validation.

Castel di Ieri area grassland, scrub, wood, rock, scree, buildings, ways, industr.area. Tag driveways as private same as gates.

Also restored original forest tag on area relation, changed to farmland in changeset/147455947

Hi,

Your area correction could have broken the large forest relation now no longer rendering. See relation/273807#map=13/45.7304/8.9337 zoom to 1km and hit Ctrl+F5 to refresh your browser cache to see the effect.

The problem is here according OSM Inpsector: https://tools.geofabrik.de/osmi/?view=areas&lon=8.93146&lat=45.77044&zoom=17&baselayer=Geofabrik%20Standard&opacity=0.50&overlays=duplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways%2Cduplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways

ciao

Hi,

Don't know why you deleted these ways in this edit set per https://overpass-api.de/achavi/?changeset=147176545 but it broke Via del Franzone and 5 routes. Repairs done in this change set
changeset/147287299#map=13/45.5282/10.2232

ciao and happy mapping with greatest care :O)

Hi,

Can you tell me where this object is?
way/939770064
The layer=-1 tag tells it's 1 level below the Piazza Lauro de Bosis which has not been mapped, only the ways that cross the square carrying that name. Also the area is connected to the ways at the surface i.e layer=0 so I think properly the highway tag of the area has to be removed and place=square to be added+name+surface details and if lit and the layer=-1 tag removed.
.
For tagging purposes, the correct tag for highway as an area is area:highway=* See wiki which has no Italian translation area:highway=*

Please let me know what that service area is and why it is at layer=-1 as right now it's causing duplicate edge warnings with adjacent pedestrian areas at ground level which a square would not cause.

On the whole, think you inherited these tags from previous mappers going back to 2021, the time being now to correct this.

thanks

Done

Hi

Welcome to OSM. In your first effort you mapped some builing on top of a driveway end. Either the building needs adjusting or the way posituon corrected. The summary above this edit warns for 1 such case.

Happy mapping

OK, well, removing the inner / outer is fine, still affixed to the bank / water outer ring and gone invisible as water supersedes in rendering. Maybe a flood prone tag, intermittent or map the water outside?

'coast' makes me think of the sea, banks would be of an inland water :O)

ciao