The documents are returned sorted on relevance depending on order, proximity, frequency of terms.
Default search behavior
By default, all search terms are optional. It behaves like an OR logic. Objects that contain the more terms are rated higher in the results and will appear first in their type. For example, wiki forum will find:
- objects that include both terms
- objects that include the term wiki
- objects that include the term forum
Requiring terms
Add a plus sign ( + ) before a term to indicate that the term must appear in results. Example: +wiki forum will find objects containing at least wiki. Objects with both terms and many occurences of the terms will appear first.
Excluding terms
Add a minus sign ( - ) before a term to indicate that the term must not appear in the results. To reduce a term's value without completely excluding it, use a tilde. Example: -wiki forum will find objects that do not contain wiki but contain forum
Grouping terms
Use parenthesis ( ) to group terms into subexpressions. Example: +wiki +(forum blog) will find objects that contain wiki and forum or that contain wiki and blog in any order.
Finding phrases
Use double quotes ( " " ) around a phrase to find terms in the exact order, exactly as typed. Example: "Alex Bell" will not find Bell Alex or Alex G. Bell.
Using wildcards
Add an asterisk ( * ) after a term to find objects that include the root word. For example, run* will find:
- objects that include the term run
- objects that include the term runner
- objects that include the term running
Reducing a term's value
Add a tilde ( ~ ) before a term to reduce its value indicate to the ranking of the results. Objects that contain the term will appear lower than other objects (unlike the minus sign which will completely exclude a term). Example: +wiki ~forum will rate an object with only wiki higher that an object with wiki and forum.
Changing relevance value
Add a less than ( < ) or greater than ( > ) sign before a term to change the term's contribution to the overall relevance value assigned to a object. Example: +wiki +(>forum < blog) will find objects that contain wiki and forum or wiki and blog in any order. wiki forum will be rated higher.
Update of the CS2 SARvatore Service to Version 2.26 (Baseline D Compliant))
Dear Users,
On 04 September 2019, the CS2 SARvatore Service:
https://gpod.eo.esa.int/services/CRYOSAT_SAR/
has been updated to version v2.26 (L1b and L2)
This version is compatible with the CryoSat-2 Baseline D which
has recently entered in operation.
The news in the release v2.26 with respect the previous version are:
- Possibility to dump SAR stack in Power and Phase for both the two channels (option from Graphic Interface)
- Add epoch field and Epoch Reference Gate field in the product
- Addition of the Leap Second in the Product
- Error in the fieldname of Boresight Beam Angle and Doppler Beam Angle fields when RIP is dumped
- Support to CLS15 Mean Sea Surface in the product
- Support to J2 Sea State Bias Model in the product
- Support to NSIDC Sea Ice Concentration in the product
- Support to NSIDC Sea Ice Age in the product
- Support to FES2014b Tide Model in the product
- Support to TPXO9 Tide Model in the product
- Support to DTU18 Mean Sea Surface in the product
- Support to CLS13 Mean Dynamic Topography in the product
- Support to GPCC Precipitation Rate in the product
- Support to distance to land based on GSHHG database
- New fields in the products GEO_Corr_SeaIce and GEO_Corr_Land
- When Waveform is Hamming-weighted, a dedicated LUT is used now
- Addition of First Guess Epoch and Epoch Bounds in the product
- Fix of a bug of distance to land field for latitude around +88
- Support to CryoSat-2 Baseline D FBR/L1b Products
We wish you a good processing time with CS2 SARvatore Service