piebro/osm-data huggingface dataset:
HellMap (2026-03-23 10:24:26+00:00): You are adding train stopping location points to the route as platforms (`platform`), but they should be stop locations (`stop`). The actual platform is the way or area that is drawn for the platform where passengers wait and board for this specific route.
MappingMore (2026-03-28 01:07:28+00:00): Reverted in changeset id:180526592
MaliMrav (2026-03-23 13:39:34+00:00): Zdravo Gagi1911,

Nisam nigde uspeo da nađem da se u nazivu:

Специјална болница за рехабилитацију 

Dodatno nalazi i reč "ANEMIA". Da li možeš da navedeš koji je izvor za ovaj naziv, ili ako je u pitanju greška, da ga ukloniš iz imena.

Hvala,
MaliMrav
Colbertson (2026-03-23 07:19:22+00:00): Did you mean the move the tree and fire hydrant?
ssundell (2026-04-19 19:31:07+00:00): Moi! En ihan ymmärrä tämän muutoksen tarkoitusta. Noilla osuuksilla, missä pyöräilymerkintää ei aiemmin ollut, pyöräily on sallittua. Hämeenkyrön osuudella - tässä muokkauksessa tuo Hanhijärven ja Heiskan eritasoliittymien väli - taas pyöräily on erikseen kielletty liikennemerkeillä.
ssundell (2026-04-19 19:33:10+00:00): Tarkennan vielä: tuolla välillä on siis kielletty pyöräily, kävely, mopoilu ja maatalousajoneuvot.
atervn (2026-04-20 15:03:10+00:00): Moi! Hyvä pointti. Olen joskus aikaisemmin pyöräillyt tuota Heiskan liittymästä Tampereen suuntaan, ja silloin siinä sai ainakin polkea. Lenkkiä suunnittelessa huomasin, että se oli nyt ainakin vastakkaiseen suuntaan kielletty (niin kuin nyt näkyy myös selkeästi esim google streetviewstä tuo mainitsemasi liikennemerkkikokoelma. Osaatko sanoa, että onko tuo Heiska-Hanhijärvi-suunta tuossa pätkällä myös nyt kielletty polkupyöriltä (ainakaan streetviewssä ei näy kieltoja, vaikka toiseen suuntaan on)?

Mutta kiitos huomautuksesta ja pahoittelut liian innokkaasta muokkaamisesta. Korjailen nuo tässä.
ssundell (2026-04-20 15:43:40+00:00): Moi! Joo, kaveri kävi eilen tarkastamassa, on myös Heiskasta Hanhijärvelle kielletty. 8)
atervn (2026-04-20 15:54:19+00:00): Selvä, hyvä tietää, ettei lähde lenkkiä tuolle välille suunnittelemaan. Kiitos vielä ja pahoittelut haitasta!
pwbriggs (2026-03-24 03:16:50+00:00): Hey, thanks for the edit! Address city name should be capitalized, and we use the state code (WA) instead of the full state name. The iD editor tries to autocomplete addresses based on nearby addresses it sees, but in sparsely-mapped areas like this one, sometimes you have to type out the full address information yourself.

My other note is that you almost certainly should use a "driveway" and not a "living street". Living streets are mostly a European concept, and similar laws and designations are rare in much of the United States. Living streets, I believe, are public and serve several residences, generally found in urban areas.

One last note is that usually buildings are rectangular or composed of rectangular shapes-in order to map these, you can use the "square corners" feature available in many editors, including the iD editor you used for this edit: select building > right click > "square" (or select building and press "q"). This will make buildings look a lot more clean and accurately represent their rectangularity.

Thanks for the contributions though. I know there's quite the learning curve to OpenStreetMap, and I'm glad you've stuck with us for some time now :)

Feel free to reach out if you have any questions. I don't remember if I've shared this with you before, but OSM US has a Slack workspace that I've found very helpful for mapping questions as well: https://slack.openstreetmap.us/

Happy mapping!
pwbriggs (2026-03-24 03:23:26+00:00): 3D tagging isn't my area of expertise, but this looks good as far as I know.

How did you get the building heights, did you use LiDAR or ARCore, or talk to building owners, or just estimate? Mostly just out of curiosity, because if you have a good process for obtaining building heights, I might have to learn from you :)

