Forum: railML.infrastructure » [railML3] Positioning approach

Home » railML newsgroups » railML.infrastructure » [railML3] Positioning approach (How to define unambiguous positions with railML 3.x)

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: [railML3] Positioning approach [message #3185 is a reply to message #3160]

Wed, 17 January 2024 13:34

Dominik Looser
Messages: 18
Registered: March 2020

Junior Member

Dear all,

A feedback from our (trafIT solutions) side regarding mileage changes.
We agree with Siemens's feedback and would also prefer using <mileageChange> objects over <anchor>s as anchors cannot be assigned to a specific netElement. If a mileage change differs (even slightly) between two tracks of a double-track section, or especially in a curved station, only the <mileageChange>-element allows a precise modelling of the <mileageChange>-elements on each netElement.

Thank you and best regards,
Dominik Looser, trafIT solutions gmbh

Report message to a moderator

[Message index]

		[railML3] Positioning approach By: christian.rahmig on Mon, 04 September 2023 12:49
		Re: [railML3] Positioning approach By: Karl-Friedemann Jerosch on Thu, 02 November 2023 17:09
		Re: [railML3] Positioning approach By: Thomas Nygreen on Mon, 06 November 2023 19:31
		Re: [railML3] Positioning approach By: christian.rahmig on Wed, 08 November 2023 06:46
		Re: [railML3] Positioning approach By: Dominik Looser on Wed, 17 January 2024 13:34
		Re: [railML3] Positioning approach By: Larissa Zhuchyi on Fri, 22 March 2024 13:54
		Re: [railML3] Positioning approach By: christian.rahmig on Wed, 07 August 2024 16:22
		Re: [railML3] Positioning approach By: Ari Tilli on Mon, 26 August 2024 08:26
		Re: [railML3] Positioning approach By: christian.rahmig on Mon, 26 August 2024 11:32

Previous Topic:	[raillML3] Revision of rulebook
Next Topic:	[railML2] Single and double derailer

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 02 08:36:15 CEST 2024