IGS New Site Checklist
This document is intended to serve as a checklist for station owners and
operators (SO) in proposing new IGS stations.
To initiate the application, submit
the following information by email to the Central Bureau (cb @ igs.org) or complete the online application form located (here):
Where is the station
Is the station
currently operating, or planned? If planned, when is the projected date it will
What agencies are
responsible for installing, managing, operating, and maintaining the station?
What is the expected
operational lifetime of the station? How secure is the funding?
Will the station
replace an existing IGS station? If so, what is the scheduled date of
decommissioning? Does the new station offer more capability than the old one?
Does/will the station
meet all of the strictly required IGS site guidelines (http://www.igs.org/network/guidelines/guidelines.html)?
What is the data
Can you set the
receiver for "all in view" tracking (including tracking of satellites
Are there currently
operating IGS stations within 1000km? Approximately how many? Does this site
offer any capabilities the others do not?
What IGS product or
project will this site benefit, based on its location, instrumentation, and
Is this station
intended to tie a national datum to the ITRF?
Is there a web page
associated with this site (please specify)? If not, please include a site photo
or two with this application.
Is data available on
a public server (please specify)?
Complete and include
a draft site log (ftp://igs.org/pub/station/general/blank.log)
according to the instructions (ftp://igs.org/pub/station/general/sitelog_instr.txt).
The proposed four
character identifier should also be included, but it remains proposed only
until confirmed by the CB. Allowed characters are A-Z and 1-9 (numerals may not
be used in the first character). You may perform an initial check of the
availability using http://sopac.ucsd.edu/scripts/checkSiteID.cgi. If the result is "available" it is certainly
available. If this web page indicates it "may already be in use," it might
be available for permanent stations anyway.
A new 4-char ID is
required if a site is moved to a new monument. The 4-char ID has a one-to-one
relationship with a monument, except in the case that more than one receiver
records data from one antenna.
primary and secondary IGS Data Centers (see http://www.igs.org/organization/centers.html), but it is not necessary to confirm arrangements with the DCs at this
The Central Bureau will reflect
this site on the schedule of future or proposed stations at http://www.igs.org/network/proposed.html and the IGS analysis community will be notified of the proposal.
If the site is requested to be
added by an IGS Analysis Center, you will be asked to:
Visit http://itrf.ensg.ign.fr/domes_request.php to request an IERS DOMES number if the monument has not already been
Contact the primary
and secondary Data Centers to confirm that they can accept the data and learn
about the transfer mechanisms.
Revise the site log,
if necessary, with confirmed IERS DOMES number, DCs, equipment codes, and
4-character ID. Validate the format of the sitelog via http://igs.org/network/sitelog_tester.php.
Logs should then be sent to the Central Bureau as plain
ASCII text. Notify the CB where a recent RINEX file may be downloaded, or
include a sample RINEX header (header only!) in the email to the CB.
When the site log
becomes available in ftp://www.igs.org/pub/station/log/, begin transmitting RINEX to the selected Data Center(s). The CB will
announce the station on IGSMail.
Subscribe to IGSMail,
IGSStation and IGS-SO mail lists to be prepared to send and receive important
emails about the station or IGS network as explained in the Site Guidelines.
If the new station is
part of a network, the responsible Operational Center must update the center
description form (download ftp://igs.org/pub/center/oper/ÕcenterÕ.acn,
modify, send via e-mail to cb @ igs.org)
If the station is
part of a new network, the new Operational Center must create a center
description form (download ftp://igs.org/pub/center/oper/BLNKFORM.OCN,
modify, and send via e-mail to cb @ igs.org)
Commonly used links:
Site Log Form
Site Log Instructions
Number Request (IGN)
site code checker (SOPAC)
IGS Antenna Files Information
and antenna naming conventions: rcvr_ant.tab
file as of April, 2013: igs08.atx
E-Mail: cb @