-
Notifications
You must be signed in to change notification settings - Fork 6
Description
The realtime feeds in the attached spreadsheet do not contain any entity label (vehicle position, trip update, service alert). This is due to the resource.features not being populated by TDG which results in the absence of labels during the import.
This is caused by 3 possible reasons:
- The TDG app/process to parse realtime feeds does not successfully detect the type of the feed (and so this propagates to our system during the import). This sometimes occurs despite the feed being in protobuf format which suggests an issue with TDG process.
- The realtime feed is not in the protobuf format, so there is no entity that can be attributed to the feed. I am able to parse these other formats (xml and json) to detect which type of realtime feed they are. These are labelled in the attached spreadsheet. We can decide how to present these feeds because they are not in the official protobuf format.
- The agencies themselves are not producing any valid realtime data at all, which results in no entities being present. This would be an issue to raise directly with the agencies.
Any of these realtime feeds that are producing realtime data whether in protobuf, json or xml format are highlighted green in the attached spreadsheet.
Finally, some of these feed can be intuited by looking at the URLs. Although some feeds are not producing any realtime data, the URL may look like:
https://proxy.transport.data.gouv.fr/resource/fluo-solea-mulhouse-gtfs-rt-service-alert?token=xdgqKBTAzhw4DSPz6zeGc4c5eW0LhwztcGv4-vpzP4U
We can assume that this feed is for service alerts. However, we must decide whether to label it as such because its not actually producing any data... These types of feeds are highlighted in orange in the attached spreadsheet.