Home » railML newsgroups » railML.infrastructure » [railML3]: operationalPoint of operationalType="block" (How to link them to a netElement)
Re: [railML3]: operationalPoint of operationalType="block" [message #2692 is a reply to message #2689] Fri, 09 April 2021 13:54 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear Dominik,

in general, your approach of locating the <operationalPoint> on a microscopic <netElement> is fine.
However, I don't understand why you want to locate an operational point with a length of zero meters using an <areaLocation>? I think, a <spotLocation> would suit better.

By the way: locating <operationalPoint> elements on microscopic topology is quite common. In particular, it is best practice to model the operational point center point (in railML2 language also known as "cross section") using a <spotLocation> on a microscopic <netElement>.

Are there any other best practice ideas from the community?

Best regards
Christian

Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Distance from track center to switch lock cabinet
Next Topic: [railMl2] Proposal for new attribute @switchable in <baliseGroup> and wiki refinement
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun May 05 09:45:18 CEST 2024