piebro/osm-data huggingface dataset:
mapman44 (2020-01-12 02:22:22+00:00): This changeset is very complex with many different types of edits and very difficult to verify. Some have changed tags that were correct back to deprecated tags. Some areas are left with no tags at all. I believe it should be reverted and re-done.
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/79464905
Joseph E (2020-01-12 03:03:28+00:00): I used JOSM to validate all the data in this county and corrected many errors with bad multipolygon relations and boundary relations and unconnected waterways, so yes, it was a complex changeset. I suppose I could have broken it up into smaller parts, but since many of the errors were single duplicate nodes that connected 2 ways, I had to edit a large number of ways to fix a few hundred duplicated waterway nodes. This is a common problem in data that was imported from the NHD (national hydrological database) unfortunately. If there are any feature left without tags please let me know; I will go and check the validator again now, but I thought I already fixed these (I had some internet connection problems last night while uploading this which might have lead to temporary problems).
Re: deprecated tags, are you talking about waterway=riverbank? That tag isn't deprecated and I like it better than natural=water + water=river since it is just one tag instead of 2.
mapman44 (2020-01-12 03:37:41+00:00): I really don't have time to check all of it for you but for one thing there's an area that was formerly "Rocks and Islands Wilderness Area" that is now just an unnamed, untagged area off the coast.
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/79464905
Joseph E (2020-01-12 07:23:43+00:00): I checked Rocks and Islands Wilderness Area - It's actually duplicated in 2 different relations, both https://www.openstreetmap.org/relation/6190582 (last edited 5 months ago) and https://www.openstreetmap.org/relation/10572994 (from my changeset - previously it was a closed way that also duplicated the same  relation), so I will delete my duplicate. 

I'll check through the rest of it, but so far JOSM isn't finding any new errors. (Too late to revert, there have been other changes in the meantime).
Abruzzzo (2020-02-07 23:41:56+00:00): Please map land uses (verifiable in reality) and don't import parcels: https://wiki.openstreetmap.org/wiki/Parcel
revent (2020-02-08 00:20:24+00:00): I'm not importing parcels, and if I was simply importing parcels (or even just drawing lines around them) then what I mapped would be look distinctly different.... it would, in fact, look like the parcels shown on Google Maps.

If you want to discuss what the verifiable 'edge' of a landuse is, thats a different issue, but I'd argue its not 'wherever someone guessed while looking at Bing'.
revent (2020-02-09 02:34:26+00:00): Just to be clear, I'm generally looking at the actual right of way dedications, and putting the edge of the neighboring landuse where the actual edge is.... which is physically verifiable, if you cared to do so, by going out and hunting down the surveyor's nails that should be within a foot or two of where I put nodes.
user_5359 (2020-01-12 06:56:26+00:00): Welcome to OSM! Short inquiry to the key service_times: the services are held every day or only on Sundays? In the latter case add a Su (followed by space character) at the beginning of the value. Please notice also: We use the 24h notation for time informations.
Romell Parks-Weekly (2020-01-12 14:27:08+00:00): I have updated the field accordingly. Thank you.
Warin61 (2024-05-08 07:34:26+00:00): Hi,

Node 5190607820, public_transport=stop_position should be on a way - where the bus stops. See https://wiki.openstreetmap.org/wiki/Tag:public_transport%3Dstop_position 
Note that if there is a 'bus stop' then stop position is redundant and can be deleted. 

The road that leads to this stop is tagged as 'construction' .. so would not be useable anyhow???
Arthtoach_Import (2020-01-12 07:56:51+00:00): Hi, you keep re-adding landuse=industrial to the following building: https://www.openstreetmap.org/way/561382719

I've previously tried to engage with you about this in this changeset: https://www.openstreetmap.org/changeset/79119651

Adding landuse=industrial to this building is unnecessary and incorrect as it is already contained within a larger landuse of industrial. The building itself is also building=industrial so you are adding no additional information to the map.

