These tools and scripts are provided for educational use only. These were written by what is unarguably the worst Python coder in the world, but they get the job done. What is the job? Automating repetitive data management and creation tasks and ensuring that consistent schema and data standards are applied across all databases. Find something wrong (actually can you find the 458 errors?)? Log an “Issue” and maybe I’ll fix it. Got a better idea? Spoon the repo and perhaps I’ll merge it back into the source.
1. Create Core Standard Feature Class in an Existing File Geodatabase: Use this tool when a NPS core standard feature class is required in an existing geodatabase. Execute the tool with user-supplied parameters. The recommend output location is the default geodatabase created when a new Pro project is created if the user has opted for that to occur in Project Options. Many parameters can be set as defaults in the tool properties. This will create all of the fields specified in the standard, as well as set default domain (pick list) values, and set certain fields as "required" (can't delete the field). This tool can be run multiple times against the same geodatabase, for example, to create a point, polygon, and polyline feature class all using the same schema. Additional executions of the tool will detect the presence of existing required domains and will not overwrite them. This tool cannot be executed against an existing feature class and will return an error if attempted.
2. Create Standard GDB in Choice of Location: Use this tool when a NPS core standard feature class is required in a new geodatabase located in a path\folder that is determined by the user. Execute the tool with user-supplied parameters. The recommend output location of the File Geodatabase is in the "Root" of the Pro project folder. Many parameters can be set as defaults in the tool properties. This will create all of the fields specified in the standard, as well as set default domain (pick list) values, and set certain fields as "required" (can't delete the field).
3. Create Standard GDB in Enforced Location in Pro Project: Use this tool when a NPS core standard feature class is required in a new geodatabase located in a path\folder that is specified in a data management SOP. Execute the tool with user-supplied parameters after executing Create Folders in Pro Project. This will place the File Geodatabase in a subfolder within the Pro project folder where the subfolder is the required location of project geodata regardless of how "Pro is intended to be used". Many parameters can be set as defaults in the tool properties. This will create all of the fields specified in the standard, as well as set default domain (pick list) values, and set certain fields as "required" (can't delete the field). Changing the output location of the geodatabase requires modification of the python source, explained elsewhere in this document.
4. Create Folders In Pro Project: Used for new work, once a new Pro Project has been created, run this tool to create the "standard" project folder directory within the project. Can be used for existing work: with caution, most existing project folders are not compatible with how Pro "manages" project folders and files. This tool satisfies any data management plan requirements that geodata reside in a specified location and only in that location.
5. Add Extended Core Attributes to Existing Feature Class: This tool is used when the user has an existing geodatabase feature class that requires the NPS Core Extended attributes and domains. Execute the tool with user-supplied parameters after executing the Create Core Standard Feature Class tool in an Existing File Geodatabase, Create Standard GDB in Enforced Location in Pro Project, Create Standard GDB in Choice of Location, on a feature class created by another process, or a pre-existing feature class. This will create all of the extended fields specified in the standard, as well as set default domain (pick list) values. Only those fields that are checked in the tool dialogue and affiliated domains will be created. This tool can also be run multiple times against the same feature class, for example, if the first tool execution only added one field, subsequent tool executions against the same feature class can add additional fields. Tool validation will detect the presence of existing extended fields and domains and will not overwrite them if they exist.
6. Add GRSM Core Attributes to Existing Feature Class: This tool is used when the user has an existing geodatabase feature class that requires the GRSM Core attributes and domains. Execute the tool with user-supplied parameters after executing the Create Core Standard Feature Class tool in an Existing File Geodatabase, Create Standard GDB in Enforced Location in Pro Project, Create Standard GDB in Choice of Location, on a feature class created by another process, or a pre-existing feature class. This will create all of the extended fields specified in the standard, as well as set default domain (pick list) values. The GRSM version of this tool presents the user with some choice of fields at run time (check boxes) however not requiring any of the optional fields is not a reason to not execute this tool: this tool adds required GRSM fields and domains to a feature class even if no optional fields are chosen in the tool dialogue, and must be executed against any GRSM feature class not containing the required fields (e.g VALID). This tool also makes some changes to the required NPS core schema: changes the default value of some attributes to another value from the NPS core schema other than the default value specified by the standard and adds a domain for MAPMETHOD. This tool can also be run multiple times against the same feature class, for example, if the first tool execution only added one field, subsequent tool executions against the same feature class can add additional fields. Tool validation will detect the presence of existing GRSM fields and domains and will not overwrite them if they exist.
7. Add GRSM Fisheries Core Attributes to Existing Feature Class: This tool is used when the user has an existing geodatabase feature class that requires the GRSM Core attributes and domains. Execute the tool with user-supplied parameters after executing the Create Core Standard Feature Class tool in an Existing File Geodatabase, Create Standard GDB in Enforced Location in Pro Project, Create Standard GDB in Choice of Location, on a feature class created by another process, or a pre-existing feature class. This will create all of the extended fields specified in the standard, as well as set default domain (pick list) values. The GRSM version of this tool presents the user with some choice of fields at run time (check boxes) however not requiring any of the optional fields is not a reason to not execute this tool: this tool adds required GRSM fields and domains to a feature class even if no optional fields are chosen in the tool dialogue, and must be executed against any GRSM feature class not containing the required fields (e.g VALID). This tool also makes some changes to the required NPS core schema: changes the default value of some attributes to another value from the NPS core schema other than the default value specified by the standard and adds a domain for MAPMETHOD. This tool can also be run multiple times against the same feature class, for example, if the first tool execution only added one field, subsequent tool executions against the same feature class can add additional fields. Tool validation will detect the presence of existing GRSM fields and domains and will not overwrite them if they exist.
8. Add Standard Core Attributes to Existing Empty Feature Class: Use this tool when a NPS core standard is required in an existing feature class that has no data. Execute the tool with user-supplied parameters. Many parameters can be set as defaults in the tool properties. This will create all of the fields specified in the standard, as well as set default domain (pick list) values, and set certain fields as "required" (can't delete the field). This tool can be run multiple times against the same geodatabase, for example, to create a point, polygon, and polyline feature class all using the same schema. Additional executions of the tool will detect the presence of existing required domains and will not overwrite them.
9. Add Standard Core Attributes to Existing Non-Empty Feature Class: Use this tool when a NPS core standard is required in an existing feature class that is populated with data. Execute the tool with user-supplied parameters. Many parameters can be set as defaults in the tool properties. This will create all of the fields specified in the standard, as well as set default domain (pick list) values, and set certain fields as "required" (can't delete the field). This tool can be run multiple times against the same geodatabase, for example, to create a point, polygon, and polyline feature class all using the same schema. Additional executions of the tool will detect the presence of existing required domains and will not overwrite them.
10. Calculate Coordinates: This tool is used to update X_COORD, Y_COORD, LON, and LAT Fields with current coordinates when a new feature is added or an existing one moved.
11. Calculate Elevation: This tool is used to attribute elevation for new or modified features.
12. Update Administrative Boundaries for Features: This tool is used to attribute "Administrative Boundaries" to a feature class. Administrative boundaries delineate data into reportable administrative classes.
13. Update Name of Nearest Line Feature for Features: This tool is used to attribute nearest line features to a point feature class. Nearest line features such as road and trail provide context to the location of a feature.