Home » railML newsgroups » railML.infrastructure » extension of <levelCrossing> in railML2.4nor
extension of <levelCrossing> in railML2.4nor [message #2170] Wed, 10 April 2019 11:23 Go to previous message
Janne Möller is currently offline  Janne Möller
Messages: 14
Registered: March 2019
Location: Oslo
Junior Member
Dear all,

the element <levelCrossing> has been extended for norwegian usage. In this forum post I would like to describe the changes that were made like announced in: [1]
The following adjustments have been made which are described underneath in further detail:

- extended definition of @pos and @absPos,
- definition of new attributes @nor:roadStartPos and @nor:roadEndPos and
- no use of the attributes @length and @dir.

The attributes @pos and @absPos for <levelCrossing> are defined in the following way:
@pos: This attribute is used to store the measured centre position of the level crossing along the track. This does not necessarily have to be the actual middle between the road borders.
@absPos: This attribute is used to store the original position of the level crossing that is provided in Banedata (database on norwegian railway network).

Furthermore we introduced to new attributes which define the start and end position of the level crossing precisely. With this information the length of the element can be calculated.
@nor:roadStartPos: This attribute is used to store the measured start position of the road the railway track is crossing. It is measured along the track from <trackBegin>, similar to the attribute @pos.
@nor:roadEndPos: see above, but end position

As stated above, the length of the level crossing can be calculated by using the newly defined attributes making it therefore unnecessary to use @length.

The attribute @dir is also not used for the element. Here I refer to this forum post: [2], in which it us suggested to deprecate @dir for <levelCrossing> among other elements.

Kind regards,
Janne Möller
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Stopping Place use cases
Next Topic: [railML2] Clearer modelling of the signal designation
Goto Forum:
  


Current Time: Sat Apr 20 01:24:33 CEST 2024