Can you please explain your reason for repeatedly readding this unnecessary tag. I would argue that the building itself should not be tagged with the landuse as it is a slightly larger area that is used industrially, including the loading bay for example. Mapping like this produces warnings in JOSM as it is not typical to tag buildings with a landuse, and also, the landuse is contained within a larger landuse.
Arthtoach (2020-01-12 07:57:41+00:00): Accidentally recorded the above comment with the wrong account. This is my normal account.
user_5359 (2020-01-12 06:26:39+00:00): Willkommen bei OSM!

Bei der Menge von Knoten muss ich von einem Import ausgehen und deshalb muss ich die Frage nach Quelle und Lizenz des Importes stellen. Sicherlich hast Du auch die vorgeschriebenen Diskussionen mit der Community geführt und die Kennzeichnungen beachtet, nicht wahr?

Ich greife mal wahllos den Knoten https://www.openstreetmap.org/node/7125240550 an der Ecke Bergstraße und Hochschulring raus. Der Hochschulring führt (laut Richtung OSM Weg) auf die Bergstraße zu. Das Schild steht angeblich auf der linken Seite (*) und ist rückwärts gerichtet (traffic_sign:backward). Ich hätte da Klärungsbedarf!

Im Einmündungsbereich stehen zwei blaue Pfeile auf der (in OSM nicht eingezeichneten) Verkehrsinsel. Beide Verkehrszeichen stehen rechts. Laut Logik müsste aus Sicht der OSM-Richtung einer links und der andere rechts stehen. Andere lösen dies auch mit dem Standort middle (siehe taginfo). Ich hätte da weiteren Klärungsbedarf. 
Übrigens wurde laut Wikipedia die Kennzeichnung des Verkehrszeichen DE:220-20 auf DE:220 geändert.

Wenden wir uns den den beiden Verkehrsschildern in der Nähe der Bushaltestelle „Wildau, Eichstraße“ zu. Beide besitzen die Schlüssel traffic_sign und traffic_sign:backward. Der Schlüssel in traffic_sign besitzt kein Prefix DE: und hat eine Nachkommastelle. Das richt mir sehr nach fehlerhaften Datenmanagement und müsste nach meiner Meinung dringend bereinigt werden. Hier sehe weiteren Klärungsbedarf.

Der zweite Knoten ist laut JOSM 1,94m vom ersten Knoten entfernt und ist laut Kennzeichnung ein Zusatzschild mit der Bedeutung „Radfahrer frei“. In Natura dürfte dieses Schild direkt unterhalb dem ersten Knoten hängen und bedarf keines zweiten Knoten. Auch hier sehe ich Klärungsbedarf.

Fußnote (*): Die Aussage "angeblich auf der linken Seite“ habe ich aus dem umdokumentierten Tag side=left entnommen. Das existiert wohl weltweit 37.894 mal, aber im Wiki steht "Mit Hilfe des Schlüssels direction=* soll die Richtung des Gesichts des Verkehrszeichens beschrieben werden. …“
user_5359 (2020-01-17 11:53:40+00:00): Der nicht abgesprochener Datenimport mit wahrscheinlich mangelhafter Qualität wurde gelöscht (auch wegen fehlender Rückmeldung).
pangoSE (2020-01-14 19:13:35+00:00): Hej. Beskrivningen här verkar ha kapats: https://www.openstreetmap.org/node/7125241132
Kan du lägga till resten i description2= ?
Tack!
pangoSE (2020-01-14 19:19:59+00:00): samma här 7125241107
pangoSE (2020-01-14 19:30:23+00:00): och här https://www.openstreetmap.org/node/7125248172
pangoSE (2020-01-14 19:50:13+00:00): och https://www.openstreetmap.org/node/7125241098
operaman (2020-01-15 20:41:17+00:00): Att deskriptionerna blir kapade är förväntat. Mina skript var inte särskilt smarta för att spara hela beskrivningar om de var längre än 255 tecken. Och jag tror inte att OSM:s taggar var tänkta som  förvaringsplats för överdrivet långa texter. Jag förväntar mig inte att någon skulle leta efter till exempel fullständiga vägbeskrivningar till en stuga i dess OSM-beskriviningsetikett.

