CDAAC
  Home Page     Data Center     Research Tools     Post Process Results     Climate Processing     NRT Processing  

Data Access Log In

  Data Access     Data Download Interface     File Formats     Documentation  


Name Template: PUB/MISSION/level1b/conPhs/YYYY.DDD/conPhs_IIII.YYYY.DDD.HH.MM.GGG_SSSS.VVVV_nc

DDDDay of year
GGGGNSS id (G28 = GPS satellite 28)
HHHour
IIIIMission ID (CHAM, SACC, CO01-06, GPSM, etc)
LLLLEO number (1-6 for COSMIC)
MISSIONMission ID (eight characters or less--champ, champrt, sacc, sacctst, etc)
MMMinute
PUBBase directory for the pub hierarchy
SSSSSubtype (an ID which tells the command options used in generating this file)
VVVVVersion (an ID which tells the version of all codes using in generating thie file)
YYYYYear

Connected atmospheric excess phase file. Pre-connected excess phase in NetCDF format. For more information on NetCDF, see . https://www.unidata.ucar.edu/software/netcdf/.

If the field 'orbtime' is present, then this conPhs file used low rate (1 second) orbits instead of 50- or 100-Hz orbits to save space. Instructions for reconstructing the high rate orbits are contained in the 'orbtime' and 'txmitLR' attributes.

Global Data

startTime

  • Description:Time in GPS seconds (seconds since 0Z Jan 6, 1980 with no leap seconds) of first data point. To convert to UTC, first convert to UNIX seconds: GPSsec + 315964800 - leapsec where leapsec is the number of leap seconds between GPS and UTC time (a variable in this file) and then use standard UNIX routines to convert UNIX seconds to UTC
  • Data Type: double
  • Units: GPS seconds

stopTime

  • Description:Ending time for the occultation
  • Data Type: double
  • Units: GPS seconds

fidName

  • Description:IGS four character name of the double difference fiducial site used, if any
  • Data Type: char(4)

fileStamp

  • Description:The complete ID for this occultation (IIII.YYYY.DDD.HH.MM.GGG).
  • Data Type: char

refsatId

  • Description:The PRN number of the reference GPS satellite
  • Data Type: int(4)
  • Valid Range: 1, 36

setting

  • Description:Flag: 1 = A setting occultation, 0 = A rising occultation
  • Data Type: int(4)
  • Valid Range: 0, 1

leapsec

  • Description:The number of integer seconds between GPS time and UTC time. See the startTime variable for more info
  • Data Type: double(8)

gast1

  • Description:Greenwich Apparent Sidereal Angle (rad) used to convert the first (gast1) or last (gast2) ECI position to ECEF using the correct rotation about the Z axis. Does not consider polar motion, precession or nutation, but these are small effects. To convert ECI to ECEF, do this: ECEF = [[sin(gast) cos(gast) 0],[-sin(gast) cos(gast) 0],[0 0 1]] * ECI (3x1 column vector)
  • Data Type: double(8)

gast2

  • Description:See gast1
  • Data Type: double(8)

Profile Data

time

  • Description:Time since start of occultation
  • Data Type: float
  • Units: s
  • Valid Range: 0, 240
  • Missing Value: -999

occheight

  • Description:Approximate occultation perigee point height (good to about 10 meters)
  • Data Type: float
  • Units: km
  • Valid Range: -400, 400
  • Missing Value: -999

caL1Snr

  • Description:Signal to Noise Ratio on the L1 channel, CA code
  • Data Type: float
  • Units: 1/10 volts/volt
  • Valid Range: 0, 65535
  • Missing Value: -999

pL1Snr

  • Description:Signal to Noise Ratio on the L1 channel, P code
  • Data Type: float
  • Units: 1/10 volts/volt
  • Valid Range: 0, 65535
  • Missing Value: -999

pL2Snr

  • Description:Signal to Noise Ratio on the L2 channel, P code
  • Data Type: float
  • Units: 1/10 volts/volt
  • Valid Range: 0, 65535
  • Missing Value: -999

xLeo

  • Description:LEO X position (ECI)
  • Data Type: double
  • Units: km
  • Valid Range: -7378, 7378
  • Missing Value: -999

yLeo

  • Description:LEO Y position (ECI)
  • Data Type: double
  • Units: km
  • Valid Range: -7378, 7378
  • Missing Value: -999

