|
The supported geometry storage mechanisms for ArcSDE are:
- Binary geometry schema
- SQL Geometry Type
The geometry storage mechanism is identified when the layer is created. Not all storage mechanisms can be supported on all databases. The following table shows
which storage schemas are available for each database:
| IBM DB2 |
YES |
YES |
| Informix |
YES |
YES |
| MS SQL Server |
YES |
YES |
| Oracle |
YES |
YES |
| PostgreSQL |
NO |
YES |
While the logical geometry model for all storage schemas is the same, not all
ArcSDE functionality is available in all formats. For example, the OpenGIS specification
does not define elevations and measures on coordinates. The following chart shows the functionality available for each storage mechanism:
| 2D geometry |
YES |
YES |
| Elevations (Z) |
YES |
YES |
| Measures (M) |
YES |
NO |
| Annotation |
YES |
YES |
| CAD |
YES |
YES |
| SQL Functions |
NO |
YES |
| AREA or LENGTH as a spatial search constraint |
YES |
YES |
*The specification for the SQL Spatial Type has been extended to support ArcSDE functionality. This is possible because the actual geometry type structure is hidden
behind the SQL function interfaces.
|
