piebro/osm-data huggingface dataset:
alopix (2022-09-22 20:56:55+00:00): I don’t agree regarding the towpath, since it is more than a generic path. It is the official and designated NCN cycle path throughout as well as an official walking/hiking path. So I think the better way would to mark it as a combination of cycle+footpath instead of keeping it this generic. Especially with having the whole path tagged differently to this section now.
f8aj3k (2022-09-22 21:52:46+00:00): I've had another look at the wiki, and I now think arguments could be made either way rather than thinking it should definitely be "path" as I did before. To quote one of the sections on shared paths: "The iD preset "Cycle & Foot Path" uses highway=cycleway along with bicycle=designated and foot=designated. On the other hand, the equivalent JOSM preset tags this as highway=path with bicycle=designated and foot=designated".

When I made the edit, I went for the latter of the above approaches based on the following logic:
1 - Only one value can be set for "highway".
2 - "highway=cycleway" implies that the path is exclusively or primarily for cycling.
3 - The towpath is also designated for walking and part of waymarked trails, therefore it shouldn't be tagged as exclusively or primarily for cycling.

I'm now not so sure anymore that point 2 is accurate, so I'm happy to change the path type back, will do so after this. If I was starting from scratch, I still think "highway=path" would be more appropriate than "=cycleway"; it just seems more aligned with the type of path that it is (a path which wasn't originally built for cycling but has since been designated for it, rather than purpose-built cycle infrastructure). But as long as walking and cycling apps route it properly, I don't really care, certainly not enough to upate the entire towpath! So fair enough, may as well just put this section back as it was :)
GinaroZ (2022-09-23 22:18:21+00:00): Thanks for changing it back and keeping it consistent :)

As for the path connected to Ashley Road, @Alopix my original question is because you added bicycle access, however I'm wondering you have done that?
GinaroZ (2022-09-23 22:18:39+00:00): *why you have done that
alopix (2022-09-25 09:53:27+00:00): @GinaroZ I had done a bike tour that day and had imagined I’d seen a shared path sign (on the wall next to the path onto the main road), but on further inspection had been wrong
mavl (2022-08-16 13:47:38+00:00): This changeset has been reverted fully or in part by changeset 124972694 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poog mapping - https://www.openstreetmap.org/changeset/124910876].
Moonwalker008 (2022-08-13 05:38:43+00:00): Hallo mtb-sauerland,
du hast viele der man_made=clearcut Flächen in natural=scrub Flächen umgeändert. Ich war vor kurzem vor Ort und an vielen der Stellen ist jedoch kein Buschland sondern nur trockene Erde und die übergebliebenen Baumstümpfe.
Gruß Moonwalker008
Moonwalker008 (2022-12-28 19:19:31+00:00): Hallo mtb-sauerland,
es ist nach wie vor der Fall, dass dort die meisten Stellen Kahlschlagflächen und kein Buschland sind. Könntest du erklären, warum du diese zu Buschland geändert hast?
Gruß Moonwalker008
sauerland-radfahrer (2022-12-29 09:50:19+00:00): Hallo Moonwalker,
wenn die Flächen schon wieder aufgeforstet sind, kannst du gerne aktualisieren.
Viele Grüße
user_2066394 (2022-08-11 11:06:34+00:00): Dann würden wir sie nicht löschen, sondern mit access=private eintragen.
https://wiki.openstreetmap.org/wiki/DE:Key:access
user_18082736 (2022-12-25 01:49:43+00:00): did you get permission from them to use the information?
syntex (2022-08-12 10:57:38+00:00): No i? To nie jest droga jednokierunkowa. To jest dwukierunkowa droga serwisowa o jednym pasie w każda stronę. Jednokierunkowy jest tylko krótki zjazd, który już był oznaczony jako jadnokierunkowy. Jeśli nie wiesz, to nie zmieniaj. Co do podwyższenia kategorii tej drogi też mam wątpliwości.
user_16178067 (2022-08-13 06:49:47+00:00): Faktycznie, nie zauważyłem że to jest dwukierunkowa droga. Ze zmianą kategorii chodzi o to, żeby wszystkie drogi łączące S7 z DW721(i odwrotnie) były oznaczone jako secondary, bo na pewno będzie tędy szedł duży ruch do Piaseczna i do Lesznowoli, tym bardziej przed otwarciem odcinka B S7.
woodpeck (2022-08-11 11:54:40+00:00): Bitte Diskussion in https://forum.openstreetmap.org/viewtopic.php?pid=869330 beachten!
look4book (2025-12-13 18:24:39+00:00): Hallo Cycleguy13 - kannst Du Dich noch erinnern, was es mit dem "großen Dach" auf sich hat? ) Da ist kein großes Dach, und auch keine touristische Attraktion)
Cycleguy13 (2025-12-13 22:09:28+00:00): Hi, ich weiß nicht wo das ist und wann ich da war XD wenn da kein Dach (mehr) ist, kann es wohl entfernt werden. Danke!
Claudius Henrichs (2022-08-11 13:48:30+00:00): Hi,
Judging from this network map though this extended route is not fully part of HSL, but only until Jokela:
https://hslfi.azureedge.net/globalassets/matkustaminen/tulostettavat-aikataulut-ja-kartat/reittikartat/liikennevalineittain/hsl_lahiliikennelinjat_pysty_700x1000_8_2021_paino.pdf
I am actually not sure how best to reflect partial network membership in a route relation. Breaking the route into separate routes for the HSL and a VR segments doesn't seem to make sense since these are operating as through services. Right now the Helsinki HSL network validator is failing because Tampere is not part of the bounding box of the network :P
https://cdn.organicmaps.app/subway/finland.html
huopa (2022-08-11 13:54:28+00:00): Totally correct.. the R route was already drawn all the way to Hämeenlinna earlier, so the check failed already then. I noticed the validator failure, but I thought that it was failing earlier too so no change there. Would removing HSL from the route tags work? Then of course the R line service which is part of HSL would not be visible in OSM related applications.. 

