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 #3997 is a reply to message #3995] Thu, 07 May 2026 20:20 Go to previous messageGo to previous message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 143
Registered: February 2025
Location: Brussels
Senior Member
Hi Milan,

Quote:
If the netElement is shared between meso and micro, how can you aggregate?
When there's no need to aggregate between a micro and a meso level. :)

For example when a meso level is defined to only aggregate the tracks of an operational point of any type that is not a station (which is more or less the case for Infrabel). (I think I have seen a similar thing at SBB but I'm not 100% sure). So a meso level is aggregating the netelements of the yards, sidings, ... but does not make any changes to the station netelements or the open track netelements.

Then there's also the case of one network having multiple meso (or micro or macro) levels. In that case most netelements could be shared by multiple levels.

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 09 19:24:41 CEST 2026