1) civ 3-14 relate to the address of the cemetery, not Togliatti. Added footway from parking to nr 7. There's steep stairs there and a board with 3 seasons opening hours. Also there's bollards there to prevent cars going in to drive to nr 3-6.
2) The post office stretch is 2 to 14 with 10+10 sub on concrete pillar right front of post office + 12+12b, building further down.
3) completed a turn restr. where via was missing and smoothed some roundabout flare shapes.
4) Added roles to the Togliatti relation.
JOSM warned for a bunch more... next time.

You put it there... node/11728064512 sans addr:street

Shop POI on first floor, no address, no addr:floor too. Where's that documented?

And that goes for the post office as well ?

PS On this CS there's also a series of housenumbers you put on the cemetery outline, a novelty to me, without street name. OSM wants addr:street

ciao

Hi,
Your worst roundabout layout yet
https://overpass-api.de/achavi/?changeset=148605588 Starts to look more and more like google style, boxcar driving. You also created several roundabout 'shortcuts' which are a router problem, no telling who's got right of way.. Flagged by multiple QA progs.

This was only a partial upload excluding a wood relation in WIP! Please do not try to correct while in WIP state!

thx

Hi,

It would have been the local CP, Gruppo Volontario Comunale di Protezione Civile Frisa (Ch), and per the www still at the Pz Piemonte square, a facebook entry at
https://m.facebook.com/groups/167258484960?view=info&refid=18

ciao

Well, the correct way is actually landuse=industrial + industrial=depot + depot=material + material=sand (the original mapping an early effort of mine). While this wiki is quite restrictive, depots are used for lots of things, and are actually called that here... deposito, Zero natural for sure. I'll make the correction in a little.

ciao

Hi,

No, it's NOT a natural=sand, that's tagging for renderer, it's a depot where sand is stored!

Kindly reverse.

PS I'd recommend to try JOSM as ID Editor is not up to complex multipolygon relation handling.

Hi,

I've done some provisional correction of this pile-up of errors, duplicate residential areas, duplicate fell zones, which are actually farmland and outline corrections for self intersection. See
changeset/148247119
For now the forest is rendering again, the fell needs to be taken apart and made into farmland and wood areas with inner farmyards and rural residential pockets.

ciao

This is what you did per Achavi deleting buildings inclusive
https://overpass-api.de/achavi/?changeset=148049957
The way is still on top/thru buildings, connects to a building corner.
You used the worst imagery possible at that (OLD Clarity). Bing/Esri is more current and has much better resolution.

Think this needs reverting and be redone correctly.

ciao

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