search

OasisLMF / ODS_OpenExposureData

Open data standards curated by Oasis.
61 stars 8 forks source link

Occupancy is only property oriented (can we include motor?) #129

Closed IPE-Pierre closed 10 months ago

IPE-Pierre commented 1 year ago

Reasons for change

OccupancyCode are only covering property and not beyond... An Other 4000 category should be introduced to cover non property exposure ## Scope of change - [ ] Location File OccupancyCode dictionnary ## Impact of change none in terms of code but massive in terms of model. Auto are somehow covered by constructionCode but implied massive duplication in terms of vulnerabilitydict redirection. Occupancy should be rather master categories and constructioncode sub categories. idea being 4000 for non property occupancy 4001 for Auto 4 wheels 4002 for 2 Wheelers etc...
MattDonovan82 commented 1 year ago

@IPE-Pierre As long as there are no duplications to existing occupancy codes and there is a demand for more 'non-property' classes, then these can be added in future, major releases.

Can you propose some codes and descriptions you would like to see added so the community can review them?

IPE-Pierre commented 1 year ago

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns="http://www.w3.org/TR/REC-html40">

OED Code | Name | Description -- | -- | -- 1400 | Auto, unknow type & cover | Unknown Use, type and cover (MTPL / MOD) 1410 | Auto, Personal 4 Wheel unknown cover | Personal car 4-Wheel drive  unknown cover (MTPL/MOD) 1411 | Auto, Personal 4 Wheel MOD | Personal car 4-Wheel drive own damage 1420 | Auto, Personal Moto unknown cover | Personal Moto 2-Wheel drive  unknown cover (MTPL/MOD) 1430 | Auto, Commercial / Utility | commercial utility car 1440 | Auto, Fleet 4 Wheel |   1450 | Auto, Truck |  

aiste-kalinauskaite commented 1 year ago

There are a number of construction codes in OED spec already: image

johcarter commented 1 year ago

From a modellers perspective, it is quite inconvenient to not have auto covered in occupancy codes. It means you have to use both occupancy code and construction code to define vulnerability, and then you end up not supporting most combinations of these two codes.

Perhaps we could consider moving auto codes out of construction and into occupancy? I don't think they would be out of place, considering all the detailed infrastructure types OED now has in occupancy.

Another option would be to identify an auto exposure by a single OccupancyCode so at least a distinct value can be entered rather than leaving it blank and defaulting to 1000 (unknown).

MattDonovan82 commented 1 year ago

I guess it depends on how the models use the codes for their vulnerabilities functions but to me, if we're considering modelling individual automobiles as @IPE-Pierre is suggesting and we ideally only want to use one set of codes, this feels like they should fall more under construction rather than occupancy which as @aiste-kalinauskaite suggests are already present in OED construction.

I suppose this would again be using two different code sets if you need to model both individual vehicles and buildings such as garages or car parks (which are covered under occupancy) together?

MattDonovan82 commented 1 year ago

Including occupancy codes for motor would be a duplication as already present in construction and would be a major change and disruptive. As previously stated, the suggestion is to use a ew single occ code '1400' with the following description.

"Auto - general, to be used in conjunction with the relevant construction codes for auto (5850 - 5875)."

Thoughts? @IPE-Pierre

IPE-Pierre commented 1 year ago

The solution you are proposing is ok for me...

MattDonovan82 commented 11 months ago

Updated as occ code 1260 (auto, general).