the Creative Commons Attribution 4.0 License.
the Creative Commons Attribution 4.0 License.
GNSS time series and velocities about a slow convergent margin processed on HPC clusters: products and robustness evaluation
Andrea Magrin
Giuliana Rossi
David Zuliani
Abstract. Global Navigation Satellite Systems are well-known fundamental tools for crustal monitoring projects and tectonic studies, thanks to the high coverage and the high-quality data. In slow convergent margins, in particular, where the deformation rates are of the order of few mm/yr, the GNSS monitoring is beneficial to detect the diffused deformation which is responsible for the tectonic stress accrual. Its strength is the high precision reached by GNSS permanent stations, particularly if long span-data and stable monuments are available at all the stations. North-East Italy is a region which can take the most from continuous and high-precision geodetic monitoring, since it is a tectonically active region located in the northernmost sector of the Adria microplate, slowly converging with the Eurasia plate, but characterised by low deformation rates and moderate seismicity. Furthermore, this region is equipped with a permanent GNSS network providing real-time data and daily observations over two decades. The Friuli Venezia Giulia Deformation Network (FReDNet) was established in the area in 2002 to monitor crustal deformation and contribute to the regional seismic hazard assessment. This paper describes GNSS time series spanning two decades of stations located in the NE-Italy and surroundings, as well as the outcoming velocity field. The documented dataset has been retrieved by processing the GNSS observations with the GAMIT/GLOBK software ver10.71, which allows calculating high-precision coordinate time series, position and velocity for each GNSS station, and by taking advantage of the high-performance computing resources of the Italian High-Performance Computing Centre (CINECA) clusters.
The GNSS observations (raw and standard RINEX formats) and the time series estimated with the same procedure are currently daily continued, collected and stored in the framework of a long-term monitoring project. Instead, velocity solutions are planned to be updated annually. The time series and velocity field dataset documented here is available at https://doi.org/10.13120/b6aj-2s32 (Tunini et al., 2023).
- Preprint
(26618 KB) - Metadata XML
- BibTeX
- EndNote
Lavinia Tunini et al.
Status: open (until 28 Oct 2023)
-
AC1: 'Comment on essd-2023-131', Lavinia Tunini, 23 Jun 2023
reply
Dear Editor,ÂIn the current version of the manuscript, the cited folder for the dataset is a folder located in an internal repository within our Institution. Since we understand your concerns, we decided to move the dataset into the Zenodo repository. In this way, the dataset will have the DOI 10.5281/zenodo.8055800 on Zenodo (DOI number is, for now, assigned as "reserved", but it will be definitive after the acceptance of the manuscript) and each of the compressed archives uploaded is characterized by its own md5 checksum code, which guarantees for its consistency.ÂA preview screenshot of the Zenodo uploaded dataset is attached.As a consequence, the reviewed version of the manuscript will cite, accordingly, that the dataset is available into Zenodo with the DOI 10.5281/zenodo.8055800.ÂBy the way, in order to increase the usability of the dataset, we will maintain also a copy of it in the internal repository at the link https://frednet.crs.ogs.it/frednet_data/Projects/2022.OGS.GPS.solution/ , and the consistency between the files deposited here and the ones on Zenodo can be checked through the checksum of the compressed archives.ÂConcerning the starting page of FRedDNet, we are aware that it requires a huge style update. We are on the way to completely renovate this webpage in the next future in order to make it clearer and more user-friendly. For the moment, for the sake of clarity, we added the caption "Data available on DOI:10.60192/frednet" on both English and Italian versions of the FReDNet website (see the right panel on https://frednet.crs.ogs.it/EnglishSite/XFReDNetHomeENG.htm). However, we would like to recall here that, in the manuscript, we have cited only the frednet repository https://frednet.crs.ogs.it/DOI/ for the daily and continuous frednet stations' data distributionÂBest regardsLavinia Tunini on behalf of all co-authors
-
RC1: 'Comment on essd-2023-131', Anonymous Referee #1, 05 Jul 2023
reply
The manuscript submitted by Tunini et al. describes GNSS processing for station networks in Italy. While the topic is of general interest and fits the journal's scope, I see serious issues with the current draft. From a geodetic point of view, I like to ask the authors to revise the paper carefully. There are several issues with using geodetic terminology and common geodetic knowledge. Moreover, I found several inconsistencies and wording issues that have to be clarified. Finally, the authors report lengthy technical details clearly specified in different guidelines, these paragraphs should be rewritten in a much shorter way. Overall, I'm in favor of recommending the paper for publication after some general editing.
Detailed comments:
l10 please re-phrase "take the most from ..."
l25 please re-phrase "GNSS provides a", strictly spoken GNSS provides some navigatio signals to the users ....
l27 what is "GNSS technology"?
l30 what is a GNSS sensor, I guess you are referring to the antenna?
l31 you can determine sub-mm positions just from one day, I guess you are referring to time series? You might add clock corrections to the precise orbits
l40ff There is no need to explain why you processed the data individually. However, please cite NGL in a proper way and re-phrase "tune" by "customize"
l44 "beginning of the century" means "early 2000s"?
l57 XX century = 20 century?
l61 15-20km is the spatial resolution (or the station distance) but not the scale. "A more" sounds wrong?
l66 what do you consider as positions? Do you distinguish between coordinates and positions?
Fig 2 check the wording
l105 references for ITRF2014 and IGS are missing
l111 "tens of data" -> "tens of stations"?
Fig3 could you explain the drop in 2013?
l130 please shorten this part, these are common geodetic standards
l143 "log sheets" -> "sitelogs"
l149 Please rephrase "piece of information ..." + shorten this part, you don't need to report the IGS site guidelines (just cite them)
l202 language check for "that implements"
l212 you are using a Helmert blocking approach (clustering) which is very useful
l215 Honestly, I don't understand the issue with these old receivers. Are these cross-correlation receivers?
l221 in terms of orbits you should not write "fixed to ... values", they are introduced apriori (the fixing is obvious if you don't estimate orbits). However, a reference is missing here.
Tab1 2nd order ionosphere is corrected using the IONEX, please re-phrase; what's about other non-tidal loadings; I miss the orbit & clock products here; please add the estimated parameters and their characteristic here
l235 I guess this sentence is about the datum definition. Please explain clearly what was done and why.
l244 what's the meaning of "combining"? Are you stack normal equations?
l251 usually we call them "datum sites" or "datum stations", the term "stabilization sites" might be a bit outdated
Fig6 there are well-known assessments of computation time regarding number of stations, you might reference related publications
Fig7 what is "stabilization", if these are the "datum stations" you are going to constrain most of your stations. Is there any reason for doing this? Usually, you estimate stations in the area of investigation as free as possible ...
l297 what are stabilization errors?
l312 I don't understand the consideration of velocity biases. I don't think this is used in Blewitt and Lavallee, 2002. Why do you cite Masson et al 2019 in this regard?
l320ff We might have new stations but they are not young. Language check for "between others, we cite"
Fig 10 remove topography from these plots, are you showing vz (velocity in z direction)? Overall, you are assuming uncorrelated coordinates in the velocity determination?
l370 the difference between VMF1 and GMF was done by many colleagues, refer to their studies. It's kind of useless to skip ocean tide loading, I recommend to remove this part.
l391 What are "time changes in the environment"
l412 What is "variable atmopsheric noise"?
Â
Â
Â
Â
Â
Â
Citation: https://doi.org/10.5194/essd-2023-131-RC1 -
AC2: 'Reply on RC1', Lavinia Tunini, 31 Jul 2023
reply
We thank the Reviewer for the constructive comments and suggestions. We shall revise the manuscript accordingly, and we address the comments as reported in the attached pdf file.
Â
-
AC2: 'Reply on RC1', Lavinia Tunini, 31 Jul 2023
reply
Lavinia Tunini et al.
Data sets
GNSS time series and velocities about a slow convergent margin processed on HPC clusters: products and robustness evaluation Lavinia Tunini, Andrea Magrin, Giuliana Rossi, David Zuliani https://doi.org/10.13120/b6aj-2s32
Lavinia Tunini et al.
Viewed
HTML | XML | Total | BibTeX | EndNote | |
---|---|---|---|---|---|
302 | 65 | 15 | 382 | 5 | 6 |
- HTML: 302
- PDF: 65
- XML: 15
- Total: 382
- BibTeX: 5
- EndNote: 6
Viewed (geographical distribution)
Country | # | Views | % |
---|
Total: | 0 |
HTML: | 0 |
PDF: | 0 |
XML: | 0 |
- 1