Show Navigation | Hide Navigation

Feature datasets in a geodatabase in Informix
Release 9.2 Last modified April 3, 2008

This topic contains information on:

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

You would use a feature dataset to group feature classes that:

Are stored in the same coordinate system
Participate in a topology
Are part of a geometric network, network dataset, or terrain dataset

In the train depot and railroad track example presented in the feature class topic, you could group these two related feature classes together by placing them in the same dataset. You could subsequently create a topology to define how these two feature classes interact.

The following describes how a feature dataset would appear in ArcCatalog, in an Informix DBMS, and in an XML document. Following that is a description of how topologies, networks, and terrains are represented in ArcCatalog, the DBMS, and XML.

Feature datasets in ArcCatalog

In the ArcCatalog tree, feature datasets look like the following:

This feature dataset is named USA, is owned by user vtest, and resides in a database called sde92.

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

Feature dataset, expanded, in ArcCatalog

Feature datasets in an Informix 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.

The following are the tables involved in a feature dataset:

Feature dataset tables in Informix

For the USA feature dataset example, the feature class Cities would be linked to the USA feature dataset through the gdb_objectclasses table.

Topologies, geometric networks, network datasets, and terrain datasets utilize additional system tables. These will be described in the corresponding sections that follow.

Feature datasets in an XML 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 would look like the following:

<DatasetDefinitions xsi: type="esri:ArrayOfDataElement">
 <DataElement xsi:type="esri:DEFeatureDataset">
  <CatalogPath>/V=sde.DEFAULT/FD=sde92:vtest.USA</CatalogPath> 
  <Name>sde92:vtest.USA</Name> 
<Children xsi:type="esri:ArrayOfDataElement">
<DataElement xsi:type="esri:DEFeatureClass">
  <CatalogPath>/V=sde.DEFAULT/FD=sde92:vtest.USA/FC=sde92:vtest.Roads</CatalogPath> 
  <Name>sde92:vtest.Roads</Name> 
  <DatasetType>esriDTFeatureClass</DatasetType> 
  <DSID>17</DSID> 
  <Versioned>false</Versioned> 
  <CanVersion>true</CanVersion> 
  <HasOID>true</HasOID> 
  <OIDFieldName>objectid</OIDFieldName> 
<Fields xsi:type="esri:Fields">
<FieldArray xsi:type="esri:ArrayOfField">
<Field xsi:type="esri:Field">
  <Name>objectid</Name> 
  <Type>esriFieldTypeOID</Type> 
  <IsNullable>false</IsNullable> 
  <Length>4</Length> 
  <Precision>10</Precision> 
  <Scale>0</Scale> 
  <Required>true</Required> 
  <Editable>false</Editable> 
  <AliasName>OBJECTID</AliasName> 
  <ModelName>OBJECTID</ModelName> 
  </Field>
.
...all other DataElements...
.
</DatasetDefinitions>

Top of page

Topologies

Topologies are rules that enforce data integrity and manage the behavior of spatially related feature classes. A geodatabase topology stores information about the feature classes (which must be in the same feature dataset) that participate in the topology, the cluster tolerance assigned to the topology, the relative rank of each feature class in the topology, and a list of the rules that apply to that topology.

For more information on the concepts related to topologies, see Topology basics and Topology in ArcGIS.

Topologies in ArcCatalog

Topologies in the ArcCatalog tree appear under the feature dataset in which the participating feature classes reside. The topology itself will look like the following:

You can right-click the topology and click Properties to open the Topology Properties dialog box. The General tab lists the name of the topology and the cluster tolerance. You can click on the Feature Classes tab to see which feature classes within the feature dataset participate in this topology.

Clicking on the Rules tab will show you the rules that apply to the topology. After the topology has been validated, you can generate a list of the errors and exceptions for each rule from the Errors tab.

Topologies in an Informix DBMS

In the DBMS, the system tables associated with a topology are gdb_topologies, gdb_toporules, and gdb_topoclasses. The gdb_topologies table stores the name of the topology and is associated with the gdb_featuredataset table, which provides the link between the topology and the participating feature classes by way of the gdb_objectclasses table.

The gdb_toporulestable stores the rules of the toplogy and is related to the gdb_topologiestable and the gdb_objectclasses table.

When you validate a topology, the dirty areas and topology errors found associated with each topology are stored in a set of tables in the schema of the user connected to the geodatabase. These are the t_<id>_dirtyareas, t_<id>_lineerrors, t_<id>_pointerrors, and t_<id>_polyerrors tables. The id in the table names correspond to the value in the id field of the gdb_topologies table. Each error table stores the violated rule in the toporuleid field. This field is linked to the gdb_toporules table. Each error table is also associated to the feature class containing the error by way of the gdb_objectclasses table.

The following is a definition of the dirty areas and topology errors tables and an example of the topology tables as they appear in a InformixDBMS.

t_<id>_dirtyareas
Dirty areas, or unvalidated parts of the topology, are stored in the geodatabase as geometries. They are tracked in the t_<id>_dirtyareas table.

This table will not appear in your database until you have validated a topology.

Field name	Field type	Description
objectid	Int	Unique identifier of the dirty area feature in the topology NOT NULL
isretired	Int	Code indicating whether the dirty area has reached the maximum number of vertices (250); when this limit is reached, a new dirty area feature will be created and this one retired (IsRetired value changes to 1). 0 = Max verticies limit not yet reached 1 = Max vertices limit
dirtyarea	St_multipolygon	Shape field

t_<id>_lineerrors, t_<id>_pointerrors, and t_<id>_polyerrors
Any violations of the topology rules are represented as error features. As with dirty areas, these error features are also stored and managed in separate topology error tables. These tables all share an almost identical schema definition, with the exception of the additional fields specific to the shape type of the topology error. As indicated by the table names, they store information about topology errors based on the type of feature for which the error occurred—line, point, or polygon.

These tables will not appear in your database until you have validated a topology.

Field name	Field type	Description
objectid	Int	Unique ID of the topology error feature in the specified topology error table; topology errors do not have unique IDs in the topology, only in their specific table.
originclassid	Int	Object class ID of the origin feature class
originid	Int	Feature ID of the feature from the origin feature class that is related to the topology error.
destclassid	Int	Object class ID of the destination feature class
destid	Int	Feature ID of the feature from the destination feature class that is related to the topology error.
toporuletype	Int	The type of topology rule; corresponds to a value from the esriTopologyRuleType constant
toporuleid	Int	The ID of the topology rule; foreign key to the ID field in the GDB_TOPORULES table
isexception	Int	A code that indicates whether or not the topology error has been marked as an exception. 0 = Not an exception (the default) 1 = Marked as an exception
shape	For lineerrors = St_multilinestring For pointerrors = St_point For polyerrors = St_multipolygon	Indicates shape type

