<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Agree wholeheartedly! Even Gerald Evenden would agree, I guess:
separate projections from datums and you get a much clearer viewof the
process. Pity he isn't on this list any more. Projections are about
getting data from an ellipsoid on to a flat surface, datums are about
translating and rotating the ellipsoid itself. I completely agree with
Cliff that the user should know what he/she is doing.<br>
<br>
Jan<br>
<br>
Dr. J. Hartmann<br>
Department of Geography<br>
University of Amsterdam<br>
<br>
Clifford J Mugnier wrote:
<blockquote
cite="mid:B597ADFC46B67741B18EA6AA13613FF7EC2657@email002.lsu.edu"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.6000.16809" name="GENERATOR">
<style>
<!--
font-face
        {font-family:Tahoma;}
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
h1
        {margin-top:6.0pt;
        margin-right:0in;
        margin-bottom:6.0pt;
        margin-left:.5in;
        text-indent:-.25in;
        page-break-after:avoid;
        font-size:12.0pt;
        font-family:Arial;}
h2
        {margin-top:6.0pt;
        margin-right:0in;
        margin-bottom:6.0pt;
        margin-left:.75in;
        text-indent:-.25in;
        page-break-after:avoid;
        font-size:14.0pt;
        font-family:Arial;
        font-style:italic;}
p.MsoBodyText2, li.MsoBodyText2, div.MsoBodyText2
        {margin-top:0in;
        margin-right:0in;
        margin-bottom:6.0pt;
        margin-left:0in;
        line-height:200%;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
span.EmailStyle19
        {
        font-family:Arial;
        color:navy;}
div.Section1
        {page:Section1;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
-->
</style>
<div id="idOWAReplyText4582" dir="ltr">In regard to this thread,
I shall offer my two cents' worth of opinions:</div>
<div dir="ltr"> </div>
<div dir="ltr">For Large scale mapping generally at 1:50,000 and
larger, the classical geodetic Datum is the primary consideration
before delving into cartographic projections of various flavors.
However, with such considerations taken into account there are a very
finite number of mathematical models appropriate for use with any
specific Datum. Those models are generally specifically legislated by
some political body that has venue over that specific geographic
region. Since PROJ does not "connect" specific Datums with specific
mathematical models, <em>e.g</em>., Rome 1940 with either a
Gauss-Boaga Transverse Mercator projection (East or West Zone), for a
national system or a Cassini-Soldner projection for a local cadastral
system (some several hundred currently exist), ... both being the ONLY
appropriate projections to be used with Rome 1940 ... the user needs to
be educated enough to know that a Krovak Oblique Conic is entirely
inappropriate to use with that Datum for that country.</div>
<div dir="ltr"> </div>
<div dir="ltr">What does that? EPSG attempts to provide the guidance
for the appropriate mathematical models for the specific classical
geodetic Datums they list in their data base, <em>e.g.</em> the French
Army Truncated Cubic Lambert for some areas in North Africa.</div>
<div dir="ltr"> </div>
<div dir="ltr">I do not see PROJ doing that ... essentially it would
be an attempt to duplicate the EPSG contrivance.</div>
<div dir="ltr"> </div>
<div dir="ltr">Separation of true geodetic concerns from classical
cartographic applications seems to be a reasonable approach. Remember,
the late John P. Snyder never attempted to write about the connections
between projections and Datums with respect to large scale topographic
mapping. John did not care for such intricacies, and he mostly left
such to me except for his private consulting work when he actually used
my software. The various versions of Transverse Mercator are indeed an
excellent resource when the user needs to couple specific math models
with specific Datums.</div>
<div dir="ltr"> </div>
<div dir="ltr">For large-scale stuff, I think separating the two is
the way to go. Let the user figure it out at the user's peril. If the
user is apprehensive about such decisions, there indeed are people in
private practice that will recommend such decisions for a fee - most
are associated with the "Oil Patch" since it does make a difference for
them and their clinetle.</div>
<div dir="ltr"> </div>
<div dir="ltr">Cliff Mugnier</div>
<div dir="ltr">LSU</div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Proj mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Proj@lists.maptools.org">Proj@lists.maptools.org</a>
<a class="moz-txt-link-freetext" href="http://lists.maptools.org/mailman/listinfo/proj">http://lists.maptools.org/mailman/listinfo/proj</a></pre>
</blockquote>
</body>
</html>