Skip to content

Commit 4924e58

Browse files
authored
Merge pull request #374 from GFDRR/372-minutes
Copy steering committee minutes from 0.3-dev
2 parents 00e14ca + 30d600c commit 4924e58

10 files changed

+766
-7
lines changed
Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
# Minutes of RDLS Technical Steering Committee 2025-2026 NO. 1
2+
3+
19 November 2025 / 08:00-09:00 EDT, 13:00-14:00 GMT / via Teams
4+
5+
## Attendees
6+
Pierre Chrzanowski, Mattia Amadio, Stuart Fraser
7+
8+
**SG members:**
9+
- James Allard, JBA Risk Management
10+
- Rachel Vint, Open Data Services
11+
- Ric Huting, Royal Haskoning
12+
- Tom Russell, Environmental Institute, U. Oxford
13+
- Sam Roeslin, EU JRC
14+
15+
16+
**Agenda**
17+
- Introductions​
18+
- Update ​
19+
- Gates Foundation Funding scope and activities​
20+
- RDLS Team​
21+
- Current state of development​
22+
- Questions, feedback​
23+
24+
25+
## Notes
26+
- Introductions included members' previous and current connection with RDLS
27+
- Rachel - ODS development work especially through 2023
28+
- James - testing schema for JBA, connection through Urban Flood Risk Assessment Framework (UFRA)
29+
- Sam - using RDLS with Risk Data Hub
30+
- Tom - exploring use of RDLS through global work and data on infrastructure
31+
- Ric - working on UFRA but not seeing requests to include RDLS in TORs so haven't used yet
32+
33+
- SF gave presentation RDLS_GF_SG1_Nov25 (saved in same folder as these notes)
34+
- Gave wider context of RDLS in Gates Foudnation funding, connections to scans, etc
35+
- Summarised workplan and activities; team / ecosystem
36+
- Keen to idenify opportunities where RDLS could get profile - example being UCL IPP report (in slides)
37+
38+
- MA gave short demo of MDE - completion through validation to submission; described of the major changes; flagging that this MDE is ahead of online documentation until Feb/March
39+
40+
## Discussion
41+
- SR: How best to contribute feedback?
42+
- SF: repo (but acknowleding there are many, put comments into any if you cant find the right place and we’ll move it if needed). Also email
43+
44+
- PC: Minutes and logo on RDLS communications ok?
45+
- All agree minutes can be online
46+
- Tom checking logo
47+
- Stu to check version logo and get latest/preferred
48+
49+
- Mat demonstrated editor
50+
- Sam – working on losses: good to see more easily the connection with fields - will test and provide feedback
51+
52+
- Communications / outreach
53+
- Bonn technical forum - Sam attending, keen to talk about RDLS; follow up to align.
54+
- Tom – working with UNDRR and UNEP GRID on Global risk metrics - will monitor for possible connections to RDLS
55+
56+
## Actions:
57+
- SF - plan Jan call, 2nd week.
58+
- SF - check logo we have and preferred logo for communications.
59+
- SF - Send urban data review outputs for SG feedback.
60+
- SF - Send slides and github repo links.
61+
- SF/PC - align with Sam on Bonn Tech Forum
62+
63+
64+
65+
66+
67+
68+
69+
70+
Lines changed: 93 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,93 @@
1+
# Minutes of RDLS Technical Steering Committee 2025-2026 NO. 2
2+
3+
14 January 2025 / 11:00-12:00 GMT / via Teams
4+
5+
## Attendees
6+
Pierre Chrzanowski, Mattia Amadio, Stuart Fraser
7+
8+
**SG members:**
9+
- James Allard, JBA Risk Management
10+
- Rachel Vint, Open Data Services
11+
- Ric Huting, Royal Haskoning
12+
- Tom Russell, Environmental Institute, U. Oxford
13+
- Sam Roeslin, EU JRC
14+
15+
16+
**Agenda**
17+
- JKAN and related tools update - feedback​
18+
- RDL Fellows​
19+
- Data pipeline - UFRA, ​
20+
- Current state of development​
21+
- Questions, feedback
22+
23+
24+
## Notes
25+
- JKAN and MDE demo
26+
- Added dataset, now 134
27+
- Features, request for feedback by end of Jan.
28+
29+
- Pipeline update - Stu to make sure Scott doesn't request from JBA; Stu to send Tom relevant links.
30+
31+
- Development - ODS timeline, send a summary of changes and where we would like inputs from the group.
32+
33+
- RDL Fellows: identifying data scientists in WB client countries - greater spread of inputs and users
34+
- FCV countries
35+
- 9 in S-S Africa, one FCV-Nexus program (global)
36+
- Timeline - KO 14 Jan. Snapshot of projects: country, focus, TTLs. Urban focus consistently
37+
- FCV Scan - make it use RDLS metadata.
38+
- JBA - a few countries JBA are active in.
39+
- Tom: PhD student from South Sudan - connect with fellow. Wider program FCDO supported, overlap with Fellow countries.
40+
41+
- Bonn Technical Forum 2025
42+
- One event – two tracks:
43+
- [Regional Pathways for Comprehensive Risk Management for Integrated Disaster Risk Reduction and Climate Action](https://www.undrr.org/event/bonn-technical-forum-2025-regional-pathways-comprehensive-risk-management-integrated-disaster)
44+
- [Accelerating tracking of hazardous events and disasters](https://www.undrr.org/event/bonn-technical-forum-2025-accelerating-tracking-hazardous-events-and-disasters)
45+
- Official release of DELTA Resilience:
46+
- Live demos and ingest of data.
47+
- Audience was a mix of policy and technical participants.
48+
- Technical questions on standards:
49+
- Hazards and assets; some heated discussions.
50+
- DELTA tool follows HIPS for hazards.
51+
- Assets – DELTA tool includes some asset categories from PDNAs (Post-Disaster Needs Assessments) to give flexibility to users. Strong debates between UNDRR and JRC as this approach does not facilitate interoperability between systems; JRC pushed for harmonised/standardised asset categories, UN preferring flexibility.
52+
<img width="976" height="528" alt="image" src="https://github.com/user-attachments/assets/22cc87f3-3a52-474b-838d-beb102c6916d" />
53+
**(Sam - please confirm OK to include this image in notes)**
54+
- Event after – Brussels – Christos attended joint DPEG/DRF group meeting (in person, 8-9 Dec 2025, Brussels):
55+
- DGs ECHO and ECFIN: discussion on European / national loss database and value of connected data.
56+
- Harmonization of data between systems; positive that country representatives understood the message/value.
57+
- Need to see how this will be implemented in practice.
58+
- IFRC GO: taxonomy they're using (GLIDE), EM-DAT classification tree. Luke Caley.
59+
- Overture Foundation – also in touch with JRC? PC: interesting approach.
60+
- Making sure standards can interoperate through different IDs.
61+
- WB might be working more with them.
62+
- First joint meeting of two expert groups: [Expert Group for Disaster Prevention and Risk Management (DPEG)](https://ec.europa.eu/transparency/expert-groups-register/screen/expert-groups/consult?lang=en&do=groupDetail.groupDetail&groupID=3733&news=1) & Disaster Risk Financing (DRF), respectively led by DG ECHO and DG ECFIN
63+
- Provided a valuable platform for dialogue between representatives of national Civil Protection authorities and financial institutions.
64+
- A key message highlighted was that effective disaster risk management requires integrated data and governance systems that support both operational needs (preparedness and prevention) and fiscal needs (budget planning).
65+
- The Risk Data Hub (RDH) team was invited to present on the importance of collecting disaster loss data.
66+
- The RDH was highlighted during the meeting as a critical link between DG ECHO and DG ECFIN and as a starting point for EU-wide harmonised loss data collection.
67+
- Highlighted the value of connected data between regional/local, national, European, and global loss database.
68+
- Need for harmonization of data between the systems.
69+
- Positive: country reps understood the message/value
70+
- Need to see how practically implemented.
71+
<img width="976" height="528" alt="image" src="https://github.com/user-attachments/assets/22cc87f3-3a52-474b-838d-beb102c6916d" />
72+
- JRC discussed with the IFRC GO team
73+
- primary contact at IFRC is Luke CALEY
74+
- IFRC spoke about the work done on the Monty STAC Extension https://ifrcgo.org/monty-stac-extension/
75+
- Interesting work done especially in the Hazard Type Mapping https://github.com/IFRCGo/monty-stac-extension/tree/main/docs/model/sources
76+
77+
78+
## Discussion
79+
- Region grouping on JKAN? - possible - need to decide on a grouping to use - not WB.
80+
- Ric: semantic search is interesting; looking at datasets as well. Useful to have a map search additional to semantic search
81+
- Map function possible: priority is getting lots of data on it, hence lightweight. Not seeking to replicate very nice geoportals.
82+
83+
84+
## Actions:
85+
- Rachel, Tom, Ric, James (and/or colleagues) to provide feedback by end Jan on JKAN functions/features as they are now (requests for map/region search already noted)
86+
- Stu to remind for feedback by end Jan
87+
- Stu to make sure Scott doesn't request from JBA.
88+
- Stu to send Tom relevant links for data review.
89+
- Mat / Stu to send a summary of pertinent changes.
90+
- Pierre to share what he can on RDL Fellow / projects
91+
- Stu to report back on DELTA / RDLS supporting loss catalogues at next SC.
92+
93+
Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
# Minutes of RDLS Steering Committee No. 7
2+
3+
14 September 2023 / 09:00-10:30 EDT, 14:00-15:30 GMT / via Teams
4+
5+
## Attendees
6+
7+
Pierre Chrzanowski, Mattia Amadio, Stuart Fraser (GFDRR)
8+
Rachel Vint, Jen Harris (Open Data Services)
9+
10+
**SC members:**
11+
- Paul Henshaw, GEM Foundation
12+
- Stephen Hutchings, JBA Risk Management
13+
- Nick Moody, IDF/GRMA
14+
15+
**Absent**
16+
- Tiziana Rossetto, UCL EPICentre
17+
- Matt Donovan, ODS
18+
- Beat Aeberhardt, Swiss Re
19+
20+
**Others**
21+
Johanna Carter (ODS)
22+
Hamish Patten (IFRC)
23+
24+
**Agenda**
25+
- Updates to documentation and request for any feedback as you review (Stuart)
26+
- Tools – Availability and use of the metadata creation and validation tool (Jen)
27+
- Update on Fellowship projects and recent workshops (Pierre/Andy/Mattia)
28+
- Communications plan for the RDLS (v0.2) – overview of blogs, webinar plans and channels for communications (Pierre).
29+
- Request for update from Joh/Matt on Oasis integration of RDLS metadata (Joh/Matt)
30+
- Others?
31+
32+
Presentation
33+
https://docs.google.com/presentation/d/1UnudkTN0LqS9_gKT8mLaHxkZ8TxNgeVSYMJeZfVbYBY/edit#slide=id.g149d21ab14c_0_77
34+
35+
## Notes
36+
37+
**Updates to documentation and request for any feedback as you review (Stuart)**
38+
- Request for data documentation: PH: MWI data not his, but checking. GEM data is in the Db format - knew data commonly used by GEM would fit, but interested to see others - agriculture, etc. Suggest to make use of other data - interoperability of data where data is used by others, or produced by others - the value for GEM is not the use of RDLS internally - already document their data in internal formats.
39+
PC: We should communicate on GEM involvement in RDL project - how to keep up on their progress, and how pushing for adoption / adopting the standard.
40+
- NM: Value is clear but what are forces and barriers to adoption. Is adoption clear in WB, or limited to GFDRR currently? PC: Strategy in WB is to go by different sectors, projects first - framework contract for risk assessment - pre-selected set of firms. TOR requests use of RDLS when sharing outputs.
41+
- SF: how can we promote adoption in organisations. SH: TOR are a stick to drive takeup, but support from the RDL that eases the process would be v helpful. PH: Convertors are helpful. Oasis convertors would be helpful. Possible for exposure. More diff for Vuln. Talking about data. HP: modular is nice, each category is clear. IFRC - our data might be able to be converted into format but in some cases it can’t - loss&damage not in the same language. Specific contexts where its 1:1 from differetn standards, examples where there are exceptions where the standard may not align. SF: follow up on examples of misalignment with IFRC.
42+
- PC: tooling component - SC could look at what is needed for development and adoption
43+
44+
**Tools – Availability and use of the metadata creation and validation tool (Jen)**.
45+
- JH: convertor demo. Highlighting errors, link to share metadata for 7 days.
46+
- SH: can we capture (download the errors)
47+
- JC: does the json file get generated with errors? - JH: - yes, with errors contained
48+
- PH: Additional fields added? - JH: Will be added in JSON - present in the object/sheet where you added it in spreadsheet. PH: Is this what we want? Action - consider how to treat add. Fields
49+
- CH: what is ultimate output - for NGOs, etc? Not the tool and validation of data. PC/SF: different levels of outputs - convertor tool is to help technical level of adoption. We will produce videos to promote at higher level - how the RDLS benefits operational projects e.g. on RDLS maximising impact of data generated [this is also the carrot for WB TTLs during internal meetings].
50+
51+
**Fellowship updates**
52+
- AG: Have held several Fellow workshops including SF/MA / HP and own fellows, highlighting Zia and Isa project work. Will be promoting RDLS at Colombia Uni conference, and in WB - and during a week of WB meetings in DC. PC: Dedicated workshop at WB HQ - November 14th. To incl data sprint, in full week of activities.
53+
54+
**Communications plan**
55+
- From Oct 2nd (see presentation for full schedule)
56+
- Request for any specific work done with RDLS to go into blog of organizations in first week of Oct.
57+
- Invitation to present at the external webinar on work done.
58+
- Video tutorials and high-level comms video
59+
- Stakeholder mapping - need to add names, and create links with orgs.
60+
- HP: Links with HDX - could create a bolt-on, ‘would you like to convert your data into RDLS’? - could be a driver of adoption.
61+
- PC - yes - could provide a way to access exposure information. SF: Would want them to host RLDS metadata as first step
62+
- HP: agrees but lots of data types on there - may throw up areas of misalignment.
63+
- NM: Mapaction has a data scientist embedded in HDX - possible useful linkage?
64+
- CH: Would repost if SRF are tagged, wouldn’t have something on their website.
65+
- Blog needs to promote benefits to end users - make it less WB focussed. How can each stakeholder use it.
66+
- External webinars - already in 4 weeks - who is doing invitations
67+
- Need to clarify more for Carolina
68+
- Oct 10th is Swiss holiday
69+
- Do we need different webinars for different audiences? Tech and high level
70+
- PH: really useful to highlight different use cases with different messages. Should be clear that RDLS is bringing advantage to these communities.
71+
72+
73+
**AOB**
74+
75+
## Actions:
76+
- Document what happens with additional fields
77+
- Set up call with HDX
78+
- Set up call with IFRC - loss and damage focus.
79+
- Add high level video production into comms plan. Focus on communicating the benefits to sectors to drive adoption, not tools/validation level technical information.
80+
81+
## Proposed agenda to include:
82+
- Final planned SC meeting under Swiss Re Foundation funding
83+
- Communications, take-up activities since September
84+
- Plan for further SC involvement
85+
86+

0 commit comments

Comments
 (0)