piebro/osm-data huggingface dataset:
NorthCrab_upload (2025-11-30 21:22:24+00:00): 🗺️ Witaj na OpenStreetMap!

Zauważyłem, że Twoja zmiana zawiera niepoprawne adresy. Przygotowałem listę obiektów do poprawy oraz dodatkowe informacje:

Nieprawidłowa wartość addr:postcode. Kod pocztowy powinien być formatu XX-XXX, gdzie X oznacza cyfrę.
https://www.openstreetmap.org/way/1427048749

Dokumentacja adresów (po polsku):
https://wiki.openstreetmap.org/wiki/Pl:Key:addr:*

W razie problemów lub pytań, proszę pisać. Chętnie pomogę.
Pozdrawiam! 🦀
eggie (2025-11-30 21:27:44+00:00): Dag bleutooth,

Vaak is het beter om geen junction roundabout toe te voegen aan het fietsgedeelte.
Soms is sprake van een tweerichtingrotonde.  Wanneer je dan er een rotonde van maakt zijn de vele fietsrouterelaties stuk.
Een deel op oneway=no zetten heeft geen zin.
Dus het is oppassen geblazen met dit soort aanpassingen. De voorgaande mapper is een zeer ervaren mapper en al bewust de rotonde hebben weggelaten.
MVG
eggie
user_16201490 (2025-12-01 18:52:29+00:00): Hmm... ok... Want de rotonde zelf is maar 1 richting voor de fietsers. Ze hebben het een beetje raar ingedeeld met de zijwegen noordelijk en zuidelijk, maar het is een rotonde met één richting voor de fietsers. Net zoals met de auto.
eggie (2025-12-01 20:49:11+00:00): Beste bleutooth,

Je vroeg feedback..

Hier ging het goed, maar als je roundabout gaat taggen op meer rotondes dan gaat het dus fout in de routering.
Zie bovenstaand commentaar. :)
SLMapper (2026-03-23 19:11:41+00:00): Hi Dimitar, this line has no tags on it after your edit
https://www.openstreetmap.org/way/1351213418/history
Dimitar155 (2026-03-26 16:47:15+00:00): Hi SL,, The line should've been part of Kalofer's level 8 admin boundary but it has not been added. I've added it.
PizzaTreeIsland (2025-11-30 21:32:01+00:00): Hi, 
I see that you requested a review. To answer your question: Roundabouts don't usually have names (unless they are big enough and have their own addresses) so it is correct not to use the name tag here. See https://wiki.openstreetmap.org/wiki/Tag:junction%3Droundabout. You can even use noname = yes to signify that it really does not have a name. See https://wiki.openstreetmap.org/wiki/Tag:noname%3Dyes for that. 
So I would in that case also remove the name = Knalhuttenweg tag from the western semi circle of the bike path. 
Other than that, your change set was really good! Thank you and happy mapping!
eggie (2025-11-30 21:34:17+00:00): We geven in OSM geen straatnaam aan een rotonde, behalve als de rotonde een eigen naam heeft.
Bij die fietspaden wordt dan weer gesjoemeld, maar die krijgen meestal niet junction roundabout mee omdat dat de fietsroutes stuk maakt.
Op een tweerichtingrotonde gaat het dan sowieso fout.

MVG,
eggie
eggie (2025-11-30 21:40:00+00:00): Dan hoeft er geen oneway=yes op een rotonde getagd te worden. het is het een of het ander.
https://community.openstreetmap.org/t/oneway-op-rotondes-spontaan-stoppen-van-de-afslagaanwijzingen/92703

en
https://community.openstreetmap.org/t/eenrichtingsverkeer-en-rotondes/80368

Ik voeg zelf aan 'fietsrotondes' geen junction=roundabout aan.
De routerelaties kloppen hier nog wel, maar het zijn wandelroutes. 
Bij fietsroutes gaat het dus vaak verkeerd dit soort aanpassingen.
Groet,
eggie
eggie (2025-11-30 21:48:01+00:00): Dit is een voorbeeld waar de fietsroutering direct om zeep zou zijn als je er een rotonde van zou maken.
Gedeeltelijk oneway=yes en oneway=no (en dat laatste doet niets in OSM met de routering) 
https://www.openstreetmap.org/#map=19/51.835649/4.692254

