| [railML 3.1] Simplification of area engineering over more than one netElement element [message #1753] |
Mon, 09 April 2018 12:17  |
Heidrun Jost
Messages: 25
Registered: September 2006
|
Junior Member |
|
|
Hi,
I’m Heidrun Jost from Thales and intend to use the new railML3.1.
From my point of view the usage of areas (like speeds, gradient curves,
restriction areas) is more complicated as in railML2.3.
For better understanding the following example.
I have a long track consisting of 7 “netElements”. For the definition of
speed along the track we need for each “netElement” an own
“associatedElement” container.
Now, in railML 3.1 the following definition applies:
<speeds>
<speedSection id="sps01" vMax="240" isTemporary="false">
<linearLocation id="sps01_lloc01" applicationDirection="normal">
<associatedElement netElementRef="TS1" keepsOrientation="true">
<linearCoordinateBegin positioningSystemRef="lps01"
measure="0.00"/>
<linearCoordinateEnd positioningSystemRef="lps01"
measure="100.000"/>
</associatedElement>
<associatedElement netElementRef="TS2" keepsOrientation="true">
<linearCoordinateBegin positioningSystemRef="lps01"
measure="100.00"/>
<linearCoordinateEnd positioningSystemRef="lps01"
measure="300.00"/>
</associatedElement>
<associatedElement netElementRef="TS3" keepsOrientation="true">
<linearCoordinateBegin positioningSystemRef="lps01"
measure="300.00"/>
<linearCoordinateEnd positioningSystemRef="lps01"
measure="400.00"/>
</associatedElement>
<associatedElement netElementRef="TS4" keepsOrientation="true">
<linearCoordinateBegin positioningSystemRef="lps01"
measure="400.00"/>
<linearCoordinateEnd positioningSystemRef="lps01"
measure="700.00"/>
</associatedElement>
<associatedElement netElementRef="TS5" keepsOrientation="true">
<linearCoordinateBegin positioningSystemRef="lps01"
measure="700.00"/>
<linearCoordinateEnd positioningSystemRef="lps01"
measure="800.00"/>
</associatedElement>
<associatedElement netElementRef="TS6" keepsOrientation="true">
<linearCoordinateBegin positioningSystemRef="lps01"
measure="800.00"/>
<linearCoordinateEnd positioningSystemRef="lps01"
measure="900.00"/>
</associatedElement>
<associatedElement netElementRef="TS7" keepsOrientation="true">
<linearCoordinateBegin positioningSystemRef="lps01"
measure="900.00"/>
<linearCoordinateEnd positioningSystemRef="lps01"
measure="1000.00"/>
</associatedElement>
</linearLocation>
</speedSection>
</speeds>
I propose the following syntax to shorten the XML definition. I believe,
this is better readable:
If we allow a net Element list the definition would be shorter:
<speeds>
<speedSection id="sps01" vMax="240" isTemporary="false">
<linearLocation id="sps01_lloc01" applicationDirection="normal">
<associatedElement netElementRefList="TS1 TS2 TS3 TS4 TS5
TS6 TS7" keepsOrientation="true">
<linearCoordinateBegin positioningSystemRef="lps01"
measure="0.00"/>
<linearCoordinateEnd positioningSystemRef="lps01"
measure="1000.000"/>
</associatedElement>
</linearLocation>
</speedSection>
</speeds>
Best regards,
--
Heidrun Jost
Software Engineer
Transportation Systems
Thales Deutschland
Phone: +49 (0) 30 688306 423
Email: heidrunjost(at)thalesgroupcom
Thales Deutschland GmbH
Schützenstr. 25 – 10117 Berlin – Germany
|
|
|
|
| Re: [railML 3.1] Simplification of area engineering over more than one netElement element [message #1773 is a reply to message #1753] |
Mon, 23 April 2018 16:10  |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Heidrun,
I took your topic with me into the "2nd railML 3.1 Workshop" in Berlin
last week.
Concluding the discussion the proposal has been seen sceptical from most
of the workshop participants: Although some lines "can be saved" in the
export file, it was highlighted that new problems and inconsistencies
may arise from the shortened topology location. In particular, listing
references in the attribute @netElementRefList has been criticized, also
because of resulting validation problems.
However, what about the rest of the community? @all: Do you have any
opinion about the proposal from Heidrun? Any feedback is highly
appreciated...
Best regards
Christian
--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
Am 09.04.2018 um 12:17 schrieb Heidrun Jost:
> Hi,
>
> I’m Heidrun Jost from Thales and intend to use the new railML3.1.
>
> From my point of view the usage of areas (like speeds, gradient curves,
> restriction areas) is more complicated as in railML2.3.
>
> For better understanding the following example.
>
> I have a long track consisting of 7 “netElements”. For the definition of
> speed along the track we need for each “netElement” an own
> “associatedElement” container.
>
> Now, in railML 3.1 the following definition applies:
> <speeds>
> <speedSection id="sps01" vMax="240" isTemporary="false">
> <linearLocation id="sps01_lloc01" applicationDirection="normal">
> <associatedElement netElementRef="TS1" keepsOrientation="true">
> <linearCoordinateBegin positioningSystemRef="lps01"
> measure="0.00"/>
> <linearCoordinateEnd positioningSystemRef="lps01"
> measure="100.000"/>
> </associatedElement>
> <associatedElement netElementRef="TS2" keepsOrientation="true">
> <linearCoordinateBegin positioningSystemRef="lps01"
> measure="100.00"/>
> <linearCoordinateEnd positioningSystemRef="lps01"
> measure="300.00"/>
> </associatedElement>
> <associatedElement netElementRef="TS3" keepsOrientation="true">
> <linearCoordinateBegin positioningSystemRef="lps01"
> measure="300.00"/>
> <linearCoordinateEnd positioningSystemRef="lps01"
> measure="400.00"/>
> </associatedElement>
> <associatedElement netElementRef="TS4" keepsOrientation="true">
> <linearCoordinateBegin positioningSystemRef="lps01"
> measure="400.00"/>
> <linearCoordinateEnd positioningSystemRef="lps01"
> measure="700.00"/>
> </associatedElement>
> <associatedElement netElementRef="TS5" keepsOrientation="true">
> <linearCoordinateBegin positioningSystemRef="lps01"
> measure="700.00"/>
> <linearCoordinateEnd positioningSystemRef="lps01"
> measure="800.00"/>
> </associatedElement>
> <associatedElement netElementRef="TS6" keepsOrientation="true">
> <linearCoordinateBegin positioningSystemRef="lps01"
> measure="800.00"/>
> <linearCoordinateEnd positioningSystemRef="lps01"
> measure="900.00"/>
> </associatedElement>
> <associatedElement netElementRef="TS7" keepsOrientation="true">
> <linearCoordinateBegin positioningSystemRef="lps01"
> measure="900.00"/>
> <linearCoordinateEnd positioningSystemRef="lps01"
> measure="1000.00"/>
> </associatedElement>
> </linearLocation>
> </speedSection>
> </speeds>
>
> I propose the following syntax to shorten the XML definition. I believe,
> this is better readable:
>
> If we allow a net Element list the definition would be shorter:
> <speeds>
> <speedSection id="sps01" vMax="240" isTemporary="false">
> <linearLocation id="sps01_lloc01" applicationDirection="normal">
> <associatedElement netElementRefList="TS1 TS2 TS3 TS4 TS5
> TS6 TS7" keepsOrientation="true">
> <linearCoordinateBegin positioningSystemRef="lps01"
> measure="0.00"/>
> <linearCoordinateEnd positioningSystemRef="lps01"
> measure="1000.000"/>
> </associatedElement>
> </linearLocation>
> </speedSection>
> </speeds>
>
> Best regards,
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
