[{"data":1,"prerenderedAt":262},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fconcepts\u002Ftrips-schedules":3,"_apollo:default":258,"_apollo:stationEditor":259,"_apollo:feedManagement":260,"_apollo:transferAnalyst":261},{"id":4,"title":5,"body":6,"description":249,"extension":250,"meta":251,"navigation":253,"path":254,"seo":255,"stem":256,"__hash__":257},"content\u002Fdocs\u002Fconcepts\u002Ftrips-schedules.md","Trips & Schedules",{"type":7,"value":8,"toc":237},"minimark",[9,34,39,51,54,88,92,102,105,131,136,139,166,176,180,190,194,207,211,214],[10,11,12,13,18,19,23,24,28,29,33],"p",{},"Trips represent scheduled transit service along a ",[14,15,17],"a",{"href":16},"\u002Fdocumentation\u002Fconcepts\u002Froutes","route",". Each trip defines the specific sequence of ",[14,20,22],{"href":21},"\u002Fdocumentation\u002Fconcepts\u002Fstops","stops"," served at particular times. Trip data is imported from ",[14,25,27],{"href":26},"\u002Fdocumentation\u002Fconcepts\u002Fsource-feeds","GTFS source feeds"," as part of each ",[14,30,32],{"href":31},"\u002Fdocumentation\u002Fconcepts\u002Fstatic-gtfs-feed-versions","feed version",".",[35,36,38],"h2",{"id":37},"trips","Trips",[10,40,41,42,50],{},"Trips are ",[14,43,46],{"href":44,"target":45},"https:\u002F\u002Fgtfs.org\u002Fdocumentation\u002Fschedule\u002Freference\u002F#tripstxt","_blank",[47,48,49],"code",{},"trips.txt"," entities imported from GTFS. A trip represents a single journey along a route at a specific time. Multiple trips typically operate on the same route throughout a service day, with each trip serving the same or similar stop sequences.",[10,52,53],{},"Key trip attributes include:",[55,56,57,65,71,77],"ul",{},[58,59,60,64],"li",{},[61,62,63],"strong",{},"Trip headsign",": The destination or direction displayed to riders (e.g., \"Downtown\" or \"Airport\")",[58,66,67,70],{},[61,68,69],{},"Direction",": Binary indicator (0 or 1) for travel direction, typically outbound vs. inbound",[58,72,73,76],{},[61,74,75],{},"Block",": Groups trips operated by the same vehicle, enabling transfer time calculations",[58,78,79,82,83,87],{},[61,80,81],{},"Shape",": Geographic path the vehicle travels (see ",[14,84,86],{"href":85},"\u002Fdocumentation\u002Fconcepts\u002Froutes#route-geometries","route geometries",")",[35,89,91],{"id":90},"stop-times-schedules","Stop Times & Schedules",[10,93,94,95,101],{},"Stop times define when a trip serves each stop along its route. This data comes from ",[14,96,98],{"href":97,"target":45},"https:\u002F\u002Fgtfs.org\u002Fdocumentation\u002Fschedule\u002Freference\u002F#stop_timestxt",[47,99,100],{},"stop_times.txt"," in GTFS feeds.",[10,103,104],{},"Each stop time includes:",[55,106,107,113,119,125],{},[58,108,109,112],{},[61,110,111],{},"Arrival and departure times",": When the vehicle arrives at and departs from each stop. If specific times are not provided for a stop, Transitland interpolates times between designated \"timepoint\" stops before and after.",[58,114,115,118],{},[61,116,117],{},"Stop sequence",": The order in which stops are visited",[58,120,121,124],{},[61,122,123],{},"Pickup and drop-off types",": Whether passengers can board, alight, or both at each stop",[58,126,127,130],{},[61,128,129],{},"Timepoint",": Indicates if the time is exact or approximate",[132,133,135],"h3",{"id":134},"service-dates","Service Dates",[10,137,138],{},"Trip schedules operate on specific dates defined by service calendars:",[55,140,141,154],{},[58,142,143,146,147,153],{},[61,144,145],{},"Regular service",": Defined in ",[14,148,150],{"href":149,"target":45},"https:\u002F\u002Fgtfs.org\u002Fdocumentation\u002Fschedule\u002Freference\u002F#calendartxt",[47,151,152],{},"calendar.txt"," with weekly patterns and date ranges",[58,155,156,146,159,165],{},[61,157,158],{},"Exceptions",[14,160,162],{"href":161,"target":45},"https:\u002F\u002Fgtfs.org\u002Fdocumentation\u002Fschedule\u002Freference\u002F#calendar_datestxt",[47,163,164],{},"calendar_dates.txt"," for holidays, special events, or service changes",[167,168,169,170],"info",{},"\n  ",[10,171,172,175],{},[61,173,174],{},"Service dates vs. calendar dates:"," GTFS uses a \"service date\" concept where a service day can extend past midnight. For example, a late-night trip departing at 1:00 AM on Saturday morning is often considered part of Friday's service date. This allows transit agencies to represent their operational day, which may not align with calendar days.",[132,177,179],{"id":178},"frequency-based-service","Frequency-Based Service",[10,181,182,183,189],{},"Some routes operate on headway-based schedules rather than fixed times. This is defined in ",[14,184,186],{"href":185,"target":45},"https:\u002F\u002Fgtfs.org\u002Fdocumentation\u002Fschedule\u002Freference\u002F#frequenciestxt",[47,187,188],{},"frequencies.txt",", indicating that vehicles depart at regular intervals (e.g., every 10 minutes) rather than specific scheduled times.",[35,191,193],{"id":192},"real-time-updates","Real-Time Updates",[10,195,196,197,201,202,206],{},"Transitland enriches static trip schedules with real-time data from ",[14,198,200],{"href":199},"\u002Fdocumentation\u002Fconcepts\u002Fsource-feeds#gtfs-realtime-feed-fetching-and-caching","GTFS Realtime feeds",". See the ",[14,203,205],{"href":204},"\u002Fdocumentation\u002Fconcepts\u002Falerts","Alerts"," concept page for information about how real-time trip updates, vehicle positions, and service alerts are made available through the API.",[35,208,210],{"id":209},"querying-schedule-data-via-transitland","Querying Schedule Data via Transitland",[10,212,213],{},"For detailed information about querying schedule data through the Transitland APIs, see:",[55,215,216,223,230],{},[58,217,218,222],{},[14,219,221],{"href":220},"\u002Fdocumentation\u002Frest-api\u002Ftrips","REST API trips endpoint"," - Query trips by route, service date, or with real-time data",[58,224,225,229],{},[14,226,228],{"href":227},"\u002Fdocumentation\u002Frest-api\u002Fdepartures","REST API departures endpoint"," - View trips serving a specific stop at particular times",[58,231,232,236],{},[14,233,235],{"href":234},"\u002Fdocumentation\u002Frouting-platform\u002Ftransit-otp","Transit routing"," - Plan journeys from an origin to a destination using trip schedules",{"title":238,"searchDepth":239,"depth":239,"links":240},"",2,[241,242,247,248],{"id":37,"depth":239,"text":38},{"id":90,"depth":239,"text":91,"children":243},[244,246],{"id":134,"depth":245,"text":135},3,{"id":178,"depth":245,"text":179},{"id":192,"depth":239,"text":193},{"id":209,"depth":239,"text":210},"GTFS trips, stop times, service calendars, and frequency-based service in Transitland, including headsigns, interpolated times, and GTFS service dates.","md",{"layout":252},"documentation",true,"\u002Fdocs\u002Fconcepts\u002Ftrips-schedules",{"title":5,"description":249},"docs\u002Fconcepts\u002Ftrips-schedules","t1X2mquNMPSdCBQdZzFAYDdRth2C597SRR_Dsw_ahKA",{},{},{},{},1791115795453]