Difference between revisions of "Deleteme"

From wiki
Jump to navigation Jump to search
m (William.mackinnon moved page EODMS Open Search API (BETA) to EODMS Open Search API: Remove beta)
m (William.mackinnon moved page EODMS APIs to Deleteme)
 
(63 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<multilang>@en|
 
  
== Overview ==
 
 
As part of the [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=28108 Directive on Open Government], the Government of Canada is committed improving its #OpenData posture. This OpenSearch API is the latest effort to align the [[Earth Observation Data Management System (EODMS)]] with giants like ESA and their Sentinel access program to improve RADARSAT-1 access
 
 
== Examples ==
 
 
To form a get query it would take the form of:
 
<pre>
 
https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/dhus/v1/products/Radarsat1/search?q={searchterms}
 
</pre>
 
 
e.g.:
 
<pre>
 
https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/dhus/v1/products/Radarsat1/search?q=footprint:Intersects((-130.496,54.672))
 
https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/dhus/v1/products/Radarsat1/search?q=beginposition:[2007-08-20T00:49:50Z%20TO%202007-08-22T10:50:50Z]
 
</pre>
 
 
The valid search terms right now are:
 
<pre>
 
producttype which can be SCN,SGF, or SLC for Radarsat-1
 
sensoroperationalmode which refers to the beam mnemonic like EH3, F1, W2, SCWB, SCNA etc..
 
polarisationmode which is only HH for R1
 
ingestiondate
 
beginposition
 
endposition
 
footprint  (point and polygon)
 
</pre>
 
 
The search terms can be used together with AND and OR. There is also support for wildcards, free text searching and other operators:
 
 
<pre>
 
Wildcard Description
 
 
* any sequence of zero or more characters
 
? any one character
 
</pre>
 
 
<pre>
 
Operator Description
 
 
AND         Narrow search and retrieve records containing all of the words it separates.
 
OR Broaden search and retrieve records containing any of the words it separates.
 
NOT Narrow 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.
 
</pre>
 
 
Heavily modeled after the ESA Data hubs so the following should apply:
 
https://colhub.copernicus.eu/userguide/OpenSearchAPI
 
 
@fr|
 
 
== Vue d'ensemble ==
 
 
Le gouvernement du Canada s'est engagé à améliorer sa posture #OpenData, et cette nouvelle API est le dernier effort visant à s'aligner sur des géants tels que l'ESA et leur programme d'accès Sentinel afin d'améliorer l'accès à RADARSAT-1.
 
 
== Exemples ==
 
 
Pour former une requête get, cela prendrait la forme suivante:
 
<pre>
 
https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/dhus/v1/products/Radarsat1/search?q={searchterms}
 
</pre>
 
 
Par exemple:
 
<pre>
 
https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/dhus/v1/products/Radarsat1/search?q=footprint:Intersects((-130.496,54.672))
 
https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/dhus/v1/products/Radarsat1/search?q=beginposition:[2007-08-20T00:49:50Z%20TO%202007-08-22T10:50 : 50Z]
 
</pre>
 
 
Les termes de recherche valides actuellement sont:
 
<pre>
 
producttype pouvant être SCN, SGF ou SLC pour Radarsat-1
 
sensoroperationalmode qui fait référence à la mnémonique du faisceau comme EH3, F1, W2, SCWB, SCNA, etc.
 
polarisationmode  qui n'est que HH pour R1
 
ingestiondate
 
beginposition
 
endposition
 
footprint  (point et polygon)
 
</pre>
 
 
Les termes de recherche peuvent être utilisés avec AND et OR. Il existe également un support pour les caractères génériques, la recherche de texte libre et d'autres opérateurs:
 
 
<pre>
 
Wildcard Description
 
 
* any sequence of zero or more characters
 
? any one character
 
</pre>
 
 
<pre>
 
Operator Description
 
 
AND         Narrow search and retrieve records containing all of the words it separates.
 
OR Broaden search and retrieve records containing any of the words it separates.
 
NOT Narrow 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.
 
</pre>
 
 
Ainsi, comme indiqué précédemment, il est fortement calqué sur les concentrateurs de données ESA:
 
https://colhub.copernicus.eu/userguide/OpenSearchAPI
 
</multilang>
 

Latest revision as of 19:05, 6 January 2022