Geo-Surface TerraZoner is a specialized web-based tool for creating management zones based on topographic wetness analysis. It uses high-resolution LiDAR elevation data to analyze terrain characteristics and generate actionable management zones for variable rate applications in precision agriculture.

Key Capabilities

• Automatic Wetness Analysis: Calculate Topographic Wetness Index (TWI) from LiDAR elevation data
• Intelligent Zone Classification: Four professional algorithms including Jenks Natural Breaks, Quantiles, Equal Interval, and Standard Deviation
• Smart Zone Refinement: Automated blob removal and boundary smoothing for cleaner, more contiguous zones
• Zone Statistics: Detailed area calculations and wetness range analysis for each zone
• Multiple Export Formats: Shapefile, GeoTIFF, KML, KMZ, GeoJSON, and PDF for compatibility with all major GIS platforms
• Prescription Creator: Generate FMIS-ready variable rate prescription shapefiles with up to 5 products per zone
• 3D Visualization: View zones draped on terrain in immersive 3D with Cesium.js

Who Should Use This Tool?

Geo-Surface TerraZoner is designed for:

• Agronomists creating variable rate seeding or fertilizer prescriptions
• Precision agriculture consultants analyzing field topography
• Farm managers optimizing input applications based on terrain
• Researchers studying relationships between topography and crop performance
• Anyone needing to classify fields into management zones based on wetness patterns

Geo-Surface TerraZoner follows a simple three-step workflow:

1Define Project Area

Upload a field boundary (KML, KMZ, or Shapefile) or draw your area of interest directly on the map.

2Get Elevation Data

Automatically fetch high-resolution LiDAR data from government servers (Canada or USA) or upload your own GeoTIFF elevation file.

3Generate Topographic Analysis

Process terrain using advanced terrain analysis to calculate a proprietary topographic wetness index - a measure based on topographic position and wetness potential that predicts where water tends to accumulate.

Once analysis is complete, zones are automatically created and you can refine them using various parameters, adjust individual zone boundaries, and export in multiple formats for use in your Farm Management Information System (FMIS).

The Geo-Surface TerraZoner interface consists of three main areas:

1. Left Sidebar (Workflow Tabs)

The collapsible left sidebar contains three workflow tabs:

• Setup Tab: Three-step workflow for project initialization (Define Area → Get Elevation → Generate Analysis)
• Zones Tab: Zone classification controls, parameters, statistics, and preview
• Tools Tab: Export options and prescription creator

2. Map View (Center)

Interactive map displaying:

• Base layer (satellite imagery, street map, or terrain)
• Field boundary (uploaded or drawn)
• HD Elevation layer (colorized LiDAR)
• Wetness Index overlay (blue gradient)
• Management zones (traffic light color scheme)
• Reference layers (land parcels, if available)

3. Toolbar & Controls

Top-right toolbar provides:

• Layer Control: Toggle visibility and adjust opacity of all layers
• Measurement Tools: Measure distances and areas
• Search: Find locations by address or coordinates
• Geolocation: Center map on your current location
• Full Screen: Expand map to full window
• View in 3D: Launch Cesium 3D viewer (after zones created)

The workflow is organized into tabs that guide you through the zone creation process:

Setup Tab (Green Cards)

Three numbered steps presented as expandable cards with status indicators. Each step must be completed before proceeding to the next. Cards show checkmarks when complete.

Zones Tab (Teal Cards)

Automatically enabled after Setup is complete. Contains three cards:

• Zone Classification: Algorithm selection and parameter controls
• Zone Statistics: Per-zone area, percentage, and wetness range (appears after zone creation)
• Zone Preview: Visibility and clearing controls

Tools Tab

Export and utility functions:

• Export Zones: Seven format options (Shapefile, GeoTIFF, KML, KMZ, GeoJSON, PDF, and download raw elevation)
• Prescription Creator: Generate variable rate prescriptions with product-specific rates per zone

Follow this workflow to create and export management zones:

1Define Project Area (Setup Tab)

• Click the upload area or "Upload Boundary or AOI" button
• Select a KML, KMZ, or Shapefile (ZIP) in WGS84 coordinates
• OR click "Draw Boundary or AOI" and draw directly on the map
• Boundary appears on map with green status indicator

2Get Elevation Data (Setup Tab)

• Click "Auto-Fetch LiDAR" (recommended) to download government data automatically
• OR click "Upload Custom GeoTIFF" if you have your own elevation file
• Wait for HD Elevation layer to appear (colorized terrain)
• Typical resolution: 1-2 meter pixels

3Generate Topo Analysis (Setup Tab)

• Click "Generate Topo Index" button
• Server processes terrain (30-60 seconds depending on field size)
• Progress dialog shows real-time status
• Wetness Index layer loads automatically when complete
• Zones Tab becomes enabled

4Create Zones (Zones Tab - Automatic)

• Switch to Zones Tab (automatic after step 3)
• Zones are created automatically with default settings (3 zones, Jenks method)
• Zone layer appears with traffic light colors (red=dry, blue=wet)
• Zone Statistics card shows area and wetness for each zone

5Refine Zones (Optional)

• Change Method: Select Jenks, Quantiles, Equal Interval, or Std Deviation
• Adjust Zone Count: Drag slider (2-10 zones)
• Set Minimum Size: Remove small blobs (0.1-10 acres threshold)
• Smooth Boundaries: Adjust iterations (2-10) for aesthetic smoothing
• Fine-Tune Breaks: Drag sliders in Zone Statistics to manually adjust boundaries
• All changes auto-refresh after 1 second (debounced)