How about two routes, one restricted to HSL area stopping in Jokela and another without HSL tag and going all the way to Tampere?
huopa (2022-08-11 14:04:11+00:00): Z route is marked only with VR
https://www.openstreetmap.org/relation/7435585

T route is marked with HSL network
https://www.openstreetmap.org/relation/358140

D stops in Riihimäki also, though according to VR map it should continue to Hämeenlinna as well, also part of HSL network
https://www.openstreetmap.org/relation/358112

so if we figure out what to do with these, we should probably fix all of them the same way.
Claudius Henrichs (2022-09-05 12:48:51+00:00): Splitting routes doesn't seem to reflect reality since it's the same train taking the whole route end to end. Creating separate routes would reflect that different routes would exist on the ground. I don't have a good idea yet on how to represent "Only this section of a route is part of HSL network" in OSM data, I'm afraid. I'll do some more research on various OSM Slack and forum channels to find if any option is out there.
huopa (2022-09-05 16:03:51+00:00): Thanks for taking the effort. I hope there is some way to do this.
josmougn (2022-08-19 20:22:33+00:00): bonjour geovelo.
Ca fait 12 ans que ce chemin est en "track" : https://www.openstreetmap.org/way/75589756
Pourquoi le passer soudain en path ? Sans doute sans y avoir posé une roue :-)
Cordialement
philippec (2024-02-01 21:58:20+00:00): Is dat het kraantje op de witte wand ? 
https://www.mapillary.com/app/?lat=51.2207463&lng=4.300009499999987&z=19.105494526993446&pKey=964709871544940&focus=photo
BBMaper (2024-02-02 06:33:45+00:00): Yes.
Lancelotance (2022-08-11 09:34:23+00:00): Source: Charmingglobe Satellite Imagery
CarolusMagnus (2022-08-11 12:42:27+00:00): Сомневаюсь, что общеупотребительным названием стройплощадки является фраза из 7 слов и 28 слогов, да ещё с запятой, что означает обязательное наличие паузы.
Прошу представить верификацию того факта, что местные жители, живущие на стройплощадке, именно так каждый раз и называют данный объект.
Полагаю, что даже после открытия действующей станции метро, никто не будет называть так, все будут говорить "Тюленева" или "Генерала Тюленева" (т.е. даже без "улица"). Но сейчас там не станция метро, а стройплощадка.
literan (2022-08-11 12:54:21+00:00): смотрите в вики правила именования стройплощадок, проголосованные сообществом
literan (2022-08-11 12:55:42+00:00): и не путайте общеупотребительное название с названием, которое употребляют жители в разговорной речи. В разговорной речи и Санкт-Петербург никто полным названием не называет
CarolusMagnus (2022-08-11 15:22:18+00:00): > В разговорной речи и Санкт-Петербург никто полным названием не называет

