Interactive toolsRegularization settings
Regularization settings
What does sits_regularize() make of the images when you change the period or the cell?
sits_regularize() turns the irregular Sentinel-2 images of two tiles into a cube with one image per period, on one grid of cells. Choose the period, the cell size and the tile to see every date of the cube it makes, from a recorded run of the pipeline. Open a date to see which images it was made from, in sits' order, and how each filled the cells.
4 dates · 256 × 200 cells of 40 m
Recorded run · 2.2 MB
sits_regularize(cube, output_dir = dir, res = 40, period = "P16D", roi = roi, crs = "EPSG:32720", multicores = 4, progress = FALSE)Loading the images of the cube, 260 kB: cube-regular-20llp.png (259 kB) · 0%
Choose a date to see how it was made.
Start 3 Jul 2018: the latest first date of the tiles (20LKP). The timeline stops before passing 27 Aug 2018, the earliest last date of the tiles (20LKP). period = "P16D" cuts it into 4 intervals of 16 days, each from its date t up to t + 16 days, that day left out. Left outside: 2 images of 20LLP, of 30 Jun 2018.
About this tool
Data. One sits run per setting, recorded by the pipeline.
Default: the book's call
sits_regularize(
cube,
output_dir = dir,
res = 40,
period = "P16D"
)Read in sits 2.0.0 (78d26eb), R/sits_regularize.R:179
The book regularizes a copy of its images over whole tiles; its call, shortened here, also sets multicores. Each setting here is a recorded run of the same function on the remote images over a region, with the three bands of a natural-colour picture and the cloud band.
Where sits does each step
| Checks of the arguments | R/sits_regularize.R:193-206 |
|---|---|
| The roi, read in crs | R/sits_regularize.R:217 |
| Timeline | R/api_gdalcubes.R:318-361 |
| Images into dates | R/api_gdalcubes.R:21-44 |
| One file per tile, band and date | R/api_gdalcubes.R:757-765 |
| 1 Order | R/api_gdalcubes.R:29-44 |
| 2 On the grid | R/api_gdalcubes.R:71-112 |
| 3 Masked | R/api_gdalcubes.R:124-158 |
| 4 First value | R/api_gdalcubes.R:573 |
| 5 Written | R/api_gdalcubes.R:586-591 |
| Resampling, bilinear | R/api_gdalcubes.R:565-575 |
| Overviews, at a cell coarser than every band | gdalcubes 0.7.4 src/gdalcubes/src/warp.cpp:123-160 and R/zzz.R:18, R/api_gdalcubes.R:599-604 |
| Crop to the region | R/api_gdalcubes.R:699-706 |
Not set here
timeline: with a month period and a mid-month date it can make sits look for a file gdalcubes named otherwiseroi: another region needs runs not recordedcrs: it only says how to read the roigrid_system: it needs runs not recordedtiles: it does not change the timeline; the Tile buttons show each tile of the runmulticores: it changes no valueprogress: it changes no valueoutput_dir: sits resumes from files of the same name there
cube: B02, B03, B04 and CLOUD of 20LKP and 20LLP · roi: x 294,880–310,240, y 8,840,000–8,848,000 (EPSG:32720)
The cube as files: 2 tiles × 3 bands × 4 dates = 24 files (CLOUD is not written), at the book's call.
Its first row of dates loads about 260 kB of pictures. Another setting loads its own row of dates, 28 kB to 3.8 MB, and a date you open loads the pictures of its images, 330 kB to 6.5 MB.