aboutsummaryrefslogtreecommitdiff
path: root/docs/source/operations/conversions
diff options
context:
space:
mode:
authorKristian Evers <kristianevers@gmail.com>2018-07-06 11:23:59 +0200
committerKristian Evers <kristianevers@gmail.com>2018-07-06 11:23:59 +0200
commitdbf24f23b835453435cb24e5c925db5202a9a925 (patch)
tree69b414d85d51c5fb9170002b02a41bd42e05bb3c /docs/source/operations/conversions
parent50b0855177a0b6ce8053c2cb94b6a0db9d480b03 (diff)
downloadPROJ-dbf24f23b835453435cb24e5c925db5202a9a925.tar.gz
PROJ-dbf24f23b835453435cb24e5c925db5202a9a925.zip
Replace +k with +k_0 in doc examples
Diffstat (limited to 'docs/source/operations/conversions')
-rw-r--r--docs/source/operations/conversions/unitconvert.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/source/operations/conversions/unitconvert.rst b/docs/source/operations/conversions/unitconvert.rst
index fab8026f..632f6aeb 100644
--- a/docs/source/operations/conversions/unitconvert.rst
+++ b/docs/source/operations/conversions/unitconvert.rst
@@ -27,7 +27,7 @@ Many North American systems are defined with coordinates in feet. For example
in Vermont::
+proj=pipeline
- +step +proj=tmerc +lat_0=42.5 +lon_0=-72.5 +k=0.999964286 +x_0=500000.00001016 +y_0=0
+ +step +proj=tmerc +lat_0=42.5 +lon_0=-72.5 +k_0=0.999964286 +x_0=500000.00001016 +y_0=0
+step +proj=unitconvert +xy_in=m +xy_out=us-ft
Often when working with GNSS data the timestamps are presented in GPS-weeks,