Oceanids Related Events

Open data API in a single place

Provided by Zenodo

Get early access to Oceanids Related Events API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2025.12.03 00:00
Created
2025.09.30
Available languages
English
Keywords
Quality scoring

Dataset description

The following dataset was collected as part of the WP3.2 Quantifying societal impact and responses to weather risks work package of the Oceanids project.  It consists of 3 files. events.json locations.json event_location.json Events data Events.json file includes a list of events and their corresponding data. The schema of the data is as follows: Field Data Type Description event_type  Enum[flood, hurricane, storm_surge, earthquake, landslide, wildfire, heatwave, tornado, coastal_erosion, other] The type of the event (e.g., hurricane, storm, flood, etc.). name String The designated name of the event. start_date ISO-8601 String The start date of the event in YYYY-MM-DD format. end_date ISO-8601 String The end date of the event in YYYY-MM-DD format (e.g., for hurricanes, this is the date of dissipation). countries Array[String] The list of countries that were directly affected by the event. areas_affected Array[String] The list of specific subnational areas (e.g., provinces, states, districts, cities) that were directly impacted by the event. fatalities Integer The number of confirmed fatalities caused by the event. people_injured Integer The number of people who sustained non-fatal injuries due to the event. people_displaced Integer The number of people who were forced to leave their homes or shelters due to the event. people_affected Integer The number of people who experienced negative consequences from the event (property damage, health impacts, or loss of access to essential services). losses String The estimated financial losses caused by the event. It contains the numerical value and the currency. All loss values correspond to the date of the event; no adjustment for inflation has been applied. infrastructure String A description of major infrastructure damage. agriculture String A description of damages that affected the agriculture sector (e.g., farms, crops) caused by the event. fisheries String A description of damages that affected the fisheries (e.g., fish population) caused by the event. tourism String A description of the consequences on the tourism sector caused by the event. public_health String A description of consequences on public health caused by the event(e.g., hospitalization due to illnesses, water contamination, psychological impacts). sources Array[String] The exact source(s) from which the event information was extracted. key String A unique event identifier used for internal parsing and referencing.   Locations Data As seen in the events schema, a list of locations(countries, areas_affected) is related with it. Geojson data is collected for the locations mentioned in the events.json file and it is stored in the locations.json file. Field Datatype Description key String The key to a location name String The name of a location region String The region the location belongs to country String The country the location belongs to coordinates Dict[type, coordinates] GeoJSON feature for coordinates. The type field’s value is Point polygon Dict[type, coordinates] Geojson feature for polygon, the type field’s value is either Polygon or MultiPolygon multiline Dict[type, coordinates] Geojson feature for multiline. The type field’s value is either LineString or MultiLinestring. Event Location Association Table Each event is associated with a list of locations. This association is done through the event_location.json file. Field Datatype Description event_key String The key to an event location_key String The key to the corresponding location   For more info email at piraptis@wtoc.eu
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks