Hi,

your 'y' edit, a meaningless comment, has been cancelled as it caused too many problems, building and highway dragging inclusive.

ciao

Hi,

made is set of corrections with changeset/141672956 as your forest had disappeared from view,

ciao

ID Editor is actually very good at breaking multipolygon relations and not telling it is as it does not download the whole of the relations worked on.

I'd recommend you try out JOSM combined with the RelToolbox (Relation Validation plugin). It allows easy downloading of complete relations and will give a detail validation error/warning list of items needing fixing prior to saving. Quite a few roles were missing here as were many sections of inner area not made member. Also whole multipolygons were made inner to the forest. Can't do that, the outlines of the MP/SP needs selecting and made inner. If an MP is not properly closed or self intersecting it will tell you and where in the Validator pane.

cheers

Hi,

Fixed some of your WIP
relation/16329595

Think the forest needs splitting along the major roads.

ciao

Right, from aerial there's no way this is a foot/bike only 'path' with those street_side parkings not to speak of the bus stops.

See https://osmose.openstreetmap.fr/en/map/#item=1170&zoom=9&lat=46.105&lon=11.921&level=3&tags=&fixable=&issue_uuid=184a2777-8622-b4d2-19ba-3f240b2f64cd for the countless double polygons needing cleaning

See your name on an edit in Ukraine... The link below confirms the name:it
https://www.merano-suedtirol.it/en/partschins-rabland-und-toell/mountain-holidays/hiking-mountain-tours/hiking-trails/difficult-difficult-high-alpine-hiking-tours/121227231-peak-roteck-monte-rosso-3-336-m.html#:~:text=The%20Roteck%2FMonte%20Rosso%20peak,best%20divided%20into%20two%20days.

Don't know why the 'highest point' value on that page is noting 3333 when it's article headed as 3337. The rock pile on top :? Never understood the proximity thing too some insisting as tagging on peaks.

You have me blessing to put the reverted values back

Cheers

Hi,

Please be aware of this revert made by a now deleted account.

changeset/140693054

hmmm, mountain peak mapped by a now deleted account, then info is added which as the change set states 'CONFIRMED' by a wikipedia page and a wikidata link, then those tag adds are reverted by VEGETATION MAH BOIIIIIIIIIIIIIS who's account is now also deleted (the same as the first delete?). Wikidata is too unreliable now? Very dubious revert.

Hi

Converting parking nodes to areas comes with additional tagging requirements
orientation= perpendicular/parallel/diagonal
what type of parking
parking= surface / street_side
access=* yes / private

annd if not streetside you have to map a service way to it and parking_aisles.

A few wikis to read and apply
osm.wiki/Parking
osm.wiki/Parking

A parking as a node is still correct mapping so whoever set this up did not do his/her homework

ciao

So, another thoroughly broken maproulette race.

If you like dragging nodes around moving objects aligned to one set of imagery to another set of imagery you may, whether it adds is in the eye of the beholder. Just don't leave things broken like your previous edit here. Now the ways and gate you added analysis as... broken. Here your gate tags don't match that what's tagged on the service way (which is not oneway for everyone), something you do frequently, same as not adding direction on stop spots, traffic signals and so on, and parking areas that are not connected to a way directly need to be qualified too in some way so routers can get a way to them.
I don't follow you around, the QA progs I look at daily do, every single day and lead me to 'fix' those thing, but now there's that series of broken turns on the motorway you marked as WIP. It's better to not edit on thing onto any road that affects driver decisions finish them or leave them off if you don't know how.
So if you do things do it DIRFT and follow up with the QA reports. I make mistakes daily but I fix them no later the next day. Some run every 12 hours, some daily.

caio

Ciao e benvenuto su OSM

Un'osservazione degna di nota è che i tuoi edifici hanno un aspetto scadente. L'obiettivo è quello di mappare esattamente' i contorni. Presta attenzione anche al fatto che gli edifici non si trovino sopra gli alberi e le strade.

Buona mappatura

Hi,

you keep fixing stuff that aint broken, the routing on the east stations of the motorway is now completely unpassable according QA. Also mapping individual parking spaces is a perfect valid way of mapping, in fact some mappers don't do anything else, so I will run a revert on this as I have no intend to go look what you broke.

Have a nice day

Ciao e benvenuto su OSM

Quando si mappano gli edifici si prega di prestare maggiore attenzione alla precisione nel tracciare i contorni. Inoltre, è meglio usare le immagini ESRI come sfondo, poiché BING ha un offset e una torsione.

Quando correggi i nomi delle strade, controlla di aver applicato la correzione a tutte le sezioni di strada con lo stesso nome. Questo influisce anche sugli indirizzi, quindi anche questi devono essere controllati quando si fa riferimento alla strada con il nome modificato.

Buona mappatura

PS uses JOSM 18622 so not sure how this got past the pre-save validator.

High Guido,

Dropped a note to the mapper of this few days ago, still does not render after your repairs. He did quite a bit of bad mapping so dropped him more comments, that stuff does render now including a vineyard that was actually a motocross pitch (must be looking at old imagery)

ciao

Hi,

I've corrected this vineyard relation and removed the orchard as member. Also a part of the orchard is a swimming pool with small building or roof. See the fixes in changeset/140352630

ciao

Hi,

I've repaired this vineyard relation some members 3x part of the same one. 1 area looks in fact in ESRI like a motocross pitch and was made inner to the wrong vineyard way/512794097
Now the area renders correctly, i.e. no large white space
changeset/140352373

ciao

Hi,

This forest relation is pretty badly broken so it stopped rendering, multiple self intersections to be seen in OSM Inspector, indicatiing this happened some 9 days ago. Are you going to fix this or do we need to fly in Brigade Spéciale from abroad?

Let me know

ciao

https://tools.geofabrik.de/osmi/?view=areas&lon=5.29255&lat=43.99643&zoom=12&baselayer=Geofabrik%20Standard&opacity=0.65&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

Hi,

This element
way/1200757141
has to be removed from the meadow relation and deleted. The large meadow is now broken and does not render.

You have to repair it yourself as there are many more issues here to include meadow mapped in meadow with overlaps in to other areas.

ciao