QUDT Vocabulary of Datatypes v3.2.0
type: Ontology
imports: qudt
imports: dtype
imports: vaem
has graph metadata: QUDT Datatypes Version 3.2Vocabulary
has graph role: VocabularyGraph

contributor
type: AnnotationProperty
range: string

creator
type: AnnotationProperty
range: string

description
type: AnnotationProperty
range: string

rights
type: AnnotationProperty
range: string

subject
type: AnnotationProperty
range: string

title
type: AnnotationProperty
range: string

ALPHANUMERIC
type: CharacterType
code: 106
literal: alphanumeric
bits: 8
bytes: 1
id: T001-00
rdfs datatype: byte

BOOLEAN
type: BooleanType
description: In computer science, the Boolean or logical data type is a data type, having two values (usually denoted true and false), intended to represent the truth values of logic and Boolean algebra. The Boolean data type is the primary result of conditional statements, which allow different actions and change control flow depending on whether a programmer-specified boolean condition evaluates to true or false.
code: 1
literal: boolean
was influenced by: Boolean data type
was influenced by: http://msdn.microsoft.com/en-us/library/aa275635(v=sql.80).aspx
ansi SQL name: BOOLEAN
encoding: Boolean Encoding
id: T000-01
java name: boolean
js name: Boolean()
microsoft SQL server name: bit
my SQL name: BOOL
my SQL name: BOOLEAN
my SQL name: TINYINT(1)
odbc name: SQL_BIT
ole DB name: DBTYPE_BOOL
oracle SQL name: RAW(1)
protocol buffers name: bool
python name: bool
rdfs datatype: boolean

Byte
type: SignedShortIntegerType
description: The byte data type is an 8-bit signed two's complement integer. It has a minimum value of -128 and a maximum value of 127 (inclusive). The byte data type can be useful for saving memory in large arrays, where the memory savings actually matters. They can also be used in place of int where their limits help to clarify your code; the fact that a variable's range is limited can serve as a form of documentation.
code: 800
literal: byte
was influenced by: datatypes.html
abbreviation: SI8
bytes: 1
c name: Byte
encoding: OCTET Encoding
id: T002-01
max inclusive: 127
min inclusive: -128
rdfs datatype: byte
signedness: Signed

Big Endian
type: EndianType
description: A big-endian machine stores the most significant byte first.
code: 1
literal: big

Bit aligned
type: AlignmentType
description: Alignment at a bit level.

Bit Encoding
type: BitEncodingType
bits: 1

Bit Field of 1 bit
type: BitField
literal: B1
was influenced by: bit-type.html
abbreviation: bf1
bits: 1
id: T010-01
my SQL name: BIT(1)

Bit Field of 2 bits
type: BitField
code: 182
literal: B2
was influenced by: bit-type.html
abbreviation: bf2
bits: 2
id: T010-02
my SQL name: BIT(2)

Bit Field of 3 bits
type: BitField
code: 183
literal: B3
was influenced by: bit-type.html
abbreviation: bf3
bits: 3
id: T010-03
my SQL name: BIT(3)

Bit Field of 4 bits
type: BitField
code: 184
literal: B4
was influenced by: bit-type.html
abbreviation: bf4
bits: 4
id: T010-04
my SQL name: BIT(4)

Bit Field of 5 bits
type: BitField
code: 185
literal: B5
was influenced by: bit-type.html
abbreviation: bf5
bits: 5
id: T010-05
my SQL name: BIT(5)

Bit Field of 6 bits
type: BitField
code: 186
literal: B6
was influenced by: bit-type.html
abbreviation: bf6
bits: 6
id: T010-06
my SQL name: BIT(6)

Bit Field of 7 bits
type: BitField
code: 187
literal: B7
was influenced by: bit-type.html
abbreviation: bf7
bits: 7
id: T010-07
my SQL name: BIT(7)

Bit Field of 8 bits
type: BitField
code: 188
literal: B8
was influenced by: bit-type.html
abbreviation: bf8
bits: 8
id: T010-08
my SQL name: BIT(8)

Bit Field of 9 bits
type: BitField
code: 189
literal: B9
was influenced by: bit-type.html
abbreviation: bf9
bits: 9
id: T010-09
my SQL name: BIT(9)

Bit Field Of 10 Bits
type: BitField
code: 190
literal: B10
was influenced by: bit-type.html
abbreviation: bf10
bit order: Big Endian
bits: 10
byte order: Big Endian
id: T010-02
my SQL name: BIT(10)

Bit Field Of 11 Bits
type: BitField
code: 191
literal: B11
was influenced by: bit-type.html
abbreviation: bf11
bits: 11
id: T010-11
my SQL name: BIT(11)

Bit Field of 12 bits
type: BitField
literal: B12
abbreviation: bf12
bits: 12
my SQL name: BIT(12)

Boolean Encoding
type: BooleanEncodingType

By Column
type: ArrayDataOrder
literal: byColumn

By Left Most Index
type: ArrayDataOrder
literal: byLeftMostIndex

By row
type: ArrayDataOrder
literal: byRow

Byte aligned
type: AlignmentType
description: Alignment of a field at a byte boundary.

Earth-centered Coordinate System Type
type: CoordinateCenterKind
literal: earthCentered

Mars-centered Coordinate System Type
type: CoordinateCenterKind
literal: marsCentered

Moon-centered Coordinate System Type
type: CoordinateCenterKind
literal: moonCentered

Sun-centered Coordinate System Type
type: CoordinateCenterKind
literal: sunCentered

Vehicle-centered Coordinate System Type
type: CoordinateCenterKind
literal: vehicleCentered

Common Data Format (CDF)
type: MultiDimensionalDataFormat
description: CDF (Common Data format), a data format for storing and manipulating scalar and multidimensional data in a platform and discipline independent manner, making interoperability between applications and tools easier. CDF provides device independent view of the CDF data model by software programming interface insulting developers from actual physical file format. CDF was developed by NASA, and is described at http://cdf.gsfc.nasa.gov/.

Concatenate Matrix Rows
type: CompositionFunction

CHAR
type: CharacterType
literal: char
bits: 8
bytes: 1
encoding: Char Encoding
id: T001-01
rdfs datatype: byte

Amber Color
type: ColorCue
literal: amber
rgb code: #FFBF00

Green color
type: ColorCue
literal: green
rgb code: #008000

Orange color
type: ColorCue
literal: orange
rgb code: #FFA500

Red color
type: ColorCue
literal: red
rgb code: #FF0000

Yellow color
type: ColorCue
literal: yellow
rgb code: #FFFF00

Countably Infinite Cardinality Type
type: CardinalityType
description: A set of numbers is called countably infinite if there is a way to enumerate them. Formally this is done with a bijection function that associates each number in the set with exactly one of the positive integers. The set of all fractions is also countably infinite. In other words, any set $X$ that has the same cardinality as the set of the natural numbers, or $| X | \; = \; | \mathbb N | \; = \; \aleph0$, is said to be a countably infinite set.
literal: countable
informative reference: http://www.math.vanderbilt.edu/~schectex/courses/infinity.pdf

