Open-EO / openeo-geotrellis-extensions

Java/Scala extensions for Geotrellis, for use with OpenEO GeoPySpark backend.
Apache License 2.0
5 stars 4 forks source link

no results for bbox near date line #279

Open bossie opened 7 months ago

bossie commented 7 months ago

This process graph will return an empty GeoTiff for sync requests and no assets for batch jobs:

{
  "process_graph": {
    "loadcollection1": {
      "process_id": "load_collection",
      "arguments": {
        "bands": [
          "B02",
          "B03",
          "B04",
          "B08"
        ],
        "id": "SENTINEL2_L2A",
        "spatial_extent": {
          "west": 178.7384,
          "east": 178.8548,
          "south": 70.769,
          "north": 70.8254
        },
        "temporal_extent": [
          "2024-04-02",
          "2024-04-03"
        ]
      }
    },
    "saveresult1": {
      "process_id": "save_result",
      "arguments": {
        "data": {
          "from_node": "loadcollection1"
        },
        "format": "GTiff",
        "options": {}
      },
      "result": true
    }
  }
}

Internal ref: CDSE-96

bossie commented 7 months ago

FWIW, forcing the CRS to EPSG:32601 makes it work.

JeroenVerstraelen commented 7 months ago

Has to be fixed in the next sprint. This was originally an issue from CDSE Zendesk.

EmileSonneveld commented 7 months ago

The PG gives a result on https://openeo-dev.vito.be But indeed no result on https://openeo-staging.creo.vito.be (no errors, no files)

EmileSonneveld commented 7 months ago

This might be due the gaps in S2 data and not the date line. When enlarging the extent I got some data crossing the line. image

https://github.com/Open-EO/openeo-geotrellis-extensions/issues/280

EmileSonneveld commented 6 months ago

Sentinel 5 also had missing data close to the date line. Found by student via Victor Verhaert

jdries commented 2 months ago

I logged a downstream issue that could also help here: https://github.com/locationtech/proj4j/issues/113

EmileSonneveld commented 2 months ago

TODO: Change code so that in unexpected cases, the old behaviour is used