Home » railML newsgroups » railML.infrastructure » speedPanel and complementaryPanel
speedPanel and complementaryPanel [message #333] Wed, 04 July 2012 20:12 Go to next message
pierre.simon is currently offline  pierre.simon
Messages: 8
Registered: July 2012
Junior Member
In the Belgium railway, speed panel may have an additional information
called <complementaryPanel>.
This gives information about the category of train which have to consider
this panel. We could have for the same <speedPanel>, a list of
<complementPanel>.

We suggest to add a <complementaryPanel> element to the <speedPanel> to
fill this information in.

[de: Es werden verschiedene Zusatztafeln fuer Geschwindigkeitstafeln
benoetigt.]

--
----== posted via PHP Headliner ==----
Re: speedPanel and complementaryPanel [message #343 is a reply to message #333] Thu, 05 July 2012 16:03 Go to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Dear Pierre,

> In the Belgium railway, speed panel may have an additional information
> called <complementaryPanel>.
> This gives information about the category of train which have to consider
> this panel. We could have for the same <speedPanel>, a list of
> <complementPanel>.

The question, for which train a speed change applies, is expressed in
RailML by the new properties of speed profiles. See [1] and Susanne's post
from Friday 29th June for further information.

If you have a speed change valid for trains with certain properties or so,
the certain properties should be listed at the speed profile the speed
change belongs to.

Possibly you have to make several speed profiles and several speed changes
at the same place (same meter), each one referencing a different speed
profile.

Any additional properties at speed changes must not be redundancies to the
properties of speed profiles.

It seams to me that <complementPanel> is a little bit too specific / too
less general.

If your speed changes really depend on the train's category, we should add
the train's category as an attribute of speed profiles. But I am not sure
whether this is advisable. In RailML, a train category is more a
'commercial' aspect than a technical. Speed changes should normally depend
on technical properties, not on commercial. So I guess the speed change
rather depends on the train having tilting technology or reduced axle load
or such. This would fit to the properties we already have introduced for
speed profiles. May be in Belgium such things as tilting technology or
reduced axle load are treated as 'train category' but this would not fit
to the more generals RailML's view.

With best regards,
Dirk.

[1] http://trac.assembla.com/railML/ticket/41
Previous Topic: small change of attribute 'zip'
Next Topic: Grouping of <ocp> elements in an <ocpGroup>
Goto Forum:
  


Current Time: Fri Mar 29 06:27:13 CET 2024