About SDM for Oracle Spatial

• You should make sure there are records in the database view: User_sdo_geom_metadata, otherwise no dataset will be included in a new Oracle Spatial datasource. The possible solution is: users try to add records to the view User_sdo_geom_metadata outside manually according to the particular data and then create datasource.
• Primary Key must be specified in spatial data table.
• Point, line, region, text and tabular datasets are supported in SDM for Oracle Spatial engine. Where, the geospatial data in point, line and region datasets is stored in the field Mdsys.Sdo_Geometry, the text dataset uses the same storage format with the one in SDM for Oracle.
• The supported Sdo_Gtypes in Mdsys.Sdo_Geometry:
• 1/2001/3001/2005/5
  2/2002/3002/2006/6
  3/2003/3003/2007/7
  
• Projection transformation is not supported in SDM for Oracle Spatial.
• Encoded type of dataset is not supported in SDM for Oracle Spatial.
• Once a SDM for Oracle Spatial datasource has been created, it will not keep the boundaries and indexes for all connected datasets or the ones being copied form outside, if there is not any geometry in dataset, please re-compute or rebuild boundary and spatial index for the dataset.
• Image dataset in SDM for Oracle Spatial is not the image format regulated by Oracle Spatial but uses the format as the one in SDM for Oracle.
• Dataset Name Regulations in SDM for Oracle Spatial: To the non AvisMap created dataset, the name is like: TableName_GeospatialcolumnName, for example, a Shapefile Street with geospatial column Shape, the corresponding dataset name in AvisMap is: Street_Shape. If there are multi Sdo_Geometry type columns in a table, each column will have a dataset or a layer to correspond. To the dataset created by AvisMap software, its name is identical with the table.