MedNet
Istituto Nazionale di Geofisica e Vulcanologia MedNet 

 Rischio Sismico, Rischio Vulcanico, Rischio di Non Sapere.

Le informazioni contenute in queste pagine sono state sinora garantite dal lavoro del personale, precari e non, dell'Istituto Nazionale di Geofisica e Vulcanologia.

Il personale dell'INGV ha decretato lo stato di agitazione contro l'emendamento 37bis alla proposta di legge 1441 quater, che provocherebbe il licenziamento del personale precario portando ad uno stato di crisi le attività istituzionale svolte dall'Ente. Di conseguenza si procederà alla sospensione dell'informazione telematica e telefonica non istituzionale, relativa ai terremoti che avvengono sul territorio nazionale.

 Seismic Risk, Volcanic Risk, Information Risk.

The information on these pages have been so far provided by the staff of INGV, which includes a large number of temporary workers.

The government now proposes to dismiss all the temporary workers (amendment 37 bis to the 1441 quater bill) thus bringing about a serious crisis in the institutional activity of INGV. Against this decision the staff as a whole will stop the release of all non-institutional information relating to national earthquakes.

Menu:

rss Earthquakes



Links:

- IRIS
- ORFEUS
- NEIC
- GEOFON
- NOA
- HL NOA

Latest news:

Jul 25, 2008:
nmxptool is one year old.

More info:

Noise spectral
These tools permit to inquire the Power spectral density MedNet station archive.
Click here...

MedNet Data

Data from the MedNet stations are continuously collected at the MedNet Data Center, where they are quality controlled, archived and then distributed at users' request.

Data and station information are available in SEED (Standard for Exchange of Earthquake Data) format through NetDC, sending an e-mail to netdc@ingv.it (see instructions below or NetDC Manual) or using NetDC Web Form: it will produce a NetDC mail for you!

AutoDRM is also available at autodrm@ingv.it (data format in GSE).

View MedNet stations metadata.

 

Instructions

E-mail format for a NetDc request.

The e-mail should be written in plain text, following the examples below, and sent to netdc@ingv.it.

.NETDC_REQUEST
.NAME Vincenzo Montella
.INST University of Roma
.EMAIL v.montella@roma.it
.LABEL myrequest
.MEDIA ftp
.END
.INV MNDC MN "AQU VSL KEG" * "LHZ BH?" "1992 02 01 00 00 00" "1992 02 03 00 00 00"
.RESP MNDC MN * * LHZ "1992 02 01 00 00 00" "1992 02 03 00 00 00"
.DATA MNDC MN BGY * BH? "1992 02 01 00 00 00" "1992 02 03 00 00 00"

Syntax of the request:

.NETDC_REQUEST is necessary to identify the mail document as a request intended for NetDC. This must always be the first line of the request.

.NAME indicates the name of the user. This is needed to identify the request and allows for the grouping of multiple requests by the same user.

.INST lists the institution that the user belongs to. This can be a company name or educational institution. This assists in establishing contact with the user should it be necessary for servicing the request.

.EMAIL is the email address of the requesting user. This entry is mandatory since the majority of user contact will be through email.

.END is a mandatory entry that signals the end of the request header

The data request lines come in three flavors: .DATA, .RESP, and .INV:

.DATA lines request waveform data, .RESP lines ask for response information, and .INV queries a site for an inventory of data holdings. All of these request types follow the same general format, even though the response to each will differ. The field layout of a data request line is as follows:

.<DATA_TYPE> <DATA_CENTER> <NETWORK> <STATION> <LOCATION> <CHANNELS> <START_TIME> <END_TIME>

NOTE: It is possible to include more than one "data request line". When requesting data, in e single line for different stations or channels the wildcards * or ? can be used or. When two or more channels are specified, they need to be enclosed in double-quotes.