Follow this link to skip to the main content
NASA Jet Propulsion Laboratory California Institute of Technology
JPL - Home Page JPL - Earth JPL - Solar System JPL - Stars and Galaxies JPL - Science and Technology
Bring the Universe to You: JPL Email News JPL RSS Feed JPL Podcast JPL Video
MISR - Multi-angle Imaging SpectroRadiometer
  Get Data  
 Home
 Mission
 Get Data
Access Data
MISR Data System
Product Maturity Levels
Local Mode Data
 Gallery
 News and Events
 Publications
 FAQs
 Ask a Question
 About Us
 Other Resources
 Internal
Local Mode Data


Contents:

  1. Introduction to Local Mode
  2. The Local Mode site database
  3. Monthly Local Mode data acquisitions
  4. Adding new sites
  5. Date versus path and orbit (tables)

Introduction to Local Mode

If all nine MISR cameras were to transmit their data at full resolution, the data rate of the MISR instrument would be prohibitively high. For this reason, the typical MISR instrument operating mode commands 24 of its 36 channels into an averaging mode. This default mode is called Global Mode (GM). In this configuration all nadir (An) camera data are kept at the higher resolution, and all of the Red channels (Band 3) for the off-nadir cameras are kept at higher resolution (275 meters). The other channels are downsampled by one-quarter, to 1.1 kilometers. This downsampling is done by contiguous averaging of 4 crosstrack by 4 downtrack line samples, and is done electronically within the instrument before data transmission.

However, MISR can also be configured to disable this on-board data averaging and provide high resolution images in all 36 channels for selected targets and observation times. This capability is referred to as Local Mode (LM). The result is a scene with a crosstrack pixel spacing of 275 meters, with downtrack sampling also at 275 meters, over a spatial area of approximately 300 kilometers downtrack by 360 kilometers crosstrack. Local Mode may be desired because the high-resolution data:

  • Can facilitate comparisons with local, point observations acquired by field teams and aircraft;
  • Allow better understanding of the anisotropy of a surface due to spatial variability (e.g. local topography, land cover type); and,
  • Allow an independent validation of MISR's Global Mode data products.

MISR Local Mode data are available as geolocated calibrated radiances.

The MISR team maintains a list of targets for Local Mode data acquisitions. New targets may also be added to this database, but must occur well in advance of the data acquisitions. Targets are scheduled on a monthly basis based upon requests from the user community. However, one or two corrupt lines of data frequently occur in a Local Mode scene because of the high data rate, and no two Local Mode sites may be scheduled for a given orbit unless they are separated by 3000 kilometers in the downtrack direction. Before ordering Local Mode data, users should remember that all of the Red channels (Band 3), and all nadir imagery, are always acquired at the highest spatial resolution in the default Global Mode data product.

The Local Mode site database

The MISR Science Team and other users of MISR data have developed a database of Local Mode sites. This is available in PDF format, organized by site name or by site id. The MISR Local Mode Production Report is also available for determining processing status and history.

Special LM requests

Some MISR Local Mode sites are not collected routinely. These include sites used for image-based instrument calibration studies, those associated with intensive field campaigns, and those where only seasonal acquisitions are to be acquired. These requests are tabluated in the PDF files given below (files for future months become available approximately 2 weeks before the upcoming month).

Month Year 2000 2001 2002 2003 2004 2005 2006
Jan   0101 0201 0301 0401 0501 0601
Feb 0002 0102 0202 0302 0402 0502 0602
Mar 0003 0103 0203 0303 0403 0503 0603
Apr 0004 0104 0204 0304 0404 0504 0604
May 0005 0105 0205 0305 0405 0505 0605
Jun 0006 0106 0206 0306 0406 0506 0606
Jul 0007 0107 0207 0307 0407 0507 0607
Aug 0008 0108 0208 0308 0408 0508 0608
Sep 0009 0109 0209 0309 0409 0509 0609
Oct 0010 0110 0210 0310 0410 0510 0610
Nov 0011 0111 0211 0311 0411 0511 0611
Dec 0012 0112 0212 0312 0412 0512 0612

Adding new sites

