Ticket #3561 (assigned enhancement)
In getFeatureInfo, add an easy way to search all pixels in requested map
|Reported by:||mraross||Owned by:||chodgson|
|Component:||MapServer C Library||Version:||unspecified|
|Cc:||sdlime, dmorissette, assefa,|
In the common getFeatureInfo scenario, a client app requests attributes of the feature under or near the cursor (see attached searchPixelsnearCursor.jpg). This is conveniently specified using &x, &y, and &radius parameters. In another, less common but important scenario, an client app requests attributes of all features within the current &width and &height of the requested map (see attached searchAllPixels.jpg). It isn't possible to specify this in terms of &x, &y, and &radius from some clients such as Google Earth since it requires a the runtime computation of &width/2,&height/2, etc. We propose an adding support for an additional boolean parameter called &searchAllPixels that, if set to true, means that &width and &height should be used to define the search extent instead of &x, &y, and &radius; if false, search extent is determined by &x, Y, and &radius. By default, &searchAllPixels=false.