Coordinate Reference System

Data Stores will try and infer the Coordinate Reference System (CRS) from the data.

Some Data Stores provide the ability to override the inferred CRS. Overriding will not re-project the data, it will simply provide information about the current spatial reference system.

You can check the CRS of the data by hovering over the icon next to the geometry column of one of the tables in the Data Store’s Read and Commit and Copy To tabs. The CRS may need to be overridden because:

• Sometimes, the source Data Store does not provide any information about its CRS.

• If the data is to be used with, or written to, another type of Data Store. In this case it is useful to be able to define the CRS in the encoding used by the other Data Store.

1Integrate uses the CRS to:

• Ensure that all data processed by a session is using the same reference system.

• Enable the writer to correctly specify their CRS.

Understanding CRS codes

The CRS codes provided have a number of caveats, depending on which Data Store or integration platform is being used.

• Native, FME and Oracle Data Stores all understand EPSG codes and are able to translate between the local encoding (i.e the FME CRS name or Oracle Spatial Reference Identifier (SRID) and the corresponding CRS code).

• FME, where possible, will return its own encoding with a tag of "FME" and an EPSG code.

• Native Data Stores understand only EPSG codes.

• The Oracle Data Store understands the Oracle SRID and EPSG codes.

These values are represented in NAME=VALUE pairs. For example:

• For a Spatial Reference Identifier (SRID) would be in the form SRID=81989

• For an EPSG code, it would be in the form EPSG=27700