Inconsistent Trip Counts based on GIS Exports

[PPaulsonOregonDOT]

The number of trips recorded via GIS export appears to vary widely depending on whether you select a specific date or not. This does not appear to be related to issue #204 , but instead to how the individual feeds are constructed. Below I've attached a sheet listing the routes where the number of trips recorded as individual entries in the GIS file did not match between an export made with no date selected from the July 2019 V2 database and one with Weds, 7,17.19. Of the 312 routes in the database, 160 are on this list, for a number of reasons:

1. The service runs Thurs-Mon, like the Columbia Gorge Express and Amtrak Connector in Corvallis, and therefore, doesn't have any trips on Weds, but has trips on another day, which are reflected in the no-date selection feed. (This issue can be resolved by merging GIS exports from 7 days, and noting that in any reports generated using those files)

2. Trips are doubled in the no-date selection because the GTFS feed has two or more service_id's, usually reflecting an anticipated service change or difference in Saturday/Sunday service and the GIS export produces an entry for each trip in all service alignments when a date isn't specified.

Unmatched_Routes_Data.xlsx