GeoPard Tutorials | Precision Ag Software
  • Introduction to GeoPard
    • GeoPard Platform: Frequently Asked Questions (FAQ)
  • 🖥️Product Tour - Web App
    • Getting Started
      • Create a new farm
      • Draw a new field
      • Upload a field boundary
      • Edit a boundary
      • Edit a field name
      • Add a label
    • 🛰️Satellite Monitoring
      • Order Planet Scope (3m daily) imagery
      • Indices for Crops and Soils
      • 📈Crop Development Index Graph
    • 📊Zones Maps and Analytics
      • Assign Variable Rates in the Zones (Ag inputs Rates Distribution Tool)
      • Creating Zones Map using Satellite Imagery
      • Creating Zones Map using Soil/Yield/As Applied Data
      • Creating Zones Map using Topography
      • Creating Zones Map using a Template
      • Draw Zones Manually, Clone from an existing layer
      • Usage of Data Classification
      • Edit Zones Map: Merge & Split
      • Multi-Year Zones
      • Multi-Layer Analytics
      • Compare layers
      • Heterogeneity factor
      • Relative variation factor
    • 📊Equation-based Analytics
      • Batch Equation analytics
      • Catalog of Predefined Agronomic Equations
      • Catalog of Custom Functions
    • ⛰️Topography
    • ⛰️3D Maps
    • Import
      • Field Boundary
      • Soil Data
      • Yield Data
      • As Applied/As Planted Data
      • Machinery Proprietary Formats
      • Import from MyJohnDeere
    • Export / Download
      • Field Boundary Export
      • Batch Export of Boundaries, Zones and Scouting Pins
      • Zones Map Export as shapefile
      • Satellite Imagery Export as geotiff or geojson
      • Export Scouting Notes as shapefile
      • Export VRA map In ISOXML Format
      • Export to MyJohnDeere
    • 🤖API
    • Operations Log - Track errors/Imports and Analytics
    • Organizations and Roles
    • Farms Sharing between Accounts & Organizations
    • Managing Crop Season information with tags(labels)
      • Case: Managing fields for several clients
      • Case: Season details including crop and year
      • Case: Field operation details
    • ⚙️User Settings
      • Subscriptions, Account limits & Plans
      • Restoring password
      • Order the package
      • Changing preferences
    • 🚜John Deere Operations Center Integration
      • 🚜John Deere Operations Center Integration
        • 1. Create Free Trial Account with you John Deere Account
        • 2. Connect to JohnDeere Operations Center
        • 3. Connect to John Deere Organizations
        • 4. Import into GeoPard from John Deere Operations Center
        • 5. Configure Automated Data Sync
        • 6. Export Rx Maps to John Deere Operations Center as Files
        • 7. Export Field Boundaries into John Deere Operations Center
          • 7a. Organization configuration of export boundary to John Deere Operations Center as File
        • 8. Export Rx Maps to John Deere Operations Center as Work Plans
        • 9. Export Soil, Topography, Satellite or Analytics as Map Layers
      • 🚜John Deere Operations Center Data Sharing
        • 1. "Staff Member" sharing
        • 2. Problem-solving of "Staff Member" sharing
        • 3. "Partner Organization" sharing
        • 4. Problem-solving of "Partner Organization" sharing
        • 5. Problem-solving of import from John Deere to GeoPard
        • 6. Problem-solving of Work Plan creation
        • 7. Sharing Fields/Boundaries Between Partner Organizations in John Deere Ops Center, DataSync config
  • 🚀Changelog & Product Releases
    • Release Notes
      • Release Web April 2025 (Rates Distribution, improved Legends)
      • Release Web March 2025 (Improved Zones, WorkPlans updates, Yield data enhancements)
      • Release Web January 2025 (Free Trial, Usage-based Pricing Plan, USDA Yield Cleaning protocol, Export of calibrated Yield data to John Deere Ops Center, Import of kml)
      • Release Web August 2024 (Data Layer Previews, Spatially localized Zones; Use zones and Equations in new Equations)
      • Release Web July 2024 (Equation Map creation, Spatially localized zones, Seeding and Application Work Plans)
      • Release Web May 2024 (Raw view for Satellite Images, export of Zone Maps as WorkPlan to the John Deere Operations Center, redesign of Batch Analytics)
      • Release Web April 2024 (Batch Equation Maps and enhanced layer transparency)
      • Release Web February 2024 (Per area pricing, units)
      • Release Web January 2024 (many UI improvements)
      • Release Web November 2023 (Clone Polygons, Subscription management)
      • Release Web October 2023 (Yield Calibration, Equation Maps as ISOXML, PDF Export and John Deere Integration)
      • Release Web September 2023 (Cleaning & Calibrating Yield Datasets, more languages support)
      • Release Mobile August 2023 (Mobile app impovements)
      • Release Web July 2023 (Operations Log page, Sum in datasets)
      • Release Web June 2023 (Improved Equations, Operations log v1)
      • Release Mobile May 2023 (Social Login)
      • Release Web May 2023 (John Deere integration improvements)
      • Release Web January 2023 (huge amount of small improvements)
      • Release Web October 2022 (Integration with AgGateway protocols, Isoxml support and more)
      • Release Web April 2022 (3D maps and Zoning Tools)
  • 👨‍🌾Agronomy
    • Precision Agronomy Use Cases & Best Practices Overview
    • Field Management Zones (Productivity Zones) Creation Process
    • Variable Rate Seeding (Planting) Maps
    • Yield Calibration & Cleaning
    • Synthetic Yield Map
    • Create Soil Sampling Zones, Points, Route, export as KML, and execute
    • Evaluate Accuracy of Seeding Application
    • Evaluate Accuracy of Fertilizer Application
    • Field Trial Analytics
    • Nitrogen Use Efficiency & Uptake
    • Comparing Yield Datasets
    • Compare Soil Scanner Data between Years
    • Flood Detection / Insurance report
    • Profit Maps (COMING)
    • VRA/Rx/Prescription Fertilizer Maps (COMING)
    • VRA/Rx/Prescription Nitrogen Maps (COMING)
    • VRA/Rx/Prescription Spraying Maps (COMING)
    • Multi-Layer Field Potential Maps (COMING)
    • VR Lime Application Based on Soil Scanner pH Data (COMING)
    • Merging Yield Datasets Belonging to the Same Field (COMING)
  • 📱Product Tour - Mobile App
    • Installation
    • Logging in
    • Viewing satellite images
    • Viewing zones maps
    • Viewing soil data
    • Viewing yield data
    • Viewing topography maps
    • Viewing as applied datasets
    • Working in the field/Scouting zones maps
    • Working offline
    • Filters
    • Options
    • Settings
  • 🤖API Docs
    • GeoPard API Overview
    • Getting Started
    • Authorization: ApiKey, Credentials or OAuth 2.0
    • Diagrams with Basic Flows
      • 1. Field Registration
      • 2. GraphQL Subscription
      • 3. Grep Satellite Imagery
      • 4. Upload Soil | AsApplied | Yield Datasets
      • 5. Execute Equations
      • 6. Generate ZonesMap
      • 7. Download Gridded Data
      • 8. Download Original Data
    • Data Schema
    • Requests Overview
      • 1. Subscription: Get Events
      • 2. Query: Get "Fields"
      • 3. Query: Get "SatelliteImages"
      • 4. Query: Get defined "SatelliteImage"
      • 5. Query: Get "RasterMaps"
      • 6. Query: Get "ZonesMaps"
      • 7. Mutation: Generate "ZonesMap"
      • 8. Mutation: Generate "RasterMap"
      • 9. Mutation: Generate "ZonesMap" asynchronously
      • 10. Mutation: Generate "RasterMap" asynchronously
      • 11. Mutation: Generate Yield based "ZonesMap" asynchronously
      • 12. Mutation: Generate Soil based "ZonesMap" asynchronously
      • 13. Mutation: Create "Farm"
      • 14. Mutation: Create a "Field" or edit the boundary of the existing field (with optional labels)
      • 15. Query: Get "TopographyMap"
      • 16. Query: Get "YieldDatasets"
      • 17. Query: Get "SoilDatasets"
      • 18. Mutation: Generate zip archive with "ZonesMap" and "Field"
      • 19. Mutation: Delete "Field"
      • 20. Mutation: Delete "Farm"
      • 21. Mutation: Delete "ZonesMap"
      • 22. Mutation: Delete "RasterAnalytisMap"
      • 23. Mutation: Delete "SoilDataset"
      • 24. Mutation: Delete "YieldDataset"
      • Notes (Pins)
        • 25. Mutation: Save "Note" attached to "Field"
        • 26. Mutation: Save "Note" attached to "ZonesMap"
        • 27. Mutation: Save "Note" attached to "SoilDataset"
        • 28. Mutation: Save multiple "Notes", Batch operation
        • 29. Mutation: Delete "Note"
        • 30. Mutation: Delete multiple "Notes"
        • 31. Query: Get all "Notes" related to "Field"
        • 32. Query: Get "Notes" related to "ZonesMap" and type
        • 33. Query: Get "Notes" related to "SoilDataset" and type
        • 34. Query: Get a selected "Note" with all "Comments"
        • 35. Mutation: Add "Comment" to the selected "Note"
        • 36. Mutation: Add multiple "Comments" to the selected "Notes"
      • 37. Query: Get "SatelliteImages" in the defined interval
      • 38. Query: Get "UserData"
      • 39. Mutation: Set custom color schemas to selected "GeoMaps"
      • 40. Query: Get "Labels" on the account level
      • 41. Mutation: Save "Labels" on the account level
      • 42. Mutation: Delete "Label" on the account level
      • 43. Query Get "Fields"
      • 44. Mutation: Set Field Labels
      • 45. Mutation: Save User Data
      • 46. Mutation: Generate multi-layer "ZonesMap" asynchronously
      • 47. Query: Get "ZonesMaps"
      • 48. Query: Get Gridded Data from "TopographyMap"
      • 49. Query: Get Gridded Data from "FieldSatelliteImage"
      • 50. Query: Get Gridded Data from "VectorAnalysisMap"
      • 51. Query: Get Gridded Data from "YieldDataset"
      • 52. Query: Get Gridded Data from "SoilDataset"
      • 53. Query: Get Gridded Data from "AsAppliedDataset"
      • 54. Query: Get Vector Data from "SoilDataset"
      • 55. Upload zip files (over 6 MB)
      • 56. Upload photos
      • 57. Query: Get "Photos" attached to the selected "Note"
      • 58. Query: Get "Photos" attached to "Comments"
      • 59. Query: Get "AsAppliedDatasets"
      • 60. Mutation: Generate As-Applied-based "ZonesMap" asynchronously
      • 61. Mutation: Delete "AsAppliedDataset"
      • 62. Mutation: Share Farms
      • 63. Mutation: Save Organization
      • 64. Mutation: Add Users to Organization
      • 65. Mutation: Delete Users from Organization
      • 66. Mutation: Save Field
      • 67. Mutation: Save Farm
      • 68. Mutation: Refresh "VectorAnalysisMap" Statistics
      • 69. Mutation: Delete "Photo"
      • 70. Mutation: Delete multiple "Photos"
      • 71. Mutation: Generate a zip archive with "Notes"
      • 72. Query: Get Gridded Data as GeoJSON or GeoTIFF
      • 73. Query: Get Gridded Data with the Selected Buffer
      • 74. Mutation: Verify "Equation"
      • 75. Mutation: Generate "EquationMap" asynchronously
      • 76. Query: Get "EquationMap"
      • 77. Mutation: Delete "EquationMap"
      • 78. Query: Find "Fields" by "externalKey"
      • 79. Query: Find "Farms" by "externalKey"
      • 80. Query: Get Original Data
      • 81. Query: Get GeoJSON of "EquationMap"
      • 82. Query: Restore Subscription Events
      • 83. Query: Collect Platform Context
      • 84. Mutation: Calibrate and Clean YieldDataset
      • 85. Mutation: Assign Rates to VectorAnalysisMap (ZonesMap)
      • 86. Query: Get "Farms"
      • 87. Mutation: Save Custom VectorAnalysisMap (ZonesMap)
      • 88. Mutation: Export ZonesMap as Zipped Shapefile
      • 89. Mutation: Export ZonesMap as Zipped ISOXML
    • Geo Endpoints
      • WMS - Get Raster Pictures of Spatial Data Layers
        • 1. LAI
        • 2. RGB
        • 3. Field: boundary
        • 4. Field: thumbnail
        • 5. ZonesMap
        • 6. ZonesMap: custom color schema
        • 7. ZonesMap: thumbnail
        • 8. RasterMap
        • 9. RasterMap: custom color schema
        • 10. RasterMap: thumbnail
        • 11. TopographyMap: elevation in absolute numbers
        • 12. YieldDatasetsMap
        • 13. SoilDatasetsMap
        • 14. SoilDatasetsMap: custom color schema
        • 15. AsAppliedDatasetsMap
        • 16. Satellite Image: cropped by Field boundary
        • 17. Satellite Image: cropped by Field boundary and custom color schema
        • 18. YieldDatasetsMap: custom color schema
        • 19. Satellite Image: 10 colors visualization
      • WFS - Get Spatial Data Layers in Vector format (shp, geojson)
        • 1. Get the Field Boundary as Geojson
        • 2. Get the Zones map as Geojson
        • 3. Get Zones Attributes as JSON
        • 4. Get Soil data as Geojson
        • 5. Get Yield data as Geojson
    • Uploading Files
    • API FAQ
  • 🛣️Platform Roadmap
    • Roadmap
  • GIS quick Hints
    • QGIS: Change String to Number values in the shapefile
    • QGIS: Yield Data Manipulations
    • QGIS: Split Boundaries Into Subfields
    • QGIS: Merge Vector Layers
    • QGIS: Merge Selected Features from Vector Files
    • QGIS: Calculate NDVI for the Drone Geotiff File
    • QGIS: Split Multi-field Shapefiles
    • QGIS: Convert CSV to SHP
    • QGIS: Reproject Shapefile
  • Policies
    • Your Data Stays Yours, Securely Managed By GeoPard
    • Terms & Conditions
    • Privacy Policy
Powered by GitBook

Start Working with GeoPard

  • Go to GeoPard Website
  • Demo Request
  • LinkedIn

This Portal Sections

  • Introduction
  • Product Tour - Web App (incl. video)
  • Product Tour - Mobile App (incl. video)
  • Precision Agronomy Use Cases

Powered by GeoPard Agriculture - Automated precisionAg platform

On this page
  • Data Preparation
  • Data Overview
  • Concept
  • Plan-based
  • Applied-based
  • Applied-based and Historical Productivity
  • Summary

Was this helpful?

  1. Agronomy

Field Trial Analytics

PreviousEvaluate Accuracy of Fertilizer ApplicationNextNitrogen Use Efficiency & Uptake

Last updated 4 months ago

Was this helpful?

Agronomists employ Trial Analytics to assess the performance of various crop varieties, cultivation techniques, and input applications, including the results of Variable Rate Applications in Precision Agriculture. By collecting, analyzing, and interpreting data generated from Field Trials, researchers gain insights into the interactions between genetics, environment, and management practices. This knowledge informs the development of crop management strategies that optimize yield potential while minimizing input usage. Furthermore, Trial Analytics not only enables the evaluation of the effectiveness of Precision Farming practices but also helps in identifying resilient crop varieties that can thrive under diverse and challenging conditions, thereby contributing to food security.

