User Information |
Login: christian.rahmig |
Registered on Fri, 15 January 2016 |
Message Count 474 |
Subject |
Forum: |
Date Posted |
Re: [railML3] InfrastructureVisualization |
railML.infrastructure |
Mon, 07 October 2019 21:45 |
Re: [railML3] Mandatory <length> element for <track>s |
railML.infrastructure |
Mon, 07 October 2019 21:33 |
Re: Definition of track/stoppingPlace/platform infrastructure vs. timetable |
railML.infrastructure |
Mon, 07 October 2019 20:28 |
Re: [railML3] References across several XML files |
railml.common |
Mon, 02 September 2019 12:39 |
Re: [railML3] Mandatory <length> element for <track>s |
railML.infrastructure |
Mon, 02 September 2019 12:05 |
Re: [railML2] modeling of a car ramp |
railML.infrastructure |
Mon, 26 August 2019 16:58 |
Re: Proposed Semantic Constraint for <speedChange> in railML 2.x |
railML.infrastructure |
Mon, 26 August 2019 15:24 |
Re: [railML3] Extension of OPEquipment |
railML.infrastructure |
Mon, 26 August 2019 14:30 |
Re: How to represent Line Continuation on railML |
railML.infrastructure |
Mon, 26 August 2019 14:24 |
Re: NetRelation inconsistency for specific topology |
railML.infrastructure |
Mon, 26 August 2019 13:06 |
Re: [railML3] Mandatory <length> element for <track>s |
railML.infrastructure |
Mon, 26 August 2019 12:49 |
Re: [railML3] Extension of OPEquipment |
railML.infrastructure |
Fri, 05 July 2019 14:02 |
Re: How to model 3 topology levels in rail.ML |
railML.infrastructure |
Fri, 05 July 2019 12:08 |
Re: Differences between <screenCoordinates> and <Infrastructure visualization> tags |
railML.infrastructure |
Fri, 05 July 2019 11:23 |
Re: [railML3] Mapping of tvdSection in infrastructure? |
railML.infrastructure |
Tue, 04 June 2019 18:56 |
[railML2] @dir |
railML.infrastructure |
Mon, 27 May 2019 11:57 |
Re: Adding of trainProtectionSystems for IS:trainProtectionChange and IS:trainProtection |
railML.infrastructure |
Fri, 03 May 2019 13:29 |
Re: How to model 3 topology levels in rail.ML |
railML.infrastructure |
Fri, 03 May 2019 12:00 |
Re: [railML3] References across several XML files |
railml.common |
Tue, 16 April 2019 20:52 |
Re: extension of <levelCrossing> in railML2.4nor |
railML.infrastructure |
Tue, 16 April 2019 20:25 |
Re: [railML2] trackRef@sequence |
railML.infrastructure |
Tue, 09 April 2019 22:09 |
Re: ]railMLv3]: switch referece point |
railML.infrastructure |
Mon, 08 April 2019 20:16 |
Re: Platform @belongsToParent and <ownsPlatformEdge> |
railML.infrastructure |
Mon, 08 April 2019 19:56 |
Re: [railML3] Infra Geometry Terminology |
railML.infrastructure |
Mon, 08 April 2019 16:52 |
Re: [railML2] trackRef@sequence |
railML.infrastructure |
Wed, 27 March 2019 07:55 |
Re: [railML3] Infra Geometry Terminology |
railML.infrastructure |
Wed, 27 March 2019 07:19 |
Re: Platform @belongsToParent and <ownsPlatformEdge> |
railML.infrastructure |
Mon, 18 February 2019 16:12 |
Re: [railml3] Signal types and functions |
railML.infrastructure |
Mon, 18 February 2019 14:55 |
Re: [railml3] Signal types and functions |
railML.infrastructure |
Mon, 18 February 2019 14:36 |
How to name a "non-fixed" balise? |
railml.interlocking |
Mon, 11 February 2019 16:05 |
Re: Embedded methods in objects |
railML.infrastructure |
Mon, 11 February 2019 15:58 |
Re: [railml3] Signal types and functions |
railML.infrastructure |
Mon, 11 February 2019 15:51 |
Re: Platform @belongsToParent and <ownsPlatformEdge> |
railML.infrastructure |
Mon, 11 February 2019 15:29 |
Re: [railml3.1] Make @applicationDirection optional |
railML.infrastructure |
Tue, 29 January 2019 16:03 |
Re: Double switch crossing: 'crossingRef' attribute for the fictive switches |
railML.infrastructure |
Mon, 28 January 2019 13:56 |
Re: swicthType "interlacedSwitch" in IL |
railML.infrastructure |
Mon, 28 January 2019 11:10 |
Re: swicthType "interlacedSwitch" in IL |
railml.interlocking |
Mon, 28 January 2019 11:10 |
Re: Include track length information in topology |
railML.infrastructure |
Mon, 21 January 2019 15:49 |
Re: meaning of 'up' and 'down' in mileageChange.dir and track.mainDir |
railML.infrastructure |
Mon, 21 January 2019 13:15 |
Re: Infrastructure registers |
railML.infrastructure |
Fri, 18 January 2019 16:33 |