NNLSC - DatabaseReferenceGuideV1 6jan2009

1
Version
Blackland Research Center
NNLSCDatabase
ReferenceGuide
TEXAS AGRILIFE RESEARCH - BLACKLAND RESEARCH CENTER
National Nutrient Loss & Soil Carbon Database
Steven R. Potter
Address questions or comments to the authors at:

Blackland Research Center
708 E. Blackland Rd
Temple, TX 76502
Phone 254.774.6038 • Fax 254.774.6001
spotter@brc.tamus.edu
Texas AgriLife Research 2008
Results from the National Nutrient Loss and Soil Carbon (NNLSC)
database distributed on the accompanying DVD have been published
by Potter et al. (2006) in Model Simulation of Soil Loss, Nutrient Loss,
and Change in Soil Organic Carbon Associated with Crop Production,
available online at URL:
http://www.nrcs.usda.gov/technical/nri/ceap/croplandreport/
That report supplements the information provided here.
Acknowledgements
This work was done under cooperative agreements between the U.S. Department of
Agriculture, Natural Resource Conservation Service, Resource Inventory and Assessment
Division and the Texas Agricultural Experiment Station, Blackland Research and Extension
Center, Temple, TX.
The National Nutrient Loss and Soil Carbon (NNLSC) database project was a team effort
involving many talented and dedicated people. Although not listed as authors, this work
would not have been possible without the sustained commitment and effort of many
individuals.
The technical knowledge, advice, and team-building skills unselfishly shared by Jerry
Lemunyon, NRCS, played a vital role in the project from its inception. Likewise, the
project greatly benefitted from the technical contributions of Lee Norfleet, NRCS. Jerry’s
and Lee’s thinking and contributions are infused throughout this work.
Theresa Pitts, TAES, programmed the modeling system, conducted the model runs, and
handled so many details with a competence that is inspiring. Jimmy Williams, TAES,
provided technical assistance on how to properly set up EPIC to make the model runs and
made revisions to the EPIC model specifically for this study. Todd Campbell, ISU CARD,
provided programming support for I–EPIC throughout the project. Joaquin Sanabria,
formerly TAES, assisted with the development of the soil and climate clustering procedure.
Bill Effland (NRCS) and Terry Sobecki (formerly NRCS) also contributed to the project.
The idea for this project predates the lead author’s involvement. Two people in particular
provided the creative spark: Don Goss, TAES, and Robert Kellogg, NRCS. Don was the
original principal investigator (instigator) before he passed away in November, 2001. Bob is
still with us; cogitating, counseling, and cajoling. His knowledge, energy, and attention to
detail proved invaluable in completing this work.
Particular acknowledgements are extended to Jay Atwood, NRCS, for his leadership and
direct involvement in all phases of the project over a period lasting many years. For much
of the project, Jay organized and led the day-to-day effort, formulated and conducted
various analyses, and wrote large sections of the reports we put out over the past several
years. It was Jay who attended to the constant myriad of details evoked by the dynamic
nature of the project. We would never have completed our work without him.
We are grateful to our many colleagues at TAES, the NRCS and elsewhere who generously
shared their knowledge and time. We remain indebted to the managers and leaders who
supported this project including: Tom Gerik, Director, Blackland Research and Extension
Center, TAES; Bill Dugas, former Director, Blackland Research and Extension Center,
TAES; Wayne Maresch, Director, Resources Inventory and Assessment Division, NRCS;
Maury Mausbach, former Deputy Chief for Soil Survey and Resource Assessment, NRCS;
and Bill Puckett, Deputy Chief for Soil Survey and Resource Assessment, NRCS.
Table of Contents
Acknowledgements ii STAT Examples 57

Chapter 1: What is the NNLSC? 1 Example 1: Basic Query functions: Group By, Count,
Sum, Expression, and Where query functions 57
The 97 NRI Microsimulation Model 1
Example 2: NRI Aggregation and Macros 60
Simulation Domain 2
Example 3: Probability Analysis 62
The Library of Runs 5
Example 4. Comparative Analysis of Functional
Chapter 2: What data are in the NNLSC? 7
Observation Groups 67
Specific data products distributed in the database 7
References 70
Baseline and Alternative Datasets 8
Appendix A 71
NNLSC Tables and Table Types 8
Microsimulation Modeling Approach 71
Data Tables 8
More on the NRI Microsimulation Domain 71
Relationships Between Datasets 9
Example illustrating method for applying weights and
Relationships Between Dataset Tables 9 aggregating estimates. 72
InSitu Table & Field Detail 13 Overview of the Modeling System and the Scheme for
Making Multiple Model Runs 76
URU ‐ Cropshare – Point Tables & Field Detail 14
RunBuilder 76
Support Tables & Field Detail 14
Model Run Database Tables Populated by RunBuilder
Relationships between Data and Support Tables 15 76
Management Weights Associated with the NNLSC 16 Tables Used by RunBuilder 77
Electronic Metadata in the NNLSC 17 The RunBuilder Process 79
Chapter 3:Table Metadata & Relational Diagrams 19 The i_EPIC Interface 80
Metadata Tables 20 The EPIC Model 82
Relationship Figures 42 Monthly weather and wind statistics 83
Chapter 4: STAT – the Status Trends Analysis Tool 51 Appendix B 84
Installing the NNLSC Database 52 Derivation of Tillage Probabilities 84
Retrieving NNLSC Data 52 Appendix C 85
Methods of Analysis 53 Model and Database Project Information Sheet 85

Tables
Table 1. The two datasets included in the NNLSC. 8 Table 24. defNutRate Metadata 35
Table 2. Tables contained in the NNLSC database. 9 Table 25. defNutTime Metadata 35
Table 3. Primary and foreign keys in the NNLSC tables. 11 Table 26. defManureCategory Metadata 36
Table 4. 97bcr_InSitu Metadata 20 Table 27. defLandUse Metadata 36
Table 5. 97NoCP_InSitu Metadata 22 Table 28. defNRI_LandUse Metadata 36
Table 6. 97bcr_URU Metadata 24 Table 29. defMoisture Metadata 36
Table 7. 97NoCP_URU Metadata 25 Table 30. defTemperature Metadata 36
Table 8. 97bcr_Cropshare Metadata 26 Table 31. defSlopeClass Metadata 36
Table 9. 97NoCP_Cropshare Metadata 27 Table 32. defSoilClass Metadata 37
Table 10. 97bcr_Point Metadata 28 Table 33. defSoilHydroGroup Metadata 37
Table 11. 97NoCP_Point Metadata 29 Table 34. defSoilTxtGrps Metadata 37
Table 12. attribURU Metadata 29 Table 35. Key relationships in NNLSC tables. 38
Table 13. attribPoint Metadata 30 Table 36. Management weights associated with the
Table 14. charClimate Metadata 31 NNLSC datasets. 41
Table 15. charClimClusClass Metadata 31 Table 37. wtsCountyTillage Metadata 41
Table 16. charWeatherStation Metadata 32 Table 38. wtsUruTillProps Metadata 41
Table 17. charCrops Metadata 32 Table 39. wtsNutrientApplications Metadata. 41
Table 18. charSoils Metadata 33 Table 40. wtsManureCategory Metadata 41
Table 19. defStates Metadata 34 Table 41. Which data table to use? 60
Table 20. defNnlscRegions Metadata 35 Table 42. Definitions of the probability‐type fields in the
InSitu table. 63
Table 21. defTillage Metadata 35
Table 43. Supplementary queries. 69
Table 22. defIrrigationCode Metadata 35
Table 23. defConserPract Metadata 35

Figures
Figure 1. Organizational scheme for the modeling system domain.
Figure 2. Overview of the 97NRI Microsimulation Modeling System.
Figure 3. Structure and relationships among the 8 data tables comprising the two datasets.
Figure 4. Relationships between 97bcr_InSitu data table and the attribute, characteristic and definition tables.
Figure 5. Relationships between 97NoCP_InSitu data table and the attribute, characteristic and definition tables.
Figure 6. Relationships between 97bcr_URU data table and the attribute, characteristic and definition tables.
Figure 7. Relationships between 97NoCP_URU data table and the attribute, characteristic and definition tables.
Figure 8. Relationships between 97bcr_Cropshare data table and the attribute, characteristic and definition tables.
Figure 9. Relationships between 97NoCP_Cropshare data table and the attribute, characteristic and definition tables.
Figure 10. Relationships between 97bcr_Point data table and the attribute, characteristic and definition tables.
Figure 11. Relationships between 97NoCP_Point data table and the attribute, characteristic and definition tables.
Figure 12. Microsimulation model from an analysis point of view
1
Chapter
N U T R I E N T L O S S D A T A B A S E R E F E R E N C E
Chapter1: What is the NNLSC?

The terms "National Nutrient Loss & Soil Carbon Database",
"NNLSC", and the "nutrient loss database" are all used
interchangeably to describe the database application on the
accompanying DVD…
T
he nutrient loss database is a catalog of databases and tools developed to aid
our understanding of physical processes occurring on U.S cropland. It
contains land use and management patterns, site characteristics, and estimates
of water and nutrient cycling, soil loss, nutrient loss, and the change in soil
organic carbon over time for hundreds of thousands of cropland situations. Because it
combines the diversity of the natural resources employed in agriculture with the variety
of management practices in use, the nutrient loss database is a powerful aid in
evaluating the relationships between agricultural practices and the resulting impacts
upon carbon, nitrogen, and phosphorus fluxes.
The database has been used to assess the status and trends of resource conditions on
approximately 298 million acres of U.S. cropland for regional and national analyses. In
a 2006 study, the NNLSC was analyzed to identify cropland areas that would benefit
most from the application of conservation practices (Potter et al., 2006). In an earlier
version, the data were successfully linked to the economic Agricultural Sector Model
(McCarl, et al., 1993) to provide combined economic and environmental analysis
products for a USDA appraisal of conservation alternatives for the Resources
Conservation Act Appraisal (USDA, 2001). NNLSC data have been used as inputs to
economic, watershed, and eutrophication models. It has also been used to evaluate the
‘what if’ effects of conservation program/policy scenarios. A similarly constructed
database was developed to provide estimates of carbon sequestration for the
Consortium for Agricultural Soils Mitigation of Greenhouse Gases (CASMGS) study.
The source of the NNLSC is the 97NRI Microsimulation Model.
The 97 NRI The microsimulation model developed to create the nutrient loss
Microsimulation database was based on the 1997 National Resource Inventory1
Model (NRI); a stratified random sample used for surveying natural
1 USDA-NRCS (2000). For more information on the NRI, see www.nrcs.usda.gov/technical/NRI/.
1
resource characteristics across the U.S. Model inputs include nutrient management
data from the Cropping Practice Survey (CPS) and Area Studies (USDA-ERS, 2000;
2001); locations and extent of crops, land management, and conservation practices
from the NRI; soils data from the Map Unit Interpretation Record2 ; and monthly
climate statistics. These datasets were extremely large, and consequently they were
reduced into manageable amounts using statistical clustering techniques; generic tillage
and irrigation scheduling; and regional, State, and sub-State averaging. The modeling
system includes statistical weights, transposed into occurrence probabilities, of land use,
site characteristics, fertilizer management, and tillage practices.
Simulation The modeling domain is a subset of the 1997 NRI sample. It includes NRI sample
Domain points with the following crops: corn, soybeans, wheat, cotton, barley, sorghum, rice,
potatoes, oats, peanuts, legume hay, and grass hay. All areas east of the Rocky
Mountains and the major cropping areas in the western U.S. were included as shown in
the map below. The western areas were delineated by the 6-digit hydrologic cataloging
unit (HUC); 19 6-digit HUCs were selected to represent cropland in the West. Hawaii,
Alaska, and U.S. territories were not included. This coverage accounts for
approximately 298.5 million acres, representing about 79 percent of the 377 million
acres of cropland in the US. The total number of NRI sample points in the domain
was 178,567.
To account for
management
factors, we
disaggregated
NRI corn
acres into corn
for grain and
corn for silage,
and NRI
wheat acres
into winter
wheat and
spring wheat.
County
proportions
for each crop
were obtained
from the 1997
Census of
Agriculture. Using this proportion, corn sample points were split into corn for grain
2 No longer available. Refer to http://soildatamart.nrcs.usda.gov/ for official tabular soil data.
2
and corn for silage points and wheat points were split into winter wheat and spring
wheat points. Each split point was accredited with a proportional share of the NRI
expansion factor (100-acre unit statistical weight). Conversely, we assumed NRI acres
for Hay/Legume (NRI Land Use 142) and Hay/Legume-Grass (NRI Land Use 143)
would be manage as legume hay. Therefore these points and their expansion factors
were combined into a single point. These procedures resulted in 222,358 “cropshare”
points.
Using NRI data, sample points were categorized according to state, crop, climate
cluster3 , soil cluster, one of three irrigation types including no irrigation, and one of 8
combinations of three conservation practices (contour farming, strip farming, and
terraces) including no practices. Each combination constitutes a Unique Resource Unit
(URU). On average, a URU represents 7 NRI sample points, with a maximum of 830
sample points in the largest URU. The acreage representation of each URU is the sum
of the expansion factors (xfact unit is 100 acres) for the NRI points corresponding to
the URU. URUs with less than 1,000 acres were discarded because model simulation of
these small areas contribute little variance to the overall assessment; the corresponding
NRI sample points were excluded from the sample domain. These procedures resulted
in 25,250 Unique Resource Units.
For modeling purposes, each URU is treated as a single homogeneous farm field.
Several model runs are made for each URU, representing different tillage systems,
different commercial fertilizer application schemes, and two types of manure
applications4 . More model runs were conducted for URUs with a diverse collection of
tillage and nutrient application possibilities than URUs with less diversity. Some crops,
for example, have more tillage and nutrient application possibilities than other crops,
and these can also vary for a given crop by region of the country. On average, 30
model runs were made for each URU to represent the various tillage, commercial
fertilizer application, and manure application options. These procedures resulted in
768,785 model runs.
3 A statistical clustering procedure was used to group NRI cropland points according to similar soil attributes
and then selecting a single set of soil attributes to represent each group of points. A similar procedure was
developed for climates. For more info on the climate and soil clustering procedures see Model Simulation of Soil
Loss, Nutrient Loss, and Change in Soil Organic Carbon Associated with Crop Production.
4 The probabilities that a particular management option applies to a URU (and the associated NRI sample
points) were estimated based on the frequency of occurrence of each option obtained from national-level
databases. For the three tillage options, probabilities were derived from the Crop Residue Management
Survey; a county-level database that reports the acres for each tillage type by crop (CTIC, 2001). The
probabilities for the commercial fertilizer application options were derived from the Cropping Practices
Survey (USDA-ERS, 2000; 2001) data by state and crop, and were based on the number of observations (i.e.,
farmers surveyed) associated with each of the selected possibilities. The percentage of acres with manure
applied as derived from the 1997 Census of Agriculture (USDA-NASS, 1999) were used as the probabilities
for options with manure applications, calculated for each state and climate zone combination. The probability
that the manure was applied on a manure producing farm or on a manure receiving farm was obtained from
the same source. For more information see Model Simulation of Soil Loss, Nutrient Loss, and Change in Soil Organic
Carbon Associated with Crop Production.
3
Area extents of the statistically clustered climate zones.
178,567 NRI Points in the Domain
Using county proportions in 1997 Census of Agriculture:
Split corn points (NRI Land Use 11) into corn for grain and corn for silage points
Split wheat points (111) into winter wheat and spring wheat points
Combine hay/legume (142) and hay/legume‐grass (143) points into legume hay point
|
222,358 Cropshare Points
Climate Cluster (66 climate zones)
Soil Clusters (2,688 soils, with 5,887 soil‐climate combinations)
State (48 states, with 6,043 state‐soil‐climate combinations)
Crop (14 crops)
Irrigation system (sprinkler, furrow, no irrigation)
Three conservation practices (8 combinations)
|
25,250 Unique Resource Units
Tillage system (3 types)
Commercial fertilizer application
Manure application
|
768,785 model runs
Figure 1. Organizational scheme for modeling the baseline domain.
4
After assembling the input data, three software programs were used in making the
model runs: RunBuilder (Appendix A), I_EPIC (Campbell, 2005) and EPIC
(Izaurralde et al., 2006; Williams, 1995; Williams et al., 1984).
1. The Visual Basic program, “RunBuilder”, combines the input data into
individual model runs, assigns dates to field management operations via plant
heat unit scheduling, and stores the runs and the associated datasets in a
relational database.
2. The I_EPIC software provides an interface between the relational database
and the EPIC model. I_EPIC controls the model input and output data and
automates large numbers of model runs in a Windows environment.
3. The EPIC biophysical model (version 0360) is a daily time step model that
simulates agricultural production systems, soil and water resources, and
environmental impacts. Major components of the model include weather
simulation, hydrology, erosion-sedimentation, nutrient cycling, pesticide fate,
plant growth, soil temperature, tillage, and plant environmental control.
In the modeling phase, 40-year runs using probabilistically generated weather were
made for 1997 conditions. Only the final 30 years of simulation results were stored for
each model run as the first 10 years were used for equilibration. Over 20 million
cropping years were simulated for the baseline domain. These results and the model
inputs data were stored in the Library of Runs.
The NNLSC was created from data in the Library of Runs. The
The Library of Runs
Library serves as a data warehouse for storing and organizing
EPIC model inputs and outputs for approximately 1.4 million
individual model runs produced using the 97NRI microsimulation model. Four
Microsimulation datasets5 stored in the library are:
1. 97NRI Baseline Cropland Results
2. 97NRI No Conservation Practice Alternative
3. 97NRI Baseline Pasture Results
4. Comprehensive Nutrient Management Plan Alternative
Stored data includes model inputs; yearly output from the model; summaries and
derivations of the model output; categorization and definition variables; management
probabilities and statistical weights; and information for converting data types and
units. Companion data including soil and topography characteristics, climate data,
landscape features and land use classifications, commercial and manure fertilizer inputs,
and information on applied conservation practices are stored in the Library. Links to
the NRI attribute database allow analysis of the simulation results across categorization
variables including highly erodible lands, land capability class, and other classifications.
5 Only the 97NRI Baseline Cropland Results and 97NRI No Conservation Practice Alternative datasets are
released on the accompanying data DVD. The 97NRI Baseline Pasture Results and Comprehensive Nutrient
Management Plan Alternative datasets are unpublished. Possibly, those datasets could be made available
under special arrangements.
5
The Library contains 40+ million rows of data, maintained in approximately 70

Microsoft Access databases requiring nearly 50 gigabytes storage.
To improve data access response time, derived or summary data tables are created for
frequently retrieved data. Some of these tables are contained within each of the model
run databases, which are managed using Visual Basic programs to perform operations
on each database sequentially. In other cases, summary data tables reside in a central
“hub” database. Hubs function as data marts; i.e. data from multiple databases are fed
into a single hub which then provides a common data distribution point for specific
analytical applications. Either within a hub or in external database application, data
processing programs, SQL6 queries, and macros convert units, summarize data, and
produce the datasets needed for analysis.
Figure 2. Overview of the 97NRI Microsimulation Modeling System

The microsimulation modeling system relates thousands of EPIC field‐scale model runs into a national framework
based on the 1997 National Resource Inventory (NRI). 1a. Point data from NRI, soil and climate data, and management
data from national‐level surveys are gathered and then reduced using statistical models and clustering techniques. 1b.
Management occurrence probabilities and weights representing homogeneous areas are derived. 2. Based on
specifically developed rules, the Visual Basic program “RunBuider” builds and stores in relational databases, thousands
of EPIC model input sets, each set representing a unique combination of geographic, environmental, and management
circumstances. 3. Water and carbon cycles, soil loss, and nutrient exports are estimated with the EPIC biophysical
model using the I_EPIC software to automate the runs and manage the output data. 4. Data from the completed model
runs are maintained in the Library of Runs. 5 & 6. Data are extracted from the Library and estimated effects are
aggregated to the watershed, region or national levels using probabilities and weights. 7. Estimated effects can be
reported in various ways or further analyzed using database, statistical, or GIS methods.
6 Structured Query Language
6
2
Chapter
Chapter2: What data are in the NNLSC?

Understanding the database, its structure and relationships, is the
foundation needed for using the National Nutrient Loss & Soil
Carbon Database…
The application distributed on the
S T Y L E E X P L A N A T I O N
accompanying DVD consists of two
Bold Caps: Access database file names Microsoft Access database files organized in
NNLSC_DATA.mdb or DATA a front end – back end configuration. The
front-end database holds the application
Italicized Bold: Full/Partial Table Names
programming and the back-end stores the
97bcr_InSitu or InSitu data. In the NNLSC, the database
application programming such as queries, temporary tables, reports, macros, or Visual
Basic code are stored in the Access database file NNLSC_STAT.mdb, also referred to
as STAT (short for Status Trends Analysis Tool7 ). Data, attribute, characteristic,
definition, and statistical weight tables are stored in NNLSC_DATA.mdb, also
referred to as DATA. Tables from DATA are linked into STAT, which serves as a
user interface to the data.
Specific data products distributed in the database
DATA and STAT include:
‐ 97NRI Microsimulation Model results from the Library of Runs
97 Baseline Cropland Results Dataset (97bcr)
97 No Conservation Practice Alternative Dataset (97NoCP)
‐ Attribute, characterization, and definition data which describe the environmental
and management conditions represented in the datasets.
‐ Probability weights for estimating the occurrence frequency of management
practices (tillage, chemical fertilizer application, and manure application)
represented in the data.
‐ Analytical methods and examples for viewing, querying, processing, and
manipulating the data.
7 Chapter 4 provides more information about the Status Trends Analysis Tool.
7
Baseline and The nutrient loss database includes results for two sets of national simulations: the
Alternative 1997 Baseline Cropland Results (97bcr) and the 1997 No Conservation Practice
Datasets Alternative (97NoCP). A comparison of the two datasets is provided in table 1. The
dataset 97bcr provides estimates of the biophysical processes occurring on 298 million
acres; approximately 80% of U.S. cropland acres. The second, 97NoCP, provides an
alternative view, without conservation practices, for the 31.7 million acre subset of
97bcr that had contours, strip cropping, and/or terraces in that analysis.
Table 1. The two datasets included in the NNLSC.

