Closed stansmith907 closed 6 years ago
So, should we require ellipsoidIdentifier
or all: semiMajorAxis, axisUnits, denominatorOfFlatteningRatio
?
Where does ellipsoidName
map to? How does it differ from ellipsoidIdentifier
?
So, should we require ellipsoidIdentifier or all: semiMajorAxis, axisUnits, denominatorOfFlatteningRatio?
I think it depends on if we want to write an FGDC or ISO record. FGDC requires ellipsoidName
, semiMajorAxis
, and demoninatorOfFlatteningRatio
; ISO needs only an ellipsoidIdentifier
, but will require semiMajorAxis
, axisUnits
, and demoninatorOfFlatteningRatio
if ellipsoidIdentifier
is not available.
This is part of the miss-match between FGDC and ISO that we try to accommodate. So, maybe require ellipsoidIdentifier
OR (ellipsoidName
, semiMajorAxis
, axisUnits
, and demoninatorOfFlatteningRatio
).
Where does ellipsoidName map to? How does it differ from ellipsoidIdentifier?
In the internal object it maps to geodetic.ellipsoidName. Maps to Ellipsoid_Name in FGDC and is not used in ISO, it would be part of identifier if one was specified.
Dropped datumName
and ellipsoidName
.
So the rules become:
Schema rules for geodetic: "parameters for the shape of the earth."
Rules:
Definitions:
Rules:
ellipsoidIdentifier
and thus requires all the remaining elements. ISO can handle either the identifier or the other elements when defining an ellipsoid.mdJson:
FGDC mapping:
ISO 19115-2 mapping: The ellipsoid elements map to MD_EllipsoidParameters in ISO 19115-2 which is not yet implemented. The ISO MD_ReferenceSystem classes were not added to the ISO XSD so I have no means of verifying my example is correct. Further, adding these classes to an ISO record will cause validation against the XSD to fail.
ISO 19115-3 mapping: Does not map to ISO 19115-1/3. This information was removed to ISO 19111 ( I do not have documentation at this time ).