GTFS-flex: Difference between revisions

From TransitWiki
Jump to navigation Jump to search
Jordanfraade (talk | contribs)
Created page with "<br> {| align="center" style="width: 60%; background-color: White; border: 1px solid #8a8; text-align: center; -moz-border-radius:8px; " cellspacing="0" cellpadding="0" | styl..."
 
Edasmalchi (talk | contribs)
m rephrase intro, add Tulare County example
Tag: visualeditor-switched
Line 1: Line 1:
[[Category: Technology]]
<br>
<br>
{| align="center" style="width: 60%; background-color: White; border: 1px solid #8a8; text-align: center; -moz-border-radius:8px; " cellspacing="0" cellpadding="0"
{| style="width: 60%; background-color: White; border: 1px solid #8a8; text-align: center; -moz-border-radius:8px; " cellspacing="0" cellpadding="0" align="center"
| style="font-size: 8pt; color: black; padding: 4pt; line-height: 1.25em;" |
| style="font-size: 8pt; color: black; padding: 4pt; line-height: 1.25em;" |
|[[File:Transitwikilogo.png|100px]]  
|[[File:Transitwikilogo.png|100px]]  
Line 14: Line 16:
<noinclude>
<noinclude>


GTFS-flex is a feed specification that allows agencies to apply typical public-transit metrics to demand-responsive or paratransit. As more agencies and transit passengers turn to GTFS for information on fixed route, scheduled service, the lack of accommodation for flexible route, demand-responsive service has become an issue for paratransit and non-urban areas. The Vermont Agency of Transportation is working on a GTFS-flex specification to bring rural transit and paratransit to apps like Google Maps.
== Introduction ==
 
GTFS-flex is an extension of the [[General Transit Feed Specification]] designed to enable trip planning for various types of demand-responsive or paratransit service. While GTFS-powered feeds offer convenient information on fixed route, scheduled service, they are not designed to show demand-responsive service, leaving users in certain areas with an incomplete picture of their options. The Vermont Agency of Transportation is working on a GTFS-flex specification to bring rural transit and paratransit to apps like Google Maps.
 
== Implementations ==
 
=== TCaT ===
 
TCaT (Tulare County Area Transit) uses a GTFS-flex powered trip planner to integrate their demand-responsive and fixed route service, providing convenience for users.
 
[[File:TCaTGoogleNoflex.png|700px|thumb|right|Tulare County: Google Maps trip planner showing no transit trips.]]
[[File:TCaT_GTFSflex.png|700px|thumb|right|Tulare County: GTFS-flex based trip planner at [https://ridetcat.org ridetcat.org] integrating demand-responsive and fixed route service.]]

Revision as of 00:04, 20 November 2019



This page is a "stub" - it needs more content.

You are invited to add your knowledge.

Please contribute!


Introduction

GTFS-flex is an extension of the General Transit Feed Specification designed to enable trip planning for various types of demand-responsive or paratransit service. While GTFS-powered feeds offer convenient information on fixed route, scheduled service, they are not designed to show demand-responsive service, leaving users in certain areas with an incomplete picture of their options. The Vermont Agency of Transportation is working on a GTFS-flex specification to bring rural transit and paratransit to apps like Google Maps.

Implementations

TCaT

TCaT (Tulare County Area Transit) uses a GTFS-flex powered trip planner to integrate their demand-responsive and fixed route service, providing convenience for users.

Error creating thumbnail: Unable to save thumbnail to destination
Tulare County: Google Maps trip planner showing no transit trips.
Error creating thumbnail: Unable to save thumbnail to destination
Tulare County: GTFS-flex based trip planner at ridetcat.org integrating demand-responsive and fixed route service.