Home » railML newsgroups » railML.infrastructure » NetRelation inconsistency for specific topology (NetRelations and NetElements problem)
NetRelation inconsistency for specific topology [message #2222] Fri, 12 July 2019 18:24 Go to previous message
Fabiana Diotallevi is currently offline  Fabiana Diotallevi
Messages: 21
Registered: October 2018
Junior Member
Dear all,

the topology shown in the image attached (but it is not the only case!), seems to bring to an inconsistency in the netRelation definition.

/forum/index.php?t=getfile&id=50&private=0
In particular, if we consider the netRelation joining netElements ne_02 and ne_03 (upper and lower central tracks), both of the following relations could be exported:

<netRelation id="nr_0203" positionOnA="0" positionOnB="0" navigability="None">
<elementA ref="ne_02"/>
<elementB ref="ne_03"/>
</netRelation>

<netRelation id="nr_0203" positionOnA="1" positionOnB="1" navigability="None">
<elementA ref="ne_02"/>
<elementB ref="ne_03"/>
</netRelation>

There is no way to decide which one is the preferred one, and I can't export both of them because they have the same id and railML does not allow for a duplicate.

Is there a way to solve this problem?

Thanks,

f.

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Proposed Semantic Constraint for <speedChange> in railML 2.x
Next Topic: [railML 3.2] extending the <speedProfile> element
Goto Forum:
  

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

Current Time: Sat Apr 20 04:29:14 CEST 2024