Home » railML newsgroups » railml.infrastructure » Additional attribute for crossing roads/rivers
Additional attribute for crossing roads/rivers [message #1258] Sat, 24 October 2015 19:44 Go to next message
Alexander Wolf is currently offline  Alexander Wolf
Messages: 5
Registered: October 2015
Junior Member
Hello railML community,

with our project GPSinfradat we record and visualise railway
infrastructure data. All measured data can be exported with railML for
utilisation in other railway applications and include information about
railway topology, track elements and operational elements. Within projects
concerning the planning of construction we are often asked to export the
name of the crossing road (level crossings) or the passed river/road
(bridges). Currently, this information can not be mapped in the railML
data model yet!

Therefore I suggest to extend the elements <bridge>, <levelCrossing> and
<tunnel> in railML v2.3 with an additional attribute for the
description/name of the crossing, e.g. "crossingElement".

Comments on this proposal are welcome!

Best regards
Alexander


--
Alexander Wolf
Bahnkonzept Dresden
Re: Additional attribute for crossing roads/rivers [message #1259 is a reply to message #1258] Mon, 26 October 2015 09:58 Go to previous messageGo to next message
Christian Rahmig is currently offline  Christian Rahmig
Messages: 151
Registered: January 2011
Senior Member
Dear Alex,
Dear railML IS community,

I took the idea and set up a ticket for this issue with the crossing
river/road/etc. (see [1]). If there are other users interested in it, we
can include this minor enhancement in the upcoming railML 2.3.

[1] https://trac.railml.org/ticket/271

Best regards
Christian

Am 24.10.2015 um 19:44 schrieb Alexander Wolf:
> Hello railML community,
>
> with our project GPSinfradat we record and visualise railway
> infrastructure data. All measured data can be exported with railML for
> utilisation in other railway applications and include information about
> railway topology, track elements and operational elements. Within
> projects concerning the planning of construction we are often asked to
> export the name of the crossing road (level crossings) or the passed
> river/road (bridges). Currently, this information can not be mapped in
> the railML data model yet!
>
> Therefore I suggest to extend the elements <bridge>, <levelCrossing> and
> <tunnel> in railML v2.3 with an additional attribute for the
> description/name of the crossing, e.g. "crossingElement".
>
> Comments on this proposal are welcome!
>
> Best regards
> Alexander
>
>
> --
> Alexander Wolf
> Bahnkonzept Dresden


--
Christian Rahmig
railML.infrastructure coordinator
Re: Additional attribute for crossing roads/rivers [message #1260 is a reply to message #1259] Mon, 26 October 2015 13:42 Go to previous messageGo to next message
Alexander Wolf is currently offline  Alexander Wolf
Messages: 5
Registered: October 2015
Junior Member
Dear Christian,

thank you for the quick response!

I had a look at your example in the ticket #271. From my point of view, it
would be a more generalized approach, allowing multiple crossing elements.

The enhanced example might look like this:

<bridge ... name="Marienbrücke">
<crossingElements>
<crossingElement ... name="Elbe" type="river" pos=2100 />
<crossingElement ... name="B6" type="road" pos=2150 />
<crossingElement ... name="Elberadweg" type="other" pos=2200 />
</crossingElements>
</bridge>

Usually only a few elements will occur here, but especially for larger
bridges a detailed description in the data model will be possible then.
Moreover, this link between the various infrastructure layers may also
help in other current railML projects [1].

Best regards,
Alexander


Links:
[1]
http://documents.railml.org/events/slides/2014-03-26_bmvi_bo ehm-bundesverkehrswegeplanung.pdf



Am 26.10.2015, 09:58 Uhr, schrieb Christian Rahmig
<coord(at)infrastructurerailmlorg>:

> Dear Alex,
> Dear railML IS community,
>
> I took the idea and set up a ticket for this issue with the crossing
> river/road/etc. (see [1]). If there are other users interested in it, we
> can include this minor enhancement in the upcoming railML 2.3.
>
> [1] https://trac.railml.org/ticket/271
>
> Best regards
> Christian
>
> Am 24.10.2015 um 19:44 schrieb Alexander Wolf:
>> Hello railML community,
>>
>> with our project GPSinfradat we record and visualise railway
>> infrastructure data. All measured data can be exported with railML for
>> utilisation in other railway applications and include information about
>> railway topology, track elements and operational elements. Within
>> projects concerning the planning of construction we are often asked to
>> export the name of the crossing road (level crossings) or the passed
>> river/road (bridges). Currently, this information can not be mapped in
>> the railML data model yet!
>>
>> Therefore I suggest to extend the elements <bridge>, <levelCrossing> and
>> <tunnel> in railML v2.3 with an additional attribute for the
>> description/name of the crossing, e.g. "crossingElement".
>>
>> Comments on this proposal are welcome!
>>
>> Best regards
>> Alexander
>>
>>
>> --
>> Alexander Wolf
>> Bahnkonzept Dresden
>
>


--
Alexander Wolf
Bahnkonzept Dresden
Re: Additional attribute for crossing roads/rivers [message #1261 is a reply to message #1260] Mon, 26 October 2015 15:43 Go to previous messageGo to next message
s.kuehnlenz is currently offline  s.kuehnlenz
Messages: 1
Registered: October 2015
Junior Member
Hello railML community,

we (Software-Service John GmbH) are interested in this new attribute. In
the context of our actual project (Bundesverkehrswegeplan 2015, Mr. Wolf
has alreadie mentioned) it would be quite useful.

With best regards,
Stephanie Kühnlenz

Alexander Wolf wrote:
>
> Dear Christian,
>
> thank you for the quick response!
>
> I had a look at your example in the ticket #271. From my point of view, it
> would be a more generalized approach, allowing multiple crossing elements.
>
> The enhanced example might look like this:
>
> <bridge ... name="Marienbr�cke">
> <crossingElements>
> <crossingElement ... name="Elbe" type="river" pos=2100 />
> <crossingElement ... name="B6" type="road" pos=2150 />
> <crossingElement ... name="Elberadweg" type="other" pos=2200 />
> </crossingElements>
> </bridge>
>
> Usually only a few elements will occur here, but especially for larger
> bridges a detailed description in the data model will be possible then.
> Moreover, this link between the various infrastructure layers may also
> help in other current railML projects [1].
>
> Best regards,
> Alexander
>
>
> Links:
> [1]
>
http://documents.railml.org/events/slides/2014-03-26_bmvi_bo ehm-bundesverkehrswegeplanung.pdf
>
>
>
> Am 26.10.2015, 09:58 Uhr, schrieb Christian Rahmig
> <coord(at)infrastructurerailmlorg>:
>
>> Dear Alex,
>> Dear railML IS community,
>>
>> I took the idea and set up a ticket for this issue with the crossing
>> river/road/etc. (see [1]). If there are other users interested in it, we
>> can include this minor enhancement in the upcoming railML 2.3.
>>
>> [1] https://trac.railml.org/ticket/271
>>
>> Best regards
>> Christian
>>
>> Am 24.10.2015 um 19:44 schrieb Alexander Wolf:
>>> Hello railML community,
>>>
>>> with our project GPSinfradat we record and visualise railway
>>> infrastructure data. All measured data can be exported with railML for
>>> utilisation in other railway applications and include information about
>>> railway topology, track elements and operational elements. Within
>>> projects concerning the planning of construction we are often asked to
>>> export the name of the crossing road (level crossings) or the passed
>>> river/road (bridges). Currently, this information can not be mapped in
>>> the railML data model yet!
>>>
>>> Therefore I suggest to extend the elements <bridge>, <levelCrossing> and
>>> <tunnel> in railML v2.3 with an additional attribute for the
>>> description/name of the crossing, e.g. "crossingElement".
>>>
>>> Comments on this proposal are welcome!
>>>
>>> Best regards
>>> Alexander
>>>
>>>
>>> --
>>> Alexander Wolf
>>> Bahnkonzept Dresden
>>
>>
>
>



--
----== posted via PHP Headliner ==----
Re: Additional attribute for crossing roads/rivers [message #1262 is a reply to message #1260] Mon, 26 October 2015 19:04 Go to previous message
coordination is currently offline  coordination
Messages: 9
Registered: May 2011
Junior Member
Dear all,

an idea - maybe already taken inti consideration by the responsible
coordinator - for better interoperability of the data:

Alexander Wolf wrote:
> The enhanced example might look like this:
>
> <bridge ... name="Marienbrücke">
> <crossingElements>
> <crossingElement ... name="Elbe" type="river" pos=2100 />
> <crossingElement ... name="B6" type="road" pos=2150 />
> <crossingElement ... name="Elberadweg" type="other" pos=2200 />
> </crossingElements>
> </bridge>

Why not using the same name for the tags like in Openstreetmap? This
description is used widely and free available via their wiki at
http://wiki.openstreetmap.org/wiki/Map_Features. Maybe we need not the
same level of detail (as we're not Openstreetmap) but it's always a good
idea to call the same things with the same name in exchange formats. If
other available formats (like GML) have descriptions too, maybe they are
closer to railML?

Regards,
--
Vasco Paul Kolmorgen
railML.org – Coordinator

--
----== posted via PHP Headliner ==----
Previous Topic: Re: Missing 'any' attributes/elements
Next Topic: Connection on TrackBegin and TrackEnd
Goto Forum:
  


Current Time: Fri Aug 18 05:08:55 CEST 2017