User Information |
Login: christian.rahmig |
Registered on Fri, 15 January 2016 |
Message Count 474 |
Subject |
Forum: |
Date Posted |
Re: Signal characteristics (de: Signaleigenschaften) |
railML.infrastructure |
Wed, 30 May 2018 15:42 |
Re: Mandatory stops e.g. before a level crossing |
railML.infrastructure |
Wed, 30 May 2018 14:04 |
Re: Include track length information in topology |
railML.infrastructure |
Wed, 30 May 2018 10:57 |
Proposal for incorporating length information in RTM NetElement |
RailTopoModel |
Wed, 30 May 2018 10:54 |
Modelling changes of mileage direction |
RailTopoModel |
Thu, 24 May 2018 19:19 |
[railML 3.1] border types |
railML.infrastructure |
Thu, 24 May 2018 18:52 |
Lateral location of elements |
RailTopoModel |
Fri, 18 May 2018 13:19 |
railML 3.x: Data Modelling Patterns |
railml.common |
Fri, 18 May 2018 09:01 |
Re: New extention element "nor:visualisationElement". |
railML.infrastructure |
Mon, 30 April 2018 17:06 |
Re: Extra attributes on signal in RailML2.3 norwegian extention |
railML.infrastructure |
Mon, 30 April 2018 16:38 |
Re: Visual positionning in step-by-step example |
railML.infrastructure |
Mon, 30 April 2018 16:21 |
Re: [railML 3.1] Simplification of area engineering over more than one netElement element |
railML.infrastructure |
Mon, 23 April 2018 16:10 |
Re: Mapping of availability periods of the infrastructure by TT:operatingPeriod |
railML.infrastructure |
Mon, 23 April 2018 14:51 |
Re: Mapping of availability periods of the infrastructure by TT:operatingPeriod |
railML.infrastructure |
Mon, 23 April 2018 14:23 |
Re: <track>@mainDir |
railML.infrastructure |
Mon, 16 April 2018 16:55 |
Re: <track>@mainDir |
railML.infrastructure |
Mon, 16 April 2018 16:51 |
Re: Infrastructure registers |
railML.infrastructure |
Tue, 03 April 2018 10:48 |
Re: Representation of operational stations |
railML.infrastructure |
Tue, 03 April 2018 10:48 |
Re: Representation of operational stations |
railML.infrastructure |
Tue, 27 March 2018 11:35 |
Re: railML 2.3 infrastructure extension proposal operational properties of an OCP |
railML.infrastructure |
Tue, 27 March 2018 11:14 |
Re: Representation of operational stations |
railML.infrastructure |
Tue, 27 March 2018 10:47 |
Re: Representation of operational stations |
railML.infrastructure |
Tue, 27 March 2018 10:42 |
Re: railML 2.3 infrastructure extension proposal operational properties of an OCP |
railML.infrastructure |
Tue, 27 March 2018 10:28 |
Re: New extention element "nor:visualisationElement". |
railML.infrastructure |
Wed, 21 March 2018 16:18 |
Re: New extention element "nor:visualisationElement". |
railML.infrastructure |
Wed, 21 March 2018 16:15 |
Re: New extention element "nor:visualisationElement". |
railML.infrastructure |
Wed, 21 March 2018 15:20 |
Validity times |
RailTopoModel |
Tue, 20 March 2018 15:49 |
Re: New extention element "nor:visualisationElement". |
railML.infrastructure |
Tue, 20 March 2018 15:35 |
Re: Ways to model temporal aspects |
railML.infrastructure |
Tue, 20 March 2018 14:37 |
Re: Infrastructure registers |
railML.infrastructure |
Mon, 19 March 2018 14:51 |
Re: <track>@mainDir |
railML.infrastructure |
Fri, 16 March 2018 08:50 |
Re: Level crossing default parameters / Standardwerte bei Bahnübergängen |
railML.infrastructure |
Fri, 16 March 2018 08:42 |
Reference to PositioningSystem |
RailTopoModel |
Mon, 12 March 2018 17:55 |
Re: <track>@mainDir |
railML.infrastructure |
Mon, 12 March 2018 17:19 |
Re: Level crossing default parameters / Standardwerte bei Bahnübergängen |
railML.infrastructure |
Mon, 12 March 2018 16:45 |
Re: Signal characteristics (de: Signaleigenschaften) |
railML.infrastructure |
Mon, 12 March 2018 15:23 |
[railML 3.1] level crossing parameters |
railML.infrastructure |
Thu, 08 March 2018 17:20 |
<track>@mainDir |
railML.infrastructure |
Thu, 22 February 2018 13:23 |
Re: Switch: usage of attribute @course |
railML.infrastructure |
Tue, 13 February 2018 11:46 |
Re: Track: description vs. trackDescr - also for <lineDescr> |
railML.infrastructure |
Tue, 13 February 2018 10:28 |