Full Text SearchFinnish Data Hub System

Search queries on the rolling archive can be performed by entering a text query in the full-text search bar.

Simple search query

The table below shows some simple text queries that can be typed in the full-text search bar:

Text QueryDescription
blank field or *returns all products in the archive
L0returns all Level-0 products
L1returns all Level-1 products
SLCreturns all SLC products
GRDreturns all GRD products
IWreturns all products in IW mode
EWreturns all products in EW mode
SMreturns all products in SM mode
DESCENDINGreturns all products of the descending passes
ASCENDINGreturns all products of the ascending passes
HHreturns all products containing a measurement dataset in HH polarisation
VVreturns all products containing a measurement dataset in VV polarisation
HVreturns all products containing a measurement dataset in HV polarisation
VHreturns all products containing a measurement dataset in VH polarisation
HH HV or HH+HVreturns all products in dual polarisation HH/HV
VV VH or VV+VHreturns all products in dual polarisation VV/VH
Wildcards and Operators

Wildcards and Operators can be used for restricting search queries. Wildcards, in particular, are useful when performing a query on the product filename. Operators for combining different search criteria. Admitted wildcards and operators are shown in the tables below

WildcardDescription
*any sequence of zero or more characters
?any one character


OperatorDescription
ANDNarrow search and retrieve records containing all of the words it separates.
ORBroaden search and retrieve records containing any of the words it separates.
NOTNarrow search and retrieve records that do not contain the term following it.
( )Group words or phrases when combining Boolean phrases and to show the order in which relationships should be considered.

Examples of queries on products filename using wildcards:

ExampleDescription
*_S1_*returns Stripmap products with elevation beam 1
*_1SD?_*returns Level-1 products in dual polarisation
*_?SD?_*returns Level-0 and Level-1 products in dual polarisation
*_0SS?_*returns Level-0 products in single polarisation

Examples of queries with Operators:

ExampleDescription
IW AND L0returns Level-0 products in IW mode
EW OR SMreturns all products in EW mode and all products in SM mode
L1 NOT IWreturns Level-1 products in EW mode and in SM mode
L0 NOT (SLC AND VV)returns all Level-0 GRD products, all Level-0 SLC products in dual polarization and all Level-0 SLC products in single polarization HH
Search Keywords

It is also possible to make full-text queries using search keywords.
The syntax is the following:
<keyword>:<values>
Depending on the keyword, the value(s) can be specified as a single value or range of values.

Search keywords can be combined with each other using Operators.
The following table contains the list of the keywords and their corresponding usage.

Search KeywordSyntax and Examples

platformname:
Search based on the Satellite Platform name regardless of the serial identifier (e.g. A, B, C ...)

platformname:<platform name>
Examples:
platformname:Sentinel-1
platformname:Sentinel-2

beginposition:
A time interval search based on the Sensing Start Time of the products.

endposition:
A time interval search based on the Sensing Stop Time of the products.

ingestiondate:
A time interval search based on the time of publication of the product on the Data Hub.

These three keywords are used with a time range expressed with the following syntax:

<keyword>:[<timestamp> TO <timestamp>]

The <timestamp< value can be expressed in one of the the following formats:

  • (ISO8601) yyyy-MM-ddThh:mm:ss.SSSZ
  • NOW
  • NOW-MINUTE(S)
  • NOW-HOUR(S)
  • NOW-DAY(S)
  • NOW-MONTH(S)

being n = 1,2,...,10,...,100,...

Examples:

beginposition:[2014-01-01T00:00:00.000Z TO NOW]
beginposition:[2014-01-01T00:00:00.000Z TO 2014-02-01T00:00:00.000Z]
beginposition:[NOW-2DAYS TO NOW]

endposition:[2014-01-01T00:00:00.000Z TO NOW]
endposition:[2014-01-01T00:00:00.000Z TO 2014-02-01T00:00:00.000Z]
endposition:[NOW-1HOUR TO NOW]

ingestiondate:[2014-01-01T00:00:00.000Z TO NOW]
ingestiondate:[2014-01-01T00:00:00.000Z TO 2014-02-01T00:00:00.000Z]
ingestiondate:[NOW-30MINUTES TO NOW]

collection:
The name of a predefined collection of products.

collection:<collection name>
(the list of the available collection names will be advertised when available)

Example:
collection:mycollectionname

filename:
Search based on the product filename

filename:<filename>

Possible <filename> values are:

  • The full product file name expressed according to the product naming convention:
    MMM_BB_TTR_LFPP_YYYMMDDTHHMMSS_YYYYMMDDTHHMMSS_OOOOO_DDDDD_CCCC
  • Part of the filename using wildcards.

Examples:

filename:S1A_EW*
filename:S1A_EW_GRDH_1SDH_20141003T003840_20141003T003920_002658_002F54_4DD1
filename:*1SD?_20141003T003840*

footprint:
Geographical search of the products whose footprint intersects or is included in a specific geographic type.

Syntax is the following:

footprint:"intersects(<geographic type>)"

The <geographic type> value can be expressed as a polygon or as a point according to the syntax described below.

POLYGON:
<geographic type>=POLYGON((P1Lon P1Lat, P2Lon P2Lat, , PnLon PnLat, P1Lon P1Lat))

where P1Lon and P1Lat are the Longitude and Latitude coordinates of the first point of the polygon in decimal degrees (DDD) format (e.g. 2.17403, 41.40338) and so on. The coordinates of the last point of the polygon must coincide with the coordinates of the first point of the polygon. The polygon describing the geographical area can have a maximum of 200 points that must be within an area described by 10 degrees of latitude and 10 degrees of longitude.

Example:

The polygon of the example is a bounding box around the Mediterranean Sea:
footprint:"Intersects(POLYGON((-4.53 29.85, 26.75 29.85, 26.75 46.80,-4.53 46.80,-4.53 29.85)))"

POINT:
<geographic type>= Lat, Lon

where the Latitude (Lat) and Longitude (Lon) values are expressed in decimal degrees (DDD) format (e.g. 41.40338, 2.17403 ).

Examples:
footprint:"intersects(Lat, Lon)"

  • Rome city centre - footprint:"intersects(41.9000, 12.5000)"
  • Etna Volcano - footprint:"intersects(37.7550, 14.9950)"
  • Bárðarbunga Volcano - footprint:"intersects(64.6300, -17.5300)"
  • Istanbul city centre - footprint:"intersects(41.0136, 28.9550)"
  • Paris city centre - footprint:"intersects(48.8567, 2.3508)"
  • Mexico City city centre - footprint:"intersects(19.4333, -99.1333)"
  • Cagliari city centre - footprint:"intersects(39.2500, 9.0500)"
  • Villa San Faustino city centre - footprint:"intersects(42.7340, 12.5324)"
  • London city centre: footprint:"intersects(51.5072, 0.1275)"
  • Berlin city centre: footprint:"intersects(52.5167, 13.3833)"

orbitnumber:
Absolute orbit number of the oldest line within the image data (the start of the product).

lastorbitnumber: Absolute orbit number of the most recent line within the image data (the end of the product)

These keywords can be used with a single value or with a range of values.

The syntax is the following:

  • orbitnumber:<orbitnumber>
  • lastorbitnumber:<lastorbitnumber>
  • orbitnumber:[<orbitnumber> TO <orbitnumber>]
  • lastorbitnumber:[<lastorbitnumber> TO <lastorbitnumber>]

Possible values for and go from 000001 to 999999.

Examples:

orbitnumber:000020 (or orbitnumber:20)
lastorbitnumber:000510 (or lastorbitnumber:510)
orbitnumber:[001020 TO 001021] (or orbitnumber:[1020 TO 1021])

orbitdirection:
Direction of the orbit (ascending, descending) for the oldest image data in the product (the start of the product).

Possible values are:
Ascending, Descending

Example:
orbitdirection:Ascending

polarisationmode:
valid polarisations for the S1 SAR instrument

Possible values are:
HH, VV, HV, VH, HH HV, VV VH

Examples:
polarisationmode:HH
polarisationmode:VV VH

producttype:
output product type

Possible values are:

SLC, GRD, OCN, S2MSI1C

relativeorbitnumber:
Relative orbit number of the oldest line within the image data (the start of the product).

lastrelativeorbitnumber:
Relative orbit number of the most recent line within the image data (the end of the product)

These keywords can be used with a single value or with a range of values.

The syntax is the following:

  • relativeorbitnumber:<relativeorbitnumber>
  • lastrelativeorbitnumber:<lastrelativeorbitnumber>
  • relativeorbitnumber:[<relativeorbitnumber> TO <relativeorbitnumber>]
  • lastrelativeorbitnumber:[<lastrelativeorbitnumber> TO <lastrelativeorbitnumber>]

Possible values for <relativeorbitnumber> and <lastrelativeorbitnumber> go from 1 to 175.

Examples:
relativeorbitnumber:5
relativeorbitnumber:10
relativeorbitnumber:[25 TO 100]

sensoroperationalmode:
The SAR instrument imaging modes

Possible values are:
SM, IW, EW

Example:
sensoroperationamode:SM

swathidentifier:
Search all valid swath identifiers for the Sentinel-1 SAR instrument. The S1-S6 swaths apply to SM products, the IW and IW1-3 swaths apply to IW products (IW is used for detected IW products where the 3 swaths are merged into one image), the EW and EW1-5 swaths apply to EW products (EW is used for detected EW products where the 5 swaths are merged into one image).

Possible values are:
S1, S2, S3, S4, S5, S6, IW, IW1, IW2, IW3, EW, EW1, EW2, EW3, EW4, EW5

Example:
swathidentifier:S1

cloudcoverpercentage:
Percentage of cloud coverage of the product for each area covered by a reference band.

Possible values go from 0 TO 100:
Example:
cloudcoverpercentage:95
cloudcoverpercentage:[0 TO 5]


back to top © ESA
;