[railML3] Time Dimension requirements from TT view [message #1462] |
Fri, 23 December 2016 14:37  |
christian.rahmig
Messages: 505 Registered: January 2016
|
Senior Member |
|
|
Dear railML TT community,
within the ongoing development process of the new railML v3 model and
schema, the topic "Time Dimension" is currently in the focus. The aim is
to provide a model of time aspects that fulfills all the requirements
from the different fields of application.
The timetable use cases already deal with with a lot and specific time
related information and railML.org would like to integrate this long
lasting knowledge into the railML3 development process, which is up to
now dominated by railway infrastructure managers and their view.
Therefore, I will be very happy if you provide answers and comments on
the following questions:
- What are the time scales that are used in railML TT use cases
(seconds, minutes, days, ...)?
- How are time aspects in railML TT applications usually structured?
Shall the bitmask structure be considered within the joint time
dimension model?
- Do you use patterns for repeating events?
- How do you deal with changes in infrastructure? Which changes of
infrastructure are relevant for TT? See also post from Mico Micic about
topology reference data [1].
- Which infrastructure changes are especially important for timetabling?
E.g. Removed switches, new switches, decommissioned tracks, relocated
signals etc.
- What requirements do you have for the precision of infrastructure
positioning?
- Besides timetable periods do you require additional timestructures
like project phases of construction work?
- What kind of metadata (descriptive data) about the actual
infrastructure data could be helpful for timetabling?
Any comments appreciated...
Thank you very much for your help and Merry Christmas everyone!
Christian
[1] http://www.railml.org/forum/index.php?t=msg&th=476&s tart=0&
--
Christian Rahmig
railML.infrastructure coordinator
[Updated on: Thu, 19 January 2017 14:51] by Moderator Report message to a moderator
|
|
|