IS:bufferStop/3.2: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(Updated page IS:bufferStop/3.2 using XSD2MediaWiki Converter 1.1.1)
(Updated page IS:bufferStop/3.2 using XSD2MediaWiki Converter 1.1.1)
 
Line 8: Line 8:
|parent={{parent|subschema=IS|name=bufferStops}}
|parent={{parent|subschema=IS|name=bufferStops}}
|children={{child|subschema=RTM|name=areaLocation|multiplicity=0..*}}, {{child|subschema=Generic|name=designator|multiplicity=0..*}}, {{child|subschema=Generic|name=external|multiplicity=0..*}}, {{child|subschema=IS|name=gmlLocations|multiplicity=0..*}}, {{child|subschema=RTM|name=isValid|multiplicity=0..*}}, {{child|subschema=RTM|name=linearLocation|multiplicity=0..*}}, {{child|subschema=Generic|name=name|multiplicity=0..*}}, {{child|subschema=IS|name=networkLocation|multiplicity=0..*}}, {{child|subschema=RTM|name=spotLocation|multiplicity=0..*}}, {{child|subschema=IS|name=typeDesignator|multiplicity=0..*}}
|children={{child|subschema=RTM|name=areaLocation|multiplicity=0..*}}, {{child|subschema=Generic|name=designator|multiplicity=0..*}}, {{child|subschema=Generic|name=external|multiplicity=0..*}}, {{child|subschema=IS|name=gmlLocations|multiplicity=0..*}}, {{child|subschema=RTM|name=isValid|multiplicity=0..*}}, {{child|subschema=RTM|name=linearLocation|multiplicity=0..*}}, {{child|subschema=Generic|name=name|multiplicity=0..*}}, {{child|subschema=IS|name=networkLocation|multiplicity=0..*}}, {{child|subschema=RTM|name=spotLocation|multiplicity=0..*}}, {{child|subschema=IS|name=typeDesignator|multiplicity=0..*}}
|attributes={{attribut|name=type|pflicht=0|typ=xs:string|documentation=type of the buffer stop|werte={{wert|name=brakingBufferStop}}{{wert|name=fixedBufferStop}}{{wert|name=headRamp}}{{wert|name=sleeperCross}}}},
|attributes={{attribut|name=type|pflicht=0|typ=xs:string|documentation=type of the buffer stop|werte={{wert|name=brakingBufferStop|documentation=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].}}{{wert|name=fixedBufferStop|documentation=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].}}{{wert|name=headRamp|documentation=a combination of a buffer stop with loading ramp which serves two purposes}}{{wert|name=sleeperCross|documentation=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].}}}},
{{attribut|name=id|pflicht=1|typ=xs:string|documentation=the identifier of the object; this can be either of type xs:ID or UUID|patterns={{pattern|(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}\}}}}}
{{attribut|name=id|pflicht=1|typ=xs:string|documentation=the identifier of the object; this can be either of type xs:ID or UUID|patterns={{pattern|(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}\}}}}}
}}
}}

Latest revision as of 13:49, 25 November 2024

Automatic Schemaexport for Element bufferStop



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.