Hi,

Is your mapper name referring to how you enter data into OSM... by "import" or machine tracing? You may want to check the buildings afterwards as you've left several nonsensical self-intersection nodes. Red flags in OSM Inpector and no rendering with the affected objects.

ciao

To be precise, grotten warning for not adding the building= to the relation which is more dots as the type=building says it all, but that's me.

I know i know about this and most all times resisted. I like to test the, fill in the dots, and this is to see if the reverse warning shows up.

Hi,

note the correction I made as the race track was not showing up in the map due to self intersecting of the javelin and racetrack in the same multipolygon. Rule of thumb: Don't use MP when areas overlay.

changeset/119437761#map=18/45.68629/11.70645

ciao

OK, this has resolved the issue of no-render in standard carto mapping.

Compare the borders as shown in France Cadastre, which happens to overlay on Openstreetmap with what is mapped in OSM and one might conclude there's more to correct than just a ridge as boundary. You can actually see the OSM apped boundaries below in e.g. https://france-cadastre.fr/cadastre/daluis

I'll park this for the moment, bookmarked and see what can sensibly be done and not open a can of worms on the go

cheers again.

PS Daluis boundary left-top does seem to kind of happen to be on the Cime Fourchais peak boundary,... offsets not only here.

Unfortunately ID Editor does not have this overlay, only BDOrtho IGN which is labelled as best available so I see if I can extract anything meaningful out of cadastre.gouv.fr

cheers.

Now it has the proper hue in carto standard.

Looks like 1 side of Di Sotto is almost done, Easter just 10 days away :O)))

Boundaries should enclose an area and not go out and back on the same mapped line causing the self intersection. If you got a link to that cadastre section with the peak ill be happy to map it proper and not let the map issue sit for years, since 2011 to be precise, without address. :o}
Ciao

Hi,

Is there a part 2 (?) as right now, 4 months later, the area is an unclosed ring mess. Click on the Nizza Millefonti link and it will red line highlight the area showing large gaps in the relation.

ciao

It means that no none can see from your edit set up front if you made edits in any other mappers regular mapping zone. Also these big edit area sets stick to the top of the local history view for days. Bad practise.

2 Wikis
osm.wiki/Good_practice
osm.wiki/Changeset#Geographical_size_of_changesets

ciao again

Hi, Benvenuto da OSM,

From Doetichem's cops office to Algiers and Malta, cool doing that in your first edit set. The idea though is that you do edit on a local area, save them and move on to the next locale, do the deed, save, move on to the next locale and so on. Great to have, not great to get this listed in my local history and having to ask the question: Does this affect MY area of mapping in any way?

Thanks for your consideration in the second and subsequent edits

ciao from Italy.

Thanks for that. How it's done I don't know, "Small Fixes" the culprit wrote" , but it sure caused lots of boundary in the Balkans to light up in Inspector.

Hi Finix

It's all very well and fine you move things around by whatever imagery you have, but now the building passage shows it's not passing at the centre of the curved outline, rather now shows in a way for cars to surely lose their left mirror and plough thru the front shrubbery and that's literally with 'all' OSM ID imagery ;o)

ciao
George

Sorry, though saved separately, Osmose editor chose to combine them causing this large CS bound box

Hi,

You're welcome. Took 18 hours before the actual large wood area east of Tserovo started mapping in the 1km zoom view, 2km and up could take a month or longer to show. One more problem left: Around Tsevoro a dozen or so areas are tagged as inner to the region, don't know why, but it causes in Inspector areas view 'rings used in multiple rings and touching rings. https://tools.geofabrik.de/osmi/?lon=14.0617&lat=42.4379&zoom=11 I propose those role tags are removed consistent with the rest in the zone. Think a 'region' is a 'region' and should only be an overall outline boundary, no tag on anything inside (360 degrees enclosed). Long as this is not taken care of the large area will continue to headline in Inspector.

ciao from Italy.

OK. this resolved the rendering of trees in the grassland strips.

osm.wiki/Demolished_Railway

You should Not remap this, its RAZED,
gone entirely and by OSM policy it should be remove and will be removed again.