# Modelling intertidal elevation using tidal data¶

## Background¶

Intertidal environments support important ecological habitats (e.g. sandy beaches and shores, tidal flats and rocky shores and reefs), and provide many valuable benefits such as storm surge protection, carbon storage and natural resources for recreational and commercial use. However, intertidal zones are faced with increasing threats from coastal erosion, land reclamation (e.g. port construction), and sea level rise. Accurate elevation data describing the height and shape of the coastline is needed to help predict when and where these threats will have the greatest impact. However, this data is expensive and challenging to map across the entire intertidal zone of a continent the size of Australia.

### Digital Earth Australia use case¶

The rise and fall of the tide can be used to reveal the three-dimensional shape of the coastline by mapping the boundary betweeen water and land across a range of known tides (e.g. from low tide to high tide). Assuming that the land-water boundary is a line of constant height relative to mean sea level (MSL), elevations can be modelled for the area of coastline located between the lowest and highest observed tide.

Imagery from satellites such as the NASA/USGS Landsat program is available for free for the entire planet, making satellite imagery a powerful and cost-effective tool for modelling the 3D shape and structure of the intertidal zone at regional or national scale. Recently, Geoscience Australia combined 30 years of Landsat data from the Digital Earth Australia archive with tidal modelling to produce the first 3D model of Australia’s entire coastline: the National Intertidal Digital Elevation Model or NIDEM (for more information, see Bishop-Taylor et al. 2019 or access the dataset here).

## Description¶

In this example, we demonstrate a simplified version of the NIDEM method that combines data from the Landsat 5, 7 and 8 satellites with tidal modelling, image compositing and spatial interpolation techniques. We first map the boundary between land and water from low to high tide, and use this information to generate smooth, continuous 3D elevation maps of the intertidal zone. The resulting data may assist in mapping the habitats of threatened coastal species, identifying areas of coastal erosion, planning for extreme events such as storm surges and flooding, and improving models of how sea level rise will affect the Australian coastline. This worked example takes users through the code required to:

1. Load in a cloud-free Landsat time series

2. Compute a water index (NDWI)

3. Tag and sort satellite images by tide height

4. Create “summary” or composite images that show the distribution of land and water at discrete intervals of the tidal range (e.g. at low tide, high tide)

5. Extract and visualise the topography of the intertidal zone as depth contours

6. Interpolate depth contours into a smooth, continuous Digital Elevation Model (DEM) of the intertidal zone

## Getting started¶

To run this analysis, run all the cells in the notebook, starting with the “Load packages” cell.

After finishing the analysis, return to the “Analysis parameters” cell, modify some values (e.g. choose a different location or time period to analyse) and re-run the analysis. There are additional instructions on modifying the notebook at the end.

Load key Python packages and supporting functions for the analysis.

[1]:

%matplotlib inline

import datacube
import sys
import xarray as xr
import pandas as pd
import numpy as np
import matplotlib.pyplot as plt
from datacube.helpers import write_geotiff

sys.path.append('../Scripts')
from dea_datahandling import mostcommon_crs
from dea_bandindices import calculate_indices
from dea_coastaltools import tidal_tag
from dea_spatialtools import subpixel_contours
from dea_spatialtools import interpolate_2d
from dea_spatialtools import contours_to_arrays
from dea_plotting import display_map
from dea_plotting import map_shapefile
from dea_plotting import rgb


/g/data/v10/public/modules/dea/20200526/lib/python3.6/site-packages/datacube/storage/masking.py:4: DeprecationWarning: datacube.storage.masking has moved to datacube.utils.masking
category=DeprecationWarning)


### Connect to the datacube¶

Activate the datacube database, which provides functionality for loading and displaying stored Earth observation data.

[2]:

# Temporary solution to account for Collection 3 data being in a different
# database on the NCI
try:
dc = datacube.Datacube(app='Intertidal_elevation', env='c3-samples')
except:
dc = datacube.Datacube(app='Intertidal_elevation')


