SnapPlus Help Version 19

What's new in version 19

What's new in version 19

This is the first topic Next topic  

What's new in version 19

This is the first topic Next topic  

What’s New in SnapPlus 19 / Release Notes

Important Note for SnapPlus 19.0 Users: Do This First

Because of an issue with how SnapPlus 19.0 handled wells within 300 feet of fields, incorrect guidance messages may appear. To correct this, go to Tools | Farm Settings and select Clear All Field Restrictions. To restore the proper restrictions, perform an upload to and download from SnapMaps. For WPDES-permitted farms (CAFOs) with W or R soils, this will also require resetting the "Acknowledge use of proper techniques..." and "Depth to bedrock has been measured..." checkboxes for that field. To check those boxes for all fields in a farm at once, go to Tools | Farm Settings and select the appropriate "Acknowledge..." entry.

Important Note for All SnapPlus Users: Upload and Download

When you open an existing farm with a any new version of SnapPlus, your first step should be to upload the farm to SnapMaps, download it, and import from SnapMaps Fields and SnapMaps Restrictions. This updates soils, restrictions, and spreadable acres.

New SnapPlus Desktop Features

Automatically fills out most of the 590 Checklist for you

Substantial speed improvements

Copy Years feature streamlined and extended

CAFOs can import and export actual yields

CAFOs have a new Liquid Waste Storage calculator

More options for Nutrient Systems

More pre-built templates for Daily Log and Records import

CAFOs can indicate pre-tillage for liquid manure applications on fields with less than 20 ft to Silurian bedrock.

New SnapMaps Features

Annotations can be placed anywhere on your map

Improved PDFs, up to 3 user-selected map images per page and "smart legend" showing only items on your map

Updated soils data and other new layers

New winter-only option for manure-prohibited areas

Change in default MRTN price ratio for corn

To be consistent with current prices, SnapPlus default MRTN price ratio for corn is now 0.10. This will not change the N rates that trigger excess N flags. If needed, you can change the default MRTN for multiple fields and years using the Rotation Wizard.

If you need to run both 19 and an earlier version on the same machine, see How to Run Two Versions of SnapPlus on One Computer.

To skip the release notes and get help with using SnapPlus right away, see 12 Steps to Developing a Plan Using SnapPlus.

How-to videos are at; for support, see Contact Information.

New double crops:

Oat-Pea Forage to Sorghum-sudan forage

Pea, field to Sorghum forage

Winter triticale to soybean

Crops with new cover crops

Beets table to small grain cover crop

Corn grain, aerial seeded rye cover

Lima bean to small grain cover crop

Sorghum-sudan forage to small grain cover crop

Winter wheat (grain) to small grain cover crop

Winter wheat (grain+straw) to small grain cover crop

Annual cover crop, spring-planted, not harvested

Added tillages:

No-till, green plant: This is for planting directly into a growing cover crop that is terminated later. Corn, grain; Corn silage, Corn silage to small grain cover, Soybeans 15-20 inch row

Alfalfa/Brome Seeding Fall: Fall vertical till

Alfalfa/Brome Seeding Spring, Oat-Pea Forage w/ Alfalfa Seeding Spring, Oat-Pea Forage w/ Alfalfa/Brome Seeding Spring, Oat-Pea Forage w/ Alfalfa/Grass Seeding Spring, Oat-Pea Forage w/ Red Clover Seeding Spring, Oatlage w/ Alfalfa/Brome Seeding Spring: Fall vertical till and Spring vertical till

Beets table and Beets table to small grain cover crop: Fall chisel, disk; Fall chisel, no disk; Spring chisel, disk; Spring chisel, no disk; Spring field cultivation.

Lima bean: Spring vertical till

Oat-Pea Forage: Spring vertical till

Oat-Pea Forage to Direct Seeded Legume Forage: Vertical till

Sorghum-sudan forage: Fall chisel, no disk; Spring chisel, no disk, and Spring vertical tillage.

Sweet Corn early plant (before May 20), Sweet Corn middle plant (May 20 - June 10), Sweet Corn late plant (June10 or Later): Fall vertical till, Spring vertical till, Strip till.

Sweet Corn early plant (before May 20) with small grain cover crop; Sweet Corn middle plant (May 20 - June 10) with small grain cover crop; Sweet Corn late plant (June10 or Later) with small grain cover crop: Fall chisel, no disk; Fall vertical till; Spring vertical till

Winter Rye (forage) to Sorghum-sudangrass: 1st crop No-till:  2nd crop vertical till

NOTE: For all no-till overwintering and annual small grain cover crops, changed seeding operation in RUSLE2 from “Drill or airseeder, double disk” to “Drill or air seeder single disk openers 7-10 in spac.”. This will lower the STIR value of seeding from 6 to 2.

Notes on cover crops

There is no way to make a non-broadcast interseeded cover crop in RUSLE2, so for drilled inter-seeded cover crops, use the aerial seeded version.

For cover crops that are broadcast following harvest, use the no-till seeding.

For winter killed cover crops and cover-crop mixes, use the annual cover crop choices.

There are now two crop choices for growing season covers:

Annual cover crop, spring-planted, not harvested,

Small grain cover crop, not harvested

For spring-planted crops following over-wintering cover crops, any tillage prior to seeding the new crop kills the cover crop in RUSLE2. For no-till and strip-till crops without a tillage operation prior to planting, the cover crop is killed by a spray operation 5 days prior to seeding. Note that this will cause soil loss to be slightly underestimated if the cover crop is killed more than five days prior to planting. For the no-till green plantings, the spray operation for killing the cover crop is put immediately before seeding the new crop in RUSLE2.

Issues Fixed in 19.1

If "Automatically open last farm" setting was on, double-clicking a SnapPlus farm database opened the wrong farm

Setting yield goals in Rotation Editor caused various errors

NM5 report was missing the crop year and some tables

The FM8 report included inactive fields when calculating fertilizer totals

Shallow Silurian label was incorrectly displaying orange even after import

Some conduits to groundwater within 300 feet of a field were incorrectly triggering guidance messages even when they were further than 50 feet away (or, for permitted farms, further than 100 feet away)

Program was not correctly identifying when there is fall tillage in checking for winter practice b

The Fertilizer application rate entry column in the Nutrient Application Planner has a whole field fertilizer data entry box that gave “out of range” errors for reasonable application rates.  In addition, on some computers the whole field fertilizer data entry box filled the whole column, making it appear like fertilizer applications could only be entered as a whole-field rate.

Reports would not display the selected preparer.  This is fixed, but only the preparer’s or consultant’s “Organization” displays on reports (not their name). If planners want their name to show, they should add it to the “Organization” line (e.g. “Joe Smith, Madison Crop Consulting”).

Winter Triticale (forage) To Soybeans crops did not have tillages

Issues Fixed in 19.2

Performance: 19.2 should be noticeably faster than 19.1 for several common operations

Manure and fertilizer applications entered into the Rotation Editor reverted to default values for season, method or rate

Field screen display unstable, particularly when editing field acres

Cropping screen and cropping grid very slow when entering or changing cropping data

SnapMaps field boundaries could be lost when using groups

Changes made in the Nutrient Application Planner or Rotation Wizard were not displayed on the Cropping Grid

Some compliance and guidance messages for applications of manure with less than 4% dry matter on soils with fall N restrictions were missing

SnapPlus would hang when deleting crop years

Sulfur-containing nitrogen fertilizers were not allowed (up to 36 lb N) on soils with fall N restrictions

Applications from a Daily Log or Records were not displaying in the Nutrient Application Planner

Importing a Daily Log spreadsheet changed the application method from Inject to Surface

Import Manure Analysis was not importing

Uploading to SnapMaps changed ditches to grassed waterways

Issues Fixed in 19.3

Added Milk as a land-applied nutrient source.

An error that caused application rate and other edits in the nutrient application planner to revert to previous values.

Partial field applications imported from the daily log getting erroneous over-application compliance messages.

Fall manure applications on N restricted soils were not getting correct compliance and guidance messages, including not flagging for fall applications of manure with DM <4% manure when incorporated/injected and no nitrification inhibitor.

Fall N fertilizer applications were not flagging properly on fields with Municipal wells or < 5ft to bedrock.

Deleting a single year on the cropping screen appeared to delete the wrong year.

Downloading and importing spreadable acres  was showing differences (highlighted orange) when the differences were only 1 tenth of an acre or less.

The checks for conservation practices in a SWQMA were not working properly.

Tile inlets did not upload and download correctly from SnapMaps.

The application planner manure application rate calculator could not handle the amount applied with liquid manure applications on larger fields.

The drop-down menu for adding new fertilizer sources was confusing.

Manure application nutrients not showing on the cropping screen in the “This year’s manure”.

Subfarms: First one created would not be saved. If all fields were assigned to subfarms, selecting default "---" item in dropdown displayed no fields and "Show all fields" as the name of the subfarm.

Incorrect orange highlighting on CAFO farm in Cropping screen (compliance messages correct)

P Management Strategy in Bulk Reports: "Both" and "PI" selections were switched.

Orange highlighting on Cropping screen for CAFO farm fields with 100-200 soil test P and manure applications when there was not a compliance problem.



The What's New for version 18 is here.

The What's New for version 17 is here.