ArcGIS Server Banner

Feature classes in a geodatabase in SQL Server

Feature classes in a geodatabase in SQL Server

Release 9.3 E-mail This TopicPrintable VersionGive Us feedback
A feature class is a collection of geographic features, all of the same geometric type (point, line, polygon, multipoint, annotation, dimension, or multipatch). For example, you could store points for all the train depots along a railroad line in one feature class. In another feature class, you could store lines that represent all the railroad tracks.

Below is a description of the way a feature class appears in ArcCatalog, in a SQL Server DBMS, and in an XML document. Following that is a description of subtypes, which are used to create subgroups of feature types in a feature class.

Feature classes in ArcCatalog

In the Catalog tree, a feature class looks like this:

Feature class in ArcCatalog (SQL Server)

If you preview the attribute table for this feature class, you will see the something similar to the following:

Preview of the Parcel attribute table

This is a polygon feature class named Parcels, which is owned by user RJP and is stored in a database named sde.

The icon to the left of the feature class name indicates the type of feature class it is. The icon above represents a polygon feature class. The icons for the other types of feature classes you can create in ArcGIS are as follows:

Point feature class icon A point or multipoint feature class

Line feature class icon A line feature class

Annotation feature class icon An annotation feature class

Dimension feature class icon A dimension feature class

Multipatch feature class icon A multipatch feature class

For a description of the different types of feature classes, see Feature class basics.

Feature classes stored in a binary format in a SQL Server DBMS

Geodatabases in a SQL Server DBMS can store spatial data in a binary format—either ArcSDE Compressed binary or the OGC well-known binary representation of geometry. By default, features are stored using the ArcSDE Compressed binary type.

Feature classes stored in a binary format consist of a business table and associated feature and spatial index tables as described below. The dashed lines indicate an implicit relationship between tables.

The business, f, and s tables for a feature class in SQL Server

Feature classes stored using the Microsoft geometry or geography type in a SQL Server DBMS

Beginning with ArcGIS 9.3, geodatabases stored in a SQL Server 2008 database can use the Microsoft geometry or geography storage types for feature storage. Feature classes that use one of these storage types also have a business table, as described in the previous section. However, for this storage type, the business table contains a column of type GEOMETRY or GEOGRAPHY, in which the feature class geometry is stored; there is no associated feature table.

Feature class tables that use geometry or geography storage also have associated system tables plus associated views. Click the following link to see a diagram of a feature class that uses the Microsoft geometry or geography storage type.

SQL Server geometry or geography feature class diagram

In the diagram, the feature class business table, buildings, is linked to the system tables by way of the table name.

The views used for the geometry or geography feature classes, ST_SPATIAL_REFERENCE_SYSTEMS and ST_GEOMETRY_COLUMNS, are not shown in the diagram because they are based on the system tables SDE_spatial_references and SDE_geometry_columns, which are already included in the diagram.

If the feature class is enabled to store CAD entities, a side table is created for the feature class to store CAD data, such as curves. All feature classes created through ArcCatalog are set to store CAD entities. If data is imported or registered with ArcSDE using ArcSDE administration commands, you specify whether or not CAD data can be stored in the resultant feature class. The feature class diagram also shows a CAD table, SDE_geometry42. The 42 in the table name refers to the feature class's layer_id from the SDE_layers table.

Joins against the CAD side table are not enabled until CAD data, such as true curves, have been added to the feature class. Once enabled, queries against the feature class will always include the CAD side table, even if the CAD data is no longer present.

Feature classes in an XML document

The following is a small portion of the content of an XML document for the Parcels feature class. The first section is the header; subsequent lines define fields and records in the feature class.

<ESRI:RecordSetData xmlns:ESRI="http://www.esri.com/schemas/ArcGIS/9.3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<Data xsi:type="ESRI:RecordSet">
   <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> 
              <DomainFixed>true</DomainFixed> 
              <AliasName>OBJECTID</AliasName> 
              <ModelName>OBJECTID</ModelName> 
          </Field>
        <Field xsi:type="esri:Field">
              <Name>ZONING</Name> 
              <Type>esriFieldTypeString</Type> 
              <IsNullable>true</IsNullable> 
              <Length>6</Length> 
              <Precision>0</Precision> 
              <Scale>0</Scale> 
          </Field>
        <Field xsi:type="esri:Field">
              <Name>PARCEL_ID</Name> 
              <Type>esriFieldTypeInteger</Type> 
              <IsNullable>true</IsNullable> 
              <Length>4</Length> 
              <Precision>10</Precision> 
              <Scale>0</Scale> 
           </Field>
         <Field xsi:type="esri:Field">
              <Name>ZONING_S</Name> 
              <Type>esriFieldTypeString</Type> 
              <IsNullable>true</IsNullable> 
              <Length>4</Length> 
              <Precision>0</Precision> 
              <Scale>0</Scale> 
              <AliasName>Zoning_simple</AliasName> 
              <ModelName>ZONING_S</ModelName> 
            <Domain xsi:type="esri:CodedValueDomain">
                  <DomainName>ZoningCodes</DomainName> 
                  <FieldType>esriFieldTypeString</FieldType> 
                  <MergePolicy>esriMPTDefaultValue</MergePolicy> 
                  <SplitPolicy>esriSPTDefaultValue</SplitPolicy> 
                  <Description>Simplified zoning codes</Description> 
                  <Owner>RJP</Owner> 
                <CodedValues xsi:type="esri:ArrayOfCodedValue">
                     - <CodedValue xsi:type="esri:CodedValue">
                       <Name>Commercial</Name> 
                       <Code xsi:type="xs:string">B</Code> 
                  </CodedValue>
                <CodedValue xsi:type="esri:CodedValue">
                       <Name>Flood Hazard Area</Name> 
                       <Code xsi:type="xs:string">FH</Code> 
                  </CodedValue>
                <CodedValue xsi:type="esri:CodedValue">
                       <Name>Institutional</Name> 
                       <Code xsi:type="xs:string">INST</Code> 
                  </CodedValue>
                <CodedValue xsi:type="esri:CodedValue">
                       <Name>Manufacturing</Name> 
                       <Code xsi:type="xs:string">M</Code> 
                  </CodedValue>
                <CodedValue xsi:type="esri:CodedValue">
                       <Name>Office</Name> 
                       <Code xsi:type="xs:string">O</Code> 
                  </CodedValue>
                <CodedValue xsi:type="esri:CodedValue">
                       <Name>Utility</Name> 
                       <Code xsi:type="xs:string">U</Code> 
                  </CodedValue>
                <CodedValue xsi:type="esri:CodedValue">
                       <Name>Residential</Name> 
                       <Code xsi:type="xs:string">R</Code> 
                  </CodedValue>
                </CodedValues>
              </Domain>
            </Field>
          <Field xsi:type="esri:Field">
              <Name>SHAPE</Name> 
              <Type>esriFieldTypeGeometry</Type> 
              <IsNullable>true</IsNullable> 
              <Length>4</Length> 
              <Precision>0</Precision> 
              <Scale>0</Scale> 
              <Required>true</Required> 
              <DomainFixed>true</DomainFixed> 
            <GeometryDef xsi:type="esri:GeometryDef">
                  <AvgNumPoints>0</AvgNumPoints> 
                  <GeometryType>esriGeometryPolygon</GeometryType> 
                  <HasM>false</HasM> 
                  <HasZ>false</HasZ> 
            <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>
        <GridSize0>147.850872887221</GridSize0> 
     </GeometryDef>
     <AliasName>SHAPE</AliasName> 
     <ModelName>SHAPE</ModelName> 
  </Field>
.
...all other fields...
.
<Records xsi:type="esri:ArrayOfRecord">
<Record xsi:type="esri:Record">
    <Values xsi:type="esri:ArrayOfValue">
         <Value xsi:type="xs:int">1</Value> 
         <Value xsi:type="xs:double">5001</Value> 
         <Value xsi:type="xs:string">0</Value> 
         <Value xsi:type="xs:string">1</Value> 
         <Value xsi:type="xs:int">6358</Value> 
         <Value xsi:type="xs:short">0</Value> 
         <Value xsi:nil="true" /> 
        <Value xsi:type="esri:PolygonB">
  <Bytes>BQAAAKIY/59+HR9BrcL/v636JEGMRP8feSgfQW+IAWB0ByVBAQAAAEIAAAAAAAAAjET/H3koH0Ga SQAg2/okQQCK49sGKB9BIJnG2MX6JEF10wDAiScfQa3C/7+t+iRBxksA4CsnH0G+SgAgJPskQYnQ AMDOJh9BlEwAoJn7JEFrJP2fqCYfQYzTAMDJ+yRB3kgA4HEmH0ExyP+/DvwkQWcj/Z9nJh9BnE4A oBv8JEGMSABgXSYfQZjI/38o/CRBT8H//xsmH0Hiyf//evwkQSpHAOAEJh9BjlAAIJj8JEH4pv3/ vSUfQbzL/3/x/CRBs7///7QlH0Hqy////PwkQcZFAOCrJR9BT1IAYAj9JEGmOP+ffyUfQffM/z9A /SRBkEQAYF4lH0HWUwAgav0kQTe+//9VJR9ByM3/f3T9JEHP8dfUOSUfQcfPvPCU/SRBWckAwAIl H0F/VQBg1P0kQZu7//+uJB9BJVcA4D3+JEHBTAGgTiQfQRFZAOC4/iRBJDP/Hx8kH0H6WQAg8/4k QX4y/5/1Ix9BnNT/fyn/JEEO0QEA1CMfQT7V//9R/yRBdD0AYJcjH0GnXABgnv8kQazPAYB7Ix9B /Nb/f8H/JEHltf9/QSMfQSHY/78KACVBoDsAYCIjH0H1XgDgMQAlQSfBAED2Ih9B1F8AoGkAJUGF wADAzSIfQaBgAKCcACVB1qEh4aMiH0H0v/AJyQAlQdtRAmB5Ih9BBmIAIPYAJUFOK/+fKSIfQWHd /79aASVByCn/H8ghH0FN3/+/1QElQQ4p/5+ZIR9Bb2YAYBACJUHSNADgbiEfQQ/h/z9GAiVBGa7/ f04hH0HqZwAgbwIlQSet//8RIR9BG2kAYLsCJUG3rP//9SAfQXHj/7/eAiVBdz4BILwgH0GV5P+/ JwMlQYoxAOCcIB9BMuX//04DJUFqJP+fcCAfQRHm/7+GAyVBf7YAQEwgH0HJ5v+/tAMlQf4fai4i IB9BG2B5uuQDJUHBqP9/+B8fQYRuAKAVBCVBTQj9H6EfH0EC6v//ggQlQahwAFCdHx9B+D0AzIcE JUHdpf9/Px8fQSZyACD+BCVBj7EAQBAfH0Ft4P6/OQUlQeewAEDmHh9B6HMAoG4FJUHzo///xB4f QVju/3+YBSVBPCkAYIkeH0GF7/+/4wUlQVoc/59sHh9BTnYAIAgGJUGtof9/Mx4fQW53ACBQBiVB LaH/fxMeH0EPeABgeAYlQeusAEDnHR9Bt/L/P7AGJUG2Gf+fwx0fQaJ5ACDdBiVBQ6wAQL0dH0GL 8/8/5QYlQXOOjgyeHR9Bh9WzdRMHJUGiGP+ffh0fQf70//9BByVB564AQGYeH0FviAFgdAclQY4G QeGNHh9BZOAZwkIHJUFBT7UiFSEfQcjAtugYBCVBro012pQjH0F8LBZ++AAlQYyEDuMmJh9BRZwe KMH9JEGMRP8feSgfQZpJACDb+iRB</Bytes> 
          </Value>
        <Value xsi:type="xs:double">112367.21137978</Value> 
      <Value xsi:type="xs:double">3597.78157570024</Value> 
    </Values>
   </Record>
.
...all other records...
.
 </Data>
</esri:RecordSetData>

Subtypes in feature classes

Subtypes are used to differentiate feature types within a feature class based on their default values, attribute domains, connectivity rules, and relationship rules. Subtypes are defined for a feature class, and only one field in the feature class can have subtypes defined for it.

Subtypes in ArcCatalog

Since subtypes are defined on the feature class, you define and view subtypes in ArcCatalog from the Feature Class Properties dialog box. Right-click the feature class, click Properties, and click the Subtypes tab to see the following dialog box:

Subtype tab of Feature Class Properties dialog box in ArcCatalog

This example shows subtypes applied to the TYPECODE field for a feature class called Laterals. You see the codes used for the subtypes, the descriptions (names) of the subtypes, and the default subtype for the TYPECODE field in the Laterals feature class.

Subtypes in a SQL Server DBMS

For the subtypes applied to the TYPECODE field of the Laterals feature class, the tables in a SQL Server DBMS would look those shown below. Dashed lines indicate implicit relationships between tables.

Subtype system tables in SQL Server

The subtypes for feature classes are tracked in the GDB_SUBTYPE system table, the default values for the subtypes are tracked in the GDB_DEFAULTVALUES system table, and the fields to which these apply are tracked in the GDB_FIELDINFO system table. The subtypes are associated to the feature class by way of the GDB_OBJECTCLASSES table. The GDB_DEFAULTVALUES table is associated with the GDB_SUBTYPES table by the subtype code, which is stored in the SubtypeCode field in the GDB_SUBTYPES table and the Subtype field in the GDB_DEFAULTVALUES table.

The name of the field to which the subtype applies is stored in the SubtypeField column of the GDB_OBJECTCLASSES table. This field is linked to the FieldName column in the GDB_FIELDINFO table, which in turn is associated to the FieldName column in the GDB_DEFAULTVALUES table.

Subtypes in an XML document

Subtypes appear in XML documents as part of the information for the feature class. They are grouped under a Subtypes tag. For the Laterals example, the subtype information in an XML document is as follows:

- <Subtypes xsi:type="esri:ArrayOfSubtype">
  <Subtype xsi:type="esri:Subtype">
      <SubtypeName>Unknown</SubtypeName> 
      <SubtypeCode>0</SubtypeCode> 
    <FieldInfos xsi:type="esri:ArrayOfSubtypeFieldInfo">
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>H_CONFID</FieldName> 
          <DefaultValue xsi:type="xs:int">0</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>DIAMETER</FieldName> 
          <DomainName>LatDiameter</DomainName> 
          <DefaultValue xsi:type="xs:double">8</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>DEPTH_BURI</FieldName> 
          <DefaultValue xsi:type="xs:double">0</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>RECORDED_L</FieldName> 
          <DefaultValue xsi:type="xs:double">0</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>WNM_TYPE</FieldName> 
          <DefaultValue xsi:type="xs:string">WUNKNOWN</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>PWTYPE</FieldName> 
          <DefaultValue xsi:type="xs:string">WUNKNOWN</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>MATERIAL</FieldName> 
          <DomainName>Material</DomainName> 
          <DefaultValue xsi:type="xs:string">DI</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>TYPECODE</FieldName> 
          <DefaultValue xsi:type="xs:int">3</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>ENABLED</FieldName> 
          <DomainName>EnabledDomain</DomainName> 
          <DefaultValue xsi:type="xs:short">1</DefaultValue> 
        </SubtypeFieldInfo>
     </FieldInfos>
  </Subtype>