Dataset Name 1997 Baseline Cropland Results 1997 No Conservation Practice Alternative
Dataset ID 81404 40905
AlphaNumCode 97_NNLSC_BCR 97_NNLSC_NoCP
ShortCode 97bcr 97NoCP
Date August 2004 April 2006
97bcr provides estimates of the biophysical 97NoCP provides a no conservation practice
processes occurring on U.S. cropland using the alternative for the 97bcr model runs having contours,
1997 NRI cropland points (approx. 80% of U.S. strip cropping, and/or terraces. The absence of
cropland). Data reduction using soil and climate practices was simulated by increasing the runoff
clustering. Tillage and nutrient management curve number and setting the P factor to 1. Effects on
Dataset Description applied using an "all combinations" approach. wind erosion were not simulated. The 97NoCPInStu
Simulation model includes NRI xfact and statistical table includes a field with the associated 97bcr run
weights derived from Cropping Practice Survey IDs. IMPORTANT NOTE: Both datasets have the
(commercial fertilizer), Census of Agriculture same URU, Cropshare, and NRI point IDs for the
(manure), and Crop Residue Management Survey subset occurring in both.
(tillage).
Counts
Model Runs 768,785 183,074
URUs 25,250 4658
Cropshare Points 222,358 19,229
NRI Points 178,567 17,401
Coverage (acres) 298,478,000 31,736,600
NNLSC Tables The Access file DATA, nearly 1 gigabyte in size, contains about 40 tables as
and Table Types described below in table 2. Eight are data tables, which contain the model outputs
and simulation results for the 97bcr and 97NoCP datasets. Others are supporting
tables. Most contain categorization or other variables useful in data analysis. Two
are attribute tables, identified by the attrib prefix, which further define records in
the data tables. Identified with the char prefix, the five characteristic tables
contain location details, climate data, crop information, and soil properties. Sixteen
definition tables, identified with the def prefix, mainly contain category
definitions, usually with an easy to interpret category name. Probabilities for the
occurrence of tillage and nutrient management operations are provided in the four
tables named using the wts prefix
Data Tables Understanding the structure and relationships of the data tables provides the
foundation for analyzing the NNLSC. The relationship diagram in figure 3 provides a
visual reference of the fields and relationships between the data tables. Four data tables
hold the model output and simulation estimates for the 97 Baseline Cropland Results
and are identified by “97bcr” preceding the underscore ( _ ) in the table name.
Another four, identified by the prefix “97NoCP”, contain the equivalent for the 97 No
Conservation Practices alternative. Name segments following the underscore indicate
the aggregation level or perspective of the table data. InSitu (“in place”) contains
8
disaggregate, unweighted (“raw”) EPIC model outputs, mainly average annual values.
Raw model outputs processed through the microsimulation model and imputed to the
unique resource unit (URU), NRI Cropshare point, and NRI point are stored in the
URU, Cropshare, and Point tables.
Relationships The four tables on the right (8 boxes in figure 38 ) contain the 97
Between Datasets Baseline Cropland Results dataset and four left-most tables
contain the 97 No Conservation Practice dataset. Lines between
tables denote table fields comprising primary to foreign key relationships. One to one
relationships (indicated by 1—1) are shown linking equivalent tables across the two
datasets. (One to one relationships between the two Cropshares and two Point tables
exist, but are not shown.) In a one to one relationship each record in one table can
have only one matching record in the linked table. For example, each record in
97NoCP_InSitu is matched to one record in 97bcr_InSitu. (Note the reverse is not
true. Many records in 97bcr_InSitu do not have a matching record in
97NoCP_InSitu because the No Conservation Practices dataset was created as a
subset of the 97 Baseline Cropland Results dataset.)
Relationships For one-to-many relationships (1—00 or 00—1) a record in one

Between Dataset table (1) can have one or more matching records in the second
Tables table (00). In figure 3, the one to many relationship is only
present among data tables within each dataset, demonstrating the relationship between
InSitu, URU, Cropshare, and Point records. For example, the figure shows many
records in 97bcr_InSitu are related to a single record (a single URU) in 97bcr_URU.
In effect, the diagram helps illustrate that 25,250 URUs were expanded into 768,785
unique model runs and conversely, that 768,785 model outcomes are aggregated into
25,250 URU simulation results. It further shows a single URU in 97bcr_URU is
related to many records (cropshare points) in 97bcr_Cropshare resulting from the
statistical clustering of multiple cropshare points into fewer number of URUs. Finally,
multiple records in 97bcr_Cropshare shown to be related to a single record in
97bcr_Point which resulted from splitting single wheat and corn NRI points into
spring and winter wheat points and corn silage and corn for grain points9 .
Relationships within the No Conservation Practice dataset are identical to those
described for the baseline dataset.
Primary and important foreign key fields for the data tables are listed in table 3.
Key fields are used to link related tables together. Field names in the different
tables should be the same when they represent the same piece of information.
Table 2. Tables contained in the NNLSC database.
8 When the table field list stretched longer than the screen, a 2nd copy placed next to the first one was placed
into the diagram.

9 Not shown is a secondary relationship in which a single legume hay record in Cropshare is inputed to
hay/legume and hay/legume-grass NRI points. Combined, the two relationships make a complex many to
many relationship.
9
10
Table Name Table Description
97 Baseline Cropland Results; one row for each simulation includes all categorization
97bcr_InSitu
variables, weights, acres, and average annual (or delta) outputs.
97 No Conservation Practices dataset; one row for each simulation includes
97NoCP_InSitu
categorization variables, weights, acres, and average annual (or delta) outputs.
97 Baseline Cropland Results weighted and aggregated to Unique Resource Unit (URU)
97bcr_URU
(state, crop, climate, soil, dry‐irr, conservation practice).
97 No Conservation Practices dataset weighted and aggregated to Unique Resource Units
97NoCP_URU
(URU).
97 Baseline Cropland Results aggregated and attached to expanded NRI points (corn and
97bcr_Cropshare
wheat points split into cropshare points).
97 No Conservation Practices dataset aggregated and attached to expanded NRI points
97NoCP_Cropshare
(corn and wheat points split into cropshare points).
97bcr_Point 97 Baseline Cropland Results aggregated and attached to NRI points
97NoCP_Point 97 No Conservation Practices dataset aggregated and attached to NRI points
Categorical variables & descriptions of environmental conditions for each Unique
attribURU
Resource Unit.
attribPoint Selected publicly available NRI attributes for the NNLSC‐NRI domain.
charClimate Average monthly climate statistics for each climate cluster weather station.
Climate characteristics, area, and baseline average annual hydrologic cycle estimates for
charClimClusClass
each climate cluster.
charWeatherStation General information for each climate cluster weather station.
charCrops Crop growth parameters used in NNLSC‐EPIC3060 model. Crop yield conversion factors.
charSoils Selected soil properties for soil clusters.
defStates State names, codes, abbreviations, and CTIC regions.
defNnlscRegions 8‐digit watersheds comprising the 6 NNLSC regions.
defTillage Tillage names & codes.
defIrrigationCode Irrigation codes & descriptions.
defConserPract Conservation practice codes & descriptions.
defNutRate Nutrient application rate codes & descriptions.
defNutTime Nutrient application timing codes & descriptions.
defManureCategory Manure application categories codes & descriptions.
defLandUse Land use categories for each crop.
defNRI_LandUse NRI land use descriptions.
defMoisture Moisture class codes and definitions
defTemperature Temperature class codes and definitions.
defSlopeClass Slope class codes & descriptions.
defSoilClass Soil HSG‐Texture categories & descriptions.
defSoilHydroGroup Hydrologic soil group codes, definitions, relative ranking of runoff and percolation.
Relates 27 soil texture groups and 7 texture subgroup. Define SQI factor for each
defSoilTxtGrps
subgroup.
Tillage category weights by County, Crop, and Irrigation as derived from CRMS. This table
wtsCountyTillage
is the source for wtsUruTillProps table, which was used in the aggregation processes.
Tillage category weights for each URU. (Note: Due to array size of 97brc_InSitu x
wtsUruTillProps wtsURUTillProp, data in 97brc_InSitu were processed for each tillage category
separately.)
wtsNutrientApplications Nutrient application category weights.
wtsManureCategory Manure category weights.
10Tables with 97bcr or 97NoCP prefix contain baseline and no conservation practice data
respectively. Tables with the attrib, char, def, or wts contain attributes, characteristics,
definitions, and weights.
10
Table 3. Primary and foreign keys in the NNLSC tables.

Table Name Primary Key (PK) Foreign Key (FK)
97bcr_InSitu ID URUid; others
97NoCP_InSitu ID 97bcr_InSitu.ID; URUid; others
97bcr_URU URUid
97NoCP_URU URUid
97bcr_Cropshare recid + Crop URUid; others
97NoCP_Cropshare recid + Crop URUid; others
97bcr_Point recid
97NoCP_Point recid
StateFIPS, ClimateCluster, SoilCluster, IrrigationCode,
attribURU URUid, URU
ConserPract, YldClass
FIPS, StateFIPS, ClimateCluster, SoilCluster, IrrigationCode,
attribPoint RecId, NriPoint
ConserPract, HUC, NRI_LU
charClimate MonthlyWS ClimateCluster
charClimClusClass ClimateCluster WSID, Tclass, Mclass, Cclass
charWeatherStation WsId ClimateCluster, Mclass, Tclass, Cclass
charCrops CropId none
charSoils SoilCluster TxtID, Texture Group TxtGrp, HSG, SoilClass, HydroClass
defStates StateFIPS CTIC Region
defNnlscRegions Region ClimateCluster, HUC
defTillage Tillage none
defIrrigationCode IrrigationCode IrrigateClass
defConserPract ConserPract none
defNutRate Nrate none
defNutTime Ntime none
defManureCategory ManureCategory none
defLandUse CropId Broad Land Use, NRI_LU
defNRI_LandUse NRI_LU none
defMoisture Mclass none
defTemperature Tclass none
defSlopeClass SlopeClass none
defSoilClass HydroClass, SoilClass HSG
defSoilHydroGroup HSG none
TextureID,
defSoilTxtGrps none
TextureName
wtsCountyTillage CntyTillWt FIPS, CropID, IrrigateClass
wtsUruTillProps UruTillWt URUid, Tillage
wtsNutrientApplications NutWt StateFIPS, CropID, ManCat, RateCat, TimeCat, AppCat
wtsManureCategory ManWT StateFIPS, ClimateCluster, CropID, YldClass, ManureCategory
11
N U T R I E N T
L O S S
D A T A B A S E
12
R E F E R E N C E
Figure 3. Structure and relationships among the 8 data tables comprising the two datasets. The four tables on the left (dashed line
box) contain the 97 Baseline Cropland Results dataset and the four on the right (solid line box) contain the 97 No Conservation
Practice dataset. Relationships are shown with connecting lines.
The aggregation levels represented in InSitu, URU, Cropshare, and Point tables
provide 4 different aggregation perspectives of the cropland processes (defined in
following paragraphs). These differences are not a function of different source data,
rather, the perspective changes as contextual information is added to or removed from
the original source data. In essence, what differs is the contextual lens through which
the processes are viewed. It’s critical to select the table that best matches the analytical
question. For example, if the analytical question involved an experimental design or
data mining analysis, using the InSitu data table might be best choice since it
encapsulates environmental outcomes from an array of management situations
associated with the widest range of explanatory data sources. Conversely, without
applying weights to the associated model estimates in each data row, InSitu does not
provide expected or real-world estimates.
InSitu Table & Each row in the InSitu tables11 is a distinct cropland situation,
Field Detail described by a unique set of categorical variables. 97bcr_InSitu
contains 768,758 records. 97NoCP_InSitu contains information
for the 183K model runs made to represent the absence of conservation practices for
those situations in the baseline which were simulated with practices. It contains one
record for each situation covered in the NNLSC cropland baseline.
As shown by the metadata in tables 4 and 5, the InSitu tables contain several types of
data. The field “ID” is the primary key, a unique identification number assigned to
every model run. IDs in 97bcr_InSitu range from 250000001 to 251040130, whereas
IDs in 97NoCP_InSitu range from 280000001 to 281039857. One additional
variable, the corresponding baseline model run ID, is written into the field “97brcID”
in 97NoCP_InSitu. Using this field to relate the two InSitu tables facilitates analyses
and sets up comparisons between the baseline and the no practice scenario. An
example in Chapter 3 illustrates the method for substituting the runs from the no
practice alternative for the baseline runs.
InSitu tables contain summarized model outputs (usually average annual estimates,
although in some cases the estimates represent initial values, final values, or change
over the simulation period) of water and nutrient cycling, management inputs, crop
yield, soil and nutrient losses, and soil carbon status
The InSitu tables contain an assortment of categorical variables including StateFIPS,

CropID, ClimateCluster, SoilCluster, IrrigationCode, ConserPract, Tillage,
ManureCategory, YldClass, NutrientRateCategory, ApplicationTiming,
ApplicationCategory, NRI_LU, and SlopeClass. Linked to the attribute, characteristic,
and definition tables; these variables describe the major properties of the cropland
situations in each data row by defining the land use, management, and site
11Metadata definitions describing 97bcr_InSitu and 97NoCP_InSitu fields are provided in Chapter 2, tables
4 and 5. Documentation includes general descriptions of each table, primary and foreign keys (PK and FK)
associated with each table, and specific information about the fields in each table. Field information includes
the field name and description, data type and size, whether the field is an index, and where applicable, per acre
units and total units are listed for most model outputs in the two rightmost columns.
13
characteristics. Relationships between InSitu tables and supporting tables are shown in
figures 4 and 5.
Also included in the InSitu tables are statistical weights associated with each cropland
situation as well as the estimated acreage each record represents. Calculated factors
include a national probability coefficient, derived from the statistical weights, which
serves as an estimate of the probability of a similar acre occurring. The statistical
weights and acreages are used to calculate the microsimulation estimates from the
model output. Note, for any related data row, the statistical weights are the same in
both InSitu tables. .
URU - Cropshare – Point URU tables contain simulated estimates aggregated to the URU level. The baseline
Tables & Field Detail table includes 25,250 data rows, each a URU, covering approximately 298.48 million
acres. The no practice scenario includes 4,658 URUs covering about 31.74 million
acres. Tables 6 and 7 provide field names, descriptions, and other metadata for
97brc_URU and 97NoCP_URU. In both tables, URUs are identified by URUid. In
contrast to the different IDs in the two InSitu tables, the URUid remains constant
between the 97brc_URU and the 97NoCP_URU tables. The table name and the
“Simulation” field distinguish the datasets. Relationship diagrams for the two URU
tables are provided in figures 6 and 7.
A data row in a Cropshare table contains the data for a unique “StateFIPS”,
“CropID”, “ClimateCluster”, “Soil Cluster”, “IrrigationCode”, and “ConserPractice”
populated from the URU table. The 97brc_Cropshare (table 8) contains 222,358 data
rows and the 97NoCP_Cropshare (table 9) 19,229 rows. For crops other than corn
and wheat, data for the cropshare point is exactly the same as for the NRI point. For
these points, the relationship between cropshare points and the NRI points in the
Point table was established using a the field “Recid”.
Cropshare data were populated in Point using the NRI key to establish the
relationship. The 222,358 cropshare points in 97bcr_Cropshare were reduced to
178,567 in 97bcr_Point (table 9) by aggreagating spring and winter wheat rows, corn
grain and silage rows and legume hay rows into hay/legume and hay/legume-grass
rows. The 19,229 cropshare points in 97NoCP_Cropshare were reduced to 17,401
NRI points in 97NoCP_Point (table 10). In all cases, the acres represented by 97bcr
and 97NoCP remained constant across data rows in URU, Cropshare, and Point.
tables.
Support Tables & The two attribute tables, attribURU and attribPoint, further define records in URU,
Field Detail Cropshare, and Point data tables. attribURU contains categorical variables and
descriptions of environmental conditions for each Unique Resource Unit. attribPoint
included extensive categorization variables as well as selected publicly available NRI
attributes for the NNLSC domain. For example, attribPoint includes classification
variables, such as land capability class and highly erodible class. Metadata definitions
describing attribURU and attribPoint fields are provided in tables 12 and 13.
14
Characteristic tables contain location details, climate data, crops information and soil
properties. Climate data used to drive the weather generator in the EPIC model are
provided in charClimate. Data includes monthly climate statistics of temperature,
precipitation, and wind. The characteristic table charClimClusClass, characteristics
for the climate cluster including area and baseline average annual hydrologic cycle
estimates. General information for each weather station is given in
charWeatherStation. Metadata definitions describing charClimate,
charClimClusClass, and charWeatherStation fields are provided in tables 14, 15,
and 16 respectively. Crop growth parameters used in the EPIC modeling are provided
in charCrops. The table charSoils lists selected soil properties (for example, percent
clay by soil layer) for the soil clusters used in the modeling. charSoils also includes
categorization variables such as soil hydrologic group and precipitation class. Tables 17
and 18 describe metadata defining describing the fields in the crop and soil
characteristic tables.
Table names beginning with def generally indicate tables containing category
definitions. Usually, the table contains an easy to interpret name category name, which
is more descriptive than category IDs contained in the data tables.
The table defStates contains state names, FIPS codes, abbreviations, and CTIC region.
defNnlscRegions lists the 8-digit HUC watersheds comprising the 6 NNLSC regions.
Metadata for these two definition tables are recorded in tables 18 and 19. defTillage,
defIrrigationCode, and defConserPract contain definitions tillage, irrigation, and
conservation practice codes. Metadata describing these definitions are found in tables
21, 22, and 23. Nutrient rate category, nutrient timing category, and manure category
definitions are provided in defNutRate, defNutTime, and defManureCategory.
Metadata describing these definitions are found in tables 24, 25, and 26.
The table defLandUse contains crop names and several land use categories types as
well as NASS, Ag Census, and CTIC crop names and codes. defNRI_LandUse list
the NRI land use name for each NRI land use code. Metadata describing these
definitions are found in tables 27 and 28. Two tables, defMoistureClass and
defTemperatureClass (metadata in tables 29 and 30) contain precipitation and
temperature class definitions. defSlopeClass (metadata in table 31) defines slope class
categories for slope ranges. Several soil category tables different texture and hydrologic
groupings are provided in and soil textures are provided defSoilClass,
defHydroSoilGroup, and defSoilTxtGrps. Metadata describing these definitions are
found in tables 32, 33, and 34.
Relationships Relationships between data and attribute, characteristic, and definition tables are
between Data predefined in the NNLSC. Joins between tables are automatically created when two
and Support tables are selected in the query builder. Table 35 identifies each matching keys between
Tables two tables. Matching keys are identified by matching a table and field under the “Key
A” across to a field and table under “Key B”. For example, examining the columns
under Key A in table 35 shows for 97bcr_InSitu, the foreign key “Crop” is related to
15
the primary key “Crop” in two tables; charCrops and defLandUse. This means that
not only is the value in the InSitu CropID field a property of each InSitu data row,
but so too are the properties of the identified Crop in charCrops and defLandUse. In
addition to the tabular presentation of keys in table 35, figures 2 through 9 provide a
visual representation of the main relationships between the tables.
Management Metadata describing the table fields in the four wts tables are provided in tables 37-40.
Weights Associated The weights represent the probability that a particular option would occur. For
with the NNLSC example, if there were only 3 management options and the probability that the first
option would occur was 20 percent, the probability that the second option would
occur was 30 percent, and the probability that the third option would occur was 50
percent, then the nutrient loss estimate for the NRI sample point would be 0.2 times
the loss estimated by EPIC for the first option plus 0.3 times the loss estimated for the
second option plus 0.5 times the loss estimated for the third option.
Included are two tillage weight tables. Derived from the 2001 Crop Residue
Management Survey, wtsCountyTillage lists the probability for the occurrence of no-
till, reduced (mulch)-till and conventional tillage by county, crop, and irrigation class.
These data were used to create wtsUruTillProps, which lists tillage occurrence
probabilities by URU and tillage category. Values from this table are the tillage
probability coefficients used in the microsimulation modeling and recorded in the
“TillWt” field of the InSitu tables.
Two tables of nutrient management weights are provided. The

wtsNutrientApplications table provides statistical weights for commercial fertilizer
application classes (rate, timing, and manure category) by state (or region), crop, and
irrigation category. These probability coefficients are used in the microsimulation
modeling and recorded in the “NutWt” field of the InSitu tables. The
wtsManureCategory table provides statistical weights for six manure application
categories (see defManureCategory for definitions of the categories) in each state,
climate cluster, and yield class. The weights are also recorded for each model run in the
“NutWt” field of the InSitu tables.
Methods and sources for deriving the statistical weights as well as application of the
weights through microsimulation modeling is treated in Model Simulation of Soil Loss,
Nutrient Loss, and Change in Soil Organic Carbon Associated with Crop Production and briefly
discussed in Appendix A of this document. However, it important to note here, that
occurrence probabilities in a domain do not always sum to one (unity). There are
various reasons for this noted elsewhere. The important point is that users should
always renormalize the weights so that the sum of weights any domain is unity.
Management weights applied in the microsimulation modeling or in analyses of the
NNLSC data are routinely renormalized “on the fly” by dividing each weight by the
sum of weights in the domain. This process is illustrated in chapter 4 examples and by
the management weight application example provided in Appendix A.
16
Electronic Metadata Three tables of metadata, identified with one or more asterisks
in the NNLSC preceding the name, are included with the NNLCS.
****DataSets lists information about the data sets in the
NNLSC. List identifies data sets not included in this release. **DataTables lists of the
tables in NNLSC_DATA.mdb and provides metadata not included in the paper
documentation. Likewise, more extensive metadata definitions describing the table
fields in NNLSC_DATA.mdb are provided in the *DataDefinitions table. In
addition, the field description in the table design view is usually filled in. This is what
the status bar text will be set to when you slide that field onto a form. Also, the
StatusBar text shows up in the lower left corner of the screen.
17
Blank
18
3
Chapter
Chapter3: Table Metadata & Relational Diagrams

