add csv export to DEA WIT notebook

[BexDunn]

Proposed changes

Adds a csv export to the WIT notebook, explains the data in the export

Checklist

(Replace [ ] with [x] to check off)

• Notebook created using the DEA-notebooks template
• Remove any unused Python packages from Load packages
• Remove any unused/empty code cells
• Remove any guidance cells (e.g. General advice)
• Ensure that all code cells follow the PEP8 standard for code. The jupyterlab_code_formatter tool can be used to format code cells to a consistent style: select each code cell, then click Edit and then one of the Apply X Formatter options (YAPF or Black are recommended).
• Include relevant tags in the final notebook cell (refer to the DEA Tags Index, and re-use tags if possible)
• Clear all outputs, run notebook from start to finish, and save the notebook in the state where all cells have been sequentially evaluated
• Test notebook on both the NCI and DEA Sandbox (flag if not working as part of PR and ask for help to solve if needed)
• If applicable, update the Notebook currently compatible with the NCI|DEA Sandbox environment only line below the notebook title to reflect the environments the notebook is compatible with
• Check for any spelling mistakes using the DEA Sandbox's built-in spellchecker (double click on markdown cells then right-click on pink highlighted words). For example:

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[BexDunn]

I haven't managed to catch the previously updated knowledge hub links in this correctly, so have converted it to draft for now

[LaurenSchenk1]

Everything looks good to me :)

[benji-glitsos-ga]

Hi Bex,

It looks great. Some minor notes about the links:

• When linking to a KH product, you don't need to include the ?tab=overview part at the end. The link can just be: https://knowledge.dea.ga.gov.au/data/product/dea-coastlines/
• Instead of linking to the datahandling github file, you can link to the API documentation which also links to the source code: https://knowledge.dea.ga.gov.au/notebooks/Tools/gen/dea_tools.datahandling/

[robbibt]

Hey @BexDunn, this looks great to me. Two small suggestions:

1. Change the Explorer links from "https://explorer.sandbox.dea.ga.gov.au/products/..." to ""https://explorer.dea.ga.gov.au/products/..." (our public facing URLs are now "https://explorer.dea.ga.gov.au" for AWS and "https://explorer.nci.dea.ga.gov.au" for NCI)
2. For links to notebooks and Python code, I'd personally prefer for us continuing to use relative links wherever possible rather than an external link to Knowledge Hub - it means that users can quickly open up the code directly on the Sandbox, but should still work in the rendered notebooks on Github and Knowledge Hub. So, I'd potentially prefer the one on the left here to the one on the right:
   

(I think you can still link to specific notebook headers in the same way you have already, just keeping the relative part of the link at front)