Research Request - VCTC- Missing Enghouse Location Information

[amandaha8]

Research Question

For VCTC, location information in the columns station name, stop id, and stop name are missing.

However, unlike RABA, VCTC's missing data is due to Kuba.

How will this research be used?

Part of our contactless payments dashboard uses location data. Transit agencies are also keen to know where passengers are boarding.

Stakeholders & End-Users

VCTC

Data sources

Enghouse

Deliverables

Fixed location data.

[amandaha8]

Check with Rebel about what to do since this is less of a data issue.

[amandaha8]

@mrtopsyt Do we need to follow up with Rebel about this?

[amandaha8]

• Dima to work on this.

[amandaha8]

Per Maarten's email on June 18, Enghouse doesn't receive any geographic data from VCTC. It's missing from Kuba, so we have to work this out between Rebel/VCTC/Kuba.

I would like to introduce you to Amanda and Anna.
They work at the California Department of Transport for the Division of Data & Digital Services and they'll provide you with insights based on data.
They are also facing the issue of missing data for VCTC, as we (Enghouse/Monet+) send through all the data that we receive from Kuba to the data warehouse of the DOT, but we can only do that with data that we actually receive.

[mrtopsyt]

This issue is not appearing for the new VCTC agencies. @mrtopsyt to check whether this is still occurring by looking at the VCTC intercity dashboards. @dima-rebel to look at all Enghouse dashboards, and itemizing where there are missing location rows between our dashboards and the Enghouse portal.

[amandaha8]

• Maarten has data from terminal provider but Enghouse can't push it to Metabase. He is working on it.
• Dima can follow up with Maarten on this.
• Anna: thinks this is only impacting one route?
• Action: look at empty null values. Amanda to do this. Look at null stop id, station ids.