Hi Nathalie! Welcome to OpenStreetMap, and thanks for the edits! It would be very helpful if each changeset was confined to a small geographic area if possible, such as a several square km area.

Second, could you cite your sources when you create a changeset? For example, how did you know there was a camp_set at the location where you mapped one?
---

Published using OSMCha: https://osmcha.org/changesets/107048999

Thanks for your reply, and again welcome to OSM!

First, don't be discouraged by the discussion here. As someone new to the project, you can't know everything about it on day one. I recommend starting by mapping things you observe in person around the areas where you live and work, such as businesses, new subdivisions, etc.

In OSM we are not allowed to copy from other maps, like the one you cited as a source - unless it has a compatible license. I don't think we can assume that is the case for the source you cited - especially since the source you cited uses a commercial web map.

If you were to observe in person a sign along the road in question that said it was "Old Route 66" it could be mapped in OSM. Routes (US highways, interstates, etc), are handled as relations in OSM. There are already relations for Historic US 66, e.g. osm.org/relation/3734410. This applies to roads that are signed as "History US 66." If your have a source with a compatible license that gives the actual location of old US 66 you could add a tag old_ref=US 66, but the official current name shouldn't be overwritten.

Hi angys,
Also, could you restrict the geographic extent of each changeset to a smaller area where possible? It would make reviewing easier.

I do agree with Vinber that a better changeset comment is needed as well as citation of sources supporting the changes.

Hi! Welcome to OpenStreetMap and thanks for "editing and contributing", we need more of that!

I was wondering what your source was for for renaming "East South Frontage Road" to "Old US 66"? You didn't cite a source that would support this. The county GIS portal[0] shows this road as "E South Frontage Road"

[0] https://gisapp.willcountyillinois.com/Html5Viewer/Index.html?viewer=Data_Viewer

I get where you are coming from regarding memory on an embedded device. I agree with you as well that post processing simplifying would be computationally costly.

With what embedded system are you working?

Thanks for the edit, and thanks for the reply!

In this case I can't think of a way the additional detail hurts, especially considering the island (if that is what it is called) in the middle.

BTW, I see you are making a substantial number of edits in the Fort Collins/Loveland area. That is great! Thanks for what you are doing!

Thanks for your reply, and again, thanks for all of the edits.

Yes, mistakes happen. Sometimes I come across an edit I made years ago, and am quite surprised at the mistakes I made. The way tagging is done in OSM can be confusing, it is constantly evolving, and not everyone in the community agrees on everything.

Please continue to edit, your contributions are appreciated!

I think that having the greater detail is better.
---

Published using OSMCha: https://osmcha.org/changesets/106913800

I see a lot of low quality edits from StreetComplete.

Thanks for all of the edits to OpenStreetMap.

In this situation, why did you delete the building=roof tag?
---

Published using OSMCha: https://osmcha.org/changesets/106906421

Interesting point, however, I see a lot of StreetComplete edits that are restricted to a reasonable geographic area.

Hi Randy. Welcome to OpenStreetMap and thanks for the edits!

The Twin Sisters Trail which you edited had been aligned with the Strava Global Heatmap (note the source:geometry=Strava Global Heatmap). This is an average of the GPX tracks of a large number of users of the Strava app who have hiked or ran this trail. As such is is much more accurate than any single GPX track. In any event, if you do find a more accurate source and use it to modify the trail, you should also modify the source:geometry tag. Let me known if you have any questions about trail mapping in OSM, I would be happy to help.
---

Published using OSMCha: https://osmcha.org/changesets/106865992

Hi Raknm,
Thanks for your response. I look forward to seeing more OpenStreetMap edits from you and the rest of the team at Amazon!
Mike

Hi, Thanks for the edits. It is great to see Amazon making contributions to OSM! If you confine the edits that are part of a given change set to a smaller geographic area, it would make review easier. The bounding box for this change set stretches the entire distance across the US from east to west.
---

Published using OSMCha: https://osmcha.org/changesets/106686978

Hi, Welcome to OpenStreetMap and thanks for the edits! If you confine the edits in a given change set to a smaller geographic area, it would make review easier. The bounding box if this change set covers a significant part of the World, thus it appears that you made changes in many different areas, when this is not the case. I look forward to seeing more edits from you!
---

Published using OSMCha: https://osmcha.org/changesets/106719698

Hi, great to see Amazon making contributions to OSM! Generally driveways should not be tagged highway=track, but rather highway=service, service=driveway. You can add surface=unpaved if that is the case.

That type of stuff happens. Thanks for the response, and again for all of the edits!

Thanks for the edits. Generally we do not put house numbers (addr:housenumber=*) on nodes that are part of roads (osm.org/node/5359275373) . Perhaps you meant to apply this to a building?

Great research and documentation! It would be interesting to know who built that trail, as I don't think it was the USFS.
---

Published using OSMCha: https://osmcha.org/changesets/105980384

Good to see the Loveland boundaries get some attention! I have been meaning to take a look at them for awhile, but there are so many other things to map!
---

Published using OSMCha: https://osmcha.org/changesets/105988261