MS 4.2 query results bug

[Ken Lord]

Hi List,

Perhaps this is fixed in later versions, please respond if you've heard of this.

It is not a serious problem, if your data is clean you won't see this
happen but this might explain a strange occurance for someone out
there ...

This was discovered upon migrating from mapserver 3.6 to 4.2. The
error does not occur in 3.6.

Mapserver 4.2, CGI, A layer based on a shapefile, type line.

The shapefile had an error where there was a record in it's table
without a corresponding spatial feature.  (this error probably
happened by editing the shapefile dbf file in excel, adding a new
record by mistake)

A mapserver query of the map always returned a result for this feature
no matter where you clicked so long as you clicked within the bounding
box of that shapefile. Tolerance settings in the map file made no
difference.  Clicking on a real feature in that layer returns the
correct resuts,  plus a result for the broken feature.

... as if any coordinates within the bounding box was allowed to
correspond to the feature that really had no coordinates at all.

The same dataset used with mapserver 3.6 did not show this problem.

Cheers,
Ken Lord
Vancouver BC