piebro/osm-data huggingface dataset:
gscscnd (2026-01-11 20:27:35+00:00): Hi! I don’t agree these characters are invalid, they are not here to insert some evil commands to one’s terminal emulator or cause a kernel panic in one’s iPhone.

U+00AD soft hyphen followed by U+2011 non-breaking hyphen is a common pattern in Polish typography that guarantees that when a line break occurs in a word composed of parts separated by hyphens, both parts in both lines keep the hyphen. When there’s no line break, only U+2011 should be normally visible. Example: "Maroko<hyphen><line break><hyphen>Nowiny". JOSM always shows both soft hyphen and non-breaking hyphen, which is not pretty, but aids editing.

U+00A0 no-break space follows one-letter conjunctions to make sure they are not left alone at the end of the line. And there are some other similar uses. Example: "PTTK<nbsp><mdash> Oddział w<nbsp>Rybniku". Many plain text editors render nbsp differently to a regular space.

I agree most OpenStreetMap contributors are not typography experts, but I’m not certain these characters pose issues that warrant their removal. It’s easier to drop them in software, for example, convert all U+00AD + U+2011 pairs, as well as lone U+2010, to plain old U+002D hyphen-minus; than to correctly guess them from such simplified representation.
*Martin* (2026-01-13 09:01:50+00:00): Hi, thanks for taking the time to explain the typographic background, I appreciate that.

I fully understand that U+00AD, U+2011 and NBSP are legitimate tools in professional typography and that they are commonly used in Polish texts to control line breaking and avoid single-letter words at line ends. I’m not suggesting these characters are "evil" or security-related in any way.

My concern is more about how OSM name=* is used in practice. It's primarily a data and interchange field, not a typesetting string. Many OSM data consumers (search engines, geocoders, QA tools, renderers, exports) either don't preserve these characters consistently or users cannot easily type them when searching. Invisible or special whitespace/hyphen characters also make manual editing and comparison harder, because strings that look identical are not equal at the data level.

Because of that, keeping typographic line-breaking hints in name=* usually doesn't reliably achieve the intended effect anyway, but it does introduce interoperability and usability issues. For example, users searching with a normal hyphen or space may not get a match, and different tools normalize these characters differently.

For this reason I'm treating U+00AD, U+2011 and NBSP in name=* as presentation-only formatting and normalizing them to a simpler, widely expected form (plain hyphen-minus and regular space, soft hyphen removed). This matches common OSM practice and keeps names easier to search, compare and process across tools.

If there is a case where a special hyphen character is explicitly part of the official written form on signage or in authoritative sources (not just a typographic hint for line breaks), I agree that it should be kept. But for general Polish typographic conventions, I think normalization in name=* is the more practical choice for OSM.

Hope this clarifies my reasoning.
gscscnd (2026-01-14 15:21:52+00:00): Thanks for sharing your opinion. You’re right introducing and maintaining advanced typography at OSM data level, at least regarding invisible characters, is difficult. I think I’ll have to make some preprocessor for OSM files that would tune the names, and use it for making maps; or a QGIS plugin, or something.
NorthCrab_upload (2026-01-12 06:48:13+00:00): Zauważyłem, że Twoja zmiana zawiera niepoprawne adresy. Przygotowałem listę obiektów do poprawy oraz dodatkowe informacje:

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

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

W razie problemów lub pytań, proszę pisać. Chętnie pomogę.
Pozdrawiam! 🦀
NorthCrab_upload (2026-01-12 06:57:54+00:00): Zauważyłem, że Twoja zmiana zawiera niepoprawne adresy. Przygotowałem listę obiektów do poprawy oraz dodatkowe informacje:

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

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

W razie problemów lub pytań, proszę pisać. Chętnie pomogę.
Pozdrawiam! 🦀
NorthCrab_upload (2026-01-12 07:07:38+00:00): Zauważyłem, że Twoja zmiana zawiera niepoprawne adresy. Przygotowałem listę obiektów do poprawy oraz dodatkowe informacje:

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

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

W razie problemów lub pytań, proszę pisać. Chętnie pomogę.
Pozdrawiam! 🦀
NorthCrab_upload (2026-01-12 07:28:16+00:00): Zauważyłem, że Twoja zmiana zawiera niepoprawne adresy. Przygotowałem listę obiektów do poprawy oraz dodatkowe informacje:

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

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

W razie problemów lub pytań, proszę pisać. Chętnie pomogę.
Pozdrawiam! 🦀
NorthCrab_upload (2026-01-12 08:38:55+00:00): Zauważyłem, że Twoja zmiana zawiera niepoprawne adresy. Przygotowałem listę obiektów do poprawy oraz dodatkowe informacje:

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

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

