Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TrailAssist - find and reconcile differences between agency datasets and OSM #24

Open
mojodna opened this issue Apr 11, 2015 · 4 comments

Comments

@mojodna
Copy link
Contributor

mojodna commented Apr 11, 2015

OpenStreetMap is a fantastic repository of facts on the ground.

However, sometimes those facts on the ground (social trails) don't match a park manager's intentions.

We intend to create a proposal that allows social trails to be tagged in such a way that they can be filtered by those who wish to respect agencies' wishes while retaining them in the data, both to prevent them from being re-added (without appropriate tagging) and to accurately represent conditions on the ground (knowledge which can potentially help mitigation of their impacts).

We would also like to build a tool that allows the data available for a given area to be visually compared to GIS data provided by a park agency, facilitating tagging improvements and improved coverage. We could incorporate Strava's Slide tool in order to improve trail alignments using the "field observations" of many unwitting athletes.

@ryanbranciforte
Copy link

This is great Seth! We've been about this as well as we are very focused on helping agencies both utilize OSM and other non-agency datasets to improve their own data as well as improve the data that shows up on third party sites/apps and OSM. It would be ideal to also include OpenTrails as a part of the solution.

Look forward to seeing this come together and help out!

@danrademacher
Copy link

Education, audience:

  1. public -- what is a social trail and why should i care
  2. agencies --
  3. mappers --
  4. developers/data consumers --

Technical goals:

  1. identify trails not present in one dataset or the other
  2. see differences in alignments
  3. see metadata disagreements
  4. facilitate updating names and metadata
  5. adding data
  6. removing data
  7. improving alignments
  8. Esri compatible export tool for results

@danrademacher
Copy link

Data layers:

  1. Agency data
  2. OSM data
  3. Strava as the background

@danrademacher
Copy link

then plug those layers into id -- to trace and etc.
surface into id with Slide integration, so you can snap to it -- or just copy the alignment from one to the other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants