Project: Mobility Bond Viewer

[atdservicebot]

This interactive public-facing map of mobility bond projects will help PIO communicate the status of bond-funded mobility efforts on a holistic, citywide scale.

Background

The project addresses the need for more dynamic, accessible information on bond-funded mobility projects in response to audit recommendations and user feedback. By transitioning from static maps to interactive visual tools, the Public Information Office (PIO) aims to improve public engagement and compliance, making vital city infrastructure information more transparent and easier to navigate.

Scope & Deliverables

We are tasked with updating the Mobility Bond pages on the Open Data Portal to include interactive maps, project information, and links to detailed fact sheets, streamlining user experience. This includes discontinuing outdated practices in favor of a more integrated approach. The project is constrained by the need to align with existing content management systems and workflows without overburdening the Digital Technology Services (DTS) team.

Desired Outcomes

The successful implementation of interactive maps will lead to increased user engagement, improved compliance with audit recommendations, and a more informed public. Success metrics include user feedback, page visitation rates, and an increase in data transparency and accessibility.

Timebox

Preliminary stages have been scoped from January to February for geo scoping, with new project scoping in March. However, the total project completion time will depend on DTS team availability and technical challenges encountered.

References

• Vision Zero Viewer map example: https://visionzero.austin.gov/viewer/map
• Current Mobility Bond pages needing updates:
  • https://data.austintexas.gov/stories/s/sa9q-m9wz
  • https://data.austintexas.gov/stories/s/ty8m-hcfi

Request details

• Requested by: Jack F.
• Executive sponsor: Anna M.
• Date: 1/2/24

-- This Github issue represents a project of Transportation Public Work's Data & Technology Services team. Project status is documented regularly in the comments below. Request ID: DTS24-111745

[amenity]

Notes for this meeting:

• Are these projects what we want on the map?
• Is there a reason we can't use AGOL for the MVP here? cc/ @andrewshensky

[amenity]

Meeting with Jack F. 3/7

Andrew, Chia, Patrick, Amenity

Ask: Improve mobility bond pages on Open Data Portal

• Current page examples
  • https://data.austintexas.gov/stories/s/sa9q-m9wz
  • https://data.austintexas.gov/stories/s/ty8m-hcfi
• Keep "What's New" page (Socrata Stories)
• Stop building the individual bond pages (see bullets here) and move those to Drupal
• Add AGOL map to this page so that users don't need to find relevant information by going through tabs
  • Dynamic (daily updates) map
  • Hides irrelevant/ private info
  • Moped data (PIO no longer sole maintainer data) 

Proposed Minimum Viable Product (MVP)

• Build AGOL Map, using Moped data a la Moped Database Viewer
• Build specific "Bond" view layer
  • Fields 
    • Program name
    • Project name
    • Date of construction
    • Status 
      • Construction and Post-Construction only (already have a resource for Planned and In-Design)
      • Funding source (can be multiple)
  • Query to capture the bond-funded products
    • "Mobility Bond" tag?
    • Funding source contains "Bond"?
  • No sidebar filters necessary - user navigates by zooming and dragging, click "More info" in project modal to learn more (this goes to mailers sent to the neighborhood uploaded in Drupal)

Process notes

• Moped data quality issues
  • Inconsistent use, e.g. ☝️tag vs. funding source
  • Project naming conventions 
• Ways to address these
  • Communication with end users
  • Small features, e.g. automatically applying a tag when certain funding sources are used
  • PIO can make corrections directly
  • Exclude problematic fields like "Description" for now 

Questions

• Are child projects, e.g. signals, accurately nested into their parent projects? 
  • Not sure 🙂

Next steps

• Write specs
  • Chia/Amenity/Patrick will identify best query to start with
  • Patrick send to Jack to verify it has the projects he expects
• Implementation ~ month after specs are handed over
  • Andrew will put together the view layer
  • Zach will use Experience Builder (ESRI project with a long lifespan) 
• Jack will update users at 3/19 Moped User Group Meeting

[amenity]

@chiaberry @patrickm02L - let's huddle on what query to use. Then Patrick can write an issue up for the MVP implementation for @andrewshensky.

[patrickm02L]

@chiaberry @patrickm02L - let's huddle on what query to use. Then Patrick can write an issue up for the MVP implementation for @andrewshensky.

16179