RTS REST Static Schedule Data
Lines are the routes that buses run along. These are different than routes in that they are separated out deeper than the routes visible in our schedule documents. For example, the 1 route would be different from the 1X/8X route, even though the 1 Park/Lake schedule would show both.
||Returns a list of lines available for the current pick period. This table displays the Line Name, which allows you to find what lines pertain to what name.
||Returns a list of lines which are split into the directions the line travels. Each line has 2 (or potentially more) directions that it is split into. In the case of 1 Park/Lake, it is split into Eastbound and Westbound segments.
||Returns a list of the groups that lines are divided into.
||Returns a list of the stops along a line given a line direction from the Lines method above.
A trip is each individual trip that a bus will make along a line. These methods allow you to find what trips are running on a particular line on a particular date.
||Returns a list of trips available. This method can be refined by providing a Line Direction from the Lines method above and a date in yyyymmdd format.
||Returns a list of event times along a given trip. Events can include pull out or pull in, regular stops, driver breaks or driver switches.
A pattern is a particular combination of stops at which a bus stops while doing a trip along a line. On a given route, the bus may skip certain stops at certain times of day or take an entirely different path along the roads, and each of these combinations is a different pattern associated with the line.
||Returns a list of patterns available. This method also displays the text that shows on the bus' head sign, and is what the customer on the street sees as a bus comes down the street.
||Returns a list of pattern segments associated with a pattern. A bus headed westbound along 1 Park/Lake would have 2 patterns; one for the east side of the city and one for the west side of the city.
A stop is any location that a bus will stop. This could be anything from a street stop to the RTS garage. These methods allow you to find information about the stops, and also determine when a bus is scheduled to stop at any particular stop along its route.
||Returns a list of stops available. The results can be refined by providing a Line Direction from the Lines method above or a Pattern from the Patterns method above.
||Returns a list of stop patterns, which are the stops along a pattern and the order in which a bus stops at them. This also provides a field called StopNum, which is used to identify the time that a bus stops at a particular stop using the StopTimes method.
||Returns a list of times in which a bus stops at a sign. This can be used to determine all the times that a bus stops along its path and where it stops. The results can be refined by providing a Line Direction from the Lines method above or a Trip from the Trips method above.
A service is how the schedule system determines what trip is run on what day (or combination of days). A service includes Weekday service, Saturday service and Sunday/Holiday service.
||Returns a list of service groups available. This response also shows the pattern of days that a service covers (SMTWTFS) in binary format (0111110 for weekdays, for example) and the name of the service grouping. A number of services can be combined into one group.
||Returns a list of service groups, which links the services to the master service groups.
||Returns a list of services available. This includes the name of the service for reference.
||Returns a list of exception combinations associated with a service group. The exceptions further clarify what day a trip runs on by excluding certain days, and can be found in the Exceptions methods below.
An exception is used to clarify when a particular trip will run or not run. As an example, with the RCSD partnership there are certain trips that only run on school days, which would have an exception combination tied to them.
||Returns a list of exception combinations available. This response also shows the name of the exception combination. An exception combination might reference, for example, RIT Only trips, which may be made up of a combination of exceptions which tell various trips to run only on particular days.
||Returns a list of exception combinations, which links the exceptions to the master exception combinations.
||Returns a list of exceptions. This response also shows the name of the exception, to clarify what each exception covers.
The calendar methods are used to limit service on particular days using exception information. This links the exception combinations to particular days.
||Returns a list of calendar days and the exception combination that is associated with each particular day. Through the exception combination, one can determine which trips run on that day.
||Returns a list of holiday dates and the service group that they fall on. This is used to determine what non-holiday service days should run holiday service.