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

Trailhead Blitz: visitor documentation of trail access points #1

Open
alanjosephwilliams opened this issue Jun 3, 2014 · 1 comment

Comments

@alanjosephwilliams
Copy link
Member

(This initial issue thread captures a conversation that occurred on another repo)

Let's figure out a cool way for the community to contribute trailhead data by going out into the field and taking photos! It would be great to come away with something that would let people put photos in and get PLATS trailhead data back out.

@jmoe

What's the linking of photos to trails look like in this idea? Is it photos linked to a specific trail manually or linking to geotagged photos or both?

@anselmbradford

Not sure yet! :-) But I believe photos would end up being linked to Trailheads, which are linked to Trails. Totally spitballing here but I imagine a workflow like

  1. User takes new photo with mobile device (location is pulled from GPS), or selects existing photo (location is pulled from EXIF data)
  2. User reviews and is able to verify or correct location (sort of like how Uber allows user to specify exact pickup location) on a displayed map (that hopefully displays existing PLATS data for area)
  3. User confirms location, adds a Name, maybe some other metadata like "kiosk", "water", "bathrooms", etc., maybe some narrative description or comments.
  4. Trailhead is created based on location, submitted to some backend for storage and retrieval. Photo is associated to Trailhead and also stored in backend.
  5. Based on location app can suggest nearby trails that the Trailhead may be associated to, let's user verify.

At this point an admin interface could be provided to park agencies to confirm Trailheads and use photos. Trailheads themselves would have photos but also by association Trails would have the the photos from the trailheads but also potentially (outside the scope of this idea) at other points along the way.

Worth noting here is that PLATS itself does not currently support the concept of photos, so this would need to be handled solely by the implementation.

Hope that helps!

@jmoe

Perhaps for a prototype the Flickr API could be used to pull in geotagged photos. Then all the photo management could be handled by Flickr (https://www.flickr.com/services/api/flickr.photos.search.html).

@anselmbradford

Yup! That's exactly what we did for http://www.transitandtrails.org. There are some issues to be aware of with doing that though, specifically around licensing and terms of service. So just be cognizant if that is the implementation. We are hoping to provide a photo storage option as part of an outdoor platform product we are building called OuterSpatial. It's almost ready for testing, we hope to provide free early access at the event, as an option to be evaluated by developers.

@jmoe

Are you thinking about something similar to Everytrail (http://www.everytrail.com/)?

@mtnbkr1

@alanjosephwilliams alanjosephwilliams changed the title Project Idea: Trailhead Blitz Trailhead Blitz: visitor documentation of trail access points Jun 3, 2014
@jmoe
Copy link

jmoe commented Jul 23, 2014

In the interest of updating any interested parties. We took a stab at this with http://www.traileditor.org

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

2 participants