Query by features should check the selection layer's projection and units instead of the map's

[sdlime]

Currently the QueryByFeatures?() function in mapquery.c uses the map's projection and units as the go between when working with 2 layers. This is (often?) not necessary when the selection layer and the layer being queried share the same projection. In that case it makes sense to keep all computations in the native projection.

A common example of this is a mapfile with epsg:4326 output but with all layers in the same underlying coordinate system (e.g. UTM).

This impacts tolerance computations (what to do if PIXELS?) as well.

Steve

[sdlime]

Actually the "instead" should really be "first" and then falling back to the map's if the projections differ...

Steve