Skip to content

Searching#

Each search function returns an ASFSearchResults object:

  • geo_search() Find product info over an area of interest using a WKT string
  • granule_search() Find product info using a list of scene names
  • product_search() Find product info using a list of product IDs
  • stack_from_id() Find a baseline stack of products using a reference scene ID
  • If the above search approaches do not meet your search needs, search() supports all available keywords:
    • search() Find product info using any combination combination of search parameters. See the keywords list below.

Examples of some search workflows can be found in this sample script. You may also reference the Jupyter notebooks for example workflows.

For more advanced usage, see sections ASFSearchResults class and ASFProduct class.

Keywords#

Keywords are used to find the desired data. Use as many or as few keywords as needed. Available keywords and descriptions are listed below. Additionally, numerous constants are provided to ease the search process. Currently, we provide constants for beam mode, flight direction, instrument, platform, polarization, and product type. You can see the full list of constants here.

Dataset Parameters#

  • platform

    • See the list of constants
    • Remote sensing platform that acquired the data. Sentinel-1 and ERS have multiple remote sensing platforms, and you may choose whether to specify a specific platform. You may specify a single value, or a list of values.
    • You may also get the available list of constants by using help(asf_search.constants.PLATFORM)
    • Example:
      • platform=asf.PLATFORM.SENTINEL1A

  • instrument

    • See the list of constants
    • Remote sensing instrument that acquired the data. For some platforms, such as ALOS, there are multiple instruments to choose from.
    • You may also get the available list of constants by using help(asf_search.constants.INSTRUMENT)
    • Example:
      • instrument=asf.INSTRUMENT.AVNIR_2

  • absoluteOrbit

    • For ALOS, ERS-1, ERS-2, JERS-1, RADARSAT-1, Sentinel-1A, and Sentinel-1B this value corresponds to the orbit count within the orbit cycle. For UAVSAR it is the Flight ID. You may specify a single value, range of values, or a list of values.
    • Example:
      • single value: absoluteOrbit=25436
      • range of values: absoluteOrbit=(12005, 12008)
      • list of values: absoluteOrbit=[25436, 25450]

  • asfFrame

    • See also 'frame'
    • This is primarily an ASF / JAXA frame reference. However, some platforms use other conventions. You may specify a single value, range of values, or a list of values.
    • Example:
      • single value: asfFrame=300
      • range of values: asfFrame=(2845, 2855)
      • list of values: asfFrame=[2800, 2845]
    • Values:
      • ERS, JERS, RADARSAT: ASF frames 0 to 900
      • ALOS PALSAR: JAXA frames 0 to 7200
      • SEASAT: ESA-like frames 208 to 3458
      • Sentinel-1: In-house values 0 to 1184

  • beamMode

    • See the list of constants
    • The beam mode used to acquire the data.
    • You may also get the available list of constants by using help(asf_search.constants.BEAMMODE)
    • Example:
      • beamMode=asf.BEAMMODE.POL

  • campaign

    • For UAVSAR, AIRSAR, and Sentinel-1 Interferogram datasets only. Search by the campaign name. You may specify a single value.
    • For a list of available campaigns, use the asf_search.campaigns() function. You must provide the desired platform.
      • asf_search.campaigns(asf_search.PLATFORM.UAVSAR)
    • Example:
      • campaign='Purace Volcano, Colombia'

  • maxDoppler

    • Doppler provides an indication of how much the look direction deviates from the ideal perpendicular flight direction acquisition.
    • Example:
      • maxDoppler=1500 or maxDoppler=1500.5

  • minDoppler

    • Doppler provides an indication of how much the look direction deviates from the ideal perpendicular flight direction acquisition.
    • Example:
      • minDoppler=100 or minDoppler=1500.5

  • maxFaradayRotation

    • Rotation of the polarization plane of the radar signal impacts imagery. HH and HV signals become mixed. One-way rotations exceeding 5° are likely to significantly reduce the accuracy of geophysical parameter recovery, such as forest biomass.
    • Example:
      • maxFaradayRotation=3.5

  • minFaradayRotation

    • Rotation of the polarization plane of the radar signal impacts imagery. HH and HV signals become mixed. One-way rotations exceeding 5° are likely to significantly reduce the accuracy of geophysical parameter recovery, such as forest biomass.
    • Example:
      • minFaradayRotation=2

  • flightDirection

    • See the list of constants
    • Satellite orbit direction during data acquisition. You may specify a single value.
    • You may also get the available list of constants by using help(asf_search.constants.FLIGHT_DIRECTION)
    • Example:
      • flightDirection=asf.FLIGHT_DIRECTION.ASCENDING

  • flightLine

    • Specify a flightline for UAVSAR or AIRSAR. You may specify a single value.
    • Example:
      • UAVSAR: flightLine='05901'
      • AIRSAR: flightLine='gilmorecreek045-1.93044'

  • frame

    • See also 'asfFrame'
    • ESA-referenced frames are offered to give users a universal framing convention. Each ESA frame has a corresponding ASF frame assigned. You may specify a single value, range of values, or a list of values.
    • Example:
      • single value: frame=300
      • range of values: frame=(305, 315)
      • list of values: frame=[300, 303, 305]
    • Values:
      • Any number from 0 to 7200.

  • groupID

    • List of specific group IDs. For some datasets, the group ID is the same as the scene name. For others, such as Sentinel-1, the group ID is unique for a group of scenes.
    • Example:
      • groupID='S1A_IWDV_0112_0118_037147_150'

  • lookDirection

    • Left or right direction of data acquisition. You may specify a single value.
    • Example:
      • lookDirection='L'
    • Values:
      • R, RIGHT, L, LEFT

  • offNadirAngle

    • Off-nadir angles for ALOS PALSAR. You may specify a single value, range of values, or a list of values.
    • Example:
      • single value: offNadirAngle=21.5
      • range of values: offNadirAngle=(9.7, 14)
      • list of values: offNadirAngle=[21.5, 23.1]
    • Values:
      • Most common: 21.5, 23.1, 27.1, 34.3
      • Other: 9.7, 9.9, 13.8, 14, 16.2, 17.3, 17.9, 18, 19.2, 20.5, 21.5, 23.1, 24.2, 24.6, 25.2, 25.8, 25.9, 26.2, 27.1, 28.8, 30.8, 34.3, 36.9, 38.8, 41.5, 43.4, 45.2, 46.6, 47.8, 49, 50, 50.8

  • polarization

    • See the list of constants
    • A property of SAR electromagnetic waves that can be used to extract meaningful information about surface properties of the earth. You may specify a single value, or a list of values.
    • You may also get the available list of constants by using help(asf_search.constants.POLARIZATION)
    • Example:
      • polarization=asf.POLARIZATION.VV

  • processingLevel

    • See the list of constants
    • Level to which the data has been processed, also type of product.
    • You may also get the available list of constants by using help(asf_search.constants.PRODUCT_TYPE)
    • Example:
      • processingLevel=asf.PRODUCT_TYPE.SLC

  • relativeOrbit

    • Path or track of satellite during data acquisition. For UAVSAR it is the Line ID. You may specify a single value, range of values, or a list of values.
    • Example:
      • single value: relativeOrbit=5905
      • range of values: relativeOrbit=(2400, 2410)
      • list of values: relativeOrbit=[500, 580]
    • Values:
      • ALOS: 1-671
      • ERS-1: 0-2410
      • ERS-2: 0-500
      • JERS-1: 0-658
      • RADARSAT-1: 0-342
      • SEASAT: 1-243
      • UAVSAR: various

Geospatial Parameters#

  • intersectsWith
    • Search by polygon, a line segment (“linestring”), or a point defined in 2-D Well-Known Text (WKT). Each polygon must be explicitly closed, i.e. the first vertex and the last vertex of each listed polygon must be identical. Coordinate pairs for each vertex are in decimal degrees: longitude is followed by latitude.
    • Example:
      • intersectsWith='POLYGON((-152.81 58.49,-154.90 57.49,-155.08 56.30,-153.82 56.34,-151.99 57.30,-151.43 58.19,-152.81 58.49))'
      • intersectsWith='LINESTRING(-119.543 37.925, -118.443 37.7421)'
      • intersectsWith='POINT(-119.543 37.925)'

Shape Validation#

If the AOI specified is its own Minimum Bounding Rectangle (MBR) in a mercator projection, the search results returned will instersect with the AOI in a mercator projection, regardless of width. This remains the case even if the international dateline is crossed within the AOI.

In order for an AOI to be considered its own MBR, it must meet the following criteria:

  • Each vertex shares a latitude or longitude with its neighbors
  • East/West points share longitude
  • North/South points share latitude

AOIs that do not fit this criteria will have their points connected along great circles.

In addition, all AOIs are validated, and then simplified as needed. The process for this is:

  1. Validate the input AOI. If it is not valid, an error is displayed.
  2. Merge overlapping shapes.
  3. Convex hull.
  4. Any out-of-range index values are handled by clamping and wrapping them to the valid range of values.
  5. Simplify points based on proximity threshold. The target is fewer than 400 points.

Each of these steps is performed only when necessary to get the AOI to a single outline with fewer than 400 points. Any unnecessary steps are skipped.

Examples of validation and simplification:

  • A self-intersecting polygon is provided:
    • An error is displayed.
  • A single outline is provided, consisting of 1000 points:
    • A simplified version of the same outline is used, consisting of fewer than 400 points.
  • Multiple geometries are provided, all of them overlapping at least in part:
    • A single outline is returned, representing the outline of all the shapes combined.
  • Multiple geometries are provided, at least some of them entirely non-overlapping:
    • A single outline is returned, representing the convex hull of all the shapes together.

Temporal Parameters#

  • processingDate

    • Limit results to records that have been processed at ASF since a given date and/or time.
    • Example:
      • processingDate='2017-01-01T00:00:00UTC'

  • start

    • Date of data acquisition. Can be used in combination with 'end'. You may enter natural language dates, or a date and/or time stamp. All times are in UTC.
    • Example:
      • start='May 30, 2019'
      • start='yesterday'
      • start='2010-10-30T11:59:59Z'
      • start='1 week ago', end='now'

  • end

    • Date of data acquisition. Can be used in combination with 'start'. You may enter natural language dates, or a date and/or time stamp. All times are in UTC.
      • end='May 30, 2018'
      • end='today'
      • end='2021-04-30T11:59:59Z'
      • start='1 week ago', end='now'

  • season

    • Start and end day of year for desired seasonal range. This keyword may be used in conjunction with start/end to specify a seasonal range within an overall date range. Values are based on the Julian calendar. You must specify both a season start and end date.
    • Example:
      • season=[1, 31]
      • season=[45, 67]
      • season=[360, 10]
    • Values:
      • 1 through 365

Baseline Parameters#

  • stack_from_id
    • Input the scene name for which you wish to see baseline results.
    • stack_from_id may not be used in conjuction with other keywords.
    • Example:
      • stack_from_id('S1A_IW_SLC__1SDV_20220215T225119_20220215T225146_041930_04FE2E_9252-SLC')
    • See the Jupyter notebook for usage examples, as well as best practices.

Results Parameters#

  • maxResults
    • Maximum number of data records to return.
    • Example:
      • maxResults=10