| questions & suggestions 2 [message #68] |
Wed, 07 April 2004 18:48  |
Matthias Hengartner
Messages: 57
Registered: August 2003
|
Member |
|
|
Hello again,
here some more points about miscellaneous topics:
- We have three element types (levelCrossings, tunnels, bridges) containing
the attribute "posInd", which has the possible values "begin", "end",
"middle" or "unknown". Farther, we have the "dir" attribute, which belongs
to each line element type. I think this could cause some confusion. The use
of these attributes has to be very well-defined. Is it possible to map the
values of "posInd" to the values of "dir" (up=begin, down=end, both=middle)
and vice versa, or not? If yes, why do we have both these attributes? If no,
how should they be used?
- I refer to the old proposal of Joachim Büchse: Shouldn't we divide the
attribute "absPos" in two parts, one for the actual (absolute) position
[km], and
the other for possible excess lengths (Überlängen) [m]? If needed, the
importing
and exporting programs can still translate it to the "traditional" pattern.
- What about an new line element type "emptyElement", which has the type
"elementBaseType"? I see three ways (maybe there are more) how they could be
applied:
1. For visualisation purposes
2. For elements, which have no line element specific information yet, but
are intended to get such information to a later point of time
3. For line elements, which are not (yet) supported by railML. Exporting
application could at least export some basic information about such an
element.
I propose to integrate <emptyElement>. The remaining question is, where to
locate it, as child of <trackTopology>, <trackData> or even both?
Suggestions?
- Should we leave the infrastructure visualisation part as a direct child
element of the <railML> root, or should we take it as a child of
<infrastructure>? Or should there be a container for all thinkable types
visualisations (not only for infrastructure)?
Thank you for your opinions!
Best regards,
Matthias Hengartner
|
|
|
|
|
|
Members
Search
Help
Login
Home