Finite Cardinality Type
type: CardinalityType
description: Any set $X$ with cardinality less than that of the natural numbers, or $$| X | \; < \; | \mathbb N | $$ is said to be a finite set.
literal: finite

Uncountable Cardinality Type
type: CardinalityType
description: Any set with cardinality greater than that of the natural numbers, or $$| X | \; > \; | \mathbb N | $$ For example $| R| \; = \; c \; > |\mathbb N |$, is said to be uncountable.
literal: uncountable

Char Encoding
type: BooleanEncodingType
type: CharEncodingType
bytes: 1

Date
type: DateStringType
description: Provides the date expressed in year, month and day. Expressed as "YYYY:MM:DD", where YYYY is a 4 digit year, MM is a 2 digit month and DD is a 2 digit day.
code: 255
literal: date
dimensionality: 1
id: T004-01
rdfs datatype: date

Date Time
type: DateStringType
description: A time stamp encoded as a string 'YYYY-MM-DDThh:mm:ss[.dd]' or 'YYYY-DDDThh:mm:ss[.dd]', where 'YYYY' is the year, 'MM' is the two-digit month, 'DD' is the two-digit day, 'DDD' is the three digit day of year, 'T' is constant, 'hh:mm:ss[.dd]' is the UTC time in hours, minutes, seconds, and optional fractional seconds. As many 'd' characters to the right of the period as required may be used to obtain the required precision. All fields require leading zeros.
literal: datetime
dimensionality: 1
exact match: UTC Date Time
rdfs datatype: dateTime

Decimal
type: NumericType
code: 101
literal: numeric
ansi SQL name: DECIMAL(p,s)
odbc name: SQL_DECIMAL(p,s)
oracle SQL name: NUMBER(p,s)
rdfs datatype: decimal

DIGIT
type: CharacterType
literal: digit
bits: 8
bytes: 1
id: T001-02
rdfs datatype: byte

Double Precision Encoding
type: FloatingPointEncodingType
bytes: 64

Earth centered earth mean equator and prime meridian coordinate system
type: EarthCoordinateSystem
code: 10
literal: EC-EMEP
coordinate center: Earth-centered Coordinate System Type
id: TECS-03
reference frame: Earth Mean Equator and Prime Meridian
definition: Earth Centered Earth Mean Equator And Prime Meridian Coordinate System
acronym: EC-EMEP

Earth centered earth true equator and prime meridian of epoch coordinate system
type: EarthCoordinateSystem
code: 12
literal: EC-ETEP
coordinate center: Earth-centered Coordinate System Type
id: TECS-04
reference frame: Earth True Equator and Prime Meridian of Epoch
definition: Earth Centered Earth True Equator And Prime Meridian Of Epoch Coordinate System

Earth centered international celestial reference system
type: EarthCoordinateSystem
code: 14
literal: EC-IC
coordinate center: Earth-centered Coordinate System Type
id: TECS-01
reference frame: International celestial reference frame
definition: Earth Centered International Celestial Reference System

Earth centered international terrestrial reference system
type: EarthCoordinateSystem
code: 16
literal: EC-IT
coordinate center: Earth-centered Coordinate System Type
id: TECS-02
reference frame: International Terrestrial Reference Frame
definition: Earth Centered International Terrestrial Reference System

Sun-Centered international celestial reference system
type: EarthCoordinateSystem
code: 90
coordinate center: Earth-centered Coordinate System Type
id: TECS-05
reference frame: International celestial reference frame
definition: Sun Centered International Celestial Reference System

Vehicle centered international celestial reference system
type: EarthCoordinateSystem
code: 100
literal: VC-IC
coordinate center: Earth-centered Coordinate System Type
id: TECS-06
reference frame: International celestial reference frame
definition: Vehicle Centered International Celestial Reference System

False
type: BooleanTypeEnumeratedValue
literal: false

FLAG
type: BooleanType
code: 2
literal: flag
id: T000-02
rdfs datatype: boolean

Double Precision Real
type: RealDoublePrecisionType
description: A double precision floating point datatype. Numbers of this type are stored using 64 bits, they require more memory than numbers of type single, which use 32 bits. However, because they are stored with more bits, numbers of type double are represented to more precision than numbers of type single. The double-precision (or double) data type is represented according to IEEE Standard 754 for double precision. A value is formatted with bit-fields for sign, mantissa and exponent.
code: 405
literal: double
was influenced by: floating-point-types.html
was influenced by: datatypes.html
was influenced by: Floating point
was influenced by: IEEE floating point
was influenced by: http://msdn.microsoft.com/en-us/library/aa275635(v=sql.80).aspx
was influenced by: floating-point-numbers.html
abbreviation: F64
ansi SQL name: DOUPLE PRECISION
base: 2
bits: 64
bytes: 8
encoding: Double Precision Encoding
exact match: IEEE754 BINARY64
id: T006-03
java name: double
js name: double
matlab name: double
max exclusive: (1-2^{-53}) \times 2^{1024}
max exponent: 1023
max mantissa: 9007199254740991
microsoft SQL server name: float
min exclusive: -(1-2^{-53}) \times 2^{1024}
min mantissa: -9007199254740991
my SQL name: DOUBLE
odbc name: SQL_DOUBLE
ole DB name: DBTYPE_R8
oracle SQL name: FLOAT(49)
rdfs datatype: double

Single Precision Real
type: RealSinglePrecisionType
description: A single precision real is a 32 bit signed floating point representation. Numbers of type single are stored using 32 bits, they require less memory than numbers of type double, which use 64 bits. However, because they are stored with fewer bits, numbers of type single are represented to less precision than numbers of type double.
literal: single
was influenced by: floating-point-types.html
was influenced by: datatypes.html
was influenced by: Floating point
was influenced by: http://msdn.microsoft.com/en-us/library/aa275635(v=sql.80).aspx
was influenced by: http://www-01.ibm.com/support/docview.wss
was influenced by: floating-point-numbers.html
was influenced by: apb.htm
ansi SQL name: FLOAT
bits: 32
bytes: 4
c name: float
encoding: Single Precision Real Encoding
id: T006-01
java name: float
js name: float
matlab name: single
max exclusive: $(2-2^{-23}) \times 2^127$
max exponent: 23
microsoft SQL server name: real
min exclusive: -(2-2^{-23}) \times 2^{127}
my SQL name: FLOAT
odbc name: SQL_FLOAT
ole DB name: DBTYPE_R4
oracle SQL name: FLOAT(23)
rdfs datatype: float

IEEE754 BINARY64
type: RealDoublePrecisionType
description: The IEEE-754 floating point datatype is a technical standard established in 1985 by the Institute of Electrical and Electronics Engineers (IEEE). Many hardware floating point units use the IEEE 754 standard.
was influenced by: IEEE floating point
base: 2
bits: 64
exact match: Double Precision Real
id: T006-05
max exponent: 970
max mantissa: 9007199254740991
min mantissa: -9007199254740991
rdfs datatype: double

Inertial Frame Type
type: FrameType
literal: inertial

Non-rotating Frame Type
type: FrameType
literal: nonrotating

Rotating Frame Type
type: FrameType
literal: rotating

Global Position Vector - double precision
type: StateSpaceVector
code: 360
datatype: Double Precision Real
dimensionality: 1
dimensions: 3

HDF5
type: MultiDimensionalDataFormat
description: The Hierarchical Data Format (HDF) is a common data format and a collection of application programming libraries developed at the NSCA primarily for the scientific community and for the exchange of scientific datasets. A commonly-used version of HDF is HDF5 which offers a simple data model and application interfaces for encoding and exchanging data without the added burden of defining mappings to the underlying machine representations.

HDF6
type: MultiDimensionalDataFormat
description: A "Hierarchical Data Format".

HEXBINARY
type: HexBinaryType
code: 803
literal: hexbinary
dimensionality: 1
rdfs datatype: hexbinary

High to Low
type: MemoryOrderType
literal: high_to_low

IEEE 754 1985 Real Encoding
type: FloatingPointEncodingType
bytes: 32

IERS-TN-32-2004
type: Citation
description: IERS Conventions (2003), D. D. McCarthy and Gérard Petit (eds.), IERS Technical Note No. 32, 2004; http://www.iers.org/iers/publications/tn/tn32.
url: http://www.iers.org/iers/publications/tn/tn32.

Integer
type: SignedIntegerType
description: An Integer is an XML Schema Definition (XSD) datatype that represents arbitrary-precision whole numbers (positive, negative, or zero) without fractional or decimal components. It is derived from xsd:decimal by restricting values to integers only..
code: 104
literal: SI
abbreviation: SI
ansi SQL name: INT
bits: 16
bytes: 2
encoding: Short Signed Integer Encoding
id: T002-03
java name: integer
js name: integer
matlab name: int
microsoft SQL server name: int
my SQL name: INT
rdfs datatype: integer

ISO 8601 UTC Date Time - Basic Format
type: DateTimeStringEncodingType
allowed pattern: [0-9]{4}[0-9]{2}[0-9]{2}T[0-9]{2}[0-9]{2}[0-9]{2}.[0-9]+Z
allowed pattern: [0-9]{4}[0-9]{2}[0-9]{2}T[0-9]{2}[0-9]{2}[0-9]{2}Z

Interpolated table
type: InterpolatedTable

Konopliv2001
type: Citation
description: "Recent Gravity Models as a Result of the Lunar Prospector Mission", A. S. Konopliv, S. W. Asmar, E. Carranza, W. L. Sjogren, and D. N. Yuan, Academic Press, Icarus 150, 1-18 (2001).

Lunar mean earth body fixed Coordinate System
type: LunarCoordinateSystem
code: 40
literal: LMEBF
coordinate center: Moon-centered Coordinate System Type
id: TLCS-01
reference frame: Lunar Mean Earth Body-Fixed
definition: Lunar Mean Earth Body Fixed Coordinate System

Lunar principal axis body fixed Coordinate System
type: LunarCoordinateSystem
description: Lunar body-fixed coordinate frame aligned with the principal axes of the Moon.
code: 42
literal: LPABF
coordinate center: Moon-centered Coordinate System Type
id: TLCS-02
realization: This is a fixed rotation from LMEBF
reference frame: Lunar Principal Axis Body-Fixed
definition: Lunar Principal Axis Body Fixed Coordinate System

Lunar Principal Axis of Epoch Coordinate System
type: LunarCoordinateSystem
code: 42
literal: LPABF
coordinate center: Moon-centered Coordinate System Type
id: TLCS-03
reference frame: Lunar Principal Axis of Epoch

LETTER
type: CharacterType
literal: letter
bits: 8
bytes: 1
id: T001-03
rdfs datatype: byte

Little Endian
type: EndianType
description: A little-endian machine stores the least significant byte first.
code: 2
literal: little

Long Signed Integer Encoding
type: IntegerEncodingType
bytes: 8

Long Unsigned Integer Encoding
type: IntegerEncodingType
bytes: 8

Low to High
type: MemoryOrderType
literal: low_to_high

Mars mean equator and IAU-Node of epoch Coordinate System
type: MarsCoordinateSystem
code: 50
literal: MMEIAUE
coordinate center: Mars-centered Coordinate System Type
id: TMCS-01
reference frame: Mars Mean Equator and IAU-Node of Epoch
definition: Mars Mean Equator And IAU-Node Of Epoch Coordinate System

Mars mean equator and prime meridian body-fixed Coordinate System
type: MarsCoordinateSystem
code: 52
literal: MMEPMBF
coordinate center: Mars-centered Coordinate System Type
id: TMCS-02
reference frame: Mars Mean Equator and Prime Meridian Body-Fixed
definition: Mars Mean Equator And Prime Meridian Body-Fixed Coordinate System

Major
type: MajorMinorType
code: 2
literal: major
order: 2

Minor
type: MajorMinorType
code: 1
literal: minor
order: 1

No
type: YesNoType
literal: N

Earth True Equator and Prime Meridian Body Fixed
type: NonRotatingInertialFrame
literal: ETEPMBF
exact match: International Terrestrial Reference Frame
frame type: Non-rotating Frame Type
id: T110-01
realization: The International Terrestrial Reference Frame (ITRF) is realized by the locations of a set of points or stations on a tide-free Earth. As measurements and models have improved or changed, these locations have been changed also and the ITRF has moved slightly with respect to the physical Earth every few years.
x axis definition: The intersection of the prime meridian and the rotation equator of the Earth.
y axis definition: Completes a standard, right-handed coordinate frame.
z axis definition: The rotation pole of the Earth.

Earth True Equator and Prime Meridian of Epoch
type: NonRotatingInertialFrame
description: The "Earth's True Equator and Prime Meridian of Epoch" refers to a coordinate system defined by Earth’s equator and prime meridian at a specific moment in time, called the “epoch.” This system is used as a reference in astronomy, geodesy, and celestial mechanics. The NASA Deep Space Network uses the Lieske precession model (1976).
literal: ETEPME
frame type: Non-rotating Frame Type
id: T110-02
informative reference: IERS-TN-32-2004
realization: The International Terrestrial Reference Frame as defined for 1993 (ITRF93), as located in the ICRF at the epoch given using a consistent set of precession, nutation, and timing and polar motion models.
x axis definition: The intersection of the prime meridian and the rotation equator of the Earth, in the ICRF and at the epoch given.
y axis definition: Completes a standard, right-handed coordinate frame.
z axis definition: The rotation pole of the Earth, in the ICRF and at the epoch given.

