Laserfiche WebLink
Harvesting day (1-31) <br />? <br />Days to full cover (1-366) <br />? <br />Length of growing season (1-366) <br />? <br />Temp of early moisture (deg F) <br />? <br />Temp of late moisture (deg F) <br />? <br />Management allowable deficit (MAD) (1-100) <br />? <br />Initial root-zone depth (ft) <br />? <br />Max. root-zone depth (ft) <br />? <br />Water holding capacity (AWC) (ft/ft) <br />? <br />Data Describing Each Spatial Identifier <br />Name of spatial identifier (string) <br />? <br />Elevation (ft) <br />? <br />Latitude and longitude (dec. degs.) <br />? <br />Crop/soil acreage per year (acre) <br />? <br />Low-level DMI Inputs <br />The high-level DMI parameter values are passed directly to the low-level DMI. <br />Area and Time Parameters <br />A number of spatial identifiers describing the specified area <br />? <br />A string defining the unit of the spatial identifier list (county, water district, hydrologic unit, <br />? <br />and river basin) <br /> <br />A list of spatial identifiers describing the specified area (county name, water district number, <br />? <br />hydrologic unit number, or river basin name) <br />The begin year for the model run <br />? <br />The end year for the model run (>= begin year) <br />? <br />An integer to represent nulls in data (e.g. -9999) <br />? <br />If a low-level routine is developed to specifically support this DMI, then no other parameters are <br />necessary since the data format and types of data are predetermined and rigid. If a general use routine is <br />developed that supports more than one calling DMI, then additional parameters may be necessary. <br />3 <br />A275 01.09.95 1.14-10 CSU IDS <br />