Feature: unmapped trails

[mmertsock]

Proposed enhancement: add support for a flag that indicates the park or trail system has trails but they are not mapped in the TrailsRoc app.

Use cases

• It can take a lot of time/effort to collect and prepare a full set of trail data in order to add a park to the map. We have a growing todo list of parks and trails to add, and it could take years to get through everything. It would be nice to just take 10 minutes to add a park pin to the map (and maybe its boundary and some parking locations) for discoverability while we work on building the actual trail maps. Examples: Dryer Road, Rob’s Trail, Brighton area parks
• Some locations have trails that are worth visiting, but we choose not to actually map the trails. This could be for copyright reasons, or the trails are informal or very short, private property, etc. For these, a nice compromise would be to show these locations on the map for discoverability and driving directions, but leave the trails unmapped. Examples: Letchworth/FLT, Grimes Glen, small city parks, maybe Cumming Nature Center

Implementation

• Add a Boolean property trailsRoc-isUnmapped to park and trail system features. If unspecified, default value is false
• If isUnmapped is true, show a text label in various places in the mobile and web apps indicating that the location has trails not shown in the app, with a “for more info” link using the URL specified by the existing trailsRoc-url property
• If in the future we decide to add that location’s trails to the map, we simply set the isUnmapped flag to false

This allows us to use all the existing map style code to render park pins and boundaries, set up relationships with other POI (e.g. parking), etc.

@mcbeth if you like this idea, I can implement this soon.

[mcbeth]

I do like the idea. My right hand is broken, and extensive typing and any mousing is painful and slow right now. It's going to be a while before I can start putting trails in again

…

On August 9, 2020 4:57:49 PM EDT, Mike Mertsock ***@***.***> wrote: Proposed enhancement: add support for a flag that indicates the park or trail system has trails but they are not mapped in the TrailsRoc app.> > ### Use cases> > - It can take a lot of time/effort to collect and prepare a full set of trail data in order to add a park to the map. We have a growing todo list of parks and trails to add, and it could take years to get through everything. It would be nice to just take 10 minutes to add a park pin to the map (and maybe its boundary and some parking locations) for discoverability while we work on building the actual trail maps. Examples: Dryer Road, Rob’s Trail, Brighton area parks> - Some locations have trails that are worth visiting, but we choose not to actually map the trails. This could be for copyright reasons, or the trails are informal or very short, private property, etc. For these, a nice compromise would be to show these locations on the map for discoverability and driving directions, but leave the trails unmapped. Examples: Letchworth/FLT, Grimes Glen, small city parks, maybe Cumming Nature Center> > ### Implementation> > - Add a Boolean property `trailsRoc-isUnmapped` to park and trail system features. If unspecified, default value is false> - If isUnmapped is true, show a text label in various places in the mobile and web apps indicating that the location has trails not shown in the app, with a “for more info” link using the URL specified by the existing `trailsRoc-url` property.> > This allows us to use all the existing map style code to render park pins and boundaries, set up relationships with other POI (e.g. parking), etc. If in the future we decide to add that location’s trails to the map, we simplify set the isUnmapped flag to false.> > @mcbeth if you like this idea, I can implement this soon.> > > -- > You are receiving this because you were mentioned.> Reply to this email directly or view it on GitHub:> #30

-- Sent from my Android device with K-9 Mail. Please excuse my brevity.

[mmertsock]

ok, heal up! I might make some time to do some of this somewhat soon.