Changes between Version 6 and Version 7 of FDORfc16

Timestamp:

03/18/08 19:43:29 (17 years ago)

Author:

traianstanev

Comment:

--

FDORfc16

@@ -33 +33 @@
 
  * Data stored and consumed in native SQLite format, and therefore accessible to other SQLite-based applications;
- * Geometry will be serialized as BLOBs in FDO geometry format (FGF). Other ways that may be considered are storing points as X,Y columns and also geometry as WKB format;
+ * Geometry will be serialized as BLOBs in FDO geometry format (FGF), WKB , or WKT 1.2 format. The type of geometry encoding will be specified in the geometry_columns table (see below) in a column called g_geometry_format. In addition, the provider may support point geometry with coordinates stored in non-geometric columns, via a connection string setting.
  * A non-persistent, spatial index usable for BBOX queries built on the fly and valid for the duration of the FDO connection;
  * Execution of arbitrary SQL commands;
- * A metadata table where the geometry coordinate system is stored in WKT or EPSG form. In addition, PRJ files will be supported as alternative means of specifying a coordinate system when a metadata table is undesirable;
+ * Metadata about feature geometry and coordinate systems will be stored in OGC geometry_columns and spatial_ref_sys tables, according to Section 6.2.1 of the OGC Simple Feature spec, Part 2;
  * A tentative list of supported FDO commands : !DescribeSchema, Select, !SelectAggregates, Insert, Update, Delete, !GetSpatialContexts, arbitrary SQL, !ApplySchema, !CreateDataStore;