diff options
| author | Kristian Evers <kristianevers@gmail.com> | 2018-03-06 09:23:33 +0100 |
|---|---|---|
| committer | Kristian Evers <kristianevers@gmail.com> | 2018-03-06 09:23:33 +0100 |
| commit | ec2b67d5df927f58af7445e589b347bf03698a30 (patch) | |
| tree | 2429815ffd6bcac59fd1e054cf0dd067e96a6d62 /html | |
| parent | ffc0a463f07b60f8cc17a3630f740584fa18c95f (diff) | |
| download | PROJ-ec2b67d5df927f58af7445e589b347bf03698a30.tar.gz PROJ-ec2b67d5df927f58af7445e589b347bf03698a30.zip | |
Remove html folder
Diffstat (limited to 'html')
| -rw-r--r-- | html/CMakeLists.txt | 12 | ||||
| -rw-r--r-- | html/faq.html | 227 | ||||
| -rw-r--r-- | html/gen_parms.html | 276 | ||||
| -rw-r--r-- | html/index.html | 13 | ||||
| -rw-r--r-- | html/man_cs2cs.html | 302 | ||||
| -rw-r--r-- | html/man_geod.html | 305 | ||||
| -rw-r--r-- | html/man_pj_init.html | 157 | ||||
| -rw-r--r-- | html/man_proj.html | 447 | ||||
| -rw-r--r-- | html/proj_logo.png | bin | 27083 -> 0 bytes |
9 files changed, 0 insertions, 1739 deletions
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 @@ -<html> -<head> -<title>PROJ.4 - Frequently Asked Questions</title> -</head> -<body BGCOLOR="#FFFFFF"> -<h1>PROJ.4 - Frequently Asked Questions</h1> - -<!--------------------------------------------------------------------------> - -<h2><a name="proj_docs">Where can I find the list of projections and their arguments?</a></h2> - -There is no simple single location to find all the required information. The -PostScript/PDF documents listed on the <a href="index.html">main</a> 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.<pp> - -The <b>proj</b> command -itself can report the list of projections using the <tt>-lp,</tt> option, -the list of ellipsoids with the <tt>-le</tt> option, the list of units with -the <tt>-lu</tt> option, and the list of built-in datums with the <tt>-ld</tt> -option.<p> - -The <a href="http://www.remotesensing.org/geotiff/proj_list/">GeoTIFF -Projections Pages</a> include most of the common PROJ.4 projections, and -a definition of the projection specific options for each.<p> - -<!--------------------------------------------------------------------------> - -<h2><a name="nad2783">How do I do datum shifts between NAD27 and NAD83?</a></h2> - -While the <b>nad2nad</b> program can be used in some cases, the <b>cs2cs</b> -is now the preferred mechanism. The following example demonstrates using -the default shift parameters for NAD27 to NAD83:<p> - -<pre> -% cs2cs +proj=latlong +datum=NAD27 +to +proj=latlong +datum=NAD83 --117 30 -</pre> -<p> - -producing:<p> - -<pre> -117d0'2.901"W 30d0'0.407"N 0.000 -</pre> - -<p> -In order for datum shifting to work properly the various grid shift files -must be available. See below. More details are available in the -<a href="gen_parms.html#nadgrids">General Parameters</a> document.<p> - -<!--------------------------------------------------------------------------> - -<h2><a name="datumshifting">How do I build/configure PROJ.4 to support datum shifting.</a></h2> - -After downloading and unpacking the PROJ.4 source, also download and unpack -the set of datum shift files. This would be a file like -<a href="ftp://ftp.remotesensing.org/pub/proj/proj-datumgrid-1.3.zip"> -ftp://ftp.remotesensing.org/pub/proj/proj-datumgrid-1.3.zip</a>. This -file should be unpacked <i>within</i> the <tt>proj/nad</tt> 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.<p> - -On Windows the extra <tt>nadshift</tt> target must be used. For instance -<tt>nmake /f makefile.vc nadshift</tt> in the <tt>proj/src</tt> directory. -<p> - -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.<p> - -<!--------------------------------------------------------------------------> - -<h2><a name="nad2783_debug">How do I debug problems with NAD27/NAD83 datum shifting?</a></h2> - -<ol> -<li> Verify that you have the binary files (eg. /usr/local/share/proj/conus) -installed on your system. If not, see the previous question. -<p> -<li> 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? <p> - -<li> 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!<p> - -<li> 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.<p> - -<li> 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. <p> - -</ol> - -<!--------------------------------------------------------------------------> - -<h2><a name="epsg">How do I use EPSG coordinate system codes with PROJ.4?</a></h2> - -There is somewhat imperfect translation between 2d geographic and -projected coordinate system codes and PROJ.4 descriptions of the -coordinate system available in the <tt>epsg</tt> definition file that -normally lives in the <tt>proj/nad</tt> directory. If installed (it is -installed by default on Unix), it is possible to use EPSG numbers like this: - -<pre> -% 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 -</pre> - -The <tt>proj/nad/epsg</tt> 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!<p> - -<!--------------------------------------------------------------------------> - -<h2><a name="datum_37">How do I use 3 parameter and 7 parameter datum shifting</a></h2> - -Datum shifts can be approximated with 3 and 7 parameter transformations. -Their use is more fully described in the -<a href="gen_parms.html#towgs84">towgs84</a> discussions.<p> - - -<!--------------------------------------------------------------------------> - -<h2><a name="locale">Does PROJ.4 work in different international numeric locales?</a></h2> - -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.<p> - -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. <p> - -eg. -<pre> -$ export LC_NUMERIC=C -$ proj ... -</pre> - -<!--------------------------------------------------------------------------> - -<h2><a name="sphere_as_wgs84">Changing Ellipsoid / Why can't I convert from WGS84 to Virtual Earth Mercator?</a></h2> - -The coordinate system definition for Virtual Earth Mercator is as follows, -which uses a sphere as the earth model for the mercator projection. - -<pre> -+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 -</pre> - -But, if you do something like: - -<pre> -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 -</pre> - -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.<p> - -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 <i>null</i> grid shift file -for switching from your spherical lat/long coordinates to WGS84.<p> - -<pre> -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 -</pre> - -Note the strategic addition of <tt>+nadgrids=@null</tt> to the spherical -projection definition.<p> - -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.<p> - -<!--------------------------------------------------------------------------> - -<hr> - -Requests to add items to the frequently asked questions list -<a href="http://bugzilla.remotesensing.org/enter_bug.cgi?product=PROJ.4"> -can be entered</a> in bugzilla.<p> -</body> -</html> 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 @@ -<html> -<head> -<title>PROJ.4 - General Parameters</title> -</head> -<body BGCOLOR="#FFFFFF"> -<h1>PROJ.4 - General Parameters</h1> - -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 -<a href="http://www.remotesensing.org/geotiff/proj_list/">Projections -Transform List</a>. The definitive documentation for most parameters -is Gerald's original documentation available from the main PROJ.4 page. <p> - -<hr> -<h2><a name="false_easting_northing">False Easting/Northing</a></h2> - -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.<p> - -<hr> -<h2><a name="pm">pm - Prime Meridian</a></h2> - -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. <p> - -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 <b>cs2cs</b> does honour prime meridians but the <b>proj</b> -user utility ignores them. <p> - -The following predeclared prime meridian names are supported. These -can be listed using the cs2cs argument <b>-lm</b>.<p> -<pre> - 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 -</pre> - -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. <p> - -<pre> - cs2cs +proj=latlong +datum=WGS84 +to +proj=latlong +datum=WGS84 +pm=madrid -0 0 <i>(input)</i> -3d41'16.48"E 0dN 0.000 <i>(output)</i> -</pre> - -<hr> -<h2><a name="towgs84">towgs84 - Datum transformation to WGS84</a></h2> - -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 <b>towgs84</b> -parameter.<p> - -In the three parameter case, the three arguments are the translations to the -geocentric location in meters.<p> - -For instance, the following demonstrates converting from the Greek GGRS87 -datum to WGS84.<p> - -<pre> -% 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 -</pre> - -The EPSG database provides this example for transforming from WGS72 to WGS84 -using an approximated 7 parameter transformation.<p> -<pre> -% 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 -</pre> - -The seven parameter case uses <i>delta_x</i>, <i>delta_y</i>, <i>delta_z</i>, -<i>Rx - rotation X</i>, <i>Ry - rotation Y</i>, <i>Rz - rotation Z</i>, -<i>M_BF - Scaling</i>. 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.<p> - -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 <b>towgs84</b> transformation -(going to WGS84). The x, y and z coordinates are in geocentric coordinates. - -Three parameter transformation (simple offsets): - -<pre> - x[io] = x[io] + defn->datum_params[0]; - y[io] = y[io] + defn->datum_params[1]; - z[io] = z[io] + defn->datum_params[2]; -</pre> - -Seven parameter transformation (translation, rotation and scaling): - -<pre> - #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; -</pre> - -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.<p> - -<hr> -<h2><a name="nadgrids">nadgrids - Grid Based Datum Adjustments</a></h2> - -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.<p> - -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).<p> - -Use of grid shifts is specified using the "nadgrids" keyword in a coordinate -system definition. For example:<p> - -<pre> -% 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 -</pre> - -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. <p> - -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.<p> - -<pre> -% 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 -</pre> - -<h3>Skipping Missing Grids</h3> - -The special prefix <b>@</b> 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. <p> - -<pre> -% 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 -</pre> - -<h3>The null Grid</h3> - -A special <b>null</b> 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.<p> - -<pre> -% 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 -</pre> - -<pre> -% 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 -</pre> - -<h3>Downloading and Installing Grids</h3> - -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 -<a href="ftp://ftp.remotesensing.org/pub/proj/proj-nad27-1.1.tar.gz"> -proj-nad27-1.1.tar.gz</a>. 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 <tt>nmake /f makefile.vc nadshift</tt> command in -the <tt>proj\src</tt> directory to build and install these files. <p> - -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 -<a href="http://www.geod.nrcan.gc.ca/software/ntv2_e.php"> -http://www.geod.nrcan.gc.ca/software/ntv2_e.php</a>. After -downloading it, just dump it in the data directory with the other -installed data files (usually /usr/local/share/proj). <p> - -<h3>Caveats</h3> - -<ol> - -<li> 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.<p> - -<li> 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!<p> - -<li> 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.<p> - -<li> PROJ.4 always assumes that grids contain a shift <b>to</b> NAD83 -(essentially WGS84). Other types of grids might or might not be usable.<p> - -</ol> - -</body> -</html> - - - - - - - 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 @@ -<HTML> -<HEAD> -<!-- Send users to the new location. --> -<TITLE>redirect</TITLE> -<META HTTP-EQUIV="refresh" -CONTENT="1;URL=http://trac.osgeo.org/proj"> -</HEAD> -<BODY> -This page has moved. You will be automatically redirected to its new location. -If you aren't forwarded to the new page, -<a href="http://trac.osgeo.org/proj">click here</a>. -</BODY> -</HTML> 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 - -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<HTML><HEAD><TITLE>Man page of CS2CS</TITLE> -</HEAD><BODY> -<H1>CS2CS</H1> -Section: User Commands (1)<BR>Updated: 2000/03/21 Rel. 4.4<BR><A HREF="#index">Index</A> -<A HREF="../index.html">Return to Main Contents</A><HR> - -<A NAME="lbAB"> </A> -<H2>NAME</H2> - -cs2cs - cartographic coordinate system filter -<A NAME="lbAC"> </A> -<H2>SYNOPSIS</H2> - -<B>cs2cs</B> - -[ -<B>-eEfIlrstvwW</B> - -[ -<I>args</I> - -] ] [ -<B>+opts[=arg]</B> - -] -<BR> - -<BR> [ <B>+to</B> [<B>+opts</B>[<B>=arg</B>]] ] -file[s] -<A NAME="lbAD"> </A> -<H2>DESCRIPTION</H2> - -<I>Cs2cs</I> - -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. -<P> - -The following control parameters can appear in any order: -<DL COMPACT> -<DT><B>-I</B> - -<DD> -method to specify inverse translation, convert from <B>+to</B> coordinate -system to the primary coordinate system defined. -<DT><B>-t</B><I>a</I> - -<DD> -<I>A</I> - -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). -<DT><B>-e</B><I> string</I> - -<DD> -<I>String</I> - -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>-b,</B> - -<B>-i</B> - -or -<B>-o</B> - -options are employed, an error is returned as HUGE_VAL -value for both return values. -<DT><B>-E</B> - -<DD> -causes the input coordinates to be copied to the output line -prior to printing the converted values. -<DT><B>-l</B><I>[p|P|=|e|u|d]</I><B>id</B> - -<DD> -List projection identifiers with -<B>-l,</B> - -<B>-lp</B> - -or -<B>-lP (expanded)</B> - -that can be selected with -<B>+proj.</B> - -<B>-l=</B><I>id</I> - -gives expanded description of projection -<I>id.</I> - -List ellipsoid identifiers with -<B>-le,</B> - -that can be selected with -<B>+ellps,</B> - -<B>-lu</B> - -list of cartesian to meter conversion factors -that can be selected with -<B>+units</B> - -or -<B>-ld</B> - -list of datums that can be selected with -<B>+datum.</B> - -<DT><B>-r</B> - -<DD> -This options reverses the order of the -expected input from longitude-latitude or x-y to latitude-longitude or y-x. -<DT><B>-s</B> - -<DD> -This options reverses the order of the -output from x-y or longitude-latitude to y-x or latitude-longitude. -<DT><B>-f</B><I> format</I> - -<DD> -<I>Format</I> - -is a -<I>printf</I> - -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. -<DT><B>-[w|W]</B><I>n</I> - -<DD> -<I>N</I> - -is the number of significant fractional digits to employ for -seconds output (when the option is not specified, -<B>-w3</B> - -is assumed). -When -<B>-W</B> - -is employed the fields will be constant width and with leading zeroes. -<DT><B>-v</B> - -<DD> -causes a listing of cartographic control parameters tested for and -used by the program to be printed prior to input data. -</DL> -<P> - -The -<B>+args</B> - -run-line arguments are associated with cartographic parameters -and usage varies with projection and for a complete description see -<I>Cartographic Projection Procedures for the UNIX Environment---A User's Manual</I> - -and supplementary documentation for Release 4. -<P> - -The <I>cs2cs</I> program requires two coordinate system definitions. The -first (or primary is defined based on all projection parameters not -appearing after the <B>+to</B> argument. All projection parameters -appearing after the <B>+to</B> 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. -<P> - -Additional projection control parameters may be contained in two -auxiliary control files: -the first is optionally referenced with the -<B>+init=</B><I>file:id</I> - -and the second is always processed after the name -of the projection has been established from either the run-line -or the contents of -<B>+init</B> - -file. -The environment parameter -<B>PROJ_LIB</B> - -establishes the default directory for a file reference without -an absolute path. This is also used for supporting files like -datum shift files. -<P> - -One or more -<I>files</I> - -(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 -<I>stdin.</I> - -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. -<P> - -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 -<B>-f %.12f </B> - -for decimal degrees with 12 decimal places), while -projected (cartesian) coordinates will be in linear (meter, feet) units. - -<A NAME="lbAE"> </A> -<H2>EXAMPLE</H2> - -The following script -<DL COMPACT><DT><DD> -<BR> <TT>cs2cs +proj=latlong +datum=NAD83 -<BR> +to +proj=utm +zone=10 +datum=NAD27 -r <<EOF -<BR> 45d15'33.1"<TT> </TT>111.5W<BR> -<BR> 45d15.551666667N<TT> </TT>-111d30<BR> -<BR> +45.25919444444<TT> </TT>111d30'000w<BR> -<BR> EOF</TT> -</DL> - -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: -<DL COMPACT><DT><DD> -<BR> <TT>1402285.99 5076292.42 0.000 -</DL> - -</TT><A NAME="lbAF"> </A> -<H2>SEE ALSO</H2> - -<B><A HREF="../man1/proj.1.html">proj</A>(1),</B> - -<BR> - -<I>Cartographic Projection Procedures for the UNIX Environment---A User's Manual,</I> - -(Evenden, 1990, Open-file report 90-284). -<BR> - -<I>Map Projections Used by the U. S. Geological Survey</I> - -(Snyder, 1984, -USGS Bulletin 1532). -<BR> - -<I>Map Projections---A Working Manual</I> - -(Snyder, 1988, USGS Prof. Paper 1395). -<BR> - -<I>An Album of Map Projections</I> - -(Snyder & Voxland, 1989, USGS Prof. Paper 1453). -<A NAME="lbAG"> </A> -<H2>HOME PAGE</H2> - -<A HREF="https://github.com/OSGeo/proj.4/wiki">https://github.com/OSGeo/proj.4/wiki</A> -<P> - -<HR> -<A NAME="index"> </A><H2>Index</H2> -<DL> -<DT><A HREF="#lbAB">NAME</A><DD> -<DT><A HREF="#lbAC">SYNOPSIS</A><DD> -<DT><A HREF="#lbAD">DESCRIPTION</A><DD> -<DT><A HREF="#lbAE">EXAMPLE</A><DD> -<DT><A HREF="#lbAF">SEE ALSO</A><DD> -<DT><A HREF="#lbAG">HOME PAGE</A><DD> -</DL> -<HR> -This document was created by -<A HREF="/cgi-bin/man/man2html">man2html</A>, -using the manual pages.<BR> -Time: 20:43:10 GMT, February 18, 2016 -</BODY> -</HTML> 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 @@ -<HTML><HEAD><TITLE>Manpage of GEOD</TITLE> -</HEAD><BODY> -<H1>GEOD</H1> -Section: User Commands (1)<BR>Updated: 2000/03/21 Rel. 4.4<BR><A HREF="#index">Index</A> -<A HREF="../index.html">Return to Main Contents</A><HR> - -<A NAME="lbAB"> </A> -<H2>NAME</H2> - -geod - direct geodesic computations -<BR> - -invgeod - inverse geodesic computations -<A NAME="lbAC"> </A> -<H2>SYNOPSIS</H2> - -<B>geod</B> - -<B>+ellps=<ellipse></B> - -[ -<B>-afFIlptwW</B> - -[ -<I>args</I> - -] ] [ -<B>+args</B> - -] -file[s] -<BR> - -<B>invgeod</B> - -<B>+ellps=<ellipse></B> - -[ -<B>-afFIlptwW</B> - -[ -<I>args</I> - -] ] [ -<B>+args</B> - -] -file[s] -<A NAME="lbAD"> </A> -<H2>DESCRIPTION</H2> - -<I>Geod</I> - -(direct) and -<I>invgeod</I> - -(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). -<P> - -The following runline control parameters can appear in any order: -<DL COMPACT> -<DT><B>-I</B> - -<DD> -Specifies that the inverse geodesic computation is to be performed. -May be used with execution of -<B>goed</B> - -as an alternative to -<B>invgeod</B> - -execution. -<DT><B>-a</B> - -<DD> -Latitude and longitudes of the initial and terminal points, -forward and back azimuths and distance are output. -<DT><B>-t</B><I>a</I> - -<DD> -<I>A</I> - -specifies a character employed as the first character to denote -a control line to be passed through without processing. -<DT><B>-le</B> - -<DD> -Gives a listing of all the ellipsoids that may be selected with the -<B>+ellps=</B> - -option. -<DT><B>-lu</B> - -<DD> -Gives a listing of all the units that may be selected with the -<B>+units=</B> - -option. -<DT><B>-[f|F]</B><I> format</I> - -<DD> -<I>Format</I> - -is a -<I>printf</I> - -format string to control the output form of the geographic coordinate values -(<B>f</B>) or distance value (<B>F</B>). -The default mode is DMS for geographic coordinates and "%.3f" for distance. -<DT><B>-[w|W]</B><I>n</I> - -<DD> -<I>N</I> - -is the number of significant fractional digits to employ for -seconds output (when the option is not specified, -<B>-w3</B> - -is assumed). -When -<B>-W</B> - -is employed the fields will be constant width with leading zeroes. -<DT><B>-p</B> - -<DD> -This option causes the azimuthal values to be output as unsigned -DMS numbers between 0 and 360 degrees. Also note -f. -</DL> -<P> - -The -<B>+args</B> - -run-line arguments are associated with geodetic parameters -for specifying the ellipsoidal or sphere to use. -See -<B>proj</B> - -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. -<P> - -One or more -<I>files</I> - -(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 -<I>stdin.</I> - -<P> - -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. -<P> - -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 -<B>-f</B> - -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. -<P> - -The Earth's ellipsoidal figure may be selected in the same -manner as program -<B>proj</B> - -by using -<B>+ellps=, +a=, +es=,</B> - -etc. -<P> - -<I>Geod</I> - -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 -<B>+lat_1=</B><I>lat</I> - -and -<B>+lon_1=</B><I>lon</I> - -parameters and either a terminus point -<B>+lat_2=</B><I>lat</I> - -and -<B>+lon_2=</B><I>lon</I> - -or a distance and azimuth from the initial point with -<B>+S=</B><I>distance</I> - -and -<B>+A=</B><I>azimuth</I> - -must be specified. -<P> - -If points along a geodesic are to be determined then either -<B>+n_S=</B><I>integer</I> - -specifying the number of intermediate points and/or -<B>+del_S=</B><I>distance</I> - -specifying the incremental distance between points must be specified. -<P> - -To determine points along an arc equidistant from the initial point both -<B>+del_A=</B><I>angle</I> - -and -<B>+n_A=</B><I>integer</I> - -must be specified which determine the respective angular increments -and number of points to be determined. - -<A NAME="lbAE"> </A> -<H2>EXAMPLE</H2> - -The following script determines the geodesic azimuths and distance in -U.S. stature miles from Boston, MA, to Portland, OR: -<DL COMPACT><DT><DD> -<BR> <TT>geod +ellps=clrk66 <<EOF -I +units=us-mi -<BR> 42d15'N 71d07'W 45d31'N 123d41'W -<BR> EOF</TT> -</DL> - -which gives the results: -<DL COMPACT><DT><DD> -<BR> <TT>-66d31'50.141" 75d39'13.083" 2587.504 -</DL> - -where the first two values are the -azimuth from Boston to Portland, the back azimuth from Portland to -Boston followed by the distance. -<P> - -An example of forward geodesic use is to use the Boston location and determine -Portland's location by azimuth and distance: -<DL COMPACT><DT><DD> -<BR> geod +ellps=clrk66 <<EOF +units=us-mi -<BR> 42d15'N 71d07'W -66d31'50.141" 2587.504 -<BR> EOF</TT> -</DL> - -which gives: -<DL COMPACT><DT><DD> -<BR> <TT>45d31'0.003"N 123d40'59.985"W 75d39'13.094"</TT> -</DL> - -Note: lack of precision in the distance value compromises -the precision of the Portland location. -<A NAME="lbAF"> </A> -<H2>SEE ALSO</H2> - -Thomas, P.D., 1970, -<I>Spheroidal Geodesics, Reference Systems & Local Geometry:</I> - -U.S. Naval Oceanographic Office, S-138. -<A NAME="lbAG"> </A> -<H2>HOME PAGE</H2> - -<A HREF="http://www.remotesensing.org/proj">http://www.remotesensing.org/proj</A> -<P> - -<HR> -<A NAME="index"> </A><H2>Index</H2> -<DL> -<DT><A HREF="#lbAB">NAME</A><DD> -<DT><A HREF="#lbAC">SYNOPSIS</A><DD> -<DT><A HREF="#lbAD">DESCRIPTION</A><DD> -<DT><A HREF="#lbAE">EXAMPLE</A><DD> -<DT><A HREF="#lbAF">SEE ALSO</A><DD> -<DT><A HREF="#lbAG">HOME PAGE</A><DD> -</DL> -<HR> -This document was created by -<A HREF="http://localhost/cgi-bin/man/man2html">man2html</A>, -using the manual pages.<BR> -Time: 13:14:56 GMT, October 14, 2005 -</BODY> -</HTML> 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 @@ -<HTML><HEAD><TITLE>Manpage of PJ_INIT</TITLE> -</HEAD><BODY> -<H1>PJ_INIT</H1> -Section: Misc. Reference Manual Pages (3U)<BR>Updated: 2001/04/05 Rel. 4.4<BR><A HREF="#index">Index</A> -<A HREF="../index.html">Return to Main Contents</A><HR> - - - -<A NAME="lbAB"> </A> -<H2>NAME</H2> - -pj_init - initialize cartographic projection -<BR> - -pj_init_plus - initialize cartographic projection -<BR> - -pj_fwd - forward cartographic projection -<BR> - -pj_inv - inverse cartographic projection -<BR> - -pj_transform - transform between coordinate systems -<BR> - -pj_free - de-initialize projection -<A NAME="lbAC"> </A> -<H2>SYNOPSIS</H2> - -<PRE> -#include <<A HREF="file:/usr/include/proj_api.h">proj_api.h</A>> - -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) - -</PRE><A NAME="lbAD"> </A> -<H2>DESCRIPTION</H2> - -Procedure <B>pj_init</B> selects and initializes a cartographic projection -with its argument control parameters. -<B>Argc</B> is the number of elements in the array of control strings -<B>argv</B> that each contain individual cartographic control keyword -assignments (<TT>+</TT> <B>proj</B> arguments). -The list must contain at least the <B>proj=</B><I>projection</I> and -Earth's radius or elliptical parameters. -If the initialization of the projection is successful a valid -address is returned otherwise a NULL value. -<P> -The <B>pj_init_plus</B> function operates similarly to <B>pj_init</B> but -takes a single string containing the definition, with each parameter -prefixed with a plus sign. For example "+proj=utm +zone=11 +ellps=WGS84". -<P> -Once initialization is performed either forward or inverse -projections can be performed with the returned value of <B>pj_init</B> -used as the argument <B>proj</B>. -The argument structure <B>projUV</B> values <B>u</B> and <B>v</B> contain -respective longitude and latitude or x and y. -Latitude and longitude are in radians. -If a projection operation fails, both elements of <B>projUV</B> are -set to HUGE_VAL (defined in <I>math.h</I>). -<P> -<B>Note:</B> 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 -<I>inv</I> will be NULL. -<P> -The <B>pj_transform</B> 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 <B>pj_fwd</B> and <B>pj_inv</B> it is also allowable -for the coordinate system definitions (<B>PJ *</B>) to be geographic coordinate -systems (defined as +proj=latlong). The <B>x</B>, <B>y</B> and <B>z</B> 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. -<P> -Memory associated with the projection may be freed with <B>pj_free</B>. -<A NAME="lbAE"> </A> -<H2>EXAMPLE</H2> - -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: -<PRE> -<TT> -#include <<A HREF="file:/usr/include/proj_api.h">proj_api.h</A>> - -main(int argc, char **argv) { - char *args[] = { "proj=merc", "ellps=clrk66", "lat_ts=33" }; - projUV p; - projPJ pj; - - if (!(pj = pj_init(3, args))) - <A HREF="../man1/exit.1.html">exit</A>(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); -} </TT> -<BR> -</PRE> - -<A NAME="lbAF"> </A> -<H2>LIBRARY</H2> - -libproj.a - library of projections and support procedures -<A NAME="lbAG"> </A> -<H2>SEE ALSO</H2> - -<B><A HREF="../man1U/proj.1U.html">proj</A>(1U),</B> - -<BR> - -<I>Cartographic Projection Procedures for the UNIX Environment---A User's Manual,</I> - -(Evenden, 1990, Open-file report 90-284). -<A NAME="lbAH"> </A> -<H2>HOME PAGE</H2> - -<A HREF="http://www.remotesensing.org/proj">http://www.remotesensing.org/proj</A> -<P> -<P> - -<HR> -<A NAME="index"> </A><H2>Index</H2> -<DL> -<DT><A HREF="#lbAB">NAME</A><DD> -<DT><A HREF="#lbAC">SYNOPSIS</A><DD> -<DT><A HREF="#lbAD">DESCRIPTION</A><DD> -<DT><A HREF="#lbAE">EXAMPLE</A><DD> -<DT><A HREF="#lbAF">LIBRARY</A><DD> -<DT><A HREF="#lbAG">SEE ALSO</A><DD> -<DT><A HREF="#lbAH">HOME PAGE</A><DD> -</DL> -<HR> -This document was created by -<A HREF="http://localhost/cgi-bin/man/man2html">man2html</A>, -using the manual pages.<BR> -Time: 13:14:22 GMT, October 14, 2005 -</BODY> -</HTML> 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 - -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<HTML><HEAD><TITLE>Man page of PROJ</TITLE> -</HEAD><BODY> -<H1>PROJ</H1> -Section: User Commands (1)<BR>Updated: 2000/03/21 Rel. 4.4<BR><A HREF="#index">Index</A> -<A HREF="../index.html">Return to Main Contents</A><HR> - -<A NAME="lbAB"> </A> -<H2>NAME</H2> - -proj - forward cartographic projection filter -<BR> - -invproj - inverse cartographic projection filter -<A NAME="lbAC"> </A> -<H2>SYNOPSIS</H2> - -<B>proj</B> - -[ -<B>-bceEfiIlmorsStTvVwW</B> - -[ -<I>args</I> - -] ] [ -<B>+args</B> - -] -file[s] -<BR> - -<B>invproj</B> - -[ -<B>-bceEfiIlmorsStTwW</B> - -[ -<I>args</I> - -] ] [ -<B>+args</B> - -] -file[s] -<A NAME="lbAD"> </A> -<H2>DESCRIPTION</H2> - -<I>Proj</I> - -and -<I>invproj</I> - -perform respective forward and inverse transformation of cartographic data -to or from cartesian data with a wide range of selectable projection functions. -<P> - -The following control parameters can appear in any order: -<DL COMPACT> -<DT><B>-b</B> - -<DD> -Special option for binary coordinate data input and output -through standard input and standard output. -Data is assumed to be in system type -<I>double</I> - -floating point words. -This option is to be used when -<B>proj</B> - -is a -<I>son</I> - -process and allows bypassing formatting operations. -<DT><B>-i</B> - -<DD> -Selects binary input only (see -<B>-b option).</B> - -<DT><B>-I</B> - -<DD> -alternate method to specify inverse projection. -Redundant when used with -<B>invproj.</B> - -<DT><B>-o</B> - -<DD> -Selects binary output only (see -<B>-b option).</B> - -<DT><B>-t</B><I>a</I> - -<DD> -<I>A</I> - -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). -<DT><B>-e</B><I> string</I> - -<DD> -<I>String</I> - -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>-b,</B> - -<B>-i</B> - -or -<B>-o</B> - -options are employed, an error is returned as HUGE_VAL -value for both return values. -<DT><B>-E</B> - -<DD> -causes the input coordinates to be copied to the output line -prior to printing the converted values. -<DT><B>-l</B><I>[p|P|=|e|u|d]</I><B>id</B> - -<DD> -List projection identifiers with -<B>-l,</B> - -<B>-lp</B> - -or -<B>-lP (expanded)</B> - -that can be selected with -<B>+proj.</B> - -<B>-l=</B><I>id</I> - -gives expanded description of projection -<I>id.</I> - -List ellipsoid identifiers with -<B>-le,</B> - -that can be selected with -<B>+ellps,</B> - -<B>-lu</B> - -list of cartesian to meter conversion factors -that can be selected with -<B>+units</B> - -or -<B>-ld</B> - -list of datums that can be selected with -<B>+datum.</B> - -<DT><B>-r</B> - -<DD> -This options reverses the order of the -expected input from longitude-latitude or x-y to latitude-longitude or y-x. -<DT><B>-s</B> - -<DD> -This options reverses the order of the -output from x-y or longitude-latitude to y-x or latitude-longitude. -<DT><B>-S</B> - -<DD> -Causes estimation of -<I>meridional</I> - -and -<I>parallel</I> - -scale factors, -<I>area</I> - -scale factor and -<I>angular distortion,</I> - -and -<I>maximum</I> - -and -<I>minimum</I> - -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. -<DT><B>-m</B><I> mult</I> - -<DD> -The cartesian data may be scaled by the -<I>mult</I> - -parameter. -When processing data in a forward projection mode the -cartesian output values are multiplied by -<I>mult</I> - -otherwise the input cartesian values are divided by -<I>mult</I> - -before inverse projection. -If the first two characters of -<I>mult</I> - -are 1/ or 1: then the reciprocal value of -<I>mult</I> - -is employed. -<DT><B>-f</B><I> format</I> - -<DD> -<I>Format</I> - -is a -<I>printf</I> - -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. -<DT><B>-[w|W]</B><I>n</I> - -<DD> -<I>N</I> - -is the number of significant fractional digits to employ for -seconds output (when the option is not specified, -<B>-w3</B> - -is assumed). -When -<B>-W</B> - -is employed the fields will be constant width and with leading zeroes. -<DT><B>-v</B> - -<DD> -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 -<B>-T</B> - -option. -<DT><B>-V</B> - -<DD> -This option causes an expanded annotated listing of the characteristics -of the projected point. -<B>-v is implied with this option.</B> - -<DT><B>-T</B><I> ulow,uhi,vlow,vhi,res[,umax,vmax]</I> - -<DD> -This option creates a set of bivariate Chebyshev polynomial -coefficients that approximate the selected cartographic projection on -<I>stdout.</I> - -The values -<I>low</I> - -and -<I>hi</I> - -denote the range of the input where the -<I>u</I> - -or -<I>v</I> - -prefixes apply to respective longitude-x or latitude-y -depending upon whether a forward or inverse projection is selected. -<I>Res</I> - -is an integer number specifying the power of 10 precision of the -approximation. -For example, a -<I>res</I> - -of -3 specifies an approximation with an accuracy better than .001. -<I>Umax,</I> - -and -<I>vmax</I> - -specify maximum degree of the polynomials (default: 15). -See also: -<B><A HREF="../man1/fproj.1.html">fproj</A>(1).</B> - -</DL> -<P> - -The -<B>+args</B> - -run-line arguments are associated with cartographic parameters -and usage varies with projection and for a complete description see -<I>Cartographic Projection Procedures for the UNIX Environment---A User's Manual</I> - -and supplementary documentation for Release 4. -<P> - -Additional projection control parameters may be contained in two -auxiliary control files: -the first is optionally referenced with the -<B>+init=</B><I>file:id</I> - -and the second is always processed after the name -of the projection has been established from either the run-line -or the contents of -<B>+init</B> - -file. -The environment parameter -<B>PROJ_LIB</B> - -establishes the default directory for a file reference without -an absolute path. This is also used for supporting files like -datum shift files. -<P> - -One or more -<I>files</I> - -(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 -<I>stdin.</I> - -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. -<P> - -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 -<B>-w</B> - -switch is not employed) and precise to 0.001" -with trailing, zero-valued minute-second fields deleted. -<A NAME="lbAE"> </A> -<H2>EXAMPLE</H2> - -The following script -<DL COMPACT><DT><DD> -<BR> <TT>proj +proj=utm +lon_0=112w +ellps=clrk66 -r <<EOF -<BR> 45d15'33.1"<TT> </TT>111.5W<BR> -<BR> 45d15.551666667N<TT> </TT>-111d30<BR> -<BR> +45.25919444444<TT> </TT>111d30'000w<BR> -<BR> EOF</TT> -</DL> - -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: -<DL COMPACT><DT><DD> -<BR> <TT>460769.27<TT> </TT>5011648.45<BR> -</DL> - -</TT><A NAME="lbAF"> </A> -<H2>OTHER PROGRAMS</H2> - -<P> - -The <I>proj</I> program is limited to converting between geographic and -projection coordinates within one datum. -<P> - -The <I>cs2cs</I> program operates -similarly, but allows translation between any pair of definable coordinate -systems, including support for datum translation. -<P> - -The <I>geod</I> program provides the ability to compute geodesic (Great -Circle) computations. -<A NAME="lbAG"> </A> -<H2>SEE ALSO</H2> - -<B><A HREF="../man1/cs2cs.1.html">cs2cs</A>(1), <A HREF="../man1/geod.1.html">geod</A>(1), <A HREF="../man3/pj_init.3.html">pj_init</A>(3),</B> - -<BR> - -<I>Cartographic Projection Procedures for the UNIX Environment---A User's Manual,</I> - -(Evenden, 1990, Open-file report 90-284). -<BR> - -<I>Map Projections Used by the U. S. Geological Survey</I> - -(Snyder, 1984, -USGS Bulletin 1532). -<BR> - -<I>Map Projections---A Working Manual</I> - -(Snyder, 1988, USGS Prof. Paper 1395). -<BR> - -<I>An Album of Map Projections</I> - -(Snyder & Voxland, 1989, USGS Prof. Paper 1453). -<A NAME="lbAH"> </A> -<H2>HOME PAGE</H2> - -<A HREF="https://github.com/OSGeo/proj.4/wiki">https://github.com/OSGeo/proj.4/wiki</A> -<P> - -<HR> -<A NAME="index"> </A><H2>Index</H2> -<DL> -<DT><A HREF="#lbAB">NAME</A><DD> -<DT><A HREF="#lbAC">SYNOPSIS</A><DD> -<DT><A HREF="#lbAD">DESCRIPTION</A><DD> -<DT><A HREF="#lbAE">EXAMPLE</A><DD> -<DT><A HREF="#lbAF">OTHER PROGRAMS</A><DD> -<DT><A HREF="#lbAG">SEE ALSO</A><DD> -<DT><A HREF="#lbAH">HOME PAGE</A><DD> -</DL> -<HR> -This document was created by -<A HREF="/cgi-bin/man/man2html">man2html</A>, -using the manual pages.<BR> -Time: 20:44:57 GMT, February 18, 2016 -</BODY> -</HTML> diff --git a/html/proj_logo.png b/html/proj_logo.png Binary files differdeleted file mode 100644 index 92d5acb6..00000000 --- a/html/proj_logo.png +++ /dev/null |
