Get desktop application:
View/edit binary Protocol Buffers messages
Column are top-level types in the schema
Used in:
specifies if the values are optional in the column and a present stream should be used
Used in:
1:1 Mapping of property and feature -> id and geometry
For M-Values -> 1:1 Mapping for property and vertex
The type tree is flattened in to a list via a pre-order traversal Represents a column if it is a root (top-level) type or a child of a nested type
Used in:
The complex type Geometry and the logical type BINARY have no children since there layout is implicit known. RangeMap has only one child specifying the type of the value since the key is always a vec2<double>.
Used in:
Used in:
,fixed size binary with 2 values of the same type either signed or unsigned Int8, Int32, Int64 as well as Float or Double
fixed size binary with 2 values of the same type either signed or unsigned Int8, Int32, Int64 as well as Float or Double
vec2<Int32> for the VertexBuffer stream with additional information (streams) about the topology
vec3<Int32> for the VertexBuffer stream with additional information (streams) about the topology
Used in:
Fields define nested or leaf types in the schema as part of a complex type definition
Used in:
,name and nullable are only needed in combination with a struct not for vec, list and map Map -> has the order key type, value type
Used in:
,physical type: list<UInt8>
physical type: map<vec2<double, T>> -> special data structure which can be used for a efficient representation of linear referencing
Used in:
,physical type: Int64 -> number of milliseconds since Unix epoch
physical type: Int32 -> number of days since Unix epoch
physical type: String
Used in:
Used in:
Used in:
,order left, bottom, right, top in WGS84
order longitude, latitude in WGS84