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".

This looks like it's a switching/transformer facility rather than a power-generating facility. The usual way to map these in OSM is to trace the fence line and tag it as "Substation", which I've done.

(If I've missed something and there's a gas turbine or the like in there, feel free to change it back.)

If you're having trouble telling what shape a building is, please switch background imagery (the third or fourth button from the top on the right-hand side, the one that looks sort of like three stacked sheets of paper). What you've drawn here looks almost nothing like how the building appears in Esri Clarity, or Mapbox Satellite, or really anything except Bing Imagery.

If you want to map an island in a pond (or a courtyard in a building, or any other object with a hole in the middle), you want to create what OSM calls a "multipolygon":

1) Trace the outer and inner edges.
2) Select one of the edges, then shift-click to select the other one as well.
3) Right-click and select "Merge".

The editor is (usually) smart enough to realize that if you're merging two concentric objects, you want to cut the inner one out of the outer one.

I've done it for you here; you can look at it in the editor to see how it's done.

The correct way to add a bridge to part of an existing road/trail/whatever is to split the way at the ends of the bridge (right-click on the node at the end of the bridge and select the "scissors" icon), then select the part that represents the bridge and select the "bridge" structure type from the list.

Simply drawing a new line over the old one and labeling it a "bridge" like you've done here doesn't work. It just makes it look like there are two abandoned railways, one of them on a bridge over the other.

Is it really signed "Sunset Highway" all the way across the state? My experience from driving it was that the "Sunset Highway" signage stopped a bit before Reardan, replaced by generic "SR 2" or "US 2" signs, except where the road picked up a new name while passing through a town.

Okay, I've undeleted it.

It appears you deleted Wenatchee Valley College in this edit. Did you intend to do so?

Welcome to OpenStreetMap!

A couple of tips for better mapping:

1. You can change the background imagery by clicking on the "Background settings" tab in the editor -- the one that looks sort of like three stacked sheets of paper. Different imagery options are newer, or sharper, or better-aligned. In the Missoula area, it looks like "Esri World Imagery" is the newest, while "Esri World Imagery (Clarity) Beta" is the sharpest. I can't tell about alignment.

2. When you're adding things to the map, try not to connect unrelated objects to each other: it makes the map harder to edit and can confuse software that's trying to interpret the data. Connecting similar types of objects is fine (eg. connecting a park to a residential area, or connecting two buildings that share a wall), and connecting intersecting roads, trails, and the like is essential for routing software to be able to work properly.

You can tell that the editor wants to connect two objects because your cursor gains a tiny green dot or line in the lower-right corner, and you can tell they've been connected because there's a gray dot at the point where they meet.

Thanks for your contributions, and happy mapping!