The ACPF toolbox depends on having reliable, high-quality core data to deliver effective results. If you have built your own core data using the ACPF Utilities Tools, you can now upload it to the ACPF National Hub. This matters most in watersheds where the ACPF does not yet have core data. Your contribution fills critical gaps and makes the national dataset stronger for everyone.
Note: The core data file geodatabases do not contain DEM data. Also, there is a separate portal to Submit ACPF Results to the ACPF National Hub.
How to Submit Your Data For Upload
We ask that the core data you submit to the ACPF National Hub meet the following conditions. We also ask that you follow one of the two suggested methods. If you need a zipping utility, we recommend the free 7-Zip software.
Method 1: Individual Zip Files - one per HUC12 watershed
Please submit a zip file, zip or .7z, named acpf and the HUC12 code (e.g., acpf040101020301). This zip file should contain the following:
- A polygon feature class containing the field boundaries named FB and the HUC12 code (e.g., FB040101020301).
- A polygon feature class containing a buffer of 1,000 meters from the watershed border and the field boundaries layer (requires a Union) named buf and the HUC12 code (e.g., buf040101020301).
- A polygon feature class containing the HUC boundary named bnd and the HUC12 code (e.g., bnd040101020301).
Method 2: One Zip File - containing many unzipped .gdb or many zipped .gdb
One zip file, .zip or .7z, with a name that DOES NOT start with acpf. This zip file should contain the following for each unzipped .gdb:
- Each geodatabase with the acpf HUC12 name (e.g., acpf040101020301). Within this geodatabase should be the following:
- A polygon feature class containing the field boundaries named FB and the HUC12 code (e.g., FB040101020301).
- A polygon feature class containing a buffer of 1,000 meters from the watershed border and the field boundaries layer (requires a Union) named buf and the HUC12 code (e.g., buf040101020301).
- A polygon feature class containing the HUC boundary named bnd and the HUC12 code (e.g., bnd040101020301).
- Or each individual HUC12 zip file follows the same three criteria as the individual geodatabase example above.
We also ask that you upload a text file (.txt) that contains your name, email, and organization in the following format:
- Full Name
- Organization
Once your data is in the correct format, you can submit it to the ACPF National Hub team via Box.
After You Submit Your Data
After your data have been submitted, you will receive a confirmation email. The ACPF National Hub Technical Team will review the datasets to ensure that field boundaries are reasonable and free of spatial irregularities (e.g., holes in the data, overlaps, or multipart polygons). If numerous irregularities are found, you may be asked to make revisions and resubmit. We will also overwrite any existing metadata with ACPF-standard metadata to ensure consistency across the national dataset.
The ACPF Hub Technical Team will periodically incorporate submitted core datasets into the national ACPF data collection. Once incorporated, these datasets will be openly accessible for public download through the ACPF Core Data Availability delivery process.
