From 49d830a13e12c1138b2d1dc59d91b2d58393d89f Mon Sep 17 00:00:00 2001 From: Alex Gregor <111502950+alexryangregor@users.noreply.github.com> Date: Wed, 22 Nov 2023 11:19:59 +0100 Subject: [PATCH] Update damage_proxy_map.rst Proofreading complete. --- docs/source/modules/dwn/damage_proxy_map.rst | 19 ++++++++----------- 1 file changed, 8 insertions(+), 11 deletions(-) diff --git a/docs/source/modules/dwn/damage_proxy_map.rst b/docs/source/modules/dwn/damage_proxy_map.rst index 3f7363ca47..cfeba68b8d 100644 --- a/docs/source/modules/dwn/damage_proxy_map.rst +++ b/docs/source/modules/dwn/damage_proxy_map.rst @@ -1,13 +1,10 @@ Damage proxy maps ================= - **Damage proxy maps based on coherence change detection** -This module provides a fully-automated workflow for the creation of damage proxy maps based on the method of coherent change detection (CCD) with Sentinel-1 SLC data, as described by `Tay *et al.* (2020) `_. - -The output data files consist of the damage proxy map as GeoTiff (*dmp_...tif*) and KMZ (*dmp_...kmz*) files, as well as the raw CCD values in GeoTiff (*CCD_...tif*) and GeoJSON (*CCD_...geojson*) formats. +This module provides a fully automated workflow for the creation of damage proxy maps based on the method of coherent change detection (CCD) with Sentinel-1 SLC data, as described by `Tay et al. (2020) `_ (SLC refers to Single Look Complex). -The files are found within a newly created folder. The folder name is based on the name of your AOI and the event date. +The output data files consist of the damage proxy map as GeoTiff (*dmp_...tif*) and KMZ (*dmp_...kmz*) files, as well as the raw CCD values in GeoTiff (*CCD_...tif*) and GeoJSON (*CCD_...geojson*) formats. The files are found within a newly created folder. The folder name is based on the name of your AOI and the event date. .. attention:: @@ -21,7 +18,7 @@ The two steps of the process are explained in the following section. Select an AOI ------------- -Using the provided AOI selector, select an AOI of your choice between the different methods available in the tool. We provide three administration descriptions (from Level 0 to Level 2) and three custom shapes (drawn directly on the map or OGR-compatible files). +Using the provided **AOI selector**, select an AOI of your choice between the different methods available in the tool. We provide three administration descriptions (from Level 0 to Level 2) and three custom shapes (drawn directly on the map or OGR-compatible files). .. figure:: https://raw.githubusercontent.com/sepal-contrib/damage_proxy_maps/main/doc/img/aoi_select.png @@ -30,16 +27,16 @@ Using the provided AOI selector, select an AOI of your choice between the differ Parameters ---------- -- Disaster event date: Pick the date where the disaster event happened. -- Copernicus credentials: Provide your Sci-Hub credentials for search and download of the relevant Sentinel-1 scenes. If you do not have an account, register with `Copernicus Sci-Hub `_. +- **Disaster event date**: Choose the date where the disaster event happened. +- **Copernicus credentials**: Provide your Sci-Hub credentials for searching and downloading relevant Sentinel-1 scenes. If you do not have an account, register with `Copernicus Sci-Hub `_. -Selecting this button will trigger the full workflow (Note: Some of the steps may take a while, such as downloading and processing, so if you have an unstable internet connection, set the minimum runtime of your instance to two hours; otherwise, stay connected to the SEPAL website by neither closing your browser or browser tab.) +Selecting this button will trigger the full workflow (Note: Some of the steps may take a while, such as downloading and processing, so if you have an unstable internet connection, set the minimum runtime of your instance to two hours; otherwise, stay connected to the SEPAL website by neither closing your browser nor browser tab.) .. note:: - If the processing does not finish, you can rerun the module with the same parameters, and the processing will continue from where it stopped. + If the processing does not finish, you can rerun the module with the same parameters and it will continue from where it stopped. -Once the computation is finished, the result files will be stored in the :code:`module_results/Damage_proxy_map/_/` folder. +Once the computation has finished, the result files will be stored in the :code:`module_results/Damage_proxy_map/_/` folder. .. figure:: https://raw.githubusercontent.com/sepal-contrib/damage_proxy_maps/main/doc/img/complete.png