Humanitarian OSM Team/HDX Disaster Data

An example: HDX page containing OSM data for Mozambique Floods in 2026

HOT Disaster Mapping on HDX: Standard Operating Procedure

Fist created: November 2025
First drafted by: Melanie Rabier (HDX), Sam Colchester (HOT)

Goal & Scope

This Wiki establishes a standard process to bring essential disaster mapping data onto HDX when sudden onset disasters occur. See this OSM Diary post for more background information.

Key Principles

• One single dataset per event (e.g., "Myanmar Earthquake, March 2025") which includes files covering all relevant OSM data: buildings, roads, etc.
• Dataset descriptions will include GLIDE number or other necessary identification to help users easily find the dataset in relation to specific events.
• The process will be manual in the first phase. After evaluation of feasibility and needs, a decision can be taken to invest in automating some tasks.
• Single point of contact established at both HOT and HDX for coordination.
• Process documented in a shared Wiki page (here) accessible to both organisations.
• Review scheduled after 3–4 activations to assess automation or improvement opportunities (this was carried out in May 2026).

Procedure

Stage 1. Assessment and Trigger

1. Disaster occurs.
2. HOT conducts completeness assessment (documented here).
3. HOT triggers an Activation.
4. HDX is informed and assesses if an event is of interest for dataset creation.

Some criteria to support assessment:

• To include on HDX:
  • Prioritisation of Humanitarian Needs and Response Plan (HNRP) countries.
• To not include on HDX:
  • Small-scale localised incidents with minimal humanitarian impact.
  • Events where data sharing restrictions or security concerns prevent public release.

Stage 2. Dataset Creation and First Upload

Step 1: Identify Disaster/Priority Area

HOT to provide the disaster/priority area boundary (GeoJSON) via email.

• This ensures the data exported reflects the needs of the community and organisations responding to the disaster.
• The file provided could be at admin level 3, 4, or both merged; a merge of all Tasking Manager projects; a GDACS event shape; or a polygon shared by a community/responder in the country (custom priority area).
• The boundaries might change slightly in the first couple of days of response.

Once downloaded, save a copy to HDX Google Drive under: HOT > Disaster Mapping > Disaster Mapping Activation (note that this drive has restricted access) and create a new folder using the convention: [Country] - [Disaster Name] - [GLIDE Number] - [Day Month Year]

Step 2: Export Data

HDX focal point to generate the export using the HOT Export Tool, using the provided GeoJSON as boundaries.

1. Login with your OSM account.
2. Click 'Start Exporting'.

A — Describe

• Add a name (mandatory; does not have to be unique).
• Other fields are optional — do not include project or description.

B: Selecting the right formats in the Export Tool

B — Formats

• GeoJSON
• Shapefile

C: Selecting the right features in the Export Tool

C — Data

• Select only one feature type at a time and export individually, to upload to HDX as separate GeoJSON + Shapefile files.
• This means, if you need to export buildings and roads, you will go through this process twice, once for buildings, once for roads.

Mandatory exports:

• Buildings (all)
• Transportation: roads

Optional exports (based on disaster type and activation):

• Healthcare (all)
• Transportation: railway
• Water: water point, waterway
• Education

D: Final check and unselecting options in Export Tool

D — Summary

• Check everything is correct before importing the boundaries and exporting.
• Unselect all options.
  • No need to select "Publish this export" (leave unchecked).
  • Do not select "Include user info on exports" — this would create PII issues on HDX.
• Do not click "Create Export" just yet.

E: Import area of interest into Export Tool

E — Map / Area of Interest

• On the right-hand side of the map, there are multiple options to draw or import the correct boundaries/area of interest.
• Recommended option: import the GeoJSON (5 MB max).
• Check the boundaries.

F — Create Export (Summary panel)

• Click 'Create Export'.

The export tool will download a zipped file containing the boundaries and data for the specific tag (building, road, etc.). Repeat for all required tags (Step C — Data).

Additional notes:

• For more information on the export tool, check the "Learn" section — especially useful for limitations such as maximum node count (10,000,000 nodes).
• During large activations, the area of interest may be split into multiple non-contiguous polygons. If so, note that:
  • The export tool cannot accommodate multiple polygons (it must be one continuous area).
  • HDX and HOT to discuss the process based on the event type and area. Options include:
    • Download features for each area separately (e.g., area1 - buildings, area2 - buildings) and upload as-is.
    • Download features for each area separately and merge into one file per feature (e.g., area1+2 - buildings, area1+2 - roads).

