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?
From: MapServer-dev <[email protected]> On Behalf Of Even Rouault via MapServer-dev Sent: Monday, September 8, 2025 4:28 PM To: Steve Lime <[email protected]> Cc: MapServer Dev Mailing List <[email protected]> Subject: Re: [MapServer-dev] More precise WMS GetFeatureInfo for point symbols: ask for opinions This message may be from an external email source. Do not select links or open attachments unless verified. Report all suspicious emails to Minnesota IT Services Security Operations Center. ________________________________ Le 08/09/2025 à 23:13, Steve Lime a écrit : I could also see this enhancement being useful for native point-based queries too (e.g. mode=query or mode=nquery). 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 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. 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 so you can have something like: IDENTIFICATION TOLERANCE 5 CLASSAUTO END On Mon, Sep 8, 2025 at 7:36 AM Even Rouault via MapServer-dev <[email protected]<mailto:[email protected]>> wrote: Hi, In https://github.com/MapServer/MapServer/pull/7318 I've introduced an enhancement to be able to identify with WMS GetFeatureInfo point features through their symbols, rather than just a square centered around their position. This helps for symbols that are not centered (offset), or whose shape is not square. I've extende MapServer syntax to be able to enable that mode, and configure how it works. If you read the PR, you'll see there is a bit of a debate on how to best express that conffiguration. Either through a new IDENTIFICATION block as a child of a LAYER block, or using PROCESSION directive or wms_ METADATA items. Are there thoughts about that? Thanks, Even -- http://www.spatialys.com<http://www.spatialys.com/> My software is free, but my time generally not. _______________________________________________ MapServer-dev mailing list [email protected]<mailto:[email protected]> https://lists.osgeo.org/mailman/listinfo/mapserver-dev -- http://www.spatialys.com<http://www.spatialys.com/> My software is free, but my time generally not.
_______________________________________________ MapServer-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapserver-dev