Click the following link to view a diagram of the tables for a validated topology. To view the diagram, you will need Adobe Acrobat Reader.

Informix topology diagram

Dashed lines indicate implicit relationships between tables. The database name field in the gdb_objectclasses, gdb_topologies, and gdb_featuredataset tables all contain the same value; the relationship lines were left off the diagram to avoid clutter. Similarly, the owner field in these three tables also contains the same value, though the relationship lines were not drawn on the diagram.

The dirty areas and topology errors tables get created in the user's schema, unlike the other tables, which are system tables that are part of the ArcSDE administrator (SDE) user's schema.

Topologies in an XML document

Topologies are types of datasets, so they appear in an XML document under a DataElement tag of type FeatureDataset. The topology rules are included and grouped with a TopologyRule tag. For the Landbase_rel_Topology example in the Landbase_rel feature dataset, the entry in the XML document looks like the following:

<DatasetDefinitions xsi:type="esri:ArrayOfDataElement">
<DataElement xsi:type="esri:DEFeatureDataset">
    <CatalogPath>/V=sde.DEFAULT/FD=sde92:vtest.landbase_rel</CatalogPath> 
    <Name>sde92:vtest.landbase_rel</Name> 
  <Children xsi:type="esri:ArrayOfDataElement">
    <DataElement xsi:type="esri:DETopology">
          <CatalogPath>/V=sde.DEFAULT/FD=sde92:vtest.landbase_rel/TOPO=sde92:vtest.landbase_rel_Topology</CatalogPath> 
        <Name>sde92:vtest.landbase_rel_Topology</Name> 
        <DatasetType>esriDTTopology</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>1</ZScale> 
             <MOrigin>0</MOrigin> 
             <MScale>1</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>
      <ClusterTolerance>0.5</ClusterTolerance> 
      <ZClusterTolerance>-1</ZClusterTolerance> 
      <MaxGeneratedErrorCount>-1</MaxGeneratedErrorCount> 
    <FeatureClassNames xsi:type="esri:Names">
         <Name>sde.RJP.Blocks</Name> 
         <Name>sde.RJP.Parcels</Name> 
      </FeatureClassNames>
    <TopologyRules xsi:type="esri:ArrayOfTopologyRule">
      <TopologyRule xsi:type="esri:TopologyRule">
           <HelpString /> 
           <RuleID>183</RuleID> 
           <Name /> 
           <GUID>7D3E7075-16CF-47AD-A8F4-842B921B1E1E</GUID> 
           <TopologyRuleType>esriTRTAreaNoOverlap</TopologyRuleType> 
           <OriginClassID>100</OriginClassID> 
           <OriginSubtype>0</OriginSubtype> 
           <DestinationClassID>100</DestinationClassID> 
           <DestinationSubtype>0</DestinationSubtype> 
           <TriggerErrorEvents>false</TriggerErrorEvents> 
           <AllOriginSubtypes>true</AllOriginSubtypes> 
           <AllDestinationSubtypes>true</AllDestinationSubtypes> 
        </TopologyRule>
      <TopologyRule xsi:type="esri:TopologyRule">
           <HelpString /> 
           <RuleID>184</RuleID> 
           <Name /> 
           <GUID>6F58891D-5BD9-4848-802E-90458152B0CE</GUID> 
           <TopologyRuleType>esriTRTAreaCoveredByArea</TopologyRuleType> 
           <OriginClassID>100</OriginClassID> 
           <OriginSubtype>1</OriginSubtype> 
           <DestinationClassID>98</DestinationClassID> 
           <DestinationSubtype>1</DestinationSubtype> 
           <TriggerErrorEvents>false</TriggerErrorEvents> 
           <AllOriginSubtypes>false</AllOriginSubtypes> 
           <AllDestinationSubtypes>false</AllDestinationSubtypes> 
        </TopologyRule>
    </TopologyRules>
</DataElement>

Top of page

Geometric networks and network datasets

Geometric networks are collections of line (edge) and point (junction) feature classes in a feature dataset that possess a connectivity relationship. Geometric networks are used to model infrastructure, such as electirc utility lines and sewer systems.

Network datasets are also collections of feature classes that possess a connectivity relationship, but network datasets are created using three types of sources—edge feature sources, such as street centerlines, junction feature sources, such as point feature classes containing railroad crossings, and turn feature sources. They are used to model transportation. To use network datasets, you must have the Network Analyst extension installed.

The tables that get created with a network depend on whether you create a geometric network or a network dataset and also whether or not there are turns present in the network.

Networks in ArcCatalog

In the ArcCatalog tree, feature datasets that contain geometric networks and network datasets look the same until you expand the dataset. Once the dataset is expanded, you will see either a geometric network or network dataset. For example, for a geometric network, you would see a layer similar to the following:
Geometric network in ArcCatalog

In this example, Water_Net is the geometric network in the dataset.

For a network dataset, you would see something similar to the following:

Network dataset in ArcCatalog

RoadNetwork_ND is the network dataset. RoadNetwork_ND_Junctions are the junctions for the RoadNetwork network dataset.

Networks in an Informix DBMS

Networks are tracked in system tables and network tables. The following are the system tables used for a geometric network:

gdb_geomnetworks
gdb_networks
gdb_netweights
gdb_netweightasocs
gdb_netclasses

Network datasets are maintained in these system tables:

gdb_extensiondatasets
gdb_networks
gdb_netweights
gdb_edgeconnrules
gdb_jnconnrules

See System tables of a geodatabase in Informix for descriptions of these tables.

In addition to these tables the network is a set of variably sized tables. The size of these tables depends on the size of the network—for example, number of junctions #j and number of edges #e.

There are 10 fixed tables per network, and they are identified by the following naming convention n_*_<table_descriptor>, where the '*' represents the ID of the network in the gdb_networks table; for example, n_1_<table descriptor>, n_2_<table descriptor>. The actual number of tables varies depending on what type of network you create—geometric network or network dataset—and what elements the network contains. A maximum of 21 tables could get created for a network dataset with turns and weights.

All of these tables are versioned when the network itself is versioned.

The 10 tables that are always created are the n_<id>_desc, n_<id>_e<#>, n_<id>_estatus, n_<id>_etopo, n_<id>_flodir, n_<id>_jdesc, n_<id>_jstatus, n_<id>_jtopo, n_<id>_jtopo2, and n_<id>_props tables. (See below for descriptions.)

n_<id>_<>
Tables in the geodatabase that begin with n_ store information about networks.

n_<id>_desc
The n_<id>_desc table describes the elements of a network. This is a normalized table whose row count is equal to the number of junctions and the number of edges in a geometric network.

