Tracking Dark Signal & Creation of a Waze Datafeed for Signal Issues

[atdservicebot]

What application are you using?

Data Tracker

Describe the problem.

We want to create an XML or JSON feed that provides traffic signals in "unscheduled flash" from https://data.mobility.austin.gov/signal-monitor to be consumed by/shared with Waze. This will provide automated traffic alerts to drivers of "Traffic Light Faults" similar to how Waze users can input them now.

Describe the outcome you'd like to see when this feature is implemented.

The first ask is to create the XML or JSON feed from our existing data from https://data.mobility.austin.gov/signal-monitor but filtered to just "unscheduled flash."

Long term, we'd like to also have a "manual override" list that amends the feed for any dark signals or signals we know are flashing but don't have working communications (wouldn't show up in the feed automatically).

Describe any workarounds you currently have in place or alternative solutions you've considered.

We have to manually input them into the Waze Reporting Tool and leaves us prone to stale or inaccurate data, so we rarely do it.

Is there anything else we should know?

Short term XML feed, hopefully within a month (ahead of SXSW and spring storm season)? Long term solution with amendment functionality, end of summer?

Requested By Lance B.

Attachment (413.87kb)

Request ID: DTS23-106370

[johnclary]

@ChristinaTremel the signal status data that Lance is referring to lives here: https://data.austintexas.gov/Transportation-and-Mobility/Traffic-Signals-Status/5zpr-dehc and is updated every 5 minutes.

Because this data is on the Open Data portal, the JSON feed already exists. This query returns the JSON feed of the dataset, filtered for signals in unscheduled flash (operation_state = 2):

https://data.austintexas.gov/resource/5zpr-dehc.json?$where=operation_state=2

☝️ this is going to be empty ([ ]) most of the time.

To test this, you can change the operation state to 3 to see all the signal with a comm issue:

https://data.austintexas.gov/resource/5zpr-dehc.json?$where=operation_state=3

In order for there to be a "manual override" like Lance describes, we would need to:

1. Add a new column to signal assets in the Data Tracker where MMC staff can set the override status - APPS
2. Update the signal status ETL to incorporate this override column.

Hope that helps :)

[johnclary]

@ChristinaTremel did you need anything else from us on this? cc @chiaberry

[ChristinaTremel]

@johnclary @chiaberry we will, but I need to work with Diana on the Knack side of this issue first. 🙂

[dianamartin]

Next Steps

In order for there to be a "manual override" like Lance describes, we would need to:

• Add a new column to the signal_assets object table in the Data Tracker where MMC staff can set the override status - APPS
  • [ ] Add field status_override(@chiaberry @johnclary - what type of field should this be? Multi-choice?)
    • [ ] options from existing Operation State field
• Update the signal status ETL to incorporate this override column. - DEV

[ChristinaTremel]

Diana and I asked John - create multi-choice status override field.

Right now, it pulls the signal data from ODP and the signal status from KITS. Filters out signals that have an issue. Signals that could be shown on the map is only as current as the ETL, which happens twice a day. When it comes to updating the ETL, it will be more work because we're assuming AMD will want a higher frequency of updates. Sync with Lance on how often he wants statuses to update.

We might be able to update the ETL based on modified dates that change. The script doesn't talk to Knack at all, but it will need to when we make this change. Should we ask if these changes should be made on KITS instead of Data Tracker since that's how the script is running currently.

[ChristinaTremel]

• We will not be able to use KITS to manually override the status
• MMC is requesting that this data is refreshed more than once a day. Would prefer for the data to be updated every time the modified date is touched.

[ChristinaTremel]

• Created the Waze datafeed in issue #14201 to identify signals in Unscheduled Flash
  • Checked in with Lance on 1/3/24 asking if he will also want to incorporate the dark signals status within the Waze datafeed we created & if so, what type and subtype these would be given
  • If he does want to update the Waze datafeed, I'll create a new issue to take notes on what we need to update.
• Working on incorporating dark signals to the Signal Monitor Page in issue #14912

[ChristinaTremel]

Notes from initial request on 2/9/2023

What application are you using?

Data Tracker

Describe the problem.

We want to create an XML or JSON feed that provides traffic signals in "unscheduled flash" from https://data.mobility.austin.gov/signal-monitor to be consumed by/shared with Waze. This will provide automated traffic alerts to drivers of "Traffic Light Faults" similar to how Waze users can input them now.

Describe the outcome you'd like to see when this feature is implemented.

The first ask is to create the XML or JSON feed from our existing data from https://data.mobility.austin.gov/signal-monitor but filtered to just "unscheduled flash."

Long term, we'd like to also have a "manual override" list that amends the feed for any dark signals or signals we know are flashing but don't have working communications (wouldn't show up in the feed automatically).

Describe any workarounds you currently have in place or alternative solutions you've considered.

We have to manually input them into the Waze Reporting Tool and leaves us prone to stale or inaccurate data, so we rarely do it.

Is there anything else we should know?

Short term XML feed, hopefully within a month (ahead of SXSW and spring storm season)? Long term solution with amendment functionality, end of summer?

Requested By Lance B.

Attachment (413.87kb)

Request ID: DTS23-106370

[Charlie-Henry]

Waze kept punting this back to us with pretty little details.

Thank you for sharing the data feed with us. We value your collaboration. We have reviewed your feed sample, and it is incomplete. Please follow the feed specifications and setup in the Feed Setup article.

I think we'll need to write a script to publish data in the format they require.