====== WebClient CRS Notes ======

When passing spatial data to the Orbit WebClient component, you need to provide a CRS (coordinate reference system) code that expresses how to interprete the co-ordinates.  This code can then be used by the Orbit WebClient component to correctly reference your spatial data.  

Orbit CRS codes map directly to the EPSG database of CRS codes. 

  * In-depth background on CRSs : [[technology/coordinate_systems/crs_theory]]

===== Version 10.4 =====

The 10.4 version of the API used the "EPSG:" prefix with CRS codes.

Internally all spatial data is kept in the publication CRS.  When adding WKT data, this should also be specified in the publication CRS.

  * "EPSG:4326" refers to WGS84.

===== Version 10.5 =====

Starting from 10.5 the ''EPSG:'' prefix is no longer required.  The reason for this is that the API now accepts (and expects) Orbit CRS codes which don't have the ''EPSG:'' prefix.  Since 10.5 the component also keeps all spatial data internally as WGS84.  This means that whenever spatial data is provided to the component that is not WGS84, an on-the-fly conversion takes place in the background.  If performance is key, please provide your spatial data as WGS84.

Starting from 10.5 you can also specify a dual horizontal + vertical CRS using a 'plus' sign to distinguish between both codes.

  * "4619+5613" refers to SWEREF99 with RH2000 height.