6Export Zones (Tools Tab)

• Switch to Tools Tab
• Choose export format:
  • Shapefile: For GIS software and most FMIS (dissolved polygons)
  • GeoTIFF: Raster format for advanced GIS analysis
  • KML/KMZ: For Google Earth or Ditch Assist
  • GeoJSON: For web mapping and custom applications
• File downloads immediately

7Create Prescription (Optional - Tools Tab)

• Click "Create Prescription" button
• Enter field name (max 20 characters)
• Select number of products (1-5)
• Name each product (e.g., "Seed", "Nitrogen", "K2O")
• Enter application rate for each zone for each product
• Click "Export Prescription Shapefile"
• Shapefile downloads with product rate columns ready for FMIS import

There are two ways to define your project area:

Method 1: Upload Boundary File

Click the upload area in Setup Tab → Step 1 to browse for a boundary file.

Supported File Formats:

• KML: Keyhole Markup Language (Google Earth format)
• KMZ: Compressed KML (ZIP)
• Shapefile: ZIP file containing .shp, .shx, .dbf, and .prj files

Coordinate System Requirements:

• Files must be in WGS84 (EPSG:4326) coordinate system
• This is standard for KML/KMZ and most exported shapefiles
• If your shapefile is in a projected system, reproject to WGS84 in QGIS or ArcGIS before uploading

Method 2: Draw Boundary on Map

Click "Draw Boundary or AOI" button to activate the drawing tool.

• Click on the map to add points around your field perimeter
• Double-click the last point to complete the polygon
• Boundary is saved automatically
• Drawing tool deactivates after completion

Drawing Tips:

• Zoom in for more accurate placement
• Click along field edges at each corner or direction change
• You can draw simple rectangles or complex polygons
• The boundary doesn't need to be perfect - it defines the analysis area

Accurate elevation data is critical for wetness analysis. You have two options:

Option 1: Auto-Fetch LiDAR (Recommended)

Click "Auto-Fetch LiDAR" button to automatically download high-resolution LiDAR elevation data from government servers.

How It Works:

• System detects boundary extent and location
• Fetches LiDAR tiles from provincial (Canada) or USGS 3DEP (USA) servers
• Merges multiple tiles into single seamless elevation raster
• Reprojects data to EPSG:3857 (Web Mercator) for map display
• HD Elevation layer appears on map with hillshade colorization

Data Specifications:

• Resolution: Typically 1-2 meter pixels (very high detail)
• Accuracy: Vertical accuracy usually 10-30 cm (0.3-1 foot)
• Coverage: Available across Canada and USA (coverage varies by region)
• Source: Government LiDAR programs (open data)

Option 2: Upload Custom GeoTIFF

Click "Upload Custom GeoTIFF" if you have your own elevation data.

File Requirements:

• Format: GeoTIFF (.tif or .tiff)
• Coordinate System: EPSG:3857 (Web Mercator) required
• Bands: Single-band raster (elevation values)
• Data Type: Float32 or Int16
• NoData: Must have NoData value defined (typically -9999)

When to Use Custom Upload:

• Auto-fetch is unavailable in your region
• You have higher resolution data from UAV/drone surveys
• You have RTK GPS elevation data processed to a DEM
• You want to use a specific elevation dataset

The region switcher (below Step 3) allows you to select your data source region:

Available Regions:

• Canada (🇨🇦): Uses provincial LiDAR servers (varies by province)
• USA (🇺🇸): Uses USGS 3DEP national LiDAR dataset

Click "Generate Topo Index" in Setup Tab → Step 3 to calculate an advanced topographic wetness index from your elevation data.

What Happens During Processing

Your elevation data is sent to a specialized terrain analysis server. The server applies proprietary algorithms that analyze topographic position and wetness potential to create a comprehensive wetness index optimized for precision agriculture zone management.

The analysis includes:

• Terrain analysis: Evaluates topographic characteristics including slope, position, and drainage patterns
• Wetness calculation: Applies advanced algorithms to identify areas with high wetness potential based on multiple terrain factors
• Normalization: Scales values to a 0-100 range specific to your field for consistent classification
• Depression identification: Finds closed depressions and areas that trap water
• Ponding prediction: Maps areas with ponding potential

Processing Time

Processing typically takes 30-60 seconds depending on:

• Field size (larger fields take longer)
• DEM resolution (higher resolution = more pixels to process)
• Server load (concurrent users)
• Network speed (uploading DEM to server)

Progress Dialog

A full-screen dialog appears showing:

• Current processing stage
• Real-time status updates
• "Processing terrain analysis..." message
• Spinning progress indicator

Results

When processing completes:

• Wetness Index layer loads automatically (blue gradient overlay)
• Wetness data stored globally for zone classification
• Zones Tab becomes enabled
• Automatic zone creation begins with default settings
• Optional visualization layers (flow, depressions, ponding) available for display

Geo-Surface TerraZoner offers four professional classification methods. Select your method from the dropdown in Zones Tab → Zone Classification card.

1. Jenks Natural Breaks (Default - Recommended)

Best for: Most agricultural applications where you want natural groupings in wetness patterns

How It Works:

Jenks (also called Fisher-Jenks) is an optimization algorithm that:

