[{"data":1,"prerenderedAt":990},["ShallowReactive",2],{"post:\u002Fblog\u002Fmtc-regional-stop-observations":3,"blog:siblings":737},{"id":4,"title":5,"authors":6,"body":8,"date":719,"description":720,"extension":721,"ghostId":722,"image":723,"imageAlt":724,"imageCaption":724,"imageVideo":724,"meta":725,"navigation":726,"path":727,"readingTime":728,"seo":729,"stem":730,"tags":731,"toc":734,"updated":735,"__hash__":736},"blog\u002Fblog\u002Fmtc-regional-stop-observations.md","Observed stop arrivals and departures through the SF Bay Area",[7],"drew",{"type":9,"value":10},"minimark",[11,15,24,29,32,50,53,57,64,67,71,78,89,96,580,584,587,602,610,623,626,630,650,653,657,660,670,693,696,704,708,711],[12,13,14],"p",{},"When did the bus arrived at that stop yesterday? This isn’t a question that transit riders ask often — but it is a question that analysts and planners often do ask.",[12,16,17,18,23],{},"Interline and the Metropolitan Transportation Commission have been archiving and processing the ",[19,20,22],"a",{"href":21},"\u002Fblog\u002Fmtc-regional-gtfs-realtime-feed\u002F","Regional GTFS Realtime"," feed in order to answer these questions.",[25,26,28],"h2",{"id":27},"what-are-stop-observations","What are stop observations?",[12,30,31],{},"“Stop observations” describes transit service as was delivered to riders: the arrival time of a vehicle at a designated stop, along with any additional contextual information available from GTFS and GTFS Realtime feeds.",[12,33,34,35,39,40,44,45,49],{},"Stop observations are in contrast with the ",[36,37,38],"code",{},"stop_times.txt"," file in the ",[19,41,43],{"href":42},"\u002Fblog\u002Fmtc-regional-gtfs-feed-release\u002F","daily Regional Feed",", which uses static GTFS data to capture transit service as it is planned and scheduled. This is also in contrast with the ",[19,46,48],{"href":47},"\u002Fblog\u002Fmtc-regional-gtfs-feed-additions\u002F#historical-feeds","monthly Historic Regional Feed",", which uses static GTFS data to capture transit service schedules, retrospectively, as they changed over an entire month (with a different schedule for each agency for each day).",[12,51,52],{},"Stop observations can be used to better understand the real-world realities of transit service as it fluctuates from day to day and location to location. Stop observations can be used to estimate on-time performance (also known as schedule adherence or punctuality) and to inform potential schedule adjustments by service planners. Stop observations can also be used by navigation app developers to provide their users with contextual information, such as an estimated range of times when a route is likely to depart from a given stop.",[25,54,56],{"id":55},"measurement-error-and-imprecision","Measurement error and (im)precision",[12,58,59,60,63],{},"Stop observations are inferred from public GTFS Realtime data feeds (trip updates and vehicle positions) and therefore, there are many potential sources for measurement error. Potential sources of error include GPS error on transit vehicles, misassignment of vehicles to “runs” of a given trip and route, imprecision or data errors in the transit agency’s computer-aided dispatch\u002Fautomatic vehicle location (CAD\u002FAVL) system, issues in the transit agency’s GTFS Realtime emitting system, issues in 511.org’s GTFS Realtime aggregation system, or issues in the ",[19,61,62],{"href":21},"Regional Realtime GTFS Feed",".",[12,65,66],{},"We’ll discuss how stop observations are calculated later in this blog post, to help users better understand stop observations as measurements. When considering potential applications for stop observations, we ask users to keep the limitations of this data source in mind.",[25,68,70],{"id":69},"what-information-is-contained-in-a-stop-observation","What information is contained in a stop observation?",[12,72,73,74,77],{},"We are distributing stop observations in the Historic Regional Feed. When users request a Historic Regional Feed with stop observations for a given year and month, a ",[36,75,76],{},"stop_observations.txt"," file will be included with all stop observations for that month.",[12,79,80,81,83,84,88],{},"The ",[36,82,76],{}," file is a CSV file based on the ",[19,85,87],{"href":86},"https:\u002F\u002Fbit.ly\u002Fgtfs-performance","GTFS-Performance draft proposal",". GTFS-Performance is an extension to the GTFS specification prepared by Remix, Swiftly, and their partners.",[12,90,91,92,95],{},"The following table is based on the GTFS-Performance draft proposal and covers columns included in our implementation of ",[36,93,94],{},"stops_observations.txt",", as well as columns that are in the proposal but not in our implementation:",[97,98,99,115],"table",{},[100,101,102],"thead",{},[103,104,105,109,112],"tr",{},[106,107,108],"th",{},"Field Name",[106,110,111],{},"Details",[106,113,114],{},"Regional GTFS stop observations support",[116,117,118,147,177,192,208,249,266,289,308,324,348,369,388,404,420,441,459,485,503,521,539,560],"tbody",{},[103,119,120,126,142],{},[121,122,123],"td",{},[36,124,125],{},"trip_id",[121,127,128,131],{},[12,129,130],{},"Identifies a trip.",[12,132,133,134,137,138,141],{}," When ",[36,135,136],{},"schedule_relationship=DUPLICATED",", then this references the trip that is copied, like GTFS Realtime ",[36,139,140],{},"TripUpdate.trip.trip_id",". ",[121,143,144],{},[12,145,146],{},"✅",[103,148,149,154,172],{},[121,150,151],{},[36,152,153],{},"trip_start_time",[121,155,156,162],{},[12,157,158,159,141],{}," See GTFS Realtime ",[36,160,161],{},"TripDescriptor.start_time",[12,163,164,165,168,169,63],{},"Required to specify the start time of a trip that’s not defined in Static GTFS which occurs when using frequency-based service defined by ",[36,166,167],{},"frequencies.txt"," or when an ad-hoc added service based on an existing trip via ",[36,170,171],{},"TripUpdate.tripschedule_relationship=DUPLICATED",[121,173,174],{},[12,175,176],{},"✅ (when provided in agency source RT feed)",[103,178,179,184,189],{},[121,180,181],{},[36,182,183],{},"stop_id",[121,185,186],{},[12,187,188],{},"Identifies a stop",[121,190,191],{},"✅ (added by Interline for developer convenience)",[103,193,194,199,204],{},[121,195,196],{},[36,197,198],{},"stop_sequence",[121,200,201],{},[12,202,203],{},"Identifies the order of stops for a particular trip.",[121,205,206],{},[12,207,146],{},[103,209,210,215,245],{},[121,211,212],{},[36,213,214],{},"schedule_relationship",[121,216,217,220],{},[12,218,219],{},"Valid options are:",[221,222,223,227,230,233,236,239,242],"ul",{},[224,225,226],"li",{}," 0 - SCHEDULED ",[224,228,229],{}," 1 - SKIPPED ",[224,231,232],{}," 2 - NO_DATA ",[224,234,235],{}," 3 - UNSCHEDULED ",[224,237,238],{}," 4 - CANCELED ",[224,240,241],{}," 5 - DUPLICATED ",[224,243,244],{},"6 - MODIFIED",[121,246,247],{},[12,248,146],{},[103,250,251,256,261],{},[121,252,253],{},[36,254,255],{},"schedule_adherence_stop",[121,257,258],{},[12,259,260],{},"Indicates if this observation is used for reporting purposes when a subset of stops are utilized, instead of all stops.",[121,262,263],{},[12,264,265],{},"No",[103,267,268,273,285],{},[121,269,270],{},[36,271,272],{},"trip_start_date",[121,274,275],{},[12,276,277,278,281,282,63],{},"The start date of this trip instance in ",[36,279,280],{},"YYYYMMDD"," format to specify the service date of the corresponding trip. This should match the value in ",[36,283,284],{},"TripDescriptor.start_date",[121,286,287],{},[12,288,146],{},[103,290,291,296,304],{},[121,292,293],{},[36,294,295],{},"vehicle_id",[121,297,298],{},[12,299,300,301,141],{}," Unique identifier for the vehicle that served this stop. This should match the value provided in real-time via ",[36,302,303],{},"VehicleDescriptor.id",[121,305,306],{},[12,307,176],{},[103,309,310,315,320],{},[121,311,312],{},[36,313,314],{},"scheduled_arrival_time",[121,316,317],{},[12,318,319],{}," GTFS static scheduled arrival time ",[121,321,322],{},[12,323,191],{},[103,325,326,331,344],{},[121,327,328],{},[36,329,330],{},"observed_arrival_time",[121,332,333],{},[12,334,335,336,339,340,343],{},"Observed arrival time at a specific stop for a specific trip on a route. For times occurring after midnight on the service day, enter the time as a value greater than ",[36,337,338],{},"24:00:00"," in ",[36,341,342],{},"HH:MM:SS"," local time for the day on which the trip schedule begins.",[121,345,346],{},[12,347,146],{},[103,349,350,355,364],{},[121,351,352],{},[36,353,354],{},"observed_departure_time",[121,356,357],{},[12,358,359,360,339,362,343],{},"Observed departure time at a specific stop for a specific trip on a route. For times occurring after midnight on the service day, enter the time as a value greater than ",[36,361,338],{},[36,363,342],{},[121,365,366],{},[12,367,368],{},"✅ (when available)",[103,370,371,376,384],{},[121,372,373],{},[36,374,375],{},"new_departure_time",[121,377,378],{},[12,379,380,381,63],{},"Required when ",[36,382,383],{},"schedule_relationship=DEPARTURE_TIME_MODIFIED",[121,385,386],{},[12,387,265],{},[103,389,390,395,400],{},[121,391,392],{},[36,393,394],{},"dwell_time_secs",[121,396,397],{},[12,398,399],{},"Seconds spend boarding\u002Falighting riders at the stop.",[121,401,402],{},[12,403,265],{},[103,405,406,411,416],{},[121,407,408],{},[36,409,410],{},"scheduled_dwell_time_secs",[121,412,413],{},[12,414,415],{},"Seconds scheduled for boarding\u002Falighting riders at the stop (when provided in agency source RT feed).",[121,417,418],{},[12,419,146],{},[103,421,422,427,437],{},[121,423,424],{},[36,425,426],{},"boardings",[121,428,429],{},[12,430,431,432,436],{},"See ",[19,433,435],{"href":434},"https:\u002F\u002Fgtfsride.org\u002F","GTFS-ride","'s board_alight.boardings",[121,438,439],{},[12,440,265],{},[103,442,443,448,455],{},[121,444,445],{},[36,446,447],{},"alightings",[121,449,450],{},[12,451,431,452,454],{},[19,453,435],{"href":434},"'s board_alight.alightings",[121,456,457],{},[12,458,265],{},[103,460,461,466,481],{},[121,462,463],{},[36,464,465],{},"source",[121,467,468,470],{},[12,469,219],{},[221,471,472,475,478],{},[224,473,474],{},"0 - Manual",[224,476,477],{},"1 - Door Sensor",[224,479,480],{},"2 - Estimated using GPS\u002FAVL data",[121,482,483],{},[12,484,265],{},[103,486,487,492,499],{},[121,488,489],{},[36,490,491],{},"uncertainty",[121,493,494],{},[12,495,431,496,63],{},[36,497,498],{},"StopTimeEvent.uncertainty",[121,500,501],{},[12,502,146],{},[103,504,505,510,517],{},[121,506,507],{},[36,508,509],{},"occupancy_status",[121,511,512],{},[12,513,431,514,63],{},[36,515,516],{},"VehiclePosition.occupancy_status",[121,518,519],{},[12,520,176],{},[103,522,523,528,535],{},[121,524,525],{},[36,526,527],{},"occupancy_percentage",[121,529,530],{},[12,531,431,532,63],{},[36,533,534],{},"VehiclePosition.occupancy_percentage",[121,536,537],{},[12,538,176],{},[103,540,541,546,556],{},[121,542,543],{},[36,544,545],{},"occupancy_type",[121,547,548],{},[12,549,431,550,552,553,63],{},[19,551,435],{"href":434},"'s ",[36,554,555],{},"board_alight.load_type",[121,557,558],{},[12,559,265],{},[103,561,562,567,576],{},[121,563,564],{},[36,565,566],{},"occupancy_source",[121,568,569],{},[12,570,431,571,552,573,63],{},[19,572,435],{"href":434},[36,574,575],{},"board_alight.source",[121,577,578],{},[12,579,265],{},[25,581,583],{"id":582},"how-are-stop-observations-calculated","How are stop observations calculated?",[12,585,586],{},"Stop observations are derived retrospectively using an archive of the Regional GTFS Realtime Feed (updated every 15 seconds). Once a day, our workflow processes GTFS Realtime trip updates and vehicle positions from the archive, combined together with the day’s static GTFS daily regional feed.",[12,588,589,593,594,597,598,601],{},[590,591,592],"strong",{},"Deriving stop observations from trip updates:"," When an agency supplies GTFS Realtime trip updates, our workflow identifies the final ",[36,595,596],{},"TripUpdate"," sent before a vehicle reaches a given stop. From that record, our workflow extracts the most recent ",[36,599,600],{},"StopTimeUpdate",". Here is an example showing three trip updates fetched from BART. The first two trip updates are before the train reaches Montgomery Station; the third trip update is after the train departs Montgomery Station. The portion of all of the records that is use to create a stop observation is marked with the orange box:",[603,604],"il-figure",{"alt":605,"img-height":606,"img-width":607,"src":608,"width":609},"illustration of three GTFS Realtime feed trip updates, showing the portion of stop time updates retained to create a stop observation record","943","1167","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftrip-update-selection-1.png","wide",[12,611,612,615,616,619,620,622],{},[590,613,614],{},"Deriving stop observations from vehicle positions",": When an agency supplies vehicle positions for a given route, our workflow also identifies the last update sent before the stop location. To do this, we need to consider the geometry of the route alignment from ",[36,617,618],{},"shapes.txt"," in the static RG feed. The workflow snaps the latitude\u002Flongitude point from each vehicle position to the route alignment, enabling it to determine from which update to take the ",[36,621,600],{}," portion. Like many geometric algorithms, this approach can be stymied by complicated paths, such as looping routes that visit the same station multiple times. Our workflow can take advantage of stop sequence, when specified. Still, the algorithm can only do its best to estimate when the route alignment is complicated and\u002For the update frequency is infrequent.",[12,624,625],{},"By being able to derive stop observations from two different parts of GTFS Realtime feeds, we have also been able to test and tune our workflow, to ensure that the two approaches agree when source feeds are of high quality.",[25,627,629],{"id":628},"related-data-specifications","Related data specifications",[12,631,632,633,637,638,642,643,646,647,649],{},"Our stop observations data model is based on the ",[19,634,636],{"href":635},"http:\u002F\u002Fbit.ly\u002Fgtfs-performance","GTFS-Performance"," proposal. The GTFS-Performance proposal is, in turn, inspired by the larger ",[19,639,641],{"href":640},"https:\u002F\u002Fapps.trb.org\u002Fcmsfeed\u002FTRBNetProjectDisplay.asp?ProjectID=4687","TCRP G-18"," project. The GTFS-Performance ",[36,644,645],{},"stop_visits.txt"," is supposed to represent a subset of the TCRP G-18 ",[36,648,645],{}," file. Thank you to the creators of GTFS-Performance and to the G-18 research team.",[12,651,652],{},"GTFS-Performance and TCRP G-18 go well beyond the functionality that we have implemented in our system for producing stop observations, to also address more internal operating concerns of transit agencies. We have intentionally implemented our system to create stop observations using only publicly available GTFS and GTFS Realtime inputs.",[25,654,656],{"id":655},"accessing-stop-observations","Accessing stop observations",[12,658,659],{},"Stop observations are now included in historical monthly RGs. To download a historical monthly RG including stop observations, make an HTTP request like so:",[661,662,667],"pre",{"className":663,"code":665,"language":666},[664],"language-text","wget https:\u002F\u002Fapi.511.org\u002Ftransit\u002Fdatafeeds?operator_id=RG&historic=2022-03-so&api_key=xxx\n","text",[36,668,665],{"__ignoreMap":669},"",[12,671,672,673,676,677,680,681,684,685,688,689,63],{},"Replace ",[36,674,675],{},"2022-03"," with a given year and month. Note the addition of ",[36,678,679],{},"-so"," to request the inclusion of stop observations. Note that ",[36,682,683],{},"wget"," is a Unix command that can be replaced by any other utility to download the URL; also note that ",[36,686,687],{},"xxx"," should be replaced by your own ",[19,690,692],{"href":691},"https:\u002F\u002F511.org\u002Fopen-data\u002Ftoken","511.org Open Data API key",[12,694,695],{},"Monthly RGs without stop observations are roughly 50Mb in size; with stop observations, the monthly RG will be roughly 500Mb to download as a compressed ZIP archive and then roughly 2Gb of uncompressed CSV files.",[12,697,698,699,703],{},"Stop observations are available on a more frequent basis to staff at MTC and Bay Area transit agencies. Transit agencies may contact the 511 SF Bay Data Portal at ",[19,700,702],{"href":701},"mailto:transitdata@511.org","transitdata@511.org"," for more information.",[25,705,707],{"id":706},"using-stop-observations-to-understand-transit","Using stop observations to understand transit",[12,709,710],{},"Public-transit agencies can be hesitant to release this type of data. In part, it’s a challenge to assemble operations data in an ongoing and consistent manner. In part, it’s a risk that the general public will take operations data out of context.",[12,712,713,714,718],{},"While we began this blog post by asking ",[715,716,717],"em",{},"When did the bus arrived at that stop yesterday?",", we hope that users of stop observations will ask an even wider range of questions of this dataset, especially questions that can explore the complexity of daily operations for over 20 agencies operating buses, trains, subways, and ferries across the Bay Area and questions that can help to improve the experience for riders using navigation apps and similar software.","2022-07-15T15:25:00.000-07:00","Interline and the Metropolitan Transportation Commission are now releasing monthly \"stop observation\" datasets derived from the Regional GTFS Realtime Feed.","md","672554e4b62841000136ed97","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftrip-update-selection.png",null,{},true,"\u002Fblog\u002Fmtc-regional-stop-observations",6,{"title":5,"description":720},"blog\u002Fmtc-regional-stop-observations",[732,733],"gtfs","511-sf-bay-regional-feed",false,"2024-11-04T16:15:25.000-08:00","VtZ2m-wkRUefJn2K2CJq-0RPTAZZrj8LMovBVwys7W8",[738,746,753,761,770,778,785,792,800,807,814,821,829,835,842,850,857,864,866,872,879,887,894,900,907,914,920,927,936,942,949,956,962,969,976,983],{"path":739,"title":740,"description":741,"date":742,"tags":743,"image":745,"imageAlt":724},"\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",[744],"transitland","\u002Fcontent\u002Fimages\u002Funsplash\u002Fphoto-1746859782086-eafe092caa85.jpg",{"path":747,"title":748,"description":749,"date":750,"tags":751,"image":752,"imageAlt":724},"\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",[744,732],"\u002Fcontent\u002Fimages\u002Funsplash\u002Fphoto-1617727553230-35c143f84010.jpg",{"path":754,"title":755,"description":756,"date":757,"tags":758,"image":759,"imageAlt":760},"\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",[732,744],"\u002Fcontent\u002Fimages\u002Funsplash\u002Fphoto-1531376653594-e9bcf0f0c65b.jpg","photograph of overlapping zippers (as a metaphor for different zip archives)",{"path":762,"title":763,"description":764,"date":765,"tags":766,"image":768,"imageAlt":769},"\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",[767],"events","\u002Fcontent\u002Fimages\u002Funsplash\u002Fphoto-1699938648771-00dd74c6ce17.jpg","elevated train in Vancouver with trees, buildings, and mountains in background",{"path":771,"title":772,"description":773,"date":774,"tags":775,"image":776,"imageAlt":777},"\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",[732,744],"\u002Fcontent\u002Fimages\u002F2025\u002F07\u002Fimage-2.png","Viewing a GTFS Realtime feed as human-readable JSON using the Transitland website",{"path":779,"title":780,"description":781,"date":782,"tags":783,"image":784,"imageAlt":724},"\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",[732,744],"\u002Fcontent\u002Fimages\u002F2025\u002F03\u002FCleanShot-2025-03-26-at-13.52.03-1.jpg",{"path":786,"title":787,"description":788,"date":789,"tags":790,"image":791,"imageAlt":724},"\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",[744],"\u002Fcontent\u002Fimages\u002F2025\u002F02\u002FCleanShot-2025-02-25-at-13.37.14.jpg",{"path":793,"title":794,"description":795,"date":796,"tags":797,"image":798,"imageAlt":799},"\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",[744],"\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":801,"title":802,"description":803,"date":804,"tags":805,"image":806,"imageAlt":724},"\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",[767],"\u002Fcontent\u002Fimages\u002F2025\u002F01\u002Fblue-slider-2025-TRB-annual-meeting-1260x468px.jpg",{"path":808,"title":809,"description":810,"date":811,"tags":812,"image":813,"imageAlt":724},"\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",[732],"\u002Fcontent\u002Fimages\u002F2024\u002F12\u002FCleanShot-2024-12-24-at-14.58.25@2x.png",{"path":815,"title":816,"description":817,"date":818,"tags":819,"image":820,"imageAlt":724},"\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",[744],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Funnamed--1--1-1.png",{"path":822,"title":823,"description":824,"date":825,"tags":826,"image":827,"imageAlt":828},"\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",[744],"\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":830,"title":831,"description":832,"date":833,"tags":834,"image":724,"imageAlt":724},"\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",[744],{"path":836,"title":837,"description":838,"date":839,"tags":840,"image":841,"imageAlt":724},"\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",[732],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fbil-geographic-service-coverage-area.png",{"path":843,"title":844,"description":845,"date":846,"tags":847,"image":849,"imageAlt":724},"\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",[848],"about-interline","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fsocial_style_3_rss-512-1.png",{"path":851,"title":852,"description":853,"date":854,"tags":855,"image":856,"imageAlt":724},"\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",[733,732],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fios-directions-with-fares-2.png",{"path":858,"title":859,"description":860,"date":861,"tags":862,"image":863,"imageAlt":724},"\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",[732],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fus-ntd-federal-register.png",{"path":727,"title":5,"description":720,"date":719,"tags":865,"image":723,"imageAlt":724},[732,733],{"path":867,"title":868,"description":869,"date":870,"tags":871,"image":724,"imageAlt":724},"\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",[744],{"path":873,"title":874,"description":875,"date":876,"tags":877,"image":878,"imageAlt":724},"\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",[744],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fglobal-transit-map-europe.png",{"path":880,"title":881,"description":882,"date":883,"tags":884,"image":885,"imageAlt":886},"\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",[848],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fmobility-data-interoperability-principles-full.png","Mobility Data Interoperability Principles overview diagram",{"path":888,"title":889,"description":890,"date":891,"tags":892,"image":893,"imageAlt":724},"\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",[733],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Flist-of-rt-enabled-agencies.png",{"path":895,"title":896,"description":897,"date":898,"tags":899,"image":724,"imageAlt":724},"\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",[744],{"path":901,"title":902,"description":903,"date":904,"tags":905,"image":906,"imageAlt":724},"\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",[744],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftlv2-map-animation.jpg",{"path":908,"title":909,"description":910,"date":911,"tags":912,"image":913,"imageAlt":724},"\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",[732],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftrb-t-93-report-cover.png",{"path":915,"title":916,"description":669,"date":917,"tags":918,"image":919,"imageAlt":724},"\u002Fblog\u002Fmtc-regional-gtfs-feed-additions","SF Bay Area's Regional GTFS Feed Expanded","2020-08-10T00:00:00.000-07:00",[732,733],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fheadway-july-only.png",{"path":921,"title":922,"description":923,"date":924,"tags":925,"image":926,"imageAlt":724},"\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",[732,733],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fmtc-regional-feed-all-routes.png",{"path":928,"title":929,"description":930,"date":931,"tags":932,"image":935,"imageAlt":724},"\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",[933,934],"geojsonl","openstreetmap","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fdownload-geojsonl-extract.png",{"path":937,"title":938,"description":939,"date":940,"tags":941,"image":724,"imageAlt":724},"\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",[732,744],{"path":943,"title":944,"description":945,"date":946,"tags":947,"image":948,"imageAlt":724},"\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",[744,733],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fstir-banner.png",{"path":950,"title":951,"description":952,"date":953,"tags":954,"image":955,"imageAlt":724},"\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",[744,732],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftlv2-architecture-diagram.png",{"path":957,"title":958,"description":959,"date":953,"tags":960,"image":961,"imageAlt":724},"\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.",[744],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftransitland_logo.png",{"path":963,"title":964,"description":965,"date":966,"tags":967,"image":968,"imageAlt":724},"\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",[934,744],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fxyz-tutorial-1-animation.jpg",{"path":970,"title":971,"description":972,"date":973,"tags":974,"image":975,"imageAlt":724},"\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",[934,933],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fpreview.png",{"path":977,"title":978,"description":979,"date":980,"tags":981,"image":982,"imageAlt":724},"\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",[767],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftable-of-contents.png",{"path":984,"title":985,"description":986,"date":987,"tags":988,"image":989,"imageAlt":724},"\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",[934],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fargo-workflow-screenshot.png",1792086309362]