.. Annual report template. Please fill your custom text here below. This is a RsT (ReStructuredText) file and also a comprehensive tutorial which might help you during editing. RsT is a lightweight markup language designed to be both easily readable/editable and processable by documentation-processing software (Sphinx) to produce html, latex or pdf output This portion of text (".. " followed by INDENTED text) is a comment block and will not be rendered. The comment block ends at the first non-indented line found .. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. FIELD LIST (BEFORE THE TITLE) .. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. Field lists are two-column table-like structures resembling database records. Each Field in a field list is in the form :name: value (note the space before value). E.g.: :Date: 2001-08-16 :Version: 0.1 In Sphinx, fields placed before the title, as the ones listed below, will never be rendered in any document and act as metadata. In this program, they define text variables which will be rendered in specific places of the document. The user has not to care about "where", just fill the relative values. As these bib. fields cannot have comments before or after (Sphinx bug?) we need to describe them all at once here, with the (theoretical) responsible in brackets: - doi (LIBRARY OR AUTHOR OR GIPP/GEOFON INPUT): the DOI of this report - subtitle (AUTHOR INPUT): self-explanatory. Filled automatically by default with the network description. Note: you should not specify newlines in it (same for subSubtitle below) - sub-sub-title (AUTHOR INPUT): self-explanatory. This is the (optional) sub-sub-subtitle (below the subtitle) - strNum (LIBRARY INPUT): the Scientific Technical Report (STR) number - strText (LIBRARY INPUT): the STR text, displayed in the bottom of the title and 2nd page - urn (LIBRARY INPUT): The urn, e.g.: urn:nbn:de:kobv:b103-xxxxx (side-note for developers: the sphinx builder might raise a warning if rst interprets it urn as URL. Please ignore the warning) - issn (LIBRARY INPUT): the issn. E.g.: 2190-7110 - publicationYear (LIBRARY INPUT): the publication year. E.g., 2016 - publicationMonth (LIBRARY INPUT): the publication month in plain english. E.g.: October - version (AUTHOR INPUT): a version number to be printed in latex second page Now you can fill their values (plain text only, no markup): :doi: 10.2312/GFZ.b103-20035 :subtitle: :subSubtitle: :strNum: STR 20/03 :strText: Scientific Technical Report :urn: urn:nbn:de:kobv:b103-20035 :issn: 2190-7110 :publicationYear: 2020 :publicationMonth: June :tocdepth: 3 :version: 2.2 :date: 2020-06-10 .. ^^^^^^ .. TITLE: .. ^^^^^^ .. Section titles are set by decorating a SINGLE line of text with under- (and optionally over-) line characters WHICH MUST BE AT LEAST AS LONG AS the section title length. There is no rule about which decoration characters to use, but equal decorations are interpreted as same "level": thus two chapter titles must have the same decorations, a chapter and a section must not GEOFON Annual Report 2019 ========================= .. ^^^^^^^^^^^^^^^^^^^^^^^^ .. FIELD LIST (AFTER TITLE) .. ^^^^^^^^^^^^^^^^^^^^^^^^ .. In Sphinx, fields placed after the title will be rendered in all documents (developer note: they can have comments before or after and no markup in their value) In this program they might be ignored, or pre-processed before rendering their value (for details see descriptions below) .. authors (AUTHOR INPUT). Provide the author(s) as comma separated items. Affiliations should be included here if needed in round brackets after each author. Affiliations shared by more authors need to be re-typed. "corresponding author(s)" should be followed by an asterix. The program will parse and correctly layout of all these informations in latex/pdf (e.g., avoiding repeated affiliations, and rendering "corresponding author" if an asterix is found). In html there is no such processing and the text below will be displayed as it is, after removing all asterixs. :Authors: Angelo Strollo, Peter Evans, Andres Heinloo, Susanne Hemmleb, Laura Hillmann, Karl-Heinz Jäckel, Javier Quinteros, Joachim Saul, Riccardo Zaccarelli, Thomas Zieke and Frederik Tilmann. .. the citation section. Write here how the user should cite this report, and/or how to cite any data related to this report, if needed. The text below will be rendered in the title back page in LaTeX. In principle, you might need to just change or re-arrange the text. For more experienced users, note the use of the custom role :doi-citation: where you can reference also an already defined bib. field before the title by wrapping the field name in "|", e.g. :doi-citation:`|doi|`. :Citations: Recommended citation for the report: :doi-citation:`|doi|` .. raw:: latex \tableofcontents \newpage Executive summary ~~~~~~~~~~~~~~~~~ - One additional station was added to the GEOFON Global Seismic Network in Germany at the Falkenstein castle (Harz, Sachsen-Anhalt) with station code FALKS. 45 stations required corrective maintenance actions. The GEOFON engineering team performed on-site maintenance at 8 sites, whereas 37 stations were serviced from remote and/or repaired by our local partners. For 13 stations spare parts were assembled and tested in Potsdam and delivered to the local partners. The Week Number Roll Over (`WNRO `_) expected to affect GPS receivers in 2019 required a large effort to prepare and fix a substantial number of stations affected. - The GFZ Seismological Data Archive hosted at GEOFON has grown by ~18 TB in 2019. The total size of the archive is ~118 TB including 137 networks and 4558 stations. Tailor-made requests from the archive have been served to more than 2700 unique users, which cumulatively made more than 190 million requests for 270+ million time windows. Real-time data export has increased slightly to ~160 TB/year to more than 300 clients. At the end of the year EPOS-IP (EU) and GDN (BMBF) projects have ended. The EIDA Next Generation services, the adoption of persistent identifier (PID) for seismic instruments (of GIPP) and improved data policies for seismic data at the GFZ are the main outcomes of the two projects. - GEOFON published 4657 events and 905 moment tensor solutions via the web pages and other dissemination channels. The `paper `_ co-authored with staff at the EMSC and the Hungarian Academy of Science has been published by *Science Advances*, demonstrating the benefits of using CrowdSeeded locations (CsLoc) to reduce the the publication delay to 1.7 min (median value for analysed data set). Aiming at introducing a new service providing the Energy Magnitude in real-time we started testing, in cooperation with ISC and Section 2.6, the procedure proposed by Di Giacomo et al., 2008. - Software development focused on preparing the new version of `SeisComP `_ 4.0.0 AGPL in cooperation with gempa GmbH for release in spring 2020. Another major activity has been the redesign of the web pages launched in October. The new web site has been optimised for mobile devices which is from where the majority of our users are coming today. The authentication service developed for EIDA has been successfully rolled out and used for the first time to access restricted data in EIDA via standard fdsn web services (AlpArray). .. raw:: latex \newpage Introduction ~~~~~~~~~~~~ The GEOFON program consists of a global seismic network (GE Network), a seismological data centre (GEOFON DC) and a global earthquake monitoring system (GEOFON EQinfo). These three pillars are part of the `MESI `_ research infrastructure of the Helmholtz Centre Potsdam - GFZ German Research Centre for Geosciences aiming at facilitating scientific research. GEOFON provides real-time seismic data, access to its own and third party data from the archive facilities as well as global and rapid earthquake information. The GEOFON Seismological Software can be considered a fourth cross-cutting module of the GEOFON Program. Data, services, products and software openly distributed by GEOFON are used by hundreds of scientists and data centres worldwide. Its earthquake information service is accessed directly by tens of thousands of visitors. The *SeisComP* software package is the flagship software provided to the community, which is geared for seismic observatory and data centre needs and used extensively to support our internal operations. As all other MESI (Modular Earth Science Infrastructure) modules GEOFON has the majority of users outside the GFZ as well as an external advisory committee that provides advice to the GFZ Executive Board and to the GEOFON team. This report describes the main activities carried out within the three GEOFON pillars and the software development group. The GEOFON global seismic network ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The GEOFON network at the end of 2019 consisted of 89 GEOFON stations (mostly distributed under the GE network code, but also including the 4 former GE stations today distributed under the WM seismic network code and WM.TIO) (:numref:`map_ge_stations`). One new station was added to the GEOFON Global Seismic Network in Germany at the Falkenstein castle with station code FALKS. Installation of the Falkenstein (FALKS) station in Germany provides better coverage for local and regional earthquakes in the Sachsen-Anhalt region. The site has been selected with the intention to have also a test site not too distant from the GFZ. The station is equipped currently with the Trillium 360 seconds BB sensor and a Quanterra (Q330S) digitizer. We plan to replace the sensor with a 120 seconds in the near future. We keep on exploring better locations in the region in coordination with the local colleagues and BGR. The GPS Week Number Roll Over, although expected in April and prepared in advance, demanded substantial effort in summer. The GEOFON engineers, already at the beginning of the year, contacted directly the GPS boards producers to get exact dates for the boards in use of the WNRO. Unfortunately for some of our digitizer was not possible to uniquely identify the GPS board in use. Most of these digitizers (~30 units in our networks) from EarthData were indeed suddenly affected on Sunday 28.07.2019. A `patch `_ for the EarthData seedlink plug-in was quickly deployed at all stations from remote and on the next Monday we had almost all stations back in operation. During the WNRO crises we managed to re-establish the connection with the Pulkovo (PUL, Russia) station operator and since then we are receiving again data as well as we back filled the archive for the previous years. Four of the GEOFON stations have not delivered any data in 2019 (SOCY and DAMY in Yemen, LVC in Chile and KERA in Greece) due to civil war in the country or political issues. The LVC station in Chile, operated in cooperation with the IRIS/GSN, was vandalised in November 2018. Despite the complex issues we are facing with these stations we hope to have them back online in the future, thus keep their epochs open. The average availability for the network excluding the new and four non-working stations is at 93%. Regular maintenance <<<<<<<<<<<<<<<<<<< 45 GEOFON stations required corrective maintenance actions. The GEOFON engineering team performed on-site maintenance at 8 of these sites (NPW in Myanmar; KAAM and HMDM in the Maldives; FALKS, RGN and IBBN in Germany; SANT in Greece; SUMG in Greenland), whereas 37 stations were repaired remotely and/or by our local partners. Here, it was necessary in 13 cases to assemble and test spare parts in Potsdam and deliver them to the local partners (Figure 1). The large number of stations demanding maintenance has been caused by the WNRO issue, not only to apply the patch to the EartData but also to check/upgrade firmwares to all other stations running old firmware versions. .. customize the includegraphics options (only for latex output) for the next figure or image found (in the former case, applies the includegraphics options to all images of the figure): .. .. includegraphics:: angle=90,width=1\textwidth .. map directive. Customize as you want, you can reference it via :numerf:`map_ge_stations` .. _map_ge_stations: .. mapfigure:: GEOFON stations in 2019. Colours denote the data availability (white: 0% to red: 100% availability). Symbols represent the level of maintenance needed: circle for “none”, square for “on site”, triangle (up) for “remote”, triangle (down) for “Remote including HW shipment”. An “X” next to the symbol indicates metadata updates. :header-rows: 1 :align: center :delim: space :quote: " :map_fontweight: regular :map_mapmargins: 0.5deg, 0.5deg, 0.5deg, 0.5deg :map_labels_h_offset: 0.005 :map_legend_borderaxespad: 1.5 :map_arcgis_service: World_Street_Map :map_urlfail: ignore :map_labels_v_offset: 0 :map_sizes: 50 :map_meridians_linewidth: 1 :map_legend_pos: bottom :map_arcgis_xpixels: 1500 :map_parallels_linewidth: 1 :map_fontcolor: k :map_maxmeridians: 5 :map_figmargins: 1,2,9,0 :map_legend_ncol: 2 :map_maxparallels: 5 Station Latitude Longitude Marker Color Label ACRG 5.641485 -0.207117 ^ #FF0101 APE 37.07274 25.52301 ^ #FF1A1A ARPR 39.09289 38.33557 ^ #FFCCCC BALJ 32.0873 35.64 ^ #FFE9E9 BBJI -7.462603 107.65 o #FF0101 BKB -1.1073 116.9048 o #FF0101 BKNI 0.3262 101.0396 o #FF1F1F BNDI -4.5224 129.9045 o #FF1717 BOAB 12.4493 -85.6659 o #FF8B8B CSS 34.9611 33.331 ^ #FF0000 DAG 76.7713 -18.655 v #FF4545 DAMY 14.5725 44.3917 o #FFFFFF DSB 53.2452 -6.3762 v #FF0101 EIL 29.6699 34.9512 v #FF2929 FAKI -2.91925 132.24889 o #FF0808 FALKS 51.6819 11.2655 s #FFFFFF X FLT1 52.3306 11.2372 ^ #FF0404 GENI -2.5927 140.1678 o #FF0505 GHAJ 31.30341 35.56648 o #FF0B0B GSI 1.3039 97.5755 o #FF1212 GVD 34.83914 24.08738 ^ #FF0606 HALK 6.0877 80.6806 v #FF6F6F HLG 54.183092 7.883014 v #FF1B1B HMDM 6.77314 73.18216 s #FF5252 IBBN 52.3063 7.7592 s #FF0D0D ILTH 54.0279 -6.3362 o #FF0000 IMMV 35.4606 23.9811 o #FFC8C8 ISP 37.8433 30.5093 o #FF0101 JAGI -8.4702 114.1521 o #FF0101 KAAM 0.49264 72.99486 s #FF4343 KARP 35.5471 27.16106 ^ #FF3A3A KBS 78.9154 11.9385 o #FF0606 X KBU 34.5151 69.1347 ^ #FF4C4C KERA 35.3692 23.5577 o #FFFFFF KIBK -2.35907 38.0433 o #FF0000 KMBO -1.1271 37.2525 o #FFC4C4 KTHA 36.2566 23.0621 ^ #FFBEBE LHMI 5.2288 96.9472 o #FF0404 LODK 3.42195 35.36165 o #FF0000 LUWI -1.0418 122.7717 o #FF3232 LVC -22.6127 -68.9111 o #FFFFFF MALK 8.39682 80.54254 ^ #FF3737 MARCO 40.29722 15.8063 o #FF0000 MATE 40.64907 16.70442 ^ #FF0101 MMRI -8.6357 122.2376 o #FF0404 MNAI -4.3605 102.9557 o #FF1F1F MORC 49.7766 17.5428 o #FF0808 MSBI 31.3126 35.358 ^ #FF4343 MTE 40.3997 -7.5442 ^ #FF2222 NPW 19.7785 96.1376 s #FF1A1A PABE 55.50523 23.96796 ^ #FF0202 PBUR 56.02361 21.92945 v #FF3E3E PLAI -8.8275 117.7765 o #FF0101 PMBI -2.9024 104.6993 o #FF1A1A PMG -9.4047 147.1597 o #FF8D8D PSZ 47.9184 19.8944 ^ #FF0202 PUL 59.767 30.317 ^ #FF0505 RGN 54.5477 13.3214 s #FF0A0A RUE 52.4759 13.78 ^ #FF0505 SALP 32.0686 35.1914 o #FF0303 SALTA -24.2241 -66.34 o #FF0303 X SANI -2.0496 125.9881 o #FF1010 SANT 36.37052 25.45926 s #FFFFFF SAUI -7.9826 131.2988 o #FF0D0D SBV -13.4584 49.9212 ^ #FF0303 SFJD 66.9961 -50.62076 o #FF0101 SLIT 57.6287 22.2905 ^ #FF0202 SMRI -7.04915 110.44067 o #FF0707 SNAA -71.6707 -2.8379 ^ #FF1A1A SOCY 12.51952 53.98742 o #FFFFFF SOEI -9.7553 124.2672 o #FF0101 STU 48.7719 9.195 ^ #FF0A0A SUMG 72.57428 -38.462075 s #FF0505 X THERA 36.366992 25.45926 ^ #FFFFFF X TIRR 44.4581 28.4128 o #FF0000 TNTI 0.7718 127.3667 o #FF0101 TOLI2 1.11119 120.78174 o #FF0101 UGM -7.9125 110.5231 o #FF0101 UJAP 31.95201 35.46435 ^ #FF0101 VAL 51.9394 -10.2442 ^ #FF0303 VOI -21.90648 46.79327 ^ #FF0505 VSU 58.462 26.7347 o #FF0101 WIN -22.5691 17.0915 ^ #FF4040 WLF 49.6646 6.1526 o #FF0303 ZKR 35.1147 26.21691 ^ #FF2323 AVE 33.2981 -7.4133 ^ #FF5757 CART 37.5868 -1.0012 ^ #FF0000 MAHO 39.8959 4.2665 v #FF5757 SFS 36.4656 -6.2055 o #FF5151 TIO 30.9267 -7.26167 o #FF0101 Technical developments <<<<<<<<<<<<<<<<<<<<<< R&D efforts were mainly directed at exploring possibilities to replace the actual PC in use at the stations, the so called seiscompbox. A prototype next generation seiscompbox has been developed bringing together the functionality of the Teltonika routers and the seiscompbox. This prototype is based on openWRT (seiscompWRT) and includes raspberrypi, solid state disk, UMTS stackable modules, power management and a number of additional switch options through the GPI board (e.g. mass centering, power cycle, etc) tests will be carried out in the near future. Redmine has been adopted as tracking and documentation system for the network. Technical support to other GFZ groups (e.g. Observatories) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< The engineering group also provided support to other projects/groups within and outside the GFZ. Within our own section (2.4) we supported the field activities of a temporary campaign in Myanmar. A substantial effort went into supporting the Integrated Plate Boundary Observatory Chile `(IPOC) `_ seismic network in remote support and migration of the documentation into the Redmine system. Support has been provided to GFZ colleagues to prepare instruments for a strong motion network in Myanmar and to other external partners during the WNRO crises. Last but not least the GEOFON group continuously provided assistance to our long term partner BMKG in Indonesia to run their seismic network and data centre for tsunami early warning. Annexes <<<<<<< A comprehensive report on engineering actions is provided as separate document linked at the end of the report. The GEOFON Data Centre ~~~~~~~~~~~~~~~~~~~~~~ Archive Service Delivery <<<<<<<<<<<<<<<<<<<<<<<<< The GFZ Seismological Data Archive hosted at GEOFON has grown by ~18 TB in 2019, similar to the previous year, with most of the added data having been acquired by temporary networks between 2014 and 2019, but also with some old data dating back to 2003 (:numref:`archive_1`). The archive (total size ~118 TB, :numref:`archive_2`) was completely integrated in the GFZ computing centre infrastructure within 2019. Substantial effort has been done to migrate from own storages (SAN-type storage, which were attached to VMs as block device) to the computing centre facilities (NAS-type storage, which is attached via NFS). The filesystem is now mirrored in two physical locations and monthly snapshots are provided. With this new approach we spare one replica of the data, only replicating once off-site at KIT. An additional advantage is that the filesystem can be dynamically expanded and mounted on multiple machines (eg., geofon1h and geofon2h) at the same time. Thus the GEOFON archive is also ready to scale up in case of sudden exponential demand of new storage space driven by emerging technologies such as DAS, Large-N etc. Most of the data were served to the 2700+ users of the archive via fdsnws, in total almost 150 million requests (34 TB), compared to 45 million via arclink (4 TB). After a decade of usage, arclink service was switched off with end of the year. To facilitate the transition we provided dedicated `documentation `_ and an alternative client to arclink_fetch named fdsnws_fetch which is able to handle arclink_fetch input files but based on FDSN standard web services. The new client supports also authentication and thus able to access restricted/embargoed data (e.g. AlpArray). Real-time data export has increased slightly to ~160 TB/year to more than 300 clients. .. figure archive_1. You can reference it via :numerf:`archive_1` .. _archive_1: .. figure:: ./data/archive_1.png :width: 100% :align: center Data archived by year of acquisition. .. figure archive_2. You can reference it via :numerf:`archive_2` .. _archive_2: .. figure:: ./data/archive_2.png :width: 100% :align: center Cumulative size of the GEOFON archive. Requests by method and by type. .. NOTE: the csv-table below allows captions and more customization than simple tables, but does not require the cells of the table body to be vertically aligned: below, the cells are aligned only to visually help the editor .. tabularcolumns:: |l|r|r|r|r| .. csv-table:: Requests by method and by type :header-rows: 1 :delim: ; :align: center Request method ; Requests ; Timewindows ; Volume ; Users fdsnws (external) ; 142.734.001 ; 195.614.480 ; 31 TB ; 2496 fdsnws (GFZ) ; 4.624.779 ; 11.830.774 ; 3 TB ; 175 arclink (external) ; 45.567.806 ; 59.998.062 ; 4 TB ; 1040 arclink (GFZ) ; 134.963 ; 620.619 ; 1 GB ; 38 Total ; 193.061.549 ; 268.063.935 ; 38 TB ; x .. figure archive_3. You can reference it via :numerf:`archive_3` .. _archive_3: .. figure:: ./data/archive_3.png :width: 100% :align: center Number of distinct user IDs provided for fdsnws and/or arclink on each day in 2019. New networks (embargo period end reports or any other change) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< At the end of the year the archive consisted of 137 networks and 4558 stations with 11 new temporary networks (listed below) added in 2019. Within the GDN project we invested substantial work in reviewing metadata, this includes GIPP grant number addded to network metadata and linked to the GIPP database from the network page. * 2L_2015 El Hierro, Spain * 3H_2014 LOFS * 5K_2015 Wanrong * 6C_2019 Myanmar * X8_2018 SMARTIE1 * 8E_2018 Seismic sensing of hydraulic and sediment transport patterns below frozen subarctic river * 4K_2017 Jasmund seismic cliff erosion monitoring network * 6G_2017 Los Humeros * 7A_2019 CaTeNA * YG_2018 DESTRESS * Z3_2015 German OBS component (GEOMAR) of Alparray DOIs minted: 8 new temporary (XC_1998, 7A_2019, 6G_2017, X8_2018, 8E_2018, 3D_2014, 1T_2014, ZW_2010) Networks Released * ZE_2012 Real-time data export via seedlink: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< The real-time data export via seedlink from the public Seedlink server at geofon.gfz-potsdam.de increased to ~160 TB/year with 300-350 continuous connections. The most requested network for real-time distribution is GE with 100+ TB followed by CX with ~10 TB and all other networks ranging between 10 TB and some MB. Service uptime <<<<<<<<<<<<<< .. tabularcolumns:: |l|c|c| =================== ======= ============ Service Up Down/Problem ------------------- ------- ------------ WebDC 99.810% 0.190% EIDA Master Table 99.977% 0.023% fdsnws-dataselect 98.951% 1.049% fdsnws-station 99.864% 0.136% routingsvc 99.989% 0.011% ------------------- ------- ------------ geofon-proc 99.938% 0.062% geofon (ping) 99.934% 0.066% geofon (Web pages) 99.807% 0.193% geofon (eqinfo) 99.765% 0.235% geofon (Seedlink) 99.808% 0.192% =================== ======= ============ Note that the service uptime is measured by a Nagios instance running on a local machine. This means that times when the computer running Nagios was down, e.g., during a power out, would not be included in the analysis, and also times when the connection to the internet was broken would not necessarily be reported as down time. Even though technically this makes the report service uptime an upper bound estimate, no major episodes of either network or power outage are known to us, such that the numbers can probably be taken at face value. Details of checks carried out: - WebDC: check Arclink responds on port 18002 at webdc.eu. - EIDA Master Table: check http://webdc.eu/arclink/table?group=eida is accessible. - geofon-proc: MySQL (SeisComP db) available, and contains recent events. - FDSN web services: - check fdsnws-station at http://geofon.gfz-potsdam.de/fdsnws/station/1/version - check fdsnws-dataselect at http://geofon.gfz-potsdam.de/fdsnws/dataselect/1/version - routing service: - check http://geofon.gfz-potsdam.de/eidaws/routing/version - geofon (ping): ping of geofon.gfz-potsdam.de - geofon (web pages): visit the front page, http://geofon.gfz-potsdam.de/ - geofon (Seedlink): telnet geofon.gfz-potsdam.de 18000 succeeds. - geofon (eqinfo): only to display http://geofon.gfz-potsdam.de/eqinfo/list.php, GEOFON Rapid Earthquake Information ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. Following the trend from last year the Earthquake Information system has got less manual interaction and more automatic solutions. Published earthquake locations and moment tensor solutions <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< In total GEOFON published 4661 events and 905 moment tensor solutions via the web pages and other dissemination channels. :numref:`eqinfo_1` shows the geographic distribution of the published events and :numref:`eqinfo_2` the distribution of the moment tensors. The number of published events and moment tensors has slightly decreased with respect to the previous year. .. figure eqinfo_1. Reference it throughout the document via :numref:`eqinfo_1` .. _eqinfo_1: .. figure:: ./data/eqinfo_1.png :width: 100% :align: center Geographic distribution of the published events in 2019. .. figure eqinfo_2. Reference it throughout the document via :numref:`eqinfo_1` .. _eqinfo_2: .. figure:: ./data/eqinfo_2.png :width: 100% :align: center Geographic distribution of the published moment tensor solutions in 2019. .. tabularcolumns:: |r|r| .. csv-table:: Events by magnitude classes in 2019 :header-rows: 1 :delim: ; :align: center Mag ; Num. events :math:`\geq7.5` ; 3 :math:`\geq6.5` ; 31 :math:`\geq5.5` ; 394 :math:`\geq4.5` ; 3702 All ; 4661 Removed "Fake" events are usually characterized by unfavorable azimuthal station coverage or even strongly clustered stations (IPOC, parts of Central Europe, Taiwan). .. The number of published fake events could be reduced significantly compared to previous years by introducing additional publication criteria such as the maximum "sum of the largest two azimuthal gaps". .. tabularcolumns:: |l|r|r|r| .. csv-table:: Event dissemination :header-rows: 1 :delim: ; :align: center Events ; No MT ; Has MT ; Total Published ; x ; x ; 4661 Status A ; 1265 ; x ; 1265 Status C ; 1852 ; 789 ; 2640 Status M ; 636 ; 116 ; 752 Removed ; 4 ; x ; 4 Event notification delays are shown in :numref:`eqinfo_3` and :numref:`eqinfo_4` . .. figure eqinfo_3. Reference it throughout the document via :numref:`eqinfo_3` .. _eqinfo_3: .. figure:: ./data/eqinfo_3.png :width: 100% :align: center Event publication (grey dots) and alert delay (big green and xxl red) vs. magnitude in 2019. Alert delay for GEOFON events in 2019 resulting in SMS alerts. Magnitude is the magnitude reported at the time of the alert. Also shown are events with only an automatic detection (status 'A'). .. tabularcolumns:: |l|r|r|r|r| .. csv-table:: Alerts issued by type :header-rows: 1 :delim: ; :align: center 2019 ; xxl ; big ; Other ; All classes Total ; 26 ; 333 ; 4302 ; 4661 The definitions of these alert types are: * 'xxl' events are those with magnitude larger than 6.5 worldwide, or larger than 5.5 in or near Europe, or 5.0 in central Europe. * 'big' events have magnitude above 5.5 in most of the world, or above 5.0 in the wider Europe/Mediterranean area and M>=4.5 in central Europe. * the 'Other' category includes internal alerts and some regional notifications. .. figure eqinfo_4. Reference it throughout the document via :numref:`eqinfo_4` .. _eqinfo_4: .. figure:: ./data/eqinfo_4.png :width: 100% :align: center GEOFON alert delay vs. first automatic publication. GEOFON web server traffic <<<<<<<<<<<<<<<<<<<<<<<<<<<<<< The number of distinct users connecting to geofon.gfz-potsdam.de is of typically ~30.000/day (:numref:`eqinfo_5`). In distinct users we count both humans browsing through the pages as well as automatic usage including mobile apps with the latter being the dominant part ("Distinct" users are those with distinct IP address and User-Agent, on mobile devices IP may change and thus increase the numbers of counts). The traffic increase starting in coincidence with the release date of the new web site is not driven by actual users visiting the new pages though. .. figure eqinfo_5. Reference it throughout the document via :numref:`eqinfo_5` .. _eqinfo_5: .. figure:: ./data/eqinfo_5.png :width: 100% :align: center Daily distinct users connecting to geofon.gfz-potsdam.de during 2019 (unique IP + user application which is dominated by automatic applications including mobile devices apps). Also shown is the magnitude of the *largest* event recorded on each day, when this exceeds 6.4. (The threshold for 'xxl' alerts is 6.5 in most of the world). Ongoing cooperation with EMSC, ISC and Section 2.6 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< The assessment phase for crowdseeded fast locations using real-time picks exchanged with EMSC via HMB (httpmsgbus - software developed at GEOFON previously) has been completed and a joint `paper `_ published. The cooperation continues exchanging real-time arrival times as well as amplitudes upon request from EMSC for each crowdsourced detection. Aiming at introducing a new service providing the Energy Magnitude in real-time we started testing, in cooperation with ISC and Section 2.6, the procedure proposed by Di Giacomo et al., 2008. We carried out the analysis of a data set including all events published in the GEOFON catalogue since 2011 with available moment tensor solution: 6106 Earthquakes; January 2011 - April 2020; 4.63 millions records. The first results will be presented at the `EGU `_ annual meeting 2020. Software development ~~~~~~~~~~~~~~~~~~~~ Software development focused on preparing the new version of SeisComP 4.0.0 AGPL in cooperation with gempa GmbH for release in spring 2020. Another major activity has been the redesign of the web pages launched in October. The authentication service developed for EIDA has been successfully rolled out and used for the first time to access restricted data in EIDA via standard fdsn web services (AlpArray). New GEOFON web pages <<<<<<<<<<<<<<<<<<<< The new web pages went live in October and as shown in :numref:`eqinfo_5` we observed a traffic increase in coincidence with the release that is not related to the launch of the new web site though. We ivestigated the number of distinct users accessing the web pages during that period and this investigation confirms that most of the traffic came from automatic services (e.g. mobile apps and browsers). The new web pages have been optimised for mobile devices which is from where about half of our users are coming today. Together with the new web pages we launched also the GEOFON `forum `_ where the EQ alerts are posted. SeisComP releases and usage (in cooperation with GEMPA) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< The following SeisComP 3 releases were published in 2019: 2018.327.03 on January 7th 2019; 2018.327.13 on May 24th; 2018.327.15 on July 26th; 2018-327.21 on December 5th. 33 new non-commercial licenses were released in 2019 (total 555 at the end of 2019). Impact, Outreach and Capacity Building ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ GEOFON data, services and products have been cited in ~700 papers published in ISI journals up to 2019 (~70 added in 2019). The full list of publications which explicitly acknowledged use of GEOFON products is available at https://geofon.gfz-potsdam.de/references/ and updated to 04.2020. In 2019 GEOFON staff have presented at several conferences and contributed to several training events. In particular lectures and presentations about the usage of GEOFON products were given at the following events/venues: * GFZ International Training Course, Potsdam, Germany. * BMKG Jakarta, Indonesia. * EGU Annual meeting, Vienna, Austria * AG Seismologie annual meeting, Rastatt, Germany * DGG Annual meeting, Munster, Germany * ORFEUS/EPOS workshop, Grenoble, France * SULU workshop OBS data, Potsdam, Germany Additionally we were invited to two singular outreach events: `"Erschütterungen" `_ (Shaking in the society) at the "Literarische Colloquium Berlin" and at `"WundeErde" `_ a series of events hosted at the Italian Embassy in Berlin where we contributed with a seminar about Earthquake research and prevention. GEOFON running projects ~~~~~~~~~~~~~~~~~~~~~~~ Geo-Data-Node (Ended in September) <<<<<<<<<<<< - Description and tasks: GDN aims to improve data management practices at GFZ by fostering the implementation and practice of research data guidelines recently approved by GFZ. These guidelines are inspired by the FAIR data principles. Specifically the GEOFON team developed procedures to improve internal data policies. Relations between existing Persistent Identifiers have been reviewed for a better discovery of all resources related to a data set. In synergy with GIPP we have adopted Persistent Identifiers (PID) for instruments and jointly worked towards an API aiming at facilitating seismic metadata creation. This work has been coordinated internationally with the Research Data Alliance (RDA). Finally templates for the GFZ's existing Scientific Technical Report series have been created to facilitate creation of STR to complement the data sets in archive. - Duration: 2017-2019 - Funded by: BMBF - PI: R.Bertelmann (GFZ) - 12 PMs EPOS-IP (Ended in September) <<<<<<<<< - Title: European Plate Observing System - Implementation Phase - Description and tasks: EPOS-IP aims at creating a pan-European infrastructure for solid Earth science to support a safe and sustainable society. GEOFON and Section 2.6 at the GFZ are contributing to the Seismology Thematic Core Service (TCS). GEOFON is responsible for the coordination of the EIDA Next Generation development and contributes to strategic activities and governance. In particular for EIDA-NG the GEOFON team has developed the Routing Service, the Authorization system and updated the Web Interface to access data (WebDC3). In addition to the newly developed services GEOFON provided continuous update, improvements and new features in the SeisComP3 software package to facilitate data centre operations. Client side software independent of SeisComP3 has been developed (fdsnws_fetch) and more sophisticated clients are being developed. Coordination of the developments is ensured through the active participation of GEOFON managers and developers in the Management Board and Technical boards of EIDA. - Duration: 2015-2019 - Funded by: European Commission - Local PI at GFZ: J. Lauterjung - PI: M. Cocco (INGV) - 22 PMs EOSC-Hub <<<<<<<< - Title: Integrating and managing services for the European Open Science Cloud - Description and tasks: The EOSC-Hub project creates the integration and management system of the future European Open Science Cloud that delivers a catalogue of services, software and data from the EGI Federation, EUDAT CDI, INDIGO-DataCloud and major research e-infrastructures. The Hub acts as a single contact point for researchers from scientific communities to discover, access, use and reuse a broad spectrum of resources for advanced data-driven research. GEOFON will be responsible for the tasks related to the Authentication and Authorization (AAI) system, as well as the Federated Data Life Cycle. In the case of AII, this extends from the initial collection of requirements, to definition of attributes roles and rules, to design and prototype development and finally to validation and assessment. In the case of the Federated Data Life Cycle, we will work on the design of automatic workflows for seismological data centres, including replication, persistent identifiers (PID) creation, and improvements in the data distribution. In a final stage, when services are already in production, we will focus on the training activities (e.g.: seminars, workshops) to foster the adoption of the services beyond seismology. - Duration: 2018-2020 - Funded by: European Commission - Local PI at GFZ: J. Quinteros - PI: Y. Legre (EGI - Netherlands) - 15 PMs SERA <<<<<<<< - Title: Seismology and Earthquake Engineering Research Infrastructure Alliance - Description and tasks: The Seismology and Earthquake Engineering Research Infrastructure Alliance for Europe (SERA) aims to reduce the risk posed by natural and anthropogenic earthquakes based on innovative research and development projects. SERA will significantly improve the access to data, services and research infrastructures for scientists and other professionals. The GEOFON team, together with four EIDA node operators, will work towards consolidating the European Integrated Data Archive infrastructure with particular focus on facilitating the integration of new data and nodes as well as improving the user experience. We are specifically contributing to: (i) extend EIDA to integrate data types from OBS, induced seismicity observation networks, structural monitoring arrays, etc.; (ii) facilitate integration and long-term sustainability by providing extensive documentation, best practice guidelines for data acquisition and distribution as well as technical support; (iii) connect key scientists to the main operators of seismological networks to design the future generation of monitoring tools for Europe. - Duration: 2017-2020 - Funded by: European Commission - Local PI at GFZ: F. Cotton - PI: D. Giardini (ETHZ - Switzerland) - 5 PMs EOSC-Pillar (Started in June) <<<<<<<< - Title: EOSC-Pillar - EOSC-Pillar is one of the European Open Science Cloud (EOSC) regional projects such as EOSC Nordic, NI4OS-Europe, EOSC Synergy and ExPaNDS. These projects aim to coordinate the efforts of the national and thematic initiatives in making a coherent contribution to EOSC, a virtual environment with open and seamless services for storage, management, analysis and re-use of research data, across borders and scientific disciplines. GFZ will work on a system describing Research Data Collections and enabling action on them (e.g. create, read, update, delete). Machine agents will be primary users of this type of systems, in which scalability and automation are important features. The system exposes a well defined API against which tools and services can be built across community boundaries. The Collection storage is agnostic and will be able to work with multiple backends. For Large-N deployments and Distributed Acoustic Sensing (DAS) we will evaluate and review the currently used metadata and data formats and investigate other options. For instance, consider alternative formats for large volumes of data suitable also for ingestion at HPC facilities e.g. PH5 (HDF5 format) possibly adding a new output format to the current FDSN services while preserving the miniSEED format output. Consider a revision of the metadata to accommodate non-conventional seismic sensors and in particular to the DAS applications with the description of virtual sensors along the fibre-optic cables. Also evaluate the impact in storage and extra computational resources needed for our service in case of adoption of the new formats. - Duration: 2019-2022 - Funded by: European Commission - Local PI at GFZ: J. Quinteros - PI: P. Ruggeri (GARR - Italy) - 36 PMs RISE (Started in September) <<<<<<<< - Title: Real-time earthquake risk reduction for a ReSilient Europe - The key objective of RISE is to advance real-time earthquake risk reduction capabilities for a resilient Europe. With an improved scientific understanding and the use of emerging technologies human and economic losses shall be further reduced. New measures are needed to compliment present efforts in implementing building codes and retrofitting existing structures. GEOFON (and its other 3 partners from ORFEUS) will investigate the challenges posed to major seismological data centers - like the ORFEUS Data Center (ODC) and other primary EIDA nodes (GFZ, INGV, ETHZ) – by the emerging methodologies and technologies in real-time observational seismology. Examples include: (i) very large density arrays of ‘traditional’ seismic instrumentation (link with Task 2.4); (ii) low cost MEMS acceleration sensor, largely used for dense structural monitoring and the emerging EEW applications through their integration in standard smartphones; (iii) optical fibres and distributed acoustic sensing, technologies with the potential to mimic a seismic observatory managing billions of sensors. - Duration: 2019-2022 - Funded by: European Commission - Local PI at GFZ: D. Schorlemmer - PI: S. Wiemer (ETHZ - Switzerland) - 6 PMs Publications by GEOFON staff ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Bindi, D., Zaccarelli, R., Strollo, A., Di Giacomo, G. (2019): Harmonized local magnitude attenuation function for Europe using the European Integrated Data Archive (EIDA). - Geophysical Journal International, 218, 1, 519-533. https://doi.org/10.1093/gji/ggz178 Steed, R. J., Fuenzalida, A., Bossu, R., Bondár, I., Heinloo, A., Dupont, A., Saul, J., Strollo, A. (2019): Crowdsourcing triggers rapid, reliable earthquake locations. - Science Advances, 5, 4, eaau9824. https://doi.org/10.1126/sciadv.aau9824 Zaccarelli, R., Bindi, D., Strollo, A., Quinteros, J., Cotton, F. (2019): Stream2segment: An Open‐Source Tool for Downloading, Processing, and Visualizing Massive Event‐Based Seismic Waveform Datasets. - Seismological Research Letters, 90, 5, 2028-2038. https://doi.org/10.1785/0220180314 Walter, T. R., Haghshenas Haghighi, M., Schneider, F. M., Coppola, D., Motagh, M., Saul, J., Babeyko, A. Y., Dahm, T., Troll, V. R., Tilmann, F., Heimann, S., Valade, S., Triyono, R., Khomarudin, R., Kartadinata, N., Laiolo, M., Massimetti, F., Gaebler, P. (2019): Complex hazard cascade culminating in the Anak Krakatau sector collapse. - Nature Communications, 10, 4339. https://doi.org/10.1038/s41467-019-12284-5 GEOFON Team (Human Resources) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ======================= ======= ===== ======= ====== ========== ======== ================== Name GE Net. GE DC EQ info GE op. Soft. Dev. Outreach Funding ======================= ======= ===== ======= ====== ========== ======== ================== Angelo Strollo x x x x x GFZ Thomas Zieke x GFZ Karl-Heinz Jäckel[*] x GFZ Javier Quinteros x x x EOSC-Hub/GDN/SERA Susanne Hemmmleb x GFZ Laura Hillmann[†] x BMKG-GEMPA/GFZ Riccardo Zaccarelli[*] x x EPOS-IP/GFZ Joachim Saul[*] x x x x GFZ Andres Heinloo x x x x x GFZ Peter Evans x x x x x x GFZ ======================= ======= ===== ======= ====== ========== ======== ================== [*] Not working full time for GEOFON [†] Since July 2019 GEOFON Advisory Committee Members ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr. Florian Haslinger, Chair, ETH Zurich, Zurich,CH Dr. Christian Bönnemann, BGR Hannover, D *(until August 2019)* Dr. Klaus Stammler, BGR Hannover, D *(since September 2019)* Prof. Dr. Wolfgang Friederich, RU Bochum, Bochum, D Prof. Dr. Thomas Meier, CAU Kiel, D Prof. Dr. Max Wyss International Centre for Earth Simulation, Geneva, CH Dr. Jan Zednik, GFU Prague, CZ Acknowledgements ~~~~~~~~~~~~~~~~ We acknowledge partners co-operating GEOFON stations and data providers enabling us to create the so called GEOFON Extended Virtual Network `(GEVN) `_ used for the rapid earthquake information. We are also thankful to users and in particular to our advisory committee for their valuable feedbacks. Thanks to Rens Hofman (FU Berlin) who kindly joined the mission to Summit (Greenland), to provide support during the moving of the seismic vault of the SUMG station. We would like to finally acknowledge also our former GEOFON head Winfried Hanka for his kind support and suggestions when asked. References ~~~~~~~~~~ Di Giacomo, D., Grosser, H., Parolai, S., Bormann, P., and Wang, R. (2008), Rapid determination of Me for strong to great shallow earthquakes, Geophys. Res. Lett., 35, L10308, doi:10.1029/2008GL033505. McNamara, Daniel & Buland, Raymond. (2004). Ambient Noise Levels in the Continental United States. Bulletin of the Seismological Society of America. 94. 1517-1527. 10.1785/012003001. Appendices ~~~~~~~~~~ Probability Density Functions (PDF) for operational GEOFON stations 01.2019 - 12.2019 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< The PDF displayed in this appendix have been calculated with PQLX v. 2011.365.P4 (McNamara & Buland 2004) only for the primary channels, that is generally a Broad-Band sensor at 20 Hz. Only operational stations during the year have been included, stations that were off-line for most of time are not included in this appendix. .. note that the :width: option is buggy (does not render the same in LaTex and HTML). The solution is to issue a includegraphics directive to force each column in the next `gridfigure` directive to be 33% (1/the number of columns) .. includegraphics:: width=.33\textwidth .. gridfigure:: GE Network PSDs (2019) :dir: ./data/PDF :delim: space :header-rows: 0 :errorsastext: true GE.ACRG.--.BHE.ALL.png GE.ACRG.--.BHN.ALL.png GE.ACRG.--.BHZ.ALL.png GE.APE.--.BHE.ALL.png GE.APE.--.BHN.ALL.png GE.APE.--.BHZ.ALL.png GE.ARPR.--.BHE.ALL.png GE.ARPR.--.BHN.ALL.png GE.ARPR.--.BHZ.ALL.png GE.BALJ.--.BHE.ALL.png GE.BALJ.--.BHN.ALL.png GE.BALJ.--.BHZ.ALL.png GE.BBJI.--.BHE.ALL.png GE.BBJI.--.BHN.ALL.png GE.BBJI.--.BHZ.ALL.png GE.BKB.--.BHE.ALL.png GE.BKB.--.BHN.ALL.png GE.BKB.--.BHZ.ALL.png GE.BKNI.--.BHE.ALL.png GE.BKNI.--.BHN.ALL.png GE.BKNI.--.BHZ.ALL.png GE.BNDI.--.BHE.ALL.png GE.BNDI.--.BHN.ALL.png GE.BNDI.--.BHZ.ALL.png GE.BOAB.--.BHE.ALL.png GE.BOAB.--.BHN.ALL.png GE.BOAB.--.BHZ.ALL.png GE.CSS.--.BHE.ALL.png GE.CSS.--.BHN.ALL.png GE.CSS.--.BHZ.ALL.png GE.DAG.--.BHE.ALL.png GE.DAG.--.BHN.ALL.png GE.DAG.--.BHZ.ALL.png GE.DSB.--.BHE.ALL.png GE.DSB.--.BHN.ALL.png GE.DSB.--.BHZ.ALL.png GE.EIL.--.BHE.ALL.png GE.EIL.--.BHN.ALL.png GE.EIL.--.BHZ.ALL.png GE.FAKI.--.BHE.ALL.png GE.FAKI.--.BHN.ALL.png GE.FAKI.--.BHZ.ALL.png GE.FALKS.--.BHE.ALL.png GE.FALKS.--.BHN.ALL.png GE.FALKS.--.BHZ.ALL.png GE.FLT1.--.BHE.ALL.png GE.FLT1.--.BHN.ALL.png GE.FLT1.--.BHZ.ALL.png GE.GENI.--.BHE.ALL.png GE.GENI.--.BHN.ALL.png GE.GENI.--.BHZ.ALL.png GE.GHAJ.--.BHE.ALL.png GE.GHAJ.--.BHN.ALL.png GE.GHAJ.--.BHZ.ALL.png GE.GSI.--.BHE.ALL.png GE.GSI.--.BHN.ALL.png GE.GSI.--.BHZ.ALL.png GE.GVD.--.BHE.ALL.png GE.GVD.--.BHN.ALL.png GE.GVD.--.BHZ.ALL.png GE.HALK.--.BHE.ALL.png GE.HALK.--.BHN.ALL.png GE.HALK.--.BHZ.ALL.png GE.HLG.--.BHE.ALL.png GE.HLG.--.BHN.ALL.png GE.HLG.--.BHZ.ALL.png GE.HMDM.--.BHE.ALL.png GE.HMDM.--.BHN.ALL.png GE.HMDM.--.BHZ.ALL.png GE.IBBN.--.BHE.ALL.png GE.IBBN.--.BHN.ALL.png GE.IBBN.--.BHZ.ALL.png GE.ILTH.--.BHE.ALL.png GE.ILTH.--.BHN.ALL.png GE.ILTH.--.BHZ.ALL.png GE.IMMV.--.BHE.ALL.png GE.IMMV.--.BHN.ALL.png GE.IMMV.--.BHZ.ALL.png GE.ISP.00.BHE.ALL.png GE.ISP.00.BHN.ALL.png GE.ISP.00.BHZ.ALL.png GE.JAGI.--.BHE.ALL.png GE.JAGI.--.BHN.ALL.png GE.JAGI.--.BHZ.ALL.png GE.KAAM.--.BHE.ALL.png GE.KAAM.--.BHN.ALL.png GE.KAAM.--.BHZ.ALL.png GE.KARP.--.BHE.ALL.png GE.KARP.--.BHN.ALL.png GE.KARP.--.BHZ.ALL.png GE.KBS.00.BH1.ALL.png GE.KBS.00.BH2.ALL.png GE.KBS.00.BHZ.ALL.png GE.KBU.--.BHE.ALL.png GE.KBU.--.BHN.ALL.png GE.KBU.--.BHZ.ALL.png GE.KIBK.--.BHE.ALL.png GE.KIBK.--.BHN.ALL.png GE.KIBK.--.BHZ.ALL.png GE.KMBO.00.BH1.ALL.png GE.KMBO.00.BH2.ALL.png GE.KMBO.00.BHZ.ALL.png GE.KTHA.--.BHE.ALL.png GE.KTHA.--.BHN.ALL.png GE.KTHA.--.BHZ.ALL.png GE.LHMI.--.BHE.ALL.png GE.LHMI.--.BHN.ALL.png GE.LHMI.--.BHZ.ALL.png GE.LODK.--.BHE.ALL.png GE.LODK.--.BHN.ALL.png GE.LODK.--.BHZ.ALL.png GE.LUWI.--.BHE.ALL.png GE.LUWI.--.BHN.ALL.png GE.LUWI.--.BHZ.ALL.png GE.MALK.--.BHE.ALL.png GE.MALK.--.BHN.ALL.png GE.MALK.--.BHZ.ALL.png GE.MARCO.--.BHE.ALL.png GE.MARCO.--.BHN.ALL.png GE.MARCO.--.BHZ.ALL.png GE.MATE.--.BHE.ALL.png GE.MATE.--.BHN.ALL.png GE.MATE.--.BHZ.ALL.png GE.MMRI.--.BHE.ALL.png GE.MMRI.--.BHN.ALL.png GE.MMRI.--.BHZ.ALL.png GE.MNAI.--.BHE.ALL.png GE.MNAI.--.BHN.ALL.png GE.MNAI.--.BHZ.ALL.png GE.MORC.--.BHE.ALL.png GE.MORC.--.BHN.ALL.png GE.MORC.--.BHZ.ALL.png GE.MSBI.--.BHE.ALL.png GE.MSBI.--.BHN.ALL.png GE.MSBI.--.BHZ.ALL.png GE.MTE.--.BHE.ALL.png GE.MTE.--.BHN.ALL.png GE.MTE.--.BHZ.ALL.png GE.NPW.--.BHE.ALL.png GE.NPW.--.BHN.ALL.png GE.NPW.--.BHZ.ALL.png GE.PABE.--.BHE.ALL.png GE.PABE.--.BHN.ALL.png GE.PABE.--.BHZ.ALL.png GE.PBUR.--.BHE.ALL.png GE.PBUR.--.BHN.ALL.png GE.PBUR.--.BHZ.ALL.png GE.PLAI.--.BHE.ALL.png GE.PLAI.--.BHN.ALL.png GE.PLAI.--.BHZ.ALL.png GE.PMBI.--.BHE.ALL.png GE.PMBI.--.BHN.ALL.png GE.PMBI.--.BHZ.ALL.png GE.PMG.00.BH1.ALL.png GE.PMG.00.BH2.ALL.png GE.PMG.00.BHZ.ALL.png GE.PSZ.--.BHE.ALL.png GE.PSZ.--.BHN.ALL.png GE.PSZ.--.BHZ.ALL.png GE.PUL.--.BHE.ALL.png GE.PUL.--.BHN.ALL.png GE.PUL.--.BHZ.ALL.png GE.RGN.--.BHE.ALL.png GE.RGN.--.BHN.ALL.png GE.RGN.--.BHZ.ALL.png GE.RUE.--.BHE.ALL.png GE.RUE.--.BHN.ALL.png GE.RUE.--.BHZ.ALL.png GE.SALP.--.BHE.ALL.png GE.SALP.--.BHN.ALL.png GE.SALP.--.BHZ.ALL.png GE.SALTA.--.BHE.ALL.png GE.SALTA.--.BHN.ALL.png GE.SALTA.--.BHZ.ALL.png GE.SANI.--.BHE.ALL.png GE.SANI.--.BHN.ALL.png GE.SANI.--.BHZ.ALL.png GE.SANT.--.BHE.ALL.png GE.SANT.--.BHN.ALL.png GE.SANT.--.BHZ.ALL.png GE.SAUI.--.BHE.ALL.png GE.SAUI.--.BHN.ALL.png GE.SAUI.--.BHZ.ALL.png GE.SBV.--.BHE.ALL.png GE.SBV.--.BHN.ALL.png GE.SBV.--.BHZ.ALL.png GE.SFJD.00.BH1.ALL.png GE.SFJD.00.BH2.ALL.png GE.SFJD.00.BHZ.ALL.png GE.SLIT.--.BHE.ALL.png GE.SLIT.--.BHN.ALL.png GE.SLIT.--.BHZ.ALL.png GE.SMRI.--.BHE.ALL.png GE.SMRI.--.BHN.ALL.png GE.SMRI.--.BHZ.ALL.png GE.SNAA.--.BHE.ALL.png GE.SNAA.--.BHN.ALL.png GE.SNAA.--.BHZ.ALL.png GE.SOEI.--.BHE.ALL.png GE.SOEI.--.BHN.ALL.png GE.SOEI.--.BHZ.ALL.png GE.STU.--.BHE.ALL.png GE.STU.--.BHN.ALL.png GE.STU.--.BHZ.ALL.png GE.SUMG.--.BHE.ALL.png GE.SUMG.--.BHN.ALL.png GE.SUMG.--.BHZ.ALL.png GE.THERA.--.BHE.ALL.png GE.THERA.--.BHN.ALL.png GE.THERA.--.BHZ.ALL.png GE.TIRR.--.BHE.ALL.png GE.TIRR.--.BHN.ALL.png GE.TIRR.--.BHZ.ALL.png GE.TNTI.--.BHE.ALL.png GE.TNTI.--.BHN.ALL.png GE.TNTI.--.BHZ.ALL.png GE.TOLI2.--.BHE.ALL.png GE.TOLI2.--.BHN.ALL.png GE.TOLI2.--.BHZ.ALL.png GE.UGM.--.BHE.ALL.png GE.UGM.--.BHN.ALL.png GE.UGM.--.BHZ.ALL.png GE.UJAP.--.BHE.ALL.png GE.UJAP.--.BHN.ALL.png GE.UJAP.--.BHZ.ALL.png GE.VAL.--.BHE.ALL.png GE.VAL.--.BHN.ALL.png GE.VAL.--.BHZ.ALL.png GE.VOI.--.BHE.ALL.png GE.VOI.--.BHN.ALL.png GE.VOI.--.BHZ.ALL.png GE.VSU.--.BHE.ALL.png GE.VSU.--.BHN.ALL.png GE.VSU.--.BHZ.ALL.png GE.WIN.--.BHE.ALL.png GE.WIN.--.BHN.ALL.png GE.WIN.--.BHZ.ALL.png GE.WLF.--.BHE.ALL.png GE.WLF.--.BHN.ALL.png GE.WLF.--.BHZ.ALL.png GE.ZKR.--.BHE.ALL.png GE.ZKR.--.BHN.ALL.png GE.ZKR.--.BHZ.ALL.png WM.AVE.--.BHE.ALL.png WM.AVE.--.BHN.ALL.png WM.AVE.--.BHZ.ALL.png WM.CART.--.BHE.ALL.png WM.CART.--.BHN.ALL.png WM.CART.--.BHZ.ALL.png WM.MAHO.--.BHE.ALL.png WM.MAHO.--.BHN.ALL.png WM.MAHO.--.BHZ.ALL.png WM.SFS.--.BHE.ALL.png WM.SFS.--.BHN.ALL.png WM.SFS.--.BHZ.ALL.png WM.TIO.--.BHE.ALL.png WM.TIO.--.BHN.ALL.png WM.TIO.--.BHZ.ALL.png Annexes ~~~~~~~~ Summary of GE maintenance team activities <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< An overview of the activity is provided in Annex 1. For each action at the station a short description is included. The summary includes also support activities for other groups within GFZ. `Annex 1: GE Network maintenance summary (2019) `_ .. ============================================================================== .. RST syntax help =============== (you can delete this section when no longer needed / after completion of editing) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ TEXT FORMATTING: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is an example of "normal" body text. It's not in a comment block. Remeber that indentation is a special RsT command and that newlines are actually not rendered (this is a newline and you shouldn't see any difference in html or latex) But you can type a new paragraph by adding an empty line above it (like in this case) Italic can be rendered by wrapping text within two asterix, bold by wrapping text within two couples of asterix: *This is rendered in italic*, **this is rendered in bold** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ HYPERLINKS: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Hyperlink (inline): simply type them: Urls are automatically recognized and linked: http://www.python.org/ Hyperlink with substitution text: point to the same url as above but display 'Python' in the built document: `Python `_ Hyperlink with substitution text, if it has to be referenced more than once. Define the hyperlink as follows: .. _Wikipedia: https://www.wikipedia.org/ And then reference them like this: Wikipedia_, and again, Wikipedia_ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ TEXT SUBSTITUTIONS: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ When the a text is repeated many times throughout one or more documents, especially if it may need to change later, define a text substitution like this (note that the line below is NOT rendered but is NOT a comment): .. |RsT| replace:: ReStructuredText Then, to see "ReStructuredText", type: |RsT| Note that by placing a backslash before a character, you render that character literally. To see "|RsT|", type "\|RsT\|", e.g.: |RsT| was obtained by typing \|RsT\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ MATH FORMULAE: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Inline math formulae, use :math:`...` or latext dollar sign with latex syntax inside (the latter is not standard rst, but is implemented in this report): Here an inline math expression: :math:`(\alpha > \beta)` = $(\alpha > \beta)$ More complex math formulae, use ..math:: then new empty line and INDENTED text, e.g.: .. math:: n_{\mathrm{offset}} = \sum_{k=0}^{N-1} s_k n_k ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ FOOTNOTES: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Footnotes with manual numbering: .. [1] First footnote .. [2] Second footnote, note that newlines which must be indented Here a ref to the first footnote [1]_ and here to the second [2]_. Footnotes with auto numbering (newlines must be INDENTED of at least three spaces): .. [#] First footnote (autonumbered) .. [#] Second footnote (autonumbered), note that newlines which must be indented Here a ref to the first footnote [#]_ and here to the second [#]_. Footnotes with auto numbering, referenced more than once (newlines must be INDENTED of at least three spaces): .. [#firstnote] First footnote (autonumbered, referenced more than once) .. [#secondnote] Second footnote (autonumbered, referenced more than once), note that newlines which must be indented Here a ref to the first footnote [#firstnote]_, again [#firstnote]_ and here to the second [#secondnote]_. Footnotes with auto symbols. DEPRECATED: seems they are buggy in latex: .. [*] First footnote (autosymbol) .. [*] Second footnote (autosymbol), note that newlines which must be indented Here a ref to the first footnote [*]_, and here to the second [*]_. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ CITATIONS: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Citations are identical to footnotes except that their labels must be case-insensitive single words of alphanumerics plus internal hyphens, underscores, and periods. No whitespace, no numeric only. E.g.: .. [CIT2002] Deep India meets deep Asia: Lithospheric indentation, delamination and break-off under Pamir and Hindu Kush (Central Asia). http://doi.org/10.1016/j.epsl.2015.11.046 Here a reference to a publication: [CIT2002]_. And here another reference to it ([CIT2002]_) IMPORTANT NOTE: Citations are automatically placed in latex in a "References" section at the end of the document, regardless of where they are input. Conversely, in HTML they are rendered where they are input. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ NUMERIC REFERENCES TO FIGURES AND TABLES: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Providing a label placed IMMEDIATELY BEFORE a specific directive (e.g. figure, table, see below): .. _labelname you can reference it in the text with :numref:`labelname` ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ LIST ITEMS: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Bullet lists (blank line before and after the list): - This is a bullet list. - Bullets can be "*", "+", or "-". Enumerated lists (blank line before and after the list): 1. This is an enumerated list. 2. Enumerators may be arabic numbers, letters, or roman numerals. Nested lists (blank lines are optional between items on the same level): * About RsT syntax: - https://pythonhosted.org/an_example_pypi`_project/sphinx.html (and links therein) - http://docutils.sourceforge.net/docs/user/rst/quickref.html * About Sphinx syntax (RsT with some commands added) - http://www.sphinx-doc.org/en/stable/rest.html#rst-primer ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ FOR DETAILS: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - About RsT syntax: + http://docutils.sourceforge.net/rst.html - About Sphinx: + http://www.sphinx-doc.org/en/stable/markup/index.html#sphinxmarkup