1CS2CS(1) PROJ CS2CS(1)
2
6 cs2cs - Cartographic coordinate system filter
7
9 cs2cs [-eEfIlrstvwW [args]]
10 [[--area <name_or_code>] | [--bbox <west_long,south_lat,east_long,north_lat>]]
11 [--authority <name>] [--no-ballpark] [--accuracy <accuracy>] [--3d]
12 ([+opt[=arg] ...] [+to +opt[=arg] ...] | {source_crs} {target_crs})
13 file ...
14 where {source_crs} or {target_crs} is one of the possibilities ac‐
17 cepted by proj_create(), provided it expresses a CRS
18 • a proj-string,
20 • a WKT string,
22 • an object code (like "EPSG:4326", "urn:ogc:def:crs:EPSG::4326",
24 "urn:ogc:def:coordinateOperation:EPSG::1671"),
25 • an Object name. e.g "WGS 84", "WGS 84 / UTM zone 31N". In that
27 case as uniqueness is not guaranteed, heuristics are applied to
28 determine the appropriate best match.
29 • a OGC URN combining references for compound coordinate reference
31 systems (e.g "urn:ogc:def:crs,crs:EPSG::2393,crs:EPSG::5717" or
32 custom abbreviated syntax "EPSG:2393+5717"),
33 • a OGC URN combining references for references for projected or de‐
35 rived CRSs e.g. for Projected 3D CRS "UTM zone 31N / WGS 84 (3D)":
36 "‐
37 urn:ogc:def:crs,crs:EPSG::4979,cs:PROJ::ENh,coordinateOpera‐
38 tion:EPSG::16031" (added in 6.2)
39 • a OGC URN combining references for concatenated operations (e.g.
41 "‐
42 urn:ogc:def:coordinateOperation,coordinateOperation:EPSG::3895,co‐
43 ordinateOperation:EPSG::1618")
44 • a PROJJSON string. The jsonschema is at
46 https://proj.org/schemas/v0.4/projjson.schema.json (added in 6.2)
47 • a compound CRS made from two object names separated with " + ".
49 e.g. "WGS 84 + EGM96 height" (added in 7.1)
50 New in version 6.0.0.
52 NOTE:
55 before 7.0.1, it was needed to add +to between {source_crs} and
56 {target_crs} when adding a filename
57
59 cs2cs performs transformation between the source and destination carto‐
60 graphic coordinate reference system on a set of input points. The coor‐
61 dinate reference system transformation can include translation between
62 projected and geographic coordinates as well as the application of da‐
63 tum shifts.
64 The following control parameters can appear in any order:
66 -I Method to specify inverse translation, convert from +to coordi‐
68 nate system to the primary coordinate system defined.
69 -t<a> Where a specifies a character employed as the first character to
71 denote a control line to be passed through without processing.
72 This option applicable to ASCII input only. (# is the default
73 value).
74 -d <n> New in version 5.2.0.
76 Specify the number of decimals to round to in the output.
79 -e <string>
81 Where string is an arbitrary string to be output if an error is
82 detected during data transformations. The default value is a
83 three character string: *\t*.
84 -E Causes the input coordinates to be copied to the output line
86 prior to printing the converted values.
87 -l<[=id]>
89 List projection identifiers that can be selected with +proj.
90 cs2cs -l=id gives expanded description of projection id, e.g.
91 cs2cs -l=merc.
92 -lp List of all projection id that can be used with the +proj param‐
94 eter. Equivalent to cs2cs -l.
95 -lP Expanded description of all projections that can be used with
97 the +proj parameter.
98 -le List of all ellipsoids that can be selected with the +ellps pa‐
100 rameters.
101 -lu List of all distance units that can be selected with the +units
103 parameter.
104 -r This options reverses the order of the first two expected inputs
106 from that specified by the CRS to the opposite order. The third
107 coordinate, typically height, remains third.
108 -s This options reverses the order of the first two expected out‐
110 puts from that specified by the CRS to the opposite order. The
111 third coordinate, typically height, remains third.
112 -f <format>
114 Where format is a printf format string to control the form of
115 the output values. For inverse projections, the output will be
116 in degrees when this option is employed. If a format is speci‐
117 fied for inverse projection the output data will be in decimal
118 degrees. The default format is "%.2f" for forward projection and
119 DMS for inverse.
120 -w<n> Where n is the number of significant fractional digits to employ
122 for seconds output (when the option is not specified, -w3 is as‐
123 sumed).
124 -W<n> Where n is the number of significant fractional digits to employ
126 for seconds output. When -W is employed the fields will be con‐
127 stant width with leading zeroes. Valid range: -W0 through -W8.
128 -v Causes a listing of cartographic control parameters tested for
130 and used by the program to be printed prior to input data.
131 --area <name_or_code>
133 New in version 8.0.0.
134 Specify an area of interest to restrict the results when re‐
137 searching coordinate operations between 2 CRS. The area of in‐
138 terest can be specified either as a name (e.g "Denmark - on‐
139 shore") or a AUTHORITY:CODE (EPSG:3237)
140 This option is mutually exclusive with --bbox.
142 --bbox <west_long,south_lat,east_long,north_lat>
144 New in version 8.0.0.
145 Specify an area of interest to restrict the results when re‐
148 searching coordinate operations between 2 CRS. The area of in‐
149 terest is specified as a bounding box with geographic coordi‐
150 nates, expressed in degrees in a unspecified geographic CRS.
151 west_long and east_long should be in the [-180,180] range, and
152 south_lat and north_lat in the [-90,90]. west_long is generally
153 lower than east_long, except in the case where the area of in‐
154 terest crosses the antimeridian.
155 --no-ballpark
157 New in version 8.0.0.
158 Disallow any coordinate operation that is, or contains, a
161 Ballpark transformation
162 --accuracy <accuracy>
164 New in version 8.0.0.
165 Sets the minimum desired accuracy for candidate coordinate oper‐
168 ations.
169 --authority <name>
171 New in version 8.0.0.
172 This option can be used to restrict the authority of coordinate
175 operations looked up in the database. When not specified, coor‐
176 dinate operations from any authority will be searched, with the
177 restrictions set in the authority_to_authority_preference data‐
178 base table related to the authority of the source/target CRS
179 themselves. If authority is set to any, then coordinate opera‐
180 tions from any authority will be searched If authority is a
181 non-empty string different of any, then coordinate operations
182 will be searched only in that authority namespace (e.g EPSG).
183 This option is mutually exclusive with --bbox.
185 --3d New in version 9.1.
187 "Promote" 2D CRS(s) to their 3D version, where the vertical axis
190 is the ellipsoidal height in metres, using the ellipsoid of the
191 base geodetic CRS. Depending on PROJ versions and the exact na‐
192 ture of the CRS involved, especially before PROJ 9.1, a mix of
193 2D and 3D CRS could lead to 2D or 3D transformations. Starting
194 with PROJ 9.1, both CRS need to be 3D for vertical transforma‐
195 tion to possibly happen.
196 The +opt run-line arguments are associated with cartographic parame‐
198 ters.
199 The cs2cs program requires two coordinate reference system (CRS) defi‐
201 nitions. The first (or primary is defined based on all projection pa‐
202 rameters not appearing after the +to argument. All projection parame‐
203 ters appearing after the +to argument are considered the definition of
204 the second CRS. If there is no second CRS defined, a geographic CRS
205 based on the datum and ellipsoid of the source CRS is assumed. Note
206 that the source and destination CRS can both of same or different na‐
207 ture (geographic, projected, compound CRS), or one of each and may have
208 the same or different datums.
209 When using a WKT definition or a AUTHORITY:CODE, the axis order of the
211 CRS will be enforced. So for example if using EPSG:4326, the first
212 value expected (or returned) will be a latitude.
213 Internally, cs2cs uses the proj_create_crs_to_crs() function to compute
215 the appropriate coordinate operation, so implementation details of this
216 function directly impact the results returned by the program.
217 The environment parameter PROJ_DATA establishes the directory for re‐
219 source files (database, datum shift grids, etc.)
220 One or more files (processed in left to right order) specify the source
222 of data to be transformed. A - will specify the location of processing
223 standard input. If no files are specified, the input is assumed to be
224 from stdin. For input data the two data values must be in the first
225 two white space separated fields and when both input and output are
226 ASCII all trailing portions of the input line are appended to the out‐
227 put line.
228 Input geographic data (longitude and latitude) must be in DMS or deci‐
230 mal degrees format and input cartesian data must be in units consistent
231 with the ellipsoid major axis or sphere radius units. Output geographic
232 coordinates will normally be in DMS format (use -f %.12f for decimal
233 degrees with 12 decimal places), while projected (cartesian) coordi‐
234 nates will be in linear (meter, feet) units.
235 Use of remote grids
237 New in version 7.0.0.
238 If the PROJ_NETWORK environment variable is set to ON, cs2cs will at‐
241 tempt to use remote grids stored on CDN (Content Delivery Network)
242 storage, when they are not available locally.
243 More details are available in the Network capabilities section.
245
247 Using PROJ strings
248 The following script
249 cs2cs +proj=latlong +datum=NAD83 +to +proj=utm +zone=10 +datum=NAD27 -r <<EOF
251 45°15'33.1" 111.5W
252 45d15.551666667N -111d30
253 +45.25919444444 111d30'000w
254 EOF
255 will transform the input NAD83 geographic coordinates into NAD27 coor‐
257 dinates in the UTM projection with zone 10 selected. The geographic
258 values of this example are equivalent and meant as examples of various
259 forms of DMS input. The x-y output data will appear as three lines of:
260 1402285.98 5076292.42 0.00
262 NOTE:
264 To get those exact values, you have need to have all current grids
265 installed locally or use networking capabilities mentioned above.
266 Using EPSG CRS codes
268 Transforming from WGS 84 latitude/longitude (in that order) to UTM Zone
269 31N/WGS 84
270 cs2cs EPSG:4326 EPSG:32631 <<EOF
272 45N 2E
273 EOF
274 outputs
276 421184.70 4983436.77 0.00
278 Using EPSG CRS names
280 Transforming from WGS 84 latitude/longitude (in that order) with EGM96
281 height to UTM Zone 31N/WGS 84 with WGS84 ellipsoidal height
282 echo 45 2 0 | cs2cs "WGS 84 + EGM96 height" "WGS 84 / UTM zone 31N" --3d
284 outputs
286 421184.70 4983436.77 50.69
288 NOTE:
290 To get those exact values, you have need to have the EGM96 grid in‐
291 stalled locally or use networking capabilities mentioned above.
292
294 proj(1), cct(1), geod(1), gie(1), projinfo(1), projsync(1)
295
297 A list of known bugs can be found at
298 https://github.com/OSGeo/PROJ/issues where new bug reports can be sub‐
299 mitted to.
300
302 https://proj.org/
303
305 Frank Warmerdam
306
308 1983-2022
3099.1.1 Dec 1st, 2022 CS2CS(1)