Loading spatial data to dbms, Manually creating a mapinfo mapcatalog – Pitney Bowes MapXtreme User Manual

Page 230

Advertising
background image

Chapter 11: Accessing Data from a DBMS

The MapInfo_MapCatalog

MapXtreme v7.1

237

Developer Guide

Your application can use a MapInfo_MapCatalog that already exists on the server. (This same
catalog is shared by various MapInfo client applications). If there is no MapInfo_MapCatalog on the
server, you need to create one. MapXtreme supports the storage of style information for individual
features in remote databases.

Loading Spatial Data to DBMS

If you have spatial data in the form of a MapInfo table, you can import it into your DBMS database.

To load data into Microsoft SQL Server, MapInfo SpatialWare for SQL Server, and Oracle Spatial,
use the MapInfo EasyLoader, that is distributed with MapInfo Professional and available for
download from

www.pbinsight.com

. The EasyLoader utility automatically creates a

MapInfo_MapCatalog when you upload a table, if there is no MapInfo_MapCatalog already present.

Manually Creating a MapInfo MapCatalog

If you are not a MapInfo Professional or EasyLoader user, you or your database administrator will
need to create the MapCatalog manually, as described below. You only have to create the
MapCatalog once per server/database.

1. Create the user MAPINFO in the specific database where the mappable tables are located.

2. Create the table MAPINFO_MAPCATALOG in the database.

The Create Table statement needs to be equivalent to the following SQL Create Table statement:
Create Table MAPINFO_MAPCATALOG (
SPATIALTYPE Float,
TABLENAME Char(32),
OWNERNAME Char(32),
SPATIALCOLUMN Char(32),
DB_X_LL Float,
DB_Y_LL Float,
DB_X_UR Float,
DB_Y_UR Float,
VIEW_X_LL Float,
VIEW_Y_LL Float,
VIEW_X_UR Float,
VIEW_Y_UR Float,
COORDINATESYSTEM Char(254),
SYMBOL Char(254),
XCOLUMNNAME Char(32),
YCOLUMNNAME Char(32),
RENDITIONTYPE INTEGER,
RENDITIONCOLUMN CHAR(32),
RENDITIONTABLE CHAR(32)

Advertising