Changeset: 126150251
added new paths, and removed possible MTB trails that do not appear to exist but are listed in Trailforks. The names of these removed trails in OSM used GPS data and names that exist only in Trailforks, and thus cannot be included in OSM unless GPS traced
Closed by BPTT
Tags
changesets_count | 552 |
---|---|
created_by | iD 2.21.1 |
host | https://www.openstreetmap.org/edit |
imagery_used | Bing Maps Aerial;Esri World Imagery (Clarity) Beta;Mapbox Satellite |
locale | en |
resolved:crossing_ways:highway-highway | 6 |
resolved:crossing_ways:highway-waterway | 1 |
resolved:disconnected_way:highway | 1 |
source | local knowledge;aerial imagery;streetlevel imagery |
Discussion
-
Comment from ElliottPlack
Hello there. The DWG received a complaint about this mass deletion of trails. How can you be sure the data was copied directly from TF, and not the reverse? I see the the source for the trails included a GPX file as the source. Further, I can see there is evidence of trails there on Strava's heatmap, which is an allowable source for OSM. Therefore, they do not exist "only" in Trailforks, but also Strava. I find it unlikely that a trail in both of those sites does not actually exist on the ground, unless it was physically closed. In the case of a trail being physically closed, it is best not to delete and instead mark it as closed.
Additionally, I saw you'd changed a footway that was marked as no bikes/horse, to a path with those access restrictions lifted. The person that originally added that information, did they do that in error?
Please help us understand why these trails were all deleted en masse. In the future, if you think something "cannot be included in OSM", you should reach out to the DWG first, so we could avoid all of this.
Thanks,
Elliott Plack
OSMF Data Working Group
data@openstreetmap.org -
Comment from BPTT
Thanks. Now that I know about the Data Working Group, I will be sure to reach out in the future. I was under the impression that using data from Trailforks in OSM violated Trailforks' user license policies - is this not the case? Moreover, the pathways I removed were not simply inaccurate to ground truth, but they also crossed many other ways without intersecting nodes, and many ways simply do not exist at all.
Which footway in particular are you referring to?
- 1094326614, v1
- 1094326615, v1
- 1094326616, v1
- 1094326617, v1
- 1094326618, v1
- 1094326619, v1
- 1094326620, v1
- 1094326621, v1
- 1094326622, v1
- Constitution Drive (1094326623), v1
- Cardinal Drive (1094326624), v1
- 1094326625, v1
- North Side Path (1094326626), v1
- 1094326627, v1
- North Side Path (1094326628), v1
- 1094326629, v1
- North Side Path (1094326630), v1
- South Side Path (1094326631), v1
- 11930698, v3
- 11931067, v3
- 10022576727, v1
- 10022576728, v1
- 10022576729, v1
- 10022576730, v1
- 10022576731, v1
- 10022576732, v1
- 10022576733, v1
- 10022576734, v1
- 10022576735, v1
- 10022576736, v1
- 10022576737, v1
- 10022576738, v1
- 10022576739, v1
- 10022576740, v1
- 10022576741, v1
- 10022576742, v1
- 10022576743, v1
- 10022576744, v1
- 10022576745, v1
- 10022576746, v1
Welcome to OpenStreetMap!
OpenStreetMap is a map of the world, created by people like you and free to use under an open license.
Hosting is supported by Fastly, OSMF corporate members, and other partners.
https://openstreetmap.org/copyright | https://openstreetmap.org |
Copyright OpenStreetMap and contributors, under an open license |