pysepal.scripts.gee#

Bootstrap for the global ee module.

Two functions, both about the same thing: making ee.Initialize() have happened. init_ee() runs it from the machine’s own credentials, and need_ee() guards code that would otherwise raise EEException: client library not initialized. Building an Earth Engine graph – ee.Image(...), ee.FeatureCollection(...) – is client-side and needs this, whoever initialised it.

Nothing here is session-aware, so nothing that executes belongs here. getInfo, getMapId, exports, and listing, inspecting or deleting assets spend a quota and touch private data. They go through the connection’s own session: get_current_gee_interface() and the GEEInterface methods.

4.0 removed the asset and task helpers this module used to carry. They ran against the global ee, which in an app-launcher container is the platform service account, so they answered for the wrong identity without erroring – and one of them deleted. docs/guides/migration-v4.md names the replacement for each.

init_ee is the gap that remains: it accepts the service-account key the session layer refuses two layers up, which pysepal/solara/_topology.py describes.

Functions

init_ee

Initialize earth engine according using a token.

need_ee

Decorator to execute check if the object require EE binding.