|
NEND | After attending classes and seminars about using yield data to analyze fields and create zones, I find myself in a predicament. First of all I have John Deere yield data, from Brown box through 2600, and now 2630 data. For the most part I have kept the raw data off my cards. I bought FarmWorks a few years ago because I wanted something more than what Apex offers for reports and zone building. The problem I see now is post calibrating that yield data. Talking to people at workshops and classes, I have learned that different companies deal with calibrating yield monitors in various ways. Correct me if I'm wrong, but if a person tweeks the calibration factor manually on a Deere monitor, it does nothing to the data already logged for that field. I am not sure what is does if you go through the yield calibration process where you zero out the harvested weight, combine for a while, and then enter the know weight. I would like to know if it revises already logged data for that field (and if so, is it just for that field, or that year, or what?). Let's say a person has been diligent about keeping raw data and wants to convert to a different mapping program. In Farm works for example, I don't know of any way you can tell what the yield cal number is for a region (for JD data). So if you read yield data from a field where you adjusted the yield monitor maybe four time for example, and brought them in the FarmWorks, unless you kept records of what the yield cal numbers were for different regions in the field, how would you know how many bushels came from each region? If you merged regions in FarmWorks and then adjusted the while region to reflect the harvested amount, one region might be too high, while another might be too low. I'm not necessarily looking to have perfectly calibrated data, for normalizing field and building zones (I feel like you're looking for variation in the field more so than exactly what the yield was). But the data should reflect a proportionally correct value throughout the field. I am wondering how a person deals with this scenario. I'm sure someone who handles data for others would have some input. | |
|
Managing Raw Data
