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

Alerts: Trails lat/long #14

Open
2 tasks done
shua123 opened this issue Nov 19, 2016 · 3 comments
Open
2 tasks done

Alerts: Trails lat/long #14

shua123 opened this issue Nov 19, 2016 · 3 comments

Comments

@shua123
Copy link

shua123 commented Nov 19, 2016

  • For trail system alerts, have ability to enter a lat/lon coordinate.
  • Output lat/lon coordinate somehow in alerts json
@shua123 shua123 modified the milestone: Status/Closure Tool Dec 14, 2016
shua123 added a commit that referenced this issue Dec 16, 2016
@shua123
Copy link
Author

shua123 commented Dec 16, 2016

Add validations for lat/long:

  • If one exists, make sure both exist
  • Check values to make sure they fall within county bounding box.

@shua123
Copy link
Author

shua123 commented Jul 17, 2017

@versatilehuman With our current setup of trail system + segments impacted, what is the current importance/priority of custom lat/long option? Do we still need this now or should we hold off to see use/feedback on current form?

@versatilehuman
Copy link

@shua123 With the way this has evolved I'd say we can hold off on this feature. "Trail segments ABC near XYZ locations" is pretty good and we can always add further description. How we would even display or link to a lat/long is still an open question. So unless we get some strong feedback that what we are giving users is not enough, I think we can hold off.

@shua123 shua123 modified the milestones: Low Priority - Future, Status/Closure Tool Jul 31, 2017
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