You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the lines_polygons branch (on climada_python) and the openstreetmap data_loader (on climada_petals) taking shape, there's a few reflections on the intersection of those two modules, as well as on some aspects where LitPop plays a role:
Vice versa, detailed map knowledge of where high-value or low-value areas are (such as buildings vs. waterbodies, grassland...) could be used to downscale LitPop exposures as so:
1) Define Low-Value areas
2) Re-assign LitPop values only to places outside low-value areas ("Downscaling")
cf the working-flow that's still left as a stub on climada_petals > feature/osm_expmaker branch (code-wise not really relevant anymore, methods would have to be re-written anyways, more as a conceptual remainder), visually:
I'll leave it here so we can pick up the discussion on which functionalities & disaggregation methods would be useful to have implemented, in the end.
This discussion was converted from issue #290 on October 15, 2025 08:43.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
With the lines_polygons branch (on climada_python) and the openstreetmap data_loader (on climada_petals) taking shape, there's a few reflections on the intersection of those two modules, as well as on some aspects where LitPop plays a role:
LitPop can be used for providing a value estimate of the respective shapes (e.g. buildings, province polygons, ...) - halfway implemented currently, as discussed in the respective thread of the pull request Code Review: Methods to handle lines and polygons with CLIMADA exposures #221
Vice versa, detailed map knowledge of where high-value or low-value areas are (such as buildings vs. waterbodies, grassland...) could be used to downscale LitPop exposures as so:
cf the working-flow that's still left as a stub on climada_petals > feature/osm_expmaker branch (code-wise not really relevant anymore, methods would have to be re-written anyways, more as a conceptual remainder), visually:
I'll leave it here so we can pick up the discussion on which functionalities & disaggregation methods would be useful to have implemented, in the end.
Beta Was this translation helpful? Give feedback.
All reactions