Handy reference material when exploring the NNLSC…
19
Table Metadata
Table 4. 97bcr_InSitu Metadata
97bcr_InSitu
Key Field Per Acre Total
Field Name Type Index? Description
PK FK Size Units Unit
Unique ID assigned to each NNLSC-EPIC3060
ID L. Int TRUE PK 4 na na
model run.
Simulation Text FALSE FK 18 Scenario na na
ID assigned to each Unique Resource Unit (A URU
URUid L. Int TRUE FK 4 consists of a unique state, crop, climate, soil, na na
irrigation system, and conservation practice.)
FK, FK2:
StateFIPS L. Int TRUE 4 State FIPS Code na na
URU
FK, FK2: Crop Grown (Cropland
CropID L. Int TRUE 4 na na
URU 1,2,3,5,6,10,11,14,16,18,29,41,60,85)
FK, FK2: IDs for 1 - 66 climate zones. Area in each zone was
ClimateCluster Integer TRUE 2 na na
URU simulated using the same weather station.
FK, FK2: IDs for 1 - 2700+ soil clusters. One soil represented
SoilCluster L. Int TRUE 4 na na
URU all soils in the cluster.
FK, FK2:
IrrigationCode Byte TRUE 1 Irrigation category. Dry=0, Sprinkler=1, Gravity=2 na na
URU
Conservation Practice category. 0-7 describes
FK, FK2: conservation practices simulated. 0 = no
ConserPract Byte TRUE 1 na na
URU conservation practice. See defConserPract for
other practice code definitions.
Tillage Byte TRUE FK 1 Conventional=1, Mulch=3, No-till=4 na na
Manure Categories 1 - 3 are "before" scenario; i.e.
actual conditions. Table does not include data for
ManureCategory L. Int TRUE FK 4 na na
Manure Categories 4 – 5; "after" implementation of
CNMP scenario.
Expected yield classes within each state-crop-climate
YldClass L. Int TRUE FK 4 zone derived from an early set of model runs. Used in na na
determining manure application rates.
Fertilizer Rate Category (1-13 describes high, med,
NutrientRateCategory Byte TRUE FK 1 na na
low, etc.)See defNutTime.
1-11 describes when fertilizer applied. See
ApplicationTiming Byte TRUE FK 1 na na
defNutTime for code definitions.
ApplicationCategory Byte TRUE FK 1 1-2 Dry or irrigated commercial fertilizer rate. na na
Land use ID for aggregating NRI probabilities for
NRI_LU L. Int FALSE FK 4 na na
cropshares instead of crop.
Slope Single FALSE Slope (used in EPIC model run). Meters
Slope Length Single FALSE Slope Length (used in EPIC model run). m/m
SlopeClass Byte TRUE FK 1 Slope Class (1-7) na
Statistical weight for commercial fertilizer
NutWt Single FALSE 4 na na
applications.
ManWt Single FALSE 4 Statistical weight for manure fertilizer applications. na na
Tillage Coefficient derived from Crop Residue
TillWt Single FALSE 4 na na
Management Survey
AllWt Single FALSE 4 Allwt = NutWt x ManWt x TillWt na na
SumWts = AllWt summed across each URU. Used
SumWts Double FALSE 8 na na
for normalization.
Adjusted A1000 (a1000a in SL). Corrected acres for
URUacres Double FALSE 8 those cropshare URUs missing the partner URU so na na
that NRI xfact equals a1000.
Probability of management represented by run
occurring in URU. Normalization corrects for any
URUprob Double FALSE 8 na na
EPIC run outputs not included in InSitu
URUprob=Allwt/Sumwts
Acres represented by model run.
RunAcres Double FALSE 8 na na
Runacres=URUacres*URUprob
National probability coefficient. Represents
NatProb Double FALSE 8 probability of a similar acre occurring. na na
NatProb=RunAcres/total acres (298478000 acres).
Yield Single FALSE 4 Crop Yield Varies na
Precip Single FALSE 4 Precipitation in in
IrrVol Single FALSE 4 Irrigation Water Applied in in
Runoff Single FALSE 4 Runoff in in
Perc Single FALSE 4 Percolation in in
SubFlow Single FALSE 4 Subsurface Lateral Flow in in
ET Single FALSE 4 Evapotranspiration in in
USLE Single FALSE 4 Water erosion (USLE) tons ac-1 tons
20
97bcr_InSitu
RUSLE Single FALSE 4 Water erosion (RUSLE) tons ac-1 tons
MUSLE Single FALSE 4 Water erosion (MUSLE) tons ac-1 tons
Wind Single FALSE 4 Wind Erosion tons ac-1 tons
TOC Single FALSE 4 Total Organic Carbon (30 Yr Avg.) tons ac-1 tons
TOC_yr1 Single FALSE 4 Beginning Organic Carbon (Yr 1) tons ac-1 tons
TOC_yr30 Single FALSE 4 Ending Organic Carbon (Yr 30) tons ac-1 tons
Change Total Organic Carbon Over 30 Yrs.
ChangeTOC Single FALSE 4 tons ac-1 tons
(TOC_yr30-TOC_yr1)
C_PoolChange Single FALSE 4 Change in Total Carbon Pool (includes first 10 years) lbs ac-1 tons
Initial CN Ratio Single FALSE 4 Initial Carbon-Nitrogen ratio (initialized as 10) na na
Final CN Ratio Single FALSE 4 Final Carbon-Nitrogen ratio na na
ERwater Double FALSE 8 Enrichment ratio for waterborne sediment. na na
ERwind Double FALSE 8 Enrichment ratio for windborne sediment. na na
HumMin Single FALSE 4 Humus Mineralization tons ac-1 tons
NetNmin Single FALSE 4 Net N mineralized (org to mineral conversion) lbs ac-1 tons
Nfix Single FALSE 4 N Fixation lbs ac-1 tons
Nitri Single FALSE 4 N converted from NHx to NOx lbs ac-1 tons
NO3RO Single FALSE 4 NO3 loss in runoff lbs ac-1 tons
NO3Leach Single FALSE 4 NO3 lost as leachate lbs ac-1 tons
NO3SubFl Single FALSE 4 NO3 loss in subsurface lateral flow lbs ac-1 tons
Nsed Single FALSE 4 Total organic N loss with sediment lbs ac-1 tons
NsedWater Single FALSE 4 Organic Nitrogen Lost with Waterborne Sediment lbs ac-1 tons
NsedWind Single FALSE 4 Organic Nitrogen Lost with Windborne Sediment lbs ac-1 tons
Nvol Single FALSE 4 N Volatilized lbs ac-1 tons
Sum of all N loss
TotalNloss Single FALSE 4 lbs ac-1 tons
(Nsed+Nvol+NO3RO+NO3Leach+NO3SubFL)
Change in Total Nitrogen Pool (includes first 10
N_PoolChange Single FALSE 4 lbs ac-1 tons
years)
Pmin Single FALSE 4 P mineralized lbs ac-1 tons
Pro Single FALSE 4 Labile P lost in runoff lbs ac-1 tons
Pleach Single FALSE 4 Labile P lost in leachate lbs ac-1 tons
Psed Single FALSE 4 Total organic P lost with sediment lbs ac-1 tons
PsedWater Single FALSE 4 Organic phosphorus lost with waterborne sediment lbs ac-1 tons
PsedWind Single FALSE 4 Organic phosphorus lost with windborne sediment lbs ac-1 tons
TotalPloss Single FALSE 4 Sum of all P loss (PRO+Pleach+Psed) lbs ac-1 tons
STP Single FALSE 4 Labile P in top 2 inches ppm
STP_yr1 Single FALSE 4 Labile P in top 2 inches (Year 1) ppm
STP_yr30 Single FALSE 4 Labile P in top 2 inches ( Year 30) ppm
ChangeSTP Single FALSE 4 Labile P in top 2 in. (Change over 30 Yrs.) ppm
FPL Single FALSE 4 Labile P Fertilizer Applied lbs ac-1 tons
FPO Single FALSE 4 Organic P Fertilizer Applied lbs ac-1 tons
TotalPfert Single FALSE 4 Total P Fertilizer Applied (FPO+FPL) lbs ac-1 tons
ManureP Single FALSE 4 Phosphorus Applied with Manure lbs ac-1 tons
Chemical Phosphorus Fertilizer Applied
FertP Single FALSE 4 lbs ac-1 tons
(TotalPfert - ManureP)
FNO Single FALSE 4 Organic N Fertilizer Applied lbs ac-1 tons
FNO3 Single FALSE 4 Nitrate Fertilizer Applied lbs ac-1 tons
FNH3 Single FALSE 4 Ammonium Fertilizer Applied lbs ac-1 tons
Sum of Nitrogen Fertilizer Applied
TotalNfert Single FALSE 4 lbs ac-1 tons
(FNO+FNO3+FNH3)
ManureN Single FALSE 4 Nitrogen Applied with Manure lbs ac-1 tons
Chemical Nitrogen Fertilizer Applied
FertN Single FALSE 4 lbs ac-1 tons
(TotalNfert - ManureN)
avgCN Single FALSE 4 Curve Number (estimated by EPIC). na 55-100
avgCFact Single FALSE 4 USLE C Factor (estimated by EPIC). na Fraction
avgRusleC Single FALSE 4 Rusle C Factor (estimated by EPIC). na Fraction
avgNstress Single FALSE 4 Days crop nitrogen stress (estimated by EPIC). na Days
avgPstress Single FALSE 4 Days crop phosphorus stress (estimated by EPIC). na Days
avgWaterStress Single FALSE 4 Days crop water stress (estimated by EPIC). na Days
21
Table 5. 97NoCP_InSitu Metadata

97NoCP_InSitu
Unique ID assigned to each 97NoCP scenario
ID L. Int TRUE PK 4 na na
model run.
Unique ID for each 97bcr model run.
97bcrID L. Int TRUE FK 4 na na
97NoCP_InSitu foriegn key.
ID assigned to each Unique Resource Unit (A
URUid L. Int TRUE FK 4 URU consists of a unique state, crop, climate, soil, na na
FK, FK2:
StateFIPS L. Int TRUE 4 State FIPS Code na na
URU
FK, FK2: Crop Grown (Cropland
CropID L. Int TRUE 4 na na
URU 1,2,3,5,6,10,11,14,16,18,29,41,60,85)
FK, FK2: IDs for 1 - 66 climate zones. Area in each zone
ClimateCluster Integer TRUE 2 na na
URU was simulated using the same weather station.
FK, FK2: IDs for 1 - 2700+ soil clusters. One soil
SoilCluster L. Int TRUE 4 na na
URU represented all soils in the cluster.
FK, FK2:
IrrigationCode Byte TRUE 1 Irrigation category. Dry=0, Sprinkler=1, Gravity=2 na na
URU
Conservation Practice category. 0-7 describes
FK, FK2: conservation practices simulated. 0 = no
ConserPract Byte TRUE 1 na na
URU conservation practice. See defConserPract for
other practice code definitions.
Tillage Byte TRUE FK 1 Conventional=1, Mulch=3, No-till=4 na na
Manure Categories 1 - 3 are "before" scenario; i.e.
actual conditions. Table does not include data for
ManureCategory L. Int TRUE FK 4 na na
Manure Categories 4 – 5; the "after"
implementation of CNMP scenario.
Expected yield classes within each state-crop-
climate zone derived from an early set of model
YldClass L. Int TRUE FK 4 na na
runs. Used in determining manure application
rates.
Fertilizer Rate Category (1-13 describes high,
NutrientRateCategory Byte TRUE FK 1 na na
med, low, etc.)See defNutTime.
1-11 describes when fertilizer applied. See
ApplicationTiming Byte TRUE FK 1 na na
defNutTime for code definitions.
ApplicationCategory Byte TRUE FK 1 1-2 Dry or irrigated commercial fertilizer rate na na
Slope Single FALSE Slope (used in EPIC model run). Meters
Slope Length Single FALSE Slope Length (used in EPIC model run). m/m
SlopeClass Byte TRUE FK 1 Slope Class (1-7) na
Statistical weight for commercial fertilizer
NutWt Single FALSE 4 na na
applications.
ManWt Single FALSE 4 Statistical weight for manure fertilizer applications. na na
Tillage Coefficent derived from Crop Residue
TillWt Single FALSE 4 na na
Management Survey
AllWt Single FALSE 4 Allwt = NutWt x ManWt x TillWt na na
SumWts = AllWt summed across each URU.
Used for normalization.
Adjusted A1000 (a1000a in SL). Corrected acres
URUacres Double FALSE 8 for those cropshare URUs missing the partner na na
URU so that NRI xfact equals a1000.
Probability of management represented by run
URUprob Double FALSE 8 na na
occuring in URU. URUprob=Allwt/Sumwts
Acres represented by model run.
RunAcres Double FALSE 8 na na
Runacres=URUacres*URUprob
National probability coefficient. Represent prob of
NatProb Double FALSE 8 a similar acre occuring. NatProb=RunAcres/total na na
acres (298478000 acres).
22
97NoCP_InSitu
(TOC_yr30-TOC_yr1)
Change in Total Carbon Pool (includes first 10
C_PoolChange Single FALSE 4 lbs ac-1 tons
years)
Initial CN Ratio Single FALSE 4 Initial Carbon-Nitrogen ratio (inialized as 10) na na
Final CN Ratio Single FALSE 4 FinalCarbon-Nitrogen ratio na na
Sum of all N loss
Change in Total Nitrogen Pool (includes first 10
N_PoolChange Single FALSE 4 lbs ac-1 tons
years)
Organic phosphorus lost with waterborne
PsedWater Single FALSE 4 lbs ac-1 tons
sediment
(FNO+FNO3+FNH3)
Chemical Nitrogen Fertilizer Applied (TotalNfert -
FertN Single FALSE 4 ManureN) lbs ac-1 tons
avgCN Single FALSE 4 Curve Number (estimated by EPIC). 55-100
avgCFact Single FALSE 4 USLE C Factor (estimated by EPIC). Fraction
avgRusleC Single FALSE 4 Rusle C Factor (estimated by EPIC). Fraction
avgNstress Single FALSE 4 Days crop nitrogen stress (estimated by EPIC). Days
Single Days crop phosphorus stress (estimated by
avgPstress FALSE Days
4 EPIC).
avgWaterStress Single FALSE 4 Days crop water stress (estimated by EPIC). Days
23
Table 6. 97bcr_URU Metadata

97bcr_URU
URUid L. Int TRUE PK 4 consists of a unique state, crop, climate, soil, irrigation na na
system, and conservation practice.)
StateFips L. Int TRUE PK2:URU State FIPS Code na
CropID L. Int TRUE PK2:URU Crop ID na
ClimateCluster Integer TRUE PK2:URU Climate Cluster na
SoilCluster L. Int TRUE PK2:URU Soil Cluster na
IrrigationCode Byte TRUE PK2:URU Irrigation Code na
ConserPract Byte TRUE PK2:URU Conservation Practice na
YldClass L. Int FALSE FK Yield Class na
SumWts = AllWt summed across each URU.
Used for normalization.
A1000 Single FALSE 4 URU acres (1000s). Sum (A1000) = 298, 477 na na
Sum of all N loss
N_PoolChange Single FALSE 4 Change in Total Nitrogen Pool (includes first 10 years) lbs ac-1 tons
Chemical Phosphorus Fertilizer Applied (TotalPfert -
ManureP)
(FNO+FNO3+FNH3)
Chemical Nitrogen Fertilizer Applied (TotalNfert -
ManureN)
24
97bcr_URU
(TOC_yr30-TOC_yr1)
Table 7. 97NoCP_URU Metadata

97NoCP_URU
URUid L. Int TRUE PK 4 consists of a unique state, crop, climate, soil, na na
StateFips L. Int TRUE PK2:URU State FIPS Code na
CropID L. Int TRUE PK2:URU Crop ID na
ClimateCluster Integer TRUE PK2:URU Climate Cluster na
SoilCluster L. Int TRUE PK2:URU Soil Cluster na
IrrigationCode Byte TRUE PK2:URU Irrigation Code na
ConserPract Byte TRUE PK2:URU Conservation Practice na
25
Table 8. 97bcr_Cropshare Metadata

97bcr_Cropshare
Recid Text TRUE PK:Cropshare 15 Record ID: Unique ID for each NRI point na na
StateFips Integer TRUE FK, FK2:URU 2 State FIPS Code na na
FIPS L. Int FALSE FK 4 County FIPS Code na na
FK ID assigned to each URU (individual State Link row
URUid L. Int TRUE 4 consisting of a unique state, crop, climate, soil, irr na na
system, and cons practice).
FK, PK:
CropID L. Int TRUE Cropshare 4 Crop ID na na
FK2: URU
ClimateCluster Integer TRUE FK, FK2:URU 2 Climate Cluster na na
SoilCluster Integer TRUE FK, FK2:URU 2 Soil Cluster na na
IrrigationCode Byte TRUE FK, FK2:URU 1 Irrigation Code na na
ConserPract Byte TRUE FK, FK2:URU 1 Conservation Practice na na
HUC L. Int TRUE FK 4 8-digit Hydrologic Cataloging Unit (watershed) na na
Acres Single FALSE 4 Acres (1000s) na na
Sum of all N loss
26
97bcr_Cropshare
TotalNfert Single FALSE 4 Sum of Nitrogen Fertilizer Applied (FNO+FNO3+FNH3) lbs ac-1 tons
(TOC_yr30-TOC_yr1)
Table 9. 97NoCP_Cropshare Metadata

97NoCP_Cropshare
Recid Text TRUE PK:Cropshare 15 Record ID: Unique ID for each NRI point na na
StateFips Integer TRUE FK, FK2:URU 2 State FIPS Code na na
FIPS L. Int TRUE FK 4 County FIPS Code na na
URUid L. Int TRUE FK 4 consists of a unique state, crop, climate, soil, na na
FK, PK:
CropID L. Int TRUE Cropshare 4 Crop ID na na
FK2: URU
ClimateCluster Integer TRUE FK, FK2:URU 2 Climate Cluster na na
SoilCluster Integer TRUE FK, FK2:URU 2 Soil Cluster na na
IrrigationCode Byte TRUE FK, FK2:URU 1 Irrigation Code na na
ConserPract Byte TRUE FK, FK2:URU 1 Conservation Practice na na
HUC L. Int TRUE FK 4 8-digit Hydrologic Cataloging Unit (watershed) na na
Number of acres. Same as xfact except for crop splits
Acres Single FALSE 4 na na
on corn and wheat
27
Table 10. 97bcr_Point Metadata

97bcr_Point
Recid Text TRUE PK 15 Record ID: Unique ID for each NRI point na na
StateFips Integer TRUE FK 2 State FIPS Code na
FIPS L. Int TRUE PK2:NriPoint 4 County FIPS Code na na
ClimateCluster Integer TRUE FK 2 Climate Cluster na
SoilCluster Integer TRUE FK 2 Soil Cluster na
IrrigationCode Byte TRUE FK 1 Irrigation Code na
ConserPract Byte TRUE FK 1 Conservation Practice na
HUC L. Int TRUE FK 4 8-digit Hydrologic Cataloging Unit (watershed) na
xfact Integer FALSE 2 NRI Expansion Factor: Acres (100s) point represents na na
TAcres Single FALSE 4 Total Acres (1000s) na na
Subflow Single FALSE 4 Subsurface Lateral Flow in in
(TOC_yr30 - TOC_yr1)
TotalNfert Single FALSE 4 Sum of Nitrogen Fertilizer Applied (FNO+FNO3+FNH3) lbs ac-1 tons
Sum of all N loss
FPl Single FALSE 4 Labile P Fertilizer Applied lbs ac-1 tons
28
97bcr_Point
Table 11. 97NoCP_Point Metadata

97NoCP_Point
Recid Text TRUE PK 25 Record ID: Unique ID for each NRI point na na
StateFips Integer TRUE FK 2 State FIPS Code na
FIPS L. Int TRUE PK2 4 County FIPS Code na na
ClimateCluster Integer TRUE FK 2 Climate Cluster na
SoilCluster Integer TRUE FK 2 Soil Cluster na
IrrigationCode Byte TRUE FK 1 Irrigation Code na
ConserPract Byte TRUE FK 1 Conservation Practice na
HUC L. Int TRUE FK 4 8-digit Hydrologic Cataloging Unit (watershed) na
NRI_LU L. Int TRUE FK 4 na
xfact Integer FALSE 2 NRI Expansion Factor: Acres (100s) point represents na na
TAcres Double FALSE 8 Total Acres (1000s) na na
Table 12. attribURU Metadata

attribURU
Key
Field Name Type Index? Description Unit
PK FK
URUid L. Int TRUE PK URUid na
StateFips L. Int TRUE FK, PK2: URU State FIPS Code na
CropID L. Int TRUE FK, PK2: URU Crop ID na
ClimateCluster Integer TRUE FK, PK2: URU Climate Cluster na
SoilCluster L. Int TRUE FK, PK2: URU Soil Cluster na
IrrigationCode Byte TRUE FK, PK2: URU Irrigation Code na
ConserPract Byte TRUE FK, PK2: URU Conservation Practice Code na
Pfactor Single FALSE P Factor Fraction
YldClassIndex Single FALSE indexed yield, proportion of average na
Slope Single FALSE Slope (average for all NRI points in URU) ft
SlopeLen Single FALSE Slope Length (average for all NRI points in URU) ft/ft
a1000a Single FALSE Corrected a1000 (adjusted for missing crop splits) na
EI Single FALSE Erosivity Index (average for all NRI points in URU) na
29
attribURU
Key
PK FK
RKLS Single FALSE RKLS (average for all NRI points in URU) na
CfactorNri Single FALSE C factor (average for all NRI points in URU) Fraction
TfactorNri Single FALSE T factor (average for all NRI points in URU) tons ac-1
USLEnri Single FALSE USLE (average for all NRI points in URU) tons ac-1
Curve Number (average estimated from all model runs
CN Single FALSE 55-100
in URU)
USLE C Factor (average estimated from all model
UsleC Single FALSE Fraction
runs in URU)
Rusle C Factor (average estimated from all model
RusleC Single FALSE Fraction
runs in URU)
Days crop nitrogen stress (average estimated from all
Nstress Single FALSE Days
model runs in URU).
Days crop phosphorus stress (average estimated from
Pstress Single FALSE Days
all model runs in URU).
Days crop water stress (average estimated from all
WaterStress Single FALSE Days
model runs in URU).
%NoTill Double FALSE %NoTill in URU Percent
%Mulch Double FALSE % Mulch tillage in URU Percent
%Conventional Double FALSE % Conventional tillage in URU Percent
Table 13. attribPoint Metadata

