Implement missing item classes and fields for item classes

[ribose-jeffreylau]

• All items: expose aliases in common detail/edit view, remove per-item aliases  #49
• All coordinate systems: remove aliases #51
• Cartesian Coordinate System: add Aliases, Coordinate Axes; remove Description #25
• Compound CRS: remove Coordinate System #26
• All CRS: expose scope in GUI #47
• Implement Concatenated Operation #27
• Conversion: expose Coordinate Operation Method in GUI #28
• Coordinate System Axis: expose everything in edit GUI, add Minimum Value and Maximum Value, add Range Meaning #29
• Ellipsoid: make Semi Minor Axis & Inverse Flattening conditionally available if isSphere == false #30
• Ellipsoidal Coordinate System: implement #31
• Engineering CRS: add Coordinate System, Base CRS, Operation #32
• Datums: rename origin description field (?) #33
• Geodetic CRS: add Base CRS, Operation (contingent on base CRS, Conversion or Transformation) #34
• Geodetic Datum: no op #35
• Coordinate Operation Method: add formula #36
• Coordinate Operation Parameter: add Aliases; remove Description #37
• Prime Meridian: no op #38
• Projected CRS: add Base CRS, Operation #39
• Spherical Coordinate System: add Aliases, Coordinate Axes; remove Description #40
• Transformation: add Aliases, Scope, Coordinate Operation Method (and its parameters, see notes on Conversion) #41
• Unit of Measurement: add Standard Unit field, make Measure Type an enum #42
• Vertical CRS: add Datum, Coordinate System, Base CRS, Operation #43
• Vertical Coordinate System: add Aliases, Coordinate Axes; remove Description #44
• Vertical Datum: no op #45

[strogonoff]

@ribose-jeffreylau Regarding #26, can you confirm that coordinateSystem should exist on all CRS except Compound? And what did you use as reference to find out these requirements?

Also, I am already seeing vertical & horizontal CRS fields on CompoundCRS in master branch, so perhaps that’s a mistake?

[ribose-jeffreylau]

@strogonoff I based all the above requirements from the <form>s as seen in https://geodetic-staging.isotc211.org/register/geodetic/crs -> Propose New.

So, instead of coordinateSystem in Compound, it has instead horizontalCrs and verticalCrs. Notice that:

• horizontalCrs takes geodeticCrs | projectedCrs | engineeringCrs, whereas
• verticalCrs takes verticalCrs | engineeringCrs.