We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Reported here https://discuss.eodc.eu/t/batch-job-vito-error/214/2 and I'm sure it has been reported before but I can't seem to find the ticket.
the openEO spec of filter_bbox states that the crs can be given as an integer EPSG code, but VITO backend does not accept that:
cube = ( con.load_collection("CGLS_LAI300_V1_GLOBAL") .filter_bbox({ "west": 16.13, "east": 16.52, "north": 48.32, "south": 48.13, "crs": 4326 }) .filter_temporal([ "2020-09-01", "2020-09-15"]) ) cube.download() -> OpenEoApiError: [500] unknown: An error occurred while calling o40914.setGlobalExtent. Trace: py4j.Py4JException: Method setGlobalExtent([class java.lang.Double, class java.lang.Double, class java.lang.Double, class java.lang.Double, class java.lang.Integer]) does not exist
The text was updated successfully, but these errors were encountered:
add support for integer EPSG code as crs
8608d5b
See Open-EO/openeo-geopyspark-driver#125
Open-EO/openeo-python-driver@8608d5b
Sorry, something went wrong.
JeroenVerstraelen
No branches or pull requests
Reported here https://discuss.eodc.eu/t/batch-job-vito-error/214/2 and I'm sure it has been reported before but I can't seem to find the ticket.
the openEO spec of filter_bbox states that the crs can be given as an integer EPSG code, but VITO backend does not accept that:
The text was updated successfully, but these errors were encountered: