Open-EO / Open-EO/openeo-python-driver

Timezone and millisecond support in `date_shift`

Open
#75 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

API enhancement minor
Dominant language
Python
Stars
12
Forks
8
Avg merge
6d 3h
Merged PRs (30d)
4

Description

In 721f7bae64f I added basic implementation of date_shift process (also see Open-EO/openeo-processes#248)

Still to do:

Both are not supported at the moment by the Rfc3339 helper class from openeo-python-client.
Because we don't expect time zone support or millisecond support to be high priority for end users, we leave this as open todo for now.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the date_shift implementation from commit 721f7bae64f and the Rfc3339 helper in openeo-python-client. Run or inspect the referenced cases in tests/test_views_execute.py around lines 1561 and 1565, and compare them with the linked date_shift proposal examples. Done means timezone and millisecond inputs are supported and those cases pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend-api-design
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.