• Minimizes variance within each zone (zones are internally similar)
• Maximizes variance between zones (zones are distinct from each other)
• Uses dynamic programming to find optimal break points

Technical Details:

• Algorithm: Fisher-Jenks optimization with O(n²k) complexity
• Performance: Stratified sampling (25,000 pixels max) for large rasters
• Result: Zones represent natural clusters in wetness distribution

When to Use:

• Default choice for most fields
• When wetness values have natural groupings or clusters
• When you want statistically optimal zone boundaries
• When zones need to be clearly differentiated

2. Equal Count (Quantiles)

Best for: Creating zones with equal acreage for balanced equipment application

How It Works:

Quantile classification divides pixels into groups with equal counts:

• Sorts all wetness values from lowest to highest
• Divides into N groups with equal number of pixels
• Each zone has approximately the same area (acres)

When to Use:

• You want each zone to cover roughly the same acreage
• Equipment operators prefer equal-sized zones for time planning
• Wetness values are evenly distributed (no extreme outliers)

Trade-offs:

• Pro: Balanced zone sizes for operations
• Con: May combine distinct wetness classes if distribution is uneven
• Con: Break values may not align with natural boundaries

3. Equal Interval

Best for: Simple, evenly-spaced wetness ranges that are easy to explain

How It Works:

Divides the wetness range into equal-width intervals:

• Finds minimum and maximum wetness values in field
• Divides range into N equal intervals
• Each zone spans the same wetness range (e.g., 0-20, 20-40, 40-60, etc.)

When to Use:

• You want simple, round-number breakpoints (e.g., every 10 points)
• Wetness values are evenly distributed across the range
• You need easy-to-communicate zone definitions

Trade-offs:

• Pro: Simple, intuitive zone definitions
• Pro: Consistent interval spacing
• Con: May create empty zones if data is clustered
• Con: Ignores natural groupings in data

4. Standard Deviation

Best for: Highlighting extreme wet/dry areas relative to field average

How It Works:

Creates zones at standard deviation intervals from the mean:

• Calculates mean and standard deviation of wetness values
• Creates breaks at mean ± 0.5 std, ± 1.0 std, ± 1.5 std, etc.
• Zones are distributed symmetrically around average

Statistical Interpretation:

• Zone 1: Significantly drier than average (> 1 std below mean)
• Middle zones: Near average wetness
• Last zone: Significantly wetter than average (> 1 std above mean)

When to Use:

• You want to identify statistical outliers (extreme wet/dry)
• Most of field is moderate with some problem areas
• You want zones defined relative to field average

Trade-offs:

• Pro: Identifies areas needing special management
• Pro: Statistical basis for zone definitions
• Con: May not work well if data is not normally distributed
• Con: Can create very small extreme zones

All parameter changes trigger automatic reclassification after a 1-second delay (debounced). This means:

• Change classification method → zones update automatically
• Drag number of zones slider → zones update automatically
• Adjust minimum size or smoothing → zones update automatically
• Drag break adjustment sliders → zones update automatically

Processing Indication

During reclassification, you'll see:

• Full-screen loading overlay
• "Classifying Zones..." message
• Spinning progress indicator
• Typical processing time: 5-15 seconds

Concurrent Prevention

The system prevents multiple simultaneous classifications. If you make changes during processing, they will queue and execute after current operation completes.

The Zone Classification card (Zones Tab) provides five key parameters for controlling zone creation:

1. Classification Method

• Control: Dropdown menu
• Options: Jenks, Equal Count, Equal Interval, Standard Deviation
• Default: Jenks Natural Breaks
• Effect: Changes algorithm used to determine zone boundaries
• See: Classification Methods section for detailed comparison

2. Number of Zones

• Control: Slider
• Range: 2-10 zones
• Default: 3 zones
• Step: 1 (integer values)
• Visual: Slider fills with green gradient as value increases
• Display: Current value shown next to slider

Choosing Number of Zones:

• 2-3 zones: Simple wet/dry or wet/moderate/dry classification. Good for basic variable rate applications.
• 4-5 zones: Recommended for most fields. Balances detail with manageability.
• 6-8 zones: High detail for complex fields or multi-product prescriptions.
• 9-10 zones: Maximum detail but may create very small zones or operational complexity.

3. Minimum Zone Size

• Control: Slider
• Range: 0.1 - 10.0 acres
• Default: 0.5 acres
• Step: 0.1 acres
• Purpose: Remove small isolated patches ("blobs")

How Blob Removal Works:

1. After initial classification, system identifies all connected components (blobs) for each zone
2. Calculates area of each blob in acres using boundary geometry
3. Any blob smaller than threshold is merged into surrounding zone
4. Merging analyzes neighbors to find best fit (closest wetness value)
5. Process runs 3 passes to catch cascading small blobs

Effect of Different Thresholds:

• 0.1-0.3 acres: Removes only tiny slivers and artifacts. Zones may still be fragmented.
• 0.5-1.0 acres: Good balance - removes small patches while preserving real features.
• 2.0-5.0 acres: Aggressive cleanup. Only large, significant zones remain.
• 5.0-10.0 acres: Very aggressive. Useful for large fields where equipment can't manage small zones.

4. Boundary Smoothing

• Control: Slider
• Range: 2-10 iterations
• Default: 5 iterations
• Step: 1 iteration
• Algorithm: Morphological mode filtering
• Can be disabled: Set to 0 for no smoothing (not visible on slider but can be achieved by other means)