### Analysis parameters¶

The following cell set important parameters for the analysis:

• lat_range: The latitude range to analyse (e.g. (-27.60, -27.665)). For reasonable load times, keep this to a range of ~0.1 degrees or less.

• lon_range: The longitude range to analyse (e.g. (153.33, 153.425)). For reasonable load times, keep this to a range of ~0.1 degrees or less.

• time_range: The date range to analyse (e.g. ('2000', '2019'))

If running the notebook for the first time, keep the default settings below. This will demonstrate how the analysis works and provide meaningful results. The example generates an intertidal elevation model for intertidal flats in Moreton Bay south of Brisbane, Australia.

To ensure that the tidal modelling part of this analysis works correctly, please make sure the centre of the study area is located over water when setting lat_range and lon_range.

[3]:

lat_range = (-27.60, -27.665)
lon_range = (153.33, 153.425)
time_range = ('2000', '2019')



## View the selected location¶

The next cell will display the selected area on an interactive map. Feel free to zoom in and out to get a better understanding of the area you’ll be analysing. Clicking on any point of the map will reveal the latitude and longitude coordinates of that point.

[4]:

display_map(x=lon_range, y=lat_range)


/g/data/v10/public/modules/dea-env/20200526/lib/python3.6/site-packages/pyproj/crs/crs.py:53: FutureWarning: '+init=<authority>:<code>' syntax is deprecated. '<authority>:<code>' is the preferred initialization method. When making the change, be mindful of axis order changes: https://pyproj4.github.io/pyproj/stable/gotchas.html#axis-order-changes-in-proj-6
return _prepare_from_string(" ".join(pjargs))
/g/data/v10/public/modules/dea-env/20200526/lib/python3.6/site-packages/pyproj/crs/crs.py:294: FutureWarning: '+init=<authority>:<code>' syntax is deprecated. '<authority>:<code>' is the preferred initialization method. When making the change, be mindful of axis order changes: https://pyproj4.github.io/pyproj/stable/gotchas.html#axis-order-changes-in-proj-6
projstring = _prepare_from_string(" ".join((projstring, projkwargs)))
/g/data/v10/public/modules/dea-env/20200526/lib/python3.6/site-packages/pyproj/crs/crs.py:53: FutureWarning: '+init=<authority>:<code>' syntax is deprecated. '<authority>:<code>' is the preferred initialization method. When making the change, be mindful of axis order changes: https://pyproj4.github.io/pyproj/stable/gotchas.html#axis-order-changes-in-proj-6
return _prepare_from_string(" ".join(pjargs))
/g/data/v10/public/modules/dea-env/20200526/lib/python3.6/site-packages/pyproj/crs/crs.py:294: FutureWarning: '+init=<authority>:<code>' syntax is deprecated. '<authority>:<code>' is the preferred initialization method. When making the change, be mindful of axis order changes: https://pyproj4.github.io/pyproj/stable/gotchas.html#axis-order-changes-in-proj-6
projstring = _prepare_from_string(" ".join((projstring, projkwargs)))

[4]:


The first step in this analysis is to load in Landsat data for the lat_range, lon_range and time_range we provided above. The code below first connects to the datacube database, and then uses the load_ard function to load in data from the Landsat 5, 7 and 8 satellites for the area and time included in lat_range, lon_range and time_range. The function will also automatically mask out clouds from the dataset, allowing us to focus on pixels that contain useful data:

[5]:

# Create the 'query' dictionary object, which contains the longitudes,
# latitudes and time provided above
query = {
'y': lat_range,
'x': lon_range,
'time': time_range,
'measurements': ['nbart_red', 'nbart_green', 'nbart_blue', 'nbart_nir'],
'resolution': (-30, 30),
}

# Identify the most common projection system in the input query
output_crs = mostcommon_crs(dc=dc, product='ga_ls8c_ard_3', query=query)

