xsd.2.0.OJP.OJP_JourneySupport.xsd Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of ojp-java-model Show documentation
Show all versions of ojp-java-model Show documentation
Generates Java model from OJP xsds using jaxb.
The newest version!
OJP/OJP_JourneySupport.xsd - Supporting definitions for journeys on public transport vehicles
[a specialisation of VIA in TMv6] STOP PLACE or SCHEDULED STOP POINT as a VIA for a particular SERVICE PATTERN. Specialisation of a VIA.
Priority of this via point to be displayed when space is limited.
Product category based on NeTEx/SIRI. A product category is a classification for VEHICLE JOURNEYs to express some common properties of journeys for marketing and fare products.
Full name of this product category, e.g., "Autoreisezug" in Switzerland or "Dampfschiff"
Short name or acronym of the product category, likely to be published, e.g., "BAV", "ARZ", "TGV". The product category is more important for publication in Switzerland than Mode / Submode.
A reference to the product category. This is the internal code used within the reference frameworks (NeTEx, SIRI). It is usually not displayed, but interpreted by the technical system, e.g., "ch:1:TypeOfProductCategory:ARZ" (Autoreisezug in Switzerland) or "ch:1:TypeOfProductCategory:BAV".
VIA restrictions for a TRIP.
Reference to specify the via place.
Duration the passenger wants to stay at the via place. Default is 0.
Services running combined with at least parts of this journey, e.g., wing trains. The contained stop sequence interval refers to the original journey.
Interval of stop sequence numbers of a given TimedLeg which may be one or multiple VEHICLE JOURNEYs. The numbering starts with 1. An example is the train from Bern to Zweisimmen that is split in Spiez. The sequence 1-3 is the first sequence, 3-9 the second.
Stop sequence number, where the interval begins (inclusive). If missing, the interval begins at the beginning of the leg (or at the beginning of the journey for uses in StopEvents and TripInfo).
Stop sequence number, where the interval ends (inclusive). If missing, the interval ends at the end of the leg (or at the end of the journey for uses in StopEvents and TripInfo).
Vehicle journey (not dated).
Properties of a service (line and direction): attributes of Continuous Journey Structure or Dated Journey Structure.
Public code of the SERVICE JOURNEY (same meaning as in NeTEx). Examples: "512", "S8" or "Circle Line" or "ICE 488".
[a specialisation of MODE in TMv6] an extended range of VEHICLE MODEs, aggregating them with some SUBMODEs
A product category for the service. This is a classification defined in NeTEx/SIRI used to identify groups of journeys with some special properties for marketing and fare products, e.g., "TE2" for SNCF or a special panorama train "PE" in Switzerland.
Line name or service description as known to the public, e.g., "512", "S8" or "Circle Line" or "ICE 488".
Contains the TrainNumber from NeTEx (TRAIN NUMBER from Transmodel). If several TrainNumber types exist, use the commercial one. In some cases also non-train modes will use TrainNumber.
Contains the Vehicle reference of the vehicle. In Transmodel this may be the VEHICLE id.
References to the OPERATORS. Multiple OPERATORS in case a ContinuousLeg can be operated by more than one operator, especially in the ALTERNATIVE MODE OF OPERATION where there can be dozens of taxi companies and many free-floating sharing companies.
Descriptive text for a route, e.g., "Airport via City Centre".
Via points of the service that may help identify the vehicle to the public (In Transmodel modelled as TRIP REQUEST PLACE.TRIP VIA PLACE.GoVia; it will also most probably be detailed as a VIA and associated DESTINATION DISPLAY in the ROUTE description).
This flag is set if the service can only be used in a restricted way. For example, a specific ACCESS MODE is required (e.g., dragLift) or the LINE is only made available to certain passenger groups (e.g., school buses, hotel shuttles).
Information about the restriction.
Note or service attribute.
Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc.
First serviced stop of a vehicle journey (also VEHICLE MEETING POINT or ADDRESSABLE PLACE).
First stop of the vehicle journey; origin stop point.
Label for first stop.
Last serviced stop of a vehicle journey (also VEHICLE MEETING POINT or ADDRESSABLE PLACE).
Last stop of vehicle journey; destination stop point.
Label for last stop. Should be set for classic public transport. Demand responsive and newer modes of operation will often not have a destination text.
Descriptive text for a route, e.g., "Airport via City Centre".
Vehicle journey that runs at a specific date.
MODE OF OPERATION for scheduled and flexible services (NeTEx).
Reference to an OPERATING DAY.
Possible types of reservation needed for services.
A reservation/booking is required for the service to operate. BookingArrangement should then be used and contain more details.
A reservation/booking is required for the service to call at the stop for boarding and alighting. BookingArrangement should then be used and contain more details.
[equivalent to DATED VEHICLE JOURNEY in TMv6] passenger carrying VEHICLE JOURNEY for one specified DAY TYPE for which the pattern of working is in principle defined by a SERVICE JOURNEY PATTERN. DatedJourney details of a service include its operating days.
The formation elements on the journey level.
Container with information on booking possibilities for this service.
Indicates whether this service needs some kind of reservation or booking to run.
A list of references to SITUATIONs.
A trip location represents the current logical position of a journey service. It can be used similarly to a place e.g., for starting a new trip request from within this service. A trip location does not(!) describe the relative position of a traveller within a vehicle, e.g., the seat.
========================================== Times, Calls, Time context ==========================================
The window of opportunity that the traveller has to perform this leg of the journey (e.g., a bridge is only open during a given interval).
Time at which window begins.
Time at which window ends.
Contains at least scheduled time, but can contain real time and estimated times
time at point as it is published
time as it was recorded
estimated time (for prognosis)
Range for estimated time.
Estimated lower limit for time.
Estimated upper limit for time.
Arrival times of a service at a stop (group of attributes of TIMETABLED PASSING TIME, ESTIMATED PASSING TIME, OBSERVED PASSING TIME, equals MONITORED LEG ARRIVAL).
Departure times of a service at a stop (group of attributes of TIMETABLED PASSING TIME, ESTIMATED PASSING TIME, OBSERVED PASSING TIME, equals MONITORED LEG DEPARTURE).
[same as CALL in SIRI] the meeting of a VEHICLE JOURNEY with a specific SCHEDULED STOP POINT
Arrival times of the service at this stop (group of attributes of TIMETABLED PASSING TIME, ESTIMATED PASSING TIME, OBSERVED PASSING TIME).
Departure times of the service at this stop (group of attributes of TIMETABLED PASSING TIME, ESTIMATED PASSING TIME, OBSERVED PASSING TIME).
A list of references to SITUATIONs.
Status properties for the vehicle call at this stop.
Sequence number of this stop in the service pattern of the journey.
The vehicle journey calls at this stop only on demand.
This stop has not been planned by the planning department.
The vehicle will not call at this stop despite earlier planning.
Boarding will not be allowed at this stop of this journey.
Alighting will not be allowed at this stop of this journey.
The Occupancy structure from SIRI can be used here. It is recommended to mainly have one ExpectedDepartureOccupancy for each FareClass and mainly focus on OccupancyLevel and OccupancyPercentage. For more details have a look at the SIRI documentation.
The Capacity structure also will probably rarely be used and parsed. When used, then it mainly shows elements that are important for accessibility.
Note or attribute.
parameters which describe the status of a DATED VEHICLE JOURNEY
Whether this trip is an additional one that has not been planned. Default is false.
Whether this trip is cancelled and will not be run. Default is false.
Whether this trip deviates from the planned service pattern. Default is false.
Whether this trip may have an undefined delay. Default is false. More details could be provided in a PtSituation.
[equivalent to OCCUPANCY in SIRI] passenger load status of a VEHICLE. If omitted, not known.
[a special form of SERVICE JOURNEY in TMv6] a vehicle movement on a continuous, non-timetabled service.
Alternative transport options.
Personal transport options.
PERSONAL MODE used either for PERSONAL MODE OF OPERATION or in ALTERNATIVE MODE OF OPERATION.
Shared mobility offer.
Container with information on booking possibilities for this service.
A list of references to SITUATIONs.
Vehicle progress relative to timetable service pattern.
Geographical and logical position of a vehicle.
Geographic position of vehicle.
Logical progress of vehicle relative to service pattern.
Bearing in compass degrees in which vehicle is heading (expected to be consistent with Transmodel ROUTE or LEG TRACK and PATH GUIDANCE).
Provides information about the progress of the vehicle along its current link, that is link from previous visited top to current position.
[a view of PLACE in TMv6] a PLACE and access to it by individual transport
Static place.
Location within a (moving) vehicle.
Time when departure/arrival from/to location is required.
Extra time needed before reaching/after leaving this location (an example of a TRIP ACCESS CONSTRAINT. In Transmodel it is modelled more extensively and could relate to ACCESS MODE e.g., walk max. 5 minutes, but cycle 10 minutes).
Options how to access/leave the place by individual transport.
========================================== Filter Groups ==========================================
parameter to control the number of TRIP results before/after a point in time. May NOT be used when departure time at origin AND arrival time at destination are set
The desired number of trip results before the given time (at origin or destination).
The desired number of trip results after the given time (at origin or destination).
Full use of real-time information, including removal of SERVICE JOURNEYS (TRIP REQUEST POLICY.UseRealTime is only a boolean in Transmodel).
Cancelled and delayed SERVICE JOURNEYs are still returned, but an additional explanatory textual information is provided to describe their current real-time status.
Only based on timetable data
Policies that control the trip search behaviour for both public and individual transport.
The number of trip results that the user wants to see at least. Be aware that some implementations will deliver one of the TripResults before the indicated departure time. This means that you can't assume that you get the exact number of results that you asked for in the request from the server.
Time window in which the trips should be, starting from the time specified in PlaceContext. Implements TRIP REQUEST.FlexibilityWindow. All trips within the window should be provided by the implementation.
The way real-time data should be used in the calculation of the trip.
Whether the trip calculation should find a solution that starts immediately (e.g., because the user is already on the way) instead of finding the latest possible start opportunity. Default is FALSE.
The maximum number of interchanges the user will accept per trip.
The type of algorithm to be used in the calculation of the trip (fastest, least walking, etc.).
Whether the trip calculation should take elevation data into account (bike, foot). Default is FALSE.
There might exist lines that have special restrictions and are not generally available to the public. E.g. school buses, company shuttles. dragLifts need to have an ACCESS MODE ski. Lines with ACCESS MODE bicycle will be included as well. If this flag is set, then existing restricted lines are considered by the router, irrespective of the selected passenger categories or the MotorisedMainTravelMode. The results are marked as restricted in the ServiceGroup. The usage could also be detailed with Attribute elements. Restricted trumps PassengerCategory, for example. If Restricted is set to true, all services are displayed.
Sequence of all passenger categories, for which this search shall be conducted. In rare cases additional offerings may be available (e.g., demand responsive service with certain areas being reserved for seniors). If multiple PassengerCategories are provided, then Services are shown when they are available for at least one PassengerCategory.
Base mobility options to be applied for both public and individual transport.
The user is not able to pass over (or wants to avoid) single steps. Stairs and non-level entrances are not excluded.
The user is not able to walk up/downstairs.
The user is not able to use an escalator.
The user is not able to use an elevator.
The user is not able to use a ramp.
The user is not able to see.
The user is not able to use a travelator.
The user needs vehicles with level entrance between platform and vehicle.
The user needs vehicles with level entrance between platform and vehicle, an appropriate ramp, or assistance for boarding or alighting (for assisted and unassisted wheelchairs, or similar constraints).
Parameters to control the level of detail of both public and individual transport journey results.
Whether the result should include TrackSection elements to describe the geographic route of each journey leg.
Whether the result should include the geographic projection (coordinates) of each journey leg.
Whether the result should include turn-by-turn instructions for each journey leg.
Whether the result should include the access features (stairs, elevator, etc.) on each path link.
Whether the result should include real time status of access features to indicate broken equipment.
Which accessibility features and other accessibility-related information to retrieve (e.g., guidance text for the visually impaired).
Whether the place context is needed. If a requestor has that information already, the response can be made slimmer, when set to false. Default is true.
Whether the situation context is needed. If a requestor has that information by other means or can't process it, the response can be made slimmer, when set to false. Default is true.
Allowed values for AccessibilityDetails.
========================================== Leg Attributes ==========================================
Attributes that are not valid on the whole service, but only on section of a TRIP made on a single MODE without interchange between boarding and alighting (facilities available on a specified (part of a) Leg of a VEHICLE JOURNEY)
The attribute is valid from the stop point with this sequence number within the leg. If missing it is valid from the beginning of the leg.
The attribute is valid to the stop point (inclusively) with this sequence number within the leg. If missing it is valid to the end of the leg.
========================================== Leg Projection ==========================================
The LINK PROJECTION of a Leg onto the topography of the route being followed.
A geographical view of a Transmodel LEG TRACK together with duration and length that can be used for representing the leg on a map. The points may be STOP PLACE, SCHEDULED STOP POINT, coordinates, or ADDRESSes. Specialisation of SECTION.
SECTION of a LEG TRACK on the infrastructure network of the LEG together with time information.
Start place of this track section (Start of a SECTION of a LEG.TRACK).
End place of this track section (End of a SECTION of a LEG.TRACK).
An oriented correspondence from one LINK of a source layer, onto an entity in a target layer: e.g., LINK SEQUENCE.
Name of the road this track section is attached to (LEG TRACK.SECTION NAME, may also be something like "bicycle line along Tellstrasse").
Duration the passenger needs to travel through this track section.
Length of this track section.
© 2015 - 2025 Weber Informatics LLC | Privacy Policy