Key
PK FK
Recid Text TRUE PK Record ID: Unique ID for each NRI point na
FIPS L. Int TRUE PK2: NriPoint County FIPS Code na
StateFips Integer TRUE FK State FIPS Code na
ClimateCluster Integer TRUE FK Climate Cluster na
SoilCluster Integer TRUE FK Soil Cluster na
IrrigationCode Byte TRUE FK Irrigation Code na
ConserPract Byte TRUE FK Conservation Practice Code na
HUC L. Int TRUE FK 8-digit Hydrologic Cataloging Unit (watershed) na
USLEnri Single FALSE Estimated USLE for point in NRI tons ac-1
WEQnri Single FALSE Estimated wind erosion (WEQ) for point in NRI tons ac-1
NRI_LU L. Int TRUE FK NRI Land Use na
LCC Text FALSE Land Capability Class (from 97 NRI) na
MLRA Text FALSE Major Land Resource Area (from 97 NRI) na
NRIPTR L. Int FALSE Id linking point to 92 NRI soil description na
SoilNameNri Text FALSE Soil Name (from 97 NRI) na
TextureNri Text FALSE Surface Texture (from 97 NRI) na
asm4soil Text FALSE Ag Sector Model soil erosion class na
Hydric Byte FALSE Hydric Soil Class (from 97 NRI) na
HEL Byte FALSE Highly Erodable Land Class (from 97 NRI) na
TfactNri Byte FALSE Soil T (Tolerance) Factor (from 97 NRI) tons ac-1
RfactNri Integer FALSE USLE R (Rainfall Erosivity) Factor (from 97 NRI)
KfactNri Single FALSE USLE K (Soil Erodibility) Factor (from 97 NRI) Fraction
CfactNri Single FALSE USLE C (Cover) Factor (from 97 NRI) Fraction
PfactNri Single FALSE USLE P (Practice) Factor (from 97 NRI) Fraction
SlopeLen Integer FALSE Slope Length (ft) (from 97 NRI) ft
Slope Single FALSE Slope (ft/ft) (from 97 NRI) ft/ft
xfact Integer FALSE NRI Expansion factor (from 97 NRI) 100s acres
30
Table 14. charClimate Metadata

Key
PK FK
WsId Integer TRUE PK: MonthlyWS Weather Station ID; Unique Key A na
Month Integer TRUE PK: MonthlyWS Month of Year: Unique Key B na
Air Temperature Average Max Single FALSE Air Temperature Average Max degrees C
Air Temperature Average Min Single FALSE Air Temperature Average Min degrees C
Air Temperature STD Max Single FALSE Air Temperature STD Max degrees C
Air Temperature STD Min Single FALSE Air Temperature STD Min degrees C
Precipitation Average Single FALSE Precipitation Average mm
Precipitation STD Single FALSE Precipitation STD mm
Precipitation Skew Coefficient Single FALSE Precipitation Skew Coefficient na
Probability Dry Wet Single FALSE Probability Dry Wet 0-1
Probability Wet Wet Single FALSE Probability Wet Wet 0-1
Rain Days Average Single FALSE Rain Days Average days
Rain Half Max Single FALSE Rain Half Max na
Solar Radiation Single FALSE Solar Radiation MJ / M**2
Relative Humidity Single FALSE Relative Humidity 0-1
Average Velocity Single FALSE Average Velocity m/sec @ 10m
Wind Velocity N Single FALSE Wind Velocity N Percent
Wind Velocity NNE Single FALSE Wind Velocity NNE Percent
Wind Velocity NE Single FALSE Wind Velocity NE Percent
Wind Velocity ENE Single FALSE Wind Velocity ENE Percent
Wind Velocity E Single FALSE Wind Velocity E Percent
Wind Velocity ESE Single FALSE Wind Velocity ESE Percent
Wind Velocity SE Single FALSE Wind Velocity SE Percent
Wind Velocity SSE Single FALSE Wind Velocity SSE Percent
Wind Velocity S Single FALSE Wind Velocity S Percent
Wind Velocity SSW Single FALSE Wind Velocity SSW Percent
Wind Velocity SW Single FALSE Wind Velocity SW Percent
Wind Velocity WSW Single FALSE Wind Velocity WSW Percent
Wind Velocity W Single FALSE Wind Velocity W Percent
Wind Velocity WNW Single FALSE Wind Velocity WNW Percent
Wind Velocity NW Single FALSE Wind Velocity NW Percent
Wind Velocity NNW Single FALSE Wind Velocity NNW Percent
Table 15. charClimClusClass Metadata

Key Per Acre Total
PK FK Units Unit
ClimateCluster Integer TRUE PK Climate Cluster ID na na
WSID Integer TRUE FK Weather Station ID na na
TemperatureClass Text FALSE Mesic < 15c; Thermic > 15c na na
Tclass Integer TRUE FK Numeric Temperture Class; Foriegn Key na na
Moisture Class: Arid, Semi-arid, Sub-humid, Humid, Sub-
MoistureClass Text FALSE tropical, Tropical na na
Mclass Integer TRUE FK Numeric Moisture Class; Foriegn Key na na
ClimateClass Text FALSE Temperature + Mosture Class na na
Cclass Integer FALSE FK Numeric Climate Class; na na
ClusterAcres Single FALSE Climate Cluster Area acres acres
AvgTemp Single FALSE Average Temperature (from monthly weater statistics) degrees C degrees C
AvgRH Single FALSE Average Relative Humidty (from monthly weater statistics) percent percent
AvgPrecip Single FALSE Average Precipitation (inches) (Model Estimated) na na
AvgIrrigation Single FALSE Average Irrigation Applied (inches) (Model Estimated) na inches
Total Water Inputs Single FALSE Irrigation + Precipitation na inches
AvgET Single FALSE Average ET (inches) (Model Estimated) na inches
PercentET Single FALSE ET as a Percent of Precipitation na percent
PercentET2 Single FALSE ET as a Percent of Total Water Inputs na percent
AvgRO Single FALSE Average Runoff (inches) (Model Estimated) na inches
PercentRO Single FALSE Runoff as a Percent of Total Water Inputs na percent
AvgPerc Single FALSE Average Percolation inches) (Model Estimated) na inches
PercentPerc Single FALSE Percolation as a Percent of Total Water Inputs na percent
AvgSSF Single FALSE Average Subsurface Lateral Flow (inches) (Model Estimated) na inches
PercentSSF Single FALSE Subsurface Lateral Flow as a Percent of Total Water Inputs na percent
31
Table 16. charWeatherStation Metadata

Key
PK FK
WsId Integer TRUE PK Weather Station ID na
WsName Text FALSE Weather Station Name na
State Text FALSE State na
Latitude Single FALSE Latitude of WS degrees
Longitude Single FALSE Longitude of WS degrees
Elevation Single FALSE Elevation of WS m
Temperature Text FALSE Mesic < 15c; Thermic > 15c na
Tclass Integer TRUE FK Numeric Temperature Class na
MoistureRegime Text FALSE Arid, Semiarid, Subhumid, Humid, Subtropical na
MClass Integer TRUE FK Numeric Moisture Class na
Climate Text FALSE Temperature + Moisture Class na
Cclass Integer FALSE FK Numeric Climate Class na
Table 17. charCrops Metadata

charCrops
Key
PK FK
CropID L. Int TRUE PK Crop ID na
CropName Text FALSE Crop Name na
Modeling Unit Text FALSE Crop Yield Unit Reported by EPIC na
Reporting Unit Text FALSE NNLSC Crop Yield Unit na
Unit Wt Single FALSE weight conversion na
Biomass Energy Ratio Single FALSE Biomass Energy Ratio na
Harvest Index Single FALSE Harvest Index na
Optimal Temperature Single FALSE Optimal Temperature degrees C
Minimum Temperature Single FALSE Minimum Temperature degrees C
Maximum Leaf Area Index Single FALSE Maximum Leaf Area Index na
Growing Season Leaf Decline Single FALSE Growing Season Leaf Decline na
Leaf Development First Point Single FALSE Leaf Development First Point na
Leaf Development Second Point Single FALSE Leaf Development Second Point na
Leaf Area Decline Rate Single FALSE Leaf Area Decline Rate na
Biomass Energy Ratio Decline Single FALSE Biomass Energy Ratio Decline na
Aluminum Tolerance Single FALSE Aluminum Tolerance na
Maximum Stomatal Conductance Single FALSE Maximum Stomatal Conductance na
Critical Aeration Factor Single FALSE Critical Aeration Factor na
Seeding Rate Single FALSE Seeding Rate na
Maximum Crop Height Single FALSE Maximum Crop Height m
Maximum Root Depth Single FALSE Maximum Root Depth m
CO2 Concentration Single FALSE CO2 Concentration na
Minimum C Factor Single FALSE Minimum C Factor na
Nitrogen in Yield Single FALSE Nitrogen in Yield na
Phosphorus in Yield Single FALSE Phosphorus in Yield na
Potassium in Yield Single FALSE Potassium in Yield na
Minimum Harvest Index Single FALSE Minimum Harvest Index na
Pest Factor Single FALSE Pest Factor na
Seed Cost Single FALSE Seed Cost na
Price for Yield Single FALSE Price for Yield na
Water in Yield Single FALSE Water in Yield na
Nitrogen Uptake Emergence Single FALSE Nitrogen Uptake Emergence na
Nitrogen Uptake Midseason Single FALSE Nitrogen Uptake Midseason na
Nitrogen Uptake Maturity Single FALSE Nitrogen Uptake Maturity na
Phosphorus Uptake Emergence Single FALSE Phosphorus Uptake Emergence na
Phosphorus Uptake Midseason Single FALSE Phosphorus Uptake Midseason na
Phosphorus Uptake Maturity Single FALSE Phosphorus Uptake Maturity na
Potassium Uptake Emergence Single FALSE Potassium Uptake Emergence na
Potassium Uptake Midseason Single FALSE Potassium Uptake Midseason na
Potassium Uptake Maturity Single FALSE Potassium Uptake Maturity na
Wind Erosion Factor Live Single FALSE Wind Erosion Factor Live na
Wind Erosion Factor Dead Single FALSE Wind Erosion Factor Dead na
Wind Erosion Factor Flat Single FALSE Wind Erosion Factor Flat na
Frost Damage First Point Single FALSE Frost Damage First Point na
Frost Damage Second Point Single FALSE Frost Damage Second Point na
Vapor Pressure Deficit Single FALSE Vapor Pressure Deficit na
VPD Threshold Single FALSE Vapor Pressure Deficit Threshold na
32
charCrops
Key
PK FK
VPD Single FALSE Vapor Pressure Deficit na
Root Weight Emergence Single FALSE Root Weight Emergence na
Root Weight Maturity Single FALSE Root Weight Maturity na
Conversion Coefficient Single FALSE Conversion Coefficient na
Biomass Moisture Content Single FALSE Biomass Moisture Content na
Germination Heat Units Single FALSE Germination Heat Units na
Price for Yield Forage Single FALSE Price for Yield Forage na
Plant Population Point 1 L. Int FALSE Plant Population Point 1 na
Plant Population Point 2 L. Int FALSE Plant Population Point 2 na
Plant Population 1 Fraction MAX LAI Single FALSE Plant Population 1 Fraction MAX LAI na
Plant Population 2 Fraction MAX LAI Single FALSE Plant Population 2 Fraction MAX LAI na
Water Use to Biomass Single FALSE Water Use to Biomass na
Yield Salinity Ratio Single FALSE Yield Salinity Ratio na
Salinity Threshold Single FALSE Salinity Threshold na
Lignin Fraction Half Mature Single FALSE Lignin Fraction Half Mature na
Lignin Fraction Maturity Single FALSE Lignin Fraction Maturity na
Fraction Turnout Single FALSE Fraction Turnout na
Fraction Lint Single FALSE Fraction Lint na
YldN Single FALSE N removed w/ harvested yield na
YldP Single FALSE P removed w/ harvested yield na
% Moisture Single FALSE Moisture in Yield na
Moisture Factor Single FALSE Moisture conversion factor na
Notes Text FALSE Notes na
Source Text FALSE Source na
Table 18. charSoils Metadata

charSoils.
Key
PK FK
SoilCluster L. Int TRUE PK Soil Cluster na
Name Text FALSE Soil Series Name na
Soils 5 ID Text TRUE Soils 5 ID na
Texture Text FALSE Surface Texture na
Text Mod Text FALSE Surface Texture Modifier na
TxtID: 1 of 27 codes describing surface texture. See
TxtID L. Int TRUE FK na
defSoilTxtGrps table.
Texture Group Text FALSE FK Texture Group na
TxtGrp Byte TRUE FK Texture Group Code na
HSG Text FALSE FK Hydrologic Soil Group Code na
Soil Test Grp Byte FALSE Soil Test Group (Alabama Soils Only) na
SoilClass L. Int TRUE FK S Class Code: Texture Group + HSG (25 classes) na
SclassDescrpt Text FALSE S Class Description na
Texture Group + HSG (19 classes; Organic and Other
HydroClass L. Int FALSE FK na
Texture classes =9999)
Number of Layers L. Int FALSE Number of Layers na
Maximum Number of Layers L. Int FALSE Maximum Number of Layers na
Initial Splitting Thickness L. Int FALSE Initial Splitting Thickness m
Weathering Code L. Int FALSE Weathering Code na
Albedo Single FALSE Soil Albedo (wet) na
Minimum Thickness Single FALSE Minimum Thickness m
Minimum Thickness Stop Single FALSE Minimum Thickness Stop m
Initial Water Content Single FALSE Initial Water Content m
Minimum Water Table Depth Single FALSE Minimum Water Table Depth m
Maximum Water Table
Single FALSE Maximum Water Table Depth m
Depth
Initial Water Table Depth Single FALSE Initial Water Table Depth m
Subsurface Flow Travel
Single FALSE Subsurface Flow Travel Time Days
Time
Runoff Curve Number 2 L. Int FALSE Runoff Curve Number 2 na
Initial Groundwater Storage L. Int FALSE Initial Groundwater Storage mm
Maximum Groundwater
L. Int FALSE Maximum Groundwater Storage mm
Storage
Return Flow Root Zone Double FALSE Return Flow Root Zone Fraction
Previous Years Cultivation L. Int FALSE Number Years Previous Cultivation Years
L1_Clay Single FALSE Layer 1 % Clay Percent
33
charSoils.
Key
PK FK
L1_Sand Single FALSE Layer 1 % Sand Percent
L1_silt Single FALSE Layer 1 % Silt Percent
L1_Coarse_Frag Single FALSE Layer 1 Coarse Fragments Percent
Organic Carbon in layer (% organic matterial/1.72 = organic
L1_OrgC Single FALSE Percent
carbon %)
L1_CEC Single FALSE Layer 1 Cation exchange capacity na
L1_Bd Single FALSE Layer 1 Bulk Density t/m^3
L1_Fc Single FALSE Layer 1 Field Capacity kPa
L1_pH Single FALSE Layer 1 pH log
L1_k Single FALSE Layer 1 Saturated Conductivity Days
carbon %)
carbon %)
carbon %)
Table 19. defStates Metadata

Key
PK FK
StateFips L. Int FALSE PK State FIPS Code
ST Text FALSE State Abbreviation
State Text FALSE State Name
CTIC Region Byte FALSE FK CTIC region code
34
Table 20. defNnlscRegions Metadata

Key
PK FK
HUC L. Int TRUE FK 8-digit Hydrologic Cataloging Unit (L. Int)
CU Text FALSE 8-digit Hydrologic Cataloging Unit (text)
ACC L. Int FALSE 6-digit Hydrologic Cataloging Unit (L. Int)
Name Text FALSE Watershed Name
Region Text FALSE PK NNLSC Region
Reg Text FALSE Region Abbrev.
RegCode Integer TRUE Region Code (1-6)
Area Double decimal FALSE empty
Perimeter Double decimal FALSE empty
Cropland Double decimal FALSE empty
Pasture Double decimal FALSE empty
ClimateCluster Integer FALSE FK Climate Cluster
Table 21. defTillage Metadata

Key
PK FK
TillName Text FALSE Short name for the 7 texture subgroups.
Tillage Byte TRUE PK Tillage Code
TillageName Text FALSE Long Name
Table 22. defIrrigationCode Metadata

Key
PK FK
IrrigationCode Byte TRUE PK Irrigation Code
Irrigation Definition Text FALSE Irrigation Definition: dryland, sprinkler, gravity.
IrrigateClass Integer FALSE FK Dry or Irrigated classification
Irrigation Yes/No FALSE Irrigation (yes or no)
Table 23. defConserPract Metadata

Key
PK FK
ConserPract Byte TRUE PK Conservation Practice Code
Practice Text FALSE Practice
CP Definition Text FALSE CP Definition
Table 24. defNutRate Metadata

Key
PK FK
Nutrient Rate Category Byte TRUE PK Nutrient Rate Category
Rate Definition Text FALSE Rate Definition
Table 25. defNutTime Metadata

Key
PK FK
ApplicationTiming Byte TRUE PK Application Timing Category
Timing Definition Text FALSE Timing Category Definition
35
Table 26. defManureCategory Metadata

Key
PK FK
ManureCategory L. Int TRUE PK Manure Category ID
Mancat6 L. Int TRUE Ditto
Scenario Text FALSE Before or After CNMP
Description Text FALSE Manure Category Definition
Name Text FALSE Scenario Name
Table 27. defLandUse Metadata

Key
PK FK
CropID L. Int TRUE PK Crop ID
CropName Text FALSE Crop Name
Epic Name Text FALSE EPIC Crop Name
LUclass Integer FALSE LU classification (1-6)
Land Use Text FALSE 6 crop types (ex. Row Crop (legume))
Broad Land Use Text FALSE FK 4 crop types (Row Crop, Small Grain, Hay, Pasture)
AG Census Name Text FALSE Crop name used in Census of Agriculture
Nass Name Text FALSE Crop name used by NASS
NassID L. Int FALSE Crop ID used by NASS
USDA Crop ID L. Int FALSE USDA Crop ID
CTIC Crop Name 1 Text FALSE Crop name used in Crop Residue Management Survey.
CTIC Crop name 2 Text FALSE Crop name used in Crop Residue Management Survey.
CTIC Crop Name 3 Text FALSE Crop name used in Crop Residue Management Survey.
NRI_LU1 L. Int FALSE FK NRI Land Use Code
NRI_LU2 L. Int FALSE FK NRI Land Use Code (where NNLSC crop is in 2 NRI LU)
Category L. Int FALSE USDA Crop Type Category
Table 28. defNRI_LandUse Metadata

Key
PK FK
NRI_LandUse L. Int TRUE PK NRI Land Use Code
Land Use Text FALSE NRI Land Use Definition
Table 29. defMoisture Metadata

Key
PK FK
Mclass Integer TRUE PK Moisture Class
Moisture Regime Text FALSE Arid, Semiarid, Subhumid, Humid, Subtropical
Definition Text FALSE M Class Definition
Table 30. defTemperature Metadata

Key
PK FK
Tclass Integer TRUE PK Numeric Temperature Class Code
Temperature Text FALSE T Class Name (Mesic or Thermic)
Definition Text FALSE T Class Definition
Table 31. defSlopeClass Metadata

Key
PK FK
SlopeClass Byte TRUE PK Slope Class (1-7)
SlopeClassName Text FALSE Slope Class Name
InSituRangeLo Single FALSE Low Range in InSitu
InSituRangeHi Single FALSE High Range in InSitu
36
Table 32. defSoilClass Metadata

Key
PK FK
SoilClass L. Int TRUE PK S Class Code
SclassDescrpt Text FALSE S class Description
Texture Group Text FALSE Seven texture groups
TexGrpCode Byte TRUE Texture group codes (1-7)
HSG Text FALSE FK Hydrologic Soil Group (A-D)
HydroClass L. Int FALSE PK2 Texture Group + HSG (19 classes)
Table 33. defSoilHydroGroup Metadata

Key
PK FK
HSG Text True PK Hydrologic Soil Group (A-D)
RunOffRank Byte FALSE HSG ranked by Runoff
PercRank Byte FALSE HSG ranked by Percolation
Definition Memo FALSE HSG Definition
Table 34. defSoilTxtGrps Metadata

Key
PK FK
TxtID L. Int TRUE PK TxtID (1-27)
TxtGrp Byte TRUE PK2 Texture Group Code
TxtCode Text TRUE Short name for the 7 texture subgroups.
TextureGroup Text TRUE Long name for the 7 texture subgroups.
Texture Text FALSE 27 specific texture definitions.
SQIfactor Single FALSE Soil Quality Index Factor
37
Table 35. Key relationships in NNLSC tables.

Tables in Key A list are related to tables in Key B list using the keys and table fields as shown.
Key A ‐ Key B
Key Key
Table Name Field Name Key Key Field Name Table Name
Type Type
97bcr_InSitu ID RunId PK FK 97bcr_InSitu.id 97bcrID 97NoCP_InSitu
97bcr_InSitu URUid URUid FK PK URU URUid 97bcr_URU
97bcr_InSitu StateFIPS State FK PK State StateFips defStates
97bcr_InSitu CropID Crop FK PK Crop CropID charCrops
97bcr_InSitu CropID Crop FK PK Crop CropID defLandUse
97bcr_InSitu ClimateCluster Climate FK FK Climate ClimateCluster charClimate
97bcr_InSitu ClimateCluster Climate FK FK Climate ClimateCluster charWeatherStation
97bcr_InSitu ClimateCluster Climate FK FK Climate ClimateCluster charClimClusClass
97bcr_InSitu SoilCluster Soil FK PK Soil SoilCluster charSoils
97bcr_InSitu IrrigationCode Irr FK PK Irr IrrigationCode defIrrigationCode
97bcr_InSitu ConserPract CP FK PK CP ConserPract defConserPract
97bcr_InSitu Tillage Till FK PK Till Code defTillage
97bcr_InSitu ManureCategory ManCat FK PK ManCat ManureCategory defManureCategory
Nutrient
97bcr_InSitu NutrientRateCategory Nrate FK PK Nrate defNutRate
RateCategory
97bcr_InSitu ApplicationTiming Ntime FK PK Ntime ApplicationTiming defNutTime
97bcr_InSitu NRI_LU NRI_LU FK PK NRI_LU NRI_LandUse defNRI_LandUse 12
97bcr_InSitu SlopeClass SlopeClass FK PK SlopeClass SlopeClass defSlopeClass
URUid FK PK URUid
WHERE
Select
(97bcr_InSitu.T CTuru
Tillage=1
illage=1);
97bcr_InSitu TillWt WHERE TillWt wtsUruTillProps
Select
Tillage (97bcr_InSitu.T Mturu
Tillage=2
illage=2);
WHERE
Select
(97bcr_InSitu.T Nturu
Tillage=3
illage=3);
StateFIPS StateFIPS
CropID CropID
97bcr_InSitu NutrientRateCategory NutWt FK PK NutWt RateCat wtsNutrientApplications
ApplicationTiming TimeCat
ApplicationCategory AppCat
StateFIPS StateFIPS
ClimateCluster ClimateCluster
97bcr_InSitu CropID ManWt FK PK ManWt CropID wtsManureCategory
YldClass YldClass
ManureCategory ManureCategory

