Skip to content

Create the Template GDB: For New Databases

Run the Create Template GDB Tool

Note

Make sure you close your Template_Domains workbook before running the tool.

Open the Python toolbox in an ArcGIS Pro project, expand the toolbox, and double-click on Create Template GDB for New Database. All parameter explanations below are also available in the tool's embedded metadata and tooltips.

Required Tool Parameters

Populate parameters as follows:

Parameter Explanation
Path to GeMS Toolbox Navigate to and select a copy of the GeMS Toolbox. It should be the most recent version.
Output Location for Template FGDB Select a folder to output the template GDB
Name for Template GDB Enter a name for the template. This name will also be used in Domain Name and Domain Descriptions.
  • Do not include .gdb in the name; the tool will instruct you to remove it.
  • If a gdb with the same name already exists, you will see a warning that a number will be appended to the name to make it unique. You can change the name instead if you prefer.
Spatial Reference for Template GDB GeologicMap Feature Dataset Select an appropriate spatial reference
Domain, DMU, DataSource, and Method Options Select ‘Custom Values’ to use the custom spreadsheet you created.
  • ‘LOCOS Template Values’ will use the original spreadsheet.
Path to Schema Spreadsheet (visible if Custom Values selected above) Navigate to the .xlsx file containing your customized schema

Template Options

The template options section includes additional database characteristics as described below.

Template Option Explanation
Add Methods Table, Domain, and MethodID Field If checked, the following will be added to the database:
  • Methods nonspatial table with Method_ID, Method, and Notes fields
  • Methods domain populated with Method_ID values from the Methods Table
  • Method_ID field, as a foreign key to the Methods table for all feature classes in the database. The Methods domain is assigned to this field

The Methods table and domain are populated based on the values in the schema spreadsheet. Refer to the Create the Custom Schema - Methods section for more information.
Methods Source Schema Excel Workbook will populate the Methods table based on the values in the schema spreadsheet.

Leave Table and Domain Blank will ignore the schema spreadsheet and add a blank Methods table, blank Methods domain, Method_ID fields to applicable feature classes, and the attribute rule that requires Method_ID. That rule only makes Method_ID required if you have data in your Methods table. So, Method_ID will be optional initially while the Methods table is blank.
Include MapUnitLabelPoints Feature Class Check this box to include a MapUnitLabelPoints feature class containing all the attribute rules and domains that would apply to the MapUnitPolys feature class. This is helpful if you plan to build MapUnitPolys from MapUnitLabelPoints and ContactsAndFaults.

Note: A MapUnitPolys feature class with attribute rules and domains will still be created if this box is checked.
Auto Populate GeMS Feature Class _ID Fields with GlobalID Check this box to automatically copy GlobalID values to GeMS feature class _ID fields such as ContactsAndFaults_ID and the DescriptionOfMapUnits, Glossary, and RepurposedSymbols tables.

Notes:
  • DataSources, Methods, and the GeoMaterialDict are excluded from this option.
  • If you leave this box unchecked, _ID fields will not be required to populate. Therefore, you must populate them via a method of your choice when finalizing the database.
Add 1 or more GenericPoints Feature Classes If checked, adds 1 or more GenericPoints feature class to the output database. After checking this box, a parameter will appear for you to enter names for each feature class you want to add.
GenericPoints Feature Class Names This parameter appears if Add a GenericPoints Feature Class is checked. Specify names for each GenericPoints feature class you would like to add. Names could be GenericPoints or a more specific descriptor for your database such as CinderConePoints. The parameter will display an error if an invalid name is used.

The toolbox will automatically rename feature classes and GeMS _ID fields.

Note: Make sure values in GeMSFeatureClass in your Symbol_Domain sheet uses the name you specify here. Refer to the Create the Custom Schema - GeMSFeatureClass section for more information.
Set ExistenceConfidence and IdentityConfidence Equal Check this box to always set ExistenceConfidence and IdentityConfidence fields equal for feature classes that use both fields.

If this box is left unchecked, for Symbols that are 'existence or identity questionable,' you will have to specify Existence and IdentityConfidence values while creating features. At least one must be set to questionable.
Map Unit Line Symbol Field Uses Map Unit Codes Refer to the table below for more information.

Make sure you set ‘Map Unit Line Symbol Field Uses Map Unit Codes’ properly based on how you set up your Symbol_Domain sheet as described below.

Refer to Create the Custom Schema - MapUnit - For MapUnitLines for more information.

Note

If you will not be digitizing MapUnitLines, you can leave this template option unchecked.

Template Option Symbol Domain Adjustments Template Option Value
Symbol field uses FGDC codes Fill in the MapUnit column with corresponding MapUnit codes DO NOT check the box for ‘Map Unit Line Symbol Field Uses Map Unit Codes.’
Symbol field uses MapUnit codes Replace the FGDC code in Symbol with MapUnit codes.

Description can be left unchanged; it will not be used in the final database.		 CHECK the box for ‘Map Unit Line Symbol Field Uses Map Unit Codes’’

Additional template options include:

Template Option Explanation
Add Surficial MapUnit Fields and Rules Check this box to add additional fields to MapUnitPolys and if applicable, MapUnitLabelPoints to capture Underlying and Subordinate MapUnits.

The following fields are added as type text with a 50 character limit:
  • UnderlyingMapUnit
  • SubordinateMapUnit
  • CompositeMapUnit
  • BedrockMapUnit
  • IdentityConfidenceSecondUnit

Both UnderlyingMapUnit and SubordinateMapUnit are assigned the MapUnit domain and are user populated fields. The following is controlled by attribute rules:
  • Both UnderlyingMapUnit and SubordinateMapUnit fields cannot be populated at the same time for the same MapUnit
  • MapUnit cannot have the same value as either UnderlyingMapUnit or SubordinateMapUnit

CompositeMapUnit is automatically constructed from MapUnit and either SubordinateMapUnit or UnderlyingMapUnit as follows:
  • If SubordinateMapUnit is filled out, CompositeMapUnit is populated as MapUnit+SubordinateMapUnit
  • If UnderlyingMapUnit is filled out, and MapUnit contains a pediment unit (Qpv, Qpd, or Qpi), CompositeMapUnit is populated as MapUnit-UnderlyingMapUnit. Otherwise, CompositeMapUnit is populated as MapUnit/UnderlyingMapUnit

BedrockMapUnit is assigned the BedrockMapUnit domain and is automatically populated if a bedrock unit is present in the CompositeMapUnit. The BedrockMapUnit domain is a subset of the full MapUnit domain. Define bedrock units on the BedrockUnits sheet in schema excel workbook. Refer to Create the Template Workbook - BedrockUnits.

IdentityConfidenceSecondUnit is assigned a domain with values of certain, questionable, and not applicable. It provides an IdentityConfidence for the second unit in a CompositeMapUnit. If only MapUnit is populated, this field is automatically set to not applicable. If either SubordinateMapUnit or UnderlyingMapUnit are populated, this field must be set to either certain or questionable. The original GeMS IdentityConfidence field indicates confidence for the first unit if there are two units, or the only unit if there is one unit.

Label is automatically constructed as the CompositeMapUnit with special characters substituted as applicable. Question marks are added after the first and second unit as applicable based on the values in IdentityConfidence and IdentityConfidenceSecondUnit.

Run the tool. It takes approximately 8 minutes to complete depending on selected template options. Messages are displayed during execution indicating general progress.

Note

If the tool takes significantly longer than 8 minutes to run, particularly during the early stages, try either deleting your project's geoprocessing history or start a new ArcGIS Pro project and re-run the tool.

When the tool completes, proceed to Finalize the Template GDB.