# Load available data from all three Landsat satellites
products=['ga_ls5t_ard_3',
'ga_ls7e_ard_3',
'ga_ls8c_ard_3'],
output_crs=output_crs,
align=(15, 15),
group_by='solar_day',
**query)


Loading ga_ls5t_ard_3 data
Combining and sorting data
Returning 642 observations as a dask array


Once the load is complete, examine the data by printing it in the next cell. The Dimensions argument revels the number of time steps in the data set, as well as the number of pixels in the x (longitude) and y (latitude) dimensions.

[6]:

print(landsat_ds)


<xarray.Dataset>
Dimensions:      (time: 642, x: 314, y: 241)
Coordinates:
spatial_ref  int32 32656
* x            (x) float64 5.326e+05 5.326e+05 ... 5.419e+05 5.42e+05
* y            (y) float64 -3.053e+06 -3.053e+06 ... -3.06e+06 -3.06e+06
* time         (time) datetime64[ns] 2000-01-26T23:34:55.629134 ... 2019-08-10T23:29:30.753736
Data variables:
nbart_red    (time, y, x) float32 dask.array<chunksize=(1, 241, 314), meta=np.ndarray>
nbart_green  (time, y, x) float32 dask.array<chunksize=(1, 241, 314), meta=np.ndarray>
nbart_blue   (time, y, x) float32 dask.array<chunksize=(1, 241, 314), meta=np.ndarray>
nbart_nir    (time, y, x) float32 dask.array<chunksize=(1, 241, 314), meta=np.ndarray>
Attributes:
crs:           epsg:32656
grid_mapping:  spatial_ref


### Plot example timestep in true colour¶

To visualise the data, use the pre-loaded rgb utility function to plot a true colour image for a given time-step. White areas indicate where clouds or other invalid pixels in the image have been masked.

Change the value for timestep and re-run the cell to plot a different timestep (timesteps are numbered from 0 to n_time - 1 where n_time is the total number of timesteps; see the time listing under the Dimensions category in the dataset print-out above).

[7]:

# Set the timesteps to visualise
timestep = 11

# Generate RGB plots at each timestep
rgb(landsat_ds, index=timestep)



## Compute Normalised Difference Water Index¶

To extract intertidal depth contours, we need to be able to seperate water from land in our study area. To do this, we can use our Landsat data to calculate a water index called the Normalised Difference Water Index, or NDWI. This index uses the ratio of green and near-infrared radiation to identify the presence of water. The formula is:

\begin{aligned} \text{NDWI} &= \frac{(\text{Green} - \text{NIR})}{(\text{Green} + \text{NIR})} \end{aligned}

where Green is the green band and NIR is the near-infrared band.

When it comes to interpreting the index, High values (greater than 0, blue colours) typically represent water pixels, while low values (less than 0, red colours) represent land. You can use the cell below to calculate and plot one of the images after calculating the index.

[8]:

# Calculate the water index
landsat_ds = calculate_indices(landsat_ds, index='NDWI',
collection='ga_ls_3')

# Plot the resulting image for the same timestep selected above
landsat_ds.NDWI.isel(time=timestep).plot(cmap='RdBu',
size=6,
vmin=-0.8,
vmax=0.8)
plt.show()



How does the plot of the index compare to the optical image from earlier? Was there water or land anywhere you weren’t expecting?

## Model tide heights¶

The location of the shoreline can vary greatly from low to high tide. In the code below, we aim to calculate the height of the tide at the exact moment each Landsat image was acquired. This will allow us to built a sorted time series of images taken at low tide to high tide, which we will use to generate the intertidal elevation model.

The tidal_tag function below uses the OTPS TPXO8 tidal model to calculate the height of the tide at the exact moment each satellite image in our dataset was taken, and adds this as a new tide_height attribute in our dataset (for more information about this function, refer to the Tidal modelling notebook).

Note: this function can only model tides correctly if the centre of your study area is located over water. If this isn’t the case, you can specify a custom tide modelling location by passing a coordinate to tidepost_lat and tidepost_lon (e.g. tidepost_lat=-27.73, tidepost_lon=153.46).

[9]:

# Calculate tides for each timestep in the satellite dataset
landsat_ds = tidal_tag(ds=landsat_ds, tidepost_lat=None, tidepost_lon=None)

# Print the output dataset with new tide_height variable
print(landsat_ds)


Setting tide modelling location from dataset centroid: 153.38, -27.63
<xarray.Dataset>
Dimensions:      (time: 642, x: 314, y: 241)
Coordinates:
spatial_ref  int32 32656
* x            (x) float64 5.326e+05 5.326e+05 ... 5.419e+05 5.42e+05
* y            (y) float64 -3.053e+06 -3.053e+06 ... -3.06e+06 -3.06e+06
* time         (time) datetime64[ns] 2000-01-26T23:34:55.629134 ... 2019-08-10T23:29:30.753736
Data variables:
nbart_red    (time, y, x) float32 dask.array<chunksize=(1, 241, 314), meta=np.ndarray>
nbart_green  (time, y, x) float32 dask.array<chunksize=(1, 241, 314), meta=np.ndarray>
nbart_blue   (time, y, x) float32 dask.array<chunksize=(1, 241, 314), meta=np.ndarray>
nbart_nir    (time, y, x) float32 dask.array<chunksize=(1, 241, 314), meta=np.ndarray>
NDWI         (time, y, x) float32 dask.array<chunksize=(1, 241, 314), meta=np.ndarray>
tide_height  (time) float64 -0.124 -0.238 -0.155 ... -0.711 -0.579 -0.292
Attributes:
crs:           epsg:32656
grid_mapping:  spatial_ref


Now that we have modelled tide heights, we can plot them to visualise the range of tide that was captured by Landsat across our time series:

[10]:

# Plot the resulting tide heights for each Landsat image:
landsat_ds.tide_height.plot()
plt.show()


## Create water index summary images from low to high tide¶

Using these tide heights, we can sort our Landsat dataset by tide height to reveal which parts of the landscape are inundated or exposed from low to high tide.

Individual remote sensing images can be affected by noise, including clouds, sunglint and poor water quality conditions (e.g. sediment). To produce cleaner images that can be compared more easily between tidal stages, we can create ‘summary’ images or composites that combine multiple images into one image to reveal the ‘typical’ or median appearance of the landscape at different tidal stages. In this case, we use the median as the summary statistic because it prevents strong outliers (like stray clouds) from skewing the data, which would not be the case if we were to use the mean.

In the code below, we take the time series of images, sort by tide and categorise each image into 9 discrete tidal intervals, ranging from the lowest (tidal interval 1) to the highest tides observed by Landsat (tidal interval 9). For more information on this method, refer to Sagar et al. 2018.

[11]:

# Sort every image by tide height
landsat_ds = landsat_ds.sortby('tide_height')

# Bin tide heights into 9 tidal intervals from low (1) to high tide (9)
binInterval = np.linspace(landsat_ds.tide_height.min(),
landsat_ds.tide_height.max(),
num=10)
tide_intervals = pd.cut(landsat_ds.tide_height,
bins=binInterval,
labels=range(1, 10),
include_lowest=True)

landsat_ds['tide_interval'] = xr.DataArray(tide_intervals,
[('time', landsat_ds.time)])

print(landsat_ds)


<xarray.Dataset>
Dimensions:        (time: 642, x: 314, y: 241)
Coordinates:
spatial_ref    int32 32656
* x              (x) float64 5.326e+05 5.326e+05 ... 5.419e+05 5.42e+05
* y              (y) float64 -3.053e+06 -3.053e+06 ... -3.06e+06 -3.06e+06
* time           (time) datetime64[ns] 2007-07-08T23:32:20.512004 ... 2010-01-29T23:32:58.543958
Data variables:
nbart_red      (time, y, x) float32 dask.array<chunksize=(1, 241, 314), meta=np.ndarray>
nbart_green    (time, y, x) float32 dask.array<chunksize=(1, 241, 314), meta=np.ndarray>
nbart_blue     (time, y, x) float32 dask.array<chunksize=(1, 241, 314), meta=np.ndarray>
nbart_nir      (time, y, x) float32 dask.array<chunksize=(1, 241, 314), meta=np.ndarray>
NDWI           (time, y, x) float32 dask.array<chunksize=(1, 241, 314), meta=np.ndarray>
tide_height    (time) float64 -0.723 -0.711 -0.698 ... 1.418 1.426 1.436
tide_interval  (time) int64 1 1 1 1 1 1 1 1 1 1 1 ... 9 9 9 9 9 9 9 9 9 9 9
Attributes:
crs:           epsg:32656
grid_mapping:  spatial_ref


We can plot the boundaries between the nine tidal intervals on the same plot we generated earlier:

[12]:

landsat_ds.sortby('time').tide_height.plot()
for i in binInterval: plt.axhline(i, c='black', alpha=0.5)


Now that we have a dataset where each image is classified into a discrete range of the tide, we can combine our images into a set of nine individual images that show where land and water is located from low to high tide. This step can take several minutes to process.

[13]:

# For each interval, compute the median water index and tide height value
landsat_intervals = (landsat_ds[['tide_interval', 'NDWI', 'tide_height']]
.compute()
.groupby('tide_interval')
.median(dim='time'))

# Plot the resulting set of tidal intervals
landsat_intervals.NDWI.plot(col='tide_interval', col_wrap=5, cmap='RdBu')
plt.show()



The plot above should make it clear how the shape and structure of the coastline changes significantly from low to high tide as low-lying tidal flats are quickly inundated by increasing water levels.

## Extract depth contours from imagery¶

We now want to extract an accurate boundary between land and water for each of the tidal intervals above. The code below identifies the depth contours based on the boundary between land and water by tracing a line along pixels with a water index value of 0 (the boundary between land and water water index values). It returns a geopandas.GeoDataFrame with one depth contour for each tidal interval that is labelled with tide heights in metres relative to Mean Sea Level.

[14]:

# Set up attributes to assign to each waterline
attribute_df = pd.DataFrame({'tide_m': landsat_intervals.tide_height.values})

# Extract waterlines
contours_gdf = subpixel_contours(da=landsat_intervals.NDWI,
z_values=0,
crs=landsat_ds.crs,
affine=landsat_ds.geobox.transform,
attribute_df=attribute_df,
min_vertices=20,
dim='tide_interval')

# Plot output shapefile over the top of the first tidal interval water index
fig, ax = plt.subplots(1, 1, figsize=(15, 10))
landsat_intervals.NDWI.sel(tide_interval=1).plot(ax=ax,
cmap='Greys',
contours_gdf.plot(ax=ax, column='tide_m', cmap='YlOrRd', legend=True)
plt.show()


Operating in single z-value, multiple arrays mode


The above plot is a basic visualisation of the depth contours returned by the subpixel_contours function. Deeper contours (in m relative to Mean Sea Level) are coloured in yellow; more shallow contours are coloured in red. Now have the shapefile, we can use a more complex function to make an interactive plot for viewing the topography of the intertidal zone.

### Plot interactive map of depth contours coloured by time¶

The next cell provides an interactive map with an overlay of the depth contours identified in the previous cell. Run it to view the map.

Zoom in to the map below to explore the resulting set of depth contours. Using this data, we can easily identify areas of the coastline which are only exposed in the lowest of tides, or other areas that are only covered by water during high tides.

[15]:

map_shapefile(gdf=contours_gdf, attribute='tide_m', continuous=True)


## Interpolate contours into a Digital Elevation Model (DEM)¶

While the contours above provide valuable information about the topography of the intertidal zone, we can extract additional information about the 3D structure of the coastline by converting them into an elevation raster (i.e. a Digital Elevation Model or DEM).

In the cell below, we convert the shapefile above into an array of points with X, Y and Z coordinates, where the Z coordinate is the point’s elevation relative to Mean Sea Level. We then use these XYZ points to interpolate smooth, continuous elevations across the intertidal zone using linear interpolation.

[16]:

# First convert our contours shapefile into an array of XYZ points
xyz_array = contours_to_arrays(contours_gdf, 'tide_m')

# Interpolate these XYZ points over the spatial extent of the Landsat dataset
intertidal_dem = interpolate_2d(ds=landsat_intervals,
x_coords=xyz_array[:, 0],
y_coords=xyz_array[:, 1],
z_coords=xyz_array[:, 2])

# Plot the output
intertidal_dem.plot(cmap='viridis', size=8, robust=True)
plt.show()



You can see in the output above that our interpolation results are very messy. This is because the interpolation extends across areas of our study area that are not affected by tides (e.g. areas of water located beyond the lowest observed tide, and on land). To clean up the data, we can restrict the DEM to only the area between the lowest and highest observed tides:

[17]:

# Identify areas that are always wet (e.g. below low tide), or always dry
above_lowest = landsat_intervals.isel(tide_interval=0).NDWI < 0
below_highest = landsat_intervals.isel(tide_interval=-1).NDWI > 0

# Keep only pixels between high and low tide
intertidal_dem_clean = intertidal_dem.where(above_lowest & below_highest)

# Plot the cleaned dataset
intertidal_dem_clean.plot(cmap='viridis', size=8, robust=True)
plt.show()



## Export intertidal DEM as a GeoTIFF¶

As a final step, we can take the intertidal DEM we created and export it as a GeoTIFF that can be loaded in GIS software like QGIS or ArcMap (to download the dataset from the DEA Sandbox, locate it in the file browser to the left, right click on the file, and select “Download”).

[18]:

# The write_geotiff function requires an xarray Dataset, not a DataArray
intertidal_dem_ds = intertidal_dem_clean.to_dataset(name='DEM')

# Give the dataset a CRS/projection system so the output raster can be used in a GIS
intertidal_dem_ds.attrs['crs'] = landsat_ds.crs

# Export as a GeoTIFF
write_geotiff(dataset=intertidal_dem_ds, filename='intertidal_dem.tif')


/g/data/v10/public/modules/dea/20200526/lib/python3.6/site-packages/datacube/helpers.py:34: DeprecationWarning: Function datacube.helpers.write_geotiff is deprecated,
category=DeprecationWarning)


## Next steps¶

When you are done, return to the “Set up analysis” cell, modify some values (e.g. time_range, lat_range, lon_range) and rerun the analysis.

If you’re going to change the location, you’ll need to make sure Landsat 5, 7 and 8 data is available for the new location, which you can check at the DEA Explorer (use the drop-down menu to view all Landsat products).

### National Intertidal Digital Elevation Model¶

For more information about the science behind this notebook, please refer to the scientific article outlining the application of this approach to the entire Australian coastline: Bishop-Taylor et al. 2019 Between the tides: Modelling the elevation of Australia’s exposed intertidal zone at continental scale.

Contact: If you need assistance, please post a question on the Open Data Cube Slack channel or on the GIS Stack Exchange using the open-data-cube tag (you can view previously asked questions here). If you would like to report an issue with this notebook, you can file one on Github.

Compatible datacube version:

[19]:

print(datacube.__version__)

1.8.0


## Tags¶

Browse all available tags on the DEA User Guide’s Tags Index

Tags: NCI compatible, sandbox compatible, landsat 5, landsat 7, landsat 8, dea_datahandling, dea_bandindices, dea_coastaltools, dea_spatialtools, dea_plotting, load_ard, mostcommon_crs, calculate_indices, tidal_tag, subpixel_contours, map_shapefile, display_map, rgb, interpolate_2d, contours_to_arrays, NDWI, tide modelling, image compositing, waterline extraction, spatial interpolation, intertidal, real world, GeoTIFF, exporting data