PublishedAfter, publishedBefore - the date limits when the product was published in our repository StartDate, completionDate - the date limits of the observation. cloudCover applies to optical satellites, but polarisation applies to radar ones), or just single one. Most of the parameters are common for all collections, but some are specific for some them (e.g. The queries are in form param=value or param=. The example of formal query - about cloudless (cloud cover below 10%) products from Warsaw Summer 2016: The query must be specified as a formal query. It is impossible to use an alternative in the question. The result is a conjunction of all sub phrases. The formal query is invoked as a sequence of sub phrases, separated by &. The last sub phrase, selecting the next page of the results, may be also written as page=2 Will return 20 least cloudy products from July 2016, while the next query would return the next 20, a little bit cloudier, such product: SortOrder=ascending or sortOrder=descending StartDate - the date when the observation was made Published - the date when the product got published in our repository (default) Will sort the output by observation date rather than by publication date. You may also change the order of how the products are presented, using the phrase like If the query is very general and the number of matching products is large, the next pages of products may be retrieved You may change the limit (beware of long execution time for queries about thousands of products) using the phrase branch of the repository tree.īy default, maximum 10 most recently published products are returned only. For example, the collection is named Sentinel2, while in the repository its data are located within /eodata/Sentinel-2/. Note, that collection names vary a bit from satellite names, as they are used in EO Data repository. While if the collection field is missing in the URL, the products from all the satellites are returned:Īs for today the following collections are defined and may be used: For example, to find 10 most recent Sentinel-2 products with cloud cover below 10%, the query should look like: If only one satellite is in the field of interest, the second approach is faster and more efficient, than filtering the general query. A query may search for data in all collections, or in one particular collection only. The data are organized in so-called collections, corresponding to various satellites. For example, the following filtered command returns name list of 100 most recent Sentinel-1 products. If you need just such a list, without additional info, provided by JSON, the solution is to filter out the formatted JSON response. The responses as text lists of products are not implemented directly yet. The responses are by default formatted in compact form for machine interpretation. To select the appropriate form, use the corresponding engine in the URL: The queries may produce their results either in JSON or XML formats. Note, that the actual EO data themselves are restricted to to Creodias users, only the catalogue (EO Data Finder) is open. The database is accessible free and anonymously (open for anonymous access for everyone, no authorization is used) It may be accessed both from the internal network (virtual machines in Creodias) and from outside, e.g. curl or wget, or from inside of users’ program. All queries may be executed as simple HTTP-Get calls, by typing the query in web browser address line, by using any HTTP client, e.g.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |