-
Notifications
You must be signed in to change notification settings - Fork 4
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
Milestone
Comments
JohanKJSchreurs
added a commit
that referenced
this issue
Mar 2, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Mar 2, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Mar 2, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Mar 3, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Mar 3, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Mar 7, 2023
…ox in extract_result_metadata
JohanKJSchreurs
added a commit
that referenced
this issue
Mar 8, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Mar 10, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Mar 20, 2023
…tial_extent may not be defined
JohanKJSchreurs
added a commit
that referenced
this issue
Mar 20, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Mar 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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...)
This line of code seems to ignore crs entirely:
openeo-geopyspark-driver/openeogeotrellis/deploy/batch_job.py
Line 100 in d7aa375
That would need to be changed...
The text was updated successfully, but these errors were encountered: