Spatial Database Import Options

The Spatial Database Import Options dialog is used to choose the table or tables to be loaded from a spatial database. Global Mapper displays this dialog after you have chosen a spatial database connection, a Spatialite database, an Esri file geodatabase, an Esri personal geodatabase, or an Esri ArcSDE* geodatabase connection file.

The table list contains the names of the tables in the spatial database. Put a check next to one or more table(s) to indicate which tables you want to load.

Click the Check All button to place select all of the tables in the list.

Click the Clear All button to remove the check mark from all of the tables in the list.

Once you have marked the tables to be loaded, click the OK button to load the tables.

The Cancel button quits the process of opening a spatial database.

The Help button displays the Global Mapper help for this dialog.

If the spatial database being opened contains elevation data or raster imagery, the Spatial Database Import Options dialog will contain a tab to specify raster options.

Under Elevation Options, choose the Vertical Unit for the elevation data. The default is meters. If you don't choose the correct unit here, you can always fix it in the Control Center.


If the spatial database being opened contains vector data, the Spatial Database Import Options dialog will contain the Import Bounds tab. This tab allows the user to select a subset of the input data based on a bounding box. All geometries that intersect the bounding box will be imported into Global Mapper. This functionality applies only to vector data in a spatial database.

You can specify the bounding box in the following ways:

Connecting to a Microsoft SQL Server Database

Microsoft SQL Server Spatial uses two different schemes to organize spatial tables. The default scheme (used in SQL Server 2012 and later) uses a set of proprietary system tables to store spatial information such as the projection used, etc. Global Mapper expects SQL Server databases to be using this organizational method by default.

The second scheme uses tables called geometry_columns and spatial_ref_sys to store information about spatial tables.  In order to use such a database with Global Mapper:

If your SQL Server database is used as the underlying database for Esri ArcSDE*, you should use an Esri ArcSDE Spatial Database connection instead of a Microsoft SQL Server connection.  

*Note that connecting to an Esri ArcSDE database requires the 32-bit version of Global Mapper.