National Irrigation Database

1. National Irrigation Database A national irrigation database would contain data about... How much water is required, and when How much water was applied, and when How much excess water was used ...for every field in Australia

2. National Irrigation Database • A great deal of detailed data is required. • Some data is already being collected, if only it was available... • How do we get the rest of the data ? Irrigators do the collecting Google Maps could be the inspiration

3. Existing data • Water orders to Water Supply Authority • Irrigation schedules calculated by irrigators • Soil moisture measurements If this data was also on the web it could be used by a national database

4. Google maps and Google Earth • Defined an xml schema for GIS data. • A data format that can be shared. • Data in a file in this format can be shown on a map or aerial photograph. • Water orders can also be read from the same file. • A National Irrigation Database can read the same file.

5. Irrigator sends water order to Water Supply Authority What happens now

6. Irrigator enters order on web form Orders via the web

7. What the Water Supply Authority would see • Paul Torzillo requires 55 Ml on 13 February • McWilliams requires 32 Ml on 12 February

8. What the National Database will see

9. What the irrigator would see

10. Irrigators who do not need to order water

11. What the irrigator and Water Authority would see

12. Web form could also calculate water requirements

13. Irrigators who measure soil moisture

14. What the irrigator and Water Authority would see

15. Soil moisture by telemetry to Water Authority

16. What the irrigator and Water Authority would see

17. Using Google xml schema • A standard format is required • The suggested format is the xml schema used by Google Maps and Google Earth • This schema defines how data should be formatted for GIS mapping • XML is extremely flexible • Standard interchange format for data on the internet

18. Additional data • XML is flexible - add extra data items • Volume_Required, Date_Required • Crop_Type, Daily_Water_Use • Soil_Moisture_Status • Total amount of water required by the end of the season

19. How the system would work

20. What is required - XML schema • Required_Volume (cu m) • Required_Date • Current_Soil_Moisture (mm) • Crop_Daily_Water_Use (mm/day) • Season Total_Volume_Required (cu m) • Crop_Type • GPS coordinates

21. What needs to be done 1 Web form for Irrigators to order water. Can also be used to calculate and post irrigation schedule. 2 Crop water use data to be available on the web in an agreed standard format. 3 Water Supply Authorities to be able to read and accept water orders in the agreed xml schema. 4 All irrigation scheduling software to output a schedule in the agreed xml schema. 5 A national irrigation database could then be set up that would also read the xml files.

22. National Irrigation Database really quite simple and achievable

23. Just calculations next...

24. Calculating water required: drip

25. Calculating water required: flood

26. Calculating water required