Я буквально два часа назад этот же продумал в уме этот довод :)

Но потом понял, что употребление бывает не только в разговорном, а в других ситуациях, где применяют именно полную форму. А название Рио-де-Жанейро полное знаете? Я думаю, что вот его точно никто не употребляет, вряд ли многие знают.

Но вообще понятие "общеупотребительное" нигде не раскрыто. На форуме видел споры по этому поводу: так и не пришли к консенсусу. Могу сказать к той теме, где это обсужалось, что объекты Павловского парка, действительно, не встречаются в широком обиходе, а музейные работники аборигенами не являются. Большинство жителей Павловска вообще не знают всех объектов, которые в парке есть.
Kovoschiz (2022-08-11 10:22:40+00:00): Hey this is not "spurious. They were a landmark, still visible from aerial imagery.
gyulasimonyi (2022-12-10 11:15:05+00:00): Note: I've done large data imports of glacier data into OSM from GLIMS (http://glims.colorado.edu/glacierdata/, also https://wiki.openstreetmap.org/wiki/GLIMS_Glacier_Database), specifically for the area called the Wakhan Corridor in NE Afghanistan that I know relatively well. All these changesets contain individually checked changes, polygon by polygon. I've also done improvements on the 'poorly vectorization' polygons before import, as this is a known issue with much of GLIMS data.
gyulasimonyi (2022-12-10 11:15:02+00:00): Note: I've done large data imports of glacier data into OSM from GLIMS (http://glims.colorado.edu/glacierdata/, also https://wiki.openstreetmap.org/wiki/GLIMS_Glacier_Database), specifically for the area called the Wakhan Corridor in NE Afghanistan that I know relatively well. All these changesets contain individually checked changes, polygon by polygon. I've also done improvements on the 'poorly vectorization' polygons before import, as this is a known issue with much of GLIMS data.
one_half_3544 (2022-08-18 18:58:55+00:00): So you've added lots of nodes, but not a single way.

This looks like a very bad import. Could you please fix it?

Thanks.
one_half_3544 (2022-08-18 18:59:32+00:00): E.g. https://www.openstreetmap.org/node/9946959291
gyulasimonyi (2022-08-20 18:41:58+00:00): Thanks for noticing it. It is now fixed.
gyulasimonyi (2022-12-10 11:15:00+00:00): Note: I've done large data imports of glacier data into OSM from GLIMS (http://glims.colorado.edu/glacierdata/, also https://wiki.openstreetmap.org/wiki/GLIMS_Glacier_Database), specifically for the area called the Wakhan Corridor in NE Afghanistan that I know relatively well. All these changesets contain individually checked changes, polygon by polygon. I've also done improvements on the 'poorly vectorization' polygons before import, as this is a known issue with much of GLIMS data.
gyulasimonyi (2022-12-10 11:14:46+00:00): Note: I've done large data imports of glacier data into OSM from GLIMS (http://glims.colorado.edu/glacierdata/, also https://wiki.openstreetmap.org/wiki/GLIMS_Glacier_Database), specifically for the area called the Wakhan Corridor in NE Afghanistan that I know relatively well. All these changesets contain individually checked changes, polygon by polygon. I've also done improvements on the 'poorly vectorization' polygons before import, as this is a known issue with much of GLIMS data.
gyulasimonyi (2022-12-10 11:14:44+00:00): Note: I've done large data imports of glacier data into OSM from GLIMS (http://glims.colorado.edu/glacierdata/, also https://wiki.openstreetmap.org/wiki/GLIMS_Glacier_Database), specifically for the area called the Wakhan Corridor in NE Afghanistan that I know relatively well. All these changesets contain individually checked changes, polygon by polygon. I've also done improvements on the 'poorly vectorization' polygons before import, as this is a known issue with much of GLIMS data.
gyulasimonyi (2022-12-10 11:14:42+00:00): Note: I've done large data imports of glacier data into OSM from GLIMS (http://glims.colorado.edu/glacierdata/, also https://wiki.openstreetmap.org/wiki/GLIMS_Glacier_Database), specifically for the area called the Wakhan Corridor in NE Afghanistan that I know relatively well. All these changesets contain individually checked changes, polygon by polygon. I've also done improvements on the 'poorly vectorization' polygons before import, as this is a known issue with much of GLIMS data.
gyulasimonyi (2022-12-10 11:14:40+00:00): Note: I've done large data imports of glacier data into OSM from GLIMS (http://glims.colorado.edu/glacierdata/, also https://wiki.openstreetmap.org/wiki/GLIMS_Glacier_Database), specifically for the area called the Wakhan Corridor in NE Afghanistan that I know relatively well. All these changesets contain individually checked changes, polygon by polygon. I've also done improvements on the 'poorly vectorization' polygons before import, as this is a known issue with much of GLIMS data.
gyulasimonyi (2022-12-10 11:14:38+00:00): Note: I've done large data imports of glacier data into OSM from GLIMS (http://glims.colorado.edu/glacierdata/, also https://wiki.openstreetmap.org/wiki/GLIMS_Glacier_Database), specifically for the area called the Wakhan Corridor in NE Afghanistan that I know relatively well. All these changesets contain individually checked changes, polygon by polygon. I've also done improvements on the 'poorly vectorization' polygons before import, as this is a known issue with much of GLIMS data.
gyulasimonyi (2022-12-10 11:14:35+00:00): Note: I've done large data imports of glacier data into OSM from GLIMS (http://glims.colorado.edu/glacierdata/, also https://wiki.openstreetmap.org/wiki/GLIMS_Glacier_Database), specifically for the area called the Wakhan Corridor in NE Afghanistan that I know relatively well. All these changesets contain individually checked changes, polygon by polygon. I've also done improvements on the 'poorly vectorization' polygons before import, as this is a known issue with much of GLIMS data.
gyulasimonyi (2022-12-10 11:14:33+00:00): Note: I've done large data imports of glacier data into OSM from GLIMS (http://glims.colorado.edu/glacierdata/, also https://wiki.openstreetmap.org/wiki/GLIMS_Glacier_Database), specifically for the area called the Wakhan Corridor in NE Afghanistan that I know relatively well. All these changesets contain individually checked changes, polygon by polygon. I've also done improvements on the 'poorly vectorization' polygons before import, as this is a known issue with much of GLIMS data.
gyulasimonyi (2022-12-10 11:14:31+00:00): Note: I've done large data imports of glacier data into OSM from GLIMS (http://glims.colorado.edu/glacierdata/, also https://wiki.openstreetmap.org/wiki/GLIMS_Glacier_Database), specifically for the area called the Wakhan Corridor in NE Afghanistan that I know relatively well. All these changesets contain individually checked changes, polygon by polygon. I've also done improvements on the 'poorly vectorization' polygons before import, as this is a known issue with much of GLIMS data.
gyulasimonyi (2022-12-10 11:14:28+00:00): Note: I've done large data imports of glacier data into OSM from GLIMS (http://glims.colorado.edu/glacierdata/, also https://wiki.openstreetmap.org/wiki/GLIMS_Glacier_Database), specifically for the area called the Wakhan Corridor in NE Afghanistan that I know relatively well. All these changesets contain individually checked changes, polygon by polygon. I've also done improvements on the 'poorly vectorization' polygons before import, as this is a known issue with much of GLIMS data.
gyulasimonyi (2022-12-10 11:14:26+00:00): Note: I've done large data imports of glacier data into OSM from GLIMS (http://glims.colorado.edu/glacierdata/, also https://wiki.openstreetmap.org/wiki/GLIMS_Glacier_Database), specifically for the area called the Wakhan Corridor in NE Afghanistan that I know relatively well. All these changesets contain individually checked changes, polygon by polygon. I've also done improvements on the 'poorly vectorization' polygons before import, as this is a known issue with much of GLIMS data.
gyulasimonyi (2022-12-10 11:14:24+00:00): Note: I've done large data imports of glacier data into OSM from GLIMS (http://glims.colorado.edu/glacierdata/, also https://wiki.openstreetmap.org/wiki/GLIMS_Glacier_Database), specifically for the area called the Wakhan Corridor in NE Afghanistan that I know relatively well. All these changesets contain individually checked changes, polygon by polygon. I've also done improvements on the 'poorly vectorization' polygons before import, as this is a known issue with much of GLIMS data.
Langlaeufer (2022-08-11 19:58:21+00:00): Hallo Nadjita,
ich denke es war vorher richtig.
siehe how to map:
crossing=traffic_signals für Fußgänger- und Radfahrerübergänge mit Ampel
highway=traffic_signals für beampelte Autokreuzungen
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/124767695
Nadjita (2022-08-12 14:11:36+00:00): Ja, war es. Osmose hatte sich beschwert, dass nirgendwo ein highway=traffic_signals war und ich war dann kurzfristig von der Wiki-Seite verwirrt, weil die nämlich sagt, dass die ganzen Zusatz-Tags wie "akkustisches Signal für Blinde" an den highway=traffic_signals gehören. Hab das mittlerweile alles wieder verbessert. Kann man Dich auch anders erreichen als über diese Kommentare? Ich lese doch recht selten E-Mails.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/124767695
Langlaeufer (2022-08-12 14:42:26+00:00): Die Kommentare haben Vorteil, das auch andere Mapper die Diskussion mitlesen können. Ich melde mich aber gleich nochmal über die OSM-Nachrichten bei dir.
gyulasimonyi (2022-12-10 11:14:21+00:00): Note: I've done large data imports of glacier data into OSM from GLIMS (http://glims.colorado.edu/glacierdata/, also https://wiki.openstreetmap.org/wiki/GLIMS_Glacier_Database), specifically for the area called the Wakhan Corridor in NE Afghanistan that I know relatively well. All these changesets contain individually checked changes, polygon by polygon. I've also done improvements on the 'poorly vectorization' polygons before import, as this is a known issue with much of GLIMS data.
ToniE (2022-08-12 08:33:16+00:00): Servus ffb20fh

bitte bei Änderungen, Verlagerungen von Bushaltestellen (auf der Straße) auch immer die betroffenen Bus-Relationen beachten.

PTNA (https://ptna.openstreetmap.de/results/DE/BY/DE-BY-MVV-Analysis.diff.html#bus_872) meldet nun:  PTv2 Route: 'role' = 'stop' aber 'public_transport' ist nicht gesetzt: Node https://www.openstreetmap.org/node/9947067664

Das war mal die public_transport=stop_position, die verlagert wurde.

Gruß
Toni
ToniE (2022-08-12 15:18:21+00:00): BTW: wo wendet denn der Bus nun?
kepivar (2022-08-11 12:26:08+00:00): Hi Rotilom,
you MAY tag terraced houses as https://wiki.openstreetmap.org/wiki/Tag:house%3Dterrace (d)
Rotilom (2022-08-11 13:08:06+00:00): Hello Kepivar,

Thank you! Is really your first day here?

I've embarked on a two-week stint adding buildings in Ballymena. This is week one where I'm just tracing buildings, and then next week I'll be more discerning and come back tag them a bit better.

Thanks! R.
Langlaeufer (2022-08-11 19:58:39+00:00): crossing=traffic_signals für Fußgänger- und Radfahrerübergänge mit Ampel
highway=traffic_signals für beampelte Autokreuzungen
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/124768012
Marc_ch (2022-08-19 16:23:36+00:00): Bonjour,
il n'y a aucun soucis pour faire un test d'import (encore que il y a un serveur de test)
Par contre pour l'import propre dit, j'attire votre attention sur https://wiki.openstreetmap.org/wiki/FR:Import/Guidelines
qui parle entre autre de :
- vérifier la licence 
- faire une page wiki qui documente la chose (cela permet aux autres de vérifier la conversion des tags qui apparement avait un soucis pour le verre, cela permettra aussi d'éviter de devoir tout refaire à 0 la prochaine fois qu'un autre utilisateur utilisera le même jeux de fichier)
- en parler avec la communauté pour accord https://lists.openstreetmap.org/listinfo/talk-fr
Cordialement,
Marc
eggie (2022-08-11 10:39:31+00:00): Dag Hans Alle adresnodes zijn directe import vanuit het Kadaster. Dat klopt meestal wel. 
Wanneer iets niet goed is dan kun je een terugmelding doen richting Kadaster.

Heb je het gecheckt bij het Kadaster?

Groet
Eggie
eggie (2022-08-11 10:45:58+00:00): Volgens mij heeft het Kadaster het niet goed verwerkt.
Stuur je zelf een terugmelding?
https://bagviewer.kadaster.nl/lvbag/bag-viewer/index.html#?searchQuery=Hazeldonkseweg%2022&resultOffset=0&objectId=0762100000000009&geometry.x=182603.07100769&geometry.y=381166.02499915&zoomlevel=7&detailsObjectId=

Gewoon op het potloodje klikken. 

MVG
eggie
eggie (2022-08-11 10:47:07+00:00): De fout komt anders met een periodieke import weer terug in OSM...
eggie (2022-08-11 11:43:11+00:00): PB contact
eggie (2022-08-11 11:48:38+00:00): Even Sebastic ingeseind.. Wellicht wat licht in de duisternis :)
Lancelotance (2022-08-11 10:17:14+00:00): 完整的网址：http://www.xt.gov.cn/xt/0101/202112/5b0ddb5f406d4dc09f8cb2701a9665b4.shtml
abakus_uploader (2022-08-11 22:31:13+00:00): (Wiadomość automatyczna)
Cześć!
Otrzymujesz ten komentarz, ponieważ dodałeś lub zmodyfikowałeś adres, który jest niepełny lub błędny.
Adres powinien zawierać minimum trzy znaczniki: addr:city=[nazwa_miejscowosci] + addr:street=[nazwa_ulicy] + addr:housenumber=[numer_porządkowy].
Wyjątkiem są miejscowości bez nazwanych ulic - wtedy stosujemy znaczniki: addr:place=[nazwa_miejscowosci] + addr:housenumber=[numer_porządkowy].
Bez poprawnego oznaczenia adresów, nie będą one brane pod uwagę przez wyszukiwarki, dlatego warto je dostosować do ww. schematu (w zależności od sytuacji).
Więcej informacji na forum: https://forum.openstreetmap.org/viewtopic.php?id=5632 - a pytania najlepiej zadawać tu: https://forum.openstreetmap.org/viewtopic.php?pid=681873
Pozdrawiamy!
abakus_uploader (2022-08-11 22:32:13+00:00): (Wiadomość automatyczna)
Cześć!
Otrzymujesz ten komentarz, ponieważ dodałeś lub zmodyfikowałeś adres, który jest niepełny lub błędny.
Adres powinien zawierać minimum trzy znaczniki: addr:city=[nazwa_miejscowosci] + addr:street=[nazwa_ulicy] + addr:housenumber=[numer_porządkowy].
Wyjątkiem są miejscowości bez nazwanych ulic - wtedy stosujemy znaczniki: addr:place=[nazwa_miejscowosci] + addr:housenumber=[numer_porządkowy].
Bez poprawnego oznaczenia adresów, nie będą one brane pod uwagę przez wyszukiwarki, dlatego warto je dostosować do ww. schematu (w zależności od sytuacji).
Więcej informacji na forum: https://forum.openstreetmap.org/viewtopic.php?id=5632 - a pytania najlepiej zadawać tu: https://forum.openstreetmap.org/viewtopic.php?pid=681873
Pozdrawiamy!
Jakka (2022-08-12 05:58:01+00:00): corriger voir message "welcom"
user_5359 (2022-08-20 14:13:12+00:00): Welcome to OSM! What kind of smart home have you added here? In the house is rather a clean house (building cleaning https://bonoclean.berlin/)...
mapperue (2024-01-28 11:12:26+00:00): Ahoj,
pozri si prosím, kedy sa používa povrch surface=rock.
https://wiki.openstreetmap.org/wiki/Tag:surface=rock
Pretože ho používaš na zjazdné cesty ako je táto cesta:
openstreetmap.org/way/51930446
Pri takejto ceste sa používa povrch gravel.