piebro/osm-data huggingface dataset:
eggie (2026-03-28 06:31:35+00:00): De gebouwen die je hebt getekend en geen gebouwen zijn heb ik verwijderd of omgetagd naar mooring=private

Kijk nog eens goed naar al die dubbele vermeldingen. Maak een keuze.
MVG
eggie
Aäron van Dijk (2026-03-28 08:13:06+00:00): Dank Eggie, 

Zag ook je DM zojuist incl de links. Was even benieuwd wat gebruikelijk is binnen de community. Pas je inderdaad het gebouw/aanleg plaats aan met de gegevens van een club/winkel of plaats of zit je een pin  met deze info erin?
eggie (2026-03-28 08:18:24+00:00): Hoi Aäron..
Voor een club of winkel gebruiken we de al bestaande adresnode... uitzonderingen daargelaten.
Kerken worden vaak op het gebouw getagd omdat de rendering dan wordt aangepast. Campings vaak ook zo...maar in principe gebruik de adresnode .. dus niet de gebouwomtrek.
Groet,
eggie
eggie (2026-03-28 06:38:59+00:00): Dag Maproll,

Alle gebouwen zijn import vanuit het Kadaster. Beter geen gebouwen op gebouwen tekenen. Ik heb nu de nodes verbonden en building:part gebruikt voor het BAG gedeelte.

MVG
eggie
Maproll (2026-03-28 12:31:13+00:00): Thanks eggie for your changes, I had been following the example by the "Blauwe Mosque" but now I know what to do, cheers.
iandees (2026-03-28 00:57:15+00:00): Hello! I noticed that node https://www.openstreetmap.org/node/7672056549 was moved a long distance in this changeset. This is a common mistake that happens when you click on a point and drag to move the map. The point moves with your mouse instead of the map.

I moved things back to where they were before in https://www.openstreetmap.org/changeset/180526495, so no harm done!

To avoid this in the future:
- Try to click on an empty part of the map when you want to move around
- If you see a point move by mistake, press Ctrl+Z (or Cmd+Z on Mac) to undo it

Happy mapping!
eerib (2026-03-28 00:03:06+00:00): Hello boncnaa,

Thank you for your edit. Unfortunately it does not meet OpenStreetMap standards and therefore has been reverted. This is an unsanctioned mountain bike trail located on unsurveyed crown land and is correctly marked as such. Please refer to the following wiki page.

https://wiki.openstreetmap.org/wiki/Why_can%27t_I_delete_this_trail%3F

If you have further questions regarding the policies or trail mapping in general then I recommend starting a discussion thread on the OpenStreetMap Community Forum.

https://community.openstreetmap.org

If you would like to dispute this revert of your edit then you can reach out to the Data Working Group, the moderation group of OpenStreetMap, by sending an email to the following email address.

data@openstreetmap.org

Thank you, eerib
eggie (2026-03-28 06:40:14+00:00): Dag Maproll,

De info heb ik samengevoegd met de bestaande adresnode
eggie (2026-03-28 06:42:12+00:00): Wat is de lauwe Transport?
Info ook verplaatst naar adresnode.
Maproll (2026-03-28 12:33:45+00:00): Hi eggie,

Unfortunately I'm not sure what type of business "DeBlauwe Transport" is, which is why I had made it a generic "building" type before. I saw them loading many suitcases into a van but I'm not sure if that makes them a shipping company, a travel company or something else entirely.
eggie (2026-03-28 13:02:50+00:00): Hi Maproll, I added office=logistics and the website at the adddressnode.
Removed the building. 
https://deblauwetransport.nl/

Greetz,
eggie
Maproll (2026-03-28 13:06:25+00:00): Hi eggie, thanks for your help :)
felipeeugenio (2026-03-28 12:10:56+00:00): Hola. No se entiende mucho la edición. Trasladó un edificio varias cuadras, pero no hay señales de un supermercado en el mapa. Dónde está realmente? el edificio sigue donde mismo?

saludos
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/180526077
felipeeugenio (2026-03-28 12:13:57+00:00): Ahí lo corregí. Era un poco más al norte, y el edificio sigue igual. Saludos
pwbriggs (2026-04-01 06:24:02+00:00): Thanks for the contributions. Please note that the name=* tag is almost exclusively for names that are written on a sign—they are not just a "label" for a map feature, because OpenStreetMap data is used for purposes beyond simply displaying general-purpose basemaps. Perhaps you meant to map the "yurt" building as building=ger instead? I've updated that, but let me know if it's not the case. Thanks, and happy mapping!
greatnameguys2472 (2026-03-29 02:30:07+00:00): Hi there, welcome to OSM. Please do be more careful in the future as it seems like you have changed an interchange back to it's previous configuration after it has been upgraded recently
Sammyhawkrad (2026-03-29 13:58:40+00:00): Hello Abdul Rahman78, welcome to OSM. 

