Forum: railML.infrastructure » [railML3] Mandatory <Location> for <genericArea>?

Home » railML newsgroups » railML.infrastructure » [railML3] Mandatory <Location> for <genericArea>?

Tue, 10 October 2023 10:51

Torben Brand
Messages: 158
Registered: March 2016

Senior Member

Dear railML community,

Do I read this right that a <location> is mandatory for <genericArea>?
https://wiki3.railml.org/wiki/IS:genericArea

In the norwegian railway sector we need project areas. They work great in railML2.4nor explained in chapter 4.9 here:
https://www.jernbanedirektoratet.no/globalassets/documenter/ railml/20230330_railml2.4norisdocumentation_v1.6.pdf

We use bounding elements using <isLimitedBy> references pointing to functional infrastructure elements (<border>s).
The same mechanisms exist in railML3.2 and we would like to use them!
But we do not have any information on circles or polygones as is the required choice under <location>!
Also we have no requirementfor them!

Se example for a project area in Advanced Example in Railoscope here:
https://railoscope.com/tickets/Fyh1WAZliOQbgVmY?modelId=64d2 293fb1421a4b8096c580&selectId=163-22

		[railML3] Mandatory <Location> for <genericArea>? By: Torben Brand on Tue, 10 October 2023 10:51
		Re: [railML3] Mandatory <Location> for <genericArea>? By: christian.rahmig on Wed, 18 October 2023 14:41
		Re: [railML3] Mandatory <Location> for <genericArea>? By: Georg Boasson on Tue, 31 October 2023 14:38
		Re: [railML3] Mandatory <Location> for <genericArea>? By: christian.rahmig on Tue, 14 November 2023 08:06
		Re: [railML3] Mandatory <Location> for <genericArea>? By: christian.rahmig on Fri, 08 December 2023 10:56

Previous Topic:	[railML 2.5] Connections without track information
Next Topic:	Missing attributes and maybe elements in railML3.2 for RTCI-a

Goto Forum:

] [

]

Current Time: Sun May 12 02:35:00 CEST 2024