Replies: 1 comment
-
Hi @charalamm , sorry for the delayed answer. FORCE uses double arithmetic to compute coordinates. What you see may be related to the floating point precision or the way that QGIS handles these data types. Please see here for some explanation about it: https://www.php.net/manual/en/language.types.float.php In any case, I don't see any practical drawbacks of this behaviour since the difference in coordinates is extremely small (if there is any, probably just the way how QGIS prints the numbers). Best, |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I am trying to create a force datacube out of Sentinel2 but the extend of the output products is slightly off to what I am expecting to see.
For example the
X0011_Y0028/20220114_LEVEL2_SEN2A_BOA.tif
of my grid according torasterio
and QGIS has an extend ofBoundingBox(left=540000.0, bottom=6119999.999999999, right=550000.0, top=6129999.999999999)
instead ofBoundingBox(left=540000.0, bottom=6120000.0, right=550000.0, top=6130000.0)
although according togdal
(gdalinfo /mnt/nas/lambis/DataCube-S1/X0011_Y0028/S1_20190528_20190609_D_139.tif | grep 'Upper\|Lower'
) has a correct extend:Does anybody know why is this happening?
I am using the following parameters among others:
Also, on level 2 processing I am getting the following
datacube-definition.prj
file which looks good to me:Thanks!
Beta Was this translation helpful? Give feedback.
All reactions