ArcGIS Server Banner

Feature datasets in a geodatabase in PostgreSQL

Feature datasets in a geodatabase in PostgreSQL
Release 9.3 E-mail This TopicPrintable VersionGive Us feedback

Feature datasets are objects that allow you to group together related feature classes.

You would use a feature dataset to group feature classes that

Feature datasets contain feature classes and can also contain topologies, relationship classes, feature-linked annotation, geometric networks, network datasets, schematics, terrains, and cadastral fabrics. Use the following links to read about different components of feature datasets in PostgreSQL:

The following describes how a feature dataset appears in ArcCatalog, a PostgreSQL DBMS, and an XML workspace document.

Feature datasets in ArcCatalog

In the Catalog tree, feature datasets stored in a PostgreSQL database look like the following:

Feature dataset in ArcCatalog (PostgreSQL)

This feature dataset, landbase, is owned by user emily and resides in the database posty.

When the feature dataset is expanded in the Catalog tree, you can see all the feature classes and other data objects that are in it.

Expanded feature dataset in ArcCatalog

Feature datasets in a PostgreSQL DBMS

In the database, feature datasets are virtual collections of feature classes. They are grouped together by a common dataset ID, which is maintained in the gdb_featuredataset system table and associated with the gdb_objectclasses system table.

For the landbase feature dataset example, the feature class, parcels, is linked to the landbase feature dataset through the gdb_objectclasses table. Dashed lines indicate implicit relationships between columns.

Feature dataset system tables in PostgreSQL

Because feature datasets are a virtual collection of objects, feature classes in feature datasets are just like stand-alone feature classes in that they have their own records in the gdb_featureclasses table and all the other tables associated with feature classes (sde_layers, sde_table_registry, sde_geometry_columns, sde_column_registry, sde_spatial_references, and gdb_object_classes). Since feature classes associated with feature datasets are database objects in their own right, they cannot have the same name as other tables or stand-alone feature classes in the same schema in the database.

Topologies, relationship classes, geometric networks, network datasets, terrain datasets, schematic datasets, and cadastral fabrics utilize additional system tables. These are described in separate topics that can be accessed using the links at the beginning of this topic.

Feature datasets in an XML workspace document

Feature datasets are grouped under the DatasetDefinitions tag in an XML document and separated by a DataElement tag of type FeatureDataset. The XML document entry for the landbase dataset looks like the following:

<DatasetDefinitions xsi: type="esri:ArrayOfDataElement">
 <DataElement xsi:type="esri:DEFeatureDataset">
  <CatalogPath>/V=sde.DEFAULT/FD=posty.emily.landbase</CatalogPath> 
  <Name>posty.emily.landbase</Name> 
  <MetadataRetrieved>false</MetadataRetrieved> 
  <DatasetType>esriDTFeatureDataset</DatasetType> 
  <DSID>-1</DSID> 
  <Versioned>true</Versioned> 
  <CanVersion>true</CanVersion> 
- <Extent xsi:type="esri:EnvelopeN">
     <XMin>503924.656249088</XMin> 
     <YMin>680110.56250334</YMin> 
     <XMax>512514.562497088</XMax> 
     <YMax>689084.187511697</YMax> 
- <SpatialReference xsi:type="esri:ProjectedCoordinateSystem">
  <WKT>PROJCS["NAD_1927_StatePlane_Alabama_East_FIPS_0101",GEOGCS["GCS_North_American_1927",DATUM["D_North_American_1927",SPHEROID["Clarke_1866",6378206.4,294.9786982]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",500000.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-85.83333333333333],PARAMETER["Scale_Factor",0.99996],PARAMETER["Latitude_Of_Origin",30.5],UNIT["Foot_US",0.3048006096012192]]</WKT> 
     <XOrigin>489871.255812</XOrigin> 
     <YOrigin>665787.099562</YOrigin> 
     <XYScale>499999.999534338</XYScale> 
     <ZOrigin>0</ZOrigin> 
     <ZScale>8192</ZScale> 
     <MOrigin>0</MOrigin> 
     <MScale>8192</MScale> 
     <XYTolerance>6.56166666666667E-04</XYTolerance> 
     <ZTolerance>2</ZTolerance> 
     <MTolerance>2</MTolerance> 
     <HighPrecision>true</HighPrecision> 
   </SpatialReference>
  </Extent>
- <SpatialReference xsi:type="esri:ProjectedCoordinateSystem">
  <WKT>PROJCS["NAD_1927_StatePlane_Alabama_East_FIPS_0101",GEOGCS["GCS_North_American_1927",DATUM["D_North_American_1927",SPHEROID["Clarke_1866",6378206.4,294.9786982]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",500000.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-85.83333333333333],PARAMETER["Scale_Factor",0.99996],PARAMETER["Latitude_Of_Origin",30.5],UNIT["Foot_US",0.3048006096012192]]</WKT> 
     <XOrigin>489871.255812</XOrigin> 
     <YOrigin>665787.099562</YOrigin> 
     <XYScale>499999.999534338</XYScale> 
     <ZOrigin>0</ZOrigin> 
     <ZScale>8192</ZScale> 
     <MOrigin>0</MOrigin> 
     <MScale>8192</MScale> 
     <XYTolerance>6.56166666666667E-04</XYTolerance> 
     <ZTolerance>2</ZTolerance> 
     <MTolerance>2</MTolerance> 
     <HighPrecision>true</HighPrecision> 
    </SpatialReference>
   </DataElement>
.
...all other DataElements...
.
</DatasetDefinitions>

Top of page