API Reference | OSGeo FDO Provider for ODBC |
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) API provides access to data in a 00006 data store. A provider is a specific implementation of the FDO API 00007 that provides access to data in a particular data store. The FDO 00008 Provider for ODBC provides FDO with access to an ODBC-based data store. 00009 </p> 00010 <p>The FDO Provider for ODBC can access simple x, y, z 00011 feature objects that can run in a multi-platform 00012 environment, including Windows, Linux, and UNIX. 00013 </p> 00014 <p>The FDO Provider for ODBC has the following characteristics: 00015 </p> 00016 <ul> 00017 <li> The FDO Provider for ODBC supports the definition of one or more feature classes in terms of 00018 any relational database table that contains an X, Y, and 00019 optionally, Z columns.</li> 00020 <li> Metadata--that maps the table name, and X, Y, and optionally, Z 00021 columns to a feature class--is maintained outside the 00022 database in a configuration file. This information, in 00023 conjunction with the table structure in the database, 00024 provides the definition of the feature class.</li> 00025 <li> The x, y, and z locations of objects are stored in 00026 separate properties in the primary object definition of a 00027 feature, but are accessible through a single class 00028 property ‘Geometry’.</li> 00029 <li> Read-only access is provided to pre-existing data defined and 00030 populated through 3rd party applications (that is, FDO 00031 Provider for ODBC will not be responsible for defining the 00032 physical schema of the data store nor for populating the object 00033 data).</li> 00034 <li> The schema configuration of the data store is 00035 provided to the FDO Provider for ODBC through an optional XML 00036 file containing the Geographic Markup Language (GML) 00037 definition of the schema that maps ‘tables’ and ‘columns’ in 00038 the data store to feature classes and property mappings in 00039 the FDO data model.</li> 00040 </ul> 00041 \note 00042 Microsoft Excel (must have at least one named range; do not use DATABASE 00043 or other reserved words as a range name) 00044 00045 <p> 00046 For more information, see <i>The Essential FDO</i> (FET_TheEssentialFDO.pdf) 00047 and the <i>FDO Developer's Guide</i> (FDG_FDODevGuide.pdf). 00048 </p> 00049 00050 <br> 00051 </div> 00052 */ 00053 00054 00055 00056
Comments? |