OK, well I only came here because OSM Inspector highlighted duplicate segments on a grassland/scrub inner combo. When doing a correction run I often do some additional mapping like here creating scree zones.
ID Is not very good at working on large multipolygons as it does not load all elements (154 or so now). JOSM actually warns for that and has a button to fetch all parts so a full integrity validation can be performed. After 2 years I switched main mapping tool and now do 99.9% in JOSM, it was getting used to though, has some really slick features and great validation diagnostics, many speciality plug-ins.

buona mappatura

That's what I did while correcting inner role issues, but then your save annulled that, so I did it again. I think you working in ID and me in JOSM on the same forest zone puts things out of sink.

ciao

Think from building node history shown in ID Editor the drag happened in CS 132582990

Hi,

Could you please avoid mapping ways on top of existing ways. Twice now I've found today you doing this in recent weeks. Also ways below bridges are not tagged with tunnel+layer=-1, can be duly removed . Bridge area almost always is at layer=1 already.

As for your Nov.2021 JOSM version 18303, may I suggest you install OpenWebStart on top which automatically upgrades JOSM when there's a new stable version which is now Jan.2023 relation/18646. Lots of fixes and improvements since 2021 to include duplicate ways.

My 18646 gives 2 validation warnings when mapping duplicate ways
1) Overlapping highways (1)
2) Highway shares segment with linear way (1)

A way at layer=-6 would be very suspicious ;0).

BTW, how I got here is looking at the routing view of OSM Inspector. It updates every 12 hours and highlights mapping issues in different colours and icons. Duplicate ways are dark blue.

happy mapping.

More work needs done on the forest relation relation/10962910 to resolve more areas with forest rendering through scrub and agricultural lands.

Corr. in relation/15474883

Hi,

don't ask me about something I put there over 2 years ago. At any rate, looked and removed since it would have been smack front of the new McD. Transferred route links to civ.19

Caio

Jan 16 - Jan 24 is certainly an unnecessary repetition same as it would be with e.g. Su 13:00 - Su 23:00, Anyway, thought I'd mention the allnighters for the icecream shop.

Thanks for the link BTW, a handy in-browser check when baffled by an error flag.

ciao

Hi,

Ma.Sa opening hours flagged in QA, from 21:30 to 13:00 next day does not seem right too, maybe the other way. Anyway, this is the suggested format without correction of the seeming inversion
We 06:00-13:00,21:30-13:00; Th-Su 21:30-13:00; Jan 16-24 off

ciao

Hi,

I've made a bunch of inner/outer role and multipolygon outline corrections in the region in the last few days with you listed as the last editor, this morning another 3 MP areas. Please study for your future endeavours allowing prevention prior to these being flagged on OSM Inspector

https://tools.geofabrik.de/osmi/?view=areas&lon=1.81492&lat=44.59267&zoom=11&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

happy mapping.

OK render is restored

Actually, you removed tourism=hotel at the same time which is a tag that makes the name render in Carto Standard (but not the area so you get lots of white space on large event areas.)
It's BTW a choice whether retail (restaurant) or hotel (commercial services). so I went for the 1st, coins have just 2 sides ;p).

ciao again

Hi,

Slip off the typeboard, changed your building=yes for the hotel area to landuse=retail which facilitates rendering as well. (So happens had to research this for one I've passed many times near Collecorvino and finally mapped ;o).

ciao

Also removed non-power mast node from long powerline making bound box big, sorry.

Hi,

I looked at just 1 of 168 nodes: node/4591029145/history

Really makes sense, not, twice a value of foundry on the same object, but maybe you can wise me up and assure me that all is fine with this one and the other 167.

ciao

Corr. link percorso relation/15429041

Benvenuti in OSM.

Dopo aver esaminato il tuo primo contributo, ho creato un percorso a piedi su percorsi esistenti e ho rimosso il tuo percorso mappato sopra questi percorsi già esistenti. Vedi questa relazione del percorso relation/1542904

Usalo come riferimento quando pianifichi di creare altre percorsi pedonali locali.

Buona mappatura

This CS also addresses the forest relation over lapping, thus rendering over the grassland strip

Hi,

Sorry about the "incorrect" name change of operator. It's in fact the ID editor tag upgrade wizard that filled this in changing Transdev Valence Mobilité to Transdev Valence resulting in a mismatch of operator name between the route and the route master which then is flagged in Osmose the next day. ID simply asks "upgrade the tags".
The person I communicated w/ in past was bhouse (Github name suggestion index (NSI)), about 1-1.5 years ago, on another preset-wizard mistake.

ciao

Hi,

OSM Inspector flagged multiple relation issues on this forest with farmland pockets, so I overhauled and simplified down from 13 to 6 members, then added few more. No need to map duplicate inner outlines, simply select the forest outline and the inside farmland, then hit the + sign in the pop up menu and correct roles are assigned automatically in ID editor.

See changeset/132003667

ciao