Mijn advies zou zijn om niet op zoek te gaan naar fietsrotondes waar junction=roundabout ontbreekt. 
Mapse
eggie
eggie (2025-11-30 21:51:35+00:00): .. en om je weer aan het twijfelen te brengen mbt straatnamen :) zie https://community.openstreetmap.org/t/straatnaam-en-wegnummer-op-rotonde/84339
PizzaTreeIsland (2025-11-30 21:38:08+00:00): Hello, 
thank you for your edit! Please take your time to write proper changeset comments in the future to make it easier for others to see what you did. 
https://wiki.openstreetmap.org/wiki/Good_changeset_comments

Thanks and happy mapping!
PizzaTreeIsland (2025-11-30 21:42:47+00:00): 	Hello,
thank you for your edit! Please take your time to write proper changeset comments in the future to make it easier for others to see what you did.
https://wiki.openstreetmap.org/wiki/Good_changeset_comments

Thanks and happy mapping!
stevea (2025-12-02 02:17:57+00:00): Thanks for the fix here, Kerry, I had not noticed this.
RedGreenBlue09 (2025-11-30 22:39:52+00:00): Source:
https://kiengiang.gov.vn/trang/TinTuc/255/9042/Ho-so-Quy-hoach-su-dung-dat-den-nam-2030-va-Ke-hoach-su-dung-dat-nam-2022-cua-huyen-Go-Quao.html
https://kiengiang.gov.vn/trang/TinTuc/255/13690/Ho-so-Quy-hoach-su-dung-dat-den-nam-2030-va-Ke-hoach-su-dung-dat-nam-2022-cua-huyen-Vinh-thuan.html
https://sogtvt.camau.gov.vn/quy-hoach/quy-hoach-ket-cau-ha-tang-giao-thong-duong-bo-do-dia-phuong-quan-ly-tren-dia-ban-tinh-ca-mau-den-192436
https://tuoitre.vn/3-900-ti-dong-lam-52km-duong-ho-chi-minh-qua-mien-tay-20231011140542624.htm
NorthCrab_upload (2025-11-30 22:51:44+00:00): Zauważyłem, że Twoja zmiana zawiera niepoprawne adresy. Przygotowałem listę obiektów do poprawy oraz dodatkowe informacje:

Duplikat adresu w okolicy. Adres można oznaczyć na dwa sposoby: na obszarze (dokładniejsze) albo na punkcie. Aktualizując adres, należy się upewnić, czy w okolicy nie pozostały żadne duplikaty.
https://www.openstreetmap.org/node/8460769740
https://www.openstreetmap.org/way/1455011779

Dokumentacja adresów (po polsku):
https://wiki.openstreetmap.org/wiki/Pl:Key:addr:*

W razie problemów lub pytań, proszę pisać. Chętnie pomogę.
Pozdrawiam! 🦀
YomanNH (2025-12-01 20:42:12+00:00): Barroszt, znowu założyłeś kolejne konto, żeby ominąć bana?
https://www.openstreetmap.org/user_blocks/18980
sarnek (2025-12-03 19:05:07+00:00): tyle dobrego zrobiłem dla tego projektu, musiałeś te złościwości wylać :) spójrz na mapę Torunia i okolice w OpenStreetMap, dużo pasji w to włożyłem, żeby nie był jakimś badziewiem, tylko odzwierciedlał rzeczywistość
sarnek (2025-12-03 19:05:49+00:00): tak to ja, moje edycje przynoszą prezenty w postaci aktualniejszych, bardziej kompletnych map
Yog Sot (2025-12-01 21:19:49+00:00): not a footway...
NeisBot (2025-12-01 00:06:34+00:00): Hi NoneyaBidness, welcome to OSM!

Thank you for your contributions to the map. I have reviewed your recent edits and noticed that 100% of the changes in this set involve deletions, including:
- 11 highway(s)

