[{"data":1,"prerenderedAt":547},["ShallowReactive",2],{"post:\u002Fblog\u002Ftlv2":3,"blog:siblings":294},{"id":4,"title":5,"authors":6,"body":9,"date":277,"description":278,"extension":279,"ghostId":280,"image":281,"imageAlt":282,"imageCaption":282,"imageVideo":282,"meta":283,"navigation":284,"path":285,"readingTime":286,"seo":287,"stem":288,"tags":289,"toc":284,"updated":292,"__hash__":293},"blog\u002Fblog\u002Ftlv2.md","Transitland Version 2",[7,8],"drew","ian",{"type":10,"value":11,"toc":266},"minimark",[12,31,42,50,55,62,65,78,82,85,98,101,104,108,116,119,127,131,134,142,150,157,160,164,167,175,179,182,193,208,214,227,231,234],[13,14,17],"il-callout",{"color":15,"emoji":16},"blue","💡",[18,19,20,24,25,30],"p",{},[21,22,23],"strong",{},"March 4, 2021",": Here's a more recent blog post ",[26,27,29],"a",{"href":28},"\u002Fblog\u002Ftransitland-v2-search\u002F","demonstrating Transitland v2's new ability to search across transit operators, feeds, and routes",".",[13,32,33],{"color":15,"emoji":16},[18,34,35,24,38,30],{},[21,36,37],{},"February 25, 2021",[26,39,41],{"href":40},"\u002Fblog\u002Ftransitland-v2-vector-map-tiles\u002F","demonstrating Transitland v2's new global transit map and vector tiles",[18,43,44,45,49],{},"It's been a quiet year on this blog, and we're overdue to share all the work that's been going on behind the scenes since the ",[26,46,48],{"href":47},"\u002Fblog\u002Ftransitland-continues\u002F","last post",". 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.",[51,52,54],"h2",{"id":53},"tlv2-functionality-and-goals","Tlv2 Functionality and Goals",[18,56,57,61],{},[58,59,60],"em",{},"Tlv2"," (as we've come to call this new version) provides continuity on the most used parts of the Transitland platform. Tlv2 will still provide a canonical service at transit.land that includes a Feed Registry of open GTFS data feeds from around the world, a queryable API, and a range of user interfaces. Tlv2, like Tlv1, will be powered by open-source components. Tlv2's API will continue to be accessible without charge, and most of the Tlv1 API will continue to be available during the transition. (As before, we will enforce rate limits to ensure no one user hogs too many server resources; more on how rate limits will change below.)",[18,63,64],{},"What we are changing in Tlv2 is in support of three goals:",[66,67,68,72,75],"ul",{},[69,70,71],"li",{},"Higher Performance",[69,73,74],{},"More Modular Architecture",[69,76,77],{},"Distributed Deployments",[51,79,81],{"id":80},"goal-1-higher-performance","Goal #1: Higher Performance",[18,83,84],{},"Tlv1 successfully parses and imports GTFS feeds from thousands of transit agencies. However its \"FeedEater\" component slows down or halts on a handful of the very larger GTFS feeds — typically single feeds that cover entire countries. This has always been a constraint on Tlv1.",[18,86,87,88,92,93,97],{},"Interline's new ",[89,90,91],"code",{},"transitland-lib"," (tlib) library solves this problem. Transitland-lib is a new transit data library written in the ",[26,94,96],{"href":95},"https:\u002F\u002Fgolang.org\u002F","Go programming language",", which provides finer-grained control of memory usage, as well as much easier patterns for concurrency and parallelization of complex tasks. Transitland-lib replaces replaces FeedEater, and will be used for feed validation, pre-processing, and importing data into the Tlv2 database. Transitland-lib is efficient enough to handle the largest feeds in a small memory footprint, and is fast enough to encourage interactive use; imports that took hours with FeedEater are completed in minutes.",[18,99,100],{},"Transitland-lib began as an experiment by Ian Rees over the last winter holidays, and it now complete enough to power multiple Interline projects, from the San Francisco Bay Area Regional GTFS Feed (which merges ~30 feeds into one) to a transit-to-routing-engine pipeline that Interline built for another client (which covers transit service for an entire country!). We look forward to releasing transitland-lib under an open-source license shortly.",[18,102,103],{},"Transitland's most demanding API users have also hit performance limitations over the years. As part of Tlv2, we'll be providing bulk data dumps that give users another option. Use the Tlv2 API to explore data or power a small web app; use Tlv2 data extracts to power a large analysis, a giant web app, or a country-wide routing engine.",[51,105,107],{"id":106},"goal-2-more-modular-architecture","Goal #2: More Modular Architecture",[18,109,110,111,115],{},"Tlv1 has succeeded in part due to its \"monolith\" architecture. FeedEater, the API, and administrative operations all live within the same ",[26,112,114],{"href":113},"https:\u002F\u002Fwww.transit.land\u002Fdocumentation\u002Fdatastore\u002F","Transitland Datastore"," codebase. This has allowed for efficient reuse of data models, helpers, and test code. The single Datastore codebase is also straightforward to deploy and configure for the canonical transit.land site. The Datastore codebase can be reused — some have in fact redeployed it for their own regional or internal GTFS management needs—but customizing and redeploying the Datastore is not straightforward.",[18,117,118],{},"For Tlv2, we're breaking the Transitland Datastore into modular components. Some components will be in Go (data processing), some will remain in Ruby (general back-end) and JavaScript (user interfaces). The canonical transit.land deployment will continue to use all. Other deployments by Interline, our partners, or open-source users may only use a subset. This more modular architecture will also allow deployments that connect Tlv2 components to internal data pipelines, routing engines, and other tools that may not be relevant to the canonical transit.land deployment.",[18,120,121,122,126],{},"While the software components of Tlv2 will be more modular, they will still be glued together using the data schemes developed for Transitland, including ",[26,123,125],{"href":124},"https:\u002F\u002Fwww.transit.land\u002Fdocumentation\u002Fconcepts\u002Fonestop-id-scheme","Onestop IDs"," and a common feed format spec (described below). Additionally, we will be sharing our database schema in versions appropriate for PostgreSQL and SQLite to help simplify additional application development, including outside of the canonical transit.land.",[51,128,130],{"id":129},"goal-3-distributed-deployments","Goal #3: Distributed Deployments",[18,132,133],{},"The Feed Registry at transit.land will continue to be our canonical list of GTFS feeds. However, some deployments of Tlv2 components may want to use just a subset of the Feed Registry or a private list of feeds. We also want to open up the canonical Feed Registry for more collaborative tending, beyond just staff from Interline and Trillium Transit.",[18,135,136,137,141],{},"The second of the two experiments that has led to Tlv2 is called the ",[26,138,140],{"href":139},"https:\u002F\u002Fgithub.com\u002Ftransitland\u002Fdistributed-mobility-feed-registry","Distributed Mobility Feed Registry",". DMFR (for short) is a standard way of representing a list of GTFS feeds as one or more JSON files. It also currently supports GTFS-RT, and we expect it to extend to GBFS (bike rental) and MDS (e-scooter rental) in the future.",[18,143,144,145,149],{},"(Some history: This experiment actually started way back in the early tests of Transitland, before the fully built out Tlv1 monolith. It's still ",[26,146,148],{"href":147},"https:\u002F\u002Fgithub.com\u002Ftransitland\u002Ftransitland-datastore","archived"," on GitHub. Now we've come full circle to revisit and build out this approach.)",[18,151,152,153,156],{},"Soon the ",[89,154,155],{},"transitland\u002Fdistributed-mobility-feed-registry"," repository on GitHub will become the source of truth for the Transitland Feed Registry of public open data feeds. We'll accept pull requests against the JSON files to add or edit feeds. This should substantially lower the burden for outside contributors to contribute new feeds and help manage existing records. However, this will be just be one repository of DMFR files. In effect we're blowing up the single Transitland Feed Registry and inviting the creation of many.",[18,158,159],{},"Transitland-lib can manage a datastore using one or more DMFR files, meaning that the canonical transit.land, distributed instances of Tlv2, and temporary interactive sessions with transitland-lib on the command line can all share the same representation for mobility data feeds. At Interline, we've gone one step further and also use DMFR files to configure some of our routing engines and any other workflow that takes two or more mobility data feeds as input. We welcome other consumers or transformers of GTFS, GTFS-RT, and related data to try a DMFR file for their own needs.",[51,161,163],{"id":162},"tlv2-architecture-diagram","Tlv2 Architecture Diagram",[18,165,166],{},"Now that we've introduced and discussed the new components of Tlv2, here's a diagram of how they connect:",[168,169],"il-figure",{"alt":170,"img-height":171,"img-width":172,"src":173,"width":174},"Tlv2 architecture diagram","942","768","\u002Fcontent\u002Ftransit-land\u002Ftlv2\u002Ftlv2-architecture-diagram.png","wide",[51,176,178],{"id":177},"gradual-deprecation-of-tlv1","Gradual Deprecation of Tlv1",[18,180,181],{},"Tlv1 requires a fair amount of attention and resources to maintain. While developing Tlv2, we've already had to split our attention. As we shift our focus to deploying and supporting Tlv2, we'll be gradually deprecating Tlv1. Don't worry — it won't be too quickly.",[18,183,184,187,188,192],{},[21,185,186],{},"Step 1: Tlv2 API Preview"," The initial release of Tlv2 will include a preview of a new ",[26,189,191],{"href":190},"https:\u002F\u002Fgraphql.org\u002F","GraphQL"," API that provides flexible, structured access to transit data. All new data will be available through this API from the start. API access will require a key. Sign-up will be free. We will institute tight rate limits at first and increase them over time, as we better understand the type and complexity of queries that users run.",[18,194,195,198,199,203,204,207],{},[21,196,197],{},"Step 2: Deprecate Tlv1 Schedule API"," Immediately upon Tlv2 release, we will stop importing new ",[26,200,202],{"href":201},"https:\u002F\u002Fwww.transit.land\u002Fdocumentation\u002Fdatastore\u002Fschedules.html","schedule data"," into Tlv1. The ",[89,205,206],{},"ScheduleStopPair"," data model is the most expensive part of Tlv1 to run and maintain. We'll first stop imports, keeping the API available against the last imported version. We'll share tutorials on how to switch to the Tlv2 GraphQL API to access schedules. Then, after sufficient notice, we'll empty old Tlv1 schedule data and remove that API endpoint.",[18,209,210,213],{},[21,211,212],{},"Step 3: Other Tlv1 Entity API Endpoints"," While the Tlv2 GraphQL API will make a number of complex queries much simpler than with the current Tlv1 API, it may take a while for us to make all Tlv1 query options available in the Tlv2 API. During this time, we'll try to continue to power the Tlv1 APIs (with the exception of the schedules endpoint). We'll recommend that you build any new applications on the Tlv2 API, in case we do have to announce any specific incompatibilities during the Tlv1-to-Tlv2 API transition.",[18,215,216,217,221,222,226],{},"We'll post updates to this site. Or watch ",[26,218,220],{"href":219},"https:\u002F\u002Ftwitter.com\u002Ftransitland","@transitland"," and ",[26,223,225],{"href":224},"https:\u002F\u002Ftwitter.com\u002Finterline_io","@interline_io"," for updates on Twitter.",[51,228,230],{"id":229},"how-you-can-help","How You Can Help",[18,232,233],{},"Here are ways you can help with the rollout of Tlv2:",[66,235,236,243,251,259],{},[69,237,238,239,30],{},"Provide your input on Tlv2 by taking our ",[26,240,242],{"href":241},"https:\u002F\u002Fdocs.google.com\u002Fforms\u002Fd\u002Fe\u002F1FAIpQLSdmhW28zcP1kBMBkmelAt7OQGqKjRcoILjsbZvGXLsGfmFNGw\u002Fviewform","survey and signing up for the beta tester list",[69,244,245,246,250],{},"Comment on the ",[26,247,249],{"href":248},"https:\u002F\u002Ffunding.communitybridge.org\u002Fprojects\u002Ftransitland","DMFR GitHub repository",". Contribute edits once we migrate over the Feed Registry to DMFR files.",[69,252,253,254,258],{},"If you work for a GTFS producing transit operator or mobility provider, ",[26,255,257],{"href":256},"mailto:info@interline.io","contact Interline"," to learn more about \"Tlv2 on premise\" and regional GTFS feeds. It's consulting projects like this that help us serve both mobility providers and further the development of transitland-lib.",[69,260,261,262,265],{},"Contribute financially to the upkeep and growth of Tlv2 through the Linux Foundation's ",[26,263,264],{"href":248},"CommunityBridge donation page for Transitland",". These contributions go directly toward upkeep of the canonical transit.land.",{"title":267,"searchDepth":268,"depth":268,"links":269},"",2,[270,271,272,273,274,275,276],{"id":53,"depth":268,"text":54},{"id":80,"depth":268,"text":81},{"id":106,"depth":268,"text":107},{"id":129,"depth":268,"text":130},{"id":162,"depth":268,"text":163},{"id":177,"depth":268,"text":178},{"id":229,"depth":268,"text":230},"2019-01-08T00:00:00.000-08:00","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.","md","67255876b62841000136ee13","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftlv2-architecture-diagram.png",null,{},true,"\u002Fblog\u002Ftlv2",6,{"title":5,"description":278},"blog\u002Ftlv2",[290,291],"transitland","gtfs","2024-11-05T13:50:59.000-08:00","ty-XGMHIq9gJr_RyZWxUb-Yf2zX71GwzGnOLIS8rJKQ",[295,302,309,317,326,334,341,348,356,363,370,377,385,391,398,406,414,421,428,434,441,449,456,462,469,476,482,489,498,504,511,513,519,526,533,540],{"path":296,"title":297,"description":298,"date":299,"tags":300,"image":301,"imageAlt":282},"\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",[290],"\u002Fcontent\u002Fimages\u002Funsplash\u002Fphoto-1746859782086-eafe092caa85.jpg",{"path":303,"title":304,"description":305,"date":306,"tags":307,"image":308,"imageAlt":282},"\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",[290,291],"\u002Fcontent\u002Fimages\u002Funsplash\u002Fphoto-1617727553230-35c143f84010.jpg",{"path":310,"title":311,"description":312,"date":313,"tags":314,"image":315,"imageAlt":316},"\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",[291,290],"\u002Fcontent\u002Fimages\u002Funsplash\u002Fphoto-1531376653594-e9bcf0f0c65b.jpg","photograph of overlapping zippers (as a metaphor for different zip archives)",{"path":318,"title":319,"description":320,"date":321,"tags":322,"image":324,"imageAlt":325},"\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",[323],"events","\u002Fcontent\u002Fimages\u002Funsplash\u002Fphoto-1699938648771-00dd74c6ce17.jpg","elevated train in Vancouver with trees, buildings, and mountains in background",{"path":327,"title":328,"description":329,"date":330,"tags":331,"image":332,"imageAlt":333},"\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",[291,290],"\u002Fcontent\u002Fimages\u002F2025\u002F07\u002Fimage-2.png","Viewing a GTFS Realtime feed as human-readable JSON using the Transitland website",{"path":335,"title":336,"description":337,"date":338,"tags":339,"image":340,"imageAlt":282},"\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",[291,290],"\u002Fcontent\u002Fimages\u002F2025\u002F03\u002FCleanShot-2025-03-26-at-13.52.03-1.jpg",{"path":342,"title":343,"description":344,"date":345,"tags":346,"image":347,"imageAlt":282},"\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",[290],"\u002Fcontent\u002Fimages\u002F2025\u002F02\u002FCleanShot-2025-02-25-at-13.37.14.jpg",{"path":349,"title":350,"description":351,"date":352,"tags":353,"image":354,"imageAlt":355},"\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",[290],"\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":357,"title":358,"description":359,"date":360,"tags":361,"image":362,"imageAlt":282},"\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",[323],"\u002Fcontent\u002Fimages\u002F2025\u002F01\u002Fblue-slider-2025-TRB-annual-meeting-1260x468px.jpg",{"path":364,"title":365,"description":366,"date":367,"tags":368,"image":369,"imageAlt":282},"\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",[291],"\u002Fcontent\u002Fimages\u002F2024\u002F12\u002FCleanShot-2024-12-24-at-14.58.25@2x.png",{"path":371,"title":372,"description":373,"date":374,"tags":375,"image":376,"imageAlt":282},"\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",[290],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Funnamed--1--1-1.png",{"path":378,"title":379,"description":380,"date":381,"tags":382,"image":383,"imageAlt":384},"\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",[290],"\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":386,"title":387,"description":388,"date":389,"tags":390,"image":282,"imageAlt":282},"\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",[290],{"path":392,"title":393,"description":394,"date":395,"tags":396,"image":397,"imageAlt":282},"\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",[291],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fbil-geographic-service-coverage-area.png",{"path":399,"title":400,"description":401,"date":402,"tags":403,"image":405,"imageAlt":282},"\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",[404],"about-interline","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fsocial_style_3_rss-512-1.png",{"path":407,"title":408,"description":409,"date":410,"tags":411,"image":413,"imageAlt":282},"\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",[412,291],"511-sf-bay-regional-feed","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fios-directions-with-fares-2.png",{"path":415,"title":416,"description":417,"date":418,"tags":419,"image":420,"imageAlt":282},"\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",[291],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fus-ntd-federal-register.png",{"path":422,"title":423,"description":424,"date":425,"tags":426,"image":427,"imageAlt":282},"\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",[291,412],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftrip-update-selection.png",{"path":429,"title":430,"description":431,"date":432,"tags":433,"image":282,"imageAlt":282},"\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",[290],{"path":435,"title":436,"description":437,"date":438,"tags":439,"image":440,"imageAlt":282},"\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",[290],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fglobal-transit-map-europe.png",{"path":442,"title":443,"description":444,"date":445,"tags":446,"image":447,"imageAlt":448},"\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",[404],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fmobility-data-interoperability-principles-full.png","Mobility Data Interoperability Principles overview diagram",{"path":450,"title":451,"description":452,"date":453,"tags":454,"image":455,"imageAlt":282},"\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",[412],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Flist-of-rt-enabled-agencies.png",{"path":457,"title":458,"description":459,"date":460,"tags":461,"image":282,"imageAlt":282},"\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",[290],{"path":463,"title":464,"description":465,"date":466,"tags":467,"image":468,"imageAlt":282},"\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",[290],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftlv2-map-animation.jpg",{"path":470,"title":471,"description":472,"date":473,"tags":474,"image":475,"imageAlt":282},"\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",[291],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftrb-t-93-report-cover.png",{"path":477,"title":478,"description":267,"date":479,"tags":480,"image":481,"imageAlt":282},"\u002Fblog\u002Fmtc-regional-gtfs-feed-additions","SF Bay Area's Regional GTFS Feed Expanded","2020-08-10T00:00:00.000-07:00",[291,412],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fheadway-july-only.png",{"path":483,"title":484,"description":485,"date":486,"tags":487,"image":488,"imageAlt":282},"\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",[291,412],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fmtc-regional-feed-all-routes.png",{"path":490,"title":491,"description":492,"date":493,"tags":494,"image":497,"imageAlt":282},"\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",[495,496],"geojsonl","openstreetmap","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fdownload-geojsonl-extract.png",{"path":499,"title":500,"description":501,"date":502,"tags":503,"image":282,"imageAlt":282},"\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",[291,290],{"path":505,"title":506,"description":507,"date":508,"tags":509,"image":510,"imageAlt":282},"\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",[290,412],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fstir-banner.png",{"path":285,"title":5,"description":278,"date":277,"tags":512,"image":281,"imageAlt":282},[290,291],{"path":514,"title":515,"description":516,"date":277,"tags":517,"image":518,"imageAlt":282},"\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.",[290],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftransitland_logo.png",{"path":520,"title":521,"description":522,"date":523,"tags":524,"image":525,"imageAlt":282},"\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",[496,290],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fxyz-tutorial-1-animation.jpg",{"path":527,"title":528,"description":529,"date":530,"tags":531,"image":532,"imageAlt":282},"\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",[496,495],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fpreview.png",{"path":534,"title":535,"description":536,"date":537,"tags":538,"image":539,"imageAlt":282},"\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",[323],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftable-of-contents.png",{"path":541,"title":542,"description":543,"date":544,"tags":545,"image":546,"imageAlt":282},"\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",[496],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fargo-workflow-screenshot.png",1792086309566]