You can bring features
from an Oracle data source into your map, creating a feature layer in Display
Manager. When you do this, you can:
- Select the feature classes to include
in your map.
- Set conditions to limit the features
in your map.
- View and edit the features
- Style, theme, and edit the features.
- Lock individual features when you check
then out for editing.
- Keep features checked out and locked
even when you close your drawing. Features are not checked back
in and unlocked until you specify.
- Automatically update the data source
with any edits you make. Your edits are immediately visible to anyone
else using the data source.
- Create versions of your data. Versioning creates
a copy of the data in the data source. Your changes are made to
the new version of the data. Versioning is useful for proposed changes
or changes that need approval. When the changes are final, you can
make your version the current one.
- Use a data source set up for AutoCAD Map 3D.
If your data source schema is not set up to work with AutoCAD Map 3D, AutoCAD Map 3D creates
a custom mapping so you can use the data in your map.
- View and edit the schema definition.
- Create an Oracle data source.
- Move SHP data into Oracle to take advantage
of better data sharing.
- Bring in a static copy of Oracle data
as drawing objects.
In the 2008 release of AutoCAD Map 3D,
a new column called geometrytype was added to the
table named F_AttributeDefinition. To use AutoCAD Map 3D 2010 to
access FDO data stores that were created in AutoCAD Map 3D 2007 and
earlier, you must first connect to the data store containing this
table and run a SQL script. Instructions for this are on the Procedure
tab of this topic. To do this, you must have the privileges required
to execute the ALTER TABLE request. In the command line, enter the
information on customizing this provider, refer to the FDO
API Reference and the FDO Provider for Oracle
API Reference. The API has custom commands for gathering
information about a provider, transmitting client services exceptions,
getting lists of accessible data stores, creating connection objects, and
creating and dropping spatial indexes.