How Smoothing Works:

1. After blob removal, smoothing algorithm examines each pixel
2. Looks at surrounding pixels in a window (3x3 initially)
3. Replaces pixel with most common zone in neighborhood (mode filter)
4. Window size grows with iterations: 3x3 → 5x5 → 7x7...
5. More iterations = progressively smoother boundaries

Effect of Smoothing Iterations:

• 2-3 iterations: Minor smoothing. Removes jagged pixels but preserves detail.
• 4-6 iterations: Moderate smoothing. Creates aesthetically pleasing, operational boundaries.
• 7-10 iterations: Heavy smoothing. Very clean boundaries but may over-generalize zone shapes.

5. Zone Transparency

• Control: Slider (appears after zones created)
• Range: 0-100%
• Default: 50%
• Step: 5%
• Effect: Adjusts opacity of zone layer overlay
• Real-time: Changes apply instantly (no reclassification)

Transparency Use Cases:

• 0-25%: Mostly transparent - see underlying terrain/wetness
• 50%: Balanced view - see both zones and underlying data
• 75-100%: Opaque zones - focus on zone boundaries only

Understanding the order in which parameters are applied helps optimize your zone creation:

Zone Processing Pipeline

1. Load wetness data - Retrieve TWI raster and boundary
2. Normalize values - Scale to 0-100 for field
3. Sample data - Stratified sampling for Jenks (performance)
4. Calculate breaks - Run selected classification algorithm
5. Classify raster - Assign zone ID to each pixel
6. Spatial smoothing (pre-blob) - 3 passes of majority filter
7. Blob removal - 3 passes using minimum size threshold
8. Boundary smoothing - N iterations of mode filter
9. Final cleanup - One more blob removal pass
10. Calculate statistics - Area, percentage, ranges per zone
11. Render visualization - Paint colored raster overlay

Key Insights

• Blob removal happens BEFORE boundary smoothing (smoothing operates on already-cleaned zones)
• Multiple smoothing passes create cascading effect (each pass smooths results of previous)
• Final blob removal catches any artifacts created during smoothing
• Spatial smoothing (pre-blob) reduces classification noise before blob analysis

After zones are created, the Zone Statistics card appears showing detailed metrics for each zone.

Information Displayed

For each zone, you'll see:

• Zone Number: Sequential numbering from driest (1) to wettest (last)
• Color Indicator: Traffic light color scheme matching map visualization
• Area (Acres): Calculated from boundary geometry using geodesic area calculation
• Percentage: Proportion of total field area
• Wetness Range: Minimum and maximum wetness values (0-100 scale) in that zone

Zone Ordering

Zones are always ordered from driest to wettest:

• Zone 1 (top) - Driest areas, labeled "Driest Areas" with sun icon
• Middle zones - Moderate wetness
• Last zone (bottom) - Wettest areas, labeled "Wettest Areas" with droplet icon

Color Scheme

Zone colors follow a traffic light pattern:

• Zone 1 (driest): Red
• Middle zones: Yellow → Green gradient
• Last zone (wettest): Blue

Exact colors vary based on number of zones (2-10) with smooth gradients for higher zone counts.

Each zone card (except the last) includes a slider for manually adjusting the upper boundary of that zone.

How Manual Breaks Work

• Each slider controls the maximum wetness value for that zone
• Slider range is constrained between adjacent zone boundaries
• Dragging slider left decreases zone upper limit (zone shrinks)
• Dragging slider right increases zone upper limit (zone grows)
• Changes to one zone automatically affect adjacent zones

Use Cases for Manual Breaks

• Fine-tuning automated results: Tweak boundaries to match your field knowledge
• Aligning with known features: Adjust to include/exclude specific wet spots
• Matching historical zones: Replicate previous year's zones
• Custom thresholds: Use agronomist recommendations or research-based values

Visual Feedback

• Slider fill shows current position with green gradient
• Real-time value display shows exact wetness threshold
• Status message changes to "Custom zone breaks applied" (purple icon)

Auto-Refresh

Adjusting breaks triggers automatic reclassification after 1-second delay. The reclassification:

• Uses custom break values instead of algorithm-calculated breaks
• Applies same spatial smoothing and blob removal
• Updates map visualization and statistics
• Preserves your custom breaks (stored in window.zoneClassification.customBreaks)

Management zones are visualized as a colored raster overlay on the map.

Rendering Technology

• Canvas Rendering: Zones painted to HTML5 canvas for performance
• OpenLayers ImageStatic: Canvas exported as static image layer
• Georeferencing: Aligned to EPSG:3857 (Web Mercator) extent
• Transparency: NoData pixels fully transparent, zones at configured opacity

Visual Effects

• Fade-in Animation: Zones fade from 0% to 50% opacity over 5 seconds when first created
• Edge Masking: Edge pixels always NoData to prevent border artifacts
• Layer Order: z-index 950 (above wetness/elevation, below UI controls)

Automatic Layer Management

When zones are displayed, the system automatically:

• Hides HD Elevation layer (to reduce visual clutter)
• Hides Land Parcels layer (if visible)
• Keeps Wetness Index visible but at lower opacity
• You can manually toggle these back on via Layer Control if desired

The Zone Preview card (Zones Tab) provides two simple controls:

Toggle Zones Visibility

• Button: Eye icon button
• Function: Show/hide zone layer on map
• State Preservation: Zones remain in memory, just visibility toggled
• Use Case: Compare with/without zones to verify accuracy

