[Proj] How does the datum "NAD27 Michigan" work?
Mikael.Rittri at carmenta.com
Mon May 7 03:05:08 EST 2012
> Option (a) is the desired intent.
> [ ... ]
> This is essentially a scale factor correction for grid to ground distances.
> Minnesota does this on a county-by-county basis; Colombia does city-by-city.
Aha, so that's the explanation for things like
They have confused me, too.
Thank you very much,
From: proj-bounces at lists.maptools.org [mailto:proj-bounces at lists.maptools.org] On Behalf Of Clifford J Mugnier
Sent: den 4 maj 2012 17:09
To: PROJ.4 and general Projections Discussions
Subject: Re: [Proj] How does the datum "NAD27 Michigan" work?
Option (a) is the desired intent. This is an attempt to translate between GIS pros and Cadastral pros. Many GIS pros back then were not aware of using the Gaussian Sphere to implement the "Sea Level Correction" muchless go above the ellipsoid to the surface. Minnesota does this on a county-by-county basis; Colombia does city-by-city. This is essentially a scale factor correction for grid to ground distances.
Sent from Cliff Mugnier's iPhone
On May 4, 2012, at 5:19, "Mikael Rittri" <Mikael.Rittri at carmenta.com<mailto:Mikael.Rittri at carmenta.com>> wrote:
I am trying to understand the "NAD27 Michigan" datum, EPSG:6268.
As represented in EPSG, this is a datum distinct from NAD27,
and uses the ellipsoid "Clarke 1866 Michigan".
"Ellipsoid taken to be 800 ft above the NAD27 reference ellipsoid."
The information source (J. P. Snyder. Map Projections: A Working Manual, p. 56, note 1)
is more precise:
"The major and minor axes of the ellipsoid are taken at exactly 1.0000382 times those
of the Clarke 1866, for Michigan only. This incorporates an average elevation throughout
the State of about 800 ft, with limited variation."
Neither EPSG nor Snyder gives any datum shift for NAD 27 Michigan.
However, the Michigan Department of Natural Resources just writes:
Ellipsoid: Modified Clarke, 1866
where the ellipsoid turns out to be the same as "Clarke 1866 Michigan".
So it seems that Michiganders regard the datum NAD27 Michigan to be the same as NAD27:
it is not an adjustment or densification or whatever, it just has a different ellipsoid.
But this can be interpreted in two ways:
a) that long/lat are the same in both datums,
b) or that geocentric Cartesian coordinates X,Y,Z are the same in both datums.
If a) is intended, then a correct datum shift for NAD27 Michigan could use the CONUS
grid shift file intended for NAD27.
And if b) is intended, then the 3-parameter shift between NAD27 Michigan
and NAD27 would be 0,0,0.
These interpretations are not quite equivalent.
I've tried out b) in Proj.4, by setting identical towgs84 parameters for both datums.
(These are not very accurate, but since they are the same on both sides, they should
cancel each other and give a 0,0,0 shift between NAD 27 Michigan and NAD27.)
>cs2cs +proj=longlat +a=6378450.0475 +b=6356826.6215 +towgs84=-9,161,179 +to +proj=longlat +ellps=clrk66 +towgs84=-9,161,179
-85 45 0
85dW 44d59'59.973"N 243.235
So, the point at the ellipsoid surface of NAD27 Michigan is 243.235 m = 798 feet
above the NAD27 ellipsoid, as expected. What surprised me is the latitude
shift of 0.027" = 0.83 meters. Well, I think understand where it comes from: the
line that is perpendicular to the ellipsoid surfaces doesn't go through the ellipsoid
center(s). But the effect is much larger than I would have thought.
So, does anyone know whether a) or b) or something else is the correct interpretation?
Proj mailing list
Proj at lists.maptools.org<mailto:Proj at lists.maptools.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Proj