Happy mapping!
richlv (2026-03-24 12:54:58+00:00): Sveiki, paldies par kartes papildināšanu.
Jautājumi par OpenStreetMap laipni gaidīti Latvijas kopienas čatā - https://osmlatvija.zulipchat.com .
Vai tas būtu par tecēšanas virzienu rediģēšanu vai jebko citu.
AdamVista (2026-03-22 21:02:27+00:00): https://richard3.net/tag/autoroute-15/#:~:text=On%20s'entend%20que%20le,Bonne%20ann%C3%A9e%202020.
AdamVista (2026-04-10 22:09:37+00:00): Certains plans indiquent que la 15 peut aller jusqu'à Amos
OlasMapy (2026-03-23 11:52:13+00:00): nie bylo wycinek bylem tam
adas (2026-03-23 12:15:56+00:00): https://www.skyscrapercity.com/threads/lk-201-nowa-wieś-wielka-maksymilianowo-kościerzyna-gdynia.1444005/page-182?post_id=196964267#post-196964267
Ale to nowe zdjęcia.
OlasMapy (2026-03-23 20:59:47+00:00): super ale widac jedynie kolejki wiec nie wiem czm zaznacyzles caly obszar od bozenkowa do zoledowa
adas (2026-03-23 21:59:59+00:00): Ale wycinki zaznaczyłem przy torach. Nie do końca rozumiem o co chodzi. Podrzuć miejsce gdzie coś zrobiłem źle...
World_Winner (2026-03-23 11:31:31+00:00): Partially reverted in changeset id: 180300256
eggie (2026-03-22 21:35:22+00:00): Hoi,

