TGIS_LayerSqlSdeAbstract class

DK11 for ActiveX | TatukGIS_XDK11.TGIS_LayerSqlSdeAbstract | Classes | Methods | Properties

Encapsulation of abstract ArcSDE SQL layer.

Available also on: Delphi | .NET | Java.

// C#
public class TGIS_LayerSqlSdeAbstract : ITGIS_LayerSqlSdeAbstract, ITGIS_LayerVectorSqlAbstractEvents 
{
}

' VisualBasic
Public Class TGIS_LayerSqlSdeAbstract
  Implements ITGIS_LayerSqlSdeAbstract
  Implements ITGIS_LayerVectorSqlAbstractEvents
End Class

// Oxygene
type
  TGIS_LayerSqlSdeAbstract = public class
  end;

ITGIS_LayerSqlSdeAbstract ITGIS_LayerVectorSqlAbstractEvents

This layer can be opened by opening the file name_of_layer.ttkls or embedding all parameters to Path property as CRLF or '\n' delimited string.

Structure of this file must be:

[TatukGIS Layer]
Storage=SdeBinary|SdeOgcWkb|SdeLob|SdeStGeometry|SdeSdoGeometry|SdeGeometry|SdeGeography
Layer=name|name;schema|name;schema;catalog
Dataset=name
Features=table/view name; if provided will replace standard features table
Dialect=MSSQL|ORACLE
Version=OLD|NEW - uses only in save (import) mode; in read mode version is automatically recognized; NEW is default one;
ReadOnly=True|False
ADO=ADO connection string if not exist then DBX connection will be used
LoginPrompt=1|0
ForceNewConnection=True|False - force new connection instead of shared one
GridSize1=
GridSize2=
GridSize3=
XFalse=
YFalse=
ScaleXY=
ZFalse=
ScaleZ=
MFalse=
ScaleM=
DriverName=see DBExpress help for TSQL Connection
GetDriverFunc=see DBExpress help for TSQL Connection
VendorLib=see DBExpress help for TSQL Connection
LibraryName=see DBExpress help for TSQL Connection
...
Parameters key=value
...

For example:

[TatukGIS Layer]
Storage=SdeBinary
Layer=Rivers
Dialect=MSSQL
ADO="DSN=MyVectorLayer"

[TatukGIS Layer]
Storage=SdeBinary
Layer=Rivers
Dialect=MSSQL
ADO="DSN=MyVectorLayer"
Version=New
GridSize1=540
GridSize2=1620
GridSize3=4860
XFalse=6491283.535
YFalse=5882125.889
ScaleXY=411272.697
ZFalse=1000
ScaleZ=1000
MFalse=1000
ScaleM=1000

This layer can also be opened by providing SQLParameters property.

OnPassword event will be fired upon connecting to a database to resolve <#user#>, <#password#> or any other <#token#> embedded into connection options.

Note :

• The ArcSDE Geodatabase implementation does not depend on any ESRI middleware. Before using it you need to launch the ArcSDE post-installation setup on properly Microsoft SQL Server or Oracle instance. Then you should make any database as a spatially enabled database with the ArcSDE repository defined. It reads a layer with taking advantage of spatial indexes for fast spatial queries. The implementation support geometry object with Z (elevation) and/or M (measure) in read and write mode for all geometry storage standards where it was provided by ESRI product implementation (except Oracle Spatial because of casting SDO_GEOMETRY to WKB).

• Try to use the uppercase layer name (in the meaning of Layer=xxxx). Layer name could or could not be case insensitive on different database engines.

Currently, support:

• ArcSDE for MS SQL Server (ArcGIS 9.1 and early versions)
• ArcSDE Personal for MS SQL Express Edition (ArcGIS 9.2)
• ArcSDE Workgroup for MS SQL Express Edition (ArcGIS 9.2)
• ArcSDE Enterprise for MS SQL Standard, Workgroup, Enterprise Edition (ArcGIS 9.2)
• ArcSDE for Oracle (ArcGIS 9.1 and later versions)

Physical storage of feature data in the geodatabase uses standard data types or provided by ESRI depend on type of DBMS. Summary of the available storage types for feature geometry within each DBMS is provided in the table below:

Summary of the available storage parameter name for feature geometry within each DBMS is provided in the table below:

SCB - ArcSDE Compressed Binary LOB - Large Object Binary data type to store SCB WKB - OpenGIS Consortium (OGC) Well-Known Binary representation for 2D geometry P - ArcSDE Personal for MS SQL Express Edition W - ArcSDE Workgroup for MS SQL Express Edition E - ArcSDE Enterprise for MS SQL Standard, Workgroup, Enterprise Edition N/A - not available in ESRI product implementation

GEOMETRY, GEOGRAPHY - Microsoft's geometry and geography spatial types. These types are available in SQL Server 2008 or later version.

Note :

