From ec2b67d5df927f58af7445e589b347bf03698a30 Mon Sep 17 00:00:00 2001 From: Kristian Evers Date: Tue, 6 Mar 2018 09:23:33 +0100 Subject: Remove html folder --- html/CMakeLists.txt | 12 -- html/faq.html | 227 ------------------------- html/gen_parms.html | 276 ------------------------------- html/index.html | 13 -- html/man_cs2cs.html | 302 ---------------------------------- html/man_geod.html | 305 ---------------------------------- html/man_pj_init.html | 157 ------------------ html/man_proj.html | 447 -------------------------------------------------- html/proj_logo.png | Bin 27083 -> 0 bytes 9 files changed, 1739 deletions(-) delete mode 100644 html/CMakeLists.txt delete mode 100644 html/faq.html delete mode 100644 html/gen_parms.html delete mode 100644 html/index.html delete mode 100644 html/man_cs2cs.html delete mode 100644 html/man_geod.html delete mode 100644 html/man_pj_init.html delete mode 100644 html/man_proj.html delete mode 100644 html/proj_logo.png (limited to 'html') diff --git a/html/CMakeLists.txt b/html/CMakeLists.txt deleted file mode 100644 index 2c0bdc7b..00000000 --- a/html/CMakeLists.txt +++ /dev/null @@ -1,12 +0,0 @@ -set(HTML_DOC_FILE faq.html - gen_parms.html - index.html - man_cs2cs.html - man_geod.html - man_pj_init.html - man_proj.html - proj_logo.png) - -install(FILES ${HTML_DOC_FILE} - DESTINATION ${DOCDIR} - PERMISSIONS WORLD_READ WORLD_WRITE) diff --git a/html/faq.html b/html/faq.html deleted file mode 100644 index 0bea1472..00000000 --- a/html/faq.html +++ /dev/null @@ -1,227 +0,0 @@ - - -PROJ.4 - Frequently Asked Questions - - -

PROJ.4 - Frequently Asked Questions

- - - -

Where can I find the list of projections and their arguments?

- -There is no simple single location to find all the required information. The -PostScript/PDF documents listed on the main PROJ.4 -page under documentation are the authoritative source but projections and -options are spread over several documents in a form more related to their -order of implementation than anything else. - -The proj command -itself can report the list of projections using the -lp, option, -the list of ellipsoids with the -le option, the list of units with -the -lu option, and the list of built-in datums with the -ld -option.

- -The GeoTIFF -Projections Pages include most of the common PROJ.4 projections, and -a definition of the projection specific options for each.

- - - -

How do I do datum shifts between NAD27 and NAD83?

- -While the nad2nad program can be used in some cases, the cs2cs -is now the preferred mechanism. The following example demonstrates using -the default shift parameters for NAD27 to NAD83:

- -

-% cs2cs +proj=latlong +datum=NAD27 +to +proj=latlong +datum=NAD83 
--117 30
-

- -producing:

- -

-117d0'2.901"W   30d0'0.407"N 0.000
-

- -

-In order for datum shifting to work properly the various grid shift files -must be available. See below. More details are available in the -General Parameters document.

- - - -

How do I build/configure PROJ.4 to support datum shifting.

- -After downloading and unpacking the PROJ.4 source, also download and unpack -the set of datum shift files. This would be a file like - -ftp://ftp.remotesensing.org/pub/proj/proj-datumgrid-1.3.zip. This -file should be unpacked within the proj/nad directory. -Then proceed with the configuration, build and install. This will ensure -that the build system knows about the grid shift files, and applies the -ascii to binary preprocessing step.

- -On Windows the extra nadshift target must be used. For instance -nmake /f makefile.vc nadshift in the proj/src directory. -

- -A default build and install on Unix will normally build knowledge of the -directory where the grid shift files are installed into the PROJ.4 library -(usually /usr/local/share/proj). On Windows the library is normally built -thinking that C:\PROJ\NAD is the installed directory for the grid shift files. -If the built in concept of the PROJ.4 data directory is incorrect, the PROJ_LIB -environment can be defined with the correct directory.

- - - -

How do I debug problems with NAD27/NAD83 datum shifting?

- -

Verify that you have the binary files (eg. /usr/local/share/proj/conus) -installed on your system. If not, see the previous question. -
-
Try a datum shifting operation in relative isolation, such as with the -cs2cs command listed above. Do you get reasonable results? If not it is -likely the grid shift files aren't being found. Perhaps you need to define -PROJ_LIB?
- -
The cs2cs command and the underlying pj_transform() API know how to -do a grid shift as part of a more complex coordinate transformation; however, -it is imperative that both the source and destination coordinate system be -defined with appropriate datum information. That means that implicitly or -explicitly there must be a +datum= clause, a +nadgrids= clause or -a +towgs84= clause. For instance "cs2cs +proj=latlong +datum=NAD27 +to -+proj=latlong +ellps=WGS84" won't work because defining the output coordinate -system as using the ellipse WGS84 isn't the same as defining it to use the -datum WGS84 (use +datum=WGS84). If either the input or output are not -identified as having a datum, the datum shifting (and ellipsoid change) step -is just quietly skipped!
- -
The PROJ_DEBUG environment can be defined (any value) to force extra -output from -the PROJ.4 library to stderr (the text console normally) with information on -what data files are being opened and in some cases why a transformation fails. -Note that PROJ_DEBUG support is not yet very mature in the PROJ.4 library.
- -
The "-v" flag to cs2cs can be useful in establishing more detail on -what parameters being used internally for a coordinate system. This will -include expanding the definition of +datum clause.
- -

