Parse several types of ITRF specifications
Several ways to specify ITRF versions are used in several contexts.
- some contexts allow years on two digits (CCSDS ODM before version 3, CCSDS ADM, CCSDS TDM, Orekit
itrf-version.conf
) - all contexts allow years on 4 digits, some require them
- some contexts use "-" as separator (CCSDS, Orekit
itrf-version.conf
) - some contexts use " " as separator (comments in IERS bulletins B)
- some contexts don't use any separators (CCSDS after ITRF2000)
- some contexts would be simpler if "_" was allowed as a separator (parsing from enumerates
name()
output) - some contexts allow lower case (Orekit
itrf-version.conf
)
It would be simpler if Orekit allowed all these variations to be used, mainly in itrf-version.conf
and in CCSDS parsing.
For consistency, the constants of the various enums (org.orekit.frames.ITRFVersion
, org.orekit.frames.HelmertTransformation.Predefined
, org.orekit.files.ccsds.definitions.CelestialBodyFrame
) should all use 4 digits years instead of mixing two digits and four digits.