-
Notifications
You must be signed in to change notification settings - Fork 42
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
feature request: allow specifying temporal extent with single string #421
Comments
JohanKJSchreurs
added a commit
that referenced
this issue
Aug 9, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Aug 11, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Aug 16, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Aug 16, 2023
PR #461 was merged but I'd like to iterate a bit further on it:
|
JohanKJSchreurs
added a commit
that referenced
this issue
Sep 6, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Sep 6, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Sep 6, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Sep 7, 2023
…stead of tuple in load_collection and filter_temporal
JohanKJSchreurs
added a commit
that referenced
this issue
Sep 7, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Sep 7, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Sep 8, 2023
…ndling available sinche v0.23.0
JohanKJSchreurs
added a commit
that referenced
this issue
Sep 8, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Sep 11, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Sep 11, 2023
soxofaan
added a commit
that referenced
this issue
Sep 15, 2023
soxofaan
added a commit
that referenced
this issue
Sep 18, 2023
soxofaan
added a commit
that referenced
this issue
Sep 18, 2023
…tency The "round up" end_date feature as originally proposed turned out to conflict too much with existing behavior and openEO spec. Still, the idea can still be provided through single string `extent`: "2022" -> ("2022-01-01", "2023-01-01")
soxofaan
added a commit
that referenced
this issue
Sep 18, 2023
soxofaan
added a commit
that referenced
this issue
Sep 18, 2023
soxofaan
pushed a commit
that referenced
this issue
Sep 20, 2023
soxofaan
pushed a commit
that referenced
this issue
Sep 20, 2023
soxofaan
pushed a commit
that referenced
this issue
Sep 20, 2023
soxofaan
pushed a commit
that referenced
this issue
Sep 20, 2023
…stead of tuple in load_collection and filter_temporal
soxofaan
pushed a commit
that referenced
this issue
Sep 20, 2023
soxofaan
pushed a commit
that referenced
this issue
Sep 20, 2023
soxofaan
pushed a commit
that referenced
this issue
Sep 20, 2023
soxofaan
pushed a commit
that referenced
this issue
Sep 20, 2023
soxofaan
added a commit
that referenced
this issue
Sep 20, 2023
soxofaan
added a commit
that referenced
this issue
Sep 20, 2023
soxofaan
added a commit
that referenced
this issue
Sep 20, 2023
…tency The "round up" end_date feature as originally proposed turned out to conflict too much with existing behavior and openEO spec. Still, the idea can still be provided through single string `extent`: "2022" -> ("2022-01-01", "2023-01-01")
soxofaan
added a commit
that referenced
this issue
Sep 20, 2023
soxofaan
added a commit
that referenced
this issue
Sep 20, 2023
done now: merged #468 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Temporal extents have to be specified as a list/tuple with two dates.
Often, when experimenting/exploring, you just need a single year or month, it would be handy if you can just pass
temporal_extent="2022"
ortemporal_extent="2023-04"
, which would be converted automatically by the client to appropriate date rangesThe text was updated successfully, but these errors were encountered: