Waze Pipeline

What's New

Check out the newest features and enhancements we've just released.

Waze jam record changes in v2.2.0 have been activated as the main JAM and JAM_POINT_SEQUENCE tables.
- Jam and jam_point_sequence records in the legacy process have been archived in the JAM_LEGACY and JAM_POINT_SEQUENCE_LEGACY tables. These tables will continue to be populated for at least 2 weeks at which point they will be permanently dropped.
- Jam and jam_point_sequence records in the updated model described in v2.2.0 are now being actively stored in the main JAM and JAM_POINT_SEQUENCE tables.
- All of your existing queries should work as expected. Additional fields in the jam and jam_point_sequence tables can be used to correlate these two types of records.

Waze irregularity records
- Waze irregularity data has been activated from this point forward.
- Tables for irregularity, irregularity_alert and irregularity_point_sequence have begun being populated from May 26, 2022 onward. Historical irregularity data is not planned for loading at this time.
- Please see the GitLab Waze wiki for more information on the irregularity data and the table structures. Irregularity_alert messages should link to the Waze alert message related to the irregularity if it exists. Irregularity_point_sequence messages should define the geographic boundary of the irregularity.

jam and jam_point_sequence records
- A jam_key_mapping table has been created to record a unique ID for each jam event.
- The jam_sdc_id key created in jam_key_mapping is also included in new tables for jam (jam_revised) and jam_point_sequence (jam_point_sequence_revised) data
- A reference jam record is noted in the jam_key_mapping table for each unique jam event. This allows an analyst to easily find basic geographical data on a jam event when multiple jam records were republished.
- Timestamps for each table are included along with batch IDs (elt_run_id) to allow the SDC Team and analysts to track when jam and jam_point_sequence records were loaded

Here are the features and enhancements we're working on... or at least we're thinking about working on them.

Following validation of the jam_revised and jam_point_sequence tables, we will rename those tables as the primary jam and jam_point_sequence tables. We will also continue to populate new records with the additional fields.

No changes have been made currently to the jam and jam_point_sequence tables. All of your existing queries should work as expected.
In fact, even after the tables have been fully upgraded, the existing fields and field names will remain unchanged. Your queries should continue to work as expected.