Generic:freightFacilities/3.2

From railML 3 Wiki
Revision as of 15:55, 8 February 2024 by RailML Bot XSD2MediaWiki (talk | contribs) (Created page Generic:freightFacilities/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 freightFacilities

Autoexport from the XML-Schema for element generic:freightFacilities of railML® version 3.2
Documentation Container for facilities available for freight transport.
Subschema generic
Parents* commercialTrainSection,

formationInformation, vehiclePart

Children designator (0..*)
Attributes:
  • count: The number of the available facilities of this type used for freight. (optional; xs:positiveInteger),

  • freightType: This attribute is not documented in the schema! (optional; xs:string; patterns: other:\w{2,})
Possible values:
  • bulkGoods
  • cars
  • container20
  • container40
  • flatPlatform
  • gas
  • liquidGas
  • liquids
  • liveStock
  • pallets
  • partLoadGoods
  • powder
  • trailers
  • trucks,

  • hasWeatherProtection: This attribute is not documented in the schema! (optional; xs:boolean),

  • load: generic type for weight/load values measured in tonnes (optional; xs:decimal),

  • loadAccess: The way of access to the vehicle for loading and unloading the freight for this facility. (optional; xs:string; patterns: other:\w{2,})
Possible values:
  • sideDoors
  • slidingRoof
  • slidingWalls,

  • loadArea: generic type for area values measured in square metres (optional; xs:decimal),

  • loadVolume: This attribute is not documented in the schema! (optional; xs:decimal),

  • selfDischarge: The specification for discharging (unloading) the freight of this facility. (optional; xs:string; patterns: other:\w{2,})
Possible values:
  • controlled
  • sideTipping
  • uncontrolled
*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.