Click here to get back home

How to properly specify NAD27 datum

 HomeNewsGroups | Search | About
 comp.infosystems.gis    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content
Subject Author Date
How to properly specify NAD27 datum Dave Patton 08-26-2004
Get Chitika Premium
Posted by Dave Patton on August 26, 2004, 9:02 pm
Please log in for more thread options
I'm looking for comments from 'the experts' about the following.

This page:
http://www.internationalboundarycommission.org/coordinates/M49thp.txt
lists the "NAD27 Official Values" for section M of the Canada/USA
border, as published by the Internation Boundary Commission(IBC).

Via email, I had asked the IBC to clarify in which variation of
NAD27 those coordinates were expressed.

The IBC replied that they didn't understand my question. I explained
further, saying that from other wording in their email I took it
to mean that they used NAD27 CONUS, but I wanted to confirm that,
and suggested they update their coordinate lists to provide such
information.

In my email I had pointed out that there are regional variants of
NAD27, such as NAD27 Alaska, NAD27 Canada, NAD27 Cuba,
NAD27 Canada - Alberta and British Columbia, NAD27 CONUS, etc.

The most recent email from the IBC stated:
"The variations that you speak of, have nothing to do with how
coordinates are published. That is just something that GPS and
GIS system manufacturers came up with. The purpose was to make it
easier for your handheld or gis software to transform from one
datum to another or one coordinate system to another, but as far
as I have seen no one publishes their NAD 27 coordinates the way
you describe."

It was my 'understanding of things' that coordinates are useless
without knowing in which datum they are expressed, either by
an explicit statement of the datum, or by implication. I am
aware that in many applications the difference between using
one datum or another may not make any practical difference, but
I'm talking about the theoretical difference.

So, my question is, who is correct?
Thanks

--
Dave Patton
Canadian Coordinator, Degree Confluence Project
http://www.confluence.org/
My website: http://members.shaw.ca/davepatton/


Posted by Melita Kennedy on August 26, 2004, 7:40 pm
Please log in for more thread options
>This page:
>http://www.internationalboundarycommission.org/coordinates/M49thp.txt
>lists the "NAD27 Official Values" for section M of the Canada/USA
>border, as published by the Internation Boundary Commission(IBC).
>
>Via email, I had asked the IBC to clarify in which variation of
>NAD27 those coordinates were expressed.
>
>The IBC replied that they didn't understand my question. I explained
>further, saying that from other wording in their email I took it
>to mean that they used NAD27 CONUS, but I wanted to confirm that,
>and suggested they update their coordinate lists to provide such
>information.
>
>In my email I had pointed out that there are regional variants of
>NAD27, such as NAD27 Alaska, NAD27 Canada, NAD27 Cuba,
>NAD27 Canada - Alberta and British Columbia, NAD27 CONUS, etc.
>
>The most recent email from the IBC stated:
>"The variations that you speak of, have nothing to do with how
>coordinates are published. That is just something that GPS and
>GIS system manufacturers came up with. The purpose was to make it
>easier for your handheld or gis software to transform from one
>datum to another or one coordinate system to another, but as far
>as I have seen no one publishes their NAD 27 coordinates the way
>you describe."
>
>It was my 'understanding of things' that coordinates are useless
>without knowing in which datum they are expressed, either by
>an explicit statement of the datum, or by implication. I am
>aware that in many applications the difference between using
>one datum or another may not make any practical difference, but
>I'm talking about the theoretical difference.

Dave,

The NMEA standard (used in GPS devices) uses datum names that
hard-code a particular transformation method and parameters.
These datum names came originally from the Defense Mapping
Agency, currently part of NGA. Thus you get NAS-A, NAS-B or
variations where NAS = NAD27 and the final letter stands for
a transformation that is designed for a particular area of
use.

ArcInfo workstation from ESRI uses the same methodology. It
supports a keyword, NAD27, which uses the NADCON conus grid
to convert to NAD83. NAS_A (aka NAS-A) uses a three parameter,
molodensky transformation method.

I work for ESRI and have concentrated on map projections and
datums for the 10 years that I've been there. When we
designed a new 'projection engine' which could be used in
more of our software products, we split the transformation
information from the datum (geographic coordinate system)
information. Data is defined on a particular datum, like
NAD27. It's only when you need to compare it or transform
it to another datum, that a transformation becomes necessary.

So, I would say that the IBC is incorrect when they say no
one publsihes their NAD27 coordinates in the manner you
described. Certainly, ArcInfo workstation (and coverages,
GRIDs and TINs) uses this methodology, and so do most GPS
devices that support the NMEA standard.