97bcr_InSitu.
97NoCP_InSitu 97bcrID FK PK RunId ID 97bcr_InSitu
id
97NoCP_InSitu URUid URUid FK PK URU URUid 97NoCP_URU
97NoCP_InSitu StateFIPS State FK PK State StateFips defStates
97NoCP_InSitu CropID Crop FK PK Crop CropID charCrops
97NoCP_InSitu CropID Crop FK PK Crop CropID defLandUse
97NoCP_InSitu ClimateCluster Climate FK FK Climate ClimateCluster charClimate
97NoCP_InSitu ClimateCluster Climate FK FK Climate ClimateCluster charWeatherStation
97NoCP_InSitu ClimateCluster Climate FK FK Climate ClimateCluster charClimClusClass
97NoCP_InSitu SoilCluster Soil FK PK Soil SoilCluster charSoils
97NoCP_InSitu IrrigationCode Irr FK PK Irr IrrigationCode defIrrigationCode
97NoCP_InSitu ConserPract CP FK PK CP ConserPract defConserPract
97NoCP_InSitu Tillage Till FK PK Till Code defTillage
97NoCP_InSitu ManureCategory ManCat FK PK ManCat ManureCategory defManureCategory
Nutrient Rate
97NoCP_InSitu NutrientRateCategory Nrate FK PK Nrate defNutRate
Category
12 NRI Broad Land Use 141 and 142 are listed together as 142 at this level.
38
Key A ‐ Key B
Key Key
Type Type
97NoCP_InSitu ApplicationTiming Ntime FK PK Ntime ApplicationTiming defNutTime
97NoCP_InSitu NRI_LU NRI_LU FK PK NRI_LU NRI_LandUse defNRI_LandUse
97NoCP_InSitu SlopeClass SlopeCl;ass FK PK SlopeClass SlopeClass defSlopeClass
URUid FK PK URUid URUid
WHERE
Select
(97bcr_InSitu.T CTuru
Tillage=1
illage=1);
97NoCP_InSitu TillWt WHERE wtsUruTillProps
Select
Tillage (97bcr_InSitu.T MTuru
Tillage=2
illage=2);
WHERE
Select
(97bcr_InSitu.T NTuru
Tillage=3
illage=3);
StateFIPS StateFIPS
CropID CropID
97NoCP_InSitu NutrientRateCategory NutWt FK PK NutWt RateCat wtsNutrientApplications
ApplicationTiming TimeCat
ApplicationCategory AppCat
StateFIPS StateFIPS
ClimateCluster ClimateCluster
97NoCP_InSitu CropID ManWt FK PK ManWt CropID wtsManureCategory
YldClass YldClass
ManureCategory ManureCategory

97bcr_URU URUid URUid PK PK URUid URUid attribURU
97bcr_URU URUid URUid PK FK URUid URUid 97bcr_Cropshare
97bcr_URU StateFIPS State FK PK State StateFips defStates
97bcr_URU CropID Crop FK PK Crop CropID charCrops
97bcr_URU CropID Crop FK PK Crop CropID defLandUse
97bcr_URU ClimateCluster Climate FK FK Climate ClimateCluster charClimate
97bcr_URU ClimateCluster Climate FK FK Climate ClimateCluster charWeatherStation
97bcr_URU ClimateCluster Climate FK FK Climate ClimateCluster charClimClusClass
97bcr_URU SoilCluster Soil FK PK Soil SoilCluster charSoils
97bcr_URU IrrigationCode Irr FK PK Irr IrrigationCode defIrrigationCode
97bcr_URU ConserPract CP FK PK CP ConserPract defConserPract

97NoCP_URU URUid URUid PK PK URUid URUid attribURU
97NoCP_URU URUid URUid PK FK URUid URUid 97bcr_Cropshare
97NoCP_URU StateFIPS State FK PK State StateFips defStates
97NoCP_URU CropID Crop FK PK Crop CropID charCrops
97NoCP_URU CropID Crop FK PK Crop CropID defLandUse
97NoCP_URU ClimateCluster Climate FK FK Climate ClimateCluster charClimate
97NoCP_URU ClimateCluster Climate FK FK Climate ClimateCluster charWeatherStation
97NoCP_URU ClimateCluster Climate FK FK Climate ClimateCluster charClimClusClass
97NoCP_URU SoilCluster Soil FK PK Soil SoilCluster charSoils
97NoCP_URU IrrigationCode Irr FK PK Irr IrrigationCode defIrrigationCode
97NoCP_URU ConserPract CP FK PK CP ConserPract defConserPract

97bcr_Cropshare Recid Point FK PK Point Recid 97bcr_Point
97bcr_Cropshare Recid Point FK PK Point Recid attribPoint
97bcr_Cropshare StateFIPS State FK PK State StateFips defStates
97bcr_Cropshare URUid URUid FK PK URUid URUid 97bcr_URU
97bcr_Cropshare CropID Crop FK PK Crop CropID charCrops
97bcr_Cropshare CropID Crop FK PK Crop CropID defLandUse
97bcr_Cropshare ClimateCluster Climate FK FK Climate ClimateCluster charClimate
97bcr_Cropshare ClimateCluster Climate FK FK Climate ClimateCluster charWeatherStation
97bcr_Cropshare ClimateCluster Climate FK FK Climate ClimateCluster charClimClusClass
97bcr_Cropshare SoilCluster Soil FK PK Soil SoilCluster charSoils
97bcr_Cropshare IrrigationCode Irr FK PK Irr IrrigationCode defIrrigationCode
97bcr_Cropshare ConserPract CP FK PK CP ConserPract defConserPract
97bcr_Cropshare HUC HUC FK FK HUC HUC defNnlscRegions
39
Key A ‐ Key B
Key Key
Type Type
97bcr_Cropshare NRI_LU NRI_LU FK PK NRI_LU NRI_LandUse defNRI_LandUse

97NoCP_Cropshare Recid Point FK PK Point Recid attribPoint
97NoCP_Cropshare Recid Point FK PK Point Recid 97NoCP_Point
97NoCP_Cropshare StateFIPS State FK PK State StateFips defStates
97NoCP_Cropshare URUid URU FK PK URU URUid 97NoCP_URU
97NoCP_Cropshare CropID Crop FK PK Crop CropID charCrops
97NoCP_Cropshare CropID Crop FK PK Crop CropID defLandUse
97NoCP_Cropshare ClimateCluster Climate FK FK Climate ClimateCluster charClimate
97NoCP_Cropshare ClimateCluster Climate FK FK Climate ClimateCluster charWeatherStation
97NoCP_Cropshare ClimateCluster Climate FK FK Climate ClimateCluster charClimClusClass
97NoCP_Cropshare SoilCluster Soil FK PK Soil SoilCluster charSoils
97NoCP_Cropshare IrrigationCode Irr FK PK Irr IrrigationCode defIrrigationCode
97NoCP_Cropshare ConserPract CP FK PK CP ConserPract defConserPract
97NoCP_Cropshare HUC HUC FK FK HUC HUC defNnlscRegions
97NoCP_Cropshare NRI_LU NRI_LU FK PK NRI_LU NRI_LandUse defNRI_LandUse

97bcr_Point Recid Point PK PK Point Recid attribPoint
97bcr_Point StateFIPS State FK PK State StateFips defStates
97bcr_Point ClimateCluster Climate FK FK Climate ClimateCluster charClimate
97bcr_Point ClimateCluster Climate FK FK Climate ClimateCluster charWeatherStation
97bcr_Point ClimateCluster Climate FK FK Climate ClimateCluster charClimClusClass
97bcr_Point SoilCluster Soil FK PK Soil SoilCluster charSoils
97bcr_Point IrrigationCode Irr FK PK Irr IrrigationCode defIrrigationCode
97bcr_Point ConserPract CP FK PK CP ConserPract defConserPract
97bcr_Point HUC HUC FK FK HUC HUC defNnlscRegions
97bcr_Point NRI_LU NRI_LU FK PK NRI_LU NRI_LandUse defNRI_LandUse

97NoCP_Point Recid Point PK PK Point Recid attribPoint
97NoCP_Point StateFIPS State FK PK State StateFips defStates
97NoCP_Point ClimateCluster Climate FK FK Climate ClimateCluster charClimate
97NoCP_Point ClimateCluster Climate FK FK Climate ClimateCluster charWeatherStation
97NoCP_Point ClimateCluster Climate FK FK Climate ClimateCluster charClimClusClass
97NoCP_Point SoilCluster Soil FK PK Soil SoilCluster charSoils
97NoCP_Point IrrigationCode Irr FK PK Irr IrrigationCode defIrrigationCode
97NoCP_Point ConserPract CP FK PK CP ConserPract defConserPract
97NoCP_Point HUC HUC FK FK HUC HUC defNnlscRegions
97NoCP_Point NRI_LU NRI_LU FK PK NRI_LU NRI_LandUse defNRI_LandUse

attribPoint Recid Point PK PK Point Recid 97bcr_Point
attribPoint Recid Point PK FK Point Recid 97bcr_Cropshare
attribPoint Recid Point PK PK Point Recid 97NoCP_Point
attribPoint Recid Point PK FK Point Recid 97NoCP_Cropshare

charSoils TxtId TextureId FK PK TextureId TxtId defSoilTxtGrps
charSoils TxtGrp TxtGrp FK 2nd PK TextureId TxtGrp defSoilTxtGrps
charSoils SoilClass SoilClass FK PK SoilClass SoilClass defSoilClass
charSoils HydroClass HydroClass FK 2nd PK HydroClass HydroClass defSoilClass
charSoils HSG HSG FK PK HSG HSG defSoilHydroGroup

charWeatherStation WsId WS PK FK WsId WsId charClimate
charWeatherStation Tclass Tclass FK PK Tclass Tclass defTemperature
charWeatherStation MClass Mclass FK PK Mclass Mclass defMoisture
charWeatherStation Cclass Cclass FK FK Cclass ClimateCluster charClimClusClass

defNnlscRegions ClimateCluster Climate FK FK Climate ClimateCluster charClimate
defNnlscRegions ClimateCluster Climate FK FK Climate ClimateCluster charWeatherStation
defNnlscRegions ClimateCluster Climate FK FK Climate ClimateCluster charClimClusClass
40
Table 36. Management weights associated with the NNLSC datasets.

Table Name PK Key FK Keys Table Description
Tillage category weights by County, Crop, and Irrigation as derived from
wtsCountyTillage CntyTillWt FIPS, CropID, IrrigateClass the CRMS. This table is the source for wtsUruTillProps table which was
used in the microsimulation modeling.
Tillage category weights for each URU. Note to sp: Due to array size of
wtsUruTillProps UruTillWt URUid, Tillage 97brc_InSitu x wtsURUTillProp, wts for each tillage type were applied
sequentially during microsimulation modeling.
StateFIPS, CropID, ManCat,
wtsNutrientApplications NutWt Nutrient application category weights.
RateCat, TimeCat, AppCat
StateFIPS, ClimateCluster,
wtsManureCategory ManWT CropID, YldClass, Manure category weights.
ManureCategory
Table 37. wtsCountyTillage Metadata

Field Name Type Index? Key PK FK Description Unit
ID L. Int TRUE Unique Id na
FIPS L. Int TRUE PK:CntyTillWt County FIPS na
CropID L. Int TRUE PK:CntyTillWt Crop ID na
IrrigateClass Integer TRUE PK:CntyTillWt Irrigation Class Code na
NoTill_Wgt Double decimal FALSE Proportion in No till Percent
MulchTill_Wgt Double decimal FALSE Proportion in Mulch till Percent
ConvenTill_Wgt Double decimal FALSE Proportion in Conventional till Percent
Fill Text FALSE Filled missing county CTIC data na
Table 38. wtsUruTillProps Metadata

URUid L. Int TRUE PK:UruTillWt URU Id na
Tillage L. Int TRUE PK:UruTillWt Tillage Code na
TillWgt Double decimal FALSE Proportional Tillage weight (sum of all 3 tillages in a URU=1) Percent
Table 39. wtsNutrientApplications Metadata.

ID L. Int TRUE Unique ID na
StateFIPS L. Int TRUE PK:NutWt State FIPS Code na
CropID Integer TRUE PK:NutWt Crop ID na
ManCat L. Int FALSE PK:NutWt Manure Category na
RateCat Byte TRUE PK:NutWt Nutrient Application Rate Category na
TimeCat Byte TRUE PK:NutWt Nutrient Application Timing Category na
AppCat Byte TRUE PK:NutWt Application Category na
Drywt Double decimal FALSE Dryland Weight na
Irrwt Double decimal FALSE Irrigated Weight na
wt Double decimal FALSE Weight na
Table 40. wtsManureCategory Metadata

StateFIPS L. Int TRUE PK: ManWt State FIPS Code na
ClimateCluster Integer TRUE PK: ManWt Climate Cluster na
CropID Integer TRUE PK: ManWt Crop ID na
Scenario Text FALSE Manure Scenario na
YldClass L. Int TRUE PK: ManWt Yield Class na
ManureCategory L. Int TRUE PK: ManWt Manure Category na
Acres Single FALSE Acres Acres
Man Acres% Double decimal FALSE Manure Acres% Percent
41
Relational Diagrams
42
Figure 3. Relationships between 97bcr_InSitu data table and the attribute, characteristic and definition tables.
43
Figure 4. Relationships between 97NoCP_InSitu data table and the attribute, characteristic and definition tables.
44
Figure 5. Relationships between 97bcr_URU data table and the attribute, characteristic and definition tables.
45
Figure 6. Relationships between 97NoCP_URU data table and the attribute, characteristic and definition tables.
46
Figure 7. Relationships between 97bcr_Cropshare data table and the attribute, characteristic and definition tables.
47
Figure 8. Relationships between 97NoCP_Cropshare data table and the attribute, characteristic and definition tables.
48
Figure 9. Relationships between 97bcr_Point data table and the attribute, characteristic and definition tables.
49
Figure 10. Relationships between 97NoCP_Point data table and the attribute, characteristic and definition tables.
50
4
Chapter
Chapter4: STAT – the Status Trends Analysis Tool

STAT contains methods and examples for examining relationships between the
biophysical processes occurring on cultivated cropland (as estimated by the model) and
the input conditions for an extensive range of management and landscape situations.
T
he nutrient loss database is divided into two database files in the Microsoft
Access 2000 format. These two files are known as the front-end database
(STAT) and the back-end database (DATA). The front-end database is used as
a workspace for viewing, querying, processing, and manipulating data. It
contains non-data objects, such as saved queries, forms, reports, macros, and modules.
It can also contain additional objects created by the user for personal use. As a
workspace, it serves as an area for managing temporary objects. Many analyses require
some type of data access that is temporary in nature: creating tables with transient data,
for example. In addition, use of multiple front-ends can organize application
programming associated with different analyses. A new front-end database can be
created for a new analysis by copying NNLSC_STAT.mdb and renaming it with a
descriptive title.
The back-end database contains the tables, relationships, and data described in
chapters 2 and 3. The tables in this database are accessed by STAT through links
in the front-end database. The figure below illustrates the two-database approach.
51
Installing the NNLSC

Database
To install the NNLSC,
1) copy the files from
the DVD on to
C:\NNLSC.
2) Remove the Read

Only attribute for
NNLSC_STAT.mdb.
(Keeping the Read
Only attribute for
DATA ensures the
data is not changed
accidentally.)
View upon first opening the file NNLSC_STAT.mdb
The links used by linked tables in STAT are based on the location of DATA. If users
move DATA to a different location, the links will fail. If it is necessary to use an
alternative folder, to make the applications work correctly, you will need to:
1) Re-link tables in STAT using Tools => Database Utilities =>
Linked Table Manager
2) Set default database folder in STAT and DATA13 : Tools =>
Options =>General => Set “Default Database” to alternative
folder
3) Set application icon folder in STAT and DATA: Tools => Startup
=> Set “Application Icon” to alternative folder.
Retrieving NNLSC Data

NNLSC data can be retrieved using queries in STAT. For those using software other
than Access, the database file NNLSC_DATA.mdb can be accessed using most
relational database or analytical software packages via Open Database Connectivity14
(ODBC).
13 Read Only attribute must be removed from NNLSC_STAT.mdb prior to steps 2 and 3.
14 Open Database Connectivity (ODBC) is Microsoft's interface for accessing data in a heterogeneous software
environment of relational and non- relational database management systems. ODBC provides a standard software
application program interface (API) for using database management systems (DBMS). See
http://support.microsoft.com/kb/110093
52
Tables also can be imported into Microsoft Excel 2007. (Excel 2007 supports up to 1
million rows and 16 thousand columns per worksheet.) In addition, tables can be
exported from Access into various formats including delimited text files.
TO EXPORT A TABLE TO A DELIMITED OR FIXED‐WIDTH TEXT FILE
1. In the Database window click the name of the table you want to export and then on the
File menu, click Export.
2. In the Save as type box, click Text Files (*.txt; *.csv; *.tab; *asc).
3. Click the arrow to the right of the Save in box, and select the drive or folder to export to.
4. In the File Name box, enter a name for the file (or use the suggested name), and then
click Export.
5. Microsoft Access starts the Export Text Wizard.
SAS users can read in tables in using the Proc Import statement as shown in the
following example for reading in the table 97bcr_Point from NNLSC_DATA.mdb.
PROC IMPORT OUT= nnlsc_a (compress=yes)
DATATABLE= "97bcr_point"
DBMS=ACCESS REPLACE;
DATABASE='c:\NNLSC\NNLSC_DATA.mdb';
RUN;
An example SAS program that reads, aggregates, and summarizes 97bcr_Point is

provided in the file nripointsummary.sas.
Retrieve Data with STAT Queries

A query is a database command that retrieves records from one or more tables.
Data can be constrained to user specified criteria, which limits the amount of data
or restricts the domain. STAT includes several queries to retrieve data. Examples
illustrating queries are provided in this chapter.
Methods of Analysis
The NNLSC study design included both sample survey and experimental design
elements. In conjunction with EPIC and the extent of coverage, the mixed design
returned considerable variability in estimated effects. Along with the broad array of
effects estimated, this richness provides several avenues for analyzing environmental
impacts from agriculture.
1. Relate a) inputs such as precipitation, solar radiation, nitrogen fertilizer
application rate, b) environmental parameters (e.g. soil pH, slope, or land
surface cover), and c) response functions (model outputs) such as runoff,
particulate nitrogen loss, or soil organic carbon flux.
2. Analyze inputs, environmental parameters, and response functions using
statistical weights to estimate environmental impacts from agriculture for
domains covering the full sample space, constraint-limited domains, as a whole
and for evaluating domain subsets based on area/spatial groupings,
management, and/or landscape and other environmental parameters.
53
3. Using the same data, infer statistical distributions of various environmental

impacts to establish percentile rankings of per acre effect levels. Combined
with weights and probabilities, the values reveal total impacts from some
portion of the total domain. The analysis might show, for instance, the 20
percent of acres having the largest per acre effects is responsible for 40 percent
of the total impact.
4. Geospatial analysis of effects a the County, 8-digit Hydrologic Catalog Units
(HUC), and Major Land Resource Area (MLRA) levels.
5. Used without the probabilities and statistical weights in an “experimental
design15 ” mode, the NNLSC provides the means to examine field-level
relationships between management practices (treatments) and environmental
impacts (responses) across regions, climates, and soils (blocks); and
6. Creating alternative projections for scenario planning.16
Figure 12 shows the microsimulation model from an analytical perspective. Various

statistical weights and environmental, management, and model parameter selections are
shown as inputs to the Sample Space Reconciliation (SSR) process and the EPIC
model. The EPIC model, its inputs, and outputs are well documented elsewhere
(Izzaralde et al., 2006; Potter et al., 2006; Williams 1995; Williams et al., 1984).
Inputs to the SSR processes include statistical weights from the NRI, Nutrient,
Manure, and Tillage samples. Concepts from probability and set theory are employed
to set up correct statistical and probabilistic relationships between elements17 in each
sample space18 , full or restricted domains19 , and/or subdomains20 .
Specific SSR functions include:

1) Account for excluded management systems (in sample designs but not
simulated) by normalizing included management weights such that the
magnitude of included weights are proportional to the sample design weights.
15 An experimental unit is a unique resource unit (URU) and on that unit, various levels of commercial
fertilizer rates, application timings, manure applications, and tillage factors are applied.
16 Information on using the NNLSC for scenario planning is forthcoming.
17 An element can be either a model run (or record), URU, Cropshare Point, or NRI Point.
18There are four sample space definitions (InSitu, URU, Cropshare, and Point) for each of the two scenarios
(97bcr and 97NoCP). A sample space is fully populated with all its elements.
19 A domain is the set of elements from a sample space that are included in an analysis. When all elements are
included, a domain is equivalent to a sample space.

20 A subdomain is a subset of a domain in which the sum of combined probabilities for subdomain elements
are set equal to one. Depending on the analysis, a subdomain may be comprised of exclusively assigned
elements or elements can be assigned into multiple subdomains.
54
2) Combine suite of management weights and NRI area weights such that
elements are proportional to management survey designs and correctly
represent NRI-derived area extents.
3) Transform weights from 1 and 2 into probabilities that maintain proportional
management likelihoods and area extents and set the sum of the joint
probabilities for all elements in the sample space equal to one.
4) When analytical domains are restricted by constraints or other selection
criteria (weights or probabilities set to zero for elements not included),
renormalize weights and probabilities of included elements such that the sum
of the joint probabilities for included elements equals one and proportional
representation of non-excluded management systems and area extents are
maintained.
5) As required by analysis renormalize element probabilities such that the sum
of joint probabilities of all elements in subdomains equal one and the sum of
sums equal the number of subdomains.
Outputs from EPIC and the reconciliation process are used in several types of
analyses. Example 1 below demonstrates basic query methods in STAT.
In Aggregation/Group By analysis using InSitu, one or more model run outputs or

