Difference between revisions of "EODMS APIs"

From wiki
Jump to: navigation, search
Line 8: Line 8:
  
 
To form a get query it would take the form of:
 
To form a get query it would take the form of:
 
+
<pre>
 
https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/products/Radarsat1/search?q={searchterms}
 
https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/products/Radarsat1/search?q={searchterms}
 +
</pre>
  
Eg:
+
e.g.:
 
+
<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/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/products/Radarsat1/search?q=beginposition:[2007-08-20T00:49:50Z%20TO%202007-08-22T10:50:50Z]
 +
</pre>
  
 
The valid search terms right now are:
 
The valid search terms right now are:
 
+
<pre>
 
producttype which can be SCN,SGF, or SLC for Radarsat-1
 
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..
 
sensoroperationalmode which refers to the beam mnemonic like EH3, F1, W2, SCWB, SCNA etc..
 
 
polarisationmode which is only HH for R1
 
polarisationmode which is only HH for R1
 
 
ingestiondate
 
ingestiondate
 
beginposition
 
beginposition
 
endposition
 
endposition
 
footprint  (point and polygon)
 
footprint  (point and polygon)
 +
</pre>
  
 
The search terms can be used together with AND and OR.
 
The search terms can be used together with AND and OR.
  
So as stated before it's heavily modeled after the ESA Data hubs so the following should apply:
+
Heavily modeled after the ESA Data hubs so the following should apply:  
 
 
 
https://colhub.copernicus.eu/userguide/OpenSearchAPI
 
https://colhub.copernicus.eu/userguide/OpenSearchAPI
  
Line 45: Line 43:
  
 
Pour former une requête get, cela prendrait la forme suivante:
 
Pour former une requête get, cela prendrait la forme suivante:
 
+
<pre>
 
https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/products/Radarsat1/search?q={searchterms}
 
https://data.eodms-sgdot.nrcan-rncan.gc.ca/api/products/Radarsat1/search?q={searchterms}
 +
</pre>
  
 
Par exemple:
 
Par exemple:
 
+
<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/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/products/Radarsat1/search?q=beginposition:[2007-08-20T00:49:50Z%20TO%202007-08-22T10:50 : 50Z]
 +
</pre>
  
 
Les termes de recherche valides actuellement sont:
 
Les termes de recherche valides actuellement sont:
 
+
<pre>
 
producttype pouvant être SCN, SGF ou SLC pour Radarsat-1
 
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.
 
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
 
polarisationmode  qui n'est que HH pour R1
 
 
ingestiondate
 
ingestiondate
 
beginposition
 
beginposition
 
endposition
 
endposition
 
footprint  (point et polygon)
 
footprint  (point et polygon)
 +
</pre>
  
 
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.
+
Ainsi, comme indiqué précédemment, il est fortement calqué sur les concentrateurs de données ESA: https://colhub.copernicus.eu/userguide/OpenSearchAPI
 
 
https://colhub.copernicus.eu/userguide/OpenSearchAPI
 
 
 
 
</multilang>
 
</multilang>

Revision as of 15:53, 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/products/Radarsat1/search?q={searchterms}

e.g.:

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/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