Home » railML newsgroups » railML.infrastructure » [railML 3.2] How to handle different granularity in node-edge-models at the level="micro"? (Managing data exchange in case of node-edge-models with different granularity)
[railML 3.2] How to handle different granularity in node-edge-models at the level="micro"? [message #2859] Wed, 08 December 2021 16:50 Go to previous message
Karl-Friedemann Jerosch is currently offline  Karl-Friedemann Jerosch
Messages: 11
Registered: May 2020
Junior Member
Dear railML users,

as a node-edge-model can be described in railML by using the topology elements "netElements", "netRelations" and "networks",
it is possible on the one hand (option 1) to define in railML a topology whereas the nodes are only switches, buffer stops and other kind of project topology borders.
On the other hand (option 2) it is also possible to define in railML a topology whereas axle counters are considered as nodes additionally to switches, buffer stops and other kind of project topology borders.


How should data exchange between two (or more) tools be managed, if one (or more) is working with option 1 and the other one(s) is running with option 2?

[Updated on: Wed, 08 December 2021 16:51]

Report message to a moderator

[Message index]
 
Read Message
Read Message
Previous Topic: serviceSections extension
Next Topic: [railML3] Designator for NetElements
Goto Forum:
  

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

Current Time: Sun May 05 22:18:04 CEST 2024