Introduction
| 🗒️
|
This article uses the unit label meter.
As the reference for this wiki is British English, the correct label is metre.
Wherever the label meter occurs, it is meant equivalently to metre.
|
|
|
Documentation
Syntax
Autoexport from the XML-Schema for element IS:bufferStop of railML ® version 3.3 |
| Documentation
|
represents a buffer stop as a node element. A buffer stop or bumper (US) is a device to prevent railway vehicles from going past the end of a physical section of track [wikipedia].
|
| Subschema
|
infrastructure
|
| Parents*
|
bufferStops
|
| Children
|
areaLocation (0..*), designator (0..*), elementState (0..*), gmlLocation (0..*), isValid (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), typeDesignator (0..*)
|
Attributes:
- type: type of the buffer stop (optional;
xs:string)
- Possible values:
- brakingBufferStop: Brake buffer stops can absorb significantly higher energies than all types of fixed buffer stops. They are usually attached to the running rails and, if necessary, additional rails with special clamps that are clamped together with screws. These clamps generate high friction and can, for example, brake a train with a mass of 850 tons from 15 km/h to a standstill in seven meters without damaging the vehicles. If higher masses or speeds are to be expected, a brake buffer stop is also equipped with drag sleepers [German Wikipedia].
- fixedBufferStop: A fixed buffer stop is firmly anchored in the ground or on the rails, in this case usually through rail holes. If starting speeds of more than 5 km/h are expected, damping systems, usually based on hydraulics, are installed to absorb the residual energy [German Wikipedia].
- headRamp: a combination of a buffer stop with loading ramp which serves two purposes
- sleeperCross: a device for temporarily blocking a track with a ballasted superstructure that is no longer accessible due to closure, construction work or similar [German Wikipedia].,
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:ID); compare: Dev:Identities
|
*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.
|
Autoexport from the XML-Schema for element IS:bufferStop of railML ® version 3.2 |
| Documentation
|
represents a buffer stop as a node element. A buffer stop or bumper (US) is a device to prevent railway vehicles from going past the end of a physical section of track [wikipedia].
|
| Subschema
|
infrastructure
|
| Parents*
|
bufferStops
|
| Children
|
areaLocation (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), typeDesignator (0..*)
|
Attributes:
- type: type of the buffer stop (optional;
xs:string)
- Possible values:
- brakingBufferStop: Brake buffer stops can absorb significantly higher energies than all types of fixed buffer stops. They are usually attached to the running rails and, if necessary, additional rails with special clamps that are clamped together with screws. These clamps generate high friction and can, for example, brake a train with a mass of 850 tons from 15 km/h to a standstill in seven meters without damaging the vehicles. If higher masses or speeds are to be expected, a brake buffer stop is also equipped with drag sleepers [German Wikipedia].
- fixedBufferStop: A fixed buffer stop is firmly anchored in the ground or on the rails, in this case usually through rail holes. If starting speeds of more than 5 km/h are expected, damping systems, usually based on hydraulics, are installed to absorb the residual energy [German Wikipedia].
- headRamp: a combination of a buffer stop with loading ramp which serves two purposes
- sleeperCross: a device for temporarily blocking a track with a ballasted superstructure that is no longer accessible due to closure, construction work or similar [German Wikipedia].,
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
|
*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.
|
Autoexport from the XML-Schema for element IS:bufferStop of railML ® version 3.1 |
| Documentation
|
This element is not documented in the schema!
|
| Subschema
|
infrastructure
|
| Parents*
|
bufferStops
|
| Children
|
any (0..*), areaLocation (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*)
|
Attributes:
- type: type of the buffer stop (optional;
xs:string)
- Possible values:
- sleeperCross
- headRamp
- fixedBufferStop
- brakingBufferStop,
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:ID; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
|
*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.
|
Changes 3.1→3.2
There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.
The element documentation has been changed.
The children have been changed.
The attributes have been changed.
Changes 3.2→3.3
There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.
The children have been changed.
The attributes have been changed.
Semantics
Best Practice / Examples
The Simple Example contains five buffer stops as part of the <functionalInfrastructure>. Four of them are located at the ends of the railway line "6869" in kilometre 0.000 and kilometre 5.000. They are of type fixedBufferStop. The fifth <bufferStop> is located on a siding track that is not part of the railway line "6869" and therefore does not have a railway line coordinate. The following code snippet summarizes the buffer stop model.
<functionalInfrastructure>
<bufferStops>
<bufferStop id="bus01" type="fixedBufferStop">
<spotLocation id="bus01_sloc01" netElementRef="ne_a01" applicationDirection="reverse" pos="0.0">
<linearCoordinate positioningSystemRef="lps01" measure="0.0"/>
</spotLocation>
</bufferStop>
<bufferStop id="bus02" type="fixedBufferStop">
<spotLocation id="bus02_sloc01" netElementRef="ne_a02" applicationDirection="reverse" pos="0.0">
<linearCoordinate positioningSystemRef="lps01" measure="0.0"/>
</spotLocation>
</bufferStop>
<bufferStop id="bus03" type="fixedBufferStop">
<spotLocation id="bus03_sloc01" netElementRef="ne_b01" applicationDirection="normal" pos="500.0">
<linearCoordinate positioningSystemRef="lps01" measure="5000.0"/>
</spotLocation>
</bufferStop>
<bufferStop id="bus04" type="fixedBufferStop">
<spotLocation id="bus04_sloc01" netElementRef="ne_b02" applicationDirection="normal" pos="450.0">
<linearCoordinate positioningSystemRef="lps01" measure="5000.0"/>
</spotLocation>
</bufferStop>
<bufferStop id="bus05" type="sleeperCross">
<spotLocation id="bus05_sloc01" netElementRef="ne_b05" applicationDirection="reverse" pos="0.0">
</spotLocation>
</bufferStop>
</bufferStops>
...
</functionalInfrastructure>
- Summary
- buffer stops are usually located on the microscopic topology level.
Additional Information
Notes
Open Issues
