User Information |
Login: christian.rahmig |
Registered on Fri, 15 January 2016 |
Message Count 486 |
Subject |
Forum: |
Date Posted |
Re: [railML 3.2] Modelling of Scheduling Rules |
railML.infrastructure |
Fri, 17 January 2025 10:44 |
Re: [railML 3.2] Modelling of Operational Rules |
railML.infrastructure |
Fri, 17 January 2025 09:56 |
Re: [railML 3.2] Modelling of Scheduling Rules |
railML.infrastructure |
Mon, 13 January 2025 14:21 |
Re: [railML 3.2] Modelling of Operational Rules |
railML.infrastructure |
Mon, 13 January 2025 13:48 |
Re: [railML 3.2] Modelling of (Station) Track Equipment |
railML.infrastructure |
Mon, 06 January 2025 15:04 |
Re: [railML 3.2] Modelling of Operational Rules |
railML.infrastructure |
Mon, 06 January 2025 14:54 |
Re: [railML 3.2] Modelling of Routing Rules |
railML.infrastructure |
Mon, 06 January 2025 14:48 |
Re: [railML3] Positioning approach |
railML.infrastructure |
Mon, 16 December 2024 14:54 |
Re: Balise group values for IS:functionalType |
railML.infrastructure |
Mon, 16 December 2024 14:38 |
Re: usage of @branchingSpeed and @joiningSpeed |
railML.infrastructure |
Mon, 16 December 2024 12:31 |
Re: [railML3] extended service section facilities |
railML.infrastructure |
Mon, 16 December 2024 11:06 |
Re: [railml3.1] speed profiles and @etcsTrainCategoryNumber |
railML.infrastructure |
Mon, 16 December 2024 10:48 |
Re: [railML3] Need for modelling Radio Infill Units |
railML.infrastructure |
Tue, 29 October 2024 15:02 |
Re: railML3 suggestion to add values for @detects in IS:detector |
railML.infrastructure |
Mon, 28 October 2024 15:14 |
Re: suggestion for new sub element <isLevelTransitionSignal> |
railML.infrastructure |
Mon, 14 October 2024 12:08 |
[railML3] speedSection maxSpeed values |
railML.infrastructure |
Mon, 14 October 2024 10:52 |
Re: [railML3] Limitation of <hasGaugeClearanceMarker> in <switchIL> |
railML.infrastructure |
Mon, 07 October 2024 11:32 |
[railML3] extended service section facilities |
railML.infrastructure |
Mon, 07 October 2024 10:41 |
[railML3] balise telegrams |
railML.infrastructure |
Mon, 07 October 2024 10:20 |
[railML3] balise location accuracy |
railML.infrastructure |
Mon, 07 October 2024 09:58 |
[railML3] Mandatory stop at level crossing |
railML.infrastructure |
Fri, 04 October 2024 17:09 |
Re: [railML3] Proposal of a semantic constraint for mileageChange |
railML.infrastructure |
Thu, 26 September 2024 10:38 |
[railML3] Transporting dangerous goods |
railML.infrastructure |
Mon, 23 September 2024 13:17 |
[railML3] Tunnel infrastructure |
railML.infrastructure |
Mon, 16 September 2024 13:31 |
Re: [railML3] tunnel resistance |
railML.infrastructure |
Mon, 16 September 2024 11:15 |
Re: Level crossing with extended information |
railML.infrastructure |
Mon, 16 September 2024 09:48 |
Re: [railML3] Need for modelling Lineside Electronic Unit |
railML.infrastructure |
Mon, 09 September 2024 11:32 |
Re: [railML3] Need for modelling Lineside Electronic Unit |
railML.infrastructure |
Mon, 09 September 2024 11:30 |
[railML3] measure and distance in linear positioning systems |
railML.infrastructure |
Fri, 30 August 2024 10:35 |
Re: [railML3] Positioning approach |
railML.infrastructure |
Mon, 26 August 2024 11:32 |
Re: [railML2] Single and double derailer |
railML.infrastructure |
Mon, 26 August 2024 09:19 |
Re: [railML3] Road traffic signals |
railML.infrastructure |
Mon, 19 August 2024 11:01 |
Re: [railML3] Grouping IS:trainProtectionElement-s |
railML.infrastructure |
Mon, 19 August 2024 10:42 |
Re: Missing attributes and maybe elements in railML3.2 for RTCI-a |
railML.infrastructure |
Mon, 12 August 2024 13:50 |
Re: [railML3] Improvement for railML element âetcsLevelTransition" |
railML.infrastructure |
Thu, 08 August 2024 14:17 |
Re: [railML3] Positioning approach |
railML.infrastructure |
Wed, 07 August 2024 16:22 |
Re: Infrastructure element datamodel quality and input-data source |
railML.infrastructure |
Fri, 02 August 2024 15:23 |
Re: railML3 suggestion to add values for @detects in IS:detector |
railML.infrastructure |
Fri, 02 August 2024 15:01 |
Re: [railML3] <border> representing open ends |
railML.infrastructure |
Fri, 02 August 2024 14:38 |
Re: [railML3] Type of a name of an operational point |
railML.infrastructure |
Fri, 21 June 2024 13:53 |