<Subtype xsi:type="esri:Subtype">
    <SubtypeName>Hydrant laterals</SubtypeName> 
    <SubtypeCode>1</SubtypeCode> 
  <FieldInfos xsi:type="esri:ArrayOfSubtypeFieldInfo">
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>H_CONFID</FieldName> 
          <DefaultValue xsi:type="xs:int">0</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>DIAMETER</FieldName> 
          <DomainName>LatDiameter</DomainName> 
          <DefaultValue xsi:type="xs:double">8</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>DEPTH_BURI</FieldName> 
          <DefaultValue xsi:type="xs:double">0</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>RECORDED_L</FieldName> 
          <DefaultValue xsi:type="xs:double">0</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>WNM_TYPE</FieldName> 
          <DefaultValue xsi:type="xs:string">WHYDLIN</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>PWTYPE</FieldName> 
          <DefaultValue xsi:type="xs:string">WHYDLIN</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>MATERIAL</FieldName> 
          <DomainName>Material</DomainName> 
          <DefaultValue xsi:type="xs:string">DI</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>ENABLED</FieldName> 
          <DomainName>EnabledDomain</DomainName> 
          <DefaultValue xsi:type="xs:short">1</DefaultValue> 
        </SubtypeFieldInfo>
     </FieldInfos>
  </Subtype>
<Subtype xsi:type="esri:Subtype">
    <SubtypeName>Fire laterals</SubtypeName> 
    <SubtypeCode>2</SubtypeCode> 
  <FieldInfos xsi:type="esri:ArrayOfSubtypeFieldInfo">
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>H_CONFID</FieldName> 
          <DefaultValue xsi:type="xs:int">0</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>DIAMETER</FieldName> 
          <DomainName>LatDiameter</DomainName> 
          <DefaultValue xsi:type="xs:double">8</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>DEPTH_BURI</FieldName> 
          <DefaultValue xsi:type="xs:double">0</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>RECORDED_L</FieldName> 
          <DefaultValue xsi:type="xs:double">0</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>WNM_TYPE</FieldName> 
          <DefaultValue xsi:type="xs:string">WFIRELIN</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>PWTYPE</FieldName> 
          <DefaultValue xsi:type="xs:string">WFIRELIN</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>MATERIAL</FieldName> 
          <DomainName>Material</DomainName> 
         <DefaultValue xsi:type="xs:string">DI</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>ENABLED</FieldName> 
          <DomainName>EnabledDomain</DomainName> 
          <DefaultValue xsi:type="xs:short">1</DefaultValue> 
        </SubtypeFieldInfo>
     </FieldInfos>
  </Subtype>
<Subtype xsi:type="esri:Subtype">
    <SubtypeName>Service laterals</SubtypeName> 
    <SubtypeCode>3</SubtypeCode> 
  <FieldInfos xsi:type="esri:ArrayOfSubtypeFieldInfo">
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>H_CONFID</FieldName> 
          <DefaultValue xsi:type="xs:int">0</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>DIAMETER</FieldName> 
          <DomainName>LatDiameter</DomainName> 
          <DefaultValue xsi:type="xs:double">8</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>DEPTH_BURI</FieldName> 
          <DefaultValue xsi:type="xs:double">0</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>RECORDED_L</FieldName> 
          <DefaultValue xsi:type="xs:double">0</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>WNM_TYPE</FieldName> 
          <DefaultValue xsi:type="xs:string">WSERVICE</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>PWTYPE</FieldName> 
          <DefaultValue xsi:type="xs:string">WSERVICE</DefaultValue> 
       </SubtypeFieldInfo>
     <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>MATERIAL</FieldName> 
          <DomainName>Material</DomainName> 
          <DefaultValue xsi:type="xs:string">DI</DefaultValue> 
        </SubtypeFieldInfo>
      <SubtypeFieldInfo xsi:type="esri:SubtypeFieldInfo">
          <FieldName>ENABLED</FieldName> 
          <DomainName>EnabledDomain</DomainName> 
          <DefaultValue xsi:type="xs:short">1</DefaultValue> 
        </SubtypeFieldInfo>
     </FieldInfos>
   </Subtype>
 </Subtypes>