Open gregbunce opened 1 year ago
Cartography is the main reason I can think of. Navigation could be another use case. Using the points as the destination for directions or emergency response when there is an injury on trail x which is accessible from trailhead y.
I could see using this layer in CAD datasets as a point of interest/common place
Imagine putting together an interactive trails map. If I was on a ride, run, or hike in an unfamiliar area, I'd want to know what amenities are available at the trailhead at the start and along the way (thinking of all the different trailheads along the JRT, MCT, BST, etc). Sometimes a vault toilet is the most beautiful structure in the whole world.
If I was developing a city's active transportation plan, I'd want to know what the nearby trailheads have, or what amenities are at trailheads not owned/maintained by the city. This could impact what facilities we plan for/build.
For creating access to trails/parks metrics, amenities probably don't matter. I know a better trailhead dataset would have been useful for the metrics I created for the the Healthy Places Index.
My cousin has asked me a couple different times "is that an official BST trailhead? Who controls access?"- so informing the public what trailheads are official vs social could be critical.
Summary of comments thus far:
What are some uses cases for this layer? This list will help us to better determine what the ugrc dataset schema should look like.