[{"data":1,"prerenderedAt":671},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fdatasets\u002Fdata-dictionary":3,"_apollo:default":667,"_apollo:stationEditor":668,"_apollo:feedManagement":669,"_apollo:transferAnalyst":670},{"id":4,"title":5,"body":6,"description":659,"extension":660,"meta":661,"navigation":662,"path":663,"seo":664,"stem":665,"__hash__":666},"content\u002Fdocs\u002Fdatasets\u002Fdata-dictionary.md","Transitland Datasets: File Formats and Data Dictionary",{"type":7,"value":8,"toc":647},"minimark",[9,14,18,47,57,61,64,81,84,89,98,126,131,188,192,211,215,218,223,237,242,286,291,317,320,328,331,393,397,405,435,439,481,485,523,527,530,576,580,583,603,606,609,612],[10,11,13],"h2",{"id":12},"data-files-and-formats","Data Files and Formats",[15,16,17],"p",{},"Each Dataset package includes data in the following standardized formats:",[19,20,21,29,35,41],"ul",{},[22,23,24,28],"li",{},[25,26,27],"code",{},"stops.csv"," - Tabular data ready to view as a spreadsheet, or import into GIS using latitude and longitude columns",[22,30,31,34],{},[25,32,33],{},"stops.geojsonl"," - Geospatial vector data ready to load into GIS or data-science tools",[22,36,37,40],{},[25,38,39],{},"routes.csv"," - Tabular data ready to view as a spreadsheet (no geometries)",[22,42,43,46],{},[25,44,45],{},"routes.geojsonl"," - Geospatial vector data including each route's shape",[48,49,50,51,56],"info",{},"\n  The GeoJSON Lines (GeoJSONL) format has a single feature on each line, separated by a line break. Unlike standard GeoJSON, which must be fully loaded into memory, GeoJSONL can be parsed in a streaming manner. Many GIS and data-science tools can work with GeoJSONL, since it's just a variant of newline-deliminted JSON. For more information, see ",[52,53,55],"a",{"href":54},"https:\u002F\u002Fwww.interline.io\u002Fblog\u002Ftag\u002Fgeojsonl\u002F","Interline's blog posts about GeoJSONL",".\n",[10,58,60],{"id":59},"data-dictionary","Data Dictionary",[15,62,63],{},"Each Dataset zip file includes:",[19,65,66,69,78],{},[22,67,68],{},"Full data dictionary in human-readable Markdown format",[22,70,71,77],{},[52,72,76],{"href":73,"rel":74},"https:\u002F\u002Fdatapackage.org\u002Fstandard\u002Fdata-package\u002F",[75],"nofollow","Frictionless DataPackage v2"," as machine-readable JSON",[22,79,80],{},"Complete field descriptions and examples",[15,82,83],{},"The latest data dictionary is also printed below for reference.",[85,86,88],"h3",{"id":87},"route-oriented-dataset-schema","Route-Oriented Dataset Schema",[15,90,91,92,94,95,97],{},"The ",[25,93,39],{}," file includes four main sets of columns and the ",[25,96,45],{}," file includes four main sets of matching properties:",[99,100,101,108,114,120],"ol",{},[22,102,103,107],{},[104,105,106],"strong",{},"Route record and metadata"," - Basic route information",[22,109,110,113],{},[104,111,112],{},"Agency record and metadata"," - Agency serving the route",[22,115,116,119],{},[104,117,118],{},"Route headway data"," - Quantitative summary of route frequency",[22,121,122,125],{},[104,123,124],{},"Feed metadata"," - Source feed information",[127,128,130],"h4",{"id":129},"route-record-and-metadata","Route Record and Metadata",[19,132,133,142,148,154,160,171,182],{},[22,134,135,138,139],{},[25,136,137],{},"route_onestop_id"," - Transitland's unique identifier for the route. Can be used to construct a link to ",[25,140,141],{},"https:\u002F\u002Fwww.transit.land\u002Froutes\u002F\u003Croute_onestop_id>",[22,143,144,147],{},[25,145,146],{},"route_short_name"," - Rider-facing short name for the route",[22,149,150,153],{},[25,151,152],{},"route_long_name"," - Rider-facing longer, descriptive name",[22,155,156,159],{},[25,157,158],{},"route_desc"," - Rider-facing description",[22,161,162,165,166,170],{},[25,163,164],{},"route_type"," - Vehicle type enum (see ",[52,167,169],{"href":168},"#route-types","Route Types"," below)",[22,172,173,176,177,181],{},[25,174,175],{},"route_id"," - GTFS ID used within the source feed. This will ",[178,179,180],"em",{},"not"," be unique across other feeds.",[22,183,184,187],{},[25,185,186],{},"route_color"," - Hex RGB value for map representation",[127,189,191],{"id":190},"agency-information","Agency Information",[19,193,194,205],{},[22,195,196,199,200,204],{},[25,197,198],{},"agency_id"," - GTFS ID from source feed for the agency; may not be unique across different feeds (see ",[52,201,203],{"href":202},"\u002Fdocumentation\u002Fconcepts\u002Fagencies-and-operators","Agencies and Operators",")",[22,206,207,210],{},[25,208,209],{},"agency_name"," - Rider-facing agency name",[127,212,214],{"id":213},"route-headway-data","Route Headway Data",[15,216,217],{},"Headway data is calculated for each route direction and day-of-week category (Monday-Friday, Saturday, Sunday). Headways represent the median number of seconds between departing trips within specific time windows.",[15,219,220],{},[104,221,222],{},"Time windows:",[19,224,225,228,231,234],{},[22,226,227],{},"7am-9am (peak morning)",[22,229,230],{},"9am-4pm (midday)",[22,232,233],{},"4pm-6pm (peak evening)",[22,235,236],{},"6pm-7am (overnight)",[15,238,239],{},[104,240,241],{},"Columns include:",[19,243,244,250,256,262,268,274,280],{},[22,245,246,249],{},[25,247,248],{},"\u003Cprefix>_selected_service_date"," - Transitland's algorithm selected this as a representative service date. The following data is all calculated from this service day's schedules.",[22,251,252,255],{},[25,253,254],{},"\u003Cprefix>_departure_times"," - Space-separated list of departure times",[22,257,258,261],{},[25,259,260],{},"\u003Cprefix>_headway_\u003Ctime>_mean"," - Average headway in seconds",[22,263,264,267],{},[25,265,266],{},"\u003Cprefix>_headway_\u003Ctime>_median"," - Median headway in seconds",[22,269,270,273],{},[25,271,272],{},"\u003Cprefix>_selected_stop_id"," - GTFS ID from source feed of the stop used to calculate headways",[22,275,276,279],{},[25,277,278],{},"\u003Cprefix>_selected_stop_intid"," - Internal stop ID within Transitland data; ensured to be globally unique.",[22,281,282,285],{},[25,283,284],{},"\u003Cprefix>_selected_stop_name"," - Rider-facing stop name",[15,287,288],{},[104,289,290],{},"Prefixes:",[19,292,293,299,305,311],{},[22,294,295,298],{},[25,296,297],{},"hw_best"," - Most departures",[22,300,301,304],{},[25,302,303],{},"hw_dow1_dir0\u002F1"," - Monday-Friday, direction 0\u002F1",[22,306,307,310],{},[25,308,309],{},"hw_dow6_dir0\u002F1"," - Saturday, direction 0\u002F1",[22,312,313,316],{},[25,314,315],{},"hw_dow7_dir0\u002F1"," - Sunday, direction 0\u002F1",[85,318,169],{"id":319},"route-types",[15,321,322,323,327],{},"Defined by the GTFS specification and extended by Transitland. For the complete list of route types including extended codes (100-1700+), see ",[52,324,326],{"href":325},"\u002Fdocumentation\u002Fconcepts\u002Froutes","Routes",".",[15,329,330],{},"Standard GTFS route types:",[19,332,333,339,345,351,357,363,369,375,381,387],{},[22,334,335,338],{},[25,336,337],{},"0",": Tram, Streetcar, Light rail",[22,340,341,344],{},[25,342,343],{},"1",": Subway, Metro",[22,346,347,350],{},[25,348,349],{},"2",": Rail",[22,352,353,356],{},[25,354,355],{},"3",": Bus",[22,358,359,362],{},[25,360,361],{},"4",": Ferry",[22,364,365,368],{},[25,366,367],{},"5",": Cable tram",[22,370,371,374],{},[25,372,373],{},"6",": Aerial lift",[22,376,377,380],{},[25,378,379],{},"7",": Funicular",[22,382,383,386],{},[25,384,385],{},"11",": Trolleybus",[22,388,389,392],{},[25,390,391],{},"12",": Monorail",[85,394,396],{"id":395},"stop-oriented-dataset-schema","Stop-Oriented Dataset Schema",[15,398,91,399,401,402,404],{},[25,400,27],{}," file includes five main sets of columns and the ",[25,403,33],{}," file includes five sets of properties on each feature:",[99,406,407,413,419,425,431],{},[22,408,409,412],{},[104,410,411],{},"Stop record and metadata"," - Basic stop information",[22,414,415,418],{},[104,416,417],{},"Administrative boundaries"," - Geographic and political boundaries",[22,420,421,424],{},[104,422,423],{},"Route records and metadata"," - Up to 5 routes serving the stop",[22,426,427,430],{},[104,428,429],{},"Transit service summary"," - Frequency of arrivals\u002Fdepartures",[22,432,433,125],{},[104,434,124],{},[127,436,438],{"id":437},"stop-record-and-metadata","Stop Record and Metadata",[19,440,441,451,457,463,469,475],{},[22,442,443,446,447,204],{},[25,444,445],{},"stop_onestop_id"," - Transitland's unique identifier for the stop location (see ",[52,448,450],{"href":449},"\u002Fdocumentation\u002Fconcepts\u002Fstops","Stops",[22,452,453,456],{},[25,454,455],{},"stop_id"," - GTFS ID from source feed for the stop (may not be unique across different feeds)",[22,458,459,462],{},[25,460,461],{},"stop_name"," - Name provided by transit operator",[22,464,465,468],{},[25,466,467],{},"stop_desc"," - Optional description",[22,470,471,474],{},[25,472,473],{},"stop_lon"," - Longitude coordinate",[22,476,477,480],{},[25,478,479],{},"stop_lat"," - Latitude coordinate",[127,482,484],{"id":483},"administrative-boundaries","Administrative Boundaries",[19,486,487,493,505,511],{},[22,488,489,492],{},[25,490,491],{},"adm0_name"," - Country name (e.g., \"United States of America\")",[22,494,495,498,499,504],{},[25,496,497],{},"adm0_iso"," - Country ISO code following ",[52,500,503],{"href":501,"rel":502},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FList_of_ISO_3166_country_codes",[75],"ISO 3166-1"," standard (e.g., \"US\")",[22,506,507,510],{},[25,508,509],{},"adm1_name"," - State\u002Fprovince name (e.g., \"Oregon\")",[22,512,513,516,517,522],{},[25,514,515],{},"adm1_iso"," - State\u002Fprovince ISO code following ",[52,518,521],{"href":519,"rel":520},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FISO_3166-2",[75],"ISO 3166-2"," standard (e.g., \"US-OR\")",[127,524,526],{"id":525},"route-records-and-metadata","Route Records and Metadata",[15,528,529],{},"Each stop can be served by up to 5 different routes. For each route (1-5), the following information is provided:",[19,531,532,538,544,550,556,562,571],{},[22,533,534,537],{},[25,535,536],{},"agency_id_N"," - ID of the transit operator",[22,539,540,543],{},[25,541,542],{},"agency_name_N"," - Name of the transit operator",[22,545,546,549],{},[25,547,548],{},"route_id_N"," - ID of the route",[22,551,552,555],{},[25,553,554],{},"route_short_name_N"," - Short name of the route",[22,557,558,561],{},[25,559,560],{},"route_long_name_N"," - Long name of the route",[22,563,564,567,568],{},[25,565,566],{},"route_type_N"," - Vehicle type of the route. See ",[52,569,570],{"href":168},"route types",[22,572,573,187],{},[25,574,575],{},"route_color_N",[127,577,579],{"id":578},"transit-service-summary","Transit Service Summary",[15,581,582],{},"Service frequency is calculated based on scheduled departures for a designated \"target week\" near the dataset delivery date. Includes:",[19,584,585,591,597],{},[22,586,587,590],{},[25,588,589],{},"departure_count_dowN"," - Total trips departing on day N (both directions)",[22,592,593,596],{},[25,594,595],{},"departure_count_dowN_dir0"," - Trips departing on day N (inbound)",[22,598,599,602],{},[25,600,601],{},"departure_count_dowN_dir1"," - Trips departing on day N (outbound)",[15,604,605],{},"Where N ranges from 1 (Monday) to 7 (Sunday).",[85,607,124],{"id":608},"feed-metadata",[15,610,611],{},"Each stop or route record includes the following columns\u002Fproperties providing information on the source lineage.",[19,613,614,628,641],{},[22,615,616,619,620,624,625],{},[25,617,618],{},"feed_id"," - Transitland's Onestop ID for source feed (see ",[52,621,623],{"href":622},"\u002Fdocumentation\u002Fconcepts\u002Fsource-feeds","Source Feeds","). Can be used to construct links to ",[25,626,627],{},"https:\u002F\u002Fwww.transit.land\u002Ffeeds\u002F\u003Cfeed_id>",[22,629,630,633,634,624,638],{},[25,631,632],{},"feed_version_sha1"," - Feed version identifier (see ",[52,635,637],{"href":636},"\u002Fdocumentation\u002Fconcepts\u002Fstatic-gtfs-feed-versions","Static GTFS Feed Versions",[25,639,640],{},"https:\u002F\u002Fwww.transit.land\u002Ffeed-versions\u002F\u003Cfeed_version_sha1>",[22,642,643,646],{},[25,644,645],{},"feed_version_fetched_at"," - Timestamp for when Transitland fetched the feed version from which this stop or route came. Can be used to evaluate data freshness.",{"title":648,"searchDepth":649,"depth":649,"links":650},"",2,[651,652],{"id":12,"depth":649,"text":13},{"id":59,"depth":649,"text":60,"children":653},[654,656,657,658],{"id":87,"depth":655,"text":88},3,{"id":319,"depth":655,"text":169},{"id":395,"depth":655,"text":396},{"id":608,"depth":655,"text":124},"Transitland Datasets file formats and field definitions for stops and routes CSV and GeoJSONL files, including headway columns, route types, and feed metadata.","md",{},true,"\u002Fdocs\u002Fdatasets\u002Fdata-dictionary",{"title":5,"description":659},"docs\u002Fdatasets\u002Fdata-dictionary","vrQ-4wkouf-JCpi4TVlzLQN1ShV9N2zKYcyK9Y1EWiE",{},{},{},{},1791115795560]