hkayabilisim commited on
Commit
1c8c8b5
·
1 Parent(s): 27dd195

Extended the documentation

Browse files
tomorrowcities/content/articles/data.md CHANGED
@@ -51,18 +51,33 @@ The layers supported by tomorrowcities are listed below. In this section, we wi
51
  ### Buildings
52
  Buildings are the core component of visioning scenarios. The features of the building with some example data are shown below:
53
 
54
- |zoneID| bldID | nHouse | residents | specialFac | expStr | fptarea | geometry |
55
  |------|-------|--------|-----------|------------|-----------------|---------|--------------|
56
  |4 | 17 | 41 | 178 | 0 |RCi+HC+18s+ResCom| 111 | MultiPolygon |
57
 
58
 
59
  where
60
 
61
- * **zoneID (integer)** refers to the unique identitifer of the zone that building is located in. The features of the corresponding zone is described in a dedicated zone table.
62
- * **bldID (integer)** is a unique building identifier.
63
- * **nHouse (integer)** is the number of household in that building.
64
  * **residents (integer)** stores the number of individual live in the building.
65
- * **expStr (string)**
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
66
 
67
  ### Intensity Measures
68
  Whether it is flood, debris or earthquake, every hazard map should contain at least two properties: a point geometry and intensity measure denotes by 'im'. The data can be provided via GeoTIFF or GeoJSON format. TIFF files should contain CRS
 
51
  ### Buildings
52
  Buildings are the core component of visioning scenarios. The features of the building with some example data are shown below:
53
 
54
+ |zoneid| bldid | nhouse | residents | specialfac | expstr | fptarea | geometry |
55
  |------|-------|--------|-----------|------------|-----------------|---------|--------------|
56
  |4 | 17 | 41 | 178 | 0 |RCi+HC+18s+ResCom| 111 | MultiPolygon |
57
 
58
 
59
  where
60
 
61
+ * **zoneid (integer)** refers to the unique identitifer of the zone that building is located in. The features of the corresponding zone is described in a dedicated zone table.
62
+ * **bldid (integer)** is a unique building identifier.
63
+ * **nhouse (integer)** is the number of household in that building.
64
  * **residents (integer)** stores the number of individual live in the building.
65
+ * **expstr (string)**
66
+
67
+ ### Households
68
+ Households are defined in a tabular format whose attributes are shown below:
69
+
70
+ |bldid|hhid|income|nind|commfacid|
71
+ |-----|----|------|----|---------|
72
+ |17 |12 |lowIncomeA|3|3643|
73
+
74
+ where
75
+
76
+ * **bldid (integer)** is the building identifier where the household is located in
77
+ * **hhid (integer)** is the unique identifier for the household
78
+ * **income (string)** is the income level of the household
79
+ * **nind (integer)** is the number of individuals living in the household
80
+ * **commfacid (integer)** is the building identifier of the community facility. In Tomorrow's Cities, it is used to define the hospital associated with the household.
81
 
82
  ### Intensity Measures
83
  Whether it is flood, debris or earthquake, every hazard map should contain at least two properties: a point geometry and intensity measure denotes by 'im'. The data can be provided via GeoTIFF or GeoJSON format. TIFF files should contain CRS
tomorrowcities/content/articles/metrics.md CHANGED
@@ -14,12 +14,12 @@ category:
14
  [TOC]
15
 
16
  ## Metrics
17
- There are seven fundamental impact metrics displayed in the web application. For each them there is an associcated threhold but for the sake of simplicity, it is not explicitly stated.
 
 
18
 
19
  ### Metric 1: Number of workers unemployed
20
- It denotes the number of invidivuals who last their jobs either due to a severe damage at the workplace
21
- or lost access to a functional workplace. When the metrics is displayed on a building-level, it is the sum of
22
- such individuals living in that building.
23
 
24
  ### Metric 2: Number of children with no access to education
