[Proj] The Michigan Georef Projection Problem
ed at topozone.com
Sat Dec 18 12:05:25 EST 2004
This problem first came up on the MapServer users list, and I pointed
out that since the usage seemed to be correct, the most likely cause was
an incorrect set of parameters for the (correctly-implemented)
projection, or an incorrect expression of those parameters in the input
to proj. I have some time later this weekend to take a look at this
user's specific situation; the problem came up once before with another
MapServer users (same Michigan projection) but was never resolved.
I'll post whatever I find, but at the moment I don't have any reason to
think there's any issues with the omerc code. Thanks!
President and Chief Mapmaker
TopoZone.com / Maps a la carte, Inc.
73 Princeton Street, Suite 305
North Chelmsford, MA 01863
Phone: +1 978 251-4242 Fax: +1 978 251-1396
From: proj-bounces at xserve.flids.com
[mailto:proj-bounces at xserve.flids.com] On Behalf Of Gerald Evenden
Sent: Saturday, December 18, 2004 10:48 AM
To: Proj List List
Subject: Re: [Proj] The Michigan Georef Projection Problem
I realize that my definition of 'proj' may not agree with its usage in
this thread but I am curious what is meant by "need to work on Proj". I
went though a good deal of rework on omerc some time ago and felt that
the projection was a properly functioning version of Hotine's oblique
If there are problems with omerc I would appreciate hearing about them
along with specifics about its alleged failure. If there is a fix, I
would appreciate knowing about that also.
Jerry and the low riders: Daisy Mae and Joshua.
"The whole religious complexion of the modern world is due to the
absence from Jerusalem of a lunatic asylum." Havelock Ellis, 1914
Proj mailing list
Proj at xserve.flids.com
More information about the Proj