Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Proposal] Vulnerability category codelist #76

Closed
odscrachel opened this issue May 24, 2023 · 13 comments · Fixed by #124
Closed

[Proposal] Vulnerability category codelist #76

odscrachel opened this issue May 24, 2023 · 13 comments · Fixed by #124
Assignees
Labels
exposure Issues related to Exposure data proposal New feature or request vulnerability Issues related to Vulnerability data

Comments

@odscrachel
Copy link
Contributor

What is your proposed change?

To create a new codelist for the field category within the vulnerability component.

Title Field name Description Type Codelist
Exposure category category The category of the assets described in the dataset. string population, buildings, infrastructures, agriculture, natural environment
@odscrachel odscrachel added the proposal New feature or request label May 24, 2023
@matamadio
Copy link
Contributor

matamadio commented May 25, 2023

This is the same field as present in the exposure component (#62) - can be used to link the two components.
Should it be fixed, or could it be an open list? Expecting some datasets might have a particular level, e.g. infrastructures (roads).

@stufraser1
Copy link
Member

This was intended as a high level category. Roads, rail, etc would be specified in taxonomy

@duncandewhurst
Copy link
Contributor

What is the proposed codelist based on? I'm unclear on the difference between buildings and infrastructure, e.g. would an exposure dataset about schools be classified as buildings or infrastructure?

@matamadio
Copy link
Contributor

matamadio commented May 29, 2023

From the original documentation about exposure, schema.

immagine
It is basically the way that GED4ALL frames it.
Note that:

  • we added Population
  • we split Agriculture (crops, livestock) and Natural environment (forestry)

I'm unclear on the difference between buildings and infrastructure, e.g. would an exposure dataset about schools be classified as buildings or infrastructure?

Buildings refer to residential, commercial and industrial buildings.
Infrastructures refer to lifelines (transport, electricity network etc) and public-use buildings (such as schools, hospitals, fire stations etc).

@duncandewhurst
Copy link
Contributor

Thanks! That makes sense. I've drafted descriptions for the codes based on GED4ALL.

The only one I'm unsure about is 'population'. Please could you provide a description for that code? I also think that 'people' would fit better with the other codes than 'population'.

Is it usual practice in disaster risk management to consider people as an asset? If not, we might need to reword the description of category.

Code Title Description
population Population
buildings Buildings Residential, commercial and industrial buildings.
infrastructure Infrastructure Infrastructure, including transport, communications, energy, water, health and education facilities.
agriculture Agriculture Agriculture, including crops, livestock and agribusiness.
naturalEnvironment Natural environment The natural environment, including forestry and other types of vegetation.

@stufraser1
Copy link
Member

@matamadio
I propose to include health and education and other public buildings in buildings with R/C/I.
Of course we refer to schools, hospitals as critical infrastructure, but I would also describe them in an analysis as public buildings. They fit better into buildings conceptually when people think about the asset type, with infrastructure being reserved for systems or network and points that transport, comms, supply infrastructure fall into.

@matamadio
Copy link
Contributor

matamadio commented May 30, 2023

That is true, population isn't strictly a location-fixed "asset", except it is often treated like it is: an indication of the density of exposed value in one place, and driver of the mortality losses in that place.
GED4ALL considers population in a separate category.

immagine

However that fits more with our Vulnerability - Socio-economic indicators component, in terms of use-case application.

@matamadio
Copy link
Contributor

matamadio commented May 30, 2023

@matamadio I propose to include health and education and other public buildings in buildings with R/C/I. Of course we refer to schools, hospitals as critical infrastructure, but I would also describe them in an analysis as public buildings. They fit better into buildings conceptually when people think about the asset type, with infrastructure being reserved for systems or network and points that transport, comms, supply infrastructure fall into.

Yes that makes sense, than it would be:

Code Title Description
population Population People
buildings Buildings Residential, commercial, industrial and public-service buildings such as education, healthcare, governmental buildings, etc.
infrastructure Infrastructure Lifelines infrastructure, including transport, communications, energy, water.
agriculture Agriculture Agriculture, including crops, livestock and agribusiness.
naturalEnvironment Natural environment The natural environment, including forestry and other types of vegetation.

@stufraser1
Copy link
Member

Great, I've aded edu and hlth in description to make it clear.

@odscrachel odscrachel added the vulnerability Issues related to Vulnerability data label May 30, 2023
@duncandewhurst
Copy link
Contributor

Regarding population density, it still seems not to fit with the other codes to me. If I understood correctly, the purpose of the field and codelist is to categorise what is exposed to risk. So it makes sense to say, for example, "buildings are exposed to risk". It doesn't make sense to say that "population density is exposed to risk" because population density is a measurement rather than an asset. I think that 'people' would be a better fit with the nature of the other codes. Would that work from your perspective?

It still seems a bit odd to describe people as an asset, but that could be addressed by updating the description of category.

Otherwise, the changes look good :-)

@stufraser1
Copy link
Member

Updated description to people

@odscjen odscjen added the exposure Issues related to Exposure data label Jun 23, 2023
@odscjen
Copy link
Contributor

odscjen commented Jun 23, 2023

also related to #62 as this codelist will be referenced in Exposure.category as well

@odscjen
Copy link
Contributor

odscjen commented Jun 26, 2023

codelist updated in #101, leaving this issue open as it still needs updating in Vulnerability

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exposure Issues related to Exposure data proposal New feature or request vulnerability Issues related to Vulnerability data
Projects
None yet
5 participants