The Microsoft Excel file that is used to generate a geodatabase consists of multiple worksheets based on the components of the geodatabase. The individual worksheets in the file contain the spatial reference, datasets, object classes, subtypes, fields, domains, and metadata you want to include in the database.
These worksheets have a specified format and cannot be altered. The information in the worksheets, other than the column names, can be modified.
The following sections describe the worksheets and the columns on each.
SpatialReferences worksheet
The SpatialReferences worksheet contains information about the spatial reference of the dataset containers or object classes. You can create one record for each spatial reference you want to use with the geodatabase, which allows you to specify the spatial reference for individual feature classes or datasets.
The following table contains the one spatial reference that the geodatabase will use, GCS_WGS_1984. If a different spatial reference is required for another dataset in the geodatabase, another record can be created for it.
Conseil :
The SpatialReferenceString field supports well-known text of coordinate reference systems (WKT or WKT-CRS) values, in which case the FactoryCode field can remain blank. Either the FactoryCode or the SpatialReferenceString field must have a valid value.
The following table provides details about the Spatial References worksheet including the types of information that can populate each one.
Column name | Description | Notes |
---|---|---|
SpatialReference_ID | An identifier that is used in the DatasetContainers or ObjectClasses worksheet | The identifier allows you to specify the spatial reference for a dataset or feature class. |
Description | The name of the spatial reference to be used for the identified datasets or object classes | |
FactoryCode | The code for the coordinate system definition | |
SpatialReferenceString | Custom projection parameters | |
VerticalDescription | The name of the vertical coordinate system to be used for the identified datasets or object classes | |
VerticalFactoryCode | The code for the vertical coordinate system definition | |
XMin | The minimum value for the x-coordinate of the defined bounding box of the data container | The x-coordinate is the longitude coordinate of the world axis. |
YMin | The minimum value for the y-coordinate of the defined bounding box of the data container | The y-coordinate is the latitude coordinate of the world axis. |
XMax | The maximum value for the x-coordinate of the defined bounding box of the data container | |
YMax | The maximum value for the y-coordinate of the defined bounding box of the data container | |
XYPrecision | The inverse of the xy resolution | |
ZMin | The minimum value for the z-coordinate of the defined bounding box of the dataset container | |
ZMax | The maximum value for the z-coordinate of the defined bounding box of the dataset container | |
ZPrecision | The inverse of the z-resolution | |
MMin | The minimum value for the m- or measurement coordinates of the defined bounding box of the dataset container | M-values are used to store measured distances along a line feature that are independent of the actual geometry lengths. They allow you to store additional information directly in the geometry. |
MMax | The maximum value for the m- or measurement coordinate of the defined bounding box of the dataset container | |
MPrecision | The inverse of the M resolution |
DatasetContainers worksheet
The DatasetContainers worksheet contains information about the feature datasets, including the type and spatial reference. Each dataset is assigned a unique identifier that can be referenced when you are creating object classes. The following table creates one dataset in the geodatabase, CTM, and it has a unique identification number associated with it.
The following table describes each column on the DatasetContainers worksheet and provides details about the types of information that can populate each one, as applicable.
Column name | Description | Notes |
---|---|---|
Dataset_ID | A unique identifier for the feature datasets that will be created | This number is used to reference the feature dataset in other worksheets. |
CreateDataset | A Boolean field that indicates whether the feature dataset will be created | |
DatasetType | Describes the Esri dataset type constant, for example, feature dataset | |
DatasetName | The name of the dataset type that will be created | |
SpatialReference_ID | A reference to the spatial reference that will be used when the dataset type is created |
ObjectClasses worksheet
The ObjectClasses worksheet contains information about the feature classes and tables that will be included in the geodatabase. The Dataset_ID field references feature datasets, which contain the feature classes and tables. The following table references one dataset.
The following table describes each column on the Object Classes worksheet and provides details about the types of information that can populate each one, as applicable.
Column name | Description | Notes |
---|---|---|
ObjectClass_ID | A unique identifier for the object classes (feature classes or tables) that will be created | This number is used to reference the object class in other worksheets. |
Dataset_ID | A reference to the Dataset_ID column on the DatasetContainers worksheet | The value in this column determines which dataset will contain the feature class or table. If the feature class or table is not part of a dataset, the value in this column should be less than 1 (preferably -9999). |
CreateObjectClass | A Boolean field that indicates whether the specified object class will be created | |
ObjectClassName | The name of the object class that will be created | This name is subject to the ArcGIS Pro restrictions on feature class and table names. |
ObjectClassAlias | The alias name for the specified object class | This is the name in the Contents pane when the object class is added to ArcGIS Pro. |
ObjectClassDescription | An optional field that can be used to further describe the specified object class | |
ObjectClassDataType | The type of object class that will be created (feature class, table, and so on) | Possible values for this column are as follows:
|
ObjectClassFeatureType | The types of features that will be stored in the specified object class (simple, annotation, and so on) | Possible values for this column are as follows:
|
ObjectClassGeometry | The type of feature geometry that will be stored in the specified object class (point, line, and polygon) | Possible values for this column are as follows:
|
SpatialReference_ID | A reference to the SpatialReference_ID column on the SpatialReferences worksheet | |
HasZ | A Boolean field that indicates whether the specified object class will store z-values | |
HasM | A Boolean field that indicates whether the specified object class will store m-values |
Subtypes worksheet
The Subtypes worksheet contains information about the subtypes. This includes the unique identification number for each subtype as well as the feature class with which it is associated. When there are multiple subtypes in a feature class, you can assign a default subtype to the feature class.
The following table describes each column on the Subtypes worksheet and provides details about the types of information that can populate each one, as applicable.
Column name | Description | Notes |
---|---|---|
Subtype_ID | A unique identifier for the subtypes | It is used on other worksheets to reference the subtype. |
ObjectClass_ID | A reference to the ObjectClass_ID column on the ObjectClasses worksheet | The value in this column determines which feature class will contain the subtype. |
CreateSubtype | A Boolean field that indicates whether the specified subtype will be created | |
SubtypeField | The integer field in the feature class that stores the subtype codes | |
SubtypeNumber | The integer value that serves as the code for the specified subtype | |
SubtypeName | The name of the subtype that will be created | |
SubtypeDescription | An optional description of the specified subtype | |
SubtypeDefault | A Boolean field that indicates whether the specified subtype is the default subtype for a feature class | If there are multiple rows for one feature class (that is, it contains multiple subtypes), only one of those rows should contain a value of True in this column because there can only be one default. |
Fields worksheet
The Fields worksheet contains information about the fields on the feature classes, including the object classes, subtypes, and domains with which they are associated. There is one entry per field for each subtype or feature class. This means that if you have the same field in multiple feature classes, it must be added for each feature class and subtype. For example, in the following table, FCSubtype and F_CODE are fields that are included in both subtype 2 and 3 for object class 2.
The order of the fields is determined by the order in this worksheet. You can define all of the fields in the first subtype and include only the fields with a valid default value or domain in the subsequent subtypes.
The following table describes each column on the Fields worksheet and provides details about the types of information that can populate each one, as applicable.
Column name | Description | Notes |
---|---|---|
Field_ID | A unique identifier for the field for a subtype or feature class | |
ObjectClass_ID | A reference to the ObjectClass_ID column on the ObjectClasses worksheet | The value in this column determines which feature class or table will contain the field. |
Subtype_ID | A reference to the Subtype_ID column on the Subtypes worksheet | The value in this column determines which subtype will contain the field. If the feature class defined in the ObjectClass_ID field does not contain any subtypes, use -9999. |
CreateField | A Boolean field that indicates whether the field will be created | |
FieldName | The name of the field that will be created | This name is subject to the ArcGIS Online restrictions on field names. Field names in the same table or feature class must be unique (you cannot have two fields with the same name). |
FieldAlias | The alias name (alternate name) of the field | The field alias can be used to show a more descriptive version of the field name. |
FieldDescription | An optional field that can be used to further describe the field | |
FieldDomainName | The name of the coded value or range domain associated with the field | If the specified field is not constrained by an attribute domain, leave the Field Domain Name value blank. |
FieldType | The types of values that will be stored in the field (text, integer, and so on) | Possible values for this field include the following:
|
FieldDefaultValue | The default value for the field | |
FieldEditable | A Boolean field that indicates whether the field can be edited | |
FieldIsNullable | A Boolean field that indicates whether the field can contain null values | |
FieldLength | The maximum number of allowable characters for the field value | This option is only applicable for String or BLOB field types. |
FieldPrecision | The number of digits that can be stored in the field | All digits are counted, regardless of which side of the decimal they are on. This column is only used for Double and Integer field types. |
FieldScale | The number of decimal places stored in a field | This column is only used for Double field types. |
Domains worksheet
The Domains worksheet contains information about coded value and range domains. The domains can be created to populate a more general range of values, such as an existence category, or they can be created specifically for a feature class or subtype field. With some databases, the individual subtypes can be domain values.
In the following table, a unique Domain_ID value is assigned to each possible domain value. The values are then grouped based on the domain name.
The following table describes each column on the Domains worksheet and provides details about the types of information that can populate each one, as applicable.
Column name | Description | Notes |
---|---|---|
Domain_ID | A unique identifier for each domain value | |
CreateDomain | A Boolean field that indicates whether the domain will be created | |
Name | The name of the domain | This name is subject to the ArcGIS Pro restrictions on domain names. |
Description | An optional field that can be used to further describe the domain | |
DomainCode | A number that represents a value in a coded domain | This column is applicable to the Coded Domain data type. |
DomainMin | The minimum value of a range domain | |
DomainMax | The maximum value of a range domain | |
DomainDescription | A description of what the coded value represents | This column is applicable to the Coded Domain data type. |
DomainDataType | The type of domain (Coded Value or Range) | Possible values for this column are as follows:
|
DomainFieldType | The types of values to be stored in the domain (text, integer, and so on) | This value must be the same as the Field Type value on the Fields worksheet for any fields with which the domain is associated. Possible values for this column are as follows:
|
DomainSplitPolicy | The behavior of an attribute's values when a feature that is split is controlled by a split policy | Possible values for this column are as follows:
|
DomainMergePolicy | The behavior of attribute values when two features are merged into a single feature | Possible values for this column are as follows:
|
MetaInfo worksheet
The MetaInfo worksheet contains feature class-level metadata information that is used to create fields on existing or newly created feature classes. Having metadata items defined on the MetaInfo worksheet allows you to include that set of fields on any feature class. For example, in the following graphic, the fields that are listed on the MetaInfo worksheet create a set of metadata attributes that can be added to all the feature classes in the database.
This is done on the Fields worksheet, where you can have a row that contains the METADATAINFO keyword in the FieldName column. In the example below, row 22 of the Fields worksheet uses METADATAINFO as the FieldName value, meaning that the attributes listed on the MetaInfo worksheet will be added to the end as metadata for the feature class. This eliminates the need to add metadata fields to each applicable feature class.
The following table describes each column on the MetaInfo worksheet and provides details about the types of information that can populate each one, as applicable.
Column name | Description | Notes |
---|---|---|
MetaInfo_ID | A unique identifier for the metadata field | |
ObjectClass_ID | A reference to the ObjectClass_ID column on the ObjectClasses worksheet | This reference is not needed for the MetaInfo worksheet; use -9999. |
Subtype_ID | A reference to the Subtype_ID column on the Subtypes worksheet | This reference is not needed for the MetaInfo worksheet; use -9999. |
CreateMetaInfo | A Boolean field that indicates whether the specified metadata field will be created | |
MetaInfoName | The name of the metadata field that will be created | This name is subject to the ArcGIS Pro restrictions on field names. Field names in the same table or feature class must be unique (you cannot have two fields with the same name). |
MetaInfoAlias | The alias name (alternate name) of the metadata field | The metadata field alias name can be used to show a more descriptive version of the metadata field name. |
MetaInfoDescription | An optional field that can be used to further describe the specified metadata field | |
MetaInfoDomainName | The name of the coded value or range domain associated with the metadata field | If the specified metadata field is not constrained by an attribute domain, MetaInfoDomainName is blank. |
MetaInfoFieldType | The types of values that will be stored in the specified metadata field (text, integer, and so on) | Possible values include the following:
|
MetaInfoDefaultValue | The default value of the metadata field | |
MetaInfoEditable | A Boolean field that indicates whether the metadata field can be edited | |
MetaInfoIsNullable | A Boolean field that indicates whether the specified metadata field can contain null values | |
MetaInfoLength | The maximum number of allowable characters for each record of the metadata field | This option is only applicable for metadata fields that are String or BLOB field types. |
MetaInfoPrecision | The number of digits that can be stored in the metadata field | All digits are counted, regardless of which side of the decimal they are on. This parameter is only used in Double and Integer metadata field types. |
MetaInfoScale | The number of decimal places stored in a metadata field | This is only applicable in Double data field types. |
Rubriques connexes
Vous avez un commentaire à formuler concernant cette rubrique ?