Hi, thanks for helping to improve the map! I'd like to invite you to the OpenStreetMap US Slack server, where you can chat with other local mappers in the channel #local-kansas. Hope to see you there!

Slack can be found at: https://slack.openstreetmap.us/

I agree we need to do some work to tighten up these definitions so they're useful to mappers. Having dangling segments of different classifications makes a mess of the map as you zoom in and out. Highways of the same classification should really form a coherent, importance-based network. Perhaps we can recruit you to draft up the Virginia guidelines?

Hey, welcome to OSM! I think this is supposed to be spelled "Nazarene", can you confirm that?

Also, I'd like to invite you to join the OSM US Slack, channel #local-kansas so that you can connect with other Kansas mappers.

You can get to Slack here:
https://slack.openstreetmap.us/

Hi,

Thank you for working to make the map better. I've reverted these changes because OpenStreetMap maps what is on the ground. If the paths in question are private, they should instead be marked with the tag "access=private" rather than deleted. This will change the appearance of the trails on the map to that of a private trail, and hiking apps will avoid routing hikers over those trails.

For more info, please see also:
osm.wiki/Why_we_won%27t_delete_roads_on_private_property

If you wish to chat with other mappers in your area, please visit the OSM US Slack at https://slack.openstreetmap.us/ and join the channel #local-massachusetts

Hi, this tiny section of road should not have been upgraded to trunk. This is a topic that is being actively worked on in the United States, and I invite you to discuss further on Slack, channel #highway-classification, or on the talk-us list or OSM World Discord.

Also, please see:
osm.wiki/United_States/2021_Highway_Classification_Guidance

Hello, why did you make this short section into a motorway?

We discussed some of these, and the bicycle tag has implications because some interstates do allow them. But I'm definitely open to starting a discussion on what makes sense for motorway defaults.

Please don't add incorrect tagging for a data consumer. If a road doesn't have a name, it doesn't have a name.

Texas and New Mexico, too. Wouldn't want anyone to feel left out!

Fortunately, there is very good documentation in the US for public lands:
osm.wiki/United_States/Public_lands

Note that the tag leisure=nature_reserve (which you have on that feature) does render (green two-tone border).

My bad, thanks for fixing this!

As long as someone can travel to this location and verify the name, it seems fine to me.

Cool, thanks for contributing!

Hi dufekin,

I see that you added landuse=grass and natural=grassland to the Black Kettle National Grassland relation. Are you sure that the the entire protected area should be tagged in that way? It is not a typical practice to tag land cover on a boundary relation, but rather to tag only the actual areas of that land cover independently of the boundary. What are your thoughts on this tagging?

This changeset is being discussed at https://lists.openstreetmap.org/pipermail/talk-us/2021-November/thread.html - please participate in discussion.

This changeset is being discussed at https://lists.openstreetmap.org/pipermail/talk-us/2021-November/thread.html - please participate in discussion.

Hi, can you explain why you added this tag? nsme:en is redundant in the United States.

Looks good to me. I agree with removing this motorway island and changing it to match the surrounding highway.

Apologies for the large bounding box, This was not intentional - I must have somehow mixed two different edits.

I realize this is two years too late, but @user_5359, rather than deleting new POIs, please try to improve them. The POI added by turnkit was clearly not spam, it just needed some additional tags. It is incredibly discouraging to treat new users in this way.