[{"data":1,"prerenderedAt":313},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fconcepts\u002Fjourneys-and-itineraries":3,"_apollo:default":312,"_apollo:stationEditor":312,"_apollo:feedManagement":312,"_apollo:transferAnalyst":312},{"id":4,"title":5,"body":6,"description":303,"extension":304,"meta":305,"navigation":306,"path":307,"seo":308,"stem":309,"__hash__":310,"lastUpdated":311},"content\u002Fdocs\u002Fconcepts\u002Fjourneys-and-itineraries.md","Journeys and itineraries",{"type":7,"value":8,"toc":295},"minimark",[9,38,43,51,58,64,115,121,125,128,148,155,168,172,175,259,270,274],[10,11,12,13,18,19,18,23,27,28,32,33,37],"p",{},"Other concept pages describe data Transitland stores: ",[14,15,17],"a",{"href":16},"\u002Fdocumentation\u002Fconcepts\u002Fstops","stops",", ",[14,20,22],{"href":21},"\u002Fdocumentation\u002Fconcepts\u002Froutes","routes",[14,24,26],{"href":25},"\u002Fdocumentation\u002Fconcepts\u002Ftrips-schedules","trips and schedules",". This page describes the results of ",[14,29,31],{"href":30},"\u002Fdocumentation\u002Frouting-platform\u002Ftransit-otp","transit routing"," on the ",[14,34,36],{"href":35},"\u002Fdocumentation\u002Frouting-platform","Interline Routing Platform",".",[39,40,42],"h2",{"id":41},"journey-itinerary-leg","Journey, itinerary, leg",[10,44,45,46,50],{},"A ",[47,48,49],"strong",{},"journey"," is a request to travel from an origin to a destination, departing at or arriving by a given time.",[10,52,53,54,57],{},"An ",[47,55,56],{},"itinerary"," is one result for a journey. A journey usually returns several itineraries, which differ in departure time, walking distance, and number of transfers.",[10,59,45,60,63],{},[47,61,62],{},"leg"," is one continuous movement within an itinerary, by one mode. There are two kinds:",[65,66,67,109],"ul",{},[68,69,45,70,73,74,77,78,82,83,85,86,90,91,95,96,99,100,95,104,108],"li",{},[47,71,72],{},"transit leg"," is a ride on one trip, from a boarding stop to an alighting stop. It includes the ",[14,75,76],{"href":21},"route"," and its ",[14,79,81],{"href":80},"\u002Fdocumentation\u002Fconcepts\u002Fagencies-and-operators","agency",", the trip and its headsign, the boarding and alighting ",[14,84,17],{"href":16},", and the ",[14,87,89],{"href":88},"\u002Fdocumentation\u002Fconcepts\u002Fstatic-gtfs-feed-versions","feed version"," the schedule came from. Use a leg's ",[92,93,94],"code",{},"routeOnestopId"," or ",[92,97,98],{},"stopOnestopId"," to query the ",[14,101,103],{"href":102},"\u002Fdocumentation\u002Frest-api","REST",[14,105,107],{"href":106},"\u002Fdocumentation\u002Fgraphql-api","GraphQL"," APIs for that route or stop.",[68,110,45,111,114],{},[47,112,113],{},"walking leg"," connects the origin to the first stop, two stops at a transfer, or the last stop to the destination. It includes a geometry and its endpoints, and no route or trip.",[10,116,45,117,120],{},[47,118,119],{},"transfer"," is the change between two transit legs, usually a walking leg plus the wait for the next departure. Transfers are counted on the itinerary and are not separate legs.",[39,122,124],{"id":123},"timings","Timings",[10,126,127],{},"An itinerary reports a start time, end time, and total duration. The duration is split into:",[65,129,130,136,142],{},[68,131,132,135],{},[47,133,134],{},"Walk time",": time on foot.",[68,137,138,141],{},[47,139,140],{},"Transit time",": time aboard a vehicle.",[68,143,144,147],{},[47,145,146],{},"Waiting time",": time at a stop waiting for a departure.",[10,149,150,151,154],{},"The itinerary also reports its number of ",[47,152,153],{},"transfers",". Each leg has its own start and end time.",[10,156,157,158,162,163,167],{},"Within the ",[14,159,161],{"href":160},"\u002Fdocumentation\u002Frouting-platform\u002Ftransit-otp#coverage","real-time coverage"," of transit routing, leg times follow the predicted departures from ",[14,164,166],{"href":165},"\u002Fdocumentation\u002Fconcepts\u002Fsource-feeds#gtfs-realtime-feed-fetching-and-caching","GTFS Realtime"," trip updates, and each transit leg reports its delay against the schedule.",[39,169,171],{"id":170},"tracing-a-leg-to-its-source-data","Tracing a leg to its source data",[10,173,174],{},"Each transit leg includes identifiers that resolve through other Transitland APIs:",[176,177,178,191],"table",{},[179,180,181],"thead",{},[182,183,184,188],"tr",{},[185,186,187],"th",{},"Field on a transit leg",[185,189,190],{},"Resolves to",[192,193,194,213,233,247],"tbody",{},[182,195,196,201],{},[197,198,199],"td",{},[92,200,94],{},[197,202,203,204,206,207,95,210,212],{},"The ",[14,205,76],{"href":21},", through the ",[14,208,103],{"href":209},"\u002Fdocumentation\u002Frest-api\u002Froutes",[14,211,107],{"href":106}," APIs",[182,214,215,227],{},[197,216,217,219,220,223,224],{},[92,218,98],{},", on the leg's ",[92,221,222],{},"from"," and ",[92,225,226],{},"to",[197,228,203,229,232],{},[14,230,231],{"href":16},"stop",", the same way",[182,234,235,240],{},[197,236,237],{},[92,238,239],{},"feedId",[197,241,203,242,246],{},[14,243,245],{"href":244},"\u002Fdocumentation\u002Fconcepts\u002Fsource-feeds","source feed"," in the Transitland Atlas",[182,248,249,254],{},[197,250,251],{},[92,252,253],{},"feedVersionSha1",[197,255,203,256,258],{},[14,257,89],{"href":88}," the schedule came from",[10,260,261,262,264,265,269],{},"To get the GTFS a leg was planned from, pass its ",[92,263,253],{}," to the ",[14,266,268],{"href":267},"\u002Fdocumentation\u002Frest-api\u002Ffeed_versions","feed versions endpoint",". It returns when the feed version was fetched, the date range it covers, and a download of the file.",[39,271,273],{"id":272},"see-also","See also",[65,275,276,282,289],{},[68,277,278,281],{},[14,279,280],{"href":30},"Transit routing endpoint",": request and response reference.",[68,283,284,288],{},[14,285,287],{"href":286},"\u002Fdocumentation\u002Fconcepts\u002Frouting-graph-and-costing","Routing graph and costing models",": how the routing graphs are built.",[68,290,291,294],{},[14,292,293],{"href":25},"Trips and schedules",": the scheduled service itineraries are built from.",{"title":296,"searchDepth":297,"depth":297,"links":298},"",2,[299,300,301,302],{"id":41,"depth":297,"text":42},{"id":123,"depth":297,"text":124},{"id":170,"depth":297,"text":171},{"id":272,"depth":297,"text":273},"Journeys, itineraries, transit and walking legs, transfers, and timings in Transitland transit routing results, and how to trace each leg to its source GTFS.","md",{},true,"\u002Fdocs\u002Fconcepts\u002Fjourneys-and-itineraries",{"title":5,"description":303},"docs\u002Fconcepts\u002Fjourneys-and-itineraries","zkjXrn4U0ijga1AUCdsIjx8pJ-9C4TSLuBiN7MC6XFo","2026-10-16T15:48:26-07:00","{}",1793614314805]