Changes to Community Section (#311)

* Squashed commit of the following: commit fe496d1 Author: isabelle-dr <[email protected]> Date: Tue Feb 6 14:29:31 2024 -0500 Removing translations (#306) * dummy commit * Remove translations part one * removing translations * Make changes based on review * Squashed commit of the following: commit 30ce1ef Author: Sergio Delgado Rodriguez <[email protected]> Date: Tue Feb 6 15:46:57 2024 -0500 new_GTFS.org_structure (#307) Adding new files for new GTFS architecture. This change does not remove the old files. commit fe496d1 Author: isabelle-dr <[email protected]> Date: Tue Feb 6 14:29:31 2024 -0500 Removing translations (#306) * dummy commit * Remove translations part one * removing translations * Make changes based on review * Updated Platforms.md and active_projects.md - Added grids to platforms for better visibility. - Added mailling lists and other community links to platforms.md -Added active projects to active projects. --------- Co-authored-by: Sergio Delgado Rodriguez <[email protected]>
MobilityData · Feb 6, 2024 · edef886 · edef886
1 parent 02d6e1f
commit edef886
Show file tree

Hide file tree

Showing 4 changed files with 256 additions and 1 deletion.
diff --git a/docs/community/active_projects.md b/docs/community/active_projects.md
@@ -1 +1,25 @@
-This is where projects in development would go
+<div class="row">
+    <div class="leftcontainer">
+            <a href="fares-v2" class="no-icon" target="_blank"><h3 class="title">GTFS-Fares v2</h3></a>
+            <p class="maintainer">Maintained by <a href="https://mobilitydata.org/" class="no-icon" target="_blank">MobilityData</a></p>
+    </div>
+    <div class="featurelist">
+        <ul>
+            <li>Enables trip planning apps to display pricing information to riders.</li>
+            <li>While the base implementation of GTFS-Fares v2 has recently been voted to pass into GTFS, some features and functionalities of this extension that are still remaining include zonal/distance-based fares, rider categories, fare capping and ranges, fare bundles passes and containers, rush hour/holiday pricing, transfer sequences, and one route behaviour.</li>
+        </ul>
+    </div>
+    </div>
+
+<div class="row">
+    <div class="leftcontainer">
+            <a href="flex" class="no-icon" target="_blank"><h3 class="title">GTFS-Flex</h3></a>
+            <p class="maintainer">Maintained by <a href="https://mobilitydata.org/" class="no-icon" target="_blank">MobilityData</a></p>
+    </div>
+    <div class="featurelist">
+        <ul>
+            <li>Extends GTFS by including deviated fixed routes and on-demand transportation service features in its data modeling that do not always follow the same for fixed stops.</li>
+            <li>The proposal is composed of 2 extensions: GTFS-FlexibleTrips, which describes the service itself and GTFS-BookingRules, which provides the booking information of GTFS-FlexibleTrips.</li>
+        </ul>
+    </div>
+    </div>
diff --git a/docs/community/fares-v2.md b/docs/community/fares-v2.md
@@ -0,0 +1,65 @@
+<a class="pencil-link" href="https://github.com/MobilityData/gtfs.org/edit/main/docs/extensions/fare-extension.md" title="Edit this page" target="_blank">
+    <svg class="pencil" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M10 20H6V4h7v5h5v3.1l2-2V8l-6-6H6c-1.1 0-2 .9-2 2v16c0 1.1.9 2 2 2h4v-2m10.2-7c.1 0 .3.1.4.2l1.3 1.3c.2.2.2.6 0 .8l-1 1-2.1-2.1 1-1c.1-.1.2-.2.4-.2m0 3.9L14.1 23H12v-2.1l6.1-6.1 2.1 2.1Z"></path></svg>
+  </a>
+
+# GTFS-Fares v2
+
+Fares v2 is a GTFS Schedule extension project that aims to address the limitations of <a href="/schedule/examples/fares-v1">Fares v1</a>.
+
+The main concepts that Fares v2 plans to represent are
+
+- Fare products (e.g tickets and passes)
+- Rider categories (e.g seniors and children)
+- Fare media (e.g transit pass, paper tickets, contactless bank cards)
+- Fare capping
+
+These concepts will allow data producers to model zone-based, time-dependent, and inter-agency fares. This extension project is being adopted in iterations. 
+
+You can see <a href="/schedule/examples/fares-v2" target="_blank">examples here</a> that show what can be modelled using the adopted Fares v2 base implementation.
+
+Producers may implement Fares v2 in the same dataset with Fares v1, since there is no technical conflict between the two. Consumers can choose which version to use independent of the other. With adoption and sufficient endorsement of Fares v2, Fares v1 may be deprecated in the future.
+
+<a class="button no-icon" href="https://share.mobilitydata.org/gtfs-fares-v2" target="_blank">See the full proposal</a>
+
+## Participate in the conversation
+You can stay up to date and join the discussions around Fares v2 by joining our Slack Chanel and the recurring working group meetings.
+
+<a class="button no-icon" href=https://share.mobilitydata.org/slack>Join #gtfs-fares on Slack</a><a class="button no-icon" href=https://www.eventbrite.ca/e/specifications-discussions-gtfs-fares-v2-monthly-meetings-tickets-522966225057>See the meeting schedule</a><a class="button no-icon" href=https://docs.google.com/document/d/1d3g5bMXupdElCKrdv6rhFNN11mrQgEk-ibA7wdqVLTU/edit>See meeting notes</a>
+
+
+## First Adopters
+
+🎉 Shoutout to Fares v2 first adopters! At least 1 data producer and 1 consumer must commit to implementing an experimental feature before a public vote is opened to add it to the official specification. These organizations invest a large amount of time and energy into experimental changes to make sure that GTFS continues to evolve.
+
+- Producers: <a href="https://www.interline.io/" target="_blank">Interline</a>, <a href="https://www.mta.maryland.gov/developer-resources" target="_blank">Maryland Department of Transportation</a>, <a href="https://dot.ca.gov/cal-itp/cal-itp-gtfs" target="_blank">Cal-ITP</a>, <a href="https://trilliumtransit.com/" target="_blank">Trillium Solutions</a>, <a href="https://www.itoworld.com/" target="_blank">ITO World</a>, <a href="https://www.mbta.com/" target="_blank">MBTA</a>, <a href="http://www.pvta.com/" target="_blank">PVTA</a>
+- Consumers: <a href="https://transitapp.com/" target="_blank">Transit</a>, <a href="https://www.apple.com/">Apple Maps</a>
+
+## Adoption tracker
+### Current
+
+<iframe class="airtable-embed" src="https://airtable.com/embed/shrZzYzPYao7iExlW?backgroundColor=red&viewControls=on" frameborder="0" onmousewheel="" width="100%" height="533" style="background: transparent; border: 1px solid #ccc;"></iframe>
+
+<a class="button no-icon" href="https://airtable.com/shr8aT0K9bpncmy0V" target="_blank">Request a change</a><a class="button no-icon" href="https://airtable.com/shr5B6Pl1r9KH9qMX" target="_blank">Add your organization (consumers)</a><a class="button no-icon" href="https://airtable.com/shrn0Afa3TPNkOAEh" target="_blank">Add your organization (producers)</a>
+
+### Future
+<iframe class="airtable-embed" src="https://airtable.com/embed/shrUrgZTO1noUF66R?backgroundColor=red&viewControls=on" frameborder="0" onmousewheel="" width="100%" height="533" style="background: transparent; border: 1px solid #ccc;"></iframe>
+
+<a class="button no-icon" href="https://airtable.com/shrvnI40zuFXmDsQI" target="_blank">Add your future plans</a>
+
+## Fares v2 Features Under Discussion
+
+<iframe src="https://portal.productboard.com/rhk8dbtic1iqakfznucry448" frameborder="0" width="100%", style="min-height:1060px;"></iframe>
+
+## History
+
+- **2017**: Industry research and data modelling
+- **October 2021**: <a href="https://github.com/google/transit/pull/286#issue-1026848880" target="_blank">Base implementation drafted and shared</a>
+- **December 2021**: <a href="https://github.com/google/transit/pull/286#issuecomment-990258396" target="_blank">Open vote #1 → did not pass</a>
+- **March 2022**: <a href="https://github.com/google/transit/pull/286#issuecomment-1080716109" target="_blank">Open vote #2 → did not pass</a>
+- **May 2022**: <a href="https://github.com/google/transit/pull/286#issuecomment-1121392932" target="_blank">Open vote #3 → passed</a>
+- **August 2022**: <a href="https://github.com/google/transit/issues/341" target="_blank">Community discussion on next phase of Fares v2 begins</a>
+- **November 2022**: <a href="https://github.com/google/transit/pull/355" target="_blank">Fare media draft pull request opened for feedback</a>
+- **December 2022**: <a href="https://github.com/google/transit/issues/341#issuecomment-1339947915" target="_blank">Community identifies stack ranked order of features to prioritize iterations</a>
+- **March 2023**: <a href="https://github.com/google/transit/pull/355#issuecomment-1468326858" target="_blank">Fare media passes</a>
+- **July 2023**: <a href="https://github.com/google/transit/pull/357#issuecomment-1653561813" target="_blank">Fares that vary by time/day passes</a>
+- **November 2023**: <a href="https://github.com/google/transit/pull/405#issuecomment-1830665141" target="_blank">Dedicated files to define networks</a>
diff --git a/docs/community/flex.md b/docs/community/flex.md
@@ -0,0 +1,130 @@
+<a class="pencil-link" href="https://github.com/MobilityData/gtfs.org/edit/main/docs/extensions/fare-extension.md" title="Edit this page" target="_blank">
+    <svg class="pencil" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M10 20H6V4h7v5h5v3.1l2-2V8l-6-6H6c-1.1 0-2 .9-2 2v16c0 1.1.9 2 2 2h4v-2m10.2-7c.1 0 .3.1.4.2l1.3 1.3c.2.2.2.6 0 .8l-1 1-2.1-2.1 1-1c.1-.1.2-.2.4-.2m0 3.9L14.1 23H12v-2.1l6.1-6.1 2.1 2.1Z"></path></svg>
+  </a>
+
+# GTFS-Flex
+
+Flex is a GTFS Schedule extension project that aims to facilitate discoverability of Demand Responsive Transportation Services.
+
+🤔 Services like dial-a-ride are often brushed over by riders, who sometimes have no clue they even exist. This lack of accessibility is an issue for transit agencies, trip planners, and riders. Imagine a group of tourists arriving at your local airport who would like to reach a rural area that only offers an on-demand bus service. The tourists check their preferred trip planner app and do not find a viable public transportation option. They end up renting a car. Being tourists, they miss all of your paper flyers posted along the hallway announcing the on-demand service. Not only is your service underused, but it lacks the discoverability to meet current and future rider demand. This is where GTFS-Flex comes in. GTFS-Flex helps riders discover your service, so they enjoy the services you worked hard to promote.
+
+<img src="../../assets/flex-userjourney-resize.jpg" alt="GTFS-Flex User Journey">
+
+🔮 MobilityData expects GTFS-Flex to open the door to deeper standardization of demand responsive transportation, including expansion into transactional and real-time components using GTFS-OnDemand. We are preparing a suggested strategy to best handle the growing number of modes of transportation and complexity of concepts in this area.
+
+<a class="button no-icon" href="https://github.com/MobilityData/gtfs-flex" target="_blank">See the full proposal</a>
+
+## Latest Pull Request
+This extension describes services that operate according to a schedule, but also include one or more flexible features, such as:
+
+- **Dial-a-ride service**: the vehicle serves a zone where pickups and drop offs are allowed during certain service hours.
+- **Route deviation services**: the vehicle serves a fixed route and ordered set of stops, and may detour to pick up or drop off a passenger between stops.
+- **Point-to-zone service**: the rider can board at a fixed stop such as a train station, and then alight anywhere within an area, or vice versa. Departures from some locations are scheduled or timed with other services.
+- **Point deviation or checkpoint service**: the rider can board at a fixed stop, and then alight anywhere among an unordered list of stops, or the opposite. The driver only serves stops at which a request is made.
+
+For more information please see [original proposal](https://github.com/MobilityData/gtfs-flex/blob/master/spec/reference.md) and [issue#382](https://github.com/google/transit/issues/382)(closed since we changed the scope).
+
+In the working meeting on June 28th, there was an agreement among the group community to pursue an iteration that covers all fields currently produced and consumed. Therefore, all fields that appear as “**in discussion**” in the [adoption tracker](https://gtfs.org/extensions/flex/#current) are included in this PR.
+
+The changes in this PR are:
+
+- Modify file:
+-- Modify `stop_areas.txt` to allow grouping of GeoJSON locations and/or stops which allow predetermined groups of these features to be specified on individual rows of `stop_times.txt`.
+-- Modify `stop_times.txt` to clarify elements of the current specification necessary to inform data consumers of how to interpret the added and extended files and fields 
+- Extend file:
+-- Extend `stop_times.txt` with `start_pickup_drop_off_window` and `end_pickup_drop_off_window` to define the time that demand responsive transportation service becomes available/ends in a GeoJSON location, stop area or stop.
+-- Extend `stop_times.txt` with `pickup_booking_rule_id` and `drop_off_booking_rule_id` to define links to booking rules
+- Add new file:
+-- `locations.geojson`, to define zones (`Polygon` or `Multipolygon`) where riders can request either pickup or drop off.
+-- `booking_rules.txt`, to define the booking rules that provide riders information about how to request service.
+
+Here is a [data example](https://docs.google.com/spreadsheets/d/1w5EHuHfxvejqApJFHA1Z0K2KytD9zahwbf8zyRlP_Ls/edit#gid=1451132209) for [RufBus](https://uvg-online.com/rufbus-angermuende/) in Angermünde and Gartzer, Germany. The image below is an example illustrating how the data could be presented in a trip planner:
+
+<img src="https://github.com/google/transit/assets/126435471/c986f79a-0164-4e38-a552-7e37405fe133" width="180" height="400">
+
+Visit the Pull Request page to read the full post and contribute to the conversation. 
+
+<a class="button no-icon" href="https://github.com/google/transit/pull/388" target="_blank">See the Pull Request</a>
+
+<a class="button no-icon" href=https://share.mobilitydata.org/slack>Join #gtfs-flex on Slack</a><a class="button no-icon" href=https://groups.google.com/g/gtfs-changes>Join GTFS-Changes Google Group</a>
+
+## Early Implementations
+
+- [MNDoT Flex Pilot Project: Trillium, IBI, Transit, MNDoT, Cambridge Systematics, and Token Transit](https://blog.transitapp.com/case-study/mndot-gtfs-flex-bringing-rural-riders-into-the-fold/) 
+- [Open Trip Planner](https://www.opentripplanner.org/)
+- [Mobility on Demand Sandbox in Vermont](https://www.connectingcommuters.org/)
+- [Tulare County Area Transit](https://ridetcat.org/)
+- [Northwest Oregon Transit Alliance (NW Connector)](https://nwconnector.org/other-services/)
+- [Vamos Mobility App](https://vamosmobileapp.com/)
+- [RTD Denver Flexride](https://www.rtd-denver.com/services/flexride)
+- [Nebraska Public Transit DRT OTP Project: Trillium, Olsson, Cambridge Systematics, and TransitPlus](https://trips.nebraskatransit.com/#/)
+
+Contact us to add your GTFS-Flex implementation to this page
+
+<a class="button no-icon" href=mailto:[email protected] >Contact us</a>
+
+## Adoption tracker
+### Current
+
+<iframe class="airtable-embed" src="https://airtable.com/embed/shrUPyCZWOWrvO2mX?backgroundColor=purple&viewControls=on" frameborder="0" onmousewheel="" width="100%" height="533" style="background: transparent; border: 1px solid #ccc;"></iframe>
+
+<a class="button no-icon" href="https://airtable.com/shrcac1fXUrMxfoDV" target="_blank">Request a change</a><a class="button no-icon" href="https://airtable.com/shrgnVR5Su9tkHvUv" target="_blank">Add your organization (consumers)</a><a class="button no-icon" href="https://airtable.com/shrsU4idBtcLuRuwZ" target="_blank">Add your organization (producers)</a>
+
+### Ideas parking lot
+
+This area is intended as a community "parking lot". Share something you would like to add to the next increment of GTFS-Flex.  
+<iframe class="airtable-embed" src="https://airtable.com/embed/shrMOvBrQCCyWPcAS?backgroundColor=purple" frameborder="0" onmousewheel="" width="100%" height="533" style="background: transparent; border: 1px solid #ccc;"></iframe>
+
+<a class="button no-icon" href="https://airtable.com/shrr4FVw46i1vsOz7" target="_blank">Add your future plans</a>
+
+## History
+
+- **2013**: Original proposal written by Brian Ferris (Google)
+- **2016**: <a href="https://github.com/MobilityData/gtfs-flex/tree/master" target="_blank">GTFS-Flex GitHub discussions begin</a>
+- **2017**: <a href="https://www.oregon.gov/odot/RPTD/RPTD%20Document%20Library/GTFS-Flex-N-CATT.pdf" target="_blank">Mobility on Demand (MOD) sandbox program (FTA, Vermont DOT, OTP)</a>
+- **2018**: MobilityData becomes GTFS-Flex steward and proposes GTFS-Flex v2
+- **November 2020**: Repository up-to-date version of GTFS-Flex and OTP2 ingests GTFS-Flex v2 data
+- **May 2022**: Start of MnDoT pilot (Cambridge Systematics, MNDoT, Token Transit, Transit, Trillium (OptiBus).  
+- **May 2023**: <a href="https://github.com/google/transit/issues/382" target="_blank">Work on GTFS-Flex: Service Discovery Begins</a>
+- **June 2023**:  <a href="https://mobilitydata.org/recap-mobilitydata-working-meeting-gtfs-flex-service-discovery/" target="_blank">Held Conceptual Working Meeting on GTFS-Flex</a>
+- **July 2023**: <a href="https://github.com/google/transit/pull/388" target="_blank">Published Pull Request #388</a>
+- **August and September 2023**: <a href="https://github.com/google/transit/pull/388" target="_blank">Held "GeoJSON in GTFS?" discussions</a>
+
+## Glossary
+
+📲 Dial-a-ride is a variation of multiple terms used across Europe. 
+
+🇨🇭 In Switzerland, it would fall under the term Rufbus / On-call bus. There's also the availability of the [PubliCar system by PostAuto](https://www.postauto.ch/en/timetable-and-network/publicar). Under this proposal, the PubliCar App and service would be discoverable in the user’s preferred trip planner app. 
+
+🇦🇹 In Austria, dial-a-ride would also be Rufbus and under the bigger umbrella of Bedarfsverkehr (Demand Responsive Transport) and Mikro-ÖV (Microtransit).
+
+- [bedarfsverkehr.at](https://www.bedarfsverkehr.at/)
+- [Wiener Linien](https://www.wienerlinien.at/documents/843721/4770179/Anleitung_Rufbus_359531.pdf/df430b95-9dd4-0d13-ffdf-bdace15932a8?t=1614165175643)
+- Rufbus (english: dial-a-bus, formerly Anruf-Sammel-Taxi or ASTAX call-collect-taxi)
+- Current GTFS implementation [as an year-long service alert](https://www.google.com/maps/dir/S%C3%BC%C3%9Fenbrunner+Pl.,+1220+Wien,+Austria/2201+Gerasdorf,+Austria/@48.2867283,16.4429959,13z/am=t/data=!4m15!4m14!1m5!1m1!1s0x476d0393b15bc6d9:0x517f69839511fb31!2m2!1d16.4958186!2d48.2772635!1m5!1m1!1s0x476d0488292e6f61:0xeee80d3d2bb6b1f5!2m2!1d16.4690073!2d48.2962096!3e3!5i1?entry=ttu )
+
+🇩🇰 In Denmark, it can be referred to NT / midttrafik / sydtrafik / FYNBUS / movia (https://flextur.dk/)
+
+- flextur (english: flex trip)
+- formerly flextrafik (english: flex transit)
+
+🇫🇷 ⚠️ In France the terms TDA (Transport à la Demande) and PMR (Personnes à Mobilité Réduite) for Paratransit services
+
+- [Reseau Mistral](https://www.reseaumistral.com/services/service-appel-bus) 
+- Appel bus (english: call bus)
+
+🇩🇪 In Germany they refer to it as On-Demand-Angebot, Flexible Fahrt and AST
+
+- [BVG](https://www.bvg.de/de/verbindungen/bvg-muva/flexible-fahrt)
+- Brand: Muva
+- On-Demand-Angebot (english: on-demand-service)
+- Flexible Fahrt (english: flexible trip)
+- Other areas
+- Anruf-sammel-taxi or AST (english: call-collect-taxi)
+
+🇬🇧 In the United Kingdom, there is the following service:
+
+- [go2 Sevenoaks](https://www.go-coach.co.uk/go2/ )
+- On-demand service
+
+The terminology varies across borders but in general we can assume that dial-a-ride is any demand responsive service that requires some form of contact by the rider to the operator.