OpenStreetMap logo OpenStreetMap

Changeset When Comment
123698208 over 3 years ago

Hi,

Per a previous discussion with a mapper, this runway is effectively in disuse but for a single annual festive event i.e. think it should be tagged as such, either additionally with disused=yes or as prefix to aeroway as disused:aeroway=runway. See changeset/118296290#map=16/50.0838/19.9952

Also per text book, runways have to be mapped as line with the length and width tags sufficing to render the area. Both tags are present. Mapped as area it gives this warning in ID Editor

"Runway 11/29 should be a line, not an area

Convert this to a line"

There's no escaping out but to hit the ignore button in ID Editor.

cheers

120099340 over 3 years ago

Hi

As a reminder, do yuo have an answer for me so the issues can be fixed?

MTIA

Come promemoria, hai una risposta per me in modo che i problemi possano essere risolti?

MGIA

125663489 over 3 years ago

It is suspected the previous mapper considered some area for the new rail corridor but much wider than the 1 track line thart already exists here. The vineyard next to the repaird farmland still looks to have a wrong shape, rail or no rail.

125516431 over 3 years ago

You've got mail. Please read and respond to these other mappers.

Hai ricevuto una email. Si prega di leggere e rispondere a questi altri mappatori.

125572308 over 3 years ago

Should be repaired now, you essentially made the 2 forests linked to each other rather then merging. See changeset/125646314 which in the CS summary confirms the issue was resolved, the forest shows again.

125572308 over 3 years ago

The convention of doing, no matter what, is that an area ALWAYS consists of a closed outline or ring as it's referred to. Here there's a big gap as the "warnings:mismatched_geometry:unclosed_multipolygon_part" in the change set summary tells. Now being flagged in various QA analysers. In 2km and lesser zoom it shows there was mostly wood (gets less frequent updated), in 1km and greater it's gone because of the broken ring. This zoom of 1km and greater is updated within minutes in standard Carto view.

Anyway, 2 adjacent areas merged is easy, select both, right click and hit + sign. Then you must remove the section of outline that are now duplicate. Easy too, cut, cut, delete relation on those sections and delete the remaining white lines. Make sure the ring is closed still, no loose extension, self intersections, or overlaps.

79669181 over 3 years ago

Hi,

2 years on, the mess created is still a mess with the result that left half of the overlapping farmland MP relation is NOT RENDERING, no useful note why this work was unfinished as the QA reports the farmland has an unclosed ring. It starts with this long straight vertical line used twice for the same farmland. Can you clarify?

thanks

125578473 over 3 years ago

OK, thumbs up from the render kings.

125565581 over 3 years ago

Hi,

What's your source of naming 3 street parts Via Monte sirente and Via monte velino ?

First, properly, street names are written as Via Monte Sirente and Via Monte Velino. Since I surveyed those streets in the past I could not find signs and certainly did not believe Via Monte Sirente as it's not connected to the long Monte Sirente 1 block southwest. More importantly, the house numbers on the Monte Sirente part fit in the series of Via Alcione.

Please recheck and let me know

Qual è la tua fonte di denominazione di 3 parti di strada Via Monte Sirente e Via monte velino?

Innanzitutto, propriamente, i nomi si scrivono come Monte Sirente e Monte Velino. Dato che ho perlustrato quelle strade in passato non sono riuscito a trovare indicazioni e di certo non credevo a Via Monte Sirente in quanto non è collegata al lungo Monte Sirente 1 isolato a sud-ovest. Ancora più importante, i numeri civici sulla parte del Monte Sirente rientrano nella serie di Via Alcione.

Per favore ricontrolla e fammi sapere

125494557 over 3 years ago

2 node edit, 1 in Moskwa and one near Canosa, España.

Please, next time, save such edits separately. All other compradres di mappatura will thank you as then it wont cause history view glut anywhere else in between.

For your reading pleasure: osm.wiki/Changeset

ciao from Italy.

125517984 over 3 years ago

Hi,

what I meant to say was that I often see and tag pitches as sports=soccer;futsal, 2 sports :O)

lHola,

lo que me faltó decir es que a menudo veo y etiqueto lanzamientos como sport=soccer; futsal, 2 deportes :O)

