Sounds good to me.

Which imagery did you use when adjusting the cliffs? Not all aerial photographs are created equal, and when tracing something with abrupt changes in height like this, it's critical that you use images with good orthorectification.

I've reverted this changeset. Yes, the current mapping throws up all sorts of automated QA errors, but fixing it properly involves an afternoon of hiking up and down the hillside to see how the trail network is adapting to the road and road-removal efforts.

Why do you think this street is residential? It has an elevated speed limit, right-of-way over traffic on cross streets, is classified by the city as an arterial, and in general is How You Get Places in that part of town. In short, it looks an awful lot like a tertiary road.

Does Go Map!! have a way of adding "building=yes" or similar when you're adding the name? Doing that would make it obvious that adding a standalone name wasn't a mistake.

This bridge is straight. It only appears bent in the imagery because of bad orthorectification.

When adding building names, it helps if you also add the buildings, or at least indicate that the points you're adding *are* buildings. I've traced three of them, but Delta Delta Delta and Delta Sigma Phi don't clearly correspond to buildings.

I'm not sure how you'd do it in iD (the website editor). The standalone JOSM editor has a "reverter" plugin you can use for easy rollback of changesets: osm.wiki/JOSM/Plugins/Reverter

Has US-97 really been upgraded to the "almost-Interstate" quality implied by "highway=trunk"? Looking at the aerial imagery, I'm not seeing most of the features I'd expect from a trunk road: four or more lanes, a median or median barrier, no intersecting driveways and few intersecting roads.

Please don't use "access=no" for brief construction closures. Most data users update no more often than once a month -- this road was open again by the time I got there, but OsmAnd had picked up your closure and refused to route to the parking lot.

Where did you get the name "South H Street" from? The name fits the pattern for the area, but I drove that road a couple months back and couldn't find a street sign anywhere.

Not all arterials are primary roads. This one, in particular, is a winding two-lane road with a significant height restriction that is unlikely to ever see much traffic.

Thanks. I've improved the tracing of the Cambell House, and added a separate outline for the carriage house.

The building outline you drew for the Cambell House appears to cover two buildings. Which one is the actual Cambell House?

I've reverted this changeset: it appears to be personal bookmarks rather than an attempt to improve the map.

Is Fifth Street really one-way over its entire length, or did you forget to split the way where it divides in two?

In several of your recent edits, you've forgotten to add tags to what you've drawn, and you've added roads that cross other roads without connecting.

A bare line that doesn't indicate what sort of thing it represents isn't very useful, and won't show up on the map. A road that isn't connected (indicated by a gray dot at the point of intersection) isn't useful for routing. I've fixed the problems I've seen, but could you be more careful in the future?

I don't know of any. Adding an additional "access:conditional=no @ winter" would express the seasonal closure without interfering with normal routing, but I don't know of any software that uses the "access:conditional" tag, and it doesn't cover the fact that the gate can be closed for other reasons (eg. a freak snowstorm in August).

When you add a normally-open gate to a road, it's important to add access information. Routing software is inconsistent about how it treats a gate with no information: some software defaults to "yes", while other software defaults to "no".

I'm pretty sure this rest area is already mapped, about a half-mile north of where you've put it.