those ways are unfinished mapping of landuse and can be later used to finish it.

Ahoj. Podľa ortofoto aj podľa fotky z roku 2020 tam je most. Prosim prever a oprav ak treba.

Ak iD editor varuje ze sa krizi ceta a vodny tok, neznamena ze je to automaticky brod.

Ahoj Peťo.

Vidím, že dosť edituješ landcover a preto ti dávam do pozornosti nástroj na www.freemap.sk, ktorý ti pre zvolenú oblasť "obkreslí" lesy/lúky: https://groups.google.com/g/osm_sk/c/d_6Csbkc5gw/m/5DhuXdsoAgAJ

Editovať potom odporúčam v editore JOSM. Ak niečo, kľudne mi napíš.

construction=house nie je dobre na celu plochu, lebo to hovori, ze tam stavaju jeden obrovsky dom

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.

uz netusim 🫣

Cau Peto. Davaj prosim access=private na tie sukromne bazeny, nech sa neobjavia v turistickych sprievodcoch :-)

opravene

I agree that the edit is valid, just unfortunately some renderrers depend on boundary=administrative on border ways. For example https://www.freemap.sk/#map=9/48.764322/22.604240&layers=X

+source ZBGIS

Neviemn. Mozno ZBGIS alebo INSPIRE data?

Hi.

It was a bad decision made long time ago. I am since then putting them on correct position and AFAIK I was reverting such changesets.

ani cesta? ani diera v plote? ;-)
kludne to prosim oprav podla reality. dakujem👋.

Vdaka za info. Trochu som to upravil, ale bude nutny prieskum na mieste.

Please don't do such edits.

Uz netusim, kludne odstran.

Hi. Please see osm.wiki/Relation:waterway

Myslim, ze namiesto image=https://backend.freemap.sk/gallery/pictures/657529/image?width=1110 dat image=https://backend.freemap.sk/gallery/pictures/657529/image

Ahoj,

Ked pridavas foto na freemap, maz prosim `?width=1110` z URL. Vdaka.

Feel free to update it in OSM if you have more precise and recent data. Thank you.