Modelling of time aspects
Description
Time is so far a missing dimension in the railML data model. This gap shall be closed latest with the new major version railML v3. This ticket is meant to collect different requirements on time dimension from the community.
Background
In the forum, Tobias Bregulla described an application for video based recording of infrastructure data. He mentioned the following requirements on time:
- recording of time with millisecond accuracy
- absolute time stamps following UTC time
- relative time in form of seconds since start of recording
Tobias Bregulla provided the following example:
<signal id="si01">
<times>
<time id="si01_t01" date="2017-05-24" utcTime="09:30:10.320Z" relTime="32.812" type="survey" gpsinfradat:SurveyRefID=”c134f4a0-6085-48f4-a3e4-79daa2305e78”>
</times>
</signal>
Links
- Forum discussion
- Tobias Bregulla, June 2017: [http://www.railml.org/forum/index.php?t=msg&th=525&start=0&]
- Trac ticket system
- Topology reference dates (de: Topologie Stichtage): [http://trac.railml.org/ticket/306]
Proposed solution for railML 3.1
tbd