International celestial reference frame
type: NonRotatingInertialFrame
description: The International celestial reference frame (ICRF) is the best-determined and most stable reference frame and is the root frame. Other reference frames are often given with respect to the ICRF.
literal: ICRF
exact match: International Celestial Reference Frame
frame type: Non-rotating Frame Type
id: T110-03
realization: The International Celestial Reference Frame (ICRF) was defined in 1995 with locations given for 22 quasars and other bright radio objects. This definition was extended by the addition of more sources in 2000.
x axis definition: Defined as the cross product of the Z-axis (as defined above) and the Earth mean orbit pole of J2000 (i.e. the ecliptic pole of J2000). The X-axis of this coordinate frame is the Earth vernal equinox of J2000.
y axis definition: Completes a standard, right-handed coordinate frame.
z axis definition: Defined as the pole vector of the Earth Mean Equator of J2000 (where J2000 = Julian date 2451545.0 TDB (Barycentric Dynamical Time)).

Lunar Principal Axis of Epoch
type: NonRotatingInertialFrame
code: 44
literal: LPAE
abbreviation: LPAE
frame type: Non-rotating Frame Type
id: T110-04
x axis definition: Points in the direction of the Moon’s prime meridian principal axis of Epoch (minimum moment of inertia).
y axis definition: Completes a standard, right-handed coordinate frame.
z axis definition: Points in the direction of the Moon’s North pole principal axis of Epoch (maximum moment of inertia).
comment: Finding the principal axes depends on solving for the dynamics of the Moon’s orientation, which must be done in conjunction with solving for its motion in space, though the Moon’s motion in space can also be solved for independently. The terms “north pole” and “prime meridian” are loosely used for the Z and X axes respectively of both this and the Lunar Mean Earth frames.
definition: Lunar Principal Axis Of Epoch Coordinate System

Mars Mean Equator and IAU-Node of Epoch
type: NonRotatingInertialFrame
code: 50
literal: MMEIAUE
frame type: Non-rotating Frame Type
id: T110-05
realization: This frame is realized from the ICRF, precessed and rotated Relationships: according to the formulae in IAU2000, [Seidelmann2000]
x axis definition: Defined as the cross product of the ICRF Z-axis with the Z-axis (as defined above).
y axis definition: Completes a standard, right-handed coordinate frame.
z axis definition: Defined as the pole vector of the Mars Mean Equator of Epoch.
definition: Mars Mean Equator And IAU-Node Of Epoch Coordinate System

Numeric
type: NumericType
code: 101
literal: numeric
ansi SQL name: DECIMAL(p,s)
odbc name: SQL_DECIMAL(p,s)
oracle SQL name: NUMBER(p,s)

Negative X
type: AxialOrientationType
description: The axis that is in the negative X direction.
code: 1
literal: negativeX

Negative Y
type: AxialOrientationType
description: The axis that is in the negative Y direction.
code: 2
literal: negativeY

Negative Z
type: AxialOrientationType
description: The axis that is in the negative Z direction.
code: 3
literal: negativeZ

NetCDF
type: MultiDimensionalDataFormat
description: NetCDF (network Common Data Form) is a set of interfaces for array-oriented data access and a freely-distributed collection of data access libraries for C, Fortran, C++, Java, and other languages. The netCDF libraries support a machine-independent format for representing scientific data. Together, the interfaces, libraries, and format support the creation, access, and sharing of scientific data.

Non modifiable parameter
type: ParameterModifiabilityType
code: 0
literal: fixed
comment: Parameter is fixed, not modifiable.

Octet
type: OctetType
code: 800
literal: octet
abbreviation: octet
bits: 8
bytes: 1
c name: Byte
encoding: OCTET Encoding
id: T002-01
max inclusive: 255
min inclusive: 0
rdfs datatype: byte
signedness: Unsigned

Off
type: OnOffStateType
code: 0
literal: off

Off
type: OnOffState
code: 0
literal: off

On
type: OnOffStateType
code: 1
literal: on

On
type: OnOffState
code: 0
literal: on

OCTET Encoding
type: BooleanEncodingType
type: ByteEncodingType
bytes: 1

One means off
type: OnOffStateType
literal: off
inverted: true

Positive Big Integer
type: PositiveBigIntegerType
literal: PI64
abbreviation: PI64
bits: 64
bytes: 8
max inclusive: 2^{64}-1
min inclusive: 1
my SQL name: BIGINT
rdfs datatype: unsignedLong
signedness: Unsigned

Unsigned Long Integer
type: PositiveIntegerType
literal: PI32
abbreviation: UI32
bits: 32
bytes: 4
encoding: Unsigned Integer Encoding
max inclusive: 2^{32}-1
min inclusive: 1
my SQL name: INT
rdfs datatype: unsignedInt
signedness: Unsigned

Pad with any
type: PaddingType
description: Pad with either a one or a zero. In other words, this is the "don't care" option.
literal: none

Pad with ones
type: PaddingType
description: Pad unused bits of a field with a one.
literal: ones

Pad with zeros
type: PaddingType
description: Pad unused bits of a field with a zero.
literal: zeros

Partially Ordered
type: OrderedType
literal: partial
plain text description: Partial ordered structure.

Pointer
type: ReferenceDatatype
description: A pointer is a programming language data type whose value refers directly to (or "points to") another value stored elsewhere in the computer memory using its address. It references a value stored elsewhere in memory, and obtaining or requesting the value to which a pointer refers is called dereferencing the pointer. A pointer is a simple implementation of the general reference data type. Pointers to data improve performance for repetitive operations such as traversing string and tree structures. While "pointer" has been used to refer to references in general, it more properly applies to data structures whose interface explicitly allows the pointer to be manipulated as a memory address.

Positive X
type: AxialOrientationType
description: The axis that is in the positive X direction.
code: 4
literal: positiveX

Positive Y
type: AxialOrientationType
description: The axis that is in the positive Y direction.
code: 5
literal: positiveY

Positive Z
type: AxialOrientationType
description: The axis that is in the positive Z direction.
code: 6
literal: positiveZ

Quaternion Vector - double precision
type: Vector
description: This vector type is intended to hold the (real-valued) coefficients to a quaternion number. That is, if $V=[a,b,c,d]$ is a vector of type QUATERNION-VECTOR, then the proper interpretation of this vector is with respect to the basis elements $1,i,j,k$ of the quaternion algebra. Specifically, the V corresponds to the quaternion $v = a*1 + b*i + c*j + d*k$. Note that for most computations, the quaternion basis elements will be replaced with their 4 X 4 dimensional matrix representations, which are elements of type QuaternionBasisMatrix. In this case, the resulting quaternion will be a 4 X 4 dimensional matrix of the form: a b c d -b a -d c -c d a -b -d -c b a
code: 340
datatype: Double Precision Real
dimensionality: 4
dimensions: 4

