Platforms and ramps for railML 2.2 [message #283] |
Thu, 22 March 2012 22:19 |
Christian Rahmig
Messages: 151 Registered: January 2011
|
Senior Member |
|
|
Hello everyone,
considering the Trac ticket #122 [1], we are thinking about the
introduction of a datatype for platforms and ramps with the next release
2.2. So, this is how it may look like:
1. <trackElements> will be extended with a new element named
<serviceSection> for modelling platforms, ramps and related facilities.
2. The new element <serviceSection> describes the part ("section") of a
track, which can be used for the exchange of passengers, goods or similar.
3. Attributes for this new element include:
- position information: defines the starting position and direction
of the serviceSection
- length: the section length which is defined as the actually usable
length (NOT the physically existing platform/ramp which can be longer)
- height: the objects's height in mm above rails (for feasible types
only)
- type: enumeration of
"platform" (passanger platform)
"ramp" (ramp for loading / unloading goods)
"maintenance" (maintenance facilities e. g. in a depot)
"loadingFacility" (Goods can be (un-)loaded from the wagon's
top / underfloor)
"cleaning" (washing facility for cars and engines)
"fueling" (facility for re-fuelling of engines)
"parking" (section for parking of rolling stock)
"preheating" (electricity or steam for pre-heating purposes)
"other"
- side: right, left (seen in positive mileage direction)
4. Each <serviceSection> can have multiple types. Tracks with platforms
on both sides need two <serviceSection> elements to force the definition
of different platform names.
5. Additional semantics:
- name: the name contains the platform number (e.g. "3")
- The associated OCP can be de-referenced from the OCP's <trackGroup>
It would be nice to hear your opinion about this model approach. Are
there any important parameters missing?
Best regards.
[1] https://trac.assembla.com/railML/ticket/122
---
Christian Rahmig
railML.infrastructure coordinator
|
|
|