| Re: Schema version V0.95-02 released [message #97 is a reply to message #95] |
Wed, 22 September 2004 10:24  |
Ulrich Linder
Messages: 28
Registered: July 2003
|
Junior Member |
|
|
Hello,
"Matthias Hengartner" <hengartner(at)ivtbaugethzch> schrieb im Newsbeitrag
news:cia2it$mjt$1(at)sifaivifhgde...
> ...
> - the attribute "type" (of <track>) should not be required (because some
> exporting programms may not know what type a track is)
ok, is done in the current release.
> - could we have something like <generalElement> also in the
> <infraAttrGroup>
> ? ("<generalInfraAttribue>" or similar)
ok, is done in the current release.
> - I'm also glad about the possibility to place a switch (and also a
> crossing) on a <trackBegin> / <trackEnd>. But I'd prefer to have only a
> reference to a switch/crossing which is located in the
> <connections>-container.
Let's discuss on Thursday.
> - It's also a good thing that we have the absolute position separated in 2
> parts. But I'm a little bit confused about the format of these to
> attributes. Both are decimals with 12 digits, 5 of them after decimal
> point.
> What unit is "absPosOffset" meant to be? In the former versions of the
> schema, the 2 patterns for "absPos" were
> 1. km: {dddd}d.d{dddd}
> 2. km + m: {dddd}d.d + {ddd}dd{.dd}
> If these are close to reality (I guess they are), my suggestion is: 10/5
> digits for "absPos" (km) and 7/2 for "absPosOffset" (m)
"absPos" and "absPosOffset" have now the unit "km" to standardize the units
(see annotations). In the current release I've changed the cont of digits to
10/5. I've not notiived that the decimal point and the sign are not included
in the total count.
> - <mileageChange>: I'm confused about the use of absPos, absPosOffset,
> absPosIn and absPosInOffset, especially after having studied the two
> mileageChanges in the demoNet-file. Perhaps it would be clearer if we had
> "absPosOut" instead of "absPosIn".
The (german) understanding of the position of a mileage change is to assign
the mileage change to the outgoing mileage. Therefore "absPos" and
"absPosOffset" contain the outgoing mileage and "absPosIn" and
"absPosInOffset" contain the incoming mileage. If the international
understanding is different, we should change this soon. Let's discuss on
Thursday.
> - We have a new element type <trainProtectionElement> in the
> <ocsElements>-container, but we have also the ("old")
> <trainProtectionChange> in <trackElements>. Intention or mistake?
> If it's intention, what is the difference between <trainProtectionElement>
> and <trainProtectionChange>?
> If it's a mistake, why is the attribute "monitoring" not included anymore?
The "trainProtectionChange" contains a general information about the train
protection system whereas a "trainProtectionElement" contains a single
element (i.e. INDUSI, "Gleissperre"). Therefore a train protection element
has no information about the type of monitoring.
See also discussion thread from Volker Knollmann 2003-11-19.
> - The new <crossing>-element has an attribute "dir". What is the use of
> this, since we have already the "branchDir"-attribute in the connection?
ok, is done in the current release.
> - I've noticed, that longitude, latitude and altitude are now implemented
> as
> attributes instead of child-elements of <geoCoords>. I'm fine with that.
ok, was done some month before ;-)
> - and finally, 2 little misprints:
> <axleCounter>/posInTrack --> outsideRIght
> annotation of "absPosAttrGroup" ("handlicng")
ok, is done in the current release.
> See you next week in Berlin!
See you tomorrow in Berlin!
With best regards
------------------------------
Dr.-Ing. Ulrich Linder
Linder Rail Consult
Mörchinger Str. 25
D-14169 Berlin
Tel. +49.30.84 72 56 87
Fax. +49.30.84 47 11 56
Email mailto:UlrichLinder(at)linder-rail-consultde
www http://www.Linder-rail-consult.de
|
|
|
|
Members
Search
Help
Login
Home
