johnclary
commented
4 years ago My initial thoughts: I see three components to this work:
Sign data capture and management
Needs
- Define a process to systematically survey all speed limit signs, and track progress as survey areas are complted.
- Ability to capture sign location and condition in the field
Solutions
- Thinking about the crosswalk data collection that @dianamartin did. Break the city into logical chunks (e.g. neighborhoods), assign them to collectors, mark them complete as the data is collected.
- Esri's new field collection tool. Can't remember what it's called, but Alan tested it out last year.
- Fulcrum
- Can we just use google street view?
Street width data capture
Needs
- Ability to track which street widths have been collected
- Ability to store street widths somewhere (e.g., street segments dataset)
Solutions?
- Nearmap
SMB Data Tracker / Work Orders
Needs
- ability to use existing points/have requesters drop points when submitting work order
- ability to automatically update asset status when work order is completed (e.g. from "Planned" to "Installed"
Solutions?
- New SMB Data Tracker UX for all of this
amenity
Enable transportation engineers to create street sign work orders from a mapping interface.
Background and Context
This project encompasses our work to support ATD's citywide prima-facie speed limit conversion from 30 to 25 MPH. Our work includes IT support for the systematic collection of speed limit sign locations, roadway widths, and SMB Data Tracker enhancements to allow for the easy creation of work orders related to these sign locations.
Resources
This Github issue represents a project of Austin Transportation's Data & Technology Services team. Project status is documented regularly in the comments below.