[{"data":1,"prerenderedAt":243},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fconcepts\u002Fstops":3,"_apollo:default":239,"_apollo:stationEditor":240,"_apollo:feedManagement":241,"_apollo:transferAnalyst":242},{"id":4,"title":5,"body":6,"description":230,"extension":231,"meta":232,"navigation":234,"path":235,"seo":236,"stem":237,"__hash__":238},"content\u002Fdocs\u002Fconcepts\u002Fstops.md","Stops",{"type":7,"value":8,"toc":222},"minimark",[9,18,23,37,83,86,90,97,131,134,138,151,155,158,214],[10,11,12,13,17],"p",{},"Stops are ",[14,15,16],"code",{},"stops.txt"," entities imported from GTFS, and include the same basic structure and fields, plus some additional metadata.",[19,20,22],"h2",{"id":21},"stop-location-types","Stop Location Types",[10,24,25,26,32,33,36],{},"According to the ",[27,28,31],"a",{"href":29,"target":30},"https:\u002F\u002Fgtfs.org\u002Fdocumentation\u002Fschedule\u002Freference\u002F#stopstxt","_blank","GTFS specification",", stops can have different ",[14,34,35],{},"location_type"," values that indicate their purpose:",[38,39,40,51,59,67,75],"ul",{},[41,42,43,50],"li",{},[44,45,46,49],"strong",{},[14,47,48],{},"0"," (or empty)",": Stop or platform where passengers board or alight from a transit vehicle. This is the most common type.",[41,52,53,58],{},[44,54,55],{},[14,56,57],{},"1",": Station - a physical structure or area containing one or more platforms.",[41,60,61,66],{},[44,62,63],{},[14,64,65],{},"2",": Entrance\u002Fexit - a location where passengers can enter or exit a station from the street.",[41,68,69,74],{},[44,70,71],{},[14,72,73],{},"3",": Generic node - a location within a station used to link together pathways.",[41,76,77,82],{},[44,78,79],{},[14,80,81],{},"4",": Boarding area - a specific location on a platform where passengers can board or alight vehicles.",[10,84,85],{},"Location types 3 and 4 are only used in the context of the GTFS-Pathways extension.",[19,87,89],{"id":88},"stop-hierarchies","Stop Hierarchies",[10,91,92,93,96],{},"Stops can form hierarchical relationships using the ",[14,94,95],{},"parent_station"," field:",[38,98,99,110,125],{},[41,100,101,102,105,106,109],{},"Stops with ",[14,103,104],{},"location_type=0"," (stops\u002Fplatforms) may belong to a parent station (",[14,107,108],{},"location_type=1",")",[41,111,112,113,116,117,120,121,124],{},"Entrances (",[14,114,115],{},"location_type=2","), generic nodes (",[14,118,119],{},"location_type=3","), and boarding areas (",[14,122,123],{},"location_type=4",") must have a parent station",[41,126,127,128,130],{},"Stations (",[14,129,108],{},") cannot have a parent station",[10,132,133],{},"This hierarchy is particularly important for complex transit facilities like major train stations or airports, where pathways connect multiple platforms, entrances, and boarding areas.",[19,135,137],{"id":136},"stop-onestop-ids","Stop Onestop IDs",[10,139,140,141,145,146,150],{},"As with ",[27,142,144],{"href":143},"\u002Fdocumentation\u002Fconcepts\u002Froutes","routes",", the ",[27,147,149],{"href":148},"\u002Fdocumentation\u002Fconcepts\u002Fonestop-id-scheme","Onestop ID"," values for stops are automatically generated. Two very similar stops may both generate the same Onestop ID, in which case a query for that Onestop ID will return two or more stop entries.",[19,152,154],{"id":153},"relationships-and-metadata","Relationships and metadata",[10,156,157],{},"When querying stops through the Transitland API, stops include additional context beyond the standard GTFS fields:",[38,159,160,177,186,205],{},[41,161,162,172,173,176],{},[44,163,164,167,168],{},[27,165,166],{"href":143},"Routes"," and ",[27,169,171],{"href":170},"\u002Fdocumentation\u002Fconcepts\u002Fagencies-and-operators","agencies",": The ",[14,174,175],{},"route_stops"," field shows which routes serve each stop, including the operating agency",[41,178,179,185],{},[44,180,181],{},[27,182,184],{"href":183},"\u002Fdocumentation\u002Fconcepts\u002Fstatic-gtfs-feed-versions","Feed version",": Metadata about the source GTFS feed and when it was fetched",[41,187,188,172,194,197,198,201,202,109],{},[44,189,190],{},[27,191,193],{"href":192},"\u002Fdocumentation\u002Fconcepts\u002Fplaces","Administrative boundaries",[14,195,196],{},"place"," object provides geographic context with country and state\u002Fprovince information (e.g., ",[14,199,200],{},"adm0_iso: \"US\"",", ",[14,203,204],{},"adm1_iso: \"US-CA\"",[41,206,207,172,210,213],{},[44,208,209],{},"Levels",[14,211,212],{},"level"," field references vertical position information for multi-level stations (platforms, mezzanines, etc.)",[10,215,216,217,221],{},"For detailed information about querying stops, see the ",[27,218,220],{"href":219},"\u002Fdocumentation\u002Frest-api\u002Fstops","REST API stops endpoint",".",{"title":223,"searchDepth":224,"depth":224,"links":225},"",2,[226,227,228,229],{"id":21,"depth":224,"text":22},{"id":88,"depth":224,"text":89},{"id":136,"depth":224,"text":137},{"id":153,"depth":224,"text":154},"Transitland stops are GTFS stops.txt records with location types, parent station hierarchies, generated Onestop IDs, and route, place, and level metadata.","md",{"layout":233},"documentation",true,"\u002Fdocs\u002Fconcepts\u002Fstops",{"title":5,"description":230},"docs\u002Fconcepts\u002Fstops","71XZ3Iy5a3P1ZpoNnBRpoZmLuEeQ0L49-EdM5pk9vSc",{},{},{},{},1791248217328]