element response function values, are multiplied into each element’s joint statistical
weight [NatProb]. The sum of products for all elements (aggregation) equals the total
value for the entire domain of 298 million acres. Dividing the sum of products by the
sum of [NatProb] results in the average per acre rate. One or more Group By fields
can be included in the aggregation.
Queries in Example 3 below provides an example of the method using STAT. Table
A-1 and text in Appendix A illustrates the Aggregation/Group By method by
demonstrating total nitrogen lost with runoff from InSitu, grouped by URU. The
method, shown for a single URU, provides a detailed look at the calculation. Similar
methods were used to develop the URU tables and with further processing and
imputation, the Cropshare, and Point tables.
Aggregating URU, Cropshare and Point are somewhat different since there are no
management weights. However, these too are used in Aggregation/Group By analyses
to report environmental outcomes at various aggregation levels. Aggregation processes
resulted in baseline estimates of environmental impacts as well as per-acre loading
inputs to economic or watershed routing models. A spatially distributed aggregation
method using STAT is demonstrated below in Example 2. In addition, data from
Cropshare and Point can be used within a GIS for geospatial analysis. One method,
not included in this documentation is detailed in Potter et al. (2006)21 .
21Pages 54-60 Model Simulation of Soil Loss, Nutrient Loss, and Change in Soil Organic Carbon Associated with Crop
Production
55
EPIC outputs without weights or probability coefficients may be evaluated by

comparing averaged effects of Functional Observation Groups. This direct
comparison of the input conditions to the output effects allows inferences about the
field-level relationships between management practices and environmental impacts
across regions, climates, and soils. Further uses of non-weighted model outputs could
include testing of management strategies to determine the circumstances under which
practices are most effective and development of screening tools. Use of data mining
techniques could lead to improved understanding of the complex physical processes
such as how interactions between components affect the behavior of the whole
system. Exploration of these approaches could facilitate linkages between model
output and the NRCS performance reporting system guides.
Use of probabilities is illustrated through Example 3 in which cropland situations

needing conservation are identified stochastically.
Figure 12. Microsimulation model from an analysis point of view.
56
STAT Examples
Example 1: Basic Query Using the tables 97bcr_InSitu, defState, and
functions: Group By, Count, defLandUse and the 6 queries exQuery1 through
Sum, Expression, and exQuery1e, this example shows several common query
Where query functions. functions including Group By, Count, Sum, Expression, and
Where.
The series of queries in this example build upon one

another, each becoming slightly more sophisticated. Set of categorical variables
in InSitu that uniquely
Tables and fields are added, query types are changed identify each model run.
and selection criteria are set. The final query produces a
crosstab record set showing the acres per crop for the StateFIPS
CropID
states in CTIC region 4.
ClimateCluster
SoilCluster
By changing the definition tables and grouping fields in IrrigationCode
this set of queries and then saving the resultant queries ConserPractice
with new names, the STAT user can create personalized Tillage
ManureCategory
sets of queries.
NutrientRateCategory
ApplicationTiming
With a little imagination and a good understanding of ApplicationCategory
the 8 datasets provided in NNLSC_DATA.mdb, these
queries can be adapted to many purposes.
FOR ANY ANALYSIS, UNDERSTANDING THE DATA IS MUCH MORE IMPORTANT THAN
UNDERSTANDING THE TOOLS FOR ACCESSING THE DATA.
1. 1exQuery1(below) retrieves all records in the InSitu table, groups the records by
StateFIPS, and counts the number in each group. The query result shows the number
of model runs per state (below right). The query can modified by adding Group By
fields in the query design grid. Deleting the StateFIPS column in the query design grid
returns a single row with a count of all records in the table (768,785).
Run Query For Design View
57
2. 1exQuery1a enhances the basic query by adding the defState table, which enables
replacing StateFIPS with state names. Descriptive names and different data formats
can be added by accessing the field properties. Shown below are the properties for the
ID field which were accessed with a right mouse click on the query field column.
Add Table
3. In 1exQuery1b, another table (defLandUse) and Group By field (CropName) adds

detail; showing the record count by state and crop. The SUM function is used to tally
the RunAcres column to show the acres for each group. Sorting the resultant query
table (called a dynaset in Access) is done by selecting a column and a sort direction (A-
>Z or Z->A).
58
4. 1exQuery1c uses an expression to calculate acres per run for each state-crop group.
Red arrows indicate aggregate function and expressions used in query. Deleting the
two Group By columns (State and CropName) the query result would show the baseline
runs cover 298,478, 000 acres for an average of 388 acres per model run. Add or
change grouping fields by dragging fields from the tables and dropping them into the
design grid. Save changes to the query with a new name using File => Save As on the
Menu Bar.
5. Changing the query type to a crosstab query transposes rows to columns in the
dynaset. In 1exQuery1d (below) we chose row headings, column headings and values
for cells. 1exQuery1e (not illustrated) adds selection criteria to the crosstab query
using the WHERE function.
59
Table 41. Which data table to use?
Any analysis of tillage, nutrient management, or manure

InSitu
management effects.
InSitu Spatial distribution limited to State or climate cluster
Cropshare or
Spatial resolution to County, HUC, and MLRA.
Point
Cropshare or Effects of tillage, nutrient management, or manure
Point management can’t be evaluated.
Grouping by NNLSC crop or evaluating crop-based information
Cropshare
such as yield at any NRI aggregation level.
Aggregation to NRI Point level. NNLSC crop information is not
Point
required.
URU Only table which can be fully exported into EXCEL.
URU Efficiently aggregate to National-level.
Evaluating effects by State, crop, climate, soil, conservation
URU
practice, irrigation or associated characteristics and definitions.
Methods Not Assess tillage, nutrient management, or manure management

Included effects at high spatial resolution.
Example 2: NRI In this example, 97bcr_Cropshares is queried to reproduce the hydrologic

Aggregation and information from table 21 from Model Simulation of Soil Loss, Nutrient Loss, and
Macros Change in Soil Organic Carbon Associated with Crop Production pages 65-66. The table, a
portion of which is reprinted below, contains average annual water inputs and
partitioned losses by region, by crop, and by crop within region. Units are inches
per acre and as a percent of inputs.
60
The first query, 2exQuery2a, a make table query, is shown in part above. The query
joins 97bcr_Cropshares, defLandUse, and defNnlscRegions, selects fields,
calculates values and aggregates results by region and crop. The expression in the
Precipitation column shows how per acre values are calculated and aggregated using:
Sum([Precip]*[Acres])/[SumAcres]22 .
Expressions for per acres rates for total water inputs, losses, and losses as a percent of
inputs are as shown.
The three final queries perform similar functions using

different aggregation groups before appending rows into
Table 21. For example, 2exQuery2b aggregates the
calculated fields by region. When running the query, Access
shows the Enter Parameter Value dialog box requesting a
value to write in the CropName field.
Queries can be manually run sequentially beginning

with 2exQuery2a or the entire series can automated
using a macro. CreateTable21Macro is a macro that
runs multiple queries using the OpenQuery action and
the query name in the action arguments. A simple
method for creating a macro to run multiple queries is
to open a macro window and drag and drop the
Selecting the Macros object in queries into it. Many alternative macro functions (listed
the database window.
22 For calculating totals rather than per acre rates, the expression Sum([Precip]*[Acres]) would be used.
61
below) are available in the Action box enabling the development of complex macros.
Macro Functions
AddMenu MoveSize RunApp
ApplyFilter MsgBox RunCode
Beep OpenDataAccessPage RunCommand
CancelEvent OpenDiagram RunSQL
Close OpenForm RunMacro
CopyDatabaseFile OpenFunction Save
CopyObject OpenModule SelectObject
DeleteObject OpenQuery SendKeys
Echo OpenReport SendObject
FindNext OpenStoredProcedure SetMenuItem
FindRecord OpenTable SetValue
GoToControl OpenView SetWarnings
GoToPage OutputTo ShowAllRecords
GoToRecord PrintOut ShowToolbar
Hourglass Quit StopAllMacros
Macro s and Methods Rename StopMacro The macro window showing actions
of the DoCmd Object RepaintObject TransferDatabase in CreateTable21Macro.
Maximize Requery TransferSpreadsheet
Minimize Restore TransferSQLDatabase
TransferText
Example 3: NNLSC probability analysis provides a means to estimate the likelihood of

Probability various outcomes for different management systems and/or environmental
Analysis
conditions.
Probabilities were estimated from the nutrient, manure, and tillage sample designs
using a relative frequency approach based on the empirical observations
encapsulated by the surveys. Model run outcomes are assigned that probability of
occurrence associated with its management.
The NRI captures the stochastic nature of land use and cover, soils, climate, and
topography. Probabilities for these environmental characteristics, were derived
from the NRI statistical design using a relative area approach. Model run
outcomes are assigned the probability of occurrence associated with NRI-based
environmental characteristics. Properties of NRI characteristics are assigned the
probability for the characteristic.
All outputs for each of the 768,785 model runs are assigned the probability of
occurrence associated with its management and environmental characteristics.
The probability can take any of several forms depending on the domain. For
instance, one form would consider just the management coefficients (derived for
nutrient management practices, manure application rates, and tillage systems) in
which the domain is the URU. For this, one could state “for a given URU, these
management systems, along with the associated outcomes have X probability of
occurrence” or ask, “what is the probability that URU x has a management system
for which USLE exceeds T?” Calculating within group variability could be useful
as well. In most cases the probabilities associated with each URU would carried
62
over to the NRI points, although corn and wheat require an extra step to account
for the grain-silage and winter-spring crop-splits. These probabilities could be
useful in evaluating likely outcomes, thus improving quantification of NPS effects
associated with cropland management.
A second probability form combines the occurrence likelihood of specific field or

resource unit types (defined by the URU or NRI point) to the management
probabilities, thus forming a nationwide probability coefficient in which the
domain includes the entire set of simulations. This national probability factor
allows dissimilar crops, fields, and managements to be juxtaposed. For instance,
one could state, “there is X probability that USLE for an acre of cotton in south
Georgia exceeds the USLE of an acre of soybeans in northeast Iowa.”
Probabilities of this type could prove useful in designing targeted national
programs and policies to efficiently reduce NPS impacts.
Although the data are not included in this database release, another form the
probability factor can assume is by expanding the domain to include the yearly
simulation outputs, in effect providing a climatic likelihood factor, which can be
combined with either aforementioned probability forms. Combined with the
management coefficients in a URU, one can estimate not only the probability that
an outcome associated with a particular management will exceed a given amount,
but will also allow an estimate of how frequently a given threshold will be
exceeded and by which management systems. The consideration of weather and
management practice is a necessary first step to include failure analysis in
conservation planning, without which, long-term benefits are highly
unpredictable/uncertain.
Table 42 defines the probability-type fields in the InSitu tables. Two fields,
[RunAcres] and [NatProb] are most commonly used weights for aggregating.
Others are made available for special analyses not discussed in this version.
Table 42. Definitions of the probability-type fields in the InSitu table.

NutWt Statistical weight for commercial fertilizer applications.
ManWt Statistical weight for manure fertilizer applications.
TillWt Tillage probability coefficient derived from Crop Residue Management Survey
AllWt AllWt = NutWt * ManWt* TillWt
SumWts AllWt summed across each URU. Used for normalization.
Corrected URU acres derived from NRI xfact for NRI points represented in the
URUacres
URU.
Normalized probability (sum of set equals 1) of management represented by
URUprob
runs occurring in URU.. URUprob=Allwt/Sumwts
RunAcres Acres represented by model run. Runacres=URUacres*URUprob
National probability coefficient. Represent the probability occurrence of a
NatProb
similar acre. NatProb = RunAcres / total acres (298,478,000 acres).
63
Summing the [NatProb] field for any aggregation level calculates the total probability
for each aggregation group. Since [NatProb] represents the probability at the national
level, a coefficient of one is returned when [NatProb] is summed across all 768,785
rows. Summing the [RunAcres] field for any aggregation level or restriction criteria
calculates the number of acres for each aggregation group.
The query below, examWts, aggregates several outcome from InSitu using each type
of weight and probabilities. When aggregating domains, probabilistic relationships
between elements are maintained by renormalizing using either [SumProb], [SumWts],
or [SumAcres].
Regardless of the aggregation level or restriction criteria used in selecting domain,
[RunAcres] and [NatProb] used with the [SumProb] and [SumAcres] are the most
robust. [AllWt] and [SumWts] should only be used when aggregating to the URU.
Query: examWts
SELECT [97bcr_InSitu].URUid,
Count([97bcr_InSitu].ID) AS CountOfID,

Sum([97bcr_InSitu].NatProb) AS SumProb,
Sum([97bcr_InSitu].SumWts) AS SumSumWts,
Sum([97bcr_InSitu].AllWt) AS SumWts,
Sum([97bcr_InSitu].RunAcres) AS SumAcres,

Sum([Yield]*[NatProb])/[SumProb] AS Pyield,
Sum([Yield]*[AllWt])/[sumwts] AS wtyield,
Sum([yield]*[runAcres])/[SumAcres] AS ayield,

Sum([USLE]*[NatProb])/[SumProb] AS PUsle,
Sum([USLE]*[AllWt])/[sumwts] AS wtUSLE,
Sum([USLE]*[runAcres])/[SumAcres] AS aUSLE,

Sum([Precip]*[NatProb])/[SumProb] AS Pprecip,
Sum([Precip]*[AllWt])/[sumwts] AS wtPrecip,
Sum([precip]*[runacres])/[SumAcres] AS aPrecip
FROM 97bcr_InSitu
GROUP BY [97bcr_InSitu].URUid
ORDER BY [97bcr_InSitu].URUid;
Partial results from the query examWts.

SumSumWts
SumAcres
SumProb
SumWts
CountID
wtUSLE
aUSLE
wtyield
URUid
Pyield
PUsle
ayield
1 38 9.0459E‐06 36.395 0.95777 2700.00 33.63 33.63 33.63 2.04 2.04 2.04
2 38 4.3554E‐06 36.395 0.95777 1300.00 33.54 33.54 33.54 1.92 1.92 1.92
4 38 8.0408E‐06 36.395 0.95777 2400.00 35.86 35.86 35.86 2.43 2.43 2.43
5 38 4.0204E‐06 36.395 0.95777 1200.00 31.94 31.94 31.94 1.72 1.72 1.72
64
Probability Example
Queries in this example demonstrate the use of the probability coefficients.
Assumptions are not intended to be realistic, rather the intention is to help explain the
national probability coefficient or [NatProb].
Assumptions:
1. Assume a domain comprised of two subdomains 1) all Iowa cropland and 2)
south Georgia (climate cluster 12) cotton acres.
2. We must randomly select an acre from the domain on which to install a soil
erosion conservation practice. We want our selection to be one that needs a
soil erosion conservation practice.
3. An erosion rate greater than four tons per acre establishes need.
Questions:
1. What is the probability that a randomly selected acre in south Georgia cotton
would exceed an erosion rate of 4 tons per acre? What is the probability that a
randomly selected acre in Iowa would exceed that same erosion rate?
2. How much better are the odds of selecting an acre needing treatment in south
Georgia than in Iowa?
3. Assuming an erosion rate of seven tons per acre establishes need, how much
better is the probability of an acre in Georgia needing treatment that one in
Iowa?
4. Assuming each state’s annual average erosion rate establishes need, in which
state would a random selection provide the highest probability of selecting an
acre needing treatment? In the state with the highest probability, how much
better are the odds of selecting an acre needing treatment as compared to the
other state?
5. How would restricting the random selection to conventional tillage acres affect
the results?
The query, 3sumP_GaDomain, totals the [NatProb] for the all south Georgia cotton
acres. This result is labeled [ProbGaCotDomain].
A similar query, 3sumP_GaUSLE>X sums the [NatProb] for cotton acres in S.

Georgia (climate cluster 12) where USLE exceeds the entered criteria (in this case 4
tons per acre). Result is labeled [ProbGaUsleExceedX].
The query, 3calcP_GaUSLE>X calculates the probability that a random acre selected
from the south Georgia cotton domain will exceed the USLE criteria by dividing the
65
USLE criteria restricted domain ([ProbGaUsleExceedX]) by the full domain

([ProbGaCotDomain]). The result is labeled [GaExceedProb].
The following three queries perform similar functions for Iowa cropland:
1) 3sumP_IaDomain,
2) 3sumP_IaUSLE>X, and
3) 3calcP_IaUSLE>X.
The query, 3compareProb, compares exceedance probabilities between south Georgia

cotton acres and Iowa cropland as shown in row 2 columns 2-4 the table below.
The USLE criteria in the queries 3sumP_GaUSLE>X and 3sumP_IaUSLE>X were

changed to the erosion rate criteria listed in column 1 and the results from
3compareProb recorded in columns 2 -4.
To estimate the probabilities with the subdomains restricted to

conventional tillage, a column where the tillage criteria equal 1
was added the four queries containing subdomain criteria. The
queries, were run and the results were recorded in columns 5-7.
All Tillage Conventional Tillage Only

How much How much
better are the better are the
odds of odds of
selecting a selecting a
south south
acre needing acre needing
Iowa Georgia Iowa Georgia
treatment in treatment
Probability cotton Probability cotton
Erosion rate south acre in south
Probability Probability
criteria for Georgia Georgia
determining a cotton than in cotton than in
conservation acre Iowa Iowa
needing treatment. cropland? cropland?
USLE >4 tons/acre 0.29 0.77 2.67 0.43 0.86 2.02
USLE >7 tons/acre 0.11 0.43 4.07 0.17 0.55 3.24
USLE >10
0.04 0.33 7.52 0.08 0.43 5.24
tons/acre
IA >3.3 State
t/a
Average
GA 0.36 0.68 1.92 0.53 0.75 1.41
>4.8 Erosion
t/a Rate
66
Example 3. Queries in probability example.

Query Name Description / Function SQL
3sumP_IaDomain Sums the probability ([NatProb]) SELECT Sum([97bcr_InSitu].NatProb) AS ProbIaDomain,
of all elements in the Iowa Count([97bcr_InSitu].ID) AS CountOfID
subdomain FROM 97bcr_InSitu
WHERE ((([97bcr_InSitu].StateFIPS)=19));
3sumP_IaUSLE>X Sums the probability ([NatProb]) SELECT Sum([97bcr_InSitu].NatProb) AS ProbIaUsleExceedX

of those elements in the Iowa FROM 97bcr_InSitu
subdomain where USLE > 4 tons WHERE ((([97bcr_InSitu].StateFIPS)=19) AND
per acre (([97bcr_InSitu].USLE)>4));
3calcP_IaUsle>X Calculates the Iowa subdomain SELECT [ProbIaUsleExceedX]/[ProbIaDomain] AS
exceedance probability. IaExceedProb
FROM 3sumP_IaDomain, [3sumP_IaUSLE>X];
3sumP_GaDomain Sums the probability ([NatProb]) SELECT Sum([97bcr_InSitu].NatProb) AS ProbGaCotDomain,

of all elements in the South FROM 97bcr_InSitu
Georgia Cotton subdomain WHERE ((([97bcr_InSitu].StateFIPS)=13) AND
(([97bcr_InSitu].ClimateCluster)=12) AND
(([97bcr_InSitu].CropID)=5));
3sumP_GaUSLE>X Sums the probability ([NatProb]) SELECT Sum([97bcr_InSitu].NatProb) AS ProbGaUsleExceedX

of those elements in the South FROM 97bcr_InSitu
Georgia Cotton subdomain where WHERE ((([97bcr_InSitu].USLE)>4) AND
USLE > 4 tons per acre (([97bcr_InSitu].StateFIPS)=13) AND
(([97bcr_InSitu].ClimateCluster)=12) AND
(([97bcr_InSitu].CropID)=5));
3calcP_GaUSLE>X Calculates the South Georgia SELECT [ProbGaUsleExceedX]/[ProbGaCotDomain] AS

Cotton subdomain exceedance GaExceedProb
probability. FROM [3sumP_GaUSLE>X], 3sumP_GaDomain;
3compareProb Compares exceedance SELECT [3calcP_IaUSLE>X].IaExceedProb,

probabilities of the two [3calcP_GaUSLE>X].GaExceedProb,
subdomains. [gaexceedprob]/[iaexceedprob] AS GA_FavorableSelectionOdds
FROM [3calcP_IaUSLE>X], [3calcP_GaUSLE>X];
Example 4. Examining the relationship between EPIC outputs and input

Comparative Analysis of conditions without weights or probability coefficients is useful
Functional Observation in examining field-level relationships between management
Groups practices and environmental impacts across regions, climates,
and soils.
One type of analysis on these data aim to identify the relative differences in effects
between groups of model outputs (which can be thought of as observations).
Investigators usually attempt to attribute between groups differences to functional
characteristics of the groups, calculate within group variability, and identify correlations
and/or cause-effects relationships.
Setting up the data for this type of analysis is covered in this example using the query
FogQ1. In the example the purpose is to compare effects of different tillage systems
on erosion. Model outputs were averaged across functional observation groups.
67
Because of the complexity of the data, we reduced confounding factors using the
following groups:
Climate Temperature (Thermic or Mesic);
Climate Moisture (Arid, Semi-arid, Sub-humid, Humid, and Sub-tropical);
Land-use (Legume Row Crop, Non-legume Row Crop, Small Grain) (Legume
Hay and Non-legume Hay are not considered since each was simulated as no-
till)
Soil Texture (Fine, Moderately Fine, Medium, Moderately Coarse, Coarse,
Organic, and Other); and
Soil Hydrologic Group: (A, B, C, and D).
Outputs from the runs are grouped to minimize confounding variation within
each group. Grouping categories include region, crop, soil texture class, soil
hydrologic group, irrigation class, and nutrient management scheme. Within each
group, input functions and response functions are calculated as the mean values
from all model inputs or outcomes.
The query FogQ2 calculated the reduction in erosion between conventional-till and
no-till. Query FogQ3 restricts and sorts the result.
A second example (query is FogSlopeClassQ1) of comparative analysis of functional

observation groups showing average USLE soil erosion when grouped by slope class.
With only 7 groupings, there is a great deal of within group variability. The query,
FogSlopeClassQ2, adds climate class to the analysis, which increases the number of
groups but reduces within group variability.
68
Table 43. Supplementary queries.