Jo, ja kunde ha gjort det bättre och ha ett skript som avslutar textrader vid punkttecken, så att de inte ser så fullt ut, men skillnaden vore riktigt liten.
pangoSE (2020-01-16 11:28:28+00:00): Ok, då vet jag. Jag är enig i att beskrivningarna med koordinater och närmaste ort, etc. inte är enbart relevanta, men det fanns ändå bra ledtråder för etiketter i dem :)
Jag får kolla upp manuellt om jag orkar.
mapman44 (2020-01-12 03:42:53+00:00): Why would you change the tags to "ditch" when they are named "canal?" Please review the Wiki info for ditch. I believe these are irrigation canals that carry useful water to crop lands.
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/79465701
mapman44 (2020-01-12 03:45:08+00:00): Why change the tag to "ditch" when "canal" is part of the name? Please review ditch in Wiki. I believe these are irrigation canals.
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/79465701
Adam Schneider (2020-01-12 03:52:56+00:00): Because most of the other irrigation "canals" in Central Oregon were already waterway=ditch, and this makes them consistent with their neighbors.  (I know you shouldn't tag for the renderer, but this also makes them look FAR better on the map!  OSM's rendering of canals is more appropriate for Panama and Suez than arid farmland.)

A few of the irrigation channels in this area (like the South Unit Canal that runs through Bend) are probably big enough to warrant "canal" status, but lots of them are tiny, making "ditch" is really more appropriate, regardless of the name — the names are really pretty arbitrary.
pangoSE (2020-01-12 13:07:00+00:00): Hej! 
Tusen tack för bidraget av vindskydd som saknades. :)
Jag tittade lite närmare och hittade följande saker som behöver åtgärdas:
1) vissa av dem ligger i vatten
2) comment ska vara description tycker jag
3) om det finns mera data kan den anges med några av taggarna här: https://wiki.openstreetmap.org/wiki/Tag:amenity%3Dshelter
4) kolla så att det inte finns några dupletter, tex https://www.openstreetmap.org/node/7125248168/history#map=17/62.78673/18.13658

Vill du ha hjälp med detta? Tips: i JOSM klicka i expert options och ladda ner via overpass sökning, se https://josm.openstreetmap.de/wiki/Help/Action/Download#DownloadfromOverpassAPI
exempelsökning: source="Facebook group Vindskydd i Norden" in sweden

då får du upp bara dem noder du lagt in
operaman (2020-01-13 23:50:03+00:00): Hej! Tack för meddelandet. Angående dina anmärkningar:
1) Tråkigt att positionsfel var såpass dåligt för dem som hamnade i vattnet. Jag kan kolla genom dem en gång till och redigera bort de drunknade.
2) Håller med, kan redigera "comment" till "description".
3) Jag försökte överföra så mycket data (dvs enstaka vindskydds särdrag) som möjligt, tror inte att jag kan lägga något mer. T ex URL till bilder kunde jag inte lägga till, för de alltid var längre än 255 tecken och inte kunde rymmas i OSM-etiketter.
4) Jag redigerade de flesta dubbletter bort innan uppladdningen (nya noder som var närmare till ett befintligt vindskydd än tröskelvärdet ansågs som dubbletter). Men några få punkter kunde ändå ha tränga sig in (som det alltid händer). Visst kommer jag radera de uppenbara dubbletter, men du och andra är visst välkomna att göra det också.
pangoSE (2020-01-14 00:09:25+00:00): Nu har jag gått igenom ca 10%. Det ser överlag bra ut tycker jag 😃
80% av de jag kollat har funnits i LM topo också och det betyder at dem är verifierade!  
Många av dem som var i vatten var det vattnet som inte låg riktigt rätt.
Bilder läggs bäst upp på commons.wikimedia.org med lämplig licens. därefter kan man tagga med wikimedia_commons=
operaman (2020-01-14 00:42:23+00:00): > Många av dem som var i vatten var det vattnet som inte låg riktigt rätt. 
Sant. Jag har nyss fixat ett par sjöar med dåliga konturnlinjer.

> Bilder läggs bäst upp på commons.wikimedia.org med lämplig licens. 

