RSQSim catalogues for the Monte Vettore Fault System (Central Italy)

Open data API in a single place

Provided by Zenodo

Get early access to RSQSim catalogues for the Monte Vettore Fault System (Central Italy) API!

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

Dataset information

Country of origin
Updated
2025.08.03 00:00
Created
2025.05.20
Available languages
English
Keywords
Quality scoring

Dataset description

Description This repository stores the simulated RSQSim earthquake catalogues shown and discussed in the preprint "Coseismic Surface Rupture Probabilities from Earthquake Cycle Simulations: Influence of Fault Geometry". We provide twelve folders, one for each RSQSim catalogue computed in the article. Each folder contains all input and output files from the RSQSim calculations, including the fault model, input parameter file and resulting catalogue files. The folder names indicate the fault geometric model considered for that catalogue (see article for details). The files contained are: A. Inputs paramfile.in: List of input parameter variables required for the RSQSim calculation and calls to the fault model where the simulations will be computed. Nodes_RSQSim_300.flt: Fault model in a text-based ascii file. Each line of the file corresponds to the info of one element of the triangular mesh that composesthe fault: X,Y,Z of the triangle nodes, fault rake (in degrees), fault slip rate (in m/s) and fault segment and fault IDs (i.e., the fault or segment where that element belongs). neighbors_300.dat: Text-based ascii file that groups the eight neighboring fault elements to each fault element. The grouping is done by their element ID - i.e., number of row in the fault model. B. Outputs eqs.italy.out: Simulated earthquake catalogue in a text-based ascii file. The file stores data for each simulated earthquake including X, Y, Z of the hypocenter, time in the catalogue (in seconds) magnitude (Mw), seismic moment, rupture area and stress drop. At the beginning of the file, the info of all input files described above is also stored. binary files: These files contain detailed information of each patch during every earthquake in the simulated catalogue, including patches activated during an event (italy.pList), their slip (italy.dList), stress drop (italy.dtauList), time of rupture (italy.tList), and the event ID - i.e., number of row in the catalogue file -  that they belong to (italy.eList), among others. Funding statement This research work was funded by the European Commission – NextGenerationEU, through Momentum CSIC Programme: Develop Your Digital Talent (project GDxGT; ref. MMT24-IGME-02), and by the TREAD project (daTa and pRocesses in sEismic hAzarD), funded by the European Union under the programme Horizon Europe: Marie Skłodowska-Curie Actions (MSCA) with grant agreement no. 101072699. Octavi Gómez-Novell is staff hired under the Generation D initiative, promoted by Red.es, an organisation attached to the Ministry for Digital Transformation and the Civil Service, for the attraction and retention of talent through grants and training contracts, financed by the Recovery, Transformation and Resilience Plan through the European Union's Next Generation funds.
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