Field name	Field type	Description
oid	Int	The unique ID of an element in a geometric network
userclassid	Int	The ID of the feature class to which the element belongs
userid	Int	The object ID of the feature
usersubid	Int	The ID of an element in a feature; only applicable to complex edge features
elementtype	Smallint	A code indicating the type of network element 1 = junction 2 = edge
eid	Int	The unique element ID of the network element; the element ID is only unique for the type of network element

n_<id>_props
The n_<id>_props table contains a summary description of a a network's properties, such as element counts and maximum eid values.

Field name	Field type	Description
propertyid	Int	The unique ID of the network property
propertyname	Varchar(32)	The name of the property
propertyvalue	Int	The value of the property

NOTE: The n_<id>_desc and n_<id>_props tables can be viewed in the DBMS but should not be altered using SQL/third-party applications; doing so can corrupt the network.

All of the remaining network tables contain the same field names and types. The table names and what they track are described below the table definition. Those tables that track turns would not be used in a geometric network dataset.

Field name	Field type	Description
oid	Int	The unique ID of the BLOB page in the table NOT NULL
pagenumber	Int	The number of the BLOB page in the table NOT NULL
pageblob	Blob	The desciription for the element the table is describing, such as edge, edge status, etc.

n_<id>_e<#>—Describe network edge weights; # = 2, 3, 4, or 5
n_<id>_edesc—Describes the edges in a network
n_<id>_estatus—Describes the status of each edge including its deleted and disabled states
n_<id>_etopo—Describes the network edge topology or connectivity
n_<id>_eturn*—Indicates whether each edge participates in a turn
n_<id>_eturn2*—Lists which turns pass through each edge in the network
n_<id>_flodir—Describes the network flow direction
n_<id>_j<#>—Describe network junction weights; # = 0 or 1
n_<id>_jdesc—Describes the network junctions
n_<id>_jstatus—Describes the status of each network junction including its deleted and disabled states
n_<id>_jtopo—Describes the connectivity of junction elements with edge elements.
n_<id>_jtopo2—Describes the connectivity of junction elements with edge elements when there are multiple edges connected to a single junction.
n_<id>_jturn*—Indicates whether each junction participates in a turn
n_<id>_jturn2*—Lists which turns pass through each junction in the network
n_<id>_t<#>*—Describes the weight values of each turn element
n_<id>_tdefn*—Defines each turn element by listing the edges and junctions that make up the turn.
n_<id>_tdefn2*—Overflow table for the turn element definition; for example, if multiple edges make up a turn.
n_<id>_tdesc*—Describes the turns in a network
n_<id>_tstatus*—Describes the status of each network turn, including its deleted and disabled states.

*Would not be present in a geometric network or network dataset without turns.

Click the following link to view the tables involved in the Water_Net geometric network shown above:

Informix geometric network diagram

The link below will open a diagram of the tables that participate in the Roads_ND network dataset:

Informix network dataset diagram

In both diagrams, dashed lines indicate implicit relationships between tables, solid lines denote explicitly defined relationships. You will need Adobe Acrobat Reader to open the files.

The owner field in the gdb_objectclasses, gdb_networks, gdb_geomnetworks, gdb_featuredataset, and gdb_extensiondatasets tables all contain the same value, but to keep the diagram from being too cluttered, the implicit relationship between these fields is not shown. The same is true for the database name field in these tables; the values are the same but the relationship is not drawn on the diagram.

Networks in an XML document

For a geometric network, the data element in an XML document is listed as type GeometricNetwork. The following is a portion of the XML document exported from the hydro2 dataset.

<DataElement xsi:type="esri:DEGeometricNetwork">
     <CatalogPath>/V=sde.DEFAULT/FD=sde92:gdb.Water/GN=sde92:gdb.Water_Net</CatalogPath> 
  <Name>sde92:gdb.Water_Net</Name> 
  <MetadataRetrieved>true</MetadataRetrieved> 
  <Metadata xsi:type="esri:XmlPropertySet">
  <XmlDoc><?xml version="1.0"?> <metadata xml:lang="en"><Esri><MetaID>{A4750260-72E0-4B84-9E59-A28ED020FBCF}</MetaID><CreaDate>20060530</CreaDate><CreaTime>14011400</CreaTime><SyncOnce>TRUE</SyncOnce></Esri></metadata></XmlDoc> 
     </Metadata>
  <DatasetType>esriDTGeometricNetwork</DatasetType> 
  <DSID>-1</DSID> 
  <Versioned>false</Versioned> 
  <CanVersion>true</CanVersion> 
  <Extent xsi:type="esri:EnvelopeN" /> 
  <SpatialReference xsi:type="esri:ProjectedCoordinateSystem">
     <WKT>PROJCS["World_Mercator",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Mercator"],PARAMETER["False_Easting",0.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",0.0],PARAMETER["Standard_Parallel_1",0.0],UNIT["Meter",1.0]]</WKT> 
  <XOrigin>-147.84354555</XOrigin> 
  <YOrigin>-0.843545550000002</YOrigin> 
  <XYScale>160000000</XYScale> 
  <ZOrigin>0</ZOrigin> 
  <ZScale>1</ZScale> 
  <MOrigin>0</MOrigin> 
  <MScale>1</MScale> 
  <XYTolerance>0.0002</XYTolerance> 
  <ZTolerance>4.7683715798108E-03</ZTolerance> 
  <MTolerance>2</MTolerance> 
  <HighPrecision>true</HighPrecision> 
     </SpatialReference>
  <NetworkType>esriNTUtilityNetwork</NetworkType> 
  <OrphanJunctionFeatureClassName /> 
  <FeatureClassNames xsi:type="esri:Names" /> 
  <ConnectivityRules xsi:type="esri:ArrayOfConnectivityRule" /> 
  <NetworkWeights xsi:type="esri:ArrayOfNetWeight" /> 
  <WeightAssociations xsi:type="esri:ArrayOfNetWeightAssociation" /> 
     </DataElement>

The following is an excerpt from an XML document created by exporting from a network dataset. The edge and junction elements' properties are listed below:

