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 #3159 is a reply to message #3156]

Mon, 06 November 2023 19:31

Thomas Nygreen
Messages: 68
Registered: March 2008

Member

Dear Christian,

The linearCoordinate and geometricCoordinate children of linearLocation should be removed to stay consistent with the use that you are describing. And I would prefer either a clear documentation of when to use linearLocation versus areaLocation, or removing the latter. Should a level/over/underCrossing that crosses a multitrack line have one linearLocation for each track or an areaLocation for all tracks? Is a switch a linear or an area element?

Best regards,
Thomas

Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

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

Previous Topic:	Infrastructure element datamodel quality and input-data source
Next Topic:	[railML3] Improvement for railML element „etcsLevelTransition"

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Aug 24 22:41:41 CEST 2024