Transformation definitions bundled with the software should have same name, method name,
defining parameters and parameter values as in EPSG Dataset. See current version of the EPSG Dataset.
The values of the parameters should be correct to at least 10 significant figures.
Transformations missing from the software or at variance with those in the EPSG Dataset should be reported.
Usage example
in order to specify their factories and run the tests in a JUnit framework,
implementers can define a subclass in their own test suite as in the example below:
public class MyTest extends Test2211 {
public MyTest() {
super(new MyCoordinateOperationAuthorityFactory());
}
}
Returns the transformation instance to be tested. When this method is invoked for the first time, it creates the
transformation to test by invoking the CoordinateOperationAuthorityFactory.createCoordinateOperation(String)
method with the current Series2000.code value in argument. The created object is then cached and returned in all
subsequent invocations of this method.