piebro/osm-data huggingface dataset:
Warin61 (2021-08-03 09:45:25+00:00): HI,
Why is this a multipolygon??? 
Relation 13044704. 

Note multipolygons outer ways cannot share segments ... see https://tools.geofabrik.de/osmi/?view=areas&lon=151.07679&lat=-33.92438&zoom=18
jogemu (2021-08-05 20:14:42+00:00): Hi,
thank you, that was not what I wanted to do, I corrected it in Changeset 108985753. I tried to outsmart iD and it backfired. I drew two buildings together and didn't want to draw both again therefore I deleted building=yes so that I can split the way and then close both before I retag them as buildings. Unfortunately when you use the wrong order of those steps iD wants to assist you by creating a relation but doesn't indicate it clear enough. Therefore I should use the JOSM tool that can split buildings along a line.

It is always good to know that someone notices my mistakes. It sometimes feels like no one notices/appreciates my changes even though I add hundreds of buildings in some of my changesets. Feel free to tell me if you notice a third relation like that. I can't rule it out that I made the mistake more than twice from what I remember.
Warin61 (2021-08-06 07:52:00+00:00): The reason why I notice is because I make similar errors and use the QA tool I linked to above. I find by monitoring the QA tool is a fairly easy way of helping new mappers ... and fixing errors. I must have made lots of errors when I first started and others fixed them, sometimes letting me know of the error sometimes not. While simply fixing the error is quick for me it may mean the same error is repeated again and again .. which is not good.
jczaplew (2021-09-27 21:44:24+00:00): Why did you delete the ski trail?
BCNorwich (2021-08-04 08:20:09+00:00): Hello and Welcome to OpenStreetMap.

Unfortunately, your mapping has resulted in many paths being duplicated. Your new paths are placed mainly on top of existing paths and roads. Even the path along the beach is duplicated. Thus because the changes and duplicated ways amend other existing ways I think it's best to revert the whole changeset.  I've reverted the changeset in my Changeset: 109131669.

I realise the problems were caused inadvertently.  Could you please explain what you were trying to do, maybe I can help.

