Datasets:

Modalities:
Image
ArXiv:
tmanzini commited on
Commit
a787fa3
·
verified ·
1 Parent(s): 9c34666

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +77 -22
README.md CHANGED
@@ -12,42 +12,97 @@ This repository contains the CRASAR-U-DROIDs dataset. This is a dataset of ortho
12
  3) [CRASAR-U-DROIDs: A Large Scale Benchmark Dataset for Building Alignment and Damage Assessment in Georectified sUAS Imagery](https://arxiv.org/abs/2407.17673). This paper presents the Center for Robot Assisted Search And Rescue - Uncrewed Aerial Systems - Disaster Response Overhead Inspection Dataset (CRASAR-U-DROIDs) for building damage assessment and spatial alignment collected from small uncrewed aerial systems (sUAS) geospatial imagery. To replicate the results from this paper, please see commit ae3e394cf0377e6e2ccd8fcef64dbdaffd766434.
13
 
14
  This dataset contains 52 orthomosaics containing 21716 building polygons collected from 10 different disasters, totaling 67 gigapixels of imagery.
15
- Building polygons were sourced from Microsoft's US Building Footprint's Dataset \[[1](https://github.com/microsoft/USBuildingFootprints)\], and in some cases building polygons were added manually by the authors.
16
  Each building polygon has been annotated using the Joint Damage Scale \[[2](https://arxiv.org/abs/1911.09296)\] and translationally aligned for model training.
17
- The dataset has been split into test and train at the disaster level with 6 disasters in the train set, and 4 disasters in the test set.
18
  A summary of the dataset, grouped by disaster and ordered by area, is included below for reference.
19
 
20
- | Disaster | Area (km^2) | Gigapixels | Building Polygons | Orthomosaics | Test or Train |
21
  | ------------------------- | --------------- | --------------- | ----------------- | ------------- | ------------- |
22
- | Hurricane Ian | 32.66517523 | 30.7383172 | 14326 | 25 | Train |
23
- | Mayfield Tornado | 8.422144185 | 9.698707535 | 2036 | 3 | Test |
24
- | Kilauea Eruption | 5.751864646 | 1.121020488 | 385 | 3 | Train |
25
- | Hurricane Idalia | 5.686794335 | 0.351551451 | 782 | 2 | Test |
26
- | Hurricane Ida | 5.139696352 | 6.743893458 | 1095 | 5 | Train |
27
- | Hurricane Michael | 3.617024461 | 9.450281054 | 1145 | 2 | Test |
28
- | Hurricane Harvey | 2.596253635 | 5.075368273 | 1336 | 4 | Train |
29
- | Hurricane Laura | 2.341867225 | 1.4456527 | 478 | 2 | Train |
30
- | Mussett Bayou Fire | 1.714575473 | 2.164129413 | 129 | 5 | Test |
31
  | Champlain Towers Collapse | 0.041536185 | 0.246084846 | 4 | 1 | Train |
32
- | **Total** | **67.97693173** | **67.03500642** | **21716** | **52** | **N/A** |
33
 
34
  ## Dataset Structure
35
- At the top level the dataset contains a statistics.csv file, with summary statistics of the dataset, and two folders, train and test.
36
- Each folder has folders imagery (which contains all of the geo.tif files) and annotations.
37
  The annotations folder then contains one folder for each source of imagery (and therefore labels): sUAS, SATELLITE, and CREWED. These folders contain the imagery-derived labels from the imagery associated with each of the imagery sources.
38
- These folders contains two groups of data: alignment_adjustments, and building_damage_assessment.
39
- These two groups of data contain JSON data that represent the the annotations for both building damage assessment and the translational alignments necessary to align the building polygons with the imagery.
40
  These two data sources are discussed below.
41
 
42
  ### Building Damage Assessment
43
- A sample of the building damage assesssment JSON file is as follows...
44
  ```json
45
- [{"source": "custom", "id": "8194baa7a68e2cbfe6506c0f6c00a785", "label": "major damage", "pixels": [{"x": 5823, "y": 6310}, ...], "EPSG:4326": [{"lat": 25.87311942079238, "lon": -80.12125843985305}, ...]}, ...]
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
46
  ```
47
 
48
- Each JSON file is a list of dictionaries, where each dictionary defines a building polygon and its metadata.
49
- - The "source" field describes the provenance of the building polygon. The possible options are "Microsoft" indicating the building polygon was sourced from the Microsot Building Footprints dataset, and "custom" indicating the polygons were manually added by the authors.
50
- - The "id" field is a unique string id for each building polygon.
51
  - The "label" field corresponds to the values of the Joint Damage Scale. The possible options are "no damage", "minor damage", "major damage", "destroyed", and "un-classified".
52
  - The "pixels" field corresponds to the coordinates of the building polygon in the pixel coordinate space of the orthomosaic.
53
  - The "EPSG:4326" field corresponds to the coordinates of the building polygon in the EPSG:4326 coordinate space.
 
12
  3) [CRASAR-U-DROIDs: A Large Scale Benchmark Dataset for Building Alignment and Damage Assessment in Georectified sUAS Imagery](https://arxiv.org/abs/2407.17673). This paper presents the Center for Robot Assisted Search And Rescue - Uncrewed Aerial Systems - Disaster Response Overhead Inspection Dataset (CRASAR-U-DROIDs) for building damage assessment and spatial alignment collected from small uncrewed aerial systems (sUAS) geospatial imagery. To replicate the results from this paper, please see commit ae3e394cf0377e6e2ccd8fcef64dbdaffd766434.
13
 
14
  This dataset contains 52 orthomosaics containing 21716 building polygons collected from 10 different disasters, totaling 67 gigapixels of imagery.
15
+ Building polygons were sourced from Microsoft's US Building Footprints Dataset \[[1](https://github.com/microsoft/USBuildingFootprints)\], and in some cases, building polygons were added manually by the authors.
16
  Each building polygon has been annotated using the Joint Damage Scale \[[2](https://arxiv.org/abs/1911.09296)\] and translationally aligned for model training.
17
+ The dataset has been split into test and train at the disaster level, with 6 disasters in the train set and 4 disasters in the test set.
18
  A summary of the dataset, grouped by disaster and ordered by area, is included below for reference.
19
 
20
+ | Disaster | Area (km^2) | Gigapixels | Building Labels | Orthomosaics | Test or Train |
21
  | ------------------------- | --------------- | --------------- | ----------------- | ------------- | ------------- |
22
+ | Hurricane Ian | 32.66517523 | 33.19155902 | 100351 | 200 | Train |
23
+ | Mayfield Tornado | 8.422144185 | 9.698707535 | 2028 | 3 | Test |
24
+ | Kilauea Eruption | 5.751864646 | 1.121020488 | 382 | 3 | Train |
25
+ | Hurricane Idalia | 5.686794335 | 1.095231308 | 4636 | 12 | Test |
26
+ | Hurricane Ida | 5.139696352 | 6.976915134 | 2068 | 9 | Train |
27
+ | Hurricane Michael | 3.617024461 | 9.567229047 | 6859 | 12 | Test |
28
+ | Hurricane Harvey | 2.596253635 | 5.128525423 | 5546 | 17 | Train |
29
+ | Hurricane Laura | 2.341867225 | 1.456463 | 500 | 3 | Train |
30
+ | Mussett Bayou Fire | 1.714575473 | 2.164129413 | 128 | 5 | Test |
31
  | Champlain Towers Collapse | 0.041536185 | 0.246084846 | 4 | 1 | Train |
32
+ | **Total** | **67.97693173** | **70.64586393** | **122502** | **265** | **N/A** |
33
 
34
  ## Dataset Structure
35
+ At the top level, the dataset contains a statistics.csv file, with summary statistics of the dataset, and two folders, train and test.
36
+ Each folder has imagery (which contains all of the geo.tif files) and annotations.
37
  The annotations folder then contains one folder for each source of imagery (and therefore labels): sUAS, SATELLITE, and CREWED. These folders contain the imagery-derived labels from the imagery associated with each of the imagery sources.
38
+ These folders contain two groups of data: alignment_adjustments, and building_damage_assessment.
39
+ These two groups of data contain JSON data that represent the annotations for both building damage assessment and the translational alignments necessary to align the building polygons with the imagery.
40
  These two data sources are discussed below.
41
 
42
  ### Building Damage Assessment
43
+ A sample of the building damage assessment JSON file is as follows...
44
  ```json
45
+ {
46
+ "8c6ab8368b726ace3807f7e64cceceb8": [
47
+ {
48
+ "EPSG:4326": [
49
+ {
50
+ "lat": 30.096003,
51
+ "lon": -93.727638
52
+ },
53
+ {
54
+ "lat": 30.096012,
55
+ "lon": -93.727236
56
+ },
57
+ {
58
+ "lat": 30.09609,
59
+ "lon": -93.727238
60
+ },
61
+ {
62
+ "lat": 30.096082,
63
+ "lon": -93.72764
64
+ },
65
+ {
66
+ "lat": 30.096003,
67
+ "lon": -93.727638
68
+ }
69
+ ],
70
+ "id": "03d519a729349cb55d581b145a780dd3",
71
+ "label": "no damage",
72
+ "pixels": [
73
+ {
74
+ "x": 1116,
75
+ "y": 1128
76
+ },
77
+ {
78
+ "x": 1414,
79
+ "y": 1121
80
+ },
81
+ {
82
+ "x": 1412,
83
+ "y": 1063
84
+ },
85
+ {
86
+ "x": 1114,
87
+ "y": 1069
88
+ },
89
+ {
90
+ "x": 1116,
91
+ "y": 1128
92
+ }
93
+ ],
94
+ "source": "Microsoft",
95
+ "boundary": "0827-B-02.geo.tif"
96
+ },
97
+ ...
98
+ ],
99
+ ...
100
+ }
101
  ```
102
 
103
+ Each JSON file is a dictionary that contains entries where the key is a building id, and each value is a list of all of the instances (views) where that building appears in the dataset's imagery. Each view contains the following information...
104
+ - The "source" field describes the provenance of the building polygon. The possible options are "Microsoft," indicating the building polygon was sourced from the Microsoft Building Footprints dataset, and "custom," indicating the polygons were manually added by the authors.
105
+ - The "id" field is a string that uniquely identifies each building. Building polygons that appear across multiple orthomosaics will share the same id. Each id will only appear once in each orthomosaic.
106
  - The "label" field corresponds to the values of the Joint Damage Scale. The possible options are "no damage", "minor damage", "major damage", "destroyed", and "un-classified".
107
  - The "pixels" field corresponds to the coordinates of the building polygon in the pixel coordinate space of the orthomosaic.
108
  - The "EPSG:4326" field corresponds to the coordinates of the building polygon in the EPSG:4326 coordinate space.