25
  Similar to the first metrics but individual here refers to a child who is associated with a school.
@@ -27,8 +27,11 @@ The metric becomes active if the school is damaged or not accessible.
27
 
28
  ### Metric 3: Number of households with no access to hospital
29
  The number of households who lost its access to its associated hospital.
30
- Either hospital is damaged or the path between the household and the hospital
31
- is broken.
 
 
 
32
 
33
  ### Metric 4: Number of individuals with no access to hospital
34
  It is derived from metric 3 by counting the individuals in the corresponding households.
 
14
  [TOC]
15
 
16
  ## Metrics
17
+ There are seven fundamental impact metrics displayed in the web application.
18
+ Their calculations heavily depend on the damage state of buildings and/or other
19
+ infrastructural elements such as electrical power generators, roads or bridges.
20
 
21
  ### Metric 1: Number of workers unemployed
22
+ It denotes the number of invidivuals who lost their jobs either due to a damage at the workplace or lost access to a workplace. When the metrics is displayed on a building-level, it is the total number of such individuals living in that building.
 
 
23
 
24
  ### Metric 2: Number of children with no access to education
25
  Similar to the first metrics but individual here refers to a child who is associated with a school.
 
27
 
28
  ### Metric 3: Number of households with no access to hospital
29
  The number of households who lost its access to its associated hospital.
30
+ Access is lost when any of the following conditions hold:
31
+
32
+ * the damage state of the associated hospital is beyond a threshold
33
+ * the associated hospital is inaccessible via transportation network
34
+ * the associated hospital has no electricity
35
 
36
  ### Metric 4: Number of individuals with no access to hospital
37
  It is derived from metric 3 by counting the individuals in the corresponding households.
tomorrowcities/content/articles/road.md CHANGED
@@ -20,28 +20,40 @@ earthquake and flood damage assessment on road networks.
20
  ## Quick Start
21
  For the impatient readers, here is a quick road to conduct road network analysis.
22
 
