SCORESBYSUND
Station summarySCOR
| IGS-type acronym : | SCOR |
| Latitude : | 70.48533317 |
| Longitude : | -21.95033554 |
| Installed date : | 1997-08-07 |
| Decommissioned date : | |
| Country : | GREENLAND (DENMARK) |
| City: | SCORESBYSUND |
| Station status : | active (green) |
| Distance to Tide Gauge (m) : | 450 |
| Domes Nr.: | 43006M002 |
| Station operator: | Unknown |
| IGS-like station form : |
GPS position times seriesSCOR
(Reference epoch: )
| M | Material change or malfunction |
| E | Earthquake |
| RF | Reference Frame change |
| U | Unknown |
| NA | Not available |
| Position discontinuity | |
| Velocity discontinuity |
Data available at SONELSCOR
Quality plots on RINEX filesSCOR
 |
 |
Plots generated using software developed with the EPN team at ROB |
| Observations & tracking performance | Satellite tracking |
(this operation may take 20 to 45s)
The satellite tracking graph has been calculated for all stations for the first day of each month. If you wish to have a graph for another date, choose the 'Calculate a specific date' option.
Co-located instrumentsSCOR
- Tide gauge : SCORESBYSUND (SCOTG)
Photo albumSCOR
Log bookSCOR
[IGSSTATION-7864] - 2020-02-05 (17/03/2020)
QAQ1, SCOR firmware have been updated version 5.3.2
[IGSSTATION-7745] - 2019-09-26 (27/09/2019)
QAQ100GRL and SCOR00GRL have been firmware upgraded from V 5.2.0 to V 5.3.0, and updated sitelogs are submittet.
[EUREFmail-9619] - 2018-11-07 (08/11/2018)
Cable repairs are completed and data flow has been resumed for our sites (QAQ1, SCOR, THU2, THU3).
[EUREFmail-9617] - 2018-11-06 (08/11/2018)
Today all the fiber cables to our server room was cut under construction work on campus. This will cause data outage for all of our sites (QAQ1, SCOR, THU2, THU3), for an unknown period of time - probably several days.
[EUREFmail-9558] - 2018-09-27 (02/10/2018)
An error in the RINEX header for SCOR has been corrected for files from 2017 DOY 194 through 2018 DOY 100, and the corrected files has been uploaded to BKG, BEV
[EUREFmail-9218] - 2017-12-06 (13/12/2017)
Due to a power loss data between Day 338-12:08 and 339-11:44 are missing.
[IGSSTATION-7073] - 2017-07-14 (17/07/2017)
The PC at SCOR has suffered a fatal crash, and thus data logging is interrupted for an unknown period of time.
[IGSSTATION-7066] - 2017-07-09 (12/07/2017)
A program error (GBSS) interrupted the data logging, causing a gap between 189 09:45 – 190 14:00.
[IGSSTATION-7059] - 2017-07-04 (05/07/2017)
A program error (GBSS) interrupted the data logging, causing a gap between 184 03:38 – 185 08:25.
[IGSSTATION-7032] - 2017-05-24 (29/05/2017)
The Computer that handles SCOR data logging is operationa again, and data logging is resumed.
Data between 2017-05-22:08:59:59 and 2017-05-24:09:38:59 are lost.
[EUREFmail-9018] - 2017-05-23 (24/05/2017)
The Computer that handles SCOR data logging has suffered a serious hardware failure and all data logging will be interrupted until further notice.
[IGSSTATION-6956] - 2017-02-17 (20/02/2017)
The router at SCOR has been replaced, and normal operation is resumed.
[IGSSTATION-6937] - 2017-02-01 (08/02/2017)
The router at the site has failed, and will need replacement. Until the affected equipment has been replaced we are unable to deliver data from SCOR.
[IGSSTATION-6572] - 2016-03-16 (23/03/2016)
The RINEX header has been updated with the full receiver serial number, to match the information in the sitelog.
[IGSSTATION-6379] - 2015-11-06 (13/11/2015)
Data logging at SCOR has been resumed at Julian Day 2015-310 at approximately 1700.
The reason for the interruption was a damaged antenna cable.
[IGSSTATION-6376] - 2015-11-04: Data logging at SCOR has been interrupted at Julian Day 2015-306 at approximately 1500.
The reason is unknown, and therefore we are unable to give a reliable estimate as to when logging will resume.
[IGSSTATION-6072] - 2015-01-20 (20/01/2015)
Data logging at SCOR has resumed spontaneously on Julian day 017, and has been performing normally since.
[IGSMAIL-7020] - 2014-12-20 (22/12/2014)
Data logging at SCOR has stopped since Julian day 352, for an unknown reason.
A replacement receiver has been shipped, but data collection must be expected to be inoperative for an unknown period, due the low frequency of package deliveries at the location.
