Hi there - actually, if the rail right-of-way is unidentifiable and completely wiped off the map (for instance, where Safeco Field currently sits) it should actually remain as "razed". An "abandoned" stretch of track would indicate that you can easily trace the right-of-way on the ground or from the air.
---

Published using OSMCha: https://osmcha.org/changesets/86712220

Welcome to OSM! Let me know if you have questions or problems - I'll gladly lend a hand!
I'm local - live in Duvall, formerly lived in Redmond. Great to see more local mappers!
---

Published using OSMCha: https://osmcha.org/changesets/86646894

Where is this landuse data coming from, and how old is it? It doesn't look very current - showing built-up parts of Butembo as "grassland".

Thank you for spotting that!

Also - as this is not a reciprocal boundary, it is not administrative, but rather political.
I'm sure it looks way rad to see CHAZ outlined as a separate country, that's not grounded in reality.
I'll be reverting the changes to the outer perimeter.

You don't set tags for the boundary - tags are edited within the relation.

Yes yes I know we don't map "temporary" features and POIs. However, I firmly feel that this situation meets the "next few weeks" standard in the Good Practice article. I don't see this being resolved anytime soon.

Oh wow... that's too bad about Telido Station. I thought it was pretty cool that they were keeping a historic name going.

That's not a very good ratio on the Spokane Co named places. Let me know if you want a hand with any of the railroad-related ones, since that's where a lot of my Spokane Co history knowledge lies.

Also - do you find that the "disused:name" tag is widely accepted as a way of labeling placenames that are no longer in use?

Apologies for the snark. After thinking about it, I'm sure I would have come to the same conclusion as you did, and assumed I was trying to map a survey marker as a place.

Didn't get that from a topo, and yes it at least used to be an inhabited place.
As I recall, someone had deleted the old "Tolido" placename so I recreated it and merged it with a Salish placename that was right next to the survey marker. Yeah I shouldn't have merged them.
Tolido was a railroad station on the Spokane-Cd'A interurban: it was the transfer station (until around 1930) for those wanting to take the train to Liberty Lake, and it was still used as a placename (between Greenacres and Lib Lake) on plat maps at least into the 70's.
http://www.gn-npjointarchive.org/GN_Spokane_Couer_d_Alene_and_Palouse_Maps_V1/SCP%20WA%20V1-07a%20Greenacres%20Tolido.pdf
http://www.gn-npjointarchive.org/GN_Spokane_Couer_d_Alene_and_Palouse_Maps_V1/SCP%20WA%20V1-07%20Tolido%20Liberty%20Lake.pdf
It was often misspelled "Telido" - and in fact there's a corresponding commercial+residential development called "Telido Station".
https://metrospokane.typepad.com/.shared/image.html?/photos/uncategorized/2008/06/17/telido_station.gif

No... the Salish placename shouldn't have been an isolated dwelling, but at least I knocked it down from hamlet.

In case you didn't notice, this change was from almost 3 years ago, in my first year of mapping for OSM.
I wonder what kind of crap map changes I would find if I looked at YOUR changesets from your first year of mapping? >:)

So please let me know if you see anything else I may have screwed up.

Thx for catching that - I fixed it. My notes from last summer are absolute crap. :(

I'll be honest - I meant to change it to unpaved. When I went there last Summer almost all of it was graveled, with an ungraveled bit in the middle.

1. Agreed, it's ridiculous that Tyler and Fishtrap should render the same - Fishtrap is not even remotely a hamlet. However, Fishtrap is a perfect example of what should be classed as an "isolated dwelling". It has its own freeway exit; it has a namesake lake, a namesake rec area, a railroad placename and associated siding, and by god it even has a few buildings. Back in the days of the phone book, Fishtrap even had its own white pages section in the Spokane directory. Granted, it was only two or three entries... so I acknowledge it's an edge case.
2. The OSM maxim "Don't map for the renderer" should be updated to "Don't map for the renderer, nor the geocoder". I have no strong opinions about any other geocoders, but Nominatim is a piece of poo. Its inability to perform a zipcode query on a placename, and return the correct USPS-defined placename for that zipcode is inexcusable. I can easily google that info, why can't a geocoder?
3. Well that has nothing to do with this. Misinformed armchair mappers will always screw things up - doesn't matter if a place is marked as a hamlet or locality.

All in all, I think we're on the same side here. I just believe in the hierarchical nature of place-naming: if you take the Babb siding west of Cheney and compare it to Fishtrap, I strongly believe those 2 are not at the same hierarchical level - Babb is nothing, and Fishtrap is a very tiny *something*.
But... I really don't want to get into an edit war, so I'm willing to downgrade Fishtrap to a locality if you feel that strongly about it.

Agreed that most of these "hamlets" are not, but if there are industrial or commercial buildings still present, it's more appropriate to not downgrade all the way to "locality". The "isolated dwelling" tag is not literal - imo it's more about placename significance and associated rendering. Do you see it differently?

Hi there - Please explain what is meant by "needs station verification" for the Empire Builder route (relation/10946021). Is there a question of accuracy here, or is there something else at play?

Claro - gracias por arreglarlo

@Viajero No worries - I appreciate you chiming in. Glad to know I'm not overreacting.
@carpbunker There are many problems with the data you're importing:
1) It's Canvec, so it's usually outdated at best, and in the case of backwoods waterways, often just plain WRONG. If you import waterways from Canvec, you should do it one river at a time and check to make sure the data is at least somewhat accurate, and try to fix it where it's not. The Tanzilla and Stikine are good examples - the water area defined by Canvec is decades old, and needs a lot of editing to fix what you placed. The Stikine in particular now has two separate channels for long stretches: the original river way, hand-traced, and your parallel CANVEC polygon that is largely incorrect, running alongside. Awful.
2) River polygons (natural=water + water=river) are importing incorrectly as named water bodies. (see my comment in change #81351653). The way in the middle of the river takes the name and all other appropriate data - not the polygon. You should especially NOT be deleting an already placed river way and replacing it with a named river polygon. Which brings me to...
3) You are deleting some waterways before replacing with Canvec data. As Viajero pointed out, that's not cool at all. I'm personally pretty steamed about it - I don't know how much other data you have treated similarly, but I'm quite sure others will also take offense.
4) You're importing river data but not lake data, so the waterways that are hitting small lakes just stop and then restart, over and over again.
5) All your waterways are importing as rivers - even the smallest creek.
6) You're placing waterways over roads without creating bridges, culverts or fords, and triggering a TON of Osmose errors in the process. That's how I found out about your imports - my Osmose errors were skyrocketing from you placing rivers over roads I placed.

I'm not an "All Imports Are Bad" mapper, and I'm grateful that you didn't import any of the land cover polygons from Canvec (which are absolute dog sh*t), but I'm asking you earnestly to fix what you've done so far, and endeavor to import more carefully in future.
Thank you!

Here ya go...
water=river :

Draw the outline area of the river and add natural=water + water=river. For long rivers the area should be split into several segments of manageable size.
In addition a way tagged as waterway=river, must be drawn in the direction of the river flow. ALL TAGS OF THE RIVER (LIKE NAME=* AND OTHER SUPPLEMENTAL TAGS) SHOULD GO TO THIS CENTER LINE.
(emphasis mine)

Add to that the cardinal rule "One feature = One name" (yeah that's a bad paraphrase).

The main issue is that data consumers generally pull water polygon data as non-flowing bodies of water, and labels are applied accordingly: One label, affixed roughly in the center of the feature. If you name a river polygon, it will not render the name correctly.

Do NOT name the river area - the named portion of the river needs to be the way in the center.