You need to understand the changes you're making before saving them.

Do not delete mapped buildings with all attributes, replacing them with low-quality ones. 
Tracing over existing buildings is also unacceptable. 

Understand the highway=* tags before using them: the roads within KNUST are not highway=primary. 

Try to fix the warnings that are highlighted when saving your changes.

There are many issues with your changeset, so I have to revert it. As a beginner, focus on adding data at places where there is none. Modifying existing data that you may not fully understand may cause more harm than good.
Sammyhawkrad (2026-03-29 14:08:38+00:00): Changeset reverted via https://www.openstreetmap.org/changeset/180585442
MassCartog (2026-03-28 01:58:15+00:00): Hi welcome to OSM. Can you discribe what you are doing in this changeset and why you removed these roads?

Please leave good changeset comment "e" tell other users nothing about why you are doing things. https://wiki.openstreetmap.org/wiki/Good_changeset_comments
NeisBot (2026-03-28 01:54:43+00:00): Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description, note or slogan contain detailed text that may be interpreted as promotional or SEO-related. To ensure OSM remains neutral and focused on map data, I recommend keeping descriptions concise, factual, and free from marketing or promotional language.

⚠️️ Problematic element (limit 1):
https://osm.org/node/13685756508 v1

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Learning center"

#MapWithoutSpam
NeisAgent (2026-03-28 05:33:14+00:00): 🕵 The changeset tags appear to reference Google as a data source.

Please note that using Google Maps, Google Street View, or similar Google services as a mapping source is not allowed in OpenStreetMap due to license restrictions.

More information: https://wiki.openstreetmap.org/wiki/Google

If the data in this changeset was derived from Google or another incompatible source, the edits may need to be reverted.

If this is a misunderstanding and the data was collected from permitted sources (e.g. local survey, Bing imagery, local knowledge, etc.), please clarify in a reply.
CAM-Gerlach_Repair (2026-06-17 01:44:41+00:00): I WOULD LIKE YOU TO STOP SPAMMING.

