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

extent in STAC result metadata should be lat lon #321

Closed
jdries opened this issue Jan 25, 2023 · 0 comments · Fixed by #360
Closed

extent in STAC result metadata should be lat lon #321

jdries opened this issue Jan 25, 2023 · 0 comments · Fixed by #360
Assignees

Comments

@jdries
Copy link
Contributor

jdries commented Jan 25, 2023

For a job (j-f4a4a6605c7c4b8d8ec8e79a2dbd408e) that specifies the bounding box in EPSG:3035, I get the metadata below in job results. I believe stac extents are always in EPSG:4326. The extent in asset crs can go in proj:bbox (but the filter_bbox crs is not necessarily asset crs...)

"extent": {
    "spatial": {
      "bbox": [
        [
          2780000.0,
          1820000.0,
          2800000.0,
          1840000.0
        ]
      ]
    },

This line of code seems to ignore crs entirely:

bbox = [spatial_extent[b] for b in ["west", "south", "east", "north"]]

That would need to be changed...

JohanKJSchreurs added a commit that referenced this issue Mar 7, 2023
JohanKJSchreurs added a commit that referenced this issue Mar 20, 2023
@jdries jdries added this to the sap05-usability milestone Apr 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants