Heath renders, but why the farmland has a role with the heath when it nowhere borders directly I do not know.

Lets try again: You don't delete ways that had been freshly mapped and tagged from survey, tags you did not port to the new way. You could have changed the designation and wiggled the nodes, retaining the history.

You deleted the way mapped the week before after survey. It included tagging with stop spot at the bottom end and other tags, the top half still fenced off.. Where did those feature tags go?

NOT DONE.

Not only that, you deleted the parking way I mapped at Mulino and than put a new one in place. Impressionante.

Lol, I've working on Spoltore for days and who pops up.

Thank you.

In web browsers on Windows F5 is refresh page view from cache (in ID editor History view here). Ctrl+F5 is the forced refetch of the data from the (OSM) website, refreshing the cache itself at the same time.

ciao

Hi, your "Inserimento elementi rilevati il 20/05/22"resulted in you breaking the forest outline with complete loss of rendering on all maps.

When you edit large areas, check back few minutes after saving in view mode and hit Ctrl+F5. If things keep showing you're fine. If things start disappearing in blocks or whole, something is wrong. Time to open the editor to find the reason.

ciao

Hi,

Per my previous comments, point 1), connections is a MUST.

On converting, yes, you can cut an already mapped way at chosen points and relabel to track and change the paving.

When tagging as track, the preferred is to select the grading in the wizard dropdown box. No need to specify the specific surface, in fact Osmose QA flags a combo of grading and surface as conflicting.
What looks like a track to a house can still be left as service road or driveway, in which case you use the surface qualifier, many options in the drop down list to include your dirt or the more general 'compacted' which says more about the expected driving experience.

cheers

However wrong it my be in your view, I've added this one and several others sections to the Aurelian wall relation. There are more parts that for whatever reason were never added to the relation on my inventory list. When the time comes I'll convert the 'site' relation to a 'proper' one. These walls haven't budged for 2000 years so it is not in any hurry. ;o)

ciao

weblink incl app at https://www.freeto-x.it
capacity 4

How to blow up the most expensive part of your e-car, the lithium battery, in 10-15 minutes, but your pedaggio is refunded.

ciao

Hi,

This building / relation has some issues, the change set summary already showing 3 warning. Most importantly though, how did this building rise to layer=5 (somewhere floating in the stratosphere ;o). For sure, one roundish building overlaps the square building, likely needing redrawing of the square to follow the outline of the round and removing the layer=5 and tag the roundish 1 as layer=1

If you navigate in OSM Inspector in the Areas view to this location you see there are quite a few issues.
https://tools.geofabrik.de/osmi/?lon=11.33603&lat=44.520912&zoom=11

Just so you know, the intersection the easiest to fix. The problem results in no building rendering there at all.

Let me know if you need help

ciao

Hi,

Please be aware that when you combine edits in far apart places, every mapper in between gets to see this edit listed in their local change set history for days. In this case some edit in Italy and another in Egypt. Try to avoid this, keep edits to a local area, save tem, then move to another place and make edits, save them, and so on.

All mappers only want to see change sets listed in their regular area of mapping.

Many thanks in advance for your consideration.

ciao

Hi,

Welcome to OSM. On your (MTB) tracks,

1) please make sure to connect the ends to other ways as else routing is impossible.

2) Don't map 1 way on top of another way that already was there.

Happy mapping

Ciao,

Benvenuto in OSM. Sulle tue tracce (MTB),

1) assicurati di collegare le estremità ad altri modi, altrimenti il ​​​​instradamento è impossibile.

2) Non mappare una via sopra un'altra che già c'era.

Buona mappatura

Hi, the immediate problem of the meadow was fixed. Looking at relation/3598469#map=12/44.5170/11.8048 it seems there are currently no broken relations with the large farmland, so not fixing what's not broken ;O)

ciao

Hi,

The problem persists, there's farmland mapped inside a greater farmland relation but the Stazione Radioastronomica di Medicina has now changed from inner to outer as it no longer is 360 enclosed by the same farmland relation, so I've changed the latter's meadow outline as temp fix. Fortunately this is just farmland and not forest as that would have given some interesting render results in Carto.

cheers

Interesting, apart from a 2 node change touching on North America and almost all of Europe, .... I've actually been using the tag source:width=estimated combined with width=n.n having 9000x use. Seemed consistent to me, source:name, source:maxheight ,:maxweight etc

FYI

Hi,

Your import is dumping building outlines with self intersection and smack on to of highways. such as this one way/1059184799
The buildings I checked have nothing at all to do with what is actually on the imagery so I suggest you reverse the whole and do the import(?) individually instead of 1100 in 1 go.

ciao

Moltissimo bennissimo ora. ;o)

👍

Just 10 easy fixes lurking in 1 place.

Hi,

Actually it was correctly tagged as area=yes. The real problem is that this area/path is crossing buildings to include it's obvious some node dragging took place of buildings while shaping the pedestrian area. Obviously the roof belongs on layer=1 and the pedestrian area needed connecting to the footways. QA will tell tomorrow if more problems exist here.

cheers