Please be more careful when editing large relations like this. You both broke the Lolo National Forest boundary and left the reservation boundary in an incomplete state.

Where are you getting the information that Prichard Creek Road/FS 9 is a secondary road? It hasn't been an important part of the road network since gold mining ended a century ago -- they don't even bother to plow it past Murray in the winter.

Have you confirmed the accuracy of the shapefile you used? Some of the Forest Service trail maps have rather serious errors, such as running along the wrong side of a lake, or having junctions a mile or more from the actual location.

GIS data isn't infalliable. The "44th Avenue" you added is a private driveway.

What's your source for the road not being there? I've driven or hiked on quite a few roads (such as way/13920613 and the surrounding tracks) that the Forest Service shows as not being there.

Judging from the surface quality shown in the Esri Clarity imagery, I think I could get my Civic through there, though I probably wouldn't be going very fast.

I'm pretty sure that what you've mapped is just a barn, and the grange hall is the blue-roofed building across the street.

Could you please do your cleanup in smaller pieces? It makes it easier to fix when you delete something (such as National Forest Development Road 2291) that you shouldn't have.

What did you try searching by? The tag lookup system isn't always perfect (for example, it used to be that you could only find road types if you searched for "road", not "street").

If all else fails, you can always add tags the hard way, by selecting a type of "point", clicking on "All tags" in the left-hand pane, and filling in the key-value combinations by hand. You'll need to look up what to use; the OSM wiki (osm.wiki/Main_Page) is usually a good place to find them.

I've updated Boulder Falls to be a waterfall.

As a general rule, driveways should be tagged as driveways rather than tracks even if they're unpaved.

Is Boulder Falls better described as a cliff, or as a waterfall?

Your aim seems to have been a bit off here. ARCpoint Labs is one building further south than where you placed it.

Thanks for your interest in improving the map.

Unfortunately, I'm afraid this edit needs to be reverted. The STA terms of service (https://www.spokanetransit.com/about-sta/developers-terms-of-use) don't permit their GTFS data to be used in OpenStreetMap (among other problems, they can revoke permission to use the data at any time). Even if they didn't, there are a number of problems with this import, such as duplicate stops (particularly in Cheney and downtown Spokane) and less-than-ideal tagging.

In the future, when importing data from outside sources please follow the guidelines at osm.wiki/Import/Guidelines -- yes, it's a slow, complicated process, but it's intended to prevent problems before they happen.

Please don't abbreviate names, particularly if they're already non-abbreviated. If a computer needs to save space, it's easy to construct an abbreviation, but going the other way is far harder. For example, should "st" be expanded to "state", "street", or "saint"?

I don't know if you've noticed, but you can change which background imagery you're using by clicking on the "Background Settings" tab in the editor (it looks a little like three stacked sheets of paper) and selecting which imagery you want to use. In the Spokane area, the "Esri World Imagery" option is sharper and better-aligned than the default "Bing" imagery.

Thanks for your addition -- it's always useful to have locally-known features added to the map.

You made a couple of mistakes here, though: first, elevations in OSM are measured in meters, not feet -- a 4826-meter-tall mountain would be the tallest in the lower 48. And second, the second digit of the number on the topo map was a "3", not an "8". I've fixed both of these problems.

Okay, I think I figured out a workable method. 26 driveways and three residential roads restored.

I'm trying to figure out how best to revert this, since several of the driveways you deleted (eg. way/6213884) were correctly aligned and tagged, while others (eg. way/6212680) were correctly aligned but incorrectly tagged.

Quite a few of the roads you deleted here were correctly-mapped driveways.

If something doesn't have a name, you don't need to give it one. Lanes in parking lots almost never have names, and someone looking for a parking space is going to be quite confused if their GPS tells them to "turn left on parking lot, and then turn right on parking lot".

Where are you getting this planned road from? It's inside the airport security fence (which argues against it being built), passes through the runway 6 overrun area (which argues more strongly that it won't be built), and traffic on it would interfere with the runway 6 ILS (which pretty much guarantees it won't be built).