Skip to content

Commit ecd3377

Browse files
fredericsimardfredericsimard
committed
2 parents f11e683 + 29e5990 commit ecd3377

12 files changed

Lines changed: 511 additions & 9 deletions

File tree

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

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -335,3 +335,62 @@ Attributions makes it possible to share additional details regarding the organiz
335335
| au01 | gra | | | Greater Region Transport | 1 | | 1 | https://www.gra1.org | contact@gra1.org | (555) 555-5555 |
336336
| op02 | | rtd023 | | Bus company A | | 1 | | https://www.buscompanya.com | contact@buscompanya.com | (333) 333-3333 |
337337
| op03 | | rtd025 | | Bus company B | | 1 | | https://www.buscompanyb.com | contact@buscompanyb.com | (888) 888-8888 |
338+
339+
## Cars Allowed
340+
341+
Cars Allowed indicates if vehicles serving specific trips (such as car ferries or trains capable of transporting cars) are able to accommodate cars or not on the vehicle. This feature helps users plan and access services that enable them to make multimodal trips.
342+
343+
344+
| Files included | Fields included |
345+
|----------------------------------|-------------------|
346+
|[trips.txt](../../../documentation/schedule/reference/#tripstxt)|`cars_allowed` |
347+
348+
349+
**Prerequisites**:
350+
351+
- [Base features](../base)
352+
353+
??? note "Sample Data"
354+
355+
<p style="font-size:16px">
356+
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`).
357+
</p>
358+
!!! note ""
359+
<p style="font-size:16px">
360+
<a href="../../../documentation/schedule/reference/#tripstxt"><b>trips.txt</b></a> <br>
361+
</p>
362+
363+
| route_id | service_id | trip_id | cars_allowed |
364+
|----------|------------|---------|---------------|
365+
| RA | WE | AWE1 | 1 |
366+
| RA | WE | AWE2 | 2 |
367+
368+
369+
## Stop Access
370+
371+
Stop Access indicates if the stop or platform can be directly accessed from the street network or not. This feature allows trip planners to generate more accurate directions to reach the stop or platform.
372+
373+
| Files included | Fields included |
374+
|----------------------------------|-------------------|
375+
|[stops.txt](../../../documentation/schedule/reference/#tripstxt)|`stop_access` |
376+
377+
378+
**Prerequisites**:
379+
380+
- [Base features](../base)
381+
382+
??? note "Sample Data"
383+
384+
<p style="font-size:16px">
385+
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`).
386+
</p>
387+
!!! note ""
388+
<p style="font-size:16px">
389+
<a href="../../../documentation/schedule/reference/#stopstxt"><b>stops.txt</b></a> <br>
390+
</p>
391+
392+
| stop_id | stop_name | location_type | parent_station | stop_access |
393+
|----------|--|------------|---------|---------------|
394+
| STATION0 | Main Street Bus Station | 1 | | |
395+
| STOP1 | Main Street Bus Station - Platform 1 | 0 | STATION0 | 0 |
396+
| STOP2 | | Main Street Station - Street Bus Stop | STATION0 | 1 |

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

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -330,6 +330,57 @@ Fare Transfers is used to define rules applicable when transferring between legs
330330
| a | a | -1 | 7200 | 1 | 0 | free_transfer |
331331

332332

