Hi,

Don't know what gave you to think deleting the denotation tag (with erroneous value) from the trees, coincidentally 1 hour after another mapper mailed me about this, but I've restored the denotation tag and made it agricultural, which is what they are.

Ciao

Well, someone in level0 deleted the tags one hour after your comment, so that's that.
changeset/161002880

Confused.... loaded this 4 month old CS into JOSM, but there's no trees in it. Loaded the large dataset of the wider area, had been working on yesterday and today, refreshed. There's like 25.5K trees in them, 98% agricultural, even 2 monumental, but none with 'e' as tag value. JOSM is great as it summary lists all the tag values used for the natural=tree nodes found.

Hi ivanbrance,

Search but got got nothing in my saved datasets and following your TI link also returns zero... maybe someone already deleted the tag, bout which I would not be happy.
Did find though 6 with denotation=aù, so changed those to agricultural

Hi

Could you please review your building additions of your change set and correct either the buildings, the roads or both since there are amny crossings here from your seeming import with MapWithAI

Thanks

It's in JOSM and ID the same... start to draw a line and after setting the second node hit the F key and hold the F to quickly trace, description"Follow a line or area"..
Unfortunately I cannot use the F with ID editor. In the Firefox browser as the browser intercepts the F key to launch the page search function.

To learn all the ID Editor commands hit the ? key in the editor view. There are 3 tabs in the shortcuts help view, Browsing, Editing, Tools.

cheers

Hi,

When mapping areas inside outer areas you have to ensure that 100% of the 'inner' area nodes do not share any single node with the 'outer'. In this case I've mapped the woodland along the river areas around and removed several river areas as inner to the wood on the river banks. See changeset/160704218 how it was done. It can be done real quick since JOSM and ID Editor have a line trace/follow function to draw lines around areas.

Cheers

Hi,

Your boundary=disused is being flagged by QA. relation/18438206
Think you need to change the tag per lifecycle methodology to disused:boundary=administrative , Thetag disused:boundary used near 6000 times per taginfo: https://taginfo.openstreetmap.org/search?q=disused%3Aboundary opposed to boundarY0disused just 100,

cheers

Hi,

I think you broke relation/12025990/ as now the forest renders white and some inner areas show as related to the wrong forest. Twice outline forest in same relations, same with several inner. Think this edit corrects this, at least now I can see the wood again changeset/160343413

ciao

Hi,

NOT a cycleway, a cycle-lane already tagged onto the road. with cycleway:right:width=2
cycleway:right=lane
and tagged as part of the BI-6 route relation.

Ciao

Hi,

Re way/1235230271

You questioned if this service road is oneway. YES, the main road has a solid line divider at centre, so turning left coming from the east is not allowed. The same for the next one west I just mapped.

Ciao

Caio

Hi,

When you do these conversions, definitely not my idea to do so, where is it written that parkings have to be areas(?), you need to add the tag parking=surface when there's a way onto the area or parking=street_side like here when it's typically on the side of the road without a specific way touching it.

ciao

Gokd moaning ;o)

Interesting read, has no effect on routing since its tagged on a stop spot point rather than a junction crossing seen often in the US. A OSM wiki conspicuously absent, it is a tag part of a preset with all and minor as options. Curiously, checking taginfo/overpass, the use is plastered all over Italy, a few actually on a crossing, unlikely, where traffic light are often mapped , AND the rest of Europe. AFA Italy is concerned, think the tag can go, absent of any effect on navigators, albeit here, obligatory stopping is rarely abided by, all driving with a little angel on both shoulders. So please remove this excess tag

Ciao

Will do.

Hi,

Don't know why you map all these 1 member multi-polygons, emphasis multi meaning 1 MP has to has at least 2 members else they are simple polygons, which OSM likes much better. I've converted all these scrub, grass, farmland etc 1 member MPs in CS changeset/159197932 probably missing others in the artea.

ciao

The boundary I took care of yesterday. Ideally roads are not used as members of boundaries as that frequently results in breaking those when mappers work on the roads with boundary relations associated with them.

Unfortunately Via Tiburtina still has the service road and your new tertiary on top of each other. Laurenziano is fine, but I don't understand how that one changed from oneway to bi-directional. You need to confirm that as it has major routing implication.

👍👍👍
Problem disappeared from all OSMI views, so goodos

👍👍👍👍

Hi,

Unfortunately you've mapped a new tertiary road, node for node, on top of a previously existing service way. The proper way to map ways of a different class which were there before is to cut up the ways that need a different classing and change the tagging, so highway=service > tertiary. In short, you need to remove the tertiary ways you mapped on top of the existing ways and reclass the old to the new status. We do not delete old roads when they get up or downgraded and map a new one... that will result in the loss of now and way history.

Let me know if you need help.

cheers

PS: In case you dont read english, go to DeepL at https://www.deepl.com/en/translator#en/it/

Stranamente, ID Editor non ha dato un avviso di chiusura nel riepilogo delle CS, a meno che non si sia accidentalmente premuto il pulsante Ignora. Anche in questo caso il tag di caratteristica (key) è minimo in qualsiasi modo. Con l'applicazione JOSM questo non sarebbe mai sfuggito. Me ne sono accorto perché. A) Osmose ha segnalato il problema con un pin sulla mappa presto mattina, B) la strada è scomparsa da Carto standard. Di routine visito ogni CS in Carto map view, premo F5 dopo circa un minuto per vedere quali modifiche sono state apportate e quali no, e rileggo perché fare errori di typo è il mio forte. Le scritte in piccolo in JOSM sono difficili da vedere per me, in Carto sono più chiare.

felice mappatura.