Difference between revisions of "Deleteme"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
To form a get query it would take the form of: | To form a get query it would take the form of: | ||
<pre> | <pre> | ||
| − | https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/products/Radarsat1/search?q={searchterms} | + | https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/dhus/v1/products/Radarsat1/search?q={searchterms} |
</pre> | </pre> | ||
e.g.: | e.g.: | ||
<pre> | <pre> | ||
| − | https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/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=footprint:Intersects((-130.496,54.672)) |
| − | https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/products/Radarsat1/search?q=beginposition:[2007-08-20T00:49:50Z%20TO%202007-08-22T10:50:50Z] | + | 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> | </pre> | ||
| Line 44: | Line 44: | ||
Pour former une requête get, cela prendrait la forme suivante: | Pour former une requête get, cela prendrait la forme suivante: | ||
<pre> | <pre> | ||
| − | https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/products/Radarsat1/search?q={searchterms} | + | https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/dhus/v1/products/Radarsat1/search?q={searchterms} |
</pre> | </pre> | ||
Par exemple: | Par exemple: | ||
<pre> | <pre> | ||
| − | https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/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=footprint:Intersects((-130.496,54.672)) |
| − | https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/products/Radarsat1/search?q=beginposition:[2007-08-20T00:49:50Z%20TO%202007-08-22T10:50 : 50Z] | + | 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> | </pre> | ||
| Line 66: | Line 66: | ||
Les termes de recherche peuvent être utilisés avec AND et OR. | Les termes de recherche peuvent être utilisés avec AND et OR. | ||
| − | Ainsi, comme indiqué précédemment, il est fortement calqué sur les concentrateurs de données ESA: https://colhub.copernicus.eu/userguide/OpenSearchAPI | + | Ainsi, comme indiqué précédemment, il est fortement calqué sur les concentrateurs de données ESA: |
| + | https://colhub.copernicus.eu/userguide/OpenSearchAPI | ||
</multilang> | </multilang> | ||
Revision as of 15:59, 30 September 2019
Overview[edit | edit source]
As part of the 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[edit | edit source]
To form a get query it would take the form of:
https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/dhus/v1/products/Radarsat1/search?q={searchterms}
e.g.:
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]
The valid search terms right now are:
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)
The search terms can be used together with AND and OR.
Heavily modeled after the ESA Data hubs so the following should apply:
https://colhub.copernicus.eu/userguide/OpenSearchAPI