Query Name Query Description / Function
Calculates weighted average outputs (per acre) from InSitu and
aggregates to URU where State = 19 and CropID = 2 and Yield >80. Query
aggInSituURU provides a good example of renormalizing weights when restricting the
domain. (In this case all nutrient and tillage managements in Iowa corn
resulting in less than 80 bu/acre were excluded.)
calcAllRegCrop Weighted totals by region and crop.
calcCountyYields Calculates per acre crop yields by county.
calcOutbyHsgTill Calculated weighted per acre outputs by HSG and tillage.
calcOutbyStateCrop Calculated weighted per acre outputs by state and crop.
Calculates weighted per acre outputs by state, crop, and manure
calcOutbyStCropMan
category.
Calculates weighted per acre outputs form InSitu by Temperature class,
calcPerAcrebyT_M_C_I_T
Moisture Class Crop, Irrigation, and Tillage. Sorts by highest USLE.
Calculates weighted average model outputs (totals) from Cropshare by
calcTotalsbyHucCrop
HUC‐Crop.
Calculates per acre erosion from URU and other outcomes by 7 texture
calcUruOutbySoilChar
classes and 4 HGS.
convertSI Output converted to SI units
countCPbyPoints Counts NRI points and sums acres in each conservation practice.
countPointsbyHUC Counts NRI points and sums acres by HUC
countPointsbyIrrRegion Counts NRI points and sums acres by irrigation within regions.
Count NRI points, sums acres and calculates per acre erosion by Land
countPointsLCC
Capability Class.
Calculates weighted average model outputs (totals) from Cropshare by
getRegionCropTotals
region‐crop.
sumTillAcresByCrop Sums acres by crop‐tillage
sumTillProbByCrop Calculates matrix of probabilities by each crop‐tillage.
sumXfactbyHsgRegion Sums acres in each HSG by region.
What Prob National Erosion Sums national probability where erosion meets criteria entered in query.
69
References
Campbell, Todd. 2005. “I_EPIC - EPIC model control system for Windows”. URL:
http://www.public.iastate.edu/~elvis/i_epic_main.html
Conservation Technology Information Center (CTIC). 2001. Crop Residue
Management Surveys, 1987–2000. Data Product, CTIC, Purdue University, West
Lafayette, IN
Izaurralde, R. C., J. R. Williams, W. B. McGill, N. J. Rosenberg, and M. C. Quiroga
Jakas. 2006. Simulating soil C dynamics with EPIC: model description and testing
against long-term data. Ecological Modelling, 192, 362-384.
McCarl, B. A., C. C. Chang, J. D. Atwood, W. I. Nayda. 1993. Documentation of
ASM: The U.S. Agricultural Sector Model. Unpubl. Tech. Report. Department of
Agricultural Economics. Texas A&M University. College Station, TX
Potter, Steven R., Susan Andrews, Jay D. Atwood, Robert L. Kellogg, Jerry
Lemunyon, M. Lee Norfleet, and Dean Oman. 2006. Model Simulation of Soil Loss,
Nutrient Loss, and Change in Soil Organic Carbon Associated with Crop Production. U.S.
Department of Agriculture, Natural Resources Conservation Service, Washington,
DC. 267 pgs. Available online at URL:
http://www.nrcs.usda.gov/technical/nri/ceap/croplandreport/
United States Department of Agriculture, Economic Research Service. 2001.
Agricultural Resource Management Study (ARMS). Available online at URL:
http://www.ers.usda.gov/data/arms/
United States Department of Agriculture, Economic Research Service. 2000. Cropping
Practice Surveys, 1990-1995. Electronic data products, stock Nos. 93018a to 93018f.
U.S. Dept. Agriculture, Economic Research Service. Washington, DC.
United States Department of Agriculture, National Agricultural Statistics Service. 1999.
The 1997 Census of Agriculture. Database available online at URL:
http://www.nass.usda.gov/census/
United States Department of Agriculture. Natural Resources Conservation Service.
2000. The 1997 National Resources Inventory. Data CD available NRCS, National
Cartography and Geospatial Center. P. O. Box 6567. Fort Worth, TX 76115.
Willimas, J.R. 1995. "Chapter 25: The EPIC Model," in Vijay P. Singh (ed.), Computer
Models of Watershed Hydrology, Water Resources Publications, Highlands Ranch,
Colorado.
Williams, J.R., C.A. Jones, and P.T. Dyke. 1984. A modeling approach to determining
the relationship between erosion and soil productivity. Trans. ASAE 27:129-144.
70
Appendix A
More information about the microsimulation model and the scheme for
making multiple model runs.
The modeling approach used in this study is based on microsimulation modeling

techniques that were originally developed by economists investigating the economic
impact of public policy. Microeconomic simulation models consist of microdata on
characteristics of individuals obtained from statistically designed surveys and response
functions that predict behavior of individuals. Macroeconomic outcomes are then
obtained by aggregating predicted outcomes of individuals represented in the sample.
The statistical sample design provides the basis for the aggregation.
Microsimulation A similar modeling approach was used to create the NNLSC. The
Modeling statistical sampling framework of the 1997 National Resources
Approach
Inventory (NRI) provided the microdata on land use and site
characterizations for a set of cropland sample points. Probabilistic
data on farm-level management were derived from farmer surveys and national level
databases. Other databases provided climate statistics, soil attribute information, plant
growth parameters, and factors defining farm equipment effects. These data were
combined in a field-level fate and transport process model23 to estimate the loss of
materials from representative farm fields and other outcomes such as the change in soil
organic carbon. The statistical sample weight associated with each sample point is used
to aggregate the model outputs to the national or regional level. The resulting
simulation model captures the diversity of land use, soils, climate, and topography from
the NRI sample points, estimates the loss of materials from farm fields at the field scale
where the science is best developed, and provides a statistical basis for aggregating
results to the national and regional levels.
More on the NRI The United States National Resources Inventory24 (NRI) is a
Microsimulation longitudinal survey of land use and land cover conducted on a
Domain nationwide sample of approximately 300,000 area segments.
NRI uses a stratified two-stage unequal probability area sample. The first stage sample
unit – primary sample unit (PSU) – is an area or segment of land. The segments vary in
size from 16 to 256 hectares (40-640 acres). Sampling rates vary across strata, but are
typically between 2% and 6%. There are about 300,000 sample segments in the current
national sample. The second stage of sampling is one or more points within the PSU.
Data are collected for the segments as a whole and for points within the segments.
23 The physical process model EPIC (Environmental Policy Integrated Climate) is used to generate estimates
of soil loss, loss of nutrients, and change in soil organic carbon for the 1997 NRI cropland sample points.
Version 3060 of EPIC was used. The Interactive-EPIC (I-EPIC) software was used to manage and automate
batch model runs. An application program called RunBuilder was developed to automate data assembly.
24 For more information on the NRI, see www.nrcs.usda.gov/technical/NRI/.
71
Generally, there are three points per segment, but some segments only contain one or
two points. Overall, there are about 800,000 sample points in the current NRI, about
300,000 of which are cropland points. At each sample point, information is collected
on nearly 200 attributes including land use and cover, soil type, cropping history,
conservation practices, erosion potential, water and wind erosion estimates, wetlands,
wildlife habitat, vegetative cover conditions, and irrigation method. Data gathered in
the NRI are linked to NRCS Soil Survey databases and can be linked spatially to
climate databases. Thus, the NRI sampling frame captures the diversity of the Nation’s
agricultural resource base (soils, topography, and climate), which is a critical factor in
assessing the contribution of conservation practices to the reduction of environmental
impacts associated with agricultural activities. For each NRI sample point, a statistical
weight (unit = 100 acres) is specified which allows grouping and aggregation of
estimates from multiple points. A unique identifier consisting of county fips, psu,
point, and psuedo point identifies individual sample points.
Understanding what each data table represents is critical to using the NNLSC data
correctly and making a valid analysis. In developing the microsimulation modeling
domain, 178 thousand NRI sample points were first split into 225 thousand NRI-
Cropshare points and then statistically clustered into a domain of approximately 25
thousand Unique Resource Units (URU). The URU domain was combined with sets
of probable management systems and expanded out into the 768 thousand cropland
situations. EPIC model outputs for these were reported as 30-year average annual
estimates in the 97bcrInSitu table.
To move data from 97bcrInSitu to the other three tables, the process was reversed.
The data were aggregated using a probabilistic weighting function to remove the
probable managements, resulting in the URU table. The 25,250 URU data were de-
clustered and imputed to the NRI-cropshare points resulting in the Cropshare table.
These data were then aggregated and the results were stored in the Point. table.
Example illustrating Table A-1 provides an example of how the NRI value for nitrate loss in runoff was
method for applying determined for URU 7462. Sprinkler irrigated corn is grown in this URU located in
weights and
Nebraska within climate cluster 27, which encompasses the northwest portion of the
aggregating estimates.
state. The soil is a Blendon fine sandy loam and conservation practices (terraces,
contour farming, and strip cropping) are not present. Nutrient management options
based on the Cropping Practices database for Nebraska corn consisted of 21 nutrient
application time and rate combinations for commercial fertilizer applications25 and two
manure fertilizer options. The 23 nutrient management options were replicated for
each of the three tillage systems--conventional-till, mulch-till, and no-till, resulting in a
total of 69 management options for the URU. Each management option requires a
unique set of field operations to simulate the management option using EPIC.
Probabilities associated with each tillage type, manure option, and commercial fertilizer
25 Specific options and probabilities of occurrence are shown in table 15 in Model Simulation of Soil Loss,
Nutrient Loss, and Change in Soil Organic Carbon Associated with Crop Production.
72
option are shown in table A-1. The joint probability for the management system is the
multiple of the three probabilities, also shown in table A-1. The weighted model output
is then calculated for each of the 69 model runs (shown in the last column in table A-1)
and summed to obtain the weighted average for the URU. As shown in the last row of
table A-1, the weighted estimate of average annual nitrogen lost in runoff is 4.52
pounds per acre for this example.
This value was then assigned to each of the 5 Cropshare points associated with this
URU. Corn for grain (crop id = 2) and corn for silage (crop id = 29) cropshare points
were combined into a single NRI point by calculating the weighted average using the
“Acres” field in Cropshare to establish the relative proportions of each crop. All
model results were calculated in this same manner for each URU and assigned to NRI
cropland sample points associated with each URU.
National and regional estimates of soil loss, loss of nutrients, and change in soil organic
carbon were derived from the EPIC model outputs estimated for each NRI cropland
sample point. Aggregated estimates were produced using the statistical sample weight
(i.e., expansion factor, or acreage weight) associated with each NRI sample point. In
the case of per-acre estimates, the expansion factors were used to derive weighted
averages. In the case of total loss estimates, the expansion factors served as acreage
estimates. In addition, maps showing the spatial distribution of EPIC model outputs
were derived from estimates for NRI cropland sample points.
73
Table A-1. Example of how EPIC-generated variables were estimated for NRI cropland sample points
Average Annual Commercial Manure Tillage Joint probability Weighted model
Fertilizer Application Manure
Tillage Application Time Nitrogen lost in fertilizer option application option option of management output for nitrogen
Rate Application
Runoff (lbs/acre)* probability probability probability system in runoff
Conventional Fall High N Average P No Manure 6.45 0.0173 0.8921 0.5066 0.00782 0.0504
Conventional Spring High N Average P No Manure 8.48 0.0370 0.8921 0.5066 0.01672 0.1418
Conventional Fall and At Plant High N Average P No Manure 6.65 0.0379 0.8921 0.5066 0.01713 0.1140
Conventional Spring and At Plant High N Average P No Manure 7.81 0.0864 0.8921 0.5066 0.03905 0.3048
Conventional At Plant and After Plant High N Average P No Manure 14.50 0.0996 0.8921 0.5066 0.04502 0.6528
Conventional Fall High N Zero P No Manure 6.45 0.0123 0.8921 0.5066 0.00556 0.0359
Conventional Spring High N Zero P No Manure 5.22 0.0428 0.8921 0.5066 0.01934 0.1010
Conventional Fall Medium N Average P No Manure 6.04 0.0099 0.8921 0.5066 0.00447 0.0270
Conventional Spring Medium N Average P No Manure 5.50 0.0379 0.8921 0.5066 0.01713 0.0942
Conventional Fall and At Plant Medium N Average P No Manure 4.92 0.0428 0.8921 0.5066 0.01934 0.0952
Conventional Spring and At Plant Medium N Average P No Manure 5.47 0.0864 0.8921 0.5066 0.03905 0.2135
Conventional At Plant and After Plant Medium N Average P No Manure 6.22 0.1012 0.8921 0.5066 0.04574 0.2847
Conventional Fall Medium N Zero P No Manure 6.65 0.0263 0.8921 0.5066 0.01189 0.0790
Conventional Spring Medium N Zero P No Manure 2.43 0.0395 0.8921 0.5066 0.01785 0.0434
Conventional Fall Low N Average P No Manure 1.54 0.0132 0.8921 0.5066 0.00597 0.0092
Conventional Spring Low N Average P No Manure 2.06 0.0247 0.8921 0.5066 0.01116 0.0230
Conventional Fall and At Plant Low N Average P No Manure 2.39 0.0370 0.8921 0.5066 0.01672 0.0399
Conventional Spring and At Plant Low N Average P No Manure 2.54 0.0872 0.8921 0.5066 0.03941 0.1003
Conventional At Plant and After Plant Low N Average P No Manure 2.16 0.0955 0.8921 0.5066 0.04316 0.0930
Conventional Fall Low N Zero P No Manure 1.42 0.0189 0.8921 0.5066 0.00854 0.0121
Conventional Spring Low N Zero P No Manure 1.24 0.0461 0.8921 0.5066 0.02084 0.0258
Conventional At plant Derived Manure Producer 0.87 1.0000 0.0276 0.5066 0.01400 0.0122
Conventional At plant Derived Manure Receiver 1.42 1.0000 0.0803 0.5066 0.04069 0.0580
Mulch Fall High N Average P No Manure 5.70 0.0173 0.8921 0.2787 0.00430 0.0245
Mulch Spring High N Average P No Manure 8.22 0.0370 0.8921 0.2787 0.00920 0.0757
Mulch Fall and At Plant High N Average P No Manure 5.73 0.0379 0.8921 0.2787 0.00942 0.0540
Mulch Spring and At Plant High N Average P No Manure 6.87 0.0864 0.8921 0.2787 0.02148 0.1476
Mulch At Plant and After Plant High N Average P No Manure 14.46 0.0996 0.8921 0.2787 0.02476 0.3582
Mulch Fall High N Zero P No Manure 5.53 0.0123 0.8921 0.2787 0.00306 0.0169
Mulch Spring High N Zero P No Manure 3.90 0.0428 0.8921 0.2787 0.01064 0.0415
Mulch Fall Medium N Average P No Manure 5.24 0.0099 0.8921 0.2787 0.00246 0.0129
Mulch Spring Medium N Average P No Manure 4.20 0.0379 0.8921 0.2787 0.00942 0.0395
Mulch Fall and At Plant Medium N Average P No Manure 4.13 0.0428 0.8921 0.2787 0.01064 0.0440
Mulch Spring and At Plant Medium N Average P No Manure 4.38 0.0864 0.8921 0.2787 0.02148 0.0942
Mulch At Plant and After Plant Medium N Average P No Manure 5.25 0.1012 0.8921 0.2787 0.02516 0.1321
Mulch Fall Medium N Zero P No Manure 6.03 0.0263 0.8921 0.2787 0.00654 0.0394
Mulch Spring Medium N Zero P No Manure 1.69 0.0395 0.8921 0.2787 0.00982 0.0166
Mulch Fall Low N Average P No Manure 1.04 0.0132 0.8921 0.2787 0.00328 0.0034
Mulch Spring Low N Average P No Manure 1.36 0.0247 0.8921 0.2787 0.00614 0.0084
Mulch Fall and At Plant Low N Average P No Manure 1.85 0.0370 0.8921 0.2787 0.00920 0.0170
Mulch Spring and At Plant Low N Average P No Manure 2.02 0.0872 0.8921 0.2787 0.02168 0.0438
Mulch At Plant and After Plant Low N Average P No Manure 2.29 0.0955 0.8921 0.2787 0.02375 0.0543
74
Average Annual Commercial Manure Tillage Joint probability Weighted model

Fertilizer Application Manure
Tillage Application Time Nitrogen lost in fertilizer option application option option of management output for nitrogen
Rate Application
Runoff (lbs/acre)* probability probability probability system in runoff
Mulch Fall Low N Zero P No Manure 0.92 0.0189 0.8921 0.2787 0.00470 0.0043
Mulch Spring Low N Zero P No Manure 0.83 0.0461 0.8921 0.2787 0.01146 0.0095
Mulch At plant Derived Manure Producer 0.80 1.0000 0.0276 0.2787 0.00770 0.0062
Mulch At plant Derived Manure Receiver 1.32 1.0000 0.0803 0.2787 0.02238 0.0296
No-till Fall High N Average P No Manure 2.32 0.0173 0.8921 0.2147 0.00331 0.0077
No-till Spring High N Average P No Manure 6.83 0.0370 0.8921 0.2147 0.00709 0.0484
No-till Fall and At Plant High N Average P No Manure 2.36 0.0379 0.8921 0.2147 0.00726 0.0171
No-till Spring and At Plant High N Average P No Manure 3.74 0.0864 0.8921 0.2147 0.01655 0.0619
No-till At Plant and After Plant High N Average P No Manure 13.17 0.0996 0.8921 0.2147 0.01908 0.2512
No-till Fall High N Zero P No Manure 2.27 0.0123 0.8921 0.2147 0.00236 0.0053
No-till Spring High N Zero P No Manure 1.32 0.0428 0.8921 0.2147 0.00820 0.0108
No-till Fall Medium N Average P No Manure 1.89 0.0099 0.8921 0.2147 0.00190 0.0036
No-till Spring Medium N Average P No Manure 1.32 0.0379 0.8921 0.2147 0.00726 0.0096
No-till Fall and At Plant Medium N Average P No Manure 1.44 0.0428 0.8921 0.2147 0.00820 0.0118
No-till Spring and At Plant Medium N Average P No Manure 2.00 0.0864 0.8921 0.2147 0.01655 0.0332
No-till At Plant and After Plant Medium N Average P No Manure 2.47 0.1012 0.8921 0.2147 0.01938 0.0479
No-till Fall Medium N Zero P No Manure 6.33 0.0263 0.8921 0.2147 0.00504 0.0319
No-till Spring Medium N Zero P No Manure 0.58 0.0395 0.8921 0.2147 0.00757 0.0044
No-till Fall Low N Average P No Manure 0.74 0.0132 0.8921 0.2147 0.00253 0.0019
No-till Spring Low N Average P No Manure 0.67 0.0247 0.8921 0.2147 0.00473 0.0032
No-till Fall and At Plant Low N Average P No Manure 1.18 0.0370 0.8921 0.2147 0.00709 0.0084
No-till Spring and At Plant Low N Average P No Manure 1.30 0.0872 0.8921 0.2147 0.01670 0.0217
No-till At Plant and After Plant Low N Average P No Manure 1.49 0.0955 0.8921 0.2147 0.01829 0.0272
No-till Fall Low N Zero P No Manure 0.59 0.0189 0.8921 0.2147 0.00362 0.0021
No-till Spring Low N Zero P No Manure 0.40 0.0461 0.8921 0.2147 0.00883 0.0036
No-till At plant Derived Manure Producer 0.68 1.0000 0.0276 0.2147 0.00593 0.0040
No-till At plant Derived Manure Receiver 0.99 1.0000 0.0803 0.2147 0.01724 0.0170
Totals for URU 7462 1.00 4.52
75
Overview of the A simple schematic of the modeling system is illustrated in figure A-1. The process works
Modeling System differently than in many other modeling systems. In a relatively short time, we build and
and the Scheme for run thousands of model input datasets that cover a multitude of soil-climate-crop-
Making Multiple
management practice combinations. Once the model runs output are screened and
Model Runs
validated, the model input and output data are stored in a systems of databases called the
Library of Runs. Simulation models (shown in figure A-1 as an Area Distribution Model)
are developed to answer specific questions. These simulation models retrieve the necessary
model data from the Library, factor those data with management probability weights, and impute the
weighted data onto specific NRI points. Using classifications associated with the NRI (e.g. region, land
use class, soil hydrologic group, etc.) the imputed data are aggregated and results are reported as
weighted average annual effects. As input data, scientific knowledge, or models improve; we build new
sets of input data and recreate the model runs to replace or supplement the Library of Runs.
Figure A-1. A simple schematic of the NNLD modeling system.
RunBuilder is a program that quickly builds many (hundreds of thousands) EPIC model run input sets in
RunBuilder
MS Access databases so that the i_EPIC interface can control and automate individual EPIC
runs. These input sets represent many geographic areas, soils, climates, crops, and
management practices. The Visual Basic program combines descriptive environmental
characteristics of an area with the appropriate tillage budget, seeding rate, chemical fertilizer, manure
application, and other management data and then assembles these data into individual model runs stored
within relational databases setup for model run input using i_EPIC. In addition, RunBuilder schedules
each field operation by calculating the average daily accumulation of heat units for the climate and sets
the earliest allowable date for each operation. Every model run is identified by a unique id which is
maintained with all data associated with the model run including the specific set categorization variables
describing the run, the set of operations performed on the field, and the model run output.
Model Run Database Figure A-2 shows the collection of data RunBuilder uses to populate three run-
Tables Populated by specific tables (Control Records, Parameters, and Field Operations) with model run
RunBuilder inputs. A control record (one row in the Control Records table) is the spatial and
historical description of a physical location that is used for a single EPIC run.
Multiple records are stored, each as a single row, in the Control Records table. Each record contains
about 70 parameters for each model run including the run id number and run description, location and
76
site information, weather, soil, and management practice codes. Additional parameters provide for
control of various modeling options within EPIC and for setting the initial conditions for several
variables.
The Field Operations table contains the specific operations performed on the field for each run in the
Control Records table. The entire budget for an individual model run consists of multiple rows while a
single row describes one specific management operation (such as a disking, planting, harvesting,
irrigating, or fertilizer application) that is performed on a field during the year. A budget for an individual
run is identified by the run id number and each row contains a month and day, operation type code,
along with parameters directly related to the operation type. RunBuilder establishes the timing for each
operation using heat unit scheduling and records the date for each operation.
The Parameters table contains the EPIC S-curve shape parameter values (SCRP), miscellaneous and
experimental parameter values (PARM), and input cost for fertilizer, fuel, and water. A single row,
identified by the run id number, stores the data for one model run.
State Link
Heat Units by Day stateFIPS Legend:
climate cluster id Tillage Schedules
climate cluster id RunBuilder output tables
soil cluster id Tillage Station Heat Units
date
dry Irrigation Code ID (climate cluster)
phu_zero RunBuilder input tables
pressure type maturity days
phu_corn
gravity crop phu
slope data plant phu
slope len plant julian PHU
Manure Applications plant date
StateFips Seeding Rates Program
Climate Cluster ID State Group
Crop NRI and
dry Control Records
Scenario irr
other data
ID
Manure Category
State FIPS Weather
ManN
Soil ID ID (Climate Cluster)
ManP
Tillage Data
FertN
Irrigation Code
Climate Cluster
Nutrient Applications Application Category
State Group code Nutrient Rate Category
Crop Application Timing
Planting Date
Application Category
RunBuilder run data/settings
Manure Category
Nutrient Rate Category
Application Time Timing Offset
Parameters
First N rate Definitions ID
Second N rate Application Timing Nutrient State Parameters
Phosphorus Rate N1 offset Groups
Phosphorus Application Time N2 offset
First N Knifed/Injected %
Second N Knifed/Injected %
P offset
state group
state fips Field Operations I-EPIC
ID
Ave. Nonzero Yield Fertilizer
NA for Manure Soil_Clus_Site Year
Dry/Irr Fert. Code
State Group code Month
Mineral Nitrogen soil cluster id
Crop Day
Mineral Phosphorus state FIPS
Dry/Irr code Type
Mineral Potassium lenslope
Manure Category Crop ID
Organic Nitrogen slope
Nutrient Rate Category parameters 1 - 7
Organic Phosphorus data
Application Time
Ammonia Nitrogen
Nitrogen Rate
Organic Carbon
Phosphorus Rate
Phosphorus Application Time
Figure A-2 RunBuilder tables and data structure.

