Correct, calibration and thermal noise reduction are applied. This is done first and at the same time. After that the geolocation processing follows, either orthorectified or non-orthorectified, depending on you settings.
Note that as of this writing speckle filtering and terrain flattening are not supported.
I hope this helps
I can respond to some of these. @marko.repse can probably answer to the rest.
-there is no coregistration involved
-there is averaging involved on lower scales. If you use it on natural scale, there is no resampling.
-there is no terrain flattening and there are no mid-term plans to do it
-we use MapZen’s DEM (https://registry.opendata.aws/terrain-tiles/)
I would like to cite that resource in papers written using SentinelHub. I would like to make a version of Figure 1 here: https://www.mdpi.com/2504-3900/18/1/11 and basically be able to say that Sentinelhub does all or some of the processing steps listed there. thanks!
@email@example.com I have downloaded the sentinel-1 GRD data for my AOI using the this .
I see the pixel size of the downloaded image in QGIS is 8.913742424687676191e-05,-6.860746012812835026e-05.
Where as when we download the GRD data separately and perform following steps :