Reverted adding SEO spam POI with advertising/malformed tags and explicit source=* of Google Maps, which is not allowed by both OSM and Google policies (see https://osm.wiki/Google ), in changeset 184205154

https://osm.org/changeset/184205154
John Kastner (2026-03-28 14:57:14+00:00): These changes look good
John Kastner (2026-03-28 14:52:21+00:00): This change is vandalism; reverted. Please do not make similar changes in the future.
John Kastner (2026-03-28 14:54:44+00:00): Reverted. This change set is also vandalism.
pitscheplatsch (2026-03-28 08:59:39+00:00): Hi,

thanks for your contribution and for working to improve name coverage.

I just wanted to flag a potential issue with this edit. In OSM, name:en is generally expected to reflect the most commonly used English name of a place. For this city, “Jerusalem” is the standard and widely recognized English name, so it would be preferable to keep name:en=Jerusalem.

Would you be open to adjusting the name accordingly?
Skayyali3 (2026-03-28 11:36:44+00:00): Did I accidentally change it? Didn't realize did this when it was still early morning.
pitscheplatsch (2026-03-28 15:41:08+00:00): Thanks for correcting @Skayyali3

https://pewu.github.io/osm-history/#/relation/6502363

https://www.openstreetmap.org/changeset/180538994
NeisBot (2026-03-28 02:42:40+00:00): Welcome, and thanks for your edits!

I noticed a few unintended crossings between roads and/or between roads and buildings in this changeset. This usually happens when geometry snaps incorrectly. Additionally, changes to tagging (e.g. modifying highway types or adding tags) can lead to unexpected crossings being detected afterwards.

In total, I detected 17 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/848466076 v3 | 9 crossings
https://osm.org/way/153269275 v3 | 8 crossings

⚠️ Dragged Nodes (max 3):
https://osm.org/node/1658347652 v3

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=180527524
eerib (2026-03-28 03:58:43+00:00): An option is always to use natural=hill

https://wiki.openstreetmap.org/wiki/Tag:natural%3Dhill

The only challenge with this option is that no mainstream outdoor navigation apps display natural=hill features.
Solarisphere (2026-03-28 05:48:56+00:00): Mapping for the renderer and all that...

But is that much better that natural=peak? Both are for local high points, and it's debatable whether there's a high point here.
Crazycaver (2026-06-28 15:40:35+00:00): I’ve been here and it’s just an open, almost marshy area. Not even much prominence from the surrounding area.
Minh Nguyen (2026-05-14 20:25:52+00:00): https://www.openstreetmap.org/changeset/182669505 changes the network=* of the Ohio River Scenic Byway in Ohio back to US:OSRB for consistency with the Indiana portion. As far as I know, there’s no Ohio’s Byway branding on this route, just the multistate branding, so there’s no need to give it a similar network=* value. Also, renderers like OpenStreetMap Americana already depend on the US:OSRB value, so this change had the effect of breaking shields that were working.
jhaluska80 (2026-04-03 00:05:37+00:00): That's some quality building outlines.  Always nice to see it.
0x4273 (2026-04-03 00:25:22+00:00): Thank you! The Bing imagery is so crisp its just a joy to trace
NeisAgent (2026-03-28 05:33:17+00:00): 🕵 The changeset tags appear to reference Google as a data source.

Please note that using Google Maps, Google Street View, or similar Google services as a mapping source is not allowed in OpenStreetMap due to license restrictions.

More information: https://wiki.openstreetmap.org/wiki/Google

If the data in this changeset was derived from Google or another incompatible source, the edits may need to be reverted.

If this is a misunderstanding and the data was collected from permitted sources (e.g. local survey, Bing imagery, local knowledge, etc.), please clarify in a reply.
Himké (2026-03-28 17:21:49+00:00): https://community.openstreetmap.org/t/southern-ontario-road-classification-ongoing-thread/139281
JuanElDemografo (2026-03-28 13:26:10+00:00): Hi I see you requested review on this. All the changes you made seem reasonable, but I would advise you split such geographically dispersed changesets up. In this case, you corrected roads in Texas, Oregon, and Georgia, which are all quite far apart. This makes them difficult to review and alerts people across the country.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/180527998
Mxdanger (2026-04-06 02:30:25+00:00): https://wiki.openstreetmap.org/wiki/Changeset#Geographical_size_of_changesets
ColbyTheWorldTraveler (2026-04-06 19:49:06+00:00): I agree with Juan. I'm trying to review changes made in Idaho, which technically, this changeset covers.
            ---
            #REVIEWED_GOOD #OSMCHA
            Published using OSMCha: https://osmcha.org/changesets/180527998
NeisAgent (2026-03-28 05:33:19+00:00): 🕵 The changeset tags appear to reference Google as a data source.

Please note that using Google Maps, Google Street View, or similar Google services as a mapping source is not allowed in OpenStreetMap due to license restrictions.

More information: https://wiki.openstreetmap.org/wiki/Google

If the data in this changeset was derived from Google or another incompatible source, the edits may need to be reverted.

If this is a misunderstanding and the data was collected from permitted sources (e.g. local survey, Bing imagery, local knowledge, etc.), please clarify in a reply.
Frank Peng (2026-03-28 06:36:21+00:00): If you check the OpenStreetMap GPS traces of this location, you will find that the alignment of roads and Wilson Creek in Bing imagery of this location is not aligned with the GPS traces. But if you look at VBMP aerial imagery of this location, you will see that the alignment of roads and Wilson Creek at this location is aligned with the GPS traces, reflecting their actual alignment on the ground. So, before adding or moving OSM objects, make sure to check the GPS traces so that you will know their actual alignment or where they actually are on the ground. Aerial imagery may be distorted, which is common in mountainous or hilly areas. Orthoimagery is usually not distorted.
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.org/changesets/180528078
Frank Peng (2026-03-28 21:03:10+00:00): I would consider that this changeset be reverted as it adjusted roads and streams to distorted Bing aerial imagery of this location, which is not aligned with GPS traces. VBMP aerial imagery of this location is not distorted and well aligned with GPS traces, as it's orthoimagery.
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.org/changesets/180528078
iismitch55 (2026-03-29 02:18:31+00:00): Realigned using VBMP imagery, reverting previous realignment:
https://www.openstreetmap.org/changeset/180564777#map=14/37.17669/-80.37486
CAM-Gerlach (2026-03-29 08:05:54+00:00): Frank mentioned it, but just to emphasize--in addition to selecting and using the most appropriate imagery source(s) for an area when mapping, it is also critical to use GPS tracks and reference features in multiple imagery layers to set the correct imagery offset, especially with fine-scale mapping and performing alignment of features like this. This is especially true with VBMP as it has a significant (>1 m) and somewhat varying offset over the Blacksburg area (whereas Bing, orthorectified or not, typically hews close to GPS traces for features at ground level). This unfortunately affects many if not most existing features in the Blacksburg area, including mapping performing recent, very detailed micromapping of things like individual parking spots that are most affected by a lack of offset. Spending just one minute to get the offset dialed in before mapping in a new area can save other mappers hours, sometimes days later of fixing the alignment on everything you map.
InsertUser (2026-03-28 16:00:44+00:00): What database?
pepsi_max2k (2026-04-05 00:30:22+00:00): Cảm ơn bạn đã cập nhật thông tin. Liệu các tuyến đường tiếp cận xung quanh Tứ Liên có nên được gắn thẻ là highway=proposed không? Trừ khi công trình đã bắt đầu thi công, trong trường hợp đó chúng ta có thể xóa bỏ bất kỳ tuyến đường nào đã bị phá dỡ trước đây không? Hiện tại rất khó để hiểu tuyến đường nào vẫn còn tồn tại và tuyến đường nào đã bị phá dỡ.

Would the approach roads around Tứ Liên be better tagged as highway=proposed ? Unless construction has physically started, in which case could we remove any previous roads that are demolished> It is currently confusing to understand which roads are still present, and which are not.
Rudy Yanez (2026-03-30 03:13:27+00:00): gpx=12266990
NeisBot (2026-03-28 05:12:42+00:00): Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description, note or slogan contain detailed text that may be interpreted as promotional or SEO-related. To ensure OSM remains neutral and focused on map data, I recommend keeping descriptions concise, factual, and free from marketing or promotional language.

⚠️️ Problematic element (limit 1):
https://osm.org/node/13685873147 v1

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Building entrance"

#MapWithoutSpam
NeisRevert (2026-04-05 10:33:06+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/180889891
(Clean up leftovers from previous edits)
NeisBot (2026-03-28 05:33:40+00:00): Welcome, and thanks for your edits!

I noticed a few unintended crossings between roads and/or between roads and buildings in this changeset. This usually happens when geometry snaps incorrectly. Additionally, changes to tagging (e.g. modifying highway types or adding tags) can lead to unexpected crossings being detected afterwards.

In total, I detected 18 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/16072003 v7 | 10 crossings
https://osm.org/way/16068278 v4 | 8 crossings

⚠️ Dragged Nodes (max 3):
https://osm.org/node/161452380 v4

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=180529202
greatnameguys2472 (2026-03-29 02:19:16+00:00): Fixed
Frank Peng (2026-03-28 06:50:28+00:00): As mentioned previously, make sure to check the GPS traces before adding or modifying OSM objects, so that you will have an understanding of their actual alignment or location on the ground. The boundary of the farmland multipolygon you created in this changeset (https://www.openstreetmap.org/relation/20383306) doesn't actually align with the GPS traces of this location.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/180529671
arjunaraoc (2026-04-05 12:55:04+00:00): Welcome to OSM.  Please visit  India page on OSM wiki (https://wiki.openstreetmap.org/wiki/India) and  join OSM India Telegram channel (https://t.me/OSMIndia). Deleted subsequently
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.org/changesets/180529795
Lucy miau (2026-07-23 11:48:20+00:00): Warum hast du einige Tags von diesem EDEKA-Supermarkt entfernt?
Metallurgin (2026-07-23 12:05:00+00:00): Hab ich das getan? 😳
Lucy miau (2026-07-23 12:12:01+00:00): Wenn ich Version 18 und 19 von way/25118573 vergleiche, ist einiges weggekommen.
eggie (2026-03-28 08:33:29+00:00): Dag Twanton...
Wanneer een instelling is verhuisd wordt niet de naam op het oude adres SNP Natuurreizen (verhuisd).
In dat hgeval gewoon de bedrijfsinfo verwijderen.
Nieuwe bedrijven graag bijtaggen op de bestaande adresnode.
Zet ook commentaar op je changeset wat je hebt gedaan svp,

MVG
eggie
eggie (2026-03-28 08:35:15+00:00): Als bovenstaand aangepast
MarinoBM (2026-03-31 21:51:52+00:00): Hola GGZALAM, bienvenido y gracias por tus aportaciones a OpenStreetMap.
Cuando se añade una construcción hay que indicar de qué tipo de construcción se trata. Por ejemplo
building=construction
construction=apartments
https://wiki.openstreetmap.org/wiki/ES:Tag:building=construction?uselang=es
Un saludo.
SomeoneElse (2026-04-03 18:42:46+00:00): Hello,
This defibrillator is in the middle of the Atlantic. Isn't it dangerous yo use one with so much water around :) ?
daganzdaanda (2026-03-28 21:45:27+00:00): Hallo Koni, 
willkommen bei OpenStreetMap!

Danke, dass du die Karte in deiner Gegend verbesserst!
Leider ist der BayernAtlas wegen Lizenzproblemen keine zulässige Quelle für OSM. Adressen und Hausnummern müssen wir vor Ort herausfinden. Mit der "StreetComplete" App geht das auch recht gut. 

Ich mache diese Änderungen rückgängig. Bitte lass dich deshalb nicht entmutigen und hilf weiter bei OSM mit!

Servus, daganzdaanda
daganzdaanda (2026-03-28 22:13:58+00:00): Hier der teilweise Revert: https://www.openstreetmap.org/changeset/180561008
Ich habe nur die Adressen rückgängig gemacht, die neuen Gebäude sind ja auf dem Luftbild zu erkennen.
osmviborg (2026-03-28 08:57:23+00:00): Dit første forsøg var faktisk OK, kortere afstand til Marienborg Alle. Du bliver dog nødt til at væbne dig med tålmodighed, routeværktøjerne bruger en kopi af af OSM, ikke den live version, som du lige har opdateret. Der kan gå mange dage før routeværktøjerne er opdateret.
crassconcrete (2026-03-28 09:17:54+00:00): Yes, det fik jeg også lige googlet mig frem til. Jeg giver det et par dage. Tak for input.
marczoutendijk (2026-03-28 08:21:34+00:00): This changeset reverts some or all edits made in changesets 180034047, 180034283, 180034286, 180063342.
aceman444 (2026-04-03 15:40:52+00:00): Tak su to nabijacky pre auta? Nie je to tam uvedene. A naozaj to nie je ZSE Drive?
Andrei Lazarev (2026-05-01 14:45:49+00:00): C чего бы это мост «Египетский», если он Турецкий?
Cherryvolk (2026-05-01 17:59:32+00:00): А почему он турецкий? О предназначении переселенческого тракта нет единой позиции, а то, что мосты строили турки - ещё менее достоверная легенда
Andrei Lazarev (2026-05-02 08:27:31+00:00): Так если он 9 лет как «Турецкий», почему вы вдруг ставите «Египетский»?
mos_next_door (2026-03-28 17:31:07+00:00): Hi aggelosy,
Thanks for your contribution! Please remove building= tag from the area - now it looks like the whole territory is a building. You can add actual buildinga inside this area. Also amenity=kindergarten might be a better tag.
ika-chan! (2026-03-28 10:56:08+00:00): Please do not remove roads just because it is private. Instead, tag it with access=private.

https://www.openstreetmap.org/changeset/180537029
kingkingHK (2026-03-29 03:39:54+00:00): Why did you remove `surface:colour=`?
Kovoschiz (2026-03-29 06:53:15+00:00): Might be an SC bug. But I can't imagine why it does this. Need to test the app on Android.
HBRSC (2026-03-31 14:20:19+00:00): Sorry, this was unintentional.
The question I answered (in the app StreetComplete, Android) concerned the surface (asphalt, concrete, etc.). No questions were asked about the surface color.
arjunaraoc (2026-04-05 13:01:57+00:00): Welcome to OSM.  Please visit  India page on OSM wiki (https://wiki.openstreetmap.org/wiki/India) and  join OSM India Telegram channel (https://t.me/OSMIndia). You can not  have a feature without a tag. example  https://www.openstreetmap.org/way/1493582087#map=18/14.659135/77.552520  Please check all your edits and add proper tags.
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.org/changesets/180534255
NeisBot (2026-03-28 09:42:39+00:00): Welcome, and thanks for your edits!

I noticed a few unintended crossings between roads and/or between roads and buildings in this changeset. This usually happens when geometry snaps incorrectly. Additionally, changes to tagging (e.g. modifying highway types or adding tags) can lead to unexpected crossings being detected afterwards.

In total, I detected 10 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/1493582764 v1 | 10 crossings

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=180534482
NeisReview (2026-04-05 10:33:08+00:00): ✅ Should be fixed by 
https://osm.org/changeset/180566646
EasyKoni (2026-04-20 05:04:32+00:00): Small roads in villages should not be classified as Secondary and in most cases not even Tertiary.

The Indonesian classification of roads already  allows smaller roads to be classified bigger than in the rest of the world:
https://wiki.openstreetmap.org/wiki/Id:Jalan 

Some of your changes definitively don’t classify for Secondary:
"Jalan yang menghubungkan secara efisien antar pusat kegiatan wilayah atau menghubungkan antara pusat kegiatan wilayah dengan pusat kegiatan lokal”

They don’t connect regional centres and are also not efficient.

Thank you.