Thanks - I saw the article you listed and figured I would see it again - thanks. It however uses a shape file - I am using attempting to query a standard SQL Server table with longs and lats stored as doubles.
The process basically goes as follows:
- A base recordset is pulled from the SQL table based on other non-geo filter criteria.
- The resulting recordset is loaded into a GeometryFeatureProvider object
- A bounding box object is built based on a user-drawn polygon
- Bounding box/GeometryFeatureProvider used to execute a intersection query
Does the article you indicated still apply in this scenario?