DEFINE_GUIDCATID_CS_CoordinateSystemFactory, 0x49937f54, 0x9921, 0x11d3, 0x81, 0x64, 0x0, 0xc0, 0x4f, 0x68, 0xf, 0xff;
DEFINE_GUIDCATID_CS_CoordinateSystemAuthorityFactory, 0x49937f53, 0x9921, 0x11d3, 0x81, 0x64, 0x0, 0xc0, 0x4f, 0x68, 0xf, 0xff;
DEFINE_GUIDCATID_CT_MathTransformFactory, 0x49937f52, 0x9921, 0x11d3, 0x81, 0x64, 0x0, 0xc0, 0x4f, 0x68, 0xf, 0xff;
DEFINE_GUIDCATID_CT_CoordinateTransformationFactory, 0x2ca0a8bd, 0xca5b, 0x11d3, 0x81, 0x98, 0x0, 0xc0, 0x4f, 0x68, 0xf, 0xff;
DEFINE_GUIDCATID_CT_CoordinateTransformationAuthorityFactory, 0x2ca0a8be, 0xca5b, 0x11d3, 0x81, 0x98, 0x0, 0xc0, 0x4f, 0x68, 0xf, 0xff;
6.2 CORBA profile
The CORBA profile is specified in the attached CORBA IDL files see Appendix A: Interface
Definition Files :
CORBA .
Each package is mapped to a CORBA module of the same name. Two-dimensional arrays e.g. matrices are modeled with a sequence of sequences. All 2D
arrays in this specification should be regular, so each sub-sequence in the 2D array should have the same length.
6.3 Java profile
The Java profile is specified in the attached Java source files. Each Java package is called “org.opengis.xx” where “xx” is the two-character package prefix
in lower case. The Java source includes tagged comments. These comments were used to generate the
accompanying HTML documentation using the JavaDoc utility. In the Java profile, structures are modeled with Java classes e.g. PT_CoordinatePoint, and
interfaces are used for entities that will have many different implementations e.g. CS_ProjectedCoordinateSystem.
This specification says that structures used as return values should use “return-by-value” semantics. This means that whenever a Java method has an object return type, the
implementation should create a new Java object. Since this is not very efficient, there are also pass-by-reference versions of heavily used functions e.g. double[] transformListdouble[] ord.
Matrices are modeled with the Java type “double[][]”. Although the Java language allows ragged multi-dimensional arrays, all arrays in this specification should be regular i.e. rectangular
in 2D.
Page 17 of 117 OGC Document Number 01-009
7 Well-Known Text format
Many entities in this specification can be printed in a well-known text format. This allows objects to be stored in databases persistence, and transmitted between interoperating computer
programs. Each entity has a keyword in upper case for example,
DATUM
or
UNIT
followed by the defining, comma-delimited, parameters of the object in brackets. Some objects are composed of objects so
the result is a nested structure. Implementations are free to substitute standard brackets for square brackets [ ] and should be prepared to read both forms of brackets.
The definition for WKT is shown below using Extended Backus Naur Form EBNF. The WKT for a math transform can be used inside a fitted coordinate system, so it is shown first.
7.1 Math Transform WKT