W razie problemów lub pytań, proszę pisać. Chętnie pomogę.
Pozdrawiam! 🦀
Seyruun (2026-01-10 09:55:45+00:00): Thank you for fixing my mistakes!
limes11 (2026-01-18 10:03:23+00:00): Hallo Fritzi,

Ist hier vor Ort erkennbar, wie lange die Sperrung anhält ? 
Wintersperrungen auf solchen Wegen sind normal, das sollten wir nicht über ein globales access=no erfassen.

Viele Grüße
Glassman (2026-01-09 23:59:43+00:00): Why did you reclassify the roads as service? They can still be consider residential even if privately owned. Can you review this edit? I'll send you more info on OSM in a message.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/177041472
gingersnaps_509 (2026-01-10 17:52:20+00:00): They were reclassified as driveways because they are a platted lane that is not maintained by the county. These types of lanes have less width and usually less maintenance than a typical residential road and should not be classified as such.
Glassman (2026-01-10 18:27:23+00:00): OSM road classification is based on the definition from England (where OSM got its start). The wiki has no requirement for width, it can even be just one lane. Even though the road is not maintained by the local government, it can still fit the definition of highway=residential. See https://wiki.openstreetmap.org/wiki/Tag:highway%3Dresidential. Also the tag ownership=private can be added.
A67-A67 (2026-01-09 22:09:47+00:00): Deze wijziging bevat dezelfde fouten als eerdere wijzingen. Ook weer geen changeset comment en geen reacties op wijzingen.

Graag stoppen met op deze manier de kaart te bewerken!
Dillen GJ (2026-01-10 10:42:37+00:00): Zou de CoMaps app geen changeset  comment veld hebben om in te vullen toevallig ?
En ziet hij deze comments via bewuste app ook niet toevallig ?
A67-A67 (2026-01-10 14:30:04+00:00): Ik heb deze foutieve en buggy wijziging teruggedraaid.

De mapper heeft eerder wel gereageerd en comments toegevoegd aan de changeset, dus het kan wel in CoMaps.
lyctkel (2026-01-12 12:36:41+00:00): Dag juni_vv,

Leuk om je als nieuwe mapper te mogen verwelkomen.
Deze opmerking is erg lang geworden en is moeilijk te lezen in het comment bij de changset. Ik stuur hem ook als bericht naar je toe.

