knitr::opts_chunk$set( collapse = TRUE, comment = "#>" )
The TheiaR package intends to provide a clean interface to download and manage data issued by Theia through its API (Application Programming Interface).
The basic functionalities are (for now):
.meta4file) obtained from Theia website.
NOTE: ongoing development, more functionalities shall be added in the future
First, load the package.
To search and download data from Theia, you will need to register to their website.
NOTE: In order to use Landsat or SpotWorldHeritage products, you'll need to make a first manual download to agree to the license and validate your account.
The first step is to create a collection of tile(s). This can be done either from a query or from a cart file.
A query is simply a named
list of search terms. For example:
myquery <- list(collection = "SENTINEL2", town = "Grenoble", start.date = "2018-07-01", end.date = "2018-07-06")
will create a query to Theia database, looking for tiles from Sentinel2 satellite around Grenoble, between 2018-07-01 and 2018-07-06.
It accepts the following terms.
collection: The collection to look for. Accepted values are:
Snow. Defaults to
platform: The platform to look for. Accepted values are:
level: Processing level of products. Accepted values are:
LEVEL3A. Defaults to
To specify the location of the tiles, several alternatives are available. You can specify the town around which you want your data with:
You can specify directly the tile ID if you know it:
You can specify a point by giving its x/y coordinates:
latitude: The x coordinate of a point.
longitude: The y coordinate of a point.
Or you can specify a rectangle by giving its min/max coordinates:
latmin: The minimum latitude to search.
latmax: The maximum latitude to search.
lonmin: The minimum longitude to search.
lonmax: The maximum longitude to search.
You can also look for a specific orbit number or relative orbit number:
orbit.number: The orbit number
rel.orbit.number: The relative orbit number
Finally, you can filter results by giving the date range and the maximum cloud cover:
max.clouds: The maximum of cloud cover wanted (0-100).
start.date: The first date to look for (format:
end.date: The last date to look for (format:
You can then create your collection with:
mycollection <- TheiaCollection$new(query = myquery, dir.path = ".", check = TRUE)
dir.path is the path you want your tiles to be downloaded. If tiles are
already present in
dir.path, they will be checked by computing a checksum and
comparing it to the hash provided by Theia (only available for Sentinel2 data,
no hash is provided for other collections, and files are then assumed to be
correct). This ensures that the files have been correctly downloaded.
check = FALSE to skip file's check.
Alternatively, you can download a cart from Theia. To create a cart, login to
Theia website, make a search
for tiles, and add wanted tiles to your cart. Then, download your cart and save
.meta4 file to your disk.
You can then create your collection using this file:
cart.path <- system.file("extdata", "cart.meta4", package = "theiaR") mycollection <- TheiaCollection$new(cart.path = cart.path, dir.path = ".", check = TRUE) print(mycollection)
As above, it will check the hash of files if they are already present in
The next step is to download your collection. You can get the status of your collection by running:
To download all tiles in a collection, simply run:
mycollection$download(auth = myauth)
where myauth is the path to file storing your Theia credentials. If it does not exist yet, you will be securely prompted for your login and password, and the file will be created.
This will check if files are present, check their hashes, and download them if needed (if files do not exist or checksums are wrong). To overwrite existing files, run:
mycollection$download(auth = myauth, overwrite = TRUE)
If you want to extract the archives, you can run:
file.path <- mycollection$extract()
which will extract tiles into the same directory as the archives.
Alternatively, you can read bands directly from the zip archives (by using the
vsizip interface provided by GDAL). Use:
to get a list of available bands. Then:
mybands <- mytile$read(bands = c("B5", "B6"))
to load the bands into memory (returns a
RasterStack object). It performs the
necessary corrections on the values.
You can also read bands from a collection by running:
mybands <- mycollection$read(bands = c("B5", "B6"))
which returns a
NOTE: loading several tiles needs a lot of memory (~900MB/tile)
Thanks to Olivier Hagolle for his work on
(github), which has inspired
Any scripts or data that you put into this service are public.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.