Melita Kennedy
(posting from home, after spending two days trying to
return from vacation. If I made a mistake in this e-mail
I'm going to blame the airlines!)



Posted by Chuck Taylor on August 26, 2004, 9:49 pm
Please log in for more thread options
wrote:

>I'm looking for comments from 'the experts' about the following.


I'm not an expert, but I play one on Usenet. Perhaps Prof. Mugnier
will chime in and give you a better answer than mine.


>This page:
>http://www.internationalboundarycommission.org/coordinates/M49thp.txt
>lists the "NAD27 Official Values" for section M of the Canada/USA
>border, as published by the Internation Boundary Commission(IBC).
>
>Via email, I had asked the IBC to clarify in which variation of
>NAD27 those coordinates were expressed.
>
>The IBC replied that they didn't understand my question. I explained
>further, saying that from other wording in their email I took it
>to mean that they used NAD27 CONUS, but I wanted to confirm that,
>and suggested they update their coordinate lists to provide such
>information.
>
>In my email I had pointed out that there are regional variants of
>NAD27, such as NAD27 Alaska, NAD27 Canada, NAD27 Cuba,
>NAD27 Canada - Alberta and British Columbia, NAD27 CONUS, etc.


There's only one NAD27. But there are different techniques, and
different sets of parameters, for converting NAD27 coordinates to
another datum and vice-versa.

The names you mentioned above designate sets of transformation
parameters used with the 3-parameter Molodensky method to transform
points between NAD27 and WGS84. Molodensky isn't terribly accurate,
but it's the most widely used technique. Those names refer to
best-fit approximations for the regions they describe when using
Molodensky.

It doesn't help much that practitioners and agencies often refer to
these different sets of transformation parameters as datums, even
though they are *not* datums but *parameters that are input to a
transformation algorithm*. Even though the sets you listed are all
different, they all serve to relate *one* datum, NAD27, to the
reference datum, which in this case happens to be WGS84.

As an example of alternative techniques, Canada publishes NTv2, and
the U.S. publishes NADCON and CORPSCON, all of which transform points
between NAD27 and NAD83 with substantially higher accuracy than
Molodensky. These tools don't use the same parameters as Molodensky;
they use grid files and interpolation instead.

For a high-accuracy transform from NAD83 to WGS84 (or one of the
ITRFs) and vice-versa, there's HTDP. It uses yet another method.

See
<URL:http://home.hiwaay.net/~taylorc/bookshelf/math-science/geodesy/datum/transform/high-accuracy/>
(note the URL will probably wrap in your reader).


>The most recent email from the IBC stated:
>"The variations that you speak of, have nothing to do with how
>coordinates are published. That is just something that GPS and
>GIS system manufacturers came up with. The purpose was to make it
>easier for your handheld or gis software to transform from one
>datum to another or one coordinate system to another, but as far
>as I have seen no one publishes their NAD 27 coordinates the way
>you describe."


Not exactly. The U.S. Defense Mapping Agency (later NIMA, now NGA)
originated and published those regional parameters to work with the
Molodensky transformation and WGS84.

See <URL:http://earth-info.nga.mil/GandG/datums/dtp/index.html>. (NGA
is also guilty of confusing datums and transformation parameters.)

The IBC is right, however, in that there's only one way to express a
point's geographic coordinates in NAD27 (notwithstanding formatting
options like decimals vs minutes and seconds, of course).


>It was my 'understanding of things' that coordinates are useless
>without knowing in which datum they are expressed, either by
>an explicit statement of the datum, or by implication. I am
>aware that in many applications the difference between using
>one datum or another may not make any practical difference, but
>I'm talking about the theoretical difference.
>
>So, my question is, who is correct?
>Thanks


IBC used NAD27, of which there is only one. If you decide to
transform those points to another datum, you'll have to choose the
method you want to use. If you choose Molodensky to transform them to
WGS84, you'll want to choose the set of parameters that offers the
best compromise between accuracy and coverage of the region in which
you're interested.

Hope that helps.


--
Chuck Taylor
http://home.hiwaay.net/~taylorc/contact/


Similar ThreadsPosted
NAD83 > NAD27 CONUS conversion problems May 12, 2005, 4:33 pm
Gis Query about Datum and Projection. February 22, 2005, 9:22 pm
Error from unknown datum August 29, 2005, 6:42 pm
Re: Converting co-ordinates from one datum to an other? July 20, 2006, 1:46 pm
USGS DLG encoded with wrong datum? May 17, 2004, 3:58 pm
georeferencing a raster in ArcMAp and transforming datum September 26, 2005, 7:19 am
Conversion WGS84 to East Timor Local Datum (1967) January 19, 2005, 8:18 pm

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap