<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Comic Sans MS";
panose-1:3 15 7 2 3 3 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Comic Sans MS";
color:#0070C0;
font-weight:bold;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Comic Sans MS";color:#0070C0">All,<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Comic Sans MS";color:#0070C0"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Comic Sans MS";color:#0070C0">I can second Steve’s idea. We were using Mapserver for years before we needed to pay attention to projections, because all of our data wasin our local coordinate
system. We now work projection across all map services for all layers, either by explicitly stating the projection or having it scripted at the web server call. Some cases it won’t matter, if ever, and others it will be instrumental in getting a site working
with many and varied projected datasets being combined.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Comic Sans MS";color:#0070C0"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Comic Sans MS";color:#0070C0">I would agree that it should be a topic more prominently displayed/noted in the documentation.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Comic Sans MS";color:#0070C0"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Comic Sans MS";color:#0070C0">Bobb<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Comic Sans MS";color:#0070C0"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Comic Sans MS";color:#0070C0"><o:p> </o:p></span></b></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> mapserver-users <mapserver-users-bounces@lists.osgeo.org>
<b>On Behalf Of </b>Steve Lime<br>
<b>Sent:</b> Monday, April 27, 2020 1:21 PM<br>
<b>To:</b> Jeff McKenna <jmckenna@gatewaygeomatics.com><br>
<b>Cc:</b> Mapserver <mapserver-users@lists.osgeo.org><br>
<b>Subject:</b> Re: [mapserver-users] Make PROJECTION mandatory?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="1" cellspacing="3" cellpadding="0" style="background:#E2F700;border:solid black 1.0pt">
<tbody>
<tr>
<td style="border:none;padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><strong><span style="font-family:"Calibri",sans-serif;color:#FF3333">Think Before You Click:
</span></strong><span style="color:#FF3333">This email originated <strong><span style="font-family:"Calibri",sans-serif">outside
</span></strong>our organization.</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">I would prefer to pursue as a documentation/communication exercise first. It's not that I don't agree that PROJECTION blocks are generally recommended but making them required and introducing artificial projections to deal with cases when
projections aren't used (embedded legends, scale bars and other static map elements) will touch a lot of code. It's also a major breaking change that would potentially break a large percentage of mapfiles going forward.
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">--Steve<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mon, Apr 27, 2020 at 8:43 AM Jeff McKenna <<a href="mailto:jmckenna@gatewaygeomatics.com">jmckenna@gatewaygeomatics.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">Hi Jukka,<br>
<br>
I personally consider defining PROJECTION blocks at the MAP level and <br>
all LAYERs mandatory, in my day-to-day work, for each and every mapfile. <br>
If you do not specify all of these, MapServer makes assumptions and <br>
you are just asking for trouble downstream through WMS clients etc. <br>
(your users)<br>
<br>
I also do not rely on any PROJECTION AUTO magic either, for my paying <br>
clients.<br>
<br>
These are all nice tricks but in critical production environments I stay <br>
away from them; instead, find the source projection, and define the MAP <br>
projection block and all LAYER projection blocks.<br>
<br>
I'm not sure this answers your questions, but this was my 'gut reaction' <br>
to your message. I believe we have the same thinking here.<br>
<br>
-jeff<br>
<br>
<br>
<br>
-- <br>
Jeff McKenna<br>
MapServer Consulting and Training Services<br>
<a href="https://gatewaygeo.com/" target="_blank">https://gatewaygeo.com/</a><br>
<br>
<br>
<br>
On 2020-04-27 10:36 a.m., Rahkonen Jukka (MML) wrote:<br>
> Hi,<br>
> <br>
> Recent Mapserver buids require PROJ and GDAL <br>
> <a href="https://mapserver.gis.umn.edu/ja/development/rfc/ms-rfc-127.html" target="_blank">
https://mapserver.gis.umn.edu/ja/development/rfc/ms-rfc-127.html</a>. That <br>
> means that every Mapserver can support PROJECTION blocks both at the MAP <br>
> level and within LAYER. And because there are no more builds without <br>
> Proj support there is no real need for writing mapfiles without <br>
> PROJECTION blocks. Therefore I suggest that such mapfiles should be <br>
> considered invalid in the future. If it is for some reason too strict <br>
> requirement, what if we at least edit the documentation <br>
> <a href="https://mapserver.org/mapfile/projection.html" target="_blank">https://mapserver.org/mapfile/projection.html</a> so that it really
<br>
> encourages users to write the PROJECTION blocks. GetCapabilities could <br>
> also show something like<br>
> <!-- WARNING: No explicit source projection defined for layer <br>
> 'my_layer'. --><br>
> <br>
> Having layers without PROJECTION saves users from writing this much text:<br>
> <br>
> “PROJECTION "init=epsg:3857" END<br>
> <br>
> but when the user meets any problem with accessing data or rendering the <br>
> first thing to check is the projection. In the mailing list it means one <br>
> more question-answer round before getting closer to the real problem – <br>
> if the problem was not in the projection, as it very often is.<br>
> <br>
> If source data are in local coordinate system it would be better to <br>
> define also that explicitly with a special keyword like PROJECTION “LOCAL”.<br>
> <br>
> Would other user consider making projection compulsory rather as an <br>
> improvement or inconvenience?<br>
> <br>
> -Jukka Rahkonen-<br>
> <br>
> <br>
> _______________________________________________<br>
> mapserver-users mailing list<br>
> <a href="mailto:mapserver-users@lists.osgeo.org" target="_blank">mapserver-users@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/mapserver-users" target="_blank">
https://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br>
> <br>
<br>
<br>
_______________________________________________<br>
mapserver-users mailing list<br>
<a href="mailto:mapserver-users@lists.osgeo.org" target="_blank">mapserver-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/mapserver-users" target="_blank">https://lists.osgeo.org/mailman/listinfo/mapserver-users</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</body>
</html>