Difference between revisions of "GTFS-flex"

From TransitWiki
Jump to: navigation, search
(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...")
 
(7 intermediate revisions by the same user not shown)
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. GTFS-flex remedies this, enabling trip planning software such as [[OpenTripPlanner]] to generate trips combining demand-responsive and fixed route service.
 +
 
 +
== Implementations ==
 +
 
 +
=== Tulare County, California ===
 +
[[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.]]
 +
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. It also reminds users about the requirement to call a day ahead to arrange demand-responsive service.
 +
 
 +
=== Vermont ===
 +
The Vermont Agency of Transportation was the first agency to implement GTFS-flex.<ref name="eval">Cordahi, G., Shaheen, S., Martin, E.. "
 +
MOD Sandbox Demonstrations Independent Evaluation (IE) Vermont Agency of Transportation (VTrans) OpenTripPlanner Evaluation Plan" June 1 2018. https://rosap.ntl.bts.gov/view/dot/36390/</ref> A demonstration project for the FTA's [[Portal:FTA Mobility on Demand Sandbox|Mobility on Demand Sandbox]], the GTFS-flex implementation in Vermont aims to provide a better trip planner than existing tools with the goal of increasing transit ridership statewide<ref name="eval" />.
 +
 
 +
== References ==
 +
<references/>

Revision as of 17:43, 20 November 2019



Transitwikilogo.png 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. GTFS-flex remedies this, enabling trip planning software such as OpenTripPlanner to generate trips combining demand-responsive and fixed route service.

Implementations

Tulare County, California

Tulare County: Google Maps trip planner showing no transit trips.
Tulare County: GTFS-flex based trip planner at ridetcat.org integrating demand-responsive and fixed route service.

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. It also reminds users about the requirement to call a day ahead to arrange demand-responsive service.

Vermont

The Vermont Agency of Transportation was the first agency to implement GTFS-flex.[1] A demonstration project for the FTA's Mobility on Demand Sandbox, the GTFS-flex implementation in Vermont aims to provide a better trip planner than existing tools with the goal of increasing transit ridership statewide[1].

References

  1. 1.0 1.1 Cordahi, G., Shaheen, S., Martin, E.. " MOD Sandbox Demonstrations Independent Evaluation (IE) Vermont Agency of Transportation (VTrans) OpenTripPlanner Evaluation Plan" June 1 2018. https://rosap.ntl.bts.gov/view/dot/36390/