-- for all types currently called GMLTYPE, we need to decide what version to support here (GML, GML profile for PIDF-LO, 29.572, 33.108)
-- for simplicity of the structure, unless otherwise indicated I stole 29.572 and adapted it to things we already have defined
-- we could adjust the name accordingly or make Polygon a choice of FORMATS
-- it is also worth noting that GML supports doubles instead of integers for both uncertainty, altitude and angles, should we define our defs the same way
AngleDecimalDegrees ::= UTF8String
-- GMLPolygons support interior borders as well. Do we think we need to support this?
GMLPolygon ::= SEQUENCE
{
pointList [1] SEQUENCE (SIZE (3..15)) OF GeoPoint
}
GMLCircle ::= SEQUENCE
{
centerPoint [1] GeoPoint,
radiusMeters [2] UncertaintyMeters
}
GMLEllipse ::= SEQUENCE
{
centerPoint [1] GeoPoint,
semiMajor [2] UncertaintyMeters,
semiMinor [3] UncertaintyMeters,
orientation [4] AngleDecimalDegrees
}
-- This is not 29.572, but is closer to GML
GMLArcBand ::= SEQUENCE
{
centerPoint [1] GeoPoint,
innerRadius [2] UncertaintyMeters,
outerRadius [3] UncertaintyMeters,
startAngle [4] AngleDecimalDegrees,
openingAngle [5] AngleDecimalDegrees
}
-- This is not 29.572 but is closer to the GML profile for PIDF-LO
GMLPIDFProfileEllipsoid ::= SEQUENCE
{
centerPoint [1] GeoPoint,
semiMajor [2] UncertaintyMeters,
semiMinor [3] UncertaintyMeters,
verticalAxis [4] UncertaintyMeters,
orientation [5] AngleDecimalDegrees
}
GMLPrism ::= SEQUENCE
{
pointList [1] SEQUENCE (SIZE (3..15)) OF GeoPoint,
height [2] UncertaintyMeters
}
FixMode ::= ENUMERATED
{
unknown(0),
@@ -171,4 +232,48 @@ FixMode ::= ENUMERATED
fix3D(3)
}
MACAddress ::= OCTET STRING (SIZE(6))
-- This choice was taken from 33.128, which copied 29.572.
-- We may want to take the format from one of the other standards.
-- The specifics do not matter at this point in the discussion, but are open for comment.