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.

Salve,

Perché hai rimosso il tag highway da Via Casale? L'ho ripristinata in quanto, A) tutte le strade necessitano di una targhetta highway=*, B) ha reso il tratto di raccordo con i passi un orfano di routing.

caio

Strictly speaking, the west part looks like being used by 2 track vehicles in recent time with some gravel additive on top, making it at least highway=track, grade 2. For path I don't tag bicycle=yes as that is implicit.... all routers assume path is foot/bicycle permitted. I only tag when there's an exception else we can start mapping millions of ways with bicycle=yes. Many signs here bicycle speed 'velocità moderata' or max 10kmh... try that on a simple bike without speed display :o)))). Latter wholly ignored by 99.999% including the cops.

Valhalla is quick, OSRM is slow GraphHopper the slowest. Got a path that at least a month later is still not routed correctly by GH. One needs a machete for that path. The start is even impassable... a 2m 80 degree slope with dense scrub. Whoever put that path there must have been on a downhill. There's lots of MTB oneway tracks for downhill only. The furgone brings you to the top, trailer with 10-12 MTBs in tow.

ciao

Hi Marco

Think the whole layer/bridge tagging needs reviewing as the pier area is tagged as on layer=1, the road isn't and than the goods_coveyor (which has no tag to say what type, such as belt), on top of the pier being on layer 1... that would than be layer 2. Maybe the thinking is, if I don't the pier /coveyor disappears in the blue. I never remember.

Unfortunately the duplicate edges are "for-ever" flags by OSMI and over time build up on the daily list, so when it legally can be resolved I'd do so,.. in past I've resorted to making things MPs, the shared edge becoming a single way in 2 MP relations, not really proper. Some mappers make every single shared edge into an MP, to me a maint horror... simple polygons for areas are my thing.
Your list sorted by issue type shows a few dozen, the most poignant those that map highways along edges of pedestrian areas.... highway-highway overlap, not only flagged by OSMI.

FYI if you don't already know it: https://resultmaps.neis-one.org/hdyc-osmi-issues?uid=175882

Anyway, I 'fix' what can be legally fixed and keep the list short making it a 1 minute daily review when the mapping day takes off. Others don't, their choice.

have e nice day.
Rob

Hi, note creator here. Was there a month ago and it was still the same with the map note I made years ago and the photo added 2 years ago by Duro Jifi. Now one part is bicycle yes and the other part is bicycle dismount. That's too late. bicycle=dismount will still route cyclists here.... a walk of a mile or more on rubble. I actually switch to the SS16 and return to the track at Le Morge. Not ideal, given the 16 is a racetrack, but does save you the agony and 1 or 2 tires. Never understood why the was never converted to proper track. Maybe because of the nude beach somewhere there, oops, now I spilled the beans.

ciao.

PS Got MTB size tires, but profile for road, Kevlar arming, chambers filled with anti-puncture goo, even 2 bottles with in bag with more goo of the "fix and inflate" type (helped me once) but that wont help prevent a cut on that rail rock stuff.

Ciao,

Ho appena tolto diversi nodi di prato mentre spostavi il tuo percorso ebike.

Ho una domanda, un commento: Hai semplicemente segnato questi percorsi ebike come highway=path, senza qualificare nulla, né la superficie, né la scala del sacco, né la difficoltà, né altro. Il risultato del semplice highway=path è che qualsiasi navigatore di biciclette normali per strade asfaltate vere e proprie viene ora indirizzato anche su questi “sentieri”, quindi è necessario specificare per chi lo sono e per chi non lo sono e le valutazioni, la superficie, ecc.

Inoltre, si tratta di percorsi ufficiali, documentati, con cartelli ecc. o semplicemente “into the wild”?

Salute.

Hi,

Just curious, the monster pier area is being flagged as having duplicated edges in OSMI, see the bridges and piers are tagged with layer=1, but the road on it is not, since recently named Ponte Alti Fondali... a name of a bridge is not on layer 1 or has the bridge tag. Would it not make sense as now the road is below it.

cheers

Ciao Giovanni,

Purtroppo è la terza volta che, dopo le modifiche apportate a questo foresta, la relazione multipoligono deve essere riparata.
osm.org/relation/11526207

Gentilmente rileggere le wiki relative alle relazioni, esterne(outer) e interne(inner), una di queste piuttosto vecchia ma ancora molto applicabile:

osm.wiki/IT:Area

Salute,
SekeRob

PS Area pedonale nel foresta che può essere raggiunta solo da sentieri (no macchine)? Non sarebbe più appropriata una qualificazione di prato o prateria o un sito per picnic?

For readers: https://www.deskaeronautico.it/s04-24-lavori-per-allungamento-pista-a-pescara/

As with anything related to construction in/round Pescara involving tax money, I see it when I see it, which is, saw the typical construction orange fencing, I think.

Hi

You broke routing instead of fixing. Look at lanes forward. backward. turn lanes and destination lanes. Does no longer add up and Osmose diagnoses aame. Think you need to revert.

Happy Fixing.

Again another snowball CS, came to fix wastewater clarifiers tags, see unmapped cycle ways and the rest. This area needs work, missing ways particularly.

Looks "A Lot" better now in AA, few probs remaining to solve there.

cheers.

Yup, I realized that after sending my second message that there are area codes of 2 (Rome e.g.), 3 and 4 digits. Sorry to have caused confusion.

Have a nice "mapping" day, they predicted sunny day here, instead overcast and drizzle in PE, so I'm mapping instead. ;-/