<EdgeFeatureSources xsi:type="esri:ArrayOfEdgeFeatureSource">
   <EdgeFeatureSource xsi:type="esri:EdgeFeatureSource">
   <ID>1</ID> 
   <ClassID>99</ClassID> 
   <Name>sde92:gdb.Streets</Name> 
   <ElementType>esriNETEdge</ElementType> 
   <Properties xsi:nil="true" /> 
   <FromElevationFieldName /> 
   <ToElevationFieldName /> 
   <Connectivity xsi:type="esri:PropertySet">
   <PropertyArray xsi:type="esri:ArrayOfPropertySetProperty">
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>Version</Key> 
   <Value xsi:type="xs:short">1</Value> 
     </PropertySetProperty>
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>UsesSubtypes</Key> 
     <Value xsi:type="xs:short">0</Value> 
   </PropertySetProperty>
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>ClassConnectivity</Key> 
   <Value xsi:type="xs:short">1</Value> 
     </PropertySetProperty>
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>SubtypeConnCount</Key> 
   <Value xsi:type="xs:int">0</Value> 
     </PropertySetProperty>
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>DefaultGroup</Key> 
   <Value xsi:type="xs:int">1</Value> 
     </PropertySetProperty>
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>GroupCount</Key> 
   <Value xsi:type="xs:int">0</Value> 
     </PropertySetProperty>
     </PropertyArray>
     </Connectivity>
     </EdgeFeatureSource>
     </EdgeFeatureSources>
   <JunctionFeatureSources xsi:type="esri:ArrayOfJunctionFeatureSource" /> 
   <SystemJunctionSources xsi:type="esri:ArrayOfSystemJunctionSource">
   <SystemJunctionSource xsi:type="esri:SystemJunctionSource">
   <ID>2</ID> 
   <ClassID>1683</ClassID> 
   <Name>sde92:gdb.RoadNetwork_ND_Junctions</Name> 
   <ElementType>esriNETJunction</ElementType> 
   <Properties xsi:nil="true" /> 
   <ElevationFieldName /> 
     </SystemJunctionSource>
     </SystemJunctionSources>
   <TurnFeatureSources xsi:type="esri:ArrayOfTurnFeatureSource" /> 
   <EvaluatedNetworkAttributes xsi:type="esri:ArrayOfEvaluatedNetworkAttribute">
   <EvaluatedNetworkAttribute xsi:type="esri:EvaluatedNetworkAttribute">
   <ID>1</ID> 
   <Name>speed</Name> 
   <Units>Unknown</Units> 
   <DataType>esriNADTBoolean</DataType> 
   <UsageType>esriNAUTRestriction</UsageType> 
   <UserData xsi:nil="true" /> 
   <UseByDefault>true</UseByDefault> 
   <AttributeParameters xsi:type="esri:ArrayOfNetworkAttributeParameter" /> 
     </EvaluatedNetworkAttribute>
   <EvaluatedNetworkAttribute xsi:type="esri:EvaluatedNetworkAttribute">
   <ID>2</ID> 
   <Name>oneway</Name> 
   <Units>Unknown</Units> 
   <DataType>esriNADTBoolean</DataType> 
   <UsageType>esriNAUTRestriction</UsageType> 
   <UserData xsi:nil="true" /> 
   <UseByDefault>true</UseByDefault> 
   <AttributeParameters xsi:type="esri:ArrayOfNetworkAttributeParameter" /> 
     </EvaluatedNetworkAttribute>
   <EvaluatedNetworkAttribute xsi:type="esri:EvaluatedNetworkAttribute">
   <ID>3</ID> 
   <Name>timeofday</Name> 
   <Units>Unknown</Units> 
   <DataType>esriNADTInteger</DataType> 
   <UsageType>esriNAUTCost</UsageType> 
   <UserData xsi:nil="true" /> 
   <UseByDefault>true</UseByDefault> 
   <AttributeParameters xsi:type="esri:ArrayOfNetworkAttributeParameter" /> 
     </EvaluatedNetworkAttribute>
   </EvaluatedNetworkAttributes>
   <NetworkAssignments xsi:type="esri:ArrayOfNetworkAssignment">
   <NetworkAssignment xsi:type="esri:NetworkAssignment">
   <IsDefault>true</IsDefault> 
   <ID>-1</ID> 
   <NetworkAttributeName>speed</NetworkAttributeName> 
   <NetworkElementType>esriNETJunction</NetworkElementType> 
   <NetworkEvaluatorCLSID>{318C4B91-F5D2-467A-996C-0AB51B0D8FF2}</NetworkEvaluatorCLSID> 
   <NetworkEdgeDirection>esriNEDNone</NetworkEdgeDirection> 
   <NetworkEvaluatorData xsi:type="esri:PropertySet">
   <PropertyArray xsi:type="esri:ArrayOfPropertySetProperty">
     <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>Version</Key> 
   <Value xsi:type="xs:short">1</Value> 
   </PropertySetProperty>
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>ConstantValue</Key> 
   <Value xsi:type="xs:boolean">false</Value> 
     </PropertySetProperty>
     </PropertyArray>
     </NetworkEvaluatorData>
     </NetworkAssignment>
   <NetworkAssignment xsi:type="esri:NetworkAssignment">
   <IsDefault>true</IsDefault> 
   <ID>-1</ID> 
   <NetworkAttributeName>speed</NetworkAttributeName> 
   <NetworkElementType>esriNETEdge</NetworkElementType> 
   <NetworkEvaluatorCLSID>{318C4B91-F5D2-467A-996C-0AB51B0D8FF2}</NetworkEvaluatorCLSID> 
   <NetworkEdgeDirection>esriNEDNone</NetworkEdgeDirection> 
   <NetworkEvaluatorData xsi:type="esri:PropertySet">
   <PropertyArray xsi:type="esri:ArrayOfPropertySetProperty">
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>Version</Key> 
   <Value xsi:type="xs:short">1</Value> 
     </PropertySetProperty>
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>ConstantValue</Key> 
   <Value xsi:type="xs:boolean">false</Value> 
     </PropertySetProperty>
     </PropertyArray>
     </NetworkEvaluatorData>
     </NetworkAssignment>
   <NetworkAssignment xsi:type="esri:NetworkAssignment">
   <IsDefault>true</IsDefault> 
   <ID>-1</ID> 
   <NetworkAttributeName>speed</NetworkAttributeName> 
   <NetworkElementType>esriNETTurn</NetworkElementType> 
   <NetworkEvaluatorCLSID>{318C4B91-F5D2-467A-996C-0AB51B0D8FF2}</NetworkEvaluatorCLSID> 
   <NetworkEdgeDirection>esriNEDNone</NetworkEdgeDirection> 
   <NetworkEvaluatorData xsi:type="esri:PropertySet">
   <PropertyArray xsi:type="esri:ArrayOfPropertySetProperty">
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>Version</Key> 
   <Value xsi:type="xs:short">1</Value> 
     </PropertySetProperty>
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>ConstantValue</Key> 
   <Value xsi:type="xs:boolean">false</Value> 
     </PropertySetProperty>
     </PropertyArray>
     </NetworkEvaluatorData>
     </NetworkAssignment>
   <NetworkAssignment xsi:type="esri:NetworkAssignment">
   <IsDefault>true</IsDefault> 
   <ID>-1</ID> 
   <NetworkAttributeName>oneway</NetworkAttributeName> 
   <NetworkElementType>esriNETJunction</NetworkElementType> 
   <NetworkEvaluatorCLSID>{318C4B91-F5D2-467A-996C-0AB51B0D8FF2}</NetworkEvaluatorCLSID> 
   <NetworkEdgeDirection>esriNEDNone</NetworkEdgeDirection> 
   <NetworkEvaluatorData xsi:type="esri:PropertySet">
   <PropertyArray xsi:type="esri:ArrayOfPropertySetProperty">
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>Version</Key> 
   <Value xsi:type="xs:short">1</Value> 
     </PropertySetProperty>
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>ConstantValue</Key> 
   <Value xsi:type="xs:boolean">false</Value> 
     </PropertySetProperty>
     </PropertyArray>
     </NetworkEvaluatorData>
     </NetworkAssignment>
   <NetworkAssignment xsi:type="esri:NetworkAssignment">
   <IsDefault>true</IsDefault> 
   <ID>-1</ID> 
   <NetworkAttributeName>oneway</NetworkAttributeName> 
   <NetworkElementType>esriNETEdge</NetworkElementType> 
   <NetworkEvaluatorCLSID>{318C4B91-F5D2-467A-996C-0AB51B0D8FF2}</NetworkEvaluatorCLSID> 
   <NetworkEdgeDirection>esriNEDNone</NetworkEdgeDirection> 
   <NetworkEvaluatorData xsi:type="esri:PropertySet">
   <PropertyArray xsi:type="esri:ArrayOfPropertySetProperty">
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>Version</Key> 
   <Value xsi:type="xs:short">1</Value> 
     </PropertySetProperty>
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>ConstantValue</Key> 
   <Value xsi:type="xs:boolean">false</Value> 
     </PropertySetProperty>
     </PropertyArray>
     </NetworkEvaluatorData>
     </NetworkAssignment>
   <NetworkAssignment xsi:type="esri:NetworkAssignment">
   <IsDefault>true</IsDefault> 
   <ID>-1</ID> 
   <NetworkAttributeName>oneway</NetworkAttributeName> 
   <NetworkElementType>esriNETTurn</NetworkElementType> 
   <NetworkEvaluatorCLSID>{318C4B91-F5D2-467A-996C-0AB51B0D8FF2}</NetworkEvaluatorCLSID> 
   <NetworkEdgeDirection>esriNEDNone</NetworkEdgeDirection> 
   <NetworkEvaluatorData xsi:type="esri:PropertySet">
   <PropertyArray xsi:type="esri:ArrayOfPropertySetProperty">
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>Version</Key> 
   <Value xsi:type="xs:short">1</Value> 
     </PropertySetProperty>
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>ConstantValue</Key> 
   <Value xsi:type="xs:boolean">false</Value> 
     </PropertySetProperty>
     </PropertyArray>
     </NetworkEvaluatorData>
     </NetworkAssignment>
   <NetworkAssignment xsi:type="esri:NetworkAssignment">
   <IsDefault>true</IsDefault> 
   <ID>-1</ID> 
   <NetworkAttributeName>timeofday</NetworkAttributeName> 
   <NetworkElementType>esriNETJunction</NetworkElementType> 
   <NetworkEvaluatorCLSID>{318C4B91-F5D2-467A-996C-0AB51B0D8FF2}</NetworkEvaluatorCLSID> 
   <NetworkEdgeDirection>esriNEDNone</NetworkEdgeDirection> 
   <NetworkEvaluatorData xsi:type="esri:PropertySet">
   <PropertyArray xsi:type="esri:ArrayOfPropertySetProperty">
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>Version</Key> 
   <Value xsi:type="xs:short">1</Value> 
     </PropertySetProperty>
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>ConstantValue</Key> 
   <Value xsi:type="xs:int">0</Value> 
     </PropertySetProperty>
     </PropertyArray>
     </NetworkEvaluatorData>
     </NetworkAssignment>
   <NetworkAssignment xsi:type="esri:NetworkAssignment">
   <IsDefault>true</IsDefault> 
   <ID>-1</ID> 
   <NetworkAttributeName>timeofday</NetworkAttributeName> 
   <NetworkElementType>esriNETEdge</NetworkElementType> 
   <NetworkEvaluatorCLSID>{318C4B91-F5D2-467A-996C-0AB51B0D8FF2}</NetworkEvaluatorCLSID> 
   <NetworkEdgeDirection>esriNEDNone</NetworkEdgeDirection> 
   <NetworkEvaluatorData xsi:type="esri:PropertySet">
   <PropertyArray xsi:type="esri:ArrayOfPropertySetProperty">
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>Version</Key> 
   <Value xsi:type="xs:short">1</Value> 
     </PropertySetProperty>
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>ConstantValue</Key> 
   <Value xsi:type="xs:int">0</Value> 
     </PropertySetProperty>
     </PropertyArray>
     </NetworkEvaluatorData>
     </NetworkAssignment>
   <NetworkAssignment xsi:type="esri:NetworkAssignment">
   <IsDefault>true</IsDefault> 
   <ID>-1</ID> 
   <NetworkAttributeName>timeofday</NetworkAttributeName> 
   <NetworkElementType>esriNETTurn</NetworkElementType> 
   <NetworkEvaluatorCLSID>{318C4B91-F5D2-467A-996C-0AB51B0D8FF2}</NetworkEvaluatorCLSID> 
   <NetworkEdgeDirection>esriNEDNone</NetworkEdgeDirection> 
   <NetworkEvaluatorData xsi:type="esri:PropertySet">
   <PropertyArray xsi:type="esri:ArrayOfPropertySetProperty">
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>Version</Key> 
   <Value xsi:type="xs:short">1</Value> 
     </PropertySetProperty>
   <PropertySetProperty xsi:type="esri:PropertySetProperty">
   <Key>ConstantValue</Key> 
   <Value xsi:type="xs:int">0</Value> 
     </PropertySetProperty>
     </PropertyArray>
     </NetworkEvaluatorData>
     </NetworkAssignment>
   </NetworkAssignments>
 <ConfigurationKeyword>NETWORK_DEFAULTS</ConfigurationKeyword> 
  </DataElement>

