Next steps

[mpaget]

We need to touch on (if not complete) each of these by mid-Dec 2022 end of April 2023. Each of the below can have their own issues as appropriate

• Get tests working (Get the tests working to provide a baseline of expected behaviour #3)
  • Product
  • Juxtapose
• Update indexed DEA datasets, ga_ls_fc_3 (Update SQL dump. Tests pass #9)
• Output format from drills
  • Determine WPS params from Terria
    • point
    • polygon
  • What are the WPS responses for these scenarios?
    • point, polygon inside data area = valid data
    • polygon striding the data area = valid data
    • point, polygon outside of data area = no data
  • Is the WPS CSV compatible with Terria?
    • yes, with v7/v8 considerations, Test and document Terria<>WPS connections #14
• Drill code
  • Confirm handling of partial pixel selections
    • variable to include pixel centres only (default) or all pixels. Anything else would need to be custom (Polygon tool library #13)
  • Multipolygon
    • Not presently accepted. Available under the hood. Need to handle incoming feature object. (Polygon tool library #13)
  • Donuts - Custom handling of a multipolygon
• Documentation
  • More documentation #22
• Deploy
  • Deploy to EASI dev #17
  • Connect EASI WPS with Terria TerriaJS/RaPPMap#133
• Test in the (semi-)wild
  • Development cycle for datacube-wps code changes into dev/easi service
  • Adapt FC drill code for Landsat/S2 FC product in EASI CSIRO