Regards Bernard
mytrails92 (2021-08-01 19:47:29+00:00): adding Dry Cottonwood Creek
Nonexhudlix (2021-08-08 14:47:56+00:00): Bitte nicht "umgezogen nach Schillerstaße 9" als Teil des Namens ... :-( :-(
OSM_RogerWilco (2023-03-23 20:40:10+00:00): Moin Romwriter,

Du hast hier Mini-Kreisverkehre (highway=mini_roundabout) eingetragen, die keine sind. mini_roundabout bitte nur für echte Kreisverkehre verwenden.

https://wiki.openstreetmap.org/wiki/DE:Tag:highway%3Dmini_roundabout

Viele Grüße
Roger Wilco
Romwriter (2023-03-23 20:57:28+00:00): Ja, stimmt, das sind Kreuzungen mit einer überfahrbaren Mittelinsel ohne Verkehrszeichen 215.
rab (2021-08-01 21:29:38+00:00): https://www.openstreetmap.org/search?query=Chreso university

not mapped yet?
mueschel (2021-08-07 10:54:37+00:00): Hi,
what does 'Mooring = trot' mean? This looks like a mistake, especially on top of a mountain.
Warin61 (2021-08-03 09:47:49+00:00): Hi
Why a multipolygon? Relation 13044876.

Note multipolygons outer ways cannot share segments ... see https://tools.geofabrik.de/osmi/?view=areas&lon=151.07397&lat=-33.92582&zoom=18
jogemu (2021-08-05 20:16:15+00:00): Hi, thank you, I explained why I made that mistake and how I corrected it in changeset 108985753.
Lee Carré (2021-09-02 16:31:31+00:00): See (also) note #2766493
k127 (2021-08-02 09:47:45+00:00): So, hier dein gewünschtes Review:

Auch wenn das Installieren einer Einbauküche einen oft zweifeln lässt – wir können hier annehmen, dass die Gebäudeumrisse rechtwinklig sind.

Für den verwendeten Editor „iD“ bedeutet das:
„zum Erzeugen rechtwinkliger Ecken (auf Englisch Tastenkürzel „q“) verwenden“ [1]

Mahlzeit!

[1] https://learnosm.org/de/hot-tips/tracing-rectangular-buildings/#die-grundlagen
user_2066394 (2021-08-01 21:40:48+00:00): Ist da aktuell Baustelle?
pater23 (2021-08-02 13:30:40+00:00): nein, Brache, aber wird wohl bald bebaut
user_2066394 (2021-08-02 14:54:57+00:00): Für die Übergangszeit könnte man das Gebäude mit
demolished:building=yes
oder die Fläche mit
landuse=brownfield
eintragen. Dann bleibt der Ort nachvollziehbar, solange das Gebäude noch in den Luftbildern sichtbar ist.
https://wiki.openstreetmap.org/wiki/DE:Lifecycle_prefix
https://wiki.openstreetmap.org/wiki/DE:Tag:landuse%3Dbrownfield
pater23 (2021-08-02 14:59:52+00:00): demolished:building=yes
hinzugefügt
user_2066394 (2021-08-01 21:47:00+00:00): Hausnummer 8 ist jetzt zweimal eingetragen, einmal auf dem Umriss und einmal auf dem Knoten.
Damit ergibt sich ein Duplikat.
k127 (2021-08-01 22:11:40+00:00): Pater, da hat er recht, der wurzelast.
Ich würd die Hausnr. an Gebäudegeometrie lassen und an dem Punkt auf dem Umriss statt der Adresse nur den Eingang angeben.
pater23 (2021-08-02 13:42:32+00:00): ja eh, erledigt
Allison P (2021-11-15 05:51:25+00:00): Code Ninjas is spelled as two words. I don't think amenity=school is an appropriate tag for it either.
h551w (2021-11-17 03:50:08+00:00): Yeah, I wasn't entirely sure on its tagging, so I just chose what seemed to be one of the closer options. Definitely feel free to update it to a more correct tagging
user_2066394 (2021-08-01 21:49:31+00:00): Hausnummer 80 ist jetzt zweimal eingetragen, einmal auf dem Umriss und einmal auf dem Knoten.
Damit ergibt sich ein Duplikat.
maraf24 (2022-09-18 16:09:32+00:00): Nie istnieje.
Poza tym - nie w tym miejscu.
tenzul (2021-08-02 09:23:27+00:00): OSMcha shows an invalid tag modification on the Oberamt building. However the iD editor and JOSM are not giving me any hints on whats wrong with it. I will happily fix this, if someone could tell me what's the problem.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/108987838
ALu68 (2021-08-02 07:48:41+00:00): Read the wiki first!

Just using the key building:levels alone is not enough.

https://wiki.openstreetmap.org/wiki/Key:building:levels "Requires
building=*"

https://wiki.openstreetmap.org/wiki/Key:building

Good changeset comments:
http://wiki.osm.org/wiki/Good_changeset_comments
BubbaJuice (2021-08-01 21:16:12+00:00): *On site map
Frans S (2021-08-28 13:35:26+00:00): Thank you for mapping. You have correctly identified the location of most buildings and accurate mapped
Please do not connect nodes of a building to highways.
Be sure that all rectangular buildings are good squared
Reviewed by a validator at random or as requested. 
Best regards and keep mapping
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/108988088
mueschel (2021-08-07 10:44:12+00:00): Hi,
could you check two bus stops, they got a strange tag:
"po_trebovaniyu"

https://www.openstreetmap.org/node/6343201009
and the adjacent one
d1sr4n (2021-08-08 22:34:35+00:00): Hi, mueschel ! 

Fixed it. Thank you for a hint. 
https://www.openstreetmap.org/changeset/109365865
Nico85 (2021-08-28 09:48:50+00:00): Kebab for Friends war bereits korrekt gemappt (35a, neben Tchibo). Doppelten Eintrag gelöscht. Siehe https://www.openstreetmap.org/changeset/110373090
user_5359 (2022-02-10 21:11:05+00:00): Welcome to OSM! I have revert your SEO SPAM (mostly no standard keys, no verifiable data, not positive verifiable address data, destroying data). If this is an error, you can report it here, then we will be happy to help restore the data. For the most information in the description we have own keys. Please have look on the website http://wiki.openstreetmap.org.
user_5359 (2022-02-12 13:17:58+00:00): Nach Abklärung durch Mailwechsel wurde die Information korrigiert eingetragen.
mueschel (2021-08-04 07:10:06+00:00): Hi,
welcome to OSM!
I see that you used many tags here that are not used in any other place, like:

    distribuition=unilateral
    light overhang=2 m
    luminaires per pole=1
    pole distance=18,67 m
    roadway width=8,05 m
    sidewalk 1 (where the post is located)=0 m
    sidewalk 2=2,17 m

This might be a good description of the object,
but is not usable in OSM - no software can understand it. 
Please use only tags that are described in the OSM Wiki or are available in the presets of your editor.
eggie (2021-08-18 18:54:16+00:00): Dag Tuffmoor  Je 'aangepast' hield in het verwijderen van alle landuse.
De landuse heb ik weer hersteld.

MVG
eggie
ivanbranco (2021-08-14 08:44:53+00:00): Hi ypaseopor,

I don't understand why you put 2020 in this node tags: https://www.openstreetmap.org/node/3130176633
yopaseopor (2021-08-14 09:29:14+00:00): I use the date_namespace suffix as keyname as you can see in https://wiki.openstreetmap.org/wiki/Comparison_of_life_cycle_concepts#Date_namespace_suffix_as_.22keyname:DATESPEC.3D...22
For topics of accessibility it will be interesting the comparison before and after of the location and number of disabled parking spaces.
G_P_J (2021-08-04 09:00:07+00:00): Cześć, w jakim celu skracasz nazwę tej ulicy? Sądząc po historii robisz to ponownie. Konwencja nazw ulic w polskim OSM zakłada rozwinięcie imion, mimo, że nie występują w nazwach oficjalnych. Oficjalną nazwę można umieścić w znacznikach official_name lub short_name. Pozdrawiam, Piotr
camoluigi (2021-08-04 09:46:47+00:00): Witam, słyszałem o tym w jednym z filmików na OpenStreetMap Polska żeby nie tworzyć takich długich nazw ulic i w całej gminie Zawadzkie je poskracałem rok temu. Myślałem, że tą ulice przeoczyłem i ją poprawiłem. Może coś źle zrozumiałem albo zmieniły się zasady, że znowu się tworzy takie długie nazwy ?
G_P_J (2021-08-04 10:45:26+00:00): Raczej chodziło o innego rodzaju długi nazwy. Imona zostawiamy. Poprawię tę ulicę.
camoluigi (2021-08-04 15:32:58+00:00): Ja zrozumiałem to inaczej właśnie żeby pisać tak jak jest w rzeczywistości, a nie pisać tak długich nazw z imionami. Muszę poszukać ten filmik na YouTube, bo tak chyba 20 ulic zmieniłem w mojej gminie. Pozdrawiam.
camoluigi (2021-08-04 15:51:35+00:00): Dobrze że ktoś czuwa tu rejonie nad zmianami, bo już myślałem, że jestem sam. W tej okolicy mało kto wprowadza jakieś zmiany i nowości :)
G_P_J (2021-08-05 09:07:02+00:00): Od początku roku staram się poprawiać tzw. "mrówki" w całej Polsce. Ta stronka: http://v3.mrowka.org/adresy/ pokazuje błędy w adresacji i brak dróg dojazdowych do posesji. Śledząc zmiany na bieżąco dość łatwo można wychwycić  nowe nieprawidłowości w nazewnictwie ulic. Np. zmianę nazwy ulicy bez zmiany tej nazwy w punktach adresowych. Likwiduję stare błędy, ale w przypadku pojawienia się nowych weryfikuję również jaka jest ich przyczyna. W ten sposób znalazłem Twoją zmianę. Miłego mapowania :) Piotr
user_12625593 (2021-08-13 18:50:54+00:00): En voor deze geldt hetzelfde, zie wederom mijn eerste reactie.
marczoutendijk (2021-08-18 18:02:06+00:00): Deze changeset is door DWG-revert https://www.openstreetmap.org/changeset/109889647
ongedaan gemaakt.
Reden: zeer voorbarige aanpassingen van de kaart.

Marc Zoutendijk
OpenStreetMap Foundation
Data Working Group
user_12625593 (2021-08-13 18:08:14+00:00): Ook deze wijzigingen horen niet in OpenStreetMap, zie mijn andere reactie.
marczoutendijk (2021-08-18 18:00:32+00:00): Deze changeset is door DWG-revert https://www.openstreetmap.org/changeset/109889607
ongedaan gemaakt.
Reden: zeer voorbarige aanpassingen van de kaart.

Marc Zoutendijk
OpenStreetMap Foundation
Data Working Group
user_12625593 (2021-08-13 18:01:45+00:00): Beste Tuffmoor, toekomstplannen van de Efteling horen niet in OpenStreetMap te staan zolang ze nog niet gerealiseerd worden/zijn. Daarom verzoek ik je vriendelijk deze wijzigingen ongedaan te maken. Mvg, oposm
marczoutendijk (2021-08-18 17:58:15+00:00): Deze changeset is door DWG-revert https://www.openstreetmap.org/changeset/109889531
ongedaan gemaakt.
Reden: zeer voorbarige aanpassingen van de kaart.
 
Marc Zoutendijk  
OpenStreetMap Foundation  
Data Working Group
tenzul (2021-08-02 09:35:58+00:00): Hey Sergei,
the Lidl supermarket was already tagged. You added a new node, so now there are two for the same supermarket. Can you take back you node?
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/108989874
iandees (2021-08-02 23:26:53+00:00): Please try your hardest to improve the existing features rather than delete and start fresh. Deleting other people's work isn't very friendly to your fellow mappers.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/108989904
amen0037 (2021-08-03 15:04:20+00:00): Almost all of it was wrong and would have taken more time to edit. As the property manager I know exactly where everything should be located on the map. The next step is tagging individual trees to the exact spot and species. Sorry if I deleted your stuff but it was not correct
Lee Carré (2021-08-02 22:48:40+00:00): What makes for http://wiki.osm.org/wiki/Good_changeset_comments 😉.

Also, smaller changeset areas, please.
user_13857586 (2021-08-01 23:54:13+00:00): To zmień na lane, a nie moją pracę niszczysz
Yunkers (2021-08-02 05:14:19+00:00): "Moją pracę niszczysz"? Multikonta zaczynają ci się mieszać, cheetah wycofywał zmianę użytkownika :DD.
cheatach (2021-08-02 10:55:43+00:00): on wie, że my wiemy, że to są wszystko jego multikonta i na bezczela sobie nimi żongluje, chyba myśli że jest przez to większym kozakiem xD
Lee Carré (2021-08-02 22:49:59+00:00): All these pan-Atlantic ways were surveyed for sidewalks?
TobiasSpeedy (2021-08-03 14:34:38+00:00): Yes. Not on the same day obviously, but I walked these places.
Lee Carré (2021-08-04 00:46:52+00:00): Fair enough, then 🙂. Thankyou for your contributions.

My caution comes from having seen a couple instances, recently, of contributors using StreetComplete, yet in a way which cast significant doubt on the source=survey being entirely truthful. One example: within 30 minutes the same mapper changing something in Germany & Spain. I don't think even a charter flight would be that fast.
TobiasSpeedy (2021-08-04 01:11:22+00:00): I think with StreetComplete one has some implicit expectation that it's being used while walking around live. But you can also use it for normal editing of areas you have been to (recently enough to say that there is a sidewalk). And getting points for that motivated me to look at all places where I know for sure about sidewalks, etc, because I've been there ;) This might be similar for other people. But you are right, streetcomplete sets source=survey. Some people might use other sources.
Lee Carré (2021-08-05 16:41:44+00:00): “expectation that [StreetComplete i]s being used while walking around live”

To my understanding that's how it's intended to be used. That's what source=survey means.

Hence the warnings which SC gives when detected location differs from the element by more than a few metres.

One of the core characteristics (principles?) of OSM is local knowledge (from locals, rather than corporate employees in a far-away armchair making dubious assumptions).

“editing of areas you have been to (recently enough to say that there is a sidewalk)”

While possible, the risk is that the date (of check_date, when the element was last modified, or of the changeset itself) won't match the date of the actual survey.
However, this is avoided if the likes of a ‘does this feature still exist’ quest is answered at the time, since SC will use the date when answered, even if the change is uploaded much later.

There was an example, in my local area, recently, of a amenity=bicycle_parking being changed (apparently to become covered=yes) since I added a note.

For such cases, using an editor which allowed setting source to “local knowledge” and any date-related tags (check_date (and derivatives), survey:date) to match when the observations were made, would be much clearer to avoid any possibility of misleading others.

Besides, while you might be diligent in only using SC for elements which you've surveyed, others ignore the warning messages. It's difficult for others to determine (for purposes of validation & verification) which is which; for large bounding boxes, there's only the mapper's word that they did survey. Whereas, the pattern of clearly-genuine use is different (small areas, uploading batches of no more than a day's worth of changes).

Though, yes, there are exceptions, such as when travelling.

Hence asking.

Even with the best of intentions, it's too easy to slip into marking guesswork as factual. Handling & indicating uncertainty is an important part of a collaborative project which aims to produce accurate data.

“getting points for that motivated me to look at all places where I know for sure about sidewalks, etc, because I've been there 😉 This might be similar for other people.”

Understandable. I can relate, since I too started with StreetComplete (in offline-mode, before I even opened an account; hence my initial changesets are not small). Though, we seem to differ in motivation.

But, constructive improvements are helpful regardless of motivation. So, happy mapping 🙂.
Nonexhudlix (2021-08-07 05:47:27+00:00): Hallo, warum sind denn Blumenstraße und Stuttgarter Straße jetzt keine Einbahnstraße mehr?
Ich nehme an das ist nicht absichtlich.
Falls doch, bitte solche wichtigen Änderungen in der Beschreibung des Changesets aufführen.
Falls nein, bitte bitte pass besser auf dass nicht wieder bestehende Einträge überschrieben werden wenn Du etwas änderst.
ticki_52 (2021-08-07 07:03:30+00:00): Hallo Mad Max,

beim Aktualisieren und Abspeichern der Haltepunkte werden im JOSM "Ungereimheiten" festgestellt, die behoben werden sollen. So wurde bei der Blumenstraße vom JOSM beanstandet, dass es nur lanes in einer Richtung gibt und das mit oneway=yes in die selbe Richtung quasi doppelt getaggt ist. Ist diese Fehlermeldung falsch?

Grüße ticki_52
Nonexhudlix (2021-08-08 09:19:44+00:00): Die Warnung bezieht sich nicht auf das oneway tag, sondern wahrscheinlich darauf dass Du trotz oneway=yes die Spuren als lanes:forward angegeben hast. Das ist redundant, bei Einbahnstraßen ist lanes=<number> ausreichend (und sinnvoller), siehe auch https://wiki.openstreetmap.org/wiki/DE:Key:lanes
Nonexhudlix (2021-08-08 09:22:46+00:00): Übrigens haben wir das gestern auch im OSM D-A-CH Forum diskutiert, einhellige Meinung war dass lanes=xx nicht oneway=yes erstezen kann.
ticki_52 (2021-08-08 10:31:04+00:00): Hallo Map Max,

sorry für das "Mad". Das war wirklich keine Absicht....

"dass lanes=xx nicht oneway=yes ersetzen" Da stimme ich inzwischen nach etwas Nachdenken in Ruhe ;-) zu.  "lanes=n", "lanes:forward/backward=n" und "turn:lanes:forward/backward=x" ist aber auch bei Einbahnstraßen (EBS) verlangt, wenn die EBS mehrspurig ist und die lanes am Ende der EBS in verschiedene Richtungen verzweigen. Oder? 

Sonntägliche Grüße ticki_52
ticki_52 (2021-08-08 11:43:15+00:00): Hallo Mo Max,
hier mal ein Beispiel für eine "Warnung"im JOSM:
Verdächtige Merkmalskombination - oneway=yes zusammen mit destination:forward
Hier die Merkmale des "verdächtigen Abschnitts"
destination:forward=Tübingen;Reutlingen;Metzingen;Neuffen
highway=primary
lanes=2
maxspeed=50
name=Neckarstraße
oneway=yes
ref=B 313
surface=asphalt
Was tun? Warnung nicht beachten oder....?

Gruß ticki_52
Nonexhudlix (2021-08-08 14:00:46+00:00): Das problem ist der Suffix xxx:forward. Bei einer Einbahnstraße macht der keinen Sinn.

Deswegen solltest Du bei Deinem Beispiel destination:forward durch destination ersetzen, dann ist die Warnung auch weg. Ebenso hier, in der Stuttgarter Straße und in der Blumenstraße lanes:forward durch lanes ersetzen.
user_13857586 (2021-08-02 00:20:50+00:00): Usuwasz w pełni poprawne zmiany, pozwoliłem sb je zrevertować :)
Supaplex (2021-08-02 02:21:49+00:00): 可以加上 old_name 放舊名稱
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/108990957
zluuzki (2021-08-22 17:55:47+00:00): Are you really sure that https://www.openstreetmap.org/way/160578487 is still used? At the Bing and Esri imagery it is clearly very stongly overgrown. (Esri should be the newest)
For me, it looks like the Parrish Spur (https://www.openstreetmap.org/relation/12698664) is divided in three parts:
Part 1 is used by CSX and goes from the junction in Palmetto to one last customer in Moorehead Ind. Park.
Part 2 goes from Moorehead Ind. Park to the RR museum in Parrish. This part is out of service.
And part 3 goes from Parrish to the RR Museum in Willow, where the track ends. It is used by the museum for excursion/hertiage trains. The Spur to Manatee P. Plant is used to store old passenger cars, not to bring stuff to the power plant, if i see this correctly.
Or am i wrong here?
zluuzki (2021-09-17 12:27:05+00:00): ?
lonvia (2022-04-09 13:08:25+00:00): Hi, I see that you have added postcodes to village places in this changeset. May I ask what the source for this is? Background is that I'm trying to figure out what the official format for postcodes in Niger is. Niger post only lists 4-digit postcodes while you've entered 8-digit numbers. So I wonder where they are from.
Johnwhelan (2022-04-09 13:16:02+00:00): Try looking at the history of the village to see who made the change.  To the best of my knowledge I haven't added any postcodes.
neuhausr (2021-08-02 15:40:06+00:00): Hi and welcome to OpenStreetMap! Thanks for putting work into editing the Hiawatha Golf Course. However, I'm wondering if you saw the golf course page on the OSM Wiki, which has some guidelines and best practices? https://wiki.openstreetmap.org/wiki/Tag:leisure%3Dgolf_course I ask because some of your edits don't seem to follow the tagging guidelines there. For example, using the "ref" tag for hole numbers, without the "#", instead of "name" tag. I know some of the golf tagging does not display on the standard OSM map right now, but it's being worked on. And it's most important that the data be correct, not that things display on that map a certain way. To show what the proper tagging can look like, this French map does a nice job rendering golf course tags: http://tile.openstreetmap.fr/?zoom=16&lat=48.72648&lon=2.60806  Hope you have a chance to take a look at the wiki. Happy mapping!
amen0037 (2021-08-03 14:59:57+00:00): I'll look into it. As the property manager I moved everything to where it needed to be regarding many changes that have been made to the property. Everything is less than a foot from where it should be
neuhausr (2021-08-03 16:27:39+00:00): Great--do you work for the MPRB? Either way, if you're bringing outside data into OSM, make sure it's compatible with OSM's license :) Info at the Imports wiki page: https://wiki.openstreetmap.org/wiki/Import
user_5359 (2021-08-02 18:52:40+00:00): Hello! Why did you add the key NAME and why has this key an other value like the key name?

see https://www.openstreetmap.org/way/271047799
doug_sfba (2021-08-02 21:20:27+00:00): Good questions (all three)
1. Table Bluffs: Agreed. Superfluous NAME tag removed
2. Mike Thompson WA: Name used to be "South Spit WA". CDFW still use that name in their GIS data, so the NAME= tag from GIS metadata was imported to document that old name.
3. Headwaters Forest Reserve: Disagreement between BLM (founders) and CDFW (operators). BLM called it a "Forest Reserve". Later, CDFW changed it to "Ecological Forest Reserve", but the name didn't stick. Everyone uses the simpler BLM name (Taken for the OSM name= tag). CDFW uses it's newer name in GIS data and website, so the CDFW NAME= was imported for documentation. I added a note= for clarification
DUGA (2021-10-27 23:00:14+00:00): Great Seneca Crk does not look like that,

https://www.openstreetmap.org/way/969664619#map=16/39.1926/-77.2126

Source: USGS
ElliottPlack (2021-10-28 15:25:57+00:00): Yes, rivers do change over time. The original shape was imported as a census designated place boundary, thus why I'd adjusted it in this changeset. Your revision looks fine though, just don't break the relations.
user_5359 (2021-08-02 18:53:06+00:00): Hello! Why did you add the key NAME and why has this key an other value like the key name?

see https://www.openstreetmap.org/way/271047818/history
user_5359 (2021-08-02 18:54:02+00:00): see also https://www.openstreetmap.org/relation/6190202/history