reverting a changeset with fake edits

changeset/150635424

reverting a changeset that added fake data (not a park)

changeset/150633903

reverting a changeset that added fake data (this is not a park, it is a school)

changeset/150633744

reverting a changeset that added fake data

changeset/150633425

reverting a changeset that added fake data

changeset/150633374

reverting a changeset that added fake data

changeset/150633351

reverting a changeset that added fake data

changeset/150633318

reverting a changeset that added fake data to the map.

changeset/150633116

reverting a changeset that added fake data to the map.

changeset/150633025

Hello again, Thanks for your interest in OpenStreetMap. OpenStreetMap is a real map used by thousands of people everyday for many purposes, including disaster response, navigation, business, and many other things. Please only add real information to the map that you know to be accurate. We are having a discussion on the forum about this topic: https://community.openstreetmap.org/t/beware-of-fake-beaches-pokemon-go/112413 I invite you to join.

Reverting a changeset that used a source that is not allowed.

changeset/150621422

Hello, Welcome to OpenStreetMap! Thanks for your edit to the map. Unfortunately, when editing OpenStreetMap we are not allowed to use Google Maps, Google Street View, Google Earth, or any imagery from Google Maps. This is due to Google's Terms of Service. Violations can put you, the OpenStreetMap project, and users of OSM data at risk legally.

Also, it looks like you have completely removed the highway tag. As long as this is a road - private or not - it should have a highway tag. To indicate that it is private, adding access=private., which you did, is sufficient.

Not a beach based on Bing aerial imagery

Hello, the "beaches" you have added do not appear to be beaches in the available imagery. Could you clarify why you believe these are beaches. Also, beaches should be mapped as areas.

This doesn't look like a beach. It looks like an area where boats dock. Also, we generally map beaches as areas, not nodes (aka points).

This doesn't look like a beach.

Good to have what I assume to be the correct road names. You might consider adding a "source" to such changesets. It would be best if the source was some publically available map the state publishes (NOT a commercial source like Google Maps), second best would be something like "local knowledge - I am the superintendent of this park" (based on your user name I assume that is true, but user names can be misleading) Happy mapping!

Hello again, The fact that a road has been "abandoned" by a land manager is not alone reason to delete it from OSM. If the road still exists physically, it would be better to leave it and tag it access=no.

Hello, Welcome to OpenStreetMap. It is good to have input from the land manager. A couple of points about this edit. First, you should connect the Wall Fork Trail to the road (way/1277267654) at what appears to be a trail head. This will allow routing engines to route trail users from the parking area onto the trail, or from the Hoffman Hollow Interpretive Trail to the Wall Fork Trail. Second, the new trail (abandoned road) has been mapped to be coincident with the edge of the treed area (natural=wood). In reality, it probably isn't exactly coincident, and should be mapped separately. In fact, the Strava Global Heatmap shows the trail as being up to 27 meters from where it has been mapped.

Reverting a changeset that used a source that is not allowed.

changeset/150549422