Nä, det var redan ganska jobbigt att rensa nodbeskrivningarna från bild-URL:er som var lös- eller friformaterade. Jag gjorde mitt bästa för att extrahera åtminstone en smula nyttig textinformation av de ursprungliga beskrivningarna. Det vore för mycket att fråga från mig att flytta samtliga bilder till en annan hosting.
pangoSE (2020-01-14 17:18:49+00:00): Hej igen, jag förstår att det är jobbigt att flytta bilderna. Jag har börjat fota vindskydden där jag bor själv med Commons Appen och det är väldigt smidigt tycker jag. Nu är utmaningen att få flera att göra likadant. https://f-droid.org/en/packages/fr.free.nrw.commons/
pangoSE (2020-01-14 17:20:21+00:00): Stort tack för att du rensade alla beskrivningarne, det måste ha tagit en stund om du gjode det manuellt.
operaman (2020-01-15 20:26:00+00:00): >det måste ha tagit en stund om du gjode det manuellt.
Oj nej, då använde jag reguljära uttrycks kraft. Kodavsnittet nedan gör jobbet:

def sanitize_nodes(new_list):
    # The tag "note=*" in import data is often bad, attempt to clean it up
    for nd in new_list:
        tag = get_item_with_k(nd.xmlitem, "note")
        if tag is None:
            return
        note = tag.attrib['v']
        # remove img tags as extremely long and impossible to keep
        while True:
            m = re.search(r"(.*)<img[^>]+>(.*)", note)
            if m:
                note = m.group(1) + m.group(2)
            else:
                break
        note = note.replace("<br>", " ")
        note = note.replace("  ", " ")
        note = note[:255].strip()
        # Mangle the existing tag
        tag.attrib['k'] = "comment"
        tag.attrib['v'] = note
operaman (2020-01-15 20:57:26+00:00): Angående vindskyddens bilder i beskrivningar. Jag har nyligen försökt extrahera dem av de jättelånga länkarna som jag fått av Google-tjänster. Sedan ville jag ladda bilderna upp till Commons-tjänsten du tidigare länkat.
Men det visade sig att kräva Google-kontos auktorisation, annars ger det 403 Forbidden som svaret. Detta försvårar automatisk extrahering. Jag är säkert att det  fortfarande är möjligt att genomföra efter lite sysslor med kakor osv. Men för tillfället har jag andra spännande kartrelaterade saker att göra.
pangoSE (2020-01-16 08:25:37+00:00): Okej, det går att spara dem enkeltvis från FB gruppen också.
Tycker vi skal tipsa om Commons appen mera i vandringsgrupper, för den är väldigt enkel och om dem bara anger ett vettigt namn också då bliver det lätt att hitta dem. Jag skal fixa kategorier åt dem, tex Vindskydd i Sverige, Raststugor i Sverige
pangoSE (2020-01-16 08:50:04+00:00): Det fanns redan kategorier, se https://commons.wikimedia.org/wiki/Category:Lean-tos_in_Sweden, https://commons.wikimedia.org/wiki/Category:Hiking_shelters_in_Sweden
Eddie845 (2020-01-13 20:51:19+00:00): Fe de erratas: La fuente erróneamente ha sido marcada como Maxar Street Level Imagery cuando en realidad corresponde a Mapillary Street Level Imagery
Eddie845 (2020-01-13 20:50:06+00:00): Fe de erratas: La fuente erróneamente ha sido marcada como Maxar Street Level Imagery cuando en realidad corresponde a Mapillary Street Level Imagery
geoaria (2020-04-03 10:22:29+00:00): سلام
خواهشمند است در ویرایش ها دقت کنید و از جداسازی و ایجاد حالت جزیره در مسیر های خودداری نمایید. ورودی یک مسیر residential از لحاظ ورود خودرو ممنوع کرده اید . مسیر residential  به صورت جزیره در می آید در این صورت یا تمام مسیر و مسیر های متصل را غیر ماشین رو کنید یا مسیر ورود خودرو را به آن مشخص کنید. 

