[{"data":1,"prerenderedAt":302},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fconcepts\u002Fjourneys-and-itineraries":3,"_apollo:default":298,"_apollo:stationEditor":299,"_apollo:feedManagement":300,"_apollo:transferAnalyst":301},{"id":4,"title":5,"body":6,"description":290,"extension":291,"meta":292,"navigation":293,"path":294,"seo":295,"stem":296,"__hash__":297},"content\u002Fdocs\u002Fconcepts\u002Fjourneys-and-itineraries.md","Journeys and Itineraries",{"type":7,"value":8,"toc":282},"minimark",[9,38,43,51,58,64,115,121,125,128,148,155,159,162,246,257,261],[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\u002F","transit routing"," on the ",[14,34,36],{"href":35},"\u002Fdocumentation\u002Frouting-platform\u002F","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\u002F","REST",[14,105,107],{"href":106},"\u002Fdocumentation\u002Fgraphql-api\u002F","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.",[39,156,158],{"id":157},"tracing-a-leg-to-its-source-data","Tracing a leg to its source data",[10,160,161],{},"Each transit leg includes identifiers that resolve through other Transitland APIs:",[163,164,165,178],"table",{},[166,167,168],"thead",{},[169,170,171,175],"tr",{},[172,173,174],"th",{},"Field on a transit leg",[172,176,177],{},"Resolves to",[179,180,181,200,220,234],"tbody",{},[169,182,183,188],{},[184,185,186],"td",{},[92,187,94],{},[184,189,190,191,193,194,95,197,199],{},"The ",[14,192,76],{"href":21},", through the ",[14,195,103],{"href":196},"\u002Fdocumentation\u002Frest-api\u002Froutes",[14,198,107],{"href":106}," APIs",[169,201,202,214],{},[184,203,204,206,207,210,211],{},[92,205,98],{},", on the leg's ",[92,208,209],{},"from"," and ",[92,212,213],{},"to",[184,215,190,216,219],{},[14,217,218],{"href":16},"stop",", the same way",[169,221,222,227],{},[184,223,224],{},[92,225,226],{},"feedId",[184,228,190,229,233],{},[14,230,232],{"href":231},"\u002Fdocumentation\u002Fconcepts\u002Fsource-feeds","source feed"," in the Transitland Atlas",[169,235,236,241],{},[184,237,238],{},[92,239,240],{},"feedVersionSha1",[184,242,190,243,245],{},[14,244,89],{"href":88}," the schedule came from",[10,247,248,249,251,252,256],{},"To get the GTFS a leg was planned from, pass its ",[92,250,240],{}," to the ",[14,253,255],{"href":254},"\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,258,260],{"id":259},"see-also","See also",[65,262,263,269,276],{},[68,264,265,268],{},[14,266,267],{"href":30},"Transit routing endpoint",": request and response reference.",[68,270,271,275],{},[14,272,274],{"href":273},"\u002Fdocumentation\u002Fconcepts\u002Frouting-graph-and-costing","Routing graph and costing models",": how the routing graphs are built.",[68,277,278,281],{},[14,279,280],{"href":25},"Trips & Schedules",": the scheduled service itineraries are built from.",{"title":283,"searchDepth":284,"depth":284,"links":285},"",2,[286,287,288,289],{"id":41,"depth":284,"text":42},{"id":123,"depth":284,"text":124},{"id":157,"depth":284,"text":158},{"id":259,"depth":284,"text":260},"Other concept pages describe data Transitland stores: stops, routes, trips and schedules. This page describes the results of transit routing on the Interline Routing Platform.","md",{},true,"\u002Fdocs\u002Fconcepts\u002Fjourneys-and-itineraries",{"title":5,"description":290},"docs\u002Fconcepts\u002Fjourneys-and-itineraries","ndzKAFcxhzX5AeGPiMdihQsfCNLOKoWTRsq0rvyE1W0",{},{},{},{},1790811151525]