Date Upload - only for authorized organizations

Data upload functionality to insert new events records, is restricted to authorized organization only. To contribute to the Database, please email the portal administrator, we will contact you as soon as possible to see how your data can be integrated in our database.

The RESTful API PostgREST will manage the data upload process. Each data provider may update only their own table, which will then be merged with other event tables to form a unified dataset for the web portal.

API - PostgREST API

Upload is possible by using the HTTP POST method with your preferred client. Here is a list of possible clients you can use:

CURL command on linux or window command line
Postman
python script

Here is the link to the General documentation of the API to insert data. you may consider the use of Client-Side libraries to insert data and to automate data insertion.

Base URL of the API is the following: https://eo4multihazards.eurac.edu/api

To create a row in a database table, post a JSON object whose keys are the names of the columns you would like to create. Missing properties will be set to default values when applicable.

curl "https://eo4multihazards.eurac.edu/api/your_table_name" \
  -X POST -H "Content-Type: application/json" \
    -d '{ "id": "value1", "geom": "value2", “event_type”:”value3”, “insert_date”:”value4”,  “start_date”:”value5”, “end_date”:”value6”, “country”:”value7”, “location”: “value8”, “description”: “value9”}' \
  --header "Authorization: Bearer secret_token_here"

To insert many obsersation at the same time, it possible to Bulk Insert. Bulk insert works exactly like single row insert except that you provide either a JSON array of objects having uniform keys, or lines in CSV format. This not only minimizes the HTTP requests required but uses a single INSERT statement on the back-end for efficiency.

curl "http://localhost:3000/people" \
  -X POST -H "Content-Type: text/csv" \
  --data-binary @- << EOF
id,geom,event_type,insert_date,start_date,end_date,country_location,description
234,POINT(6 10),Drought,26/09/2025,20/09/2025,24/09/2025,IT,Veneto,drought event that affected the Veneto region
235,POINT(6 45),Flood,26/09/2025,10/09/2025,11/09/2025,IT,Casale sul Sile,
236,POLYGON((1 1,5 1,5 5,1 5,1 1),(2 2, 3 2, 3 3, 2 3,2 2)),Drought,26/09/2025,22/09/2025,26/09/2025,IT,nord of Italy,drought event that affected the NOrd of Italy
237,...
...

It is also possible to update records of your table to update or delete values, following the General documentation

The secret-token will be sent to the authorized organization only, that will have the possibility to update records in their dedicated DB table. Different data upload methods can be agreed upon to meet specific requirements.

Table structure

Data providers have their dedicated event table that has the following structure:

id: identifier of the record that you use in your DB. This will be used to compose a unique ID composed in the form "provider_id"+"_"+"record_id" (ex.: 4_34584).
geom: this is the geometry of your record in WKB format
event_type: this field should correspond to the UNDRR hazard classification
insert_date: date of record creation/update
start_date: date start of the event
end_date: date end of the event (can be equal to "start_date")
country: country where event happened, according to the NUTS nomenclatur
location: specific list of location where the event happened. It's a free text to better describe event location, but not mandatory
description: text field to describe event
data_provider: automatically inserted by the EO4MULTIHAZARDS system to identify your organization

Event record table

The EO4MULTIHAZARDS application uses a unique table that merge all input datasets from diverse sources. Each data source is organized in an independent table that can be update by the data provider autonomously or is updated by a GIT-pipeline as for EMDAT and EFFIS tables.

Here below you can see the records tables schema.

map tools

Please contact us with any questions. We are available to assist you with any technical issues you may encounter.