You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When reading an xarray file compared to the STAC item, the x-coordinates/longitude and y-coordinates/latitude diverge by one. Concretely, when reading the STAC Item, the last coordinate of the list is left out.
I suspect this comes from these two lines. Here, the upper coordinate of the bounding box is treated as an exclusive bound due to endpoint=False, however, in the STAC Item specification the bounds of the bbox attribute, which is used to extract the bounds, are inclusive.
This leads to inconsistencies in the x-/y-coordinates and longitude/latitude when reading from the STAC Item vs. directly reading the xarray file. I would propose setting endpoint=True to mitigate this issue unless I missed some deeper meaning in the upper bound being exclusive.
The text was updated successfully, but these errors were encountered:
When reading an xarray file compared to the STAC item, the x-coordinates/longitude and y-coordinates/latitude diverge by one. Concretely, when reading the STAC Item, the last coordinate of the list is left out.
I suspect this comes from these two lines. Here, the upper coordinate of the bounding box is treated as an exclusive bound due to
endpoint=False
, however, in the STAC Item specification the bounds of thebbox
attribute, which is used to extract the bounds, are inclusive.This leads to inconsistencies in the x-/y-coordinates and longitude/latitude when reading from the STAC Item vs. directly reading the xarray file. I would propose setting
endpoint=True
to mitigate this issue unless I missed some deeper meaning in the upper bound being exclusive.The text was updated successfully, but these errors were encountered: