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
triggered from #682: we allow GeometryCollection as GeoJSON type, but that's actually an anti-pattern (e.g. see Open-EO/openeo-processes#389)
openeo-python-client/openeo/rest/datacube.py
Lines 630 to 632 in d5180c3
Lines 1197 to 1199 in d5180c3
Lines 1474 to 1477 in d5180c3
Line 2058 in d5180c3
We should get rid of that. I'm not sure if we should first deprecate it with warnings, or just drop support without deprecation phase
The text was updated successfully, but these errors were encountered:
No branches or pull requests
triggered from #682: we allow GeometryCollection as GeoJSON type, but that's actually an anti-pattern (e.g. see Open-EO/openeo-processes#389)
openeo-python-client/openeo/rest/datacube.py
Lines 630 to 632 in d5180c3
openeo-python-client/openeo/rest/datacube.py
Lines 1197 to 1199 in d5180c3
openeo-python-client/openeo/rest/datacube.py
Lines 1474 to 1477 in d5180c3
openeo-python-client/openeo/rest/datacube.py
Line 2058 in d5180c3
We should get rid of that. I'm not sure if we should first deprecate it with warnings, or just drop support without deprecation phase
The text was updated successfully, but these errors were encountered: