amenity
commented
4 years ago 
Data
Austin Transportation
- Active Mobility Projects (Interim Project DB, ATSD, Nathan Wilkes)
- Development Mitigation
- Emerging Projects
- High Injury Network (Vision Zero)
- High Injury Roadways (Vision Zero)
Public Works
- 2016 Bond — Substandard Streets and Capital Renewal
- Sidewalk Projects (Colleen)
- Safe Routes to Schools — Intersections, Sidewalks, Street, Trail
- Street and Bridge Service Plan — FY20, FY21, FY22
- Urban Trails — Construction 2020, Design and Engineering Report 2020, Improvements 2020
Watershed
- High Risk Erosion Areas
- High Risk Water Crossings
- 2016 Bond — Corridors, Regional Mobility
- TXDOT Projects
Tabular view
-
Uses Data Tables
-
By default renders polygons visible in map extent
-
Can be unhooked from map so that table can show all record
Map view
- Vector tiles via Mapbox — would use OpenLayers if he could do it again; Mapbox is rock-solid but not using much of the functionality
- Martin does translation from PostGIS table into vector tiles; Docker; binary WFS server
- Performant combination — seems fast even on Frank's "resource starved" server
Associations/queries
- Geometries can be compared based on any attribute
- Features have nothing in common in terms of attributes; come from various sources
- Did not attempt to standardize at all, just
- Unique ID
- Name
- Hand-selected whitelist of attributes; no way to access any sensitive data
Tech
- Backend written in Pearl
- Martin written in Rust
- Frontend vanilla Javascript
Upcoming features
- Dynamic connection between various datasets and PostGIS DB
- Sortable tables based on
- Distance of projects
- Number of projects associated, e.g. which of these areas has the greatest number of projects associated with it
Moped thoughts
- @johnclary: Should we consider using the VZ location polygons for Moped project geographies instead of free-hand drawing a shape or selecting street segments, the user selects all locations polygons that intersect with their project area?
- @JaceDeloney points out that this would be a step towards addressing the Modifiable areal unit problem that could come up in Moped. We should push for standardized street segments.
- Does QGIS (or other OSGeo solutions) have a place in our stack?
- Where does Moped fit in? Moped will standardize some of these datasets and provide a single point of integration.
Objective
The VIsion Zero team has been building a geospatial tool to help understand what work may be happening or planned for at some of our highest Vision Zero comprehensive cost locations. It will also be used by the 2018 Vision Zero bond engineer team.
Frank has gotten it to a good alpha version and there are some interesting aspects that may fit nicely with the MOPED concept as it moves forward
Participants
8/7/20 — John, Jace, Mateo, Frank, Lewis 8/14/20 — Sergio, Mike, Frank, Amenity