svn commit: r35 - trunk/www
gregboone at osgeo.org
gregboone at osgeo.org
Tue Jul 18 23:24:41 EDT 2006
Author: gregboone
Date: 2006-07-19 03:24:40+0000
New Revision: 35
Modified:
trunk/www/OSProviderOverviews.html
trunk/www/featureDescriptions.html
trunk/www/gettingStarted.html
trunk/www/glossary.html
trunk/www/history.html
trunk/www/index.html
trunk/www/productsUsingFdo.html
Log:
FDO2
Modified: trunk/www/OSProviderOverviews.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/OSProviderOverviews.html?view=diff&rev=35&p1=trunk/www/OSProviderOverviews.html&p2=trunk/www/OSProviderOverviews.html&r1=34&r2=35
==============================================================================
--- trunk/www/OSProviderOverviews.html (original)
+++ trunk/www/OSProviderOverviews.html 2006-07-19 03:24:40+0000
@@ -25,7 +25,7 @@
</tr>
<tr>
<td>OSGeo FDO Provider for SDF</td>
- <td>Read-write access to feature data in an SDF-based data store. Autodesk’s geospatial file format, SDF, supports multiple features/attributes, provides high performance for large data sets, and interoperability with other Autodesk products. Supports spatial indexing and is a valid alternative to database storage. Note that this release of the SDF provider supports version 3.0 of the SDF file format.</td>
+ <td>Read-write access to feature data in an SDF-based data store. Autodesk’s geospatial file format, SDF, supports multiple features/attributes, provides high performance for large data sets, and interoperability with other Autodesk products. Supports spatial indexing and is a valid alternative to database storage.</td>
</tr>
<tr>
<td>OSGeo FDO Provider for SHP</td>
@@ -37,11 +37,11 @@
</tr>
<tr>
<td>OSGeo FDO Provider for WFS</td>
- <td>Read-only access to feature data in an OGC WFS-based data store. Supports a client/server environment and retrieves geospatial data encoded in GML from one or more Web Feature Services sites. Client/server communication is encoded in XML with the exception of feature geometries, which are encoded in GML. Note that there is no public API documentation for this provider; all WFS functionality is accessible through the base ProductName API.</td>
+ <td>Read-only access to feature data in an OGC WFS-based data store. Supports a client/server environment and retrieves geospatial data encoded in GML from one or more Web Feature Services sites. Client/server communication is encoded in XML with the exception of feature geometries, which are encoded in GML. Note that there is no public API documentation for this provider; all WFS functionality is accessible through the FDO API.</td>
</tr>
<tr>
<td>OSGeo FDO Provider for WMS</td>
- <td>Read-only to feature data in an OGC WMS-based data store. Web Map Service (WMS) produces maps of spatially referenced data dynamically from geographic information, which are generally rendered in PNG, GIF, or JPEG, or as vector-based Scalable Vector Graphics (SVG) or Web Computer Graphics Metafile (WebCGM) formats</td>
+ <td>Read-only to feature data in an OGC WMS-based data store. Web Map Service (WMS) produces maps of spatially referenced data dynamically from geographic information, which are generally rendered in PNG, GIF, or JPEG formats</td>
</tr>
</tbody>
</table>
Modified: trunk/www/featureDescriptions.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/featureDescriptions.html?view=diff&rev=35&p1=trunk/www/featureDescriptions.html&p2=trunk/www/featureDescriptions.html&r1=34&r2=35
==============================================================================
--- trunk/www/featureDescriptions.html (original)
+++ trunk/www/featureDescriptions.html 2006-07-19 03:24:40+0000
@@ -7,7 +7,7 @@
</head>
<body>
<h1>FDO Open Source - Feature Descriptions</h1>
- <p>This page describes the features referenced in the feature matrix pages.</p>
+ <p>This page describes the features referenced in the <a href="history.html">feature matrix</a> page.</p>
<table border="1" rules="all">
<thead>
<tr>
@@ -84,7 +84,7 @@
</tr>
<tr>
<td>Schema Overrides</td>
- <td>This allows FDO applications to customize the mappings between Feature (logical) Schemas and the Physical Schema of the Provider DataStore. Schema Mappings will be customized through Schema Override sets. Each Feature Schema may have a number of associated sets, one per FDO Provider that the Feature Schema might be applied against.</td>
+ <td>This allows FDO applications to customize the mappings between Feature (logical) Schemas and the Physical Schema of the Provider data store. Schema Mappings will be customized through Schema Override sets. Each Feature Schema may have a number of associated sets, one per FDO Provider that the Feature Schema might be applied against.</td>
</tr>
<tr>
<td>Foreign Schemas</td>
@@ -96,7 +96,7 @@
</tr>
<tr>
<td>Data Property Constraints</td>
- <td>Specify that a property or list of properties taken together have unique values for all objects of that class in a datastore. A unique constraint that is based on a list of two or more properties is called a composite unique constraint. This constraint type applies to all data property types except for Boolean, BLOB, and CLOB. A Boolean property can be included if it is part of a composite unique constraint.</td>
+ <td>Specify that a property or list of properties taken together have unique values for all objects of that class in a data store. A unique constraint that is based on a list of two or more properties is called a composite unique constraint. This constraint type applies to all data property types except for Boolean, BLOB, and CLOB. A Boolean property can be included if it is part of a composite unique constraint.</td>
</tr>
<tr>
<td>Inheritance</td>
@@ -119,7 +119,7 @@
</tr>
<tr>
<td>XML Configuration</td>
- <td>Supports provider-specific configuration. For the Raster provider, the parameters are logical schema, schema overrides, and spatial context. For the WMS provider, the only parameter is logical schema. For the ODBC provider, the parameters are</td>
+ <td>Supports provider-specific configuration.</td>
</tr>
<!--
<tr>
Modified: trunk/www/gettingStarted.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/gettingStarted.html?view=diff&rev=35&p1=trunk/www/gettingStarted.html&p2=trunk/www/gettingStarted.html&r1=34&r2=35
==============================================================================
--- trunk/www/gettingStarted.html (original)
+++ trunk/www/gettingStarted.html 2006-07-19 03:24:40+0000
@@ -18,7 +18,7 @@
makefile.am and configure.in files found in the FDO source directories
on Linux.
<h3>Windows</h3>
- <p>The assumption is that you are using Visual Studio 2005.</p>
+ <p>The assumption is that you are using Visual Studio Express, Standard or Professional 2005.</p>
<p>
Use the installation path to set up the environment so that headers
and libraries can be located at compile time,
@@ -109,7 +109,6 @@
<h2>Write the Code to Connect to a Provider</h2>
<p>Do the following:</p>
<ol>
- <li></li>
<li>Get the list of installed providers</li>
<li>Create a connection manager</li>
<li>Create a connection</li>
@@ -117,7 +116,7 @@
<li>Get the connection properties</li>
<li>Get values for the connection properties</li>
<li>Set the connection properties</li>
- <li>Open a connection<li>
+ <li>Open a connection</li>
<li>Open a pending connection</li>
</ol>
<h3>Create a Provider Registry</h3>
Modified: trunk/www/glossary.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/glossary.html?view=diff&rev=35&p1=trunk/www/glossary.html&p2=trunk/www/glossary.html&r1=34&r2=35
==============================================================================
--- trunk/www/glossary.html (original)
+++ trunk/www/glossary.html 2006-07-19 03:24:40+0000
@@ -12,7 +12,7 @@
<dd>
A set of classes and their corresponding properties and relationships.
Each Feature Schema typically contains the classes for a specific domain,
- for example, Electrical Schema, Gas Schema, etc..
+ for example, Electrical Schema, Gas Schema, etc.
The Feature Schema defines its classes in an FDO provider-independent form.
</dd>
<dt>GML</dt
@@ -25,7 +25,7 @@
and an RDBMS schema might be composed of multiple logical schemas.
</dd>
<dt>OGC</dt>
- <dd>Open Gis Consortium</dd>
+ <dd>Open GIS Consortium</dd>
<dt>Schema Mapping</dt>
<dd>
A set of hints that determine how Feature Schemas are stored
@@ -35,7 +35,7 @@
<dt>Tolerance</dt>
<dd>
Used to determine when two points are close enough to be considered to be
- equivalent in certain spatial tests. In FDOL, the tolerance value is used
+ equivalent in certain spatial tests. In FDO, the tolerance value is used
as a radius around a position rather than as a distance along an axis.
In the majority of cases, the distance between the points is compared
to the tolerance using the 'less than' predicate. If the X and Y tolerances
Modified: trunk/www/history.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/history.html?view=diff&rev=35&p1=trunk/www/history.html&p2=trunk/www/history.html&r1=34&r2=35
==============================================================================
--- trunk/www/history.html (original)
+++ trunk/www/history.html 2006-07-19 03:24:40+0000
@@ -20,7 +20,7 @@
</p>
<ul>
<li>
- Provides an object based feature model of geospatial data
+ Provides an object-based feature model of geospatial data
that is generic and independent of any particular native implementation.
</li>
<li>
@@ -37,18 +37,18 @@
</li>
<li>
Defines a capabilities API to allow clients to determine specific
- capabilities of a particular provider and thus respond correctly no what
- provider they are connected to.
+ capabilities of a particular provider and thus respond correctly
+ to the provider to which they are connected.
</li>
<li>
Allows new commands and schema additions to be easily added over time to
- the generic APPI and allows custom commands to be added to a particular
+ the generic API and allows custom commands to be added to a particular
provider. The capabilities API allows a client to discover the custom commands.
</li>
</ul>
<h2>Before Open Source</h2>
<p>
- The first version of FDO was shipped with the Autodesk Map 2005 product
+ The first version of FDO was shipped with the Autodesk Map 3D 2005 product
in the spring of 2004. It included providers for Oracle and SDF.
Version 2.0 added the ArcSDE provider, and
version 3.0 added providers for MySQL, SQL Server, ODBC, SHP, Raster,
Modified: trunk/www/index.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/index.html?view=diff&rev=35&p1=trunk/www/index.html&p2=trunk/www/index.html&r1=34&r2=35
==============================================================================
--- trunk/www/index.html (original)
+++ trunk/www/index.html 2006-07-19 03:24:40+0000
@@ -130,8 +130,8 @@
<a href="history.html">History</a><br>
<a href="productsUsingFdo.html">Products Using FDO</a><br>
<a href="featureDescriptions.html">Feature Descriptions</a><br>
- <a href="OSProviderOverviews.html">Open Source Provider Overviews</a><br>
- <a href="OSFeatureMatrix.html">Open Source Feature Matrix</a><br>
+ <a href="OSProviderOverviews.html">Provider Overviews</a><br>
+ <a href="OSFeatureMatrix.html">Feature Matrix</a><br>
<!--
<a href="enterpriseProviderOverviews.html">Enterprise Provider Overviews</a><br>
<a href="enterpriseFeatureMatrix.html">Enterprise Feature Matrix</a><br>
Modified: trunk/www/productsUsingFdo.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/productsUsingFdo.html?view=diff&rev=35&p1=trunk/www/productsUsingFdo.html&p2=trunk/www/productsUsingFdo.html&r1=34&r2=35
==============================================================================
--- trunk/www/productsUsingFdo.html (original)
+++ trunk/www/productsUsingFdo.html 2006-07-19 03:24:40+0000
@@ -16,27 +16,27 @@
</thead>
<tbody>
<tr>
- <td>Autodesk Map 2005</td>
+ <td>Autodesk Map 3D 2005</td>
<td>1.0</td>
</tr>
<tr>
- <td>Autodesk Map 2006</td>
+ <td>Autodesk Map 3D 2006</td>
<td>2.0</td>
</tr>
<tr>
- <td>Autodesk Map 2007</td>
+ <td>Autodesk Map 3D 2007</td>
<td>3.0</td>
</tr>
<tr>
- <td>Autodesk MapGuide 2007</td>
+ <td>Autodesk MapGuide Enterprise 2007</td>
<td>3.1</td>
</tr>
<tr>
- <td>OSGeo MapGuide 1.0.0</td>
+ <td>OSGeo MapGuide OpenSource 1.0.0</td>
<td>3.0</td>
</tr>
<tr>
- <td>OSGeo MapGuide 1.0.1</td>
+ <td>OSGeo MapGuide OpenSource 1.0.1</td>
<td>3.1</td>
</tr>
</tbody>
More information about the Fdo-commits
mailing list