Ik heb een klein foutje opgemerkt.
Bij https://www.openstreetmap.org/node/13443738637, https://www.openstreetmap.org/node/13448113914,https://www.openstreetmap.org/node/13448113915  en https://www.openstreetmap.org/node/6242892756 gebruik je recycling:glass=yes.
Reinis is hier niet erg duidelijk geweest bij het beschrijven van de afvalcontainers.
Hoewel er glas op de containers staat, betekent dit niet dat alle soorten glas worden ingezameld. Hier wordt bedoeld recycling:glass_bottles=yes
Als je bijvoorbeeld borosilicaatglas (Pyrex, wordt gebruikt voor kookgerei) hebt, mag dit niet in deze containers (zie ook https://reinis.nl/afvalwijzer). Dit geldt ook voor vensterglas en andere soorten glas. Zie ook https://wiki.openstreetmap.org/wiki/Tag:amenity%3Drecycling .

Ik heb nog een extra verzoek. Er is nog een tag waarmee containers voor glas kunnen worden aangevuld: recycling:glass_bottles:colour
Deze wordt gebruikt om de kleur van het ingezamelde glas te beschrijven.
Het is tot nu toe nog niet gedocumenteerd in de wiki, maar wordt wel gebruikt en er is een discussie over (https://community.openstreetmap.org/t/rfc-tagging-glass-recycling/101011/32). 
Typische waarden hiervan zijn hier te vinden: https://taginfo.openstreetmap.org/keys/recycling%3Aglass_bottles%3Acolour#values
Als er meerdere verschillende kleuren zijn, sorteer ik deze alfabetisch bij de values.

Hartelijke groeten en veel plezier met het in kaart brengen in de winter, dat verdient respect!

lyctkel
OscarBrownbread (2026-02-26 12:39:31+00:00): Addresses on this lane still show as "Humbert Mall". Where did you get "Humbert Lane" from? We can add both names if necessary. If there is a street sign, then that can be the main name.
Man in Mayo (2026-03-07 09:35:24+00:00): My apologies, it may have been a mistake on my part. I don't think there's a street sign. Certainly not one that I can see, anyway. I asked someone who has lived in Castlebar for a few years, and she thought it was called Humber Lane.

It's possible that it doesn't have a name.
OscarBrownbread (2026-03-07 10:30:54+00:00): I've reverted that lane back to "Humbert Mall" as the official name. It's "Humbert Lane" on GMaps, so that's a bit of a trap. I've chosen to not add "Lane" it as an alternative name. I hope you are happy with that.

Thanks for mapping on the ground. It's valuable to talk to people, but in this case we need to be careful to use official names and sources.
OscarBrownbread (2026-03-07 10:30:59+00:00): https://www.openstreetmap.org/changeset/179484029
ceirios (2026-01-09 21:26:10+00:00): Hi CalJones93,

Thanks for contributing! The white and orange striped lines (white and grey on the map) are a road under construction, and you drew a new road on top of this instead of changing it to the residential road.

I'm not quite sure you're aware of what you're doing here, so I suggest going through the Walkthrough (maybe a box came up on your screen when you started editing?) - you can find it by pressing H on your keyboard when you're in the editor.

Cofion
Ceirios
StC (2026-01-09 21:45:00+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.
sweatsoon (2026-01-18 10:44:50+00:00): Merci, je me doutais du problème, je suppose qu'il fallait mettre à jour des relations, ce que je ne maitrise pas.
Cdt.
StC (2026-01-18 10:50:04+00:00): Oui, hélas c'est compliqué de modifier des chemins quand on ne maîtrise pas les relations, d'autant que les outils n'aident pas.
NeisBot (2026-01-10 07:29:58+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/13416569117 v2

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Sports nutrition and tanning store in Richmond KY"

#MapWithoutSpam
NeisRevert (2026-01-18 11:22:23+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/177369079
NeisBot (2026-01-10 07:28: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 44 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/44831231 v14 | 5 crossings
https://osm.org/way/41425175 v10 | 4 crossings

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=177042835
pitscheplatsch (2026-01-10 08:08:41+00:00): In this case, it seems the reported issues are false positives. The geometries were not changed in a way that would introduce crossings, and the tagging adjustments did not create any new conflicts. 

Sorry for the inconvenience, and thanks again for your map edits.

Regards,
Pascal
Fizzie-DWG (2026-01-25 03:46:15+00:00): DWG revert - apparent undiscussed import

https://www.openstreetmap.org/changeset/177668049
NeisBot (2026-01-10 07:30:02+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/13440539265 v3

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Appliance store in Murrells Inlet"

#MapWithoutSpam
NeisRevert (2026-01-18 11:22:24+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/177369080
lotug (2026-01-10 09:28:15+00:00): Plantagen i Kalmar har stängt ner sen ett år tillbaka
simer_lkpg (2026-01-10 14:09:13+00:00): Vet du om lokalen har fått någon ny butik eller är vakant?
lotug (2026-01-11 16:56:14+00:00): Den är vakant.
EneaSuper (2026-01-10 09:37:14+00:00): Ciao, dai un'occhiata a questo:

https://wiki.openstreetmap.org/wiki/Tag:barrier%3Dlog
MrAndrea (2026-01-10 09:45:49+00:00): Ciao, ho aggiunto barrier:log.
Mi sono accorto che mappi la zona di Seui, io ho mappato quasi tutto a Ussassai e le zone limitrofe!
EneaSuper (2026-01-10 09:53:04+00:00): Perfetto, ottimo lavoro!

Sì mi ricordo di te, come stai? 😊

Anche se non ti ho più visto attivo per molto tempo 😲
MrAndrea (2026-01-10 11:00:17+00:00): tutto bene, sì per un bel po non ho fatto quasi più nulla, ultimamente aggiungo qualche cosa che vedo che manca
MrAndrea (2026-01-10 11:00:51+00:00): solo che ora le mappe sono abbastanza complete e trovare sentieri o stradine mancanti è difficile
martiensch (2026-03-09 10:42:07+00:00): Hoi Jan
Ook hier hetzelfde. Wat is er secondary aan de verbindingen rondom de afrit Groningen-Zuidoost en Groningen-Europapark?
joel56dt (2026-01-09 22:57:02+00:00): Mapping temporary road closures on OSM is difficult. If you believe there is a better way of mapping this, please go ahead and make the change.

Closer to Jan 26th, it will probably be best to change this to oneway=yes so that all routers reflect this significant road closure. I do not believe most routers will consider the temporary oneway tagging I added in their calculation.
eggie (2026-01-10 07:28:14+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privebericht.
Feedback Info samengevoegd met bestaande adresnode.
MVG,
Eggie
Namens de OSM Community
RivRavs (2026-01-10 07:58:04+00:00): Hi Eggie,

Dank voor je bericht met handige tips en links en het samenvoegen van de feedback info.

Mvg,
River
tomhukins (2026-01-14 14:31:16+00:00): Thank you for your helpful contribution to OpenStreetMap.

The opening hours to added to https://www.openstreetmap.org/way/1465733332 as "Fri-Sun 7-11" aren't in the correct format described at https://wiki.openstreetmap.org/wiki/Key:opening%20hours

Is this club only open between 7pm and 11pm between Friday and Sunday or did you mean something else?

If I'm right, the correct format would be "Fr-Su 19:00-23:00".

Please don't take this as criticism: it's great that you have contributed to the map and I would like to help add to your improvements.
Ianv80 (2026-01-15 11:42:12+00:00): No worries - I have now updated. 
Thanks for letting me know
tomhukins (2026-01-15 14:15:25+00:00): Thanks again, that's great.
Glassman (2026-01-10 18:18:57+00:00): Thhe school's website shows the address as 2202 M Avenue. https://www.asd103.org/AMS. Yet you show it as 2200. Can you confirm the address is correct?
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/177044694
trailrunner13 (2026-01-10 18:32:34+00:00): I updated the address as part of adding a Node for the Anacortes School District  office at 2200 M Avenue (https://www.asd103.org/) which appears to be collocated within Anacortes Middle School. I will revert the school's addr:housenumber.
CanopyFalls (2026-01-10 11:05:00+00:00): Thank you for your contributions to the map, I have marked this changeset bad on OSMCha but note that doesn't mean the contributions aren't appreciated, they very much are, just that more work is needed here.

Love that you mapped the pavements! I've been doing that in my local area as well, Have a look around the Manor area for some examples if you want. When mapping sidewalks make sure to connect them to the road either using `footway=link` with `barrier=kerb` or using crossings with similar `barrier=kerb` tags on either side. I've added these for this section of road so feel free to look at that as an example.

Splitting the terraces up is really good work and makes the information much more useful! When you have many segments like that don't try to align them all by hand, I'm impressed you got it even close to straight using iD like that. You can instead select them all and square them all using the "q" key while they're selected.

Other than that looks all good! Feel free to reply here or message me if you have any questions and best of luck mapping!

Also if you happen to live in the area the app Street Complete is excellent for surveying and we really need more on the ground data in Sheffield!
Norbert Dichter (2026-01-10 13:36:24+00:00): Hello, thanks for mapping and welcome to HOT. Thank you for your contribution. The buildings you mapped are well done as to their location. But pay attention to the squareness of the corners. Always draw buildings as square and precise as you can. Then add the Building feature type. And last, right click it and click the square icon. Or just hit the Q-key.
Also please keep in mind: many buildings are very close but do not actually touch each other, try to map them close to each other without letting them connect or share nodes with each other, roads, or residential area outlines. In the iD web editor, holding down the "alt" key will keep nodes from "snapping" to each other and accidentally connecting.  Thanks so much for your contribution, Norbert 'Nodi' Dichter, HOT validator.
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.org/changesets/177046105
S-zation (2026-01-10 03:37:58+00:00): Hello and thank you for contributing to OpenStreetMap!

I've confirmed that this camera exists and corrected some tags. See https://deflock.me/report for the best tags to use for Flock cameras.

Please keep in mind when using streetlevel imagery that Google is copyrighted and not permitted for OSM use. However, mapillary.com is allowed and encouraged (and has excellent new image coverage in CT). In the image editor, press "U" and then check "Mapillary" to pull up street imagery.
ChaireMobiliteKaligrafy (2026-01-10 12:48:34+00:00): I understand that it would be dangerous/weird to walk there, but is there a sign prohibiting it? If not, the OSM wiki says to use the foot=no or bicycle=no tags only if there is a sign prohibiting access. Thanks and have a nice day!
NeisBot (2026-01-10 07:30:07+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/13444335759 v1

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Home inspection services"

#MapWithoutSpam
NeisRevert (2026-01-18 11:22:57+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/177369096
(Deleted leftovers after several edits)
PeriodicChair (2026-01-10 01:39:51+00:00): Freshly installed Flock. Picture taken about 5 hours after installation.
NeisBot (2026-01-10 07:30:08+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/13444464991 v1

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Digital marketing agency in Brisbane"

#MapWithoutSpam