-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
2 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -67,9 +67,7 @@ In this section we give a brief introduction to datacube wrangling. First, termi | |
|
||
We first present a general overview on standards-based datacube access, and then provide some use-case specific examples. If you want to see further examples added, [contact us](mailto:[email protected])! | ||
|
||
### General | ||
|
||
#### Coverages | ||
### Coverages | ||
|
||
Coverages are designed to be self-describing. While always more metadata can be added to some object, the coverage contains the essentials for understanding the pixels. The canonical structure of a coverage consists of | ||
|
||
|
@@ -101,7 +99,7 @@ Note that http requires certain characters to be ["URL-encoded"](https://www.url | |
|
||
See [this tutorial](https://earthserver.eu/wcs/#wcs) for more details on WCS. | ||
|
||
#### Coverage Processing | ||
### Coverage Processing | ||
|
||
WCPS allows processing, aggregation, fusion, and more on datacubes with a high-level, easy-to-use language which does not require any programming skills like python. The following example inspects coverage A and returns a cutout with a range extent expressed in Easting and Northing (assuming this is the native coordinate reference system of the coverage) and a slice at a time point, returned in PNG format: | ||
|
||
|