You might want to work on your aim. A number of the crossings you've added recently have been close to, but not actually on, the point where a pedestrian way intersects the road.

When you're editing in Spokane County, Esri World Imagery is far sharper and better-aligned than the other options, and is nearly as new as Bing or DigitalGlobe Standard.

Where are you getting the route of this railroad from? I'm not seeing evidence of it in the aerial imagery, and neither the 1903, 1961, nor 1987 USGS topo maps of the area show it.

Where are you getting the name "3I" from? Looking at historic topo maps, it appears to be "state highway 31", and I can't find a reference to it that's less than 68 years old.

Where are you getting that this has a traffic signal? It was a four-way stop when I drove through a few weeks ago, and I haven't heard of any construction since.

Where are you getting the street layout of Tecomate from? It doesn't show up on any of the aerial imagery.

Don't vandalize the map.

Please stop making changes based on outdated maps. Inland Empire south of 23rd hasn't been an arterial since it was cut off from US-195.

Maxwell between Washington and Ash was re-engineered earlier this year in a way that's significantly reducing the traffic flow.

Are you sure this is a state park? The Flathead County Parks website lists it as a county park: https://flathead.mt.gov/parks_rec/parks.php

The "Salmon River" relation you created has a waterway type of "LowerSalmon", which isn't a valid type, it includes a seemingly arbitrary part of the Snake River, and it excludes a similarly-arbitrary part of the Salmon River.

I'm not sure what you were trying to do here, but I don't think it worked.

Drawing one thing on top of another like you've done here doesn't work very well.

If you want to indicate that "Cosway Road" permits foot traffic, you should select it and set the "foot" allowed-access field to "yes". If instead there's a trail running parallel to "Cosway Road", carefully draw it parallel to the road, only intersecting at the ends.

If you're going to be editing in Spokane County, please use Esri World Imagery. It's considerably newer, sharper, and better-aligned than Mapbox Satellite.

You might want to read osm.wiki/Relations/Relations_are_not_Categories -- "Spokane County Highway Bike Routes" seems like a textbook example of what relations should not be used for.

When I'm mapping buildings, I'll flip back and forth between the clearest available imagery (usually Esri Clarity, but sometimes Esri World) and the newest available imagery (usually DigitalGlobe Standard). I might also bring in a third image option if it's got useful shadows (eg. for telling if something is a flat-roofed building or a ground-level feature).

I noticed it at the intersection of "County Road" and "D Street": changeset/60646750#map=19/45.93509/-116.12952

The five smallest building outlines there look more like utility trailers than buildings.

You appear to have traced a half-dozen utility trailers here, in addition to the buildings.

Normally, a large river such as the Stillwater or the Flathead is mapped in two parts: an area or multipolygon tracing the banks, and a line down the middle following the path of greatest flow. The "River" tag and the name of the river go on the the central line, while the outer edge is tagged as "Riverbank".

It looks like whoever added the Stillwater didn't do the second part: the central line for the Stillwater ends right where he started adding the riverbank.

The usual tags for the roads in/accessing a parking lot are "Parking aisle", "Driveway", or if you're not sure how to classify it, the generic "Service road".