Get Data
DOWNLOADING DATA VIA HTTPS
To learn more about Earthdata Login and register for an account, please see How to Register with Earthdata Login. Once you have logged in, data can be downloaded via a Web browser, command line, or client. For help with downloading data, please see Options Available for Bulk Downloading Data from HTTPS with Earthdata Login.
NOTE: Reverb will be decommissioned in the coming months and replaced with Earthdata Search. All links to Reverb will be removed at that time.
IceBridge Ku-Band Radar L1B Geolocated Radar Echo Strength Profiles, Version 2
This data set contains elevation and surface measurements over Greenland, the Arctic, and Antarctica, as well as flight path charts and echogram images acquired using the Center for Remote Sensing of Ice Sheets (CReSIS) Ku-Band Radar Altimeter.
Version 2 data are in netCDF format beginning with the 2012 Antarctica campaign.
Version 1 data are in MATLAB and binary format for Spring 2012 and earlier campaigns.
- Beginning with the 2012 Antarctica campaign, the data file format is netCDF.
- Data files for all previous campaigns are to be replaced with netCDF files.
Geographic Coverage
Spatial Coverage: |
|
---|---|
Spatial Resolution: |
|
Temporal Coverage: |
|
Temporal Resolution: | Varies |
Parameter(s): |
|
Platform(s) | DC-8, P-3B |
Sensor(s): | Ku-Band Radar |
Data Format(s): |
|
Version: | V2 |
Data Contributor(s): | Prasad Gogineni, Carl Leuschen, Fernando Rodriguez-Morales, John Paden, Chris Allen |
Metadata XML: | View Metadata Record |
Data Citation
As a condition of using these data, you must cite the use of this data set using the following citation. For more information, see our Use and Copyright Web page.
Leuschen, C., P. Gogineni, F. Rodriguez-Morales, J. Paden, and C. Allen. 2014, updated 2016. IceBridge Ku-Band Radar L1B Geolocated Radar Echo Strength Profiles, Version 2. [Indicate subset used]. Boulder, Colorado USA. NASA National Snow and Ice Data Center Distributed Active Archive Center. doi: http://dx.doi.org/10.5067/D7DX7J7J5JN9. [Date Accessed].Detailed Data Description
Operation IceBridge products may include test flight data that are not useful for research and scientific analysis. Test flights usually occur at the beginning of campaigns. Users should read flight reports for the flights that collected any of the data they intend to use. Check IceBridge campaign Flight Reports for dates and information about test flights.
The data files are in netCDF format. The echogram and flight path image files are JPEG files.
Each data file is paired with an associated XML file. XML files contain file level metadata and location, platform, and campaign information.
Echogram.jpg files contain depth echograms. The echograms are useful for tracking internal layers and shallow ice thicknesses.
Map.jpg files show campaign flight locations and flight lines.
The y-axis in the JPEG files show depth relative to a range around the surface. The surface is in the center of the y-axis and the y-axis is set to a fixed range, usually from 0 meters to 60 or 80 meters for the land ice, and 0 meters to 4 meters for sea ice.
Currently IceBridge Ku-Band Radar L1B Geolocated Radar Echo Strength Profiles (IRKUB1B) data for 2009 through the 2012 Greenland campaign are in binary format stored separately as IRKUB1B Version 1. Beginning with the 2012 Antarctica campaign, all data are provided in netCDF format. In the near future, data from all campaigns prior to 2012 Antarctica will be replaced with netCDF data and added to Version 2.
For details on the IRKUB1B Version 1 data, see the Version 1 documentation.
Deconvolution Files and Supplement Files
Deconvolution files and supplement files are included in the data files for 19 March 2015 for data files captured over sea ice.
Deconvolution Files
Fast-time deconvolution filtering has been applied which affects the data file "amplitude" field. The deconvolution filter for each range line is constructed from nearby sea ice lead responses. The purpose of the deconvolution filter is to reduce sidelobes.
Supplement Files
Supplement files contain metadata information for the data segment (SS = segment and FFF =frame in the segment. There is one supplement file per data granule, containing a quality mask for each data frame. Supplement files contain the following seven classification masks:
- coh_noise_removal_artifact: Coherent noise removal artifacts in radar echogram. uint8 type, set to 0 for no substantial coherent noise removal artifacts and 1 if artifacts exist.
- deconvolution_artifact: Deconvolution artifacts (e.g. sidelobes) in radar echogram. uint8 type, set to 0 for no substantial deconvolution artifacts and 1 if artifacts exist.
- vertical_stripes_artifact: Vertical stripes or raised noise floor artifacts in radar echogram. uint8 type, set to 0 for no substantial vertical striping artifacts and 1 if artifacts exist.
- missing_data: Radar echogram is missing data because radar range gate clips echogram, truncating the radar return. uint8 type, set to 0 for no missing data and 1 if there is missing data.
- low_SNR: Low signal to noise ratio. uint8 type, set to 0 for sufficient SNR and 1 if the SNR is low.
- unclassified_artifact: Unclassified artifacts exist in radar echogram. uint8 type, set to 0 for no unclassified artifacts and 1 if artifacts exist.
- land_ice: Land ice, ice shelf, or ice berg contained in echogram. uint8 type, set to 0 for sea ice and 1 for land ice.
NOTE: uint8 = Unsigned (no negative sign) Integers only 8 bits of information – min value 0, max value 255.
Data Files
Data files are named according to the following convention and as described in Table 1.
Example:IRKUB1B_20121012_02_034.nc
IRKUB1B_YYYYMMDD_xx_xxx.NNN
Where:
Variable | Description |
---|---|
IRKUB1B |
Short name for IceBridge Ku-Band Radar L1B Geolocated Radar Echo Strength Profiles |
YYYY |
Four-digit year of survey |
MM |
Two-digit month of survey |
DD |
Two-digit day of survey |
xx |
Segment number |
xxx |
Frame number |
NNN |
Indicates file type. For example: netCDF (.nc), or XML (.xml) |
JPEG Files
JPEG files are named according to the following convention and as described in Table 2:
Example:IRKUB1B_20121012_02_034_Echogram.jpg
IRKUB1B_YYYYMMDD_xx_xxx_aaa.jpg
Where:
Variable | Description |
---|---|
IRKUB1B |
Short name for IceBridge Ku-Band Radar L1B Geolocated Radar Echo Strength Profiles |
YYYY |
Four-digit year of survey |
MM |
Two-digit month of survey |
DD |
Two-digit day of survey |
xx |
Segment number |
xxx |
Frame number |
aaa |
Image type. Examples: Echogram, or Map |
jpg |
Indicates JPEG file type. |
NetCDF files range from approximately 400 KB to 5.2 MB.
XML files range from approximately 4 KB to 6 KB.
JPEG files range from approximately 775 Bytes to 380 KB.
The entire data set is approximately 1.2 TB.
Spatial coverage for the IceBridge ku-band radar campaigns includes the Arctic, Greenland, Antarctica, and surrounding ocean areas. This represents the two coverages noted below.
Arctic / Greenland:
Southernmost Latitude: 60° N
Northernmost Latitude: 90° N
Westernmost Longitude: 180° W
Easternmost Longitude: 180° E
Antarctic:
Southernmost Latitude: 90° S
Northernmost Latitude: 53° S
Westernmost Longitude: 180° W
Easternmost Longitude: 180° E
Spatial Resolution
Spatial Resolution varies dependent on along-track, cross-track, and aircraft height characteristics. See the Derivation Techniques and Algorithms section for further detail on resolution and bandwidth.
Projection and Grid Description
Referenced to WGS-84 Ellipsoid.
These data were collected seasonally from 12 October 2012 to 15 May 2015 as part of Operation IceBridge funded campaigns.
Temporal Resolution
IceBridge campaigns are conducted on an annual repeating basis. Arctic and Greenland campaigns are conducted during March, April, and May, and Antarctic campaigns are conducted during October and November.
The Ku-Band Radar Level-1B Geolocated Radar Echo Strength Profiles data set contains elevation and surface measurements.
Parameter Description
The Ku-band Radar netCDF files contain fields as described in Table 3.
Parameter | Description | Units |
---|---|---|
altitude | WGS-84 geodetic elevation coordinate of the measurement's phase center. Dimension is time. | Meters |
amplitude | Power detected radar echogram data matrix. The first dimension is fasttime and time is the second dimension. Power is relative to the current range line only. Each range line may contain a different bias and so power comparisons between range lines may not be possible. | Relative power (log scale) |
Elevation_Correction | Represents the number of zeros that were inserted during elevation compensation for each range line to simulate near-level flight. These zeros are not included in the truncation noise statistics. Only available when amplitude is truncated. Dimension is time. | Range bins |
fasttime | Fast time. Zero time is the time at which the transmit waveform begins to radiate from the transmit antenna. | Microseconds |
heading | Platform heading attitude (zero is north, positive to east). Dimension is time. | Degrees |
lat | WGS-84 geodetic latitude coordinate of the measurement phase center. Always referenced to North. Dimension is time. | Degrees |
lon | WGS-84 geodetic longitude coordinate of the measurement phase center. Always referenced to East. Dimension is time. | Degrees |
pitch | Platform pitch attitude (zero is level flight, positive is up). Dimension is time. | Degrees |
roll | Platform roll attitude (zero is level flight, positive is right wing tip down). Dimension is time. | Degrees |
Surface | Estimated two way propagation time to the surface from the collection platform. This uses the same frame of reference as the fasttime variable. This information is sometimes used during truncation to determine the range bins that can be truncated. Dimension is time. | Seconds |
time | UTC time of day. This is also known as the slow time dimension. The parameter units attribute contains a string of the form: seconds since YYYY-MM-DD 00:00:00, which indicates the day related to this time parameter. This pertains to data sets that wrap over a UTC day boundary which will cause this parameter to be outside the range [0,86400]. | Seconds |
Truncate_Bins | Indices into the original (before truncation) fasttime vector for which the amplitude values are available. Only available when amplitude is truncated. Dimension is time. | n/a |
Truncate_Mean | Represents a mean of the noise power for the truncated range bins before the surface return. When no range bins were truncated before the surface return the value is NaN. Only available when amplitude is truncated. Dimension is time. | n/a |
Truncate_Median | Represents a median of the noise power for the truncated range bins before the surface return. When no range bins were truncated before the surface return the value is NaN. Only available when amplitude is truncated. Dimension is time. | n/a |
Truncate_Std_Dev | Represents a standard deviation of the noise power for the truncated range bins before the surface return. When no range bins were truncated before the surface return the value is NaN. Only available when amplitude is truncated. Dimension is time. | n/a |
Software and Tools
See the NetCDF Resources at NSIDC page for tools to work with netCDF files.
CReSIS netCDF files are compatible with HDF5 libraries, and can be read by HDF readers such as HDFView. If the netCDF file reader you are using does not read the data, seehttp://www.unidata.ucar.edu/software/netcdf/ and http://nsidc.org/data/netcdf/tools.html for information on updating the reader.
CReSIS MATLAB readers are available for loading, plotting, and elevation compensation for CReSIS Level-1B radar products. These tools are provided by the Principal Investigator as-is as a service to the user community in the hope that they will be useful. Please note that support for these tools is limited. Bug reports, comments, and suggestions for improvement are welcome; please send to nsidc@nsidc.org.
JPEG files may be opened using any image viewing program that recognizes the JPEG file format.
XML files can be read with browsers such as Firefox and Internet Explorer.
Data Acquisition and Processing
The Ku-band radar uses a Frequency Modulated Continuous Wave (FMCW) architecture (Carrara 1995). This is done to reduce the required sampling frequency of the Analog to Digital Converter (ADC) and is possible when the range gate is limited. Currently, the range gate is limited to low altitude flights to achieve the full bandwidth. In the FMCW radars, a long chirp signal of approximately 250 μs is generated which sweeps linearly in frequency from the start frequency to the stop frequency. This signal is transmitted and also fed to a mixer in the receiver to be used to demodulate the received signal. Signals outside the range gate are suppressed by the Intermediate Frequency (IF) filter and aliased by the system.
The dominant scattered signal is the specular or coherent reflection from the air-snow surface and shallow layers beneath this surface. A bistatic antenna configuration is used to provide isolation between the transmit and receive paths which is important because the FMCW system receives while transmitting and too little isolation means that the direct path from the transmitter to the receiver will be too strong and saturate the receiver. The antennas are mounted so that the main beam is pointed in the nadir direction to capture the specular surface and layer reflections.
The Pulse Repetition Frequency (PRF), or along-track sampling rate, does not necessarily capture the full Doppler bandwidth for point scatterers without aliasing. However, as the target energy is mostly coherent, it occupies only a small portion of the Doppler spectrum so the undersampling in along-track is not generally a problem. Since the coherent portion of the surface and layer scattering is the primary signal of interest, presumming is used to lower the data rate, which effectively low-pass-filters and decimates the Doppler spectrum.
The narrow beam width of the antennas have a fixed pointing direction, which means that when the aircraft rolls beyond approximately 10 degrees, the specular reflection falls outside the main lobe of the antennas and therefore the signal strength is reduced.
Echograms posted include altitude correction, but the data files do not. Correction can be applied by shifting a record from bottom to top by the altitude correction value. Altitude variations within a data file are removed by subtracting the minimum altitude from all values. The result is variation in meters from the minimum. These values are then converted to whole pixel values given the radar parameters: sampling frequency = 58.32 MHz, pulse length, FFT length, and bandwidth. Note: sampling frequency after the 2009 Greenland campaign is 62.5 MHz.
Flat Surface Range Resolution
For a flat surface the range resolution is expressed by Equation 1:
(Equation 1)
Where:
Variable | Description |
---|---|
kt | kt = 1.5 due to the application of a Hanning time-domain window to reduce the range sidelobes of the chirped transmit waveform. |
c | Speed of light in a vacuum |
B | Bandwidth, nominally 3500 MHz (13 to 16.5 GHz range) |
n | Index of refraction for the medium |
Bandwidth
The bandwidth for a particular segment can be determined by reading the param_radar structure in the echogram data file or by looking at the parameter values f0, f1, and fmult and doing the calculation in Equation 2:
(Equation 2)
Where:
Variable | Description |
---|---|
B | Bandwidth |
param_radar.f1 | Stop frequency of chirp out of Direct Digital Synthesis (DDS) and into Phase-Locked Loop (PLL) |
param_radar.f0 | Start frequency of chirp out of DDS and into PLL |
param_radar.fmult | PLL frequency multiplication factor |
The range resolutions for several indices of refraction are shown in Table 6.
Index of Refraction | Range Resolution (cm) | Medium |
---|---|---|
1 | 6.4 | Air |
sqrt(1.53) | 5.2 | Snow |
sqrt(3.15) | 3.6 | Solid Ice |
Index of Refraction
The index of refraction can be approximated by the calculation in Equation 3:
(Equation 3)
Where:
Variable | Description |
---|---|
ρsnow | Density of the snow in grams per cm3 |
A dielectric of 1.53 is used which corresponds to a snow density of 0.3 g per cm3 (Warren 1999).
Along Track Resolution
In the along-track dimension, the raw data, before any hardware or software coherent averages, have a resolution derived in the same manner as the cross-track resolution. However, a basic form of focusing is applied called unfocussed SAR processing, also known as stacking or coherent averaging. If all effects are accounted for, the data may be coherently averaged to a SAR aperture length using Equation 4.
(Equation 4)
Where:
Variable | Description |
---|---|
H | Height above ground |
λc | Wavelength |
For H = 500 m and a center frequency of 14.75 GHz, the data may be averaged to a length of 2.25 m. The resolution turns out to be approximately equal to this with the exact definition given below. However, these data are only coherently averaged 16 times which includes both hardware and software averaging, and decimated by this same amount. At a platform speed of 140 m/s this is an aperture length, L, of 1.12 m. The sample spacing is likewise 1.12 m. Therefore the actual resolution is less fine, given by Equation 5.
(Equation 5)
Where:
Variable | Description |
---|---|
H | Height above ground |
λc | Wavelength |
L | SAR aperture length |
For H = 500 m, the along-track resolution is 4.54 m.
A 1 range-bin by 5 along-track-range-line boxcar filter is applied to the power detected data and then decimated in the along-track by 5 so the data product has an along-track sample spacing of 5.6 m.
Fresnel Zone and Cross Track Resolution
For a smooth or quasi-specular target, for example internal layers, the primary response is from the first Fresnel zone. Therefore, the directivity of specular targets effectively creates the appearance of a cross-track resolution equal to this first Fresnel zone. The first Fresnel zone is a circle with diameter given by Equation 6.
(Equation 6)
Where:
Variable | Description |
---|---|
H | Height above the air/ice interface |
T | Depth in ice of the target |
λc | Wavelength at the center frequency |
Table 11 gives the cross-track resolution for this case.
Center Frequency (MHz) | Cross-track Resolution H = 500 m T = 0 m |
---|---|
14750 | 4.5 |
For a rough surface with no appreciable layover, the cross-track resolution will be constrained by the pulse-limited footprint, approximated in Equation 7.
(Equation 7)
Where:
Variable | Description |
---|---|
H | Height above the air/ice interface |
T | Depth in ice of the target |
c | Speed of light in a vacuum |
kt | kt = 1.5 due to the application of a hanning time-domain window to reduce the range sidelobes of the chirped transmit waveform |
B | Bandwidth in radians |
Table 13 gives the cross-track resolution with windowing.
Bandwidth (MHz) | Cross-track Resolution H = 500 m T = 0 m |
---|---|
3500 | 16.0 |
For a rough surface where layover occurs, the cross-track resolution is set by the beamwidth, β , of the antenna array. The antenna beamwidth-limited resolution is expressed by Equation 8:
(Equation 8)
Where:
Variable | Description |
---|---|
H | Height above ground level |
T | Depth in ice of the target |
βy | Beamwidth in radians |
Footprint
The antenna installed in the bomb bay of the NASA P-3 aircraft, the wing roots of the DC-8, and the nadir port of the Twin Otter is a Pasternack Enterprises 9854-20 standard gain horn antenna. The E-plane of the antenna is aligned in the along-track. The approximate beamwidths are 19 degrees in along-track and 19 degrees in cross-track. The footprint is a function of range as shown in Equation 9.
(Equation 9)
Where:
Variable | Description |
---|---|
β | Beamwidth in radians |
H | Height above ground level |
For H = 500 m, the footprint is 167 m in along-track and 167 m in cross-track.
Trajectory and Attitude Data
The trajectory data used for this data release was from a basic GPS receiver. Lever arm and attitude compensation has not been applied to the data.
Processing Steps
The following processing steps are performed by the data provider.
- Set digital errors to zero. Error sequences are four samples in length and occur once every few thousand range lines.
- Synchronization of GPS data with the radar data using the UTC time stored in the radar data files.
- Conversion from quantization to voltage at the ADC input.
- Removal of DC-bias by subtracting the mean.
- For 2013 Greenland P3 and later, a tracking and truncation function has been implemented in the hardware which reduces the recorded data volume. Each range line is tracked and truncated separately and a step is added here to undo the tracking and truncation step so that the data can be placed in a matrix with constant time bins. This requires zero padding and time shifting of the data to get each range line to line up.
- The quick look output is generated using presumming or unfocused SAR processing for a total of 16 coherent averages which includes hardware and software averages. If the PRF is 2000 Hz, the new effective PRF is 125 Hz.
- A fast-time FFT is applied with a Hanning window to convert the raw data into the range domain, analogous to pulse compression. The data are flipped around based on the Nyquist zone.
- A high pass filter is applied in the along-track to remove coherent noise.
- A 1 range-bin by 5 along-track-range-line boxcar filter is applied to the power detected data and then decimated by 5 in along-track.
- The quick-look output is used to find the ice surface location, fully automated.
- The output is elevation compensated to the nearest radar range bin and then truncated in fast time to reduce the data volume.
The purpose of the elevation compensation, when applied, is to remove the large platform elevation changes to make truncation more effective. The process is not designed to perform precision elevation compensation and is probably not sufficient for scientific analysis. The following steps are performed:
- Let:
- Elevation_Orig be the 1 by N elevation vector before elevation compensation
- Data_Orig be the M_orig by N data matrix before elevation compensation
- Time_Orig be the M_orig by 1 fast-time time axis before elevation compensation
- Elevation be the 1 by N vector from the data product file
- Dat be the matrix from the data product file
- Time be the M by 1 fast-time time axis from the data product file
- maxElev = max(Elevation_Original)
- dRange = maxElev - Elevation_Original
- dt = Time_Orig(2) - Time_Orig (1)
- Sample spacing in fast-time (i.e. one range bin)
- dBins = round(dRange / (c/2) / dt)
- This is a 1 by N vector of the number of range bins for each range line used to shift Data_Orig. In other words, this is the elevation compensation for each range line written in terms of range bins.
- M = M_orig + max(dBins)
- The original data matrix is zero padded to M and then each range line is shifted by the corresponding entry in dBins.
- Because of the round function for creating dBins, the elevation compensation is only done with range bin accuracy.
- The new Data matrix is similar to what would have been collected if the aircraft had flown at a constant elevation of maxElev.
- The elevation matrix is modified according to the elevation compensation so that: Elevation_Orig = Elevation - dBins*dt*c/2. Once again, because of the round function, the Elevation vector will be nearly constant, but not quite: the quantization noise caused by the round function remains.
- The Time_Orig vector is extended in length by the maximum bin shift to create the new Time vector.
Version History
IRKUB1B Version 2: Beginning with the 2012 Antarctica campaign, data are provided in netCDF format. In the near future, data from all campaigns prior to Fall 2012 will be replaced with netCDF data. For details on the Version 1 data, see the V1 documentation.
Error Sources
GPS Time Error:
The CReSIS accumulation, snow, MCoRDS, and kuband data acquisition systems have a known issue with radar data synchronization with GPS time. When the radar system is initially turned on, the radar system acquires Universal Time Coordinated (UTC) time from the GPS National Marine Electronics Association (NMEA) string. If this is done too soon after the GPS receiver has been turned on, the NMEA string sometimes returns GPS time rather than UTC time. GPS time is 15 seconds ahead of UTC time during this field season. The corrections for the whole day must include the offset -15 second correction. GPS corrections have been applied to all of the data using a comparison between the accumulation, snow, and kuband radars which have independent GPS receivers. A comparison to geographic features and between ocean surface radar return and GPS elevation is also made to ensure GPS synchronization. GPS time corrections are given in the vector worksheet of the parameter spreadsheet.
The error affects Version 2 of the Level 1B CReSIS data sets. Ku-band radar data are affected for the time period: October 2012 - 2013. In the near future, the NSIDC DAAC will publish updated data files with a correction to the 'Time' field.
As described on the CReSIS Sensors Development Radar Web site, the ku-band radar operates over the frequency range from 13 to 17 GHz. The primary purpose of this radar is high precision surface elevation measurements over polar ice sheets. The data collected with this radar can be analyzed in conjunction with laser-altimeter data to determine thickness of snow over sea ice. The radar has been flown on the NASA DC-8 and P-3 aircrafts, and the National Science Foundation-provided Twin Otter aircraft.
References and Related Publications
Contacts and Acknowledgments
Carl Leuschen, Prasad Gogineni, Richard Hale, John Paden, Fernando Rodriguez, Ben Panzer, Daniel Gomez
CReSIS
Nichols Hall
2335 Irving Hill Road
University of Kansas
Lawrence, Kansas 66045
Data and data products from CReSIS were generated with support from NSF grant ANT-0424589 and NASA grant NNX10AT68G.
Document Information
DOCUMENT CREATION DATE
22 October 2014
DOCUMENT REVISION DATE
12 December 2016
Access complete Knowledge Base
Questions? Please contact:NSIDC User Services
Phone: 1 303 492-6199
Email: nsidc@nsidc.org