Problems with Geotransformation – VertiGIS Support

Problem

If the markups are not visible on the printout when printing with markups (e. g. dimensions, drawings).

Message in the WebOffice log file

trouble_geotransformation1

Problem cause and solution

The parameter for the date transformation MUST always be configured if a WebOffice 10.8 SP2 project, i. e. the main map service is not in WGS 1984 or based on WGS 1984

Note: Details on the definition of the transformation can be found in the chapter ArcGIS Server Ausgabe-Service.

Note: Details on configuring projections can be found in the chapter Projection.

Background

The data frame of the SynOutputService and the FeatureClasses in the fGDB are "by design" in WebOffice 10.8 SP2 always in WebMercator. These are a black box and may NOT be changed (normally).

Sample scenario

The only reason why the problem probably does not occur so frequently or irregularly in the customer system is that they have configured the date transformation on the coordinate tool, the Extract tool, the print tool or the Position Determination tool and in an emergency, WebOffice 10.8 SP2 uses these configuration elements as a fallback.

This was also the case with this exemplary scenario - here the detailed analysis

This is because no geotransformation has been entered in project "A" but it has already been entered in project "B" (because it is defined in the TOOL_GEOLOCATION, for example).

ArcGIS (Desktop, Server, Engine) internally runs a "SpatialReferenceEnvironment" as Singleton in each process, which manages the geotransformations among other things. In an operation that requires a geotransformation, i. e. reprojection of geometries or a map presentation, so-called "GeoTransformationDefaults" are retrieved from this environment and applied.

In the initial state (all components freshly loaded) is the state with regard to geotransformations:

-------------------------------------------------------------

-------------------------------------------------------------

-------------------------------------------------------------

Now in the project "A" with markup is printed. No geotransformation is configured here. The contained markup is re-projected to WebMercator, without geotransformation, i. e. wrong. Since it does not exist, the output MXD is also generated without geotransformation and exported by extensions without geotransformation. Apparently, the map representation is therefore wrong to the same extent as the previous reprojection and therefore apparently correct.

-------------------------------------------------------------

-------------------------------------------------------------

-------------------------------------------------------------

Then in project "B" will be printed. Everything seems to be right here. Projection, presentation, output.

-------------------------------------------------------------

-------------------------------------------------------------

| keine | 1676 | 1676 | 1676 | 1676 |

-------------------------------------------------------------

Reason: The geotransformation 1676 remains in the spatial environment of the extension, so the status would be after a print with "B":

-------------------------------------------------------------

-------------------------------------------------------------

| keine | 1676 | nicht vorhanden | 1676 |

-------------------------------------------------------------

Finally again a print with project "A". Since there is now a geotransformation in the extensions, we are less fortunate than with the first print, where everything seemed to be correct, because now the geotransformation is used, ONLY in the representation, not in the reprojection, --> this finally leads to a wrong representation.

-------------------------------------------------------------

-------------------------------------------------------------

-------------------------------------------------------------

Note: As of version 10.5 SP1, a corresponding warning is issued in the WebOffice log file if a date transformation is required in the project configuration but this was not configured.