Exposure data in CLIMADA #667

Activity

1. aleeciu

   assigned

   aleeciu

   ,

   chahank

   ,

   peanutfun

   and

   emanuel-schmid

   on Mar 1, 2023
2. thomini commented on Mar 2, 2023

   

   thomini

   on Mar 2, 2023

   More actions

   I am happy to share some code, how I import exposure data as a CLIMADA-user.

   1. Exposure = Population Count from .shp

   import geopandas as gpd
   from climada.entity import Exposures
   
   data = gpd.read_file('../../population2020.shp')
   # change CRS - original is 3035 
   data.to_crs(epsg=4326, inplace=True)
   
   exp = Exposures(data) 
   exp.ref_year = 2020 
   exp.value_unit = 'Population Count'
   exp_pts = exp.copy() 
   # change geometry & set lat lon
   exp_pts.gdf['geometry'] = exp_pts.gdf['geometry'].centroid 
   exp_pts.set_lat_lon() 
   exp_pts.gdf['value'] = exp_pts.gdf['count'] 
   
   exp_pts.check()

   This is of course the most easy way, when I was working with pure population count. I had also a case where e.g., based on some variables of the gdf, I split the exposure in age-classes. In general I always would do that prior to creating an Exposures instance. (e.g. Heat impacts)

   2. Exposure = Asset Values from polygons

   E.g. using a version of the BEAM dataset (https://emergency.copernicus.eu/mapping/list-of-components/EMSN123)

   import geopandas as gpd
   from climada.entity import Exposures
   import climada.util.lines_polys_handler as u_lp
   
   beam_df = gpd.read_file('../../country.shp')
   
   # needed because otherwise the lat lon calculation in the next steps is not working properly 
   beam_df.to_crs(epsg=4326, inplace=True) 
   # transforming from polygones to points 
   # each point gets average value within polygon
   beam_pts = u_lp.exp_geom_to_pnt(
       Exposures(beam_df), 
       res=100,
       to_meters=False, 
       # note: res is always the unit of the coordinate system used in exposure (in this case it is meters) 
       disagg_met=u_lp.DisaggMethod.DIV, 
       disagg_val=None ) 
   
   # setting the reference year and the value of the unit: 
   beam_pts.ref_year = 2022 
   beam_pts.value_unit = 'EUR'
   
   exp_pts.check()

   Hope that this is of help!

   If you see anything which can be done more professional, I am happy for feedback.

   👍React with 👍1Reacted by Chahan M. Kropf
3. aleeciu commented on Jul 31, 2023

   

   aleeciu

   on Jul 31, 2023

   CollaboratorAuthor

   More actions

   A late follow-up on this. I am quite aligned with @thomini : not too fancy things should be needed to load most of exposure data out there. Yet, sometimes some handling is needed. Here are a collected few examples:

   https://github.com/ChrisFairless/nccs-supply-chain/blob/main/docs/exposures.ipynb

   so the question remains, does it make sense to have a place (stand alone file, ad hoc class) in CLIMADA to easien access to all these various exposures ?
4. chahank commented on Jul 31, 2023

   

   chahank

   on Jul 31, 2023

   Member

   More actions

   I still do not really understand what you are thinking of, but sure, why not. Can you make a proposal?
5. aleeciu commented on Jul 31, 2023

   

   aleeciu

   on Jul 31, 2023

   Last edited by aleeciu

   CollaboratorAuthor

   More actions

   mmh, actually there are several options/proposals listed above... I think this issue is about finding what is desired way forward.. or we simply close it.
6. chahank commented on Jul 31, 2023

   

   chahank

   on Jul 31, 2023

   Member

   More actions

   Yes, indeed! Sorry for not being clear. What I meant is an actual simple example of how you would think of implementing you favorite options from the ones above.

   I do not really see at the moment how something more general than having all the methods from GeoPandas, direct imports from all OpenStreetMap, as well as functions to handle all polygons an lines, which are all currently available, would look like. Thus, an example from your side would help tremendously.

   The only example I can see from the attached notebook that might benefit from extra methods are the handling of netcdf files. This can be easily solved by writing a from_netcdf method for the exposures class. Would you like to implement this?

   Also, concerning the API, we already have exposures data on it, so please feel free to add more.

   Finally, maybe someone else sees a more general implementation, so we can well expand the discussion!
7. CLIMADA-project

   locked and limited conversation to collaborators on Jul 31, 2023
8. chahank

   converted this issue into a discussion #759 on Jul 31, 2023