Import a whole dataset of hazard reports or relief points at once, using Nigraan's CSV template, and fix the rows it skips.
For: Validators, Partners, Institutional users, Administrators
Staff can add many records in one go from a CSV or JSON file. Every imported record goes into the review queue as pending, exactly like a single report, so nothing reaches the public map without a reviewer's approval.
Download the template from the uploader and fill it in. It is a CSV file with these columns:
| Column | Required? | What goes in it |
|---|---|---|
hazard_type |
Yes | A hazard (Flood, Earthquake, Fire, Landslide, Cyclone / Storm, Heatwave, Drought, Disease Outbreak, House Collapse, Lightning, Electrocution, Tree Fall, Other) or a relief type (Food Distribution, Water, Shelter, Medical). |
location_name |
Yes | The place's name. |
city |
No | City or district. |
province |
No | Province. |
latitude, longitude |
No, but needed for the map | Decimal degrees, inside Pakistan, e.g. 27.7052, 68.8574. |
description |
No | What happened, or what the relief point offers. |
timestamp |
No | When it happened, e.g. 2026-07-15T09:30:00Z. |
expires_at |
Relief rows only | When the relief listing should leave the map. It must be in the future. Leave it blank for hazards. |
The template includes one worked hazard row and one worked relief row. Replace them with your own.
A JSON file works too: an array of objects with the same keys.
Nigraan would rather skip a doubtful row than store it wrongly. The result counts every skipped row and lists the first few with their reasons, for example:
expires_at that is not a date, or is in the past.Fix those rows in your file and upload just them again. The rows that were accepted are already in the queue, so do not upload them twice.
Your records wait in the review queue until a validator or administrator approves them. See Review submitted reports.