188 > 18 (routes).
All is fine now, that is for the various bits that would need reviewing updating and adding, but that's wont be on my calendar or Todo.

The version inheriting is correct, the loss of the 18 routes on the V1 segment is not. It just should not have happened with just a simple way split, I know for a fact that route G21 was closed, Ran 3 weeks ago an analysis and the outcome was that all was fine. Reloaded the bookmarked link and the report states it's fine again:

https://ra.osmsurround.org/analyzeRelation?relationId=14341380&_noCache=on

caio

The ways themselves are not broken The split at the bus stop west side is OK since a 2 hike routes take a left at bottom of steps.

Ground imagery of Feb 22 shows a marked crossing missing from the map where the footway connects to the road. There's a bus stop painted on road, but no pole and a 3 car parking. Not going to touch anything more here as that what I came for has been corrected.

I know there are bugs in the history keeping. I.e. problems show up on the Inspector maps who's last tag is years ago, nothing in the history to indicate there was a change, yet there was a change. Yesterday a self intersecting building, V1, 4 years ago, yet the self intersection must be from the day before as the building renders in 2km zoom and below (1 week old render update) but not in 1km and up (render update in minutes). Just fix it and move on. If I could put my finger on it I'd report it, but cant. The OSM change log few iterations ago mentioned a better tag retention and history when splitting, but can't this here as a statement of improvement.

BTW, This is what Turbo overpass says

create way/1116858964
timestamp 2022-11-24 12:28
user micheleOSM3
version 1
changeset 129320775
highway primary
lanes 2
maxspeed 50
maxweight 5
noname yes
ref SS14
surface asphalt

https://dev.overpass-api.de/achavi/?changeset=129320775&relations=true

First there was a change from V14 to V15, then a split was applied at the bus stop where a hike route seems to have overshot to the south past the bus stop on east side. Cut point was fine, why all 188 route got lost, not just the hike part is mysterious.

As an aside there's a maxweight=5 on that road. Primary, brand new asphalt, doubt it. No source:maxweight tag to say what the source is of the restriction. Don't want to know but suspect it's something that proliferated when early there was 1 long way mapped in OSM for the SS14.

Caio

Hi,

Weeeell, you changed this one, but not the other 2 with the same 'typo', so I fixed that this morning since a soundex flag was raised. Now all 3 are same and correct.

ciao

Don''t know, V1 is the logical result of splitting a way but AFAIK it never deletes the relations. from from any section except when it pertains to turn relations, then the 'from' or 'to' part stays with the way that connects to the 'via' node.

At any rate, tomorrow we'll learn what the QA analysers think of this. One thing though i always do: When splitting ways and modifying I check afterwards of of routes in any direction crossing the modified ways are still whole. Here I checked the before and after this V1 part to see all were whole. Even the SS14 road number relation was broken.

Wish mappers would do this checking with new roundabouts which pop up like cup cakes. The number of routes I've repaired around this road feature are nearing countless.

cheers.

Well, when i reatored the 18 route relations on that way it had version V1 on it. Splitting does not lose relations, that is for sure. Cant even disconnect a way in ID editor long as a relation link exists on a way, but in JOSM anything is possible, just hit ignore and upload.

Why i got there is because I worked on route 21 and suddenly got msgd by Osmose it had a new gap again at tbat section then seeing that all route relations had a gap tbere with a bus stop for the 4n routes. There's a hiking route that branches off from that newly cut section.

Anyway it took time to fix and why i fixed all 18 is because if you touvh a way, Osmose makes you co-owner of all linked problems.

Ciao

Hi,

Whatever you did, turbo overpass says you were the last one to touch this road section, but 18 routes were broken here at this short road piece.

ciao

Hi,

Grazie per la mappatura

Potresti aggiungere il tag defibrillator:location di questi DEA che ne descrive la posizione, il colore, l'interno/esterno, la marca, ecc.?

Grazie

Thanks for mapping.

Could you add the defibrillator:location tag of these DEA's describing their position, colour, indoor/outdoor, make etc.?

Hi.

You used deprecated tags!

Please fix.

Mapper was sent a PM.

Hi,

Sembra che tu abbia interrotto la relazione della foresta con la tua modifica, infatti sembra che la foresta sia sparita e solo gli elementi che hai aggiunto hanno una relazione "interna" con ciò che non c'è più.

Vedere https://dev.overpass-api.de/achavi/?changeset=129198498&relations=true

Ciao

Hi,

You seem to have broken the forest relation with your edit, in fact it seems the forest is gone and only the elements you added have an 'inner' relation to what is no more.

See https://dev.overpass-api.de/achavi/?changeset=129198498&relations=true

ciao

Ciao

Il proprio link del sito web di CAI e https://www.caitivoli.it incl https://

Il prefisso https (sicuro) o http (non sicuro) nei collegamenti OSM è obbligatorio

Collego anche le estremità delle nuove tracce e rimuovo quelle vecchie.

ciao

Absolutely, he walked around this region quite a lot :O))))

thx and fixed in a jiffy.

Anglicization = canalisation ;P)

That area is under 'emergency and urgency' repair , reconstruction and Anglicization of the 'fiume' as it euphemistically is called. Under the auspices of the province of Pescara, since before the summer of 2021.

Of course the budgetted money ran out long before it was finished to include a snazzy redo of the cycle track.

I'll repair it in a little incl the relation.

thanks for asking.

Hi,

There's a supplemental tag another 'auditing' mapper pointed out to me when being asked about me using artificial_path=yes which I got from the UK , instead now using virtual=yes for paths to satisfy routing software, so I revisited all the cases where I the artificial.

Like so many tags barely found when scanning the Italian territory only.

ciao

Hi,

your 'small fixes' were combined across a 'very large area' from Italy to China.

Pretty please, do your fixes and save them on a country by country basis. Nobody needs to get these listed in their local history.

Thank you for doing so on all your future edits.

ciao

Link: Mappng etichette, osm.wiki/Changeset

PS The English wiki page is far more complete than the Italian translation.

A mere 177 issues resolved per the above summary. The area is still needing major surgery after this, triple bypass.

Riparazioni eseguite con ascia smussata su 3 percorsi.

changeset/129100580#map

'Solo' 177 problemi risolti, incroyable

Hi,

You seem to have extended a farmland area relations with many parts, residential etc that are not inside the farmland with the result of this relation picture: relation/13430810#map=13/48.7103/1.5750

You need to remove these 'external' parts from the version 16 farmland relation and create a new farmland area multipolygon and relate those parts to that that new relation as right now, the largest area does not show any farming has been mapped.

If this is a WIP (Work In Progess) you should have noted that in your change set comment... right now it's guessing.

Also see the below link for an analysis of your changes.
https://dev.overpass-api.de/achavi/?changeset=128609745&relations=true

ciao

In 3D imagery I see cars parked on your footway and a service road looping to the back of the Villa at the right side going to some 2 level underground/covered facility which is why I wondered about that footway designation for the part mapped.