Trails data/schema updates

[nathankota]

Benefit

The current trails dataset has a sort of "trails junk drawer" approach- there's a bunch of stuff in there, its not very clearly organized, and it's hard to know why some things are the way they are. An updated schema will make it more generally useful than being targeted towards a single use case or organization, and improved/updated data will obviously benefit everyone.

Furthermore, because the trails are on all our basemaps, this is a high-visibility layer. Errors/omissions are visible to everyone and hurt the credibility of our maps and data in general.

Acceptance Criteria

Immediate

• [ ] Triage current schema/attributes
  • Yes/No for inclusion in base maps to help clean that up

Ideal

• [ ] An updated schema, both published and implemented
• [ ] Pull data from OSM
• [ ] Up-to-date trail data with non-trail features removed

Notes

Risks

• Pushback from partners and data sources
• The incompatibility of the schemas from the vast number of source datasets
• Lack of good data
• Confusion around the core purpose of this dataset leading to complicated schemas and data (looking at you, multi-modal network analysis)

[gregbunce]

@jacobdadams let me know how'd you like to proceed with this one. there are a lot of directions we can go with it. also, the efforts that OSM is making should be factored into the next steps for this layer. i'll let you drive it, but happy to play a role.

[nathankota]

moved to Q4 uncommitted