EcoService Models Library (ESML)
loading
Variables Details
: (EM-549)
Back
- Collapse All Expand All
- Export Data to Spreadsheet (Free Viewers)
- View Variable Relationship Diagram (PDF)(1 pp, 80 KB, About PDF)
EM-549 | |
Document Author
variable.detail.emDocumentAuthorHelp
?
|
Saleh, A. and O. Gallego |
Document Year
variable.detail.emDocumentYearHelp
?
|
2018 |
Crop type ?Comment:To add a crop to the rotation, click Add Crop to Rotation. The user is then asked to select a crop from the pick list, a tillage type (No-till, reduced till, or intensive till), and rotation year. The crop list is customized according to the region in which the project is located. The rotation year indicates the sequence of the crop within the crop schedule, it does not represent the calendar year. Once the user has selected a crop type, tillage type and rotation year, clicking Upload will add the crop to the crop schedule. Once a crop is added to the crop schedule you will note that it includes several default management characteristics including a planting date, fertilizer applications, tillage schedule, and harvest. These operations can be modified or deleted as needed and new operations can be added. |
Autofertigation total nitrogen concentration ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Autofertigation is the application of fertilizers, soil amendments, or other water-soluble products through an autoirrigation system. Autofertigation is an automatic fertilization process in which fertilizer is dissolved and distributed through the irrigation system. This makes autofertigation very similar to autoirrigation with the only additional user input required being nitrogen concentration. The amount of nitrogen in irrigation water in parts per million. Total N applied through autofertigation will be dependent upon the overall irrigation frequency which in turn is dependent upon water stress, frequency and maximum application factors set by the user. |
Autoirrigate a maximum frequency of every (0-365) days ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This field is asking for the maximum frequency (in days) that irrigation can take place. If the frequency is set to 1, then irrigation can occur every day. If frequency is set to 7 then irrigation can occur, at most, once a week. The value can be any whole number greater than or equal to zero and less than or equal to 365. |
Autoirrigation efficiency ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This value is the fraction of irrigation application that is not lost to runoff. This must be a value that is greater than 0 and less than or equal to 1. The closer the value is to 0, the greater the percentage of water lost to runoff and does not reach the crop. A value of 1 means that no water was lost to runoff. Different irrigation systems have different irrigation efficiencies. NTT supplies typical irrigation efficiency values for the irrigation type selected, but these values can be modified by the user. |
Autoirrigation type ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. Irrigation types include sprinkler, furrow/flood, drip, and furrow diking. |
Burn date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Continuous grazing animal type ?Comment:User indicates the type of animals being grazed on the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing animal units ?Comment:User indicates the total animal units being grazed on the field. Animal units represent 1,000 lbs of live animal weight. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing end date ?Comment:User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing hours in field ?Comment:User indicates the total hours per day that animals are grazed in the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing start date ?Comment:User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Countour buffer (strip farming crop grass/vegetation ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. Contour buffer strips are permanent, narrow bands of grasses/legumes planted on the contour (across or perpendicular to a slope) between wider strips of crops. Contour buffers trap sediment and enhance filtration of nutrients and pesticides by slowing down runoff that could enter the local surface waters. This is the type of grass or vegetation that will be present in the buffer sections of the contour buffer. |
Cover crop planting date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Cover crop planting method ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Cover crop type ?Comment:Cover crops are not fertilized and are not harvested, rather they are chopped prior to planting of the next crop in the rotation. This optional variable is constant with respect to Crop type for this specific application. |
Cover crop year ?Comment:The cover crop year should indicate the year within the rotation that the cover crop is planted. This optional variable is constant with respect to Crop type for this specific application. |
Crop width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width, in feet, of the strips of the main crop that was planted. It can be any number greater than 0. Crop width, along with buffer width, determine the number of buffer and crop strips in the field. |
End of season date ?Comment:End of season indicates to the model that the crop is removed from the field. If an End of Season operation is not present, then the model assumes that the crop is left growing. End of season should be used for all annual crops. For certain perennial crops like hay and pasture, End of Season operations may be absent from the crop schedule. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer amount ?Comment:User needs to indicate the amount of fertilizer applied. Units will vary depending on the type of fertilizer selected (lbs/ac, tons/ac, 1000 gals/ac). This variable is constant with respect to Crop type for the specific model application. |
Fertilizer category ?Comment:User must indicate the fertilizer category (commercial, liquid manure, or solid manure). This variable is constant with respect to Crop type for the specific model application. |
Fertilizer compostion ?Comment:For commercial fertilizer, these fields indicate the N and P composition. These fields are pre-filled based on the fertilizer type selected, but can be modified if needed. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer depth ?Comment:If the fertilizer is incorporated, user should indicate the depth of incorporation here. If fertilizer is not incorporated, this field can be left blank. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer type ?Comment:The fertilizer type pick list will vary depending on the fertilizer category selected. For manure fertilizer, pick list will contain types of animal manure. This variable is constant with respect to Crop type for the specific model application. |
Field (area of interest) ?Comment:After creating a new project, users will be asked to define the location of the project using the interactive Google map. The interactive map allows the user to define one or more areas of interest (AOI). The area of interest should correlate to fields within the project area. The map is ONLY used for mainland United States. If you would like to simulate using an area outside of mainland United States, follow the instructions for User Input. When defining the AOI, the underlying weather, soils, and slope information is retrieved from the underlying spatial data. There are two ways to define your areas of interest: you may manually draw your areas of interest using the zoom features and drawing tools on the interactive map, or you may upload your own shapefile. After drawing the field, a message will pop up telling the user to enter the name of the AOI. |
Field area ?Comment:Field area displays the calculated area of the field in acres. The user may refine this value if needed. |
Forest strip width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the width of the forest buffer (not including the grass strip). |
Fraction of area controlled by ponds/WASCB ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. Water and sediment control basins (WASCOBs), or ponds, consist of an embankment across the slope of a field or minor waterway to temporarily detain and release water through a piped outlet or through infiltration. They are constructed perpendicular to the flow direction and parallel to each other. WASCOBs are usually installed in areas where the land is relatively steep and undulating. They detain water from contributing areas, inducing sedimentation and controlling the release of water, thereby reducing the erosive power of the water downstream. Additional benefits are settling of sediment-bound pollutants and some infiltration. Only one input is required for ponds: fraction of area controlled by ponds. This is the fraction (a value between 0 and 1) of the field runoff that flows through (is controlled by) the pond/WASCOB. As modeled, ponds only treat runoff that originates in this field. Inflow from other fields is not routed through the ponds. Ponds/WASCOBs are assumed to be within field. |
Fraction of field treated by buffer ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the estimated fraction (0.00-1.00) of the runoff from the field that is routed through the buffer. |
Fraction of field treated by grass waterway ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. The fraction of the field that drains to the grass waterway. A number between 0.00 and 1.00. |
Grass buffer vegetation type ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the type of grass or vegetation that is planted in the Filter Strip. |
Grass buffer/forest buffer area ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. Forest buffers are linear wooded areas with well-developed root systems, an organic surface layer, and understory vegetation. When they are adjacent to open water they are referred to as riparian forest buffers. Non-riparian buffers are linear wooded areas along down-slope field edges. Forest buffers trap sediment and increase infiltration, thereby reducing sediment and nutrient losses. Forest buffers often include a grass buffer between the field and the forested buffer. If present, please also include the width of the grass buffer. Grass buffers, also known as a filter strips, are an area of vegetation, generally narrow in width and long across the downslope edge of a field, that slows the rate of runoff, allowing sediments, organic matter, and other pollutants that are being conveyed by the water to be removed by settling out. Filter strips reduce erosion and the accompanying sediment-bound pollution. In NTT, filter strips function by providing for better infiltration of soluble nutrients, trapping of sediment, and increased uptake of water and nutrients by the filter strip vegetation. The saturated conductivity value is also modified for filter strip simulation in NTT. The inputs for grass buffers are the same as for forest buffers (see Forest Buffer), with the additional requirement that the user specify type of vegetation. This is the total area of the Riparian Buffer. This field is optional. If left blank, the area will automatically be calculated using the width of the buffer and the length of the field edge (where the field edge is calculated as the square root of the area of the field). |
Grass strip width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the width of the grass strip between the crop and the forested buffer, if present. |
Grass waterway crop ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. A grassed waterway is a natural or constructed swale, shaped or graded and established in suitable vegetation for the safe conveyance of runoff. Grassed waterways are designed to prevent soil erosion while draining runoff water from adjacent cropland. As water travels down the waterway, the grass vegetation prevents erosion that would otherwise result from concentrated flows and uptakes nutrients. Grassed waterways also help prevent gully erosion in areas of concentrated flow. For example, they may be used to drain runoff from terraces and runoff water diversions. By intercepting runoff, grassed waterways slow erosion and minimize nutrient losses. |
Grass waterway width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width of the grassed waterway, in feet, including both sides of the vegetated channel. This can be any number greater than 0. |
Grass/vegetation width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width, in feet, of the buffer strips. It can be any number greater than 0. Buffer width, along with crop width, determine the number of buffer and crop strips in the field. |
Harvest date ?Comment:A default date is automatically entered for harvest. This can be modified as needed. This variable is constant with respect to Crop type for the specific model application. |
Irrigation amount ?Comment:User indicates the volume of water applied in this irrigation event in inches. This optional variable is constant with respect to Crop type for the specific application. |
Irrigation efficiency ?Comment:This field defaults to a typical irrigation efficiency value (as a fraction) based on the irrigation method that is selected. This value can be modified. This optional variable is constant with respect to Crop type for the specific application. |
Irrigation method ?Comment:An optional variable that is constant with respect to Crop type for the specific application. |
Is buffer included in AOI? (y/n) ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. If buffer has been drawn as part of the AOI, then the area will be subtracted from the crop area. If it has not been drawn as part of the AOI, it will be assumed to be adjacent to one edge of the field. |
Is wetland area included in your AOI? (y/n) ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Users indicate here whether the AOI representing the field includes the wetland feature within the drawn polygon or if the wetland feature lies outside of the AOI. If the wetland feature is included in the AOI, then the wetland acres will be subtracted from the field area. |
Land leveling slope reduction ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. Land leveling is used to reduce the slope on high soil slopes. By reducing the slope, the surface land is better able to retain water and soil, reducing erosion and increasing infiltration. The input for land leveling is slope reduction percentage. This is the percent reduction in the slope of the soil. The number can be any percentage between 0% and 100%. The closer the slope is to 100, the more the slope is reduced. |
Lime amount ?Comment:User must indicate amount of lime applied (lbs/ac). This optional variable is constant with respect to Crop type for this specific application. |
Lime date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Maximum single application ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This value signifies the maximum amount of water than can be applied in a single irrigation event. It is in inches, and it can be any number greater than 0. If there are no constraints on the maximum single application, this value should be set to a high number. |
Moisture content ?Comment:For manure fertilizer, this is the percentage, by weight, of moisture content in the manure. Typical values for each manure type are provided, but can be modified by the user. This variable is constant with respect to Crop type for the specific model application. |
Number of consecutive days grazed at a time (in each paddock) ?Comment:User indicates the number of days livestock will spend in each paddock before being rotated to a new paddock. This optional variable is constant with respect to Crop type for this specific application. |
Pasture rest time between grazing ?Comment:User indicates the number of days that the pasture is rested between rotational grazing cycles. This optional variable is constant with respect to Crop type for this specific application. |
Plant water stress factor ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. The water stress factor indicates the water stress level of the crop. This is the value that is used to trigger the start of auto irrigation. For example, if water stress is set to 0.8 then NTT will trigger an irrigation event when the crop is 80% water-stressed, as long as conditions for maximum frequency are also met. The plant water stress factor can be any value greater than 0 and less than or equal to 1. The closer the value is to 100, the less water stress is allowed before the automatic irrigation is turned on. |
Planting date ?Comment:This variable is constant with respect to Crop type for the specific model application. |
Rotation year ?Comment:The rotation year indicates the sequence of the crop within the crop schedule, it does not represent the calendar year. This variable is constant with respect to Crop type for the specific model application. |
Rotational grazing animal type ?Comment:User indicates the type of animals being grazed on the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing animal units ?Comment:User indicates the total animal units being grazed on the field. Animal units represent 1,000 lbs of live weight. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing end date ?Comment:The rotational grazing operation, unlike continuous grazing, assumes that the pasture is divided into paddocks and that livestock are moved through the paddocks as needed. Thus, each paddock is given a recovery period between grazing events, improving vegetative cover. User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing hours in field ?Comment:User indicates the total hours per day that animals are grazed in the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing start date ?Comment:The rotational grazing operation, unlike continuous grazing, assumes that the pasture is divided into paddocks and that livestock are moved through the paddocks as needed. Thus, each paddock is given a recovery period between grazing events, improving vegetative cover. User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Seed amount ?Comment:This field is pre-filled with standard seeding rates for each crop type. If the user has more specific information on seeding rate they may enter it. This variable is constant with respect to Crop type for the specific model application. |
Soil organic matter ?Comment:The default soil organic matter (%) value returned by the SSURGO soils database is displayed for each soil in the soils list. However, if the user has more precise data they may enter it here. |
Soil P ?Comment:Users should enter the soil phosphorus test value for their field, if available. If None was selected for the P test then this field will be disabled and a minimum phosphorus concentration in the soil will be used. Similarly, if a soil test is selected, but the field Soil P value is left blank, the tool will assume a minimum phosphorus concentration in the soil. |
Soil P test ?Comment:The user should select a soil test, if applicable, that was used to determine the soil phosphorus. Currently NTT includes conversions for the Fe-strip test, Olsen, Bray-1, and Mehlich-3 tests. If you have used a different test, please select Other. If you do not have a soil P test for your soil, leave these fields blank and NTT will use default soil P values. |
Terrace system (y/n) ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. A terrace system is a leveled section of a hill cultivated area, designed as a method of soil conservation to slow or prevent the rapid surface runoff of water. Terraces decrease hill slope-length, reduce formation of gullies, and intercept and conduct runoff to a safe outlet thereby reducing sediment content in runoff water. Often, in application the landscape is formed into multiple terraces, giving a stepped appearance. Terraces are simulated by reducing the practice factor (PEC). |
Tile drain depth ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. For NTT applications, underground drainage systems are simulated in APEX. The depth of the drainage system to reduce plant stress is a key parameter used in simulating tile drainage systems in NTT. Tile drainage simulation in NTT increases subsurface flow, which may provide an avenue for increased nutrient losses in subsurface flow. The only input for tile drains is depth. This is the depth in feet at which the drainage system is installed. It is any number greater than 0. |
Tillage ?Comment:User must indicate the tillage method using the drop down selection. This variable is constant with respect to Crop type for the specific model application. |
Total N concentration ?Comment:For manure fertilizer, the user should indicate the total N content per ton of solid manure or per 1000 gallons of liquid manure. Typical values are pre-filled for the user, but can be modified. This variable is constant with respect to Crop type for the specific model application. |
Total P concentration ?Comment:For manure fertilizer, the user should indicate the total P content per ton of solid manure or per 1000 gallons of liquid manure. Typical values are pre-filled for the user, but can be modified. This variable is constant with respect to Crop type for the specific model application. |
Wetland area ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Wetlands are those areas that are inundated or saturated by surface or groundwater at a frequency and duration sufficient to support, and that under normal circumstances do support, a prevalence of vegetation typically adapted for life in saturated soil conditions. Wetlands generally include swamps, marshes, bogs and similar areas. The wetland area is simulated as a shallow reservoir (1 ft. depth) with growing wetland vegetation – it is essentially simulated as an artificial wetland and not a natural wetland. The slope of wetland area is set as 1%. Simulated wetlands trap sediment, reduce runoff, increase infiltration, and also increase uptake of water and nutrients by the vegetation in the area covered by the wetland. The area of the wetland is input in acres. Since this area is no longer able to be used for crop production, there may be a lower total crop yield (although there may be a greater crop yield/acre). |
Change in crop yield ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in deep percolation loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in irrigation applied loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in manure erosion ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in organic N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in organic P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in other water info loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in PO4 loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in runoff N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in subsurface flor loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in subsurface N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface erosion loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface flow loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface/subsurface/tile drain flow loss |
Change in tile drain flow loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in tile drain N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in tile drain P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total sediment loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Crop yield ?Comment:The scenario results presented in your table represent an AVERAGE annual yield across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Deep percolation loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Irrigation applied loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Manure erosion loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Organic N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Organic P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Other water info loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
PO4 loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Runoff N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Subsurface flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Subsurface N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface erosion loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface/subsurface/tile drain flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total sediment loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
|
Variable ID
variable.detail.varIdHelp
?
|
13307 | 13475 | 13472 | 13471 | 13470 | 13443 | 13433 | 13434 | 13432 | 13435 | 13431 | 13492 | 13448 | 13449 | 13446 | 13447 | 13494 | 13427 | 13314 | 13312 | 13316 | 13315 | 13313 | 12560 | 12614 | 13482 | 13479 | 13483 | 13491 | 13485 | 13480 | 13481 | 13486 | 13487 | 13493 | 13426 | 13429 | 13430 | 13428 | 13484 | 13478 | 13495 | 13445 | 13444 | 13474 | 13425 | 13441 | 13442 | 13473 | 13310 | 13309 | 13438 | 13439 | 13437 | 13440 | 13436 | 13311 | 12617 | 12616 | 12615 | 13496 | 13476 | 13308 | 13370 | 13424 | 13477 | 13506 | 13513 | 13512 | 13516 | 13498 | 13508 | 13511 | 13509 | 13499 | 13504 | 13500 | 13515 | 13503 | 13502 | 13505 | 13501 | 13510 | 13497 | 13507 | 13514 | 13459 | 13466 | 13465 | 13469 | 13451 | 13461 | 13464 | 13462 | 13452 | 13457 | 13453 | 13468 | 13456 | 13455 | 13458 | 13454 | 13463 | 13450 | 13460 | 13467 |
Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | Not reported | |
Qualitative-Quantitative
variable.detail.continuousCategoricalHelp
?
|
Qualitative (Class, Rating or Ranking) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Qualitative (Class, Rating or Ranking) | Quantitative (Cardinal Only) | Qualitative (Class, Rating or Ranking) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Qualitative (Class, Rating or Ranking) | Quantitative (Cardinal Only) | Qualitative (Class, Rating or Ranking) | Qualitative (Class, Rating or Ranking) | Qualitative (Class, Rating or Ranking) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Qualitative (Class, Rating or Ranking) | Qualitative (Class, Rating or Ranking) | Quantitative (Cardinal Only) | Qualitative (Class, Rating or Ranking) | Qualitative (Class, Rating or Ranking) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Qualitative (Class, Rating or Ranking) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Qualitative (Class, Rating or Ranking) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Qualitative (Class, Rating or Ranking) | Qualitative (Class, Rating or Ranking) | Qualitative (Class, Rating or Ranking) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Qualitative (Class, Rating or Ranking) | Qualitative (Class, Rating or Ranking) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Qualitative (Class, Rating or Ranking) | Qualitative (Class, Rating or Ranking) | Quantitative (Cardinal Only) | Qualitative (Class, Rating or Ranking) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) | Quantitative (Cardinal Only) |
Cardinal-Ordinal
variable.detail.cardinalOrdinalHelp
?
|
Non-Ordinal | Cardinal | Cardinal | Cardinal | Non-Ordinal | Cardinal | Non-Ordinal | Cardinal | Cardinal | Cardinal | Cardinal | Non-Ordinal | Cardinal | Non-Ordinal | Non-Ordinal | Ordinal | Cardinal | Cardinal | Cardinal | Non-Ordinal | Non-Ordinal | Cardinal | Non-Ordinal | Non-Ordinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Non-Ordinal | Cardinal | Cardinal | Non-Ordinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Non-Ordinal | Non-Ordinal | Non-Ordinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Ordinal | Non-Ordinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Non-Ordinal | Non-Ordinal | Cardinal | Non-Ordinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal | Cardinal |
Not applicable | ppm | days | % | Not applicable | day of year | Not applicable | lbs animal mass/1000 lbs | day of year | hrs/day | day of year | Not applicable | day of year | Not applicable | Not applicable | Not applicable | ft | day of year | amount per acre | Not applicable | Not applicable | Not reported | Not applicable | Not applicable | acres | ft | % | % | % | Not applicable | ac | ft | Not applicable | ft | ft | day of year | in | % | Not applicable | Not applicable | Not applicable | % | lbs/ac | day of year | in | % | days | days | % | day of year | Not applicable | Not applicable | lbs animal mass/1000 lbs | day of year | hrs/day | day of year | seeds/sq. ft. | % | ppm | Not applicable | Not applicable | ft | Not applicable | user specified | user specified | acres | % | % | % | % | % | % | % | % | % | % | % | % | % | % | % | % | % | % | % | % | Not reported | in | in | t/ac | lbs/ac | lbs/ac | in | lbs/ac | lbs/ac | in | lbs/ac | t/ac | in | in | in | lbs/ac | lbs/ac | lbs/ac | lbs/ac | t/ac |
Crop type ?Comment:To add a crop to the rotation, click Add Crop to Rotation. The user is then asked to select a crop from the pick list, a tillage type (No-till, reduced till, or intensive till), and rotation year. The crop list is customized according to the region in which the project is located. The rotation year indicates the sequence of the crop within the crop schedule, it does not represent the calendar year. Once the user has selected a crop type, tillage type and rotation year, clicking Upload will add the crop to the crop schedule. Once a crop is added to the crop schedule you will note that it includes several default management characteristics including a planting date, fertilizer applications, tillage schedule, and harvest. These operations can be modified or deleted as needed and new operations can be added. |
Autofertigation total nitrogen concentration ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Autofertigation is the application of fertilizers, soil amendments, or other water-soluble products through an autoirrigation system. Autofertigation is an automatic fertilization process in which fertilizer is dissolved and distributed through the irrigation system. This makes autofertigation very similar to autoirrigation with the only additional user input required being nitrogen concentration. The amount of nitrogen in irrigation water in parts per million. Total N applied through autofertigation will be dependent upon the overall irrigation frequency which in turn is dependent upon water stress, frequency and maximum application factors set by the user. |
Autoirrigate a maximum frequency of every (0-365) days ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This field is asking for the maximum frequency (in days) that irrigation can take place. If the frequency is set to 1, then irrigation can occur every day. If frequency is set to 7 then irrigation can occur, at most, once a week. The value can be any whole number greater than or equal to zero and less than or equal to 365. |
Autoirrigation efficiency ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This value is the fraction of irrigation application that is not lost to runoff. This must be a value that is greater than 0 and less than or equal to 1. The closer the value is to 0, the greater the percentage of water lost to runoff and does not reach the crop. A value of 1 means that no water was lost to runoff. Different irrigation systems have different irrigation efficiencies. NTT supplies typical irrigation efficiency values for the irrigation type selected, but these values can be modified by the user. |
Autoirrigation type ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. Irrigation types include sprinkler, furrow/flood, drip, and furrow diking. |
Burn date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Continuous grazing animal type ?Comment:User indicates the type of animals being grazed on the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing animal units ?Comment:User indicates the total animal units being grazed on the field. Animal units represent 1,000 lbs of live animal weight. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing end date ?Comment:User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing hours in field ?Comment:User indicates the total hours per day that animals are grazed in the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing start date ?Comment:User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Countour buffer (strip farming crop grass/vegetation ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. Contour buffer strips are permanent, narrow bands of grasses/legumes planted on the contour (across or perpendicular to a slope) between wider strips of crops. Contour buffers trap sediment and enhance filtration of nutrients and pesticides by slowing down runoff that could enter the local surface waters. This is the type of grass or vegetation that will be present in the buffer sections of the contour buffer. |
Cover crop planting date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Cover crop planting method ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Cover crop type ?Comment:Cover crops are not fertilized and are not harvested, rather they are chopped prior to planting of the next crop in the rotation. This optional variable is constant with respect to Crop type for this specific application. |
Cover crop year ?Comment:The cover crop year should indicate the year within the rotation that the cover crop is planted. This optional variable is constant with respect to Crop type for this specific application. |
Crop width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width, in feet, of the strips of the main crop that was planted. It can be any number greater than 0. Crop width, along with buffer width, determine the number of buffer and crop strips in the field. |
End of season date ?Comment:End of season indicates to the model that the crop is removed from the field. If an End of Season operation is not present, then the model assumes that the crop is left growing. End of season should be used for all annual crops. For certain perennial crops like hay and pasture, End of Season operations may be absent from the crop schedule. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer amount ?Comment:User needs to indicate the amount of fertilizer applied. Units will vary depending on the type of fertilizer selected (lbs/ac, tons/ac, 1000 gals/ac). This variable is constant with respect to Crop type for the specific model application. |
Fertilizer category ?Comment:User must indicate the fertilizer category (commercial, liquid manure, or solid manure). This variable is constant with respect to Crop type for the specific model application. |
Fertilizer compostion ?Comment:For commercial fertilizer, these fields indicate the N and P composition. These fields are pre-filled based on the fertilizer type selected, but can be modified if needed. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer depth ?Comment:If the fertilizer is incorporated, user should indicate the depth of incorporation here. If fertilizer is not incorporated, this field can be left blank. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer type ?Comment:The fertilizer type pick list will vary depending on the fertilizer category selected. For manure fertilizer, pick list will contain types of animal manure. This variable is constant with respect to Crop type for the specific model application. |
Field (area of interest) ?Comment:After creating a new project, users will be asked to define the location of the project using the interactive Google map. The interactive map allows the user to define one or more areas of interest (AOI). The area of interest should correlate to fields within the project area. The map is ONLY used for mainland United States. If you would like to simulate using an area outside of mainland United States, follow the instructions for User Input. When defining the AOI, the underlying weather, soils, and slope information is retrieved from the underlying spatial data. There are two ways to define your areas of interest: you may manually draw your areas of interest using the zoom features and drawing tools on the interactive map, or you may upload your own shapefile. After drawing the field, a message will pop up telling the user to enter the name of the AOI. |
Field area ?Comment:Field area displays the calculated area of the field in acres. The user may refine this value if needed. |
Forest strip width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the width of the forest buffer (not including the grass strip). |
Fraction of area controlled by ponds/WASCB ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. Water and sediment control basins (WASCOBs), or ponds, consist of an embankment across the slope of a field or minor waterway to temporarily detain and release water through a piped outlet or through infiltration. They are constructed perpendicular to the flow direction and parallel to each other. WASCOBs are usually installed in areas where the land is relatively steep and undulating. They detain water from contributing areas, inducing sedimentation and controlling the release of water, thereby reducing the erosive power of the water downstream. Additional benefits are settling of sediment-bound pollutants and some infiltration. Only one input is required for ponds: fraction of area controlled by ponds. This is the fraction (a value between 0 and 1) of the field runoff that flows through (is controlled by) the pond/WASCOB. As modeled, ponds only treat runoff that originates in this field. Inflow from other fields is not routed through the ponds. Ponds/WASCOBs are assumed to be within field. |
Fraction of field treated by buffer ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the estimated fraction (0.00-1.00) of the runoff from the field that is routed through the buffer. |
Fraction of field treated by grass waterway ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. The fraction of the field that drains to the grass waterway. A number between 0.00 and 1.00. |
Grass buffer vegetation type ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the type of grass or vegetation that is planted in the Filter Strip. |
Grass buffer/forest buffer area ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. Forest buffers are linear wooded areas with well-developed root systems, an organic surface layer, and understory vegetation. When they are adjacent to open water they are referred to as riparian forest buffers. Non-riparian buffers are linear wooded areas along down-slope field edges. Forest buffers trap sediment and increase infiltration, thereby reducing sediment and nutrient losses. Forest buffers often include a grass buffer between the field and the forested buffer. If present, please also include the width of the grass buffer. Grass buffers, also known as a filter strips, are an area of vegetation, generally narrow in width and long across the downslope edge of a field, that slows the rate of runoff, allowing sediments, organic matter, and other pollutants that are being conveyed by the water to be removed by settling out. Filter strips reduce erosion and the accompanying sediment-bound pollution. In NTT, filter strips function by providing for better infiltration of soluble nutrients, trapping of sediment, and increased uptake of water and nutrients by the filter strip vegetation. The saturated conductivity value is also modified for filter strip simulation in NTT. The inputs for grass buffers are the same as for forest buffers (see Forest Buffer), with the additional requirement that the user specify type of vegetation. This is the total area of the Riparian Buffer. This field is optional. If left blank, the area will automatically be calculated using the width of the buffer and the length of the field edge (where the field edge is calculated as the square root of the area of the field). |
Grass strip width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the width of the grass strip between the crop and the forested buffer, if present. |
Grass waterway crop ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. A grassed waterway is a natural or constructed swale, shaped or graded and established in suitable vegetation for the safe conveyance of runoff. Grassed waterways are designed to prevent soil erosion while draining runoff water from adjacent cropland. As water travels down the waterway, the grass vegetation prevents erosion that would otherwise result from concentrated flows and uptakes nutrients. Grassed waterways also help prevent gully erosion in areas of concentrated flow. For example, they may be used to drain runoff from terraces and runoff water diversions. By intercepting runoff, grassed waterways slow erosion and minimize nutrient losses. |
Grass waterway width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width of the grassed waterway, in feet, including both sides of the vegetated channel. This can be any number greater than 0. |
Grass/vegetation width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width, in feet, of the buffer strips. It can be any number greater than 0. Buffer width, along with crop width, determine the number of buffer and crop strips in the field. |
Harvest date ?Comment:A default date is automatically entered for harvest. This can be modified as needed. This variable is constant with respect to Crop type for the specific model application. |
Irrigation amount ?Comment:User indicates the volume of water applied in this irrigation event in inches. This optional variable is constant with respect to Crop type for the specific application. |
Irrigation efficiency ?Comment:This field defaults to a typical irrigation efficiency value (as a fraction) based on the irrigation method that is selected. This value can be modified. This optional variable is constant with respect to Crop type for the specific application. |
Irrigation method ?Comment:An optional variable that is constant with respect to Crop type for the specific application. |
Is buffer included in AOI? (y/n) ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. If buffer has been drawn as part of the AOI, then the area will be subtracted from the crop area. If it has not been drawn as part of the AOI, it will be assumed to be adjacent to one edge of the field. |
Is wetland area included in your AOI? (y/n) ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Users indicate here whether the AOI representing the field includes the wetland feature within the drawn polygon or if the wetland feature lies outside of the AOI. If the wetland feature is included in the AOI, then the wetland acres will be subtracted from the field area. |
Land leveling slope reduction ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. Land leveling is used to reduce the slope on high soil slopes. By reducing the slope, the surface land is better able to retain water and soil, reducing erosion and increasing infiltration. The input for land leveling is slope reduction percentage. This is the percent reduction in the slope of the soil. The number can be any percentage between 0% and 100%. The closer the slope is to 100, the more the slope is reduced. |
Lime amount ?Comment:User must indicate amount of lime applied (lbs/ac). This optional variable is constant with respect to Crop type for this specific application. |
Lime date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Maximum single application ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This value signifies the maximum amount of water than can be applied in a single irrigation event. It is in inches, and it can be any number greater than 0. If there are no constraints on the maximum single application, this value should be set to a high number. |
Moisture content ?Comment:For manure fertilizer, this is the percentage, by weight, of moisture content in the manure. Typical values for each manure type are provided, but can be modified by the user. This variable is constant with respect to Crop type for the specific model application. |
Number of consecutive days grazed at a time (in each paddock) ?Comment:User indicates the number of days livestock will spend in each paddock before being rotated to a new paddock. This optional variable is constant with respect to Crop type for this specific application. |
Pasture rest time between grazing ?Comment:User indicates the number of days that the pasture is rested between rotational grazing cycles. This optional variable is constant with respect to Crop type for this specific application. |
Plant water stress factor ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. The water stress factor indicates the water stress level of the crop. This is the value that is used to trigger the start of auto irrigation. For example, if water stress is set to 0.8 then NTT will trigger an irrigation event when the crop is 80% water-stressed, as long as conditions for maximum frequency are also met. The plant water stress factor can be any value greater than 0 and less than or equal to 1. The closer the value is to 100, the less water stress is allowed before the automatic irrigation is turned on. |
Planting date ?Comment:This variable is constant with respect to Crop type for the specific model application. |
Rotation year ?Comment:The rotation year indicates the sequence of the crop within the crop schedule, it does not represent the calendar year. This variable is constant with respect to Crop type for the specific model application. |
Rotational grazing animal type ?Comment:User indicates the type of animals being grazed on the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing animal units ?Comment:User indicates the total animal units being grazed on the field. Animal units represent 1,000 lbs of live weight. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing end date ?Comment:The rotational grazing operation, unlike continuous grazing, assumes that the pasture is divided into paddocks and that livestock are moved through the paddocks as needed. Thus, each paddock is given a recovery period between grazing events, improving vegetative cover. User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing hours in field ?Comment:User indicates the total hours per day that animals are grazed in the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing start date ?Comment:The rotational grazing operation, unlike continuous grazing, assumes that the pasture is divided into paddocks and that livestock are moved through the paddocks as needed. Thus, each paddock is given a recovery period between grazing events, improving vegetative cover. User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Seed amount ?Comment:This field is pre-filled with standard seeding rates for each crop type. If the user has more specific information on seeding rate they may enter it. This variable is constant with respect to Crop type for the specific model application. |
Soil organic matter ?Comment:The default soil organic matter (%) value returned by the SSURGO soils database is displayed for each soil in the soils list. However, if the user has more precise data they may enter it here. |
Soil P ?Comment:Users should enter the soil phosphorus test value for their field, if available. If None was selected for the P test then this field will be disabled and a minimum phosphorus concentration in the soil will be used. Similarly, if a soil test is selected, but the field Soil P value is left blank, the tool will assume a minimum phosphorus concentration in the soil. |
Soil P test ?Comment:The user should select a soil test, if applicable, that was used to determine the soil phosphorus. Currently NTT includes conversions for the Fe-strip test, Olsen, Bray-1, and Mehlich-3 tests. If you have used a different test, please select Other. If you do not have a soil P test for your soil, leave these fields blank and NTT will use default soil P values. |
Terrace system (y/n) ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. A terrace system is a leveled section of a hill cultivated area, designed as a method of soil conservation to slow or prevent the rapid surface runoff of water. Terraces decrease hill slope-length, reduce formation of gullies, and intercept and conduct runoff to a safe outlet thereby reducing sediment content in runoff water. Often, in application the landscape is formed into multiple terraces, giving a stepped appearance. Terraces are simulated by reducing the practice factor (PEC). |
Tile drain depth ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. For NTT applications, underground drainage systems are simulated in APEX. The depth of the drainage system to reduce plant stress is a key parameter used in simulating tile drainage systems in NTT. Tile drainage simulation in NTT increases subsurface flow, which may provide an avenue for increased nutrient losses in subsurface flow. The only input for tile drains is depth. This is the depth in feet at which the drainage system is installed. It is any number greater than 0. |
Tillage ?Comment:User must indicate the tillage method using the drop down selection. This variable is constant with respect to Crop type for the specific model application. |
Total N concentration ?Comment:For manure fertilizer, the user should indicate the total N content per ton of solid manure or per 1000 gallons of liquid manure. Typical values are pre-filled for the user, but can be modified. This variable is constant with respect to Crop type for the specific model application. |
Total P concentration ?Comment:For manure fertilizer, the user should indicate the total P content per ton of solid manure or per 1000 gallons of liquid manure. Typical values are pre-filled for the user, but can be modified. This variable is constant with respect to Crop type for the specific model application. |
Wetland area ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Wetlands are those areas that are inundated or saturated by surface or groundwater at a frequency and duration sufficient to support, and that under normal circumstances do support, a prevalence of vegetation typically adapted for life in saturated soil conditions. Wetlands generally include swamps, marshes, bogs and similar areas. The wetland area is simulated as a shallow reservoir (1 ft. depth) with growing wetland vegetation – it is essentially simulated as an artificial wetland and not a natural wetland. The slope of wetland area is set as 1%. Simulated wetlands trap sediment, reduce runoff, increase infiltration, and also increase uptake of water and nutrients by the vegetation in the area covered by the wetland. The area of the wetland is input in acres. Since this area is no longer able to be used for crop production, there may be a lower total crop yield (although there may be a greater crop yield/acre). |
Change in crop yield ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in deep percolation loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in irrigation applied loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in manure erosion ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in organic N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in organic P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in other water info loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in PO4 loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in runoff N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in subsurface flor loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in subsurface N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface erosion loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface flow loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface/subsurface/tile drain flow loss |
Change in tile drain flow loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in tile drain N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in tile drain P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total sediment loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Crop yield ?Comment:The scenario results presented in your table represent an AVERAGE annual yield across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Deep percolation loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Irrigation applied loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Manure erosion loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Organic N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Organic P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Other water info loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
PO4 loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Runoff N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Subsurface flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Subsurface N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface erosion loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface/subsurface/tile drain flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total sediment loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
|
Predictor-Intermediate-Response
variable.detail.displayVariableTypeHelp
?
|
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Predictor |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Response |
Predictor Variable Type
variable.detail.displayPredictorVariableTypeHelp
?
|
Time- or Space-varying Variable |
Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Constant or Parameter | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Response Variable Type
variable.detail.resClassHelp
?
|
Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Computed Variable |
Data Source/Type
variable.detail.dataTypeHelp
?
|
Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Variable Classification Hierarchy
variable.detail.vchLevel1Help
?
|
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
2. Land Surface (or Water Body) Cover, Use, Substrate, or Metric |
6. Non-monetary Indicators of Human Demand, Use or Benefit of Ecosystem Goods and Services |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
6. Non-monetary Indicators of Human Demand, Use or Benefit of Ecosystem Goods and Services |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
6. Non-monetary Indicators of Human Demand, Use or Benefit of Ecosystem Goods and Services |
6. Non-monetary Indicators of Human Demand, Use or Benefit of Ecosystem Goods and Services |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
6. Non-monetary Indicators of Human Demand, Use or Benefit of Ecosystem Goods and Services |
6. Non-monetary Indicators of Human Demand, Use or Benefit of Ecosystem Goods and Services |
6. Non-monetary Indicators of Human Demand, Use or Benefit of Ecosystem Goods and Services |
6. Non-monetary Indicators of Human Demand, Use or Benefit of Ecosystem Goods and Services |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
6. Non-monetary Indicators of Human Demand, Use or Benefit of Ecosystem Goods and Services |
6. Non-monetary Indicators of Human Demand, Use or Benefit of Ecosystem Goods and Services |
6. Non-monetary Indicators of Human Demand, Use or Benefit of Ecosystem Goods and Services |
6. Non-monetary Indicators of Human Demand, Use or Benefit of Ecosystem Goods and Services |
6. Non-monetary Indicators of Human Demand, Use or Benefit of Ecosystem Goods and Services |
6. Non-monetary Indicators of Human Demand, Use or Benefit of Ecosystem Goods and Services |
6. Non-monetary Indicators of Human Demand, Use or Benefit of Ecosystem Goods and Services |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
6. Non-monetary Indicators of Human Demand, Use or Benefit of Ecosystem Goods and Services |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
4. Human-Produced Stressor or Enhancer of Ecosystem Goods and Services Production |
5. Ecosystem Attributes and Potential Supply of Ecosystem Goods and Services |
--Land use/land cover type or dominant habitat type |
--Human-caused release, presence or characteristics of polluting substances |
--CICES categories: Ecosystem goods and services - or landscape-level indices of suitability to supply EGS |
--CICES categories: Ecosystem goods and services - or landscape-level indices of suitability to supply EGS |
--CICES categories: Ecosystem goods and services - or landscape-level indices of suitability to supply EGS |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Land use/land cover type or dominant habitat type |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Land use/land cover type or dominant habitat type |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Land use/land cover type or dominant habitat type |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Human-caused release, presence or characteristics of polluting substances |
--Human-caused release, presence or characteristics of polluting substances |
--Human-caused release, presence or characteristics of polluting substances |
--Human-caused release, presence or characteristics of polluting substances |
--Human-caused release, presence or characteristics of polluting substances |
--Geographic position, horizontal or vertical |
--Spatial resolution or extent of cell, pixel, polygon |
--Ecological buffers or riparia |
--Nonnatural structures associated with ecosystem access, enhancement, restoration or water storage |
--Ecological buffers or riparia |
--Land use/land cover type or dominant habitat type |
--Ecological buffers or riparia |
--Ecological buffers or riparia |
--Ecological buffers or riparia |
--Land use/land cover type or dominant habitat type |
--Land use/land cover type or dominant habitat type |
--Land use/land cover type or dominant habitat type |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Ecological buffers or riparia |
--Land use/land cover type or dominant habitat type |
--Geographic position, horizontal or vertical |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Harvest activities and related ecological disturbance (except pollutant release) |
--CICES categories: Ecosystem goods and services - or landscape-level indices of suitability to supply EGS |
--Human-caused release, presence or characteristics of polluting substances |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Physical/chemical characteristics of nonliving ecosystem components |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Land use/land cover type or dominant habitat type |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Chemical (C, N, P, sediment/particulate) characteristics of ecosystem components |
--Chemical (C, N, P, sediment/particulate) characteristics of ecosystem components |
--Chemical (C, N, P, sediment/particulate) characteristics of ecosystem components |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Human structures (e.g., dams, buildings, armoring, etc.), activities (presence, noise) potentially related to ecological or aesthetic disturbance |
--Harvest activities and related ecological disturbance (except pollutant release) |
--Human-caused release, presence or characteristics of polluting substances |
--Human-caused release, presence or characteristics of polluting substances |
--Land use/land cover type or dominant habitat type |
--Demand for or use of provisioning services-Nutrition and ingestion |
--Physical/chemical characteristics of nonliving ecosystem components |
--Demand for or use of provisioning services-Materials |
--Physical/chemical characteristics of nonliving ecosystem components |
--Demand for or use of regulation & maintenance services-Mediation of wastes |
--Demand for or use of regulation & maintenance services-Mediation of wastes |
--Physical/chemical characteristics of nonliving ecosystem components |
--Demand for or use of regulation & maintenance services-Mediation of wastes |
--Demand for or use of regulation & maintenance services-Mediation of wastes |
--Demand for or use of regulation & maintenance services-Mediation of flows |
--Demand for or use of regulation & maintenance services-Mediation of wastes |
--Physical/chemical characteristics of nonliving ecosystem components |
--Demand for or use of regulation & maintenance services-Mediation of flows |
--Demand for or use of regulation & maintenance services-Mediation of flows |
--Demand for or use of regulation & maintenance services-Mediation of flows |
--Demand for or use of regulation & maintenance services-Mediation of wastes |
--Demand for or use of regulation & maintenance services-Mediation of wastes |
--Demand for or use of regulation & maintenance services-Mediation of wastes |
--Demand for or use of regulation & maintenance services-Mediation of wastes |
--Physical/chemical characteristics of nonliving ecosystem components |
--Demand for or use of provisioning services-Nutrition and ingestion |
--Physical/chemical characteristics of nonliving ecosystem components |
--CICES categories: Ecosystem goods and services - or landscape-level indices of suitability to supply EGS |
--Physical/chemical characteristics of nonliving ecosystem components |
--Human-caused release, presence or characteristics of polluting substances |
--Human-caused release, presence or characteristics of polluting substances |
--Physical/chemical characteristics of nonliving ecosystem components |
--Human-caused release, presence or characteristics of polluting substances |
--Human-caused release, presence or characteristics of polluting substances |
--Physical/chemical characteristics of nonliving ecosystem components |
--Human-caused release, presence or characteristics of polluting substances |
--Physical/chemical characteristics of nonliving ecosystem components |
--Physical/chemical characteristics of nonliving ecosystem components |
--Physical/chemical characteristics of nonliving ecosystem components |
--Physical/chemical characteristics of nonliving ecosystem components |
--Human-caused release, presence or characteristics of polluting substances |
--Human-caused release, presence or characteristics of polluting substances |
--Human-caused release, presence or characteristics of polluting substances |
--Human-caused release, presence or characteristics of polluting substances |
--Physical/chemical characteristics of nonliving ecosystem components |
|
----Agroecosystems |
----Human additions of fertilizers |
----Suitability to supply provisioning services-Materials |
----Suitability to supply provisioning services-Materials |
----Suitability to supply provisioning services-Materials |
----Agricultural and ranching activities and disturbance |
----Agricultural and ranching activities and disturbance |
----Agricultural and ranching activities and disturbance |
----Agricultural and ranching activities and disturbance |
----Agricultural and ranching activities and disturbance |
----Agricultural and ranching activities and disturbance |
----Other, multiple, unspecified or unclear |
----Agricultural and ranching activities and disturbance |
----Agricultural and ranching activities and disturbance |
----Agroecosystems |
----Agricultural and ranching activities and disturbance |
----Agroecosystems |
----Agricultural and ranching activities and disturbance |
----Human additions of fertilizers |
----Human additions of fertilizers |
----Human additions of fertilizers |
----Human additions of fertilizers |
----Human additions of fertilizers |
----Other, multiple, unspecified or unclear |
----Other, multiple, unspecified or unclear |
----Nonnatural structures associated with water storage |
----Other, multiple, unspecified or unclear |
----Grasslands/prairie/steppe |
----Other, multiple, unspecified or unclear |
----Other, multiple, unspecified or unclear |
----Other, multiple, unspecified or unclear |
----Grasslands/prairie/steppe |
----Grasslands/prairie/steppe |
----Other, multiple, unspecified or unclear |
----Agricultural and ranching activities and disturbance |
----Agricultural and ranching activities and disturbance |
----Agricultural and ranching activities and disturbance |
----Agricultural and ranching activities and disturbance |
----Other, multiple, unspecified or unclear |
----Inland wetlands |
----Slope, roughness, ruggedness |
----Agricultural and ranching activities and disturbance |
----Agricultural and ranching activities and disturbance |
----Suitability to supply provisioning services-Materials |
----Human additions of fertilizers |
----Agricultural and ranching activities and disturbance |
----Agricultural and ranching activities and disturbance |
----Physical/chemical characteristics of soils, substrates, rocks |
----Agricultural and ranching activities and disturbance |
----Agroecosystems |
----Agricultural and ranching activities and disturbance |
----Agricultural and ranching activities and disturbance |
----Agricultural and ranching activities and disturbance |
----Agricultural and ranching activities and disturbance |
----Agricultural and ranching activities and disturbance |
----Agricultural and ranching activities and disturbance |
----Carbon-related characteristics of ecosystem components |
----Phosphorus-related characteristics of ecosystem components |
----Phosphorus-related characteristics of ecosystem components |
----Agricultural and ranching activities and disturbance |
----Presence of man-made structures (e.g., dams, buildings, armoring, etc.) potentially related to ecological or aesthetic disturbance |
----Agricultural and ranching activities and disturbance |
----Human additions of fertilizers |
----Human additions of fertilizers |
----Inland wetlands |
----Cultivated crops |
----Physical/chemical characteristics of water |
----Ground water for non-drinking purposes |
----Physical/chemical characteristics of soils, substrates, rocks |
----Filtration/sequestration/storage/accumulation by ecosystems |
----Filtration/sequestration/storage/accumulation by ecosystems |
----Physical/chemical characteristics of water |
----Filtration/sequestration/storage/accumulation by ecosystems |
----Filtration/sequestration/storage/accumulation by ecosystems |
----Hydrological cycle and water flow maintenance |
----Filtration/sequestration/storage/accumulation by ecosystems |
----Physical/chemical characteristics of soils, substrates, rocks |
----Hydrological cycle and water flow maintenance |
----Hydrological cycle and water flow maintenance |
----Hydrological cycle and water flow maintenance |
----Filtration/sequestration/storage/accumulation by ecosystems |
----Filtration/sequestration/storage/accumulation by ecosystems |
----Filtration/sequestration/storage/accumulation by ecosystems |
----Filtration/sequestration/storage/accumulation by ecosystems |
----Physical/chemical characteristics of soils, substrates, rocks |
----Cultivated crops |
----Physical/chemical characteristics of water |
----Suitability to supply provisioning services-Materials |
----Physical/chemical characteristics of soils, substrates, rocks |
----Release, presence or characteristics of reactive forms of nitrogen in air or water |
----Release, presence or characteristics of phosphorus in air or water |
----Physical/chemical characteristics of water |
----Release, presence or characteristics of phosphorus in air or water |
----Release, presence or characteristics of reactive forms of nitrogen in air or water |
----Physical/chemical characteristics of water |
----Release, presence or characteristics of reactive forms of nitrogen in air or water |
----Physical/chemical characteristics of soils, substrates, rocks |
----Physical/chemical characteristics of water |
----Physical/chemical characteristics of water |
----Physical/chemical characteristics of water |
----Release, presence or characteristics of reactive forms of nitrogen in air or water |
----Release, presence or characteristics of phosphorus in air or water |
----Release, presence or characteristics of reactive forms of nitrogen in air or water |
----Release, presence or characteristics of phosphorus in air or water |
----Physical/chemical characteristics of soils, substrates, rocks |
||
------Other, multiple, unspecified or unclear |
------Ground water for non-drinking purposes |
------Ground water for non-drinking purposes |
------Ground water for non-drinking purposes |
------Other, multiple, unspecified or unclear |
------Row crop |
------Ground water for non-drinking purposes |
------Soil hydrologic characteristics |
------Other, multiple, unspecified or unclear |
------Carbon presence (in terrestrial or aquatic ecosystem components) |
------Phosphorus presence (in terrestrial ecosystem components) |
------Phosphorus presence (in terrestrial ecosystem components) |
------Water volume or flow in aquifers |
------Soil, slope or land stability or erosiveness |
------Water volume or flow over ground surface (i.e., runoff) |
------Soil, slope or land stability or erosiveness |
------Soil, slope or land stability or erosiveness |
------Water volume or flow in aquifers |
------Ground water for non-drinking purposes |
------Soil, slope or land stability or erosiveness |
------Water volume or flow over ground surface (i.e., runoff) |
------Water volume or flow over ground surface (i.e., runoff) |
------Soil, slope or land stability or erosiveness |
------Water volume or flow over ground surface (i.e., runoff) |
------Water volume or flow over ground surface (i.e., runoff) |
------Water volume or flow over ground surface (i.e., runoff) |
------Soil, slope or land stability or erosiveness |
Crop type ?Comment:To add a crop to the rotation, click Add Crop to Rotation. The user is then asked to select a crop from the pick list, a tillage type (No-till, reduced till, or intensive till), and rotation year. The crop list is customized according to the region in which the project is located. The rotation year indicates the sequence of the crop within the crop schedule, it does not represent the calendar year. Once the user has selected a crop type, tillage type and rotation year, clicking Upload will add the crop to the crop schedule. Once a crop is added to the crop schedule you will note that it includes several default management characteristics including a planting date, fertilizer applications, tillage schedule, and harvest. These operations can be modified or deleted as needed and new operations can be added. |
Autofertigation total nitrogen concentration ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Autofertigation is the application of fertilizers, soil amendments, or other water-soluble products through an autoirrigation system. Autofertigation is an automatic fertilization process in which fertilizer is dissolved and distributed through the irrigation system. This makes autofertigation very similar to autoirrigation with the only additional user input required being nitrogen concentration. The amount of nitrogen in irrigation water in parts per million. Total N applied through autofertigation will be dependent upon the overall irrigation frequency which in turn is dependent upon water stress, frequency and maximum application factors set by the user. |
Autoirrigate a maximum frequency of every (0-365) days ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This field is asking for the maximum frequency (in days) that irrigation can take place. If the frequency is set to 1, then irrigation can occur every day. If frequency is set to 7 then irrigation can occur, at most, once a week. The value can be any whole number greater than or equal to zero and less than or equal to 365. |
Autoirrigation efficiency ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This value is the fraction of irrigation application that is not lost to runoff. This must be a value that is greater than 0 and less than or equal to 1. The closer the value is to 0, the greater the percentage of water lost to runoff and does not reach the crop. A value of 1 means that no water was lost to runoff. Different irrigation systems have different irrigation efficiencies. NTT supplies typical irrigation efficiency values for the irrigation type selected, but these values can be modified by the user. |
Autoirrigation type ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. Irrigation types include sprinkler, furrow/flood, drip, and furrow diking. |
Burn date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Continuous grazing animal type ?Comment:User indicates the type of animals being grazed on the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing animal units ?Comment:User indicates the total animal units being grazed on the field. Animal units represent 1,000 lbs of live animal weight. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing end date ?Comment:User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing hours in field ?Comment:User indicates the total hours per day that animals are grazed in the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing start date ?Comment:User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Countour buffer (strip farming crop grass/vegetation ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. Contour buffer strips are permanent, narrow bands of grasses/legumes planted on the contour (across or perpendicular to a slope) between wider strips of crops. Contour buffers trap sediment and enhance filtration of nutrients and pesticides by slowing down runoff that could enter the local surface waters. This is the type of grass or vegetation that will be present in the buffer sections of the contour buffer. |
Cover crop planting date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Cover crop planting method ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Cover crop type ?Comment:Cover crops are not fertilized and are not harvested, rather they are chopped prior to planting of the next crop in the rotation. This optional variable is constant with respect to Crop type for this specific application. |
Cover crop year ?Comment:The cover crop year should indicate the year within the rotation that the cover crop is planted. This optional variable is constant with respect to Crop type for this specific application. |
Crop width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width, in feet, of the strips of the main crop that was planted. It can be any number greater than 0. Crop width, along with buffer width, determine the number of buffer and crop strips in the field. |
End of season date ?Comment:End of season indicates to the model that the crop is removed from the field. If an End of Season operation is not present, then the model assumes that the crop is left growing. End of season should be used for all annual crops. For certain perennial crops like hay and pasture, End of Season operations may be absent from the crop schedule. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer amount ?Comment:User needs to indicate the amount of fertilizer applied. Units will vary depending on the type of fertilizer selected (lbs/ac, tons/ac, 1000 gals/ac). This variable is constant with respect to Crop type for the specific model application. |
Fertilizer category ?Comment:User must indicate the fertilizer category (commercial, liquid manure, or solid manure). This variable is constant with respect to Crop type for the specific model application. |
Fertilizer compostion ?Comment:For commercial fertilizer, these fields indicate the N and P composition. These fields are pre-filled based on the fertilizer type selected, but can be modified if needed. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer depth ?Comment:If the fertilizer is incorporated, user should indicate the depth of incorporation here. If fertilizer is not incorporated, this field can be left blank. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer type ?Comment:The fertilizer type pick list will vary depending on the fertilizer category selected. For manure fertilizer, pick list will contain types of animal manure. This variable is constant with respect to Crop type for the specific model application. |
Field (area of interest) ?Comment:After creating a new project, users will be asked to define the location of the project using the interactive Google map. The interactive map allows the user to define one or more areas of interest (AOI). The area of interest should correlate to fields within the project area. The map is ONLY used for mainland United States. If you would like to simulate using an area outside of mainland United States, follow the instructions for User Input. When defining the AOI, the underlying weather, soils, and slope information is retrieved from the underlying spatial data. There are two ways to define your areas of interest: you may manually draw your areas of interest using the zoom features and drawing tools on the interactive map, or you may upload your own shapefile. After drawing the field, a message will pop up telling the user to enter the name of the AOI. |
Field area ?Comment:Field area displays the calculated area of the field in acres. The user may refine this value if needed. |
Forest strip width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the width of the forest buffer (not including the grass strip). |
Fraction of area controlled by ponds/WASCB ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. Water and sediment control basins (WASCOBs), or ponds, consist of an embankment across the slope of a field or minor waterway to temporarily detain and release water through a piped outlet or through infiltration. They are constructed perpendicular to the flow direction and parallel to each other. WASCOBs are usually installed in areas where the land is relatively steep and undulating. They detain water from contributing areas, inducing sedimentation and controlling the release of water, thereby reducing the erosive power of the water downstream. Additional benefits are settling of sediment-bound pollutants and some infiltration. Only one input is required for ponds: fraction of area controlled by ponds. This is the fraction (a value between 0 and 1) of the field runoff that flows through (is controlled by) the pond/WASCOB. As modeled, ponds only treat runoff that originates in this field. Inflow from other fields is not routed through the ponds. Ponds/WASCOBs are assumed to be within field. |
Fraction of field treated by buffer ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the estimated fraction (0.00-1.00) of the runoff from the field that is routed through the buffer. |
Fraction of field treated by grass waterway ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. The fraction of the field that drains to the grass waterway. A number between 0.00 and 1.00. |
Grass buffer vegetation type ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the type of grass or vegetation that is planted in the Filter Strip. |
Grass buffer/forest buffer area ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. Forest buffers are linear wooded areas with well-developed root systems, an organic surface layer, and understory vegetation. When they are adjacent to open water they are referred to as riparian forest buffers. Non-riparian buffers are linear wooded areas along down-slope field edges. Forest buffers trap sediment and increase infiltration, thereby reducing sediment and nutrient losses. Forest buffers often include a grass buffer between the field and the forested buffer. If present, please also include the width of the grass buffer. Grass buffers, also known as a filter strips, are an area of vegetation, generally narrow in width and long across the downslope edge of a field, that slows the rate of runoff, allowing sediments, organic matter, and other pollutants that are being conveyed by the water to be removed by settling out. Filter strips reduce erosion and the accompanying sediment-bound pollution. In NTT, filter strips function by providing for better infiltration of soluble nutrients, trapping of sediment, and increased uptake of water and nutrients by the filter strip vegetation. The saturated conductivity value is also modified for filter strip simulation in NTT. The inputs for grass buffers are the same as for forest buffers (see Forest Buffer), with the additional requirement that the user specify type of vegetation. This is the total area of the Riparian Buffer. This field is optional. If left blank, the area will automatically be calculated using the width of the buffer and the length of the field edge (where the field edge is calculated as the square root of the area of the field). |
Grass strip width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the width of the grass strip between the crop and the forested buffer, if present. |
Grass waterway crop ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. A grassed waterway is a natural or constructed swale, shaped or graded and established in suitable vegetation for the safe conveyance of runoff. Grassed waterways are designed to prevent soil erosion while draining runoff water from adjacent cropland. As water travels down the waterway, the grass vegetation prevents erosion that would otherwise result from concentrated flows and uptakes nutrients. Grassed waterways also help prevent gully erosion in areas of concentrated flow. For example, they may be used to drain runoff from terraces and runoff water diversions. By intercepting runoff, grassed waterways slow erosion and minimize nutrient losses. |
Grass waterway width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width of the grassed waterway, in feet, including both sides of the vegetated channel. This can be any number greater than 0. |
Grass/vegetation width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width, in feet, of the buffer strips. It can be any number greater than 0. Buffer width, along with crop width, determine the number of buffer and crop strips in the field. |
Harvest date ?Comment:A default date is automatically entered for harvest. This can be modified as needed. This variable is constant with respect to Crop type for the specific model application. |
Irrigation amount ?Comment:User indicates the volume of water applied in this irrigation event in inches. This optional variable is constant with respect to Crop type for the specific application. |
Irrigation efficiency ?Comment:This field defaults to a typical irrigation efficiency value (as a fraction) based on the irrigation method that is selected. This value can be modified. This optional variable is constant with respect to Crop type for the specific application. |
Irrigation method ?Comment:An optional variable that is constant with respect to Crop type for the specific application. |
Is buffer included in AOI? (y/n) ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. If buffer has been drawn as part of the AOI, then the area will be subtracted from the crop area. If it has not been drawn as part of the AOI, it will be assumed to be adjacent to one edge of the field. |
Is wetland area included in your AOI? (y/n) ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Users indicate here whether the AOI representing the field includes the wetland feature within the drawn polygon or if the wetland feature lies outside of the AOI. If the wetland feature is included in the AOI, then the wetland acres will be subtracted from the field area. |
Land leveling slope reduction ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. Land leveling is used to reduce the slope on high soil slopes. By reducing the slope, the surface land is better able to retain water and soil, reducing erosion and increasing infiltration. The input for land leveling is slope reduction percentage. This is the percent reduction in the slope of the soil. The number can be any percentage between 0% and 100%. The closer the slope is to 100, the more the slope is reduced. |
Lime amount ?Comment:User must indicate amount of lime applied (lbs/ac). This optional variable is constant with respect to Crop type for this specific application. |
Lime date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Maximum single application ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This value signifies the maximum amount of water than can be applied in a single irrigation event. It is in inches, and it can be any number greater than 0. If there are no constraints on the maximum single application, this value should be set to a high number. |
Moisture content ?Comment:For manure fertilizer, this is the percentage, by weight, of moisture content in the manure. Typical values for each manure type are provided, but can be modified by the user. This variable is constant with respect to Crop type for the specific model application. |
Number of consecutive days grazed at a time (in each paddock) ?Comment:User indicates the number of days livestock will spend in each paddock before being rotated to a new paddock. This optional variable is constant with respect to Crop type for this specific application. |
Pasture rest time between grazing ?Comment:User indicates the number of days that the pasture is rested between rotational grazing cycles. This optional variable is constant with respect to Crop type for this specific application. |
Plant water stress factor ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. The water stress factor indicates the water stress level of the crop. This is the value that is used to trigger the start of auto irrigation. For example, if water stress is set to 0.8 then NTT will trigger an irrigation event when the crop is 80% water-stressed, as long as conditions for maximum frequency are also met. The plant water stress factor can be any value greater than 0 and less than or equal to 1. The closer the value is to 100, the less water stress is allowed before the automatic irrigation is turned on. |
Planting date ?Comment:This variable is constant with respect to Crop type for the specific model application. |
Rotation year ?Comment:The rotation year indicates the sequence of the crop within the crop schedule, it does not represent the calendar year. This variable is constant with respect to Crop type for the specific model application. |
Rotational grazing animal type ?Comment:User indicates the type of animals being grazed on the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing animal units ?Comment:User indicates the total animal units being grazed on the field. Animal units represent 1,000 lbs of live weight. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing end date ?Comment:The rotational grazing operation, unlike continuous grazing, assumes that the pasture is divided into paddocks and that livestock are moved through the paddocks as needed. Thus, each paddock is given a recovery period between grazing events, improving vegetative cover. User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing hours in field ?Comment:User indicates the total hours per day that animals are grazed in the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing start date ?Comment:The rotational grazing operation, unlike continuous grazing, assumes that the pasture is divided into paddocks and that livestock are moved through the paddocks as needed. Thus, each paddock is given a recovery period between grazing events, improving vegetative cover. User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Seed amount ?Comment:This field is pre-filled with standard seeding rates for each crop type. If the user has more specific information on seeding rate they may enter it. This variable is constant with respect to Crop type for the specific model application. |
Soil organic matter ?Comment:The default soil organic matter (%) value returned by the SSURGO soils database is displayed for each soil in the soils list. However, if the user has more precise data they may enter it here. |
Soil P ?Comment:Users should enter the soil phosphorus test value for their field, if available. If None was selected for the P test then this field will be disabled and a minimum phosphorus concentration in the soil will be used. Similarly, if a soil test is selected, but the field Soil P value is left blank, the tool will assume a minimum phosphorus concentration in the soil. |
Soil P test ?Comment:The user should select a soil test, if applicable, that was used to determine the soil phosphorus. Currently NTT includes conversions for the Fe-strip test, Olsen, Bray-1, and Mehlich-3 tests. If you have used a different test, please select Other. If you do not have a soil P test for your soil, leave these fields blank and NTT will use default soil P values. |
Terrace system (y/n) ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. A terrace system is a leveled section of a hill cultivated area, designed as a method of soil conservation to slow or prevent the rapid surface runoff of water. Terraces decrease hill slope-length, reduce formation of gullies, and intercept and conduct runoff to a safe outlet thereby reducing sediment content in runoff water. Often, in application the landscape is formed into multiple terraces, giving a stepped appearance. Terraces are simulated by reducing the practice factor (PEC). |
Tile drain depth ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. For NTT applications, underground drainage systems are simulated in APEX. The depth of the drainage system to reduce plant stress is a key parameter used in simulating tile drainage systems in NTT. Tile drainage simulation in NTT increases subsurface flow, which may provide an avenue for increased nutrient losses in subsurface flow. The only input for tile drains is depth. This is the depth in feet at which the drainage system is installed. It is any number greater than 0. |
Tillage ?Comment:User must indicate the tillage method using the drop down selection. This variable is constant with respect to Crop type for the specific model application. |
Total N concentration ?Comment:For manure fertilizer, the user should indicate the total N content per ton of solid manure or per 1000 gallons of liquid manure. Typical values are pre-filled for the user, but can be modified. This variable is constant with respect to Crop type for the specific model application. |
Total P concentration ?Comment:For manure fertilizer, the user should indicate the total P content per ton of solid manure or per 1000 gallons of liquid manure. Typical values are pre-filled for the user, but can be modified. This variable is constant with respect to Crop type for the specific model application. |
Wetland area ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Wetlands are those areas that are inundated or saturated by surface or groundwater at a frequency and duration sufficient to support, and that under normal circumstances do support, a prevalence of vegetation typically adapted for life in saturated soil conditions. Wetlands generally include swamps, marshes, bogs and similar areas. The wetland area is simulated as a shallow reservoir (1 ft. depth) with growing wetland vegetation – it is essentially simulated as an artificial wetland and not a natural wetland. The slope of wetland area is set as 1%. Simulated wetlands trap sediment, reduce runoff, increase infiltration, and also increase uptake of water and nutrients by the vegetation in the area covered by the wetland. The area of the wetland is input in acres. Since this area is no longer able to be used for crop production, there may be a lower total crop yield (although there may be a greater crop yield/acre). |
Change in crop yield ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in deep percolation loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in irrigation applied loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in manure erosion ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in organic N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in organic P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in other water info loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in PO4 loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in runoff N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in subsurface flor loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in subsurface N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface erosion loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface flow loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface/subsurface/tile drain flow loss |
Change in tile drain flow loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in tile drain N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in tile drain P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total sediment loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Crop yield ?Comment:The scenario results presented in your table represent an AVERAGE annual yield across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Deep percolation loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Irrigation applied loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Manure erosion loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Organic N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Organic P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Other water info loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
PO4 loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Runoff N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Subsurface flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Subsurface N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface erosion loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface/subsurface/tile drain flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total sediment loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
|
Spatial Extent Area
variable.detail.spExtentHelp
?
|
Not applicable | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Spatially Distributed?
variable.detail.spDistributedHelp
?
|
No | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No | No |
Observations Spatially Patterned?
variable.detail.regularSpGrainHelp
?
|
Not applicable | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Spatial Grain Type
variable.detail.spGrainTypeHelp
?
|
Not applicable | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not recorded for Constant or Paarameter Variables | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Spatial Grain Size
variable.detail.spGrainSizeHelp
?
|
Not applicable | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Spatial Density
variable.detail.spDensityHelp
?
|
Not applicable | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
EnviroAtlas URL
variable.detail.enviroAtlasURLHelp
?
|
GAP Ecological Systems | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | GAP Ecological Systems | Agricultural water use (million gallons/day) | GAP Ecological Systems | Agricultural water use (million gallons/day) | Water supply from NID reservoirs (million gallons) | GAP Ecological Systems | GAP Ecological Systems | GAP Ecological Systems | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | GAP Ecological Systems | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | GAP Ecological Systems | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | Agricultural water use (million gallons/day) | GAP Ecological Systems |
Crop type ?Comment:To add a crop to the rotation, click Add Crop to Rotation. The user is then asked to select a crop from the pick list, a tillage type (No-till, reduced till, or intensive till), and rotation year. The crop list is customized according to the region in which the project is located. The rotation year indicates the sequence of the crop within the crop schedule, it does not represent the calendar year. Once the user has selected a crop type, tillage type and rotation year, clicking Upload will add the crop to the crop schedule. Once a crop is added to the crop schedule you will note that it includes several default management characteristics including a planting date, fertilizer applications, tillage schedule, and harvest. These operations can be modified or deleted as needed and new operations can be added. |
Autofertigation total nitrogen concentration ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Autofertigation is the application of fertilizers, soil amendments, or other water-soluble products through an autoirrigation system. Autofertigation is an automatic fertilization process in which fertilizer is dissolved and distributed through the irrigation system. This makes autofertigation very similar to autoirrigation with the only additional user input required being nitrogen concentration. The amount of nitrogen in irrigation water in parts per million. Total N applied through autofertigation will be dependent upon the overall irrigation frequency which in turn is dependent upon water stress, frequency and maximum application factors set by the user. |
Autoirrigate a maximum frequency of every (0-365) days ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This field is asking for the maximum frequency (in days) that irrigation can take place. If the frequency is set to 1, then irrigation can occur every day. If frequency is set to 7 then irrigation can occur, at most, once a week. The value can be any whole number greater than or equal to zero and less than or equal to 365. |
Autoirrigation efficiency ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This value is the fraction of irrigation application that is not lost to runoff. This must be a value that is greater than 0 and less than or equal to 1. The closer the value is to 0, the greater the percentage of water lost to runoff and does not reach the crop. A value of 1 means that no water was lost to runoff. Different irrigation systems have different irrigation efficiencies. NTT supplies typical irrigation efficiency values for the irrigation type selected, but these values can be modified by the user. |
Autoirrigation type ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. Irrigation types include sprinkler, furrow/flood, drip, and furrow diking. |
Burn date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Continuous grazing animal type ?Comment:User indicates the type of animals being grazed on the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing animal units ?Comment:User indicates the total animal units being grazed on the field. Animal units represent 1,000 lbs of live animal weight. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing end date ?Comment:User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing hours in field ?Comment:User indicates the total hours per day that animals are grazed in the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing start date ?Comment:User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Countour buffer (strip farming crop grass/vegetation ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. Contour buffer strips are permanent, narrow bands of grasses/legumes planted on the contour (across or perpendicular to a slope) between wider strips of crops. Contour buffers trap sediment and enhance filtration of nutrients and pesticides by slowing down runoff that could enter the local surface waters. This is the type of grass or vegetation that will be present in the buffer sections of the contour buffer. |
Cover crop planting date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Cover crop planting method ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Cover crop type ?Comment:Cover crops are not fertilized and are not harvested, rather they are chopped prior to planting of the next crop in the rotation. This optional variable is constant with respect to Crop type for this specific application. |
Cover crop year ?Comment:The cover crop year should indicate the year within the rotation that the cover crop is planted. This optional variable is constant with respect to Crop type for this specific application. |
Crop width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width, in feet, of the strips of the main crop that was planted. It can be any number greater than 0. Crop width, along with buffer width, determine the number of buffer and crop strips in the field. |
End of season date ?Comment:End of season indicates to the model that the crop is removed from the field. If an End of Season operation is not present, then the model assumes that the crop is left growing. End of season should be used for all annual crops. For certain perennial crops like hay and pasture, End of Season operations may be absent from the crop schedule. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer amount ?Comment:User needs to indicate the amount of fertilizer applied. Units will vary depending on the type of fertilizer selected (lbs/ac, tons/ac, 1000 gals/ac). This variable is constant with respect to Crop type for the specific model application. |
Fertilizer category ?Comment:User must indicate the fertilizer category (commercial, liquid manure, or solid manure). This variable is constant with respect to Crop type for the specific model application. |
Fertilizer compostion ?Comment:For commercial fertilizer, these fields indicate the N and P composition. These fields are pre-filled based on the fertilizer type selected, but can be modified if needed. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer depth ?Comment:If the fertilizer is incorporated, user should indicate the depth of incorporation here. If fertilizer is not incorporated, this field can be left blank. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer type ?Comment:The fertilizer type pick list will vary depending on the fertilizer category selected. For manure fertilizer, pick list will contain types of animal manure. This variable is constant with respect to Crop type for the specific model application. |
Field (area of interest) ?Comment:After creating a new project, users will be asked to define the location of the project using the interactive Google map. The interactive map allows the user to define one or more areas of interest (AOI). The area of interest should correlate to fields within the project area. The map is ONLY used for mainland United States. If you would like to simulate using an area outside of mainland United States, follow the instructions for User Input. When defining the AOI, the underlying weather, soils, and slope information is retrieved from the underlying spatial data. There are two ways to define your areas of interest: you may manually draw your areas of interest using the zoom features and drawing tools on the interactive map, or you may upload your own shapefile. After drawing the field, a message will pop up telling the user to enter the name of the AOI. |
Field area ?Comment:Field area displays the calculated area of the field in acres. The user may refine this value if needed. |
Forest strip width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the width of the forest buffer (not including the grass strip). |
Fraction of area controlled by ponds/WASCB ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. Water and sediment control basins (WASCOBs), or ponds, consist of an embankment across the slope of a field or minor waterway to temporarily detain and release water through a piped outlet or through infiltration. They are constructed perpendicular to the flow direction and parallel to each other. WASCOBs are usually installed in areas where the land is relatively steep and undulating. They detain water from contributing areas, inducing sedimentation and controlling the release of water, thereby reducing the erosive power of the water downstream. Additional benefits are settling of sediment-bound pollutants and some infiltration. Only one input is required for ponds: fraction of area controlled by ponds. This is the fraction (a value between 0 and 1) of the field runoff that flows through (is controlled by) the pond/WASCOB. As modeled, ponds only treat runoff that originates in this field. Inflow from other fields is not routed through the ponds. Ponds/WASCOBs are assumed to be within field. |
Fraction of field treated by buffer ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the estimated fraction (0.00-1.00) of the runoff from the field that is routed through the buffer. |
Fraction of field treated by grass waterway ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. The fraction of the field that drains to the grass waterway. A number between 0.00 and 1.00. |
Grass buffer vegetation type ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the type of grass or vegetation that is planted in the Filter Strip. |
Grass buffer/forest buffer area ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. Forest buffers are linear wooded areas with well-developed root systems, an organic surface layer, and understory vegetation. When they are adjacent to open water they are referred to as riparian forest buffers. Non-riparian buffers are linear wooded areas along down-slope field edges. Forest buffers trap sediment and increase infiltration, thereby reducing sediment and nutrient losses. Forest buffers often include a grass buffer between the field and the forested buffer. If present, please also include the width of the grass buffer. Grass buffers, also known as a filter strips, are an area of vegetation, generally narrow in width and long across the downslope edge of a field, that slows the rate of runoff, allowing sediments, organic matter, and other pollutants that are being conveyed by the water to be removed by settling out. Filter strips reduce erosion and the accompanying sediment-bound pollution. In NTT, filter strips function by providing for better infiltration of soluble nutrients, trapping of sediment, and increased uptake of water and nutrients by the filter strip vegetation. The saturated conductivity value is also modified for filter strip simulation in NTT. The inputs for grass buffers are the same as for forest buffers (see Forest Buffer), with the additional requirement that the user specify type of vegetation. This is the total area of the Riparian Buffer. This field is optional. If left blank, the area will automatically be calculated using the width of the buffer and the length of the field edge (where the field edge is calculated as the square root of the area of the field). |
Grass strip width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the width of the grass strip between the crop and the forested buffer, if present. |
Grass waterway crop ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. A grassed waterway is a natural or constructed swale, shaped or graded and established in suitable vegetation for the safe conveyance of runoff. Grassed waterways are designed to prevent soil erosion while draining runoff water from adjacent cropland. As water travels down the waterway, the grass vegetation prevents erosion that would otherwise result from concentrated flows and uptakes nutrients. Grassed waterways also help prevent gully erosion in areas of concentrated flow. For example, they may be used to drain runoff from terraces and runoff water diversions. By intercepting runoff, grassed waterways slow erosion and minimize nutrient losses. |
Grass waterway width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width of the grassed waterway, in feet, including both sides of the vegetated channel. This can be any number greater than 0. |
Grass/vegetation width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width, in feet, of the buffer strips. It can be any number greater than 0. Buffer width, along with crop width, determine the number of buffer and crop strips in the field. |
Harvest date ?Comment:A default date is automatically entered for harvest. This can be modified as needed. This variable is constant with respect to Crop type for the specific model application. |
Irrigation amount ?Comment:User indicates the volume of water applied in this irrigation event in inches. This optional variable is constant with respect to Crop type for the specific application. |
Irrigation efficiency ?Comment:This field defaults to a typical irrigation efficiency value (as a fraction) based on the irrigation method that is selected. This value can be modified. This optional variable is constant with respect to Crop type for the specific application. |
Irrigation method ?Comment:An optional variable that is constant with respect to Crop type for the specific application. |
Is buffer included in AOI? (y/n) ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. If buffer has been drawn as part of the AOI, then the area will be subtracted from the crop area. If it has not been drawn as part of the AOI, it will be assumed to be adjacent to one edge of the field. |
Is wetland area included in your AOI? (y/n) ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Users indicate here whether the AOI representing the field includes the wetland feature within the drawn polygon or if the wetland feature lies outside of the AOI. If the wetland feature is included in the AOI, then the wetland acres will be subtracted from the field area. |
Land leveling slope reduction ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. Land leveling is used to reduce the slope on high soil slopes. By reducing the slope, the surface land is better able to retain water and soil, reducing erosion and increasing infiltration. The input for land leveling is slope reduction percentage. This is the percent reduction in the slope of the soil. The number can be any percentage between 0% and 100%. The closer the slope is to 100, the more the slope is reduced. |
Lime amount ?Comment:User must indicate amount of lime applied (lbs/ac). This optional variable is constant with respect to Crop type for this specific application. |
Lime date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Maximum single application ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This value signifies the maximum amount of water than can be applied in a single irrigation event. It is in inches, and it can be any number greater than 0. If there are no constraints on the maximum single application, this value should be set to a high number. |
Moisture content ?Comment:For manure fertilizer, this is the percentage, by weight, of moisture content in the manure. Typical values for each manure type are provided, but can be modified by the user. This variable is constant with respect to Crop type for the specific model application. |
Number of consecutive days grazed at a time (in each paddock) ?Comment:User indicates the number of days livestock will spend in each paddock before being rotated to a new paddock. This optional variable is constant with respect to Crop type for this specific application. |
Pasture rest time between grazing ?Comment:User indicates the number of days that the pasture is rested between rotational grazing cycles. This optional variable is constant with respect to Crop type for this specific application. |
Plant water stress factor ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. The water stress factor indicates the water stress level of the crop. This is the value that is used to trigger the start of auto irrigation. For example, if water stress is set to 0.8 then NTT will trigger an irrigation event when the crop is 80% water-stressed, as long as conditions for maximum frequency are also met. The plant water stress factor can be any value greater than 0 and less than or equal to 1. The closer the value is to 100, the less water stress is allowed before the automatic irrigation is turned on. |
Planting date ?Comment:This variable is constant with respect to Crop type for the specific model application. |
Rotation year ?Comment:The rotation year indicates the sequence of the crop within the crop schedule, it does not represent the calendar year. This variable is constant with respect to Crop type for the specific model application. |
Rotational grazing animal type ?Comment:User indicates the type of animals being grazed on the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing animal units ?Comment:User indicates the total animal units being grazed on the field. Animal units represent 1,000 lbs of live weight. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing end date ?Comment:The rotational grazing operation, unlike continuous grazing, assumes that the pasture is divided into paddocks and that livestock are moved through the paddocks as needed. Thus, each paddock is given a recovery period between grazing events, improving vegetative cover. User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing hours in field ?Comment:User indicates the total hours per day that animals are grazed in the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing start date ?Comment:The rotational grazing operation, unlike continuous grazing, assumes that the pasture is divided into paddocks and that livestock are moved through the paddocks as needed. Thus, each paddock is given a recovery period between grazing events, improving vegetative cover. User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Seed amount ?Comment:This field is pre-filled with standard seeding rates for each crop type. If the user has more specific information on seeding rate they may enter it. This variable is constant with respect to Crop type for the specific model application. |
Soil organic matter ?Comment:The default soil organic matter (%) value returned by the SSURGO soils database is displayed for each soil in the soils list. However, if the user has more precise data they may enter it here. |
Soil P ?Comment:Users should enter the soil phosphorus test value for their field, if available. If None was selected for the P test then this field will be disabled and a minimum phosphorus concentration in the soil will be used. Similarly, if a soil test is selected, but the field Soil P value is left blank, the tool will assume a minimum phosphorus concentration in the soil. |
Soil P test ?Comment:The user should select a soil test, if applicable, that was used to determine the soil phosphorus. Currently NTT includes conversions for the Fe-strip test, Olsen, Bray-1, and Mehlich-3 tests. If you have used a different test, please select Other. If you do not have a soil P test for your soil, leave these fields blank and NTT will use default soil P values. |
Terrace system (y/n) ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. A terrace system is a leveled section of a hill cultivated area, designed as a method of soil conservation to slow or prevent the rapid surface runoff of water. Terraces decrease hill slope-length, reduce formation of gullies, and intercept and conduct runoff to a safe outlet thereby reducing sediment content in runoff water. Often, in application the landscape is formed into multiple terraces, giving a stepped appearance. Terraces are simulated by reducing the practice factor (PEC). |
Tile drain depth ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. For NTT applications, underground drainage systems are simulated in APEX. The depth of the drainage system to reduce plant stress is a key parameter used in simulating tile drainage systems in NTT. Tile drainage simulation in NTT increases subsurface flow, which may provide an avenue for increased nutrient losses in subsurface flow. The only input for tile drains is depth. This is the depth in feet at which the drainage system is installed. It is any number greater than 0. |
Tillage ?Comment:User must indicate the tillage method using the drop down selection. This variable is constant with respect to Crop type for the specific model application. |
Total N concentration ?Comment:For manure fertilizer, the user should indicate the total N content per ton of solid manure or per 1000 gallons of liquid manure. Typical values are pre-filled for the user, but can be modified. This variable is constant with respect to Crop type for the specific model application. |
Total P concentration ?Comment:For manure fertilizer, the user should indicate the total P content per ton of solid manure or per 1000 gallons of liquid manure. Typical values are pre-filled for the user, but can be modified. This variable is constant with respect to Crop type for the specific model application. |
Wetland area ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Wetlands are those areas that are inundated or saturated by surface or groundwater at a frequency and duration sufficient to support, and that under normal circumstances do support, a prevalence of vegetation typically adapted for life in saturated soil conditions. Wetlands generally include swamps, marshes, bogs and similar areas. The wetland area is simulated as a shallow reservoir (1 ft. depth) with growing wetland vegetation – it is essentially simulated as an artificial wetland and not a natural wetland. The slope of wetland area is set as 1%. Simulated wetlands trap sediment, reduce runoff, increase infiltration, and also increase uptake of water and nutrients by the vegetation in the area covered by the wetland. The area of the wetland is input in acres. Since this area is no longer able to be used for crop production, there may be a lower total crop yield (although there may be a greater crop yield/acre). |
Change in crop yield ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in deep percolation loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in irrigation applied loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in manure erosion ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in organic N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in organic P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in other water info loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in PO4 loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in runoff N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in subsurface flor loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in subsurface N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface erosion loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface flow loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface/subsurface/tile drain flow loss |
Change in tile drain flow loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in tile drain N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in tile drain P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total sediment loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Crop yield ?Comment:The scenario results presented in your table represent an AVERAGE annual yield across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Deep percolation loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Irrigation applied loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Manure erosion loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Organic N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Organic P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Other water info loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
PO4 loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Runoff N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Subsurface flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Subsurface N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface erosion loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface/subsurface/tile drain flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total sediment loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
|
Temporal Extent
variable.detail.tempExtentHelp
?
|
Not applicable | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 | 35 yr | 35 yr | Not applicable | 35 yr | 35 yr | 35yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr | 35 yr |
Temporally Distributed?
variable.detail.tempDistributedHelp
?
|
Yes | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Regular Temporal Grain?
variable.detail.regularTempGrainHelp
?
|
No | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Not applicable | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Temporal Grain Size Value
variable.detail.tempGrainSizeValHelp
?
|
Not applicable | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | Not applicable | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
Temporal Grain Size Units
variable.detail.tempGrainSizeUnitHelp
?
|
Not applicable | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | year | year | year | year | year | year | year | year | year | year | year | year | year | year | year | year | year | year | year | year | year | Day | year | year | Not applicable | year | year | year | year | year | year | year | year | Day | year | year | year | year | year | year |
Temporal Density
variable.detail.tempDensityHelp
?
|
user defined | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Crop type ?Comment:To add a crop to the rotation, click Add Crop to Rotation. The user is then asked to select a crop from the pick list, a tillage type (No-till, reduced till, or intensive till), and rotation year. The crop list is customized according to the region in which the project is located. The rotation year indicates the sequence of the crop within the crop schedule, it does not represent the calendar year. Once the user has selected a crop type, tillage type and rotation year, clicking Upload will add the crop to the crop schedule. Once a crop is added to the crop schedule you will note that it includes several default management characteristics including a planting date, fertilizer applications, tillage schedule, and harvest. These operations can be modified or deleted as needed and new operations can be added. |
Autofertigation total nitrogen concentration ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Autofertigation is the application of fertilizers, soil amendments, or other water-soluble products through an autoirrigation system. Autofertigation is an automatic fertilization process in which fertilizer is dissolved and distributed through the irrigation system. This makes autofertigation very similar to autoirrigation with the only additional user input required being nitrogen concentration. The amount of nitrogen in irrigation water in parts per million. Total N applied through autofertigation will be dependent upon the overall irrigation frequency which in turn is dependent upon water stress, frequency and maximum application factors set by the user. |
Autoirrigate a maximum frequency of every (0-365) days ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This field is asking for the maximum frequency (in days) that irrigation can take place. If the frequency is set to 1, then irrigation can occur every day. If frequency is set to 7 then irrigation can occur, at most, once a week. The value can be any whole number greater than or equal to zero and less than or equal to 365. |
Autoirrigation efficiency ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This value is the fraction of irrigation application that is not lost to runoff. This must be a value that is greater than 0 and less than or equal to 1. The closer the value is to 0, the greater the percentage of water lost to runoff and does not reach the crop. A value of 1 means that no water was lost to runoff. Different irrigation systems have different irrigation efficiencies. NTT supplies typical irrigation efficiency values for the irrigation type selected, but these values can be modified by the user. |
Autoirrigation type ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. Irrigation types include sprinkler, furrow/flood, drip, and furrow diking. |
Burn date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Continuous grazing animal type ?Comment:User indicates the type of animals being grazed on the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing animal units ?Comment:User indicates the total animal units being grazed on the field. Animal units represent 1,000 lbs of live animal weight. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing end date ?Comment:User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing hours in field ?Comment:User indicates the total hours per day that animals are grazed in the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing start date ?Comment:User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Countour buffer (strip farming crop grass/vegetation ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. Contour buffer strips are permanent, narrow bands of grasses/legumes planted on the contour (across or perpendicular to a slope) between wider strips of crops. Contour buffers trap sediment and enhance filtration of nutrients and pesticides by slowing down runoff that could enter the local surface waters. This is the type of grass or vegetation that will be present in the buffer sections of the contour buffer. |
Cover crop planting date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Cover crop planting method ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Cover crop type ?Comment:Cover crops are not fertilized and are not harvested, rather they are chopped prior to planting of the next crop in the rotation. This optional variable is constant with respect to Crop type for this specific application. |
Cover crop year ?Comment:The cover crop year should indicate the year within the rotation that the cover crop is planted. This optional variable is constant with respect to Crop type for this specific application. |
Crop width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width, in feet, of the strips of the main crop that was planted. It can be any number greater than 0. Crop width, along with buffer width, determine the number of buffer and crop strips in the field. |
End of season date ?Comment:End of season indicates to the model that the crop is removed from the field. If an End of Season operation is not present, then the model assumes that the crop is left growing. End of season should be used for all annual crops. For certain perennial crops like hay and pasture, End of Season operations may be absent from the crop schedule. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer amount ?Comment:User needs to indicate the amount of fertilizer applied. Units will vary depending on the type of fertilizer selected (lbs/ac, tons/ac, 1000 gals/ac). This variable is constant with respect to Crop type for the specific model application. |
Fertilizer category ?Comment:User must indicate the fertilizer category (commercial, liquid manure, or solid manure). This variable is constant with respect to Crop type for the specific model application. |
Fertilizer compostion ?Comment:For commercial fertilizer, these fields indicate the N and P composition. These fields are pre-filled based on the fertilizer type selected, but can be modified if needed. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer depth ?Comment:If the fertilizer is incorporated, user should indicate the depth of incorporation here. If fertilizer is not incorporated, this field can be left blank. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer type ?Comment:The fertilizer type pick list will vary depending on the fertilizer category selected. For manure fertilizer, pick list will contain types of animal manure. This variable is constant with respect to Crop type for the specific model application. |
Field (area of interest) ?Comment:After creating a new project, users will be asked to define the location of the project using the interactive Google map. The interactive map allows the user to define one or more areas of interest (AOI). The area of interest should correlate to fields within the project area. The map is ONLY used for mainland United States. If you would like to simulate using an area outside of mainland United States, follow the instructions for User Input. When defining the AOI, the underlying weather, soils, and slope information is retrieved from the underlying spatial data. There are two ways to define your areas of interest: you may manually draw your areas of interest using the zoom features and drawing tools on the interactive map, or you may upload your own shapefile. After drawing the field, a message will pop up telling the user to enter the name of the AOI. |
Field area ?Comment:Field area displays the calculated area of the field in acres. The user may refine this value if needed. |
Forest strip width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the width of the forest buffer (not including the grass strip). |
Fraction of area controlled by ponds/WASCB ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. Water and sediment control basins (WASCOBs), or ponds, consist of an embankment across the slope of a field or minor waterway to temporarily detain and release water through a piped outlet or through infiltration. They are constructed perpendicular to the flow direction and parallel to each other. WASCOBs are usually installed in areas where the land is relatively steep and undulating. They detain water from contributing areas, inducing sedimentation and controlling the release of water, thereby reducing the erosive power of the water downstream. Additional benefits are settling of sediment-bound pollutants and some infiltration. Only one input is required for ponds: fraction of area controlled by ponds. This is the fraction (a value between 0 and 1) of the field runoff that flows through (is controlled by) the pond/WASCOB. As modeled, ponds only treat runoff that originates in this field. Inflow from other fields is not routed through the ponds. Ponds/WASCOBs are assumed to be within field. |
Fraction of field treated by buffer ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the estimated fraction (0.00-1.00) of the runoff from the field that is routed through the buffer. |
Fraction of field treated by grass waterway ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. The fraction of the field that drains to the grass waterway. A number between 0.00 and 1.00. |
Grass buffer vegetation type ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the type of grass or vegetation that is planted in the Filter Strip. |
Grass buffer/forest buffer area ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. Forest buffers are linear wooded areas with well-developed root systems, an organic surface layer, and understory vegetation. When they are adjacent to open water they are referred to as riparian forest buffers. Non-riparian buffers are linear wooded areas along down-slope field edges. Forest buffers trap sediment and increase infiltration, thereby reducing sediment and nutrient losses. Forest buffers often include a grass buffer between the field and the forested buffer. If present, please also include the width of the grass buffer. Grass buffers, also known as a filter strips, are an area of vegetation, generally narrow in width and long across the downslope edge of a field, that slows the rate of runoff, allowing sediments, organic matter, and other pollutants that are being conveyed by the water to be removed by settling out. Filter strips reduce erosion and the accompanying sediment-bound pollution. In NTT, filter strips function by providing for better infiltration of soluble nutrients, trapping of sediment, and increased uptake of water and nutrients by the filter strip vegetation. The saturated conductivity value is also modified for filter strip simulation in NTT. The inputs for grass buffers are the same as for forest buffers (see Forest Buffer), with the additional requirement that the user specify type of vegetation. This is the total area of the Riparian Buffer. This field is optional. If left blank, the area will automatically be calculated using the width of the buffer and the length of the field edge (where the field edge is calculated as the square root of the area of the field). |
Grass strip width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the width of the grass strip between the crop and the forested buffer, if present. |
Grass waterway crop ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. A grassed waterway is a natural or constructed swale, shaped or graded and established in suitable vegetation for the safe conveyance of runoff. Grassed waterways are designed to prevent soil erosion while draining runoff water from adjacent cropland. As water travels down the waterway, the grass vegetation prevents erosion that would otherwise result from concentrated flows and uptakes nutrients. Grassed waterways also help prevent gully erosion in areas of concentrated flow. For example, they may be used to drain runoff from terraces and runoff water diversions. By intercepting runoff, grassed waterways slow erosion and minimize nutrient losses. |
Grass waterway width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width of the grassed waterway, in feet, including both sides of the vegetated channel. This can be any number greater than 0. |
Grass/vegetation width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width, in feet, of the buffer strips. It can be any number greater than 0. Buffer width, along with crop width, determine the number of buffer and crop strips in the field. |
Harvest date ?Comment:A default date is automatically entered for harvest. This can be modified as needed. This variable is constant with respect to Crop type for the specific model application. |
Irrigation amount ?Comment:User indicates the volume of water applied in this irrigation event in inches. This optional variable is constant with respect to Crop type for the specific application. |
Irrigation efficiency ?Comment:This field defaults to a typical irrigation efficiency value (as a fraction) based on the irrigation method that is selected. This value can be modified. This optional variable is constant with respect to Crop type for the specific application. |
Irrigation method ?Comment:An optional variable that is constant with respect to Crop type for the specific application. |
Is buffer included in AOI? (y/n) ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. If buffer has been drawn as part of the AOI, then the area will be subtracted from the crop area. If it has not been drawn as part of the AOI, it will be assumed to be adjacent to one edge of the field. |
Is wetland area included in your AOI? (y/n) ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Users indicate here whether the AOI representing the field includes the wetland feature within the drawn polygon or if the wetland feature lies outside of the AOI. If the wetland feature is included in the AOI, then the wetland acres will be subtracted from the field area. |
Land leveling slope reduction ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. Land leveling is used to reduce the slope on high soil slopes. By reducing the slope, the surface land is better able to retain water and soil, reducing erosion and increasing infiltration. The input for land leveling is slope reduction percentage. This is the percent reduction in the slope of the soil. The number can be any percentage between 0% and 100%. The closer the slope is to 100, the more the slope is reduced. |
Lime amount ?Comment:User must indicate amount of lime applied (lbs/ac). This optional variable is constant with respect to Crop type for this specific application. |
Lime date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Maximum single application ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This value signifies the maximum amount of water than can be applied in a single irrigation event. It is in inches, and it can be any number greater than 0. If there are no constraints on the maximum single application, this value should be set to a high number. |
Moisture content ?Comment:For manure fertilizer, this is the percentage, by weight, of moisture content in the manure. Typical values for each manure type are provided, but can be modified by the user. This variable is constant with respect to Crop type for the specific model application. |
Number of consecutive days grazed at a time (in each paddock) ?Comment:User indicates the number of days livestock will spend in each paddock before being rotated to a new paddock. This optional variable is constant with respect to Crop type for this specific application. |
Pasture rest time between grazing ?Comment:User indicates the number of days that the pasture is rested between rotational grazing cycles. This optional variable is constant with respect to Crop type for this specific application. |
Plant water stress factor ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. The water stress factor indicates the water stress level of the crop. This is the value that is used to trigger the start of auto irrigation. For example, if water stress is set to 0.8 then NTT will trigger an irrigation event when the crop is 80% water-stressed, as long as conditions for maximum frequency are also met. The plant water stress factor can be any value greater than 0 and less than or equal to 1. The closer the value is to 100, the less water stress is allowed before the automatic irrigation is turned on. |
Planting date ?Comment:This variable is constant with respect to Crop type for the specific model application. |
Rotation year ?Comment:The rotation year indicates the sequence of the crop within the crop schedule, it does not represent the calendar year. This variable is constant with respect to Crop type for the specific model application. |
Rotational grazing animal type ?Comment:User indicates the type of animals being grazed on the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing animal units ?Comment:User indicates the total animal units being grazed on the field. Animal units represent 1,000 lbs of live weight. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing end date ?Comment:The rotational grazing operation, unlike continuous grazing, assumes that the pasture is divided into paddocks and that livestock are moved through the paddocks as needed. Thus, each paddock is given a recovery period between grazing events, improving vegetative cover. User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing hours in field ?Comment:User indicates the total hours per day that animals are grazed in the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing start date ?Comment:The rotational grazing operation, unlike continuous grazing, assumes that the pasture is divided into paddocks and that livestock are moved through the paddocks as needed. Thus, each paddock is given a recovery period between grazing events, improving vegetative cover. User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Seed amount ?Comment:This field is pre-filled with standard seeding rates for each crop type. If the user has more specific information on seeding rate they may enter it. This variable is constant with respect to Crop type for the specific model application. |
Soil organic matter ?Comment:The default soil organic matter (%) value returned by the SSURGO soils database is displayed for each soil in the soils list. However, if the user has more precise data they may enter it here. |
Soil P ?Comment:Users should enter the soil phosphorus test value for their field, if available. If None was selected for the P test then this field will be disabled and a minimum phosphorus concentration in the soil will be used. Similarly, if a soil test is selected, but the field Soil P value is left blank, the tool will assume a minimum phosphorus concentration in the soil. |
Soil P test ?Comment:The user should select a soil test, if applicable, that was used to determine the soil phosphorus. Currently NTT includes conversions for the Fe-strip test, Olsen, Bray-1, and Mehlich-3 tests. If you have used a different test, please select Other. If you do not have a soil P test for your soil, leave these fields blank and NTT will use default soil P values. |
Terrace system (y/n) ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. A terrace system is a leveled section of a hill cultivated area, designed as a method of soil conservation to slow or prevent the rapid surface runoff of water. Terraces decrease hill slope-length, reduce formation of gullies, and intercept and conduct runoff to a safe outlet thereby reducing sediment content in runoff water. Often, in application the landscape is formed into multiple terraces, giving a stepped appearance. Terraces are simulated by reducing the practice factor (PEC). |
Tile drain depth ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. For NTT applications, underground drainage systems are simulated in APEX. The depth of the drainage system to reduce plant stress is a key parameter used in simulating tile drainage systems in NTT. Tile drainage simulation in NTT increases subsurface flow, which may provide an avenue for increased nutrient losses in subsurface flow. The only input for tile drains is depth. This is the depth in feet at which the drainage system is installed. It is any number greater than 0. |
Tillage ?Comment:User must indicate the tillage method using the drop down selection. This variable is constant with respect to Crop type for the specific model application. |
Total N concentration ?Comment:For manure fertilizer, the user should indicate the total N content per ton of solid manure or per 1000 gallons of liquid manure. Typical values are pre-filled for the user, but can be modified. This variable is constant with respect to Crop type for the specific model application. |
Total P concentration ?Comment:For manure fertilizer, the user should indicate the total P content per ton of solid manure or per 1000 gallons of liquid manure. Typical values are pre-filled for the user, but can be modified. This variable is constant with respect to Crop type for the specific model application. |
Wetland area ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Wetlands are those areas that are inundated or saturated by surface or groundwater at a frequency and duration sufficient to support, and that under normal circumstances do support, a prevalence of vegetation typically adapted for life in saturated soil conditions. Wetlands generally include swamps, marshes, bogs and similar areas. The wetland area is simulated as a shallow reservoir (1 ft. depth) with growing wetland vegetation – it is essentially simulated as an artificial wetland and not a natural wetland. The slope of wetland area is set as 1%. Simulated wetlands trap sediment, reduce runoff, increase infiltration, and also increase uptake of water and nutrients by the vegetation in the area covered by the wetland. The area of the wetland is input in acres. Since this area is no longer able to be used for crop production, there may be a lower total crop yield (although there may be a greater crop yield/acre). |
Change in crop yield ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in deep percolation loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in irrigation applied loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in manure erosion ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in organic N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in organic P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in other water info loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in PO4 loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in runoff N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in subsurface flor loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in subsurface N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface erosion loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface flow loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface/subsurface/tile drain flow loss |
Change in tile drain flow loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in tile drain N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in tile drain P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total sediment loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Crop yield ?Comment:The scenario results presented in your table represent an AVERAGE annual yield across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Deep percolation loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Irrigation applied loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Manure erosion loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Organic N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Organic P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Other water info loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
PO4 loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Runoff N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Subsurface flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Subsurface N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface erosion loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface/subsurface/tile drain flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total sediment loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
|
Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | |
Min Value
variable.detail.minEstHelp
?
|
Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Max Value
variable.detail.estHelp
?
|
Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Other Value Type
variable.detail.natureOtherEstHelp
?
|
Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Other Value
variable.detail.otherEstHelp
?
|
Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Crop type ?Comment:To add a crop to the rotation, click Add Crop to Rotation. The user is then asked to select a crop from the pick list, a tillage type (No-till, reduced till, or intensive till), and rotation year. The crop list is customized according to the region in which the project is located. The rotation year indicates the sequence of the crop within the crop schedule, it does not represent the calendar year. Once the user has selected a crop type, tillage type and rotation year, clicking Upload will add the crop to the crop schedule. Once a crop is added to the crop schedule you will note that it includes several default management characteristics including a planting date, fertilizer applications, tillage schedule, and harvest. These operations can be modified or deleted as needed and new operations can be added. |
Autofertigation total nitrogen concentration ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Autofertigation is the application of fertilizers, soil amendments, or other water-soluble products through an autoirrigation system. Autofertigation is an automatic fertilization process in which fertilizer is dissolved and distributed through the irrigation system. This makes autofertigation very similar to autoirrigation with the only additional user input required being nitrogen concentration. The amount of nitrogen in irrigation water in parts per million. Total N applied through autofertigation will be dependent upon the overall irrigation frequency which in turn is dependent upon water stress, frequency and maximum application factors set by the user. |
Autoirrigate a maximum frequency of every (0-365) days ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This field is asking for the maximum frequency (in days) that irrigation can take place. If the frequency is set to 1, then irrigation can occur every day. If frequency is set to 7 then irrigation can occur, at most, once a week. The value can be any whole number greater than or equal to zero and less than or equal to 365. |
Autoirrigation efficiency ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This value is the fraction of irrigation application that is not lost to runoff. This must be a value that is greater than 0 and less than or equal to 1. The closer the value is to 0, the greater the percentage of water lost to runoff and does not reach the crop. A value of 1 means that no water was lost to runoff. Different irrigation systems have different irrigation efficiencies. NTT supplies typical irrigation efficiency values for the irrigation type selected, but these values can be modified by the user. |
Autoirrigation type ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. Irrigation types include sprinkler, furrow/flood, drip, and furrow diking. |
Burn date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Continuous grazing animal type ?Comment:User indicates the type of animals being grazed on the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing animal units ?Comment:User indicates the total animal units being grazed on the field. Animal units represent 1,000 lbs of live animal weight. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing end date ?Comment:User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing hours in field ?Comment:User indicates the total hours per day that animals are grazed in the field. This optional variable is constant with respect to Crop type for the specific application. |
Continuous grazing start date ?Comment:User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Countour buffer (strip farming crop grass/vegetation ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. Contour buffer strips are permanent, narrow bands of grasses/legumes planted on the contour (across or perpendicular to a slope) between wider strips of crops. Contour buffers trap sediment and enhance filtration of nutrients and pesticides by slowing down runoff that could enter the local surface waters. This is the type of grass or vegetation that will be present in the buffer sections of the contour buffer. |
Cover crop planting date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Cover crop planting method ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Cover crop type ?Comment:Cover crops are not fertilized and are not harvested, rather they are chopped prior to planting of the next crop in the rotation. This optional variable is constant with respect to Crop type for this specific application. |
Cover crop year ?Comment:The cover crop year should indicate the year within the rotation that the cover crop is planted. This optional variable is constant with respect to Crop type for this specific application. |
Crop width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width, in feet, of the strips of the main crop that was planted. It can be any number greater than 0. Crop width, along with buffer width, determine the number of buffer and crop strips in the field. |
End of season date ?Comment:End of season indicates to the model that the crop is removed from the field. If an End of Season operation is not present, then the model assumes that the crop is left growing. End of season should be used for all annual crops. For certain perennial crops like hay and pasture, End of Season operations may be absent from the crop schedule. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer amount ?Comment:User needs to indicate the amount of fertilizer applied. Units will vary depending on the type of fertilizer selected (lbs/ac, tons/ac, 1000 gals/ac). This variable is constant with respect to Crop type for the specific model application. |
Fertilizer category ?Comment:User must indicate the fertilizer category (commercial, liquid manure, or solid manure). This variable is constant with respect to Crop type for the specific model application. |
Fertilizer compostion ?Comment:For commercial fertilizer, these fields indicate the N and P composition. These fields are pre-filled based on the fertilizer type selected, but can be modified if needed. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer depth ?Comment:If the fertilizer is incorporated, user should indicate the depth of incorporation here. If fertilizer is not incorporated, this field can be left blank. This variable is constant with respect to Crop type for the specific model application. |
Fertilizer type ?Comment:The fertilizer type pick list will vary depending on the fertilizer category selected. For manure fertilizer, pick list will contain types of animal manure. This variable is constant with respect to Crop type for the specific model application. |
Field (area of interest) ?Comment:After creating a new project, users will be asked to define the location of the project using the interactive Google map. The interactive map allows the user to define one or more areas of interest (AOI). The area of interest should correlate to fields within the project area. The map is ONLY used for mainland United States. If you would like to simulate using an area outside of mainland United States, follow the instructions for User Input. When defining the AOI, the underlying weather, soils, and slope information is retrieved from the underlying spatial data. There are two ways to define your areas of interest: you may manually draw your areas of interest using the zoom features and drawing tools on the interactive map, or you may upload your own shapefile. After drawing the field, a message will pop up telling the user to enter the name of the AOI. |
Field area ?Comment:Field area displays the calculated area of the field in acres. The user may refine this value if needed. |
Forest strip width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the width of the forest buffer (not including the grass strip). |
Fraction of area controlled by ponds/WASCB ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. Water and sediment control basins (WASCOBs), or ponds, consist of an embankment across the slope of a field or minor waterway to temporarily detain and release water through a piped outlet or through infiltration. They are constructed perpendicular to the flow direction and parallel to each other. WASCOBs are usually installed in areas where the land is relatively steep and undulating. They detain water from contributing areas, inducing sedimentation and controlling the release of water, thereby reducing the erosive power of the water downstream. Additional benefits are settling of sediment-bound pollutants and some infiltration. Only one input is required for ponds: fraction of area controlled by ponds. This is the fraction (a value between 0 and 1) of the field runoff that flows through (is controlled by) the pond/WASCOB. As modeled, ponds only treat runoff that originates in this field. Inflow from other fields is not routed through the ponds. Ponds/WASCOBs are assumed to be within field. |
Fraction of field treated by buffer ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the estimated fraction (0.00-1.00) of the runoff from the field that is routed through the buffer. |
Fraction of field treated by grass waterway ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. The fraction of the field that drains to the grass waterway. A number between 0.00 and 1.00. |
Grass buffer vegetation type ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the type of grass or vegetation that is planted in the Filter Strip. |
Grass buffer/forest buffer area ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. Forest buffers are linear wooded areas with well-developed root systems, an organic surface layer, and understory vegetation. When they are adjacent to open water they are referred to as riparian forest buffers. Non-riparian buffers are linear wooded areas along down-slope field edges. Forest buffers trap sediment and increase infiltration, thereby reducing sediment and nutrient losses. Forest buffers often include a grass buffer between the field and the forested buffer. If present, please also include the width of the grass buffer. Grass buffers, also known as a filter strips, are an area of vegetation, generally narrow in width and long across the downslope edge of a field, that slows the rate of runoff, allowing sediments, organic matter, and other pollutants that are being conveyed by the water to be removed by settling out. Filter strips reduce erosion and the accompanying sediment-bound pollution. In NTT, filter strips function by providing for better infiltration of soluble nutrients, trapping of sediment, and increased uptake of water and nutrients by the filter strip vegetation. The saturated conductivity value is also modified for filter strip simulation in NTT. The inputs for grass buffers are the same as for forest buffers (see Forest Buffer), with the additional requirement that the user specify type of vegetation. This is the total area of the Riparian Buffer. This field is optional. If left blank, the area will automatically be calculated using the width of the buffer and the length of the field edge (where the field edge is calculated as the square root of the area of the field). |
Grass strip width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. This is the width of the grass strip between the crop and the forested buffer, if present. |
Grass waterway crop ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. A grassed waterway is a natural or constructed swale, shaped or graded and established in suitable vegetation for the safe conveyance of runoff. Grassed waterways are designed to prevent soil erosion while draining runoff water from adjacent cropland. As water travels down the waterway, the grass vegetation prevents erosion that would otherwise result from concentrated flows and uptakes nutrients. Grassed waterways also help prevent gully erosion in areas of concentrated flow. For example, they may be used to drain runoff from terraces and runoff water diversions. By intercepting runoff, grassed waterways slow erosion and minimize nutrient losses. |
Grass waterway width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width of the grassed waterway, in feet, including both sides of the vegetated channel. This can be any number greater than 0. |
Grass/vegetation width ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. This is the width, in feet, of the buffer strips. It can be any number greater than 0. Buffer width, along with crop width, determine the number of buffer and crop strips in the field. |
Harvest date ?Comment:A default date is automatically entered for harvest. This can be modified as needed. This variable is constant with respect to Crop type for the specific model application. |
Irrigation amount ?Comment:User indicates the volume of water applied in this irrigation event in inches. This optional variable is constant with respect to Crop type for the specific application. |
Irrigation efficiency ?Comment:This field defaults to a typical irrigation efficiency value (as a fraction) based on the irrigation method that is selected. This value can be modified. This optional variable is constant with respect to Crop type for the specific application. |
Irrigation method ?Comment:An optional variable that is constant with respect to Crop type for the specific application. |
Is buffer included in AOI? (y/n) ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to the Crop type for the specific application. If buffer has been drawn as part of the AOI, then the area will be subtracted from the crop area. If it has not been drawn as part of the AOI, it will be assumed to be adjacent to one edge of the field. |
Is wetland area included in your AOI? (y/n) ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Users indicate here whether the AOI representing the field includes the wetland feature within the drawn polygon or if the wetland feature lies outside of the AOI. If the wetland feature is included in the AOI, then the wetland acres will be subtracted from the field area. |
Land leveling slope reduction ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. Land leveling is used to reduce the slope on high soil slopes. By reducing the slope, the surface land is better able to retain water and soil, reducing erosion and increasing infiltration. The input for land leveling is slope reduction percentage. This is the percent reduction in the slope of the soil. The number can be any percentage between 0% and 100%. The closer the slope is to 100, the more the slope is reduced. |
Lime amount ?Comment:User must indicate amount of lime applied (lbs/ac). This optional variable is constant with respect to Crop type for this specific application. |
Lime date ?Comment:This optional variable is constant with respect to Crop type for this specific application. |
Maximum single application ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. This value signifies the maximum amount of water than can be applied in a single irrigation event. It is in inches, and it can be any number greater than 0. If there are no constraints on the maximum single application, this value should be set to a high number. |
Moisture content ?Comment:For manure fertilizer, this is the percentage, by weight, of moisture content in the manure. Typical values for each manure type are provided, but can be modified by the user. This variable is constant with respect to Crop type for the specific model application. |
Number of consecutive days grazed at a time (in each paddock) ?Comment:User indicates the number of days livestock will spend in each paddock before being rotated to a new paddock. This optional variable is constant with respect to Crop type for this specific application. |
Pasture rest time between grazing ?Comment:User indicates the number of days that the pasture is rested between rotational grazing cycles. This optional variable is constant with respect to Crop type for this specific application. |
Plant water stress factor ?Comment:This variable pertains to one of the optional conservation practices available to apply in NTT. This variable is constant with respect to Crop type for the specific scenario. Autoirrigation refers to Automatic irrigation systems are irrigation systems that are controlled by a computerized controller. Autoirrigation overall can greatly increase crop yield. Within NTT, the autoirrigation feature will irrigate the field when certain user-supplied criteria for water stress and frequency are met, and will limit water application to the user supplied maximum application amount. The water stress factor indicates the water stress level of the crop. This is the value that is used to trigger the start of auto irrigation. For example, if water stress is set to 0.8 then NTT will trigger an irrigation event when the crop is 80% water-stressed, as long as conditions for maximum frequency are also met. The plant water stress factor can be any value greater than 0 and less than or equal to 1. The closer the value is to 100, the less water stress is allowed before the automatic irrigation is turned on. |
Planting date ?Comment:This variable is constant with respect to Crop type for the specific model application. |
Rotation year ?Comment:The rotation year indicates the sequence of the crop within the crop schedule, it does not represent the calendar year. This variable is constant with respect to Crop type for the specific model application. |
Rotational grazing animal type ?Comment:User indicates the type of animals being grazed on the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing animal units ?Comment:User indicates the total animal units being grazed on the field. Animal units represent 1,000 lbs of live weight. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing end date ?Comment:The rotational grazing operation, unlike continuous grazing, assumes that the pasture is divided into paddocks and that livestock are moved through the paddocks as needed. Thus, each paddock is given a recovery period between grazing events, improving vegetative cover. User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing hours in field ?Comment:User indicates the total hours per day that animals are grazed in the field. This optional variable is constant with respect to Crop type for the specific application. |
Rotational grazing start date ?Comment:The rotational grazing operation, unlike continuous grazing, assumes that the pasture is divided into paddocks and that livestock are moved through the paddocks as needed. Thus, each paddock is given a recovery period between grazing events, improving vegetative cover. User indicates the start and end dates of grazing on the field. This optional variable is constant with respect to Crop type for the specific application. |
Seed amount ?Comment:This field is pre-filled with standard seeding rates for each crop type. If the user has more specific information on seeding rate they may enter it. This variable is constant with respect to Crop type for the specific model application. |
Soil organic matter ?Comment:The default soil organic matter (%) value returned by the SSURGO soils database is displayed for each soil in the soils list. However, if the user has more precise data they may enter it here. |
Soil P ?Comment:Users should enter the soil phosphorus test value for their field, if available. If None was selected for the P test then this field will be disabled and a minimum phosphorus concentration in the soil will be used. Similarly, if a soil test is selected, but the field Soil P value is left blank, the tool will assume a minimum phosphorus concentration in the soil. |
Soil P test ?Comment:The user should select a soil test, if applicable, that was used to determine the soil phosphorus. Currently NTT includes conversions for the Fe-strip test, Olsen, Bray-1, and Mehlich-3 tests. If you have used a different test, please select Other. If you do not have a soil P test for your soil, leave these fields blank and NTT will use default soil P values. |
Terrace system (y/n) ?Comment:This variable pertains to optional Conservation Practices provided by NTT. This variable is constant with respect to Crop type in the specific application. A terrace system is a leveled section of a hill cultivated area, designed as a method of soil conservation to slow or prevent the rapid surface runoff of water. Terraces decrease hill slope-length, reduce formation of gullies, and intercept and conduct runoff to a safe outlet thereby reducing sediment content in runoff water. Often, in application the landscape is formed into multiple terraces, giving a stepped appearance. Terraces are simulated by reducing the practice factor (PEC). |
Tile drain depth ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. For NTT applications, underground drainage systems are simulated in APEX. The depth of the drainage system to reduce plant stress is a key parameter used in simulating tile drainage systems in NTT. Tile drainage simulation in NTT increases subsurface flow, which may provide an avenue for increased nutrient losses in subsurface flow. The only input for tile drains is depth. This is the depth in feet at which the drainage system is installed. It is any number greater than 0. |
Tillage ?Comment:User must indicate the tillage method using the drop down selection. This variable is constant with respect to Crop type for the specific model application. |
Total N concentration ?Comment:For manure fertilizer, the user should indicate the total N content per ton of solid manure or per 1000 gallons of liquid manure. Typical values are pre-filled for the user, but can be modified. This variable is constant with respect to Crop type for the specific model application. |
Total P concentration ?Comment:For manure fertilizer, the user should indicate the total P content per ton of solid manure or per 1000 gallons of liquid manure. Typical values are pre-filled for the user, but can be modified. This variable is constant with respect to Crop type for the specific model application. |
Wetland area ?Comment:This variable pertains to one of the optional conservation practices available in NTT. This variable is constant with respect to the Crop type for the specific application. Wetlands are those areas that are inundated or saturated by surface or groundwater at a frequency and duration sufficient to support, and that under normal circumstances do support, a prevalence of vegetation typically adapted for life in saturated soil conditions. Wetlands generally include swamps, marshes, bogs and similar areas. The wetland area is simulated as a shallow reservoir (1 ft. depth) with growing wetland vegetation – it is essentially simulated as an artificial wetland and not a natural wetland. The slope of wetland area is set as 1%. Simulated wetlands trap sediment, reduce runoff, increase infiltration, and also increase uptake of water and nutrients by the vegetation in the area covered by the wetland. The area of the wetland is input in acres. Since this area is no longer able to be used for crop production, there may be a lower total crop yield (although there may be a greater crop yield/acre). |
Change in crop yield ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in deep percolation loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in irrigation applied loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in manure erosion ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in organic N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in organic P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in other water info loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in PO4 loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in runoff N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in subsurface flor loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in subsurface N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface erosion loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface flow loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in surface/subsurface/tile drain flow loss |
Change in tile drain flow loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in tile drain N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in tile drain P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total N loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total P loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Change in total sediment loss ?Comment:This variable computes the difference between two scenarios for this modeled result (response). |
Crop yield ?Comment:The scenario results presented in your table represent an AVERAGE annual yield across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Deep percolation loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Irrigation applied loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Manure erosion loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Organic N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Organic P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Other water info loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
PO4 loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Runoff N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Subsurface flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Subsurface N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface erosion loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Surface/subsurface/tile drain flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain flow loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Tile drain P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total N loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total P loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
Total sediment loss ?Comment:The scenario results presented in your table represent AVERAGE annual edge of field losses across the period of simulation. NTT simulates over a period of 35 years. To view year by year results, the user can view use the Graphical results feature (See View Graphical Results.). This result is produced separately for the initial scenario and all subsequent scenarios. |
|
Variability Expression Given?
variable.detail.variabilityExpHelp
?
|
Not applicable | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Variability Metric
variable.detail.variabilityMetricHelp
?
|
None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None |
Variability Value
variable.detail.variabilityValueHelp
?
|
None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None |
Variability Units
|
None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None |
Resampling Used?
variable.detail.bootstrappingHelp
?
|
Not applicable | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Variability Expression Used in Modeling?
variable.detail.variabilityUsedHelp
?
|
Not applicable | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not recorded for Constant or Parameter Variables | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Change in crop yield | Change in deep percolation loss | Change in irrigation applied loss | Change in manure erosion | Change in organic N loss | Change in organic P loss | Change in other water info loss | Change in PO4 loss | Change in runoff N loss | Change in subsurface flor loss | Change in subsurface N loss | Change in surface erosion loss | Change in surface flow loss | Change in surface/subsurface/tile drain flow loss | Change in tile drain flow loss | Change in tile drain N loss | Change in tile drain P loss | Change in total N loss | Change in total P loss | Change in total sediment loss | Crop yield | Deep percolation loss | Irrigation applied loss | Manure erosion loss | Organic N loss | Organic P loss | Other water info loss | PO4 loss | Runoff N loss | Subsurface flow loss | Subsurface N loss | Surface erosion loss | Surface flow loss | Surface/subsurface/tile drain flow loss | Tile drain flow loss | Tile drain N loss | Tile drain P loss | Total N loss | Total P loss | Total sediment loss | |
Variable ID
variable.detail.varIdHelp
?
|
13506 | 13513 | 13512 | 13516 | 13498 | 13508 | 13511 | 13509 | 13499 | 13504 | 13500 | 13515 | 13503 | 13502 | 13505 | 13501 | 13510 | 13497 | 13507 | 13514 | 13459 | 13466 | 13465 | 13469 | 13451 | 13461 | 13464 | 13462 | 13452 | 13457 | 13453 | 13468 | 13456 | 13455 | 13458 | 13454 | 13463 | 13450 | 13460 | 13467 |
Validated?
variable.detail.resValidatedHelp
?
|
Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Validation Approach (within, between, etc.)
variable.detail.validationApproachHelp
?
|
None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None |
Validation Quality (Qual/Quant)
variable.detail.validationQualityHelp
?
|
None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None |
Validation Method (Stat/Deviance)
variable.detail.validationMethodHelp
?
|
None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None |
Validation Metric
variable.detail.validationMetricHelp
?
|
None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None |
Validation Value
variable.detail.validationValHelp
?
|
None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None |
Validation Units
|
None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None |
Use of Measured Response Data
variable.detail.measuredResponseDataHelp
?
|
None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None | None |