Clear Zones

• Button: Eraser icon button
• Function: Completely remove zones from map and reset interface
• Effect: Zone layer removed, statistics hidden, status reset
• Warning: Permanent action with no undo (must recreate zones)
• Use Case: Start over with different parameters from scratch

Access the Layers Popover via the toolbar (top-right) to control all map layers.

Available Layers

• HD Elevation: Colorized LiDAR elevation data
• Wetness Index: TWI raster (blue gradient)
• Management Zones: Classified zones (traffic light colors)
• Boundary: Field boundary polygon
• Land Parcels: Cadastral boundaries (if available for region)

Layer Controls Per Layer

• Visibility Toggle: Checkbox to show/hide
• Opacity Slider: Adjust transparency (0-100%)
• Z-Index: Change stacking order (which layers appear on top)
• Remove: Delete layer from map

Recommended Layer Stack for Zones

For best visualization when working with zones:

• Base: Satellite imagery at 100%
• Wetness: 30-40% opacity (subtle background reference)
• Zones: 50-70% opacity (visible but not overpowering)
• Boundary: 100% (clear field outline)
• HD Elevation: Off (turn on temporarily to verify terrain)

The Zone Merger allows you to manually combine two or more zones into a single zone. This is useful when:

• Adjacent zones have similar wetness values and can be managed identically
• You want to simplify a complex zone map for easier field operations
• Small zones need to be combined with neighbors for equipment limitations
• You want custom zones based on field knowledge rather than algorithm output

How to Merge Zones

Follow these steps to merge zones in the Zones Tab → Zone Statistics card:

Step 1: Enter Merge Mode

• Click the "Merge Zones" button at the top of the Zone Statistics card
• Button changes to "Cancel Merge" and highlights green
• Checkboxes appear next to each zone in the statistics list

Step 2: Select Zones to Merge

• Check the boxes for 2 or more zones you want to combine
• Selected zones show checked boxes
• Must select at least 2 zones to proceed
• Can select non-adjacent zones (they will all become one zone)

Step 3: Confirm Merge

• When 2+ zones selected, "Merge Selected Zones" button appears
• Button shows count (e.g., "Merge 3 Selected Zones")
• Click button to proceed
• Confirmation dialog shows which zones will be merged and preview of result
• Click "Confirm Merge" or "Cancel"

Step 4: Review Results

• Selected zones are merged into a single zone
• Zone is assigned the ID of the lowest selected zone (e.g., merging zones 2, 4, 5 creates new "Zone 2")
• Remaining zones are automatically reindexed to remove gaps
• Total zone count decreases
• Map visualization updates immediately with new zone boundaries
• Zone statistics recalculated (total area, wetness range combined)
• Colors automatically reassigned to all zones

Undo Merge

Immediately after merging, an "Undo" option is available:

• Green success banner appears at top of screen
• Banner shows number of zones merged and total count
• "Undo" button available for 10 seconds
• Click "Undo" to restore previous zone configuration
• After 10 seconds, banner auto-dismisses and undo is no longer available

Exit Merge Mode

To exit merge mode without performing a merge:

• Click "Cancel Merge" button (was "Merge Zones" before entering mode)
• Checkboxes disappear
• Any selections are cleared
• Returns to normal view mode

Scenario 1: Simplifying a Complex Zone Map

Problem: Algorithm created 8 zones but field equipment can only handle 4-5 distinct application rates.

Solution:

1. Review zone statistics to identify zones with similar wetness ranges
2. Merge zones with overlapping or adjacent wetness values
3. Example: Merge zones 1+2 (driest), merge zones 7+8 (wettest), keep middle zones separate
4. Result: Reduced from 8 to 6 zones with clearer differentiation

Scenario 2: Combining Small Scattered Zones

Problem: Zone 4 exists as several small patches scattered across the field, too fragmented for practical management.

Solution:

1. First try increasing "Min Zone Size" parameter and reclassifying
2. If fragments persist, merge Zone 4 with the most similar adjacent zone (Zone 3 or 5)
3. Alternatively, merge all similar scattered zones into one management unit

Scenario 3: Creating Custom Management Units

Problem: You know from experience that certain areas of the field should be managed together, even if algorithm separated them.

Solution:

1. Create initial zones using algorithm (establishes base wetness patterns)
2. Use Zone Merger to combine zones based on your field knowledge
3. Example: The northeast corner and southwest drainage both need extra nitrogen, even if they're different zones - merge them

Geo-Surface TerraZoner supports multiple export formats for maximum compatibility with GIS and Farm Management Information Systems. All formats are accessible from the Tools Tab → Export Zones card.

1. Shapefile (.zip)

Best for: GIS software and Farm Management Information Systems (FMIS)

File Contents:

Downloads as ZIP containing:

• .shp - Geometry (MultiPolygon features)
• .shx - Spatial index
• .dbf - Attribute table
• .prj - Projection (WGS84 EPSG:4326)

Attributes:

• zone - Zone number (integer: 1, 2, 3...)
• zone_name - Zone name (string: "Zone 1", "Zone 2"...)

Geometry Type:

MultiPolygon - All polygons for each zone dissolved into single feature. This means:

• One feature per zone (not dozens of individual polygons)
• Discontinuous zones represented as multi-part geometries
• Cleaner attribute table (N zones = N features)

Processing Steps:

