Home » railML newsgroups » railML.infrastructure » suggestion for switchIS@type="crossingPart" (new enumerations value in railML3.4)
Re: suggestion for switchIS@type="crossingPart" [message #3846 is a reply to message #3840] Tue, 16 December 2025 15:12 Go to previous messageGo to previous message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 167
Registered: February 2025
Location: Brussels
Senior Member
Hello Christian, yes I know that there is no switching possibility on crossing parts, the example was to show how it could work with the proposal of Torben in the topic start:

Quote:
Thus, I suggest introducing the new enumerations value in railML3.4: switchIS@type="crossingPart"
with definition:
crossingPart: a crossing part of a singleSwitchCrossing or crossing segments part of a simple crossing
just as you requested:
Quote:
A code example may give us an impression of how such a simple switch crossing can look like.
The problem that this forum topic tries to discuss is that a schematic track layout tool is not capable of knowing what to draw left and what to draw right, based on a <crossing> or <switchIS type="singleSwitchCrossing">, because it is missing left/right information that is supplied as <switchIS type="switchCrossingPart"> for <switchIS type="doubleSwitchCrossing">


Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
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: [railML3] Restricting aggregation of RailTopoModel
Next Topic: [railML3] Order of geometricCoordinate attributes
Goto Forum:
  


Current Time: Sun Sep 13 10:39:40 CEST 2026