Step 3: Create Dataset on HDX

HDX focal point will create a new dataset on HDX using the template below and under the HOT organisation page (contributor).

• Upload all of the files previously exported.
• Files will be separated by features and provided in 2 different formats each (geojson, shapefile).
  • Always include buildings, roads.
  • Based on disaster type include other features (e.g.: powergrid, waterways, etc.)
  • Upload each type of feature as a separate file in both formats (e.g.: one GeoJSON and .shp for building, one GeoJSON and .shp for roads, one GeoJSON and .shp for waterways, etc).

Required Fields:

Field	Value
Title	[Country] [Disaster Type] [Month Year] - OpenStreetMap Data E.g.: Myanmar - Earthquake - March 2025 - OpenStreetMap Data
Time period of the dataset	Date range from first export date (start) to latest export (end)
Frequency of Update	See Section 3 — Updates. Start with every 2 days.
Data Source	OpenStreetMap contributors
HDX Tags	facilities-infrastructure natural disasters geodata transportation (for roads); Include the disaster type, for example cyclones-hurricanes-typhoons flooding earthquake-tsunami; If included in feature type add rivers (for waterways) populated places-settlements (for populated places).
Location	Country of the event (multiple countries possible if cross-border)
Contributor	Humanitarian OpenStreetMap Team (HOT)
Methodology	Crowdsourced disaster mapping
License	Open Database License (ODC-ODbL)
File Formats	Automatic - will be GeoJSON and shapefile

Description Template:

This dataset contains OpenStreetMap data exported from the HOT disaster mapping response to [disaster name] - [GLIDE Number].

[Brief disaster context and location — 1 sentence]

The data has been contributed by volunteers through the Humanitarian OpenStreetMap Team's Tasking Manager and represents [buildings, roads], and other critical infrastructure in the affected area. It is updated [frequency] as mapping progresses. Subscribe to this dataset to be notified of any new updates.

This dataset includes all OpenStreetMap features in the area of interest for this event, covering:

• Buildings
• Roads and transportation networks
• [Other relevant features]

Tasking Manager Projects: [Number] projects included (see list: [link to HOT activation page/wiki])
Contributors: [Number if available]

Stage 3. Updates

Update Frequency

Phase	Timeframe	Frequency
Active mapping phase	First 2 weeks	Every 2–3 days
Sustained mapping phase	Weeks 2–6	Weekly
Closing phase	After 6 weeks	Bi-weekly or as needed

These can be adjusted based on the needs of a specific activation.

Update Process

1. Re-export using the same geographic and data (tag) parameters.
2. Re-upload the same resources to the dataset (this overwrites existing files; data is augmented with each export).
3. Update the dataset date range — the end date should reflect the day of the new export.
4. Update the description as needed to document any changes (new features added, new frequency, change in areas/boundaries, etc.).
5. The "Last Updated" field will update automatically.

Stage 4. Maintenance & Archiving

New exports will no longer be generated once one or more of the following triggers are met:

• No significant mapping activity for 30 consecutive days (<100 edits/week).
• HOT activation officially closed.
• 3 months post-disaster.
• Or, if it occurs before any of the above, all Tasking Manager projects marked as complete (fully mapped and validated).

When exports stop, HDX focal point to update:

• Frequency of update: Set to Never.
• Description: Update any reference to frequency of updates.

The dataset will remain on HDX as per its internal SOPs. After a period of 5 years, the dataset is archived.

Instances of Use

The following list contains direct links to the HDX entries that have resulted from this initiative:

• Mozambique Floods, January 2026
• Madagascar, Tropical Cyclone Gezani, February 2026

Review Schedule

Process review scheduled after 3–4 activations (potentially Q2 2026) to assess:

• Validation of the process
• Process improvements
• Automation opportunities
• Resource and effort requirements

This review was carried out in May 2026, at which point HDX/HOT agreed to continue the initiative while keeping an eye out for means to automate steps.

Contacts

• HOT: Sam Colchester — sam.colchester@hotosm.org