<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=us-ascii">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.Shkpostityyli17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 2.0cm 70.85pt 2.0cm;}
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="FI" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hi,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">Recent Mapserver buids require PROJ and GDAL
</span><a href="https://mapserver.gis.umn.edu/ja/development/rfc/ms-rfc-127.html"><span lang="EN-US">https://mapserver.gis.umn.edu/ja/development/rfc/ms-rfc-127.html</span></a><span lang="EN-US">. That means that every Mapserver can support PROJECTION blocks
both at the MAP level and within LAYER. And because there are no more builds without Proj support there is no real need for writing mapfiles without PROJECTION blocks. Therefore I suggest that such mapfiles should be considered invalid in the future. If it
is for some reason too strict requirement, what if we at least edit the documentation
<a href="https://mapserver.org/mapfile/projection.html">https://mapserver.org/mapfile/projection.html</a> so that it really encourages users to write the PROJECTION blocks. GetCapabilities could also show something like<br>
<!-- WARNING: No explicit source projection defined for layer 'my_layer'. --><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Having layers without PROJECTION saves users from writing this much text:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">“PROJECTION "init=epsg:3857" END<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">but when the user meets any problem with accessing data or rendering the first thing to check is the projection. In the mailing list it means one more question-answer round before getting closer to the real problem –
if the problem was not in the projection, as it very often is.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">If source data are in local coordinate system it would be better to define also that explicitly with a special keyword like PROJECTION “LOCAL”.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Would other user consider making projection compulsory rather as an improvement or inconvenience?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">-Jukka Rahkonen- <o:p></o:p></span></p>
</div>
</body>
</html>