Competency questions

1. Siguiendo GTFS to Transmodel & UC-1
2. UC1 Accessible Stops
3. UC2 Accesible coaches
4. UC3 Public WC/Restrooms at Stops
5. UC4 Transport Facilities
6. UC5 Transport issues
7. UC6 Public Bicycles
8. UC7 TP Businness/services inside the PT network
9. UC8 Transportation exchange
10. UC9 Fares
11. UC10 Garbage Collection System
12. UC11 Carbon Print Awareness

1 Siguiendo GTFS to Transmodel & UC-1

Facts

Fact	Status	Source (provenance)	SubSource
A `Route` is an ordered list of located `Point`	r	TMv6	NT Route Model
A `Route` defines a single path	r	TMv6	NT Route Model
A `Route` may pass through the same `Point`	r	TMv6	NT Route Model
Different `Route` may pass through the same `Point`	r	TMv6	NT Route Model
A `Line` has a `Start` and an `End`	r	TMv6	NT Route Model
A `Line` has a `StartingPoint`	r	TMv6	NT Route Model
A `Line` has an `EndingPoint`	r	TMv6	NT Route Model
A `Line` goes from the `StartingPoint` to the `EndingPoint`	r	TMv6	NT Route Model
A `Line` goes back from the `EndingPoint` to the `StartingPoint`	r	TMv6	NT Route Model

Competency Questions

Competency Questions	Comments	Source (provenance)
How many `ROUTE` there are from one `point` to another
How many `line` start in the same `StartingPoint`
How many `Route` pass through the same `point`

2 UC1 Accessible Stops

Facts

Facts	Status	Comments	Source (provenance)	SubSource
A `location` has a `location_type` property	r		gtfs	stops.txt
A `location_type` can be a stop (0), station (1), entrance/exit (2), generic node (3) or boarding area (4)	r		gtfs	stops.txt
A `stop` is a `location`	r	location_type=0	gtfs	stops.txt
A `station` is a `location`	r	location_type=1	gtfs	stops.txt
An `entrance/exit` is a `location`	r	location_type=2	gtfs	stops.txt
A `generic node` is a `location`	r	location_type=3	gtfs	stops.txt
A `boarding area` is a `location`	r	location_type=4	gtfs	stops.txt
A `stop` may have a `stop_name`	r	known name of the location. If the location is a boarding area, it should contain the name of the boarding area as displayed by the agency_id	gtfs	stops.txt
A `stop` may have a `stop_desc`	r	description	gtfs	stops.txt
A `station` has a `latitude`	r		gtfs	stops.txt
A `stop` has a `latitude`	r		gtfs	stops.txt
An `entrance/exit` has a `latitude`	r		gtfs	stops.txt
A generic node may have a `latitude`	r		gtfs	stops.txt
A boarding area my have a `latitude`	r		gtfs	stops.txt
A `Stop` has a `longitude`	r		gtfs	stops.txt
A station has a `latitude`	r		gtfs	stops.txt
An entrance/exit has a `latitude`	r		gtfs	stops.txt
A generic node may have a `longitude`	r		gtfs	stops.txt
A boarding area may have a `longitude`	r		gtfs	stops.txt
A `longitude` or a `latitude` are expressed in WGS84	r		gtfs	stops.txt
A `stop` belongs to a `zone_id`	r	required if fare information is provided	gtfs	stops.txt
A `stop` may have a `stop_url`	r		gtfs	stops.txt
A `stop` may have a `parent_station`	r	the id of the `stop_id`	gtfs	stops.txt
An `entrance` may have a `parent_station`	r	the id of the `stop_id`	gtfs	stops.txt
An `exit` may have a `parent_station`	r	the id of the `stop_id`	gtfs	stops.txt
A `boarding area` may have a `parent_station`	r	in this case the field contains the ID of a platform/quay	gtfs	stops.txt
A `station` has not `parent_station`	r		gtfs	stops.txt
A `stop` may have a `stop_timezone`	r		UC1
A `stop_timezone` has a IANA TZ valid code	r		gtfs, UC1	stops.txt
A `StopPlace` may have several wellknown names	r		TMv6
A `Stop` must be accessible	r		UC1
A `stop` has an ID `stop_id`	r		gtfs	stops.txt
A `stop` may have a code, `stop_id`	r		gtfs	stops.txt
A `stop` may have a `stop_id`	r		gtfs	stops.txt
A `stop` may belong to more than one line	r		UC1, gtfs	stops.txt
A `stop` may allow `transfer`	r		gtfs	transfers.txt
A `stop` has an `Entrance`	r		gtfs	stops.txt
An `Entrance` place can be an `Exit` place also	r		gtfs	stops.txt
A `stop` may have a `platform_id`	r	It is a text for a platform stop (a stop belonging to a station)	gtfs	stops.txt
A `Stop` may have several `level`	r	does not indicate how many levels	gtfs	stops.txt
A `level` must have a `level_id`	r		UC1, gtfs	levels.txt, stops.txt
A `level_id` is an `ID`	r		UC1, gtfs	levels.txt, stops.txt
A `level` must have a `level_index`	r		UC1, gtfs	levels.txt, stops.txt
A `level_index` is a `Float`	r		UC1, gtfs	levels.txt, stops.txt
Ground level is 0	r		UC1, gtfs	levels.txt, stops.txt
A `level` may have a `level_name`	r		UC1, gtfs	levels.txt, stops.txt
A `level_name` is a text	r		UC1, gtfs	levels.txt, stops.txt
If `Stop` has levels there must be electric chairs	r		UC1
If a `Stop` have levels there must be elevators	r		UC1
An Elevator/electric stair may work or not (state)	r		UC1
An Elevator/electric stair must update its state when it changes	r		UC1
Elevators and electric stairs must interconnect Entrance with Mezannine	r		UC1
Elevators and electric stairs must interconnect Mezannine with quays	r		UC1
Wheel chairs or baby buggies are not allowed in electric chairs	r		UC1
A `Stop` must have information/s panel/s	r		UC1
One information panel must be at the Entrancy	r		UC1
An information panel must be at the quay	r		UC1
Information panels must show the state of services in the station, including PT	r		UC1
Lift car dimmensions are sufficient for a wheelchair user and their companion	g		netex part1
The lift has audible announcements	r		netex part1
The lift has an emergency alarm button in easy reach for all users	r		netex part1
The steps must have handrails	r		netex part1
The `PTS` has an `Access`	g		TMv6	CC Generic Place Model
A `Place` can be an `Access`	r		TMv6	CC Generic Place Model
An `AccessEnd` is an `Access`	r		TMv6	CC Generic Place Model
A `Point` can be an `AccessEnd`	r		TMv6	CC Generic Place Model
A `PlaceSign` is a sign withe the name of a `Place` on it	g		TMv6	NT Sign Equipment Model
In `Access` people may access or leave PTS	g		TMv6	CC Generic Place Model
In `PTS` there are `Trip`	r		TMv6	CC Generic Place Model
A `Trip` has an `Origin`	r		TMv6	CC Generic Place Model
A `Trip` has a `Destination`	r		TMv6	CC Generic Place Model
A `PTTrip` is part of the `Trip`	r		TMv6	CC Generic Place Model
A `PTTrip` has an `Origin`	r		TMv6	CC Generic Place Model
A `PTTrip` has a `Destination`	r		TMv6	CC Generic Place Model
An `Origin` is a `Place`	r		TMv6	CC Generic Place Model
A `Destination` is a `Place`	r		TMv6	CC Generic Place Model
An `Origin` can be a `ScheduledStopPoint`	r		TMv6	CC Generic Place Model
A `Destination can be a =ScheduledStopPoint`	r		TMv6	CC Generic Place Model
A `Trip` may have an `AccessLink`	r		TMv6	CC Generic Place Model
An `AccessLink` has an `AccessEnd`	r		TMv6	CC Generic Place Model
An `AccessLink` connects the `Origin` of the `Trip` with the `Origin` of the `PTTrip`	g		TMv6	CC Generic Place Model
An `AccessLink` connects the `Destination` of the `Trip` with the `Destination` of the `PTTrip`	g		TMv6	CC Generic Place Model
A `StopPlace` is a `Place`	r		TMv6	NT Stop Place Model
A `Place` may have one or more `Location`	r		TMv6	NT Stop Place Model
A `StopPlaceVehicleEntrance` is a physical entrance or exit to/from a `StopPlace` for a `Vehicle`	g		TMv6	NT Stop Place Model
A `Location` is the position of a `Point` with a reference to a given `LocatingSystem` (e.g. coordinates)	g		TMv6	CC Generic Location Model
A `Point` has a `Position`	r		TMv6	CC Generic Location Model
A `Position` has a `Latitude`	r		TMv6	CC Generic Location Model
A `Position` has a `Longitude`	r		TMv6	CC Generic Location Model
A `LocatingSystem` is the system used as reference for `Location` and graphical representation of the network and other spatial objects	g		TMv6	CC Generic Location Model
A `LocatingSystem` is a `Location`	r		TMv6	CC Generic Location Model
A `Layer` is an user-defined `GroupOfEntity` specified for a particular functional purpose, associating data referring to a particular `LocatingSystem`	g		TMv6	CC Generic Layer Model
A `Layer` is a `GroupOfEntity`	r		TMv6	CC Generic Layer Model
A `Vehicle` may stop at a `StopPlace`	r		TMv6	NT Stop Place Model
A `Passenger` may board at `StopPlace`	r		TMv6	NT Stop Place Model
A `Passenger` may leave vehicle at `StopPlace`	r		TMv6	NT Stop Place Model
A `Passenger` may prepare its trip at a `StopPlace`	r		TMv6	NT Stop Place Model
A `StopPlace` have one or more `WellKnownName`	r		TMv6	NT Stop Place Model
A `StopPlace` may have `StopPlaceComponent`	r		TMv6	NT Stop Place Model
A `StopPlaceComponent` describe parts of the structure of `Stop`	g		TMv6	NT Stop Place Model
A `StopPlaceComponent` share common properties for data management, accessibility and other features	g		TMv6	NT Stop Place Model
A `StopPlace` may have an `AccessSpace`	r		TMv6	NT Stop Place Model
An `AccessSpace` is a passenger area within a `StopPlace` such as a concourse or booking hall, inmigration hall or security area that is accessible by passengers but without a direct access to vehicles.	g		TMv6	NT Stop Place Model
A `StopPlace` may have an `AccessSpace`	r		TMv6	NT Stop Place Model
An `AccessSpace=is a =PassengerArea`	r		TMv6	NT Stop Place Model
A `StopPlace` may have a `Concourse`	r		TMv6	NT Stop Place Model
A `Concourse` is a `PassengerArea`	r		TMv6	NT Stop Place Model
A `StopPlace` may have a `BookingHall`	r		TMv6	NT Stop Place Model
A `BookingHall` is a `PassengerArea`	r		TMv6	NT Stop Place Model
A `StopPlace` may have an `InmigrationHall`	r		TMv6	NT Stop Place Model
An `InmigrationHall` is a `PassengerArea`	r		TMv6	NT Stop Place Model
A `StopPlace` may have a `SecurityArea`	r		TMv6	NT Stop Place Model
a `SecurityArea` is a `PassengerArea`	r		TMv6	NT Stop Place Model
A `StopPlace` may have a `StopPlaceEntrance`	r		TMv6	NT Stop Place Model
A `StopPlaceEntrance` is a physical entrance or exit to/from a `StopPlace`	r		TMv6	NT Stop Place Model
A `StopPlaceEntrance` may be a door, barrier, gate or any other recognizable point of access	g		TMv6	NT Stop Place Model
A `Door` is a `StopPlaceEntrance`	r		TMv6	NT Stop Place Model
A `Barrier` is a `StopPlaceEntrance`	r		TMv6	NT Stop Place Model
An `Gate` is a `StopPlaceEntrance`	r		TMv6	NT Stop Place Model
A `StopPlace` may have a `StopPlaceSpace`	r		TMv6	NT Stop Place Model
A `Quay` is a `StopPlaceSpace`	r		TMv6	NT Stop Place Model
A `Quay` may have a `BoardingPosition`	r		TMv6	NT Stop Place Model
A `Quay` is a place such as a platform, stance, or quayside where a `Passenger` have access to a PT `Vehicle`, `Taxi`, `Car` or other mean of transportation. A `Quay` may serve one or more `VehicleStoppingPlace` and be associated with one or more `ScheduledStopPoint`. A `Quay` may contain other sub `Quay`. A child `Quay` must be phisically contained within its parent `Quay`.	g		TMv6	NT Stop Place Model
A `Platform` is a `Quay`	r		TMv6	NT Stop Place Model
A `Stance` is a `Quay`	r		TMv6	NT Stop Place Model
A `Quayside` is a `Quay`	r		TMv6	NT Stop Place Model
A `Quay` may serve one or more `VehicleStoppingPlace`	r		TMv6	NT Stop Place Model
A `Quay` may be associated with one or more `ScheduledStopPoint`	r		TMv6	NT Stop Place Model
A `Quay` may have sub `Quay`	r		TMv6	NT Stop Place Model
A `BoardingPosition` is a `StopPlaceSpace`	r		TMv6	NT Stop Place Model
A `BoardingPosition` is a `Location` within a `Quay` from which a `Passenger` may directly board, or onto which may directly alight from a `Vehicle`	g		TMv6	NT Stop Place Model
An `Access Space` is a `StopPlaceSpace`	r		TMv6	NT Stop Place Model
An `EquipmentPlace=is a =StopPlaceSpace`	r		TMv6	NT Stop Place Model
A `StopPlaceVehicleEntrance` is an `Entrance`	r	Entrance refers to Entrance and Exit	TMv6	NT Stop Place Model
A `StopPlaceVehicleEntrance` is an `Exit`	r	Entrance refers to Entrance and Exit	TMv6	NT Stop Place Model
A `StopPlace` has an `AccessSpace`	r		TMv6	NT Stop Place Model
A `Room` may be an `AccessSpace`	r		TMv6	NT Stop Place Model
A `Hall` may be an `AccessSpace`	r		TMv6	NT Stop Place Model
A `Concourse` may be an `AccessSpace`	r		TMv6	NT Stop Place Model
A `Corridor` may be an `AccessSpace`	r		TMv6	NT Stop Place Model
A `BoundedOpenSpace` may be an `AccessSpace`	r		TMv6	NT Stop Place Model
An `AccessZone` is a `Zone` for which the duration to cover any `AccessLink` to a particular `ScheduledStopPoint` is the same	g		TMv6	NT Site Model
An `AccessLink` is an `Access`	r	Described in `AccessZone`	TMv6	NT Site Model
An `AlternativeName` is and alternative name for an `Entity`	g		TMv6	CC Alternative Name Model/
An `Entity` is any data instance to be managed in an operational Version Management System. When Several `DataSource` coexist (multimodality and/or interoperability), an `Entity` has to be related to a given `DataSource` in which is defined	g		TMv6	CC Generic Data Model
A `DataInstance` is an `Entity`	r		TMv6	CC Generic Data Model
A `VersionManagementSystem` has once or more `DataInstance`	r		TMv6	CC Generic Data Model
A `DataSource` identifies the system which has produced the data. References to a `DataSource` are useful in an interoperated computer system	g		TMv6	CC Generic Responsability Data Model
A `DataInstance` belongs to a `DataSource`	r		TMv6	CC Generic Entity Model
An `Entity` is defined in a `DataSouce`	r		TMv6	CC Generic Entity Model
An `AlternativeName` is the alternative name of an `Entity`	g		TMv6	CC Alternative Name Model
An `Entity` may have an `AlternativeName`	r		TMv6	CC Alternative Name Model
A `Version` is a group of operational `DataInstances` which share the same `ValidityCondition`. A `Version` belongs to a unique `VersionFrame` and is characterised by a unique `TypeOfVersion`	g		TMv6	CC Generic Version Model
A `Version` is a group of `DataInstance` instances	r		TMv6	CC Generic Version Model
A `DataInstance` may have a `ValidityCondition`	r		TMv6	CC Generic Version Model
A `Version` belongs to a unique `VersionFrame`	r		TMv6	CC Generic Version Model
A `Version` has a unique `TypeOfVersion`	r		TMv6	CC Generic Version Model
A `ResourceFrame` is a set of resource data to which the same `ValidityCondition` have been assigned	g		TMv6	CC Resource Frame Model
A `Trace` is a way to record the context of the changes ocurred in a given `Entity` instance, as regards the authors, the causes of the changes, etc., possibly accompanied by a descriptive text.	g		TMv6	CC Generic Data Model
A `Trace` has an `Author`	r		TMv6	CC Generic Data Model
A `Trace` has a `Description`	r		TMv6	CC Generic Data Model
A `Trace` has a `Commit`	r	Description	TMv6	CC Generic Delta Model
An `EntityInVersion` is the `Entity` associated to a given `Version`	g		TMv6	CC Generic Delta Model
An `EntityInVersion` is an `Entity`	r		TMv6	CC Generic Delta Model
A `Delta` is a record of the detailed changes of a given `EntityInVersion` from one version to the next one. A `Delta` contains pairs of attributes' old values - new values	g		TMv6	CC Generic Delta Model
A `TypeOfVersion` is a classification of `Version`	r		TMv6	CC Generic Version Model
A `VersionFrame` is a set of `Version` referring to a same `DataSource` and belonging to the same `TypeOfFrame`. A `Frame` may be restricted by `ValidityCondition`	g		TMv6	CC Generic Version Frame Model
A `VersionFrame` is a set of `Version`	r		TMv6	CC Generic Version Frame Model
A `VersionFrame` refers to the same `DataSource`	r		TMv6	CC Generic Version Frame Model
A `VersionFrame` belongs to the same `TypeOfFrame`	r		TMv6	CC Generic Version Frame Model
A `TypeOfFrame` may be restricted by a `ValidityCondition`	r	In `VersionFrame` is stated that a `Frame` may be restricted by a `ValidityCondition` but I think it must say `TypeOfFrame` or at least to define `Frame`	TMv6	CC Generic Version Frame Model
A `TypeOfFrame` is a classification of `VersionFrame` according to a common purpose. E.g. line descriptions for line versions, vehicle schedules, operating costs. A type of frame is ruled by a unique `TypeOfValidity`	g		TMv6	CC Generic Version Frame Model
A `TypeOfFrame` is a classification of `VersionFrame`	r		TMv6	CC Generic Version Frame Model
A `TypeOfValidity` is a classification of the validity of `TypeOfFrame`. E.g. frames for schedules designed for `DayType` , for specific `OperatingDay`	g		TMv6	CC Generic Version Frame Model
A `TypeOfFrame` is ruled by `TypeOfValidity`	r		TMv6	CC Generic Version Frame Model
A `TypeOfValidity` is a classification of `TypeOfFrame`	r	A classification of the validity of `TypeOfFrame`	TMv6	CC Generic Version Frame Model
A `ClassInFrame` is a `ClassInRepository` which can be relevant for corresponding `VersionFrame`	g		TMv6	CC Generic Version Frame Model
A `ClassInFrame` is a `ClassInRepository`	r		TMv6	CC Generic Version Frame Model
A `SiteFrame` is a set of `Site` data to which the same `ValidityCondition` have been assigned.	g		TMv6	Site Frame Model
A `ClassInRepository` is any `Entity` name belonging to the `Repository`	g		TMv6	CC Generic Entity Model
A `ClassInRepository` is an `Entity`	r		TMv6	CC Generic Entity Model
A `Repository` is a `DataSource`	r	First time it is mentioned `Repository` and sounds pretty the same as `DataSource` Model	TMv6	CC Generic Entity
A `DayType` is a `ClassInRepository`	r		TMv6	CC Generic Entity Model Class in Repository
A `DayType` is a type of day characterised by one or more properties which affect public transport operation. For example: weekday in school holidays.	g		TMv6	CC Service Calendar Model
A `DayType` is a type of `Day`	r		TMv6	CC Service Calendar Model
An `OrganisationDayType` is a `DayType` that is defined in terms of operation or not of a referenced `ServicedOrganisation`	g		TMv6	CC Additional Organisation Model
An `OrganisationDayType` is a `DayType`	r		TMv6	CC Additional Organisation Model
A `DayTypeAssignment` is the assignment of operational characteristics, expressed by `DayType` to particular `OperatingDay` within a `ServiceCalendar`	g		TMv6	CC Service Calendar Model
An `OperatingDay` is a day of public transport operation of which the characteristics are defined within in a specific ServiceCalendar. An Operating day may last more than 24 hours.	g		TMv6	CC Service Calendar Model
An `OperatingPeriod` is a continous interval of time between two `OperatingDay` which will be used to define validities	g		TMv6	CC Service Calendar Model
A `ServiceCalendar` is a collection of `DayTypeAssignment`	g		TMv6	CC Service Calendar Model
A `ServiceCalendarFrame` is a coherent set of assignments of `OperatingDay` to `DayType`	g		TMv6	CC Service Calendar Frame Model
A `PropertyOfDay` is a `ClassInRepository`	r		TMv6	CC Service Calendar Model
A `PropertyOfDay` is a property which a day may possess, such as school holiday, weekday, summer, winter, etc.	g		TMv6	CC Service Calendar Model
A `PropertyOfDay` is the property of a `DayType`	r	It says Day but I mean `DayType`	TMv6	CC Service Calendar Model
A `PropertyOfDay` is a `ClassInRepository`	r		TMv6	CC Generic Entity Model Class in Repository
A `TimeBand` is a `ClassInRepository`	r		TMv6	CC Service Calendar Model
A `TimeBand` is a period in a day significant for some aspect of public transport, e.g. similar traffic conditions or fare category	g		TMv6	CC Service Calendar Model
A `TimeBand` is a `Period`	r		TMv6	CC Service Calendar Model
A `Period` is an `Interval`	r	Check whether there is an interval or not	W3C Time Ontology
A `VehicleType` is a `ClassInRepository`	r		TMv6	CC Generic Entity Model Class in Repository
A `CrossingEquipment` is the specialisation of `PlaceAccessEquipment` for `CrossingEquipment` (zebra, pedestrian, lights, acoustic device sensor, tactile guide strip, etc.)	g		TMv6	NT Access Equipment Model
A `CrossingEquipment` is a `PlaceAccessEquipment`	r		TMv6	NT Access Equipment Model
A `PlaceAccessEquipment` is the specialisation of `PlaceEquipment` dedicated to `Access` (e.g. lifts, entrances, stairs, ramps, etc.)	r		TMv6	NT Access Equipment Model
A `PlaceAccessEquipment` is a `PlaceEquipment`	r		TMv6	NT Access Equipment Model
A `PlaceAccessEquipment` is located in `Access`	r		TMv6	NT Access Equipment Model
A `PlaceAccessEquipment` can be a lift, entrance, stair, ramp, etc.	r		TMv6	NT Access Equipment Model
A `RoughSurface` is the specialisation of `PlaceEquipment` for rough surfaces, giving properties of surface texture, mainly for impaired person information.	g		TMv6	NT Access Equipment Model
A `QueuingEquipment` is the specialisation of `PlaceAccessEquipment` dedicated to queuing	g		TMv6	NT Access Equipment Model
A `QueuingEquipment` is a `PlaceAccessEquipment`	r		TMv6	NT Access Equipment Model
A `RampEquipment` is a specialisation of `PlaceAccessEquipment` for ramps	g	Provides ramp characteristics like length, gradient, etc.	TMv6	NT Access Equipment Model
A `RampEquipment` is a `PlaceAccessEquipment`	r		TMv6	NT Access Equipment Model
A `LiftEquipment` is the specialisation of `PlaceAccessEquipment` for `Lift`	g	Provides lift characteristics like depth, maximum load, etc.	TMv6	NT Access Equipment Model
A `LiftEquipment` is a `PlaceAccessEquipment`	r		TMv6	NT Access Equipment Model
A `Lift` is a `LiftEquipment`	r		TMv6	NT Access Equipment Model
A `Notice` is a text for informational purposes on exceptions in a `Line, =JourneyPattern`, etc. The information may be usable for `Passenger` or `Driver` information =	g		TMv6	CC Notice Model
A `Notice` is a text	r		TMv6	CC Notice Model
A `NoticeAssignment` is the assignment of a `Notice` showing an exception in a `JourneyPattern`, a `CommonSection` or a `VehicleJourney`, possibly specifying at which `PointInJourneyPattern` the validity of the `Notice` starts and ends respectively.	g		TMv6	NT Notice Assignment Model
A `Notice` may have `NoticeAssignment`	r		TMv6	NT Notice Model
A `DeliveryVariant` is a variant text of a `Notice` for use in a specific media or delivery channel (voice, printed, material, etc.)	g		TMv6	CC Notice Model
A `Notice` may have a `DeliveryVariant`	r		TMv6	CC Notice Model
A `PointInJourneyPattern` is a `ScheduledStopPoint` or `TimingPoint` in a `JourneyPattern` with its order in that `JourneyPattern`	g		TMv6	NT Journey Pattern Model
A `PointInJourneyPattern` is a `Point`	r		TMv6	NT Journey Pattern Model
A `PointInLinkSequence` is a `Point` in a `LinkSequence` indicating its order in that particular `LinkSequence`	g		TMv6	CC Generic Point & Link Sequence Model
A `PointInLinkSequence` is a `Point`	r		TMv6	CC Generic Point & Link Sequence Model
A `LinkSequence` has two or more `PointInLinkSequence`	r		TMv6	CC Generic Point & Link Sequence Model
A `PointOfInterest` is a type of `Place` to or through which `Passenger` may wish to navigate as part of their `Journey` and which is modelled in detail by `Journey` planners	g		TMv6	NT Point Of Interest Model
A `PointOfInterest` is a `Place`	r		TMv6	NT Point Of Interest Model
A `PointOfInterestClassification` is a classification of a `PointOfInterest` that may be used in a `PointOfInterestClassificationHierarchy` to categorise the `Point` by nature of interest using a systematic taxonomy	g	for example Museum, Football, Stadium	TMv6	NT Point Of Interest Model
A `PointOfInterestClassificationHierarchy` is a logical hierarchy for organizing `PointOfInterestClassification`.	g	A `PointOfInterestClassification` can belong to more than one `PointOfInterestClassificationHierarchy`	TMv6	NT Point Of Interest Model
A `PointOfInterestClassificationMembership` is a `PointOfInterestClassification`	r	For example Educational Building, School, Primary School, Cultural	TMv6	NT Point Of Interest Model
A `PointOfInterestComponent` is the specialisation of `SiteComponent` for a component of a `PointOfInterest`	g	Usually used for `PointOfInterestSpace`	TMv6	NT Point Of Interest Model
A `PointOfInterestEntrance` is the specialisation of `Entrance` to enter/exit a `PointOfInterest`	g		TMv6	NT Point Of Interest Model
A `PointOfInterestSpace` is a specialisation of `PointOfInterestComponent` for spaces.	g	A physical area within the `PointOfInterest`, such as a concourse. Check this `Space`	TMv6	NT Point Of Interest Model
A `PointOfInterestVehicleEntrance` is a physical entrace or exit to/from a `PointOfInterest` for `PublicTransporService`	g		TMv6	NT Point Of Interest Model