Tables Used by
State Link. Table contains the set of modeling units unique resource units (URU) that
RunBuilder form the basis of the modeling system. Each URU consists of a climate zone, a soil
cluster, a specific state, a specific crop, one of three irrigation types including no
irrigation, and one of 8 combinations of three conservation practices (contour farming,
strip farming, and terraces) including no practices. URUs are derived from the NRI and for modeling,
each URU is treated as a single homogeneous farm field. There are 25,250 URUs representing cropland
77
and 7679 representing pasture land. RunBuilder retrieves state, crop, climate zone, soil type, irrigation
system, and conservation practice identifiers as well as several other variables from the state link table.
Tillage Schedule. Contains the generic tillage budgets and has soil preparation, planting, cultivating, and
harvesting operations for each cropping system (combination of crop and irrigation type). In the
irrigated systems, there are operations for turning the auto-irrigation functions on/off, specifying the
date and amount for manual irrigation applications, setting auto-irrigate water stress factors, and building
furrows where necessary.
Station Heat Units. Table contains the earliest allowable plant date, the minimum number of heat units
required before planting, a no-till planting date differential, the number of days to crop maturation, and
the total heat units needed for maturation for each crops by climate zone.
Heat Units by Day. Contains average annual accumulated heat units for the zero base temperature and
each crop base temperature for each climate zone. RunBuilder uses this table to set the HUSC for each
operation by converting the proportional daily intervals between operations from the generic tillage
schedules in to HUSC based on daily heat unit accumulation. The table is also used to convert the daily
interval of fertilizer applications into HUSC.
Seeding Rate. Contains the dry and irrigated seeding rates for each crop by state-group.
Nutrient Applications. Contains the chemical N and P commercial fertilizer quantities for each rate,
timing, and dry/irrigated category that are applied to a crop in a state or state-group area. Also, the
percent of N that is knifed or injected is quantified. The amounts were derived from the CPS.
Timing Offset Definitions (Application Timing). Table describes the nutrient timing schema for the 10
timing categories. Application dates are set relative to planting or harvest dates and are 30 days before
planting, at plant, 30 days after plant or 30 days after harvest.
Manure Applications. Contains the manure application rates for the four manure categories (2 baselines:
Receiver and Producer; and 2 for a scenario analysis: N-standard and P-standard). Table also quantifies
any supplemental chemical N and P fertilizers used with the manure applications.
Fertilizer. Table describes the mineral N, organic N, NH3, mineral P, organic P, and organic carbon
proportions of each listed fertilizer. Note that manure is applied as a fertilizer and the different types
used in the NNLSC described in this table. Each fertilizer is identified by a code, which RunBuilder
writes in the appropriate Field Operation rows.
Climate Cluster Weather Stations. Table cross-references the climate zone id to the weather station id for
input to the control record.
Rotations. Contains the crop rotation schemes used in the NNLSC. Each sequence is identified by a
unique id. Except for testing, the NNLSC currently uses only continuous cropping schemes. In these
continuous systems the crop id and the rotation id are the same.
Operations. Each line in table represents a type of operation and contains the coefficients that describe
the field effects of the machinery operation including tillage depth, mixing efficiency, surface roughness,
ridge height and interval, and the fraction of soil compacted. Additional parameters list the various
78
economic costs of the equipment. Each operation is identified by an operation code, which is also listed
in the Tillage Schedule and the Field Operations tables. Table A-3 describes those variables contained in
the Operations table.
The RunBuilder
The first step in building the model runs was to replicate input database template and
Process name the new databases. In the NNLSC, over 50 separate Access databases were
required. For each of these databases, the state and crops to build were selected and
the RunBuilder program was invoked. The general operation of the program
proceeded as follows:
1. Opens tables, sets up indexes, sets or resets variables, flags, etc. to default values.
2. Program retrieves first URU in state link table that matches the selected state and crop
3. Sets hydrologic condition to 1 if grain, hay, or pasture; or 2 if silage.
4. Retrieves and sets seed rate for state-crop-dry/irrigated.
5. Sets the slope, slope length, and P factor variables.
6. Sets the first Tillage type variable to build.
7. Checks Irrigation type
a. If slope >0.03, Changes Irrigation = 2 to Irrigation = 1
b. If till = 4 and crop is not hay/pasture Changes Irrigation = 2 to Irrigation = 1
c. Sets irrigation related variables (IRI, BRI, EFI, VIMX, ARMN, ARMX).
8. Sets Weather Station ID from Climate Cluster table.
9. Sets first Manure Category (1 to 5)
10. For ManCat = 1
a. Searches NA table for crop to match on State-Crop-Dry/Irrigated
b. If Match, For Each Rate and Timing Category,
Sets App Cat, Rate Cat, and Time Cat variables.
Set Nrate 1, Nrate2, and Prate variables from NA table
Converts N rates and P rates from lb/ac to kg/ha (Nrate x 1.120197 and Prate x 1.120197 x
0.44)
c. If No Match (State-Crop-Dry/Irr),
Retrieve Nrate 1 and Prate variables from Fill Gap Final table
Convert Nrate and Prate from lb/ac to kg/ha (Nrate x 1.120197 and Prate x 1.120197)
11. For ManCat 2 & 3
a. Search MA table to match on State-Climate-crop-Scenario-Manure Category-Yield Class
b. If Match, Sets Man N and Man P variables.
c. Convert Nrate and Prate from lb/ac to kg/ha (Nrate x 1.120197 and Prate x 1.120197)
12. For ManCat 4 & 5
a. Set lenslope and Pfactor values based on Tillage from State Link table
b. Set Nutrient Rate Category = 12 & Application Timing = 12
c. Search MA table to match on State-Climate-crop-Scenario-Manure Category-Yield Class
d. If Match, Set Nrate 1 and Prate = 0
13. Retrieves Plant Day and Plant PHU and Total PHU from SHU Table
a. If no-till, adjusts Plant Day for all crops except crops 41, 46, 47 & 60
b. Writes planting operation in FO table.
14. Sets harvest operation date using HU to harvest and writes in FO table.
15. Sets kill operation date and writes in FO table.
16. Compares Plant Date (from TS) and Plant Day (from SHU) and sets offset for other operations.
17. Sets other operation dates and writes in FO table.
18. Calls writeNutAppRows (to write nutrient application rows in FO table).
a. Sets application timing offsets from Timing Offset table.
b. Sets dates for nutrient applications.
79
c. Checks for knifed or injected value and sets Parm2

d. Sets Parm7 (% tot HU at which operation occurs).
e. Writes 1st N row in Field Operations (FO) table.
f. Sets anhydrous application depth based on date.
g. Sets other nutrient dates and parms and writes rows. (2nd N) in similar manner as above.
19. Writes Manure Application rows in FO table.
20. Calls writeControlRecord
a. Sets simulation length based on number of crops in rotation (1 = 40, 2 = 80, 3 =120)
b. Sets other values (defaults are hard-coded, others are retrieved as variables set previously).
c. Writes row into Control Record table.
21. Calls writeParametersRecord
a. Sets Minimum C Factor and Water Erosion Cover Factor variables based on tillage.
b. Sets N Fixation Rate
For soybeans, peanuts and Alfalfa in ManCat 2, 3 & 4 set to 1
All other crops for ManCat 2, 3 & 4 set to 0.05
All crops for ManCat 1 & 5 set to 0.50
c. Other parameters are defaults (contained in Parameters Template table).
d. Writes row in Parameters table.
22. Finds next match in SL table….
23. Starts next crop…
Starts next state…
The i_EPIC software is a windows-based program that interfaces between the input
The i_EPIC
Interface
databases and the EPIC model to manage and automate large numbers of individual
EPIC runs. The data structure used by the i_EPIC are shown in Figure A-3 and Table
A-2 lists the data input and output tables required by i_EPIC.
Input tables include the three run–specific tables written by RunBuilder, as well as tables containing data
common to all runs. Common tables include information and coefficients required by the EPIC model
describing crop growth, soil properties, machinery characteristics, and climate.
Provisions are made for storing both yearly output and average annual output from the EPIC model.
The Output Annual table contains annual EPIC model outputs such as runoff, USLE soil loss, N lost in
leachate, and organic P lost with sediment as well as the amount of precipitation, irrigation water, and
applied fertilizers. Stored in a separate row for each year of each model run, rows are uniquely identified
by the run ID and run year. The Output Annual Crop Yields table contains crop yield estimated each
year by EPIC. Unique rows are identified by run ID and run year. Yields are stored as completely dry
biomass (no moisture) in metric tons per hectare.
Using a relational database system (MS Access) to manage, store, and organize the model input data and
the EPIC output is more manageable than maintaining thousands of individual ‘run’ data files. In
addition, a relational database avoids storing redundant data by linking the model run databases to
associated databases containing information that is common to many runs.
Essentially, the i_EPIC program operates by 1) converting the input data for a single run into the EPIC
format, 2) invoking EPIC, 3) cataloging the EPIC output, and 4) repeating the process for the next run.
80
Each run takes about 1.1 – 1.5 seconds on a current computer and yearly outputs from EPIC are written
into database tables by i_EPIC as each run occurs. Approximately fifty thousand runs (limited by size
limits in MS Access) can be completed without user intervention. According to Gassman et al., (2002)
the database is read into i_EPIC using a standard Windows read function. Then the user selects one of
four EPIC versions through the configuration command under the file menu. i_EPIC provides a user-
friendly interface for examining and modifying input parameter values, running single or multiple model
runs, and examining model outputs. The i_EPIC software is accessible on-line by going to
http://www.public.iastate.edu/~elvis and clicking on i_EPIC.
Legend:
Heat Units Common tables
RunBuilder ID (climate cluster)
maturity days
PHU
Program Run Specific tables
phu
plant phu Simulation Results
Field Operations plant julian
ID plant date
Year
Output Variables
Month
15 user defined columns
Day Fertilizer
Type Weather
Parameters ID (fertilizer)
Crop ID ID (Climate Cluster)
ID parameters
parameters 1 - 7 Data Output
Parameters
ID
YN03 Conc.
Control Records Weather Monthly PRKN Conc.
ID ID (climate cluster) YN03 loading
State FIPS month PRKN loading
Soil ID data
Tillage I-EPIC
Irrigation Code
Climate Cluster Output Pesticide
Application Category Operations ID
Nutrient Rate Category ID (Operation) application
Application Timing Parameters runoff, etc.
run data/settings
Manure Category
Output Annual
Pesticides ID
ID (Pesticide) year
Parameters standard output
Output Annual
Soils
Crops ID (soil cluster)
Crop Yields
Soil Layers
ID (Crop) Soil ID data ID Validation:
Year
Parameters Layer Number Queries
Yield
data 15 variables Reports
Figure A-3. i_EPIC table and data structure.
81
Figure A-4. Relationships between the Control Records, Output Annual, and Output Annual Crop
Yields tables. Frequently accessed data from these tables are joined to make the ALL Data table. The
All Data table contains a row for every year of each simulation and the table forms the basis of several
summary data sets including the Average Data table.
The EPIC Model Agriculture Research Service (ARS) scientists developed EPIC in the early 1980's to
assess the effect of erosion on productivity. Various components from the CREAMS and
SWRRB models were used in developing EPIC and the GLEAMS pesticide component
was added later. Since its use in 1985 for a national analysis required under the Soil and Water Resource
Conservation Act, EPIC has been expanded and refined to allow simulation of many processes
important in agricultural management. The major components in EPIC are weather simulation,
hydrology, erosion-sedimentation, nutrient cycling, pesticide fate, crop growth, soil temperature, tillage,
economics, and plant environment control. Although EPIC operates on a daily time step, the optional
Green and Ampt infiltration equation simulates rainfall excess rates at shorter time intervals (0.1 h). The
model offers optional methods for simulating several processes including five PET equations, six
erosion/sediment yield equations, two peak runoff rate equations, etc. EPIC can be used to compare
management systems and their effects on nitrogen, phosphorus, carbon, pesticides and sediment. The
management components that can be changed are crop rotations, tillage operations, irrigation
scheduling, drainage, furrow diking, liming, grazing, tree pruning, thinning, and harvest, manure
handling, and nutrient and pesticide application rates and timing. The drainage area considered by EPIC
is generally a field-size area, up to about 100 ha, where weather, soils, and management systems are
assumed to be homogeneous. Runs were built using EPIC version 3060 with an executable date of July
2004.
82
Table A-8. List of tables required for the ACCESS database used by i_EPIC (adapted from Gassman et
al., 2002)
Database Table Description Keya

Input data
ID, Weather Station ID, Soil Cluster ID,
Control records Characteristics for each EPIC simulation
Crop ID
b
Crops Standard EPIC crop parameter file Crop ID
b
Fertilizer Standard EPIC fertilizer characteristics file Fert ID
Field operations Operation schedules for EPIC opsc files ID, Crop ID, Fert ID, Op Code, Pest ID
c
Management Management data for APEX subarea files -
b
Operations Standard EPIC machinery operations file Op Code
b
Parameters Standard EPIC miscellaneous parameter file ID
b
Pesticides Standard EPIC pesticide characteristics file Pest ID
Soil layers Soil layer data Soil Cluster ID
Soils Soil name; miscellaneous soil data Soil Cluster ID
Weather Weather station; miscellaneous weather data Weather Station ID
Weather by month Monthly weather and wind statistics Weather Station ID

15 variables that user can select for annual
Output variables -
output
Output data
Output Average annual results for four variables ID
Output Annual Annual results for up to 45 output variables ID
Output Annual Crop Yields Annual yields for simulated crops in each ID
Output Soil Carbon Nitrogen EPIC1015 output file with C and N results ID
a
Keys used to link tables either relationally in database or dynamically during the EPIC simulation; ID is the run ID number for each EPIC
simulation.
b
The specific variables and the total number of variables can vary for these files between EPIC versions.
c Table is nonfunctional at present.
83
Appendix B
Derivation of Tillage For the tillage and field operation management options, probabilities were derived from
Probabilities the Crop Residue Management Survey, which is a county-level database that reports the
acres for each tillage type by crop (CTIC, 2001). Surveys prior to the 2000 specified acres
for only a limited set of crops including corn, soybeans, sorghum, and cotton while acres
for other crops were lumped into spring-seeded small grains, fall-seeded small grains, forage, or “other”.
In 2000, the crop set was extended to include peanuts, fall-seeded wheat (winter wheat), spring-seeded
wheat (spring wheat), barley, oats, rice, and potatoes; leaving only one NNLSC crop to be lumped (corn
silage into forage). Thus, the 2000 survey was obtained to derive the tillage probabilities.
Acres for total tillage, no-till, ridge-till, mulch-till, tillage leaving 15-30% residue, and tillage leaving less
than 15% residue were arranged in a single data row for each county FIPS and crop. Mismatches
between the CRMS and NNLSC tillage categories were resolved as follows: CRMS ridge-till and mulch-
till were combined to represent NNLSC mulch-till and the two CRMS tillage categories leaving 30% or
less residue were combined to represent NNLSC conventional tillage. The no-till category did not
require adjustments. Tillage probability weights were calculated by dividing the CRMS acres associated
with the NNLSC tillage categories by total tillage acres for each county and crop group.
Several adjustments or “fixes” were necessary to account for cases in which all three tillage categories
were not simulated in the NNLSC Database. Alfalfa, grass hay, and pastures were always simulated as
no-till, thus for these crops the no-till probability was set to one and both other tillage probabilities were
set to zero. Cotton, rice, and peanuts were simulated as having only mulch and conventional tillage, so
for these crops the no-till probability was added into the mulch-till probability, while the conventional-till
probabilities remained unchanged. Potatoes were simulated as conventional-till only, so that probability
was set to one and the others were set to zero. For the remaining crops, all three tillage systems were
simulated whenever the URU had either no irrigation or sprinkler irrigation. For URUs with gravity
irrigation, only conventional-till and mulch-till were simulated, thus for these cases, the county-crop data
row was duplicated, identified with an irrigation category variable and for gravity row, the no-till
probability was added into the mulch-till probability. The conventional-till probabilities remained
unchanged.
In a few cases (less than 10 percent), NRI points were located in counties without any CRMS data for
the crop indicated by the NRI. For these cases, the missing county data were filled in by either state or
regional averages.
84
Appendix C
Model and Database Project Information Sheet
Project National Nutrient Loss & Soil Carbon Modeling System & Database
Da Model Simulation of Soil Loss, Nutrient Loss, and Change in Soil Organic Carbon Associated with Crop
Production
Da Info http://www.nrcs.usda.gov/technical/nri/ceap/croplandreport/
Process Model EPIC3060 (executable date: 7-28-2004)

Runbuilder Version: July 2004
I_EPIC Date: 6-24-2004
Simulation Model 97NRI Microsimulation

Area distribution based on 1997 National Resource Inventory (NRI) statistical sample design.
Management distribution based on statistical weights derived from Cropping Practice Survey
(commercial fertilizer), Census of Agriculture (manure), and Crop Residue Management Survey
(tillage).
Application Name National Nutrient Loss & Soil Carbon Database

Short Name NNLSC
Distribution Date August 2008
Software Microsoft Access 2003
Database Files NNLSC_DATA.mdb (Data, Attributes, Characteristics, Definitions)

NNLSC_STAT.mdb (Status Trends & Assessment Tool)
Datasets 97 Baseline Cropland Results

97 No Conservation Practice Alternative
Install Location C:\NNLSC
Blackland Research
Steven Potter
Center Contact
Blackland Research Center – Texas Agricultural Experiment Station
720 E. Blackland Rd, Temple TX 76502
Spotter@brc.tamus.edu
254-774-6038
NRCS Project Manager Robert Kellogg

USDA NRCS - Resource Inventory & Assessment Division
5601 Sunnyside Ave., mail stop 5410, Beltsville, MD 20705
Robert.Kellogg@wdc.usda.gov
301-504-2294
85
Data Processing and Storage Perspective
Data Analysis Perspective
Two conceptual views of the microsimulation model. Diagram on the left focuses on data processing, physical process
modeling and creation of the Library of Runs. Diagram on the right presents the model from a sample design and data
analysis perspective.

NNLSC - DatabaseReferenceGuideV1 6jan2009

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

NNLSC - DatabaseReferenceGuideV1 6jan2009

Загружено:

Авторское право:

Доступные форматы

1

Blackland Research Center

National Nutrient Loss & Soil Carbon Database

Address questions or comments to the authors at:

Texas AgriLife Research 2008

Acknowledgements ii STAT Examples 57

Chapter1: What is the NNLSC?

1 USDA-NRCS (2000). For more information on the NRI, see www.nrcs.usda.gov/technical/NRI/.

2 No longer available. Refer to http://soildatamart.nrcs.usda.gov/ for official tabular soil data.

Area extents of the statistically clustered climate zones.

Figure 1. Organizational scheme for modeling the baseline domain.

The Library contains 40+ million rows of data, maintained in approximately 70

Figure 2. Overview of the 97NRI Microsimulation Modeling System

6 Structured Query Language

Chapter2: What data are in the NNLSC?

Table 1. The two datasets included in the NNLSC.

Relationships For one-to-many relationships (1—00 or 00—1) a record in one

Table 2. Tables contained in the NNLSC database.

into the diagram.

Table 3. Primary and foreign keys in the NNLSC tables.

The InSitu tables contain an assortment of categorical variables including StateFIPS,

Two tables of nutrient management weights are provided. The

Chapter3: Table Metadata & Relational Diagrams

Table 5. 97NoCP_InSitu Metadata

Table 6. 97bcr_URU Metadata

Table 7. 97NoCP_URU Metadata

Table 8. 97bcr_Cropshare Metadata

Table 9. 97NoCP_Cropshare Metadata

Table 10. 97bcr_Point Metadata

Table 11. 97NoCP_Point Metadata

Table 12. attribURU Metadata

Table 13. attribPoint Metadata

Table 14. charClimate Metadata

Table 15. charClimClusClass Metadata

Table 16. charWeatherStation Metadata

Table 17. charCrops Metadata

Table 18. charSoils Metadata

Table 19. defStates Metadata

Table 20. defNnlscRegions Metadata

Table 21. defTillage Metadata

Table 22. defIrrigationCode Metadata

Table 23. defConserPract Metadata

Table 24. defNutRate Metadata

Table 25. defNutTime Metadata

Table 26. defManureCategory Metadata

Table 27. defLandUse Metadata

Table 28. defNRI_LandUse Metadata

Table 29. defMoisture Metadata

Table 30. defTemperature Metadata

Table 31. defSlopeClass Metadata

Table 32. defSoilClass Metadata

Table 33. defSoilHydroGroup Metadata

Table 34. defSoilTxtGrps Metadata

Table 35. Key relationships in NNLSC tables.

Table 36. Management weights associated with the NNLSC datasets.

Table 37. wtsCountyTillage Metadata

Table 38. wtsUruTillProps Metadata

Table 39. wtsNutrientApplications Metadata.

Table 40. wtsManureCategory Metadata

Chapter4: STAT – the Status Trends Analysis Tool

Installing the NNLSC

2) Remove the Read