pysepal

Diagnose and fix common pysepal, Solara, and GEE runtime errors.

13|4|Updated Jul 27, 2020
One-click install
npx skills add https://github.com/openforis/pysepal --skill pysepal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pysepal
Source: https://github.com/openforis/pysepal/tree/main/skills/pysepal
Command: npx skills add https://github.com/openforis/pysepal --skill pysepal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building and maintaining pysepal-based Solara dashboards for the SEPAL platform requires deep, scattered knowledge of GEE async patterns, component conventions, and common error fixes, leading to avoidable runtime errors and inconsistent implementations without centralized guidance.

Core Features & Use Cases

  • Component Discovery: Automatically identifies all valid pysepal components and their correct import paths to eliminate usage of deprecated or non-existent components.
  • Error Diagnosis & Fixes: Provides pre-defined solutions for common pysepal/Solara/GEE errors including event loop mismatches, silent empty widgets, and stale GEE interface instances.
  • App Auditing: Scans existing pysepal apps for deprecated patterns (such as old MapApp layouts, incorrect async task configs, and inline notification widgets) to ensure compatibility with current pysepal versions.
  • Use Case: A developer building a new SEPAL dashboard that displays Google Earth Engine land cover data can use this skill to implement correct async workflows, standardized export flows, and proper notification handling to avoid runtime crashes.

Quick Start

Use the pysepal skill to build a new Solara dashboard for SEPAL that displays Google Earth Engine land cover data with correct async patterns and component structure.

Frequently Asked Questions about pysepal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix event loop mismatch errors when building Solara dashboards for SEPAL?

Event loop mismatch errors in Solara dashboards for SEPAL occur when Google Earth Engine async workflows are incorrectly configured. You can resolve them by applying standardized session-backed GEE async patterns and proper component import paths to ensure stable runtime execution.

Why does my Google Earth Engine data load silently as empty widgets in a Solara app?

Silent empty widgets in a Solara app happen when the Google Earth Engine interface instance becomes stale during dashboard rendering. Diagnosing this requires auditing the Solara component structure and refreshing the GEE async workflow to restore data flow.

How do I implement correct async patterns for Google Earth Engine in a SEPAL dashboard?

Implementing correct Google Earth Engine async patterns in a SEPAL dashboard requires using session-backed GEE workflows and proper component discovery. This prevents event loop mismatches and ensures your Solara dashboard handles asynchronous tasks without crashing.

Can I use Solara to build a SEPAL dashboard with Google Earth Engine land cover data?

Yes, you can use Solara to build a SEPAL dashboard displaying Google Earth Engine land cover data. Correct implementation requires following standardized async patterns, proper component discovery, and integrating standardized export flows to avoid runtime errors.

What is the best way to audit existing pysepal apps for deprecated patterns?

Auditing existing pysepal apps for deprecated patterns involves scanning the codebase for old MapApp layouts, incorrect async task configs, and inline notification widgets. Updating these patterns ensures compatibility with current pysepal versions and Solara best practices.

Why are my inline notification widgets causing issues in my SEPAL dashboard?

Inline notification widgets cause issues in SEPAL dashboards because they violate current Solara best practice compliance and component conventions. Migrating to standardized notification system integration prevents these runtime errors and ensures proper component discovery.