To make it easy, this map with coloured pins has many green ones. Click on them with mouse and a balloon pops up with a description of the problem (not all green are phone related, but the bulk in G are ATM. When you see the phone prefix issue, click on one of the links for ID (I use JOSM), and the editor will open on with the problem object selected, edit, save. In JOSM it's easier as it just opens the same editor app window and do all in one, then save. The ones I corrected you can use as reference check if you're stuck with a odd number.

ciao

map link Osmose: https://osmose.openstreetmap.fr/en/map/#loc=14/42.82483/13.93171&item=1xxx%2C2xxx%2C3xxx%2C4010%2C4020%2C4030%2C4040%2C4060%2C4070%2C4080%2C4090%2C4100%2C4110%2C4130%2C5020%2C5030%2C5040%2C5050%2C5060%2C5070%2C5080%2C6xxx%2C7010%2C7011%2C7012%2C7020%2C7050%2C7051%2C7070%2C7080%2C7090%2C7100%2C7110%2C7120%2C7130%2C7160%2C7170%2C7190%2C7220%2C7240%2C8010%2C8011%2C8012%2C8020%2C8021%2C8022%2C8025%2C8026%2C8030%2C8031%2C8032%2C8040%2C8042%2C8050%2C8051%2C8060%2C8070%2C8080%2C8090%2C8091%2C8100%2C8101%2C8110%2C8120%2C8121%2C8122%2C8130%2C8131%2C8132%2C8140%2C8150%2C8151%2C8152%2C8160%2C8161%2C8162%2C8170%2C8180%2C8182%2C8190%2C8191%2C8192%2C8212%2C8221%2C8230%2C8240%2C8250%2C8260%2C8270%2C8280%2C8281%2C8282%2C8290%2C8300%2C8310%2C8320%2C8330%2C8331%2C8340%2C8341%2C8350%2C8351%2C8360%2C8370%2C8380%2C8381%2C8382%2C8390%2C8391%2C8392%2C8400%2C8401%2C8410%2C8411%2C8412%2C8420%2C8430%2C8431%2C8450%2C8460%2C8470%2C8480%2C8490%2C8500%2C8510%2C8520%2C8530%2C8540%2C9000%2C9003%2C9004%2C9005%2C9006%2C9007%2C9009%2C9010%2C9011%2C9014%2C9015%2C9016%2C9017%2C9018%2C9019%2C9020&level=1%2C2%2C3

Hi,

Could I ask you to please return to 'the scene of the mapping crime' ;o) and correct all the phone number notation

1) They all need the international prefix of +39
2) The formatting where the local number is
a) 6 digits is +39 aaa nnnnnn
b) 5 digits is +39 aaa nnnnn
c) 7 digits is +39 aaa nnn nnnn

I've already done a few dozen last month, and thanks for adding many more POI to Giulianova and happy continued
mapping.

PS, best is when
d) Fixed phone tag contact:phone=
e) cell phone tag mobile=

More details in the wiki: osm.wiki/Key:phone (no Italian translation available unfortunately)

Think that would be an idea, then add disused=yes. Possible the bells go ringing again as there's no way, but remember solving this somewhere near that large chem wastedump near Popoli. Sure looking forward to see what they're going to do with those ramp embankments and how they're going the bridge structure off crossing the road... maybe crane it while closing the road for a few days.

Anyway, my biweekly cycle tour check of vrs constructions there's now a cycleway on an embankment coming in the BI-6 or as they like to sign it in Abruzzo as Ciclovia Adriatica 6. In Marche it's simply signed as 6 with a bike symbol.

TTYL

Hi,

One more proof that ID is inadequate... alarm bells went off and when loading the area into JOSM, the connections, restrictions showed broken, nothing to control, nor is it a motorroad anymore, so I took the axe to these. The other aerts I ignored such as bridge with no way on it. Looks weird though... one cycles past and underneath but nothing on the map. We'll see if the demolition really starts in Jan. Noticeable is that the new smaller work board showed a dropped price for these works. Maybe because they subtracted the cost of the 'new' bypass.

Have a nice day..

Hi,

waiting on part 7 with baited breath. Now many of these Elba islets are highlighted as needing an inner role. Since there are two lines each, both with outer, think last time the 'outer' correction landed on the wrong outline. So my interpretation, that all in the Elba relation need to be outer and those with the Santuaire Pelagos need to be inner. Took me a long time to load all members into JOSM than dragged a islet node to kick the validator and sure the MP is not working, warning there is a style on member outlines members.
https://tools.geofabrik.de/osmi/?view=areas&lon=10.35879&lat=42.74781&zoom=19&baselayer=Geofabrik%20Standard&opacity=0.50&overlays=duplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways%2Cduplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways
Personally I'd tag this as a boundary as it is now and removing all the 'inner' as everything inside the SP sea zone is automatically part of the reserve. Maybe another reader of this has comment to this.

ciao

Comment to self: This is a rouge CS created during a crashed JOSM sessions while uploading a 1300 node CS set. Lesson to take away from: When JOSM upload/session crashes or comp has power faiil during upload and restarting JODM to recover the data not yet uploaded, check if a partial CS was entered into OSM. Two possible solutions. 1) Backout/revert the CS resulting from the crashed/partial CS upload and then retry to original upload. 2). Run a JOSM Update Data or Update Modified to fetch any node IDs that may have been created during the failed upload. If you dont you could likely end up with orphaned nodes, in this case exactly 1000. Saves lots of time the next day not having to delete these duplicate nodes from the system.

Hi,

There are bunch 'Correzione coastline' on Elba which actually have self intersections which stop them to render. Are you going to fix these? Details found on OSM Inspector, in bright, light blue and purple at :https://tools.geofabrik.de/osmi/?view=areas&lon=10.29763&lat=42.79609&zoom=12&baselayer=Geofabrik%20Standard&opacity=0.50&overlays=duplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways%2Cduplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways

Please let us know