This is about the 4th repair on this monster 1520 member forest in a few weeks. It keeps disappearing from the > 1km zoom view and being flagged in OSM Inspector. In 2km and less zoom nobody sees as that does not get re-rendered other then every month or so, low frequency. Anyway, you were about an hour ahead of me arriving to address the break, even before the 12 hourly Inspector update flagged it last night.

cheers.

For completeness see osm.wiki/Talk:Buses#Depots

For the funny bone, there's having the amenity of a sea-view towards the Adriatic in a very small window, south east looking from the pool deck.

Buone Feste.

I've confirmed there is indeed a large park section outline with DUPLICATE mapping ALMOST perfectly overlaying except for a few nodes (show white in ID Editor, the rest are grey).

Waiting with bated breath on your response how you're going to address this because it looks really bad in the Area view of OSM Inspector.

Hi,

Whatever you did, the forests have disappeared from the rendering in Standard OSM carto view and OSM Inspector shows a bunch of area intersections in the OSM Inspector Area view. What I see is new lines appearing that seem to duplicate already mapped boundaries. For sure if e.g. a bare rock zone is made inner of one forest and it also is partly on an adjacent forest, things break.

If you dont know how to repair this, as the Data Work Group to reverse the edit.

cheers

PS An edit set with 'no comment' is bad!

Hi,

Your 'fix from Osmose' actually broke the area in OSM Inspector, Area layer view, both a series of duplicate segments and unclosed ends.

layer: duplicate_segment
obj_type: r
obj_id: 4241604
nodes: 10624

layer: ring_not_closed
obj_type: r
obj_id: 4241604
nodes: 10624

Maybe you tagged the borders twice.

At any rate, when hitting Ctrl+F5 in the ID Editor view the protected area border disappears.

cheers

Ok, ill check it out Tomorrow. The issue is, there were 3 simple polygons. When merged you get duplicate segments on the former polygon-polygon borders. Not seen what the goned fixme said or the reason to merge, but someone reason ed it was fallow land, Something which is hardly anywhere used but Italy so I read in the wiki.

No idea. The line is white in ID edit mode i.e. what's there does require correction.

Hi

Whatever 'x' is supposed to mean as comprehensible comment, your merging of 3 farmland sections into a single multi-polygon broke the integrity. "layer: duplicate_segment
obj_type: r obj_id: 13578336"
Also your merging lost the history of what it was before.... there's no telling which part was corn and which cereal or why this land is tagged as fallow, meaning there's no active agriculture on this land for several years. The last imagery of ESRI suggests the land is in use. Did you survey to confirm the state is 'not-in-use'? Neither Bing shows this as in disuse.

ciao

This also closed a break in Prenestino-Centocelle \o/

Please be aware of the warning your edit caused "warnings:mismatched_geometry:unclosed_multipolygon_part" needing repair as what you did made the forest disappear from the rendered map.

node/9354116929

cheers

Hi there SarahDon,

Welcome to OSM.
You did buildings in Jordan, AND something in LonDon at the same time
on Armsby House causing everyone in-between to see this edit in their local change set list from England, to Algeria to Ukraine to the Sinai. On any future edits please only make changes in one country at the time, save and move to the next place. Ideally, the smaller the area covered the easier it is for other local mappers the review and understand.

Cheers and happy mapping.

You'll find quite a few of these 'w' and 'ù' suffixed fat finger typos of mine courtesy of my old keyboard. Not sure why I did not change it to parking=surface since I mapped both, the aisles added after inserting the hedges which made it no longer street_side. I'll make the correction.

Thanks for alerting.

ciao

Hi,

I've repaired your 'aggiornamenti' as you left the big orchard "layer: ring_not_closed obj_type: r
obj_id: 13567015"

see osm.org/edit?editor=id&relation=13567015

When closing an edit set, view it for any warnings. There's one on this one: warnings:mismatched_geometry:unclosed_multipolygon_part meaning the orchard did not have a complete ring. Normally ID Editor gives the warning before saving but not always which is why reviewing the edit set after saving is important.

cheers and happy mapping.

This correction was on a 5 year old issue :O)

Hi,

your change set generated 2 alerts of the warnings:mismatched_geometry:unclosed_multipolygon_part . Whatever you deleted yesterday in ways and nodes (deletion are hard to review). I had to repair MS residential area as it had disappeared from the map after OSM Inspector reported the triple open ends close to Via Vestina.

As for 'modifiche', the comment field is there to describe what you did... Changed road, added way, mapped track, add hamlet, in English or Italian, whatever you prefer. Reviewers than have an idea what went in the mapping work.

cheers

The fragmentation has been addressed which had it's origins in superfluous turn restrictions on 1 way streets connecting with 1 way streets. Humans will happily violate the traffic rules but navigators won't, 1 street close my house has double sized no-entry signs + elevated bright yellow kerbs and still the talking heads go straight against the traffic. Can't program for these.

ciao

The idiocy complete, yesterday Osmose signalled to add fuel:GTL_diesel, today Osmose signals this station does not. Hit the ignore button

Gas station update
16 Adriatica, Km. 433+170, nord 64028, SILVI
way/958797948 josm iD edit
fix-josm fix-edit
fuel:GTL_diesel

Hi,

According Osmose you missed 3 parts on Marruccini, so I fixed them

cheers

30376 1 5080 5080 similar name 1 E 14.31 42.41 way/207896445 (j) way/898436638 (j) Via dei Marrucini ✘ / ✔
30376 1 5080 5080 similar name 1 E 14.31 42.41 way/651607352 (j) way/898436638 (j) Via dei Marrucini ✘ / ✔
30376 1 5080 5080 similar name 1 E 14.31 42.41 way/898436637 (j) way/898436638 (j) Via dei Marrucini ✘ / ✔

Finally, with this oversized change set, a dozen a day crow-barring their way into my local history view, now I get it what this linked view does and how to use it to see where it actually hits the ground. Hit today on a farm track that had 20 nodes within 100 meters, virtually straight... a data import effort of 10 years ago. It's like those BAG imports in the Netherlands, Countless nodes per house in a row.

Thanks E de Wit, and Shaw_Sank may hope for redemption ;O)))