Relative Date And Time
type: DateStringType
description: Days and time relative to some Epoch
code: 76
literal: reldate
dimensionality: 1
id: T004-08

Real number binary base
type: RealNumberType
description: A rational number can be expressed in the form m*b^e, where m (the mantissa), b (the base), and e (the exponent) are integers. In this case b is chosen to be 2, and then the values of m and e are determined given this choice of base.

Real number decminal base
type: RealNumberType
description: A rational number can be expressed in the form m*b^e, where m (the mantissa), b (the base), and e (the exponent) are integers. In this case b is chosen to be 10, and then the values of m and e are determined given this choice of base.

Earth Mean Equator and Prime Meridian
type: RotatingReferenceFrame
description: A rotating reference frame is a coordinate system that rotates relative to an inertial (non-accelerating) reference frame. It is often used in physics, engineering, and mechanics to analyze motion from the perspective of an observer within the rotating frame. A rotating reference frame is non-inertial because it experiences angular acceleration or constant angular velocity relative to an inertial frame. This requires the inclusion of fictitious forces (e.g., centrifugal and Coriolis forces) when applying Newton's laws of motion. Earth can be treated as a rotating reference frame to account for the Coriolis effect, which affects weather patterns and ocean currents. Analysis of systems like rotating machinery, merry-go-rounds, or gyroscopes often involves rotating reference frames. In astronomy it is used to simplify calculations in celestial mechanics by considering rotating planetary orbits. To relate observations in the rotating frame to an inertial frame, one must account for the angular velocity vector and apply transformations like: $$\vec{F}{\text{inertial}} = \vec{F}{\text{rotating}} - 2m (\vec{\omega} \times \vec{v}) - m \vec{\omega} \times (\vec{\omega} \times \vec{r})$$ where $\vec{\omega}$ is the angular velocity, $\vec{v}$ is velocity in the rotating frame, and $\vec{r}$ is the position vector.
literal: EMEPM
frame type: Non-rotating Frame Type
id: T110-07
realization: This frame is realized from the ICRF, precessed and rotated according to the formulae in IAU2000.
x axis definition: The intersection of the prime meridian and the rotation equator of the Earth, in the ICRF and as a function of time.
y axis definition: Completes a standard, right-handed coordinate frame.
z axis definition: The mean rotation pole of the Earth, in the ICRF and as a function of time.

Earth-Moon Rotating
type: RotatingReferenceFrame
description: In this coordinate frame, the two collinear Lagrange points LL_1 and LL_2 (sometimes called Libration points) both lie along the positive X-axis approximately 60000 kilometers from the Moon. The LL_1 point lies on the X-axis between the Moon and the Earth and the LL_2 point lies on the X-axis on the other side of the Moon away from the Earth. See [Roncoli2005] for more information about Lagrange points.
code: 20
literal: EM-ROT
frame type: Rotating Frame Type
id: T110-08
x axis definition: Points in the direction of the vector from the Earth to the Moon.
y axis definition: Completes a standard, right-handed coordinate frame.
z axis definition: Points in the direction of the instantaneous orbit normal of the Moon about the Earth.
definition: Earth-Moon Rotating Coordinate System

International Celestial Reference Frame
type: ReferenceFrame
description: The ICRF is the best-determined and most stable reference frame and is the “root” frame—other reference frames are often given with respect to the ICRF. The vehicle-centered, EME2000 coordinate system is useful for vehicle attitude determination since the positions of stars in star catalogs used with star trackers, and other celestial sensors are generally expressed using the EME2000 coordinate frame. However, caution must be exercised here since the EME2000 frames realized in the past by various star catalogs (such as FK5) and ephemerides (such as DE205) were actually slightly different frames, because estimates of the actual location EME2000 changed with improvements in models and new data. For this reason the ICRF is the recommended standard.
literal: ICRF
exact match: International celestial reference frame
frame type: Non-rotating Frame Type
id: T110-06
realization: The International Celestial Reference Frame (ICRF) was defined in 1995 with locations given for 22 quasars and other bright radio objects. This definition was extended by the addition of more sources in 2000. See Reference 8 for further information.
x axis definition: Defined as the cross product of the Z-axis (as defined above) and the Earth mean orbit pole of J2000 (i.e. the ecliptic pole of J2000). The X-axis of this coordinate frame is the Earth vernal equinox of J2000.
y axis definition: Completes a standard, right-handed coordinate frame.
z axis definition: Defined as the pole vector of the Earth Mean Equator of J2000 (where J2000 = Julian date 2451545.0 TDB (Barycentric Dynamical Time)).
alternative label: Earth Mean Equator and Equinox of J2000

International Terrestrial Reference Frame
type: RotatingReferenceFrame
description: At current levels of accuracy and precision the location of the ITRF at any point in time with respect to the ICRF cannot be predicted because the Earth (and its weather!) are not modeled that accurately. The location of the true pole depends on modeling precession and nutation and then measuring the actual rotation pole relative to the modeled pole with respect to both the ITRF and the ICRF. One can use either the NASA Deep Space Network’s models and file of pole locations, which also includes timing information to tell where the prime meridian was OR one can use the IERS models and file of pole locations and timing called the Earth Orientation Parameters (EOP) file BUT NOT BOTH, e.g., do not use the IERS EOP with the DSN models for precession and nutation. The IERS information is more publicly available and is recommended. See Reference 8 for more information, including the relationships between the various ITRF frames.
literal: ITRF
exact match: Earth True Equator and Prime Meridian Body Fixed
frame type: Rotating Frame Type
id: T110-09
realization: The International Terrestrial Reference Frame (ITRF) is realized by the locations of a set of points or stations on a tide-free Earth. As measurements and models have improved or changed, these locations have been changed also and the ITRF has moved slightly with respect to the physical Earth every few years; ITRF93 is recommended.
x axis definition: The intersection of the prime meridian and the rotation equator of the Earth.
y axis definition: Completes a standard, right-handed coordinate frame.
z axis definition: The rotation pole of the Earth.

