SAES-422 Multistate Research Activity Accomplishments Report

Status: Approved

Basic Information

Participants

Daniel Kaiser, University of Minnesota, representative (Chair) Antonio Mallarino, Iowa State University, representative M Rasel Parvej, University of Missouri, representative John Jones, University of Illinois Urbana-Champaign, representative (Incoming Chair) Andrew Stammer, University of Wisconsin-Madison, representative Matthew Ruark, University of Wisconsin-Madison Dorivar Ruiz Diaz, Kansas State University, representative Sunjeong Park, Ohio State University, representative Manbir Rakkar, (virtual) Ohio State University Brady Goetle, (virtual) North Dakota State University Sylvie Brouder (virtual) Purdue, representative Javed Iqbal, (virtual) University of Nebraska-Lincoln, representative Not represented: Michigan State University South Dakota State University

Accomplishments

Impacts

  1. The Fertilizer Response Support Tool (soiltestFRST.org) went live in 2024. There currently are data from all the participating NCERA013 states in the response database. Iowa leads the database with 580 total trials, Ohio with 522 trials, Missouri with 139, Nebraska with 68, Minnesota with 38, Indiana with 30, North Dakota with 25, South Dakota with 21, Michigan with 14, Illinois with 8, and Kansas with 5 for a total of 1450 for the region. The tool was just launched and there is no way to look at the impact that the NCERA013 data has compared to other states and regions.
  2. At least an additional 6 field trials of data were added from the region from researchers on the committee. The USDA-CIG project aims to further increase additional data into the first database targeting around 80 new sites over the next three years.
  3. Our annual workshop drew 30 in attendance where we covered several topics on current soil test methods that have been topics of questiosn and discussions by soil testing labs

Publications

NCR 223 Publication [Online] https://extension.missouri.edu/publications/sb1001

Kaiser, D. E., Fabrizzi, K. P, Sims, A. L., Rosen, C.J., Vetsch, J. A., Strock, J.S., & Lamb, J. A. (2025). Phosphorus management strategies for corn and soybean in the Upper US Midwest. Agronomy Journal, 117, e70054. https://doi.org/10.1002/agj2.70054Recommended Chemical Soil Test Procedures for the North Central Region.

Rakkar, M., Jones, Miller, P., & Engel, R.  2024. Lime Management to Increase Soil pH in Semi‐Arid Regions of the US. crops & Soils 57 (1), 38-41." This is from Western US, not sure if it would be relevant.

Barker, D., Chiavegato, M., Essman, A., Fulton, J., Haden, V., LaBarge, G., Lentz, E., Lindsey, A., Lindsey, L., Lopez-Nicora, H., Michel, A., Noel, J., Ortez, O., Paul, P., Rakkar, M., Sulc, M., Tilmon, K., Wilson, A., & Witter, J. (2024). Ohio Agronomy Guide, 16th Edition . Bulletin ANR 472HO. The Ohio State University. https://extensionpubs.osu.edu/ohio-agronomy-guide-16th-edition/

Rakkar, M.K., A. Douridas, and G. LaBarge. 2024. Nutrient management in tight margins. Private Pesticide Applicator Proceedings.

Rakkar, M.K. and LaBarge, G. 2024. Response of soils and crops to gypsum application in Ohio. Ohioline. https://ohioline.osu.edu/factsheet/anr-0153.

Rakkar, M.K., LaBarge, G., Lindsay, A. and Karhoff, S. 2024 Look Out for Nitrogen Loss Due to Heavy Rains. C.O.R.N Newsletter. https://agcrops.osu.edu/newsletter/corn-newsletter/2024-09/look-out-nitrogen-loss-due-heavy-rains

Rakkar, M.K. and G. LaBarge. 2024. Crop Response to Phosphorus Fertilizer in Ohio. C.O.R.N. newsletter. https://agcrops.osu.edu/newsletter/corn-newsletter/2024-03/crop-response-phosphorus-fertilizer-ohio

Rakkar, M.K. and G. LaBarge, 2024. Soil Phosphorus and Crop Response to Phosphorus Fertilizer in Ohio. Ohioline. (https://ohioline.osu.edu/factsheet/anr-0146)

Rakkar, M.K. and G. LaBarge, 2024. Potassium Uptake and Ohio Crop Response. Ohioline. (https://ohioline.osu.edu/factsheet/anr-0147)

 

 

 

Log Out ?

Are you sure you want to log out?

Press No if you want to continue work. Press Yes to logout current user.

Report a Bug
Report a Bug

Describe your bug clearly, including the steps you used to create it.