[{"data":1,"prerenderedAt":525},["ShallowReactive",2],{"post:\u002Fblog\u002Fus-national-transit-database-releases-data-and-requests-more-feedback-2":3,"blog:siblings":272},{"id":4,"title":5,"authors":6,"body":8,"date":255,"description":256,"extension":257,"ghostId":258,"image":259,"imageAlt":260,"imageCaption":260,"imageVideo":260,"meta":261,"navigation":262,"path":263,"readingTime":264,"seo":265,"stem":266,"tags":267,"toc":269,"updated":270,"__hash__":271},"blog\u002Fblog\u002Fus-national-transit-database-releases-data-and-requests-more-feedback-2.md","US National Transit Database releases data and requests more feedback",[7],"interline",{"type":9,"value":10},"minimark",[11,29,38,54,67,74,82,92,105,108,121,124,135,148,151,172,175,206,212,215,218,228,240,252],[12,13,15],"il-callout",{"color":14},"yellow",[16,17,18,22,23,28],"p",{},[19,20,21],"strong",{},"January 3, 2025",": FTA has extended the comment period to January 29 regarding ",[24,25,27],"a",{"href":26},"https:\u002F\u002Fwww.regulations.gov\u002Fdocument\u002FFTA-2024-0013-0001","National Transit Database: Proposed Reporting Changes and Clarifications for Report Years 2025 and 2026",".",[12,30,33],{"color":31,"emoji":32},"blue","📧",[16,34,35,36,28],{},"We've submitted the following public comment to the Federal Transit Administration regarding ",[24,37,27],{"href":26},[12,39,41],{"color":31,"emoji":40},"📖",[16,42,43,44,48,49,53],{},"For background, see earlier posts on the Interline blog: \"",[24,45,47],{"href":46},"\u002Fblog\u002Fus-ntd-reporting-gtfs-adopted\u002F","US Federal Transit Administration finalizes plan to collect GTFS URLs in US National Transit Database","\" (2023) and \"",[24,50,52],{"href":51},"\u002Fblog\u002Fus-ntd-reporting-gtfs\u002F","US National Transit Database to collect GTFS URLs","\" (2022).",[16,55,56,57,61,62,66],{},"Interline Technologies is the maintainer of the ",[24,58,60],{"href":59},"https:\u002F\u002Fwww.transit.land\u002F","Transitland open data platform",". Transitland aggregates approximately 1,000 static GTFS feeds from across the United States (as well as real-time feeds, plus feeds from international sources). To power the platform's APIs, our staff and external contributors maintain the ",[24,63,65],{"href":64},"https:\u002F\u002Fgithub.com\u002Ftransitland\u002Ftransitland-atlas","Transitland Atlas feed registry repository",", which is publicly hosted on GitHub under a permissive license. This feed registry maintains lists of public GTFS feed URLs in addition to associated metadata (including US NTD IDs). The following comments regarding the proposed NTD reporting changes are based on our experience creating and operating these open-data systems since 2015.",[68,69,71],"h2",{"id":70},"re-section-b-additional-data-within-publicly-hosted-general-transit-feed-specification-gtfs-datasets",[19,72,73],{},"Re Section B. Additional Data Within Publicly Hosted General Transit Feed Specification (GTFS) Datasets",[16,75,76,77,81],{},"Thank you to agencies and NTD for beginning to collect GTFS feeds from reporting agencies. The ",[24,78,80],{"href":79},"https:\u002F\u002Fwww.transit.dot.gov\u002Fntd\u002Fdata-product\u002F2023-annual-database-general-transit-feed-specification-gtfs-weblinks","2023 Annual Database General Transit Feed Specification (GTFS) Weblinks dataset"," is a useful public release.",[12,83,85],{"color":31,"emoji":84},"🙋",[16,86,87,88,28],{},"Transitland Atlas maintainers and contributors are reviewing the NTD weblinks dataset to look for new feed sources to add to the Transitland Atlas, as well as out-of-date references to update in Transitland Atlas. To help, see the ",[24,89,91],{"href":90},"https:\u002F\u002Fgithub.com\u002Ftransitland\u002Ftransitland-atlas\u002Ftree\u002Fmain\u002Fscripts\u002Fntd-gtfs-weblinks","ntd-gtfs-weblinks projects subdirectory",[12,93,95],{"color":31,"emoji":94},"🚌",[16,96,97,100,101],{},[19,98,99],{},"For transit agencies currently unable to host their GTFS feed at a public URL",": We invite you to email a copy of your latest feed to our team at ",[24,102,104],{"href":103},"mailto:hello@transit.land","hello@transit.land",[16,106,107],{},"To further increase the use of this weblinks dataset in future years, please guide as many agencies as possible to host their GTFS feeds at URLs that are public and stable. That is:",[109,110,111,115,118],"ul",{},[112,113,114],"li",{},"URLs - hosting their GTFS feed on an agency-controlled website (instead of submitting feed version as archives via email)",[112,116,117],{},"public - a URL that third-parties can download from (rather than a private submission to NTD)",[112,119,120],{},"stable - a URL that remains the same, while the GTFS feed archive itself is changed as the agency releases new schedules\u002Fversions (i.e., no dates in the file name)",[16,122,123],{},"Finally, please keep in mind that it's best for agencies to be reporting to NTD the exact same GTFS feed versions that they share with third-party navigation apps and open-data aggregation platforms. This ensures that all data consumers are working from similar information, and makes it easier for data producers to focus their efforts. This is even more relevant for agencies that produce GTFS Realtime feeds as well (which need to match certain identifiers within associated static feeds). Our feedback regarding adding NTD IDs is also based on this goal of preventing agencies from having to produce separate feed files for NTD reporting purposes than they already produce for trip-planning and operational purposes.",[68,125,127],{"id":126},"re-align-agency_id-and-ntd-id-within-gtfs-file",[19,128,129,130,134],{},"Re Align ",[131,132,133],"code",{},"agency_id"," and NTD ID Within GTFS File",[16,136,137,138,142,143,147],{},"We support the proposed goal of adding NTD IDs to GTFS feeds. NTD IDs are a useful \"crosswalk\" between the rider-facing data in a GTFS feed and the operational\u002Fplanning\u002Ffinancial datasets in the NTD. However, we recommend that the means of adding NTD IDs to GTFS feeds be carefully considered. Interline strongly agrees with related feedback submitted from other commenters, including ",[24,139,141],{"href":140},"https:\u002F\u002Fwww.regulations.gov\u002Fcomment\u002FFTA-2024-0013-0003","MBTA"," and the ",[24,144,146],{"href":145},"https:\u002F\u002Fwww.regulations.gov\u002Fcomment\u002FFTA-2024-0013-0006","MobilityData"," non-profit (of which Interline is also a member).",[16,149,150],{},"We recommend:",[152,153,154,160,166],"ol",{},[112,155,156,159],{},[19,157,158],{},"NTD IDs should be added to GTFS feeds in a flexible manner that can map on to an entire feed, an agency within a feed, or a subset of routes within a feed."," This is necessary because rider-facing \"brand names\" of transit agencies do not always line up 1-to-1 with NTD reporting IDs, nor do NTD reporting IDs necessarily line up 1-to-1 with the internal means of organizing an agencies' data systems that produce records in agencies.txt",[112,161,162,165],{},[19,163,164],{},"NTD IDs be added to GTFS feeds in a way that does not conflict with existing data-producing systems."," This is toward the goal of agencies reporting their existing GTFS feeds to NTD, rather than creating \"one off\" feed versions that they customize and submit once a year to NTD. Based on our experience working with a wide range of transit agencies, we recommend that data-producers have the choice to either add an entirely new file or add columns to existing files. For some agencies, it may be simpler to add a single hard-coded file to their feed, while for other agencies, it may be simpler to add an extra custom column to the relevant files in their feed. ",[112,167,168,171],{},[19,169,170],{},"NTD IDs be added to GTFS feeds in a way that does not conflict with existing data-consuming systems."," Consumers can choose to accept or ignore new columns and\u002For new files in GTFS feeds. This makes it simpler for them to \"opt in\" rather than to have to adapt to a change in the meaning of agency_id.",[16,173,174],{},"Our specific recommendation for your consideration:",[109,176,177,180,187],{},[112,178,179],{},"Give reporters two approaches for adding NTD IDs to their feeds.",[112,181,182,183,186],{},"The first approach will be to add a file named ",[131,184,185],{},"us-ntd-ids.txt"," (or similar) to their feeds. This would be a CSV file in which each row maps an NTD ID to a chosen entity (e.g., an agency or a route). For a simple situation in which there is one NTD ID for a single agent in a feed, this file would only have one row (after the header row); for a complex situation, there may be multiple rows defining how different agencies and\u002For routes are mapped to different NTD IDs.",[112,188,189,190,193,194,197,198,201,202,205],{},"The second approach will be to add a ",[131,191,192],{},"us_ntd_id"," column (or similar) to existing ",[131,195,196],{},"feed_info.txt",", ",[131,199,200],{},"agencies.txt",", and\u002For ",[131,203,204],{},"routes.txt"," files. Data producers could add this column to just the files in which they want to list one or more NTD IDs.",[16,207,208,209,211],{},"Our overall recommendation is to provide flexibility to data-producers in where and how they add US NTD IDs. This will lower the uncertainty of changing existing fields (such as the meaning of the ",[131,210,133],{},"). This will also decrease the technical trade-offs for agencies with complicated existing IT systems, which may limit how they can change or customize their GTFS feeds.",[16,213,214],{},"This proposal does slightly increase the burden of data-consumers to extract the relevant NTD IDs from GTFS feeds and figure out how to apply them to feed contents. We believe that is a reasonable burden for data-consumers to take on. Transitland already does similar operations across the thousands of GTFS feeds it consumes. In exchange, the benefit of this approach is that it encourages agencies to fit NTD IDs into their production systems (rather than producing one-off feed versions just for NTD reporting).",[16,216,217],{},"Finally, we recommend reviewing uptake of these two approaches by agencies after a year or two. Perhaps one approach will be fine and the requirement can be refined in the future. Still, we recommend beginning with reporting agencies having more initial flexibility.",[68,219,221],{"id":220},"re-shapestxt-file-geospatial-drawing-of-routes-as-part-of-gtfs-submission",[19,222,223,224,227],{},"Re ",[131,225,226],{},"shapes.txt"," File (Geospatial Drawing of Routes) as Part of GTFS Submission",[16,229,230,231,233,234,236,237,239],{},"We agree that recommending agencies add ",[131,232,226],{}," files for all routes\u002Ftrips will be beneficial to data consumers, especially trip-planners, GIS analyses, and visualizations. However, in our experience, the quality of ",[131,235,226],{}," geometries can vary wildly. Imprecise and inaccurate shapes can often be worse than no shapes. Data consumers such as Transitland and trip planning apps already have to run automated checks to see whether our systems even want to ingest ",[131,238,226],{}," records for a given trip or to instead ignore them.",[16,241,242,243,247,248],{},"The ",[24,244,246],{"href":245},"https:\u002F\u002Fgtfs.org\u002Fdocumentation\u002Fschedule\u002Fexamples\u002Fshapes\u002F","shapes guidance webpage"," shared by MobilityData is worth sharing with agencies. It's also worth sharing with agencies and reiterating the value of the ",[24,249,251],{"href":250},"https:\u002F\u002Fgtfs.org\u002Fdocumentation\u002Fschedule\u002Fschedule-best-practices\u002F","GTFS \"best practices.\"",[16,253,254],{},"Thank you for accepting this feedback.","2024-12-24T14:54:17.000-08:00","Our recommendations to the US Federal Transit Administration regarding National Transit Database: Proposed Reporting Changes and Clarifications for Report Years 2025 and 2026. ","md","676995f6ea4ece000174601e","\u002Fcontent\u002Fimages\u002F2024\u002F12\u002FCleanShot-2024-12-24-at-14.58.25@2x.png",null,{},true,"\u002Fblog\u002Fus-national-transit-database-releases-data-and-requests-more-feedback-2",5,{"title":5,"description":256},"blog\u002Fus-national-transit-database-releases-data-and-requests-more-feedback-2",[268],"gtfs",false,"2025-01-06T12:02:03.000-08:00","ekGvkj_xkoExwY9pHrXPTTpErRjn553OzYdu_Cqxg7A",[273,281,288,296,305,313,320,327,335,342,344,351,359,365,371,379,387,393,400,406,413,421,428,434,441,448,455,462,471,477,484,491,497,504,511,518],{"path":274,"title":275,"description":276,"date":277,"tags":278,"image":280,"imageAlt":260},"\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",[279],"transitland","\u002Fcontent\u002Fimages\u002Funsplash\u002Fphoto-1746859782086-eafe092caa85.jpg",{"path":282,"title":283,"description":284,"date":285,"tags":286,"image":287,"imageAlt":260},"\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",[279,268],"\u002Fcontent\u002Fimages\u002Funsplash\u002Fphoto-1617727553230-35c143f84010.jpg",{"path":289,"title":290,"description":291,"date":292,"tags":293,"image":294,"imageAlt":295},"\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",[268,279],"\u002Fcontent\u002Fimages\u002Funsplash\u002Fphoto-1531376653594-e9bcf0f0c65b.jpg","photograph of overlapping zippers (as a metaphor for different zip archives)",{"path":297,"title":298,"description":299,"date":300,"tags":301,"image":303,"imageAlt":304},"\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",[302],"events","\u002Fcontent\u002Fimages\u002Funsplash\u002Fphoto-1699938648771-00dd74c6ce17.jpg","elevated train in Vancouver with trees, buildings, and mountains in background",{"path":306,"title":307,"description":308,"date":309,"tags":310,"image":311,"imageAlt":312},"\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",[268,279],"\u002Fcontent\u002Fimages\u002F2025\u002F07\u002Fimage-2.png","Viewing a GTFS Realtime feed as human-readable JSON using the Transitland website",{"path":314,"title":315,"description":316,"date":317,"tags":318,"image":319,"imageAlt":260},"\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",[268,279],"\u002Fcontent\u002Fimages\u002F2025\u002F03\u002FCleanShot-2025-03-26-at-13.52.03-1.jpg",{"path":321,"title":322,"description":323,"date":324,"tags":325,"image":326,"imageAlt":260},"\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",[279],"\u002Fcontent\u002Fimages\u002F2025\u002F02\u002FCleanShot-2025-02-25-at-13.37.14.jpg",{"path":328,"title":329,"description":330,"date":331,"tags":332,"image":333,"imageAlt":334},"\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",[279],"\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":336,"title":337,"description":338,"date":339,"tags":340,"image":341,"imageAlt":260},"\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",[302],"\u002Fcontent\u002Fimages\u002F2025\u002F01\u002Fblue-slider-2025-TRB-annual-meeting-1260x468px.jpg",{"path":263,"title":5,"description":256,"date":255,"tags":343,"image":259,"imageAlt":260},[268],{"path":345,"title":346,"description":347,"date":348,"tags":349,"image":350,"imageAlt":260},"\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",[279],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Funnamed--1--1-1.png",{"path":352,"title":353,"description":354,"date":355,"tags":356,"image":357,"imageAlt":358},"\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",[279],"\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":360,"title":361,"description":362,"date":363,"tags":364,"image":260,"imageAlt":260},"\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",[279],{"path":366,"title":47,"description":367,"date":368,"tags":369,"image":370,"imageAlt":260},"\u002Fblog\u002Fus-ntd-reporting-gtfs-adopted","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",[268],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fbil-geographic-service-coverage-area.png",{"path":372,"title":373,"description":374,"date":375,"tags":376,"image":378,"imageAlt":260},"\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",[377],"about-interline","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fsocial_style_3_rss-512-1.png",{"path":380,"title":381,"description":382,"date":383,"tags":384,"image":386,"imageAlt":260},"\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",[385,268],"511-sf-bay-regional-feed","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fios-directions-with-fares-2.png",{"path":388,"title":52,"description":389,"date":390,"tags":391,"image":392,"imageAlt":260},"\u002Fblog\u002Fus-ntd-reporting-gtfs","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",[268],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fus-ntd-federal-register.png",{"path":394,"title":395,"description":396,"date":397,"tags":398,"image":399,"imageAlt":260},"\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",[268,385],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftrip-update-selection.png",{"path":401,"title":402,"description":403,"date":404,"tags":405,"image":260,"imageAlt":260},"\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",[279],{"path":407,"title":408,"description":409,"date":410,"tags":411,"image":412,"imageAlt":260},"\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",[279],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fglobal-transit-map-europe.png",{"path":414,"title":415,"description":416,"date":417,"tags":418,"image":419,"imageAlt":420},"\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",[377],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fmobility-data-interoperability-principles-full.png","Mobility Data Interoperability Principles overview diagram",{"path":422,"title":423,"description":424,"date":425,"tags":426,"image":427,"imageAlt":260},"\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",[385],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Flist-of-rt-enabled-agencies.png",{"path":429,"title":430,"description":431,"date":432,"tags":433,"image":260,"imageAlt":260},"\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",[279],{"path":435,"title":436,"description":437,"date":438,"tags":439,"image":440,"imageAlt":260},"\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",[279],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftlv2-map-animation.jpg",{"path":442,"title":443,"description":444,"date":445,"tags":446,"image":447,"imageAlt":260},"\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",[268],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftrb-t-93-report-cover.png",{"path":449,"title":450,"description":451,"date":452,"tags":453,"image":454,"imageAlt":260},"\u002Fblog\u002Fmtc-regional-gtfs-feed-additions","SF Bay Area's Regional GTFS Feed Expanded","","2020-08-10T00:00:00.000-07:00",[268,385],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fheadway-july-only.png",{"path":456,"title":457,"description":458,"date":459,"tags":460,"image":461,"imageAlt":260},"\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",[268,385],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fmtc-regional-feed-all-routes.png",{"path":463,"title":464,"description":465,"date":466,"tags":467,"image":470,"imageAlt":260},"\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",[468,469],"geojsonl","openstreetmap","\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fdownload-geojsonl-extract.png",{"path":472,"title":473,"description":474,"date":475,"tags":476,"image":260,"imageAlt":260},"\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",[268,279],{"path":478,"title":479,"description":480,"date":481,"tags":482,"image":483,"imageAlt":260},"\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",[279,385],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fstir-banner.png",{"path":485,"title":486,"description":487,"date":488,"tags":489,"image":490,"imageAlt":260},"\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",[279,268],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftlv2-architecture-diagram.png",{"path":492,"title":493,"description":494,"date":488,"tags":495,"image":496,"imageAlt":260},"\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.",[279],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftransitland_logo.png",{"path":498,"title":499,"description":500,"date":501,"tags":502,"image":503,"imageAlt":260},"\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",[469,279],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fxyz-tutorial-1-animation.jpg",{"path":505,"title":506,"description":507,"date":508,"tags":509,"image":510,"imageAlt":260},"\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",[469,468],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fpreview.png",{"path":512,"title":513,"description":514,"date":515,"tags":516,"image":517,"imageAlt":260},"\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",[302],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Ftable-of-contents.png",{"path":519,"title":520,"description":521,"date":522,"tags":523,"image":524,"imageAlt":260},"\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",[469],"\u002Fcontent\u002Fimages\u002F2024\u002F11\u002Fargo-workflow-screenshot.png",1792086309826]