New Rule Proposal: Feed-wide error given certain threshold of scheduled Trips not being accounted for in Trip Updates feed

[evansiroky]

Summary:

An error should be raised whenever a "vast majority" of Trips that should be in service at the time a Trip Update feed was downloaded are not accounted for in the given TripUpdate records in the Trip Update feed.

Steps to reproduce:

Given a TripUpdate dataset and its associated GTFS Schedule dataset When when the validator has compiled a list of all trips that should be currently in service and has scanned through all TripUpdate entities in a Trip Updates feed and does not find a "vast majority" of Trips that were expected to be in service being accounted for in the TripUpdate records Then the validator should raise an overall flag that the Trip Updates feed as a whole did not have a "vast majority" of Trips being accounted for in the Trip Update feed.

Expected behavior:

The GTFS-Realtime Best Practices state:

Feeds should cover the vast majority of trips included in the companion static GTFS dataset. In particular, it should include data for high-density and high-traffic city areas and busy routes.

The GTFS Validator should flag when the "vast majority" of Trips were not accounted for at the time that the trips should have been in service.

Observed behavior:

An error or warning is not raised for this problem at this time.

etc

• This issue seeks to add more detailed scope to https://github.com/MobilityData/gtfs-realtime-validator/issues/119.
• The definition of "vast majority" needs some kind of percentage given to it