Pitney Bowes MapMarker USA - Manual (Page 287)

Appendix B:
Adding Rows to the MapInfo_MapCatalog
MapMarker USA 25
287
User Guide
Adding Rows to the MapInfo_MapCatalog
For each spatial table that you want to access from your application, you need to add a row to the
MAPINFO_MAPCATALOG table. If you do not use MapInfo Professional to manage the
MapInfo_MapCatalog, you will have to add rows to the MAPINFO_MAPCATALOG table manually.
The following describes the syntax and meaning of each column in the Map Catalog Table .
Map Catalog Table
Column Name Values to Assign Examples
SPATIALTYPE MapInfo Spatial Object Format
See
Spatial Index Types for SPATIALTYPE
Spatial Object Type
x.0: Points only
x.1: Lines only
x.2: Regions only
x.3: All types supported
This column describes the Spatial Object Format of how
the data is stored and indexed and the Spatial Object
type(s) supported and not supported in the column. The
digits to the left of the decimal point are the Spatial
Object Format. The digits to the right represent the type
of Spatial Object Type that can be stored in the column
25.0 = SQL Server
TABLENAME The name of the table. STATES
OWNERNAME The owner name of the table. BOB
SPATIALCOLUMN The name of the column, if any, containing spatial
features:
SW_GEOMETRY
(mappable using SpatialWare Type/IDS/UDO)
NO_COLUMN
(mappable using X–Y)
MI_SQL_MICODE (mappable using MI Code) Or the
name of the IDS/UDO, or Oracle column that is
ST_SPATIAL datatype.
Name of the Oracle SDO_GEOMETRY column.
SW_GEOMETRY
DB_X_LL The X coordinate of the lower left corner of the layer’s
bounding rectangle, in units that are indicated by the
COORDINATESYSTEM (see below). –360
DB_Y_LL The lower left bounding Y value. –90
DB_X_UR The upper right bounding X value. 360