- - - -

How do I use EPSG coordinate system codes with PROJ.4?

- -There is somewhat imperfect translation between 2d geographic and -projected coordinate system codes and PROJ.4 descriptions of the -coordinate system available in the epsg definition file that -normally lives in the proj/nad directory. If installed (it is -installed by default on Unix), it is possible to use EPSG numbers like this: - -

-% cs2cs -v +init=epsg:26711
-# ---- From Coordinate System ----
-#Universal Transverse Mercator (UTM)
-#       Cyl, Sph
-#       zone= south
-# +init=epsg:26711 +proj=utm +zone=11 +ellps=clrk66 +datum=NAD27 +units=m
-# +no_defs +nadgrids=conus,ntv1_can.dat
-#--- following specified but NOT used
-# +ellps=clrk66
-# ---- To Coordinate System ----
-#Lat/long (Geodetic)
-#
-# +proj=latlong +datum=NAD27 +ellps=clrk66 +nadgrids=conus,ntv1_can.dat
-

- -The proj/nad/epsg file can be browsed and searched in a text editor -for coordinate systems. There are known to be problems with some coordinate -systems, and any coordinate systems with odd axes, a non-greenwich prime -meridian or other quirkiness are unlikely to work properly. Caveat Emptor!

- - - -

How do I use 3 parameter and 7 parameter datum shifting

- -Datum shifts can be approximated with 3 and 7 parameter transformations. -Their use is more fully described in the -towgs84 discussions.

- - - - -

Does PROJ.4 work in different international numeric locales?

- -No. PROJ.4 makes extensive use of sprintf() and atof() internally to translate -numeric values. If a locale is in effect that modifies formatting of -numbers, altering the role of commas and periods in numbers, then PROJ.4 -will not work. This problem is common in some European locales.

- -On unix-like platforms, this problem can be avoided by forcing the use -of the default numeric locale by setting the LC_NUMERIC environment variable -to C.

- -eg. -

-$ export LC_NUMERIC=C
-$ proj ...
-

- - - -

Changing Ellipsoid / Why can't I convert from WGS84 to Virtual Earth Mercator?

- -The coordinate system definition for Virtual Earth Mercator is as follows, -which uses a sphere as the earth model for the mercator projection. - -

-+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 
-     +x_0=0.0 +y_0=0 +k=1.0 +units=m +no_defs
-

- -But, if you do something like: - -

-cs2cs +proj=latlong +datum=WGS84 
-    +to +proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 
-                   +x_0=0.0 +y_0=0 +k=1.0 +units=m +no_defs
-

- -to convert between WGS84 and mercator on the sphere there will be substantial -shifts in the Y mercator coordinates. This is because internally cs2cs is -having to adjust the lat/long coordinates from being on the sphere to being -on the WGS84 datum which has a quite differently shaped ellipsoid.

- -In this case, and many other cases using spherical projections, the desired -approach is to actually treat the lat/long locations on the sphere as if -they were on WGS84 without any adjustments when using them for converting -to other coordinate systems. The solution is to "trick" PROJ.4 into applying -no change to the lat/long values when going to (and through) WGS84. This -can be accomplished by asking PROJ to use a null grid shift file -for switching from your spherical lat/long coordinates to WGS84.

- -

-cs2cs +proj=latlong +datum=WGS84 
-    +to +proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 
-                   +x_0=0.0 +y_0=0 +k=1.0 +units=m +nadgrids=@null +no_defs
-

- -Note the strategic addition of +nadgrids=@null to the spherical -projection definition.

- -Similar issues apply with many other datasets distributed with projections -based on a spherical earth model - such as many NASA datasets, and also -(I think) the Google Maps mercator projection.

- - - -

- -Requests to add items to the frequently asked questions list - -can be entered in bugzilla.

- - diff --git a/html/gen_parms.html b/html/gen_parms.html deleted file mode 100644 index 8cd8e161..00000000 --- a/html/gen_parms.html +++ /dev/null @@ -1,276 +0,0 @@ - - -PROJ.4 - General Parameters - - -

PROJ.4 - General Parameters

- -This document attempts to describe a variety of the PROJ.4 parameters -which can be applied to all, or many coordinate system definitions. This -document does not attempt to describe the parameters particular to particular -projection types. Some of these can be found in the GeoTIFF -Projections -Transform List. The definitive documentation for most parameters -is Gerald's original documentation available from the main PROJ.4 page.

- -

False Easting/Northing

- -Virtually all coordinate systems allow for the presence of a false easting -(+x_0) and northing (+y_0). Note that these values are always expressed in -meters even if the coordinate system is some other units. Some coordinate -systems (such as UTM) have implicit false easting and northing values.

- -

pm - Prime Meridian

- -A prime meridian may be declared indicating the offset between the prime -meridian of the declared coordinate system and that of greenwich. A prime -meridian is clared using the "pm" parameter, and may be assigned a symbolic -name, or the longitude of the alternative prime meridian relative to -greenwich.