1. Convert classified raster to 2D array
2. Polygonize using marching squares algorithm
3. Dissolve all polygons by zone ID
4. Create MultiPolygon features
5. Generate shapefile components with shp-write.js
6. Compress to ZIP with JSZip

Filename:

zones_dissolved.zip

Compatible With:

• QGIS, ArcGIS, Global Mapper
• John Deere Operations Center
• Climate FieldView
• CNH Advanced Farming Systems
• AGCO Fuse
• Trimble Ag Software
• Most other FMIS platforms

2. GeoTIFF (.tif)

Best for: GIS raster analysis, remote sensing software, further processing

Specifications:

• Format: GeoTIFF raster
• Coordinate System: EPSG:3857 (Web Mercator)
• Data Type: Int16 (signed 16-bit integer)
• Pixel Values: 1, 2, 3... (zone IDs, 1-indexed)
• NoData Value: -9999 (outside zones)

Metadata Included:

• ModelPixelScale (resolution in meters)
• ModelTiepoint (georeferencing anchor)
• GeoKeyDirectory (projection parameters)
• GDAL_NODATA tag

Filename:

zones.tif

Compatible With:

• QGIS, ArcGIS, ERDAS
• GDAL/OGR tools
• Python (rasterio, GDAL)
• R (terra, raster packages)

3. KMZ (.kmz) - Image Overlay

Best for: Google Earth visualization, field scouting, sharing with collaborators, loading in soil sampling equipment

Recommended for Google Earth: This is the primary Google Earth export format. Unlike traditional KML vector files, this exports zones as a georeferenced image overlay (GroundOverlay) which provides better performance and accurate color representation in Google Earth.

Specifications:

• Format: KMZ (compressed KML with PNG image)
• Type: GroundOverlay (raster image, not vector)
• Coordinate System: WGS84 (EPSG:4326)
• Georeferencing: LatLonBox defines image extent
• Colors: Original zone colors preserved exactly
• File Size: Compressed for efficient download

Filename:

zones.kmz

Compatible With:

• Google Earth (desktop and web)
• Google Maps (with import)
• Ditch Assist
• Many mobile scouting and farming apps
• Some soil sampling equipment controllers

4. GeoJSON (.geojson)

Best for: Web mapping, custom applications, modern GIS workflows

Specifications:

• Format: GeoJSON FeatureCollection (JSON)
• Coordinate System: WGS84 (EPSG:4326)
• Geometry: MultiPolygon features (dissolved by zone)

Structure:

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": {
        "zone": 1,
        "zone_name": "Zone 1"
      },
      "geometry": {
        "type": "MultiPolygon",
        "coordinates": [[[...]]]
      }
    }
  ]
}
                

Filename:

zones.geojson

Compatible With:

• QGIS, ArcGIS Pro
• Leaflet.js, Mapbox GL JS, OpenLayers
• Python (geopandas, shapely)
• JavaScript mapping libraries
• PostGIS, MongoDB (spatial databases)

5. Download LiDAR

Best for: Backing up elevation data, external terrain analysis, archiving

What It Does:

• Exports the currently loaded LiDAR elevation data
• Same data used for wetness analysis
• Useful for archiving or processing in other software

Specifications:

• Format: GeoTIFF
• Coordinate System: EPSG:3857 (Web Mercator)
• Data Type: Float32 (elevation values in meters)

6. PDF Export

Best for: Printable zone maps, field records, sharing with agronomists

What It Does:

• Generates a printable PDF map of your zones
• Includes zone legend with colors, labels, and acreages
• Professional format for documentation and collaboration
• Great for keeping paper records or sharing via email

Contents:

• Map View: Current map visualization with zones displayed
• Zone Legend: All zones with color swatches, zone names, and acres
• Title: "Geo-Surface TerraZoner - Topographic Zone Management Map"
• Date: Export date for record-keeping
• Data Source: "Topographic Wetness Analysis"

Specifications:

• Format: PDF (Portable Document Format)
• Page Size: Letter (11" x 8.5")
• Orientation: Landscape
• Resolution: Matches current map canvas resolution
• Filename: TerraZoner_Map_YYYY-MM-DD.pdf

Use Cases:

• Field Reference: Print and bring to field for zone verification
• Documentation: Attach to agronomic reports or soil test results
• Collaboration: Email to consultants, agronomists, or farm managers
• Recordkeeping: Archive zone plans for future seasons

Polygonization Algorithm

Vector exports (Shapefile, KML, KMZ, GeoJSON) use a marching squares algorithm to convert raster zones to polygon boundaries:

1. Raster to Array: Classified zone raster converted to 2D array
2. Boundary Tracing: Marching squares identifies edges between zones
3. Polygon Construction: Traced boundaries converted to coordinate sequences
4. Dissolve: All polygons with same zone ID merged into MultiPolygon
5. Simplification: Optional coordinate reduction (not currently implemented)
6. Format Conversion: Geometries written to target format

Coordinate System Transformations

Zoner handles projections automatically:

• Internal Processing: EPSG:3857 (Web Mercator for map display)
• Vector Exports: Reprojected to WGS84 (EPSG:4326) for compatibility
• GeoTIFF Export: Remains in EPSG:3857 (GIS can reproject as needed)

The Prescription Creator converts management zones into actionable variable rate application maps with product-specific rates for each zone.

Opening Prescription Creator

• Navigate to Tools Tab → Prescription Creator card
• Click "Create Prescription" button (enabled after zones created)
• Modal popup dialog appears with prescription configuration form

