WFRC bikeways map - phase 2

[nathankota]

Benefit

• Provide the most up-to-date, mapped inventory of the multi-use pathway and on-street bike facilities, and proximate amenities/destinations (i.e. rec centers, school, grocery stores etc) and other context (AADT traffic volume and approximate speed limit -- or Level of Traffic Stress LoTS)
• Allow users to explore areas of interest to view bike-friendly transportation links, with full detail about the type of facility: class/subclass for on street bike facilities (e.g. buffered bike lane, sharrow route, etc), paved/non-paved for multi-use trails
• Allow users to use the interactive map to contribute geographic-specific edit suggestions to the map -- specifically new, updated, or missing links

Acceptance Criteria

• Feature Services wfrc-bike-map#5
• Figure out if this new derived dataset should be added to SGID
• Layout wfrc-bike-map#8
• GPS Location wfrc-bike-map#12

Notes

We have around 200 hours (PRJTASK0614068) on their general technical service contract left for this year.

Risks

• Time among priorities
• Scope creep

[stdavis]

Questions:

• The current app is built using plain JS and Esri Calcite components to make it easier for WFRC devs to contribute to the project. It's been months and they haven't been able to do anything with it. We will likely be doing all of the work for this project ourselves. Is this still the best option?
• Bert wants this app hosted at bikemap.utah.gov. Is this the best place for it? This likely means that we need to use the Utah Design System which means that the current layout/UI with Esri Calcite components likely won't work.
• Bert also wants us to host the data for this app which is derived from other SGID datasets. Is this a good candidate for the SGID? Do we want to take on the maintenance of the arcpy code that generates it?
• It appears that Bert has the interest from some folks from UDOT (Stephanie Tomlin satomlin@utah.gov, Jared Bowling jbowling@utah.gov, Neda Kiani fkiani@utah.gov). Do we want to involve them?