Top of page

Schematic datasets

Schematic datasets are similar to feature datasets but they contain a collection of schematic diagram classes and schematic element classes (which are the schematic equivalent of feature classes). They are used to graphically visualize and manipulate network data.

A schematic dataset is always associated with a schematic project. When you create a schematic dataset in ArcCatalog, an associated schematic project is automatically created. A schematic project contains the graphic parameters and display rules for the schematic diagrams generated and stored in the schematic dataset.

Schematic datasets in ArcCatalog

The following is an example of a schematic dataset, schematic folders, and the schematic diagrams they contain in ArcCatalog:

Schematic dataset in ArcCatalog

Schematic datasets in an Informix DBMS

The following tables are used to store information on schematic datasets.

sch_dataset
Contains one record for each schematic dataset. The id field in this table is used to identify the assosiated element and diagram tables.

Field name	Field type	Description
id	Int	Unique identifier of the schematic dataset Not null
major	Int	Release number of the dataset version; not used at this time Not null
minor	Int	Minor release number of the dataset version; not used at this time Not null
bugfix	Int	Patch or service pack number of the dataset version; not used at this time Not null
dbname	Varchar(32)	Name of the database in which the schematic dataset is stored
owner	Varchar(32)	The user who created the schematic dataset
name	Varchar(128)	The name of the schematic dataset Not null
extclsid	Varchar(38)	Not currently in use
spatialref	Varchar(1024)	Default spatial reference used when creating new diagrams
blobs	Blob	Stores the default parameters for the dataset, such as the default node symbol, text separator, and character

sch_release
The sch_release table is not currently in use.

Field name	Field type	Description
major	Int	Release number of the system tables; not used at this time Not null
minor	Int	Minor release number of the system tables; not used at this time Not null
bugfix	Int	Patch or service pack number of the system tables; not used at this time Not null

sch_uniqueid
The sch_uniqueid table stores the unique identifier of a diagram type.

Field name	Field type	Description
id	Int	The unique identifier used when creating new diagram types for the object class Not null
dummy	Int	Not in use at this time

sch<id>_clsentry
Stores the associations between the diagram types and the element types in a schematic dataset

Field Name	Field Type	Description
id	Int	Uniquely identifies the relationship between a diagram type and element type Not null
diagramclassid	Int	Foreign key to the id field in the sch<id>_diaclass table Not null
elementclassid	Int	Foreign key to the id field in the sch<id>_eltclass table Not null

sch<id>_datasrc
Contains a list of all the data sources accessed by the schematic dataset

Field name	Field type	Description
id	Int	Uniquely identifies a data source Not null
name	Varchar(255)	Name of the data source Not null
clsid	Varchar(38)	Class id of the data source component Not null
label	Varchar(255)	Not currently in use
connection	Blob	Parameters of the connection; used to persist and restore the connection Not null

sch<id>_diaclass
Tracks all the diagram types present in a schematic dataset

Field name	Field type	Description
id	Int	Uniquely identifies a diagram type Not null
objectclassid	Int	Foreign key to the id field in the sch_uniqueid table Not null
creationname	Varchar(255)	Name of the diagram class when the table is created Not null
name	Varchar(255)	Current name of the diagram class (if it was changed from the original name) Not null
parentid	Int	Id of the parent diagram class entry Not null
datasourceid	Int	Foreign key to the id field of sch<id>_datasrc
builderclsid	Varchar(38)	Class id for the schema builder (custom query, network dataset, or standard)
linkerclsid	Varchar(38)	Component managing feature to element relationship method
algorithmclsid	Varchar(38)	Class id of the algorithm that is automatically applied to diagrams of this type
blobs	Blob	Stores all the attribute and symbology information

sch<id>_eltclass
Maintains a list of all the element types for each dataset

Field name	Field type	Description
id	Int	Uniquely identifies an element type Not null
objectclassid	Int	Foreign key to id in gdb_objectclasses table Not null
creationname	Varchar(255)	Name of the element class when the table is created Not null
name	Varchar(255)	Current name of the element class (if it changed) Not null
parentid	Int	Id of the parent element class entry
elementtype	Int	Value specifying the type of element (node, link, etc.)
relationclsid	Varchar(38)	Relationship to a feature class
associateddsid	Int	Data source id of related feature class
associatedocid	Int	Id of the related feature classes from the gdb_objectclasses table
datasourceid	Int	Foreign key to the ID field in the sch<id>_datasrc table
blobs	Blob	Stores attribute and symbology

sch<id>_folder
Maintains a list of all the folders created in a dataset

Field name	Field type	Description
id	Int	Unique identifier for the folder Not null
name	Varchar(255)	Name of the folder Not null
pfid	Int	Id of the parent folder if nested Not null
xml	Blob	Stores the metadata of the folder

sch<id>a_<element_type_name>
Tracks the associations between an element and a feature

Field name	Field type	Description
id	Int	Uniquely identifies the association between an element and a feature Not null
schematicid	Int	Unique id for an element Not null
datasourceid	Int	Foreign key to the id field in the sch<id>_datasrc table
ucid	Int	Class id of the related feature
uoid	Int	Object id of the related feature
usid	Int	Subtype id of the related feature
ueid	Int	Enabled id of the related feature

sch<id>d_<diagram_type_name>
Stores a list of all diagrams created using a particular diagram type (the one indicated by the <diagram_type_name>)

Field name	Field type	Description
id	Int	Uniquely identifies a diagram Not null
name	Varchar(255)	Name of the diagram
folderid	Int	Foreign key to the sch<id>_folder table Not null
diagramclassid	Int	Foreign key to sch<id>_diaclass table's objectclassid field Not null
lastupdate	Datetime	Date and time of last user update Not null
version	Varchar(255)	If generated from versioned data, lists which version
creationdate	Datetime	Date and time diagram was created
creator	Varchar(100)	Name of the user that created the diagram
updatedby	Varchar(100)	Name of the user that last updated the diagram
spatialref	Char(1024)	Spatial coordinates
blobs	Blob	Stores the current positioning of all elements in the diagram

sch<id>e_<element_type_name>
Stores a list of all the elements created using an element type
Element types define the attributes and symbology of an element.

Field name	Field type	Description
id	Int	Uniquely identifies an element Not null
diagramclassid	Int	Foregn key to the sch<id>_diaclass table's objectclass id field Not null
diagramobjectid	Int	Foreign key to the sch<id>d_<diagram_type_name> table Not null
schematicid	Varchar(128)	Uniquely identifies an element; consists of diagramobjectid, diagramclassid, datasourceid, ucid, uoid, and usid Not null
isinitial	Int	Indicates whether this element was part of the initial creation list Not null
isdisplayed	Int	Indicates whether this element is currently displayed Not null
relationobjectid	Int	Object id of related feature in relationship
relationclassid	Int	Class id of related feature in relationship
datasourceid	Int	Foreign key to sch<id>_datasrc table
ucid	Int	Class id of corresponding feature
uoid	Int	Object id of corresponding feature
usid	Int	Subtype id of corresponding feature
ueid	Int	Enabled value of corresponding feature
subtype	Int	Subtype of feature
propertyset	Blob	Holds attribute information
initialx	Decimal(32,20)	X positon of element when created
initialy	Decimal(32,20)	Y position of element when created

sch<id>r_<diagram_type_name>
Stores a list of all the relationship rules for a diagram type

