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!

I see that you have used the editor built-in to the OpenStreetMap website. I believe you may have entered in a lot of correct information but directly edited the values in the "Tags" section as they would make sense to a human. I'd highly recommend trying to use only the first two sections of the feature editor and not use the "Tags" directly if you're just starting out with OpenStreetMap. The "Tags" each have a special meaning and are mainly meant to be read by computers.

Fortunately, it looks like another mapper has corrected most of these things for you, but there is one item that would really improve things. Try to select a "Feature Type" again to be a Dry Cleaner. That way this business will show up with a nice Dry Cleaning icon on the map!

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!

There are actually a number of options for reverting OpenStreetMap changesets as listed on this wiki page: osm.wiki/Change_rollback.

If you want to do a complete rollback, you may want to use the Revert UI (http://revert.osmz.ru/) (I actually haven't tried this one yet) and send it over this changeset ID. Otherwise, if want to partially revert your changeset, you will probably want to use JOSM and the Reverter plugin (osm.wiki/JOSM/Plugins/Reverter).

I think as long as an amenity hasn't been completely demolished or something, it's best to change the existing "amenity" tag to have the "disused:amenity" tag while keeping the original value for the "amenity" tag.

Even if you delete an entity, it is still preserved in the changeset history, so there is still a record of its existance.

The easiest thing to do is to amend what you added. As I mentioned, I'd recommend editing the polygon you made by selecting it, and then removing the landuse and building tags and then change the feature type to be a Horseback Riding Center.

I generally like to also include pedestrian ways even when there are also pedestrian areas as I believe it helps inform pedestrian routing engines better. In particular, it can be useful for providing directions to elevators and escalators which are now a little disconnected from the pedestrian network after this edit.

I know it may not look super pretty, but I'd probably revert the changes and add them back, but that's just me and my strong preference for adding data to help routing engines.

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.

In your comments, I see that you note that your address is showing up incorrectly on Instagram. That must be frustrating! I don't know exactly how Instagram and OpenStreetMap are connected, but I can definitely give you guidance on how to make some edits in OpenStreetMap.

I see that you have used the editor built-in to the OpenStreetMap website. I'd highly recommend trying to use only the first two sections of the feature editor and not use the "Tags" directly if you're just starting out with OpenStreetMap. The "Tags" each have a special meaning and are mainly meant to be read by computers.

I'm not sure how it happened, but as of right now, it looks like a few "tags" are conflicting with each other. Unfortunately, the big polygon that was drawn is being interpreted as one giant building! I'd recommend deleting the "building"="San Antonio Stables" tag to resolve that. There also exists the "landuse"="commercial" tag. It would be more appropriate to remove this tag and instead change the "Feature type" in the top part of the editor to be "Horseback Riding Center". See the OpenStreetMap wiki article here (leisure=horse_riding) for more info.

Also, it looks like in another edit you added a "name" tag to the roadway junction on the east side of the facility. This name can be removed.

Finally, I know you are probably just looking to update the address, but there is a fairly wide range of ways to add information about Horseback riding to OpenStreetMap as noted in this wiki article (osm.wiki/Riding).

Good luck and thanks for contributing to OpenStreetMap!

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.

It looks like you're trying to mark this feature as either being closed or no longer existing and you used OpenStreetMap's website's iD editor to do so. When businesses close, they can either be deleted entirely or have the "amenity" tag changed to have the "disused:*" prefix as explained here (disused:=**).

I see in some edits that you have used the EveryDoor app. The EveryDoor app has a way to mark a business as being defunct, so that is another option that accomplishes basically the same thing.

Thanks for contributing and good luck 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!

I see that you have used the editor built-in to the OpenStreetMap website. I believe you may have entered in a lot of correct information in the "Feature Type" and "Fields" sections, but then directly edited the values in the "Tags" section to make more sense to a human. I'd highly recommend trying to use only the first two sections of the feature editor and not use the "Tags" directly if you're just starting out with OpenStreetMap. The "Tags" each have a special meaning and are mainly meant to be read by computers.

Fortunately, it looks like another mapper has corrected most of these things for you, but there are two items that could still use correcting. Try to select a "Feature Type" again to be a tailor. Also, it looks like you could change the address in the "Fields" section so that the house number and street number are in separate and appropriate fields.

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!

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 are right that this cycle path crossing does look a bit funky. In the satellite imagery, there is clearly a cycleway crossing.

A great way to go about editing the map would be to add the proper crosswalks at this intersection. Usually, the crosswalks could be marked as explained in the OSM wiki article about crossings (crossing=*). In this case, I'd specifically mark the crossing of Doolittle drive as a Cycleway Crossing (cycleway=crossing). There are a few presets in the iD editor of OpenStreetMap that should allow you to find these kinds of tags.

If you're not familiar with adding ways, I'd recommend going through the iD editor tutorial. If you need to get to the tutorial, you can begin editing on this website, then open up the help tab and click the "Start the Walkthrough" button.

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 this a review.

If you used GPX data to verify these changes then that is a reliable source of information.

However, even with GPX data, sometimes satellite imagery can be a little off even between different providers. There is a way to account for this which involves using the editor's built-in tools to offset the satellite imagery as needed. See this blog post for more info: https://blog.mapbox.com/better-openstreetmap-data-with-ids-new-imagery-offset-tool-ff1906ef6c53

In general, these small corrections to the alignment of roads look great and convey the needed information about where there are twists and turns in the road.

Good luck with future mapping!

Everything is looking great now! Nice work.

Well, the new turning links in the middle of Hwy 17 look great. However, Vine Hill Road southeast of Hwy 17 has now been classified as a trunk link road all the way down to the intersection of Mountain View/Branciforte. That should probably be changed back to the original classification.

Hi there! You flagged this changeset as requesting a review, so I'm giving it a review.

It appears that you are at the very least desiring to mark that it is possible to make a left turn from Vine Hill Road on the southeast side of Highway 17 to go southbound (SB) on Highway 17.

This changeset now makes it possible to do so, but now involves a very sharp left turn once going onto SB Hwy 17. Also, it now makes it possible to completely cross Hwy 17 to go onto Vine Hill Road on the northwest side of Hwy 17.

There are some similarly-mapped crossings of Hwy 17 at both Glennwood Cutoff and also Glennwood that I would recommend taking a look at if it is desired to properly mark the middle turning lanes that can be used when making a maneuver to/from SB Hwy 17.

While I guess it is physically possible also to make a maneuver all the way across Hwy 17 to Vine Hill Road on the other side, this does seem a little dangerous. Moreover, the lane markings seem to indicate an exclusive left turn only from SB Hwy 17 onto Vine Hill Road (southeast of Hwy 17). I'll leave it up to you and your local knowledge whether or not it may make sense to keep this configuration or change it to be a southbound left turn only as it was mapped before.

Good luck mapping and nice to see you mapping in the area!

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

I'd say it looks pretty good in terms of the alignment. However, it appears that there are actually some stairs in a part of this path as viewable in this Mapillary picture (https://www.mapillary.com/app/?pKey=1040872109779147&focus=photo&lat=36.973116759897&lng=-121.91576116351&z=17&x=0.3655237689180826&y=0.5726536438508365&zoom=0.6639344262295084).

This changeset could be improved by splitting up the pathway so that the sections with stairs are classified as "highway=steps".

FYI, I went ahead and fixed the Toronto TZ so the relation members were in the correct order. See changeset/125327667.

Is there a place where you're making notes about this items? It could be useful for making a case to the maintainers of the timezone database. If you want to, I wouldn't mind at all for you to post documents to the linked GitHub issue to store the files there.

I know we were discussing (https://github.com/evansiroky/timezone-boundary-builder/issues/131) that `America/Thunder_Bay` may not have existed, but there is still an entry for it in the timezone database. Could the removal of its relation be a little premature here?

Thanks! Seems like a nice transit center.

Forgot to add a source: https://www.youtube.com/watch?v=MVHAwgPSLEs

This changeset appears to have deleted a lot of relations. Most notably, the relation/2551642: the state of Nayarit.