Data Preparation

For effective trial analytics, a few essential datasets are required:

  1. Yield Dataset: This dataset captures the yield data. We can import this from the or manually upload it as or as .

  2. Application Dataset: This is crucial for understanding the actual executed Application on the Field. At a minimum, it contains attributes like TargetRate, AppliedRate, and some machinery-related metrics. As with the Yield Dataset, we have options to import it from the or manually upload it as or as .

  3. Zones/Plots with Trials/Experiments: These show the planned Application rates for our Trials, giving insight into the experimental design. If such a data layer is available, we upload it as into the AsApplied/AsPlanted or Yield control. This ensures compatibility when building EquationMaps, streamlining your trial analytics experience. If such a data layer isn't available, the TargetRate attribute from the Application Dataset can serve as a substitute for Trial evaluations.

  4. Historical Field Potential Zones: These zones are generated by GeoPard (details are ). They are useful for analyzing Trials with consistent historical productivity. This is particularly beneficial when Trials are distributed across regions with varied historical productivity.

Once we've gathered these datasets, the next step is starting the Trial evaluation process.

Data Overview

There are the following data for the 2023 agricultural season of winter wheat:

  • Yield Dataset highlighting Wet Mass distribution (Fig.1)

  • Nitrogen (N34) VRA plan (150 kg/ha) with 2 Trial Plots (120kg/ha and 180 kg/ha)(Fig.2)

  • Application Dataset showcasing applied statistics (Fig.3)

  • Historical Field Productivity (Fig.4)

