The National Geodetic Survey
(NGS) has designed UFCORS as a web-interface to facilitate the retrieval of
GNSS data (prior to version 4.0 only GPS data could be retrieved)
and associated metadata from the Continuously Operating Reference
Station (CORS) Network. In particular, users can for a specific CORS site:
You should choose a date and start time that matches the start date you collected your observation data and a duration that covers all the data you collected. NGS recommends that in addition you buffer this time period by 30 min to 1 hour before and after to ensure you have complete overlap with the data you collected.
The RINEX files you receive are provided in the time format of the satellite system requested (which is very close to UTC time). Some users find it easier to work in their local time zone to identify their start times in which case switch from UTC to the appropriate GMT time.
e.g. Eastern Standard (GMT - 5)
Eastern Daylight Savings (GMT - 4)
Central Standard (GMT - 6)
Central Daylight Savings (GMT - 5)
Mountain Standard(GMT - 7)
Mountain Daylight Savings (GMT - 6)
Pacific Standard (GMT - 8)
Pacific Daylight Savings (GMT - 7)
Alaska Standard (GMT - 9)
Alaska Daylight Savings (GMT - 8)
Hawaii-Aleutian (GMT -10)
Guam, Saipan, Rota (GMT +10)
Some CORS stations are able to collect GPS +GLONASS data, if a station is collecting additional signals to GPS the box for GLONASS will automatically be selectable.
If the four-character identifier for a particular site does not appear in the list, then the site is not part of the CORS network. To check that you have the correct 4-character identifier go to the main CORS web page and check the CORS map to identify if the site is part of the CORS network.
A "coordinate" file contains the NGS computed position and velocity for the site's antenna reference point (ARP) as well as for its L1 phase center and possibly for the MON (monument). The ARP usually corresponds to the center point on the bottom of the CORS antenna. The coordinate file contains positions and velocities in both a global frame ITRF2014 and the North American Datum of 1983 (NAD 83). This file differs from the NGS datasheet for the site, which does not contain velocities or ITRF2014 coordinates, but which may contain orthometric heights. For additional information, including a discussion on how CORS positions and velocities are derived, see: https://geodesy.noaa.gov/CORS/coords.shtml.
A "broadcast/navigation" orbit file (one for GPS and one for GLONASS) is automatically included with every request. The satellite orbit positions in this file have an accuracy of 2-5 meters. If your post-processing software supports the use of the International GNSS Service (IGS) orbits (sp3c format) you may select those as an optional additional data set. The IGS orbits have an accuracy of between one and several centimeters and should result in more accurate coordinates being computed by your post-processing software. The IGS provides three orbit products for GPS data in increasing order of accuracy and latency: ultra-rapid within ~6 hrs., rapid ~17 hrs. and final ~15 days. For GLONASS it only provides the final orbits ~ 15 days. UFCORS will include the most accurate orbits available at the time of the request. If your data request spans two UTC days then a single orbit file spanning both days is included.
Current and historical equipment information about a site is available in a site's station log. This is automatically included with a data request. The RINEX header information may be incorrect and the site log should always be viewed as containing the most accurate information with regards to the equipment at the site. The coordinate in the log file and RINEX header is not accurate and the coordinate file or datasheet should be consulted. You can also go to the site specific page on our website to see photographs of the site. Go to our main CORS website, then type in the 4-character id or use the map to find the site.
There are three possible causes for not getting data or not getting all the data requested:
You can write a script to do batch downloads of CORS data from our anonymous ftp servers. Please read our README file to obtain information on directory structure, file types, and retention rules ftp://geodesy.noaa.gov/cors/README.txt.
With UFCORS 4.x we began providing the full GPS constellation signals L1+L2+L2C+L5 along with GLONASS. If you requested just GPS you will receive L1+L2+L2C+L5 older GPS processing software does not recognize these new signals. We added on 2014-Aprxx a new option called "GPS (L1+L2 Only)". This option allows a user to only obtain L1 and L2 data like the old UFCORS 3.x provided. This should resolve most issues for legacy users.
NGS does not use/support the Trimble Pathfinder software> directly, therefore we recommend that you contact Trimble support for assistance. You might also try and download the data you want directly from NGS to see if UFCORS is working.
As mentioned in FAQ 9 users can write their own scripts to submit request data via URL command see examples at the bottom of the page.
The options are as follows:
timezone = UTC
starttime = [hh:mm] start hour in hours and minutes e.g. 04:00
duration = [h/hh] number of hours after start hour maximum value is 24hrs e.g. 6 or 12
year = [yyyy] 4-digit start year e.g. 2006
yearday = [jjj] 3-digit start day-of-year e.g. Jan 15 = 015
epic(epochInterval) = [As Is, 1, 5, 15, 30] seconds data) e.g. As Is or 1
siteselection = [ssss] i.e. 4 characters siteID e.g. ab33
coordinatefile = [no/yes]
datasheets = [no/yes]
observables = = [gps/gnss/gpsl1l2] if blank or omitted GPS only data (L1+L2+L2C+L5) will be provided. Currently if gnss is specified only GPS+GLONASS data will be provided (not all sites track both GPS+constellations)
For Version 4.0:
Version 4.0 Parameters: (backward compatible with version 3.x)
GNSS data request (GPS+GLONASS):
GPS data request (GPS L1+L2+L2C+L5) default:
GPS restricted data request (L1+L2):