Home » railML newsgroups » railML.infrastructure » Infrastructure registers
Re: Infrastructure registers [message #1682 is a reply to message #1667] Fri, 15 December 2017 13:24 Go to previous messageGo to previous message
Philip Wobst is currently offline  Philip Wobst
Messages: 47
Registered: November 2013
Location: Hanover, Germany
Member
Am 20.11.2017 um 16:19 schrieb Christian Rahmig:
> Dear all,
>
> the described problem may be solved with version 2.4. The related Trac
> ticket #310 is available in [1].
>
> I would like to have your feedback on answering the main question: Do
> you prefer having one codelist including all the different existing
> registers for providing codes and designators to railway infrastructure
> elements, or would you like to have separated codelists?

Dear all,

the current proposal is to have one register only for all known
registers and without a distinction by type. Please provide feedback for
this as soon as possible.

Best regards,

Philip Wobst
 
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: Use the concept of layer for splitting the data
Next Topic: meaning of 'up' and 'down' in mileageChange.dir and track.mainDir
Goto Forum:
  


Current Time: Thu May 02 09:17:46 CEST 2024