Lunar Mean Earth Body-Fixed
type: RotatingReferenceFrame
description: Lunar body-fixed coordinate frame aligned with the rotation axis of the Moon. The location of the LMEBF is a fixed rotation from the LPABF given in [Williams96] as: “The three rotations (in arcseconds) from Principal (P) to Mean (M) axes are: M = R_1(-0.15') R_2(-79.12') R_3(-66.48') P." Historical data and surface maps are given in this frame.
code: 40
literal: LMEBF
frame type: Rotating Frame Type
id: T110-10
realization: This is realized by the locations of the three Apollo and one Lunar laser ranging retroreflectors
x axis definition: Points in the direction of the Moon’s historical prime meridian (mean direction toward Earth).
y axis definition: Completes a standard, right-handed coordinate frame.
z axis definition: Points in the direction of the Moon’s North rotation pole (mean rotation axis).
comment: Reference: “Lunar moments, tides, orientation, and coordinate frames,” J. G. Williams, X. X. Newhall, and J. O. Dickey, Planet. Space Sci. 44:1077-1080, 1996.
definition: Lunar Mean Earth Body Fixed Coordinate System

Lunar Principal Axis Body-Fixed
type: RotatingReferenceFrame
description: Lunar body-fixed coordinate frame aligned with the principal axes of the Moon. The location of the LPABF in the ICRF should be solved for in conjunction with solving for the Moon’s motion in space. Lunar gravity fields are defined in this frame. Finding the principal axes depends on solving for the dynamics of the Moon's orientation, which must be done in conjunction with solving for its motion in space, though the Moon's motion in space can also be solved for independently. The terms “north pole” and “prime meridian” are loosely used for the Z and X axes respectively of both this and the Lunar Mean Earth frames.
code: 42
literal: LPABF
frame type: Rotating Frame Type
id: T110-11
realization: This is a fixed rotation from LMEBF
x axis definition: Points in the direction of the Moon's prime meridian principal axis (minimum moment of inertia).
y axis definition: Completes a standard, right-handed coordinate frame.
z axis definition: Points in the direction of the Moon's North pole principal axis (maximum moment of inertia).

Local Vertical Curvilinear
type: RotatingReferenceFrame
description: Since this coordinate system is non-Euclidean, the axes are not defined by vectors but are lines and circles in space through an origin at a vehicle in orbit around a central body.
literal: LVC
frame type: Non-rotating Frame Type
id: T110-12
realization: Defined by the position and velocity vectors associated with a vehicle and thus directly related to the coordinate system in which those vectors are expressed.
x axis definition: Defined as the circle that intersects the vehicle center-of-mass, is centered on the central body center, and lies in the vehicle orbit plane, positive in the direction of motion.
x coordinate definition: Defined as the distance on C between the radial projection of P onto C and the Y-axis; this is taken to be positive if P is on the same side from the Y-Z plane as the vehicle velocity vector points and negative otherwise. Equivalently, if we let θ be the centralbody-centered angle from the vehicle to the projection of P onto the orbit plane (measured positively in a right-handed sense with respect to the vehicle orbit angular momentum), then the xcoordinate of the point is θ (in radians) times the radius of the vehicle. Note that the LVC x-coordinate is arbitrary for P located on N.
y axis definition: Defined as the line that intersects the vehicle center-of-mass and is normal to the vehicle orbit plane, positive opposite the direction of the orbit angular momentum vector (thus completing a right-handed coordinate system).
y coordinate definition: Defined as the distance from the orbit plane, positive on the side opposite the angular momentum direction.
z axis definition: Defined as the line through the vehicle center-of-mass and the central body center, positive toward the central body center.
z coordinate definition: Defined as the distance from the central body center to the vehicle center-of-mass minus the distance between P and N; equivalently, the radius of C minus the radius of the projection of P onto the vehicle orbit plane.

Local Vertical Local Horizontal
type: RotatingReferenceFrame
literal: LVLH
frame type: Rotating Frame Type
id: T110-13
realization: Defined by the position and velocity vectors associated with a Relationships: vehicle and thus directly related to the coordinate system in which those vectors are expressed.
x axis definition: Defined as the circle that intersects the vehicle center-of-mass, is centered on the central body center, and lies in the vehicle orbit plane, positive in the direction of motion.
y axis definition: Completes a standard, right-handed coordinate frame and is positive in the direction of vehicle motion.
z axis definition: Defined as a line that lies along the radius vector from the central body center to the vehicle center-of-mass and is positive toward the central body center.

Mars Mean Equator and Prime Meridian Body-Fixed
type: RotatingReferenceFrame
description: Mars body-fixed coordinate frame with the Mars North pole and prime meridian directions defined by the IAU/IAG [@Seidelmann:2000].
code: 52
literal: MMEPMBF
frame type: Rotating Frame Type
id: T110-14
definition: Mars Mean Equator And Prime Meridian Body-Fixed Coordinate System

Sun-Earth Rotating
type: RotatingReferenceFrame
description: In this coordinate frame, the two collinear Lagrange points EL_1 and EL_2 (sometimes called Libration points) both lie along the positive X-axis approximately 1.5 million kilometers from the Earth. The EL_1 point lies on the X-axis between the Earth and the Sun and the EL_2 point lies on the X-axis on the other side of the Earth away from the Sun. See [Roncoli2005] for more information about Lagrange points.
code: 92
literal: SE-ROT
frame type: Rotating Frame Type
id: T110-15
informative reference: Roncoli2005
x axis definition: Points in the direction of the vector from the Sun to the Earth.
y axis definition: Completes a standard, right-handed coordinate frame.
z axis definition: Points in the direction of the instantaneous orbit normal of the Earth about the Sun.

Roncoli2005
type: Citation
description: "Lunar Constants and Models Document”, R. Roncoli, JPL D-32296, September 23, 2005, http://ssd.jpl.nasa.gov/?lunar_doc.
url: http://ssd.jpl.nasa.gov/

Signed Big Integer
type: SignedBigIntegerType
description: The Signed Big Integer, (long in Java) data type is a 64-bit signed two's complement integer. It has a minimum value of -9,223,372,036,854,775,808 and a maximum value of 9,223,372,036,854,775,807 (inclusive). Use this data type when you need a range of values wider than those provided by int.
code: 109
literal: SI64
was influenced by: datatypes.html
was influenced by: stdtypes.html
was influenced by: http://msdn.microsoft.com/en-us/library/4xwz0t37(v=vs.71).aspx
was influenced by: int16.html
abbreviation: SI64
bits: 64
bytes: 8
encoding: Long Unsigned Integer Encoding
id: T002-02
java name: long
matlab name: int64
max inclusive: 2^{63}-1
min inclusive: -2^{63}
my SQL name: BIGINT
protocol buffers name: int64
rdfs datatype: long
signedness: Signed

Signed Integer
type: SignedIntegerType
description: A Signed Integer or 'short' data type is a 16-bit signed two's complement integer. It has a minimum value of -32,768 and a maximum (inclusive) value of 32,767. As with byte, the same guidelines apply: you can use a short to save memory in large arrays, in situations where the memory savings actually matters.
code: 105
literal: SI16
was influenced by: datatypes.html
was influenced by: stdtypes.html
was influenced by: http://msdn.microsoft.com/en-us/library/4xwz0t37(v=vs.71).aspx
was influenced by: int16.html
abbreviation: SI16
ansi SQL name: SMALLINT
bits: 16
bytes: 2
encoding: Short Signed Integer Encoding
id: T002-03
java name: short
js name: short
matlab name: int16
max inclusive: 32767
microsoft SQL server name: smallint
min inclusive: -32767
my SQL name: SMALLINT
rdfs datatype: short

Signed Long Integer
type: SignedLongIntegerType
description: A Signed Long Integer is a 32 bit signed integer in 2's complement form. It has a minimum value of -2,147,483,648 and a maximum value of 2,147,483,647 (inclusive). For integral values, this data type is generally the default choice unless there is a reason (like the above) to choose something else. This data type will most likely be large enough for the numbers a program will use. If a wider range of values is needed use long instead.
literal: SI32
was influenced by: datatypes.html
was influenced by: stdtypes.html
was influenced by: http://msdn.microsoft.com/en-us/library/4xwz0t37(v=vs.71).aspx
abbreviation: SI32
ansi SQL name: INTEGER
bits: 32
bytes: 4
c name: int
id: T002-04
java name: int
js name: int
matlab name: int32
max inclusive: 2^{31}-1
microsoft SQL server name: integer
min inclusive: -2^{31}
my SQL name: INT
odbc name: SQL_INTEGER
ole DB name: DBTYPE_I4
oracle SQL name: NUMBER(10)
protocol buffers name: int32
rdfs datatype: int
signedness: Signed

Signed Medium Integer
type: SignedMediumIntegerType
was influenced by: integer-types.html
abbreviation: SI24
bits: 24
bytes: 3
max inclusive: 8388607
min inclusive: -8388608
my SQL name: MEDIUMINT

Signed Short Integer
type: SignedShortIntegerType
description: Unsigned 8 bit integer.
code: 103
literal: SI8
abbreviation: SI8
ansi SQL name: NUMERIC(3,0)
bits: 8
bytes: 1
encoding: OCTET Encoding
id: T002-06
max inclusive: 127
microsoft SQL server name: tinyint
min inclusive: -127
my SQL name: TINYINT
odbc name: SQL_TINYINT
ole DB name: DBTYPE_I1
rdfs datatype: byte

String
type: StringType
description: A String is an ordered list of characters. Typically the characters are UTF-8 characters.
literal: string
dimensionality: 1
member datatype: CHAR
protocol buffers name: string
rdfs datatype: string

Seidelmann2000
type: Citation
description: “Report of the IAU/IAG Working Group on Cartographic Coordinates and Rotational Elements of the Planets and Satellites: 2000”, P.K. Seidelmann, V. K. Abalakin, M. Bursa, M. E. Davies, C. DeBergh, J. H. Lieske, J. Oberst, J. L. Simon, E. M. Standish, P. Stooke, and P. C. Thomas, Celestial Mechanics and Dynamical Astronomy 82: 83-110, 2002 (http://springerlink.metapress.com, follow the links from “Browse by Online Libraries (subject areas)”, then “Physics and Astronomy”, then “Celestial Mechanics and Dynamical Astronomy”, then “Volume 82 - Number 1/January 2002”, then follow the links to download the paper.

Short Signed Integer Encoding
type: IntegerEncodingType
bytes: 2

Short Unsigned Integer Encoding
type: BooleanEncodingType
type: IntegerEncodingType
bytes: 2

Signed
type: SignednessType
literal: signed

Signed Integer Encoding
type: IntegerEncodingType
bytes: 4

Single Precision Real Encoding
type: FloatingPointEncodingType
bytes: 32

System modifiable parameter
type: ParameterModifiabilityType
code: 1
literal: system
comment: Parameter is modifiable by a (computer) system.

Earth-Centered Earth-Moon Rotating Coordinate System
type: ThreeBodyRotatingCoordinateSystem
code: 20
literal: EM-ROT
coordinate center: Earth-centered Coordinate System Type
id: TTBRCS-01
reference frame: Earth-Moon Rotating

Earth-Centered Sun Earth Rotating Coordinate System
type: ThreeBodyRotatingCoordinateSystem
code: 92
literal: SE-ROT
coordinate center: Earth-centered Coordinate System Type
id: TTBRCS-02
reference frame: Sun-Earth Rotating
definition: Earth-Centered Sun Earth Rotating Coordinate System

Moon-Centered Earth-Moon Rotating Coordinate System
type: ThreeBodyRotatingCoordinateSystem
code: 20
literal: EM-ROT
coordinate center: Moon-centered Coordinate System Type
id: TTBRCS-03
reference frame: Earth-Moon Rotating

Sun-Centered Sun Earth Rotating Coordinate System
type: ThreeBodyRotatingCoordinateSystem
code: 92
literal: SE-ROT
coordinate center: Sun-centered Coordinate System Type
id: TTBRCS-04
reference frame: Sun-Earth Rotating
definition: Sun-Centered Sun Earth Rotating Coordinate System

TIME
type: TimeStringType
description: Time in hh:mm:ss[Z|(+|-)hh:mm]format.
code: 68
literal: time
dimensionality: 1
id: T004-12
rdfs datatype: time

True
type: BooleanTypeEnumeratedValue
literal: true

TYPE-MATRIX-4by4-FLOATDP
type: TypeList

Totally Ordered
type: OrderedType
literal: total
plain text description: Totally ordered structure.

true
type: BooleanStateType
code: 1
literal: true

UNARY-FUNCTION
type: FunctionDatatype
description: This type identifies functions that have exactly one argument.
function arity: 1

Unsigned Big Integer
type: UnsignedBigIntegerType
code: 117
literal: UI64
abbreviation: UI64
bits: 64
bytes: 8
id: T002-08
max inclusive: 2^{64}-1
min inclusive: 0
my SQL name: BIGINT
rdfs datatype: unsignedLong
signedness: Unsigned

Unsigned Integer
type: UnsignedIntegerType
description: An unsigned 16-bit integer in the range 0 to 65,535
code: 113
literal: UI16
abbreviation: UI16
bits: 16
id: T002-09
max inclusive: 65535
microsoft SQL server name: smallint
min inclusive: 0
my SQL name: SMALLINT
rdfs datatype: unsignedShort
signedness: Unsigned

Unsigned Long Integer
type: UnsignedLongIntegerType
code: 115
literal: UI32
abbreviation: UI32
bits: 32
bytes: 4
encoding: Unsigned Integer Encoding
id: T002-10
max inclusive: 2^{32}-1
min inclusive: 0
my SQL name: INT
rdfs datatype: unsignedInt
signedness: Unsigned

Unsigned Medium Integer
type: UnsignedMediumIntegerType
was influenced by: integer-types.html
abbreviation: UI24
bits: 24
bytes: 3
max inclusive: 8388607
min inclusive: -8388608
my SQL name: MEDIUMINT
signedness: Unsigned

Unsigned Short Integer
type: OctetType
code: 111
literal: UI8
was influenced by: http://msdn.microsoft.com/en-us/library/aa275635(v=sql.80).aspx
abbreviation: UI8
bits: 8
bytes: 1
id: T002-13
max inclusive: 255
microsoft SQL server name: tinyint
min inclusive: 0
ole DB name: DBTYPE_UI1
rdfs datatype: unsignedByte
signedness: Unsigned

UTC Date Time
type: DateStringType
description: UTC is the time-scale maintained by the BIPM, with assistance from the IERS, which forms the basis of a coordinated dissemination of standard frequencies and time signals. It corresponds exactly in rate with the international reference scale of atomic time (TAI) but differs from it by an integer number of seconds. TAI, based on the second (SI), as realized on the rotating geoid, is formed by the BIPM on the basis of clock data supplied by cooperating establishments. It is in the form of a continuous scale, e.g. in days, hours, minutes and seconds from the origin 1 January, 1958 (adopted by the CGPM 1971). UTC date times are expressed as "YYYY-MM-DDThh:mm:ss[.dd]" or "YYYY-DDDThh:mm:ss[.dd]", where 'YYYY' is the year, 'MM' is the two-digit month, 'DD' is the two-digit day, 'DDD' is the three digit day of year, 'T' is constant, 'hh:mm:ss[.dd]' is the UTC time in hours, minutes, seconds, and optional fractional seconds. As many 'd' characters to the right of the period as required may be used to obtain the required precision. All fields require leading zeros.
code: 78
literal: utc-date
dimensionality: 1
exact match: Date Time
id: T004-13
rdfs datatype: dateTime

UTC DAY TIME
type: DateStringType
description: UTC day time is expressed as "YYYY-DDDThh:mm:ss.ddZ", where each character is an ASCII character using one octet with the following meanings: YYYY = Year in four-character subfield with values 0001-9999, DDD = Day of year in three-character subfield with values 001-365 or -366, T = Calendar-Time separator, hh = Hour in two-character subfield with values 00-23, mm = Minute in two-character subfield with values 00-59, ss = Second in two-character subfield with values 00-59 (-58 or -60 during leap seconds), dd = Decimal fraction of second in one- to n-character subfield, each d has values 0-9, and Z = time code terminator (optional)"
code: 79
literal: utc-dayTime
dimensionality: 1
id: T004-14
rdfs datatype: UTC Day time

UTC Day time
type: Datatype
description: YYYY-DDDThh:mm:ss.ddZ, where each character is an ASCII character using one octet with the following meanings: YYYY = Year in four-character subfield with values 0001-9999, DDD = Day of year in three-character subfield with values 001-365 or -366, T = Calendar-Time separator, hh = Hour in two-character subfield with values 00-23, mm = Minute in two-character subfield with values 00-59, ss = Second in two-character subfield with values 00-59 (-58 or -60 during leap seconds), dd = Decimal fraction of second in one- to n-character subfield, each d has values 0-9, and Z = time code terminator (optional)
comment: [0-9]{4}\\-[0-9]{3}T[0-9]{2}:[0-9]{2}:[0-9]{2}\\.[0-9]{2}Z?
subclass of: string

UTF16 CHAR
type: CharacterType
code: 150
literal: utf16
bits: 16
bytes: 2
id: T001-04
rdfs datatype: short

UTF16 String
type: StringUTF16
literal: utf16
dimensionality: 1
encoding: UTF-16 String
member datatype: UTF16 CHAR
rdfs datatype: string

UTF-16 String
type: StringEncodingType

UTF8 CHAR
type: CharacterType
code: 122
literal: utf8
bits: 8
bytes: 1
id: T001-05
rdfs datatype: byte

UTF8 String
type: StringUTF8
description: String consisting of UTF-8 characters
literal: utf8
dimensionality: 1
encoding: UTF-8 Encoding
member datatype: UTF8 CHAR
rdfs datatype: string

UTF-8 Encoding
type: StringEncodingType

Unordered
type: OrderedType
literal: unordered
plain text description: Unordered structure.

Unsigned
type: SignednessType
literal: unsigned

Unsigned Integer Encoding
type: IntegerEncodingType
bytes: 4

User modifiable parameter
type: ParameterModifiabilityType
code: 2
literal: user
comment: Parameter is modifiable by a user.

Vehicle centered local vertical curvilinear coordinate system
type: LocalCoordinateSystem
type: VehicleCoordinateSystem
code: 30
literal: VC-LVC
coordinate center: Vehicle-centered Coordinate System Type
id: TVCS-01
reference frame: Local Vertical Curvilinear

Local vertical local horizontal coordinate system
type: LocalCoordinateSystem
type: VehicleCoordinateSystem
code: 32
literal: LVLH
coordinate center: Vehicle-centered Coordinate System Type
id: TVCS-02
definition: Local Vertical Local Horizontal Coordinate System

Dry
type: WetDryState
code: 2
literal: dry

Wet
type: WetDryState
code: 1
literal: wet

Word aligned
type: AlignmentType
description: Alignment of a field at a word boundary, that is 2 bytes.

Year Day Time
type: DateStringType
code: 215
literal: YDT
dimensionality: 1
id: T004-16
rdfs datatype: string

Yes
type: YesNoType
literal: Y

Yes
type: YesNoType
literal: Y

negative
type: Polarity
code: 1
literal: negative

positive
type: Polarity
code: 2
literal: positive

QUDT Datatypes Version 3.2Vocabulary
type: GraphMetaData
contributor: Steve Ray
created: 2026-03-16T16:25:54.850+00:00
creator: Ralph Hodgson
description: The QUDT 'Datatype' vocabulary is a specification of scalar and structured data types. Scalar data types are defined for all the commonly encountered forms of numbers, characters and booleans, with their representations in a number of vendor and industry specific technologies. Structured data types cover arrays, lists, trees and many other forms of composite data elements. Specification of coordinate systems is also covered.
modified: 2026-03-25T12:57:16Z
rights: The QUDT Ontologies are issued under a Creative Commons Attribution 4.0 International License (CC BY 4.0), available at https://creativecommons.org/licenses/by/4.0/. Attribution should be made to QUDT.org
subject: Datatypes
label: QUDT Vocabulary for Datatypes - Version 3.2.0
graph title: QUDT Datatypes Version 3.2.0
has graph role: VocabularyGraph
intent: Provides a vocabulary of datatypes for both human and machine use
is metadata for: QUDT Vocabulary of Datatypes v3.2.0
latest published version: https://qudt.org/doc/2026/03/DOC_VOCAB-DATATYPES.html
name: QUDT
namespace: http://qudt.org/schema/qudt/
namespace prefix: qudt
owner: QUDT.ORG
title: QUDT Vocabulary for Datatypes - Version 3.2.0
turtle file URL: QUDT Vocabulary of Datatypes v3.2.0
uses non imported resource: abstract
uses non imported resource: created
uses non imported resource: creator
uses non imported resource: modified
uses non imported resource: rights
uses non imported resource: title
uses non imported resource: QUDT-Attribution
with attribution to: QUDT-Attribution