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