Prescription Configuration Form

The popup is organized into four sections:

Section 1: Field Name

• Input: Text field
• Max Length: 20 characters
• Required: Yes
• Sanitization: Spaces → underscores, special characters removed, truncated to 20 chars
• Example: "North_Field_2025"
• Purpose: Identifies prescription in FMIS, used in filename

Section 2: Product Count

• Control: Five buttons (1, 2, 3, 4, 5)
• Default: 1 product
• Selection: Click button to select number of products
• Effect: Shows/hides product configuration cards dynamically

Section 3: Product Configuration

For each product selected, a configuration card appears with:

Product Name

• Text input, max 10 characters
• Required for each product
• Sanitized (no spaces/special chars)
• Examples: "Seed", "Nitrogen", "K2O", "P2O5", "Lime"
• Becomes column name in output shapefile

Application Rates by Zone

• Grid of numeric inputs (one per zone)
• Each input labeled with zone number ("Zone 1", "Zone 2"...)
• Step: 0.01 (two decimal precision)
• Minimum: 0 (non-negative values only)
• Placeholder: "0.00"
• Required: At least one rate per product

Section 4: Export Button

• "Export Prescription Shapefile" button at bottom
• Validates all inputs before processing
• Shows error alert if validation fails

Output Format

• Format: Shapefile (ZIP containing .shp, .shx, .dbf, .prj)
• Filename: [FieldName]-rx.zip (e.g., "North_Field_2025-rx.zip")
• Coordinate System: WGS84 (EPSG:4326)
• Geometry: MultiPolygon (zones dissolved)

Attribute Table Structure

The shapefile contains these columns:

• zone - Zone number (integer: 1, 2, 3...)
• zone_name - Zone name (string: "Zone_1", "Zone_2"..., note underscore)
• [ProductName] - One column per product with application rate (float, 2 decimals)

Example Attribute Table

Three-product prescription with 3 zones:

zone	zone_name	Seed	Nitrogen	K2O
1	Zone_1	32500.00	120.00	45.00
2	Zone_2	34000.00	140.00	50.00
3	Zone_3	35500.00	160.00	55.00

Processing Steps

1. Validate all form inputs (field name, product names, rates)
2. Sanitize field and product names
3. Polygonize zones (same as shapefile export)
4. Dissolve by zone ID (one feature per zone)
5. Create attribute table with zone info + product rate columns
6. Generate shapefile using shp-write.js
7. Download as ZIP

Rate Determination

How to decide application rates for each zone:

• Agronomic Recommendations: Base rates on soil test results, yield goals, and crop requirements
• Historical Yield Data: Use yield maps from previous years to correlate with wetness patterns
• Wetness-Based Logic: Common patterns:
  • Seeding: Lower in wet zones (prevent stand issues), higher in dry zones
  • Nitrogen: Variable - wet zones may need more (leaching) or less (denitrification)
  • Lime/Gypsum: Often higher in wet zones (drainage improvement)
• Consult Agronomist: Professional recommendations trump automated zoning

Product Naming

• Use simple, recognizable names ("Seed", "N", "P", "K")
• Match your FMIS product library if possible
• Avoid special characters and spaces
• Max 10 characters (shapefile DBF limitation)

Field Naming

• Use descriptive names that identify field and year
• Examples: "North40_2025", "HomeField_VR", "Section12_Spring"
• Helps organize prescriptions when managing multiple fields

Validation Before Export

Before exporting prescription, verify:

• Zone boundaries match your expectations (check map visualization)
• Application rates are reasonable (no typos - 3500 vs 35000 seeds!)
• Product names are correct (will map to FMIS products)
• All zones have rates entered (no blank cells)

The Project Backup feature allows you to save your entire Zoner session to a file and restore it later. This is essential for:

• Continuing work on a project across multiple sessions
• Sharing complete zone analysis with colleagues or clients
• Archiving field analyses for future reference
• Creating backups before making major changes
• Working on multiple fields simultaneously (save one, load another)

What Gets Saved in a Backup?

The backup ZIP file contains everything needed to recreate your exact session:

• Field Boundary: Original uploaded or drawn boundary geometry
• Elevation Data (DEM): Complete LiDAR raster (clipped to boundary)
• Wetness/TWI Layer: Processed topographic wetness index raster
• Zone Classification: Current classified zones with all parameters
• Zone Settings: Classification method, number of zones, blob size, smoothing iterations
• Custom Breaks: Manual break adjustments (if any)
• Metadata: Project name, timestamp, version info

Creating a Backup

To save your current project:

1. Navigate to Tools Tab → Project Backup card
2. Click "Backup Project" button
3. System packages all project data into a ZIP file
4. File downloads automatically (typically 5-50 MB depending on field size)
5. Default filename: zoner-project-[timestamp].zip

Backup Requirements

To create a backup, you must have at minimum:

• Field boundary uploaded or drawn
• Elevation data loaded (DEM layer)

Wetness and zones are optional - you can backup intermediate states.

File Size Expectations

• Small field (50 acres): 3-10 MB
• Medium field (200 acres): 10-30 MB
• Large field (500+ acres): 30-100 MB

Size depends on elevation resolution and boundary complexity.

How to Restore

To load a previously saved project:

