piebro/osm-data huggingface dataset:
Cebderby (2020-09-16 12:33:35+00:00): Thanks for your prompt reply.  Sorry if this reply gets a bit long, quite a few things to mention here.
First I should say that if the data is as consistent and accurate as it appears it is a valuable addition and is not doing anyone any harm by being there for the time being,  but may need to be adjusted to match OSM practise.  I did comment to Aman Saraf (after the first ~106 edits I think) but no reply and the edits continued.
The key tflLine is a problem due to duplicating 'line' and not following OSM naming conventions.  'line', while undocumented as a regular tag for railway=station seems to be in use in Kiev,Berlin,Denver and a few others as well as London.  
Regarding the values, pretty much all the data in OSM (with obvious exception of 'description','note' etc free text) is potentially machine readable, with semicolon the usual separator for multiple values.  The existing 'line' values match this (but not the one you added here).  Also OSM uses names with upper case first letters, unabbreviated in almost all cases eg "Hammersmith & City".  So the 'line' values are semicolon-separated lists of line names, potentially exactly what you are looking for.
You didn't directly comment on the purpose of adding this data, if you are looking to integrate OSM data with other systems/data can you cope with a lookup table from OSM names to TFL ones?  I did note some stations with existing line values of "Northern City" which you could also map to your "northern" if the branch is not useful for you?
Other thoughts: you are at the margins of being involved with what OSM refers to as 'organised editing' see https://wiki.openstreetmap.org/wiki/Organised_Editing_Guidelines
and also skirting close to the description of data imports in https://wiki.openstreetmap.org/wiki/How_We_Map
If you are not just personally adding data for benefit of OSM and its user community, (or if this discussion gets any more complicated than I've just made it!) can I point you at the 'Talk-GB' mailing list https://lists.openstreetmap.org/listinfo/talk-gb
where a wider group of the OSM community can advise on any of this stuff.  When its decided what's best to do, the data can potentially be manipulated without having to re-edit each station individually.
regards
Cebderby (Clive)
ceilfors (2020-09-16 13:33:33+00:00): Hi Clive,

- Apologies, Aman (my colleague) might not have checked his inbox. Also thank you for guiding us through, we'll be keen to make sure that the data is in the format that the community can benefit from.

- Question: Is there a documentation on how we can edit nodes in batch? We've been updating these manually :(

- Our use case: Yes, we're trying to integrate OSM data with other system. We thought of using this opportunity to help the community as well as these are useful additional information.

- Confusion 1: Just to double confirm, is the recommendation for us to delete `tflLine` because it's to coupled with other system? Sticking with `line` tag sounds good to me.

- Confusion 2: On the convention, is th recommendation to change the value from "Circle, Hammersmith & City" to "Circle;Hammersmith & City"? Note that the "&" is actually part of the name of the line. I'm not sure if I get what you meant correctly as I don't see any abbreviation involved.

- Organised editing: We may not need the `tflLine` if the `line` is a better alternative for OSM. The line info itself is actually from OSM wiki: https://wiki.openstreetmap.org/wiki/List_of_London_Underground_stations.
Cebderby (2020-09-16 16:14:32+00:00): If 'line' is going to work for you (provided the data is complete and consistent) then that is is direction we should go, and move the new information you've added (but with uppercase and semicolons) over from 'tflLine' to 'line' where missing.  
There will be some with "Overground" in the list and "Northern City" as previously mentioned is currently there.  This last one confused me as I thought it referred to a branch of the Northern line but I see at https://en.wikipedia.org/wiki/Northern_City_Line
that it is something different.

Sorry, my comment on abbreviations wasn't a good example, I only meant to avoid your "hammersmith-city" values and use "Hammersmith & City".

Regarding bulk editing: for most purposes, it's important to use the normal editors in the normal manual fashion, it stops people getting into too much trouble and ensures every edit is checked not automated.  However I think I can see a way I could carefully edit this data without another 270 changesets once we're happy.
Aman Saraf (2020-09-16 17:47:23+00:00): Hey Cebderby,

Apologies !! I completely missed my email yesterday. I'll take a note of that.

Let me walk you through the motivation behind adding tflLine tag for Stations. 

1. While investigating the station schema of London Public Transport https://wiki.openstreetmap.org/wiki/London_public_transport_tagging_scheme#Station_or_tram_stop

I came to know that there's isn't anything called line key defined in the schema. Also, when I personally verified the presence of line in station node, the data was present for some nodes , while for other the data were missing. 

Hence, the first point for motivation was the data inconsistency & No official recommendation of line key.

2. Also, I thought of not changing the line key for existing nodes or add for the new nodes because of unclear motivation of it being there. If I would have edited or added info to line, it might have resulted in breaking change.

3. As mentioned by my colleague above, the tflLine is intended to provide the line code (id's) which is coming directly from TFL Official API's.

I sort of agree with you on naming conventions, such as use of semicolon, but use of english casing would not have made sense, because Id's has to be exact match. 

For ex:  in TFL, the line id of Northern Line is northern. We cannot simply put the id as Northern in OSM, because it is not a match.
Same for Hammersmith & City, in TFL the id for this line hammersmith-city

The benefit of having line id in OSM is that in future any person can use these id to communicate directly with TFL Api's and get more info if required. I personally think it's a great addition

Sorry, I didn't knew about the naming convention to be followed for tag key, because i couldn't find those conventions anywhere written. Maybe I might have missed those. 

Please let me know what you think about it. I hope it clears your doubt. Lets come to common ground to resolve this.
Cebderby (2020-09-16 22:13:33+00:00): Thanks for the reply Aman Saraf.  Sorry that my message yesterday was a bit abrupt, I was primarily hoping to stop you doing a lot of editing we may have had to undo.  But the added data seems very precise and consistent so I'm sure it will be useful however it ends up.
Yes, a lot of the choices in OSM are based on consensus and consistency not on any written rules.
For me the big choice now is whether you can happily use the data if we were to make it consistent with the existing OSM data, ie under key 'line' with semicolon separated names with upper case eg "Circle;Hammersmith & City" etc.  If so, I am prepared to move the data over (actually this can be done in little time).  Then we have merely made an existing tag have more complete and consistent data which is unconditionally a good thing.   But then your interface between OSM and TFL has to provide a mapping of identifiers (but perhaps this is exactly what the interface should do?).
Alternatively, if you really want to store more/different data in OSM then we can either just leave the data there and see if you get other feedback/questions/challenge to it, or can put a message onto the talk-gb mailing list and see what people think.  You guys would need to be ready to describe what extra benefit you'd get from having this data under a special key and with particular values, but I think the similarity with 'line' and using nearly-but-not-actual names would require some convincing argument.  There are tags for other systems' ids - eg wikidata and fhrs come to mind - but they tend to be reference numbers not nearly-the-names, and stored once on the object they map to/from.
Aman Saraf (2020-09-16 23:21:45+00:00): Thanks Cebderby for the prompt response. Yes I can guarantee about the consistency of the data added by me. However, if moving the data from tflLine to existing line can be done with a little effort, then I'm happy to pair up with you on this. It will be a great learning exercise. We can certainly change our system to adapt to new tag. 

Please let me know your availability. We can have a google meet for the same purpose. I am situated in India.
Cebderby (2020-09-17 00:04:05+00:00): No need, I have the data.  Can you have a look at changeset 91010652, I find this tool useful:
https://overpass-api.de/achavi/?changeset=91010652
If you look at changed dot markers, the tags are in alphabetical order so 'line' is near the top above 'name', not always highlighted if no change, the 'tflLine' down the bottom so you may have to click the dot and scroll down too see it, left=old, right=new obviously.
This contains 10 of the stations including some that had 'line', some where it wasn't there.  Any reason this wouldn't work for you if done for all?
Aman Saraf (2020-09-17 09:28:35+00:00): Yes, I saw the data and it looks perfect. This new change will work for us too. How are you bulk editing ? Is there some script which can be leveraged ?
Cebderby (2020-09-17 09:53:27+00:00): The tool http://overpass-turbo.eu/
is nice (but complicated!) for querying data, best thing is to start by running the wizard on something simple like railway=station.  Once you have a working query it's possible to hand edit the content. adding extra conditions on the line acts as a filter ie 'and' logic, adding extra lines (in the right places!)  is additive ie 'or' logic.
I was playing with various combinations of 
node["railway"="station"] ["station"="subway"] [!"tflLine"] ["line"]
where '!' means logical 'not', to see underground stations with or without line and/or tflLine (by adding one or both of those last two conditions with or without '!'s)

The other tool I used is JOSM which is an editor with all sorts of capabilities, and I did a certain amount of (careful, manual) text search-replace and cut and paste.
The most important thing with editing other than completely manually within an editor user interface is to follow what is intended in https://wiki.openstreetmap.org/wiki/How_We_Map
including the bottom-most link on automated edits - which this comes close to, but the important issue is that each change here has been manually checked - I've looked through (actually twice) a list of the data changes to ensure no surprises.  What's not allowed is to apply an automated process to data, check it for a few cases and then hope for the best with all the rest.

I'll apply the rest of the changes, I'll do it in a few chunks so each changeset is not too large, either spanning too large an area or numbers of stations.
Cebderby (2020-09-17 10:30:08+00:00): All done, actually used the normal JOSM upload command rather than the 'upload selected' I'd meant so all went in one go, but all is well. All the 'tflLine' is gone and looks like every station has 'line', any existing data that had comma separation was adjusted to semicolon so should be good to use.
Aman Saraf (2020-09-17 11:22:16+00:00): Thats a great piece of knowledge to know. Thanks a lot cebderby for all the help.
Aman Saraf (2020-09-17 11:24:57+00:00): Also, while doing the sanity in OSM, I found some London trams stop which uses tag public_transport = tram_stop, but in official documentation, public_transport=station tag should be used. 

Shall I go ahead and edit those tram stops. example is : https://www.openstreetmap.org/node/128665478

The official documentation is : https://wiki.openstreetmap.org/wiki/London_public_transport_tagging_scheme#Station_or_tram_stop
Cebderby (2020-09-17 12:14:21+00:00): NO  the node you indicate looks perfectly tagged.
I would start at:
https://wiki.openstreetmap.org/wiki/Public_transport
for information on public transport tagging.  

I do not know where that page you refer to has come from.  Looking at the history it seems to be the work of a single individual, before that a different? (or same with different account?) individual.

OSM has consistent mapping across the world, there should be nothing conflicting in any local advice, just expected standards or maybe making a choice if there are different possible ways of doing something.

I see a few some tram places mapped as if they were railway stations which I think is wrong.  It is my understanding that there should be a stop_position on the track.  There is no direct equivalent of railway=station for tram stopping places.
Aman Saraf (2020-09-17 12:52:45+00:00): Cool. Thanks for pointing that out. After reading the documentation shared by you, 

I came to following conclusion:
1. For all rail stops except trams: use railway=station

2. For trams/light rail = use railway=tram_stop

I'll modify my query then !
Aman Saraf (2020-09-18 10:33:41+00:00): Hey Cebderby, I think we should remove Northern City line from line key for some stations because Northern City line is not an underground line. 

Ex: https://www.openstreetmap.org/node/70804547
Cebderby (2020-09-18 11:37:00+00:00): NO, deleting existing data is not ok, the station serves both lines and is correctly labelled.  You've added underground lines and are currently interested in them, but that does not mean that they are the only lines.  I mentioned that there would be other values like Overground etc in the list in almost every comment I made.
Aman Saraf (2020-09-18 12:33:18+00:00): Okay Okay. Make sense !
user_5359 (2020-09-15 04:21:40+00:00): Hello, you have now destroyed all the changes that were made to OSM step by step. First you added keys that only you use, then you deleted the corrections you made. For an introduction, please read the page wiki.osm.org for example about the stadium https://wiki.openstreetmap.org/wiki/Tag:leisure%3Dstadium. 
I urgently ask you to restore your address details accordingly or to explain why you have to use your own keys.
dgitto (2020-09-16 08:57:21+00:00): You are using wrong tags:
"Coordenadas"
"Grado de protecciòn"
"Propietario"
cartomatto (2021-03-11 20:11:39+00:00): errato uso di waterway=canal che è un canale navigabile o un grande canale di irrigazioen (tipo canale cavour).
le bealere, e i canali irrigui coem questi sono ditch
lukasbrunner (2021-03-11 21:00:52+00:00): Grazie della segnalazione.
Duja (2020-09-15 08:18:59+00:00): Ovde treba malo poznavati lokalne prilike... Admin_level=10 su mesne zajednice, koje se negde poklapaju a negde ne sa stvarnim opštepoznatim gradskim četvrtima. U SD baš i ne odgovaraju... ja bih obrisao tvoje place=suburb. 
Btw, place=suburb bih koristio samo za baš velike delove grada kao što su beogradski. U manjim gradovima place=quarter bolje pasuje, ako ništa ono zbog renderinga.
Badojo (2020-09-15 10:52:00+00:00): Da, u biti slažem se ali mislim da bar neke zajednice poput Donjeg Grada i Zlatnog Brda jesu četvrti. Karađorđev Dud i 25. maj možda ipak nisu.
Duja (2020-09-15 11:37:29+00:00): Zlatno brdo je više brdo nego četvrt, tu bi pre išao place=locality. Od meni poznatih četvrti nedostaju Carina, Papazovac, Leštar, ali izgleda da tu nisu unete ni granice MZ. Nije mi poznato da Smederevci taj kraj zovu Donji Grad, to je prosto "Centar"... Nisam baš lokalac nego zet.. :)
Badojo (2020-09-15 11:40:09+00:00): Ja ću dodat granice mesne zajednice, a onda ću vidit kako ću sa četvrtima i kvartovima. Malo treba kopati po internetu
Duja (2020-09-25 11:27:46+00:00): Nego, da ne bude da samo kritikujem... hvala za ažuriranje. Ne mogu da verujem da niko nije uneo Sportski centar nekih 10 godina otkako je napravljen :(
Badojo (2020-09-25 11:29:45+00:00): A šta ćeš. Mapperi se samo bave najvećim gradovima. Smederevo je veliki grad ali očito ne dovoljno velik.
BrackoNe (2020-10-28 07:36:55+00:00): S druge strane, mi se na primer baš fokusiramo na mesta koja su mnogo manja od Smedereva, i to zaseoci. Pokušavamo da do svakog sela "doteramo" put i da do kraja sledeće godine nemamo nijedno selo koje nije povezano sa putnom mrežom.
OSM_RogerWilco (2020-09-16 08:54:21+00:00): Hallo stephanholldorf,
willkommen bei OSM und vielen Dank für Deine Mitarbeit!
Sehr gut ist, dass Du den Weg nicht einfach gelöscht hast, sondern den Weg korrekt mit access=private getaggt hast.
Viele Grüße
Roger Wilco
eggie (2020-09-14 19:28:37+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privébericht.
MVG,
Eggie
Carnildo (2020-09-15 08:23:47+00:00): Could you be a bit more careful with your editing?  You keep attaching things to the Gas Transmissions Northwest pipeline, and it makes it look like you're scattering your edits across the entire Idaho Panhandle.
deven_smith_ (2020-09-15 15:56:13+00:00): I attached the area boundaries to the pipeline because that is where their property line sat on, though I will be more careful and I'll try to place the corner points right next to the pipeline(s) instead of attaching
Carnildo (2020-09-15 21:11:31+00:00): Running the boundary up to the pipeline is fine, but you should only attach things to each other if they're actually attached.  For example, landuse to landuse is fine, as is connecting two buildings that share a common wall.  Connecting unrelated things such as a building and a neighboring forest can make it harder to update the map when things change.  Connecting objects that aren't physically adjacent, such as an industrial area and a pipeline running under it, can cause confusion -- software analyzing the map data might conclude that the industrial area is related to the pipeline.

A useful technique when mapping objects that are close together is to hold down the "Alt" (Windows and Linux) or "Option" (Mac) key.  This keeps the editor from connecting things to each other when you don't want it to.
abakus_uploader (2020-09-14 22:31:18+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!
Leo Slager (2020-09-15 10:27:03+00:00): Dat is een mooi aantal foutmeldingen wat je achterlaat. Zoals je ziet bij de meest W lijnen, is het niet de bedoeling die lijnen op elkaar te plakken.
Inmiddels heb ik de NO lijnen gerepareerd.
Wordt vervolgd.
http://tools.geofabrik.de/osmi/?view=geometry&lon=4.68658&lat=52.32084&zoom=15&opacity=0.76
BCNorwich (2020-09-15 06:36:44+00:00): Hi, Welcome to OpenStreetMap.

I don't think this change worked out as you intended, it dragged a fence and woods line out of alignment. I've reverted the change so there's no harm done. Need help please just ask.

Regards Bernard.
skquinn (2020-09-14 23:17:58+00:00): Please don't make changes this far apart in the same changeset, i.e. save after editing China before editing in the US again (or vice versa).
BCNorwich (2020-09-15 06:50:52+00:00): Hi, I squared up the buildings to make them neater, tweaked/corrected  a few. More than one house in a building then it can be tagged building=residential, either that or terrace the building.

Regards Bernard.
Carnildo (2020-09-15 02:42:45+00:00): Bigelow Gulch wasn't physically divided at the Argonne interchange when I drove through a couple weeks back, but it did have a two-way center-turn lane.  Why have you mapped it as a divided road without a center-turn lane?
deven_smith_ (2020-09-15 16:01:49+00:00): I changed it because I thought, and you can explain why I am wrong, it made more sense with the rest of the Bigelow Gulch projects that the road should be marked divided.
Carnildo (2020-09-15 23:13:21+00:00): Mapping a road as divided should generally only be done when it's physically divided.  There are some exceptions (for example, if the road is *legally* divided by having four yellow stripes down the middle, and is an extension of a physically-divided road, such as with Sunset Highway approaching Airway Heights).

The Argonne interchange is very much not one of those exceptions: not only is it not physically divided, mapping it as divided prevents mapping useful information such as turn lanes.
jaap de vries (2021-02-11 09:58:03+00:00): Ik zie dat je een monument hebt toegevoegd in het Elsenburger bos, ter plaatse heb ik niks kunnen ontdekken. Bedoel je geen snelweg monumentje?
The_ABM (2021-02-12 11:11:37+00:00): ter plekke is er een BMX baan in het bos, toen ik de tag deed wist ik niet welk ik moest kiezen en daarna ben ik er van vergeten.

hier zie je een paar van de ban heuvels tussen de bomen.

https://www.google.com/maps/@52.0355289,4.3354407,3a,15y,105.14h,89.44t/data=!3m6!1e1!3m4!1sBhqOpyHC1yyb7ndHGfCnTQ!2e0!7i16384!8i8192?hl=en
jaap de vries (2021-02-16 07:39:44+00:00): De bxm baan ken ik wel, nu staat er een tag voor monument dus totaal wat anders. Als je iets niet weet is een opmerking op de kaart beter dan zomaar iets neerzetten. Ik zal e.e.a. aanpassen.
VictorIE (2025-06-10 08:03:24+00:00): Hi,

https://www.openstreetmap.org/way/362301802/

These little towers in mid-20th century primary schools are water towers - because architects preferred to add a water tower than work out the plumbing properly.
naveenpf (2020-09-16 00:48:01+00:00): Welcome to OSM Kerala.
https://wiki.openstreetmap.org/wiki/Kerala/Members

To join OSM Kerala Telegram click on. 
https://t.me/osmkerala
            ---
            #REVIEWED_GOOD #OSMCHA
            Published using OSMCha: https://osmcha.org/changesets/90880316
Ze0zohk1 (2021-01-01 08:41:24+00:00): Hallo Karthoo,

ich bin über diese beiden Wege gestolpert: https://www.openstreetmap.org/way/847260171
https://www.openstreetmap.org/way/847260170

Was soll highway=garage bedeuten? Meinst du vielleicht highway=service?

Viele Grüße und ein frohes Neues
Karthoo (2021-01-01 14:57:26+00:00): Danke, da hab ich wohl nicht ganz aufgepasst. Klar, das soll natürlich highway=service sein. Habe es gleich korrigiert.

Grüße und ein gutes Neues!
skquinn (2020-09-14 23:58:48+00:00): I was under the impression direction was optional on traffic controls on one-way roads (i.e. that it was implied since traffic only moves in one direction). Am I mistaken?
afdreher (2020-09-15 00:01:50+00:00): I would certainly assume so; mostly I was just adding it for the sake of the renderer so that it would properly visualize the stop direction.
nlme (2020-09-14 18:47:39+00:00): Hey there - there's already a node for this restaurant at 746719446.
pangoSE (2020-12-02 14:54:01+00:00): hej, skulle du kunna alltid lämna nån kommentar? Det gör det mycket enklare att genomse ditt arbete. På förhand tack.
UT93 (2020-11-10 00:36:36+00:00): Grüsse.
Bist du dir sicher, dass die Treppe https://www.openstreetmap.org/way/847263483 auch wirklich existent ist?
Tungmar (2020-11-10 06:04:02+00:00): Hello,
I passed by and saw it. What I could think of is that I put the note on a wrong place, but I currentli assume it is corroect. Where you there and didn't find it?
eggie (2020-09-14 19:41:22+00:00): Beste medemapper.. het gebied van je edits is veel te groot. Je negeert elke aanwijzing. Je edits zijn nauwelijks te controleren.

Graag reactie .. dan kunnen we helpen om op de juiste manier te mappen.
MVG,
Eggie
eggie (2020-09-14 19:57:39+00:00): reverted by changeset #90883824
due ignoring advice to decrease his mapping area.
ChristianA (2020-10-13 08:36:55+00:00): "height=q" är nog fel antar jag?
Mvh
red- (2020-10-13 09:17:44+00:00): Absolut! Fixar det.