I added those because I hiked them and have GPS traces showing the routing.

OSM isn't supposed to be a copy of various official maps, it's supposed to be the result of looking at what's actually there. Just because something isn't on an official map isn't a reason to delete it.

As far as I can tell, the paths you deleted still exist. Why did you delete them?

Where did you get this name from? The BC government has some very different names for this section of highway.

The most common way to map a business inside a building is to add a point with the business information; a more detailed method is the Simple Indoor Tagging scheme: osm.wiki/Simple_Indoor_Tagging

Drawing one building over another just confuses everyone involved.

I don't think an access of "permissive" is correct for something that's in a public park.

When you divide a road like you did at the intersection of Lancaster and US-95, please make sure you update the lane counts and move the traffic signals to the new intersection points.

How about we call it the "Elko-Roosville Highway", since that's what the BC government seems to call it: https://web.archive.org/web/20170105151258/http://www2.gov.bc.ca/gov/content/transportation/transportation-reports-and-reference/numbered-routes#

The section between Revere Road and Imbler Creek is packed fine gravel. I don't know what it's like any further west than that.

Is US-2 physically divided here? Recent imagery isn't sharp enough to show something like a median barrier.

If it isn't, then please don't map it as such -- with a pair of ways, there's nowhere to put the center turn lane that's visible in older imagery.

The section of Palouse to Cascades going past Revere Wildlife Area looked reasonably cycleway-like when I hiked it a few months back.

Is Rehmke Road really private along its entire length?

Welcome to OSM!

You specified a width of "8" for the trail. Any time units aren't specified, the OSM software assumes meters, which would make this as wide as a two-lane road. Should the width be changed to "8 ft"?

It takes time for changes to propagate to all the layers. Cycle Map has a two-week update frequency, which would explain why it's not showing your changes yet.

Which map are you checking? The "standard" layer on OSM.org is designed around drawing streets, but if you click on the "layers" tab on the right, you can bring up the "CyclOSM" or "Cycle Map" layer, both of which have Trail Street highlighted in blue.

There's a lot more information in OSM than can be shown on any one map. People have produced specialist maps for everything from power lines to downhill ski routes based on it.

Welcome to OSM!

I'm not sure what you were trying to do with the bicycle path on Trail Street, but drawing one thing over another like that confuses the heck out of route-finding software.

If you were trying to indicate that the Milwaukee Trail follows Trail Street, that's done through what's called a "route relation", and Trail Street is already part of the relation for the Milwaukee Trail.

Please don't abbreviate street names. It's easy enough for a computer to construct an abbreviation if it needs to save space, but it's impossible to go the other way. (For example, should "St" be expanded to "Street", "State", or "Saint"?)

Why are you putting multiple names into the "name" field? Spelling variations should go into the "alt_name" or "official_name" fields, while names in different languages should go in the appropriate multilingual name field.

I don't see any value in having these numbers in OSM if they're not present on the signs. Without signs on the ground, they're useless for navigation.

That's because neither the developer of iD nor the developer of JOSM expected the mayor of Wallace to proclaim the intersection of Bank and Sixth to be the Center of the Universe, and have a custom manhole cover made to mark the spot.

Sometimes you need to ignore the warnings and map what's actually there. The world is more complicated than JOSM's validator code realizes.