Command

Notes on using SDX+ for Oracle Spatial

  1. First of all, to be sure that there are records in User_sdo_geom_metadata view, or the new created datasource will have no datasets. Resolving method: at outside add records to ser_sdo_geom_metadata manually according to actual data and then create a new datasource.
  2. Primary Key is needed in spatial table. It is highly recommended that you specify one if there is not.
  3. Now the following five dataset types are supported in SDX+ for Oracle Spatial: Point, line, region, text and tabular. And data in point, line and region dataset are stored using Mdsys.Sdo_Geometry field while the text dataset has the same storage format as that in SDX+ for Oracle.
  4. Sdo_Gtype of Mdsys.Sdo_Geometry is supported:

  5. 1, 2001, 3001, 2005, 5

    2, 2002, 3002, 2006, 6

    3, 2003, 3003, 2007, 7

  6. Projection transformation is not supported.
  7. Dataset encoding is not supported.
  8. After creating a new datasource, the system will not recompute boundary and index for existing datasets, so you need to recompute boundary and index for them if there is no features in the dataset.
  9. Image Dataset: now there is no image format special for Oracle Spatial, and the storing format is the same as that of SDX+ for Oracle.
  10. Rules of naming a dataset:

    For dataset not created in AvisMap, the dataset name is "'Table name'_'spatial data column name'", such as spatial data column Shape in Street table, the name will be Street_Shape. To distinguish serveral SDO_GEOMETRY columns existing in a single table, one SDO_GEOMETRY column will respond to one dataset.

    For dataset created in AvisMap, the name is the same as that of the table.

mapping software provider