Update README.md
Browse files
README.md
CHANGED
|
@@ -33,25 +33,90 @@ configs:
|
|
| 33 |
---
|
| 34 |
|
| 35 |
# Welcome to the KATE-PD Dataset
|
| 36 |
-
Welcome to the home page of Kahramanmaraş Türkiye Earthquake-Post Disaster Dataset (KATE-PD). If you are reading this README, you are probably visiting one of the following places to learn more about **KATE-PD Dataset** and the associated study "*A
|
| 37 |
|
| 38 |
-
* [Code Ocean Capsule](https://
|
| 39 |
* [GitHub Repository](https://github.com/cscrs/kate-pd)
|
| 40 |
* [HuggingFace](https://huggingface.co/datasets/cscrs/kate-pd)
|
| 41 |
|
| 42 |
-
The **KATE-PD Dataset** and the associated codes and supplementary information are published in three places i.e. CodeOcean, GitHub and
|
| 43 |
|
| 44 |
## Content of the KATE-PD Dataset
|
| 45 |
-
The KATE-PD dataset is designed to facilitate the development and evaluation of earthquake damage assessment algorithms on post disaster images. It provides high-resolution satellite imagery from post-earthquake events, specifically covering the regions affected by the Kahramanmaraş earthquake in Türkiye. Given the scarcity of earthquake damage assessment datasets, KATE-PD aims to bridge this gap by offering high-quality annotated data, enabling researchers to train and test machine learning models for damage assessment. If you are looking for a dataset suitable for change detection algorithms, you can visit our sister project [KATE-CD: Kahramanmaraş Türkiye Earthquake-Change Detection Dataset](10.24433/CO.3747729.v1).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 46 |
|
| 47 |
### Source of Satellite Imagery
|
| 48 |
The dataset includes satellite images from Maxar Open Data and Airbus Pleiades, covering seven heavily affected cities: Adıyaman, Gaziantep, Hatay, Kahramanmaraş, Kilis, Osmaniye, and Malatya. These images have a resolution ranging from 0.3m to 0.5m. The collection process involved selecting imagery captured under various lighting conditions, using different sensors and viewing angles. The coordinate reference system EPSG:32637 was chosen for consistency, and radiometrically corrected images with 8-bit spectral resolution were used to maintain uniform color representation across sources.
|
| 49 |
|
| 50 |
### Labelling Process
|
| 51 |
-
A grid-based labeling approach was used to divide the images into 512×512 pixel patches. The Label Studio tool was employed for manual annotation, where post-earthquake images were reviewed, and damaged buildings were marked with polygonal annotations. A binary labeling strategy was applied, where pixels inside damage polygons were assigned a value of 1, and all others were set to 0.
|
| 52 |
|
| 53 |
### Machine-Learning Ready Format
|
| 54 |
-
The main structure of the dataset provided in CodeOcean is formatted in YOLO format under */data/katepd* folder where post-disaster images are provided as PNG files and the polygons are encoded in TXT files. The files are also organized with respect to partitions.
|
| 55 |
|
| 56 |
## Reproducibility: CodeOcean
|
| 57 |
The dataset is published on three platforms: CodeOcean, GitHub and HuggingFace. The purpose of CodeOcean is to provide data, codes and the computing instructions to reproduce the results. CodeOcean uses the term *capsule* to define the collection of everything needed to reproduce the results. Depending on your goal and your time constraints, CodeOcean provide two alternatives to run the capsule and obtain the results: via Open Science Library or Capsule Export.
|
|
@@ -89,13 +154,14 @@ docker run --platform linux/amd64 --rm \
|
|
| 89 |
## Published results
|
| 90 |
In the results folder of the CodeOcean capsule, you can reach the pre-computed outputs of the code or you can generate them from scratch with single-click in CodeOcean. In either case, these outputs correspond to the published content in the manuscript. The mapping between capsule results and the content in the manuscript is as follows:
|
| 91 |
|
| 92 |
-
Code CodeOcean
|
| 93 |
-
------------
|
| 94 |
-
evaluate.py */val_scores.txt
|
| 95 |
*/train_scores.txt
|
| 96 |
*/test_scores.txt
|
| 97 |
-
evaluate.py yolo/test_plots.pdf
|
| 98 |
-
|
|
|
|
| 99 |
|
| 100 |
## For Developers
|
| 101 |
### Differences between the platforms:
|
|
|
|
| 33 |
---
|
| 34 |
|
| 35 |
# Welcome to the KATE-PD Dataset
|
| 36 |
+
Welcome to the home page of Kahramanmaraş Türkiye Earthquake-Post Disaster Dataset (KATE-PD). If you are reading this README, you are probably visiting one of the following places to learn more about **KATE-PD Dataset** and the associated study "*A Rapir Damage Assessment using Remote Sensing: Türkiye 2023 Post-Earthquake Dataset: KATE-PD*", to be presented in the IEEE International Geoscience and Remote Sensing Symposium ([IGARSS 2025](https://www.2025.ieeeigarss.org/)).
|
| 37 |
|
| 38 |
+
* [Code Ocean Capsule](https://doi.org/10.24433/CO.8064763.v1) in [Open Science Library](https://codeocean.com/explore)
|
| 39 |
* [GitHub Repository](https://github.com/cscrs/kate-pd)
|
| 40 |
* [HuggingFace](https://huggingface.co/datasets/cscrs/kate-pd)
|
| 41 |
|
| 42 |
+
The **KATE-PD Dataset** and the associated codes and supplementary information (630 MB in total) are published in three places i.e. CodeOcean, GitHub and HuggingFace for providing redundancy and extended reach. All of the content uploaded to the three websites are the same except small differences because of platform requirements. The CodeOcean platform is mainly used for reproducibility, whereas GitHub is used to provide git access and hence easy collaboration between **KATE-PD Dataset** developers. Finally HuggingFace provides an easy access to the database where you can run existing models in HuggingFace on KATE-PD without too much effort.
|
| 43 |
|
| 44 |
## Content of the KATE-PD Dataset
|
| 45 |
+
The KATE-PD dataset is designed to facilitate the development and evaluation of earthquake damage assessment algorithms on post disaster images. It provides high-resolution satellite imagery from post-earthquake events, specifically covering the regions affected by the Kahramanmaraş earthquake in Türkiye. Given the scarcity of earthquake damage assessment datasets, KATE-PD aims to bridge this gap by offering high-quality annotated data, enabling researchers to train and test machine learning models for damage assessment. If you are looking for a dataset suitable for change detection algorithms, you can visit our sister project [KATE-CD: Kahramanmaraş Türkiye Earthquake-Change Detection Dataset](https://doi.org/10.24433/CO.3747729.v1).
|
| 46 |
+
|
| 47 |
+
The directory structure of **KATE-PD Dataset** is:
|
| 48 |
+
|
| 49 |
+
|-- metadata
|
| 50 |
+
| |-- metadata.yml # used by CodeOcean
|
| 51 |
+
|-- environment
|
| 52 |
+
| |-- Dockerfile # used by CodeOcean & VSCode
|
| 53 |
+
|-- code
|
| 54 |
+
| |-- utils
|
| 55 |
+
| | |-- create_cover_image.py
|
| 56 |
+
| | |-- hf_update_db.py # to update HuggingFace DB
|
| 57 |
+
| | |-- yolo_to_geojson.py
|
| 58 |
+
| |-- evaluate.py
|
| 59 |
+
| |-- LICENSE
|
| 60 |
+
| |-- run # main entrypoint for CodeOcean
|
| 61 |
+
| |-- smp_segmentation.py
|
| 62 |
+
| |-- test.py
|
| 63 |
+
| |-- train.py
|
| 64 |
+
| |-- utils.py
|
| 65 |
+
| |-- yolo_test.py
|
| 66 |
+
|-- data
|
| 67 |
+
| |-- checkpoints
|
| 68 |
+
| | |-- resnet152_e14_iou_0.36.pth # published SMP Model
|
| 69 |
+
| | |-- yolo_best.py # published YOLO Model
|
| 70 |
+
| |-- katepd # dataset in YOLO format
|
| 71 |
+
| | |-- images
|
| 72 |
+
| | | |-- train
|
| 73 |
+
| | | | |-- trn_tile_177_patch_1.png
|
| 74 |
+
| | | | |-- ...
|
| 75 |
+
| | | |-- val
|
| 76 |
+
| | | | |-- val_tile_182_patch_6.png
|
| 77 |
+
| | | | |-- ...
|
| 78 |
+
| | | |-- test
|
| 79 |
+
| | | | |-- tst_tile_188_patch_12.png
|
| 80 |
+
| | | | |-- ...
|
| 81 |
+
| | |-- labels
|
| 82 |
+
| | | |-- train
|
| 83 |
+
| | | | |-- trn_tile_177_patch_1.txt
|
| 84 |
+
| | | | |-- ...
|
| 85 |
+
| | | |-- val
|
| 86 |
+
| | | | |-- val_tile_182_patch_6.txt
|
| 87 |
+
| | | | |-- ...
|
| 88 |
+
| | | |-- test
|
| 89 |
+
| | | | |-- tst_tile_188_patch_12.txt
|
| 90 |
+
| | | | |-- ...
|
| 91 |
+
| | |-- classes.txt
|
| 92 |
+
| | |-- katepd.yaml
|
| 93 |
+
| |-- preprocessing # extra information for database
|
| 94 |
+
| | |-- grid_maxar.geojson
|
| 95 |
+
| | |-- grid_pleidas.geojson
|
| 96 |
+
| | |-- history_maxar.json
|
| 97 |
+
| | |-- history_pleidas.json
|
| 98 |
+
| | |-- katepd_polygons.geojson
|
| 99 |
+
| | |-- label_studio_annotations.csv
|
| 100 |
+
| | |-- label_studio_files.txt
|
| 101 |
+
| | |-- README.md
|
| 102 |
+
| |-- LICENSE
|
| 103 |
+
|-- .codeocean # CodeOcean computing environment info
|
| 104 |
+
| |-- environment.json
|
| 105 |
+
|-- .gitignore
|
| 106 |
+
|-- results # to store CodeOcean capsule results
|
| 107 |
+
|-- .devcontainer # for VSCode DevContainers
|
| 108 |
+
| |-- devcontainer.json
|
| 109 |
+
|-- CITATION.cff # provides Cite link in GitHub repo
|
| 110 |
+
|-- README.md
|
| 111 |
|
| 112 |
### Source of Satellite Imagery
|
| 113 |
The dataset includes satellite images from Maxar Open Data and Airbus Pleiades, covering seven heavily affected cities: Adıyaman, Gaziantep, Hatay, Kahramanmaraş, Kilis, Osmaniye, and Malatya. These images have a resolution ranging from 0.3m to 0.5m. The collection process involved selecting imagery captured under various lighting conditions, using different sensors and viewing angles. The coordinate reference system EPSG:32637 was chosen for consistency, and radiometrically corrected images with 8-bit spectral resolution were used to maintain uniform color representation across sources.
|
| 114 |
|
| 115 |
### Labelling Process
|
| 116 |
+
A grid-based labeling approach was used to divide the images into 512×512 pixel patches. The Label Studio tool was employed for manual annotation, where post-earthquake images were reviewed, and damaged buildings were marked with polygonal annotations. A binary labeling strategy was applied, where pixels inside damage polygons were assigned a value of 1, and all others were set to 0. During labelling, no extra information other than the post-images is used.
|
| 117 |
|
| 118 |
### Machine-Learning Ready Format
|
| 119 |
+
The main structure of the dataset provided in CodeOcean is formatted in YOLO format under */data/katepd* folder where post-disaster images are provided as PNG files and the polygons are encoded in TXT files. The files are also organized with respect to partitions: train (%80), val (%10) and test (%10). On HuggingFace, we also created mask files (by combining image and label pairs) for those not willing to work with polygons. Due to limitations on large files, we don't include the dataset on GitHub.
|
| 120 |
|
| 121 |
## Reproducibility: CodeOcean
|
| 122 |
The dataset is published on three platforms: CodeOcean, GitHub and HuggingFace. The purpose of CodeOcean is to provide data, codes and the computing instructions to reproduce the results. CodeOcean uses the term *capsule* to define the collection of everything needed to reproduce the results. Depending on your goal and your time constraints, CodeOcean provide two alternatives to run the capsule and obtain the results: via Open Science Library or Capsule Export.
|
|
|
|
| 154 |
## Published results
|
| 155 |
In the results folder of the CodeOcean capsule, you can reach the pre-computed outputs of the code or you can generate them from scratch with single-click in CodeOcean. In either case, these outputs correspond to the published content in the manuscript. The mapping between capsule results and the content in the manuscript is as follows:
|
| 156 |
|
| 157 |
+
Code CodeOcean Results Manuscript
|
| 158 |
+
------------ ----------------------- ----------
|
| 159 |
+
evaluate.py */val_scores.txt Table II
|
| 160 |
*/train_scores.txt
|
| 161 |
*/test_scores.txt
|
| 162 |
+
evaluate.py yolo/test_plots.pdf Figure 2
|
| 163 |
+
resnet152/test_plots.pdf Figure 2
|
| 164 |
+
-------------------------------------------------
|
| 165 |
|
| 166 |
## For Developers
|
| 167 |
### Differences between the platforms:
|