Harmonize angles, courses, headings

[cdmgtri]

Migrated from NIEM/NIEM-Releases#12

A lot of custom angular measurement types exist for properties with related but slightly different semantics. It may be better to create some generic types that could be reused. These types would need to support multiple representations.

This would be similar to how NIEM uses nc:DateType as the generic type for date properties. This one basic type provides consistency and reusability, and also allows for users to choose the individual representation (date, datetime, time, year, etc.) that meets their requirements.

MilOps is moving ahead with some solutions for their domain in 4.1, but recommends harmonization in Core.

[cdmgtri]

Current (as of Jul 2020)

nc:AngleMeasureType (nc:MeasureType)

• nc:AngleUnitAbstract
  • mo:AngleUnitCode ("Degrees", "Mils")

nc:AngularMeasureType (structures:ObjectType)

This type can be used with either only the degrees element as a decimal value, or broken out into the degrees, minutes, and seconds elements.

• nc:AngularDegreeValue (niem-xs:decimal)
• nc:AngularMinuteValue (allows values 0 - 60)
• nc:AngularSecondValue (allows values 0 - 60)

mo:AngularMeasureAugmentationType

• mo:AngularNATOMilValue (allows values 0 - 6400)
• nc:AngleMeasure
• mo:HorizontalAngularMeasureAbstract
  • mo:AngularMeasureCompassCode (nc:DirectionCodeType - "N", "S", "E", "W", "NE", "NNE", etc.)

mo:CourseAngleDegreesMeasureType (structures:ObjectType)

• mo:AngleDegreesMeasure (nc:AngularMeasureType)
• mo:DirectionDatumAbstract
  • mo:DirectionDatumCode (NGA codes - "geodetic", "Magnetic", "militaryGrid", "Relative")

Element mo:CourseAbstract substitution group

• mo:CourseAngleDegreesMeasure (mo:CourseAngleDegreesMeasureType)
• mo:CourseAngleMeasure (nc:AngularMeasureType)
• mo:CourseCode (nc:DirectionCodeType)
• mo:CourseValue (nc:Degree360Type)

mo:HorizontalAngularMeasureType (nc:AngularMeasureType)

• mo:DirectionDatumAbstract
  • mo:DirectionDatumCode (nga:DirectionDatumCodeType) - "geodetic", "Magnetic", "militaryGrid", "Relative"

mo:VerticalAngularMeasureType (nc:AngularMeasureType)

• nc:LocationHeightVerticalDatumAbstract
  • nc:LocationHeightVerticalDatumText
  • nga:VerticalDatumCode ("approxMeanSeaLevel", "groundLevel", "wgs84Ellipsoid", etc.)

Proposed

nc:AngleMeasureType (nc;MeasureType)

• nc:AngleRepresentation - new
  • nc:AngleValue (niem-xs:decimal) - new
  • nc:AngleDegree (nc:AngleDegreeType)
  • nc:AngleCompassCode (nc:DirectionCodeType) - "N", "S", "E", "W", etc.
  • nc:AngleDegree360Value (nc:Degree360Type) - new
  • nc:AngleDegree180Value (nc:Degree180PlusMinusType) - new
  • nc:AngleDegree90Value (nc:Degree90PlusMinusType) - new
  • mo:Angle~Angular~NATOMilValue (allows values 0 - 6400)
• nc:AngleUnitAbstract
  • mo:AngleUnitCode ("Degrees", "Mils")
• nc:AngleMeasureDatumText

nc:~AngularMeasure~AngleDegreeType (structures:ObjectType)

This type can be used with either only the degrees element as a decimal value, or broken out into the degrees, minutes, and seconds elements.

• nc:AngularDegreeValue (niem-xs:decimal)
• nc:AngularMinuteValue (allows values 0 - 60)
• nc:AngularSecondValue (allows values 0 - 60)

~mo:AngularMeasureAugmentationType~

• ~mo:AngularNATOMilValue~ (allows values 0 - 6400)
• ~nc:AngleMeasure~
• ~mo:HorizontalAngularMeasureAbstract~
  • ~mo:AngularMeasureCompassCode~ (nc:DirectionCodeType - "N", "S", "E", "W", "NE", "NNE", etc.)

~mo:CourseAngleDegreesMeasureType~ (structures:ObjectType)

• ~mo:AngleDegreesMeasure~ (nc:AngularMeasureType)
• ~mo:AngularMeasureDecimalValue~ (niem-xs:decimal)
• ~mo:DirectionDatumAbstract~
  • ~mo:DirectionDatumCode~ (NGA codes - "geodetic", "Magnetic", "militaryGrid", "Relative")

Element mo:CourseAbstract substitution group

• ~mo:CourseAngleDegreesMeasure~ (mo:CourseAngleDegreesMeasureType)
• ~mo:CourseAngleMeasure~ (nc:AngularMeasureType)
• ~mo:CourseCode~ (nc:DirectionCodeType)
• ~mo:CourseValue~ (nc:Degree360Type)

nc:DatumType (structures:ObjectType)

• nc:DatumRepresentation
  • nc:DatumText

nc:HorizontalDatumType (nc:DatumType)

• nga:HorizontalDatumCode ("geodetic", "Magnetic", "militaryGrid", "Relative")

nc:VerticalDatumType (nc:DatumType)

• nga:VerticalDatumCode ("approxMeanSeaLevel", "groundLevel", "wgs84Ellipsoid", etc.)

nc:HorizontalAngleMeasureType ~mo:HorizontalAngularMeasureType~ (nc:Angle~Angular~MeasureType)

• nc:HorizontalDatum (nc:HorizontalDatumType)

nc:VerticalAngleMeasureType ~mo:VerticalAngularMeasureType~ (nc:Angle~Angular~MeasureType)

• nc:VerticalDatum (nc:VerticalDatumType)

• nc:LocationHeightVerticalDatumAbstract

  • nc:Location~Height~VerticalDatumText
  • nga:VerticalDatumCode ("approxMeanSeaLevel", "groundLevel", "wgs84Ellipsoid", etc.)

nc:LocationHeightMeasureType (nc:LengthMeasureType)

• ~nc:LocationHeightVerticalDatumAbstractAbstract~
  • ~nc:LocationHeightVerticalDatumText~
  • ~nga:VerticalDatumCode~
• nc:LocationHeightVerticalDatum (nc:VerticalDatumType)

[cdmgtri]

(Aug 2020) The Harmonization Workgroup recommends deferring on this issue for now. There is some overlap that could be resolved, but there have been no raised problems about the current content and a better solution would likely be reached when some subject matter experts are available to participate in the refactoring.