Field name	Field type	Description
id	Int	Uniquely identifies relationship rule Not null
ordernumber	Int	Indicates in which order rules will be run Not null
active	Int	Indicates whether or not the rule is active Not null
clsid	Varchar(38)	Class id of the rule Not null
propertyset	Blob	Property page values

Click the following link to see an example of schematic dataset system tables showing implicit links. Implicit links are denoted with the dashed lines.

Informix schematic dataset diagram

Schematic datasets in XML

Exporting schematic datasets to XML is not presently supported.

Top of page

Terrain datasets

Terrain datasets are surfaces that represent three-dimensional space. They use measurements (stored as feature classes) and rules to generate TIN pyramids to represent elevation.

The source feature classes either can be referenced by the terrain dataset or be embedded in the terrain dataset.

For an explanation of terrain datasets, read the topics in the book Understanding terrain datasets. You can begin with the topic What is a terrain dataset?

Terrains in ArcCatalog

In the ArcCatalog tree, terrain datasets look like any other feature dataset. The difference is terrain datasets contain a terrain. In the example below, the napa_sub terrain dataset contains the terrain napa_sub_terrain1.
Terrain dataset in ArcCatalog

You can see two of the feature classes that participate in the terrain—napa_sub_breaks and napa_sub_clip. To find out if there are any embedded feature classes in the terrain dataset, check the terrain properties. Right-click the terrain, and click the Data Sources tab. This will list all feature classes used to create the terrain. In this example a third, embedded feature class—napasub_embedded—was used to create this terrain.

Terrains in an Informix DBMS

Being datasets, terrain datasets are managed in the geodatabase in the same tables as feature datasets, plus there are terrain-specific tables created in the schema of the user who created the terrain dataset. These tables are as follows:

dtm_<id>_compositetiles
Composite tiles are incomplete, in terms of data coverage, around their perimeter. They could be void of measurements entirely or within the proximity of one or more corners. To define a surface that covers the extent of these tiles data is used from surrounding tiles. This table is used to identify which tiles are composite tiles and what neighboring tiles provide data to complete them. One record is used per composite tile.

Field name	Field type	Description
id	Int	The unique identifier of the shape pointing to neighbor tiles. Not null
tilenr	Int	The composite tile number. This is defined by the terrain's tile system. A value of -1 is reserved for one record containing the centroids of the terrain's perimeter tiles. Not null
emptytile	Smallint	A value of -1 indicates the tile is void of any measurements. A value of 0 indicates the tile has some data but is incomplete. Not null
othertiles	St_multipoint	Multipoint shape storing the tile centroid of each surrouding tile that provides measurements to complete the composite tile.

dtm_<id>_dirtyarea
Dirty areas are tiles that have been invalidated as a result of edits to features in one or more participating feature classes. This table is used to keep track of these invalidated tiles and to record which in feature classes the edits have taken place. One record is used per feature class in which edits have been made. The table will be empty if no edits have been made.

Field name	Field type	Description
id	Int	The unique identifier for the shape. Not null
classid	Int	The class ID of the feature class that's the source of the edits. Not null
tilecount	Int	The number of dirty tiles resulting from edits to the feature class. Not null
dirtyarea	St_multipoint	Mutlipoint shape containing the tile centroids invalided as a result of edits to the feature class. Not null

dtm_<id>_embed_#
Embed tables are used to store embedded multipoint feature classes. There may be 0..n embed tables. Their existance depend on whether the terrain has any embedded data. One table is used per embedded feature class. An embed table has the dual purpose of being part of the terrain's pyramid structure. The embedded data are grouped by tile and pyramid level.

Field name	Field type	Description
id	Int	The unique identifier for the shape Not null
tilerow	Int	The row number of the terrain tile to which the embedded points belong
tilecol	Int	The column number of the terrain tile to which the embedded points belong
resolution	Decimal(32,8)	Indicates in which pyramid level(s) the points are used Since pyramid levels are cumulative, points participate in levels with resolutions equal to or greater than themselves A special case involves the terrain overview. The resolution of the overview level is indicated with a value of -1. Points assigned this value participate through the entire pyramid.
pointcount	Int	The number of points in the multipoint Not null
neighbordata	Smallint	Indicates whether points are inside the tile neatline boundary; Those outside are used to ensure complete coverage of the tile area. A value of 0 indicates the points are inside the tile. -1 indicates they are outside. Not null
shape	St_multipoint	Embedded multipoint geometry

dtm_<id>_insidetiles
The InsideTiles table is used to record which terrain tiles are within the data area, or interpolation zone, of the terrain. This is recorded per pyramid level because it's possible for the extent to differ across levels (i.e. with the use of different clip polygon feature classes in different pyramid levels). One record is used per pyramid level. This includes both overview and full resolution levels.

Field name	Field type	Description
id	Int	The unique identifier for the shape Not null
ztolerance	Decimal(32,8)	The resolution of the pyramid level A value of -1 indicates the overview level. Not null
insidetiles	St_multipoint	Multipoint geometry storing the data tile centroids

dtm_<id>_mrfc
The MRFC is the pyramid structure for non-embedded feature classes. Mass points and breakline vertices for referenced feature classes are stored here under the pre-condition they participate in the full resolution pyramid level (they can also participate in other levels). Data are grouped by tile and pyramid level.

Field name	Field type	Description
id	Int	The unique identifier for the shape Not null
tilerow	Int	The row number of the terrain tile to which the pyramid points/vertices belong
tilecol	Int	The column number of the terrain tile to which the pyramid points/vertices belong
resolution	Decimal(32,8)	Indicates in which pyramid level(s) the points are used Since pyramid levels are cumulative, points participate in levels with resolutions equal to or greater than themselves. A special case involves the terrain overview. The resolution of the overview level is indicated with a value of -1. Points assigned this value participate through the entire pyramid.
pointcount	Int	The number of points in the multipoint Not null
neighbordata	Smallint	Indicates whether points are inside the tile neatline boundary; those outside are used to ensure complete coverage of the tile area. A value of 0 indicates the points are inside the tile. -1 indicates they are outside. Not null
shape	St_multipoint	Multipoint geometry

dtm_<id>_props
The terrain props table is used to hold version specific properties for an individual terrain dataset. These include point count and extent. The information is stored in a BLOB and is not user accessible through the table. Instead, use terrain's ArcObjects API to access the information.

Field name	Field type	Description
id	Int	The objectid for the record Not null
properties	Blob	Stores the version specific dataset properties

A record is also created in the gdb_extensiondatasets table to track the terrain dataset. The id in the names of the dtm tables come from the id field of the gdb_extensiondatasets table.

As mentioned, terrain datasets are tracked with the same system tables as feature datasets. The additional tables for a terrain dataset are shown below. The 2 in the example DTM_* table names relates these tables to the id field in the gdb_extensiondatasets table.

