Next phase ideas

[dabreegster]

Not likely to work on these yet, but tracking bigger ideas

• [ ] Link to or embed Scheme Browse maps with relevant layers for some questions
• [ ] If possible and appropriate, automatically look up values from those layers
• [ ] Have some kind of cloud storage for the files, allowing version control and various collaboration patterns
• [ ] Make the cross-section tool much more Streetmix-like
• [ ] Explore data sources and automation for will-it-fit checks
• [ ] For internal use, replace the DALOG approach with integration with a DB/CMS
• [ ] #44
• [ ] Automatically detect SA11 from OS pavement polygons
• [ ] Integrate quality control workflow

[dabreegster]

Cross-section thoughts...

• Assume we can generate or get access to an "available width" dataset
• User defines the desired route as a linestring
• User defines a set of cross sections. Each one has a min and max width required.
• Automatically, we determine which cross sections fit along different parts of the route. Where there are options (a preferred section with min widths, or a compromised section with max widths), the user can pick tradeoffs. We can visualize the thickened street feature polygons along the linestring
• Find the pinch points and sections that won't fit, and point them out easily
• Automating some form of this against LCWIP data or a route network derived from PCT or od2net demand data could reveal "quick wins"