- -Currently prime meridian declarations are only utilized by the -pj_transform() API call, not the pj_inv() and pj_fwd() calls. Consequently -the user utility cs2cs does honour prime meridians but the proj -user utility ignores them.

- -The following predeclared prime meridian names are supported. These -can be listed using the cs2cs argument -lm.

-   greenwich 0dE                           
-      lisbon 9d07'54.862"W                 
-       paris 2d20'14.025"E                 
-      bogota 74d04'51.3"E                  
-      madrid 3d41'16.48"W                  
-        rome 12d27'8.4"E                   
-        bern 7d26'22.5"E                   
-     jakarta 106d48'27.79"E                
-       ferro 17d40'W                       
-    brussels 4d22'4.71"E                   
-   stockholm 18d3'29.8"E                   
-      athens 23d42'58.815"E                
-        oslo 10d43'22.5"E                  
-

- -Example of use. The location long=0, lat=0 in the greenwich based -lat/long coordinates is translated to lat/long coordinates with Madrid -as the prime meridian.

- -

- cs2cs +proj=latlong +datum=WGS84 +to +proj=latlong +datum=WGS84 +pm=madrid
-0 0                           (input)
-3d41'16.48"E    0dN 0.000     (output)
-

- -

towgs84 - Datum transformation to WGS84

- -Datum shifts can be approximated by 3 parameter spatial translations (in -geocentric space), or 7 parameter shifts (translation + rotation + scaling). -The parameters to describe this can be described using the towgs84 -parameter.

- -In the three parameter case, the three arguments are the translations to the -geocentric location in meters.

- -For instance, the following demonstrates converting from the Greek GGRS87 -datum to WGS84.

- -

-% cs2cs +proj=latlong +ellps=GRS80 +towgs84=-199.87,74.79,246.62 \
-    +to +proj=latlong +datum=WGS84
-20 35
-20d0'5.467"E    35d0'9.575"N 8.570
-

- -The EPSG database provides this example for transforming from WGS72 to WGS84 -using an approximated 7 parameter transformation.

-% cs2cs +proj=latlong +ellps=WGS72 +towgs84=0,0,4.5,0,0,0.554,0.219 \
-    +to +proj=latlong +datum=WGS84
-4 55
-4d0'0.554"E     55d0'0.09"N 3.223
-

- -The seven parameter case uses delta_x, delta_y, delta_z, -Rx - rotation X, Ry - rotation Y, Rz - rotation Z, -M_BF - Scaling. The three translation parameters are in meters as -in the three parameter case. The rotational parameters are in seconds of -arc. The scaling is apparently the scale change in parts per million.

