Pitney Bowes MapXtreme - Manual (Page 161)

Chapter 8: Working with Data
Supported Table Types
MapXtreme v7.1 168 Developer Guide
ADO.NET A table of non-spatial data that is based upon an ADO.NET DataTable or
IDbCommand.
This table type supports many different data providers with provider-
specific implementations. ADO.NET is the choice when there is no
MapXtreme supported data provider. ADO.NET is designed to support both
Connected (IDBCommand) and Disconnected (DataTable) ADO.NET
models. IDBTables are read-only. Cache may be applied forcibly (implicit
keys). DataTables are editable and run-time serialization is supported. See
Using an ADO.NET Data Provider .
Raster A table containing a raster image.
This typically provides a base map for other spatial table types. Tables
have only a single record and a fixed column schema (RasterInfo,
MI_Geometry, MI_Style). These tables may be joined with vector tables
using spatial predicates (for example, “within”). See
Chapter 17: Working
with Rasters and Grids .
Grid A table containing a grid image.
This table type provides a base map for other spatial table types. Tables
have only a single record and a fixed column schema (GridInfo,
MI_Geometry, MI_Style). These tables may be joined with vector tables
using spatial predicates (for example, “within”). GridRead class provides
access to grid cell values. MapInfo.Raster.GridCreatorFromFeatures class
creates a grid using an interpolator. See
Chapter 17: Working with
Rasters and Grids .
WMS A table containing an image from a Web Map Service (WMS).
This table type provides a base map for other spatial table types. Tables
have only a single record and a fixed column schema (GridInfo,
MI_Geometry, MI_Style). These tables may be joined with vector tables
using spatial predicates (for example, “within”). WMS tables are accessed
like dynamic raster through a MapInfo.Wms.WmsClient. See
Chapter 19:
Web Map Service .
Seamless A table that combines two or more base tables with contiguous geography.
It displays as a single map layer.
Seamless tables are specifically tuned for spatial queries, such as drawing
a map, which uses seamless tables for optimally querying appropriate
component tables. Component tables that make up a seamless table may
be vector or raster. They must all have the same schema. They are read-
only. The underlying component tables cannot be modified directly. Sorting
and aggregating operations examine every record of every component
tables (could be have a significant performance impact when working with
vector tables.)