piebro/osm-data huggingface dataset:
Frans S (2026-06-28 10:10:32+00:00): Hello. Thanks for mapping.
Please try to map more precisely by following the rooflines and adjust the position of hi rise buildings to their footprint,
Check this webpage with my modifications.
And, perhaps as a reminder
How to map high and high-rise buidings
https://youtu.be/u31wPYWkm3E?si=lDbvDutpUyZWQXXL

Best regards
Frans S (2026-06-28 10:11:19+00:00): Forgot to add
https://overpass-api.de/achavi/?changeset=184735287
Best regards
Andrea Musuruane (2026-07-10 07:58:17+00:00): Questa parafarmacia è chiusa da anni. Per favore, non inserire dati senza verificarli. Grazie.
Silviopen (2026-07-13 13:22:15+00:00): Non potendo verificare di persona mi sono fidato del file CSV del ministero (e dal portale cerca prarafarmacie) in cui risulta attiva dal 1/2/21 in via G. Ferraris 11/d e non ancora chiusa
Andrea Musuruane (2026-07-13 16:29:50+00:00): Quel file ha diversi errori
DaveF (2026-06-29 12:23:20+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:23:13+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:23:07+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:23:01+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:22:45+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:22:52+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:22:35+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:22:40+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:22:28+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:22:13+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:22:08+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:22:02+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:21:58+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 15:50:38+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:21:47+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:21:53+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:21:42+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:21:37+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:21:32+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:21:20+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
DaveF (2026-06-29 12:21:00+00:00): Do not create multiple changesets of just one edit of similar entities. It makes it much more difficult to validate.
eggie (2026-06-28 15:55:20+00:00): Alle begin is moeilijk. Ik heb je rest area verwijderd. Dat wordt in een andere context gebruikt langs wegen.
Pitch was al gemapt. Dus de node verwijderd. Het is anders dubbel.
Die parkeervakken zijn geen parkeerterreinen. We tagging die met parking=street_side. De noodzijde ook aangepast als voorbeeld.
Mapse,
eggie
CAM-Gerlach_Repair (2026-07-02 07:38:22+00:00): Reverted SEO spammer changing valid tags to nonsense ones

https://osm.org/changeset/184959169
Toby Broom (2026-06-28 10:12:46+00:00): http://relevancy.bger.ch/php/aza/http/index.php?highlight_docid=aza%3A%2F%2F21-02-2025-1C_390-2024&lang=en&type=show_document
Canard164 (2026-06-28 11:38:41+00:00): Hello,

I think your previous value for the website, which was going to the main page of the website, was correct.
In this last update, you changed it for the reservations web page. There are other attributes to store that information as explained in this wiki page: https://wiki.openstreetmap.org/wiki/Key%3Awebsite%3Areservation

I would put back the main page in the website attribute, and put the reservations page in one of the reservations attribute.

In any case, thank you for your updates.
Naelfnir (2026-06-28 13:19:03+00:00): Hello,

Thank you for your vigilance. I'm new to this, so excuse my errors.

I've added informations by the way, hope i did it well. But I didn't find the reservation field as suggested in the docs you specified.
Canard164 (2026-06-28 13:47:45+00:00): I just added the reservation website (in French version, but one can change the language once there).

To do this, I logged on in osm.org, then selected the restaurant to display the existing attributes. At the bottom, you can add specific attributes by unfolding the ones already completed. You have to enter the exact name of the attribute. I chose "website:booking", then on the right enter the value.
Then send the update.

You do not need to do it for this restaurant as I did it already; the explanation is just in case you find it useful for another restaurant.

You will not see this modification in the CoMaps app, as it does not display this value. But it is nonetheless in the OpenStreetMap database, as displayed on osm.org

Thank you again for contributing to OpenStreetMap. I hope you will enjoy it!

Have a nice day,
Naelfnir (2026-06-28 13:56:54+00:00): Thanks a lot for these explanations ! I'll be ready next time :). I'll prefer modification from osm.org website further then.

May I ask you how you saw I modified this restaurant metadata ? Did you kind of subscribe to informations about modifications in defined area ?

Wish you a great sunday in return !
Canard164 (2026-06-28 14:10:51+00:00): CoMaps is nice to make quick updates when you already are in the app, but it is a navigation app, and I do not think their goal is to become a full-featured OpenStreetMap editor. So yes for CoMaps for simple things. For more complete contributions, you have the osm.org website. You can also download the Vespucci app on your phone, which is complete but difficult to use; it is not really beginner-friendly. There is also StreetComplete, which is beginner-friendly, to complete small quests.
And the wiki to know which attribute to use. In case you are lost, ask on the international forum https://community.openstreetmap.org/ or the French forum https://forum.openstreetmap.fr/

(Or ask me but you will probably wait less on the forums!).

For your other question, yes, I use the WhoDidIt tool to have notifications of updates around my place, to see what is happening: https://simon04.dev.openstreetmap.org/whodidit/
It generates an RSS feed that I integrated with all my other news feeds.
user_5359 (2026-06-30 13:47:13+00:00): Hello! Please have a look on https://overpass-turbo.eu/s/2sv6. What is the mean of the tag NATUR_DESC = Trottoir?
Arflha (2026-07-01 08:16:10+00:00): https://www.openstreetmap.org/changeset/184390244
PL 2188677 (2026-06-28 14:31:18+00:00): “Natural Space Misclassification: He repeatedly labeled an area as an “edification area,” despite the city council geographer officially classifying it as a natural space (PDM oficial document 2024).“ There is no farmyard, there are buildings and the space around them is a natural space, protected. No more buildings can be built there. So this is not correct, again.
danieldegroot2 (2026-06-28 13:57:48+00:00): This looks incorrect. Could you take a look at this, please?

Neither are road/multi-use crossings on Panoramax 2025. Perhaps you were thinking of service way to the north.
https://www.openstreetmap.org/node/11236658811/history

Did they change the kerb at Patrick's Court from raised to lowered/flush to allow ie. bicycles? I assume they have not, as there is pedestrian crossing nearby.

Made this more explicit in
https://osmcha.org/changesets/184743239
(adding in-editor note here prevents it from being mapped incorrectly again in the future. I won't do this on ie. connection to building entrance of course.)

The other is T-junction between pedestrian road crossing and sidewalk. Footway continuing west/left goes to likely private steps.

As such, I would suggest reverting this changeset.
b-unicycling (2026-06-29 00:00:26+00:00): I was trying out the wheelchair navigation on openrouteservice and it sends wheelchairs coming from Ormond Rd over the marked crossing on Patrick Street, then across the road at the traffic lights again. I haven't figured out why it does that, but I thought there might be missing crossings on this side of the street.
danieldegroot2 (2026-06-29 09:59:43+00:00): If you put it in front of AIB north of signalled crossing it will go around as you said.

However, if you put it instead on footway south of Caffe 500 it will route over crossing on Ormonde Street.

In left sidebar, scroll down to Alternative routes
Set number of routes to 3
Set share factor to maximum
(It shares most of its length with the route you mentioned)
Keep weight factor at >1
(It is 'longer' somehow, perhaps spending more time at unmarked crossing or in side-street)

Now it will be shown as alternative route.

Maybe it prefers routing along main street (penalizes side-street) / prefers signalled crossings vs marked ones, ignores this crossing which is now too far along path /...

Regardless, adding non-existing crossings or other to increase 'accessibility' of route would be mapping for the router.

Reverted this changeset fully in
https://www.openstreetmap.org/changeset/184784765

Regards,

Daniel
MrLocalFixer (2026-06-28 16:27:51+00:00): I think you should add the whole collage campus as a collage grounds too.
contrapunctus (2026-06-28 21:12:56+00:00): That's what I tried to do at first, but then I realized it's really two colleges in one campus and I don't know their exact boundaries 😅

(Also, changes in Mumbai and other places got mixed up here. Sorry.)
MrLocalFixer (2026-06-29 15:48:08+00:00): Yeah, that happens too, but made sure to not repeat that mistake in future :),
I also mistakenly pushed changes from 2 different countries and got bombarded with the osm community notes and rules lol.
Tatfahren (2026-06-28 11:58:50+00:00): Quelle falsch, statt Bing: "Mecklenburg-Vorpommern DOP20"
CAM-Gerlach_Repair (2026-06-28 13:12:05+00:00): Reverted adding SEO spam POI with blatant advertising, malformed tags and possible Google Maps source

https://www.openstreetmap.org/changeset/184741865
Halfix (2026-06-29 07:58:25+00:00): Hallo Konsti, ich sehe, dass das dein erster OSM-Change war, also erst einmal herzlich willkommen im Kreis der Mapper. Aber nachdem die Meister auch hier nicht vom Himmel fallen, hast du ein paar Anfängerfehler gemacht. Eigentlich reicht mein Beobachtungsgebiet nicht bis Michelau, ich interessiere mich für den südlichen Steigerwald (weil ich da aufgewachsen bin), aber dein Change hat weitreichende Wirkung, weil du deinen Trail am unteren Ende an die Grenzlinie des Landschaftsschutzgebietes "Steigerwald" angeschlossen hast und nicht, wie vermutlich beabsichtigt, an den Flurweg am Waldrand. Da die "Grenze des Steigerwald" verändert wurde, reicht dein Change bis zu mir an den Schwanberg, weswegen ich ihn überhaupt gesehen habe. Es gibt im iD-Editor die Möglichkeit bestimmte Objekttypen (z.B. Grenzen) auszublenden, dann läuft man auch nicht Gefahr sie versehentlich zu verändern. Grenzen habe ich selbst immer ausgeblendet. Wegbreiten "width" werden per Default in Meter angegeben, d.h. die Werte, die man dort einträgt, sind immer nur Zahlen ohne Maßeinheit. Gebrochene Zahlen (wenn nötig) mit Punkt statt Komma, da müssen wir uns an die Angelsachsen anpassen. Also "width=1 m" ist syntaktisch falsch, es muss "width=1" sein. Wenn er noch schmäler wäre, dann z.B. "width=0.5". Ein besonders heikles Kapitel ist der "access", mit dem sich auch fortgeschrittene Mapper oft noch schwertun. "access" ist per Definition dazu gedacht rechtliche Einschränkungen zu dokumentieren, es hat nicht die Aufgabe die "Eignung" eines Weges für eine bestimmte Fortbewegungsart zu beschreiben. Wenn man also "access=no" für irgendwas setzt, dann sollte dort am Weg normalerweise ein Schild stehen, das dieses Verbot ausspricht oder es sollte eine regionale administrative Anordnung geben, die bestimmte generelle Verbote für eine Zone vorsieht. Darüber hinaus sollte man sich bei "access" auch an das Default-Prinzip halten, d.h. wenn du ein generelles "access=no" setzt, dann gilt das als Default für alle Fortbewegungsarten, wenn nicht für eine bestimmte Fortbewegungsart explizit anders angegeben. Also "access=no" und dann noch einmal explizit "foot=no" und "horse=no" macht keinen Sinn. Ein generelles "access=no" impliziert bereits "foot=no" und "horse=no" und man sollte das dann nicht explizit doppelt moppeln.
Schöne Grüße, Gerhard (Halfix) aus Erlangen.
woodpeck (2026-06-28 18:04:31+00:00): Dear kazuzu, you are adding a large number of buildings. Please state the source for these additions. If you have personally surveyed these buildings, simply put "source=survey". If you are using a third-party data source, specificy that source. Since you are adding the number of levels to each building, it does not seem likely that you are just adding them from imagery?
nyampire (2026-07-01 12:30:53+00:00): こんにちは、OSM Foundation Japanのいいだ（nyampire）と申します。

OSMありがとうございます、OSMへようこそ、、、

と言いたいところですが、あなたの行っている編集はいったんすべてリバート（巻き戻し）させていただきます。
理由は以下のとおりです。

* 編集に利用しているデータが、基盤地図情報の可能性が極めて高い。基盤地図情報のデータインポートは、ライセンスの競合により、許可されていません。
* 事前に相談されていないインポートである。OSMはインポートなどの大規模編集を行う際、Import Guidelineに従った手続きを事前に行う必要があります。
* 事前に相談されていない組織的編集である。金沢周辺を対象に、いくつかのアカウントがほぼ同じ活動をしています。組織として作業を行う場合、組織的編集のガイドラインに従う必要があります。

その他、投入されたデータは、既に描かれた建物と重複して登録されているなど、データ品質の面からも看過できない状況となっています。

また、別のアカウントからコメントをいただき、大学の研究でデータを利用したい、ということを伺いました。
それであれば、代替となるデータセットの紹介や、別アプローチでのアクションなども相談させていただきます。
nyampire@gmail.com までメールをいただけるよう、お手数ではありますが、指導教官あるいはリーダーに状況のエスカレーションを行ってください。
必要に応じてWeb会議などもセット可能です。
user_8655426 (2026-07-05 07:58:56+00:00): All changesets by user:kazuzu have been reverted.  (undiscussed import)
BCNorwich (2026-06-30 05:30:49+00:00): Way: Pakridyal - Sahasralingam Rd (1533018850) removed as it duplicates the line of an existing highway. Thus it could have caused disruption to routing.
nileshbarawkar (2026-06-30 10:51:55+00:00): Hi,

Could you please let us know the basis on which you changed the highway classification from trunk to unclassified? This road is NH 227F, and as per OSM highway classification guidelines, National Highways should be mapped as trunk roads.

Kindly refer to the OSM highway classification guidelines before making such edits to ensure consistency and accuracy.

Thank you.
BCNorwich (2026-06-30 12:26:40+00:00): Hi, Could you please read my comment above? You will see that you mapped a new highway on top of an existing highway; this could lead to disruption of routing on maps derived from OSM data. OSM highway classification guidelines do not allow for highways to be mapped on top of each other on the same layer.

You should not map any features on top of existing features. Rather if a feature, including a highway, needs amending/correcting, the amendment/correction should, if possible, be done to the existing feature, thus the feature's history is maintained in the OSM database. If this method cannot be done, then as an alternative method, the existing feature should be removed and the new feature mapped.

I have reverted or removed several highways that you have duplicated in this manner. There are 3 or 4 more highways you've duplicated that I've not yet sorted out.

Regards Bernard.
BCNorwich (2026-06-30 12:27:45+00:00): I've made comments about duplicated highways on 3 or 4 other changesets of yours.
BCNorwich (2026-07-02 05:54:06+00:00): I've now removed all the duplications that are/were on Geofabrik OSM Inspector Routing layer. I've also removed some route relations for those highways that have only one item.

There may be some sections of the existing highway where the status has been altered. I don't know those original statuses so they need to be checked.

Regards Bernard
PS they are now adding railway stations on lines that have yet to be constructed.
DD1GJ (2026-06-29 12:50:19+00:00): Revert.

Hallo coelac, danke für Dein Engament bei den Stolpersteinen. OSM ist keine Karte, sondern eine Geodatenbank. Wir tragen die einzelnen Objekte grundsätzlich an den Positionen ein, wo sie sich in der Realität befinden. Der jeweilige Kartenersteller entscheidet, was er ein welcher Form und Reihenfolge bei Platzmangel darstellt. So werden manknchel vorhandenen Dinge bzw. deren Beschriftung nicht angezeigt. Deshalb gibt es auch eine spezielle Stolpersteinkarte:

https://www.historic.place/themes/stolpersteine/index.html?zoom=18&lat=50.35379&lon=7.59463&layers=B0TT

Daher habe ich Deine Änderungen rückgängig gemacht und noch Adresse und Wikimedia Commons ergänzt. Melde Dich bitte bei weiteren Fragen oder Unklarheiten.

Viele Grüße, Joachim
Frans S (2026-06-28 12:52:43+00:00): Hello. Thanks for mapping.
Please map courtyards inside a building as well. Make a polygon from those mappings.
Check the lessons how to do that,
In short.  Select both mappings and press the Ctr+B button.
Best regards
BCNorwich (2026-06-29 06:01:34+00:00): Hi, Welcome to OpenStreetMap.

You are adding lots of duplicated highways which causes disruption to routing. You have warnings about crossing highways (see above), this also disrupts routing.

If a highway needs correcting, please make the correction to the existing highway; don't just map a new highway on top.

I'm removing some of the duplications that I can see.

Regards Bernard.
BCNorwich (2026-06-29 06:03:08+00:00): Your route relations are not needed, the tags can be added to the highway.
kre777 (2026-07-02 15:13:29+00:00): Hallo Piene
Die Einträge der St.2105 Straße way/212765585 & way/536092723 waren vor deiner Änderung zu cycleway_left:separate absolut OK und auch Korrekt.
Cycleway:no und cycleway:seperat sagen einem Routingprogramm exakt des gleiche. >Kein Radweg auf oder direkt an der Straße also der Highway_secondary_Linie< Als eigene Linie eingetragene Wege/Pfade sind sowiso klar erkennbar. Deshalb ist es auch NICHT angebracht diese und andere Straßen (wegen "zeitweisen Fahrradwegen") zu zerstückeln. Bedenke: Zukünftiges Mapping wird sehr kompliziert, wenn die Straße in duzende Stücke zerlegt ist. Nochmal zum besseren Verständnis: Die Linie way/212765585 (=Landstraße) hat keinen lane oder track integriert. Somit war und ist Cycleway:no in Ordnung. Dein Eintrag ist auch anderen aufgefallen. www.openstreetmap.org/note/5367117
Grüße kre777
Sanniu (2026-07-09 13:22:05+00:00): Hi, the street name is המלך אסא - ether fix address or rename street, so Nominatim can find the all other languages
Joseph R P (2026-06-29 19:35:21+00:00): Please do not change such short sections of controlled-access highways to motorways. Per the OSM Wiki:

"Roads which are disconnected from the motorway network, but briefly exhibit motorway-like characteristics for short distances (also known as "motorway islands"), should not be tagged as a motorway. In general, a disconnected motorway should have multiple grade-separated, controlled access interchanges over a significant distance, generally at least 2-10 miles, in order to be tagged as an isolated highway=motorway."
CAM-Gerlach_Repair (2026-06-29 17:32:17+00:00): Reverted adding SEO spam POI with blatant advertising and malformed tags, likely sourced from Google Maps, in changeset 184808917

https://osm.org/changeset/184808917
gotitim (2026-06-29 07:05:16+00:00): Hej, budynek który edytowałeś był oznaczony jako gospodarczy, nie nieokreślony, więc upewnij się że zmieniasz to co chcesz. Na przyszłość, zmieniaj proszę tagi na już istniejącym obiekcie (https://wiki.openstreetmap.org/wiki/Pl:Dobre_praktyki) zamiast usuwać i dodawać nowy.

PS możesz nie chcieć robić tego typu pojedynczych edycji bo się trochę doxujesz
relaxxxxx (2026-06-28 13:21:06+00:00): la rue lenoir est maintenant à sens unique sur une seule voie
Flynn Marquardt (2026-06-28 13:36:52+00:00): Correction:

Split way to fix border https://www.openstreetmap.org/relation/10371557
eggie (2026-06-28 15:25:47+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privebericht.
MVG,
Eggie
Namens de OSM Community
pitscheplatsch (2026-06-28 15:00:23+00:00): Hi, thanks for updating the information. I noticed that the name tag seems to describe the feature rather than being its actual name. Furthermore your added website is ... well, interesting?!
eggie (2026-06-28 15:39:32+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privebericht.
Feedback .. Wanneer er niets meer van het sporr te zien is dan kun je razed gebruiken ipv disused.
Maar het is de vraag of deze  historische lijnen nog op de kaart behoren te komen.
Er is nog een aparte historische railwaykaart op basis van OSM
MVG,
Eggie
Namens de OSM Community
woodpeck (2026-07-08 15:44:57+00:00): Dear etgg, you have in the past admitted to illegally using OS Mastermap as a source for your OSM contributions. Any contributions copied from OS Mastermap must be removed from OSM, and if OSM were to be found to be a vehicle for copyright violations it would seriously undermine OSM's standing in the UK. 

In this changeset, and quite a few others during the last year, you have added information without specifying a source, and this information just so happened to be the same as on OS Mastermap. In order to pre-empt any doubts that people might have, please make it a habit to properly specify your data source when uploading anything it OSM. If your data source is "survey", then be prepared to answer the occasional question about particular data items (for example: how did you determine the locality name "Kiln Dub" added in this changeset); ideally, retain any photos or notes that you have created while surveying so that if someone comes knocking, we can prove that this is indeed a bona fide survey. 

If members of the community ask you about the source of something, please don't take that as harassment; they will want to make sure that OSM can prove wrong any accusations of copyright violation. Please answer such questions patiently and truthfully.

I trust that the data you have contributed is indeed from surveys, and the amount of work that must have gone into these surveys is commendable! In the unlikely case, however, that you should repeatedly be unable to supply evidence that something was indeed personally surveyed (or copied from a legal source), then unfortunately OSM would have to assume the worst, namely that the data you contributed wasn't surveyed at all, and would have to delete all your contributions to inoculate us against copyright violation claims.