Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"geometry" of STAC Item for GeoTiff job result is not in EPSG:4326 #854

Closed
bossie opened this issue Sep 3, 2024 · 2 comments · Fixed by Open-EO/openeo-python-driver#309 or #858
Closed
Assignees
Labels

Comments

@bossie
Copy link
Collaborator

bossie commented Sep 3, 2024

An oversight perhaps? In this case it prevents the STAC Item from being load_stac'ed:

OpenEO batch job failed: java.lang.IllegalArgumentException: Geometry or Bounding box provided by the catalog has to be in EPSG:4326, but got Extent(581900.0, 9559080.0, 592140.0, 9569320.0) for catalog entry Feature(openEO.tif,Extent(39.737687843764, -3.988745051782351, 39.83000704287855, -3.896026580585802),2019-01-01T00:00Z,[Lorg.openeo.opensearch.OpenSearchResponses$Link;@318d04c6,Some(10.0),None,Some(POLYGON ((581900 9559080, 581900 9569320, 592140 9569320, 592140 9559080, 581900 9559080))),Some(EPSG:32737),GeneralProperties(None,None,None,None,None),Some(Extent(581900.0, 9559080.0, 592140.0, 9569320.0)),None)

Original job with GTiff output: j-240902a1f7054c21950f4e96a0d8d7a8
load_stac job that failed: j-240903da85a64bcbb1f061c1270b1509

"geometry" should be in EPSG:4326 but is in native CRS instead:

{
  "coordinates": [
    [
      [
        581900,
        9559080
      ],
      [
        581900,
        9569320
      ],
      [
        592140,
        9569320
      ],
      [
        592140,
        9559080
      ],
      [
        581900,
        9559080
      ]
    ]
  ],
  "type": "Polygon"
}

"bbox" is fine however:

[
  39.737687843764,
  -3.988745051782351,
  39.83000704287855,
  -3.896026580585802
]
@bossie bossie added the bug label Sep 3, 2024
@Open-EO Open-EO deleted a comment Sep 3, 2024
bossie added a commit that referenced this issue Sep 4, 2024
bossie added a commit that referenced this issue Sep 4, 2024
bossie added a commit to Open-EO/openeo-python-driver that referenced this issue Sep 4, 2024
bossie added a commit to Open-EO/openeo-python-driver that referenced this issue Sep 4, 2024
bossie added a commit to Open-EO/openeo-python-driver that referenced this issue Sep 4, 2024
bossie added a commit to Open-EO/openeo-python-driver that referenced this issue Sep 4, 2024
bossie added a commit that referenced this issue Sep 4, 2024
bossie added a commit that referenced this issue Sep 4, 2024
bossie added a commit to Open-EO/openeo-python-driver that referenced this issue Sep 4, 2024
@bossie
Copy link
Collaborator Author

bossie commented Sep 4, 2024

Requires a merge of the PR in this repo.

@bossie bossie reopened this Sep 4, 2024
bossie added a commit that referenced this issue Sep 4, 2024
* reproduce problem with trimmed process graph

#854

* fix this case

#854

* fix other cases

#854

* reference pyhon-driver with fix; update version/CHANGELOG

#854

* add proper test

#854

* align "geometry" values with those of "bbox"

#854

* remove process graph used for debugging

#854
@bossie
Copy link
Collaborator Author

bossie commented Sep 5, 2024

Available on staging.

Original job with GTiff output has a valid "geometry": j-2409054165ac4b089a2734bde280f956.
That made it load_stac'able: j-2409054b31de40b3a9d662779362426b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment