Add Intro to Fuel Moisture Content notebook to DEA Notebooks

[biancafichera]

Proposed changes

The DEA Fuel Moisture Content product and Knowledge Hub page is currently live, so it's time for us to also officially upload the Introduction to DEA Fuel Moisture Content notebook.
This notebook was originally reviewed by many in a draft pull request, but we created a new branch for the file name convention changes so this is a new pull request and comes from a different branch. All suggestions in the draft pull request have been changed here and this is the most up to date file.

Checklist

If this is a notebook, then have you:

• Checked the structure of the notebook follows our DEA-notebooks template
• Removed any unused Python packages from Load packages
• Removed any unused/empty code cells
• Removed any guidance cells (e.g. General advice)
• Ensured 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).
• Included relevant tags in the final notebook cell (refer to the DEA Tags Index, and re-use tags if possible)
• Tested notebook on the DEA Sandbox
• Cleared all outputs, run notebook from start to finish, and save the notebook in the state where all cells have been sequentially evaluated
• If applicable, update the Notebook currently compatible with 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

[review-notebook-app]

View / edit / reply to this conversation on ReviewNB

GL-S commented on 2025-10-10T05:50:49Z
----------------------------------------------------------------

Something strange is happening in the x axis: the first tick label is "2021" rather than "Jan". Happy to help and have a look on why this is happening this Monday morning!

[cbur24]

Looks great @biancafichera! I made a few minor edits to the markdown text, and a few comments below that you could consider addressing.

• Recommend using a DEA Maps link that has FMC pre-loaded.
• When run on the unstable sandbox (ODC-1.9) the list_products cell produces many ugly warnings In odc-geo GridSpec, resolution is expected in (X, Y) order, or simply X if using square pixels with inverted Y axis. Not sure if you can resolve this as I think its a broader issue but I thought it was worth noting. Maybe you should remove the list_products and just keep list_measurements since there is only one product anyway?
• Consider reducing the size of the area so it loads a little quicker - kinda slow with loading an entrire year of S2. I tried adding a progress bar to dc.load but it doesnt seem to work on odc-1.9.

[GL-S]

About the last figure, as Chad mentioned it is not a bug, but an expected behaviour.
If you prefer a more consistent look of the x axis, you could do something like this:

fig, ax = plt.subplots(figsize=(12, 4))

monthly_mean.plot(ax=ax)
ax.set(
    xlabel=None,
    ylabel="FMC (%)",
    title="Average monthly FMC in \n Wiarborough Nature Reserve and Surrounds for 2021",
)

x_ticks = pd.to_datetime(monthly_mean.time.values)
ax.set_xticks(x_ticks)
ax.set_xticklabels(x_ticks.strftime("%b %Y"), rotation=40)

ax.grid(alpha=0.5);

And it would look like the following: