[mapguide-users] Filter queries on FeatId field of SHP files giving
unexpected results
cagray
colin.gray at 1spatial.com
Fri Oct 2 04:19:19 EDT 2009
Hi,
I have an interesting situation when applying filters to a SHP file's FeatId
field (the primary key field).
If I apply a filter of:
FeatId > 20
When you preview/save and view the layer I only get the feature with FeatId
20 showing in the layer instead of the 40 or so features that actually have
a FeatId > 20. However if I do a query on this layer using the same filter
using code such as:
MgFeatureQueryOptions queryOptions = new MgFeatureQueryOptions();
queryOptions.SetFilter("FeatId > 20");
MgFeatureReader featureReader =
featureService.SelectFeatures(layerResourceId, className, queryOptions);
the results of this filter are as expected and I get the 40 or so rows
returned that actually have a FeatId above 20.
It looks like when rendering the FeatId > 20 gets interpreted as FeatId =
20. I tried other operators such as <, <= and >= and they all behaved the
same way.
Has anyone seen this before? Is it the SHP files I am using or a generic
issue for SHP files?
Thanks for any help
Colin
--
View this message in context: http://n2.nabble.com/Filter-queries-on-FeatId-field-of-SHP-files-giving-unexpected-results-tp3754139p3754139.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
More information about the mapguide-users
mailing list