32.66386/51.65229
مسیر حشمت و معابر متصل به آن جزیره شده است . دلیل شما برای ممنوعیت ورود خودرو چیست آیا وجود یک نگهبانی است . اگر هست که ورودی را خصوصی نمایید نه اینکه ورود خدرو را مموع کنید.
MikeN (2020-01-12 15:50:57+00:00): Welcome to OSM!  Something to be aware of when aligning roads - the default image Bing usually has a significant alignment error.  When aligning roads, select the "Background Layers", then use the older but better aligned "ESRI World Imagery (Clarity) Beta) layer
Adamant1 (2020-01-13 07:18:40+00:00): Hi there. If the Bing images are accurate and this isn't a parking lot anymore it might be worth deleting it altogether and mapping the building that's there now. Otherwise, someone will probably just come along and re-map the parking aisles. Plus, its more accurate that way.

Thanks
payelgh (2020-02-11 12:18:49+00:00): Hi Adamant1,

Thanks for your comment. Apologies for the delay in response. As per your suggestion, I've deleted the entire data in the area and mapped it to the current building under changeset#80849482

Looking forward to learning from you.

Thanks,
Payelgh
angys (2020-01-12 07:17:17+00:00): I suggest that your company editors use OpenStreetCam to record the roads.

and then, Please make a update log on roadname so that our local mapper can trace whatever your team had made changes, and prevent any inaccurancy. For the other info like road surface and classification is unnecessary to list out.

e.g.
Member A-12 Jan-Add new street names at District 51
*Jalan 51
*Jalan 52

If your team provide street level imagery to Openstreetcam, then these will ensure and become the evidence of your team are edit locally, not armchair mapping like GrabOSM team, and prevent somebody thought (or claim) that your team are copying data, I am a little bit fear of this.

For Penang area, please do note that mostly newer development area like in Bandar Cassia, Penang North Science Park, south Nibong Tebal, Bertam dont have a name in OSM database, and some village will have street name but still need to take as alley as only 1 car can in/out at the same time.
Velocimaptor (2020-01-12 13:09:13+00:00): Thank you angys for your excellent feedback! My team and I are currently physically here in Penang making these changes while driving the city each day. We are only editing what we see on the ground and adding names as we see them on road signs. All reclassifications of small roads have also been based on what we are seeing during our current ground survey. 

All of the imagery that we collect while here will be available on Mapillary within the next few weeks for the public to have available for further editing and verification once we are able to get it uploaded.

Please reach out and send me a message if you have any questions or would be interested in getting together while we are here!
angys (2020-01-12 13:35:35+00:00): Let me see your team till when (in Penang)? Maybe we can do a meetup at Bukit Mertajam next week (if I have time). I suggest that your team use Openstreetcam because it is under CC BY SA license, so maybe some of your streetview imagery that contain buildings and POI can be transferred into Wikipedia. (Mapillary will leave a watermark and I had asked osm community in Telegram and they prefer us to use Openstreetcam) 
and then,  i think your team should add source=Kaart Groubd Survey 2020 while adding new roadname into OSM database, so that your team's effort can be seen  And again while recording the streetside please use a higher quality camera so that can capture more POI around Malaysian cities and can contribute back to our local community,  some current imagery are blurry and unable to see. You may do your update log at our OSM Malaysia forum,  thank you very much.
angys (2020-01-12 07:12:05+00:00): I suggest that your company editors use OpenStreetCam to record the roads.

and then, Please make a update log on roadname so that our local mapper can trace whatever your team had made changes, and prevent any inaccurancy. For the other info like road surface and classification is unnecessary to list out.

e.g.
Member A-12 Jan-Add new street names at District 51
*Jalan 51
*Jalan 52

If your team provide street level imagery to Openstreetcam, then these will ensure and become the evidence of your team are edit locally, not armchair mapping like GrabOSM team, and prevent somebody thought (or claim) that your team are copying data, I am a little bit fear of this.