23
- * Download [Sample Dataset](https://drive.google.com/file/d/1BGPZQ2IKJHY9ExOCCHcNNrCTioYZ8D1y/view?usp=sharing)
24
- * Go to https://huggingface.co/spaces/hkayabilisim/app-engine/engine
25
- * Go the [Engine](/engine)
26
- * Drag and drop the following files inside sample dataset to the engine:
27
- * rapti_road_edges.geojson
28
- * rapti_road_nodes.geojson
29
- * rapti_road_fragility.xlsx
30
- * rapti_flood_max_depth_70yr_future_212mm_05.tif
31
- * rapti_dummy_individual.json
32
- * rapti_dummy_household.json
33
- * rapti_dummy_buildings.geojson
34
- * Unselect *Building*
35
- * Select Road and Earthquake for infrastructure and hazard type, respectively.
36
- * Click Calculate to run the engine.
 
 
 
 
 
 
37
 
38
  When completed successfully:
39
 
40
  * The damage state of the bridges will be shown in the *ds* attribute of the *road edges* layer.
41
  * In the same layer, you will see the boolean *is_damaged* attribute.
42
  * The roads in the *road edge* layer will also be colored red if *is_damaged* attribute is true.
43
- * Every building will have a new attribute called *nearest_road_node* which determines the nearest junction point
44
  of the transportation network. When you click the buildings, this information will be shown in details view.
 
 
 
 
 
 
45
 
46
  ## Data
47
  From a computational point of perspective, a road transportation network is a bi-directional graph
@@ -104,9 +116,8 @@ Whereas a sink is a node where hospitals are associated.
104
 
105
  ### Earthquake
106
  * Unlike flood, in earthquake we don't need to create a buffer around roads. Instead,
107
- we simply find the nearest intensity measure to the road.
108
 
109
- After
110
 
111
  ### Parameters
112
  As you may notice, there are several parameters used in the calculations. Let's summarize them here:
 
20
  ## Quick Start
21
  For the impatient readers, here is a quick road to conduct road network analysis.
22
 
23
+ * Go to engine
24
+ * Download [Sample Dataset](https://drive.google.com/file/d/1BGPZQ2IKJHY9ExOCCHcNNrCTioYZ8D1y/view?usp=sharing) to your local environment and unzip the archive file.
25
+ * Drag/drop following files in the sample dataset to the drop zone of the engine.
26
+ rapti_dummy_buildings.geojson
27
+ rapti_dummy_earthquake_fragility.xlsx
28
+ rapti_dummy_household.json
29
+ rapti_dummy_individual.json
30
+ rapti_dummy_landuse.geojson
31
+ rapti_flood_max_depth_20yr_future_173mm_05.tif
32
+ rapti_road_edges.geojson
33
+ rapti_road_fragility.xlsx
34
+ rapti_road_nodes.geojson
35
+ * Select **building** from the infrastructure, **earthquake** from hazard and click **calculate**
36
+ * Observe the metrics populating. Please note that metric3 (number of households with no access to hospitals) is zero because the only hospital in the exposure is not affected.
37
+ * Now also select **road** from the infrastructure and click **calculate**
38
+ * Observe that the metric3 will be non-zero because there will be many buildings which lost access to the hospital due to the damaged bridges in the transportation network.
39
+
40
+ <video width="853" controls>
41
+ <source src="https://github.com/TomorrowsCities/tomorrowcities/assets/2515171/ec2dc36d-fe76-42fb-b9be-47a1690374de" type="video/mp4">
42
+ </video>
43
 
44
  When completed successfully:
45
 
46
  * The damage state of the bridges will be shown in the *ds* attribute of the *road edges* layer.
47
  * In the same layer, you will see the boolean *is_damaged* attribute.
48
  * The roads in the *road edge* layer will also be colored red if *is_damaged* attribute is true.
49
+ * Every building will have a new attribute called *node_id* which determines the nearest junction point
50
  of the transportation network. When you click the buildings, this information will be shown in details view.
51
+ * In **building** and **household** layers, a new attribute (**hospital_acccess**) will be shown to indicate
52
+ the accessibility of hospital. For a household, it implies the accessibility of associated hospital whereas,
53
+ for a building it means that the building can access to at least one *hospital node* which is simple a node in the
54
+ transportation network for which a hospital is assigned to.
55
+ * The third metric, which is the number of households with no access to hospitals, will be non-zero when **road**
56
+ infrastructure is selected for analysis.
57
 
58
  ## Data
59
  From a computational point of perspective, a road transportation network is a bi-directional graph
 
116
 
117
  ### Earthquake
118
  * Unlike flood, in earthquake we don't need to create a buffer around roads. Instead,
119
+ we simply find centroid of the bridge and find closest intensity measure to the centroid.
120
 
 
121
 
122
  ### Parameters
123
  As you may notice, there are several parameters used in the calculations. Let's summarize them here:
tomorrowcities/content/articles/welcome.md CHANGED
@@ -17,6 +17,16 @@ category:
17
  TCDSE is a web application designed to conduct computational tasks to generate information needed for decision mechanisms in designing future cities. The web application, which will be referred as TCDSE for short, contains a computational engine capable of executing several hazard scenarios on different exposure datasets and infrastructures.
18
 
19
  ## What is New?
 
 
 
 
 
 
 
 
 
 
20
  **v0.2**
21
 
22
  * Transportation network analysis for flood and earthquake damage assessment
@@ -47,41 +57,55 @@ TCDSE is a web application designed to conduct computational tasks to generate i
47
  when clicked.
48
  * Implementation Capacity Score is added. If medium or low is selected, then building-level metrics is increased by 25% and 50%, respectively. If high is selected, there is no change in the metrics.
49
 
50
- ### New policies
51
- * Eight new policies are added. See their definitions [here](/docs/policies)
52
- * New info related to flood damage assessment is added [here](/docs/flood)
 
 
 
 
 
 
53
 
54
- ### Policy Support
55
- Two new policies are added to the computing engine. More info is [here](/docs/policies)
56
 
57
- ### Excel support:
58
- You can upload Excel files containing your tabular data such as individual, household, fragility or vulnerability data. However, processing excel files is very slower than processing JSON files so I definitely suggest working with JSON files. You can convert your Excel files via panda framework. The platform also does not try to convert the coordinates even if there is any in the Excel file because there is no way to know which columns represent the coordinates or coordinate reference systems without metadata. So Excel spreadsheets should be used to provide non-geo related tabular data. So please use them only for data not containing any geo-specific information.
 
 
 
59
 
60
- ### Dar Es Salaam Study
61
- [Sample Dataset](https://drive.google.com/file/d/1BGPZQ2IKJHY9ExOCCHcNNrCTioYZ8D1y/view?usp=sharing) now contains some visioning scenario for Dar Es Salaam case.
62
 
63
  ## Features
64
  General capabilities/features of the web application can be summarized as follows:
65
 
66
-
67
  *Hazard Scenarios*
68
 
69
  * Earthquake
70
  * Flood
71
- * Debris
72
 
73
  *Exposure Scenarios*
74
 
75
  * Buildings
76
  * Power networks
77
  * Transportation
78
- * Water networks
79
 
80
  *Impact Metrics*
81
 
82
  * Building and infrastructure-level damage states
83
  * Household and individual-level derived metrics
84
 
 
 
 
 
 
 
 
 
 
 
85
  *Visualization*
86
 
87
  * GIS Maps
@@ -92,7 +116,8 @@ General capabilities/features of the web application can be summarized as follow
92
  *Data structure*
93
 
94
  * GeoJSON format for geospatial data
95
- * Vanilla JSON for non-geospatioal tabular data
 
96
 
97
  *Software*
98
 
@@ -100,25 +125,4 @@ General capabilities/features of the web application can be summarized as follow
100
  * Reactive user interface via Solara
101
  * geospatial database via postgis
102
  * Leaflet backend for maps
103
- * Easy deployment to cloud
104
-
105
-
106
- ## Quickstart
107
- * Download [Sample Dataset](https://drive.google.com/file/d/1BGPZQ2IKJHY9ExOCCHcNNrCTioYZ8D1y/view?usp=sharing) to your local environment and unzip the archieve file.
108
- * Go to [engine](/engine)
109
- * Drag/drop necessary files to the drop zone of the engine and execute the engine. A sample session is displayed below.
110
- * The impact metrics will be immediately seen on the page.
111
-
112
- <video width="853" controls>
113
- <source src="https://github-production-user-asset-6210df.s3.amazonaws.com/2515171/270064030-0733ad34-0a7f-445e-86fb-9a61df4e2969.mp4" type="video/mp4">
114
- </video>
115
-
116
- In case the file names in the video are not clearly seen, they are:
117
-
118
- * nairobi_business_buildings.geojson
119
- * nairobi_business_household.json
120
- * nairobi_business_individual.json
121
- * nairobi_earthquake_fragility.json
122
- * nairobi_earthquake_intensity.geojson
123
-
124
- The used files above satisfy minimum requirements to run Earthquake analysis on buildings.
 
17
  TCDSE is a web application designed to conduct computational tasks to generate information needed for decision mechanisms in designing future cities. The web application, which will be referred as TCDSE for short, contains a computational engine capable of executing several hazard scenarios on different exposure datasets and infrastructures.
18
 
19
  ## What is New?
20
+
21
+ **v0.2.1**
22
+
23
+ * [27dd195](https://github.com/TomorrowsCities/tomorrowcities/commit/27dd195a240cbb97a97d124fc9b132ee2ea1f5e9) Integrated road network analysis into metric3
24
+ * [de6fbca](https://github.com/TomorrowsCities/tomorrowcities/commit/de6fbca8d8b03d350096190ae35646f47a9a0414) Changed engine layout to be more compact
25
+ * [bc436b6](https://github.com/TomorrowsCities/tomorrowcities/commit/bc436b62c35f66b7432e40ca5e6c47364690c8f3) Bugfix a layout problem in engine page
26
+ * [0b1cd96](https://github.com/TomorrowsCities/tomorrowcities/commit/0b1cd96149e129de30e5524f8956db1569202450) Bugfix in metric calculation: a typo in code_level
27
+ * Extended documentation in welcome, data, metrics, and road pages.
28
+ * Added [a demonstration video](https://github.com/TomorrowsCities/tomorrowcities/assets/2515171/ec2dc36d-fe76-42fb-b9be-47a1690374de) to GitHub discussion page[discussion](https://github.com/TomorrowsCities/tomorrowcities/discussions/6).
29
+
30
  **v0.2**
31
 
32
  * Transportation network analysis for flood and earthquake damage assessment
 
57
  when clicked.
58
  * Implementation Capacity Score is added. If medium or low is selected, then building-level metrics is increased by 25% and 50%, respectively. If high is selected, there is no change in the metrics.
59
 
60
+ ## Quickstart
61
+ * Download [Sample Dataset](https://drive.google.com/file/d/1BGPZQ2IKJHY9ExOCCHcNNrCTioYZ8D1y/view?usp=sharing) to your local environment and unzip the archieve file.
62
+ * Go to [engine](/engine)
63
+ * Drag/drop necessary files to the drop zone of the engine and execute the engine. A sample session is displayed below.
64
+ * The impact metrics will be immediately seen on the page.
65
+
66
+ <video width="853" controls>
67
+ <source src="https://github-production-user-asset-6210df.s3.amazonaws.com/2515171/270064030-0733ad34-0a7f-445e-86fb-9a61df4e2969.mp4" type="video/mp4">
68
+ </video>
69
 
70
+ In case the file names in the video are not clearly seen, they are:
 
71
 
72
+ * nairobi_business_buildings.geojson
73
+ * nairobi_business_household.json
74
+ * nairobi_business_individual.json
75
+ * nairobi_earthquake_fragility.json
76
+ * nairobi_earthquake_intensity.geojson
77
 
78
+ The used files above satisfy minimum requirements to run Earthquake analysis on buildings.
 
79
 
80
  ## Features
81
  General capabilities/features of the web application can be summarized as follows:
82
 
 
83
  *Hazard Scenarios*
84
 
85
  * Earthquake
86
  * Flood
 
87
 
88
  *Exposure Scenarios*
89
 
90
  * Buildings
91
  * Power networks
92
  * Transportation
 
93
 
94
  *Impact Metrics*
95
 
96
  * Building and infrastructure-level damage states
97
  * Household and individual-level derived metrics
98
 
99
+ *Policies*
100
+
101
+ * 20 [policies](/docs/policies) related to damage mitigation
102
+
103
+ *[Sample Dataset](https://drive.google.com/file/d/1BGPZQ2IKJHY9ExOCCHcNNrCTioYZ8D1y/view?usp=sharing)*
104
+
105
+ * Dar Es Salaam
106
+ * Rapti
107
+ * Nairobi
108
+
109
  *Visualization*
110
 
111
  * GIS Maps
 
116
  *Data structure*
117
 
118
  * GeoJSON format for geospatial data
119
+ * Vanilla JSON and Excel for non-geospatioal tabular data
120
+ * XML support for [Global Vulnerability Model](https://github.com/gem/global_vulnerability_model)
121
 
122
  *Software*
123
 
 
125
  * Reactive user interface via Solara
126
  * geospatial database via postgis
127
  * Leaflet backend for maps
128
+ * Easy deployment to cloud