piebro/osm-data huggingface dataset:
vasagavavv (2026-03-24 14:54:06+00:00): Для хорошего тона и понимания внесенных изменений коллегами необходимо оставлять правильные комментарии, ссылку на примеры и статью с вики прикладываю:

https://wiki.openstreetmap.org/wiki/RU:Хороший_стиль#Оставляйте_информативные_комментарии_к_вашим_правкам
impiaaa (2026-03-24 17:53:46+00:00): Welcome to OpenStreetMap! Please use the changeset description during upload to describe what you changed and why—for example, "Aligned taxiway to aerial imagery." You can read more guidance and examples here: https://wiki.openstreetmap.org/wiki/Good_changeset_comments
rarad74 (2026-03-24 10:05:37+00:00): Hi, Maybe you can add some housenumbers too.
Have a good day!
Taya_S (2026-03-24 09:15:08+00:00): OpenStreetMap is a map that records the world as it currently is. Please stop attempting to add this proposed railway tunnel thing as if it actually exits.

Looking it up they're not even out of the proposal phase yet, not by a long shot.Before anyone actually starts digging into the ground, this project has no place on OpenStreetMap.

Creating more sockpuppets simply to put this piece of fiction on the map will not be tolerated. These accounts will simply be blocked and their edits promptly reverted.

Best regards,  
Taya Snijder,  
On behalf of the OSMF Data Working Group
pwbriggs (2026-03-25 19:02:02+00:00): I think destination=* is the right tag for this; roads generally shouldn't be tagged with names unless there's a sign alongside the road reading "NB Off-Ramp to Clark Rd"-- rather, these roads are described by the destination roads they link to.