Wellicht heb je hier iets aan?
https://viewer.satellietdataportaal.nl/@52.35350,4.913737,19/?datastrip=20260225_SVNEO-04&sensorname=SuperView-NEO
JakovBušić (2026-03-23 16:44:16+00:00): Wrong hgv restriction made in this changeset was set right in changeset/180314582. #OptimoRoute
World_Winner (2026-03-24 04:33:36+00:00): Reverted in changeset id:180333846
InsertUser (2026-03-24 22:58:02+00:00): You appear to have marked "Rolle's Electrical Plumbing & Hardware" (https://www.openstreetmap.org/way/1491651205) as a school. 

I assume this was a mistake?
StC (2026-04-11 09:43:57+00:00): Bonjour,

ce changeset a brisé la continuité d'un itinéraire pédestre qui passe par là. Je m'occupe de la réparation.
zbh0170 (2026-04-11 19:10:52+00:00): Désolé pour le désagrément. Je vais m'efforcer d'être plus vigilent.
IvaKraljić (2026-03-22 23:02:35+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180275555#map=17/42.772476/-73.782114. #OptimoRoute
IvaKraljić (2026-03-22 23:04:04+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180275595. #OptimoRoute
IvaKraljić (2026-03-23 16:22:05+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180313657. #OptimoRoute
IvaKraljić (2026-03-22 23:13:33+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180275785. #OptimoRoute
IvaKraljić (2026-03-22 23:14:44+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180275796#map=18/42.761072/-73.884695. #OptimoRoute
IvaKraljić (2026-03-22 23:15:39+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180275808. #OptimoRoute
NeisBot (2026-03-22 22:48: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 9 potential crossings.

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

⚠️ Dragged Nodes (max 3):
https://osm.org/node/3658278624 v5

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=180275231
rajdhani (2026-03-23 11:17:57+00:00): Reverted in changeset id:180299771
pitscheplatsch (2026-03-23 11:57:56+00:00): @rajdhani Thanks for fixing the mentioned issue and for commenting here.

Would it be possible to add a direct link to the changeset instead of only the raw changeset ID? Something like https://www.openstreetmap.org/changeset/180299771 would be very helpful.

Thanks!
IvaKraljić (2026-03-27 15:40:30+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180508922. #OptimoRoute
IvaKraljić (2026-03-22 23:44:04+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180276253. #OptimoRoute
IvaKraljić (2026-03-27 15:42:43+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180509016. #OptimoRoute
IvaKraljić (2026-03-27 15:44:18+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180509093. #OptimoRoute
IvaKraljić (2026-03-22 23:45:36+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180276268. #OptimoRoute
IvaKraljić (2026-03-27 15:46:08+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180509201. #OptimoRoute
IvaKraljić (2026-03-22 23:46:31+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180276279. #OptimoRoute
Tatfahren (2026-03-23 09:23:03+00:00): Da ist wohl was schiefgegangen, in diesem changeset hast du nur die Wege gelöscht.
IvaKraljić (2026-03-27 15:47:35+00:00): The wrong tag has since been deleted in the changeset https://www.openstreetmap.org/changeset/180509311. #OptimoRoute
IvaKraljić (2026-03-27 15:51:16+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180509485. #OptimoRoute
eggie (2026-03-23 07:56:42+00:00): Top!
IvaKraljić (2026-03-27 15:53:48+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180509613. #OptimoRoute
IvaKraljić (2026-03-27 15:55:23+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180509732. #OptimoRoute
IvaKraljić (2026-03-27 15:56:52+00:00): The unnecessary source tag has since been removed in the changeset https://www.openstreetmap.org/changeset/180509803. #OptimoRoute
IvaKraljić (2026-03-27 15:58:37+00:00): The wrong weight restriction tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180509897#map=18/42.764376/-73.888328. #OptimoRoute
IvaKraljić (2026-03-27 16:01:32+00:00): The wrong tag has since been fixed in the changeset https://www.openstreetmap.org/changeset/180510069. #OptimoRoute
iandees (2026-03-22 23:39:03+00:00): Hello! I noticed that node https://www.openstreetmap.org/node/6179289818 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/180276165, 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!
felipeeugenio (2026-03-23 12:10:26+00:00): Hola. El tag noexit va cuando los caminos se terminan y no es posible continuar en ningún medio. Aquí fue usado en un lugar donde el camino continúa.

Por otro lado, por favor no replicar el nombre del condominio/parcelación en los nombres de los caminos. Eso es incorrecto.
 Saludos
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/180276089
felipeeugenio (2026-03-23 12:29:35+00:00): Hola. Varios de los nombres que agregó están incorrectos. Cual es la fuente que está usando?
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/180276089
jptolosa (2026-03-23 21:34:50+00:00): Hola Bustte, en sus ediciones se ha cambiado reiteradamente nombres de calles y lugares. ¿Cuáles son las fuentes?
Saludos.
jamesks (2026-03-25 09:38:53+00:00): THanks. I have t fix alot of those too
CAM-Gerlach (2026-05-23 23:24:13+00:00): Removed addr:unit=* added to an entire building and fixed name=* and addr:street=* for this SEO POI in changeset 183087207

https://www.openstreetmap.org/changeset/183087207
LakeTana (2026-03-30 18:54:02+00:00): Hello brunoconter and thank you for mapping!

I noticed that in your changeset https://www.openstreetmap.org/changeset/180276477 you have upgraded multiple track highways to tertiaries. OSM policy states that tag highway=track is used for minor land-access roads that are mostly used for agriculture, forestry, outdoor recreation, and similar activities on open land (https://wiki.openstreetmap.org/wiki/Tag:highway%3Dtrack).

The highway=tertiary tag is used for roads connecting smaller settlements, and within large settlements for roads connecting local centres (https://wiki.openstreetmap.org/wiki/Tag:highway%3Dtertiary). Since these roads you upgraded are mainly used for agricultural purposes and do not appear to be connecting city centers and or settlements what do you think about changing them to tracks or even unclassified, as that class is for "minor public roads"? If you have any other resources or insight for the change in road class that supports all these being tertiary, please let me know and I would be happy to review. 
Thanks, and looking forward to hear from you.


Olá, brunoconter, e obrigado por mapear!

Notei que, no seu conjunto de alterações https://www.openstreetmap.org/changeset/180276477, você promoveu várias vias do tipo *track* (trilha/estrada rural) para a categoria *tertiary* (terciária). A política do OSM estabelece que a tag `highway=track` é utilizada para vias de acesso terrestre menores, usadas principalmente para agricultura, silvicultura, recreação ao ar livre e atividades similares em áreas abertas (https://wiki.openstreetmap.org/wiki/Tag:highway%3Dtrack).

Já a tag `highway=tertiary` é empregada para vias que conectam assentamentos menores e, dentro de grandes assentamentos, para vias que conectam centros locais (https://wiki.openstreetmap.org/wiki/Tag:highway%3Dtertiary). Visto que as vias que você promoveu são utilizadas majoritariamente para fins agrícolas e não parecem conectar centros urbanos ou assentamentos, o que você acha de reclassificá-las como *tracks* ou até mesmo como *unclassified* (não classificadas) — já que esta última categoria se destina a "vias públicas menores"? Caso você possua quaisquer outros recursos ou informações que justifiquem a alteração da classe dessas vias para *tertiary*, por favor, avise-me; terei prazer em analisá-los.
Obrigado, e aguardo seu retorno.
World_Winner (2026-03-24 10:33:33+00:00): Reverted in changeset id:180345417
Wildsharky (2026-03-25 10:24:26+00:00): Partially reverted in changeset id:180345712
Kovoschiz (2026-03-23 17:30:00+00:00): How is this a village? There's not even anyone living here?
MappingMore (2026-03-24 04:34:29+00:00):  Revert of 180231913
AlejandroAlba (2026-03-28 01:08:52+00:00): hola. No entiendo por que borraste el building del SUM Barrio Sur
MappingMore (2026-03-28 01:24:24+00:00): Reverted in changeset id:180242846
Glassman (2026-03-23 22:26:12+00:00): Thanks for the updates. One tip, please leave a changeset comment to help others and yourself with what was done. See https://wiki.openstreetmap.org/wiki/Good_changeset_comments for more information.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/180278173
TrickyFoxy (2026-04-19 15:34:51+00:00): Почему вы удалили весь парк?
CAM-Gerlach (2026-03-23 07:00:32+00:00): Hey Frank, just FYI per both the wiki and recent discussions and consensus with the OSM-US Pedestrian Working Group and PWG schema, since you already mapped separate kerb notes (great!) no need to tag kerb=* on the highway=crossing node when the kerbs are already tagged separately, and in fact that is actively discouraged, e.g. per the wiki https://wiki.openstreetmap.org/wiki/Key:kerb#To_add_information_to_another_map_feature

> If you place separate barrier=kerb nodes, please remove the kerb=* tag from [the crossing] node (otherwise a router might think that there are four kerbs to cross).

Also, just FYI I recommend tagging crossing:signals=* as well (no in these cases), as it is unambiguous and more clear and expressive then relying on the overloaded and somewhat ambiguous crossing=* tag, and it also is the only thing missing for your mapping here to get this area fully up to PWG Silver Tier https://wiki.openstreetmap.org/wiki/Foundation/Local_Chapters/United_States/Pedestrian_Working_Group/Schema
MappingMore (2026-03-28 07:57:31+00:00): Partially reverted in changeset id:180531576
statelyelms (2026-03-23 03:42:24+00:00): Man that is one dispicably ugly render they have for natural=ridge. Makes it look like the ridge is some one-metre-wide, knife's-edge stuff.
statelyelms (2026-03-23 03:43:48+00:00): Might end up removing it, the peak is all that really needs to stay. The tag description says "linear hill" which this matches very well but there's no accessible page article, only an error. And again, the render is butt ugly.
neuhausr (2026-03-24 14:45:19+00:00): Hi, the woods area you mapped in this changeset has some issues with self-intersection/nodes that are too close. (see warnings in changeset tags above, or the OSM Inspector https://tinyurl.com/mtnw3b6v) It'd be great if you could clean those up, and be aware of it going forward. Thanks and happy mapping!
one_half_3544 (2026-03-25 10:22:09+00:00): please don't duplicate existing date (e.g. https://www.openstreetmap.org/node/13670627541#map=19/42.222997/79.416362 is a duplicate of an already present natural=peak)
one_half_3544 (2026-03-25 10:22:58+00:00): Also, if you're adding natural=peak, please connect them to the existing natural=ridge lines
one_half_3544 (2026-03-25 10:27:32+00:00): Also, please don't add name=Tarn (https://www.openstreetmap.org/way/1491694643) - name tag is meant to be used for names, not descriptions (see https://wiki.openstreetmap.org/wiki/Key:name)
one_half_3544 (2026-03-25 10:31:37+00:00): Also, please don't add tags with default values (like tidal=no for https://www.openstreetmap.org/way/563699048/), they just clutter the database, not bringing any benefit
NeisBot (2026-03-23 03:54: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 7 potential crossings.

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

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=180279755
ajmat (2026-03-24 05:10:01+00:00): Partially reverted in changeset id: 180334537
woodpeck_repair (2026-06-11 09:09:21+00:00): This changeset has been reverted fully or in part by changeset 183960779 where the changeset comment is: revert low-quality AI building imports
Colin Smale (2026-03-23 09:04:07+00:00): The border you have removed was not a current administrative border but between the "traditional" counties of Essex and Hertfordshire, which has changed in the course of time, as you can see here: https://maps.nls.uk/geo/explore/side-by-side/#zoom=15.0&lat=51.86329&lon=0.17397&layers=10&right=osm
Removing a segment of the boundary breaks things for others, please revert this change!
Regards, Colin
LordGarySugar (2026-03-27 02:05:36+00:00): Restored in https://www.openstreetmap.org/changeset/180481933
woodpeck_repair (2026-06-11 09:01:16+00:00): This changeset has been reverted fully or in part by changesets 183960337, 183960380, 183960341, 183960408, 183960275, 183960389, 183960221, 183960319, 183960306, 183960280, 183960292, 183960414, 183960349, 183960228, 183960252, 183960358, 183960240, 183960299, 183960267, 183960399, 183960370, 183960328, 183960364 where the changeset comment is: revert low-quality AI building imports
woodpeck_repair (2026-06-11 09:10:52+00:00): This changeset has been reverted fully or in part by changeset 183960779 where the changeset comment is: revert low-quality AI building imports
woodpeck_repair (2026-06-11 09:00:26+00:00): This changeset has been reverted fully or in part by changesets 183960337, 183960380, 183960341, 183960408, 183960275, 183960389, 183960221, 183960319, 183960306, 183960280, 183960292, 183960414, 183960349, 183960228, 183960252, 183960358, 183960240, 183960299, 183960267, 183960399, 183960370, 183960328, 183960364 where the changeset comment is: revert low-quality AI building imports
woodpeck_repair (2026-06-11 09:12:35+00:00): This changeset has been reverted fully or in part by changeset 183960779 where the changeset comment is: revert low-quality AI building imports
woodpeck_repair (2026-06-11 09:13:02+00:00): This changeset has been reverted fully or in part by changeset 183960779 where the changeset comment is: revert low-quality AI building imports
World_Winner (2026-03-25 04:26:53+00:00): Reverted in changeset id: 180385450
woodpeck_repair (2026-06-11 08:58:50+00:00): This changeset has been reverted fully or in part by changesets 183960337, 183960380, 183960341, 183960408, 183960275, 183960389, 183960221, 183960319, 183960306, 183960280, 183960292, 183960414, 183960349, 183960228, 183960252, 183960358, 183960240, 183960299, 183960267, 183960399, 183960370, 183960328, 183960364 where the changeset comment is: revert low-quality AI building imports
woodpeck_repair (2026-06-11 09:06:42+00:00): This changeset has been reverted fully or in part by changeset 183960779 where the changeset comment is: revert low-quality AI building imports
NeisBot (2026-03-23 04:30: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 15 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/564231657 v2 | 11 crossings
https://osm.org/way/564231630 v5 | 4 crossings

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

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=180280860
iandees (2026-03-23 08:05:57+00:00): Hello! I noticed that nodes https://www.openstreetmap.org/node/1804225965, https://www.openstreetmap.org/node/5436840994 were 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/180289930, 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!
World_Winner (2026-03-24 06:29:39+00:00): Partially reverted in changeset id: 180336762
pitscheplatsch (2026-03-24 06:36:34+00:00): @World_Winner Thanks for fixing the mentioned issue and for commenting here.

Would it be possible to add a direct link to the changeset instead of only the raw changeset ID? Something like https://www.openstreetmap.org/changeset/180336762 would be very helpful.

Thanks!
okadatsuneo (2026-03-23 04:47:20+00:00): 53360587の間違い
okadatsuneo (2026-03-23 04:47:38+00:00): 53360587の間違い
Flap Slimy Outward (2026-03-23 05:19:06+00:00): Sorry, the URL for source=* should have been https://www.tollbrothers.com/luxury-homes-for-sale/Nevada/Reflection-Ridge#siteplan.