piebro/osm-data huggingface dataset:
ItsAlyx (2026-02-23 22:32:38+00:00): please avoid such geographically large changesets unless absolutely necessary, 4 different changesets you made are spanning multiple continents
vogelfreier (2026-02-24 09:33:20+00:00): After logging into Osmose with our account, it is possible to correct our own errors as well as those caused by other users. In this case, I had over 100 errors, as there were only a few left that should no longer have noexit=yes on the way due to my entry from over 10 years ago. For the other errors, other users continued to draw the way or added a new way to the last node where the value noexit=yes (https://wiki.openstreetmap.org/wiki/Tag:noexit%3Dyes) was entered by me on the last node of the path.

I didn't want to deal with each case individually so as not to be tempted to improve things (which would have been wrong in the end), which in turn would have taken more time.

From the list, it was not clear to me, given the time I spent on my many edits, which continent I was currently working on.

(Not only the user's osm.org page shows how often they have contributed to osm, but https://hdyc.neis-one.org and https://yosmhm.neis-one.org also provide an overview of edits around the world.


Translated with deepl.com
OSM_RogerWilco (2026-02-25 07:48:20+00:00): I thought the same thing. Take a look at:
https://wiki.openstreetmap.org/wiki/Changeset#Geographical_size_of_changesets
jhuang97 (2026-02-27 18:37:02+00:00): This edit turned the entire city of Grand Island, Nebraska into a big building. I reverted this in 179144224.  Presumably you wanted to add a specific building for Nebraskaland Distributors?
旧加卷 (2026-02-24 01:53:34+00:00): 距离上次你对学校多边形关系的所有子元素路径添加 education= 值才过去了2个月，为何相同类型的重大编辑错误会反复出现在你的变更内容中？
aighes (2026-02-24 01:56:32+00:00): Was this automated edit somewhere discussed?
fluffycupcakes (2026-02-24 02:14:11+00:00): There has been a forum post created 3 hours ago for this:
https://community.openstreetmap.org/t/golf-features-tagged-incorrectly-according-to-the-wiki-and-obscure-tags/141786/1
impiaaa (2026-02-23 19:01:40+00:00): Hi, where was this automated edit discussed? https://wiki.openstreetmap.org/wiki/Automated_Edits_code_of_conduct
Hypsometric (2026-02-23 22:10:14+00:00): I took this as a blatant fix, where no discussion would be needed. The wiki says "Do not use sport=golf or leisure=pitch" on features of a golf course. I came across enough that it made more sense to edit in an automated way.

If you think this warrants discussion, let me know. There are other areas I have not fixed yet.
impiaaa (2026-02-23 23:38:35+00:00): Yes, as the page I linked says, "documentation of tagging on the Wiki is not the final arbiter of 'correct' tagging."
ChehrehBargi (2026-02-23 15:36:49+00:00): Branch naming conflicts with OSM tagging guidelines. Awaiting DWG review.
Glassman (2026-02-24 16:12:45+00:00): DWG here - can you show where on the wiki you documented this mass change?
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/178947319
Hypsometric (2026-02-25 00:13:04+00:00): Hi, Glassman. Sorry for the confusion here. Regretfully, I mistook this for a blatant error. So I did not discuss first. I am waiting to make further edits, including reverting it, until I can get some input on the forums. There are a few other edits related to golf=* that are mentioned there as well. Your input would be greatly appreciated.

https://community.openstreetmap.org/t/golf-features-tagged-incorrectly-according-to-the-wiki-and-obscure-tags/141786
Glassman (2026-02-25 03:00:27+00:00): I haven't made many golf course edit, which is ironic since I live next to the 14th hole of a defunct course. 
I did run a query which showed 24 edits likely involved. I can provide you a list if needed.

My suggestion is to quickly get your proposal document on the wiki, especially which tag you want to remove or change. Get that to the community and let's see what the consensus is. If there is major push back, then we may have to revert. I can help with that.
Hypsometric (2026-02-25 13:42:48+00:00): Thanks for the help so far. I'll post on the wiki.

Depending on feedback, I can pull my changesets and manually revert if needed. While there were other fixes (e.g. typos) I should be able to key in on the main focus of each changeset and make the needed revert.

I appreciate the offer of help and I will take you up on it if I need it. I already feel bad for my misunderstanding. So I'll try to minimize additional impact on others for now :-)

Thanks again. I'll post the link to the discussion in the wiki shortly.
Hypsometric (2026-02-25 14:30:08+00:00): Two new topics in the wiki discussion:

https://wiki.openstreetmap.org/wiki/Talk:Tag:leisure%3Dgolf_course#Automated_edits_to_remove_leisure=pitch_+_sport=golf
ChehrehBargi (2026-02-23 15:37:02+00:00): Branch naming conflicts with OSM tagging guidelines. Awaiting DWG review.
ChehrehBargi (2026-02-23 15:37:12+00:00): Branch naming conflicts with OSM tagging guidelines. Awaiting DWG review.
007Transformer (2026-02-24 09:14:05+00:00): Partially reverted in changeset id: 178977922
gurglypipe (2026-02-23 15:14:41+00:00): Hiya, thanks for your contribution to OpenStreetMap.

I’ve undone these changes as the ford was already correctly mapped here: it’s a public right of way, so needs to be mapped. The impassability of it was already tagged with various tags.

https://www.openstreetmap.org/changeset/178948274
qstep (2026-02-23 18:37:54+00:00): Üdv! Több hiba is van a szerkesztésedben:

- Erre a relációra ráraktál egy "Játszótér" nevet, valószínűleg véletlen: https://www.openstreetmap.org/relation/7335240 

- Présház utcai park → Présház utcai játszótér "Cseresznyés játszótér": Ki van ott írva ez a név? name mezőbe az kerül, ami ki van írva, vagy így hívja mindenki. loc_name-be ha a helyiek által használt név eltér a valódi névtől. alt_name-be az "egyéb név". Kérlek olvasd át a wikit: https://wiki.openstreetmap.org/wiki/Names

- https://www.openstreetmap.org/way/313825904 - nem szükséges a Játszótér név, ott van már a leisure=playground - kérlek olvasd át a https://wiki.openstreetmap.org/wiki/Tagging_for_the_renderer cikket.

- https://www.openstreetmap.org/way/378887241 - törölted a shop=convenience-t de nem állítottál be másikat, így csak a név szerepel. Válassz egyet: https://wiki.openstreetmap.org/wiki/Key:shop
mcliquid (2026-02-23 15:59:33+00:00): Grüß dich!
Wieso entfernst du hier das Vorrangschild?
https://www.openstreetmap.org/node/13593135344

Siehe zuvor: https://www.openstreetmap.org/node/9846799095
rene78 (2026-02-24 06:12:14+00:00): Ich habe mir erlaubt, es wieder einzutragen.(https://www.openstreetmap.org/changeset/178971940)
eggie (2026-02-23 16:25:13+00:00): Tot de rotonde Strandweg heb ik access=no verwijderd. Het traject iets aangepast mbv de BGT en laatste luchtfoto.

Gr eggie
eggie (2026-02-23 20:41:37+00:00): Dag cascer

Dit zijn de parkeervakken, maar de parkeerruimte amenity=parking ontbreek nog.
Als voorbeeld één vlak aangepast

MVG
eggie
cascer1 (2026-02-24 07:16:33+00:00): Hoi Eggie,

Bedankt voor de info. Ik had op de wiki gekeken: https://wiki.openstreetmap.org/wiki/Parking en vond het lastig om daar precies uit te halen hoe het gemapt moet worden.

Dus zodat ik het goed begrijp, klopt het volgende:

1. Altijd een amenity=parking area mappen
2. Eventueel nog losse amenity=parking_space toevoegen per parkeerplek

Verder had ik nog een relation gemaakt met daarin de parking spaces met role parking_space en de aisle de role parking_aisle. 

Moet ik de nieuwe amenity=parking ook nog aan deze relatie toevoegen?
eggie (2026-02-24 07:23:13+00:00): Een groepje parking_space had ik voorzien van vlak parking.
Die andere zou je ook kunnen doen. Een relatie is niet nodig.
Mapse
eggie (2026-02-24 07:25:20+00:00): De wiki..
https://wiki.openstreetmap.org/wiki/Tag:parking%3Dstreet_side
eggie (2026-02-24 07:29:00+00:00): De vakken geven alleen een toegevoegde waarde.. bv voor gehandicapten of een laadpaal.
Een street_side geeft een kleine P. Voor woonstraten.
Alleen amenity=parking (terrein) een grote P.
cascer1 (2026-02-24 07:45:01+00:00): Dus wat zou ik beter kunnen doen? De "normal" parking spaces verwijderen en dan alleen de amenity=parking laten staan? En dan op de amenity=parking waar de accessible spaces in zitten een capacity van 10?
eggie (2026-02-24 07:50:08+00:00): Nou.. die parking_space vakken kun je gewoon laten staan.
Zelf neem ik niet zo  de moeite om die parkeervakjes er in te tekenen, maar het kan natuurlijk wel. Dan zie je op de standaardkaart ook de vakken in het geheel.
De hoofdtag is natuurlijk amenity=parking. Dat levert de P op en de grijze rendering. 
Wie een parkeerplaats zoekt in app of gps vindt dan ook werkelijk een parkeerterrein of strook. 
De capacity kan op het vlak amenity=parking
eggie (2026-02-24 07:51:51+00:00): Even CTRL-F5 hier om de rendering te verversen. Dan zie je het verschil.
eggie (2026-02-24 07:53:49+00:00): Hier een voorbeeld van micromapping, waar iemand de moeite heeft genomen ook nog alle vakken in te tekenen..
https://www.openstreetmap.org/#map=18/51.882394/4.490506
qstep (2026-02-23 18:29:31+00:00): Üdv az OpenStreetMap-en! Ezt a telefont beletetted egy épületbe: https://www.openstreetmap.org/node/13593163702

Kérlek töröld, vagy mozdítsd a helyére!

További jó térképezést!
Yesofcourse (2026-02-24 14:40:10+00:00): Az épület alatt ott valójában egy út megy el, bent az épület alatt található a telefon.
Szymson (2026-02-23 17:47:43+00:00): W jakim celu został wykonany duplikat adresu Klifowa 1A na wjeździe do parkingu podziemnego?
dypa (2026-03-22 18:43:34+00:00): Пожалуйста используйте для диких кустарников тег natural=scrub, тег natural=shrubbery используется для декоративных кустарников
osmmapper222 (2026-02-23 19:32:25+00:00): Hallo Schottjer,

in OSM empfiehlt es sich, abgerisse Gebäude mit dem Präfix demolished: zu taggen (hier dann demolished:building=yes).

Andernfalls kann es passieren, dass ein anderer Mapper auf Basis nicht tagesaktueller Luftbilder das Gebäude wieder einträgt.

Mit der Löschung ist auch die Adresse des Gebäudes entfernt worden, obwohl diese für das Grundstück / Flurstück noch fortbesteht.

Die Adresse habe ich wiederhergestellt.

Viel Spaß beim weiteren Kartieren wünscht
osmmapper222
蕉饼电脑 (2026-02-24 01:22:23+00:00): w/1442293878 与 w/1442293879 是2025年12月完成沥青路面铺装的 地面 道路，且有围挡阻止社会车辆驶入。你是如何认定此段道路为已开放的 下穿隧道 的？
totera (2026-02-24 08:10:59+00:00): Ciao soflor, come puoi verificare da tutte le fonti (https://www.comuneancona.it/wp-content/uploads/2019/11/AllegatoA-Stradario-UfficialeA-GGIORNATO-01.10.2020.pdf, https://www.comuneancona.it/cartografia/VIARIO.xls, https://sit.comune.ancona.it/portal/home/, https://anncsu.open.agenziaentrate.gov.it/age-inspire/opendata/anncsu/getds.php?STRAD_MARC) il nome corretto è proprio "Via Montagnola".  
"Via della Montagnola" era indicato come nome alternativo con il tag alt_name
rhhs (2026-02-23 16:58:47+00:00): Like so many times before, you made a complete mess out of your edits and I'm getting so sick of repairing the damage that I'm considering to ask for a ban of your account.
- You added a new shop node at almost exactly the location of an already existing shop (a watchmaker). If the new shop replaces the old one, please update the tags of the existing shop node instead of creating a new one.
- you added address tags while the node is inside a building that already has address tags. Please don't add address tags unless the address is different from that of the building, and if so, use the spelling of the nearby street in Cyrillic. There is usually no need to add anything but the street name and house number because software can determine the rest.
- Please check the format of the opening hours here https://wiki.openstreetmap.org/wiki/Key:opening_hours You failed to include a ; to separate the day ranges
- this time you got the phone number format right! It should always start with +359 for Bulgaria
seopinnacleagency (2026-02-24 10:33:54+00:00): Sorry about the issue, the two businesses are door to door.
rhhs (2026-02-24 12:42:34+00:00): So which business did the pastry shop replace? In that building there are 4 shop spaces, until recently occupied by Pavillion24, a shoemaker, a watchmaker, and a fireplace shop. In the next building is Promarket supermarket. Where is the new pastry shop?
seopinnacleagency (2026-02-26 07:39:46+00:00): The one that is next to the watchmaker - right to him (https://prnt.sc/d9y5C6mR3y84), it is between the watchmaker and the supermarket, but the enterence is closer to the watchmaker.
seopinnacleagency (2026-02-26 07:41:10+00:00): So it is ArtPro, will fix it. Sorry again!
Glassman (2026-02-24 17:15:48+00:00): #TIP: Descriptive name like name=Residence are not used. Tags can do the trick. I removed the name tag
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/178950256
qstep (2026-02-23 18:27:06+00:00): Üdv az OpenStreetMap-en. Javítottam a hibákat: https://www.openstreetmap.org/changeset/178956397
markalex- (2026-02-23 18:56:06+00:00): Why are you creating all these relations?
Tag description for `route=road` says that "Most urban streets and minor roads which are identified only by a `name=*` tag do not belong to a relation.": https://wiki.openstreetmap.org/wiki/Tag:route%3Droad
Olgerts V (2026-02-23 20:39:20+00:00): These relations are creating to illustrate the location of streets on a city map in Wikipedia, such as https://lv.wikipedia.org/wiki/Dzimtenes_iela
In this sense, each street is to be shown along its entire length according to the cadastral map, including pedestrian and planned parts.
If some tags are used by me incorrectly, please show me the right way.
markalex- (2026-02-24 00:08:51+00:00): So, as I understand, you are trying to work around the limitation of wikipedia's map plugin by creating relations in OSM. This is a wrong path.
Please create route=road only where it is really necessary.

And if you still really want to have full outline of the street, you might go GeoJSON route. Extraction of GeoJSON for embedding in wikipedia can be done with tools like https://overpass-turbo.eu
markalex- (2026-03-01 20:30:38+00:00): After discussion in OSM's chat, and since your approach seems to be the best what is currently possible with existing tooling, I would like to retract my request of you stopping: please proceed with creation of route=road at will.

Link to the discussion for reference: https://osmlatvija.zulipchat.com/#narrow/channel/358602-general/topic/Road.20routes/
joost schouppe (2026-04-26 07:36:14+00:00): That's a sea gate you added :)
I turned it into a normal gate
b-holdet (2026-02-25 06:56:43+00:00): Hvor har du navnet på den ekstra vej fra?
Google er ikke et sted vi må benytte pga. deres licens. Og desuden er det ikke mere nøjagtigt end andre kort.

Så et billede af vejskiltet på vejen vil være mere sigende.

Ifølge DAR, så ender Slagtehusgade ved Staldgade, som også var tegnet på kortet

https://kortoverblik.dk/spatialmap?mapheight=1351&mapwidth=1847&label=&ignorefavorite=true&profile=sdfikort&selectorgroups=gst_dhym+matrikelkort+adresser&layers=theme-dtk_skaermkort_daempet_daf+theme-daf_matrikelkort_roed+theme_forvaltning2_vejnavne_basiskort_gst_custom+userpoint+userline+userpolygon+selectorpoint+selectorline+selectorpolygon+selectorbufferzone&opacities=1+1+1+1+1+1+1+1+1+1&mapext=723807.6679849753+6174844.602278198+724118.0095240783+6175071.377365946&maprotation=

Og så er det ikke så godt at du tegner to veje oven i hinanden. Kun et vejstykke repræsenterer vejen. Du kan altid klippe et vejstykke op og navngive det med et andet navn.
Jørn-osm (2026-02-26 23:10:40+00:00): På kortoverblik.dk kan der vises et kort over området. Har zoommet ind og valgt "Vejnavn mindre".


https://kortoverblik.dk/spatialmap?mapheight=772&mapwidth=1231&label=&ignorefavorite=true&profile=sdfikort&selectorgroups=gd-baggrundskort+kom_gruppe&layers=theme-dtk_skaermkort_daempet_daf+theme-kommunikationskort-vejnavne-mindre+userpoint+userline+userpolygon+selectorpoint+selectorline+selectorpolygon+selectorbufferzone&opacities=1+1+1+1+1+1+1+1+1&mapext=723962.1764473729+6174938.503826289+724042.6954796901+6174988.877478645&maprotation=


Der er flere veje der bør rettes. Her er de første par stykker.


https://www.openstreetmap.org/way/23803807
Hedder Slagtehusgade


https://www.openstreetmap.org/way/165507979
Hedder Staldgade


https://www.openstreetmap.org/way/165507978
Skal opdelles og hedder Halmtorvet hhv. Staldgade


Mellem bygning
https://www.openstreetmap.org/way/115857535
og bygning
https://www.openstreetmap.org/way/115857524
mangler en ved der hedder Staldgade
aighes (2026-02-24 01:56:11+00:00): Was this automated edit somewhere discussed?
Hypsometric (2026-02-24 04:21:02+00:00): You commented there already. In case anyone else has input on these tags that the wiki says not to use on golf=*, the link to a forum post is below with further explanation.

https://community.openstreetmap.org/t/golf-features-tagged-incorrectly-according-to-the-wiki-and-obscure-tags/141786
NeisBot (2026-02-23 16:48: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 9 potential crossings.

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

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=178952188
NeisReview (2026-03-03 17:33:18+00:00): ✅ Should be fixed by 
https://osm.org/changeset/179188980
ChehrehBargi (2026-02-23 20:11:13+00:00): The height tag should only be applied to actual building areas. Using height on standalone nodes outside buildings is invalid. Please follow OSM building guidelines. Awaiting DWG review.
GuKe43 (2026-02-23 16:59:59+00:00): An Stelle von Spar ist jetzt Müller
ChehrehBargi (2026-02-23 20:16:38+00:00): The level tag should only be used on actual building areas. Standalone nodes outside buildings are not valid. Please follow OSM building guidelines. Awaiting DWG review.
ChehrehBargi (2026-02-23 20:17:50+00:00): The level tag should only be used on actual building areas. Standalone nodes outside buildings are not valid. Please follow OSM building guidelines. Awaiting DWG review.
NeisBot (2026-02-23 16:57:48+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/13474339945 v4

Could you please revise your text accordingly?

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

#MapWithoutSpam
NeisRevert (2026-03-03 17:33:14+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/179314306
(Clean up leftovers from previous edits)
ChehrehBargi (2026-02-23 20:19:50+00:00): The level tag should only be used on actual building areas. Standalone nodes outside buildings are not valid. Please follow OSM building guidelines. Awaiting DWG review.
GuKe43 (2026-02-23 17:00:51+00:00): Korrekter Standort des Geldautomaten
ChehrehBargi (2026-02-23 20:53:14+00:00): The operator tag should reflect the official full name as displayed. Please avoid shortening personal names.
ChehrehBargi (2026-02-23 20:22:15+00:00): The level tag should only be used on actual building areas. Standalone nodes outside buildings are not valid. Please follow OSM building guidelines. Awaiting DWG review.
ChehrehBargi (2026-02-23 20:24:44+00:00): The level tag should only be used on actual building areas. Standalone nodes outside buildings are not valid. Please follow OSM building guidelines. Awaiting DWG review.
NeisBot (2026-02-23 17:03:42+00:00): Hello, welcome and thank you for your contribution to OSM!

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

⚠️️ Problematic element (limit 1):
https://osm.org/node/11480954215 v2

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Ceramic grill store"

#MapWithoutSpam
NeisRevert (2026-03-03 17:33:16+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/179314310
(Clean up leftovers from previous edits)
ChehrehBargi (2026-02-23 20:25:28+00:00): The level tag should only be used on actual building areas. Standalone nodes outside buildings are not valid. Please follow OSM building guidelines. Awaiting DWG review.
ChehrehBargi (2026-02-23 20:26:31+00:00): The level tag should only be used on actual building areas. Standalone nodes outside buildings are not valid. Please follow OSM building guidelines. Awaiting DWG review.
ChehrehBargi (2026-02-23 19:12:34+00:00): Branch naming conflicts with OSM tagging guidelines. Awaiting DWG review.
ChehrehBargi (2026-02-23 20:34:09+00:00): The level tag should only be used on actual building areas. Standalone nodes outside buildings are not valid. Please follow OSM building guidelines. Awaiting DWG review.
ChehrehBargi (2026-02-23 20:43:54+00:00): The level tag should only be used on actual building areas. Standalone nodes outside buildings are not valid. Please follow OSM building guidelines. Awaiting DWG review.
ChehrehBargi (2026-02-24 14:23:58+00:00): Branch naming conflicts with OSM tagging guidelines. Awaiting DWG review.
NeisBot (2026-02-23 17:12: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/13556592065 v3

Could you please revise your text accordingly?

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

#MapWithoutSpam
NeisRevert (2026-03-03 17:33:17+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/179314311
(No visible changes after review)
ChehrehBargi (2026-02-23 20:48:19+00:00): The operator tag should reflect the official full name as displayed. Please avoid shortening personal names.
ChehrehBargi (2026-02-23 20:49:07+00:00): The level tag should only be used on actual building areas. Standalone nodes outside buildings are not valid. Please follow OSM building guidelines. Awaiting DWG review.
NeisBot (2026-02-23 17:12:41+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 36 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/1207968421 v2 | 5 crossings
https://osm.org/way/434510313 v5 | 3 crossings
https://osm.org/way/34874968 v61 | 11 crossings

⚠️ Dragged Nodes (max 3):
https://osm.org/node/12548054534 v2
https://osm.org/node/12548054535 v2
https://osm.org/node/12548054538 v2

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=178953192
NeisReview (2026-03-03 17:33:18+00:00): ✅ Should be fixed by 
https://osm.org/changeset/178953964