In order to schedule a Local Mode acquisition, a site must be on the currently released version of the Local Mode list. However, since the specific sites required by an investigator may change with time, it is possible to request additions or changes to the list. The requester of Local Mode data should be aware of the following schedule guidelines:

Two (2) months or more prior to a field campaign: Compile a list of field sites and dates where Local Mode data are to be requested. Submit these to the MISR Local Mode Science Coordinator (Ms. Barbara Gaitley) using the Ask MISR email form. Information should include, if known or appropriate, the following parameters. Database field sizes are indicated. Items marked with an asterisk (*) are required.

* Site name Name of Local Mode site. Must be 12 characters or less, with no spaces.
Region name A name or descriptor of the region, state, or country where the site resides. This should be roughly 20 characters or less (spaces allowed).
* Latitude (degrees) Format ±xx.xxxx. This refers to the center of the Local Mode site.
* Longitude (degrees) Format ±xx.xxx. This refers to the center of the Local Mode site.
* Elevation (meters) Surface elevation in meters, format xxxx.
Surface descriptor This should be a short descriptor of the site, or purpose of the study (i.e., marine aerosol, cloud, desert, vicarious calibration). This field should be roughly 20 characters or less.
Type CAL: calibration target; CAM: field campaign scheduled; NET: network acquiring continuous validation information; SCI: targets that have been requested on a one time basis, driven by needs of a specific scientific investigator; OFF: no targets have yet been acquired at this location.
Extent (kilometers) The extent refers to the allowable crosstrack distance away from the spacecraft ground track. A Local Mode scene covers a minimum area of 360 kilometers crosstrack, and this parameter will be assigned a value of 180, unless otherwise specified.
Observation frequency This is used for sites where continuous LM data are requested, such as for Network and Desert calibration sites. This value is typically set to 2 observations per month. Values of 1-4, however, are reasonable.
Campaign name Field campaign name.
Campaign date range This information is appropriate for field campaigns, or for LM data acquisition requests that are seasonal, or at specific times of the year.
Network name Name of ground-based instrument network (e.g. AERONET) or organization.
Requester name Name of Experiment Principal Investigator requesting this Local Mode site.
Contact information This should include phone number and e-mail address, at a minimum.

The Science Coordinator will determine if a site already exists within the Local Mode database. If the target is more than 50 kilometers away from an existing site, then a new site may be added. A mid-latitude target usually has three paths (that is, three opportunities) for viewing; targets at higher latitudes will have more than three opportunities. In rare instances, the decision to not add a site of a given location would reduce the number of available visits to two, in the mid-latitude example. This can be determined in advance, and the Coordinator will request justification from the requester before a final decision is made, should this be the case.

Six (6) weeks prior to the field campaign: The requester should review his experiment plan and sites for which Local Mode data are desired and verify that hte site exists on the MISR Local Mode list, as published on this web page, that the campaign dates are accurate, and that the site latitude and longitude are correct. He should notify the Coordinator of any necessary changes.

One (1) week prior to the month in which the campaign is conducted: Local Mode scheduling begins. All changes should be submitted prior to this deadline. If need be, the instrument command table may be re-written up to 24 hours before data acquisition, provided the target is in the Local Mode database. If this is not the case, last minute additions can be accommodated only by considering the campaign site a "target of opportunity". Manual scheduling would need approval from the MISR PI, and EOS Operations Center (EOC) manager. Notify the Science Coordinator should this be necessary.

Date versus path and orbit tables

These tables provide a listing of the path and orbit for a given date, beginning with launch and ending in 2008.

 MISR 1999 2000 2001 2002 2003 2004 2005 2006 2007
January   01 01 01 01 01 01 01 01
February   02 02 02 02 02 02 02 02
March   03 03 03 03 03 03 03 03
April   04 04 04 04 04 04 04 04
May   05 05 05 05 05 05 05 05
June   06 06 06 06 06 06 06 06
July   07 07 07 07 07 07 07 07
August   08 08 08 08 08 08 08 08
September   09 09 09 09 09 09 09 09
October   10 10 10 10 10 10 10 10
November   11 11 11 11 11 11 11 11
December 12 12 12 12 12 12 12 12 12