The YieldDataset, after calibration and cleaning, is displayed in Fig.5, along with the updated statistics. This dataset will be utilized in subsequent steps.

Concept

Here the objective of Trial Analytics is to ascertain the most effective Nitrogen (N34) rate for the field. There are the pinpointed areas with Nitrogen rates of 120kg/ha, 150kg/ha, and 180kg/ha. This data is derived from the ApplicationDataset on one hand and the calibrated YieldDataset on the other.

We're focusing our analysis on three distinct zones:

  • 120kg/ha (designated as the trial zone)

  • 150kg/ha (considered the main zone)

  • 180kg/ha (another trial zone)

Our approach will include the following evaluations:

  1. Plan-based: using the Planned Variable Rate Application (VRA) linked to the Calibrated Yield.

  2. Applied-based: Comparing the Actual Applied Datasets against the Calibrated Yield.

  3. Applied-based and Historical Productivity: Comparing the Actual Applied Datasets against the Calibrated Yield overlapped with Historical Field Potential Zones.

This methodical approach will allow for a comprehensive evaluation of Nitrogen's impact on Yield, based on both Planned and actual Applied application data.

Plan-based

The influence of applied planned Nitrogen (N34) on Yield distribution is visually captured in the subsequent screenshots (Fig.6, Fig.7, Fig.8). Here's a concise breakdown of the findings:

  • The main zone, with a Nitrogen rate of 150 kg/ha, spans 45.8 ha and averages a yield of 4.99 t/ha (Fig.6).

  • The first trial zone, utilizing a 180 kg/ha Nitrogen application, covers 1.76 ha, yielding an average of 6.5 t/ha (Fig.7).

  • The second trial zone, with 120 kg/ha of Nitrogen, encompasses 1.86 ha and produces an average yield of 6.39 t/ha (Fig.8).

