Skip to content

ChangeLog

V1.2.0 - 5/19/2026

Enhancements

  • The Add Methods Table, Domain, and MethodID Field template option now adds MethodID to all feature classes. Previously, only a subset of feature classes gained this field.
  • Add support for OverlayPolys. Symbol receives its own domain. Attribute rules control Type and if applicable, OverlayPolys_ID. IdentityConfidence and DataSourceID are domain controlled and required by constraint rules.
  • Add DataSourceID domain to DMU DescriptionSourceID and Glossary DefinitionSourceID fields.

V1.1.1 - 3/6/2026

Bug Fixes

  • If the DMU_Table sheet of the template Excel workbook contained map unit descriptions longer than 3000 characters, the corresponding MapUnit would fail to append to the GeMS database, although it would be part of the MapUnit domain. Now, the template toolbox will increase the Description field length if needed.

V1.1.0 - 3/6/2026

Enhancements

  • Include ability to parse legacy LTYPE field for MapUnitLines. The attribute rule can handle both Symbol=MapUnit and Symbol=FGDC Code.

Bug Fixes

  • CartographicLines and IsoValueLines would always include an LTYPE field, regardless of whether the user selected the Add LTYPE, PTTYPE, and PTYPE Fields options.

V1.0.0 - 1/12/2026 - Initial Provisional Release

There are no toolbox changes in this version. This release indicates that the toolbox is publicly available via provisional release.

Prior versions are maintained below for historical reference. Only a subset have actual formal releases. All others are from an archived version of this repository and were squashed into a single initial commit within this repository.

V0.13.01 - 9/17/2025

Enhancements

  • For OrientationPoints, Inclination can now be set to -9999 for inclined features such as bedding measurements. This can be useful when digitizing a legacy map that does not have an Inclination label printed on the map. If -9999 is used, Label will be left blank.

V0.13.0 - 9/4/2025

Enhancements

  • An unlimited number of custom named GenericPoints feature classes can be added to a template database. Previously, only one GenericPoints feature class could be added

Bug Fixes

  • The Trigger Attribute Rules tool excluded certain supported feature classes. Now, all feature classes supported by the template work with this tool
  • In certain cases, Caclulate GeMS Field Values did not update PlotAtScale values. This has been corrected.

V0.12.0 - 7/21/2025

Enhancements

  • The Auto Populate GeMS Feature Class _ID Fields with GlobalID template option now includes the DescriptionOfMapUnits, Glossary, and RepurposedSymbols tables.
  • If Auto Populate GeMS Feature Class _ID Fields with GlobalID is selected, DescriptionOfMapUnits data added via the template spreadsheet or a standalone DMU table will have their DescriptionOfMapUnits_ID fields populated with GlobalID.
  • If Auto Populate GeMS Feature Class _ID Fields with GlobalID is selected, Glossary table rows for certain and questionable entries will have their Glossary_ID set to their GlobalID.
  • All nonspatial tables now have GlobalIDs regardless of whether they use attribute rules.
  • The Trigger Attribute Rules utility tool can now trigger rules for the DescriptionOfMapUnits, Glossary, and RepurposedSymbols tables.

V0.11.1 - 7/16/2025

Bug Fixes

  • Fixed an issue where databases created by this toolbox caused the GeMS Validate Database script to crash with version 2.13.5 of the GeMS toolbox and version 3.4.3 of ArcGIS Pro. Specifically, GlobalIDs must be enabled before adding a Topology class to a feature dataset.

For databases created before this release, any of the following will allow the GeMS Validate Database script to run:

  1. Deleting and recreating the topology class - this is a permanent fix
  2. Skipping topology
  3. Deleting the topology class without recreating it, thereby allowing the Validate Database script to create a separate database to check topology.

V0.11.0 - 7/3/2025

Enhancements

  • Added Export and Delete Attribute Rules tool which saves a copy of all rules and the AttrRules_CalcFromSymbol table before deleting the rules and table
  • Added Reimport Attribute Rules tool which can take the export generated by Export and Delete Attribute Rules and reimport the AttRules_CalcFromSymbol table and attribute rules

V0.10.2 - 7/1/2025

This release is for documentation changes only. This includes:

  • Removal of trailing whitespace from Methods table in LOCOS domains spreadsheet

V0.10.1 - 6/6/2025

This release is for documentation changes only. This includes:

  • Instructions for external collaborators to install the toolbox and generate the documentation locally
  • Update to GeMS Tools version compatability. This toolbox is compatible with v2.13.5 of the GeMS Toolbox

V0.10.0 - 9/19/2024

