User Information |
Login: Torben Brand |
Registered on Thu, 03 March 2016 |
Message Count 180 |
Subject |
Forum: |
Date Posted |
How to interpret application direction for derailers |
railML.infrastructure |
Mon, 07 April 2025 10:52 |
Interpreting "begin" and "end" in the sub elements <linearCoordinateBegin> and <linearCoordinateEnd> |
railML.infrastructure |
Mon, 07 April 2025 10:22 |
Re: Vote for revision of ISO RailDax |
railml.common |
Wed, 02 April 2025 20:07 |
Re: [railML3] New semantic constraint to ensure unambiguous infrastructure states |
railML.infrastructure |
Wed, 05 March 2025 21:37 |
Re: railML 2.3 infrastructure extension proposal operational properties of an OCP |
railML.infrastructure |
Wed, 05 March 2025 21:01 |
Re: [railML 3.2] Modelling of Routing Rules |
railML.infrastructure |
Thu, 23 January 2025 18:52 |
Re: New reflected thoughts towards railML 2.3 infrastructure extension proposal line sections |
railML.infrastructure |
Thu, 16 January 2025 18:11 |
Re: [railML3] Station borders |
railML.infrastructure |
Thu, 16 January 2025 17:42 |
Re: [railML3] Restricting IS:line and RTM:linearPositioningSystem |
railML.infrastructure |
Wed, 15 January 2025 14:19 |
Re: usage of @branchingSpeed and @joiningSpeed |
railML.infrastructure |
Wed, 15 January 2025 13:24 |
Re: [railml3.1] speed profiles and @etcsTrainCategoryNumber |
railML.infrastructure |
Fri, 06 December 2024 15:08 |
Re: [railML3] extended service section facilities |
railML.infrastructure |
Wed, 04 December 2024 11:44 |
Re: [railml3.1] speed profiles and @etcsTrainCategoryNumber |
railML.infrastructure |
Wed, 27 November 2024 09:19 |
usage of @branchingSpeed and @joiningSpeed |
railML.infrastructure |
Wed, 20 November 2024 14:52 |
Re: [railML3] Positioning approach |
railML.infrastructure |
Tue, 19 November 2024 15:10 |
Re: RE: [railML3] Refactoring of OrganizationalUnits |
railml.common |
Sun, 27 October 2024 15:32 |
Re: [railML3] Refactoring of states (e.g. infrastructure states) |
railml.common |
Fri, 25 October 2024 14:04 |
Re: [railML3] Infra Geometry Terminology |
railML.infrastructure |
Wed, 16 October 2024 17:16 |
Re: [railML2] Single and double derailer |
railML.infrastructure |
Tue, 27 August 2024 08:57 |
Re: [railML2] Single and double derailer |
railML.infrastructure |
Sat, 20 July 2024 08:40 |
Re: Infrastructure element datamodel quality and input-data source |
railML.infrastructure |
Fri, 05 July 2024 10:13 |
Re: [railML2] Single and double derailer |
railML.infrastructure |
Thu, 04 July 2024 13:10 |
Re: Infrastructure element datamodel quality and input-data source |
railML.infrastructure |
Sat, 27 April 2024 09:10 |
suggestion for new sub element <isLevelTransitionSignal> |
railML.infrastructure |
Fri, 19 April 2024 09:41 |
Re: Definition suggestion for isMovementSignal and its suggested attributes |
railML.infrastructure |
Fri, 22 March 2024 13:33 |
Re: Definition suggestion for isMovementSignal and its suggested attributes |
railML.infrastructure |
Fri, 22 March 2024 12:26 |
Re: Infrastructure element datamodel quality and input-data source |
railML.infrastructure |
Mon, 18 March 2024 14:34 |
Infrastructure element datamodel quality and input-data source |
railML.infrastructure |
Wed, 13 March 2024 11:44 |
Re: [railML3] Re: Signal combinations |
railML.infrastructure |
Fri, 08 March 2024 09:57 |
Definition suggestion for isTrainMovementSignal and its suggested attributes |
railML.infrastructure |
Wed, 06 March 2024 09:33 |
Re: [railml3] Signal types and functions |
railml.interlocking |
Wed, 28 February 2024 11:56 |
Re: [railml3] Signal types and functions |
railml.interlocking |
Fri, 23 February 2024 10:57 |
Re: [railML 3] railway signal modeling |
railML.infrastructure |
Fri, 23 February 2024 09:59 |
Re: Vote for revision of ISO RailDax |
railml.common |
Wed, 01 November 2023 08:27 |
Vote for revision of ISO RailDax |
railml.common |
Tue, 31 October 2023 15:54 |
[railML3] Mandatory <Location> for <genericArea>? |
railML.infrastructure |
Tue, 10 October 2023 10:51 |
Re: Fwd: Suggestion for a new use case: run time calculation |
railml.timetable |
Mon, 25 September 2023 08:35 |
Missing attributes and maybe elements in railML3.2 for RTCI-a |
railML.infrastructure |
Thu, 21 September 2023 21:27 |
Re: Fwd: Suggestion for a new use case: run time calculation |
railml.timetable |
Thu, 21 September 2023 17:00 |
Requirements for RTCI-a (Infrastructure) UC |
railML.infrastructure |
Thu, 21 September 2023 16:57 |