| User Information |
| Login: christian.rahmig |
Registered on Fri, 15 January 2016 |
Message Count 546 |
| Subject |
Forum: |
Date Posted |
| Re: [railML3] Stopping places with several lengths |
railML.infrastructure |
Mon, 04 May 2026 21:11 |
| Re: Turntable and Transfer table |
railML.infrastructure |
Fri, 01 May 2026 07:50 |
| Re: Turntable and Transfer table |
railML.infrastructure |
Fri, 01 May 2026 07:40 |
| Re: Need for crossing angles for under|overCrossings? |
railML.infrastructure |
Fri, 01 May 2026 07:32 |
| Re: Position of spotLocation and definition of length@value |
railML.infrastructure |
Fri, 17 April 2026 11:14 |
| Re: Excellent implementation |
railML.infrastructure |
Thu, 16 April 2026 19:34 |
| Re: Turntable and Transfer table |
railML.infrastructure |
Thu, 16 April 2026 19:16 |
| Re: suggestion for switchIS@type="crossingPart" |
railML.infrastructure |
Fri, 27 March 2026 12:51 |
| Re: suggestion for switchIS@type="crossingPart" |
railML.infrastructure |
Fri, 20 March 2026 12:33 |
| Re: [railML3] Modelling expansion joints |
railML.infrastructure |
Fri, 20 March 2026 12:07 |
| Re: St. Andrews cross on road side signals |
railML.infrastructure |
Mon, 09 March 2026 08:50 |
| Re: [railML3] Texts on boards |
railML.infrastructure |
Sun, 08 March 2026 22:58 |
| Re: [railML3] Additional Switch attributes |
railML.infrastructure |
Sun, 08 March 2026 21:56 |
| Re: suggestion for switchIS@type="crossingPart" |
railML.infrastructure |
Sun, 08 March 2026 08:14 |
| Re: Turntable and Transfer table |
railML.infrastructure |
Fri, 06 March 2026 12:05 |
| Re: [railML3] Extensions to the Modelling of Signals |
railML.infrastructure |
Fri, 06 March 2026 09:51 |
| Re: [railml3.1] speed profiles and @etcsTrainCategoryNumber |
railML.infrastructure |
Fri, 06 February 2026 10:39 |
| Re: [railML3] Transporting dangerous goods |
railML.infrastructure |
Mon, 05 January 2026 15:04 |
| Re: [railML3] electrification is IS, RS and CO |
railML.infrastructure |
Mon, 05 January 2026 14:48 |
| Re: Ways to model temporal aspects |
railML.infrastructure |
Mon, 05 January 2026 12:14 |
| Re: Geometry |
railML.infrastructure |
Mon, 05 January 2026 11:58 |
| Re: [railML3] Tunnel infrastructure |
railML.infrastructure |
Mon, 05 January 2026 09:37 |
| Re: suggestion for switchIS@type="crossingPart" |
railML.infrastructure |
Mon, 15 December 2025 13:56 |
| Re: [railML3] Additional Switch attributes |
railML.infrastructure |
Fri, 12 December 2025 11:47 |
| Re: St. Andrews cross on road side signals |
railML.infrastructure |
Mon, 08 December 2025 07:49 |
| Re: suggestion for switchIS@type="crossingPart" |
railML.infrastructure |
Mon, 08 December 2025 07:44 |
| Re: Turntable and Transfer table |
railML.infrastructure |
Mon, 08 December 2025 07:18 |
| Re: Level crossing with extended information |
railML.infrastructure |
Mon, 08 December 2025 06:02 |
| Re: [railML3] Extensions to the Modelling of Signals |
railML.infrastructure |
Mon, 08 December 2025 05:50 |
| Re: Designator for geometry elements |
railML.infrastructure |
Mon, 01 December 2025 11:49 |
| Re: [railML3] @lateralSide and @verticalSide and distances |
railML.infrastructure |
Mon, 17 November 2025 13:33 |
| Re: [railML3.3] xs:choice between linearCoordinate and geometricCoordinate |
railML.infrastructure |
Fri, 22 August 2025 14:41 |
| Re: [railML3] Proposal of a semantic constraint for <baliseGroup> |
railML.infrastructure |
Fri, 15 August 2025 09:43 |
| Re: [railML3 wiki] opEquipment |
railML.infrastructure |
Mon, 11 August 2025 13:26 |
| Re: Turntable and Transfer table |
railML.infrastructure |
Mon, 11 August 2025 12:20 |
| Re: Orientation of baliseGroup and validity direction of balise telegrams |
railML.infrastructure |
Mon, 11 August 2025 11:36 |
| Re: Correspondence IL:trackIL und IS:track |
railml.interlocking |
Mon, 23 June 2025 14:31 |
| Re: associated netElements coordinates for LPS and measure precision issues |
railML.infrastructure |
Fri, 20 June 2025 11:39 |
| Re: Modellig lineside telephones v3.2 RailML |
railML.infrastructure |
Fri, 13 June 2025 09:20 |
| Re: UC NEST Positioning approach for lineSegment with 2 or more tracks |
railML.infrastructure |
Wed, 11 June 2025 16:42 |