[{"data":1,"prerenderedAt":1769},["ShallowReactive",2],{"post:\u002Fblog\u002Fmtc-regional-gtfs-feed-additions":3,"blog:siblings":1515},{"id":4,"title":5,"authors":6,"body":8,"date":1497,"description":1498,"extension":1499,"ghostId":1500,"image":1501,"imageAlt":1502,"imageCaption":1502,"imageVideo":1502,"meta":1503,"navigation":1504,"path":1505,"readingTime":1506,"seo":1507,"stem":1508,"tags":1509,"toc":1512,"updated":1513,"__hash__":1514},"blog\u002Fblog\u002Fmtc-regional-gtfs-feed-additions.md","SF Bay Area's Regional GTFS Feed Expanded",[7],"drew",{"type":9,"value":10},"minimark",[11,30,47,60,63,94,98,101,104,115,122,127,130,133,206,209,213,216,220,228,231,390,397,411,417,465,474,478,481,484,503,506,510,513,536,543,580,583,594,602,606,609,877,880,887,891,894,925,928,945,949,959,985,988,1008,1104,1121,1261,1278,1298,1383,1411,1414,1418,1421,1424,1427,1453,1456,1460,1462,1478,1483,1487,1490,1494],[12,13,16],"il-callout",{"color":14,"emoji":15},"blue","💡",[17,18,19,23,24,29],"p",{},[20,21,22],"strong",{},"October 4, 2022",": MTC and Interline have released updated fares and transfer discounts for all Bay Area transit agencies using the adopted GTFS-Fares v2 \"base implementation.\" See ",[25,26,28],"a",{"href":27},"\u002Fblog\u002Fmtc-regional-gtfs-feed-fares-updates\u002F","this blog post for more information",".",[12,31,32],{"color":14,"emoji":15},[17,33,34,37,38,42,43,29],{},[20,35,36],{},"September 10, 2021",": MTC and Interline have now released the Regional GTFS ",[39,40,41],"em",{},"Realtime"," Feed, which provides up-to-the-minute service alerts, trip updates, and vehicle positions using the same ID scheme as the static Regional GTFS Feed. See ",[25,44,46],{"href":45},"\u002Fblog\u002Fmtc-regional-gtfs-realtime-feed\u002F","this blog post for an overview",[17,48,49,50,54,55,59],{},"Earlier this year, ",[25,51,53],{"href":52},"\u002Fblog\u002Fmtc-regional-gtfs-feed-release\u002F","Interline and the Metropolitan Transportation Commission released the Regional GTFS Feed for the San Francisco Bay Area",". The Regional GTFS Feed is produced on a daily basis and made available through ",[25,56,58],{"href":57},"https:\u002F\u002F511.org\u002Fopen-data","511 SF Bay’s Open Data Portal"," and its Open Transit Data API.",[17,61,62],{},"We’re pleased to now share a series of additions to the Regional GTFS Feed that we’ve released together over recent months:",[64,65,66,76,85],"ul",{},[67,68,69,75],"li",{},[25,70,72],{"href":71},"#historical-feeds",[20,73,74],{},"Historical Feeds"," which provide a retrospective look at an entire month of service",[67,77,78,84],{},[25,79,81],{"href":80},"#station-pathways-and-levels",[20,82,83],{},"Station Pathways and Levels"," to provide richer wayfinding for all types of riders",[67,86,87,93],{},[25,88,90],{"href":89},"#fares-and-transfer-discounts",[20,91,92],{},"Fares and Transfer Discounts"," [beta] to calculate the cost of transit journeys on and across the eight largest agencies",[95,96,74],"h2",{"id":97},"historical-feeds",[17,99,100],{},"Since we released the Regional GTFS Feed in January, much has changed across the Bay Area. Transit agencies and their dedicated staff have rapidly reduced and re-targeted transit service for those riders who perform essential work or depend upon transit for their necessary journeys.",[17,102,103],{},"Using the newly released Historical Feeds component of the Regional GTFS Feed, we can visualize how transit service has changed throughout the Bay Area from January to July of 2020:",[105,106,112],"il-video",{"img-height":107,"img-width":108,"poster":109,"src":110,"width":111},"1582","2000","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fheadway-animation.jpg","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fheadway-animation.mp4","wide",[17,113,114],{},"Buses, trains, and ferries throughout the San Francisco Bay Area color-coded by frequency: the reddest route lines are routes that operate at least every 10 minutes; medium hues of red are 10 - 20 minute headways; the lightest hue of red are routes with service less than once every 20 minutes. This animation is created by using the Historical Feeds for the months of January through July of 2020.",[17,116,117,118,29],{},"Historical Regional Feed products are fully valid GTFS feeds, but they differ somewhat in their contents from the daily Regional Feed products. Read on to understand the process used to produce the Historical Regional Feed products and their key differences, or skip to the end of this section to ",[25,119,121],{"href":120},"#download-historical-feed-products","download Historical Feed products",[123,124,126],"h3",{"id":125},"slicing-regional-feeds","Slicing regional feeds",[17,128,129],{},"Each day, the Regional Feed is produced from the versions of agency feeds on 511.org that provide the best view of service on that day. Each month, the Historical Regional Feed creation process takes these Regional Feeds and combines them together, taking one day of service from each feed, which we are calling a “slice.”",[17,131,132],{},"For example:",[134,135,136,152],"table",{},[137,138,139],"thead",{},[140,141,142,146,149],"tr",{},[143,144,145],"th",{},"Feed filename",[143,147,148],{},"Published",[143,150,151],{},"Contributes service slice for",[153,154,155,166,176,186,196],"tbody",{},[140,156,157,161,164],{},[158,159,160],"td",{},"mtc-regional-feed-2020-04-24.zip",[158,162,163],{},"2020-04-24",[158,165,163],{},[140,167,168,171,174],{},[158,169,170],{},"mtc-regional-feed-2020-04-23.zip",[158,172,173],{},"2020-04-23",[158,175,173],{},[140,177,178,181,184],{},[158,179,180],{},"mtc-regional-feed-2020-04-22.zip",[158,182,183],{},"2020-04-22",[158,185,183],{},[140,187,188,191,194],{},[158,189,190],{},"mtc-regional-feed-2020-04-21.zip",[158,192,193],{},"2020-04-21",[158,195,193],{},[140,197,198,201,204],{},[158,199,200],{},"mtc-regional-feed-2020-04-20.zip",[158,202,203],{},"2020-04-20",[158,205,203],{},[17,207,208],{},"If the Regional Feed for a given day is missing, the closest previous day provides service. For instance, if 2020-04-22 was missing, the 2020-04-21 feed slice would cover both 2020-04-21 and 2020-04-22.",[123,210,212],{"id":211},"global-entity-copying","Global entity copying",[17,214,215],{},"Agencies, stops, and routes are considered “global”, and are handled using a simple ID-based merge with the most recent version winning. For example, if BART has a route with ID “OR-S” that is called “Richmond - Warm Springs”, but then later renames it to “Richmond to Warm Springs”, then the latter version will be used.",[123,217,219],{"id":218},"trip-hashing-comparison-and-copying","Trip hashing, comparison, and copying",[17,221,222,223,227],{},"Trips are more complicated and handled separately. A simple combining of all the trips and stop_times in all of the input files can easily create a GTFS feed that is too large for practical use, especially given that programs like ",[25,224,226],{"href":225},"\u002Frouting-platform\u002F","OpenTripPlanner"," need to hold the entire schedule in memory. Therefore, duplicate copies of trips are detected using a hash based approach and only copied to the output once. This reduces the output size by approximately 90%.",[17,229,230],{},"For example, here are three hypothetical versions of Trip ID “BA:2210503” from three consecutive days of input regional feeds.",[134,232,233,263],{},[137,234,235],{},[140,236,237,239,242,245,248,251,254,257,260],{},[143,238,145],{},[143,240,241],{},"Trip ID",[143,243,244],{},"Route ID",[143,246,247],{},"Service ID",[143,249,250],{},"Headsign",[143,252,253],{},"1st stop",[143,255,256],{},"2nd stop",[143,258,259],{},"n stops",[143,261,262],{},"Hash",[153,264,265,311,348],{},[140,266,267,273,278,283,288,291,296,301,306],{},[158,268,269],{},[270,271,272],"code",{},"2020-04-24.zip",[158,274,275],{},[270,276,277],{},"BA:2210503",[158,279,280],{},[270,281,282],{},"BA:OR-S",[158,284,285],{},[270,286,287],{},"BA:Wkd_BASE-Weekday-07",[158,289,290],{},"Warm Springs\u002FSouth Fremont",[158,292,293],{},[270,294,295],{},"RICH 5:03",[158,297,298],{},[270,299,300],{},"DELN 5:07",[158,302,303],{},[270,304,305],{},"PLZA 5:10...",[158,307,308],{},[270,309,310],{},"8c4ecb",[140,312,313,318,322,326,330,332,336,340,344],{},[158,314,315],{},[270,316,317],{},"2020-04-23.zip",[158,319,320],{},[270,321,277],{},[158,323,324],{},[270,325,282],{},[158,327,328],{},[270,329,287],{},[158,331,290],{},[158,333,334],{},[270,335,295],{},[158,337,338],{},[270,339,300],{},[158,341,342],{},[270,343,305],{},[158,345,346],{},[270,347,310],{},[140,349,350,355,359,363,367,370,375,380,385],{},[158,351,352],{},[270,353,354],{},"2020-04-22.zip",[158,356,357],{},[270,358,277],{},[158,360,361],{},[270,362,282],{},[158,364,365],{},[270,366,287],{},[158,368,369],{},"Warm Springs to South Fremont",[158,371,372],{},[270,373,374],{},"RICH 5:04",[158,376,377],{},[270,378,379],{},"DELN 5:06",[158,381,382],{},[270,383,384],{},"PLZA 5:12...",[158,386,387],{},[270,388,389],{},"a4bf1a",[17,391,392,393,396],{},"For each of these, the hashing function takes into account all trip attributes, all the calendar attributes for that trip, and the full details of each entry in ",[270,394,395],{},"stop_times.txt",". Any change in any field will result in a different hash. This allows us to directly compare trips between versions of the input feed. Above, all details and schedule for 2020-04-23 and 2020-04-24 match exactly, so these trips two will be considered identical. The trip for 2020-04-22 has some minor differences in name and schedule, so will generate a different hash, and be considered a different trip.",[17,398,399,400,402,403,406,407,410],{},"As the historical feed merging program processes each input feed, it calculates the hash of each trip in the feed. If it has not seen a trip before, it copies it to the output and notes the hash for future use. If it has been seen before, it is not copied again. To prevent clashes, the original Trip IDs are appended with the trip hash (e.g. ",[270,401,277],{}," -> ",[270,404,405],{},"BA:2210503:8c4ecb","). The merging program then takes all trips in the input feed (both seen and unseen) and examines the calendars to see which are active for each day in this slice, and then creates ",[270,408,409],{},"calendar_dates.txt"," entries for each trip on each day where that trip is scheduled to run. The original service IDs are changed to be the same as the hash appended Trip ID, and the calendar is unrolled into a day-by-day format, but it works reliably. This hashing approach is resource efficient and allows us to create historical feeds of arbitrary duration while minimizing the output size.",[17,412,413,414,416],{},"Example output ",[270,415,409],{},":",[134,418,419,431],{},[137,420,421],{},[140,422,423,425,428],{},[143,424,247],{},[143,426,427],{},"Date",[143,429,430],{},"Exception Type",[153,432,433,444,454],{},[140,434,435,439,441],{},[158,436,437],{},[270,438,405],{},[158,440,163],{},[158,442,443],{},"1 (Added)",[140,445,446,450,452],{},[158,447,448],{},[270,449,405],{},[158,451,173],{},[158,453,443],{},[140,455,456,461,463],{},[158,457,458],{},[270,459,460],{},"BA:2210503:a4bf1a",[158,462,183],{},[158,464,443],{},[17,466,467,468,470,471,473],{},"In this way, the ",[270,469,310],{}," version of the trip is scheduled to run on the two days of input data where it was seen, and the ",[270,472,389],{}," version is scheduled to run on the other day.",[123,475,477],{"id":476},"differences-between-regional-and-historic-feeds","Differences between Regional and Historic feeds",[17,479,480],{},"Historic Regional Feeds are equivalent to the original daily Regional Feeds in the stops, routes, and scheduled services they contain. Using a Historic will produce the same output in a routing engine or another type of analysis.",[17,482,483],{},"Historic Feeds are different from Regional Feeds in their specific GTFS structure:",[64,485,486,494,500],{},[67,487,488,491,492],{},[270,489,490],{},"calendars.txt"," records are removed and rewritten in ",[270,493,409],{},[67,495,496,499],{},[270,497,498],{},"trips.txt"," records are hashed and compared (as described above)",[67,501,502],{},"IDs for global records are namespaced (as described above)",[17,504,505],{},"These differences should not affect routing engine or similar types of analysis. However, keep these differences in mind if you are trying to use historical feeds to understand changes in GTFS data and its practices over time at Bay Area agencies.",[123,507,509],{"id":508},"download-historical-feed-products","Download Historical Feed products",[17,511,512],{},"To use the Historical Feed products:",[514,515,516,522,533],"ol",{},[67,517,518],{},[25,519,521],{"href":520},"https:\u002F\u002F511.org\u002Fopen-data\u002Ftoken","Sign up for a 511 Open Data API token",[67,523,524,525,528,529,532],{},"Download from ",[270,526,527],{},"http:\u002F\u002Fapi.511.org\u002Ftransit\u002Fdatafeeds?api_key=[your_key]&operator_id=RG&historic=YYYY-MM"," (for example, to request May 2020: ",[270,530,531],{},"historic=2020-05",")",[67,534,535],{},"At the start of each month, the Historic Feed for the last month is created and posted. You may download as many months as you wish and combine them to analyze as many months\u002Fquarters\u002Fyears as you wish at once.",[17,537,538,539,542],{},"As of this blog post, the following months are available for download (that is, you can you any of these values for the ",[270,540,541],{},"historic"," query parameter):",[64,544,545,550,555,560,565,570,575],{},[67,546,547],{},[270,548,549],{},"2020-01",[67,551,552],{},[270,553,554],{},"2020-02",[67,556,557],{},[270,558,559],{},"2020-03",[67,561,562],{},[270,563,564],{},"2020-04",[67,566,567],{},[270,568,569],{},"2020-05",[67,571,572],{},[270,573,574],{},"2020-06",[67,576,577],{},[270,578,579],{},"2020-07",[95,581,83],{"id":582},"station-pathways-and-levels",[17,584,585,586,589,590,593],{},"The Regional Feed exists to both merge together individual agency GTFS feeds and to serve as a home for new GTFS data that describes cross-agency conditions. The daily Regional Feed now comes with layouts for 35 key transit stations across the Bay Area, each of which serves multiple agencies. Using the newly added ",[270,587,588],{},"pathways.txt"," and ",[270,591,592],{},"levels.txt"," files in GTFS, Interline and MTC are now able to provide more detailed information about how to transfer from one agency to another. This includes information on elevators, escalators, and routes that may not be accessible to those in wheelchairs. Pathways and levels information will equip trip planning apps to provide more helpful wayfinding information to their users, particular those who are new to the Bay Area or who have limited vision.",[105,595,599],{"img-height":596,"img-width":108,"poster":597,"src":598,"width":111},"948","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Funiversity-ave-pathways.jpg","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Funiversity-ave-pathways.mp4",[17,600,601],{},"Pathways and levels throughout the University Ave\u002FDowntown Palo Alto station served by Caltrain regional rail on two platforms and VTA and SamTrans buses at bus bays.",[123,603,605],{"id":604},"_35-regional-transit-hubs","35 Regional Transit Hubs",[17,607,608],{},"Here is a list of the 35 stations currently in the Regional Feed:",[134,610,611,621],{},[137,612,613],{},[140,614,615,618],{},[143,616,617],{},"Transit station\u002Fhub",[143,619,620],{},"County",[153,622,623,631,638,645,652,660,668,675,682,689,696,703,711,718,726,734,741,748,755,763,770,777,784,791,798,805,812,820,827,834,841,848,855,863,870],{},[140,624,625,628],{},[158,626,627],{},"Embarcadero BART",[158,629,630],{},"San Francisco",[140,632,633,636],{},[158,634,635],{},"Montgomery BART",[158,637,630],{},[140,639,640,643],{},[158,641,642],{},"Caltrain Station 4th & King",[158,644,630],{},[140,646,647,650],{},[158,648,649],{},"Salesforce Transit Center",[158,651,630],{},[140,653,654,657],{},[158,655,656],{},"12th St Oakland City Center BART",[158,658,659],{},"Alameda",[140,661,662,665],{},[158,663,664],{},"El Cerrito Del Norte BART",[158,666,667],{},"Contra Costa",[140,669,670,673],{},[158,671,672],{},"19TH St Oakland BART",[158,674,659],{},[140,676,677,680],{},[158,678,679],{},"Powell ST BART",[158,681,630],{},[140,683,684,687],{},[158,685,686],{},"Civic Center BART",[158,688,630],{},[140,690,691,694],{},[158,692,693],{},"Walnut Creek BART",[158,695,667],{},[140,697,698,701],{},[158,699,700],{},"Richmond BART\u002FAmtrak",[158,702,667],{},[140,704,705,708],{},[158,706,707],{},"San Jose Diridon Station",[158,709,710],{},"Santa Clara",[140,712,713,716],{},[158,714,715],{},"Palo Alto Station",[158,717,710],{},[140,719,720,723],{},[158,721,722],{},"San Rafael Transit Center",[158,724,725],{},"Marin",[140,727,728,731],{},[158,729,730],{},"Millbrae BART",[158,732,733],{},"San Mateo",[140,735,736,739],{},[158,737,738],{},"Pleasant Hill BART",[158,740,667],{},[140,742,743,746],{},[158,744,745],{},"San Francisco Ferry Terminal",[158,747,630],{},[140,749,750,753],{},[158,751,752],{},"Daly City BART",[158,754,630],{},[140,756,757,760],{},[158,758,759],{},"Santa Rosa Transit Mall",[158,761,762],{},"Sonoma",[140,764,765,768],{},[158,766,767],{},"Union City BART",[158,769,659],{},[140,771,772,775],{},[158,773,774],{},"MacArthur BART",[158,776,659],{},[140,778,779,782],{},[158,780,781],{},"Dublin\u002F Pleasanton BART",[158,783,659],{},[140,785,786,789],{},[158,787,788],{},"Warm Springs\u002F South Fremont BART",[158,790,659],{},[140,792,793,796],{},[158,794,795],{},"Santa Clara Caltrain",[158,797,710],{},[140,799,800,803],{},[158,801,802],{},"Oakland Coliseum BART",[158,804,659],{},[140,806,807,810],{},[158,808,809],{},"SFO",[158,811,630],{},[140,813,814,817],{},[158,815,816],{},"Fairfield Transportation Center",[158,818,819],{},"Solano",[140,821,822,825],{},[158,823,824],{},"OAK",[158,826,659],{},[140,828,829,832],{},[158,830,831],{},"Petaluma Transit Mall",[158,833,725],{},[140,835,836,839],{},[158,837,838],{},"Vallejo Ferry Terminal",[158,840,819],{},[140,842,843,846],{},[158,844,845],{},"Mountain View Station",[158,847,710],{},[140,849,850,853],{},[158,851,852],{},"Great America",[158,854,710],{},[140,856,857,860],{},[158,858,859],{},"Napa Intermodal",[158,861,862],{},"Napa",[140,864,865,868],{},[158,866,867],{},"SJC",[158,869,710],{},[140,871,872,875],{},[158,873,874],{},"Great Mall\u002FMilpitas BART",[158,876,710],{},[17,878,879],{},"Note that just as the ongoing pandemic has made our work on the Historic Feed all the more relevant, our work on Station Pathways and Levels has had to adapt to current circumstances. Our staff have been working from home using aerial imagery, architectural drawings, station maps, and other materials. Interline’s Station Editor tool also works on tablets, and we look forward to again going out into the field to all of these stations to correct and improve details.",[17,881,882,883,29],{},"We welcome questions and corrections sent to the ",[25,884,886],{"href":885},"https:\u002F\u002Fgroups.google.com\u002Fforum\u002F#!forum\u002F511sfbaydeveloperresources","511SFBayDeveloperResources mailing list",[123,888,890],{"id":889},"using-station-pathways-and-levels","Using Station Pathways and Levels",[17,892,893],{},"Download the daily Regional Feed like so:",[514,895,896,900,905,913],{},[67,897,898],{},[25,899,521],{"href":520},[67,901,524,902],{},[270,903,904],{},"http:\u002F\u002Fapi.511.org\u002Ftransit\u002Fdatafeeds?api_key=[your_key]&operator_id=RG",[67,906,907,908,589,910,912],{},"Look for the ",[270,909,588],{},[270,911,592],{}," files inside the zip archive.",[67,914,915,916,920,921,29],{},"For more information, see the ",[25,917,919],{"href":918},"https:\u002F\u002Fgtfs.org\u002Freference\u002Fstatic#pathwaystxt","static GTFS documentation"," and the ",[25,922,924],{"href":923},"https:\u002F\u002Fbit.ly\u002Fgtfs-pathways","GTFS-Pathways extension proposal document",[95,926,92],{"id":927},"fares-and-transfer-discounts",[17,929,930,931,935,936,940,941,29],{},"To date, the Regional GTFS Feed has focused on how to plan a journey by transit. Now we’re curating and adding additional data to help riders understand how to pay for their journeys. The Bay Area’s Regional GTFS Feed is now the first in the world to include data using the GTFS Fares-v2 specification. This ",[25,932,934],{"href":933},"https:\u002F\u002Fbit.ly\u002Fgtfs-fares","newly proposed specification"," allows us to model the many different fare products and discounts that are available to the Bay Area’s transit riders. For example, we can now account for how some agencies provide riders a discount when they pay by Clipper Card rather than by cash. (",[25,937,939],{"href":938},"https:\u002F\u002Fwww.clippercard.com\u002F","Clipper Card"," is the contact-less payment card and system operated by MTC and available on buses, trains, and ferries throughout the Bay Area.) We can also capture how riders can receive a discount when transferring from certain agencies to other agencies. Read on for a detailed example of how Fares-v2 work in practice, or skip ahead to ",[25,942,944],{"href":943},"\u002Fblog\u002Fmtc-regional-gtfs-feed-additions\u002F#using-fares-and-transfer-discounts","use the Fares-v2 beta data",[123,946,948],{"id":947},"an-example-of-fares-v2-in-practice","An Example of Fares-v2 in Practice",[950,951,956],"il-figure",{"alt":952,"img-height":953,"img-width":954,"src":955,"width":111},"map of a journey by BART and AC Transit originating in San Francisco, transferring in Oakland, and ending in Alameda","1042","1606","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fbart-to-ac-transit-route.png",[17,957,958],{},"A journey by BART and AC Transit, from San Francisco to Oakland to Alameda, which we will use in the following example of how to calculate the total cost. (Credit: BART Trip Planner)",[17,960,961,962,589,965,968,969,972,973,976,977,980,981,984],{},"Fares-v2 expands the traditional route- and zone-based GTFS fares model with several additional files, each focused on modeling a different part of a complex fare scheme. Imagine a rider making a transfer from BART to AC Transit; both BART and AC Transit have different prices for adult fares, eligible discount fares, and different prices when paying with cash or when using a Clipper Card; additionally, the discount applied when transferring from BART to AC Transit has different values and rules when using Clipper. Calculating the individual fares for each leg of this trip requires a description of any zones that apply to routes and stops (",[270,963,964],{},"fare_networks.txt",[270,966,967],{},"fare_areas.txt","), the costs and requirements of the base fare for each leg (",[270,970,971],{},"fare_leg_rules.txt","), any discount categories that might include the rider (",[270,974,975],{},"fare_profiles.txt","), and the type of payment used by the rider (",[270,978,979],{},"fare_containers.txt","). All of these factors are considered and then used to search for any transfer discounts that may apply for the trip (",[270,982,983],{},"fare_transfer_rules.txt",").",[17,986,987],{},"Let’s work through the hypothetical trip above, first taking BART from Embarcadero Station to 12th St. in Oakland, and then riding an AC Local bus, 51A, to Alameda.",[17,989,990,991,993,994,997,998,997,1001,589,1004,1007],{},"The following is an except from ",[270,992,971],{}," with some columns removed for brevity. This file contains sets of rules that are matched against a single leg of a trip, without regard to transfers. The columns ",[270,995,996],{},"from_area_id",", ",[270,999,1000],{},"to_area_id",[270,1002,1003],{},"fare_container_id",[270,1005,1006],{},"fare_category_id"," references values defined in the other files mentioned above.",[134,1009,1010,1034],{},[137,1011,1012],{},[140,1013,1014,1017,1020,1022,1024,1027,1029,1031],{},[143,1015,1016],{},"order",[143,1018,1019],{},"leg_group_id",[143,1021,996],{},[143,1023,1000],{},[143,1025,1026],{},"amount",[143,1028,1003],{},[143,1030,1006],{},[143,1032,1033],{},"notes",[153,1035,1036,1062,1083],{},[140,1037,1038,1041,1044,1047,1050,1053,1056,1059],{},[158,1039,1040],{},"90",[158,1042,1043],{},"BA:",[158,1045,1046],{},"EMBR",[158,1048,1049],{},"12TH",[158,1051,1052],{},"1.35",[158,1054,1055],{},"clipper",[158,1057,1058],{},"BA:Senior\u002FDisabled Clipper",[158,1060,1061],{},"Embarcadero to 12th with Clipper and discount",[140,1063,1064,1067,1069,1071,1073,1076,1078,1080],{},[158,1065,1066],{},"100",[158,1068,1043],{},[158,1070,1046],{},[158,1072,1049],{},[158,1074,1075],{},"3.70",[158,1077,1055],{},[158,1079],{},[158,1081,1082],{},"Embarcadero to 12th with Clipper",[140,1084,1085,1088,1090,1092,1094,1097,1099,1101],{},[158,1086,1087],{},"110",[158,1089,1043],{},[158,1091,1046],{},[158,1093,1049],{},[158,1095,1096],{},"4.20",[158,1098],{},[158,1100],{},[158,1102,1103],{},"Embarcadero to 12th with cash surcharge",[17,1105,1106,1107,589,1109,1111,1112,1114,1115,1117,1118,1120],{},"The BART leg would match the first the rules above based on ",[270,1108,996],{},[270,1110,1000],{},", with fares of $1.35, $3.70, and $4.20. However, the first two rules are only available when using a Clipper Card (",[270,1113,1003],{},"), and the first of these is only available to riders eligible for a discounted fare (",[270,1116,1006],{},"). The ",[270,1119,1016],{}," field is used to select the correct fare when multiple rules match the trip leg: any applicable discounted Clipper fare would match first, followed by adult Clipper fare, then finally the fare including additional charge for cash riders. In the event two (or more) rules match with the same order value, both are considered valid options to present to the rider.",[134,1122,1123,1146],{},[137,1124,1125],{},[140,1126,1127,1129,1131,1133,1135,1137,1139,1142,1144],{},[143,1128,1016],{},[143,1130,1019],{},[143,1132,996],{},[143,1134,1000],{},[143,1136,1026],{},[143,1138,1003],{},[143,1140,1141],{},"fare_product_id",[143,1143,1006],{},[143,1145,1033],{},[153,1147,1148,1171,1193,1216,1238],{},[140,1149,1150,1152,1155,1157,1159,1162,1164,1166,1168],{},[158,1151,1066],{},[158,1153,1154],{},"AC:local",[158,1156,1154],{},[158,1158,1154],{},[158,1160,1161],{},"2.25",[158,1163,1055],{},[158,1165],{},[158,1167],{},[158,1169,1170],{},"Adult local fare with clipper $2.25",[140,1172,1173,1175,1177,1179,1181,1184,1186,1188,1190],{},[158,1174,1087],{},[158,1176,1154],{},[158,1178,1154],{},[158,1180,1154],{},[158,1182,1183],{},"2.5",[158,1185],{},[158,1187],{},[158,1189],{},[158,1191,1192],{},"Adult local fare $2.5",[140,1194,1195,1197,1199,1201,1203,1206,1208,1210,1213],{},[158,1196,1066],{},[158,1198,1154],{},[158,1200,1154],{},[158,1202,1154],{},[158,1204,1205],{},"1.12",[158,1207],{},[158,1209],{},[158,1211,1212],{},"AC:senior",[158,1214,1215],{},"Discounted local fare $1.12 with Clipper",[140,1217,1218,1220,1222,1224,1226,1229,1231,1233,1235],{},[158,1219,1066],{},[158,1221,1154],{},[158,1223,1154],{},[158,1225,1154],{},[158,1227,1228],{},"1.25",[158,1230],{},[158,1232],{},[158,1234,1212],{},[158,1236,1237],{},"Discounted local fare $1.25",[140,1239,1240,1242,1244,1246,1248,1251,1253,1256,1258],{},[158,1241,1066],{},[158,1243,1154],{},[158,1245,1154],{},[158,1247,1154],{},[158,1249,1250],{},"0",[158,1252],{},[158,1254,1255],{},"AC:local:monthly",[158,1257],{},[158,1259,1260],{},"Free local fare with monthly pass",[17,1262,1263,1264,1266,1267,1269,1270,1273,1274,1277],{},"The AC Transit fare rules are similar, with the addition of a few extra columns. The 51A is an East Bay local only route (",[270,1265,1000],{}," is assumed), and matches each rule, and the rules for discounts and cash are applied as above. The ",[270,1268,1141],{}," field describes additional rules that are available to users of certain prepaid products, such as day passes and monthly passes. In this case, a rider with an Adult Local 31 Day Pass ($84, described in ",[270,1271,1272],{},"fare_products.txt",") would enjoy a free ride. More complex AC Transit fares use additional columns not pictured here (",[270,1275,1276],{},"fare_network_id",") and handle cases such as riding a Transbay bus and the different prices applied when riding within the East Bay vs. taking the trip all the way to the Salesforce Transit Center in downtown San Francisco.",[17,1279,1280,1281,1283,1284,1286,1287,1289,1290,1292,1293,1295,1296,29],{},"Any applicable transfers are calculated by reading the rules in ",[270,1282,983],{}," and matching each leg of the trip against each subsequent leg of the trip. This can create quite complicated models, but let’s start by looking at our BART and AC Transit legs. The clever bit is that many ",[270,1285,971],{}," rules can share the same ",[270,1288,1019],{},", which simplifies the number and types of transfer rules that must be defined. For example, all of the BART rules above use ",[270,1291,1043],{}," and all of the AC Transit rules use ",[270,1294,1154],{},". The table below is an except of ",[270,1297,983],{},[134,1299,1300,1330],{},[137,1301,1302],{},[140,1303,1304,1306,1309,1312,1314,1316,1319,1322,1325,1328],{},[143,1305,1016],{},[143,1307,1308],{},"from_leg_group_id",[143,1310,1311],{},"to_leg_group_id",[143,1313,1003],{},[143,1315,1026],{},[143,1317,1318],{},"duration_limit",[143,1320,1321],{},"duration_limit_type",[143,1323,1324],{},"fare_transfer_type",[143,1326,1327],{},"spanning_limit",[143,1329,1033],{},[153,1331,1332,1358],{},[140,1333,1334,1336,1338,1340,1342,1345,1347,1350,1353,1355],{},[158,1335,1066],{},[158,1337,1043],{},[158,1339,1154],{},[158,1341,1055],{},[158,1343,1344],{},"-0.5",[158,1346,1040],{},[158,1348,1349],{},"2",[158,1351,1352],{},"1",[158,1354,1349],{},[158,1356,1357],{},"1 credit of $-0.50 to AC w\u002Fin 90 minutes",[140,1359,1360,1362,1364,1366,1368,1371,1373,1375,1377,1380],{},[158,1361,1087],{},[158,1363,1043],{},[158,1365,1154],{},[158,1367],{},[158,1369,1370],{},"-0.25",[158,1372],{},[158,1374],{},[158,1376,1352],{},[158,1378,1379],{},"3",[158,1381,1382],{},"Cash: 2 fare credits of $0.25 each",[17,1384,1385,1386,997,1389,1392,1393,1396,1397,1400,1401,997,1404,1407,1408,1410],{},"Two different discounts apply when taking an AC Transit leg after a BART leg. When using Clipper, a $0.50 (",[270,1387,1388],{},"amount=-0.5",[270,1390,1391],{},"fare_transfer_type=1",") discount is applied to the first AC Transit leg (",[270,1394,1395],{},"spanning_limit=2",", which means it can only match a subjourney of two legs). Alternatively, a paper transfer slip given to cash users contains two tabs, each of which applies a $0.25 discount to the AC Transit cash fare (",[270,1398,1399],{},"spanning_limit=3",", or a subjourney of up to three legs). Additionally, the Clipper discount expires within 90 minutes after tagging off BART (",[270,1402,1403],{},"duration_limit=90",[270,1405,1406],{},"duration_limit_type=2","). Because the ",[270,1409,1016],{}," value is different, these two transfer options are mutually exclusive to Clipper and cash riders respectively.",[17,1412,1413],{},"The combination of matching fare rules and fare transfer rules allows describing even complicated transfers, such as discounts to SamTrans local bus riders who hold a Caltrain 2 zone or higher monthly pass, the several categories of upgrade charges when transfering from an AC Transit Local to an AC Transit Transbay bus, and the many varied products and transfers that apply full or partial fare to trips on the Dumbarton Express.",[123,1415,1417],{"id":1416},"agencies-in-the-beta-release","Agencies in the Beta Release",[17,1419,1420],{},"Note that this is a “beta” release. The GTFS Fares-v2 specification is still being finalized. It does not fully capture some functionality, like how AC Transit and VTA use “fare capping” so that riders never have to pay more in one day than the cost of a day pass. We also expect that as trip planners and other apps begin to consume the Regional Feed’s fare data that we may need to revise some of the data or our schema.",[17,1422,1423],{},"To our knowledge, Interline is the only organization to have a “rules engine” that can calculate journey costs using GTFS Fares-v2 data. We expect that as other organizations adopt the Interline fares rules engine or build their own equivalents, we may need to revisit some of the assumptions built into the engine.",[17,1425,1426],{},"The beta release of data includes fares and transfer discounts within and between eight agencies:",[64,1428,1429,1432,1435,1438,1441,1444,1447,1450],{},[67,1430,1431],{},"BART",[67,1433,1434],{},"SFMTA",[67,1436,1437],{},"AC Transit",[67,1439,1440],{},"SamTrans",[67,1442,1443],{},"VTA",[67,1445,1446],{},"Caltrain",[67,1448,1449],{},"Golden Gate Transit (bus only; not ferries)",[67,1451,1452],{},"Dumbarton Express",[17,1454,1455],{},"This list includes the seven largest agencies and a key connector across San Francisco Bay (Dumbarton Express). It should provide a broad enough sample of fares and transfer discounts to power a wide range of potential applications. This sample is also deep enough to inform analyses of fares, the cost of riding transit, and ideally even ways to reform fares and transfer discounts to produce more equitable outcomes for Bay Area transit riders.",[123,1457,1459],{"id":1458},"using-fares-and-transfer-discounts","Using Fares and Transfer Discounts",[17,1461,893],{},[514,1463,1464,1468,1472],{},[67,1465,1466],{},[25,1467,521],{"href":520},[67,1469,524,1470],{},[270,1471,904],{},[67,1473,1474,1475,29],{},"For more information about the fares and transfer discount files in the GTFS feed, see the ",[25,1476,1477],{"href":933},"GTFS-Fares v2 proposal document",[17,1479,1480,1481,29],{},"Interline and MTC expect to improve both the Fares-v2 beta data and schemas as we learn more. We welcome questions and corrections sent to the ",[25,1482,886],{"href":885},[95,1484,1486],{"id":1485},"public-transit-in-2020","Public Transit in 2020",[17,1488,1489],{},"A final note that behind every piece of transit data and every multi-modal trip plan are real people who drive vehicles, serve riders, and maintain equipment and facilities. Thank you to all the front-line workers keeping the Bay Area’s public transit systems and riders moving safely!",[95,1491,1493],{"id":1492},"acknowledgements","Acknowledgements",[17,1495,1496],{},"Credit and many thanks to project team members including Ian Rees and Ruth Miller (Interline), Nisar Kapeel and Kapeel Daryani (MTC), and our partners at Bay Area transit agencies.","2020-08-10T00:00:00.000-07:00","","md","672547ebb62841000136ed0a","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fheadway-july-only.png",null,{},true,"\u002Fblog\u002Fmtc-regional-gtfs-feed-additions",14,{"title":5,"description":1498},"blog\u002Fmtc-regional-gtfs-feed-additions",[1510,1511],"gtfs","511-sf-bay-regional-feed",false,"2024-11-04T16:45:36.000-08:00","nwAlyLzwiYzn79oMKEdW00japfGFzlWi122y9zZMr8o",[1516,1524,1531,1539,1548,1556,1563,1570,1578,1585,1592,1599,1607,1613,1620,1628,1635,1642,1649,1655,1662,1670,1677,1683,1690,1697,1699,1706,1715,1721,1728,1735,1741,1748,1755,1762],{"path":1517,"title":1518,"description":1519,"date":1520,"tags":1521,"image":1523,"imageAlt":1502},"\u002Fblog\u002Friding-transit-to-californias-beaches","Riding transit to California's beaches","California Coastal Commission maps car parking at 1,600+ public access points. A spatial join with Transitland Datasets reveals which trailheads, surf spots, and overlooks can be reached by bus or rail.","2026-04-23T10:12:35.000-07:00",[1522],"transitland","\u002Fcontent\u002Fimages\u002Funsplash\u002Fphoto-1746859782086-eafe092caa85.jpg",{"path":1525,"title":1526,"description":1527,"date":1528,"tags":1529,"image":1530,"imageAlt":1502},"\u002Fblog\u002Fexplore-gtfs-pathways-station-layouts-using-transitland","Explore GTFS-Pathways station layouts using Transitland","Visualize subway station topologies. Inspect wheelchair-accessible navigation. Transitland's free GTFS-Pathways viewer is powered by Interline Station Editor.","2026-03-04T20:48:03.000-08:00",[1522,1510],"\u002Fcontent\u002Fimages\u002Funsplash\u002Fphoto-1617727553230-35c143f84010.jpg",{"path":1532,"title":1533,"description":1534,"date":1535,"tags":1536,"image":1537,"imageAlt":1538},"\u002Fblog\u002Fgtfs-checksum-versioning","Same data, different zip: How to identify unique GTFS feed versions","Standard zip hashes are unreliable for GTFS versioning due to variable metadata. Learn to use content-aware checksums to accurately identify unique transit datasets.","2026-02-11T14:45:59.000-08:00",[1510,1522],"\u002Fcontent\u002Fimages\u002Funsplash\u002Fphoto-1531376653594-e9bcf0f0c65b.jpg","photograph of overlapping zippers (as a metaphor for different zip archives)",{"path":1540,"title":1541,"description":1542,"date":1543,"tags":1544,"image":1546,"imageAlt":1547},"\u002Fblog\u002Finterline-at-mobilitydatas-2025-workshop","Interline at MobilityData's 2025 Workshop","We're excited to be participating in this year’s MobilityData Workshop in Vancouver.","2025-10-02T10:58:42.000-07:00",[1545],"events","\u002Fcontent\u002Fimages\u002Funsplash\u002Fphoto-1699938648771-00dd74c6ce17.jpg","elevated train in Vancouver with trees, buildings, and mountains in background",{"path":1549,"title":1550,"description":1551,"date":1552,"tags":1553,"image":1554,"imageAlt":1555},"\u002Fblog\u002Feasily-inspect-gtfs-realtime-using-transitlands-website-or-api","Easily inspect GTFS Realtime using Transitland's website or API","Web browsers and text editors can't open GTFS Realtime. But with Transitland, you now can.","2025-07-21T20:45:24.000-07:00",[1510,1522],"\u002Fcontent\u002Fimages\u002F2025\u002F07\u002Fimage-2.png","Viewing a GTFS Realtime feed as human-readable JSON using the Transitland website",{"path":1557,"title":1558,"description":1559,"date":1560,"tags":1561,"image":1562,"imageAlt":1502},"\u002Fblog\u002Fannouncing-transitland-lib-v1-0-0","Announcing transitland-lib v1.0.0","We're pleased to announce the release of transitland-lib version 1.0.0. This software library, written in the Go programming language, is the foundation of the Transitland platform and integral to a growing range of purpose-built applications.","2025-03-28T12:56:25.000-07:00",[1510,1522],"\u002Fcontent\u002Fimages\u002F2025\u002F03\u002FCleanShot-2025-03-26-at-13.52.03-1.jpg",{"path":1564,"title":1565,"description":1566,"date":1567,"tags":1568,"image":1569,"imageAlt":1502},"\u002Fblog\u002Ftransitland-for-nighttime","Transitland for nighttime","Our engineering team has recently been refactoring some of the internals of the Transitland website. The main goal has been to update various components and dependencies, to better support Interline's consulting clients who also use these components. As a side effect: the canonical Transitland website now has an optional dark mode.","2025-02-25T14:23:06.000-08:00",[1522],"\u002Fcontent\u002Fimages\u002F2025\u002F02\u002FCleanShot-2025-02-25-at-13.37.14.jpg",{"path":1571,"title":1572,"description":1573,"date":1574,"tags":1575,"image":1576,"imageAlt":1577},"\u002Fblog\u002Fbuilt-with-transitland-instructables","Built with Transitland: Digital departures screen","Want to build your own display to show when a bus, train, or ferry next departs? Here's a fun Instructables how-to guide.","2025-01-10T09:40:06.000-08:00",[1522],"\u002Fcontent\u002Fimages\u002F2025\u002F01\u002FScreenshot-2025-01-10-at-09-28-24-NYC-Ferry-Schedule-Ticker-Clock-6-Steps--with-Pictures----Instructables.png","screenshot of webpage titled \"NYC Ferry Schedule Ticker Clock\"",{"path":1579,"title":1580,"description":1581,"date":1582,"tags":1583,"image":1584,"imageAlt":1502},"\u002Fblog\u002Finterline-at-trb-am-2025","Interline at TRB AM 2025","We'll be represented at the US Transportation Research Board Annual Meeting in Washington, D.C., by Interline principal Drew Dara-Abrams.","2025-01-03T10:37:33.000-08:00",[1545],"\u002Fcontent\u002Fimages\u002F2025\u002F01\u002Fblue-slider-2025-TRB-annual-meeting-1260x468px.jpg",{"path":1586,"title":1587,"description":1588,"date":1589,"tags":1590,"image":1591,"imageAlt":1502},"\u002Fblog\u002Fus-national-transit-database-releases-data-and-requests-more-feedback-2","US National Transit Database releases data and requests more feedback","Our recommendations to the US Federal Transit Administration regarding National Transit Database: Proposed Reporting Changes and Clarifications for Report Years 2025 and 2026. ","2024-12-24T14:54:17.000-08:00",[1510],"\u002Fcontent\u002Fimages\u002F2024\u002F12\u002FCleanShot-2024-12-24-at-14.58.25@2x.png",{"path":1593,"title":1594,"description":1595,"date":1596,"tags":1597,"image":1598,"imageAlt":1502},"\u002Fblog\u002Fhow-current-is-that-schedule","How current is that schedule?","The GTFS Best Practices guide recommends publishing data for the current data plus at least 7 days in the future. We've used the Transitland archives to assess how many feeds meet this goal.","2024-11-25T11:36:52.000-08:00",[1522],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Funnamed--1--1-1.png",{"path":1600,"title":1601,"description":1602,"date":1603,"tags":1604,"image":1605,"imageAlt":1606},"\u002Fblog\u002Fgiving-equal-prominence-to-buses-and-trains-on-the-map","Giving equal prominence to buses and trains on the map","We've refined Transitland's global map to emphasize where riders can access the most frequent transit service. Thanks to leaders at San Francisco's transit agency for informing this improvement.","2024-11-14T11:42:08.000-08:00",[1522],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002FRefinements-to-rail-line-width-1.png","screenshots of Transitland global transit map before and after changes to rail styling",{"path":1608,"title":1609,"description":1610,"date":1611,"tags":1612,"image":1502,"imageAlt":1502},"\u002Fblog\u002Fturning-off-the-transitland-v1-datastore-api","Turning off the Transitland v1 Datastore API","We announced the multi-step deprecation of the Transitland v1 API in a blog post in 2019. The time has now come the Interline team to finally turn off the v1 Datastore API.","2023-09-14T00:00:00.000-07:00",[1522],{"path":1614,"title":1615,"description":1616,"date":1617,"tags":1618,"image":1619,"imageAlt":1502},"\u002Fblog\u002Fus-ntd-reporting-gtfs-adopted","US Federal Transit Administration finalizes plan to collect GTFS URLs in US National Transit Database","To meet meet the Bipartisan Infrastructure Law's requirement to collect data on American transit agencies' \"geographic service area coverage,\" the US Federal Transit Administration will begin to require GTFS feeds from fixed-route transit agencies that receive federal funds.","2023-04-28T00:00:00.000-07:00",[1510],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fbil-geographic-service-coverage-area.png",{"path":1621,"title":1622,"description":1623,"date":1624,"tags":1625,"image":1627,"imageAlt":1502},"\u002Fblog\u002Finterline-blog-rss-feed","Follow the Interline blog using RSS","For the latest updates from Interline, you can now follow our blog using an RSS feed reader","2022-11-28T00:00:00.000-08:00",[1626],"about-interline","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fsocial_style_3_rss-512-1.png",{"path":1629,"title":1630,"description":1631,"date":1632,"tags":1633,"image":1634,"imageAlt":1502},"\u002Fblog\u002Fmtc-regional-gtfs-feed-fares-updates","Updated GTFS-Fares v2 for the SF Bay Area","MTC and Interline have released updated fares and transfer discounts for over 30 Bay Area transit agencies using the adopted GTFS-Fares v2 \"base implementation\" and a series of proposed extensions. ","2022-10-04T00:00:00.000-07:00",[1511,1510],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fios-directions-with-fares-2.png",{"path":1636,"title":1637,"description":1638,"date":1639,"tags":1640,"image":1641,"imageAlt":1502},"\u002Fblog\u002Fus-ntd-reporting-gtfs","US National Transit Database to collect GTFS URLs","American public transit agencies that receive federal funds are required to report information for inclusion in the National Transit Database. The Federal Transit Administration is proposing that each agency will also provide a URL for a GTFS feed in their NTD reports.","2022-09-07T00:00:00.000-07:00",[1510],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fus-ntd-federal-register.png",{"path":1643,"title":1644,"description":1645,"date":1646,"tags":1647,"image":1648,"imageAlt":1502},"\u002Fblog\u002Fmtc-regional-stop-observations","Observed stop arrivals and departures through the SF Bay Area","Interline and the Metropolitan Transportation Commission are now releasing monthly \"stop observation\" datasets derived from the Regional GTFS Realtime Feed.","2022-07-15T15:25:00.000-07:00",[1510,1511],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftrip-update-selection.png",{"path":1650,"title":1651,"description":1652,"date":1653,"tags":1654,"image":1502,"imageAlt":1502},"\u002Fblog\u002Fdownloading-archived-gtfs-feed-versions-from-transitland","Downloading archived GTFS feed versions from Transitland","We are adjusting access to Transitland's GTFS feed version archive to better balance concerns.","2022-06-16T00:00:00.000-07:00",[1522],{"path":1656,"title":1657,"description":1658,"date":1659,"tags":1660,"image":1661,"imageAlt":1502},"\u002Fblog\u002Fvector-map-tiles","Transitland Vector Tile Improvements","Since releasing the global transit map and v2 Vector Tiles API last year, we've added a variety of improvements in functionality and in rendering.","2022-06-10T00:00:00.000-07:00",[1522],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fglobal-transit-map-europe.png",{"path":1663,"title":1664,"description":1665,"date":1666,"tags":1667,"image":1668,"imageAlt":1669},"\u002Fblog\u002Fmobility-data-interoperability-principles","Supporting the Mobility Data Interoperability Principles","Interline is pleased to sign the newly drafted Mobility Data Interoperability Principles.","2021-11-18T00:00:00.000-08:00",[1626],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fmobility-data-interoperability-principles-full.png","Mobility Data Interoperability Principles overview diagram",{"path":1671,"title":1672,"description":1673,"date":1674,"tags":1675,"image":1676,"imageAlt":1502},"\u002Fblog\u002Fmtc-regional-gtfs-realtime-feed","SF Bay Area's Regional GTFS Realtime Feed","The Metropolitan Transportation Commission and Interline are pleased to announce a single consolidated Regional GTFS Realtime feed. Developers can now get a comprehensive and up-to-date views of the Bay Area's bus, train, and ferry services.","2021-09-10T00:00:00.000-07:00",[1511],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Flist-of-rt-enabled-agencies.png",{"path":1678,"title":1679,"description":1680,"date":1681,"tags":1682,"image":1502,"imageAlt":1502},"\u002Fblog\u002Ftransitland-v2-search","Use Transitland v2 to Search Across Operators, Feeds, and Routes","Here's one of our favorite new additions to Transitland v2: search across all of the operators, feed records, and routes in Transitland.","2021-03-04T00:00:00.000-08:00",[1522],{"path":1684,"title":1685,"description":1686,"date":1687,"tags":1688,"image":1689,"imageAlt":1502},"\u002Fblog\u002Ftransitland-v2-vector-map-tiles","Transitland v2 Adds a Global Map and Vector Tiles","Here's one of our favorite new additions to Transitland v2: a \"slippy map\" of transit routes and stops around the world.","2021-02-25T00:00:00.000-08:00",[1522],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftlv2-map-animation.jpg",{"path":1691,"title":1692,"description":1693,"date":1694,"tags":1695,"image":1696,"imageAlt":1502},"\u002Fblog\u002Ftrb-transit-idea-gtfs-realtime-report","Our GTFS Realtime validation report published by the Transportation Research Board","In 2019 and 2020, Interline and the Center for Urban Transportation Research at University of South Florida collaborated on a Transit IDEA Program grant from the US Transportation Research Board. Our goal has been to help transit agencies to validate and improve the quality of their GTFS Realtime feeds. This first grant is now complete and TRB has published the full report with our findings and proposed next steps.","2021-01-19T00:00:00.000-08:00",[1510],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftrb-t-93-report-cover.png",{"path":1505,"title":5,"description":1498,"date":1497,"tags":1698,"image":1501,"imageAlt":1502},[1510,1511],{"path":1700,"title":1701,"description":1702,"date":1703,"tags":1704,"image":1705,"imageAlt":1502},"\u002Fblog\u002Fmtc-regional-gtfs-feed-release","A Regional GTFS Feed for the San Francisco Bay Area","Last year, Interline began a \"startup in residence\" at the Metropolitan Transportation Commission. Now we're pleased to publicly release our first creation: the San Francisco Bay Area's Regional GTFS Feed.","2020-01-08T00:00:00.000-08:00",[1510,1511],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fmtc-regional-feed-all-routes.png",{"path":1707,"title":1708,"description":1709,"date":1710,"tags":1711,"image":1714,"imageAlt":1502},"\u002Fblog\u002Fhere-cli-support-geojsonl","Even more geospatial tools supporting the \"GeoJSONL\" format","\"GeoJSONL\" has the easy readability of a GeoJSON file without the the performance limitations of the format. Last year we started producing GeoJSONL files from our OSM Extracts service. Now a growing list of long-existing and brand-new geospatial tools.","2019-03-08T00:00:00.000-08:00",[1712,1713],"geojsonl","openstreetmap","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fdownload-geojsonl-extract.png",{"path":1716,"title":1717,"description":1718,"date":1719,"tags":1720,"image":1502,"imageAlt":1502},"\u002Fblog\u002Ftransportation-research-board-funds-gtfs-realtime","Transportation Research Board funds an open platform for transit agencies to improve the quality of their real-time data","We’re excited to share that the Transportation Research Board has awarded a Transit IDEA Program grant to Interline. We’re using this unique opportunity to expand Transitland to support GTFS Realtime feeds.","2019-01-23T00:00:00.000-08:00",[1510,1522],{"path":1722,"title":1723,"description":1724,"date":1725,"tags":1726,"image":1727,"imageAlt":1502},"\u002Fblog\u002Fmetropolitan-transportation-commission-selects-interline","Metropolitan Transportation Commission and Interline to tackle regional transit data challenges","We're excited to share that the Metropolitan Transportation Commission has selected Interline through a competitive process to participate in its 2019 Startup in Residence (STIR) program. Interline and MTC will collaborate on the problem of regional transit data.","2019-01-10T00:00:00.000-08:00",[1522,1511],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fstir-banner.png",{"path":1729,"title":1730,"description":1731,"date":1732,"tags":1733,"image":1734,"imageAlt":1502},"\u002Fblog\u002Ftlv2","Transitland Version 2","What first started as two simple, separate, little experiments has grown into the seeds of a major revision of the entire Transitland platform: Transitland Version 2.","2019-01-08T00:00:00.000-08:00",[1522,1510],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftlv2-architecture-diagram.png",{"path":1736,"title":1737,"description":1738,"date":1732,"tags":1739,"image":1740,"imageAlt":1502},"\u002Fblog\u002Ftransitland-continues","Transitland Continues in 2019","Just like a garden, open-source and open-data projects require continual tending. With 2019 beginning, we're glad to share more widely these plans for Transitland's ongoing tending and growth as an open platform.",[1522],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftransitland_logo.png",{"path":1742,"title":1743,"description":1744,"date":1745,"tags":1746,"image":1747,"imageAlt":1502},"\u002Fblog\u002Fhere-xyz-open-geo-data","Bringing Back the Spirit of Map Mashups: Combine Open Geodata APIs using HERE XYZ","Interline and HERE are collaborating to make Interline's open data services like OSM Extracts and the Transitland API easy to combine, mix, filter, analyze, and visualize using the new HERE XYZ platform. ","2018-10-01T00:00:00.000-07:00",[1713,1522],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fxyz-tutorial-1-animation.jpg",{"path":1749,"title":1750,"description":1751,"date":1752,"tags":1753,"image":1754,"imageAlt":1502},"\u002Fblog\u002Fgeojsonl-extracts","GeoJSONL: An optimized format for large geographic datasets","GeoJSON Lines (geojsonl) is a simple, newline-delimited variant of GeoJSON that allows large datasets to be loaded with a much lower memory footprint and easily integrate with traditional text-based tools. Interline OSM Extracts now provides geojsonl, along with a small but growing number of tools.","2018-09-11T00:00:00.000-07:00",[1713,1712],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fpreview.png",{"path":1756,"title":1757,"description":1758,"date":1759,"tags":1760,"image":1761,"imageAlt":1502},"\u002Fblog\u002Fopen-source-best-practices-for-otp-summit","Practices that help complex and collaborative open-source projects survive and thrive","We've encountered many practices that can help complex and collaborative open-source projects survive and thrive. This blog post provides a tour through many open-source practices, particularly ones that are helpful for aging but popular software packages like OpenTripPlanner.","2018-07-06T00:00:00.000-07:00",[1545],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftable-of-contents.png",{"path":1763,"title":1764,"description":1765,"date":1766,"tags":1767,"image":1768,"imageAlt":1502},"\u002Fblog\u002Fscaling-openstreetmap-data-workflows","Producing 200 OpenStreetMap extracts in 35 minutes using a scalable data workflow","Interline now offers OSM Extracts, a service enabling software developers and GIS professionals to download chunks of OpenStreetMap data for 200 major cities and regions around the world.","2018-05-25T00:00:00.000-07:00",[1713],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fargo-workflow-screenshot.png",1792086309178]