Analyzing data – Pitney Bowes MapXtreme User Manual
Page 193
Chapter 8: Working with Data
Analyzing Data
MapXtreme v7.1
200
Developer Guide
Analyzing Data
Once your data is available in the Catalog, you will want to analyze it to meet your business
objectives. The Catalog has an SQL processor that allows you parse and aggregate your data. Here
you have two options:
•
OGC object-based query interface
•
ADO.NET SQL-based interface
The diagram below shows the relationship between the two.
Group 1 shows the OGC query interface. Use these objects to construct a query. The interface
allows you to create queries to filter columns and rows, as well as add spatial and non-spatial
conditions. The queries interact through the Search methods off those query objects to return data
readers and result sets. Use these objects if you are more comfortable with object-oriented
programming and less so with SQL syntax. See
SearchInfo and SearchInfoFactory
The ADO.NET interfaces, shown in group 2, use the defined ADO.NET model to allow access via
the MapInfo SQL language. The ADO.NET interfaces use SQL syntax to interact with the Catalog. In
this instance you need to generate the SQL statement and assign it to the MICommand object.
These objects use the Execute command to return a data reader or result set. See
MapXtreme Data Model
Both the OGC query-based and ADO.NET command-based approaches use the Catalog (group 3)
to organize the data sources as a response to the object or SQL query. The object-based query API
will generate SQL and pass this to the Catalog for processing. In some instances you may be able to
generate more efficient SQL by hand, but the objects are well defined and the interfaces restrict how