Hey there! I'm a local mapper from Scotts Valley, California. I see that you requested a review of this changeset, so I'm giving it a review.

The new house you added looks great!

Thanks for contributing to OpenStreetMap!

Hey there! I'm a local mapper from Scotts Valley, California. I see that you requested a review of this changeset, so I'm giving it a review.

The new driveway along with the gate you added looks great!

Thanks for contributing to OpenStreetMap!

Hey there! I'm a local mapper from Scotts Valley, California. I see that you requested a review of this changeset, so I'm giving it a review.

I will admit that I have no clue about powerline voltage. That being said, since I don't have a clue about it, this changeset and others could really be improved if you added a source to your changesets (see OSM wiki about this: source=*#How_to_use_on_changesets).

When you add a source, you can say how you figured out the voltage of these powerlines. Perhaps you are referring to some kind of other map that shows these voltages. In that case you could provide a link to that map.

Hello again! I see that you requested a review of this changeset, so I'm giving it a review.

It looks like you've started from scratch and simply changed this area to be of a farmland type. This is fine as it is.

However, I do see that all of the other tags were removed. The address tags did provide useful information as did the name. Information about the name and address would actually add value to this map. I'd recommend adding those back as you see fit.

Hey there! I'm a local mapper from Scotts Valley, California. I see that you requested a review of this changeset, so I'm giving it a review.

In general, some roads may not need to be explicitly marked as being bikeable. I'd recommend reading the OSM wiki page about "OSM tags for routing/Access restrictions" osm.wiki/OSM_tags_for_routing/Access_restrictions.

In general, certain road classifications have certain default access restrictions that are generally believed to be what routers should interpret. Of the roads that you marked, it appears that it merely confirms what the default expectations are in the US.

Hey there! I'm a local mapper from Scotts Valley, California. I see that you requested a review of this changeset, so I'm giving it a review.

You have added a lot of great and mostly correctly formatted information about this business. However, the "image" tag appears to be an email address, so the "email" tag should be used here instead.

Also, since this business appears to be located within a large building, I would recommend also adding information in the "Unit" field and potentially even add the "addr:floor" tag to indicate which floor the business is located on.
addr:floor=*

Thanks for your contributions to OpenStreetMap!

Hey there! I'm a local mapper from Scotts Valley, California. I see that you requested a review of this changeset, so I'm giving it a review.

It looks like you seem to have already done a number of other edits in this area and changed the bike route relation. These edits all look mostly good, but the new roundabout created along Pondorado road could be improved such that it indicates one-way travel in the inner part of the roundabout and on the approaches too.

If you're looking for another example of a good roundabout in the area, I'd recommend taking a look at this one near Roseville: osm.org/#map=19/38.76796/-121.27096

Otherwise, nice work adding this new information to OpenStreetMap!

Hey there! I'm a local mapper from Scotts Valley, California. I see that you requested a review of this changeset, so I'm giving it a review.

This looks pretty good, although, I would change the classification from "highway=footway" to "highway=path" to show that is not suitable for vehicles.

Also, if you are interested in a more complex way to improve this, you could add this new path to be part of a new Hiking Route Relation. See the OSM Wiki documentation about Hiking Routes here: route=hiking. These hiking routes relations show up in many maps such as this one: https://hiking.waymarkedtrails.org/#?map=14.0/37.9024/-122.6093

Hey there! I'm a local mapper from Scotts Valley, California. I see that you requested a review of this changeset, so I'm giving it a review.

It looks like you've added some helpful information to this business and all things look like they've been added appropriately.

Hey there! I'm a local mapper from Scotts Valley, California. I see that you requested a review of this changeset, so I'm giving it a review.

I see that you added the "locked=yes" tag to this gate node. This seems fine, but depending on what you're trying to imply with this, you may want to add some more information. The "access=no" tag may be helpful to add to imply that nobody can open the gate. More about this can be read on the OSM wiki: access=*

Hey there! I'm a local mapper from Scotts Valley, California. I see that you requested a review of this changeset, so I'm giving it a review.

All the edits you made seem to be coded correctly! Thanks for your contributions!

Hey there! I'm a local mapper from Scotts Valley, California. I see that you requested a review of this changeset, so I'm giving it a review.