333+
## Contactless EMV Support
334+
335+
The Contactless EMV 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).
336+
This feature provides a simplified alternative to communicate the availability of contactless payment at an agency or route level, but it is not a replacement for detailed fare information provided through [Fare Media](../fares/#fare-media).
337+
338+
| Files included | Fields included |
339+
|----------------------------------|-------------------|
340+
|[agency.txt](../../../documentation/schedule/reference/#agencytxt)|`cemv_support`|
341+
|[routes.txt](../../../documentation/schedule/reference/#routestxt)|`cemv_support`|
342+
343+
**Prerequisites**:
344+
345+
- [Base features](../base)
346+
347+
??? note "Sample Data"
348+
349+
<p style="font-size:16px">
350+
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>
351+
352+
!!! note ""
353+
<p style="font-size:16px">
354+
<a href="../../../documentation/schedule/reference/#agencytxt"><b>agency.txt</b></a> <br>
355+
</p>
356+
357+
| agency_id | agency_name | agency_url | agency_timezone | cemv_support |
358+
| :---- | :---- | :---- | :---- | :---- |
359+
| AA | Agency A | [www.gtfsagencya.org](http://www.gtfsagencya.org) | America/Denver | 1 |
360+
| BB | Agency B | [www.gtfsagencyb.org](http://www.gtfsagencyb.org) | America/Denver | |
361+
| CC | Agency C | [www.gtfsagencyc.org](http://www.gtfsagencyc.org) | America/Denver | |
362+
363+
<p style="font-size:16px">
364+
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>
365+
366+
!!! note ""
367+
<p style="font-size:16px">
368+
<a href="../../../documentation/schedule/reference/#routestxt"><b>routes.txt</b></a> <br>
369+
</p>
370+
371+
| route_id | agency_id | route_short\_name | route_type | cemv_support |
372+
| :---- | :---- | :---- | :---- | :---- |
373+
| AA001 | AA | A1 | 3 | |
374+
| AA002 | AA | A2 | 3 | |
375+
| AA003 | AA | A3 | 3 | |
376+
| BB001 | BB | B1 | 3 | 1 |
377+
| BB002 | BB | B2 | 3 | 2 |
378+
| BB003 | BB | B3 | 3 | 1 |
379+
| CC001 | CC | C1 | 3 | 1 |
380+
| CC002 | CC | C2 | 3 | 2 |
381+
| CC003 | CC | C3 | 3 | 2 |
382+
383+
333384
## Fares v1
334385

335386
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‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -112,6 +112,17 @@ These features enhance a GTFS dataset, improving rider experience and facilitati
112112

113113
[:octicons-arrow-right-24: Learn more](../base_add-ons/#attributions)
114114

115+
- :material-plus-box-multiple-outline:{ .lg .middle } __Cars Allowed__
116+
117+
Communicate if vehicles are able to accommodate cars or not.
118+
119+
[:octicons-arrow-right-24: Learn more](../base_add-ons/#cars-allowed)
120+
121+
- :material-plus-box-multiple-outline:{ .lg .middle } __Stop Access__
122+
123+
Communicate how a stop is accessed relative to its parent station.
124+
125+
[:octicons-arrow-right-24: Learn more](../base_add-ons/#stop-access)
115126
</div>
116127

117128

@@ -188,6 +199,12 @@ GTFS can model various fare structures, such as zone, distance, or time-of-day b
188199

189200
[:octicons-arrow-right-24: Learn more](../fares/#fare-transfers)
190201

202+
- :material-cash:{ .lg .middle } __Contactless EMV Support__
203+
204+
Communicate if users can pay their fare using contactless EMV cards or devices.
205+
206+
[:octicons-arrow-right-24: Learn more](../fares/#contactless-emv-support)
207+
191208
- :material-cash:{ .lg .middle } __Fares V1__
192209

193210
Legacy feature that allows a simpler representation of fare information.

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

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -338,3 +338,60 @@
338338
| op02 | | rtd023 | | Bus company A | | 1 | | https://www.buscompanya.com | contact@buscompanya.com | (333) 333-3333 |
339339
| op03 | | rtd025 | | Bus company B | | 1 | | https://www.buscompanyb.com | contact@buscompanyb.com | (888) 888-8888 |
340340

341+
## Autos Permitidos
342+
343+
Autos permitidos indica si los vehículos que prestan servicio en viajes específicos (como ferris y trenes que pueden transportar autos) pueden transportar automóviles o no. Esta función ayuda a las personas usuarias a planear y acceder a servicios que les permiten realizar viajes multimodales.
344+
345+
| Archivos incluidos | Campos incluidos |
346+
|----------------------------------|-------------------|
347+
|[trips.txt](../../../documentation/schedule/reference/#tripstxt)|`cars_allowed` |
348+
349+
350+
**Requisitos previos**:
351+
352+
- [Funciones Base](../base)
353+
354+
??? note "Datos de muestra"
355+
356+
<p style="font-size:16px">
357+
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`).
358+
</p>
359+
!!! note ""
360+
<p style="font-size:16px">
361+
<a href="../../../documentation/schedule/reference/#tripstxt"><b>trips.txt</b></a> <br>
362+
</p>
363+
364+
| route_id | service_id | trip_id | cars_allowed |
365+
|----------|------------|---------|---------------|
366+
| RA | WE | AWE1 | 1 |
367+
| RA | WE | AWE2 | 2 |
368+
369+
370+
## Acceso a la Parada
371+
372+
Acceso a la Parada indica si se puede acceder directamente a la parada o andén desde la red vial. Esta función permite a los planificadores de viajes generar indicaciones más precisas para llegar a la parada o andén.
373+
374+
| Archivos incluidos | Campos incluidos |
375+
|----------------------------------|-------------------|
376+
|[stops.txt](../../../documentation/schedule/reference/#stopstxt)|`stop_access` |
377+
378+
379+
**Requisitos previos**:
380+
381+
- [Funciones Base](../base)
382+
383+
??? note "Datos de muestra"
384+
385+
<p style="font-size:16px">
386+
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`).
387+
</p>
388+
!!! note ""
389+
<p style="font-size:16px">
390+
<a href="../../../documentation/schedule/reference/#stopstxt"><b>stops.txt</b></a> <br>
391+
</p>
392+
393+
| stop_id | stop_name | location_type | parent_station | stop_access |
394+
|----------|--|------------|---------|---------------|
395+
| STATION0 | Main Street Bus Station | 1 | | |
396+
| STOP1 | Main Street Bus Station - Platform 1 | 0 | STATION0 | 0 |
397+
| STOP2 | | Main Street Station - Street Bus Stop | STATION0 | 1 |

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

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -330,7 +330,58 @@ Las categorías de pasajeros se utilizan para representar los diferentes tipos d
330330
|-------------------|-----------------|----------------|----------------|---------------------|--------------------|-----------------|
331331
| a | a | -1 | 7200 | 1 | 0 | free_transfer |
332332

333+
334+
## Soporte Contactless EMV
335+
336+
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").
337+
Esta función proporciona una alternativa simplificada para comunicar la disponibilidad de pagos contactless a nivel de agencia o ruta, pero no reemplaza la información detallada sobre tarifas proporcionada mediate [Medios de Tarifa](../fares/#medios-de-tarifa).
338+
339+
340+
| Archivos incluidos | Campos incluidos |
341+
|----------------------------------|-------------------|
342+
|[agency.txt](../../../documentation/schedule/reference/#agencytxt)|`cemv_support`|
343+
|[routes.txt](../../../documentation/schedule/reference/#routestxt)|`cemv_support`|
344+
345+
**Requisitos previos**:
333346

347+
- [Funciones Base](../base)
348+
349+
??? note "Datos de muestra"
350+
351+
<p style="font-size:16px">
352+
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>
353+
354+
!!! note ""
355+
<p style="font-size:16px">
356+
<a href="../../../documentation/schedule/reference/#agencytxt"><b>agency.txt</b></a> <br>
357+
</p>
358+
359+
| agency_id | agency_name | agency_url | agency_timezone | cemv_support |
360+
| :---- | :---- | :---- | :---- | :---- |
361+
| AA | Agency A | [www.gtfsagencya.org](http://www.gtfsagencya.org) | America/Denver | 1 |
362+
| BB | Agency B | [www.gtfsagencyb.org](http://www.gtfsagencyb.org) | America/Denver | |
363+
| CC | Agency C | [www.gtfsagencyc.org](http://www.gtfsagencyc.org) | America/Denver | |
364+
365+
<p style="font-size:16px">
366+
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>
367+
368+
!!! note ""
369+
<p style="font-size:16px">
370+
<a href="../../../documentation/schedule/reference/#routestxt"><b>routes.txt</b></a> <br>
371+
</p>
372+
373+
| route_id | agency_id | route_short_name | route_type | cemv_support |
374+
| :---- | :---- | :---- | :---- | :---- |
375+
| AA001 | AA | A1 | 3 | |
376+
| AA002 | AA | A2 | 3 | |
377+
| AA003 | AA | A3 | 3 | |
378+
| BB001 | BB | B1 | 3 | 1 |
379+
| BB002 | BB | B2 | 3 | 2 |
380+
| BB003 | BB | B3 | 3 | 1 |
381+
| CC001 | CC | C1 | 3 | 1 |
382+
| CC002 | CC | C2 | 3 | 2 |
383+
| CC003 | CC | C3 | 3 | 2 |
384+
334385
## Tarifas v1
335386

336387
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‎

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,6 +111,18 @@
111111
Comunicar quién participó en la creación del conjunto de datos.
112112

113113
[:octicons-arrow-right-24: Más información](../base-add-ons/#atribuciones)
114+
115+
- :material-plus-box-multiple-outline:{ .lg .middle } __Autos Permitidos__
116+
117+
Indicar si los vehículos pueden transportar automóviles o no.
118+
119+
[:octicons-arrow-right-24: Learn more](../base_add-ons/#autos-permitidos)
120+
121+
- :material-plus-box-multiple-outline:{ .lg .middle } __Acceso a la parada__
122+
123+
Indicar cómo se accede a una parada con respecto a su estación principal.
124+
125+
[:octicons-arrow-right-24: Learn more](../base_add-ons/#acceso-a-la-parada)
114126

115127
</div>
116128

@@ -136,7 +148,8 @@
136148

137149
Proporciona las entradas necesarias para convertir el texto de los nombres de las paradas en audio.
138150

139-
[:octicons-arrow-right-24: Más información](../accessibility/#texto-a-voz)
151+
[:octicons-arrow-right-24: Más información](../accessibility/#texto-a-voz)
152+
140153
</div>
141154

142155

@@ -186,6 +199,12 @@
186199
Definir las tarifas aplicables al transbordo de un tramo del viaje a otro.
187200

188201
[:octicons-arrow-right-24: Más información](../fares/#transferencias-de-tarifas)
202+
203+
- :material-cash:{ .lg .middle } __Soporte Contactless EMV__
204+
205+
Indicar si las personas pueden pagar utilizando tarjetas o dispositivos Contactless EMV.
206+
207+
[:octicons-arrow-right-24: Learn more](../fares/#soporte-contactless-emv)
189208

190209
- :material-cash:{ .lg.middle } __Tarifas V1__
191210

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

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -340,3 +340,62 @@
340340
| au01 | gra | | | Greater Region Transport | 1 | | 1 | https://www.gra1.org | contact@gra1.org | (555) 555-5555 |
341341
| op02 | | rtd023 | | Bus company A | | 1 | | https://www.buscompanya.com | contact@buscompanya.com | (333) 333-3333 |
342342
| op03 | | rtd025 | | Bus company B | | 1 | | https://www.buscompanyb.com | contact@buscompanyb.com | (888) 888-8888 |
343+
344+
## Voiture Autorisée
345+
346+
Voiture Autorisée indique si les véhicules (comme les ferries et les trains qui peuvent transporter des voitures) 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.
347+
348+
349+
| Fichiers inclus | Champs inclus |
350+
|----------------------------------|-------------------|
351+
|[trips.txt](../../../documentation/schedule/reference/#tripstxt)|`cars_allowed` |
352+
353+
354+
**Prérequis**:
355+
356+
- [fonctionnalités de Base](../base)
357+
358+
??? note "Exemples de données"
359+
360+
<p style="font-size:16px">
361+
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`).
362+
</p>
363+
!!! note ""
364+
<p style="font-size:16px">
365+
<a href="../../../documentation/schedule/reference/#tripstxt"><b>trips.txt</b></a> <br>
366+
</p>
367+
368+
| route_id | service_id | trip_id | cars_allowed |
369+
|----------|------------|---------|---------------|
370+
| RA | WE | AWE1 | 1 |
371+
| RA | WE | AWE2 | 2 |
372+
373+
374+
## Accès aux Arrêts
375+
376+
L'accès aux Arrêts indique si l'arrêt ou le quai est directement accessible depuis le réseau routier. Cette fonctionnalité permet aux planificateurs de trajets de générer des itinéraires. Cela permet aux applications de planification d’itinéraire de générer des itinéraires plus précis pour atteindre l'arrêt ou le quai.
377+
378+
| Fichiers inclus | Champs inclus |
379+
|----------------------------------|-------------------|
380+
|[stops.txt](../../../documentation/schedule/reference/#stopstxt)|`stop_access` |
381+
382+
383+
**Prérequis**:
384+
385+
- [fonctionnalités de Base](../base)
386+
387+
??? note "Exemples de données"
388+
389+
<p style="font-size:16px">
390+
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`).
391+
</p>
392+
!!! note ""
393+
<p style="font-size:16px">
394+
<a href="../../../documentation/schedule/reference/#stopstxt"><b>stops.txt</b></a> <br>
395+
</p>
396+
397+
| stop_id | stop_name | location_type | parent_station | stop_access |
398+
|----------|--|------------|---------|---------------|
399+
| STATION0 | Main Street Bus Station | 1 | | |
400+
| STOP1 | Main Street Bus Station - Platform 1 | 0 | STATION0 | 0 |
401+
| STOP2 | | Main Street Station - Street Bus Stop | STATION0 | 1 |

0 commit comments

Comments
 (0)