Each trip has a defined number of dates it runs on. This set of dates is called a
service pattern in tidytransit. Trips with the same servicepattern id run on the same
dates. In general, service_id can work this way but it is not enforced by the
GTFS standard.
set_servicepattern(
gtfs_obj,
id_prefix = "s_",
hash_algo = "md5",
hash_length = 7
)modified gtfs_obj with added servicepattern list and a table linking
trips and pattern (trip_servicepatterns), added to gtfs_obj$. sublist.
gtfs feed (tidygtfs object)
all servicepattern ids will start with this string
hashing algorithm used by digest
length the hash should be cut to with substr(). Use -1 if the full
hash should be used