| Re: Additional attribute for crossing roads/rivers [message #1261 is a reply to message #1260] |
Mon, 26 October 2015 15:43   |
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 ==----
|
|
|
|
Members
Search
Help
Login
Home