hasta la vista

125517984 over 3 years ago

Hi

futbal could also be futsal, the size of the field and goal sizes will tell. Many soccer fields here double as futsal fields, e.g. over the length soccer, over the width 2 futsal fields.

trad:

Hola

futbal también podría ser futsal, el tamaño del campo y el tamaño de las porterías lo dirán. Muchos campos de fútbol aquí, Italia, funcionan como campos de fútbol sala, p. sobre el largo fútbol, ​​sobre el ancho 2 canchas de futsal.

ciao

125524899 over 3 years ago

Hi, seeing what you did on half a dozen or more provincial routes of Chieti, could I entice you to do the same on the SP roads of the Province of Pescara which I suspect then would get the network ref of IT:PE , suspecting some gunk build over the years. 'length' then becoming 'distance' as you amended.

MTIA

Rob

124628034 over 3 years ago

OK, the mud areas do show in Carto.fr render version of Osmose, so that's good.

ciao

124628034 over 3 years ago

Hi,

I've corrected your La Falerina, mostly, members cant be inner to multiple areas, just one plus there was on 'inner' mapped of La Falerina that shared border with the outline.

Strangely, the mud areas don't render though properly made inner but that could be because lots of things don't render in Carto.

cheers.

PS Good to see you mapping again ;o)

125451763 over 3 years ago

Hi,

When correcting the geometry of trails, please make sure to disconnect the trail first from any points where it shows a grey node shared with an area. If you don't and drag the trail node, you also cause the geometry of the area to change and may risk self intersections while doing so like here. Area corrected.

cheers

125468179 over 3 years ago

Hi,

If you did so, you may have dragged path nodes causing a self intersection on the bare rock. This caused it to disappear from rendering. Duly corrected.

cheers

125290993 over 3 years ago

Finally someone did the deed. looks a lot cleaner now in QA.

125465088 over 3 years ago

Hi,

You should NOT add arbitrary names to general public roads and tracks, use the official.

I see you already created a Lungofiume Foro route relation, where each section needs to get the proper track rating (grades 1-5) and mtb scales etc.

You can create as many route relations as you like on the same ways, tag them as local or per the official national/regional network coding. If Percorso Lungofiume Foro is different to this relation you made/edited.

At any rate, the asphalt road you marked with name "Percorso..." is Contrada San Vincence and has the road ref of ex SS263.

cheers

PS Respect ways that are signed with 'strada/proprieta privata. Don't include them in any routing and if you see the access=private tag missing on a way where signed, please add them.

traduzione:

NON dovresti aggiungere nomi arbitrari a strade e piste pubbliche in generale, usa l'ufficiale.

Vedo che hai già creato una relazione di percorso Lungofiume Foro, dove ogni sezione deve ottenere la corretta valutazione del tracciato (gradi 1-5) e scale mtb ecc.

Puoi creare tutte le relazioni di percorso che desideri negli stessi modi, contrassegnarle come locali o secondo la codifica della rete nazionale/regionale ufficiale. Se Percorso Lungofiume Foro è diverso da questa relazione che hai realizzato/modificato.

Ad ogni modo, la strada asfaltata che hai segnato con il nome "Percorso..." è Contrada San Vincence e ha il rif. ex SS263.

Saluti

PS Rispettare le vie che si firmano con 'strada/proprieta privata. Non includerli in nessun percorso e se vedi il tag access=private mancante in un percorso, aggiungili.

124393930 over 3 years ago

Hi,

The min height are correct, the 'height' is not. It should be the total height i.e. 54 (of the base)+6(the section)=60 (top above ground). You can check in StreetComplete 3D view how St Peter renders. The big cupola shows correct above the main outline, the octagonal parts don't.

Check now and check back in a week to see the difference.

Also, building parts are not made part of a multipolygon. The whole cathedral should be all parts made member of a type=building relation with the circumference drawn a second time to serve as outline base. That hot potato in global viewership I wont do with all these correction racers sure to jump in if a comma is wrong. This one was flagged by OSM Inspector BTW.

Anyway MP's for buildings are not a good idea as then all parts will assume the same maximum height, and I speak of experience.

cheers