Add cEMV support, Stop Access and Cars Allowed features to GTFS.org

docs/en/getting-started/features/base-add-ons.md

@@ -335,3 +335,63 @@ Attributions makes it possible to share additional details regarding the organiz
         | au01           | gra       |          |         | Greater Region Transport |           1 |             |            1 | https://www.gra1.org             | contact@gra1.org        | (555)        555-5555    |
         | op02           |           | rtd023   |         | Bus company A            |             |           1 |              | https://www.buscompanya.com      | contact@buscompanya.com | (333)        333-3333    |
         | op03           |           | rtd025   |         | Bus company B            |             |           1 |              | https://www.buscompanyb.com      | contact@buscompanyb.com | (888)        888-8888    |
+
+## Cars Allowed
+
+Cars Allowed indicates if vehicles serving specific trips are able to accommodate cars or not, helping users to plan and access services that enable them to make multimodal trips (such as car ferries and trains that can transport cars in a similar way).
+
+
+
+| Files included                   | Fields included   |
+|----------------------------------|-------------------|
+|[trips.txt](../../../documentation/schedule/reference/#tripstxt)|`cars_allowed` |
+
+
+**Prerequisites**: 
+
+- [Base features](../base)
+
+??? note "Sample Data"
+
+    <p style="font-size:16px">
+    The following sample specifies that the vehicle used in trip `AWE1` can accommodate at least one car on board (`cars_allowed=1`), and the vehicle used in trip `AWE2` cannot (`cars_allowed=2`).
+    </p>
+    !!! note ""
+        <p style="font-size:16px">
+        <a href="../../../documentation/schedule/reference/#tripstxt"><b>trips.txt</b></a> <br>
+        </p>
+
+        | route_id | service_id | trip_id | cars_allowed |
+        |----------|------------|---------|---------------|
+        | RA       | WE         | AWE1    |             1 |
+        | RA       | WE         | AWE2    |             2 |
+
+
+## Stop Access
+
+This feature indicates how the stop is accessed for a particular station. This allows trip planners to generate directions for the stop either using pathways or the street network.
+
+| Files included                   | Fields included   |
+|----------------------------------|-------------------|
+|[stops.txt](../../../documentation/schedule/reference/#tripstxt)|`stop_access` |
+
+
+**Prerequisites**: 
+
+- [Base features](../base)
+
+??? note "Sample Data"
+
+    <p style="font-size:16px">
+    The following sample specifies that the stop with `stop_id` = `STOP1` must be accessed from a station entrance or using pathways (`stop_access=0`), and the stop with `stop_id` = `STOP2` can be accessed directly without taking into account entrances or pathways of the parent station `STATION0` (`stop_access=1`).
+    </p>
+    !!! note ""
+        <p style="font-size:16px">
+        <a href="../../../documentation/schedule/reference/#stopstxt"><b>stops.txt</b></a> <br>
+        </p>
+
+        | stop_id | stop_name | location_type | parent_station | stop_access |
+        |----------|--|------------|---------|---------------|
+        | STATION0   | Main Street Bus Station                | 1            |       |      |
+        | STOP1      |  Main Street Bus Station - Platform 1  | 0            | STATION0   | 0 |
+        | STOP2   |  |  Main Street Station - Street Bus Stop  | STATION0    |             1 |

docs/en/getting-started/features/fares.md

@@ -330,6 +330,58 @@ Fare Transfers is used to define rules applicable when transferring between legs
         | a                 | a               | -1             | 7200           | 1                   | 0                  | free_transfer   |
 
 
+## cEMV Support
+
+The cEMV support feature allows data producers to indicate whether riders can access a transit service using contactless cards or devices (for example, in tap-to-pay systems).
+It provides a simplified way to communicate the availability of contactless payment when publishing full fare media and fare rules is not possible.
+This feature is intended as a simplified alternative, and not replacement to detailed fare information provided through [Fare Media](../fares/#fare-media).
+
+| Files included                   | Fields included   |
+|----------------------------------|-------------------|
+|[agency.txt](../../../documentation/schedule/reference/#agencytxt)|`cemv_support`|
+|[routes.txt](../../../documentation/schedule/reference/#routestxt)|`cemv_support`|
+
+**Prerequisites**:
+
+- [Base features](../base)
+
+??? note "Sample Data"
+
+    <p style="font-size:16px">
+    In the following example, the first table specifies that all services operated by agency `AA` can be accessed by riders paying with contactless cards or devices (cEMV). </p>
+
+    !!! note ""
+        <p style="font-size:16px">
+        <a href="../../../documentation/schedule/reference/#agencytxt"><b>agency.txt</b></a> <br>
+        </p>
+
+        | agency\_id | agency\_name | agency\_url | agency\_timezone | cemv\_support |
+        | :---- | :---- | :---- | :---- | :---- |
+        | AA | Agency A | [www.gtfsagencya.org](http://www.gtfsagencya.org) | America/Denver | 1 |
+        | BB | Agency B | [www.gtfsagencyb.org](http://www.gtfsagencyb.org) | America/Denver |  |
+        | CC | Agency C | [www.gtfsagencyc.org](http://www.gtfsagencyc.org) | America/Denver |  |
+
+    <p style="font-size:16px">
+    In the second table, only specific routes (`BB001`, `BB003` and `CC001`) can be accessed by riders paying with contactless cards or devices (cEMV). All other routes from agencies `BB` and `CC` do not support contactless payment. </p>
+
+    !!! note ""
+        <p style="font-size:16px">
+        <a href="../../../documentation/schedule/reference/#routestxt"><b>routes.txt</b></a> <br>
+        </p>
+
+        | route\_id | agency\_id | route\_short\_name | route\_type | cemv\_support |
+        | :---- | :---- | :---- | :---- | :---- |
+        | AA001 | AA | A1 | 3 |  |
+        | AA002 | AA | A2 | 3 |  |
+        | AA003 | AA | A3 | 3 |  |
+        | BB001 | BB | B1 | 3 | 1 |
+        | BB002 | BB | B2 | 3 | 2 |
+        | BB003 | BB | B3 | 3 | 1 |
+        | CC001 | CC | C1 | 3 | 1 |
+        | CC002 | CC | C2 | 3 | 2 |
+        | CC003 | CC | C3 | 3 | 2 |
+
+
 ## Fares v1
 
 Fares v1 is a legacy alternative to other Fares features described above. It allows to model basic fare information such as fare pricing, payment methods transfers and zone-based fares using the `fare_rules.txt` and `fare_attributes.txt` files. While simpler to produce, it's less capable or modeling more complex fare structures and may be deprecated with sufficient endorsement of other Fare features (that are part of what is called Fares v2).

docs/en/getting-started/features/overview.md

@@ -112,6 +112,17 @@ These features enhance a GTFS dataset, improving rider experience and facilitati
 
     [:octicons-arrow-right-24: Learn more](../base_add-ons/#attributions)
 
+- :material-plus-box-multiple-outline:{ .lg .middle } __Cars Allowed__
+
+    Communicate if vehicles are able to accommodate cars or not.
+
+    [:octicons-arrow-right-24: Learn more](../base_add-ons/#cars-allowed)
+
+- :material-plus-box-multiple-outline:{ .lg .middle } __Stop Access__
+
+    Communicate how a stop is accessed relative to its parent station.
+
+    [:octicons-arrow-right-24: Learn more](../base_add-ons/#stop-access)
 </div>
 
 
@@ -188,6 +199,12 @@ GTFS can model various fare structures, such as zone, distance, or time-of-day b
 
     [:octicons-arrow-right-24: Learn more](../fares/#fare-transfers)
 
+-   :material-cash:{ .lg .middle } __cEMV Support__
+
+    Communicate if users can pay their fare using contactless EMV cards or devices.
+
+    [:octicons-arrow-right-24: Learn more](../fares/#cemv-support)
+
 -   :material-cash:{ .lg .middle } __Fares V1__
 
     Legacy feature that allows a simpler representation of fare information.

docs/es/getting-started/features/base-add-ons.md

@@ -338,3 +338,60 @@
         | op02           |           | rtd023   |         | Bus company A            |             |           1 |              | https://www.buscompanya.com      | contact@buscompanya.com | (333)        333-3333    |
         | op03           |           | rtd025   |         | Bus company B            |             |           1 |              | https://www.buscompanyb.com      | contact@buscompanyb.com | (888)        888-8888    |
 
+## Autos Permitidos
+
+Autos permitidos indica si los vehículos que prestan servicio en viajes específicos pueden transportar automóviles o no, lo cual ayuda a las personas usuarias a planear y acceder a servicios que les permiten realizar viajes multimodales (como ferris y trenes que pueden transportar autos).
+
+| Archivos incluidos | Campos incluidos | 
+|----------------------------------|-------------------|
+|[trips.txt](../../../documentation/schedule/reference/#tripstxt)|`cars_allowed` |
+
+
+**Requisitos previos**: 
+
+- [Funciones Base](../base) 
+
+??? note "Datos de muestra"
+
+    <p style="font-size:16px">
+    El siguiente ejemplo especifica que el vehículo utilizado en el viaje `AWE1` puede transportar al menos un automóvil a bordo (`cars_allowed=1`), y que el vehículo utilizado en el viaje `AWE2` no puede (`cars_allowed=2`).
+    </p>
+    !!! note ""
+        <p style="font-size:16px">
+        <a href="../../../documentation/schedule/reference/#tripstxt"><b>trips.txt</b></a> <br>
+        </p>
+
+        | route_id | service_id | trip_id | cars_allowed |
+        |----------|------------|---------|---------------|
+        | RA       | WE         | AWE1    |             1 |
+        | RA       | WE         | AWE2    |             2 |
+
+
+## Acceso a la Parada
+
+Esta función indica cómo se accede a una parada en una estación determinada. Esto permite que los planificadores de viajes generen indicaciones hacia la parada utilizando los recorridos internos (pathways) o la red vial.
+
+| Archivos incluidos | Campos incluidos | 
+|----------------------------------|-------------------|
+|[stops.txt](../../../documentation/schedule/reference/#stopstxt)|`stop_access` |
+
+
+**Requisitos previos**: 
+
+- [Funciones Base](../base) 
+
+??? note "Datos de muestra"
+
+    <p style="font-size:16px">
+    El siguiente ejemplo especifica que a la parada con `stop_id` = `STOP1` se debe acceder desde una entrada de la estación o utilizando recorridos (pathways) internos (`stop_access=0`), y que a la parada con `stop_id` = `STOP2` se puede acceder directamente, sin tener en cuenta las entradas ni los recorridos (pathways) internos de la estación principal `STATION0` (`stop_access=1`).
+    </p>
+    !!! note ""
+        <p style="font-size:16px">
+        <a href="../../../documentation/schedule/reference/#stopstxt"><b>stops.txt</b></a> <br>
+        </p>
+
+        | stop_id | stop_name | location_type | parent_station | stop_access |
+        |----------|--|------------|---------|---------------|
+        | STATION0   | Main Street Bus Station                | 1            |       |      |
+        | STOP1      |  Main Street Bus Station - Platform 1  | 0            | STATION0   | 0 |
+        | STOP2   |  |  Main Street Station - Street Bus Stop  | STATION0    |             1 |

docs/es/getting-started/features/fares.md

@@ -330,7 +330,59 @@ Las categorías de pasajeros se utilizan para representar los diferentes tipos d
         |-------------------|-----------------|----------------|----------------|---------------------|--------------------|-----------------|
         | a                 | a               | -1             | 7200           | 1                   | 0                  | free_transfer   |
 
+
+## Soporte Contactless EMV
+
+Soporte Contactless EMV se utiliza para indicar si los pasajeros pueden acceder a un servicio de transporte utilizando tarjetas o dispositivos contactless (por ejemplo, en sistemas "tap-to-pay").
+Proporciona una forma simplificada de comunicar la disponibilidad de pagos contactless cuando no es posible publicar la información completa de tarifas.
+Esta función pensada como una alternativa simplificada, y no un sustituto a la información detallada de tarifas proporcionada mediante [Medios de Tarifa](../fares/#medios-de-tarifa).
+
+
+| Archivos incluidos                   | Campos incluidos   |
+|----------------------------------|-------------------|
+|[agency.txt](../../../documentation/schedule/reference/#agencytxt)|`cemv_support`|
+|[routes.txt](../../../documentation/schedule/reference/#routestxt)|`cemv_support`|
+
+**Requisitos previos**: 
 
+- [Funciones Base](../base) 
+
+??? note "Datos de muestra"
+
+    <p style="font-size:16px">
+    En el siguiente ejemplo, la primera tabla indica que todos los servicios operados por la agencia `AA` pueden ser utilizados pagando con tarjetas o dispositivos contactless (cEMV). </p>
+
+    !!! note ""
+        <p style="font-size:16px">
+        <a href="../../../documentation/schedule/reference/#agencytxt"><b>agency.txt</b></a> <br>
+        </p>
+
+        | agency\_id | agency\_name | agency\_url | agency\_timezone | cemv\_support |
+        | :---- | :---- | :---- | :---- | :---- |
+        | AA | Agency A | [www.gtfsagencya.org](http://www.gtfsagencya.org) | America/Denver | 1 |
+        | BB | Agency B | [www.gtfsagencyb.org](http://www.gtfsagencyb.org) | America/Denver |  |
+        | CC | Agency C | [www.gtfsagencyc.org](http://www.gtfsagencyc.org) | America/Denver |  |
+
+    <p style="font-size:16px">
+    En la segunda tabla, únicamente ciertas rutas (`BB001`, `BB003` y `CC001`) pueden ser utilizadas pagando con tarjetas o dispositivos contactless (cEMV). El resto de las rutas de las agencias `BB` y `CC` no admiten pagos contactless. </p>
+
+    !!! note ""
+        <p style="font-size:16px">
+        <a href="../../../documentation/schedule/reference/#routestxt"><b>routes.txt</b></a> <br>
+        </p>
+
+        | route\_id | agency\_id | route\_short\_name | route\_type | cemv\_support |
+        | :---- | :---- | :---- | :---- | :---- |
+        | AA001 | AA | A1 | 3 |  |
+        | AA002 | AA | A2 | 3 |  |
+        | AA003 | AA | A3 | 3 |  |
+        | BB001 | BB | B1 | 3 | 1 |
+        | BB002 | BB | B2 | 3 | 2 |
+        | BB003 | BB | B3 | 3 | 1 |
+        | CC001 | CC | C1 | 3 | 1 |
+        | CC002 | CC | C2 | 3 | 2 |
+        | CC003 | CC | C3 | 3 | 2 |
+
 ## Tarifas v1 
 
  Tarifas v1 es una alternativa heredada a otras funciones de Tarifas descritas anteriormente. Permite modelar información básica de tarifas, como precios de tarifas, transferencias de métodos de pago y tarifas basadas en zonas utilizando los archivos `fare_rules.txt` y `fare_attributes.txt`. Si bien es más simple de producir, es menos capaz de modelar estructuras de tarifas más complejas y puede quedar obsoleto con el respaldo suficiente de otras funciones de Fare (que son parte de lo que se llama Tarifas v2). 

docs/es/getting-started/features/overview.md

@@ -111,6 +111,18 @@
     Comunicar quién participó en la creación del conjunto de datos. 
 
     [:octicons-arrow-right-24: Más información](../base-add-ons/#atribuciones) 
+
+ - :material-plus-box-multiple-outline:{ .lg .middle } __Autos Permitidos__
+
+    Indicar si los vehículos pueden transportar automóviles o no.
+
+    [:octicons-arrow-right-24: Learn more](../base_add-ons/#autos-permitidos)
+
+ - :material-plus-box-multiple-outline:{ .lg .middle } __Acceso a la parada__
+
+    Indicar cómo se accede a una parada con respecto a su estación principal.
+
+    [:octicons-arrow-right-24: Learn more](../base_add-ons/#acceso-a-la-parada)
 
 </div> 
 
@@ -136,7 +148,8 @@
 
     Proporciona las entradas necesarias para convertir el texto de los nombres de las paradas en audio. 
 
-    [:octicons-arrow-right-24: Más información](../accessibility/#texto-a-voz) 
+    [:octicons-arrow-right-24: Más información](../accessibility/#texto-a-voz)
+
 </div> 
 
 
@@ -186,6 +199,12 @@
     Definir las tarifas aplicables al transbordo de un tramo del viaje a otro. 
 
     [:octicons-arrow-right-24: Más información](../fares/#transferencias-de-tarifas) 
+
+-   :material-cash:{ .lg .middle } __Soporte Contactless EMV__
+
+    Indicar si las personas pueden pagar utilizando tarjetas o dispositivos Contactless EMV.
+
+    [:octicons-arrow-right-24: Learn more](../fares/#soporte-contactless-emv)
 
  - :material-cash:{ .lg.middle } __Tarifas V1__ 
 

docs/fr/getting-started/features/base-add-ons.md

@@ -340,3 +340,62 @@
         | au01           | gra       |          |         | Greater Region Transport |           1 |             |            1 | https://www.gra1.org             | contact@gra1.org        | (555)        555-5555    |
         | op02           |           | rtd023   |         | Bus company A            |             |           1 |              | https://www.buscompanya.com      | contact@buscompanya.com | (333)        333-3333    |
         | op03           |           | rtd025   |         | Bus company B            |             |           1 |              | https://www.buscompanyb.com      | contact@buscompanyb.com | (888)        888-8888    |
+
+## Voiture Autorisée
+
+ Voiture Autorisée indique si les véhicules effectuant des déplacements spécifiques sont en mesure d’accueillir des voitures ou non, aidant ainsi les utilisateurs à planifier et à accéder aux services qui leur permettent d’effectuer des déplacements multimodaux (comme les ferries et les trains qui peuvent transporter des voitures de manière similaire).
+
+
+| Fichiers inclus | Champs inclus   |
+|----------------------------------|-------------------|
+|[trips.txt](../../../documentation/schedule/reference/#tripstxt)|`cars_allowed` |
+
+
+**Prérequis**: 
+
+- [fonctionnalités de Base](../base)
+
+??? note "Exemples de données"
+
+    <p style="font-size:16px">
+    L'exemple suivant spécifie que le véhicule utilisé dans le trajet `AWE1` peut accueillir au moins une voiture à bord (`cars_allowed=1`), et que le véhicule utilisé dans le trajet `AWE2` ne le peut pas (`cars_allowed=2`).
+    </p>
+    !!! note ""
+        <p style="font-size:16px">
+        <a href="../../../documentation/schedule/reference/#tripstxt"><b>trips.txt</b></a> <br>
+        </p>
+
+        | route_id | service_id | trip_id | cars_allowed |
+        |----------|------------|---------|---------------|
+        | RA       | WE         | AWE1    |             1 |
+        | RA       | WE         | AWE2    |             2 |
+
+
+## Accès aux Arrêts
+
+Indique comment accéder à l'arrêt pour une station donnée. Cela permet aux applications de planification d’itinéraire de générer des itinéraires vers l'arrêt en utilisant soit les parcours (pathways), soit le réseau routier.
+
+| Fichiers inclus | Champs inclus   |
+|----------------------------------|-------------------|
+|[stops.txt](../../../documentation/schedule/reference/#stopstxt)|`stop_access` |
+
+
+**Prérequis**: 
+
+- [fonctionnalités de Base](../base)
+
+??? note "Exemples de données"
+
+    <p style="font-size:16px">
+    L'exemple suivant spécifie que l'arrêt avec `stop_id` = `STOP1` doit être accessible depuis une entrée de station ou en utilisant des parcours (`stop_access=0`), et que l'arrêt avec `stop_id` = `STOP2` peut être accessible directement sans tenir compte des entrées ou des parcours de la station parent `STATION0` (`stop_access=1`).
+    </p>
+    !!! note ""
+        <p style="font-size:16px">
+        <a href="../../../documentation/schedule/reference/#stopstxt"><b>stops.txt</b></a> <br>
+        </p>
+
+        | stop_id | stop_name | location_type | parent_station | stop_access |
+        |----------|--|------------|---------|---------------|
+        | STATION0   | Main Street Bus Station                | 1            |       |      |
+        | STOP1      |  Main Street Bus Station - Platform 1  | 0            | STATION0   | 0 |
+        | STOP2   |  |  Main Street Station - Street Bus Stop  | STATION0    |             1 |