| Re: Platforms and ramps for railML 2.2 [message #358 is a reply to message #283] |
Sun, 16 September 2012 09:48   |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Dear railML users,
> 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>
including the comments from Dirk and the discussions with the other
schema coordinators, platforms and service sections will be implemented
in railML 2.2 as follows (c.f. [1]):
1. <trackElements> will be extended with two new elements:
<platformEdges> for modelling platforms
<serviceSections> for modelling ramps and related facilities like
maintenance and fueling areas.
2. A <platformEdge> contains the following attributes:
- position information: defines the starting position and direction
of the platform
- length: the length of the platform from an operational view
(usable length)
- height: the platform's height in mm above rails
- side: right, left (seen in positive direction of the track)
3. A <serviceSection> contains the following attributes:
- position information, length, height and side as described for
the platformEdge
- various boolean attributes for a functional classification of the
service section. A service section may fulfill multiple functions and
therefore multiple boolean attributes may be set true.
[1] https://trac.assembla.com/railML/ticket/122
Regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
