Pitney Bowes MapXtreme User Manual
Page 160
Chapter 8: Working with Data
Supported Table Types
MapXtreme v7.1
167
Developer Guide
ASCII
Data stored in a delimited .CSV or text file. The maximum string length is
255 characters (including up to two quotation marks). ASCII tables are
Insert only.
The table may have an associated .MAP file containing FeatureGeometry
and Style information. Non-spatial data is stored in a .CSV or .TXT file.
MS Access
Microsoft Access database table.
This file-based table located inside of a Microsoft Access .MDB database
may have an associated .MAP file containing FeatureGeometry and Style
information. Non-spatial data is stored in an Access file.
Shapefile
An ESRI Shapefile table.
These tables are read-only and support three-dimensional geometries (X,
Y, Z, M). Non-spatial attribute data is stored in .DBF file format.
FeatureGeometry values stored in ESRI .shp file format. MapXtreme does
not have access to the spatial index. Caching is supported as a .MAP file
that can be temporary or persistent. A persistent cache can be shared with
MapInfo Professional. It is controlled by the PersistentCache property on
the TableInfoShapefile class.
MemTable
An in-memory storage of non-spatial attribute data.
FeatureGeometry data and indices are stored on disk. These are
temporary tables—all data is lost when the table is closed. MemTables are
serializable. The data can be persisted in workspaces (data only; keys may
be changed when reloading). This table type is available as a storage
format to be used when caching. There is no .TAB file equivalent to a
MemTable. See
RDBMS Server
A spatial table stored in a remote database management system (such as
SQL Server or Oracle).
The table is defined by a native SQL SELECT statement. MapXtreme
performs query parsing and modification. Caching is enabled by default.
Supported protocols (toolkits) include: OCI (Oracle Spatial) and ODBC (,
SQL Server, SpatialWare and XY). See