When working with spatial databases, it is essential to understand the associated terminology and concepts. The following terms are used throughout this document. DataStore—A collection or integrated set of objects contained in a single data storage location or repository such as an Oracle® Spatial database. Specific to Autodesk Map 3D, a DataStore is a set of feature classes contained in a single data storage location (feature source).

Feature—An abstraction of natural or manufactured real-world objects represented by drawing objects such as points and lines. For example, a line might represent a road feature, and a point might represent a fire hydrant. Feature Class—A schema element that describes a type of real-world object (feature) such as a road or parcel and the specific properties such as layer, color, linetype, and attribute information that describe the object. Feature Data Objects (FDO)—Technology that enables Autodesk Map 3D to read and write data in an external geospatial data repository such as Oracle Spatial. Feature Source—A set of feature classes contained in a single data storage location or repository. Often, the terms DataStore and feature source are used interchangeably.

Provider—The software component that provides access to data in a particular DataStore. Schema—A collection of database objects. Used to refer to the complete collection of defined tables and their relationships, metadata, and other information associated with one data set.

Service (also Oracle Service)—An executable process installed in the Microsoft® Windows® registry and administered by the operating system. Once a service is created and started, it can run even when no user is logged on to the computer.

Transaction—A unit of interaction with a database management system or similar system that is treated in a coherent and reliable way independent of other transactions. A single transaction might require several queries, each reading and/or writing information in the database.

Download