Competency questions

Competency Questions		Comments	Source (provenance)
<60>		<20>	<20>>
How many stops have elevators in the PT Network?
How many stops have fully accessible elevators?
From this starting point to this ending point, which stops have elevators?
What lifts are working properly now (YYYY-MM-DD)?
What stops have audio information panels?
What's the state of the elecric stairs in the network now (YYYY-MM-DD)?
The `AccessibilityAssessment` are the characteristics of an entity used by passengers such as a `StopPlace` or a `StopPlaceComponent`. Described by `AccessibilityLimitations` and/or a set of suitabilities.		CC Generic Accessibility Model	TMv6
The `AccessibilityLimitation` is a categorisation of the accessibility characteristics of a `Site` to indicate its usability by passengers with specific needs	g	for example, those needing wheelchair access, step-free access or wanting to avoid confined spaces such as lifts. \\ A small number of well-defined categories are used that are chosen to allow the consistent capture of data and the efficient computation of routes for different classes of user.	TMv6 CC Generic Accessibility Model
A `WheelchairVehicleEquipment` is the specialisation for wheel chair accessibility on board a `Vehicle` providing information such as the number of wheel chair areas and the access dimmensions.	g		CC Vehicle Passenger Equipment Model
A `WheelchairVehicleEquipment` is a `VehicleEquipment`	r		CC Vehicle Passenger Equipment Model
A `WheelchairVehicleEquipment` has a number of wheel chair available	r		CC Vehicle Passenger Equipment Model
A `WheelchairVehicleEquipment` has an access dimmensions	r		CC Vehicle Passenger Equipment Model
The `TypeOfAccessibilityTools` is a classification for `AccessibilityTool` used by or available from `AssistanceService`	g	e.g. wheelchair, walking stick, audio navigator, visual navigator, etc.	TMv6 NT Local Service Equipment Model
A `TypeOfActivation` is a classification of real-time processes that are activated when vehicles passes an `ActivationPoint` or an `ActivationLink`	g		NT Activation Model
A `TypeOfAssistanceService` is a classification of `AssistanceService`	g	e.g. boarding assistance, onboard assistance, porterage,foreign language, sign language translation, etc.	NT Local Service Equipment Model
A `TypeOfBoardingPosition` is a classification of `BoardingPosition`	g		NT Stop Place Model
A `TypeOfCateringService` is a classification of `CateringService`	g	e.g. beverage vending machine, buffet, food vending machine, restaurant, snacks, torlley service, no beverages available, no food available.	NT Local Commercial Service Model
A `TypeOfCheckConstraint` is a classification of `CheckConstraint`	g	e.g. a ticket collection, ticket purchase, baggage check-in, incoming customs, outgoing customs, tax refunds, etc.	NT Check Constraint Model
A `TypeOfCommunicationService` is a classification of `CommunicationService`	g	e.g. free wifi, public wifi, phone, movile coverage, internet, video entertainment, audio entertainment, post box, post office, business services	NT Local Commercial Service Model
A `TypeOfCongestion` is a typology of congestions resulting from `CheckConstraint`	g	e.g. no waiting, queue, crowding, full	NT Check Constraint Model
A `TypeOfCoupling` is a classification for `Coupling` of `BlockPart`	g		TI Coupled Journey Model
A `TypeOfCycleStorageEquipment` is a classification of `CycleStorageEquipment`	g	e.g. racks, bars, railings, etc.	NT Parking Equipment Model
A `TypeOfDeliveryVariant` is a classification of a `DeliveryVariant`	g	The way of delivering a `Notice`: by vocal announcement, by visual display, issuing printed material	CC Notice Model
A `TypeOfDirectionOfUse` is the direction in which `Equipment` can be used	g	e.g. up, down, level, one way, both way, etc.	NT Access Equipment Model
A `TypeOfEmergencyService` is a typology of emergency services	g	e.g. police, first aid, sos point, cctv
A `TypeOfEntity` is a classification of `Entity`	g	for instance according to the domain in which they are defined or used.	CC Generic Entity Model
A `TypeOfFacility` is a classification of a `Facility` or a `FacilitySet`.	g		CC Facility Model
A `TypeOfFareClass` is a classification for fare classes	g	e.g. first class, second class, business class, etc.	CC Service Restriction Model
A `TypeOfFlexibleService` is a typology of flexibles `Service`.	g	The type of flexibiliity can be defined at `JourneyPattern` level or at `PointInJourneyPattern` level in case of mixed types of flexible service inside the same `JourneyPattern`. \\ - Virtual line service; \\ - flexible service with main route; \\ - corridor service; \\ - fixed stop area-wide flexible service; \\ mixed types of flexible service (not at `Point` level) ;	TI Flexible Service Model
A `TypeOfFrame` is a classification of `VersionFrame` according to a common purpose.	g	e.g. line descriptions for line versions, vehicle schedules, operating costs; \\ A `TypeOfFrame` is ruled by a unique `TypeOfValidity`.	CC Generic Version Frame Model
A `TypeOfGenderLimitation` is a classification for `GenderLimitation`	g	Mainly for `SanitaryEquipment`, e.g. male only, female only, both.	NT Passenger Service Equipment Model
A `TypeOfHandrail` is a classification of `Handrail`	g	e.g. one side, both sides	NT Stair Equipment Model
A `TypeOfHireService` is a classification of `HireService`	g	e.g. car hire, motor cycle hire, cycle hire, recreational device hire	NT Local Commercial Service Model
A `TypeOfJourneyPattern` is a classification of `JourneyPattern` used to distinguish other categories of `JourneyPattern` than `ServiceJourneyPattern` and `DeadRunPattern`	g		NT Journey Pattern Model
A `TypeOfLine` is a classification of `Line`	g		NT Route Model
A `TypeOfLink` is a classification of `Link` to express the different functional roles of `Link`.	g		CC Generic Point & Link Model
A `TypeOfLinkSequence` is a classification of `LinkSequence` used to define the different functions a `LinkSequence` may be used for	g	e.g. `Route`, road, border line, etc.	CC Generic Point & Link Sequence Model
A `TypeOfLocalService` is a generic abstract classification of `LocalService`	g		NT Local Service Equipment Model
A `TypeOfLuggageLocker` is a classification for `LuggageLockerEquipment`	g	e.g. left luggage, lockers, bike carriage, porterage, free trolleys, pais trolleys, etc.	NT Site Equipment Model
A `TypeOfMoneyService` is a classification of `MoneyService`	g	e.g. cash machine, bank, insurance, bureau of change	NT Local Commercial Service Model
A `TypeOfNotice` is a classification for `Notice`	g		CC Notice Model
A `TypeOfOperation` is a classification of `Operation` to express the different fuctional roles of a department	g		CC Generic Organisation Model
A `TypeOfOrganisation` is a classification for `Organisation` according to their activity	g	e.g. public transport company, an IT company, etc.	CC Generic Organisation Model
A `TypeOfPassage` is a classification for spaces to express how the space can be used as a passage	g	e.g. pathway, corridor, overpass, underpass, tunnel, etc.	NT Stop Place Model
A `TypeOfPassengerInformationEquipment` is a classification for `PassengerInformationEquipment`	g	e.g. next stop indicator, stop announcements, passenger information facility	NT Passenger Information Display Assignment Model
A `TypeOfPaymentMethod` is a classification for payment method	g	e.g. cash, credit card, debit card, travel card, contactless travel card, mobile phone, token, etc.	CC Service Restriction Model
A `TypeOfPlace` is a classification for `Place`	g		CC Generic Place Model
A `TypeOfPoint` is a classification of `Point` according to their functional purpose	g		CC Generic Point & Link Model
A `TypeOfPointOfInterestSpace` is a classification for `PointOfInterestSpace`	g		NT Point Of Interest Model
A `TypeOfProductCategory` is a classification for `VehicleJourney` to express some common properties of journeys for marketing and fare products	g		TI Vehicle Journey Model
A `TypeOfQuay` is a classification for `Quay`	g		NT Stop Place Model
A `TypeOfRelationToVehicle` is a classification of the way a `VehicleStoppingPosition` is used	g	e.g. front left, front right, back left, driver left, driver right.	NT Vehicle Stopping Model
A `TypeOfResponsabilityRole` is a classification of `ResponsabilityRole`	g	e.g. data ownership	CC Responsability Role Model
A `TypeOfRetailService` is a classification of `RetailService`	g	e.g. food, newspaper, tobacco, health hygiene, beauty, fashion accessories, bank finance insurance, tourism, photo booth	NT Local Commercial Service Model
A `TypeOfSanitaryFacility` is a classification for `SanitaryEquipment`	g	e.g. a toilet, wheelchair access toilet, shower, baby change, wheelchair baby change	NT Passenger Service Equipment Model
A `TypeOfSeatingEquipment` is the classification of `SeatingEquipment`	g		NT Site Equipment Model
A `TypeOfServiceNature` is a classification for service available for a `CheckConstraint`	g	e.g. serlf-service machine, counter service.	NT Check Constraint Model
A `TypeOfShelter` is a classification for `ShelterEquipment`	g	It mentions `Shelter` instead of `ShelterEquipment`	NT Site Equipment Model
A `TypeOfStopPlace` is a classification for `StopPlace`	g	e.g. simple, complex, multimodal	NT Stop Place Model
A `TypeOfStopPoint` is a classification of `ScheduledStopPoint` used for instance to characterize the equipment to be installed at `Stops`	g	e.g. post, shelter, seats, etc.	NT Service Pattern Model
A `TypeOfSuitability` is a classification for `Suitability`	g	i.e. assessments as regards a possible `Suitability` of `Access` acording `UserNeed`	CC Generic Accessibility Model
A `TypeOfSurface` is a classification for `RoughSurface` types	g		NT Access Equipment Model
A `TypeOfTicket` is a classification for tickets available at a `TicketingEquipment` g	g	e.g. standard, concession, promotion, group, season, travel card, etc.	CC Service Restriction Model
A `TypeOfTrafficControlPoint` is a classification of `TrafficControlPoint`	g		NT Activation Model
A `TypeOfTrainElement` is a classification of `TrainElement`	g		CC Train Model
A `TypeOfTransfer` is a classification of `Transfer`	g		CC Generic Place Model
A `TypeOfUserNeed` is a classification of `UserNeed`	g		CC Generic Accessibility Model
A `TypeOfWaitingRoom` is a classification of `WaitingRoomEquipment`	g		NT Site Equipment Model

3 UC2 Accesible coaches

Facts