Further down, you'll find an in-depth discussion of the formulas and configurations employed during the evaluation.

Here are the Equations to run to reproduce the calculations.

  1. Main with 150 kg/ha: Yield_Main = np.where(Zone==1, Yield_WetMass, np.nan)

  2. Trial with 120 kg/ha: Yield_Zone = np.where(Zone==3, Yield_WetMass, np.nan)

  3. Trial with 180 kg/ha: Yield_Zone = np.where(Zone==2, Yield_WetMass, np.nan)

It is important to activate Numpy (Fig.9) and turn off Interpolation (Fig.10).

Applied-based

A notable observation is that the actual Applied Rate during the Trial doesn't consistently align with the Planned (Target) Rate. Specifically, a distribution ranges from 120 kg/ha to as high as 189 kg/ha (Fig.11). Given this variability, it became crucial to set a benchmark for error tolerance. Thus, a ±5% accuracy was determined to be an acceptable threshold to deem the trial suitable for evaluation.

Presented in the subsequent screenshots (Fig.12, Fig.13, Fig.14) is the statistical distribution of the Yield, focusing on the Nitrogen (N34) actually Applied numbers. Here are the summarized statistics, keeping in mind the ±5% accuracy acceptance:

  • The main zone at 150 kg/ha had an applied area of 43.5 ha, yielding an average of 4.9 t/ha (Fig.12).

  • The first trial zone at 180 kg/ha covered an area of 1.47 ha and produced an average yield of 6.5 t/ha (Fig.13).

  • The second trial zone set at 120 kg/ha spanned an area of 1.44 ha, with an average yield of 6.3 t/ha (Fig.14).

For a deeper understanding of the methodology and the specifics of these results, the used Equations are below:

  1. Trial actual Applied Nitrogen: Applied_Trial = np.where((Zone == 3) | (Zone == 2), Applied_Value, np.nan)

  2. Main with 150 kg/ha incorporating 5% acceptance: Yield_Main = np.where((Zone == 1) & (Applied_Value >= 142.5) & (Applied_Value <= 157.5), Yield_WetMass, np.nan)

  3. Trial with 120 kg/ha incorporating 5% acceptance: Yield_Trial = np.where((Zone == 3) & (Applied_Value >= 114.0) & (Applied_Value <= 126.0), Yield_WetMass, np.nan)

  4. Trial with 180 kg/ha incorporating 5% acceptance: Yield_Trial = np.where((Zone == 2) & (Applied_Value >= 171.0) & (Applied_Value <= 189.0), Yield_WetMass, np.nan)

Applied-based and Historical Productivity

The Yield figures from the Trials consistently surpass the average Yield across the entire Field. A key factor driving this disparity appears to be the historically high productivity zone where the Trials took place, as visualized in Fig.15 and Fig.16. For a more nuanced evaluation of the Trials, it's crucial to factor in the productivity zones when analyzing results.