Could you please confirm if these deletions were intentional or if they occurred by mistake?

Looking forward to your response.

#DeletionsCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=175335797
NoneyaBidness (2025-12-01 00:18:16+00:00): This is intentional, these trails have been completely destroyed by the park. New trails are being built but are nowhere near complete and will not follow any of the old paths. Please remove these so they no longer show on any maps and so when the new trails are finished they can be added
NoneyaBidness (2025-12-08 19:21:12+00:00): Can someone help? I am still seeing these old/destroyed trails on Trailforks Topo map. These trails no longer exist and are presenting an overlay obstruction to mark the new trails. How can this information be deleted permanently?
user_5359 (2025-12-09 07:31:29+00:00): Welcome to OSM! Please read the wiki before changing route tagging. What is the mean of the tag source="network=nCN" or network:type	= "network=ncn" ?
MassCartog (2025-12-01 01:59:08+00:00): Hi welcome to OpenStreetMap, Could you explain a little bit more why you removed these trails. Try to add good change that comments so others understand why you are doing what you are doing.

Looking at the Strava heatmap data for this area in the last 12 months it looks like the trails you removed were pretty accurate. So could you give us a little bit more context why you decided to remove them? thanks 

https://i.imgur.com/Cqzb3pZ.png
NoneyaBidness (2025-12-01 02:07:14+00:00): Yes, the trail exists but the name and route/direction were completely wrong. I am the Trailforks Administrator for Oleta, OpenStreetMaps has most of these trails completely wrong and I am trying to update them.

https://www.trailforks.com/region/oleta-river-state-park
MassCartog (2025-12-01 15:17:12+00:00): Okay thanks for the reply and the added context. When changing things on OSM its better to update the data that is already there instead of removing it all and starting again. This preserves the history of the feature, I added a Link to the wiki page if you would like to read more about that. 

As theses trails do exist on the ground, and they match up pretty well with current strava heatmap data they have been restored. This changeset removed 3 trails, not a ton of work was lost.

Feel free to update them again, but if you are going to remove them they should be replaced with at the corrected features at same time. Removing mostly accurate data with the intension to fix it later is not a good practice, since sometimes we forget or get busy and the trails are now gone. Also a lot of services that use OSM data only update every once in a while, and could just happened to pick today, now there would be no trails for months or even years on their maps. 

Thanks for updating the trails in this area, its good work!

https://wiki.openstreetmap.org/wiki/Keep_the_history
NoneyaBidness (2025-12-01 15:32:09+00:00): The old trails did not have the correct starting and ending point and did not flow correctly into each other. I have the trails updated on trailforks, can we use a GPX (or other) file to import the correct path for these trails?
Please let me know so they can be imported ASAP.
MassCartog (2025-12-01 16:10:08+00:00): Hi, if you are getting the GPX data or copying data from Trailforks that is not allowed!

See: 
https://community.openstreetmap.org/t/trail-forks-or-other-databases/103373

https://www.trailforks.com/about/data/

If they are YOUR gpx files, you can upload them to OSM here: https://www.openstreetmap.org/traces Then when they are uploaded, you can click, "Edit map" on that trace to open it in the editor.

Then you can trace over them. but again the trails dont seem far off, its better to just work with what is already there, adjusting and adding trails to match your imported GPS trace.
NoneyaBidness (2025-12-01 16:40:48+00:00): The GPS/X data are from my ride logs. There are several trails on OSM for Oleta that are completely wrong and are split into several sections when they are just one trail. I am seeing incorrect OSM trails/roads/data at every MTB park I administer and is very frustrating seeing basemap data that is outdated or just plain incorrect. I will not spend a lot of time re-creating something that has already been done. Can someone help understand how to add current and CORRECT trail data to OSM as quickly and efficiently as possible?
MassCartog (2025-12-01 17:04:31+00:00): OSM is all volunteer and if you are not interested in taking on the work to update the trails no worries. But we ask for you not to removed existing work that others before you have done without replacing it with more accurate information.

