| Re: Extension of railML's Advanced Example [message #3118 is a reply to message #3116] |
Tue, 29 August 2023 14:18   |
Torben Brand
Messages: 158
Registered: March 2016
|
Senior Member |
|
|
Dear all,
I would like to make some suggestions for changes in the existing version 11. There seems to be missing an explicit mileageChange and some mileages seem to be a bit off in relation to where they are drawn in the schematics in the PDF. As Railoscope places the objects automatic according to position on the track this becomes clearly apparent. Please see list below for details. Also as table attached for better formating.
Also, I would like to add some elements to fulfil the UC runtime calculation input data for infrastructure ("RTCI-a" currently under development in the railML.org "SCTP" working group). To limit the number of objects we could restrict adding those objects to the line "8176" (from Arnau to Eimber"). But having them in the complete advanced example is also fine for me, as this is simple to do in a graphical editor like Railoscope. See table below for suggested additional objects. Use the link for "Proposals JDIR" given in the earlier post here to visualise the proposals in Railoscope.
OCP:
- Should we add geo coordinates? To remain fictitious, we could have geo coordinates somewhere remote without railway. Maybe Iceland? 😉
- Station codes (designator@entry) are given. I used "railML" as designator@register.
- Missing example for ocp@parentOCPref: Child OP Kudowa depot under Kudowa station with Km 52,15 and separate OP area as suggested in "proposal" branch in NorRailView
Reference point OP
Ok, but some positions should be adjusted/move crossSections for:
- Cranz from 4,800 to 4,500 (center platforms)
- Kudowa reference point is not at platform; suggest to move from Km 52,6 to 53,55
Stop marker
- Kudowa: stopPost not at platform or as shown in PDF. Assume typo. Suggest moving from Km 52,459 to Km 53,459. Suggest to add vaildForMovements@kind= "passengerTrains" and trainLength="200" m.
- Suggest to add also to Arnau, Cranz and Grestin as suggested in "proposal" branch in NorRailView
topology
- ok
Mileage change
- There is currently a "jump" between object at km 0,3 and next object at km 4,322 Suggest making explicit on entry Cranz between line 8176 and 8671 on Km 0,3|4,2 with mileage direction change. See suggested fixed in "proposal" branch in NorRailView
speed
Partially in example; See some additional suggested speeds in "proposal" branch in NorRailView
Deflecting speed
Partially in example; See som additional suggested values on remaining switches in "proposal" branch in NorRailView
Gradient
- missing; see suggested very simple gradient profile in "proposal" branch in NorRailView
Tunnel (resistance)
- Suggest to add a single track tunnel between Arnau and Cranz Km 3,067. Can then use original tunnel for double track tunnel case with portal. As suggested in "proposal" branch in NorRailView
(main)signal
Ok, but some questions:
- Should we have both signal type="combined" and combination of signals where main signal and distant signal are on the same post (same location/absPos)? I suggest to add both in the example as both are allowed in railML2
- Semaphore signals are not supported in NorRailView using regular signals without <sigSystem> or <ruleCode> and suggest to modify manually in XML
Route
missing; generic routes generated for tools that require routes for RTC Routes for line "8176" as suggested in "proposal" branch in NorRailView
TVD
Not required for RTCI, but TCB is not centred between switches as shown in PDF. Suggest to move from Km 52,338 to Km 53,388 (typo?)
Clearance (for placement of main signal if missing)
Missing, but have TVDs suggested clearance of "74" m examples for the two switches in Grestin station. See "proposal" branch in NorRailView.
Operational rules (limiting)
missing, ok for now?
electrificationChange
Ok, placed in trunk
trainProtectionSystemChange
Missing explicit. Added as suggested in "proposal" branch in NorRailView
Restriction sections/possesions
Missing/relevant for UC?
|
|
|
|
Members
Search
Help
Login
Home
