[Property] OED fields update for offshore assets modelling

[jm-moratalla]

Description

We are proposing updates to the OED schema, to allow for coding of offshore renewable assets.
See attached .xlsx for proposed changes.
Cells highlighted yellow, have been edited/added from the original schema.
Unedited rows/tabs have been removed for clarity.

Reasons for change

To allow for coding of offshore renewable assets.

Scope of change

Changes proposed to:

• Location File

Impact of change

• We have updated some offshore FoundationType names and descriptions
• Also, for including liquefaction effects in the calculations, we have identified the need of a new field (SoilLiquefiable), which determines whether the soil is susceptible to liquefaction or not. Description of how this is determined are included in the notes of the attached.
  These changes should only impact models by Renew-Risk, as other models do not yet use the proposed codings, to our knowledge.

Data type, default values, are blanks allowed, list valid values

See attached .xlsx for proposal.
OpenExposureData_Spec-RenewRisk Proposal 240618.xlsx

[johcarter]

Thanks @jm-moratalla

Have reviewed and have the following comments

• As you are changing descriptions only and adding a new field and codes, this would be a minor non-breaking change but would go into the next major OED release v4 as that is the next release.
• You have sent notes for FoundationType 13+, but can you also supply helpful notes for 1-12 which are currently N/A?
• New field SoilLiquefiable - a few suggestions

1. Make data type tinyint with default value 0
2. Make default value 0 mean unknown / or not applicable and shift no and yes to values 1 and 2

Reason for 2: you may not always know if soil is liquefiable or it may not be relevant (for non earthquake locations). If it is unknown then modeller can choose how to map the exposures to vulnerability given the uncertainty.

[jm-moratalla]

Thanks Jo. We have proposed FoundationType 13 onwards, as they relate to offshore, so have provided notes for these. But we have not proposed the onshore foundations, so it perhaps wouldn’t be appropriate for us to propose the notes. As an idea, can these be mostly taken from the GEM taxonomy (i.e. could we perhaps ask someone from GEM to have a look at the onshore ones (i.e. copy across the notes/descriptions from the GEM taxonomy for the most relevant foundation types)? Re your suggestions on SoilLiquefiable, yes these changes are absolutely fine with us. Jose Moratalla Catastrophe Model Developer E: ***@***.*** [A logo with blue and black text Description automatically generated] From: johcarter ***@***.***> Sent: Wednesday, June 19, 2024 12:06 PM To: OasisLMF/ODS_OpenExposureData ***@***.***> Cc: Jose Moratalla ***@***.***>; Mention ***@***.***> Subject: Re: [OasisLMF/ODS_OpenExposureData] OED fields update for offshore assets modelling (Issue #191) Thanks @jm-moratalla<https://github.com/jm-moratalla> Have reviewed and have the following comments * As you are changing descriptions only and adding a new field and codes, this would be a minor non-breaking change but would go into the next major OED release v4 as that is the next release. * You have sent notes for FoundationType 13+, but can you also supply helpful notes for 1-12 which are currently N/A? * New field SoilLiquefiable - a few suggestions 1. Make data type tinyint with default value 0 2. Make default value 0 mean unknown / or not applicable and shift no and yes to values 1 and 2 Reason for 2: you may not always know if soil is liquefiable or it may not be relevant (for non earthquake locations). If it is unknown then modeller can choose how to map the exposures to vulnerability given the uncertainty. — Reply to this email directly, view it on GitHub<#191 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BEL7QMZATJY2B3XAKCVRGZDZIFJYNAVCNFSM6AAAAABJRUDKOGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZYGI4DKOBTGI>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[johcarter]

Under discussion (new field) fyi @aiste-kalinauskaite

[johcarter]

OpenExposureData_Spec-RenewRisk.Proposal.240618_updated.xlsx

Updated proposal as discussed above. Will be implemented if there are no further comments.

[johcarter]

Implemented version attached

OpenExposureData_Spec-RenewRisk.Proposal.240618_updated2.xlsx

[MattDonovan82]

All looks fine - no additional comments from me.