% cvs -d :pserver:anonymous@cvs.remotesensing.org:/cvsroot login Password: anonymous % cvs -d :pserver:anonymous@cvs.remotesensing.org:/cvsroot co proj ...The following files are available from the proj ftp directory:
This mailing list is for development and user discussions of the PROJ.4 library.
To subscribe send mail to majordomo@remotesensing.org, with no subject. In the body type:
subscribe osrs-proj
To unsubscribe send mail to majordomo@remotesensing.org, with no subject, and in the body type:
unsubscribe osrs-proj
To post an email to this list, send email to: osrs-proj@remotesensing.org. To review previous posts visit the web archive.
Bugs can be entered and can be viewed in BugZilla.
Since work started on the PROJ.4.4.x series of releases, various bux fixes have been incorporated, and the build system has been overhauled to use autoconf/libtool. Support has also been added for 3 and 7 parameter datum shifts, the PJ* structure now also carries datum information and PJ* can be considered a full coordinate system (geographic coordinate systems are also now supported with the +proj=latlong pseudo-projection). The new cs2cs program performs a similar function to the proj program, but transforming from any one coordinate system to another. The new pj_transform() is used to access the extended coordinate system to coordinate system transformation with datum shifting. A mapping file (epsg) has also been introduced mapping most EPSG ( www.epsg.org) coordinate systems to PROJ.4 format.
Future plans for PROJ.4 will hopefully include better online documentation, refinement of datum shifting support and extension of the external programming API for greater convenience in handling coordinate systems from applications.
If you are a user of PROJ.4, and/or are interested in contributing please drop me a line and join the mailing list.
All source, data files and other contents of the PROJ.4 package are available under the following terms. Note that the PROJ 4.3 and earlier was "public domain" as is common with US government work, but apparently this is not a well defined legal term in many countries. I am placing everything under the following MIT style license because I believe it is effectively the same as public domain, allowing anyone to use the code as they wish, including making proprietary derivatives.
Though I have put my own name as copyright holder, I don't mean to imply I did the work. Essentially all work was done by Gerald Evenden.
-------------- Copyright (c) 2000, Frank Warmerdam Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.