Redmine

h1. Contributing data to the GEOFON Data Centre @ GFZ ( "DAS":https://das-metadata.gitbook.io/das-metadata-standard-by-das-rcn/ ) 

h2. 1.Scope of this document

The present document aims to provide simple guidelines to assist data providers during the archival of their data at GEOFON DC.

h2. 2. Request a network code at FDSN

For requesting a temporary network code for your project, we need the following information:

|- Title of the experiment  |

|- Start year  | 

|- End Year  | 

|- Short abstract (max 200 words)  | 

|- Estimated size  | 

|- PI(s) (ideally with ORCID iD)  |

|- Funding Agency |

|- Deployment area |

|- Will the data be embargoed |

|- Expected release date, for GIPP* is up to 4 years after the completion of the experiment|

|- License (after releasing dataset), default for GIPP* is "CC-BY":https://creativecommons.org/licenses/by/4.0/|

*"Geophysical Instrument Pool Potsdam (GIPP) Terms of use":https://www.gfz-potsdam.de/fileadmin/gfz/sec22/pdf_doc/GIPP/rules_GIPP_10_2019.pdf

Most of the above named information will be reused for minting a DOI later. Therefore we have prepared one writable PDF-file for serving both purposes.

Please download and fill in this "PDF":https://nextcloud.gfz-potsdam.de/s/crw53zyKpEc5jKj  to provide all the information needed to archive your dataset and create a DOI for it.

Of course, if you prefer, you can "request an FDSN network code yourself":https://www.fdsn.org/networks/request/temp/ . In this case please be cautious, there are a few little traps. Please keep in mind that we *still* need the "PDF":https://nextcloud.gfz-potsdam.de/s/crw53zyKpEc5jKj. Please also name the software that was used for downsampling and ideally provide a website.

* Please make sure to choose *Do nothing right now* if you do not already have a DOI minted for your network. GFZ will mint a DOI for you and *afterwards* insert it into the FDSN network mask.

* Please also make sure that you choose the right institution at *Operating institution* . You can also insert a new institution if you can't find yours in the drop-down menu. *Please do not choose GEOFON Program here!* 

* Choose *Geofon* as your *webservice* in order to enable FDSN to get your station metadata from our webservices automatically.

If you prefer to request an FDSN network code on your own, please make sure to forward the response message to *geofon_dc(at)gfz-potsdam.de* !

h2. 3. Data Preparation

For data preparation we recommend the "GIPPtools from the Geophysical Instrument Pool Potsdam":https://www.gfz-potsdam.de/en/section/geophysical-imaging/infrastructure/geophysical-instrument-pool-potsdam-gipp/software/gipptools by Christof Lendl or "msmod":https://github.com/earthscope/msmod by Chad Trabant.

The receiver program on our server expects MiniSEED data with the following configuration.

Header containing the final network code (assigned by FDSN), appropriate station code, channel naming and location code. 

Please also choose:

Blocksize *512* or *4096*

ByteOrder: *BigEndian*

Compression: *Steim1* or *Steim2* (please be consistent stationwise to avoid different compressions in one day file)

Since the conversion can be very time consuming especially for large datasets, we strongly recommend to *try first with a small amount of data*.

h2. 4. Send Metadata

"Station.xml":https://www.fdsn.org/xml/station/ or "SeisComp3 inventory.xml":https://www.seiscomp.de/doc/base/concepts/inventory.html or "dataless seed":https://ds.iris.edu/ds/nodes/dmc/data/formats/dataless-seed/ or a table containing the following information:

*| StationCode  | Place/Country  | Latitude  | Longitude  | Elevation  | SamplingRate | LocalDepth  | StartDate  | EndDate |* 

For fibre optics experiments we use channel code HSF according to the "SEED channel naming":https://ds.iris.edu/ds/nodes/dmc/data/formats/seed-channel-naming/ .

If you provide station.xml, please make sure that your streams have start-date and end-date of deployment (for temporary networks). Even if we also may store data from before and after deployment time, only the data during the deployment epoch will be available for the user.

h2. 5. Data Transfer

Now you have to download and install the "Ringserver":https://seiscode.iris.washington.edu/projects/ringserver Client software "miniseed2dmc":https://github.com/iris-edu/miniseed2dmc

*Please read the manual* . It‘s possible to do Dry Runs (without server connection) for testing purposes, in order to find out if the data is recognized as miniSEED. 

The next step should be the transfer of a small amount of data to see if all criteria have been met.

Call *miniseed2dmc -v 139.17.3.77:port* with port number being assigned by our data centre.

In any case, should you have difficulties with one or more of the steps described above, please contact us at geofon_dc(at)gfz-potsdam.de. Most probably we‘ll find a solution.

Looking forward to hosting your data at our data centre,

The GEOFON DC operators