The ACPF relies on high-quality core data in order for the toolbox to work effectively. The core data is the ACPF soil and land use data that currently exists for over 12,000 watersheds in Illinois, Iowa, Minnesota, Nebraska, Wisconsin, and parts of Indiana, Kansas, Michigan, Missouri, and Ohio.
ACPF users can create their own core data by using the ACPF Utilities Suite and can now upload newly created core data to the ACPF National Hub where it can be incorporated into the national dataset and shared widely for other ACPF users.
Please note – core data file geodatabases do not contain tool results or DEM data. There will be a separate portal for submitting ACPF results to the ACPF National Hub – more details coming soon!
HOW TO SUBMIT YOUR DATA FOR UPLOAD
We ask that 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 free 7zip.
- 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 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 field boundaries layer 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).
- Please submit a zip file, zip or .7z, named acpf and the HUC12 code (e.g. acpf040101020301). This zip should contain the following:
- One Zip File – containing many unzipped fgdb or many zipped fgdb
- One zip file, .zip or .7z, with a name that DOES NOT start with acpf. This zip should contain the following for each unzipped fgdb:
- 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 field boundaries layer 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 following the same three criteria as the individual geodatabase example above.
- Each geodatabase with the acpf HUC12 name (e.g. acpf040101020301). Within this geodatabase should be the following:
- One zip file, .zip or .7z, with a name that DOES NOT start with acpf. This zip should contain the following for each unzipped fgdb:
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. ACPF National Hub Technical Team staff will evaluate the dataset(s) to make sure that the field boundaries are reasonable and do not contain any spatial irregularities (e.g. holes in the data, overlaps, or multi-part polygons). Staff will also verify that tabular data is valid; if there are many irregularities, we may ask you to make changes and resubmit. Once the data have been verified and meet our requirements, we will update the soils and land use files within the geodatabase. We will also overwrite any existing metadata with ACPF standard metadata so there is consistency within the national datasets.
The ACPF Hub Technical Team will periodically incorporate submitted core datasets to the national data collection, which will then be available for download via the ACPF core data delivery application portal. As a result of this, please be aware that data submitted to the ACPF team will be made publicly available.