Open-EO / Open-EO/openeo-python-client

Easy way to invoke 'inspect' in datacube

Open
#795 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request good first issue low hanging fruit usability
Dominant language
Python
Stars
217
Forks
56
Avg merge
1d 22h
Merged PRs (30d)
2

Description

The 'inspect' method allows to log properties of a datacube, which is useful for debugging.
It is however not so easy to invoke it. What I would intuitively expect based on other processes, is a simple cube.inspect().

Note that importing 'inspect' from openeo.processes is an option, but invoking that method returns a ProcessBuilder object, which does not have the convenience functionality to start jobs.

The current workaround I found was to do this:

connection.datacube_from_process("inspect",data=cube)

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 by tracing the datacube API and the existing connection.datacube_from_process("inspect", data=cube) workaround, then compare it with the inspect process imported from openeo.processes. Done means a datacube can invoke inspect through the proposed convenience API while retaining the ability to start jobs.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, data
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
44/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.