The FDO Providers (AutoCAD Map 2008, 2009, 2010, 2011, 2012, 2013, 2014, and FME) Reader/Writer allows FME to access various back-end formats through the generic Autodesk® Feature Data Object (FDO) interface.
Note: Please see the FDO Quick Facts Licensing section for details about licensing requirements for extending MapGuide 6.5 and MapGuide Enterprise.
Overview
Feature Data Objects (FDO) is an Application Programming Interface (API) for manipulating, defining, and analyzing geospatial information. Through a generic interface, geospatial information is written to various formats through FDO Providers. The FDO Reader/Writer encapsulates the API and enables FME to read and write to FDO Datastores.
The feature types expressed by the FDO reader/writer correspond to FDO Feature Classes. The Feature Classes compose an FDO Schema. The name of the feature type encodes the name of the corresponding Feature Class and the retaining Schema in the form <Schema name>.<Feature Class name>.
When writing, if the Schema name is not specified in the destination feature type, then the default schema name specified by the FDO Provider Connection String writer parameter is used.
FDO Spatial Context is a coordinate system with an identity. Spatial data that is to be spatially related must have a common Spatial Context. Each Feature Class is associated with a Spatial Context.
FME contains the following FDO readers/writers:
- FDO_FME
- FDO_MAP2008
- FDO_MAP2009
- FDO_MAP2010
- FDO_MAP2011
- FDO_MAP2012
- FDO_MAP2013
- FDO_MAP2014
FME includes the FDO library and some FDO Providers.
|
Format |
Reader/Writer Action |
|---|---|
| FDO_FME |
Load the FDO library and the FDO providers packaged with FME. This format does not have dependencies outside of FME. We are currently shipping the following providers: SDF3 and SQLITE3FDO They are available from the generic FDO_FME format and also under their own format names. Note: We are no longer shipping MySQL or SpatiaLite through FDO. |
| FDO_MAP2008 |
Search for an existing installation of Autodesk Map 3D 2008 and utilize the FDO libraries and FDO providers installed with that application. |
| FDO_MAP2009 | Search for an existing installation of Autodesk Map 3D 2009 and utilize the FDO libraries and FDO providers installed with that application. |
| FDO_MAP2010 | Search for an existing installation of Autodesk Map 3D 2010 and utilize the FDO libraries and FDO providers installed with that application. |
| FDO_MAP2011 | Search for an existing installation of Autodesk Map 3D 2011 and utilize the FDO libraries and FDO providers installed with that application. |
| FDO_MAP2012 | Search for an existing installation of Autodesk Map 3D 2012 and utilize the FDO libraries and FDO providers installed with that application. |
| FDO_MAP2013 | Search for an existing installation of Autodesk Map 3D 2013 and utilize the FDO libraries and FDO providers installed with that application. |
| FDO_MAP2014 | Search for an existing installation of Autodesk Map 3D 2014 and utilize the FDO libraries and FDO providers installed with that application. |
Note: A workspace cannot include both the FDO_FME format and another one of the formats listed above.
Note: The SDF3 or SQLITE3FDO Reader/Writer can only be used together with FDO_FME, not with any other format listed above.
Reader Overview
The reader queries the FDO Provider for schematic information and feature data. Regardless of the underlying back-end format, the FDO reader will provide a consistent view of the schema and data.
Writer Overview
The writer can modify existing FDO Datastores or create new Datastores. The behavior of the writer is similar to database-based formats. Commands such as inserts, updates, and deletes, may be supported by individual FDO providers, regardless of whether the underlying format is file-based.
Most file-based FDO Providers do not require explicit Datastore management. However, if the FDO Provider provides an explicit method of creating Datastores, the writer parameters may also contain an option to create a Datastore.
The destination feature type corresponds to an FDO Feature Class in the destination Datastore.
If the name matches an existing Feature Class in the Datastore, the writer will apply features of that feature type to the existing Feature Class.
If the Feature Class does not exist, a new Feature Class will be created.
When a new Feature Class is created, FME will use several writer parameters to determine the FDO Spatial Context that will be associated with the new Feature Class.
More Information
For more information regarding the FDO reader/writer and FDO Provider specific issues, visit the FME Knowledge Center.
For more information regarding the FDO architecture, visit