Presented in the subsequent screenshots (Fig.17, Fig.18, Fig.19) is the statistical distribution of the Yield, focusing on the Nitrogen (N34) actually Applied numbers overlapped with Historical Productivity Zones (created in GeoPard). Here are the summarized statistics, keeping in mind the ±5% accuracy acceptance for Applied numbers:

  • The main zone at 150 kg/ha had an applied area of 2.65 ha, yielding an average of 6.34 t/ha (Fig.17).

  • The first trial zone at 180 kg/ha covered an area of 1.08 ha and produced an average yield of 6.41 t/ha (Fig.18).

  • The second trial zone set at 120 kg/ha spanned an area of 1.78 ha, with an average yield of 6.33 t/ha (Fig.19).

For a deeper understanding of the methodology and the specifics of these results, the used Equations are below:

  1. Main with 150 kg/ha incorporating 5% acceptance overlapped with Historical Productivity: Yield_Main = np.where((Application_Zone == 1) & (Productivity_SubZone == 51) & (Applied_Value >= 142.5) & (Applied_Value <= 157.5), Yield_WetMass, np.nan)

  2. Trial with 120 kg/ha incorporating 5% acceptance overlapped with Historical Productivity: Yield_Trial = np.where((Application_Zone == 3) & (Productivity_SubZone == 51) & (Applied_Value >= 114.0) & (Applied_Value <= 126.0), Yield_WetMass, np.nan)

  3. Trial with 180 kg/ha incorporating 5% acceptance overlapped with Historical Productivity: Yield_Trial = np.where((Application_Zone == 2) & (Productivity_SubZone == 51) & (Applied_Value >= 171.0) & (Applied_Value <= 189.0), Yield_WetMass, np.nan)

where

  • the part Productivity_SubZone == 51 reflects the high Productivity Zones with the applied experiments,

  • the parts (Applied_Value >= 142.5) & (Applied_Value <= 157.5) , (Applied_Value >= 114.0) & (Applied_Value <= 126.0), (Applied_Value >= 171.0) & (Applied_Value <= 189.0) incorporate ±5% accuracy from the rates 150, 120, 180 kg/ha.

Summary

The Yield results from the Trials closely align with the average Yield observed across the high Historical Productivity Zone of the Field. In other words, the experimental application of N34 product at rates of 120 kg/ha - 150 kg/ha - 180 kg/ha, resulted in average Yields of 6.33 t/ha - 6.34 t/ha - 6.41 t/ha respectively, does not have a significant impact on the harvested Yield within the high Productivity Zone.

The YieldDataset hasn't been calibrated: multiple harvesters were operating there, there are turnaround and missing data traces, and noise is evident. It's recommended to apply the Yield Calibrate and Clean operations on top for optimal results. A step-by-step tutorial can be found at .

The results prompt a significant query: Why does the lower application rate seem to be more efficient than the higher one? To gain deeper insights, the next phase involves.

To delve deeper into the Equation approach and its execution, please consult our tutorials for both the and .

👨‍🌾
LINK
User Interface
API
evaluating the Trials using the actual Applied data
JohnDeere Operation Center
shapefile
machinery proprietary format
JohnDeere Operation Center
shapefile
machinery proprietary format
shapefile
HERE
Fig.1 Original YieldDataset
Fig.2 Nitrogen (N34) VRA plan with Trial Plots
Fig.3 Application Dataset
Fig.4 Historical Field Productivity
Fig.5 Calibrated and Cleaned YieldDataset
Fig.6 Main Zone with N34 150kg/ha
Fig.7 Trial Zone with N34 180kg/ha
Fig.8 Trial Zone with N34 120kg/ha
Fig.9 Activate "Numpy"
Fig.10 Turn off using of "Interpolated" data
Fig.11 Actual Applied Rates in Trials
Fig.12 Main Zone with N34 150kg/ha ±5%
Fig.13 Trial Zone with N34 180kg/ha ±5%
Fig.14 Trial Zone with N34 120kg/ha ±5%
Fig.15 Historical Field Potential Zones
Fig.16 Historical Field Potential Zones as YieldDataset
Fig.17 Main Zone with N34 150kg/ha overlapped with Historical Productivity
Fig.18 Trial Zone with N34 180kg/ha ±5% overlapped with Historical Productivity
Fig.19 Trial Zone with N34 120kg/ha ±5% overlapped with Historical Productivity