Your message dated Tue, 2 Jun 2009 20:22:20 +0200
with message-id <>
and subject line Fixed in 4.6.1
has caused the Debian Bug report #514904,
regarding proj: Examples in man page and readme broken, in one case due to 
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: proj
Version: 4.6.0-2
Severity: normal


I'm having trouble with the examples from the man page and your 
README.Debian.  First, "man cs2cs" suggests:

             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

The problem with this is the curly-quote character in the first and last 
data lines (which may or may not reach you depending on how 
unicode-friendly everything between me and you is).  The curly-quote 
character is not present in the man page source so presumably it's a 
result of man being "clever".  My guess is that there is some way to 
escape the character so that it is not munged but I'm not enough of a 
man expert to know how to do it.  cs2cs doesn't report an error when it 
gets this input; it just produces wrong output.  That in itself is 
probably a bug.

Having fixed that, I'm still getting the wrong answer:

$ cs2cs +proj=latlong +datum=NAD83 +to +proj=utm +zone=10 +datum=NAD27 -r
45d15'33.1"   111.5W
1402224.58      5076275.42 -0.00

The output that the man page says I should get is:
1402285.99      5076292.42 0.000

Maybe the examples from README.Debian will give a clue:

$ cs2cs +proj=latlong +datum=NAD27 +to +proj=latlong +datum=NAD83 
-117 30
117dW   30dN 0.000

So this conversion from NAD27 to NAD83 has changed nothing, which is 
clearly wrong, and I guess that the error in the previous example could 
also be due to a 27/83 mixup.

With nad2nad I get a more explicit error:

$ nad2nad -i 83 -o 27 -r conus
Rel. 4.6.0, 21 Dec 2007
datum file: conus, failed: no system list, errno: 2

program abnormally terminated

Any ideas what's going on?

Cheers,  Phil.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.21-1-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages proj depends on:
ii  libc6                         2.7-5      GNU C Library: Shared libraries

proj recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Package: proj
Version: 4.6.1-1

The complete datum shifts have been added to proj.

Francesco P. Lovergine

--- End Message ---
Pkg-grass-devel mailing list

Reply via email to