Crop Management Database (CropMD)

CropMD is a stand-alone runtime database developed with FileMaker Pro ®. CropMD software permits the user to enter data, update crop input rates and costs, generate and print summary reports, and archive and transfer data between years. Historic data may be stored in the computer as tab files or kept in database format for easy access.

Information is entered into CropMD on a per-farm basis. Each field is represented in the database as a record. The user chooses the Data Entry Menu and selects the appropriate layout to enter initial data based on a crop management plan. Records are changed as needed to reflect modifications to plans and new data collected during the growing season. The standard screen layout and button placement enable the user to easily access, modify, or process information in the system (Figure 1.2). Pop-up menus allow users to employ standard terminology for data entry (Figure 1.3).

figure 1.2

Figure 1.2. A button bar at the top of data entry screens allows users to move easily from one screen to another and to sort and find records.

figure 1.3

Figure 1.3. Pop-up menus facilitate and standardize data entry.

The database system uses lookup tables with rates and costs of crop inputs, custom costs of cropping activities, conservation practice names and descriptions, and soil characteristics. For example, the Lookup Herbicide table is used to enter herbicide rates and costs; active ingredients and Environmental Protection Agency (EPA) numbers are obtained from a lookup table built into the base system. Each database contains lookup tables with values customized to correspond to each specific farm (Figure 1.4).

figure 1.4

Figure 1.4. Lookup data are entered for individual farms, allowing associated input features to relate to inputs entered for specific farm fields.

After data are entered into CropMD, generating field-specific nutrient management recommendations and other standardized reports important for documenting, comparing and evaluating management practices are as easy as selecting a button. For example, the Nutrient Budget report recommends estimated application rates of nitrogen, phosphorus, and potassium based on the farmer's crop, yield goal, soil test levels and nutrient contributions from manures and previous legume crops. It also estimates soil phosphorus and potassium levels remaining after crop removal (Figure 1.5).

figure 1.5

Figure 1.5. The Soil Nutrient Status and Budget report provides comprehensive nutrient information by field.

CropMD is a relational database that stores data in two-dimensional tables. Each CropMD table has data relating to a single object, with data from many tables being used to provide an answer to a particular question. For example, CropMD uses data from five tables to calculate a nitrogen recommendation. Also, in conforming to relational database characteristics (Vernon 2001), CropMD has a structure that maintains records and field values in no particular order. In addition, it maintains entity and referential integrity that prohibits two records with the same primary or foreign key; and maintains normalization so that no record contains repeating groups of attributes. When datasets from different farms or years are merged into the same set, field, subfield and crop input records are re-serialized. Although this requires additional computing time, it ensures unique serial numbers for each record.

Pennsylvania's CropMD is not unique. Producers are using CropMD versions created for Iowa, Vermont and New Jersey. The Pennsylvania version is $30 and is available from Penn State University. Contact Jan Pruss (jap5@psu.edu) in the Department of Crop and Soil Sciences.