- -A more complete discussion of the 3 and 7 parameter transformations can be -found in the EPSG database (trf_method's 9603 and 9606). Within PROJ.4 -the following calculations are used to apply the towgs84 transformation -(going to WGS84). The x, y and z coordinates are in geocentric coordinates. - -Three parameter transformation (simple offsets): - -

-  x[io] = x[io] + defn->datum_params[0];
-  y[io] = y[io] + defn->datum_params[1];
-  z[io] = z[io] + defn->datum_params[2];
-

- -Seven parameter transformation (translation, rotation and scaling): - -

-  #define Dx_BF (defn->datum_params[0])
-  #define Dy_BF (defn->datum_params[1])
-  #define Dz_BF (defn->datum_params[2])
-  #define Rx_BF (defn->datum_params[3])
-  #define Ry_BF (defn->datum_params[4])
-  #define Rz_BF (defn->datum_params[5])
-  #define M_BF  (defn->datum_params[6])
-
-  x_out = M_BF*(       x[io] - Rz_BF*y[io] + Ry_BF*z[io]) + Dx_BF;
-  y_out = M_BF*( Rz_BF*x[io] +       y[io] - Rx_BF*z[io]) + Dy_BF;
-  z_out = M_BF*(-Ry_BF*x[io] + Rx_BF*y[io] +       z[io]) + Dz_BF;
-

- -Note that EPSG method 9607 (coordinate frame rotation) coefficients can be -converted to EPSG method 9606 (position vector 7-parameter) supported by -PROJ.4 by reversing the sign of the rotation vectors. The methods are -otherwise the same.

- -

nadgrids - Grid Based Datum Adjustments

- -In many places (notably North America and Australia) national geodetic -organizations provide grid shift files for converting between different -datums, such as NAD27 to NAD83. These grid shift files include a shift to -be applied at each grid location. Actually grid shifts are normally computed -based on an interpolation between the containing four grid points.

- -PROJ.4 currently supports use of grid shift files for shifting between -datums and WGS84 under some circumstances. The grid shift table formats are -ctable (the binary format produced by the PROJ.4 nad2bin program), -NTv1 (the old Canadian format), and NTv2 (.gsb - the new Canadian and -Australian format).

- -Use of grid shifts is specified using the "nadgrids" keyword in a coordinate -system definition. For example:

- -

-% cs2cs +proj=latlong +ellps=clrk66 +nadgrids=ntv1_can.dat \
-    +to +proj=latlong +ellps=GRS80 +datum=NAD83 << EOF
--111 50 
-EOF
-111d0'2.952"W   50d0'0.111"N 0.000
-

- -In this case the /usr/local/share/proj/ntv1_can.dat grid shift file -was loaded, and used to get a grid shift value for the selected point.

- -It is possible to list multiple grid shift files, in which case each will be -tried in turn till one is found that contains the point being transformed.

- -

-% cs2cs +proj=latlong +ellps=clrk66 \
-          +nadgrids=conus,alaska,hawaii,stgeorge,stlrnc,stpaul \
-    +to +proj=latlong +ellps=GRS80 +datum=NAD83 << EOF
--111 44
-EOF
-111d0'2.788"W   43d59'59.725"N 0.000
-

- -

Skipping Missing Grids

- -The special prefix @ may be prefixed to a grid to make it optional. If -it not found, the search will continue to the next grid. Normally any -grid not found will cause an error. For instance, the following would -use the ntv2_0.gsb file if available, otherwise it would fallback to using -the ntv1_can.dat file.

- -

-% cs2cs +proj=latlong +ellps=clrk66 +nadgrids=@ntv2_0.gsb,ntv1_can.dat \
-    +to +proj=latlong +ellps=GRS80 +datum=NAD83 << EOF
--111 50 
-EOF
-111d0'3.006"W   50d0'0.103"N 0.000
-

- -

The null Grid

- -A special null grid shift file is shift with releases after 4.4.6 (not -inclusive). This file provides a zero shift for the whole world. It may -be listed at the end of a nadgrids file list if you want a zero shift to -be applied to points outside the valid region of all the other grids. -Normally if no grid is found that contains the point to be transformed an -error will occur.

- -

-% cs2cs +proj=latlong +ellps=clrk66 +nadgrids=conus,null \
-    +to +proj=latlong +ellps=GRS80 +datum=NAD83 << EOF
--111 45
-EOF
-111d0'3.006"W   50d0'0.103"N 0.000
-

- -

-% cs2cs +proj=latlong +ellps=clrk66 +nadgrids=conus,null \
-    +to +proj=latlong +ellps=GRS80 +datum=NAD83 << EOF
--111 44
--111 55
-EOF
-111d0'2.788"W   43d59'59.725"N 0.000
-111dW   55dN 0.000
-

- -

Downloading and Installing Grids

- -The source distribution of PROJ.4 contains only the ntv1_can.dat file. To -get the set of US grid shift files it is necessary to download an additional -distribution of files from the PROJ.4 site, such as - -proj-nad27-1.1.tar.gz. Overlay it on the PROJ.4 source distribution, -and re-configure, compile and install. The distributed ASCII .lla files -are converted into binary (platform specific) files that are installed. -On windows using the nmake /f makefile.vc nadshift command in -the proj\src directory to build and install these files.

- -It appears we can't redistribute the Canadian NTv2 grid shift file freely, -though it is better than the NTv1 file. However, end users can download it -for free from the NRCan web site at - -http://www.geod.nrcan.gc.ca/software/ntv2_e.php. After -downloading it, just dump it in the data directory with the other -installed data files (usually /usr/local/share/proj).

- -

Caveats

- -

Where grids overlap (such as conus and ntv1_can.dat for instance) the -first found for a point will be used regardless of whether it is appropriate -or not. So, for instance, +nadgrids=ntv1_can.dat,conus would result in the -canadian data being used for some areas in the northern United States even -though the conus data is the approved data to use for the area. Careful -selection of files and file order is necessary. In some cases border spanning -datasets may need to be pre-segmented into Canadian and American points -so they can be properly grid shifted.
- -
There are additional grids for shifting between NAD83 and various -HPGN versions of the NAD83 datum. Use of these haven't been tried recently -so you may encounter problems. The FL.lla, WO.lla, MD.lla, TN.lla and WI.lla -are examples of high precision grid shifts. Take care!
- -
Additional detail on the grid shift being applied can be found by -setting the PROJ_DEBUG environment variable to a value. This will result -in output to stderr on what grid is used to shift points, the bounds of the -various grids loaded and so forth.
- -
PROJ.4 always assumes that grids contain a shift to NAD83 -(essentially WGS84). Other types of grids might or might not be usable.
- -

- - - - - - - - - - diff --git a/html/index.html b/html/index.html deleted file mode 100644 index e56f5767..00000000 --- a/html/index.html +++ /dev/null @@ -1,13 +0,0 @@ - - - -redirect - - - -This page has moved. You will be automatically redirected to its new location. -If you aren't forwarded to the new page, -click here. - - diff --git a/html/man_cs2cs.html b/html/man_cs2cs.html deleted file mode 100644 index 5454714b..00000000 --- a/html/man_cs2cs.html +++ /dev/null @@ -1,302 +0,0 @@ -Content-type: text/html; charset=UTF-8 - - -Man page of CS2CS - -

CS2CS

-Section: User Commands (1)
Updated: 2000/03/21 Rel. 4.4
Index -Return to Main Contents

- - -

NAME

- -cs2cs - cartographic coordinate system filter - -

SYNOPSIS

- -cs2cs - -[ --eEfIlrstvwW - -[ -args - -] ] [ -+opts[=arg] - -] -
- -
[ +to [+opts[=arg]] ] -file[s] - -

DESCRIPTION

- -Cs2cs - -performs transformation between the source and destination cartographic -coordinate system on a set of input points. The coordinate system -transformation can include translation between projected and geographic -coordinates as well as the application of datum shifts. -

- -The following control parameters can appear in any order: -

-I - -: -method to specify inverse translation, convert from +to coordinate -system to the primary coordinate system defined. -
-ta - -: -A - -specifies a character employed as the first character to denote -a control line to be passed through without processing. -This option applicable to ascii input only. -(# is the default value). -
-e string - -: -String - -is an arbitrary string to be output if an error is detected during -data transformations. -The default value is: *\t*. -Note that if the --b, - --i - -or --o - -options are employed, an error is returned as HUGE_VAL -value for both return values. -
-E - -: -causes the input coordinates to be copied to the output line -prior to printing the converted values. -
-l[p|P|=|e|u|d]id - -: -List projection identifiers with --l, - --lp - -or --lP (expanded) - -that can be selected with -+proj. - --l=id - -gives expanded description of projection -id. - -List ellipsoid identifiers with --le, - -that can be selected with -+ellps, - --lu - -list of cartesian to meter conversion factors -that can be selected with -+units - -or --ld - -list of datums that can be selected with -+datum. - -
-r - -: -This options reverses the order of the -expected input from longitude-latitude or x-y to latitude-longitude or y-x. -
-s - -: -This options reverses the order of the -output from x-y or longitude-latitude to y-x or latitude-longitude. -
-f format - -: -Format - -is a -printf - -format string to control the form of the output values. -For inverse projections, the output will be in degrees when this option -is employed. -If a format is specified for inverse projection the -output data will be in decimal degrees. -The default format is "%.2f" for forward projection and DMS -for inverse. -
-[w|W]n - -: -N - -is the number of significant fractional digits to employ for -seconds output (when the option is not specified, --w3 - -is assumed). -When --W - -is employed the fields will be constant width and with leading zeroes. -
-v - -: -causes a listing of cartographic control parameters tested for and -used by the program to be printed prior to input data. -

- -The -+args - -run-line arguments are associated with cartographic parameters -and usage varies with projection and for a complete description see -Cartographic Projection Procedures for the UNIX Environment---A User's Manual - -and supplementary documentation for Release 4. -

- -The cs2cs program requires two coordinate system definitions. The -first (or primary is defined based on all projection parameters not -appearing after the +to argument. All projection parameters -appearing after the +to argument are considered the definition -of the second coordinate system. If there is no second coordinate system -defined, a geographic coordinate system based on the datum and ellipsoid of -the source coordinate system is assumed. Note that the source and destination -coordinate system can both be projections, both be geographic, or one of -each and may have the same or different datums. -

- -Additional projection control parameters may be contained in two -auxiliary control files: -the first is optionally referenced with the -+init=file:id - -and the second is always processed after the name -of the projection has been established from either the run-line -or the contents of -+init - -file. -The environment parameter -PROJ_LIB - -establishes the default directory for a file reference without -an absolute path. This is also used for supporting files like -datum shift files. -

- -One or more -files - -(processed in left to right order) -specify the source of data to be transformed. -A - will specify the location of processing standard input. -If no files are specified, the input is assumed to be from -stdin. - -For input data the two data values must be in the -first two white space separated fields and -when both input and output are ASCII all trailing portions -of the input line are appended to the output line. -

- -Input geographic data -(longitude and latitude) must be in DMS or decimal degrees format and input -cartesian data must be in units consistent with the ellipsoid -major axis or sphere radius units. -Output geographic coordinates will normally be in DMS format (use --f %.12f - -for decimal degrees with 12 decimal places), while -projected (cartesian) coordinates will be in linear (meter, feet) units. - - -

EXAMPLE

- -The following script -

: -
cs2cs +proj=latlong +datum=NAD83 - +to +proj=utm +zone=10 +datum=NAD27 -r <<EOF - 45d15'33.1" 111.5W - 45d15.551666667N -111d30 - +45.25919444444 111d30'000w - EOF -

- -will transform the input NAD83 geographic coordinates into NAD27 coordinates -in the UTM projection with zone 10 selected. -The geographic values of this example are equivalent and meant -as examples of various forms of DMS input. -The x-y output data will appear as three lines of: -

: -
1402285.99 5076292.42 0.000 -

- - -

HOME PAGE

- -https://github.com/OSGeo/proj.4/wiki -

- -

-This document was created by -man2html, -using the manual pages.
-Time: 20:43:10 GMT, February 18, 2016 - - diff --git a/html/man_geod.html b/html/man_geod.html deleted file mode 100644 index 8150b4d1..00000000 --- a/html/man_geod.html +++ /dev/null @@ -1,305 +0,0 @@ -Manpage of GEOD - -

GEOD

-Section: User Commands (1)
Updated: 2000/03/21 Rel. 4.4
Index -Return to Main Contents

- - -

NAME

- -geod - direct geodesic computations -
- -invgeod - inverse geodesic computations - -

SYNOPSIS

- -geod - -+ellps=<ellipse> - -[ --afFIlptwW - -[ -args - -] ] [ -+args - -] -file[s] -
- -invgeod - -+ellps=<ellipse> - -[ --afFIlptwW - -[ -args - -] ] [ -+args - -] -file[s] - -

DESCRIPTION

- -Geod - -(direct) and -invgeod - -(inverse) -perform geodesic (``Great Circle'') computations for determining -latitude, longitude and back azimuth of a terminus point -given a initial point latitude, longitude, azimuth and distance (direct) or -the forward and back azimuths and distance between an initial and -terminus point latitudes and longitudes (inverse). -

- -The following runline control parameters can appear in any order: -

-I - -: -Specifies that the inverse geodesic computation is to be performed. -May be used with execution of -goed - -as an alternative to -invgeod - -execution. -
-a - -: -Latitude and longitudes of the initial and terminal points, -forward and back azimuths and distance are output. -
-ta - -: -A - -specifies a character employed as the first character to denote -a control line to be passed through without processing. -
-le - -: -Gives a listing of all the ellipsoids that may be selected with the -+ellps= - -option. -
-lu - -: -Gives a listing of all the units that may be selected with the -+units= - -option. -
-[f|F] format - -: -Format - -is a -printf - -format string to control the output form of the geographic coordinate values -(f) or distance value (F). -The default mode is DMS for geographic coordinates and "%.3f" for distance. -
-[w|W]n - -: -N - -is the number of significant fractional digits to employ for -seconds output (when the option is not specified, --w3 - -is assumed). -When --W - -is employed the fields will be constant width with leading zeroes. -
-p - -: -This option causes the azimuthal values to be output as unsigned -DMS numbers between 0 and 360 degrees. Also note -f. -

- -The -+args - -run-line arguments are associated with geodetic parameters -for specifying the ellipsoidal or sphere to use. -See -proj - -documentation for full list of these parameters and contrl. -The options are processed in left to right order -from the run line. -Reentry of an option is ignored with the first occurrence assumed to -be the desired value. -

- -For direct determinations input data must be in latitude, -longitude, azimuth and distance order and output will be -latitude, longitude and back azimuth of the terminus point. -Latitude, longitude of the initial and terminus point are -input for the inverse mode and respective forward and back -azimuth from the initial and terminus points are output along -with the distance between the points. -

- -Input geographic coordinates -(latitude and longitude) and azimuthal data must be in DMS format and input -distance data must be in units consistent with the ellipsoid -major axis or sphere radius units. -Output geographic coordinates will be in DMS -(if the --f - -switch is not employed) to 0.001" -with trailing, zero-valued minute-second fields deleted. -Output distance data will be in the same units as the ellipsoid or -sphere radius. -

- -The Earth's ellipsoidal figure may be selected in the same -manner as program -proj - -by using -+ellps=, +a=, +es=, - -etc. -

- -Geod - -may also be used to determine intermediate points along either -a geodesic line between two points or along an arc of specified distance -from a geographic point. -In both cases an initial point must be specified with -+lat_1=lat - -and -+lon_1=lon - -parameters and either a terminus point -+lat_2=lat - -and -+lon_2=lon - -or a distance and azimuth from the initial point with -+S=distance - -and -+A=azimuth - -must be specified. -

- -If points along a geodesic are to be determined then either -+n_S=integer - -specifying the number of intermediate points and/or -+del_S=distance - -specifying the incremental distance between points must be specified. -

- -To determine points along an arc equidistant from the initial point both -+del_A=angle - -and -+n_A=integer - -must be specified which determine the respective angular increments -and number of points to be determined. - - -

EXAMPLE

- -The following script determines the geodesic azimuths and distance in -U.S. stature miles from Boston, MA, to Portland, OR: -

: -
geod +ellps=clrk66 <<EOF -I +units=us-mi - 42d15'N 71d07'W 45d31'N 123d41'W - EOF -

- -which gives the results: -

: -
-66d31'50.141" 75d39'13.083" 2587.504 -

- -where the first two values are the -azimuth from Boston to Portland, the back azimuth from Portland to -Boston followed by the distance. - - -An example of forward geodesic use is to use the Boston location and determine -Portland's location by azimuth and distance: -

: - geod +ellps=clrk66 <<EOF +units=us-mi - 42d15'N 71d07'W -66d31'50.141" 2587.504 - EOF -

- -which gives: -

: -
45d31'0.003"N 123d40'59.985"W 75d39'13.094" -

- -Note: lack of precision in the distance value compromises -the precision of the Portland location. - -

HOME PAGE

- -http://www.remotesensing.org/proj -

- -

Index

NAME: -
SYNOPSIS: -
DESCRIPTION: -
EXAMPLE: -
SEE ALSO: -
HOME PAGE: -

-This document was created by -man2html, -using the manual pages.
-Time: 13:14:56 GMT, October 14, 2005 - - diff --git a/html/man_pj_init.html b/html/man_pj_init.html deleted file mode 100644 index 25889942..00000000 --- a/html/man_pj_init.html +++ /dev/null @@ -1,157 +0,0 @@ -Manpage of PJ_INIT - -

PJ_INIT

-Section: Misc. Reference Manual Pages (3U)
Updated: 2001/04/05 Rel. 4.4
Index -Return to Main Contents

- - - - -

NAME

- -pj_init - initialize cartographic projection -
- -pj_init_plus - initialize cartographic projection -
- -pj_fwd - forward cartographic projection -
- -pj_inv - inverse cartographic projection -
- -pj_transform - transform between coordinate systems -
- -pj_free - de-initialize projection - -

SYNOPSIS

- -

-#include <proj_api.h>
-
-projPJ pj_init(int argc, char **argv)
-
-projPJ pj_init_plus(const char *defn)
-
-projUV pj_fwd(projUV val, projPJ proj)
-
-projUV pj_inv(projUV val, projPJ proj)
-
-int pj_transform(projPJ src_cs, projPJ dst_cs, long point_count, 
-                 double *x, double *y, double *z)
-               
-void pj_free(projPJ proj)
-
-

DESCRIPTION

- -Procedure pj_init selects and initializes a cartographic projection -with its argument control parameters. -Argc is the number of elements in the array of control strings -argv that each contain individual cartographic control keyword -assignments (+ proj arguments). -The list must contain at least the proj=projection and -Earth's radius or elliptical parameters. -If the initialization of the projection is successful a valid -address is returned otherwise a NULL value. -

-The pj_init_plus function operates similarly to pj_init but -takes a single string containing the definition, with each parameter -prefixed with a plus sign. For example "+proj=utm +zone=11 +ellps=WGS84". -

-Once initialization is performed either forward or inverse -projections can be performed with the returned value of pj_init -used as the argument proj. -The argument structure projUV values u and v contain -respective longitude and latitude or x and y. -Latitude and longitude are in radians. -If a projection operation fails, both elements of projUV are -set to HUGE_VAL (defined in math.h). -

-Note: all projections have a forward mode, but some do not have -an inverse projection. -If the projection does not have an inverse the projPJ structure element -inv will be NULL. -

-The pj_transform function may be used to transform points between -the two provided coordinate systems. In addition to converting between -cartographic projection coordinates and geographic coordinates, this function -also takes care of datum shifts if possible between the source and destination -coordinate system. Unlike pj_fwd and pj_inv it is also allowable -for the coordinate system definitions (PJ *) to be geographic coordinate -systems (defined as +proj=latlong). The x, y and z arrays -contain the input values of the points, and are replaced with the output -values. The function returns zero on success, or the error number (also in -pj_errno) on failure. -

-Memory associated with the projection may be freed with pj_free. - -

EXAMPLE

- -The following program reads latitude and longitude values in decimal -degrees, performs Mercator projection with a Clarke 1866 ellipsoid and -a 33° latitude of true scale and prints the projected -cartesian values in meters: -

-
-#include <proj_api.h>
-
-main(int argc, char **argv) {
-        char *args[] = { "proj=merc", "ellps=clrk66", "lat_ts=33" };
-        projUV p;
-        projPJ pj;
-
-        if (!(pj = pj_init(3, args)))
-           exit(1);
-        while (scanf("%lf %lf", &p.v, &p.u) == 2) {
-           p.u *= DEG_TO_RAD;
-           p.v *= DEG_TO_RAD;
-           p = pj_fwd(p, pj);
-           printf("%.2f\t%.2f\n", p.u, p.v);
-        }
-        exit(0);
-} 
-

-

- - -

LIBRARY

- -libproj.a - library of projections and support procedures - -

HOME PAGE

- -http://www.remotesensing.org/proj -

- -

Index

NAME: -
SYNOPSIS: -
DESCRIPTION: -
EXAMPLE: -
LIBRARY: -
SEE ALSO: -
HOME PAGE: -

-This document was created by -man2html, -using the manual pages.
-Time: 13:14:22 GMT, October 14, 2005 - - diff --git a/html/man_proj.html b/html/man_proj.html deleted file mode 100644 index 74980a94..00000000 --- a/html/man_proj.html +++ /dev/null @@ -1,447 +0,0 @@ -Content-type: text/html; charset=UTF-8 - - -Man page of PROJ - -

PROJ

-Section: User Commands (1)
Updated: 2000/03/21 Rel. 4.4
Index -Return to Main Contents

- - -

NAME

- -proj - forward cartographic projection filter -
- -invproj - inverse cartographic projection filter - -

SYNOPSIS

- -proj - -[ --bceEfiIlmorsStTvVwW - -[ -args - -] ] [ -+args - -] -file[s] -
- -invproj - -[ --bceEfiIlmorsStTwW - -[ -args - -] ] [ -+args - -] -file[s] - -

DESCRIPTION

- -Proj - -and -invproj - -perform respective forward and inverse transformation of cartographic data -to or from cartesian data with a wide range of selectable projection functions. -

- -The following control parameters can appear in any order: -

-b - -: -Special option for binary coordinate data input and output -through standard input and standard output. -Data is assumed to be in system type -double - -floating point words. -This option is to be used when -proj - -is a -son - -process and allows bypassing formatting operations. -
-i - -: -Selects binary input only (see --b option). - -
-I - -: -alternate method to specify inverse projection. -Redundant when used with -invproj. - -
-o - -: -Selects binary output only (see --b option). - -
-ta - -: -A - -specifies a character employed as the first character to denote -a control line to be passed through without processing. -This option applicable to ascii input only. -(# is the default value). -
-e string - -: -String - -is an arbitrary string to be output if an error is detected during -data transformations. -The default value is: *\t*. -Note that if the --b, - --i - -or --o - -options are employed, an error is returned as HUGE_VAL -value for both return values. -
-E - -: -causes the input coordinates to be copied to the output line -prior to printing the converted values. -
-l[p|P|=|e|u|d]id - -: -List projection identifiers with --l, - --lp - -or --lP (expanded) - -that can be selected with -+proj. - --l=id - -gives expanded description of projection -id. - -List ellipsoid identifiers with --le, - -that can be selected with -+ellps, - --lu - -list of cartesian to meter conversion factors -that can be selected with -+units - -or --ld - -list of datums that can be selected with -+datum. - -
-r - -: -This options reverses the order of the -expected input from longitude-latitude or x-y to latitude-longitude or y-x. -
-s - -: -This options reverses the order of the -output from x-y or longitude-latitude to y-x or latitude-longitude. -
-S - -: -Causes estimation of -meridional - -and -parallel - -scale factors, -area - -scale factor and -angular distortion, - -and -maximum - -and -minimum - -scale factors to be listed between <> for each input point. -For conformal projections meridional and parallel scales factors -will be equal and angular distortion zero. -Equal area projections will have an area factor of 1. -
-m mult - -: -The cartesian data may be scaled by the -mult - -parameter. -When processing data in a forward projection mode the -cartesian output values are multiplied by -mult - -otherwise the input cartesian values are divided by -mult - -before inverse projection. -If the first two characters of -mult - -are 1/ or 1: then the reciprocal value of -mult - -is employed. -
-f format - -: -Format - -is a -printf - -format string to control the form of the output values. -For inverse projections, the output will be in degrees when this option -is employed. -The default format is "%.2f" for forward projection and DMS -for inverse. -
-[w|W]n - -: -N - -is the number of significant fractional digits to employ for -seconds output (when the option is not specified, --w3 - -is assumed). -When --W - -is employed the fields will be constant width and with leading zeroes. -
-v - -: -causes a listing of cartographic control parameters tested for and -used by the program to be printed prior to input data. -Should not be used with the --T - -option. -
-V - -: -This option causes an expanded annotated listing of the characteristics -of the projected point. --v is implied with this option. - -
-T ulow,uhi,vlow,vhi,res[,umax,vmax] - -: -This option creates a set of bivariate Chebyshev polynomial -coefficients that approximate the selected cartographic projection on -stdout. - -The values -low - -and -hi - -denote the range of the input where the -u - -or -v - -prefixes apply to respective longitude-x or latitude-y -depending upon whether a forward or inverse projection is selected. -Res - -is an integer number specifying the power of 10 precision of the -approximation. -For example, a -res - -of -3 specifies an approximation with an accuracy better than .001. -Umax, - -and -vmax - -specify maximum degree of the polynomials (default: 15). -See also: -fproj(1). - -

- -One or more -files - -(processed in left to right order) -specify the source of data to be transformed. -A - will specify the location of processing standard input. -If no files are specified, the input is assumed to be from -stdin. - -For ASCII input data the two data values must be in the -first two white space separated fields and -when both input and output are ASCII all trailing portions -of the input line are appended to the output line. -

- -Input geographic data -(longitude and latitude) must be in DMS format and input -cartesian data must be in units consistent with the ellipsoid -major axis or sphere radius units. -Output geographic coordinates will be in DMS -(if the --w - -switch is not employed) and precise to 0.001" -with trailing, zero-valued minute-second fields deleted. - -

EXAMPLE

- -The following script -

: -
proj +proj=utm +lon_0=112w +ellps=clrk66 -r <<EOF - 45d15'33.1" 111.5W - 45d15.551666667N -111d30 - +45.25919444444 111d30'000w - EOF -

- -will perform UTM forward projection with a standard UTM -central meridian nearest longitude 112°W. -The geographic values of this example are equivalent and meant -as examples of various forms of DMS input. -The x-y output data will appear as three lines of: -

: -
460769.27 5011648.45 -

- - -

OTHER PROGRAMS

- -

- -The proj program is limited to converting between geographic and -projection coordinates within one datum. -

- -The cs2cs program operates -similarly, but allows translation between any pair of definable coordinate -systems, including support for datum translation. -

- -The geod program provides the ability to compute geodesic (Great -Circle) computations. - -

HOME PAGE

- -https://github.com/OSGeo/proj.4/wiki -

- -

Index

NAME: -
SYNOPSIS: -
DESCRIPTION: -
EXAMPLE: -
OTHER PROGRAMS: -
SEE ALSO: -
HOME PAGE: -

-This document was created by -man2html, -using the manual pages.
-Time: 20:44:57 GMT, February 18, 2016 - - diff --git a/html/proj_logo.png b/html/proj_logo.png deleted file mode 100644 index 92d5acb6..00000000 Binary files a/html/proj_logo.png and /dev/null differ -- cgit v1.2.3

PROJ.4 - Frequently Asked Questions

PROJ.4 - General Parameters

Skipping Missing Grids

The null Grid

Downloading and Installing Grids

Caveats

CS2CS

NAME

SYNOPSIS

DESCRIPTION

EXAMPLE

SEE ALSO

HOME PAGE

Index

GEOD

NAME

SYNOPSIS

DESCRIPTION

EXAMPLE

SEE ALSO

HOME PAGE

Index

PJ_INIT

NAME

SYNOPSIS

DESCRIPTION

EXAMPLE

LIBRARY

SEE ALSO

HOME PAGE

Index

PROJ

NAME

SYNOPSIS

DESCRIPTION

EXAMPLE

OTHER PROGRAMS

SEE ALSO

HOME PAGE

Index