Fact/Competency Question	Status	Comments	Source (provenance)	SubSource
A coach must be accessible	r		UC2
A coach must have an Entrance accessible	r		UC2
A coach must have an Exit accessible	r		UC2
A coach has/have reserved seats for people with dissabilities or functionally diverse	r		UC2
A coach must have reserved seats for people carrying a wheelchair or a baby buggy	r		UC2
Every reserved seat must have a sensor with the states free/busy	r		UC2
The sensor must be updated everytime it changes.	r		UC2
The status of the sensor must be recorded	r		UC2
a `trip` may have a `wheelchair_accessible`	r	Values for `wheelchair_accessible`: 0, no information available; 1, one seat at least; 2, not availabe	gtfs trips.txt
An `EncumbranceNeed` is a specific `UserNeed`	g	i.e. a requirement of a `Passenger` travelling with luggage, animal or any other object requiring special arrangements to access `PublicTransport`	TMv6	CC generic Accessibility Model
An `EncumbranceNeed` is an `UserNeed`	r		TMv6	CC generic Accessibility Model
A `UserNeed` is a user's need for a particular `Suitability`	r		TMv6	CC generic Accessibility Model
A `Suitability` is a statement of whether a particular `UserNeed` can be met. It can be used to state wheter a site can be accessed by a passenget with a particular `UserNeed`	g		TMv6	CC Generic Accessibility Model
A `Passenger` may have one or more `UserNeed`	r		TMv6	CC Generic Accessibility Model
A `MedicalNeed=is a specific =UserNeed`	g	i.e. a requirement of a `Passenger` as regards medical constraint (e.g. allergy) to access `PublicTransport`	TMv6	CC Generic Accessibility Model
A `MedicalNeed` is a `UserNeed`	r		TMv6	CC Generic Accessibility Model
A `MobilityNeed` is a specific `UserNeed`	g	i.e a constraint of a `Passenger` as regards his mobility, e.g. wheelchair, assisted wheelchair…	TMv6	CC Generic Accessibility Model
A `MobilityNeed` is a `UserNeed`	r		TMv6	CC Generic Accessibility Model
A `PsychosensoryNeed` is a specific `UserNeed`	g	i.e. a constraint of a passenger as regards his psycho-sensory impairments, such as visual impairment, auditory impairment, averse to confined spaces…	TMv6	CC Generic Accessibility Model
An `Entrance` is the physical `Entrance` or `Exit` to/from a `Site`. May be a door, barrier, gate, revolving door or other recognizable `Point` of `Access`	g		TMv6	NT Site Model
An `Entrance` is a `Place`	r		TMv6	NT Site Model
An `EntranceEquipment` is a specialisation of `PlaceAccessEquipment` for `Entrance`	g		TMv6	NT Access Equipment Model
An `EntranceEquipment` is a `PlaceAccessEquipment`	r		TMv6	NT Access Equipment Model
An `EquipmentPlace` is a `SiteComponent` containing `Equipment`	g		TMv6	NT Place Equipment Location Model
An `EquipmentPlace` is an `SiteComponent`	r		TMv6	NT Place Equipment Location Model
A `SiteComponent` may have `EquipmentPlace`	r		TMv6	NT Place Equipment Location Model
An `EquipmentPosition` is the location of the `EquipmentPlace`	r		TMv6, NeTEx Part 1 v29	NT Place Equipment Location Model
An `EscalatorEquipment` of `StairEquipment` for `Escalator`	g		TMv6	NT Place Equipment Location Model
An `EscalatorEquipment` is a `StairEquipment`	r		TMv6	NT Place Equipment Location Model
A `StairEquipment` is the specialisation of `PlaceAccessEquipment` for `Stairs`	g		TMv6	NT Stair Equipment Model
A `Stair` can be a stair, escalator, staircase, etc.	r		TMv6	NT Stair Equipment Model
A `StairEquipment=is a =PlaceAccessEquipment`	r		TMv6	NT Stair Equipment Model
A `StairCaseEquipment` is the specialisation of `StairEquipment` for staircases.	g		TMv6	NT Stair Equipment Model
A `StairCaseEquipment` is a `StairEquipment`	r		TMv6	NT Stair Equipment Model
A `TravelatorEquipment` is a specialisation of `PlaceAccessEquipment` for travelators	g	Provides travelator properties like speed	TMv6	NT Stair Equipment Model
A `SiteFacilitySet` is a set of `Facility` available for a `SiteElement`	g		TMv6	CC Facility Model
A `SiteFacilitySet` have two or more `Facility`	r		TMv6	CC Facility Model
A `SiteElement` may have a `SiteFacilitySet`	r		TMv6	CC Facility Model
A `Facility` is a named amenity availabe for the public at a `Site` or on a `Service`. A `Facility` has no further properties other than a name. An `Equipment` or `LocalService` is used to describe the further properties provided as part of a particular `Facility`	g		TMv6	CC Facility Model
A `Passenger` can use a `Facility`	r		TMv6	CC Facility Model
An `Equipment` must have a `Facility`	r		TMv6	CC Facility Model
A `FacilityRequirement` is a classification of `PublicTransportVehicle` according to the facilities available on the `Vehicle`	g		TMv6	CC Vehicle Type Model
A `FacilityRequirement` is a classification of `PublicTransportVehicle`	r		TMv6	CC Vehicle Type Model
A `FacilitySet` is a set of `Facility` available for a `ServiceJourney` or a `JourneyPart`.	g		TMv6	CC Facility Model. The set may be available only for a specific `VehicleType` within the `Service`
A `ServiceJourney` may have a `FacilitySet`	r		TMv6	CC Vehicle Type Model
A `JourneyPart` may have a `FacilitySet`	r		TMv6	CC Vehicle Type Model
A `ServiceFacilitySet=is a set of =Facility` available for specific `VehicleType` possibly only for a `Service`	g	e.g. carriage equipped with low floor\\ service as `ServiceJourney` or `Journey`	TMv6	CC Vehicle Type Model
A `Journey` is a `Service` =	r		TMv6	CC Vehicle Type Model
A `ServiceJourney` is a `Service`	r		TMv6	CC Vehicle Type Model
A `ServiceFacilitySet` is a set of `Facility`	r		TMv6	CC Vehicle Type Model
A `ServiceFrame` is a set of `Network` `Service` `Data` to which the same `ValidityCondition` has been assigned	g	and other data logically related to these	TMv6	Service Frame Model
A `ServiceFrame` is `Data`	c		TMv6	Service Frame Model

Competency Questions

Fact/Competency Question Comments Source (provenance)

4 UC3 Public WC/Restrooms at Stops

Facts

Facts	Status	Source (provenance)
A `Stop` may have a WC	r	UC3
A `Stop` may have a restroom	r	UC3
A `WC` must have a changing table (baby changing facilities)	r	UC3
A `WC` must be unisex fully accessible	r	UC3
A `Stop` may have a lactation room	r	UC3
A `WC` may have a potty.	r	UC3
A WC must have baby cnag	r	UC3
The accessible WC doors are not automatic	r	UC3
The toilets must have locks.	r	UC3
The toilets must have an alarm key	r	UC3

Competency Questions

Facts Comments Source (provenance)

5 UC4 Transport Facilities

Facts

