Moisture at different depths
See where the soil is wetting and drying. Compare the depths your probes measure instead of treating the whole root zone as one number.
Introducing ATLAS
Farm intelligence for broadacre cropping, orchards, vineyards and irrigated farms. Bring soil readings, paddock history and weather together, with plant-stress monitoring being developed for trees and vines.
Soil monitoring in the current build.
Plant sensing on the roadmap.
Inside Atlas today
The current development build gives you a place to review the soil profile, compare trends and find readings that need a closer look. Measurements depend on the sensors installed.
See where the soil is wetting and drying. Compare the depths your probes measure instead of treating the whole root zone as one number.
Follow temperature changes at each sensor location and read them alongside moisture and seasonal conditions.
Review electrical conductivity with moisture and temperature. EC can flag changes worth investigating; it is not a direct nutrient analysis.
Keep paddocks, orchard blocks, probes and mapped assets together, so each reading has a location your team recognises.
Review forecast and rainfall information from separate weather sources when interpreting the field data.
Check configured thresholds, battery readings, last report times and readings that need attention.
John Deere Operations Center™
Your farm layout shouldn’t need entering twice. Atlas’s API connection is designed to bring your existing farms, fields and available boundaries across from John Deere Operations Center, with your permission.
Start with the paddocks you already know. Add soil probes and field observations to that map, rather than redraw the operation before you can get started.
Discuss your existing setupThe connection we’re building
Authorise access to the Operations Center organisations and records you want to use with Atlas.
Reuse farm names, fields and available boundaries. Keep the paddock layout your team already works with.
Place your monitoring points on the map and review soil readings in the right paddock or block.
Data available to Atlas depends on enabled APIs, your account permissions and completed integration testing. Additional field-operation and equipment data will be assessed as the connection develops.
Atlas is independently developed by Integrated Ag Systems. John Deere and Operations Center are trademarks of Deere & Company; no endorsement is implied. John Deere API information.
Orchards & vineyards · next-stage monitoring
We’re working towards a combination of soil probes, trunk sensors and sap-flow measurements. Read alongside weather and crop stage, these signals can help build a clearer picture of water stress and irrigation timing.
Moisture, temperature and EC at selected depths show how the soil profile changes through wetting and drying cycles.
In the current Atlas buildDendrometers measure small changes in trunk size. Sap-flow sensors track water movement through the plant. Together they can add evidence of developing water stress.
Sensor evaluation & integration plannedCombine plant and soil signals with weather, growth stage and agronomic advice to develop more useful irrigation guidance.
Decision support under developmentThe goal
We want Atlas to help answer two practical questions: can this block safely wait, and what changed after the last irrigation? Where a grower is applying more water than the crop needs, better timing could reduce water use and pumping costs.
There is no single stress threshold for every crop. Soil, variety, rootstock, weather and growth stage all matter. We’ll validate the interpretation in the field before presenting it as irrigation guidance.
Plant sensors measure physical responses; water stress is inferred from the pattern and its context. Agriculture Victoria researchers and NSW DPIRD describe how trunk measurements and sap flow can support irrigation scheduling. That is the basis for this development direction, not evidence of a measured Atlas water-saving result.
The history matters
Compare moisture, temperature and EC over time, whether the water came from rainfall or irrigation. Review the trends with your agronomist and check them against what you see in the paddock.
A practical development path
Atlas is being developed in stages, so growers can see what the system does now and where it is heading. Additional capabilities need suitable hardware, integration and field testing.
Mapped blocks, moisture by depth, soil temperature, EC, weather context, history and configured alerts.
Evaluate trunk and sap-flow sensors, plus flow, pressure and water-level monitoring where it adds value.
Develop crop-specific recommendations and, later, controlled automation with manual override and appropriate safeguards.
The sequence may change with field results. Automatic pump or valve control is not part of the current Atlas offering.
Hardware & field trials
Sensor positions, depth, power and connectivity all affect what the system can tell you. We start with the crop and the question, then work through a suitable setup.
LoRaWAN and cellular connections are both part of the approach. Compatibility is confirmed for the selected device and data connection before deployment.
We’re interested in practical input on sensor placement, crop thresholds and how to turn the readings into useful field decisions.
Before you start
No. Atlas is being developed for broadacre cropping and irrigated farms as well as orchards and vineyards. Soil monitoring, mapped paddocks and weather context support a range of crops. Planned tree and vine sensors are an additional option, not a requirement for broadacre use.
The John Deere Operations Center connection is designed to reuse farms, fields and available boundaries you have already mapped. You authorise the connection; the records available depend on your account permissions and the APIs enabled for Atlas. Sensor placement and any missing boundaries still need to be set up. The integration is in development, so talk to us about your account before planning a rollout.
Not in its current form. The present build is for monitoring and review. Irrigation recommendations and automatic control are development goals that need crop-specific validation, compatible control hardware and safety checks.
Possibly. We’ll need the sensor model, communication method and access to its data. A documented LoRaWAN payload, API or other usable interface lets us assess the integration before you commit.
There is no fixed percentage we can honestly promise for Atlas yet. Savings depend on existing irrigation practice, weather, soil, crop and management. A useful trial would compare metered water use and crop results, with seasonal differences accounted for.
Not directly. They measure conditions at the probe. The planned tree-stress work adds trunk and sap-flow measurements, interpreted alongside soil, weather and crop information.
Broadacre, horticulture & agronomy
Tell us what you grow, which systems you already use and which field decision you want to improve. We’ll talk through whether an Atlas trial makes sense.