<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Aptos;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.qt-msonormal1, li.qt-msonormal1, div.qt-msonormal1
{mso-style-name:qt-msonormal1;
margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
span.size
{mso-style-name:size;}
span.font
{mso-style-name:font;}
span.EmailStyle26
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">I favor functional parity if possible. MapScript leverages those msQueryBy… functions too.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Seth G <sethg@geographika.co.uk>
<br>
<b>Sent:</b> Tuesday, September 9, 2025 10:04 AM<br>
<b>To:</b> Lime, Steve D (MNIT) <steve.lime@state.mn.us>; Even Rouault <even.rouault@spatialys.com>; Steve Lime <sdlime@gmail.com><br>
<b>Cc:</b> MapServer Devs <mapserver-dev@lists.osgeo.org><br>
<b>Subject:</b> Re: [MapServer-dev] More precise WMS GetFeatureInfo for point symbols: ask for opinions<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I'm not sure how much mode=query and mode=nquery are used now, compared with through WMS, and if it is worth implementing this feature for them. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">My preference would be to leave as WMS only, with WMS metadata parameters. If in the future there is another OGC standard that works similar to GetFeatureInfo then promote it to an IDENTIFY block. If it is going to be available to mode=query
then it would also make sense to create an IDENTIFY block. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Having said that, I'm in favour of adding in the feature with any of the current or suggested implementations.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Seth<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="sig62266145">
<div>
<p class="MsoNormal">--<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">web:<a href="https://geographika.net/">https://geographika.net</a> & <a href="https://mapserverstudio.net/">https://mapserverstudio.net</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">mastodon: @<a href="mailto:geographika@mastodon.social">geographika@mastodon.social</a><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">On Mon, Sep 8, 2025, at 11:48 PM, Lime, Steve D (MNIT) via MapServer-dev wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt;overflow-wrap:break-word" id="qt">
<div>
<p class="qt-msonormal1"><span class="size"><span style="font-size:11.0pt">Ok, cool – then moving the TOLERANCE* parameters inside the new directive makes more sense. Note, I like IDENTIFY more than IDENTIFICATION but that’s just semantics. Would layer-level
TOLERANCE* values continue to work, at least for a bit?</span></span><o:p></o:p></p>
<p class="qt-msonormal1"><span class="size"><span style="font-size:11.0pt"> </span></span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in;border-right-color:currentcolor;border-bottom-color:currentcolor;border-left-color:currentcolor;border-image-outset:0;border-image-repeat:stretch;border-image-slice:100%;border-image-source:none;border-image-width:1">
<p class="qt-msonormal1"><span class="size"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b></span><span class="size"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> MapServer-dev <<a href="mailto:mapserver-dev-bounces@lists.osgeo.org">mapserver-dev-bounces@lists.osgeo.org</a>>
<b>On Behalf Of </b>Even Rouault via MapServer-dev</span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
<span class="size"><b>Sent:</b> Monday, September 8, 2025 4:28 PM</span><br>
<span class="size"><b>To:</b> Steve Lime <<a href="mailto:sdlime@gmail.com">sdlime@gmail.com</a>></span><br>
<span class="size"><b>Cc:</b> MapServer Dev Mailing List <<a href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a>></span><br>
<span class="size"><b>Subject:</b> Re: [MapServer-dev] More precise WMS GetFeatureInfo for point symbols: ask for opinions</span></span><o:p></o:p></p>
</div>
</div>
<p class="qt-msonormal1"> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" align="left" width="100%" style="width:100.0%">
<tbody>
<tr>
<td style="background:#FFC845;padding:5.25pt 1.5pt 5.25pt 1.5pt;background-position-x:0%;background-position-y:0%;background-size:auto;background-origin:padding-box;background-clip:border-box;background-attachment:scroll">
</td>
<td width="100%" style="width:100.0%;background:#FFF3DD;padding:5.25pt 3.75pt 5.25pt 11.25pt;background-position-x:0%;background-position-y:0%;background-size:auto;background-origin:padding-box;background-clip:border-box;background-attachment:scroll">
<div>
<div>
<p class="qt-msonormal1" style="mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span class="size"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#003865">This message may be from an external email source.</span></b></span><o:p></o:p></p>
</div>
<div>
<p class="qt-msonormal1" style="mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span class="size"><span style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:#003865">Do not select links or open attachments unless verified. Report all suspicious emails to Minnesota IT Services Security Operations Center.</span></span><o:p></o:p></p>
</div>
</div>
</td>
</tr>
</tbody>
</table>
<p class="qt-msonormal1"> <o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal" align="center" style="text-align:center"><o:p> </o:p></p>
<div>
<p> <o:p></o:p></p>
<div>
<p class="qt-msonormal1">Le 08/09/2025 à 23:13, Steve Lime a écrit :<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="qt-msonormal1">I could also see this enhancement being useful for native point-based queries too (e.g. mode=query or mode=nquery).<o:p></o:p></p>
</div>
</blockquote>
<p>I guess they could be enhanced to use that functionality. The would need to populate the new query->getFeatureInfo->x_pixel and query->getFeatureInfo->y_pixel fields, so a new X_PIXEL and Y_PIXEL variable should be added<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="qt-msonormal1">If that's feasible, then I wouldn't tie the configuration to WMS explicitly. What about just using TOLERANCE AUTO? I mean, it seems that this is trying to address the limitations of that configuration parameter.<o:p></o:p></p>
</div>
</blockquote>
<p>This isn't exclusive of the TOLERANCE value. The TOLERANCE value can be used to add an extra buffer around the filled areas of the symbol<o:p></o:p></p>
<p>so you can have something like:<o:p></o:p></p>
<p>IDENTIFICATION<br>
TOLERANCE 5<br>
CLASSAUTO<br>
END<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="qt-msonormal1"> <o:p></o:p></p>
<div>
<div>
<p class="qt-msonormal1">On Mon, Sep 8, 2025 at 7:36<span class="font"><span style="font-family:"Arial",sans-serif"> </span></span>AM Even Rouault via MapServer-dev <<a href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</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-top:5.0pt;margin-right:0in;margin-bottom:5.0pt;border-top-color:currentcolor;border-right-color:currentcolor;border-bottom-color:currentcolor;border-image-outset:0;border-image-repeat:stretch;border-image-slice:100%;border-image-source:none;border-image-width:1">
<p class="qt-msonormal1">Hi,<br>
<br>
In <a href="https://github.com/MapServer/MapServer/pull/7318" target="_blank">https://github.com/MapServer/MapServer/pull/7318</a> I've introduced an
<br>
enhancement to be able to identify with WMS GetFeatureInfo point <br>
features through their symbols, rather than just a square centered <br>
around their position. This helps for symbols that are not centered <br>
(offset), or whose shape is not square.<br>
<br>
I've extende MapServer syntax to be able to enable that mode, and <br>
configure how it works. If you read the PR, you'll see there is a bit of <br>
a debate on how to best express that conffiguration. Either through a <br>
new IDENTIFICATION block as a child of a LAYER block, or using <br>
PROCESSION directive or wms_ METADATA items. Are there thoughts about that?<br>
<br>
Thanks,<br>
<br>
Even<br>
<br>
-- <br>
<a href="http://www.spatialys.com/" target="_blank">http://www.spatialys.com</a><br>
My software is free, but my time generally not.<br>
<br>
_______________________________________________<br>
MapServer-dev mailing list<br>
<a href="mailto:MapServer-dev@lists.osgeo.org" target="_blank">MapServer-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">https://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><o:p></o:p></p>
</blockquote>
</div>
</blockquote>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">-- <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New""><a href="http://www.spatialys.com/">http://www.spatialys.com</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">My software is free, but my time generally not.<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal">_______________________________________________<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">MapServer-dev mailing list<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="mailto:MapServer-dev@lists.osgeo.org">MapServer-dev@lists.osgeo.org</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://lists.osgeo.org/mailman/listinfo/mapserver-dev">https://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>