Facts	Status	Comments	Source (provenance)	SubSource
A `passenger` plans a `trip`	r	passenger is named in gtfs stops.txt and gtfs pathways.txt; trip is named in the name of trips.txt	UC4
A `trip` follows a `route`	r	route id in the name of gtfs routes.txt	UC4
A `Mean` has one or more `VehicleJourney`	r	A `Mean` is quoted in `VehicleMode`	TMv6
A `VehicleMode` is a characterisation of the public transport operation according to the means of transport (bus, tram, metro, train, ferry, ship)	g		TMv6	CC Transport Mode Model
A `VehicleMode` is a characterisation of the `PublicTransportOperation`	r		TMv6	CC Transport Mode Model
A `PublicTransportOperator` is an `Operator`	r		TMv6	CC Transport Mode Model
An `Operator` is a `Company` providing `PublicTransporService`	g		TMv6	CC Transport Organisation Model
A `Bus` is a `MeanOfTransport`	r		TMv6	CC Transport Mode Model
A `Tram` a `MeanOfTransport`	r		TMv6	CC Transport Mode Model
A `Metro` is a `MeanOfTransport`	r		TMv6	CC Transport Mode Model
A `Train` is a `MeanOfTransport`	r		TMv6	CC Transport Mode Model
A `Ferry` is a `MeanOfTransport`	r		TMv6	CC Transport Mode Model
A `Ship` is a `MeanOfTransport`	r		TMv6	CC Transport Mode Model
A `VehicleJourney` is the planned movement of a `PublicTransportVehicle` on a `DayType` from the `StartPoint` to the `EndPoint` of a `JourneyPattern` on a specified `Route`	g		TMv6	TI Vehicle Journey Model
A `PublicTransportVehicle` is a `Vehicle`	r		TMv6	TI Vehicle Type Model
A `VehicleJourney` has a `StartPoint`	r		TMv6	TI Vehicle Type Model
A `TemplateServiceJourney` is a `Passenger` carrying `TemplateServiceJourney`	g	It may represent multiple `Journey`	TMv6	TI Service Journey Model
A `TemplateServiceJourney` is ruled by a `Passenger`	r		TMv6	TI Service Journey Model
A `Journey` may have a `TemplateServiceJourney`	r		TMv6	TI Service Journey Model
A `TemplateServiceJourney` can be shared by two or more `Journey`	r		TMv6	TI Service Journey Model
A `TemplateVehicleJourney` is a repeating `VehicleJourney` for which a frequency has been specified, either as a `HeadwayJourneyGroup` or a `RhythmicalJourneyGroup`	g	It may thus represent multiple journeys	TMv6	TI Service Journey Model
A `VehicleJourney` can have a `TemplateVehicleJourney`	r		TMv6	TI Service Journey Model
A `HeadwayJourneyGroup` is a `TemplateVehicleJourney`	r		TMv6	TI Service Journey Model
A `RhythmicalJourneyGroup` is a `TemplateVehicleJourney`	r		TMv6	TI Service Journey Model
A `Trip` has an `Origin`	r	A `Trip` is not defined in TMv6 but is quoted in `Access` as "origin of the trip"	TMv6	TI Service Journey Model
A `VehicleJourney` has an `EndPoint`	r	An `EndPoint` is quoted in `VehicleJourney`	TMv6	TI Service Journey Model
A `Trip` has an `Destination`	r	A `Trip` is not defined in TMv6 but is quoted in `Access` as "destination of the trip"	TMv6	TI Service Journey Model
A `RhythmicalJourneyGroup` is a group of `VehicleJourney` following the same `JourneyPattern` having the same rhyth	g	Every hour between a specified start and end time	TMv6	TI Vehicle Journey Times Model
A passenger takes a mean of transport	r		UC4
A trip has a begining	r		UC4
A trip has an end	r		UC4
A passenger may exchanges means of transport in stops	r		UC4
A passenger gets into a coach	r		UC4
A passenger gets off the coach	r		UC4
A sensor determines when a passenger takes off the coach	r		UC4
A coach has a way to calc the amount of passengers travelling	r		UC4
The number of passengers in the coach is updated every time it changes	r		UC4
A coach may have a dedicated place to bring the bicycle	r	bicycleReservationsCompulsory	UC4
A `Trip` may have a `bikes_allowed` property	r		gtfs	trips.txt
A `bikes_allowed` property have one value (0-2)	r	- 0, empty;\\ - 1, at least one bicycle;\\ - 2, no bicycles allowed	UC4
A stop may have a place to park the bicycle	r		UC4
A coach may have a WC	r		UC4
The WC of the coach must have a location	r		UC4
The WC of the coach have a state (free/busy)	r		UC4
The state of the WC is spread in the information system	r		UC4
A Stop may have a security locker area	r		UC4
a Stop may have a shop area	r		UC4
A shop area has a location	r		UC4
A shop area has a schedule	r		UC4
The information of the shop area is in the public information service	r		UC4
A shop has types of facilities (PassengerCommsFacilities)	r		NeTEx part 1
A communication service as the post office belongs to a classification of communication services	r		NeTEx part 1	page 41
A commercial service is classified as hire, money, retail, refreshments or communication services	r		NeTEx part 1	page 797
A type of refreshment service is part of a local commercial Service	r		NeTEx part 1	page 44
A Stop may have a park&ride parking	r		UC4
A park&ride parking is a type of ParkingTypeEnum	r		NeTEx part 1	page 867
A `Zone` is a two-dimensional (dimension 2) `Place` within the `ServiceArea` of a `PublicTransportOperator` (`AdministrativeZone`, `TariffZone`, `AccessZone`, etc.)	g		TMv6	CC Generic Zone and Feature Model
A `ServiceArea` may have a `Zone`	r		TMv6	CC Generic Zone and Feature Model
A `ComplexFeature` is an aggregate of `SimpleFeature` and other `ComplexFeature`	g		TMv6	CC Generic Zone and Feature Model
A `ComplexFeature` has two or more `SimpleFeature`	r		TMv6	CC Generic Zone and Feature Model
A `ComplexFeature` may have one or more `ComplexFeature`	r		TMv6	CC Generic Zone and Feature Model
A `ComplexFeatureProjection` is an oriented correspondence from one `ComplexFeature` in the source layer, onto an `Entity` in a target layer: e.g. `Point`, `ComplexFeature`, within a defined `TypeOfProjection`	g		TMv6	CC Generic Projection Model
A `TypeOfProjection` is a classification of the projections according to their functional purpose, the source and target layers	g		TMv6	CC Generic Projection Model
A `TypeOfProjection` may have a functional purpose	r		TMv6	CC Generic Projection Model
A `TypeOfProjection` may have a source	r		TMv6	CC Generic Projection Model
A `TypeOfProjection` may have target layers	r		TMv6	CC Generic Projection Model
A `PointProjection` is an oreinted correspondence form one `Point` of a source layer onto a `Entity` in a target layer.	g	e.g. `Point`, `Link`, `LinkSequence`, `ComplexFeature`, within a defined `TypeOf`	TMv6	CC Generic Projection Model
A `SimpleFeature` is an abstract representation of `ElementaryObject` related to the spatial representation of the `Network`.	g	- A `Point` (0-dimensional object);\\ - `Link` (1-dimensional object); \\ - and `Zone` (2-dimensional object). CC Generic Zone and Feature Model	TMv6	CC Generic Projection Model
A `SimpleFeature` is an `ElementaryObject`	r		TMv6	CC Generic Zone and Feature Model
A `Point` is an `ElementaryObject`	r		TMv6	CC Generic Zone and Feature Model
A `Link` is an `ElementaryObject`	r		TMv6	CC Generic Zone and Feature Model
A `Zone` is an `ElementaryObject`	r		TMv6	CC Generic Zone and Feature Model
A `Network` is a named grouping of `Line` under which a `TransportNetwork` is known.	g		TMv6	NT Route Model
A `Network` has 2 or more `Line`	r		TMv6	NT Route Model
A `TransportNetwork` is a `Network`	r		TMv6	NT Route Model
An `OvertakingPossibility` is a `NetworkRestriction` specifying a `Point` or a `Link` where `Vehicle` of specified `VehicleType` are or are not allowed to overtake each other	g		TMv6	NT Network Restriction Model
A `Vehicle` may have an `OvertakingPossibility`	r		TMv6	NT Network Restriction Model
A `VehicleType` may have an `OvertakingPossibility`	r		TMv6	NT Network Restriction Model
A `Place` is a `GeographicPlace` of any type which may be specified as the `Origin` or `Destination` of a `Trip`	g		TMv6	CC Generic Place Model
A `Place` may be represented as a `Point` (dimension 0), a `RoadSection` (dimension 1) or a `Zone` (dimension 2)	g		TMv6	CC Generic Place Model
A `Site` is a `Place`	r		TMv6	NT Site Model
A `Site` is a well-known `Place` to which a `Passenger` may refer to indicate the `Origin` or a `Destination` of a `Trip`	g		TMv6	NT Site Model
A `ServiceSite` is a sub-type of `Site` other than a `Operator` which is of specific interest for the `Operator`	g		TMv6	NT Site Model
A `Level` is an identified storey within an interchange building or `Site` on which `SiteComponent` reside	g	A `PathLink` may connect components on different `Level` \\ A storey can be: ground, first, basement, mezzanine, etc.	TMv6	NT Site Model
A `PathLink` is a link within a `Place` or between two `Place` that represents a step in a possible route for pedestrians, cyclists or other out-of-vehicle passengers	g	It is possible but not mandatory that a `PathLink` projects onto a more detailed set of infrastructure or mapping links that plot the spatial course, allowing it to be represented on maps and to tracking systems	TMv6	NT Path & Navigation Path Model
A `PathLinkEnd` is the beginning or end `Site` for a `PathLink`	g	May be linked to a specific `Level` of the `Site`	TMv6	NT Path & Navigation Path Model
A `PathLinkInSequence` is a step of a `NavigationPath` indicating traversal of a particular `PathLink` as part of a recommended `Route`.	g	The same `PathLink` may ocurr in different sequences in different `NavigationPath`	TMv6	NT Path & Navigation Path Model
A `PathJunction` is a designated `Point`, inside or outside of a `StopPlace` or `PointOfInterest` at which to or more `PathLink` may connect or branch.	g		TMv6	NT Path & Navigation Path Model
A `NavigationPath` is a designated `Path` between two `Place`	g	May include an ordered sequence of `PathLink`	TMv6	NT Path & Navigation Path Model
A `NavigationPathAssignment` is the allocation of a `NavigationPath` to a specific `StopPointAssignment`	g	For example to indicate the path to be taken to make a `Connection`	TMv6	NT Path Assignment Model
A `PlaceInSequence` is a `Point` traversed by a `NavigationPath` in sequence, connected by a `PathLink` to the next `Point`. May be a `Place`, `PathJunction` or `Point`.	g		TMv6	NT Path Assignment Model
A `PlaceLigthing` is a specialisation of `PlaceEquipment` for `LightingEquipment`	g	e.g. lamp post	TMv6	NT Access Equipment Model
A `PlaceLighting` is a `PlaceEquipment`	r		TMv6	NT Access Equipment Model
A `LightingEquipment` has a `PlaceLighting`	r		TMv6	NT Access Equipment Model
A `Site` may have one or more `Level`	r		TMv6	NT Site Model
A `Site` may have one or more `SiteComponent`	r		TMv6	NT Site Model
A `SiteComponent` reside on a `Site`	r		TMv6	NT Site Model
The `Accomodation` is the set of characteristics available on a `Service`	g		TMv6	CC Facility Model
An `ActivatedEquipment` is a state of the `Equipment`	r		TMv6	NT Activation Model
An `ActivationPoint` is a `Point` where a control process is activated	r		TMv6	NT Activation Model
An `ActivationLink` is a `Link` where a control process is activated	g		TMv6	NT Activation Model
A `Link` is an oriented spatial object of dimension 1 with view to the overall description of a network describing a connection between two points	g		TMv6	CC Generic Point & Link Model
A `Link` has a `LinkSequence`	r		TMv6	CC Generic Point & Link Sequence Model
An `ActualVehicleEquipment` is an `Item`	r		TMv6	CC Actual Vehicle Equipment
An `ActualVehicleEquipment` is an `Item` of `Equipment` of a particular type in an individual `Vehicle`	g		TMv6	CC Actual Vehicle Equipment
A `Vehicle` has an `ActualVehicleEquipment`	r		TMv6	CC Actual Vehicle Equipment
A `Equipment` has an `Item`	r		TMv6	CC Actual Vehicle Equipment
A `Vehicle` carries `Passenger`	r		TMv6	CC Vehicle Type Model
A `PurposeOfEquipmentProfile` is a functional purpose which requires a certain set of equipment of different types put together in a `VehicleEquipmentProfile`	g		TMv6	CC Vehicle Type Model
A `VehicleEquipmentProfile` is each instantiation of this entity which gives the number of items of one `TypeOfEquipment` a `VehicleModel` should contain for a given `PurposeOfEquipmentProfile`	g	The set of instantiations for one `VehicleModel` and one purpose gives one complete profile.	TMv6	CC Vehicle Type Model
A `TypeOfEquipment` is a classification of `Equipment` to be installed at `StopPlace` or `Vehicle`	g		TMv6	CC Generic Equipment Model
A `DestinationDisplay` is an advertised destination of a specific `JourneyPattern`, usually displayed on a `HeadingSign` or at other on-board locations	g		TMv6	NT Route Model
A `JourneyPattern` may have a `DestinationDisplay`	r		TMv6	NT Route Model
A `JourneyPattern` may have a `DestinationDisplayVariant`	r		TMv6	NT Route Model
A `DestinationDisplayVariant` is an advertised destination of a specific `JourneyPattern`, usually displayed on a `HeadingSign` or at other on-board locations	g		TMv6	NT Route Model
A `DestinationDisplay` is usually displayed on a `HeadingSign`	r		TMv6	NT Route Model
A `DestinationDisplayVairant` is usually displayed on a `HeadingSign`	r		TMv6	NT Route Model
A `DisplayAssignment` is the assignment of one `ScheduledStopPoint` and one `JourneyPattern` to a `PassengerInformationEquipment` specifiying that information on the `ScheduledStopPoint` and the `JourneyPattern` wil be provided (e.g. displayed, printed)	g		TMv6	NT Passenger Information Display Assignment Model
A `PassengerInformationEquipment` has a `DisplayAssignment`	r		TMv6	NT Passenger Information Display Assignment Model
A `PassengerInformationEquipment` is a public transport information piece of `Equipment`, as for instance terminals (on street, at information desks, telematic, etc.) or printed material (leaflets displayed at stops, booklets…)	g		TMv6	NT Passenger Information Display Assignment Model
A `PassengerInformationEquipment` is an `Equipment`	r		TMv6	NT Passenger Information Display Assignment Model
An `InformationDesk` is a `PassengerInformationEquipment`	r		TMv6	NT Passenger Information Display Assignment Model
A `StreetDesk` is a `PassengerInformationEquipment`	r		TMv6	NT Passenger Information Display Assignment Model
A `VirtualDesk` is a `PassengerInformationEquipment`	r		TMv6	NT Passenger Information Display Assignment Model
A `Leaflet` is a `PassengerInformationEquipment`	r		TMv6	NT Passenger Information Display Assignment Model
A `Booklet` is a `PassengerInformationEquipment`	r		TMv6	NT Passenger Information Display Assignment Model
A `LogicalDisplay` is a set of data than can be assembled for assignment to a physical `PassengerInformationEquipment` or to a logical channel such as web or media.	g	It is independent of any physical embodiment	TMv6	NT Passenger Information Display Assignment Model
A `LogicalDisplay` is a set of data	r		TMv6	NT Passenger Information Display Assignment Model
A `LogicalDisplay` may have a set of `DisplayAssignment`	g		TMv6	NT Passenger Information Display Assignment Model
A `LogicalDisplay` corresponds to a `SiriStopMonitoringPoint`	g		TMv6	NT Passenger Information Display Assignment Model
A `PassengerInformationEquipment` displays `LogicalDisplay`	g		TMv6	NT Passenger Information Display Assignment Model
A `DynamicStopAssignment` is the dynamic association of a `ScheduledStopPoint` with the next available `StopPlace`, `Quay` or `BoardingPosition` within a `StopPlace`	g		TMv6	NT Stop Assignment Model
A `StopAssignment` is the allocation of a `ScheduledStopPoint` to a specific `StopPlace` for either `ServiceJourney` or `VehicleService`	g		TMv6	NT Stop Assignment Model
A `VehicleService` is a `Workplan` for a `Vehicle` for a whole day planned for a specific `DayType`	g		TMv6	TI Vehicle Service Model
A `Workplan` is a plan	r		TMv6	TI Vehicle Service Model
A `HeadingSign` is the specialisation of `SignEquipment` for headings providing information like `DirectionName`, `LineName`, etc.	g		TMv6	NT Sign Equipment Model
A `HeadingSign` is a `SignEquipment`	r		TMv6	NT Sign Equipment Model
A `SignEquipment` is the specialisation of `PlaceEquipment` for `Sign`	g		TMv6	NT Sign Equipment Model
A `PlaceEquipment` is an item of equipment of a particular type actually available at a location within a `Place`	g		TMv6	NT Sign Equipment Model
A `PlaceEquipment` is an `Equipment`	r		TMv6	CC Generic Equipment Model
An `Equipment` is an item of `Equipment` installed either fixed (`PlaceEquipment`) or on-board vehicles (`VehicleEquipment`). A `Service` (`LocalService` such as `LeftLuggage`, `TicketingService` is considered as immaterial `Equipment` as well	g		TMv6	CC Generic Equipment Model
A `VehicleEquipment` is an `Equipment`	r		TMv6	CC Generic Equipment Model
A `SeatingEquipment` is a specialisation of `PlaceEquipment` describing the properties of seating	g		TMv6	NT Site Equipment Model
A `SeatingEquipment` is a `PlaceEquipment`	r		TMv6	NT Site Equipment Model
A `TicketingService` is the specialization of `LocalService` for ticketing, providing ticket counter and online purchase information, also associated with payment method and `TypeOfTicket`	g		TMv6	CC Generic Equipment Model
A `TicketingService` is a `LocalService`	r		TMv6	CC Generic Equipment Model
A `LocalService` is a named service relating the use of the `Site` or transport services at a particular location, for example porterage, assistance for disabled users, booking offices, etc. The service may have a `ValidityCondition` associated with it. A `LocalService` is treated as a form of immaterial `Equipment`	g		TMv6	CC Generic Equipment Model
A `LocalService` is a `Equipment`	r		TMv6	CC Generic Equipment Model
A `Porterage` is a `LocalService`	r		TMv6	CC Generic Equipment Model
A `ShelterEquipment` is the specialisation of `WaitingEquipment` for a shelter	g		TMv6	NT Site Equipment Model
A `ShelterEquipment` is a `WaitingEquipment`	r		TMv6	NT Site Equipment Model
A `WaitingEquipment` is the specialisation of `StopPlaceEquipment` for `WaitingEquipment`	g	e.g. shelter, waiting room, etc.	TMv6	NT Site Equipment Model
A `StopPlaceEquipment` is the specialisation of `PlaceEquipment` for `StopPlace`	r		TMv6	NT Site Equipment Model
A `WaitingRoomEquipment` is the specialisation of `WaitingEquipment` for `WaitingRoom`	g	Classified by `TypeOfWaitingRoom`	TMv6	NT Site Equipment Model
A `WaitingRoomEquipment` is a `WaitingEquipment`	r		TMv6	NT Site Equipment Model
A `MoneyService=is the specialisation of =LocalService` dedidated to `MoneyService`	g		TMv6	NT Local Commercial Service Model
A `MoneyService` is a `LocalService`	r		TMv6	NT Local Commercial Service Model
An `AssistanceService` is the specialisation of `LocalService` for assistance providing information like language, accessibility trained staff, etc.	g		TMv6	NT Local Service Equipment Model
An `AssistanceService` is a `LocalService`	r		TMv6	NT Local Service Equipment Model
A `CateringService` is the specialisation of `LocalService` dedicated to catering service	g		TMv6	NT Local Commercial Service Model
A `CateringService` is a `LocalService`	r		TMv6	NT Local Commercial Service Model
A `TypeOfCateringService` is a classification of `CateringService`	g	e.g. beverage vending machine, buffet, food vending machine, restaurant, snacks, trolley service, no beverages available, no food available.	TMv6	NT Local Commercial Service Model
A `CateringService` has a `TypeOfCateringService`	r		TMv6	NT Local Commercial Service Model
A `VehicleChargingEquipment` is a specialisation of `PlaceEquipment` for `Vehicle` charging	g		TMv6	NT Parking Equipment Model
A `VehicleChargingEquipment` is a `PlaceEquipment`	r		TMv6	NT Parking Equipment Model
A `CycleOperatingEquipment` is a specialisation of `PlaceEquipment` describing cycle parking equipment	g		TMv6	NT Parking Equipment Model
A `CycleOperatingEquipment` is a `PlaceEquipment`	r		TMv6	NT Parking Equipment Model
A `CycleOperatingEquipment` is for `Cycle`	r		TMv6	NT Parking Equipment Model
A `LuggageLockerEquipment` is he specialisation of `StopPlaceEquipment` for `LuggageLocker`	g		TMv6	NT Site Equipment Model
A `LuggageLockerEquipment` is a `StopPlaceEquipment`	r		TMv6	NT Site Equipment Model
A `SiteEquipment` is the specialisation of `PlaceEquipment` for `Site`	g		TMv6	NT Site Equipment Model
A `TrolleyStandEquipment` is the specialisation of `StopPlaceEquipment` for trolley stands	g		TMv6	NT Site Equipment Model
A `TrolleyStandEquipment` is a `StopPlaceEquipment`	r		TMv6	NT Site Equipment Model
A `PlaceEquipment` is an item of a particular type actually available at a `Location` within a `Place`	g		TMv6	CC Generic Equipment Model
A `PlaceEquipment` is an `Equipment`	r		TMv6	CC Generic Equipment Model
A `SiteComponent` is an `Element` of a `Site` describing a part of its structure. `SiteComponent` share common properties for data management, accessibility and other features.	g		TMv6	NT Site Model
A `Site` may have `SiteComponent`	r		TMv6	NT Site Model
A `SiteElement` is a type of `AddressablePlace` specifying common properties of a `Site` or a `SiteComponent` to describe it	g	Including `Accessibility`	TMv6	NT Site Model
A `SiteElement` is an `AddressablePlace`	r		TMv6	NT Site Model
A `SiteComponent` is an `Equipment`	r		TMv6	According to NT Site Model, a `SiteComponent` is an "element" but there are not other elements than `Equipment` as defined in CC Generic Equipment Model
A `CheckConstraint` is a characteristic of a process that takes place at a `SiteComponent` such as check-in, security screening, ticket control or immigration, that may potentially incur a time penalty that should be allowed for when `JourneyPlanning`	g		TMv6	NT Check Constraint Model
An `Equipment` may have a `CheckConstraint`	r	According to NT Site Model, a `SiteComponent` is an "element" but there are not other elements than `Equipment` as defined in CC Generic Equipment Model, so and `Equipment` may have a `CheckConstraint`	TMv6
A `TypeOfAccessFeature` is a classification of `AccessFeature` for `CheckConstraint`	g	e.g. barrier, narrow entrance, confined psace, queue management, etc.	TMv6	NT Check Constraint Model
A `CheckConstraintDelay` is a `TimePenalty` associated with a `CheckConstraint`	g		TMv6	NT Check Constraint Model
A `CheckConstraint` may have a `CheckConstraintDelay`	r		TMv6	NT Check Constraint Model
A `CheckConstraintDelay` is a `TimePenalty`	r		TMv6	NT Check Constraint Model
A `TimePenalty` is a `DurationDescription`	r		W3C Time Ontology in OWL	https://www.w3.org/2001/sw/BestPractices/OEP/Time-Ontology
A `CheckConstraintThroughput` is the number of `Passenger` who can pass through it in a specified interval	g		TMv6	NT Check Constraint Model
A `CheckConstraintThroughput` has an integer number (of `Passenger`)	r		TMv6	NT Check Constraint Model
A `CheckConstraintThroughput` has a `DurationDescription`	r		TMv6	NT Check Constraint Model
A `TypeOfService` is a classification for `VehicleJourney` and `SpecialService` to express some common properties of `Journey` to be taken into account in the scheduling and/or operations control process.	g		TMv6	TI Vehicle Journey Model
A `TypeOfService` are a set of properties	r		TMv6	TI Vehicle Journey Model
A `TypeOfService` is a classification	r		TMv6	TI Vehicle Journey Model

Competency Questions

CQ Comments Source (provenance)

6 UC5 Transport issues

Facts

Fact/Competency Question	Status	Comments	Source (provenance)	SubSource
A `Passenger` makes a `Trip`	r	The journey made by the passenger	GTFSvsTM
A `Vehicle` makes a `VehicleJourney`	r	The journey made by the vehicle	TFSvsTM
A `VehicleModel` is a classification of `PublicTransportVehicle` of the same `VehicleType`	g	e.g. according to equipment specifications or model generation	TMv6	CC Vehicle Type Model
A `VehiclePositionAlignment` is the alignment of a particular `BoardingPosition` with the entrance of a `Vehicle` as the result of positioning the `Vehicle` at a particular `VehicleStoppingPlace`	g		TMv6	NT Vehicle Stopping Model
A `VehiclePositionAlignment` is the position of the `Vehicle`	r		TMv6	NT Vehicle Stopping Model
A `VehiclePositionAlignment` happens in a `VehicleStoppingPlace`	r		TMv6	NT Vehicle Stopping Model
A `Vehicle` has a `BoardingPosition`	r		TMv6	NT Vehicle Stopping Model
A `BoardingPosition` happens in a `VehicleStoppingPlace`	r		TMv6	NT Vehicle Stopping Model
A `VehicleScheduleFrame` is the set of all `Block` defined for a specific `DayType` to which the same `ValidityCondition` have been assigned.	g	Usually defined for a specific `GroupOfLine`	TMv6	Vehicle Schedule Frame Model
A `VehicleServicePart` is a part of a `VehicleService` composed of one or more `Block` and limited to periods spent at the `Garage` managing the `Vehicle` in question.	g		TMv6	TI Vehicle Service Model
A `VehicleServicePart` is a part of a `VehicleService`	r		TMv6	TI Vehicle Service Model
A `VehicleServicePart` is composed by two or more `Block`	r		TMv6	TI Vehicle Service Model
A `VehicleServicePart` does not happen in `Garage`	r		TMv6	TI Vehicle Service Model
A `VehicleStoppingPosition` is the stopping position of a `Vehicle` or one of its components	g	- May be specified as a `Zone` corresponding to the bounding polygon of the vehicle; \\ Two or more `Point` corresponding to parts of the vehicle such as a door.\\ - If given as a single `Point`, indicates the position for the door relative to an indicated side of the `Vehicle`	TMv6	NT Vehicle Stopping Model
A `VehicleTypeAtPoint` is the number of `Vehicles` of a specified `VehicleType` which may wait at a specified `Point` at any one time.	g	If the capacity is 0, then that type of `Vehicle` may not stop there.	TMv6	NT Network Restriction Model
A `VehicleTypeAtPoint` is a number	r		TMv6	NT Network Restriction Model
A `Point` may have a `VehicleTypeAtPoint`	r		TMv6	NT Network Restriction Model
A `VehicleTypePreference` is the preference for the use of a particular `VehicleType` for a `ServiceJourneyPattern` depending on the `DayType` and `TimeDemandType`.	g	The rank of preferences must be recorded. \\ Different `VehicleType` may be given the same rank.	TMv6	NT Journey Pattern Model
A `ServiceJourneyPattern` may have a `VehicleTypePreference`	r		TMv6	NT Journey Pattern Model
A `VehicleTypeStopAssignment` is the allocation of a `VehicleStoppingPosition` of a `VehicleType` for a particular `VehicleJourney`	g		TMv6	TI Stopping Position Assignment Model
A `Via` is a secondary `HeadingSign` relevant for a certain part of the `JourneyPattern` advertising and onward intermediate destination to suplement the advertised (final) `Destintation` of `DestintationDisplay`	g	They call it heading but I mean it's `HeadingSign`	TMv6	NT Route Model
A `Via` is a `SignEquipment`	r		TMv6	NT Route Model
A `Trip` follows one or more `Routes`	r		UC5
A `trip` has a `trip_id`	r	A `trip` is defined in the name of gtfs trips.txt and in several definitions of TMv6	gtfs, TMv6	trips.txt
A `trip` may have a `trip_headsign`	r	gtfs uses `trip_headsign` instead of `start-point` and it can change during a trip, overridden by specific values from `stop_id`	gtfs	trips.txt
A `trip` may have a `trip_short_name`	r		gtfs	trips.txt
A `trip` may have a `direction_id`	r		gtfs	trips.txt
A `direction_id` indicates the direction of travel for a trip (`VehicleJourney`)	r		gtfs	trips.txt
a `direction_id` can be 0 (one way trip)	r		gtfs	trips.txt
a `direction_id` can be 1 (round trip)	r		gtfs	trips.txt
A `Trip` may have a `block_id`	r	Looks like a `Line`	gtfs	trips.txt
A `Trip` may have a `shape_id`	r		gtfs	trips.txt
Several `Trips` may share the `block_id`	r		gtfs	trips.txt
A `VehicleJourney` can be a `DayType`, a `DatedVehicleJourney` or a `MonitoredVvehicleJourney`	r		GTFSvsTM
A `Route` is a sequence of two or more `Stops`	r		GTFSvsTM
A `Vehicle` has a `Route`	r		GTFSvsTM
A `route` has a named service	r	identifies the route or vehicle journey	GTFSvsTM
A `route` has a `route_id`	r		gtfs	routes.txt
A `route` may be operated by several `agency_id`	r	The inconsistency of route, trip and journey	gtfs	agency.txt, routes.txt
A `route` may have at least one `agency_id`	r		gtfs	agency.txt, routes.txt
A `route` must have a `route_short_name`	r		gtfs	routes.txt
A `route` must have a `route_long_name`	r		gtfs	routes.txt
A `route` may have a `route_desc`	r		gtfs	routes.txt
A `route` must have a `route_type`	r		gtfs	routes.txt
A `route` may have a `route_url`	r		gtfs	routes.txt
A `route` may have a `route_color`	r		gtfs	routes.txt
A `route_color` is expressed in hexadecimal	r		gtfs	routes.txt
A route may have a `route_text_color`	r	if ommited when `route_color` set, default value is `ffffff`	gtfs	routes.txt
A `route_text_color` is expressed in hexadecimal	r	it must provide sufficent contrast whith `route_color`	gtfs	routes.txt
A `trip` may have a `shape_dist_traveled` property	r		gtfs	stop_times.txt
A `shape_dist_traveled` property has a non-negative float	r		gtfs	stop_times.txt
The value of `shape_dist_traveled` is a sum of the distance in between `stops` in a `route`	r	interperetation of `shapes_dist_traveled`	gtfs	stop_times.txt
An `agency` must have an `agency_id`	r	gtfs identifies agencies as transit brands or transit agencies, although agencies and brands are not the same.	gtfs	agency.txt
An `Operator` must have an `agency_id`	r	interpretation of gtfs agency.txt. In gtfs is called transit brand or transit agency	UC5, gtfs	agency.txt
An `agency` must have an `agency_name`	r		gtfs	agency.txt
An `Operator` must have an `agency_name`	r	interpretation of gtfs agency.txt. In gtfs is called transit agency	UC5, gtfs	agency.txt
An `Operator` may have a `brand`	r	interpretation of gtfs agency.txt. In gtfs is called transit agency	UC5, gtfs	agency.txt
An `Operator` must have an `agency_url`	r	interpretation of gtfs agency.txt. In gtfs is called transit agency	UC5, gtfs	agency.txt
An `agency` must have an `agency_url`	r		gtfs	agency.txt
An `agency_url` is a URI	r		gtfs	agency.txt
An `Operator` must have an `agency_timezone`	r	interpretation of gtfs agency.txt. In gtfs is called transit agency	UC5, gtfs	agency.txt
An `agency` must have an `agency_timezone`	r		gtfs	agency.txt
An `agency_timezone` is a standard UTC timezone	r		UC5
An `Operator` may have a `agency_lang`	r	interpretation of gtfs agency.txt. In gtfs is called transit agency	UC5, gtfs	agency.txt
A `agency_lang` is a standard language code ISO 639	r		UC5, gtfs	agency.txt
An `agency` may have an `agency_lang`	r		gtfs	agency.txt
An `Operator` may have an `agency_phone`	r		gtfs	agency.txt
An `agency` may have an `agency_phone`	r		gtfs	agency.txt
An `agency_phone` is a string o numbers, spaces or symbols as `+`	r		UC5
A `VehicleJourney` must have two or more stops	r		UC5, TMv6
An `Operator` may have an `agency_fare_url`	r	interpretation of gtfs agency.txt. In gtfs is called transit agency	UC5, gtfs	agency.txt
An `agency_fare_url` is an URI	r		UC5, gtfs	agency.txt
A `Trip` may have a `pickup_type` property	r		gtfs	stop_times.txt
A `pickup_type` property can have values: 0 or empty for regularly scheduled pickup; 1 for no pickup available; 2 for agency arrangement; or 3 for driver arrangement	r		gtfs	stop_times.txt
A `Trip` may have a `drop_off_type` property	r		gtfs	stop_times.txt
A `drop_off_type` property can have values: 0 or empty for regularly scheduled pickup; 1 for no drop off available; 2 for agency arrangement; or 3 for driver arrangement	r		gtfs	stop_times.txt
An `AllowedLineDirection` is an allowed `Direction` that can be used on a given `Route`. This can be used to validate the selection of allowed values	g		TMv6	NT Route Model
An `AllowedLineDirection` is a `Direction`	r		TMv6	NT Route Model
A `Direction` is a classification for the general orientation of a `Route`	g		TMv6	NT Route Model
A `Route` is and ordered list of located `Point` defining one single path through the road (or rail) network.	g		TMv6	NT Route Model
A `RouteLink` is an oriented link between two `RoutePoint` allowing the definition of a unique path through the network	g		TMv6	NT Route Model
A `RouteLink` has two `RoutePoint`	r		TMv6	NT Route Model
A `RoutePoint` may have a `RouteLink`	r		TMv6	NT Route Model
A `RoutePoint` is a `Point` used to define the shape of a `Route` through the `TransportNetwork`	g		TMv6	NT Route Model
A `RoutePoint` is a `Point`	r		TMv6	NT Route Model
A `TurnStation` is a `Place` where a `Vehicle` can revers its `Direction`	g	Often the `Place` is a `Terminus`. \\ From a `Route` to another of opposite `Direction` The	TMv6	NT Route Model
A `TurnStation` is a `Place`	r		TMv6	NT Route Model
A `TurnAroundTimeLimit` is the maximum and/or minimum time for which a vehicle may be scheduled to wait at a particular `TimingPoint` (often included in a `TurnStation`) without being returned to a `ParkingPoint`	g	This may be superseded by a `DeadRun`	TMv6	TI Journey Pattern Times Model
A `Vehicle` can revers in a `TurnStation`	r		TMv6
A `Route` has a `Direction`	r		TMv6
A `Direction` has an opposite	r		TMv6
A `RoutingConstraintZone` is a `Zone` defining a `RoutingConstraint`.	g	The `Zone` may be defined by its contained `ScheduledStopPoint` or by its boundary points. \\ Example: if you board on this `Zone` you can't alight on this `Zone`	TMv6	NT Routing Constraint Zone
A `RoutingConstraintZone` is a `Zone`	r		TMv6	NT Routing Constraint Zone
A `Zone` is a two-dimensional `Place` within the `ServiceArea` of a `PublicTransportOperator`	g	e.g. an administrative zone, a `TariffZone`, an `AccessZone`	TMv6	CC Generic Zone and Feature Model
A `Zone` is a `Place`	r		TMv6	CC Generic Zone and Feature Model
A `TypeOfZone` is a classification of `Zone`	g		TMv6	CC Generic Zone and Feature Model
A `ZoneProjection` is an oriented correspondence: from one zone in a source layer onto a target `Entity`	g	e.g. `Point`, `ComplexFeature`, within a defined `TypeOfProjection`	TMv6	CC Generic Zone and Feature Model
A `TariffZone` is a `Zone` used to define a zonal fare structure in a zone-counting or `zone-matrix` system	g		TMv6
A `TariffZone` is a `Zone`	r		TMv6
A `Route` may pass through the same `Point` more than once	g		TMv6	NT Route Model
A `Route` may have `TimingPoint`	r		TMv6	NT Journey Pattern Model
An `Authority` is the organisation under which the responsability of organising the transport service in a certain area is placed	g		TMv6	NT Transport Organizations Model
An `Authority` is an `Organisation`	r		TMv6	NT Transport Organizations Model
An `Organisation` is a legally incorporated body associated with any aspect of the transport service	g		TMv6	CC Generic Organisation Model
A `ServicedOrganisation` is a public or private `Organisation` for which `PublicTransportService` are provided on specific days	g	e.g. a school, university or work.	TMv6	CC Generic Organisation Model
A `ServicedOrganisation` is an `Organisation`.	r		TMv6	CC Generic Organisation Model
A `PublicTransportService` is a set of `ServiceJourney`	r		TMv6	CC Generic Organisation Model
An `AvailabilityCondition` is a `ValidityCondition` expressed in terms of temporal parameters and referring to `Day`	g		TMv6	CC Availability Condition Model
A `CompositeFrame` is a set of `VersionFrame` to which the same `ValidityCondition` have been assigned	g		TMv6	CC Composite Frame Model
A `CompositeFrame` is a set of `VersionFrame`	r		TMv6	CC Composite Frame Model
A `CompositeFrame` has an `AvailabilityCondition`	r		TMv6	CC Composite Frame Model
A `Day` is approximately the period of time during which the Earth completes one rotation around its axis. A solar day is the length of time which elapses between the Sun reaching its highest point in the sky two consecutive times	g		Wikipedia
A `Day` may have `AvailabilityCondition`	r		TMv6	CC Availability Condition Model
A `ValidityCondition` is the condition used in order to characterise a given `Version` of a `VersionFrame`	g		TMv6	CC Generic Validity Model
A `ValidityCondition` consists of a parameter (e.g. date, triggering event, etc.) and its type of application (e.g. for, from, until, etc.).	g		TMv6	CC Generic Validity Model
A `ValidityCondition` may have a `ValidityRuleParameter`	r		TMv6	CC Generic Validity Model
A `ValidityRuleParameter` is a user defined `ValidityCondition` used by a rule for selecting versions. E.g. river level > 1,5m and bad weather.	g		TMv6	CC Generic Validity Model
A `ValidityTrigger` is an external `Event` defining a `ValidityCondition`. E.g. exceptional flow of a river, bad weather, road closure for works	g		TMv6	CC Generic Validity Model
A `ValidityCondition` may have a `ValidityTrigger`	r		TMv6	CC Generic Validity Model
A `ValidityCondition` must have a `Parameter`	r		TMv6	CC Generic Validity Model
A `ValidityCondition` must have a `TypeOfApplication`	r		TMv6	CC Generic Validity Model
A `TrafficControlPoint` is a `Point` where the traffic flow can be influenced	g	Examples are traffice lights (lanterns), barriers	TMv6	NT Activation Model
A `TrafficControlPoint` is a `Point`	r		TMv6	NT Activation Model
A `BeaconPoint` is a `Point` where a `Beacon` or similar device to support the automatic detection of vehicles passing by is located	g		TMv6	NT Activation Model
A `BeaconPoint` is a `Point`	r		TMv6	NT Activation Model
A `Point` is a 0-dimensional `Node` of the `Network` used for the spatial description of the network. `Point` may be located by a `Location`	g		TMv6	CC Generic Point & Link Model
A `Point` has dimension 0	r		TMv6	CC Generic Point & Link Model
A `Network` is a named grouping of `Line` under which a `TransportNetwork` is known	g		TMv6	NT Route Model
A `LineNetwork` is the topological structure of a `Network` as a graph of `LineSection`.	g	This allows the branches and loops of a `Line` to be described as a whole	TMv6	NT Line Network Model
A `LineSection` is a part of a `Network` comprising and edge between two nodes. Not directional	g		TMv6	NT Line Network Model
A `LineSection` is a `LineNetwork`	r		TMv6	NT Line Network Model
A `LineShape` is the graphical shape of a `Link` obtainied from a formula or other means, using the `Location` of its limiting `Point` and depending on the `LocatingSystem` used for the graphical representation	g		TMv6	CC Generic Projection Model
A `LineShape` is the graphical shape of a `Link`	r		TMv6	CC Generic Projection Model
A `Link` may have a `LineShape`	r		TMv6	CC Generic Projection Model
A `PointOnLink` is a `Point` on a `Link` which is not needed for `LinkDefinition` but may be used for other purposes	g	e.g. for purposes of automatic `Vehicle` monitoring, `Passenger` information of for driver information	TMv6	CC Generic Point & Link Model
A `LinkProjection` is an oriented correspondence from one `Link` of a source layer onto an `Entity` in a target layers	g		TMv6	CC Generic Point & Link Model
A `LinkSequence` is an ordered sequence either of `Point` or of `Link` defining a `Path` through the `Network`	g	e.g. `LinkSequence`, `ComplexFeature`, within a defined `TypeOfProjection`	TMv6	CC Generic Point & Link Sequence Model
A `TransportNetwork` is a `Network`	r		TMv6	NT Route Model
A `CompoundBlock` is the work of a `Vehicle` during the time it is coupled to another `Vehicle`	g		TMv6	TI Vehicle Service Model
A `Vehicle` can be coupled to another `Vehicle`	r		TMv6	TI Vehicle Service Model
A `CompoundBlock` is the work of a `Vehicle`	r		TMv6	TI Vehicle Service Model
A `CompoundTrain` is a `VehicleType` composed of a sequence of more than one `Vehicle` of type `Train`	g		TMv6	CC Train Model
A `CompoundTrain` is a `VehicleType`	r		TMv6	CC Train Model
A `CompoundTrain` has 2 or more `Train`	r		TMv6	CC Train Model
A `VehicleType` is a classification of `PublicTransportVehicle` according to the `Vehicle` scheduling requirements in mode and capacity (e.g. standard bus, double-deck, …)	g		TMv6	CC Train Model
A `Vehicle` has scheduling requirements	r		TMv6	CC Train Model
A `Vehicle` has a `Mode`	r		TMv6	CC Train Model
A `Mode` is any `MeanOfTransport`	r		TMv6	CC Train Model
A `Submode` is a variant of a `Mode`	g	As for instance international or domestic rail, rail being the `Mode`	TMv6	CC Transport Submode Model
A `Train` is a `VehicleType` composed of a set of `TrainElement` in a certain order, i.e. of wagons assembled together and propelled by a locomotive or one of the wagons	g		TMv6	CC Train Model
A `TrainElement` is an elementary component of a `Train` (e.g. wagon, locomotive)	g		TMv6	CC Train Model
A `Wagon` is a `TrainElement`	r		TMv6	CC Train Model
A `Locomotive` is a `TrainElement`	r		TMv6	CC Train Model
A `TrainComponent` is a specification of the order of `TrainElement` in a `Train`	g		TMv6	CC Train Model
A `TrainComponentLabelAssignment` is the allocation of and advertised designation for a `Vehicle` or `VehicleElement` for `Passenger`	g		TMv6	TI Train Component Label Assignment Model
A `TrainInCompoundTrain` is the specification of the order of `TrainElement` in `Train`	g		TMv6	CC Train Model
A `TrainNumber` is the specification of codes assigned to particular one or more `VehicleJourney` when operated by one or more `Train` in a `CompoundTrain` according to a functional purpose (passenger information, operation follow-up, etc.)	g		TMv6	TI Vehicle Journey Model
A `TrainNumber` is a code	r		TMv6	TI Vehicle Journey Model
A `Train` may have a `TrainNumber`	r		TMv6	TI Vehicle Journey Model
A `TrainStopAssignment` is the association of a `TrainComponent` at a `ScheduledStopPoint` with a specific `StopPlace` and also possibly a `Quay` and `BoardingPosition`	g		TMv6	NT Train Stop Assignment Model
A `Country` is a jurisdictional geographic boundary	g		TMv6	CC Topographic Place Model
A `Country` normally has a two character IANA identifier	r	https://en.wikipedia.org/wiki/List_of_tz_database_time_zones	TMv6
A `PostalAddress` is a specification of `Address` refining it by using the attributes used for conventional identification for mail.	g	Comprises variously a building identifier, Street Name, Post code and other descriptions	TMv6	CC Topographic Place Model
A `CrewBase` is a `Place` where `OperatingEmployee` (e.g. `Driver`) report on and register their work	g		TMv6	NT Vehicle & Crew Point Model.
A `CrewBase` is a `Place`	r		TMv6	NT Vehicle & Crew Point Model.
An `OperatingEmployee` is a `Worker`	r		TMv6	NT Vehicle & Crew Point Model.
An `OperatingEmployee` works in the `PublicTransportNetwork`	r		TMv6	NT Vehicle & Crew Point Model.
A `Worker` is a `Person`	r		TMv6	NT Vehicle & Crew Point Model.
A `Driver` is an `OperatingEmployee`	r		TMv6	NT Vehicle & Crew Point Model.
A `DeadRun` is a non-service `VehicleJourney`	r		TMv6	TI Vehicle Journey Model
A `DeadRun` is a `VehicleJourney`			TMv6	TI Vehicle Journey Model
A `VehicleJourney` has a `ServiceStatus`	r	Service or Non-service	TMv6	TI Vehicle Journey Model
A `DeadRunPattern` is a `JourneyPattern` to be used for `DeadRun`	g		TMv6	NT Journey Pattern Model
A `DeadRunPattern` is a `JourneyPattern`	r		TMv6	NT Journey Pattern Model
A `Department` is an `OrganisationPart` specific to a purpose and/or organisational structure	g		TMv6	CC Generic Organisation Model
A `Department` is an `OrganisationPart`	r		TMv6	CC Generic Organisation Model
An `OperatingDepartment` is a specific `Department` which administers certain `Line`	g		TMv6	CC Transports Organisation Model
An `OperatingDepartment` is a `Department`	r		TMv6	CC Transports Organisation Model
An `OrganisationUnit` is an `OrganisationPart` to which a set of responsabilities in a `PublicTransportCompany` for planning and control is assigned	g		TMv6	CC Generic Organisation Model
An `OrganisationUnit` is an `OrganisationPart`	r		TMv6	CC Generic Organisation Model
An `OperationalContext` is a characterization of a set of operational objects, such as timing or `Link` determined either by a `Department` or by an `OrganisationalUnit`	g		TMv6	CC Transport Organisation Model
A `PublicTransportCompany` is an `Operator`	r		TMv6	CC Generic Organisation Model
An `OtherOrganisation` is a generic `Organisation` being neither an `Authority` neither a `PublicTransportOperator` (`TravelAgent`, `ManagementAgent`, etc.)	r		TMv6	CC Generic Organisation Model
An `OtherOrganisation` is an `Organisation`	r		TMv6	CC Generic Organisation Model
A `TravelAgent` is a specialisation of `Organisation` for `TravelAgent`	g		TMv6	CC Additional Organisation Model
A `TravelAgent` is an `Organisation`	r		TMv6	CC Additional Organisation Model
A `ManagementAgent` is a specialisation of `Organisation` for `ManagementAgent`	g		TMv6	CC Additional Organisation Model
A `ManagementAgent=is an =Organisation`	r		TMv6	CC Additional Organisation Model
A `GeneralFrame` is a set of data containing information, to which the same `ValidityCondition` have been assigned	g		TMv6	CC General Frame Model
A `GeneralSign` is a specialisation of `SignEquipment` which are not `HeadingSign` nor `PlaceSign`	g		TMv6	NT Sign Equipment Model
A `GeneralSign` is a `SignEquipment`	r		TMv6	NT Sign Equipment Model
A `GroupOfEntities` is a set of `Entity` grouped together according to a `PurposeOfGrouping`	g	e.g. grouping of stops known to the public by a common name.	TMv6	CC Generic Grouping Model
A `GroupOfEntities` have two or more `Entity`	r		TMv6	CC Generic Grouping Model
A `GroupOfEntities` has a `PurposeOfGrouping`	r		TMv6	CC Generic Grouping Model
A `PurposeOfGrouping` is a functional purpose for which group of elements are defined. The `PurposeOfGrouping` may be restricted to one or more types of the given object.	g		TMv6	CC Generic Grouping Model
A `GroupOfLines` is a grouping of `Line` which will be commonly referenced for a specific purpose.	g		TMv6	NT Route Model
A `GroupOfLines` has two or more `Lines`	r		TMv6	NT Route Model
A `GroupOfLinkSequences` is a grouping of two or more `LinkSequence`	g		TMv6	CC Generic Point & Link Model
A `GroupOfLinks` is a grouping of `Link`	g	E.g. Ones managed by the same `Authority`	TMv6	CC Generic Point & Link Model
A `GroupOfOperators` is a group of `Operator` having for instance common schemes for fare collection or passenger information	g		TMv6	CC Transport Organisations Model
A `TypeOfPoint` is a classification of `Point` according to their functional purpose	g		TMv6	CC Transport Organisations Model
A `Point` may have a `TypeOfPoint`	r		TMv6	CC Generic Point & Link Model
A `GroupOfServices` is a group of `Service` often known to its users by a name or a number	g		TMv6	TI Service Journey Model
A `Service` may have one (or more?) `GroupOfServices`	r		TMv6	TI Service Journey Model
A `JourneyHeadway` is a `HeadwayInterval` that is available for all the `VehicleJourney` running on the `JourneyPattern` for a given `TimeDemandType` at a given `TimingPoint`.	g	This is default value that can be superseded by `VehicleJourneyHeadway`. \\ This information must be consistent with `HeadwayJourneyGroup` if available	TMv6	TI Service Journey Model
A `JourneyHeadway` is a `HeadwayInterval`	r		TMv6	TI Service Journey Model
A `VehicleJourney` may have a `JourneyHeadway`	r		TMv6	TI Service Journey Model
A `VehicleJourneyHeadway` is a `HeadwayInterval` that is available for a `VehicleJourney`	g	The delay between the previous and the next `VehicleJourney`	TMv6	TI Vehicle Journey Times Model
A `VehicleJourneyHeadway` is a `HeadwayInterval`	r		TMv6	TI Vehicle Journey Times Model
A `VehicleJourney` may have a `VehicleJourneyHeadway`	r		TMv6	TI Vehicle Journey Times Model
A `VehicleJourneyLayover` is a time allowance at the end of a specified `VehicleJourney`	g	This time supersedes any global layover or `JourneyPatterLayover`	TMv6	TI Vehicle Journey Times Model
A `VehicleJourney` may have a `VehicleJourneyLayover`	r		TMv6	TI Vehicle Journey Times Model
A `VehicleJourneyRunTime` is the time taken to traverse a specified `TimingLinkInJourneyPattern` on a specified `VehicleJourney`	g	This gives the most detailed control for the `VehicleJourney`. \\ This oversedes `DefaultServiceJourneyRunTime`, `JourneyPatternRunTime` and `DefaultDeadRunRunTime`	TMv6	TI Vehicle Journey Times Model
A `VehicleJourneyWaitTime` is the time for a `Vehicle` to wait at a particular `TimingPointInJourneyPattern` on a specified `VehicleJourney`	g	This wait time will override the `JourneyPatternWaitTime`	TMv6	TI Vehicle Journey Times Model
A `Vehicle` may have a `VehicleJourneyWaitTime`	r		TMv6	TI Vehicle Journey Times Model
A `VehicleJourney` may have a `VehicleJourneyRunTime`	r		TMv6	TI Vehicle Journey Times Model
A `JourneyLayover` is the time allowance at the end of each `Journey` on a specified `JourneyPattern`, to allow for delays and for other purposes	g	This `JourneyLayover` supersedes any global layover and may be supersede by a specific `VehicleJourneyLayover`	TMv6	TI Vehicle Journey Times Model
A `JourneyPattern` may have a `JourneyLayover`	r		TMv6	TI Vehicle Journey Times Model
A `JourneyMeeting` is a time constraint for one or several `ServiceJourney` fixing interchanges between them and/or an external event	g	(e.g. arrival or departure of a feeder line, opening time of the theatre, etc.)	TMv6	TI Vehicle Journey Times Model
A `ServiceJourney` may have a `JourneyMeeting`	g		TMv6	TI Interchange Model
A `JourneyPartCouple` are two `JourneyPart` of different `VehicleJourney` served simultaneously by a train set up by coupling their single `Vehicle`	g		TMv6	TI Coupled Journey Model
A `JourneyPartCouple` has 2 `JourneyPart` of different `VehicleJourney`	r		TMv6	TI Coupled Journey Model
A `PurposeOfJourneyPartition` is an operational purpose changing within a `JourneyPattern` and with this subdividing the `ServiceJourney` into `JourneyPart`	g		TMv6	TI Coupled Journey Model
A `Parking` is a designated `Location` for leaving vehicles such as cars, motorcycles and bicycles	g	These vehicles are not `PublicTransportVehicle`	TMv6	NT Parking Model
A `ParkingEntranceForVehicle` is an `Entrance` for vehicles to the `Parking` from the road.	g		TMv6	NT Parking Model
A `ParkingArea` is a marked zone within a `Parking` containing `ParkingBay`	g		TMv6	NT Parking Model
A `ParkingBay` is a place to park an individual vehicle	g		TMv6	NT Parking Model
A `ParkingArea` has one or more `ParkingBay`	r		TMv6	NT Parking Model
A `ParkingCapacity` is a `ParkingProperty` providing information about its capacity	g		TMv6	NT Parking Model
A `ParkingComponent=is a generic component of a =Parking`	g	e.g. `ParkingArea` or `ParkingBay`	TMv6	NT Parking Model
A `ParkingArea` is a `ParkingComponent`	r		TMv6	NT Parking Model
A `ParkingBay` is a `ParkingComponent`	r		TMv6	NT Parking Model
A `ParkingPassengerEntrance` is an entrance to the `Parking` for `Passenger` on foot or other out-of-vehicle mode, such as wheelchair.	g		TMv6	NT Parking Model
A `ParkingProperty` is a `Parking` specific property other than its capacity	g		TMv6	NT Parking Model
A `TypeOfAccessibilityLimitation` is a classification for `AccessibilityLimitation`	g	e.g. audio, visual, step free, etc.	TMv6	CC Generic Accessibility Model
A `PassengerAccessibilityNeed` is a `Passenger` 's requirement for accessibility, comprising one or more `UserNeed`.	g	For example, that he is unable to navigate stairs, or lifts, or has visual or auditory impairments. \\ It can be used to derive an accessibility constraint for the `Passenger`, allowing the computation of paths for those with specifically constrained mobility. Example: wheelchair, no lifts, no stairs	TMv6	CC Generic Accessibility Model
A `PassengerAccessibilityNeed` may have one or more `UserNeed`	r		TMv6	CC Generic Accessibility Model
A `PassengerCarryingRequirement` is a classification of requirements for a `PublicTransportVehicle` according to the `Passenger` carrying capabilities of the `Vehicle`	g		TMv6	CC Vehicle Type Model
A `PassengerEquipment` is an item of equipment of a particular type actually available at a location within a `Place` or a `Vehicle`	g		TMv6	CC Generic Equipment Model
A `PassengerSafetyEquipment` is the specialisation of `PassengerEquipment` for `Passenger` safety.	g		TMv6	NT Passenger Service Equipment Model
A `PassengerStopAssignment` is the allocation of a `ScheduledStopPoint` to a specific `StopPlace=for a =ServiceJourney`, and also possibly a `Quay` and `BoardingPosition`	g	i.e. a `ScheduledStopPoint` of a `ServicePattern` or `JourneyPattern`	TMv6	NT Stop Assignment Model

route_type

0
Tram, Streetcar, Light rail. Any light rail or street level system within a metropolitan area.

1
Subway, Metro. Any underground rail system within a metropolitan area.

2
Rail. Used for intercity or long-distance travel.

3
Bus. Used for short- and long-distance bus routes.

4
Ferry. Used for short- and long-distance boat service.

5
Cable car. Used for street-level cable cars where the cable runs beneath the car.

6
Gondola, Suspended cable car. Typically used for aerial cable cars where the car is suspended from the cable.

7
Funicular. Any rail system designed for steep inclines.

Competency Questions

CQ Comments Source (provenance)

7 UC6 Public Bicycles

Facts

Facts	Status	Source (provenance)
A passenger can buy a ticket for a public bike	r	UC6
Bicycles are hosted in BikeStops	r	UC6
A bicycle can go through bicycle paths	r	UC6
Bikestops are located near stops or stopStations	r	UC6

Competition Questions

Facts Comments Source (provenance)

8 UC7 TP Businness/services inside the PT network

Facts

Fact/Competency Question	Status	Source (provenance)
A passenger may need to send a postcard	r	UC7
A passenger may need to make the passport	r	UC7
A passenger need to know what type of services	r	UC7

Competency Questions

Fact/Competency Question Comments Source (provenance)

9 UC8 Transportation exchange

Facts

Fact/Competency Question	Status	Comments	Source (provenance)	SubSource
A `Trip` has an `arrival_time` in every `Stop`	r	intepretation of `arrival_time` in gtfs stop_times.txt	gtfs	stop_times.txt
A `Trip` has a `departure_time` in every `Stop`	r	intepretation of `departure_time` in gtfs stop_times.txt	gtfs	stop_times.txt
An `arrival_time` may have a `timepoint`	r	interpretation of `timepoint` of gtfs stop_times.txt	gtfs	stop_times.txt
A `departure_time` may have a `timepoint`	r	interpretation of `timepoint` of gtfs stop_times.txt	gtfs	stop_times.txt
A `timepoint` can be 0 for approximate of 1 for exact	r	interpretation of `timepoint` of gtfs stop_times.txt	gtfs	stop_times.txt
A `Trip` must have a `stop_sequence`	r	interpretation of `stop_sequence` in gtfs stop_times.txt due to the fact it is calculated for stop_times instead of trips	gtfs	stop_times.txt
A `stop_sequence` is a non-negative integer	r	it doesn't need to be consecutive	gtfs	stop_times.txt
A `Stop` may have a `stop_headsign`	r		gtfs	stop_times.txt
A `stop_headsign` substitutes to `trip_headsign` if its value is valid in every `Stop` of the `Trip`	r		gtfs	stop_times.txt
A `Trip` may have `Stops` at convenience	r		UC5
A `Line` has a frequency value	r	Lines in TMv6 , Trips that operates on regular headways (time between trips) in gtfs frequencies.txt	TMv6, gtfs	frequencies.txt
The `frequency` value is 0 if service does not follow a fixed schedule throughout the day	r		gtfs	frequencies.txt
The `frequency` value is 1 if service follow a fixed schedule throughout the day	r		gtfs	frequencies.txt
A `Line` must have a `start_time` property	r	time at which the first vehicle departs from the first stop of the trip with the specified headway	gtfs	frequencies.txt
The value of `start_time` is UTC	r		UC8
A `Line` must_have a `end_time` property	r	time at which service changes to a different headway (or ceases) at the first stop in the trip	gtfs	frequencies.txt
The value of `end_time` is UTC	r		UC8
A `Line` must have a `headway_secs` property	r	Time, in seconds, between departures from the same stop (headway) for the trip during the time interval specified by `start_time` and `end_time`	gtfs	frequencies.txt
The value of `headway_secs` is a non-negative integer	r		gtfs	frequencies.txt
A `Trip` may have a `from_trip_id` property	r	Interpretation of gtfs-extensions in order to associate it to `Trip`	gtfs	extensions
The value of `from_trip_id` is a `trip_id`	r		gtfs	extensions
If a `Trip` has a `from_trip_id` property, it also has a `to_trip_id`, and viceversa	r		UC8
A `Trip` may have a `to_trip_id` property	r	Interpretation of gtfs extensions in order to associate it to `Trip`	gtfs	extensions
The value of `to_trip_id` is a `trip_id`	r		gtfs	extensions
A `Route` may have a `from_route_id` property	r	Interpretation of gtfs extensions in order to associate it to `Route`	gtfs	extensions
The value of `from_route_id` is a `route_id`	r		gtfs	extensions
A `Route` may have a `to_route_id` property	r	Interpretation of gtfs transfers.txt in order to associate it to `Route`	gtfs	extensions
The value of `to_route_id` is a `route_id`	r		gtfs	extensions
A `PointOnRoute` is a `Route` `Point` used to define a `Route` with its order on that `Route`	g		TMv6	NT Route Model
A `PointOnRoute` is a `Point`	r		TMv6	NT Route Model
A `TransferRestriction` is a constraint that can be applied on a `Connection` or `Interchange` between two `ScheduledStopPoint` preventing or forbidding the passenger to use it	g		TMv6	NT Routing Constraint Model
A `Connection` may have a `TransferRestriction`	r		TMv6	NT Routing Constraint Model
A `Interchange` may have a `TransferRestriction`	r		TMv6	NT Routing Constraint Model
A `Transfer` connects at least two `Point`	r		TMv6	CC Generic Place Model
A `Connection` have at least two `ScheduledStopPoint`	r		TMv6	NT Service Pattern Model
A `ScheduledStopPoint` is a class of `Point`	r	interpretation of `ScheduledStopPoint` of NT Service Pattern Model	TMv6	NT Service Pattern Model
A `StopArea` is a group of `ScheduledStopPoint` close to each other	g		TMv6	NT Service Pattern Model
A `StopPointInJourneyPattern` is a `Point` in a `JourneyPattern` which is `ScheduledStopPoint`	g		TMv6	NT Service Pattern Model
A `StopPointInJourneyPattern` is a `ScheduledStopPoint`	r		TMv6	NT Service Pattern Model
A `StopPointInJourneyPattern` is a `Point`	r		TMv6	NT Service Pattern Model
A `ScheduledStopPoint` is a `Point` where a `Passenger` can board or alight from a `Vehicle`	g		TMv6	NT Service Pattern Model
A `Passenger` can board from `Vehicle` in a `ScheduledStopPoint`	r	interpretation of `ScheduledStopPoint` of NT Service Pattern Model	TMv6	NT Service Pattern Model
A `Passenger` can alight from `Vehicle` in a `ScheduledStopPoint`	r	interpretation of `ScheduledStopPoint` of NT Service Pattern Model	TMv6	NT Service Pattern Model
A `Stop` may have several `from_stop_id` property	r	it connects one different stop with another one. This is the "different stop".	gtfs	transfers.txt
A `from_stop_id` is a `stop_id`	r		gtfs	transfers.txt
A `Stop` may have several `to_stop_id` property	r	it connects one different stop with another one. This is the "another one"	gtfs	transfers.txt
A `to_stop_id` is a `stop_id`	r		gtfs	transfers.txt
A `to_stop_id` inherits to every `stop_id` if `stop_id` is location=1 (station)	r		gtfs	transfers.txt
A `from_stop_id` inherits to every `stop_id` if `stop_id` is location=1 (station)	r		gtfs	transfers.txt
A `stop` may have a `transfer_type` property	r		gtfs	transfers.txt
A `transfer_type` property with value 0 is undefined	r		gtfs	transfers.txt
A `transfer_type` property with value 1 means the departing `vehicle` is expected to wait for the arriving one	r		gtfs	transfers.txt
A `transfer_type` property with value 2 means the transfer requires `min_transfer_time`	r		gtfs	transfers.txt
A `transfer_type` property with value 3 means it is not possible to make transfers.	r		gtfs	transfers.txt
A `min_transfer_time` is the minimum amount of time to transfer	r		gtfs	transfers.txt
A `min_transfer_time` is represented in seconds as a non-negative integer	r		gtfs	transfers.txt
A `transfer` may have several `pathways`	r		gtfs	transfers.txt
A `pathway` must have a `pathway_id`	r		gtfs	transfers.txt
A `pathway` must have a `from_stop_id` property	r		gtfs	transfers.txt
A `pathway` must have a `to_stop_id` property	r		gtfs	transfers.txt
A `pathway` must have a `pathway_mode` property	r		gtfs	transfers.txt
A `pathway_mode` is a enumeration of 1 or more Values	r	see below	gtfs	transfers.txt
A `pathway` must have a `is_bidirectional` property	r		gtfs	transfers.txt
A `is_bidirectional` value can be unidirectional	r	I wonder why a boolean was not chosen in this case	gtfs	transfers.txt
A `is_bidirectional` value can be bidirectional	r	but `pathway_mode=6` and `pathway_mode=7`	gtfs	transfers.txt
A `pathway` may have a `length` property	r	This field is recommended for walkways (pathway_mode=1), fare gates (pathway_mode=6) and exit gates (pathway_mode=7).	gtfs	transfers.txt
A `length` is expressed in non-negative meters	r		gtfs	transfers.txt
A `pathway` may have a `traversal_time` property	r	This field is recommended for moving sidewalks (pathway_mode=3), escalators (pathway_mode=4) and elevator (pathway_mode=5).	gtfs	transfers.txt
A `traversal_time` is expressed in a positive integer	r		gtfs	transfers.txt
A `pathway` may have a `stairs_count` property	r	This field is recommended for stairs (pathway_mode=2).	gtfs	transfers.txt
A `stairs_count` property is a non-null integer	r		gtfs	transfers.txt
A `pathwaay` may have a `max_slope` property	r	This field is recommended for stairs (pathway_mode=2).	gtfs	transfers.txt
A `max_slope` is a float	r		gtfs	transfers.txt
A `pathway` may have a `min_width` property	r	Minimum width of the pathway in meters. This field is highly recommended if the minimum width is less than 1 meter.	gtfs	transfers.txt
A `min_width` is a positive float	r		gtfs	transfers.txt
A `pathway` may have a `signposted_as` property	r		gtfs	transfers.txt
A `signposted_as` is a string	r	String of text from physical signage visible to transit riders	gtfs	transfers.txt
A `pathway` may have a `reverse_signposted_as` property	r		gtfs	transfers.txt
A `reverse_signposted_as` is a string	r	Same than the signposted_as field, but when the pathways is used backward	gtfs	transfers.txt
An `Address` is descripted data associated with a `Place` that can be used to describe the unique geographical context of a `Place` for the purposes of identifying it.	g		TMv6	CC Topographic Place Model
A `RoadAddress` is an `Address`	r		TMv6	CC Topographic Place Model
A `PostalAddress` is an `Address`	r		TMv6	CC Topographic Place Model
A `TopographicPlace` is a type of `Place` providing the topographical context when searching for or presenting travel information, for example as the `Origin` or `Destination` of a `Trip`. It may be of any size (e.g. County, City, Town, Village) and of different specificity (e.g. Greater London, London, West end, Westminster, St James s).	g		TMv6	CC Topographic Place Model
A `TopographicPlace` is a `Place`	r		TMv6	CC Topographic Place Model
A `TopographicPlace` provides topographic information	r		TMv6	CC Topographic Place Model
A `RoadAddress` is the specialisation of `Address` refining it by using the characteristics such as road number and name used for conventional identification of along a road	g		TMv6	CC Topographic Place Model
A `RoadAddress` is an `Address`	r		TMv6	CC Topographic Place Model
A `SchematicMap` is a map representing schematically the layout of the topographic structure of `Place=or the =PublicTransportNetwork`.	g	It can include a pixel projection of a set of `Entity` onto a bitmap image so as to support hyperlinked interactions.	TMv6	CC Schematic Map Model
An `AdministrativeZone` is the area of a district, a region, a city, a municipality or other area with which an `Organization` has a `ResponsabilityRol`	g		TMv6	CC Generic Organisation Model
An `AdministrativeZone` is an `Area`	r		TMv6	CC Generic Organisation Model
A `District` has an `Area`	r		TMv6	CC Generic Organisation Model
A `Region` has an `Area`	r		TMv6	CC Generic Organisation Model
A `City` has an `Area`	r		TMv6	CC Generic Organisation Model
A `Municipality` has an `Area`	r		TMv6	CC Generic Organisation Model
An `Organisation` has a `ResponsabilityRol`	r		TMv6	CC Generic Organisation Model
An `Organisation` has an `AdministrativeZone`	r		TMv6	CC Generic Organisation Model
An `Organisation` may have `ContactDetails`	r		TMv6	CC Generic Organisation Model
A `ResponsabilityRole` is a particular role an `Organisation` or an `OrganisationPart` as regards the responsability it will have as regards specific data	g	e.g. data origination, data augmentation, data aggregation, data distribution, planning, operation, control, ownership, etc.	TMv6	CC Responsability Role Model
An `Organisation` may have `ResponsabilityRole`	r		TMv6	CC Responsability Role Model
An `OrganisationPart` may have `ResponsabilityRole`	r		TMv6	CC Responsability Role Model
A `ResponsabilityRoleAssignment` is the assignment of one or more `ResponsabilityRole` to an `Organisation` or an `OrganisationPart` as regards the responsability it will have as regards specific data (e.g. ownership, planning, etc.) and the management of this data (e.g. distribution, update, etc.)	g		TMv6	CC Responsability Role Model
A `ResponsabilityRole` has a `ResponsabilityRoleAssignment`	r		TMv6	CC Responsability Role Model
A `ResponsabilitySet` is a list of possible responsabilities over one or more `Entity` in `Version`, resulting from the porcess of the assignment of `ResponsabilityRole` (usch as data origination, ownership, etc,) on specific data (instances) to `Organisation` or `OrganisationPart`.	g		TMv6	CC Responsability Role Model
A `ControlCentre` is an `OrganisationPart` form an operational team who are responsible for issuing commands to control the services	g		TMv6	CC Generic Organisation Model
An `OrganisationPart` is a part of an `Organisation` to which specific responsabilities upon the data and data management may be assigned	g		TMv6	CC Generic Organisation Model
An `OrganisationPart` may have one or more `OrganisationPart`	r		TMv6	CC Generic Organisation Model
An `OrganisationPart` manages data	r		TMv6	CC Generic Organisation Model
An `AddressablePlace` is a type of `Place` to which `Passenger` may refer to indicate the `Origin` or a `Destination` of a trip and that is so specific that it has an `Address`	g		TMv6	CC Topographic Place Model
An `AddressablePlace` is a `Place`	r		TMv6	CC Topographic Place Model
An `Origin` may have an `AddressablePlace`	r		TMv6	CC Topographic Place Model
A `Destination` may have an `AddressablePlace`	r		TMv6	CC Topographic Place Model
A `Block` is the work of a `Vehicle` from the time it leaves a `ParkingPoint` after parking until its next return to park at a `ParkingPoint`	g	Start time of BLOCK in principle this can be derived from the Start time of the first journey and the preparation duration. End time of BLOCK in principle this can be derived from the Start time of the last journey and the finishing duration.	TMv6	TI Vehicle Service Model
A `Vehicle` has a `Block`	r		TMv6	TI Vehicle Service Model
A `Block` has one or more `BlockPart`	r		TMv6	TI Vehicle Service Model
A `BlockPart` is a `JourneyPart` of a `VehicleJourney` in a `Block`	g		TMv6	TI Vehicle Service Model
A `JourneyPart` is a part of a `VehicleJourney` created according to a specific functional purpose, for instance in siturations when vehicle coupling on separating occurrs.	g		TMv6	TI Coupled Journey Model
A `JourneyPart` belongs to a `VehicleJourney`	r		TMv6	TI Coupled Journey Model
A `ParkingPoint` is a `TimingPoint` where a `Vehicle` may stay unattended for a long time.	g	A `Vehicle` 's return to a `ParkingPoint` marks the end of a `Block`	TMv6	NT Vehicle and Crew Point Model
A `TimingPoint` is a `Point` against which the timing information necessary to build schedules may be recorded	g		TMv6	NT Journey Pattern Model
A `TimingPoint` is a `Point`	r		TMv6	NT Journey Pattern Model
A `Connection` is the physical (spatial) possibility for a `Passenger` to change from one `PublicTransportVehicle` to another `PublicTransportVehicle` to continue the `Trip` determined by to `ScheduledStopPoint`	g	Different times may be necessary to cover the link between these points, depending on the kind of `Passenger`. NT Service Pattern Model	TMv6	NT Journey Pattern Model
A `Connection` has two `PublicTransportVehicle`	r	Different times may be necessary to cover the link between these points, depending on the kind of `Passenger`. NT Service Pattern Model	TMv6	NT Journey Pattern Model
A `Trip` may have one or more `Connection`	r		TMv6	NT Journey Pattern Model
A `ConnectionEnd` is one end of a `Connection`	g		TMv6	NT Journey Pattern Model
A `Connection` has an `ConnectionEnd`	r		TMv6	NT Journey Pattern Model
A `DatedBlock` is the work of a `Vehicle` on a particular `OperatingDay` from the time it leaves a `ParkingPoint` after parking until its next return to park at a `ParkingPoint`	g		TMv6	TI Vehicle Service Model
A `DatedBlock` is the work of a `Vehicle`	r		TMv6	TI Vehicle Service Model
A `DatedBlock` happens on a `OperatingDay`	r		TMv6	TI Vehicle Service Model
A `NormalDatedBlock` is a `DatedBlock` identical to a long-terms planned `Block`	g	Possibly updated according to short-term modifications decided by the control staff	TMv6	TI Vehicle Service Model
A `NormalDatedVehicleJourney` is a `DatedVehicleJourney` identical to a long-term planned `VehicleJourney`	g	Possibly updated according to short-term modifications of the `ProductionPlan` decided by the control staff	TMv6	TI Dated Journey Model
A `Vehicle` leaves a `ParkingPoint`	r		TMv6	TI Vehicle Service Model
A `Vehicle` is parked in a `ParkingPoint`	r		TMv6	TI Vehicle Service Model
A `Vehicle` returns to a `ParkingPoint`	r		TMv6	TI Vehicle Service Model
A `ReliefOpportunity` is a time in a `Block` where a `Vehicle` passes a `ReliefPoint`	g	This opportunity may or may not be actually used for a relief	TMv6	TI Vehicle Service Model
A `ReliefPoint` is a `TimingPoint` where a relief is possible.	g	i.e. a driver may take on or hand over a `Vehicle`. \\ The `Vehicle` may sometimes be left unattended.	TMv6	TI Vehicle Service Model
A `DatedPassingTime` is a `PassingTime` on a particular `OperatingDay`	g		TMv6	TI Passing Times Model
A `DatedPassingTime` is a `PassingTime`	r		TMv6	TI Passing Times Model
A `PassingTime` is a time data concerning `PublicTransportVehicle` passing a particular `Point`; e.g. arrival time, departure time, waiting time.	g		TMv6	TI Passing Times Model
A `TargetPassingTime` is time data about when a `PublicTransportVehicle` should pass a particular `PointInJourneyPattern` on a particular `DatedVehicleJourney` in order to match the latest valid plan	r		TMv6	TI Passing Times Model
A `TimetableFrame` is a set of `TimetableData` to which the same `ValidityCondition` has been assigned	g		TMv6	Timetable Frame Model
A `TimetabledPassingTime` is a long-term planned time data concerning `PublicTransportVehicle` passing a particular `PointInJourneyPattern` on a specified `VehcleJourney` for a certain `DayType`	g		TMv6	NT Passing Times Model
A `DatedVehicleJourney` is a particular `Journey` of a `Vehicle` on a particular `OperatingDay` including all modifications possibly decided by the control staff a	g		TMv6	TI Dated Journey Model
A `DatedVehicleJourney` is a `Journey`	r		TMv6	TI Dated Journey Model
A `DatedVehicleJourney` happens on a `OperatingDay`	r		TMv6	TI Dated Journey Model
A `DatedVehicleJourney` may have modifications	r		TMv6	TI Dated Journey Model
A `Vehicle` may have a `DatedVehicleJourney`	r		TMv6	TI Dated Journey Model
An `OnBoardStay` is the permission to board early before the `Journey` or stay on board after it	g		TMv6	CC Facility Model
A `Journey` may have one or two `OnBoardStay`	r		TMv6	CC Facility Model
A `DayOfWeek` is a particular week day	r	From Monday to Sunday	TMv6	CC Service Calendar Model
A `DefaultConnection` is the physical (spatial) possibility for a `Passenger` to change from one `PublicTransportVehicle` to another `PublicTransportVehicle` to continue the `Trip`. It specifies default times to be used to change from one mode of transport to another at an area or national level as specified by a `TopographicPlace, =StopArea or =SiteElement`. It may be restricted to a specific `Mode` or `Operator` or only apply in particular direction of transfer, e.g. bus to rail may have a different time for rail to bus.	g		TMv6	NT Service Connection Model
A `DefaultConnectionEnd` is the end of a `DefaultConnection`	g		TMv6	NT Service Connection Model
A `Trip` may have a `DefaultConnection`	r		TMv6	NT Service Connection Model
A `DefaultConnection` have two `PublicTransportVehicle`	r		TMv6	NT Service Connection Model
A `DefaultDeadRunRunTime` is the time taken to traverse a `TimingLink` during a `DeadRun`, for a specified `TimeDemandType`. This time may be superseded by the `JourneyPatternRunTime` or =VehicleJourneyRunTime=if these exist.	g		TMv6	TI Time Demand Times Model
A `Transfer` is a couple of `Point` located sufficiently near that it may represent for a `Passenger` a possibility to reach one of these `Point` when starting at the other one in a timescale which is realistic when carrying out a trip, e.g. `Access`	g		TMv6	NT Service Connection Model
A `TransferEnd` is an `EndPoint` of a `Transfer`	g		TMv6	CC Generic Place Model
A `TransferRestriction` is a constraint that can be applied on a `Connection` or `Interchange` between two `ScheduledStopPoint`, preventing or forbidding the `Passenger` to use it.	g		TMv6	NT Routing Constraint Model
An `Interchange` is the scheduled possibility for `Transfer` of `Passenger` between two `ServiceJourney` at the same or different `ScheduledStopPoint`	g		TMv6	TI Interchange Model
A `SiteConnection` is the physical (spatial) possibility for a `Passenger` to change from one `PublicTransportVehicle` to another to continue the `Trip`.	g	- Determined by physical locations such as `Site` and/or its componentes and/or `Entrance`, in particular `StopPlace` and/or its components \\ - Different times may be necessary to cover the resulting distance, depending on the kind of `Passenger`	TMv6	NT Service Connection Model
A `SiteConnectionEnd` is one end of a `SiteConnection`	g		TMv6	NT Service Connection Model
A `TimingLink` is an ordered paired of `TimingPoint` for which run times may be recorded.	g		TMv6	NT Timing Pattern Model
A `TimingLink` has at least a pair of `TimingPoint`	r		TMv6	NT Journey Pattern Model
A `TimingLinkInJourneyPattern` is the position of a `TimingLink` in a `JourneyPattern`. This entity is needed if a `TimingLink` is repeated in the same `JourneyPattern`, and separate information is to be stored about each iteration of the `TimingLink`	g		TMv6	NT Timing Pattern Model
A `TimingPattern` is the subset of a `JourneyPattern` made up only of `TimingPoint` in `JourneyPattern`	g		TMv6	NT Timing Pattern Model
A `TimingPattern` is a `JourneyPattern`	r		TMv6	NT Timing Pattern Model
A `TimingPattern` has `TimingPoint`	r		TMv6	NT Timing Pattern Model
A `TimingPointInJourneyPattern` is a `Point` in a `JourneyPattern` which is a `TimingPoint`	r		TMv6	NT Journey Pattern Model
A `TimingPointInJourneyPattern` is a `TimingPoint`	r		TMv6	NT Journey Pattern Model
A `JourneyPattern` may have `TimingPointInJourneyPattern`	r		TMv6	NT Journey Pattern Model
A `DefaultInterchange` is a quality parameter fixing the acceptable duration (standard and maximum) for an `Interchange` to be planned between two `ScheduledStopPoint`. This parameter will be used to control whether any two `VehicleJourney` serving those points may be in connection.	g		TMv6	TI Interchange Model
An `Interchange` has a `DefaultInterchange`	r		TMv6	TI Interchange Model
A `DefaultServiceJourneyRunTime` is the default time taken by a `Vehicle` to traverse a `TimingLink` during a `ServiceJourney` for a specified `TimeDemandType`. This time may be superseded by the `JourneyPatternRunTime` or `VehicleJourneyRunTime` if these exist.	g		TMv6	TI Time Demand Times Model
A `TimeDemandType` is an indicator of traffic conditions or other factors which may affect vehicle run or wait times. It may be entered directly by the scheduler or defined byt the use of `TimeBand`	g		TMv6	TI Time Demand Times Model
A `TimeDemandTypeAssignment` is the assignment of a `TimeDemandType` to a `TimeBand` depending on the `DayType` and `GroupOfTimingLink`	g		TMv6	TI Time Demand Times Model
A `GroupOfTimingLink` is a set of `TimingLink` grouped together according to the similarity of `TimeBand` which are relevant to them. There may be a `GroupOfTimingLink` which covers all `TimingLink`, for use when different `GroupOfTimingLink` are not needed.	g		TMv6	NT Timing Pattern Model
A `GroupOfTimeBand` is a grouping of `TimeBand`	g		TMv6	CC Service Calendar Model
A `GroupOfTimeBand` has two or more `TimeBand`	r		TMv6	CC Service Calendar Model
A `FlexibleArea` is the specialisation of a `FlexibleQuay` (which is abstract) to identify what is the catchment area for a flexible service (so that a stop finder can find the nearest available types of transport). It is a named zone visited by a particular mode of transport. It is part of the site dataset rather than the service dataset, since it can be defined and exist independently of an actual service.	g		TMv6	NT Flexible Stop Place Model
A `FlexxibleArea` is a `FlexibleQuay`	r		TMv6	NT Flexible Stop Place Model
A `FlexibleQuay` is a physical zone such as a section of a road where a `FlexibleService` is available on demand. The existance of the `Zone` makes the services visible to `Journey` planners looking for available services for an area	g		TMv6	NT Flexible Stop Place Model
A `FlexibleQuay` is a `Zone`	r		TMv6	NT Flexible Stop Place Model
A `FlexibleService` has a `FlexibleQuay`	r		TMv6	NT Flexible Stop Place Model
A `FlexibleRoute` is the specialisation of `Route` for a `FlexibleService`. May include both point and zonal areas and ordered and unordered sections.	g		TMv6	NT Flexible Network Model
A `FlexibleService` has a `FlexibleRoute`	r		TMv6	NT Flexible Network Model
A `FlexibleRoute` is a `Route`	r		TMv6	NT Flexible Network Model
A `FlexibleLine` is the specialisation of `Line` for `FlexibleService`. As all the service on a `Line` may not all be flexible, flexibility itself is described at `JourneyPattern` level (meaning that a separate `JourneyPattern` is needed for each type of flexibiliby available for the line.	g		TMv6	NT Flexible Network Model
A `FlexibleLine` is a `Line`	r		TMv6	NT Flexible Network Model
A `FlexibleLinkProperties` is a set of properties describing the flexible characteristics of a `Link`. A composition is used with `Link` in order to avoid multiple inheritance and a type explosion of link subtypes.	g		TMv6	NT Flexible Network Model
A `FlexiblePointProperty` is a set of characteristics describing the possible flexibility of `Point`. A composition is used with `Point` in order to avoid multiple inheritance	g		TMv6	NT Flexible Network Model
A `Point` may have a `FlexiblePointProperty`	r		TMv6	NT Flexible Network Model
A `FlexibleRoute` is a specialisation of `Route` for flexible service. May include both point and zonal areas and ordered and unordered sections.	g		TMv6	NT Flexible Network Model
A `FlexibleRoute` is a `Route`	r		TMv6	NT Flexible Network Model
A `FlexibleServiceProperty` is an additional characteristic of `FlexibleService`. A service may be partly fixed, partly flexible.	g		TMv6	NT Flexible Network Model
A `FlexibleService` may have some `FlexibleServiceProperty`	r		TMv6	NT Flexible Network Model
A `FlexibleStopAssignment` is the allocation of a `ScheduledStopPoint` to a specific `FlexibleStopPlace` and also possibly a `FlexibleArea` or `HileAndRideArea`. May be subject to a `ValidityCondition`	g	i.e. a `StopPoint` of a `ServicePattern` or `JourneyPattern`	TMv6	NT Flexible Stop Place Model
A `HailAndRideArea` is the specialisation of a `FlexibleQuay` to identify the catchment zone for a hail and ride service (so that a stop finder can finde the neares available types of transport). It is a named zone visited by a particular mode of transport and may be designated by a start point and end point on the road. It is part of the Site dataset rather than the service dataset, since it can be defined and exists independently of an actual service.	r		TMv6	NT Flexible Stop Place Model
A `HailAndRideArea` is a `FlexibleQuay`	r		TMv6	NT Flexible Stop Place Model
A `FlexibleStopPlace` is a specialisation of a `StopPlace` describing a stop of a `FlexibleService`. It may be composed of `FlexibleArea` or `HailAndRideArea` identifying the catchmetn areas for `FlexibleService` (when they use `Area` or `FlexibleQuay`. Some `FlexibleService` also use regular `StopPlace` for their `Stop`. When assigned to a `ScheduledStopPoint` the corresponding `ScheduledStopPoint` is supposed to be a `Zone` (the centroid point of the `Zone` being the `ScheduledStopPoint`)	g		TMv6	NT Flexible Stop Place Model
A `Garage` is a `Facility` used for parking and maintaining vehicles. `ParkingPoint` in a Garage are called `GaragePoint`	g		TMv6	NT Vehicle & Crew Point Model
A `Garage` is a `Facility`	r		TMv6	NT Vehicle & Crew Point Model
A `GaragePoint` is a subtype of `ParkingPoint` located in a `Garage`	g		TMv6	NT Journey Pattern Model
A `GaragePoint` is a `ParkingPoint`	r		TMv6	NT Journey Pattern Model
A `HeadwayInterval` is a time interval or a duration defining a headway period and characterizing `HeadwayJourneyGroup`	g	E.g. every 10 min, every 4-6 min.	TMv6	NT Journey Pattern Model
A `HeadwayJourneyGroup` is a group of `VehicleJourney` following the same `JourneyPattern` having the same `HeadwayInterval` between specified start and end time	g	E.g. every 10 min	TMv6	NT Journey Pattern Model
A `HireService` is a specialisation of `LocalService` dedicated to hire services	g	e.g. cycle hire, car hire…	TMv6	NT Local Commercial Service Model
A `HireService` is a `LocalService`	r		TMv6	NT Local Commercial Service Model
A `ManoeuvringRequirement` is a classification of requirements for a `PublicTransportVehicle` according to the manoeuvring capabilities of the `Vehicle`	g		TMv6	CC Vehicle Type Model
A `PublicTransportVehicle` may have a `ManoeuvringRequirement`	r		TMv6	CC Vehicle Type Model
An `ImpossibleManoeuvre` is a specification of impossible move for a certain type of `Vehicle` . It specifies from which `InfrastructureLink` to which other `InfrastructureLink` a certain `VehicleType` cannot proceed due to physical restrictions	g		TMv6	NT Network Restriction Model
An `InfrastructureLink` is a super-type including all `Link` of the physical network (e.g. `RailwayElement`	g		TMv6	NT Infrastructure Network Model
A `MeetingRestriction` is a pair of `InfrastructureLink` where `Vehicle` of specified `VehicleType` are note allowed to meet	g		TMv6	NT Network Restriction Model
A `RailwayElement` is a type of `InfrastructureLink` used to describe a `RailwayNetwork`	g		TMv6	NT Network Restriction Model
A `RailwayElement` is an `InfraestructureLink`	r		TMv6	NT Network Restriction Model
A `RailwayNetwork` have two or more `RailwayElement`	r		TMv6	NT Network Restriction Model
A `RailwayJunction` is a type of `InfrastructurePoint` used to describe a `RailwayNetwork`	g		TMv6	NT Network Restriction Model
A `RailwayJunction=is a type of =InfrastructurePoint`	r		TMv6	NT Network Restriction Model
An `InfrastructureFrame` is a set of `InfrastructureNetworkData` (and other data logically related to these) to which the same `ValidityCondition` have been assigned	g		TMv6	Infrastructure Frame Model
An `InfrastructureFrame` is a set of `InfrastructureNetworkData`	r		TMv6	Infrastructure Frame Model
An `InfrastructureLink` is a super-type including all `Link` of the `PhysicalNetwork` (e.g. `RailwayElement`)	g		TMv6	NT Infrastructure Network Model
An `InfrastructurePoint` is a super-type including all `Point` of the `PhysicalNetwork` (e.g. `RailwayJunction`).	r		TMv6	NT Infrastructure Network Model
A `WireElement` is a type of `InfrastructureLink` used to describe a wire `Network`	g		TMv6	NT Infrastructure Network Model
A `WireElement` is a type of `InfrastructureLink`	r		TMv6	NT Infrastructure Network Model
A `WireJunction` is a type of =InfrastructurePoint=used to describe a wire network	g		TMv6	NT Infrastructure Network Model
A `RoadElement` is a type of `InfrastructureLink` used to describe a Road Network	g		TMv6	NT Infrastructure Network Model
A `RoadElement` is an `InfrastructureLink`	r		TMv6	NT Infrastructure Network Model
A `RoadJunction` is a type of `InfrastructurePoint` used to describe a road network	g		TMv6	NT Infrastructure Network Model
A `RoadJunction` is a type of `InfrastructurePoint`	r		TMv6	NT Infrastructure Network Model
An `InstalledEquipment` is an `Item` of `Equipment` either fixed (`PlaceEquipment`) or on board i.e. associated with `Vehicle`. This `Equipment` is materialised as opposed to a service (`LocalService`) considered as an immaterial `Equipment`	g		TMv6	CC Generic Equipment Model
An `InterchangeRule` are conditions for considering `Journey` to meet or not to meet, specified indirectly: by a particular `Mode`, `Direction` or `Line`. Such conditions may alternatively be specified directly, indicating the corresponding services. In this case they are ither a `ServiceJourneyPatternInterchange` or a `ServiceJourneyInterchange`.	g		TMv6	TI Interchange Rule Model
An `InterchangeRuleParameter` is the assignment of parameters characterising an `InterchangeRule`	g		TMv6	TI Interchange Rule Model
An `InterchangeRuleTiming` are the timings for an `InterchangeRule` for a given `TimeDemandType` or `TimeBand`	g		TMv6	TI Interchange Rule Model
A `JourneyAccounting` are the parameters characterizing `VehicleJourney` or `SpecialService` used	g		TMv6	TI Journey Accounting Model
A `JourneyFrequencyGroup` is a group of `Journey` defined in order to describe special behaviour like frequency based services or rhythmical services.	g		TMv6	TI Vehicle Journey Times Model
A `JourneyHeadway` is a `HeadwayInterval` information that is available for all the `VehicleJourney` running on the `JourneyPattern` for a given `TimeDemandType` at a given `TimingPoint`. This is a default value that can be superseded by `VehicleJourneyHeadway` if available (`HeadwayJourneyGroup` being a more detailed way of describing headway services	g		TMv6	TI Journey Timing Model
			TMv6

pathway_mode:

1
walkway

2
stairs

3
moving sidewalk/travelator

4
escalator

5
elevator

6
fare gate (or payment gate)

7
exit gate: Indicates a pathway exiting an area where proof-of-payment is required into an area where proof-of-payment is no longer required.

Competency Questions

Fact/Competency Question Comments Source (provenance)

10 UC9 Fares

Facts

Facts	Status	Comments	Source (provenance)	SubSource
An user makes a journey	r		UC9
A journey needs a ticket at least	r		UC9
A ticket must be validated in the Entrance	r		UC9
A ticket may be validated in the Exit	r		UC9
A ticket is based in fares	r		UC9
Fares dependes on age, rol, place of residence, seats to occupy, distance, areas, type of ticket	r		UC9
Some users don't need tickets	r		UC9
Users who don't need tickets have to go with someone who have it	r		UC9
Babies under 3 year-old don't need a ticket	r		UC9
A fare has a cost	r		UC9
Some fares are free	r		UC9
Children from 3 to 7 don't pay a fare	r		UC9
Children from 3 to 7 must validate tickets	r		UC9
In some public transports a pet need a ticket	r		UC9
An user with visual impairment brings a guideDog	r		UC9
People with impaired vision have special fares	r		UC9
guideDogs are allowed to travel for free	r		UC9
An user may have a card	r		UC9
A card is paid monthly or annually	r		UC9
The card itself has a price	r		UC9
A card has a fare	r		UC9
The fare of the carnet is based on the zones	r		UC9
The public transport service of a region is divided into zones	r		UC9
A special service has a spacial fare	r		UC9
A `route` may have a `fare`	r	route is defined by the name of the file routes.txt	gtfs	fare_rules.txt
A `fare` must have a `fare_id`	r	fare is defined by the name of the file fare_rules.txt. Identifies a fare class	gtfs	fare_rules.txt
A `route` has an `origin_zone`	r	origin_zone is named in origin_id	gtfs	fare_rules.txt
A `route` has a `destination_zone`	r	destination_zone is named in destintation_id	gtfs	fare_rules.txt
An `origin_zone` has an `origin_id`	r		gtfs	fare_rules.txt
A `destination_zone` has a `destination_id`	r		gtfs	fare_rules.txt
Fares have a `fare_id`	r		gtfs	fare_atributes.txt
A `fare_id` is an ID	r		gtfs	fare_atributes.txt
A `fare` can apply to multiple `origin_zones`	r	"If a fare class has multiple origin zones, create a record in fare_rules.txt for each `origin_id`	gtfs	fare_rules.txt
A `fare` can apply to multiple `destination_zones`	r	"If a fare class has multiple destination zones, create a record in fare_rules.txt for each `destination_id`	gtfs	fare_rules.txt
A `fare` must have a `price`	r		gtfs	fare_attributes.txt
Fares have a `currency_type`	r		gtfs	fare_attributes.txt
A `passenger` pays with a `payment_method`	r		gtfs	fare_attributes.txt
The fare allows to make `transfers`	r		gtfs	fare_attributes.txt
A `fare` may have an `expiration_date`	r	In gtfs fare_atributes.txt identifies `transfer_duration` as a non-negative integer, optional, which value is the length of time in seconds before a transfer expires. When `transfers=0` this field can be used to indicate how long a ticket is valid for or it can be left empty.	gtfs	fare_attributes.txt
A fare may have a `route_id`	r	gtfs fare_rules.txt identifies a route associated withe the fare class. If several routes withe the same fare attributes exist, create a record in `fare_rules.txt` for each route	gtfs	fare_rules.txt
A `BookingArrengement` is an `Arrangement` for `FlexibleLine`	g		TMv6	NT Flexible Network Model
A `FlexibleLine` is the specialisation of `Line` for `FlexibleService`. As all the `Service` on a `Line` may not all be flexible, flexibility itself is described at `JourneyPattern` level (meaning that a separate `JourneyPattern` is needed for each type of flexibility available for the line).	g		TMv6	NT Flexible Network Model
A `Line` is a group of `Route` which is generally known to the public by a similar name or number	g		TMv6	NT Route Model
A `Line` has one or more `Route`	r		TMv6	NT Route Model
A `JourneyPattern` is an ordered list of `ScheduledStopPoint` and `TimingPoint` on a single `Route`, describing the pattern of working for `PublicTransportVehicle`.	g		TMv6	NT Journey Pattern Model
A `JourneyPattern` have `ScheduledStopPoint`	r		TMv6	NT Journey Pattern Model
A `JourneyPatternHeadway` is a `HeadwayInterval` information that is available for all the `VehicleJourney` running on the `JourneyPattern`	g	This is a default value that can be superseded by the `VehicleJourneyHeadway` on a specific `Journey`. This information must be consistent with `HeadwayJourneyGroup` if available	TMv6	TI Journey Pattern Times Model
A `JourneyPatternHeadway` is a `HeadwayInterval`	r		TMv6	TI Journey Pattern Times Model
A `JourneyPattern` may have a `JourneyPatternHeadway`	r		TMv6	TI Journey Pattern Times Model
A `JourneyPatternLayover` is the time allowance at the end of each `Journey` on a specified `JourneyPattern`	g	This layover supersedes any global layover and may be superseded by a specific `VehicleJourneyLayover`	TMv6	TI Journey Pattern Times Model
A `JourneyPattern` may have a `JourneyPatternLayover`	r		TMv6	TI Journey Pattern Times Model
A `JourneyPatternRunTime` is the time taken to traverse a `TimingLink` in a particular `JourneyPattern` for a specified `TimeDemandType`	g	If it exists it will override the `DefaultServiceJourneyRunTime` and `DefaultDeadRunRunTime`	TMv6	TI Journey Pattern Times Model
A `TimingLink` may have a `JourneyPatternRunTime`	r		TMv6	TI Journey Pattern Times Model
A `JourneyPatternWaitTime` is the time a `Vehicle` has to wait at a specific `TimingPointInJourneyPattern` for a specified `TimeDemandType`	g	This wait time can be superseded by a `VehicleJourney`	TMv6	TI Journey Pattern Times Model
A `TimeDemandTime` may have a `JourneyPatternWaitTime`	r		TMv6	TI Journey Pattern Times Model
A `JourneyRunTime` is the time taken to traverse a `TimingLink` in a particular `JourneyPattern` for a specified `TimeDemandType`	g	If exists, it will override the `DefaultServiceJourneyRunTime` and `DefaultDeadRunRunTime`	TMv6	TI Journey Pattern Times Model
A `JourneyTiming` is a time-related information referring to `Journey` timing whose value depends on the time of use and so can be associated with a `TimeDemandType`, `TimeBand` or `OperationalContext`	r		TMv6	TI Journey Pattern Times Model
An `OperationlContext` is a characterisation of a set of operational objects such as timing or links determined either by a `Department` or by an `OrganisationalUnit`	r		TMv6	TI Journey Pattern Times Model
A `JourneyWaitTime` is the time a `Vehicle` has to wait at a specific `TimingPointInJourneyPattern` for a specified `TimeDemandType`	g	This can be superseded by `VehicleJourney`	TMv6	TI Journey Timing Model
A `TimeDemandTime` may have a `JourneyRunTime`	r		TMv6	TI Journey Timing Model
A `Route` may have `JourneyPattern`	r		TMv6	NT Journey Pattern Model
A `Journey` are the common properties of `VehicleJourney` and `SpecialService`	g		TMv6	TI Vehicle Journey Model
A `Journey` is a set of properties	r		TMv6	TI Vehicle Journey Model
A `VehicleJourney` has a `Journey`	r		TMv6	TI Vehicle Journey Model
A `SpacialService` has a `Journey`	r		TMv6	TI Vehicle Journey Model
A `SpecialService` is the work of a `Vehicle` that is not planned in a classical way	g	i.e. thai is generally not based on `VehicleJourney` using `JourneyPattern`. \\ It involves specific characteristics such as specific access rights and/or may be operated under specific circumstances	TMv6	TI Vehicle Journey Model
A `VehicleJourney` follows a `JourneyPattern`	r		TMv6	TI Vehicle Journey Model
A `ClassOfUse` is a classification of `ServiceClass`	r		TMv6	CC Service Restriction Model
A `Fare` is a `ServiceClass`	r	CC Service Restriction Model	TMv6	CC Service Restriction Model
A `ClassOfUse` is a category of `ServiceClass`	r	CC Service Restriction Model	TMv6	CC Service Restriction Model
A `TicketScope` is a scope of ticket	g		TMv6	CC Service Restriction Model
A `TicketValidatorEquipment` is a specialisation of `PassengerEquipment` (`PlaceEquipment`) describing ticket validators	g		TMv6	NT Ticketing Equipment Model
A `TicketValidatorEquipment` is a `PassengerEquipment`	r		TMv6	NT Ticketing Equipment Model
A `TicketValidatorEquipment` is a `PlaceEquipment`	r		TMv6	NT Ticketing Equipment Model
A `TicketingEquipment` is a specialisation of `PassengerEquipment` for ticketing	g		TMv6	NT Ticketing Equipment Model
A `TicketingEquipment` is a `PassengerEquipment`	r		TMv6	NT Ticketing Equipment Model
A `CoupledJourney` is a complete `Journey` operated by a `CoupledTrain` composed of two or more `VehicleJourney` remaining coupled together all along a `JourneyPattern`. A `CoupledJourney` may be viewed as a single `VehicleJourney`	g		TMv6	TI Coupled Journey Model
A `CoupledJourney` can be a `VehicleJourney`	r		TMv6	TI Coupled Journey Model
A `CoupledJourney` is a `Journey`	r		TMv6	TI Coupled Journey Model
A `CoupledJourney` is operated by a `CoupleTrain`	r		TMv6	TI Coupled Journey Model
A `CoupledJorney` is composed of two or more `VehicleJourney`	r		TMv6	TI Coupled Journey Model
A `CourseOfJourney` is a part of a `Block` composed of consecutive `VehicleJourney` defined for the same `DayType`, all operated in the same `Line`	g		TMv6	TI Vehicle Service Model
A `CourseOfJourney` is part of a `Block`	r		TMv6	TI Vehicle Service Model
A `CourseOfJourney` is composed of `VehicleJourney`	r		TMv6	TI Vehicle Service Model
A `CourseOfJourney` is defined for the same `DayType`	r		TMv6	TI Vehicle Service Model
A `CourseOfJourney` is operated in the same `Line`	r		TMv6	TI Vehicle Service Model
A `CommonSection` is a part of the `PublicTransportNetwork` where the `Route` of several `JourneyPattern` are going in parallel and where the syncronisation of `ServiceJourney` may be planned and controlled with respect to commonly used `Link` and `ScheduledStopPoint`	g	A `CommonSection` is defined arbitrarily and need not cover the total lengths of topologically bundled sections	TMv6	TI Vehicle Service Model
A `CommonSection` is a part of the `PublicTransportNetwork`	r		TMv6	NT Common Section Model
A `CommonSection` have more than one `Route`	r		TMv6	NT Common Section Model
A `ServiceJourney` can be syncronised with another `ServiceJourney`	g		TMv6	NT Common Section Model
The syncronization of a `ServiceJourney` can be planned	r		TMv6	NT Common Section Model
The syncronization of a `ServiceJourney` can be controlled	r		TMv6	NT Common Section Model
A `Route` can go in parallel with other `Route`	r		TMv6	NT Common Section Model
A `ServiceJourney` is a `Passenger` carrying `VehicleJourney` for one specified `DayType`. The pattern of working is defined by a `ServiceJourneyPattern`	g		TMv6	NT Common Section Model
A `ServiceJourneyPattern` is the `JourneyPattern` for a (`Passenger` carrying) `ServiceJourney`	g		TMv6	NT Common Section Model
A `ServiceJourneyInterchange` is the scheduled possibility for `Transfer` of `Passenger` between two `ServiceJourney` at the same or different `ScheduledStopPoint`	g		TMv6	TI Interchange Model
A `ServiceJourneyPatternInterchange` is a recognised/organised possibility for `Passenger` to change `PublicTransportVehicle` using two `ScheduledStopPoint` (which may be identical) on two particular `ServiceJourneyPattern`, including the maximum wait duration allowed and the standard to be aimed at.	g	These may supersede the times given for the `DefaultInterchange`. \\ Schedulers may use this entity for synchronisation of `Journey`	TMv6	TI Interchange Model
A `ServiceExclusion` is a constraint expressing the fact that the service, on a specific `JourneyPattern` cannot operate when another (regular) `Service` operates	g	The `JourneyPattern` is usually a flexible transport service `JourneyPattern`. \\ This may occur only on a subpart of the `JourneyPattern` or only on one or some specific `ScheduledStopPoint`	TMv6	NT Routing Constraint Model
A `ServiceLink` is a `Link` between an orderd pair of `ScheduledStopPoint`	g		TMv6	NT Service Pattern Model
A `ServiceLink` is a `Link`	r		TMv6	NT Service Pattern Model
A `ServicePattern` is the subset of a `JourneyPattern` made up only of `StopPoint` in `JourneyPattern`	g		TMv6	NT Service Pattern Model
A `ServiceRestriction` are the parameters describing the limitations as regards the use of `Equipment` or `Service`	g		TMv6	CC Service Restriction Model
An `Equipment` may have a `ServiceRestriction`	r		TMv6	CC Service Restriction Model
A `CommunicationService` is the specialisation of `LocalService` dedicated to communication services	g		TMv6	NT Local Commercial Service Model
A `ComplaintService` is the specialisation of `CustomerService` for complaints	g		TMv6	NT Local Commercial Service Model
A `CommunicationService` is a `LocalService`	r		TMv6	NT Local Commercial Service Model
A `ComplaintService` is a `CustomerService`	r		TMv6	NT Local Commercial Service Model
A `CustomerService` is a generic specialisation of `LocalService` for `CustomerService` (lost properties, meeting point, complaints…)	g		TMv6	NT Local Commercial Service Model
A `CustomerService` is a `LocalService`	r		TMv6	NT Local Commercial Service Model
A `LostPropertyService` is a specialisation of `CustomerService` for lost properties	g		TMv6	NT Local Commercial Service Model
A `LostPropertyService` is a `CustomerService`	r		TMv6	NT Local Commercial Service Model
A `RetailService` is the specialisation of `LocalService` dedicated to `RetailService`	g		TMv6	NT Local Commercial Service Model
A `RetailService` is a `LocalService`	r		TMv6	NT Local Commercial Service Model
A `LugaggeService` is a specialisation of `CustomerService` for luggage services	g	Provides luggage service facilities and characteristics like luggage trolley, free to use, etc. NT Local Service Equipment Model	TMv6	NT Local Commercial Service Model
A `LuggageService` is a `CustomerService`	r		TMv6	NT Local Service Equipment Model
A `LeftLuggageService` is a specialisation of `CustomerService` for left luggage	g	Provides left luggage information like self service locker, locker free, etc.	TMv6	NT Local Service Equipment Model
A `LeftLuggageService` is a `CustomerService`	r		TMv6	NT Local Service Equipment Model
A `MeetingPointService` is a specialisation of `CustomerService` for meeting points	g	Provides characteristics like description, label, etc	TMv6	NT Local Service Equipment Model
A `MeetingPointService` is a `CustomerService`			TMv6	NT Local Service Equipment Model
A `TypeOfStaffing` is a classification for the availability of the `AssistanceStaff` associated with an `AssistanceService`	g	E.g. full time, part time.	TMv6	NT Local Service Equipment Model
An `AssistanceService` has an `AssistanceStaff`	r		TMv6	NT Local Service Equipment Model
An `AssistanceStaff` has a `TypeOfStaffing`	r		TMv6	NT Local Service Equipment Model

Competency Questions

Competency Questions Comments Source (provenance)

How many users

Competency Questions	Comments	Source (provenance)
How many users

11 UC10 Garbage Collection System

Facts

Facts	Status	Comments	Source (provenance)	SubSource
A `RubbishDisposal` is the specialization of `Equipment` for `RubbishDisposal`	g	describing rubbish types	TMv6	NT Passenger Service Equipment Model
A `RubbishDisposal` is an `Equipment`	r		TMv6	NT Passenger Service Equipment Model
A `SanitaryEquipment` is the specialization of `PassengerEquipment` for sanitary facilities.	g		TMv6	NT Passenger Service Equipment Model
A `SanitaryEquipment` is a `PassengerEquipment`	r		TMv6	NT Passenger Service Equipment Model

Competency Questions

Competency Questions Comments Source (provenance)

12 UC11 Carbon Print Awareness

Facts

Fact/Competency Question	Status	Source (provenance)
A passenger may need to send a postcard	r	UC11
A passenger may need to make the passport	r	UC11
A passenger need to know what type of services	r	UC11

Competency Questions

Competency Questions Comments Source (provenance)

Competency questions

Table of Contents

1 Siguiendo GTFS to Transmodel & UC-1

2 UC1 Accessible Stops

3 UC2 Accesible coaches

4 UC3 Public WC/Restrooms at Stops

5 UC4 Transport Facilities

6 UC5 Transport issues

7 UC6 Public Bicycles

8 UC7 TP Businness/services inside the PT network

9 UC8 Transportation exchange

10 UC9 Fares

11 UC10 Garbage Collection System

12 UC11 Carbon Print Awareness