Dev:CommonDataTypes: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[unchecked revision][checked revision]
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{note|This page is outdated. Instead, consult [[dev:Unit]].|error}}
'''Warning: This page has to be harmonized with other subschema attribute/element/type pages!'''
----
This page is used to collect all data types used in the schemas. The target is to harmonize and re-use data types throughout the different schemas.
This page is used to collect all data types used in the schemas. The target is to harmonize and re-use data types throughout the different schemas.


Line 35: Line 41:
|
|
|
|
|Geographical position. The used coordinate system is still under discussion.
|Geographical position. The used coordinate system has to be referenced.
|-
|-
|UIC-Number
|UIC-Number
Line 89: Line 95:
|
|
|
|
|Is this correct?
|
|-
|-
|Speed
|Speed
Line 98: Line 104:
|
|
|x
|x
|Or did we agree on [m/s] in the last meeting?
|
|-
|-
|Angle
|Angle
Line 107: Line 113:
|
|
|
|
|Should we really use radian instead of grad (2 Pi = 360 Grad)?
|
|-
|-
|Slope
|Slope
|Promille (has no unit) ?
|Permille (has no unit)
|float (6.2)
|float (6.2)
|x
|x
Line 116: Line 122:
|
|
|
|
|Is the unit correct? Or do we use "Percent"?
|
|-
|-
|Country ID (for Balises)
|Country ID (for Balises)
Line 174: Line 180:


= Attributes with arbitrary values =
= Attributes with arbitrary values =
Currently there are a lot of "free parameters" (mostly strings), which are not strictly typed. In order to improve the interoperability between railML-capable applications, these only loosely typed variables should be defined more strictly.


The following table lists the variables which can currently be assigned with arbitrary values:
The following table lists the variables which can currently be assigned with arbitrary values:
Line 270: Line 274:
|
|
|
|
|Meaning? Examples?
|Meaning?
|-
|-
|model
|model
Line 297: Line 301:
|
|
|
|
|Meaning? Examples?
|Meaning?
|-
|-
|protection
|protection
Line 306: Line 310:
|
|
|
|
|Clearness detection of the LX (Radar, visual)? Or "selbstüberwacht" ("Überwachungssignal") vs. block protected ("HP")?
|
|-
|-
|kind
|kind
Line 315: Line 319:
|
|
|x
|x
|Meaning? Examples?
|Meaning?
|-
|-
|sigSystem
|sigSystem
Line 324: Line 328:
|
|
|
|
|Something like, Ks, H/V, ...
|
|-
|-
|staticTelegram
|staticTelegram
Line 371: Line 375:
|(comment)
|(comment)
|}
|}
[[category:DeprecatedDescriptions]]

Latest revision as of 12:16, 3 June 2019

❗ This page is outdated. Instead, consult dev:Unit.


Warning: This page has to be harmonized with other subschema attribute/element/type pages!

This page is used to collect all data types used in the schemas. The target is to harmonize and re-use data types throughout the different schemas.


Simple Types

"Simple Types" are scalars based on integers or floating point numbers. The describe values like time, length or velocities. Vectors, lists (enumerations) or structures are not covered in this section!


Scalar's Name Scalar's Unit Encoding Used in ... Comment
IS IL RS TT
Position, distance, radius km, m float (0.3) x x May occur as absolute or relative Position along the track, as abs. or rel. offset, as distance between two points, as radius or as superelevation
Latitude, Longitude, Altitude ? float x Geographical position. The used coordinate system has to be referenced.
UIC-Number (none) integer x UIC-No. which belongs to a <<Owner>>.
Voltage V integer x
Frequency Hertz (1/s) float x
Gauge mm float (0.3) x
Weight kg float x
Axle Load ("meterload") kg/m float (0.3) x
Speed km/h (?) float x x
Angle rad (has no unit) float x
Slope Permille (has no unit) float (6.2) x
Country ID (for Balises) (none) integer x
Group ID (for Balises) (none) integer x
Point (Coordinates on a screen) pixel float x Used in the visualization part. Shouldn't the unit be integer?
Size (Screen size of an element) pixel float x Used in the visualization part. Shouldn't the unit be integer?
(name) (unit) (enc) (comment)
(name) (unit) (enc) (comment)

Attributes with arbitrary values

The following table lists the variables which can currently be assigned with arbitrary values:

Attribute Part of Type Used in ... Comment
IS IL RS TT
ID (various) string x x Occurs as infrastructureID, lineID, trackID, elemID, ocpID
name (various) string x x Occurs in almost all elements as optional identifier / classifier
description tOperatingPeriod, tTrain, tHoliday string x Something longer than a name
Owner Name OwnerType string x
modeLegislative operationModeType string x
modeExecutive operationModeType string x
style powerTransmissionType string x
model switchType, crossingType string x Model of the switch or crossing. Meaning?
system trainProtectionElementType string x Meaning?
model trainProtectionElementType string x Meaning? Examples?
trainCategory speedType string x Letter indicating the type of Train (e. g. "R")
status speedType, speedChangeType string x Meaning?
protection levelCrossingType string x
kind bridgeType, trainType string x x Meaning?
sigSystem signalType string x
staticTelegram baliseType, baliseGroupType string x Coded? Uncoded? Binary? Plaintext?
model trainDetectorType string x Examples?
number operationControlPointType, ocpAreaType string x Meaning?
type ocpPropOperationalType string x Meaning?
(name) (parent) (type) x (comment)
Retrieved from "https://wiki2.railml.org/index.php?title=Dev:CommonDataTypes&oldid=9901"