zLeo

  • Description:LEO Z position (ECI)
  • Data Type: double
  • Units: km
  • Valid Range: -7378, 7378
  • Missing Value: -999

xdLeo

  • Description:LEO X velocity (ECI)
  • Data Type: double
  • Units: km/s
  • Valid Range: -8, 8
  • Missing Value: -999

ydLeo

  • Description:LEO Y velocity (ECI)
  • Data Type: double
  • Units: km/s
  • Valid Range: -8, 8
  • Missing Value: -999

zdLeo

  • Description:LEO Z velocity (ECI)
  • Data Type: double
  • Units: km/s
  • Valid Range: -8, 8
  • Missing Value: -999

xGps

  • Description:GPS X position (ECI)
  • Data Type: double
  • Units: km
  • Valid Range: -26564, 26564
  • Missing Value: -999

yGps

  • Description:GPS Y position (ECI)
  • Data Type: double
  • Units: km
  • Valid Range: -26564, 26564
  • Missing Value: -999

zGps

  • Description:GPS Z position (ECI)
  • Data Type: double
  • Units: km
  • Valid Range: -26564, 26564
  • Missing Value: -999

xdGps

  • Description:GPS X velocity (ECI)
  • Data Type: double
  • Units: km/s
  • Valid Range: -5, 5
  • Missing Value: -999

ydGps

  • Description:GPS Y velocity (ECI)
  • Data Type: double
  • Units: km/s
  • Valid Range: -5, 5
  • Missing Value: -999

zdGps

  • Description:GPS Z velocity (ECI)
  • Data Type: double
  • Units: km/s
  • Valid Range: -5, 5
  • Missing Value: -999

exL1

  • Description:Excess Phase on L1 channel
  • Data Type: double
  • Units: m
  • Valid Range: -5000, 5000
  • Missing Value: -999

exL2

  • Description:Excess Phase on L2 channel
  • Data Type: double
  • Units: m
  • Valid Range: -5000, 5000
  • Missing Value: -999

exLC

  • Description:Excess Phase (ionosphere corrected)
  • Data Type: double
  • Units: m
  • Valid Range: -5000, 5000
  • Missing Value: -999

xmdldd

  • Description:Open Loop Phase Model minus Computed Phase Model
  • Data Type: double
  • Units: m
  • Valid Range: -5000, 5000
  • Missing Value: -999

xrng

  • Description:Open Loop Range Model minus LEO and GPS clocks
  • Data Type: double
  • Units: m
  • Valid Range: -5000, 5000
  • Missing Value: -999
Optional low-rate orbit vectors

orbtime

  • Description:Low rate time used for orbit products. Allows interpolation of orbit positions to high rate time. For LEO orbits, a simple high order polynomial interpolation can be used. GNSS orbits are stored at signal transmission time, so the procedure described for txmitLR must be used
  • Data Type: double
  • Units: GPS seconds

txmitLR

  • Description:Low rate time of GNSS signal transmission. Used for reconstructing high rate GNSS orbits: First txmitHR = linear_interp(timeLR, txmitLR, time+tstart), then GNSS_hr_x = poly_interp(xGnssLR, txmitLR, txmitHR). Do the last step also for Y and Z components.
  • Data Type: double
  • Units: GPS seconds

xLeoLR

  • Description:Low rate LEO X position (ECI)
  • Data Type: double
  • Units: km
  • Valid Range: -7378, 7378
  • Missing Value: -999

yLeoLR

  • Description:Low rate LEO Y position (ECI)
  • Data Type: double
  • Units: km
  • Valid Range: -7378, 7378
  • Missing Value: -999

zLeoLR

  • Description:Low rate LEO Z position (ECI)
  • Data Type: double
  • Units: km
  • Valid Range: -7378, 7378
  • Missing Value: -999

xGnssLR

  • Description:Low rate GNSS X position (ECI)
  • Data Type: double
  • Units: km
  • Valid Range: -26564, 26564
  • Missing Value: -999

yGnssLR

  • Description:Low rate GNSS Y position (ECI)
  • Data Type: double
  • Units: km
  • Valid Range: -26564, 26564
  • Missing Value: -999

zGnssLR

  • Description:Low rate GNSS Z position (ECI)
  • Data Type: double
  • Units: km
  • Valid Range: -26564, 26564
  • Missing Value: -999






|   Comments: maggie[at]ucar[dot]edu  |

|  Last Modified: 2024  |

|   UCAR Privacy Policy  |

|   Terms of Use   |

|  © Copyright  |