FDO API Reference | Feature Data Objects |
00001 /*! \mainpage Introduction 00002 <div class="mainpage"> 00003 <!-- This is the index.html page that the user first sees. --> 00004 00005 <p>The Feature Data Objects (FDO) application 00006 programming interface (API) is a set of APIs used to 00007 manipulate, define, and analyze geospatial information. 00008 </p> 00009 <p>FDO supports the retrieving and updating of spatial and non-spatial 00010 GIS feature data through a rich classification model that is 00011 based on OpenGIS and ISO standards. 00012 </p> 00013 <p>From the perspective of a client application user: the FDO API 00014 provides consistent access to feature data, 00015 whether it comes from a CAD-based data source, or from a 00016 relational data store that supports rich classification. To 00017 achieve this, FDO supports a model that can readily follow 00018 the capabilities of each data source, allowing for consumer 00019 applications functionality that is tailored to match that of 00020 the data source. For example, some data sources may support 00021 spatial queries, while others do not. Also, a flexible 00022 metadata model is required in FDO, allowing clients to adapt 00023 to the underlying feature schema exposed by each data source. 00024 </p> 00025 <p>From the perspective of a client application engineer: the 00026 FDO API provides a common, general purpose abstraction layer 00027 for accessing geospatial data from a variety of data sources. 00028 The API is, in part, an interface specification of the 00029 abstraction layer. A provider, such as FDO Provider for SDF, is 00030 an implementation of the interface for a specific type of 00031 data source, which in this example is an implementation for 00032 Autodesk's spatial database format 00033 (SDF). The API can support the standard data store 00034 manipulation operations, such as querying, updating, versioning, 00035 locking, and others, only when the underlying data store has 00036 the same capabilities for these operations. 00037 </p> 00038 <h2> 00039 Architecture 00040 </h2> 00041 00042 <p> 00043 The high-level architecture of FDO comprises feature 00044 providers that plug into an application to expose a 00045 consistent feature schema and a consistent interface for 00046 interacting with geospatial feature data, regardless of the 00047 underlying data store. The client applications interact 00048 through the various FDO interfaces, such as 00049 FdoIConnection or FdoICommand, using an FDO interface layer, or feature 00050 access manager. 00051 </p> 00052 <p> 00053 FDO is assembled in or consists of conceptual packages of similar 00054 functionality. This packaging is reflected in the 00055 substructure of the FDO SDK 'includes' folder. FDO commands, 00056 provider-specific commands, and connections/capabilities 00057 provide access to native data stores through each specific 00058 FDO provider. Schema management (using XML), client services, 00059 and filters/expressions are all provider-independent packages 00060 that connect directly to the FDO API. 00061 </p> 00062 <p> 00063 For more information, see <i>The Essential FDO</i> (FET_TheEssentialFDO.pdf) 00064 and the <i>FDO Developer's Guide</i> (FDG_FDODevGuide.pdf). 00065 </p> 00066 00067 \image html FDO_architecture.png 00068 <br> 00069 </div> 00070 */ 00071 00072 00073 00074
Comments or suggestions? Send us feedback. |