How do I create a custom coordinate reference system (CRS)?
A coordinate reference system (CRS) the relationship between Cartesian and Geodetic coordinates. Insight uses these relationship to transform coordinates accurately.
Insight includes thousands of CRS definitions, available through the CRS selection table (see the Select a project CRS section in Creating a Project or Configuring project CRS section in Configure a Project).
The CRS definitions are sourced from the well regarded Spatial Reference Database: http://spatialreference.org.
We make efforts to update the list on a regulatr basis, but reference systems are created and updated to better server different areas. In cases where a specific CRS is not available, a custom one can be created.
Custom CRS in Insight
Custom CRS definitions must be stored in a file named, "customcrs.txt" and placed in the project directory.
The file contains projection and transformation parameters to define one (or more) coordinate reference systems.
Insight uses the Proj4 CRS definition format. Full details about Proj4 definition can be found here: https://github.com/OSGeo/proj.4/wiki/GenParms.
This example of an Insight customcrs.txt file includes:
- a comment describing the transformation (starting with '#'), and
- a single line defining the CRS.
# custom UTM zone with CM=18E <99999> +proj=tmerc +ellps=WGS84 +datum=WGS84 +units=m +no_defs +lon_0=18 +x_0=500000 +y_0=0 +k_0=0.9996
These example parameters define a transformation between UTM Cartesian Coordinates (with a Central Meridian at 18E) and WGS84 Geodetic Coordinates.
The parameters above are:
- # = The name of your custom CRS (this is the name that will be displayed in the CRS selection table)
- <99999> = This number is a unique identifier for the CRS. Use 99999, 99998, etc. to avoid conflict with existing CRS numbers
- +proj = Projection name
- +ellps = Ellipsoid name
- +datum = Datum name
- +units = meters, US survey feet, etc.
- +no_defs = Do not use the proj_def.dat defaults file
- +lon_0 = Central meridian - defines the origin of the x-coordinates
- +x_0 = False easting
- +y_0 = False northing
- +k_0 = Scale factor
Once created, save the customcrs.txt file in the Insight project directory. The custom CRS will be listed in the CRS selection table in Insight.
Other parameters and their required syntax can be found in the Proj4 general parameters website: https://github.com/OSGeo/proj.4/wiki/GenParms.
Multiple Custom CRS Definitions
Multiple custom CRS definitions can be included in the customcrs.txt file. For example:
# custom UTM zone with CM=18E <99999> +proj=tmerc +ellps=WGS84 +datum=WGS84 +units=m +no_defs +lon_0=18 +x_0=500000 +y_0=0 +k_0=0.9996 # custom Myanmar CRS <99998> +proj=tmerc +ellps=evrstSS +units=m +no_defs +lon_0=93 +x_0=500000 +y_0=0 +k_0=0.9996 +towgs84=246.632,784.833,276.923
Note: Remember to use a unique identifier for each custom CRS in the file and no empty line between each parameters.
Check your results!
Because CRS transformations have such a large impact on your data, we strongly recommend carefully checking all custom CRS transformations. To do this, use points in the custom CRS that have known, correct locations in another CRS, convert them and compare the results. Contact firstname.lastname@example.org for details on how to do this.
If you are unsure about creating custom CRS definitions, please send the details to email@example.com and we will create a customcrs.txt file for you.