Enhancements

  • Add IsoValueLines GeMS feature class to output template databases complete with applicable attribute rules
  • Add ability to parse PTYPE for non-composite map units into GeMS fields
  • Add ability to parse PTTYPE for point feature classes
  • Add ability to parse LTYPE for CartographicLines and IsoValueLines; template toolbox adds LTYPE fields to these feature classes
  • Add toolbox categories to organize toolbox scripts into 1. Database Creation and 2. Utility Tools

  • Add various utility tools to help with database cleanup, largely after appending data from a non-GeMS database. Tools that make data changes automatically create backups by using the GeMS Compact and Backup tool:

    • Calculate GeMS Field Values - SourceID fields, PlotAtScale, OrientationConfidenceDegrees, MapUnit in point feature classes
    • Delete Optional Unused Feature Classes and Tables - deletes any unused feature classes/tables added by the tool that are optional
    • Toggle Legacy PTYPE/LTYPE/PTTYPE Parsing Rules - enable or disable legacy field parsing rules throughout the database
    • Trigger Attribute Rules - ability to trigger attribute rules on selected feature classes

V0.9.1 - 9/10/2024

This release is for documentation changes only. The quick start tutorial mentions a LOCOS_Template_Example.lyrx file that should be in the zip folder LOCOS_Template_Example.gdb.zip. However it was not, making it difficult to follow the tutorial. The lyrx file has been moved to the correct location.

V0.9.0 - 7/31/2024

Enhancements

  • Add the RepurposedSymbols GeMS nonspatial table to output template databases
  • Add the option to include a GenericPoints feature class along with the ability to specify a custom name. The custom name will rename both the feature class and the GeMS _ID field. Applicable attribute rules are automatically added.

V0.8.0 - 7/12/2024

Prior versions of the Template Workbook will not function with this version of the toolbox

Enhancements

  • For the template option Add Surficial MapUnit Fields and Rules, change how BedrockMapUnits are identified. Users now specify BedrockMapUnits in a new sheet in the Template Workbook. The template toolbox then generates a BedrockMapUnits domain from that sheet. The attribute rule that controls BedrockMapUnit then populates the field if CompositeMapUnit contains a unit in the BedrockMapUnit domain.
  • Update attribute rule for Include Attribute Rule to Parse PTYPE into Component MapUnits template option to populate BedrockMapUnit based on the BedrockMapUnit domain, to match the behavior described above.
  • Update toolbox site documentation with instructions on new Template Workbook sheet and changes in BedrockMapUnit population behavior.

V0.7.0 - 6/24/2024

Enhancements

  • add LTYPE parsing rule as an option for a template conversion database. This rule uses the AttrRules_CalcFromSymbol table to parse LTYPE into GeMS attributes.
  • Update CompositeMapUnit rules to exclude ml from BedrockMapUnit.
  • Add IdentityConfidenceSecondUnit field to track confidence values for a second unit in CompositeMapUnit. Includes attribute rule updates to maintain Label and enforce use of field where applicable.
  • Add WBR_Template_Domains_TEST.xlsx, a second example spreadsheet, which does not have DataSources (other than standard entries), a DMU, or Methods.

Bug Fixes

  • Label attribute rule for MapUnitLabelPoints/Polys was not processing pediment units correctly, added a / instead of a -.
  • Toggle Attribute Rules/Editor Tracking utility tool would fail if attempting to enable/deactivate attribute rules in a feature class with no attribute rules.
  • In LOCOS_Template_Domains_Test.xlsx, OrientationPoint symbols and descriptions 09.001 - 09.099 were missing a leading zero after the decimal.
  • In LOCOS_Template_Domains_Test.xlsx, Inclination values were occasionally assigned for symbols that do not use inclination but that had vertical or horizontal in their descriptions.

V0.6.0 - 4/29/2024

This is a documentation changes only release. Toolbox functionality has not been changed.

  • Home page rebuilt
  • Getting Started Guide largely rewritten to incorporate both a tutorial on using the example database and a tutorial on the tool itself
  • Creating template gdbs section largely rewritten and re-organized
  • New references section, as a placeholder for future documentation, has been added. Pages currently marked as under construction

Documentation related to conversion gdbs, qc-ing source databases, and appending data is under construction and marked as such within the documentation.

V0.5.0 - 4/17/2024

This is a documentation changes only release. Toolbox functionality has not been changed. The Wiki for this project has been removed. All documentation has been migrated to a GitLab page. The ReadMe has also been significantly simplified, with many links now provided to the GitLab page. Embedded toolbox metadata that used to link to the wiki now points to the GitLab page.

The GitLab page can be accessed via the GitLab Pages button on the project's main page, through the various links in the ReadMe, and directly here: GitLab Page. The GitLab page is generated from the .md files in the docs directory using a CI/CD setup provided by the USGS CTEK group. The setup involves use of MkDocs and the Material Theme

The .md files in the docs directory can be viewed locally in a text editor but are best viewed via the GitLab page.

The documentation has been partially reorganized, but no major changes have been made.

Future documentation updates will be made in separate branches and merged with the main branch. Releases will be tagged each time documentation updates are made. The GitLab Page is regenerated whenever the underling .md files are updated on the main branch.

V0.4.4 - 4/8/2024

Migrating from Previous Versions

If you used a prior version of this tool, make sure to use the version of the schema spreadsheet included with this release (or later releases). The Symbol Domain tab was renamed to make it more compatible with script tools. The tool will crash if you use an outdated version of the spreadsheet.

Enhancements

  • AttrRules_CalcFromSymbol table now has editor tracking fields which are enabled from the beginning of the script. The toggle attribute rules/editor tracking tool continues to ignore this table and will not deactivate/activate editor tracking.
  • The Description and GeMSFeatureClass columns from the Symbol_Domain workbook sheet are now retained by the table in the database.
  • LTYPE, PTYPE, and PTTYPE are included both in the Symbol_Domain workbook sheet and are retained in the database table.

V0.4.3 - 3/26/2024

Take Note in V0.4.0 about changes required to migrate to this version if you were previously using 0.3.x or earlier.

Bug Fixes

  • The script would crash for databases with long names. Intermediate data is saved to memory for performance reasons. However, if the names of tables are too long, data cannot be saved to memory. Intermediate table names no longer use the gdb name since it is only intermediate data.
  • MapUnit domain order was dependent on the order of the input table or spreadsheet which could result in mis-ordered map units. Instead, sort the domain by hierarchy key.
  • Symbol domain order was dependent on the order of the input spreadsheet which could result in unhelpful ordering of symbols. Instead, sort the domain by Symbol, which is typically 0 padded FGDC codes.

V0.4.2 - 3/25/2024

Take Note in V0.4.0 about changes required to migrate to this version if you were previously using 0.3.x or earlier.

Bug Fixes

  • When importing data from spreadsheets, blank column values are imported as white space. Template toolbox now uses GeMS Tools Fix Strings to clean up the data.
  • The Notes field in the Method table was not set to allow null values, which was causing the GeMS Fix Strings tool to fail to clean up all spreadsheet data. Set to nullable.
  • Attribute rule for calculating BedrockMapUnit could fail to populate the field if the unit appeared in UnderlyingMapUnit.

V0.4.1 - 3/21/2024

Take Note in V0.4.0 about changes required to migrate to this version. This minor version fixes the following bugs:

Bug Fixes

  • An updated attribute rules file for MethodID was not included in the original release, causing the toolbox to fail if a Methods table was included.

V0.4.0 - 3/21/2024

Migrating from Previous Versions If you used a prior version of this tool, make sure to use the version of the schema spreadsheet included with this release (or later releases). The Methods tab and DataSources tab were reorganized with different column names. The tool will crash if you use an outdated version of the spreadsheet.

Enhancements

  • DataSources, DMU, and Methods tables can be populated from either the schema spreadsheet or a corresponding non-spatial table in a file geodatabase. The nonspatial fgdb table must follow GeMS.
  • Split the Create New Template GDB into two tools, one designed for new data and one designed for appending data. The tool for appending data has more options to aid in that workflow.
  • Order of extra fields added to feature classes has been updated. CompositeMapUnit and related fields appear after GeMS standard fields. MethodID, if applicable, then appears. Editor Tracking fields appear next and GlobalID appears at the end.
  • Added option to include a blank Methods Table. The domain is included and assigned, but also contains no values, and MethodID is still added to applicable feature classes. The MethodID is required constraint rule only requires the field if there is data added to the Methods table.
  • Parse PTYPE attribute rule no longer skips dependent fields if they have values.

Bug Fixes

  • The tool copies DMU information to memory for performance reasons. In some cases, the DMU in memory was not deleted when the script finished.
  • In certain cases, MapUnitLabelPoints and Methods did not have editor tracking fields.

V0.3.0 - 3/12/2024

Enhancements

  • Add support for pediments in CompositeMapUnit attribute rule
  • Add option for including an attribute rule to parse PTYPE composite units into its components
  • Include BedrockMapUnit and corresponding attribute rule to Add Surficial MapUnit Fields and Rules template option
  • When adding surficial MapUnit fields and rules, both MapUnitPolys and MapUnitLabelPoints no longer have a domain assigned to Symbol and Symbol is set equal to CompositeMapUnit. Previously, MapUnit and Symbol were equal and both used a MapUnit domain.
  • Add options in Create Template GDB to disable attribute rules and editor tracking in the output database
  • Add separate tool to allow toggling of attribute rules and editor tracking in a database
  • Add use instructions section to ReadMe pointing to the Wiki for enhanced visibility

Bug Fixes

  • Fix issue with CompositeMapUnits not being editable, which could cause appends to fail.
  • Fix issue with script occasionally crashing when Methods rules are added.
  • Remove hidden rows from LOCOS_Template_Domains_TEST.xlsx.

V0.2.1 - 3/5/2024

Enhancements

  • Added support for keeping DMU Headings in the DMU_Table spreadsheet when creating a custom template. Users no longer have to append the headings after the fact. ReadMe and Wiki updated to reflect this change.

V0.2.0 - 3/4/2024

Enhancements

  • The toolbox user interface no longer has a collapsible section for Template Options. They are now always shown.
  • Addition of a Methods table with Methods domain and Method_ID field is now optional.
  • Ability to add surficial map unit fields: UnderlyingMapUnit, SubordinateMapUnit, and CompositeMapUnit have been added along with applicable. attribute rules. Refer to the embedded tooltip and wiki for more information.
  • Ability to add LTYPE/PTYPE/PTTYPE fields.
  • Updates to the wiki to reflect these changes.