IS:opOperation/3.2

From railML 3 Wiki
Revision as of 13:49, 25 November 2024 by RailML Bot XSD2MediaWiki (talk | contribs) (Updated page IS:opOperation/3.2 using XSD2MediaWiki Converter 1.1.1)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Automatic Schemaexport for Element opOperation



Autoexport from the XML-Schema for element IS:opOperation of railML® version 3.2
    
Documentation railway operation
Subschema infrastructure
Parents*

opOperations

Children

None

Attributes:
  • operationalType: operational characterization of the operational point (optional; xs:string; patterns: other:\w{2,}; consider Dev:UsingAny too.)
Possible values:
  • depot: an operational point where railway vehicles can start and end
  • block: on operational point where the spacing of trains is monitored; can be a block signal (mainly unstaffed and automated) or a block post (mainly staffed)
  • siding: an operational point to collect and deliver of cargo wagons to build trains, but not for train operation
  • borderPoint: operational point is a border point (e.g. at national border)
  • crossover: a connection between two tracks of a double-track line
  • junction: joining/splitting of two lines
  • station: a usual station for beginning, ending, overtaking of trains with passing tracks, etc.
  • stoppingPoint: an operational point without signals, switches, additional tracks where trains start, stop or end e. g. for passenger exchange,

  • trafficType: definition of traffic type that is operating in this operational point (optional; xs:string; patterns: other:\w{2,}; consider Dev:UsingAny too.)
Possible values:
  • freight: the prevailing traffic occurring at this ocp is freight traffic
  • operational: no passengers, no goods, just staff
  • passenger: the prevailing traffic occuring at this ocp is passenger traffic
  • shunting: the prevailing traffic occuring at this ocp is shunting traffic, e. g. in a depot or a workshop
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this Wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.