This map editor is not able to use your imported GPX tracks directly. You would need to use a more advanced editor tool for that. How it works here with this in browser editor is you import your GPX tracks and you can trace them out in the editor. Its not that much work once you learn some basics. 

Once you import the GPX file into the iD editor, it will display the track as a background layer for you to manually trace over. OSM does not automatically convert GPX data into a road or path feature, as GPX files often contain inaccuracies. You will need to manually draw the new way by clicking along the GPX trace, smoothing out any "wiggles" or inaccuracies as you go. 

That just how this editor works.

I'd suggest learning how to use the tools before tackling really big projects.
NoneyaBidness (2025-12-08 19:39:47+00:00): There are so many things wrong with the trail data in this area. To start with, the trail named Gilligan is not called Gilligan and is a part of another trail and it is marked with the wrong direction going the opposite direction of a downhill path and should be considered a safety issue. The other trails in this Region do not have the correct route/path. I understand you suggest these be left for others to see but if anyone followed them, they could cause serious injury due to someone going in the correct direction. I am frustrated that OSM insists on keeping/using incorrect or long outdated information rather than removing it. There are over 9 miles of trails here and almost everything on OSM is completely wrong. I have spent a substantial amount of time updating the trail on Trailforks and are up to date with correct routes and directions and wondering why that would not be an easy solution to add to OSM.
MassCartog (2025-12-08 20:58:38+00:00): Hello again! OSM is all volunteer, if you know its incorrect, you can choose to volunteer your time to fix it. Or you can choose to leave it alone, but again you cannot remove it without replacing it.

I've taken a look and compared the trails with a heat map, I circled some parts that do look bad here:

https://i.imgur.com/YYtTO7i.jpeg

But as you can see, there are a lot more parts that look alright, good enough for navigation, much much better then nothing if they are removed all together.

Someone spent their time mapping these trails, they are not 100% accurate yet, but that is the nature of OSM, we improve the map, we don't remove it.

There are tools that could let you import your work and add it to OSM. But they have a much bigger learning curve then the editor here. If your willing to spend the time learning the tools and improving the map check out the editor called "JOSM".
JoeG (2025-12-31 00:47:01+00:00): Hi! I intend to revert deleted fences and footway=sidewalk in this one.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/175336140
5m4u9 (2025-12-02 15:28:47+00:00): hola, gracias por mejorar el mapa.

Solo tengo una sugerencia, cuando edites (dibujes) edificios rectangulares, hay una opción para rectangulizarlos (colocar esquinas a 90°)...

Solo debes seleccionar lo que dibujaste (edificio) y seleccionas la 3ra opción (clic derecho) o presionas la tecla Q. Puedes seleccionar varios edificios a la vez...
gpserror (2025-12-01 01:13:12+00:00): urk.  Should use ref=x instead the "descriptive name" of name="building x"
ICT_maps (2025-12-01 01:52:19+00:00): Easy enough - swapped them over at https://www.openstreetmap.org/changeset/175337578
gpserror (2025-12-01 06:47:31+00:00): Thanks!  Sorry I started making some changes but then noticed you got some so I abandoned my edits so we don't collide.
Thanks again for taking care of it all!
Udarian (2025-12-01 02:13:33+00:00): this is either completely wrong or its position is very incorrect as the Outback Steakhouse that this was placed inside of seemingly still exists based on its website and I have seen it open somewhat recently.
https://locations.outback.com/florida/miami/7705-w.-flagler-street

Happy Mapping,
Udar.
Fizzie-DWG (2025-12-06 22:01:10+00:00): DWG revert - fictitious changes

https://www.openstreetmap.org/changeset/175602975
maxwellward (2025-12-01 04:51:36+00:00): 👋 Hi pussreboots, thank you very much for your contribution!

Just a heads up, when working with buildings and other often square-like objects, please square the objects.

You can use "Q" on your keyboard (or right click -> "Square") to square off the corners of a building to more accurately match the aerial imagery.

