Forum: railML.infrastructure

Home » railML newsgroups » railML.infrastructure » [railML2] @dir

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

Re: [railML2] @dir [message #2259 is a reply to message #2256]

Wed, 16 October 2019 15:22

Janne Möller
Messages: 14
Registered: March 2019
Location: Oslo

Junior Member

Dear Christian

I would like to comment on your post by sharing the common practice on the three listed points in the Norwegian railway sector.

regarding 1)
Agreed. For elements that have an application direction the attribute @dir is used.

regarding 2)
This is handled a bit differently here. For elements that have a length, but their position is a concrete coordinate, we are using the beginning of the element, not the middle. Which of these approaches is easier and more universally applicable seems to be worth a discussion.
We deviate from the mentioned rule concerning the element levelCrossing.

regarding 3)
We think this point is definitely a possibilty on how to handle long linear elements. It could be useful when such an element has several entries or exits that lie on different tracks. Currently we handle this case by defining another element of the same type on the beginning of the diverging track.

Best regards,

Janne Möller
Kapasitetsrådgiver
Jernbanedirektoratet

Report message to a moderator

[Message index]

		[railML2] @dir By: christian.rahmig on Mon, 27 May 2019 11:57
		Re: [railML2] @dir By: christian.rahmig on Mon, 07 October 2019 21:51
		Re: [railML2] @dir By: Janne Möller on Wed, 16 October 2019 15:22
		Re: [railML2] @dir By: Morten Johansen on Wed, 11 December 2019 09:07
		Re: [railML2] @dir By: Thomas Nygreen on Tue, 17 December 2019 15:09

Previous Topic:	[railML 3.2] extending the <balise> element
Next Topic:	Stopping Place use cases

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Apr 26 01:20:25 CEST 2024