|
Well-known text representation of coordinate reference systems
Well-known text representation of coordinate reference systems (WKT or WKT-CRS) is a text markup language for representing spatial reference systems and transformations between spatial reference systems. The formats were originally defined by the Open Geospatial Consortium (OGC) and described in their Simple Feature Access[1] and Well-known text representation of coordinate reference systems[2] specifications. The current standard definition is ISO 19162:2019.[3] This supersedes ISO 19162:2015.[4] Version historyThis WKT format was initially defined by the Open Geospatial Consortium (OGC) in 1999, then extended in 2001. This format, also defined in ISO 19125-1:2004, is sometime known as "WKT 1".[5] Later, evolution of the Coordinate Reference System conceptual model, new requirements and inconsistencies in implementation of WKT 1 format between different software have encouraged the revision of that format. The updated "Well-known text representation of coordinate reference systems" standard, sometime known as "WKT 2", was adopted by the Open Geospatial Consortium in 2015.[6]: Annex E This standard is published conjointly by the International Organization for Standardization as ISO 19162:2015.[7] Confusingly, the original 2015 "WKT 2" standard has a version number 1 for the new, stricter WKT-CRS specification. A newer revision called WKT-CRS 2 was published in 2018, with the ISO version being ISO 19162:2019.[8] Backward compatibilityA software capable to read coordinate reference systems in WKT 2 format can also read many (but not all) equivalent systems in WKT 1 format.[9] Some caveats exist, notably the removal of the ESRI vs OGCEsri, which also participated in writing the WKT 2 specification, had a few variations on OGC's WKT 1 specification, making it stricter and contain less ambiguities. As a result, some databases differentiate between "OGC WKT" and "ESRI WKT" representations. The problem is largely resolved in WKT 2, as it is better-defined.[11] One distinction is that it does not have Coordinate reference systemsWKT can describe coordinate reference systems. For example, the WKT below describes a two-dimensional geographic coordinate reference system with a latitude axis first, then a longitude axis. The coordinate system is related to Earth by the WGS84 geodetic datum: GEODCRS["WGS 84",
DATUM["World Geodetic System 1984",
ELLIPSOID["WGS 84", 6378137, 298.257223563, LENGTHUNIT["metre", 1]]],
CS[ellipsoidal, 2],
AXIS["Latitude (lat)", north, ORDER[1]],
AXIS["Longitude (lon)", east, ORDER[2]],
ANGLEUNIT["degree", 0.0174532925199433]]
The WKT format can describe not only geographic coordinate reference systems, but also geocentric, projected, vertical, temporal and engineering ones (for example a coordinate reference system attached to a boat). The standard describes how to combine those coordinate reference systems together. Coordinate operationsA WKT format is defined to describe the operation methods and parameters used to convert or transform coordinates between two different coordinate reference systems. The WKT 1 and WKT 2 formats are incompatible regarding coordinate operations, because of differences in the modelling.[13] Below is an example of a concatenation of two WKT 1 transformation descriptions, where the Mercator projection is applied first and then an affine transform is applied on the result: CONCAT_MT[
PARAM_MT["Mercator_2SP",
PARAMETER["semi_major",6370997.0],
PARAMETER["semi_minor",6370997.0],
PARAMETER["central_meridian",180.0],
PARAMETER["false_easting",-500000.0],
PARAMETER["false_northing",-1000000.0],
PARAMETER["standard parallel 1",60.0]],
PARAM_MT["Affine",
PARAMETER["num_row",3],
PARAMETER["num_col",3],
PARAMETER["elt_0_1",1],
PARAMETER["elt_0_2",2],
PARAMETER["elt 1 2",3]]]
Below is an example of a datum shift operation in WKT 2 format. Contrarily to an equivalent description in WKT 1 format, the WKT 2 description specifies the source and target coordinate reference systems, together with the domain of validity and the accuracy (in metres) that we can expect from this operation: COORDINATEOPERATION["AGD84 to GDA94 Auslig 5m",
SOURCECRS[…full CRS definition required here but omitted for brevity…],
TARGETCRS[…full CRS definition required here but omitted for brevity…],
METHOD["Geocentric translations", ID["EPSG", 1031]],
PARAMETER["X-axis translation", -128.5, LENGTHUNIT["metre", 1]],
PARAMETER["Y-axis translation", -53.0, LENGTHUNIT["metre", 1]],
PARAMETER["Z-axis translation", 153.4, LENGTHUNIT["metre", 1]]
OPERATIONACCURACY[5],
AREA["Australia onshore"],
BBOX[-43.7, 112.85, -9.87, 153.68]]
APIs that provide support
See alsoReferences
External links |