1. Navigate to Tools Tab → Project Backup card
2. Click "Restore Project" button
3. File picker opens - select your backup ZIP file
4. System validates and extracts all project data
5. Boundary, elevation, wetness, and zones load automatically
6. Map view zooms to restored boundary extent
7. All tabs and controls update to reflect restored state

What Happens During Restore

The restore process recreates your exact session:

• Step 1: Boundary geometry loaded and displayed on map
• Step 2: HD Elevation layer appears (colorized DEM)
• Step 3: Wetness Index layer loads (if saved in backup)
• Step 4: Zones layer displays with original colors (if saved)
• Step 5: Zone statistics populate in Zones Tab
• Step 6: All sliders and controls set to saved values

Restore Validation

The system validates backup files before restoring:

• Checks for required files (boundary.json, dem.tif, metadata.json)
• Verifies file formats and data integrity
• Validates coordinate systems match
• Shows error message if backup is corrupted or incompatible

When to Create Backups

• Before major changes: Save before experimenting with drastically different parameters
• After successful classification: Save when you've achieved good zones you might want to reference
• End of session: Always save before closing browser if you plan to continue later
• Before exporting: Backup ensures you can regenerate exports if needed
• Multiple scenarios: Create backups of different classification approaches for comparison

File Organization

• Rename backup files with descriptive names: NorthField_5zones_jenks.zip
• Store by field: Create a folder per field with multiple backup iterations
• Date stamps: Include year in filename for multi-year analysis
• Archive after export: Keep backup after exporting zones (you might need to regenerate)

Backup Limitations

• Browser-only: Backups don't sync across devices (save to cloud storage for access elsewhere)
• No version control: Each backup is independent (no automatic versioning)
• One project at a time: Restoring replaces current session (save current work first if needed)
• File size: Very large fields (1000+ acres) may create large backup files

Collaborative Workflow

Project backups enable team collaboration:

Scenario: Agronomist Reviews Consultant's Zones

1. Consultant creates zones using Jenks with 5 zones
2. Saves project backup: SmithFarm_zones_draft.zip
3. Emails backup file to agronomist client
4. Agronomist restores project in their browser
5. Reviews zones, adjusts parameters, merges zones based on field knowledge
6. Creates new backup with their modifications: SmithFarm_zones_final.zip
7. Returns final backup to consultant for prescription creation

Advantages of Backup Sharing

• Full context shared (not just final zones)
• Recipient can see methodology (classification method, parameters used)
• Easy to modify and regenerate
• No data loss in translation (exact raster data preserved)
• Standard ZIP format (email-friendly)

The 3D Terrain Viewer provides immersive visualization of your field with zones draped on the terrain surface.

Accessing 3D Viewer

• Button Location: Floating button in bottom-right of map (globe icon)
• Label: "View in 3D"
• Availability: Enabled after zones are created
• Interface: Full-screen modal popup

3D Viewer Technology

• Engine: Cesium.js (industry-standard WebGL globe)
• Rendering: GPU-accelerated terrain mesh
• Terrain Data: Your LiDAR elevation data converted to terrain tiles
• Zone Overlay: Classified zones rendered as textured overlay on terrain surface
• Lazy Loading: Cesium library loaded on-demand (not loaded until 3D clicked)

The 3D viewer interface includes several controls for customizing the view:

Vertical Exaggeration Slider

• Range: 1x - 10x
• Default: 3x
• Purpose: Amplifies terrain relief for better visibility
• Use Case: Flat fields benefit from 5-10x exaggeration
• Effect: Higher values make slopes and depressions more dramatic

Zone Visibility Toggle

• Control: Checkbox
• Function: Show/hide zones in 3D
• Use Case: Toggle off to see bare terrain relief

Wireframe Mode Toggle

• Control: Checkbox
• Function: Show terrain mesh as wireframe
• Use Case: Visualize terrain triangulation and mesh structure
• Technical: Helps understand terrain resolution and quality

Reset View Button

• Function: Return camera to default position
• Use Case: If you get disoriented, reset to overhead view

Close Button

• Function: Exit 3D viewer and return to 2D map
• Location: Top-right corner (X icon)

Cesium uses standard 3D navigation controls:

Mouse Controls

• Left-click drag: Rotate view around target point
• Right-click drag: Pan camera (move laterally)
• Scroll wheel: Zoom in/out
• Middle-click drag: Tilt camera (change pitch/angle)

Keyboard Shortcuts

• Arrow keys: Pan camera
• + / -: Zoom in/out
• W / S: Tilt camera up/down

Touch Controls (Mobile/Tablet)

• One finger drag: Rotate view
• Two finger drag: Pan
• Pinch: Zoom in/out
• Two finger twist: Rotate view

Navigation Tips

• Orient yourself: Find north arrow or use landmarks
• Oblique angles: Tilt camera 30-45° for best relief visualization
• Multiple perspectives: Rotate 360° to see all slope aspects
• Zoom levels: Zoom out for field context, zoom in for zone detail

When to Use 3D Viewer

• Client Presentations: Impressive visual for stakeholders
• Terrain Understanding: Better sense of slope and relief than 2D
• Zone Validation: Verify zones align with visible terrain features
• Drainage Flow Visualization: See how water would flow across surface
• Communication: Easier for non-technical audiences to understand

Limitations

• Not suitable for precise measurements (use 2D map)
• Can't export 3D view directly (screenshot or screen recording)
• Performance dependent on hardware (may be slow on older devices)
• Requires internet connection (Cesium assets loaded from CDN)