I don't know of a single yield mapping customer who has not had a "D'OH" moment, when reviewing yield data, only to see a duplicated field name, yield data which shows up in the wrong field and other disappointments. The more of these wrongly assigned bits of data, the greater the frustration of the software user. Many have simply thrown up their hands in surrender, blamed the brand or abandoned the exercise in confusion. My general reaction to these problems is to say "No big deal..."
Less than perfect yield data represent 4 general issues:
1. Problem: Wrong Field Names Solution: Edit it back in the office If you don't like the name you gave the field out in the combine: Edit it in the office software. In SMS: Highlight the field name in the management tree, right mouse click to select EDIT from the pop-up menu. From this window type the field name you wish to use and even re-select the grower or farm name that this field should be associated with. The illustrations below show the original window where we change Field name and add a different Farm designation, and the managment tree after the change is saved.
So, if you don't like the way the field is named as it comes in from the yield monitor, then change it. If you do not want this to happen again, then utilize the device set-up utility, which allows you to send field names FROM the office TO the yield monitor. All brands can be sent the list of field names. You will use the office software to make your perfect list, then send it to the equipment.
2. Problem: Data shows up in wrong field Solution: Use the SMS tool: SPATIAL SORT If you have a boundary for the field, whether drawn or mapped with GPS, SMS has a function that Sets the field boundary (or freezes it to the field name). In effect this makes the boundary the "official" field boundary that the program can then use to search for data that belongs within it. So we have a bunch of yield data that is sitting under the wrong field name because someone forgot to change the field name when they changed fields. (Note: Usually this is blamed on someone else as in "Dad was running the combine when...") Simply highlight the offending data, right click and choose SPATIAL SORT> Sort Loads into Fields. As long as there is a boundary in the right field, the data will disapear from this field and reappear in the right one. Occassionally yield in the wrong field doesn't move. This is because it was harvested with the same load name as the right stuff. In this case you select the load that needs to be divided and right click to select the SPLIT LOAD/REGION command. In the same way as above the load will be split and assigned to the right field according to the boundary area.
3. Problem: Yield map data doesn't match scale weights Solution: First-Decide if it is important to change this The purpose of a yield map is to assess the within-field variability. The yield patterns will be the same (higest here, lowest there) regardless of the actual values and some users only wish to see these relative differences. Actual values are of secondary importance. Yield summaries are most useful if they are correct of course. You want them to reflect the actual performance of the season. There are many reasons why they are slightly off, or completely off, depending how consistently you performed the calibration during the season. A minor deviation is expected.
To fine tune the summary highlight the harvest level in the management tree, right click to select ADD SIMPLE ANALYSYS/SCALE DATA. This function allows you to enter a factor (> 1= increase, <1 = decrease). If you needed to reduce the yield to 95% of the summary total you would enter .95. The data will be recalculated so that all data is incremenatally decreased. Your map will show the same patterns, but will show a corrected range of values. Below we see unscaled data (mid range 148 bu/ac) and data scaled to 75% of the original-exagerated for illustration purposes (mid range 110 bu/ac).
This function does not change the original values; they remain as the monitor summary. An adjusted has been made to the spatial data. You can remove this analysis. To see the results of this correction select the summary tab and select spatial data as the summary type.
4. Problem: Missing map data Solution: Check as you go and get to know your system Most of the newer yield monitors show you a map onscreen as you go. If you don't see a map while you are combining STOP! Something is amiss. Fix it now, as this is an indication that data is not being logged. Using your manual as reference; make sure you have set up the logging function. Usually there are settings in the memory and /or console to indicate you are mapping internally to 'the box' or to a memory card. Is the card in? Did you you turn on mapping? Is there a GPS connected?
In some newer systems all of the data is logged to internal memory and you have to actually go to the data management menu to EXPORT or send the data to a card or USB device to move the information to the office. If you get to the office and maps you were sure would be there aren't go back to the combine and export it out again. In the older yield monitors that did not have map display there are two important indicators of successful data logging. In these systems, yield and load summary data was written to the internal memory of 'the box', but the GPS locational data and second by second yield went directly to the card.
There is a symbol that shows you have a memory card inserted, that you have successful GPS signal (DG) and an arrow pointing to card, to illustrate GPS is going to CARD! If a data card goes to the office and no maps come in...chances are you never logged it in the field. If you download often, this operation problem can be fixed before too much data is lost. Check it early and often is the rule of thumb.