Home » railML newsgroups » railML.infrastructure » some understanding questions: cross section & stations & stopping points
Re: some understanding questions: cross section & stations & stopping points [message #147 is a reply to message #146] Wed, 16 February 2005 13:56 Go to previous messageGo to previous message
Volker Knollmann is currently offline  Volker Knollmann
Messages: 32
Registered: October 2003
Member
On 14.02.2005 17:03, Albrecht Achilles wrote:
> 1.crossSection
> What is meant with this element?

I would guess that this element descibes a passenger crossing in a
station. Or other possibility: this describes the exact middle of a
station (in German: "Bahnhofsmitte") which is a reference point for
things like mileage, borders, etc.

Furthermore, in German there is the word "Bahnhofsquerschnitt" which is
closest translation to "crossSection". AFAIK this "Bahnhofsquerschnitt"
has a certain operational meaning, but I don't remember what it is. And
neither Prof. Pachl's glossary nor allmighty google could answer that
question. But perhaps I'm just wrong...

Can anyone please rectify or falsify my assumptions? Thanks!

> 2.stations
> When I want to create a station on a track so i have to use the ocp's and
> its attributes!?

Yes.

> But how can I indicate that the station has a length, and
> is not only a point?

Well, "ocp" just introduces a station. It's more or less a declaration
("There is thing called ABCD").

And now it's time for some nitpicking:

<nitpick>
The "length of a station" (that's what you asked for) is given
implicitly by the distance between it's entry signals. This information
can be derived from the existing railML-scheme.

What you probably meant was the "length of a platform", and yes, this
information is not yet provided in the infrastructure scheme.
</nitpick>

If you want to save the length of a platform, you could store it as
"generalElement" indicating the start or end of a platform. Thus, you
keep compatible with version 1.0.

But of course you may also think of a suitable XML-description and post
it in this list for further discussion. Then you proposal can be taken
into account for future railML-versions.

One last hint:
In one of the last railML-meetings (I think it was in Braunschweig in
April 2004) we've had a presentation about a station-scheme. Perhaps you
can find some useful information in the presentations and proceedings of
that meeting. The document are available on the railML-website. I don't
know about the current status of the station-scheme.

> 3.stopping points
> how can I display a stopping point in a railml file?

Quick and dirty (don't try this at home!):
<.....>
<signal pos="4.242" function="stoppingPoint" type="sign"/>
<.....>

Occasionally, you can add "switchable=false" to indicate that this is a
static sign and no switchable signal (if the "switchable"-attribute is
really meant like that).
The schema does not give further constraints for the values of the
"function"- or "type"-field of <signal>-elements. Basically, you can do
whatever you want here and be perfectly compatible with yourself (and
probably noone else).

IIRC, we have discussed that topic earlier here but without result.
Perhaps we should reactivate that discussion for future versions.


Please anyone feel free to correct we!


HTH,
Volker Knollmann
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: <speedChangeGroup>
Next Topic: New coordinator for infrastructure schema
Goto Forum:
  


Current Time: Sat May 18 15:06:08 CEST 2024