Forum: railML.infrastructure » NetRelation inconsistency for specific topology

Home » railML newsgroups » railML.infrastructure » NetRelation inconsistency for specific topology (NetRelations and NetElements problem)

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: NetRelation inconsistency for specific topology [message #2225 is a reply to message #2222]

Fri, 19 July 2019 07:47

Jörg von Lingen
Messages: 91
Registered: March 2016

Member

Dear Fabiana,

I would suggest to collect netRelations always seen from connecting point clockwise. In your case you would get

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

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

Regards,
Jörg von Lingen - Interlocking Coordinator
Fabiana Diotallevi wrote on 12.07.2019 18:24:
> <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>

Report message to a moderator

[Message index]

		NetRelation inconsistency for specific topology By: Fabiana Diotallevi on Fri, 12 July 2019 18:24
		Re: NetRelation inconsistency for specific topology By: Jörg von Lingen on Fri, 19 July 2019 07:47
		Re: NetRelation inconsistency for specific topology By: christian.rahmig on Mon, 26 August 2019 13:06
		Re: NetRelation inconsistency for specific topology By: Fabiana Diotallevi on Tue, 17 September 2019 10:31

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

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Nov 03 20:39:29 CET 2024