If you have any questions, please feel free to respond here and I'd be happy to help.
旧加卷 (2025-12-11 06:24:17+00:00): Why was Dongguanxi Railway Sta. (n/12290352339) excluded from the route relation?
"public_transport=station" is duplicated.
samho1234567 (2025-12-11 07:39:11+00:00): I didn't intend to delete Dongguanxi Railway Sta. (n/12290352339) from the route relation. This note was deleted from the route relation accidentally. The purpose of this changeset is to create a stop area of Dongguanxi Railway Station. It might be a bug of iD editor.
bxl-forever (2025-12-01 02:36:34+00:00): Hello, and welcome to OSM.

Please do not type addresses directly on shops, that causes unwanted duplicates (especially here because what you typed mismatched the official spelling).  We fixed your edit.
KennyDap (2025-12-01 03:40:54+00:00): Vandalism

https://www.openstreetmap.org/changeset/175339222
Frans S (2026-02-28 13:37:16+00:00): Hello. Thanks for mapping.
Please do not connect nodes of buildings to each other or other features.
Check the instructions under Buildings:
'Try to avoid the overlapped building and glued to each other.'
Best regards
CAM-Gerlach (2025-12-01 21:08:06+00:00): Hey, so just FYI as this changeset neglected to update the corresponding tags when changing the modeling/geometry, it resulted in broken tagging and route guidance, with an incorrect `lanes` and missing `turn:lanes`, `destination:lanes` and `destination:lanes:ref` on the Price's Fork Road westbound way leading in to the junction, and spurious `turn:lanes`, `destination:lanes` and `destination:lanes:ref` that lead to nowhere on the way before that. Also, while given the lack of physical separation the modeling change is justifiable per OSM conventions, the new motorway link positioning is displaced well off the physical carriageway centerline it should be following, leading to skewed turn geometry for Price's Fork westbound.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/175338357
CAM-Gerlach (2025-12-01 21:08:46+00:00): I've fixed this in changeset #175376236 https://osmcha.org/changesets/175376236 as well as refined the Price's Fork eastbound positioning to better align with reliable imagery and reduce the skew in that direction, as well as using `placement` to displace the turn lane to the motorway link to its correct position. (I considered merging the two Price's Fork westbound ways, but as that would modify a bunch of bus route relations ballooning the changeset size, I decided against it).
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/175338357
LordGarySugar (2025-12-02 18:45:38+00:00): Hi, thanks for making this change. Fyi your edit removed building=apartments which I have just restored.
mueschel (2025-12-04 11:04:44+00:00): Hi,
I found several 'service:en' tags on train routes.
"service" is a defined tag as described in the wiki and doesn't need translations in different languages. The defined value for local trains is "regional".

The type of service (各駅停車) has been tagged on some other routes as "service:name" which seems to be the better tag for this.
AlexM51 (2025-12-07 20:59:32+00:00): Hi.
I'm thinking about better tagging for different services and finally choose "service:name" which can be localized in standard way.
Local train routes in Japan often too short to classify as regional.
ivanbranco (2025-12-25 19:31:26+00:00): Hi likeToTravel, 

thanks for your edits. I was wondering what's the source for the fence you mapped? Is not visible in the imagery you used...

At the same time you deleted this fence: https://www.openstreetmap.org/way/1434631241/history
which is visible in the imagery used to trace it (Ersi world imagery)

thanks and good mapping
likeToTravel (2025-12-25 20:14:36+00:00): you may add it back if you see it @ivanbranco
ivanbranco (2025-12-25 20:19:13+00:00): Maybe your source is more up to date, which is why I asked. Would you mind sharing which source you used, so I can check as well?
likeToTravel (2025-12-25 20:23:44+00:00): I think I used bing but tbh I forgot what imagery i used, thats why in newer changesets i started putting what imagery i was using
I-76 (2025-12-08 00:11:55+00:00): Hello sconner1987, and welcome to Openstreetmap! I just have an FYI about your change here - Unless "Maintenance" is the official name of this building, please don't tag it as such. You could retag the building as a shed, maybe, but please don't use the name field for a description, if that's what it is. Thanks!
i2004 (2025-12-01 11:11:55+00:00): que cambios hiciste en esas lineas?
Fizzie-DWG (2025-12-01 06:02:22+00:00): DWG revert - improper deletions

https://www.openstreetmap.org/changeset/175341714
Fizzie-DWG (2025-12-01 06:00:26+00:00): Please see https://www.openstreetmap.org/user_blocks/19060
Kovoschiz (2025-12-01 11:45:17+00:00): Please don't blindly merge different road sections. They are split to show different attributes.
Kovoschiz (2025-12-01 11:51:16+00:00): I don't know what you are doing. But you should multi-select by holding [Shift] as usual.
user_5359 (2025-12-09 09:42:13+00:00): Hello! Please have a look on https://www.osm.org/node/3044538941. Did you have any source for the value of the key population:212 ?
user_5359 (2025-12-01 07:34:22+00:00): Welcome to OSM! Sorry, but business entries without addresses are not in line with OSM. Please add the street and house number, or we will have to mark this as SPAM.
I have now reverted your changes.
NeisBot (2025-12-13 21:54:26+00:00): Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description or slogan contains 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.

Could you please revise your description accordingly?

For example, a more neutral and factual version of your description could be: "Home cleaning service in Highlands Ranch"

#MapWithoutSpam #Comment #Description
pitscheplatsch (2025-12-13 22:01:27+00:00): Reverted by https://www.openstreetmap.org/changeset/175344056
Ewen Hill (2025-12-01 07:29:51+00:00): Gday Steve, I hope you are good. When doing edits, try and just edit in a single country, preferably state or local area. It makes it easier for local validators to review changesets. Keep on keeping the rubber side down. Ewen
norgis (2025-12-04 13:20:34+00:00): Det ser ut som det har blitt innført en del feil gjennom denne importen: det er midtdeler større deler av strekningen fra øst (nesten helt inn til rundkjøringa) og vest (helt frem til der Gamle E6 kobles på), fjerna svingrestriksjon der midtdeler mangler i vest osv. Alt dette lå inne tidligere...
norgis (2025-12-04 13:27:48+00:00): NVDB har åpenbart gjort det enkelt med å la nyvegen være én linje uten midtdeler, men det stemmer altså ikke med virkeligheten. Plassering kunne blitt justert til å samsvare med NVDB, men geometrien slik det ligger nå etter importen er rett og slett feil. Løsningen slik den var før importen var bekrefta fra stedlig befaring.
NKA (2025-12-04 14:04:40+00:00): Hei, endringene ble gjort fordi den innmålte veien og rundkjøringen fra NVDB hadde en del avvik mot det som var lagt inn fra før. Innmålingene fra entreprenør for slike hovedveier pleier å stemme. Jeg la ikke inn midtdeler fordi det bare lå en forenklet midtlinje i NVDB og jeg har ikke vært på stedet. Du må gjerne justere slik at midtdeler kommer med, basert på hva du har synfart, og basert på den oppdaterte linjen. Du må gjerne legge inn svingerestriksjon også, men de pleier ikke være nødvendige for routerne i slike situasjoner. Svingerestriksjonen ble ikke oppdatert fordi jeg ikke visste hvor den nye midtdeleren ville ende.
norgis (2025-12-05 12:48:18+00:00): Jeg kommer ikke til å gidde å legge inn alt på nytt, nei, det bør jo den som overskriver informasjon fra stedlig befaring gjøre... Så du må gjerne justere slik at det stemmer overens med det jeg hadde lagt inn tidligere mht. midtdeler og adskilte kjørefelt!
norgis (2025-12-04 13:24:27+00:00): Har du kontrollert at dette stemmer? At fartgrensa var 70 der det var 3 felt før overgang til 2 var bekrefta fra stedlig befaring...
NKA (2025-12-04 14:09:29+00:00): Nei, jeg har ikke annen informasjon enn fra NVDB. Den egentlige endringen her var et forlenget påkjøringsfelt ift. tidligere.
TrickyFoxy (2026-01-01 16:01:27+00:00): Это точно парк, а не детская площадка?