For Johor Bahru area, please do note that newer development area in northern Tebrau almost no street name and also for some new region around Iskandar Puteri, Pasir Gudang, Kulai and Penggerang, part of JB metropolitian.
canfe (2025-07-26 17:40:00+00:00): Non mettere i cicivic"sui" buildings.
Son da mettere come nodo dove c'è la "buca delle lettere"
canfe (2025-07-26 17:43:26+00:00): Nucleo Bertin, pur essendo sul cartello non indica che quella strada sia chiamata così e tantomeno che nel name abbia anche i civici.
EppesuigOSM (2025-07-26 20:23:07+00:00): Ciao Canfe, scusa ma è una modifica di 5 anni fa, della quale adesso non ricordo granché. Potresti spiegarmi meglio cosa dovrei correggere? Grazie.
canfe (2025-07-27 05:30:54+00:00): Bertin l'ho già sistemato.
E' più un pro memoria per invitarti a non mescolare civico, esercizio e building tutto assieme, bensì di staccarli.
Inoltre in zona mi apre che tu abbia dato come name alla strada, quello riportato sul cartello ma che in realtà indica che ci si trova nella (frazione) tal dei tali. Le frazioni si mappano come nodo.
Magari dai una ripassata per quel che ti ricordi.
A67-A67 (2020-02-12 12:40:41+00:00): Bedankt voor de verbetering.
Het is echter niet de bedoeling dat er wegen uit de busroute worden gehaald die daarna niet vervangen worden. Zo ontstaan er onderbrekingen in busroute. Om de route te verbeteren hoort dus de route verlegd te worden naar de correcte route, in plaats van slechts het verwijderen van verkeerde delen.
Diógenes de Sinope (2020-01-14 02:59:07+00:00): Hi MEDITALENTO, while I was reviewing edits made in Luanda, I could not help but notice this one in particular, does the node that you placed at this location correspond to the residence of someone name Tony? If that is the case, OpenStreetMap dissuades users from adding personally identifiable information about private individuals to the map [ https://wiki.openstreetmap.org/wiki/Limitations_on_mapping_private_information ] | Olá MEDITALENTO, enquanto eu estava revendo as alterações feitas em Luanda, não pude deixar de notar esta em particular, será que o nó que você colocou neste local corresponde à residência de alguém chamado Tony? Se for esse o caso, o OpenStreetMap dissuade colaboradores de adicionar informações pessoalmente identificáveis sobre indivíduos particulares ao mapa [ https://translate.google.com/translate?sl=en&tl=pt&u=https%3A%2F%2Fwiki.openstreetmap.org%2Fwiki%2FLimitations_on_mapping_private_information ]
opendcc (2020-01-12 08:09:29+00:00): Hallo,

Du hast hier relativ viel Adressen eingetragen. Darf ich bitte nach der Datenquelle fragen - woher hast Du die Adressinformationen?
user_5359 (2020-01-12 09:10:43+00:00): Weiterhin besteht eine Adresse mindetens aus Straße und Hausnummer, dass ist nicht in allen Fällen der Fall. Außerdem ist die Qualität nicht immer sauber: Beim Gebäude https://www.osm.org/way/410622469 kann ich die Hengersberger Straße nicht in der Nähe finden.
opendcc (2020-01-14 21:40:05+00:00): Hallo, ist keine Quellenangabe möglich?
user_5359 (2020-01-16 05:08:59+00:00): Hallo Kolsa, bitte lege Deine Quellen bis Freitag morgen offen, da wir sonst von nicht erlaubten Quelle ausgehen müssten und Deinen Beitrag aus Lizenzgründen revoltieren müssten.
user_5359 (2020-01-17 12:05:52+00:00): Dieser Änderungssatz wurde wegen Verdacht auf Import aus nicht qualifizierten Quellen (und fehlender Rückmeldung) gelöscht.
Vinber (2020-01-20 10:45:22+00:00): Bonjour et bienvenue dans OpenStreetMap,

nouvelle-nouveau, un petit mot ici pour faciliter votre arrivée : https://wiki.openstreetmap.org/wiki/FR:WikiProject_France/bienvenue

Cas particulier / Vous êtes en seconde, en cours de SNT, alors s'il vous plait, veuillez faire suivre à votre enseignant-e le lien suivant https://dane.ac-lyon.fr/spip/spip.php?article628

Et n'hésitez pas à répondre, poser des questions, ...