It appears that you are updating the name of an apartment complex that may have been named something differently in the past. As such, you correctly updated to the new name, but then used the "not:name" tag for the previous name. While I don't know the full history of this particular apartment complex, I think the most likely sequence of events had the apartment complex might undergo a change in ownership and when that happened, it changed its name. If that is the case, then it would probably be more appropriate to use the "old_name" tag instead of "not:name" tag. If the apartment complex was never called "Parkwood Terrace Apartments" then the "not:name" would be more appropriate.

In case you'd like to read up more on what these tags mean, here are the links to the OSM wiki for each tag: old_name=*, not:name=*

Also, it's great that you added more information about the website and whether smoking is allowed.

Thanks for contributing to OpenStreetMap!

Gotcha. In the event that you're using knowledge based on your presence at the location, then you can mark the changeset as having a source of "survey".

Regarding the tags, I think it could be more useful to change the "URL" tag to be "operator:website". (see wiki page for URL saying that website should be used instead url=*)

Also, the payment:card is one that maybe could be changed. I believe that BikeLink requires their own card to use the lockers, so maybe the "payment:cards" could be changed to "payment:electronic_purses". See payments documentation: payment:=**#Electronic_Purses_/_Intersector_Electronic_Purses_(IEP)_/_Stored-value_cards

Hey there! I'm a local mapper from Scotts Valley, California. I see that you requested a review of this changeset, so I'm giving it a review.

Everything seems to be coded correctly, so that's good. One thing that may help in some changesets is to indicate the method with which it was determined that these bike lockers existed. Was it done via a survey or was street-level imagery used or looking at information on the BikeLink website? That could help improve the credibility of the changesets.

Hey there! I'm a local mapper from Scotts Valley, California. I see that you requested a review of this changeset, so I'm giving it a review.

The method you used for adding these traffic signals is great!

There are actually 2 possible ways to add information about traffic signals at complex intersections like these as noted in the OSM wiki about traffic signals: highway=traffic_signals#Tag_all_crossings. So another acceptable way to map these would be to create traffic signal nodes at the position where the incoming cars would stop and wait for a traffic signal.

Thanks for contributing to OpenStreetMap!

Hey there! I'm a local mapper from Scotts Valley, California. I see that you requested a review of this changeset, so I'm giving it a review.

It looks like you're on a building-adding spree which is fine by me. The only feedback I can give is that every once in a while some of the buildings might slightly overlap a road or alleyway, so it'd be good to try to manually adjust those buildings so there's no overlap.

Otherwise, I'm personally all for mass-adding these buildings like this. In my immediate vicinity, I like to get super precise and map out all the corners of the buildings, but I'd rather see most buildings added in like this than none at all.

Hey there! I'm a local mapper from Scotts Valley, CA. I see that you requested a review of this changeset, so I'm giving it a review.

You have entered a lot of great details about this business which is great! Everything you entered appears to be formatted correctly!

If you wanted to, you could also add information about the website of this business.

I also see that you are adding a lot of POIs using the OpenStreetMap website's editor. There are also other editors available as apps that can make it possible to make your edits while out in the field! I personally really like the EveryDoor app. StreetComplete is fun too.

Happy mapping!

Hey there! I'm a local mapper from Scotts Valley, CA. I see that you requested a review of this changeset, so I'm giving it a review.

You have entered a lot of great details about this business which is great! Everything you entered appears to be formatted correctly!

If you wanted to, you could also add information about the website or phone number of this business.

Thanks for contributing to OpenStreetMap!

Nice work!

Hey there! I'm a local mapper from Scotts Valley, CA. I see that you requested a review of this changeset, so I'm giving it a review.

You have entered a lot of great details about this business which is great! Everything you entered appears to be formatted correctly except for the phone number. The phone number should be in the format: "+1-xxx-xxx-xxxx".

If you wanted to, you could also add information about the website or opening hours of this business.

One final thing I'll add is that this web editor for the OpenStreetMap unfortunately has a terrible UI for correctly setting the opening hours! The other mapper formatted the correct hours for you, so you're good for now. If you need to update these things in the future, I'd recommend using the EveryDoor app which has a much better editor to update the opening hours.

Thanks for contributing to OpenStreetMap!