Home » railML newsgroups » railML.infrastructure » [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation (Ensuring that each netElement and netRelation belongs to exactly one RTM:level)
Re: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation [message #3590 is a reply to message #3578] Wed, 23 April 2025 22:25 Go to previous messageGo to previous message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 145
Registered: February 2025
Location: Brussels
Senior Member
Quote:
"Can a netElement or netRelation be linked with more than one level of aggregation?"
Yes, this is the case for the topology management system at Infrabel. NetElements can be shared between the micro and 'a' meso level. The meso level aggregates some more complex railway installations to make a more easy to read map. The associated positioning systems of the netelements are also more schematic for the meso level. But the NetElements are the same.

Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML 3.4 bèta 3] BaliseGroup attribute validityDirection
Next Topic: [railML3] @lateralSide and @verticalSide and distances
Goto Forum:
  

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

Current Time: Sun Aug 16 06:10:09 CEST 2026