An overview of geodatabase settings


The Geodatabase Settings section of the Environment Settings dialog box provides environment settings for results placed in a geodatabase. Included are the following settings that can be changed:

The following subtopics supplement the reference topics found in Environment settings.

Output CONFIG keyword

The configuration keyword specifies the storage parameters (configuration) for file geodatabases or for geodatabases in a Relational Database Management System (RDBMS)—ArcSDE Enterprise Edition only.

The database storage configuration enables you to fine-tune how data is stored. The configuration parameters are grouped together into one or more configuration keywords, one of which is the defaults configuration keyword that specifies the default storage parameters.

When you create a dataset, such as a feature class, geometric network, or raster, you can tell the database which configuration keyword to use. Different configuration keywords can be used for different datasets. Normally, you can use the defaults configuration keyword, which geoprocessing tools will access automatically. In some cases, you may have created alternative configuration keywords for use when you create particular datasets or types of data to maximize their performance, or when you fine-tuned some aspect of how they were stored in the database. In this case, an alternative keyword can be specified.

Learn more about configuration keywords for file geodatabases

Learn more about configuration keywords for ArcSDE Enterprise Edition geodatabases

Output spatial grid

You can set up output spatial grid which are two-dimensional grid systems that span a feature class. When zoomed in on a feature class and performing a spatial search, only the features that fall in the necessary cells of the spatial grid are searched, enabling the quick location of features that might match the criteria of the spatial search.

Personal geodatabase feature classes require a single spatial grid. ArcSDE geodatabase feature classes can have up to three spatial grids. Each spatial grid must be at least three times the size of the previous spatial grid. Feature size is an important factor in determining an optimum size for the spatial grid. Data that contains features of different sizes may require additional spatial grids to increase the speed of graphical queries.

If you are unfamiliar with creating spatial grids, use the default, which will calculate an appropriate size. A poorly defined grid size can increase the spatial search time.

Setting spatial domains (x, y, z, and m)

Data created 9.2 (and later) geodatabase have logic to automatically calculates a valid xy domain. This environment is only supported when creating data in a pre-9.2 geodatabase OR when creating data with an Unknown coordinate system in a 9.2 (or later) geodatabase. You can still control resolution (called precision before the 9.2 release) by setting the xy resolution environment.

When results from running tools will be feature classes or feature datasets within a geodatabase, you can first set up the spatial domains which defines the allowable coordinates range for x,y coordinates; m-values, such as mileages along a highway; and z-values, such as building heights.

Precedence rules dictate where the spatial domain information will come from when running tools.

Related topic

- Learn more about setting the coordinate system before running tools

- Spatial reference and geoprocessing

See Also