A terrain dataset in Informix

Terrains in an XML document

Terrain datasets are denoted in an XML document with the dataset type ersriDTTerrain.

<DatasetType>esriDTTerrain</DatasetType>

The following is a portion of the XML document for the napa_sub terrain dataset. The XML document excerpt below covers the definition of the dataset, including data sources, up to the point of describing the first feature class in the dataset.

 <esri:Workspace xmlns:esri="http://www.esri.com/schemas/ArcGIS/9.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <WorkspaceDefinition xsi:type="esri:WorkspaceDefinition">
  <WorkspaceType>esriRemoteDatabaseWorkspace</WorkspaceType> 
  <Version>RJP.WO2557</Version> 
  <Domains xsi:type="esri:ArrayOfDomain" /> 
  <DatasetDefinitions xsi:type="esri:ArrayOfDataElement">
    <DataElement xsi:type="esri:DEFeatureDataset">
      <CatalogPath>/V=RJP.WO2557/FD=sde92.gdb.napa_sub</CatalogPath> 
      <Name>sde92.gdb.napa_sub</Name> 
      <Children xsi:type="esri:ArrayOfDataElement">
        <DataElement xsi:type="esri:DETerrain">
          <Version>2</Version> 
              <CatalogPath>/V=RJP.WO2557/FD=sde92.gdb.napa_sub/TERR=sde92.gdb.napa_sub_terrain1</CatalogPath> 
          <Name>sde92.gdb.napa_sub_terrain1</Name> 
          <DatasetType>esriDTTerrain</DatasetType> 
          <DSID>2</DSID> 
          <FeatureDatasetName>sde92.gdb.napa_sub</FeatureDatasetName> 
          <Versioned>false</Versioned> 
          <CanVersion>false</CanVersion> 
          <ChildrenExpanded>true</ChildrenExpanded> 
          <MetadataRetrieved>false</MetadataRetrieved> 
          <FullPropsRetrieved>true</FullPropsRetrieved> 
          <PyramidType>0</PyramidType> 
          <TileSize>6000</TileSize> 
          <MaxShapeSize>5000</MaxShapeSize> 
          <MaxOverviewSize>50000</MaxOverviewSize> 
          <TerrainDataSources xsi:type="esri:ArrayOfTerrainDataSource">
            <TerrainDataSource xsi:type="esri:TerrainDataSource">
              <Version>1</Version> 
              <FeatureClassID>875</FeatureClassID> 
              <FeatureClassName>sde92.gdb.dtm_2_disconnect_3</FeatureClassName> 
              <GroupID>1</GroupID> 
              <SourceStatus>1</SourceStatus> 
              <SourceType>1</SourceType> 
              <SurfaceFeatureType>18</SurfaceFeatureType> 
              <IsBase>true</IsBase> 
              <ApplyToOverview>true</ApplyToOverview> 
              <AutoGeneralize>false</AutoGeneralize> 
              <ResolutionLowerBound>0</ResolutionLowerBound> 
              <ResolutionUpperBound>0</ResolutionUpperBound> 
              <SourceName>napasub_embedded</SourceName> 
              <HeightField>Shape</HeightField> 
              <TagValueField /> 
              <ReservedFields xsi:type="esri:ArrayOfString" /> 
           </TerrainDataSource>
           <TerrainDataSource xsi:type="esri:TerrainDataSource">
              <Version>1</Version> 
              <FeatureClassID>874</FeatureClassID> 
              <FeatureClassName>sde92.gdb.napa_sub_breaks</FeatureClassName> 
              <GroupID>2</GroupID> 
              <SourceStatus>1</SourceStatus> 
              <SourceType>0</SourceType> 
              <SurfaceFeatureType>1</SurfaceFeatureType> 
              <IsBase>true</IsBase> 
              <ApplyToOverview>false</ApplyToOverview> 
              <AutoGeneralize>false</AutoGeneralize> 
              <ResolutionLowerBound>0</ResolutionLowerBound> 
              <ResolutionUpperBound>2.6</ResolutionUpperBound> 
              <SourceName /> 
              <HeightField>Shape</HeightField> 
              <TagValueField /> 
              <ReservedFields xsi:type="esri:ArrayOfString" /> 
           </TerrainDataSource>
           <TerrainDataSource xsi:type="esri:TerrainDataSource">
              <Version>1</Version> 
              <FeatureClassID>873</FeatureClassID> 
              <FeatureClassName>sde92.gdb.napa_sub_clip</FeatureClassName> 
              <GroupID>3</GroupID> 
              <SourceStatus>1</SourceStatus> 
              <SourceType>0</SourceType> 
              <SurfaceFeatureType>10</SurfaceFeatureType> 
              <IsBase>false</IsBase> 
              <ApplyToOverview>true</ApplyToOverview> 
              <AutoGeneralize>false</AutoGeneralize> 
              <ResolutionLowerBound>0</ResolutionLowerBound> 
              <ResolutionUpperBound>31</ResolutionUpperBound> 
              <SourceName /> 
              <HeightField /> 
              <TagValueField /> 
              <ReservedFields xsi:type="esri:ArrayOfString" /> 
           </TerrainDataSource>
         </TerrainDataSources>
         <TerrainPyramidLevelZTols xsi:type="esri:ArrayOfTerrainPyramidLevelZTol">
           <TerrainPyramidLevelZTol xsi:type="esri:TerrainPyramidLevelZTol">
           <Version>1</Version> 
           <PyramidLevelStatus>1</PyramidLevelStatus> 
           <PointCount>-1</PointCount> 
           <MaxScale>10000</MaxScale> 
           <Resolution>5</Resolution> 
         </TerrainPyramidLevelZTol>
         <TerrainPyramidLevelZTol xsi:type="esri:TerrainPyramidLevelZTol">
           <Version>1</Version> 
           <PyramidLevelStatus>1</PyramidLevelStatus> 
           <PointCount>-1</PointCount> 
           <MaxScale>20000</MaxScale> 
           <Resolution>10</Resolution> 
         </TerrainPyramidLevelZTol>
       </TerrainPyramidLevelZTols>
      </DataElement>
      <DataElement xsi:type="esri:DEFeatureClass">

Top of page

Feature datasets in a geodatabase in Informix

Feature datasets in ArcCatalog

Feature datasets in an Informix DBMS

Feature datasets in an XML document

Topologies in ArcCatalog

Topologies in an Informix DBMS

Topologies in an XML document

Networks in ArcCatalog

Networks in an Informix DBMS

Networks in an XML document

Schematic datasets in ArcCatalog

Schematic datasets in an Informix DBMS

Schematic datasets in XML

Terrains in ArcCatalog

Terrains in an Informix DBMS

Terrains in an XML document