I did some more work on this area, let me know how it looks.
MappingMore (2026-03-25 12:59:18+00:00): Reverted in changeset id:180406516
mueschel (2026-03-24 10:48:45+00:00): Something went wrong here - all these objects don't have any valid tag.
MapmakerrrJohn (2026-03-24 13:12:30+00:00): It exists still, I've been to this Whole Foods market for like a million times.
brendan77 (2026-03-24 19:23:20+00:00): This changeset confirmed that this place exists.
World_Winner (2026-03-25 04:33:43+00:00): Partially reverted in changeset id: 180340501
rajdhani (2026-03-25 07:54:05+00:00): Partially reverted in changeset id:180392391
AlexTopoRO (2026-03-24 06:16:05+00:00): Sal, vezi ca nu ai facut ceva bine, toate pct de inflexiune sunt point in loc de. punct de inflexiune a poligoanelor XD. poate era prea tarziu in miezu noptii nu e graba de corectat, e bine sa fim odihniti!
b-jazz (2026-03-25 17:10:32+00:00): Thanks for working on improving golf courses. Please make sure you aren't drawing greens and fairways in a way that they cross over each other like you did near one of the bunkers on the 17th hole. This sets of Q/A tools and requires others to come in and clean up your work. Thanks.
NeisBot (2026-03-24 01:27:49+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/4366854960 v2

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Werbeagentur"
---
Zum Beispiel könnte eine neutralere und faktischere Version deines Textes lauten: "Werbeagentur"
---
(Auto-translation)

#MapWithoutSpam
NeisRevert (2026-04-01 04:33:05+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/180700621
(Restore previous tags. No changes)
PizzaTreeIsland (2026-03-25 18:44:49+00:00): Hello Mchimwa, 
Thank you for adding all those details! 
Please use fewer name=* tags, they are only for actual names. For example, a restaurant gets tagged amenity=restaurant, not name=restaurant. The name=* tag is supposed to hold the actual name of the restaurant. If you don't know the name, just don't add a name tag, that's fine. Same with house numbers: Please use addr:housenumber=4 instead of name=4. 
For more information, see https://wiki.openstreetmap.org/wiki/Names#Names_are_not_for_descriptions. 

Thank you and happy mapping!
007Transformer (2026-03-25 06:16:57+00:00): Reverted in changeset id 180388099
蕉饼电脑 (2026-03-24 06:34:46+00:00): S201 is provincial highway
ajmat (2026-03-25 11:51:13+00:00): Partially reverted in changeset id: 180403434
nevw (2026-03-24 04:54:28+00:00): I think you added this to the wrong building. I shifted it to the one next door #430
yelisey90 (2026-03-24 09:02:50+00:00): reverted - tag "entrance" can have any needed value, "shop", "hotel" or in this case "kindergarten", to differentiate it from the main entrance to the apartment building

https://www.openstreetmap.org/changeset/180342115
opendcc (2026-03-24 10:32:06+00:00): Entrance describes the type of the entrance, not the kind of building nor the amenity. If you want to give some advice related to the entrance, you could tag ref or description. Why are you running a revert before any discussion?
yelisey90 (2026-03-24 10:42:07+00:00): "the type of the entrance" — precisely, and we need to distinguish between different kinds of entrances here. As can bee seen from https://taginfo.openstreetmap.org/keys/?key=entrance#values , there are widely used values "shop", "office" & "restaurant"; so yes, the differentiation is commonly used basing on the type of services. In this case it's a kindergarten in an apartment building; if you can suggest another, more generic value that would suit this case, it may do.

"Why are you running a revert before any discussion?" - likewise, I can ask why are you fixing something that isn't broken.
opendcc (2026-03-24 13:37:08+00:00): No, it is not the kind of service, it is the type of entrance. Service is described with the amenity tag. So a kindergarden can have a main entrance (if there are many entrances) or a separate service entrance. If you see entrance=kindergarden as useful new tagging, please make a suggestion to the mailing list.
yelisey90 (2026-03-24 19:59:23+00:00): "a kindergarden can have a main entrance (if there are many entrances) or a separate service entrance" — yup, if it's building=kindergarten. Here it's building=residential (apartments, de facto), with at least four entrances: one main, one secondary, one which I'm not sure about but my guess is that it's to a private apartment, and one to kindergarten. Some type should be assigned to it; if you have any other suggestions beside plain "yes", don't keep them to yourself.

And no, as long as we have entrance=shop etc., I see no reason to engage into any discussions about new values.
GrabTH_Bulakorn (2026-03-24 03:22:32+00:00): Also revert road class change of w26518912
NeisBot (2026-03-24 03: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 8 potential crossings.

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

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

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=180332856
TheSwavu (2026-03-24 03:48:15+00:00): Reverted in https://www.openstreetmap.org/changeset/180333160
ajmat (2026-03-25 08:15:54+00:00): Partially reverted in changeset id: 180393117
woodpeck_repair (2026-06-11 09:01:42+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:07:15+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:06:54+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 08:59:27+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:13:07+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
Glassman (2026-03-24 17:37:09+00:00): Thank you for your edit. I reviewed your work and it looks good.
            ---
            #REVIEWED_GOOD #OSMCHA
            Published using OSMCha: https://osmcha.org/changesets/180333324
TheNightRider (2026-03-24 09:51:32+00:00): We have a problem here because we have a way (Rove) tagged as a charging station that has a node inside also tagged as a charging station (Tesla Supercharger).
TheNightRider (2026-03-24 09:54:05+00:00): The Tesla Supercharger station is a separate station as given by https://www.tesla.com/findus/location/supercharger/4006656 . There are other chargers at Rove (12 CCS posts, 2 of which have a CHAdeMO plug).  Not sure yet who owns them (maybe EVgo) and if they have their own network.
weblogdryads (2026-03-24 14:03:25+00:00): I agree this is a very interesting conundrum. Rove is a unique situation and I thought “Charging Statiom” was more accurate than “Retail Area”. I will survey it and responf with more accurate details
TheNightRider (2026-03-24 16:23:34+00:00): Here's an example of how they map something like this in Norway. There are 3 different charging stations there, including a Tesla Supercharger.
https://www.openstreetmap.org/node/3002125370
Maybe what we do is enlarge the retail area to include Goodwill to the north (which might be a separate building). Rove occupies the smaller building next to the charging area. There will be at least 1 other charging station next to the Supercharger. Check this thread where we've been watching this place get built for not quite a year. I'm electrons4u on that forum and you can see plans and more:
https://teslamotorsclub.com/tmc/threads/supercharger-costa-mesa-ca-harbor-blvd-rove-charging-live-23-mar-2026-28-v4-stalls.345055/
TheNightRider (2026-03-24 16:29:13+00:00): What I meant to say is enlarge the retail area that currently only includes the Goodwill, and expand it to include Rove. Then this problem goes away. Rove has a Gelsen's c-store that's not yet been mapped. Also there are solar PV canopies that cover most of the 40 stalls. All good stuff to map.
TheNightRider (2026-03-24 16:32:35+00:00): Unfortunately, we don't have aerial imagery yet within OSM. Even Esri World Imagery only has the beginning of construction.
TheNightRider (2026-03-24 16:35:59+00:00): None of the major map sites have it: Gmaps, Apple Maps, or Bing Maps. Surprising about Apple because a friend who works for Vantor (formerly Maxar) told me last year the Apple was buying more of their satellite imagery than G - for Apple Maps.
weblogdryads (2026-03-25 15:26:30+00:00): I have added the roads, buildings, shops, wall, and solar via in person survey. Once Aerial imagery is avalible it will be easier to add more individual details. There was a lot of info on the forum you sent, but I didnt know if their license was compatible with OSM. Thank you for inspiring me to more detailed map this area. I had never done a pre-aerial survey before.
TheNightRider (2026-03-29 23:00:06+00:00): Looks good. Yes, we're lacking aerial imagery there at the new Rove Charging Center. It's an interesting situation regarding licensing. Starting with the teslamotorsclub.com forum, I and others will post info from city and county building permits, news reports, plugshare, wherever. We'll also take photos of charging stations at various stages of construction and post them there. Then, the supercharge.info team takes that and plops a pin (not a way or relation) in their database, which uses OSM as a basemap. supercharge.info gave permission to OSM to use its info, and on 2025-06-22 a bulk import from supercharge.info into OSM was done. It was half-baked and added a lot of bogus data to OSM including: 1) overwriting good lat/lon with wrong lat/lon 2) creating duplicate stations 3) making L2 Tesla Destination Chargers into Tesla Superchargers 4) adding some bogus info that didn't even come from supercharge.info. I was the first OSM user to flag this and the discussion didn't go well. Read the whole saga at:  https://community.openstreetmap.org/t/bulk-import-of-tesla-superchargers-in-the-united-states/131561
TheNightRider (2026-03-29 23:03:42+00:00): The DWG (Data Working Group) got involved and the bulk import author got upset and basically packed up all his toys and went home.
TheNightRider (2026-03-29 23:04:23+00:00): We are still cleaning up that mess and probably will be cleaning for another year.
TheNightRider (2026-03-29 23:17:05+00:00): supercharge.info has pretty good info overall, but there are gaps. The main problem has been lat/lon, and the reason that's mostly wrong is they add a location when they first find out about a new charging station. They can get away with that because they're not actually editing OSM; they're just using it as a basemap. They don't have a formal process in place to track it, so when a station gets built and it's at a different lat/lon, nobody checks to see until someone like me comes back later, takes the time to get the lat/lon correct for OSM, then flags the supercharge.info team, who then updates their lat/lon. So the bulk editor guy didn't know this, and he didn't even come to the place where most of this Supercharger activity happens. If he had, we would have told him, "Whatever you do, don't use the lat/lon from supercharge.info!"
TheNightRider (2026-03-29 23:32:20+00:00): BTW, I've been doing ground surveys around Denver, and it's amazing what you find out when you're on the ground. It's also amazing what you don't find out from aerial imagery, and you can often tell when people do "armchair mapping" as OSM puts it, because they get stuff wrong that would be obvious if you were on the ground.
kmpoppe (2026-06-21 15:07:06+00:00): DWG Ticket#2026061610000401
kmpoppe_repair (2026-06-23 05:16:38+00:00): This changeset has been reverted fully or in part by changeset 184458708 where the changeset comment is: DWG Ticket#2026061610000401, disputed information
woodpeck_repair (2026-06-11 09:00:10+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
Udarian (2026-03-24 15:01:41+00:00): The address listed in this changeset does not match the address of the building it is within, can you please double check the address. You have also put "Apt" in the hoursenumber, from my understanding that should be a number without any characters.

Happy mapping,
Udar.
Udarian (2026-03-24 19:00:33+00:00): Also is this trying to represent a Airbnb or Vrbo listing?

Happy mapping,
Udar
Udarian (2026-05-04 18:34:13+00:00): please respond
woodpeck_repair (2026-06-11 09:08:43+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 08:59:43+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:01:41+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:08:51+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:11:27+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 08:59:55+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
tux67 (2026-03-24 16:50:12+00:00): Hi, danke fürs detaillieren. Da ich meist zu faul bin, mappe ich den einen Poller, der als Datenpunkt fürs Routing hilft. Wenn aber eine Pollerreihe, hier vielleicht eine kleine gedankliche Inspiration nach diesem Schema zu mappen:  
https://wiki.openstreetmap.org/wiki/DE:Tag:barrier=bollard?uselang=de#Pollerreihen
Neben den mehr optischen Aspekten weiterter einzelner Poller Nodes auf der Karte ist - denke ich - für Rollstuhl, Kinderwagen, Lastenfahrrad (oder Anhänger) das https://wiki.openstreetmap.org/wiki/DE:Key:maxwidth:physical noch ein sinnvoller auswertbarer Datenpunkt für Programme, die Fahrzeugdimensionen beachten. Bei der guten Auflösung der DOPs an dieser Stelle kann man (zumindest bei JOSM) die Abstände ganz gut messen (hier ~2m) .. nur so als Idee ;-)
Gruß
tux67
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/180334197
LingM (2026-03-24 20:36:34+00:00): Pollerreihen sind mir bekannt. Die lösen aber das Problem weshalb ich hier überhaupt noch mal Hand angelegt habe nicht: Die drei unterschiedlichen Poller-Arten, die hier verbaut sind.

Zumindest mit dem dokumentierten Schema von bollard=* lässt sich das nicht abbilden.

Das maxwidth:physical nützlich ist, da stimme ich dir zu. Das wird bei Pollern aber eh auch von StreetComplete abgefragt. JOSM habe ich noch nie verwendet und in iD gibt es meines Wissens nach keine Messfunktion.
tux67 (2026-03-25 06:16:30+00:00): Naja, ohne einen Bezug zum way werden nur diejenigen die Früchte deiner Arbeit genießen können, die sich manuell die Poller und deren Werte auf der Karte ansehen. Aber so ist's ja wenigstens mehr  dokumentiert als vorher.
LingM (2026-03-25 06:59:16+00:00): Ja, perfekt ist es nicht, aber ein ganzes Proposal für bessere Poller-Reihen schreiben ist mir auch zu viel Arbeit.

In einem Fall wie diesem wäre für manche Nutzer (Umzugsfirma, Feuerwehr, ...) neben maxwidth:physical=* sicherlich auch von Interesse wie weit man die Öffnung maximal machen kann. Also wenn entfernbare Poller rausgenommen und Faltbare umgelegt sind. Ist mir auch kein passender Tag für bekannt.
woodpeck_repair (2026-06-11 08:58:33+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:11:16+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
SD Mapman (2026-03-26 17:22:17+00:00): Hello! We've been discussing memorial names and highway number-based names on the forum: https://community.openstreetmap.org/t/veterans-of-foreign-wars-of-the-united-states-memorial-highway-aka-i-83/141703
Baconcrisp (2026-06-16 20:42:20+00:00): What resource did you use to make these name changes? Did you consult with the local community before making these changes. From what I've most of your changes are incorrect and need to be reverted.

Please link the resource(s) you used and consult with the local community before making any changes on this scale.

Baconcrisp
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/180334382
Flap Slimy Outward (2026-06-16 21:37:16+00:00): According to Wikipedia, the official name of US 6 is "Grand Army of the Republic Highway." These edits have already been reverted.
Baconcrisp (2026-06-17 15:01:39+00:00): I appreciate the response. I checked this morning and none of your edits were reverted like you said. Thank you providing your source for the "Grand Army of the Republic" changes, but you neglected to share your source for the other changes you made in this changeset. I would like to see your source for ALL of your changes in this changeset if you please so I can verify each one. You modified multiple relations, deleted multi-polygons, changed POI tags, modified ref information, modified names, etc. These changes span from Utah to Colorado. Please share your sources for all of these changes.

You also never answered my question about whether or not you consulted with the local communities before making these changes so I'll ask again. Did you consult with these two communities before making these changes?

Baconcrisp
SD Mapman (2026-06-17 19:21:13+00:00): So for reference I manually reverted some of the changes in CO (mainly road name/ref edits). I did not do anything in Utah.
Flap Slimy Outward (2026-06-17 19:47:11+00:00): To answer the main question: No, I did not consult any community about this, since the name "Grand Army of the Republic Highway" applies to US 6 nationwide, rather than applying to a specific stretch of US 6.

I've made numerous miscellaneous edits in Utah, and that was right after I visited said area (so, the source is local knowledge and aerial imagery, namely Bing).
Baconcrisp (2026-06-17 21:58:20+00:00): I did see that you reverted some of Flaps changes SD Mapman. Thank you for that.

In regards to the "Grand Army of the Republic" name change. That is something that should've been discussed either on the OSM Forum or the OSM US Slack because its nationwide and affects multiple communities. I saw that you also incorrectly added "Dinosaur Diamond Scenic Byway" as the street name for parts of "US 6 & 50" as can be seen here: https://www.mapillary.com/app/?lat=39.11335200745302&lng=-108.64940846262999&z=17&focus=photo&dateFrom=2017-01-01&pKey=884343990641540&x=0.37189943923430735&y=0.5107448552082803&zoom=0. This is another name that belongs on the route relation. I saw that you changed the name of the "Grand Army of the Republic" route to "Dinosaur Diamond Scenic Byway" and SD reverted that change. Please stop adding these names to the highways without consulting the local communities. These names belong on the routes, not the main highway.

Visiting a place does not count as local knowledge. That's a survey. A local would be able to confirm their edits with mapillary or a government source that's usable in OSM. Since this changeset spans across two states its unlikely that this was part of a survey. For future edits please keep them smaller in both size and area so the data stays relevant to the place you are working.

Baconcrisp