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

Constraints on spatiotemporal extents in wizards #309

Open
jdries opened this issue Aug 28, 2023 · 0 comments
Open

Constraints on spatiotemporal extents in wizards #309

jdries opened this issue Aug 28, 2023 · 0 comments

Comments

@jdries
Copy link

jdries commented Aug 28, 2023

The wizards in the web editor currently nudge users towards creating fairly large spatiotemporal extents, which is a common source of failing jobs.
Our general constraint in openEO platform is that we test up to 100x100km at 10m resolution, but this is not super easy to check client side for arbitrary collections.

So here's two suggestions:

  • run /validate by default at the end of the wizard, to show potential warnings/errors generated by the backend
  • make default extents more on the safe side, for instance by zooming in a lot more on the map, and settings last month as temporal extent?
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

No branches or pull requests

1 participant