• To work with ADO.NET and new SQL server 2008 geometry types, the ttkADONET.dll and Microsoft.SqlServer.Types.dll from Microsoft SQL Server System CLR Types libraries are required for client applications.
• If there are different CLR types installed, use assembly redirection policy for your process to force SQL Client to load a new version (define runtime assemblyBinding in App.config file)
• It is possible to update attribute values of feature or rebuild structure (without geometry modification) and delete whole feature objects.

ArcSDE Personal and Workgroup geodatabases stored in SQL Server Express databases use the ArcSDE Compressed Binary storage type Storage=SdeBinary. You cannot specify another geometry storage type. ArcSDE Enterprise geodatabases stored in SQL Standard, Workgroup, Enterprise Edition databases use the ArcSDE Compressed Binary storage type Storage=SdeBinary or Well-Known Binary representation Storage=SdeOgcWkb.

The implementation support ArcSDE on Oracle for ST_Geometry and SDO_Geometry data type only in read mode with exception features data in write mode.

The implementation supports two versions of the geodatabase repository structure. The first one Version=Old is equivalent to Geodatabase 1.0 which regards 8.3 and early versions of ArcSDE for MS SQL Server. The second one Version=New is equivalent to Geodatabase 2.0 which regards to 9.0 and later versions of ArcSDE for MS SQL Server and ArcSDE for Oracle.

Currently supported geodatabase versions (repository structure):

• Version=Old - ArcSDE for MS SQL Server (ArcGIS 8.3 and early versions)
• Version=New - ArcSDE for MS SQL Server (ArcGIS 9.0 and later versions)
• Version=New - ArcSDE for Oracle (ArcGIS 9.0 and later versions)

Use the above setting only in import mode. At reading mode version is automatically recognized. If “Version” parameter wasn't provided “New” is the default value.

Should be provided parameters of spatial index and coordinate reference system setting in following form:

GridSize1=540
GridSize2=1620
GridSize3=4860
XFalse=6491283.535
YFalse=5882125.889
ScaleXY=411272.697
ZFalse=1000
ScaleZ=1000
MFalse=1000
ScaleM=1000

Spatial index setting:

• GridSize1 - Spatial grid cell size on the first level. If the parameter wasn't provided the value of the parameter is equal 1000.
• GridSize2 - Spatial grid cell size on the second level. If the parameter wasn't provided the value of the parameter is equal 0.
• GridSize3 - Spatial grid cell size on the third level. If the parameter wasn't provided the value of the parameter is equal 0.

Coordinate reference system setting:

• XFalse - The X offset used when transforming ground coordinates to internal system coordinates. If the parameter wasn't provided a value of the parameter is automatically calculated.
• YFalse - The Y offset used when transforming ground coordinates to internal system coordinates. If the parameter wasn't provided a value of the parameter is automatically calculated.
• ScaleXY - The scale factor to apply when transforming ground coordinates to internal system coordinates. If the parameter wasn't provided a value of the parameter is automatically calculated.
• ZFalse - The Z (elevation) offset to transform ground coordinates to internal system coordinates. If the parameter wasn't provided a value of the parameter is equal 0.
• ScaleZ - The scale factor to use when transforming Z values to internal system coordinates. If the parameter wasn't provided a value of the parameter is equal 1.
• MFalse - The M (measure) offset to transform ground coordinates to internal system coordinates. If the parameter wasn't provided a value of the parameter is equal 0.
• ScaleM - The scale factor to use when transforming M values to internal system coordinates. If the parameter wasn't provided the value of the parameter is equal 1.

Microsoft OLE DB Provider for Oracle (MSDAORA) at this moment doesn't support BLOB data type. Only in read mode access, it is possible to set initialization parameter GeometryFieldCast=LongRaw. This setting could be useful with another type of Oracle database connection drivers in read-only mode for cast BLOB to LONG RAW.

Sql Server Native Client (SQLNCLI) must be used with DataTypeCompatibility=80 option to support BLOB data type, otherwise empty geometry data will be returned.

Summary of the available RebuildSpatialIndex procedure for optimize the spatial index of geometry within each DBMS is provided in the table below:

This implementation manages the spatial index throughout the life of the layer. As features are inserted, updated or deleted the spatial index is automatically updated. Advanced users of ArcSDE often experiment with the spatial index, trying different cell sizes and different grid level configuration. The RebuildSpatialIndex procedure can help you optimize the spatial index by changing the grid cell sizes and adding new grid levels with altering operation. Users may assign the spatial grid index one, two or three grid levels each with its own distinct cell size. The mandatory first grid level has the smallest cell size. The optionally second and third grid level could be disabled by setting them to zero. If enabled the next (second, third) grid cell size must be at least three times larger then the previous grid cell size. Keep in mind that the default configuration of one level grid with the size of 1000 is specified in the units of the feature class's coordinate system. This means if your feature class is in a geographic coordinate system and you use the default parameter setting, all features will be placed in a single grid cell. This will provide no benefits to performance. This procedure is recommended only for experienced users. Operation is possible for the following storage types:

• SdeBinary
• SdeOgcWkb
• SdeLob
• SdeStGeometry