Merge branch 'master' of https://github.com/tsherlockcraig/gtfs-flex

.github/workflows/stale.yml

@@ -0,0 +1,20 @@
+name: 'Close stale issues and PRs'
+on:
+  schedule:
+    - cron: '0 0 * * *'
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v4
+        with:
+          stale-issue-message: 'This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.'
+          close-issue-message: 'This issue has been closed due to inactivity. Issues can always be reopened after they have been closed.'
+          stale-pr-message: 'This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.'
+          close-pr-message: ' This pull request has been closed due to inactivity. Pull requests can always be reopened after they have been closed.'
+          stale-issue-label: 'stale'
+          stale-pr-label: 'stale'
+          days-before-stale: 365
+          days-before-close: 14
+          remove-stale-when-updated: true

README.md

@@ -1,43 +1,20 @@
-This directory contains the "Version 1" GTFS-flex specification and documentation. Data following the specification laid out in this repository can be found at http://vermont-gtfs.org, and is in use by the [GoVermont Flexible Trip Planner](http://plan.govermont.org). The trip planner utilizes the open source [OpenTripPlanner](http://www.opentripplanner.org/), and the code for the flexible transit routing is in the process of being merged into the coming OTP 1.4.
+Update: 
+- February 14, 2024. The most recent GTFS-Flex proposal can be found on [google/transit](https://github.com/google/transit/pull/433). **If the proposal passes, this repo will be out-of-date and removed.** Please consult [this proposal](https://github.com/google/transit/pull/433) for more details. 
+- November 25, 2020. The spec in this repository is now the most up-to-date version of GTFS-Flex. The code in this repo contains the official proposal for GTFS-Flex v2, a GTFS extension that covers all demand-responsive services for the purposes of discovery in trip planning. All features of this specification proposal are currently produced by [Trillium](https://trilliumtransit.com/) and consumed by [OpenTripPlanner version 2](https://www.opentripplanner.org/). DemandTrans and IBI group expect to produce data in this spec by early 2021.
 
-Drawing from the development of GTFS-flex data in Vermont, MobilityData has begun an effort to refine and propose changes to the GTFS specification following the objectives of the GTFS-flex project. This new work by MobilityData constitutes a "Version 2" of the spec, which is under development [here](http://bit.ly/gtfs-drt). At this time, discussion of the specification proposal should be centered on the text in that Google Document.
+"Version 1" of the GTFS-Flex specification is utilized by OTP 1.4. You can review the Version 1 specification by reviewing versions of this repository from before October 2020.
 
-### About GTFS-flex
+### About GTFS-Flex
 
-GTFS-flex is a proposed/prototype extension to the [General Transit Feed Specification](https://github.com/google/transit/tree/master/gtfs). GTFS-flex would add the capability to model various demand-responsive transportation (DRT) services to GTFS, which currently only models fixed-route public transportation. GTFS-flex is in a prototyping phase in which its capabilities to model transportation services are being tested and adapted. There is no software that currently consumes GTFS-flex data, though projects have been proposed.
+GTFS-Flex is a proposed extension to the [General Transit Feed Specification](http://gtfs.org/). GTFS-Flex adds the capability to model various demand-responsive transportation (DRT) services to GTFS, which currently only models fixed-route public transportation. GTFS-flex is now produced for over 100 transit services, and provides flexible transit trip plans through [OpenTripPlanner](https://www.opentripplanner.org/).
 
-### Quick links
-* [GTFS-flex draft spec in this repo](spec/reference.md)
-* [GTFS-flex Google Group](https://groups.google.com/forum/#!forum/gtfs-flexible-wg)
-* [Original Google Doc proposal](https://docs.google.com/document/d/1UTcpMJlANSoJ1ZEk5IrQh_plza1ZnvgwraMEBI_o2mw/edit?usp=sharing)
-
-### Change Process
-
-Discussion and change proposals are strongly encouraged. Rapid iteration and prototyping at this stage is necessary to develop GTFS-flex. We have adopted the following change proposal process:
-
-1. Discussion and needs documentation occur in GitHub issue threads. Refer to and describe real DRT service features in order to develop and support needs for GTFS-flex modeling capabilities.
-2. Propose changes to the spec that refer to needs identified in GitHub issues spec.
-3. Create pull request to vote on changes to the prototype spec. The pull requester becomes advocate for the proposal.
-4. Over the course of 7 days, stakeholders vote on the pull requests. Constructive feedback or alternative suggestions are required with downvote.
-5. Pull requests with at least one +1 and no -1 are merged.
-
-The above process is intended to begin tentative governance practices, and prevent spec bloat. Given that the GTFS-flex is in early prototype phase, speculative and experimental features are welcome.
+[See the GTFS-Flex proposal here.](spec/reference.md)
 
 ### Spec extension schematic diagram
 
-The below shows updated and added files in GTFS-flex, compared to the current GTFS (original Google Drawing is [here](https://docs.google.com/drawings/d/1g1kuTZPLFphMa942htywksIhxXqM_mMFCROOiEw5eNo/edit?usp=sharing)).
-
-![Diagram of added files in GTFS-flex](spec/GTFS%20and%20GTFS-flex.jpg)
-
-### Background & Purpose
-
-We’d like to better support modeling of flexible public transportation services in GTFS. For the purposes of this discussion, “flexible” services will be defined with regard to the following characteristics, as defined in [TCRP Program Report #140 - A Guide for Planning and Operating Flexible Public Transportation Services](http://www.trb.org/Main/Blurbs/163788.aspx):
+The below shows updated and added files in GTFS-Flex.
 
-* **Route Deviation:** vehicles operating on a regular schedule along a well-defined path, with or without marked bus stops, that deviate to serve demand-responsive requests within a zone around the path. The width or extent of the zone may be precisely established or flexible.
-* **Point Deviation:** vehicles serving demand-responsive requests within a zone and also serving a limited number of stops within the zone without any regular path between the stops.
-* **Demand-Responsive Connector:** vehicles operating in demand-responsive mode within a zone, with one or more scheduled transfer points that connect with a fixed-route network. A high percentage of ridership consists of trips to or from the transfer points.
-* **Request Stops:** vehicles operating in conventional fixed-route, fixed-schedule mode and also serving a limited number of undefined stops along the route in response to passenger requests.
-* **Flexible-Route Segments:** vehicles operating in conventional fixed-route, fixed-schedule mode, but switching to demand-responsive operation for a limited portion of the route.
-* **Zone Route:** vehicles operating in demand-responsive mode along a corridor with established departure and arrival times at one or more end points in the zone.
+![Diagram of added files in GTFS-Flex](spec/Flex%20Schema%20Diagram.png)
 
-The TCRP report catalogs a number of transit agencies across the US, evaluating how each agency uses flexible public transportation services in their own system. What’s clear from this analysis is that these agencies use a variety of techniques, picking and choosing from various strategies and flavors of flexible service when implementing their systems. Supporting all such services in GTFS will be tricky, but hopefully not impossible.
+### Example Flex v2 Feeds
+[On-demand service](spec/FlexExample--on-demand-service.zip)<br>[Same-day service](spec/FlexExample--same-day-service.zip)<br>[Various](spec/FlexExample--various.zip)