The Precision Farming Primer
Appendix C: Checklist for Yield Mapping
Software
© 1999
Precision Farming Primer
Overview — summaries content and organization of the checklist
Part 1 — lists items for General Information and System Specification
Part 2 — lists items for Software Installation, Program Environment, and Documentation/Support
Part 3 — lists items for Data Handling
Part 4 — lists items for Map Generation and Summary
Part 5 — lists items for General Comments and Overview Summary
About — provides references and general information about the @gInnovator project(Back to the Table of Contents)
______________________________Before you spring for a yield mapping software package, there are a few questions you should ask beyond "how much?" and "how pretty?" The following checklist was used in an extensive review of yield mapping systems conducted in 1997. Although the systems have evolved, the basic information outlined in the project still serves as a good reference for evaluating today's software packages.
The evaluation checklist assists users in conducting their own reviews of mapping software marketed for agriculture. While the review project "checklist" focuses primarily on comparative features, readers now have an objective set of criteria to arm themselves with questions as they contact vendors, and a common base on which to make their mapping software purchase decisions.
The checklist provides a comparative listing of software capabilities useful in evaluating yield mapping software packages. This information can assist users in identifying their mapping needs and the software that meets those needs, along with price-performance indicators. Following the five-part checklist is the documentation of the review process used in the @gInnovator review.
1.0 General Information and System Specifications (back to top Appendix C )
1.1 General Information
1.1.1 Company Description
Company Name—identify full company name plus acronym
Physical mailing address—(street and/or PO box, city, state, ZIP code)
Phone (area code, number)—identify product inquiries contact number
Fax (area code, number)—identify product inquiries contact number
E-mail—identify product inquiries contact address
Web Site—identify product inquiries contact URL address
Sales Contact Individual—identify position, title or individual for product inquiries
First Yield Mapping Product Introduction—identify introduction date
Employees in Ag Mapping Group—count
Number of Related Products—count (list products in comments)1.1.2 Product Description
Product Name—identify full product name of the software reviewed (e.g., AggiePaint (AgP) Perfect Mapper); add COMMENT (e.g., acronym is AgP)
Version—identify exact version of software reviewed (e.g., Version 1.01a)
Retail Price—identify retail cost of the software reviewed in US dollars (e.g., US$2,995.95)
Licensing Terms—identify: IU= Individual Unit (maps a particular yield monitor unit with specified serial#); SS= Single Seat (can map multiple units from one computer); MU= Multiple User (software can be loaded and concurrently executed on a specified number of computers); or SL= Site License (software can be loaded and executed on all computers within a site). Note: List all applicable licensing terms noting which level is reflected in the retail price identified above (e.g., IU,SS). Note: SS single seat license version used in the review.
Number of Units in Use—identify which of five levels <50, 51-100, 101-300, 301-500, >500
Anticipated Future Update—identify expected date (version number in comments)
Product Category—identify: D = data confirmation (or viewing) utility; M = mapping from yield monitor data only (e.g., yield, moisture, elevation, flags, etc.); E = extended analysis and layering; A = advanced spatial analysis and modeling, etc.
Intended User Category—identify: B = basic/beginner; I = intermediate; A = advanced and add comments (e.g., basic functions available with default settings in advanced)
One-Sentence Product Description—identify in comments section (e.g., "AggiePaint Farm Edition" provides basic mapping of data from most yield monitors, etc.)1.1.3 Yield Mapping System Type
Stand-Alone Software System—yes or no (yes if software is independent of specific Y-monitor and/or GPS receiver with software sold separately)
Integrated System—yes or no (yes if available as a vendor supported integrated package with Y- monitor and/or GPS receiver). Note: yes for both indicates the system is available as an integrated system with vendor supported Y-monitor/GPS and as a standalone system accessing multiple brands of Y-monitor/GPS configurations (COMMENT: e.g., can indicate if product is integrated but also available as stand-alone for own YM data only)
1.1.4 Geographic Referencing and Data Structure
Default Coordinate/Projection System—identify default system (identify non-earth if coordinates are not "tied to the ground" using a standard system, such as Lat/Long WGS84 or UTM NAD27)
Conversions Among Coordinate/Projection Systems—count of the number of conversions supported (note in COMMENT the major conversions, such as Lat/Long NAD27 to Lat/Long WGS84 and UTM NAD27 to Lat/Long WGS84)
Vector Data Structure—yes or no (yes if line-based data structure, such as point directory, chain, TIN, and/or proprietary, is supported)
Raster Data Structure—yes or no (yes if any grid-based data structure, such as col/row matrix and/or quadtree, is supported)
Raster to Vector Conversion—yes or no (yes if grid-base data can be converted to vector data structure)
Vector to Raster Conversion—yes or no (yes if line-based data can be converted to raster data structure)
Image Data Structure—yes or no (yes if any pixel-based structure, such as .PCX or .TIF, is supported)
1.2 System Specifications
1.2.1 Operating Systems Supported
DOS—yes or no (yes if system can run under DOS; note in comments section the minimum DOS version)
Windows 3.x—yes or no (yes if system can run under Windows 3.x; N/A if simply running as DOS application; note in comment section minimum Windows version)
Windows 95—yes or no (yes if system can run under Windows '95; N/A if simply running as DOS application)
Windows CE—yes or no (yes if system can run under Windows CE)
Windows NT—yes or no (yes if system can run under Windows NT)
MacOS—yes or no (yes if system runs under MacOS; N/A if simply running in PC emulation mode)
Others (OS2, UNIX, etc.)—yes or no (yes if system runs under an operating system not noted above; note in comment section the additional operating systems supported)
OS Interaction—list (identify K = keyboard, P = pen, T = touch, V = voice; list primary method first)
1.2.2 Computing Environment
Minimum/Recommended CPU Family—identify CPU family (e.g., 486/Pentium)
Minimum/Recommended CPU Speed—identify CPU speed (e.g., 33/100MHz)
Minimum/Recommended RAM Memory—identify RAM memory (e.g., 8/16MB)
Minimum/Recommended Disk Storage—identify disk storage (e.g., 500MB/1.2GB)
Minimum/Recommended Graphics Environment—identify video card type (e.g., EGA/SVGA)
Minimum/Recommended Output Device—identify type (e.g., 9x9 BW dot matrix/color inkjet 720x720)
Number COM Ports Required/Recommended—count (e.g., 0/1)
Number PC Card Slots Required—count (e.g., 1/1; note- use Type 2 slot for data card reader)
Special Proprietary Interface or Other Hardware Required—yes or no
1.2.3 Yield Monitor Requirements
Number of Yield Monitors Directly Supported—count
Listing of Yield Monitors Directly Supported—identify monitors (list only those the vendor has direct field experience and provides technical assistance in linking Y-monitor to software)
1.2.4 GPS Receiver Requirements
Number of GPS Receivers Directly Supported—count
Listing of GPS Receivers Directly Supported—identify receivers (list only those the vendor has direct field experience and provides technical assistance in linking GPS receiver to software)
"Generic" Data Streams Supported—identify streams (list only those the vendor has direct field experience and provides technical assistance in linking generic data stream to software¾ e.g., NMEA 183)
2.0 Software Installation, Program Environment, and Documentation/Support (back to top Appendix C )
2.1 Computing Environment Used For Evaluation
CPU Family—identify CPU family(e.g., Pentium)
CPU Speed—identify CPU speed (e.g., 100MHz)
RAM Memory—identify RAM memory(e.g., 16MB)
Disk Storage—Identify disk storage (e.g., 1.2GB)
Graphics Environment—identify video card type (e.g., SVGA)
Output Device—identify device (e.g., Canon BJC 610 Color Bubble Jet Printer, 720x720 resolution)
2.2 Software Installation
2.2.1 Program Media
Internet or Bulletin Board—yes or no (yes if system can be downloaded)
CD ROM—yes or no (yes if system is available on a CD disk)
Floppy Disks—yes or no (yes if system is available as floppy disks)
Media Used For Review Installation— identify IB = Internet, Bulletin Board, CD = CD-ROM or FD = Floppy Disks)
2.2.2 Installation Procedure
"Express" Installation—yes or no (yes if system installs with defaults requiring little or no user interaction)
"Custom" Installation—yes or no (yes if system installs with user specifications, such as directory assignments)
User-Specified Drive—yes or no (yes if system user can specify drive)
Network Support—yes or no (yes if system can be installed and operated under a local area network, such as Ethernet)
Test for Available Space—yes or no (yes if system tests for available space before installation)
Uninstall Feature—yes or no (yes if system can be uninstalled automatically)
Installation Procedure Used For Review—identify: E= Express or C= Custom
Number of Discrete Installation Steps—count (count screens requiring user interaction during installation)
Elapsed Time to Install—number of decimal hours ("breaking shrink wrap" to accessing the system's main screen, including self- and tech-help time)
Clarity of On-Screen Prompts—rank from 1=Poor, Fair, Average, Good, Excellent=5
Ease of Installation Process—rank from 1=Poor, Fair, Average, Good, Excellent=5
2.3 General Program Environment
2.3.1 Program Organization and Access
Number of Directories for Program Storage—count (include all directories and subdirectories containing program files and tutorial data)
Disk Space Required for Program—identify storage requirements for programs and tutorial data (MB)
Supports Program Globals—yes or no (yes if system supports user-specified program initiation parameters, such as default directories, filenames and menu layout)
Number of Intermediate Screens—count (include only screens during requesting user interaction from program initiation to main screen ready to read a data file or invoke a system operation, such as run a tutorial)
General Program Completeness and Organization—rank from 1=Poor, Fair, Average, Good, Excellent=5
2.3.2 User Interface
Command Line Interface—yes or no (yes if user can enter commands lines)
Fixed Menu Interface—yes or no (yes if user can interacts with a single set or cascading series of menu items)
Graphical Interface—yes or no (yes if user can interact with icons, such as buttons, toggles and scroll lists)
Customizable Screen Layout—yes or no (yes if users can modify screen layout, such as moving tool bars and dialog boxes)
Customizable Color Scheme—yes or no (yes if users can change the screen color scheme)
User Interface "Look-and-Feel"—rank from 1=Poor, Fair, Average, Good, Excellent=5
2.4 Program Documentation/Support
2.4.1 Program Documentation:
User's Manual—yes or no (yes if documentation for a general user is available as separate sections or binding)
Reference Manual—yes or no (yes if documentation for a technical user is available as separate sections or binding)
Manual Indexing—rank from 1=Poor, Fair, Average, Good, Excellent=5
Manual Organization—rank from 1=Poor, Fair, Average, Good, Excellent=5
Manual Completeness—rank from 1=Poor, Fair, Average, Good, Excellent=5
Printed Tutorial—yes or no (yes if bound hardcopy tutorial is available)
On-line Tutorial—yes or no (yes if on-line tutorial is available)
Video Tutorial—yes or no (yes if video tutorial is available)
Tutorial(s) Completeness—rank from 1=Poor, Fair, Average, Good, Excellent=5
2.4.2 Program Help
Help Wizard—yes or no (yes if Help Wizard to "walk" through a procedure is available)
Help Search/Find—yes or no (yes if help for searching a topic is available, such as "changing map scale")
Contextual Help—yes or no (yes if help on operations is available, such as automatically providing help for a currently selected operation)
Help Menu—yes or no (yes if help table of contents can be accessed and specified sections retrieved)
Help Completeness and Operation—rank from 1=Poor, Fair, Average, Good, Excellent=5
2.4.3 Technical Assistance:
Fee for Technical Assistance—identify amount in US$ (enter 0 if free)
Duration of Technical Support—identify decimal months (time period for the assistance level listed above¾ e.g., "free for 90 days" would be specified as $0 and 3.0 months)
Technical Assistance Hours—identify office days/hours (e.g., "8-5 Monday through Friday at the Iowa home office" would be specified as M-F/8am-5pm CST)
800 Phone Line—yes or no (yes if free 800 phone line available for tech assistance)
Fax/Email Contact Point—yes or no (yes if electronic tech assistance is available)
Phone Time to Reach Technician—number of minutes (sum multiple phone-backs if encountered) In COMMENT. Note also time and date called.
Time for Fax/E-mail Turn-Around—number of decimal hours
Assistance Access and Competence—rank from 1=Poor, Fair, Average, Good, Excellent=5; "test" question
2.5 Overall Installation/Environment/Support Evaluation Ratings (SUMMARY)
Installation Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
Program Environment Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
Documentation/Tutorial Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
Program Help Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
Technical Assistance Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
OVERALL Installation, Environment, and Support Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
3.0 Data Handling (back to top Appendix C )
3.1 Data Exchange Formats
Standard Data Files—identify formats supported and exchange type as I= import, E= export, B= both (e.g., CSV=B, Excel=I, dBASE=B etc)
Yield Monitor Files—identify formats supported and exchange type as I= import, E= export, B= both (e.g., AgLeader 2000 Basic = B, AgLeader 2000 Advanced = B, MicroTrack = I, Deere = I etc)
Vector Geographic Data Files—identify formats supported and exchange type as I= import, E= export, B= both (e.g., AutoCAD DXF, ArcInfo Exchange E00, MapInfo Interchange Format MIF, etc.)
Raster Geographic Data Files—identify formats supported and exchange type as I= import, E= export, B= both (e.g., ASCII Matrix=B, Surfer GRD=I, USGS DEM=I)
Graphics/Image Files—identify formats supported and exchange type as I= import, E= export, B= both (e.g., PCX=B, TIF=I, BMP=I etc)
3.2 Data Import/Export Operation
Imported Data Stored As a File—yes or no (yes if data import and map generation are two distinct procedures and the imported data is stored as a file; if no, then identify NA = not applicable for remaining questions in this section)
Retains Calibration/Header/Metadata Information—yes or no (yes if system creates internal files containing information about a Y-monitor data set)
Supports Import Batch Processing—yes or no (yes if user can specify several files to be imported without user interaction)
Import Program (DLL) Type—identify P = proprietary, M = monitor mfg, or B = both
Elapsed Time to Import "Clean" Data File (First Time)—number of minutes (from initiation to end of reading file, including self- and tech-help learning time)
Processing Time to Import "Clean" Data File (Proficient)—number of decimal minutes
Number of Steps to Import "Clean" Data File—count (include all user interactions required from specifying raw data file through completion of importing the data)
Import/Export Completeness and Effectiveness—rank from 1=Poor, Fair, Average, Good, Excellent=5
3.3 Data Merging/Disaggregation
3.3.1 Data Merging/Disaggregation Specifications
Data Merging Supported—yes or no (yes if multiple data files, such as data for a field by two different data cards, days, or Y-monitors, can be merged; if no, then identify NA = not applicable for remaining questions in this section)
Supports Simple Merging Based on Date/Time—yes or no (yes if system merges data files for the same field collected at different times)
Supports Simple Merging Based on Multiple Fields—yes or no (yes if system merges data files for different fields into a single "farm-wide" data layer)
Supports Interlaced Merging—yes or no (yes if system merges data files collected for the same field by two or more Y-monitors operating at the same time)
Supports Batch Processing for Merging—yes or no (yes if user can specify several files to be merged without user interaction)
Supports Automatic Field Partitioning Based on Location—yes or no (yes if system can disaggregate a field into parcels based on geometry, e.g., "quarter-field" blocks)
Supports Automatic Field Partitioning Based on Attribute—yes or no (yes if system can disaggregate a field into parcels based on attribute value, e.g., "high yield" areas)
Supports Interactive Field Partitioning—yes or no (yes if system can disaggregate a field into user specified parcels, such as "heads-up" digitized areas)
Data Merging/Disaggregation Completeness—rank from 1=Poor, Fair, Average, Good, Excellent=5
3.3.2 Data Merging Operation
Elapsed Time to Reconstruct "Multiple" Data File (First Time)—number of minutes (from initiation, importing, and merging multiple files into a fully reconstructed file of the entire field, including self- and tech-help; if the system does not support data merging, then identify NA = not applicable for this and remaining responses in 3.3.2 Data Merging Operation)
Processing Time to Reconstruct "Multiple" Data File (Proficient)—number of decimal minutes
Number of Steps to Reconstruct "Multiple" Data File—count (include all user interactions required from specifying raw data files through completion)
Data Merging/Disaggregation Effectiveness—rank from 1=Poor, Fair, Average, Good, Excellent=5
3.4 Data Management/Archival
3.4.1 Data Management Scheme
Internal Data Management Support—yes or no (yes if system has procedures for managing and organizing the data files beyond simply a suggested directory and naming convention; if no, then identify NA = not applicable for remaining questions in this section)
Date/Time—yes or no (yes if data files can be automatically organized and accessed by the data/time of their acquisition)
Field Name or ID Number—yes or no (yes if data files can be automatically organized and accessed by unique identification number for each field, such as its ASCS Field Number)
Farm Name or ID Number—yes or no (yes if data files can be automatically organized and accessed by unique identification number for farm, effectively linking several fields)
Geographic Location—yes or no (yes if data files can be automatically organized and accessed by their geographic positioning, such as field centroid)
Crop/Variety—yes or no (yes if data files can be automatically organized and accessed by crop type, variety planted, or other management action)
Yield Monitor ID Number— yes or no (yes if data files can be automatically organized and accessed by unique identification number for each Y-monitor)
Other Indexing Schemes— yes or no (identify in the comment section other schemes by which data files can be automatically organized and accessed)
Map Library/Workspace Organization—yes or no (yes if a library of all maps is maintained and can be selectively reassembled into workspace environments, such as "Joe's Fields of Interest")
Map Lineage/Pedigree—yes or no (yes if an integrated file containing information about individual maps is maintained, such as field history and data acquisition info)
Modeled Map Logic—yes or no (yes if system supports tracking of the procedures used to generate a derived/modeled map, e.g., a flow chart of map analysis processing analogous to identifying ingredients and procedures in a recipe for banana bread)
System Procedure for "Off-Line" Archival—yes or no (yes if system has a fully integrated capability for compressing and decompressing a map or group of maps analogous to the popular PKZIP system)
System Procedure for Raw Data Archival—yes or no (yes if system retains complete original raw data file and does not replace or delete it after pre-processing)
System Procedure for Backup—yes or no (yes if system has a fully integrated capability for backing up a map or group of maps to another storage device, such as magnetic tape)
Data Management/Archival Completeness—rank from 1=Poor, Fair, Average, Good, Excellent=5
3.4.2 Data Management Operation
Number of Files Used to Store "Clean" Data Set—count (include all "linked" files used to store the data)
Storage Requirement of the "Clean" Data Set—identify disk space required (MB)
Number of Steps to Assign Then Retrieve a File Using Data Management Indexing—count (include all user interactions required from specifying raw data files through completion)
Data Management/Archival Effectiveness—rank from 1=Poor, Fair, Average, Good, Excellent=5
3.5 Ancillary Data Input
3.5.1 Digitizer and Other Geo-referenced data Input
Ancillary Data Input Is Supported—yes or no (yes if mapped data can be directly entered into the system, such as digitizing a field's boundary or access road; if no, then identify NA = not applicable for remaining questions in this section)
Manual From Digitizing Tablet—yes or no (yes if "heads-down" digitizing using cursor to trace features from a map taped to a digitizing tablet is a feature)
Manual On-Screen—yes or no (yes if "heads-up" digitizing using mouse to trace features directly on the computer screen is a feature)
GPS Data Stream—yes or no (yes if "feet-down" digitizing using GPS coordinates to trace features in the field is a feature)
Multimedia Link—yes or no (in comments, indicate type¾ e.g., voice, video, or other annotation input and whether real time or post-processed data) add COMMENT
Ancillary Systems and Sensor Data—yes or no (yes if system supports other onboard or remote data such as weather station, protein/oil analyzer, pH sensor, etc)
3.5.2 Geographic Registration
Registration Point Entry During Digitizing—yes or no (registration point coordinates can be specified during the digitizing session)
Registration Point Entry After Digitizing—yes or no (predefined registration point coordinates can be stored in an existing linked file)
3.5.3 Topological Structuring
Point Features—yes or no (discrete X,Y location)
Simple Line Features—yes or no (set of "loosely" linked X,Y coordinates used to draft independent lines)
Structured Line Features—yes or no (set of "topologically structured" X,Y coordinates organized into sets of interconnected line features)
Simple Polygonal Features—yes or no (set of "loosely" linked X,Y coordinates used to simply draft independent polygon boundaries)
Structured Areal Features—yes or no (set of "topologically structured" X,Y coordinates organized into sets of spatially related polygonal features)
3.5.4 Attribute Tagging and Database Linking
Internally Assigned Attribute Tag—yes or no (yes if each map feature assigned an internal identification number)
"On-the-Fly" User Assigned Attribute Tag Link—yes or no (yes if user can assign map feature "alias," such as Field 3, during the digitizing process which can be used to join a pre-existing database map features)
"On-the-Fly" Database Table Definition/Entry—yes or no (yes if user can define and complete entries in a database table during the digitizing process)
Interactive Database Table Entry/Editing—yes or no (yes user can "select" a map feature then append or change its database information)
3.5.5 Raster Data Entry and Updating
Batch Data Entry—yes or no (yes if data can be read into a table identifying Column, Row and cell Value)
Interactive Data Entry—yes or no (yes if user interactively specifies Column, Row and cell Value)
"Point and Click" Value Assignment—yes or no (yes if user identifies cell(s) with a mouse then specifies the Value)
Automatic Regridding—yes or no (yes if changes the cell size through resampling the analysis grid of an existing raster map resulting in an increase (higher spatial resolution) or decrease (lower) in the number of Columns and Rows covering the mapped area)
Digitized Data Input Completeness—rank from 1=Poor, Fair, Average, Good, Excellent=5
3.6 Overall Data Handling Evaluation Ratings (SUMMARY)
Data Import/Export Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
Data Merging/Disaggregation Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
Data Management/Archival Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
Ancillary Data Input Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
OVERALL Data Handling Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
4.0 Map Generation and Summary (back to top Appendix C )
4.1 Data Preprocessing
4.1.1 Data Preprocessing Approach
Data Preprocessing Support—yes or no (yes if system preprocesses the data, such as data conditioning or aggregation to a continuous surface, before generating a map display; if no, then identify NA = not applicable for remaining questions in this section)
Data Preprocessing Integrated with Map Generation—yes or no (yes if data preprocessing is done during map display and conditioned and/or aggregated data is not stored as a new map)
Processed Data Stored as a New Map—yes or no (yes if the conditioned and/or aggregated data is stored as a separate map, and not simply used for generating the map display, then discarded)
Percent of the Data Eliminated—identify percent of the data eliminated by ratio of difference between "raw" and "processed" data (# of data points or file size)
Elapsed Time to Preprocess (First Attempt)—number of decimal minutes (from initiation through preprocessed data file storage)
Processing Time to Preprocess (Proficient)—number of decimal minutes (from initiation through preprocessed data file storage)
4.1.2 Point Data Conditioning
Identify Positioning Errors—yes or no (yes if system automatically identifies "out-lyers" where GPS coordinates appear spurious )
Identify Data Errors—yes or no (yes if automatically identifies Y-monitor or other data ("out-lyers") values which appear spurious)
Disposition of Positioning/Data Errors—identify type of disposition as U= user specified, D= automatically deletes record, A= automatically adjusts record using internal algorithm
Mass Flow Adjustment—yes or no (yes if adjusting yield measurements based on time/distance/speed lag: identify type of adjustment in comments)
4.1.3 Data Aggregation for a Continuous Surface
Swath Element Aggregation—yes or no (yes if aggregated cell size is adjusted to width and path/speed of combine head, resulting in a series of interconnected rectangular blocks)
Analysis Grid Aggregation—yes or no (yes if aggregated cell size and position is geometrically fixed, resulting in a spatially consistent analysis grid); identify fixed cell size in comments
Flexible Spatial Resolution—yes or no (yes if user can specify cell size used to aggregate the data, such as combine head width (swath element) or grid dimensions (analysis grid)); identify in comments
Flexible Aggregation Algorithm—yes or no (yes if user can specify technique used to aggregate data, such as simple or weighted moving average of neighboring data values); identify procedures in comments
Procedure to Fill Gaps in Raw Data—identify: SA = simple neighborhood average; NN = weighted nearest neighbors; KR = Kriging; O = other (identify other in comments)
Data Preprocessing Completeness—rank from 1=Poor, Fair, Average, Good, Excellent=5
4.2 Map Generation
4.2.1 Map Types
Point Yield Map (Y-monitor Data)—yes or no (yes if a point map can be generated using colored "dot" to represent each measurement)
Swath Element Yield Map (Y-monitor Data)—yes or no (yes if a swath element map can be generated using a colored "block" to represent aggregation of measurements occurring along the width of the harvester's header for distance based on time/speed)
Smoothed Yield Map (Y-monitor Data)—yes or no (yes if a smoothed map can be generated using a colored "cell" and/or "contour line" to represent the yield surface formed by aggregation of measurements occurring within a statistical analysis grid)
Other Y-monitor Data Map(s)—yes or no (yes if maps can be generated using other Y-monitor data, such as moisture; list other maps in comment section)
Harvest Path Map (GPS X,Y Coordinates)—yes or no (yes if a map of the path of the harvester can be generated)
Comparison Map—yes or no (yes if a map can be generated summarizing two or more spatially registered maps, such as "normalizing" or averaging two year's data or comparing differences between two years; list in comment section)
Elevation (GPS Z Coordinates) Surface—yes or no (yes if a map of terrain relief can be generated)
Interpolated Surfaces—yes or no (yes if surface maps, such as terrain elevation or soil nutrient levels, can be generated from a set of discrete point samples)
Prescription Map—yes or no (yes if maps of management action, such as amount of fertilizer or seeding rates, can be generated; LIST other maps in the comment section)
Economic Analysis Surfaces—yes or no (yes if maps of economic analyses, such as cost, revenue or net income, can be generated; list other maps in the comment section)
Selection Maps—yes or no (yes if maps resulting from database geo-queries, such as locating all locations within a field that have both high yield .AND low high moisture, can be generated; list other maps in the comment section)
Statistical Error Maps—yes or no (yes if maps of statistical analyses, such as standard deviation and coefficient of variation of any map layer, can be generated; list other maps in the comment section)
Univariate GIS Analysis Map—yes or no (yes if maps of spatial relationships within a map layer, such as stream buffers or terrain steepness, can be generated; list other maps in the comment section)
Multivariate GIS Analysis Map—yes or no (yes if maps of spatial relationships among map layers, such as spatial correlation, multivariate clustering, or region-wide summaries, can be generated; list other maps in the comment section)
Verification Map—yes or no (yes if map of actual output of machine controlled¾ e.g., map of actual rate or population applied regardless of prescription command)
Map Type Completeness—rank from 1=Poor, Fair, Average, Good, Excellent=5
4.2.2 Map Generation Process
Number of Steps to Generate Basic Yield Map—count (from initiation to final display accepting system defaults; note whether "point" or "smoothed" map)
Elapsed Time to Generate (First Attempt)—number of decimal minutes (from initiation through basic yield map display, including self- and tech-help time; note whether point or smoothed map)
Processing Time to Generate (Proficient)—number of decimal minutes (from initiation through basic yield map display; note whether point of smoothed map)
Map Generation Completeness and Effectiveness—from 1=Poor, Fair, Average, Good, Excellent=5
4.3 Map Display
4.3.1 Types of Display
Output Medium—identify S= screen, P= printer/plotter, or B= both
Point—yes or no (yes if system assigns a color to each measurement based on its data value, then displays a colored "dot/symbol" at the location on the screen or paper determined by its GPS coordinates)
Swath Element—yes or no (yes if system aggregates individual measurements into a series of aligned "blocks" along the harvest path, assigns a color to each block based on its "typical" or accumulated value, then displays colored "rectangles" at the appropriate locations)
Smoothed (Filled)—yes or no (yes if system removes the "salt and pepper" effect of the individual measurements and fills in any gaps by considering the neighboring yield measurements within the vicinity of each map location (smoothed map), then displays colored "squares" corresponding to the smoothed values at each grid space forming the map surface)
Smoothed (Contour)—yes or no (yes if system displays a smoothed map as a series of "contour lines" corresponding to the break lines along the map surface formed by data intervals); list data interval etc and other explanation in comments
Surface—yes or no (yes if system displays a smoothed map as a set of X,Y line traces forming a "Fishnet" perspective plot)
Draped Surface—yes or no (yes if system displays a smoothed map as a "Fishnet" perspective plot with color filled areas, such as data intervals, "draped" over the surface)
Map Display Types Completeness—rank from 1=Poor, Fair, Average, Good, Excellent=5
4.3.2 Data Categorizing
Fixed Categorizing—yes or no (yes if preset data intervals are used with no ability for the user to specify specific ranges or categorizing technique)
Equal Interval Technique—yes or no (yes if mapped data intervals contain equal ranges of data values)
Equal Count Technique—yes or no (yes if mapped data intervals contain approximately equal number of data points)
Quantile Technique—yes or no (yes if mapped data intervals divide an ordinal ranking into a specified number of classes containing approximately equal percentages of the data population)
Standard Deviation Technique—yes or no (yes if mapped data intervals can identify positive and negative standard deviation steps around the data mean)
Natural Breaks Technique—yes or no (yes if mapped data intervals computed to minimize the difference between the data values and their mean within each interval)
User-Specified Breaks (Custom)—yes or no (yes if intervals can be directly specified by the user)
Data Categorizing Completeness—rank from 1=Poor, Fair, Average, Good, Excellent=5
4.3.3 Display Colors/Symbols/Patterns
Display Colors—identify: F= fixed if user cannot change; C= custom if user can change colors used in the map display; S= if "single hue" gradations can be selected
Display Symbols/Patterns—identify: F= fixed if user cannot change; or C= custom if user can change the symbols and/or patterns used in the map display
Display Colors/Symbols/Patterns Completeness and Effectiveness—rank from 1=Poor, Fair, Average, Good, Excellent=5
4.3.4 Display Features
Map Scale—identify F= fixed or C= custom if user can change displayed map scale
Map Zoom—yes or no (yes if user can interactively increase or decrease map scale)
Map Pan—yes or no (yes if user can interactively shift a map display up, down, left, right)
Cursor Queries—yes or no (yes if user can use the cursor to query map information, such as geographic coordinates, map value, distances, etc.)
Annotation—yes or no ( yes if user can freely draw or write on the map display)
Display Features Completeness and Effectiveness—rank from 1=Poor, Fair, Average, Good, Excellent=5
4.3.5 Map Labeling
Map Labeling Available—yes or no (no if labels cannot be inserted within the map boundaries; if no, indicate NA = not applicable for remaining questions in this subsection)
Labeling Control—identify: A= automatically placed,; U= user placed; or B= both
Label Format—identify: F= fixed if user cannot change; or C= custom if user can change format, such as text styles, color and size, used in the map display
Label Positioning—identify: F= fixed if user cannot change; or C= custom if user can change the positioning of labels used in the map display
Map Labeling Completeness and Effectiveness—rank from 1=Poor, Fair, Average, Good, Excellent=5
4.3.6 Map Legend
Map Legend Available—yes or no (no if a legend is not available and indicate NA = not applicable for remaining questions in this subsection)
Legend Control—identify: A= automatically placed; U= user placed; or B= both
Legend Format—identify: F= fixed if user cannot change; or C= custom if user can change the format, such as text styles, color and size, used in the map display
Legend Positioning—identify: F= fixed if user cannot change; or C= custom if user can change the positioning of labels used in the map display
Legend Printing—yes or no (yes if legend can be printed with map display)
Map Legend Completeness and Effectiveness—rank from 1=Poor, Fair, Average, Good, Excellent=5
4.3.7 Ancillary Layers
Ancillary Layers Supported—yes or no (no if only Y-monitor data supported and ancillary layers, such as roads and streams, cannot be; if no, indicate NA = not applicable for remaining questions in this subsection)
Graphical Vector Overlay—yes or no (yes if ancillary vector overlays, such as lines depicting roads and streams, can be displayed)
Graphical Raster Underlay—yes or no (yes if ancillary raster underlays, such as an airphoto of the farm, can be displayed)
Ancillary Layer Completeness and Effectiveness—rank from 1=Poor, Fair, Average, Good, Excellent=5
4.4 Summary Tables/Graphics
Summary Tables/Graphics Supported—yes or no (no if only map displays are produced; if no, indicate NA = not applicable for remaining questions in this subsection)
Weigh Wagon or Other Weighted/Scaled Tables—yes or no (yes if a weigh table estimating total yield for portions of a field can be made from either Y-monitor data or map summary)
Statistical Tables—yes or no (yes if a table of descriptive statistics, such as average, standard deviation or coefficient of variation, can be generated for a map)
Coincidence Tables—yes or no (yes if a table summarizing the coincidence among two or maps, such as a cross-tabular table, can be generated)
Plot of Data Distribution for Individual Maps—yes or no (yes if the data values comprising a map can be plotted as a histogram or X,Y line plot)
Plot of Data Distribution for Multiple Maps—yes or no (yes if the data values for two or more maps can be plotted as a bar chart, pie chart, line plot, or X,Y scatter plot)
Summary Tables/Graphics Completeness and Effectiveness—rank from 1=Poor, Fair, Average, Good, Excellent=5
4.5 Map Layout
Screen Capture—yes or no (yes if screen can be captured to graphics file, such as .PCX or .TIF)
Map Layout Supported—yes or no (yes if user can interactively specify display content and characteristics; if no, indicate NA = not applicable for remaining questions in this subsection)
Multiple Layer Displays—yes or no (yes if multiple layers, such as yield and farm roads integrated into a single display to screen and or output device)
Multiple Map Displays—yes or no (yes if multiple maps, such as yield for two different years, can be positioned side-by-side in a single display to screen and or output device)
Integrated Display of Maps, Tables and Graphs—yes or no (yes if maps, tables and graphs, such as a yield map, a table of its descriptive statistics and a histogram of its data distribution, can be composited into a single display)
Graphical Objects Support—yes or no (yes if layout elements, such as maps, table and graphs, are treated as "graphical objects" which independently can be sized, positioned, etc.)
Map Layout Completeness and Effectiveness—rank from 1=Poor, Fair, Average, Good, Excellent=5
4.6 Mapping and Output Evaluation Ratings (SUMMARY)
Data Preprocessing Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
Richness of Map Types Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
Map Display Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
Summary Tables and Graphics Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
Ease Generating a Basic Yield Map Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
OVERALL Yield Mapping Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5
5.0 General Comments and Overall Summary (back to top Appendix C )
General Yield Mapping System Ratings (LASTING IMPRESSIONS)
Ease of Use Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5 (are installation, data handling and yield mapping procedures intuitively presented and easy to use?)
Features Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5 (does the system offer a complete set of data handling and yield mapping features?)
Performance Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5 (are maps and summaries quickly, efficiently and flexibly generated from field collected data?)
Support Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5 (is support readily available as easily accessible as printed documentation, online help and technical assistance?)
Overall Rating—rank from 1=Poor, Fair, Average, Good, Excellent=5 (compared to other yield mapping systems, how does this system generally compare?)
5.1 General Comments
Strengths— concise wording of major advantages (e.g., comprehensive data handling, efficient storage; fast yield map generation; good documentation; many GPS receivers supported)
Weaknesses— concise wording of major disadvantages (e.g., unable to handle multiple data files of the same field; fixed 4-color map display; non-earth coordinate system; does not support ancillary map features for visual reference)
5.2 Include a narrative description of the system
Comment on any particularly interesting responses (pro and con)
_______________________________________________
Review of Mapping Systems for Site-Specific
Management (back
to top Appendix C )
Project Description
The @g/INNOVATOR (@/I) mapping
software review is a "reader service" project, approached from a user
point of view. We aim to assist our readers in understanding the
capabilities of mapping software, and assessing their needs as a critical
component in site-specific decision-making.
The Evaluation Team
The project is coordinated by Dr.
Joseph K. Berry, Berry & Associates // Spatial Information Systems, Ft.
Collins, CO, a leading geographic information systems consultant, educator,
author and developer. The team includes farm producers, agricultural
advisers and academics. (This yield mapping review continues the
preliminary evaluation work performed by Edaphos Ltd, Minneapolis, MN.)
The Project Sponsor
@g/INNOVATOR is a publication of
Successful Farming, published by Meredith Corporation. It is the premier and
authoritative resource for agricultural computing, site-specific precision
farming and information technologies for agriculture. The @g/INNOVATOR
INSTITUTE is an educational expression of @g/INNOVATOR, which provides online,
in-print and on-site information resources.
Project Contacts
|
@g/INNOVATOR //
Successful Farming |
Berry &
Associates // Spatial Information Systems, Inc. |
Project Scope
The current phase of this review project involves a comparative portion and an evaluative portion, with the following objectives:
Identify a set of "objective criteria" to be used by the @/I review team to evaluate mapping software for agriculture. The team consists of experienced farm producers, ag advisers, and academics. The criteria have been developed with the direct input of the mapping software developer community as well as users. (In addition, this criteria can be used by readers to perform their own software reviews.)
Prepare a non-evaluated "comparative listing" of all features of mapping software commonly used in agriculture (with "Yes/No/NA(not apply)" responses coming directly from the developers/vendors.
Objectively "evaluate yield mapping" features of the mapping software products for sale in the ag market, with the procedures and criteria outlined below. Each member of the review team will evaluate the software. Scores will be listed individually as well as averaged for a composite rating for each product, to aid user interpretation.
Publish "ratings results" to reflect the reviewed yield mapping portion, while taking into account the listings of features for each product. Results will also reflect the software category (purpose and scope), so as not to unduly penalize products with more or fewer features. Results will also include additional vendor comments.
Other phases of this on-going review process will further investigate other features and capabilities. This portion focuses on assisting the reader in identifying his mapping needs and the products that can meet those needs. Our goal is an informed consumer--which makes a better customer.
Extended features and modules, such as data analysis, will be noted but not evaluated. At this time, it is beyond the scope of this project to comment on the relative accuracy of the systems reviewed. As a future reference, potential extensions of this yield mapping software review include yield mapping accuracy, data collection systems and procedures (e.g., sampling and scouting systems), prescription mapping, spatial analysis/modeling, variable rate application instrumentation and procedures, performance mapping and advanced data analysis systems.