Hi, we don't copy anything from Google Maps - both because it is a violation of Google and OSM's licenses, but also because Google is often wrong (a good reason to have a community edited map!).

In this case, looking at the aerial imagery sources, Sherman does not appear to have any cycle infrastructure, unless some was very recently added. I removed the cycle relation and the cycleway since they don't seem to exist.

If I'm wrong, and there is a dedicated bike lane there that you can confirm locally, then instead of stacking two ways on top of each other or using a relation, you would add the correct cycleway tag to the main road way. See this guide for a list of cycleway tags used to describe different types of bike routes on a road. https://github.com/BikeOttawa/OSM-Bike-Ottawa-Tagging-Guide/blob/master/README.md

Hi, thanks for mapping! Another tip - the grassy median areas are probably best tagged "landuse = grass" rather than as a recreation ground, which implies that you can use it for activities, hiking, dog walking, etc. In this case I don't think the small grassy areas you traced would quite qualify as a recreation ground.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/81348318

Hi, thanks for editing the map! When you are done tracing a building, use the "Q" shortcut in the editor to square the corners of the building - it will make your additions look much more professional.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/81350853

Haha, sorry, this is Sherman and Congress in NJ, not CO, they look similar up close. :)

Either way, same comment - Sherman Ave. here doesn't really look like a cycle route to me, though cycleway=shared_lane may be an appropriate tag if cyclists are allowed/expected to share the traffic lane with cars.

Hi Michaela, thanks for editing. I'm in the denver area and am pretty familiar with the neighborhood. What is it you are trying to accomplish exactly? Cycle route relations are typically used for large routes that span cities or states, while individual tags on the way such as "cycleway=shared_lane" are used to indicate how a cyclist can use a particular road.

Hi Polarbear, you may not be familiar with US map sources, but the snippet is clearly a USGS quad topo, which is released in the public domain by the US government and is fully license compatible with OSM.

Of course that doesn't address the other tagging changes - sounds like some cleanup is needed for tag consistency.

Hi Jaymac, thanks for mapping - we've noticed a lot of additions to golf courses recently due to the use of the data in the simulator, it is a clever use of the data and everyone benefits from the more accurate maps.

For changeset comments, they are mostly used in the moment by people who are reviewing local changes to make sure they are correct, and in the future by mappers wanting to understand why the previous editor had changed something (perhaps years in the past). They don't need to be in depth, but something like, "Adding details to Lake Ridge golf course from aerial imagery" would usually be sufficient. If what you are changing isn't obvious, say, Bing has the old course and Maxar Imagery has the new course, an explanation helps people know what you did, "Adding details to golf course from Maxar, most updated imagery in this location".

The user is currently on a block for other incorrect edits. I've removed the "not a park" and made a few additional fixes in the area.

Hi Jake, the road got that name because at some point in the past a US Census mapper was told by someone that the road was named that - those names hang around in the database for a long time (possibly decades).

I've removed the name, and changed the way to a private driveway so no routing will occur. I've left the line in place, however, since likely someone would just remap it later, and these private driveways are still used for emergency services and deliveries.

There may be rare times when gluing them together makes sense, but it is usually easier to maintain if they remain separate shapes. One way to do this is to use the filters in iD (or JOSM) to hide the other features - for instance, when setting up the natural area you can hide Boundaries, and when working on the boundary you can hide Landuse features. Using the filters to hide everything except what you are working on is a good way to prevent inadvertent gluing.

True, there is a delay before it picks up changes, though I've found the address tools to be pretty accurate once they've sync'd up. I've put a lot of work into the DRCOG buildings and addresses import in Denver, so have learned (the hard way) about both correcting issues from the import and before the import. For every problem you find, another seems to sneak through...

Have fun at the ice fest! I am indeed a climber and cyclist, may of my edits have to do with places to be outside, or cycle infrastructure. I was pleased to be the one to put the Ouray Ice Park into OSM and get the cliffs labeled and named. Made a few updates two weeks ago when I was up doing some climbing, the weather was great and the ice had been coming in nicely!

Hi, things are coming along nicely with the cleanup, thanks! One thing I'm noticing is that there is often a mismatch between Avenue and Street for the addresses in Ouray (and possibly elsewhere), so addresses that should be 5th Avenue are getting labeled 5th Street, for example. See this inspector link for examples:

http://tools.geofabrik.de/osmi/?view=addresses&lon=-107.67102&lat=38.02156&zoom=17&overlays=buildings_with_addresses,street_not_found,place_not_found,misformatted_housenumber_lenient,nodes_with_addresses_defined,connection_lines,nearest_roads
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/79768733

Thanks for taking a look at it, definitely want to get these addresses right. My favorite tool for address validation is Geofabrick's address validator - this is the long permalink to the Ouray area:

http://tools.geofabrik.de/osmi/?view=addresses&lon=-107.67073&lat=38.02237&zoom=16&overlays=buildings,buildings_with_addresses,no_addr_street,street_not_found,place_not_found,misformatted_housenumber_lenient,nodes_with_addresses_defined,nodes_with_addresses_interpolated,connection_lines,nearest_points,nearest_roads

The nice thing is that it shows you when the address doesn't match a street, and when it DOES match a street, it draws a line from the building to the street it is matched to, which is helpful in verifying that you have connected it to the correct street.

Hi, welcome to the map! A few suggestions - square up your buildings by using the "q" shortcut, and don't use the "name" tag for personal information - remember that this is a public map - you don't want the entire world knowing that this is "Brett's House". :)
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/79584090

Hi, welcome to the map! Don't forget to square your buildings by using the "q" shortcut, and please don't use the "name" tag to add your name, or things like "My garage" - this is the public map open to the whole world, and you don't want personal information or notes like that included.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/79584289

Hi, thanks for bringing so many addresses in, but I think the import dataset needs cleanup before being imported - does this import have a discussion page already?

In particular, many street names are coming in malformed - for instance, in Ouray, points like this address (node/7103252271) are coming in with the street name of "2Nd", rather than "2nd Street" as it should be. Can you take a look and try to fix these using the original dataset, rather than fixing one at a time?

Hi Keith, it sounds like you are in good shape - we see a lot of changesets where people have copied something from Google, which isn't allowed, but in this case you are the source of the information, not Google, so all is good. Sometimes our warnings to people misfire.

As for the routing issue, I looked at the tagging and it looks correct to me - the access=no and motorvehicle=no tags should correctly prevent Amazon and other OSM based routers sending people through the gate. It may take a month or so for everyone's map databases to catch the update.

Thanks for mapping!

Thanks for confirming! The transition from proposed to construction to built happens fast in CO these days! Are any of the other roads in the area that are currently marked as in construction already built? You might be in a good position to update them. Thanks, phidauex.

Hi, are these new roads built yet? If not they may be best indicated as "highway=construction" and "construction=residential".
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/78693603

Hi, welcome to OSM! Please be aware that you are editing the live map database which is published immediately, so please don't enter test or other unverified information. Please remove the offices you created, or they will be reverted. If you need to test something, there is a development server you can use.