Earth2studio Create Datasource
NVIDIAOfficialCreated by NVIDIA Earth-2 Team
- Skill
- Workflow
- Software development
- Apache-2.0
- Medium risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured, 14-step procedure for developers to integrate new remote data sources into the Earth2Studio framework. It covers the entire lifecycle from initial analysis of the remote store, through implementation of the appropriate source wrapper (DataSource, ForecastSource, DataFrameSource, or ForecastFrameSource), to testing, documentation, and PR submission. The workflow emphasizes asynchronous data fetching patterns, proper lexicon mapping, and rigorous validation using sanity-check plots to ensure data integrity before final submission.
What it does
- Determines the correct Earth2Studio source wrapper type based on data characteristics.
- Guides the implementation of asynchronous data fetching logic using fsspec.
- Facilitates the creation of lexicon mappings to standardize variable names.
- Automates the generation of skeleton files for source code and unit tests.
- Provides templates for variable validation and sanity-check visualization.
- Assists with PR creation and automated code review triage.
When to use it
- When you need to connect a new remote data store (S3, GCS, Azure, HTTP, HuggingFace) to Earth2Studio.
- When implementing custom data ingestion logic for gridded or sparse climate data.
- When you need to ensure your new data source meets project standards for testing, linting, and documentation.
- When you require a systematic approach to validate variable coverage and data quality.
Advantages
- Ensures consistency across all Earth2Studio data source implementations.
- Promotes high code quality through mandatory linting, formatting, and 90% test coverage.
- Reduces development time by providing standardized skeletons and async utility patterns.
- Prevents common errors by enforcing a clear validation and sanity-check process.
Usage examples
- “Add a new data source for the NOAA GFS analysis stored on S3.”
- The agent will initiate the 14-step workflow, starting by analyzing the S3 bucket, determining the appropriate DataSource type, and guiding you through the implementation, testing, and PR submission process.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/nvidia/earth2studio-create-datasource/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip earth2studio-create-datasource.zip -d .agents/skills
Documentation by NVIDIA Earth-2 Team
Create and Validate Data Source
Purpose
End-to-end workflow for implementing a new Earth2Studio data source wrapper that connects a remote data store (S3, GCS, Azure, HTTP, HuggingFace) to Earth2Studio's async data fetching infrastructure — from analysis through implementation, testing, validation, and PR submission.
Prerequisites
Earth2Studio dev environment with
uv(uv run pythonmust work)Git configured with fork (
origin) and upstream (upstream) remotesAccess to the target remote data store (credentials if private)
Python 3.10+
Workspace
Use the directory containing pyproject.toml. For Harbor evals, write to
/workspace/output/ preserving paths. Never read evals/targets/.
Instructions
Python Environment: Always use
uv run pythonor the local.venv. Never use the system Python directly.
Follow every step in order.
[CONFIRM] gates: Only Step 1 (Source Type) and Step 12 (Sanity-Check Plots) require explicit user approval. All other
[CONFIRM]markers are advisory — present decisions inline and proceed without blocking.Deliverables first: Write the source file and test file (Steps 6–7) before extended exploration, documentation, registration, CHANGELOG, or PR work. Skip Steps 8–14 when the user asks for implementation only.
Before you finish: Run verification commands in the repo root so results appear in the session log:
uv run pytest test/data/test_<source>.py -x make format && make lintBe concise: Avoid long architecture reports; summarize decisions in a few sentences and move on to file writes.
Hangs or User Feedback If agent becomes stuck or user provides a correction during this skills use, conservatively review relevant part of the skill and improve. Be concise.
One source type per invocation. Invoke again for companion types.
Reference Files
Load these on demand during the relevant steps:
| File | Content | Load at |
|---|---|---|
references/implementation-guide.py | Skeleton source with FILL comments | Steps 3–10 |
references/testing-guide.py | Test skeleton with FILL comments | Step 11 |
references/validation-guide.md | Plot templates, PR body template, Greptile handling | Steps 12–14 (optional, for templates) |
Workflow Overview
Step 0: Obtain reference → Step 1: Determine type → Step 2: Dependencies
→ Step 3: Add deps → Step 4: Create lexicon → Step 5: Update vocab/schema
→ Step 6: Create skeleton → Step 7: Implement source → Step 8: Register
→ Step 9: Documentation → Step 10: CHANGELOG → Step 11: Tests
→ Step 12: Validate & plots (user confirms) → Step 13: PR + sanity comment
→ Step 14: Greptile reviewStep 0 — Obtain Remote Data Store Reference
If $ARGUMENTS is provided, use it (URL → WebFetch; file path → read).
If empty, ask:
Please provide a URL, API documentation link, or description of the remote data store. This will be used to understand storage format, access pattern, variable inventory, temporal/spatial resolution.
Step 1 — Determine Source Type
| Protocol | Returns | Has lead_time? | Use |
|---|---|---|---|
| DataSource | xr.DataArray | No | Gridded analysis/reanalysis |
| ForecastSource | xr.DataArray | Yes | Gridded forecast |
| DataFrameSource | pd.DataFrame | No | Sparse/station obs |
| ForecastFrameSource | pd.DataFrame | Yes | Sparse forecast obs |
Key factors: gridded vs sparse → DataArray vs DataFrame; analysis vs forecast → Source vs ForecastSource.
[CONFIRM — Source Type]
Present recommended type with justification. Ask for confirmation.
Step 2 — Examine Remote Store & Propose Dependencies
Analyze: storage backend, file format, authentication, access pattern, temporal/spatial resolution, variable inventory.
Prefer fsspec:
| Backend | Preferred | Avoid |
|---|---|---|
| AWS S3 | s3fs (core dep) | boto3 directly |
| GCS | gcsfs (core dep) | google-cloud-storage |
| Azure | adlfs | azure-storage-blob |
| HTTP | fsspec (core dep) | requests |
| HuggingFace | huggingface_hub (core dep) | custom scripts |
Only fall back to dedicated libraries when fsspec cannot access the store.
Check pyproject.toml — only propose packages not already present.
Core deps include: s3fs, gcsfs, fsspec, zarr, netCDF4, h5py,
pygrib, huggingface-hub, pandas, pyarrow.
[CONFIRM — Dependencies & Access Pattern]
Present: backend, fsspec filesystem, new packages (with license), auth method.
Step 3 — Add Dependencies
Load
references/implementation-guide.pyfrom here through Step 10.
If new packages needed:
uv add --extra data <package>uv lockAdd optional dependency imports using
OptionalDependencyFailurepattern
Step 4 — Create Lexicon Class
Create earth2studio/lexicon/<source_name>.py with:
metaclass=LexiconTypeVOCAB: dict[str, str]mapping E2S names → remote keysget_item(cls, val)returningtuple[str, Callable]Use
::separator for structured keys
Map remote variables against E2STUDIO_VOCAB (282 entries in
earth2studio/lexicon/base.py).
[CONFIRM — Lexicon & Variable Mapping]
Present: class name, key format, full mapping table, modifiers, reference URL.
Step 5 — Update E2STUDIO_VOCAB / SCHEMA (if needed)
New vocab: surface = descriptive abbrev; pressure =
{name}{level}New schema fields: DataFrame sources only, check
E2STUDIO_SCHEMA
[CONFIRM — Vocabulary & Schema Updates]
Skip if no updates needed.
Step 6 — Create Skeleton Data Source File
Follow canonical method ordering:
Class constants
SCHEMA
__init___async_init__call__fetch_create_tasksfetch_wrapperfetch_array_validate_timeHelpers
cachepropertyavailableclassmethod
Use async task dataclass pattern for parallel execution.
[CONFIRM — Skeleton]
Present: class name, file path, skeleton code, task dataclass.
Step 7 — Implement the Data Source & Tests
The test file is a co-equal deliverable. Create
test/data/test_<filename>.pyalongside the source. Addtest_<source>_call_mockfor async sources.
Sync sources: Use prep_data_inputs/prep_forecast_inputs, direct __call__.
Async sources: See references/implementation-guide.py for required patterns:
_sync_async, managed_session, gather_with_concurrency, async_retry,
pure async I/O, try/finally cleanup. Constructor params: cache=True,
verbose=True, async_timeout=600, async_workers=16, retries=3.
DataFrame sources add time_tolerance.
Step 8 — Register the Source
earth2studio/data/__init__.py— alphabetical importearth2studio/lexicon/__init__.py— alphabetical importVerify
pyproject.tomldeps
Step 9 — Update Documentation
Add to correct RST file (
datasources_analysis.rst/_forecast.rst/_dataframe.rst)Class docstring: Parameters, Warning (download size), Note (reference URLs), Badges (last)
All public methods: NumPy-style docstrings
Step 10 — Update CHANGELOG.md
Add entry under the current unreleased version. See
references/implementation-guide.py REGISTRATION CHECKLIST for the format.
One line per source. Do NOT add separate lexicon entries.
Step 11 — Verify Style & Expand Tests
Run make format && make lint && make license. Load references/testing-guide.py
for test skeletons. Required tests: test_<source>_fetch (slow), _cache (slow),
_call_mock, _exceptions, _available. Target 90%+ coverage with --slow.
[CONFIRM — Tests]
Present test file, functions, coverage.
Step 12 — Validate Variables & Sanity-Check
Validate all lexicon vars against real data (run script, do NOT commit)
Remove variables with < 10% valid data
Create sanity-check plot (gridded or sparse template)
Tell user the plot path and ask for visual confirmation
[CONFIRM — Sanity-Check Plots]
User MUST visually inspect plots. Do not proceed without confirmation.
Step 13 — Branch, Commit & Open PR
Create branch
feat/data-source-<name>Commit (do NOT add sanity-check script/images)
Push to fork
gh pr create --repo NVIDIA/earth2studioImmediately post sanity-check validation as PR comment with:
Variable coverage table (name, count, range, unit)
Data validation summary (regions, storms/stations, time range)
Key findings (physically reasonable values, conversions verified)
Full validation script in
<details>blockImage placeholder:
<!-- Drag and drop sanity-check image here -->
[CONFIRM — Ready to Submit]
Verify all steps complete before creating PR.
Step 14 — Automated Code Review
Poll for Greptile review (5 min timeout)
Categorize feedback (bug/style/perf/docs/suggestion/false-positive)
Present triage table to user
Implement accepted fixes
Respond to PR comments
Push
[CONFIRM — Review Triage]
User approves which comments to address.
Examples
User: Add a data source for the NOAA GFS analysis on S3
Agent: [loads skill, proceeds through Steps 0–14]Limitations
One source type per invocation
Requires network access for validation (Step 12)
SPDX license headers required in all files
Reminders
DO: uv run python, loguru.logger, alphabetical order in __init__.py/RST/CHANGELOG,
canonical method ordering, async utilities (managed_session, gather_with_concurrency,
async_retry), pure async I/O, reference URLs in docstrings, try/finally cleanup.
AVOID: asyncio.to_thread, bare tqdm.gather, xarray for loading, full file downloads.
NEVER: loop.set_default_executor(), commit secrets, commit sanity-check scripts/images.
Files
- ATTRIBUTION.mdAdded by AutoGineer961 B
- BENCHMARK.md2.4 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md10.4 KiB
- evals/config.yml1.1 KiB
- evals/environment/Dockerfile867 B
- evals/environment/setup/bootstrap.shScript934 B
- evals/evals.json6.1 KiB
- evals/targets/eval_1_target.pyScript2.5 KiB
- evals/targets/eval_2_target.pyScript2.9 KiB
- evals/targets/eval_3_target.pyScript3.8 KiB
- evals/targets/eval_4_target.pyScript11.5 KiB
- evals/targets/test/eval_1_test_target.pyScript2.4 KiB
- evals/targets/test/eval_2_test_target.pyScript3.1 KiB
- evals/targets/test/eval_3_test_target.pyScript3.7 KiB
- evals/targets/test/eval_4_test_target.pyScript4.5 KiB
- references/implementation-guide.pyScript17.3 KiB
- references/testing-guide.pyScript10.1 KiB
- references/validation-guide.md9.5 KiB
- skill-card.md2.6 KiB
- skill.oms.sig7.9 KiB
references/testing-guide.py
# SPDX-FileCopyrightText: Copyright (c) 2024-2026 NVIDIA CORPORATION & AFFILIATES.
# SPDX-FileCopyrightText: All rights reserved.
# SPDX-License-Identifier: Apache-2.0
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
"""Test reference skeleton for new Earth2Studio data sources.
This file is a TEMPLATE. Copy it to test/data/test_<source_name>.py,
rename all ``source`` prefixes, and fill in every ``# FILL:`` comment.
Canonical test order (must match this sequence):
1. test_source_fetch — slow, xfail, real network
2. test_source_cache — slow, xfail, cache toggle
3. test_source_call_mock — REQUIRED, no network, no xfail
4. test_source_exceptions — error paths
5. test_source_available — available() classmethod
6. test_source_validate_time — (optional) _validate_time internals
Rules:
- No docstrings on test functions (project convention)
- Use strategic parameterization — minimize combos, maximize coverage
- Target 90%+ line coverage with --slow
- Run: pytest test/data/test_<source_name>.py -v
Automatic Test Skipping:
------------------------
If your data source requires optional dependencies (e.g., special decoders,
API clients), register your test file in test/conftest.py's _TEST_DEPENDENCIES
mapping. This ensures pytest skips the file during collection when dependencies
are missing, preventing ImportError before tests even run.
Example in test/conftest.py:
_TEST_DEPENDENCIES: dict[str, list[str]] = {
# ...existing entries...
"test/data/test_newsource.py": ["data"], # use pyproject.toml group
"test/data/test_special.py": ["special_decoder"], # or individual package
}
This replaces the need for pytest.importorskip() at module level for skipping
the entire file. Use pytest.importorskip() only when you need to skip specific
tests within a file that otherwise runs without optional deps.
See real examples:
- Gridded ForecastSource: test/data/test_cfs.py
- DataFrame DataFrameSource: test/data/test_nnja.py
- HTTP DataFrame: test/data/test_gdas.py
"""
from __future__ import annotations
import pathlib
import shutil
from datetime import datetime, timedelta
from unittest.mock import AsyncMock, patch
import numpy as np
import pandas as pd
import pytest
# FILL: Import your source class
# from earth2studio.data import SourceName
# FILL: If source has optional deps, guard with importorskip:
# pytest.importorskip("special_decoder", reason="special_decoder not installed")
# FILL: Pick a known-valid time for network tests (inside source's valid range)
_TEST_TIME = datetime(year=2024, month=6, day=1, hour=0)
# ======================================================================
# 1. Network fetch test (slow, xfail)
# ======================================================================
@pytest.mark.slow
@pytest.mark.xfail
@pytest.mark.timeout(60)
@pytest.mark.parametrize(
"time",
[
_TEST_TIME, # FILL: single datetime
[_TEST_TIME, _TEST_TIME + timedelta(hours=6)], # FILL: list of datetimes
],
)
@pytest.mark.parametrize("variable", ["t2m", ["t2m", "msl"]]) # FILL: real variables
def test_source_fetch(time, variable):
# FILL: Instantiate your source
# ds = SourceName(cache=False)
# data = ds(time, variable)
# FILL: For ForecastSource, add lead_time arg:
# data = ds(time, timedelta(hours=6), variable)
if isinstance(variable, str):
variable = [variable]
if isinstance(time, datetime):
time = [time]
# FILL: Assert shape matches expectations
# DataSource: (time, variable, lat, lon)
# assert data.shape == (len(time), len(variable), EXPECTED_LAT, EXPECTED_LON)
# ForecastSource: (time, lead_time, variable, lat, lon)
# assert data.shape == (len(time), 1, len(variable), EXPECTED_LAT, EXPECTED_LON)
# assert not np.isnan(data.values).any()
# assert np.array_equal(data.coords["variable"].values, np.array(variable))
pass
# ======================================================================
# 2. Cache test (slow, xfail)
# ======================================================================
@pytest.mark.slow
@pytest.mark.xfail
@pytest.mark.timeout(60)
@pytest.mark.parametrize("cache", [True, False])
def test_source_cache(cache):
# FILL: Instantiate and fetch
# ds = SourceName(cache=cache)
# data = ds(_TEST_TIME, ["t2m"])
#
# assert not np.isnan(data.values).any()
# assert pathlib.Path(ds.cache).is_dir() == cache
#
# # Second fetch exercises cache path
# data2 = ds(_TEST_TIME, ["t2m"])
# assert data2.shape == data.shape
#
# try:
# shutil.rmtree(ds.cache)
# except FileNotFoundError:
# pass
pass
# ======================================================================
# 3. Mock test — REQUIRED (no network, no xfail, no slow)
# ======================================================================
@pytest.mark.timeout(15)
def test_source_call_mock(tmp_path, monkeypatch):
# FILL: Set cache dir to tmp_path
monkeypatch.setenv("EARTH2STUDIO_CACHE", str(tmp_path))
# FILL: Create fake data that your fetch_array/decode would return
# For gridded sources:
fake_grid = np.full((181, 360), 273.15, dtype=np.float32) # FILL: grid dims
# FILL: Define async mocks for the I/O layer
async def _fake_fetch_array(task):
return fake_grid
# FILL: Instantiate source
# ds = SourceName(cache=True)
# FILL: Patch the async methods that do real I/O
# Strategy: patch _async_init (skip fs creation) + fetch_array (skip network)
#
# with (
# patch.object(ds, "_async_init", new=AsyncMock(return_value=None)),
# patch.object(ds, "fetch_array", side_effect=_fake_fetch_array),
# ):
# ds.fs = object() # type: ignore[assignment] # truthy sentinel
# data = ds(_TEST_TIME, ["t2m", "msl"])
#
# # Verify output shape and content
# assert data.shape == (1, 2, 181, 360) # FILL: expected shape
# np.testing.assert_allclose(data.sel(variable="t2m").values[0], fake_grid)
pass
# ======================================================================
# 3b. Mock test for DataFrame sources
# ======================================================================
@pytest.mark.timeout(15)
def test_source_call_mock_dataframe(tmp_path, monkeypatch):
# FILL: Only include this if your source returns pd.DataFrame
monkeypatch.setenv("EARTH2STUDIO_CACHE", str(tmp_path))
# FILL: Create mock DataFrame matching your source's SCHEMA
# mock_df = pd.DataFrame({
# "time": pd.to_datetime(["2024-06-01 00:30:00", "2024-06-01 01:00:00"]),
# "lat": np.array([40.0, 35.0], dtype=np.float32),
# "lon": np.array([250.0, 280.0], dtype=np.float32),
# "observation": np.array([273.15, 288.0], dtype=np.float32),
# "variable": ["t", "t"],
# # FILL: Add all SCHEMA columns
# })
# FILL: Mock the async fetch path
# with patch("earth2studio.data.<module>._sync_async") as mock_sync:
# mock_sync.return_value = mock_df
# ds = SourceName(cache=False)
# df = ds(_TEST_TIME, ["t"])
#
# assert isinstance(df, pd.DataFrame)
# assert list(df.columns) == ds.SCHEMA.names
# assert not df.empty
# assert set(df["variable"].unique()) == {"t"}
pass
# ======================================================================
# 4. Exception / error handling tests
# ======================================================================
@pytest.mark.timeout(10)
def test_source_exceptions():
# FILL: Test invalid variable via lexicon
# with pytest.raises(KeyError):
# from earth2studio.lexicon import SourceNameLexicon
# SourceNameLexicon["nonexistent_variable"]
# FILL: Test invalid time raises ValueError from _validate_time
# ds = SourceName(cache=False)
# with pytest.raises(ValueError):
# ds(datetime(1800, 1, 1), ["t2m"]) # before MIN_DATE
# FILL: Test misaligned time (e.g. odd hour for 6h interval)
# with pytest.raises(ValueError):
# ds(datetime(2024, 1, 1, 13), ["t2m"])
# FILL: For DataFrame sources, test invalid fields
# with pytest.raises(KeyError):
# SourceName.resolve_fields(["nonexistent_field"])
pass
# ======================================================================
# 5. Available classmethod test
# ======================================================================
@pytest.mark.timeout(5)
def test_source_available():
# FILL: Valid time should return True
# assert SourceName.available(datetime(2024, 6, 1, 0)) is True
# FILL: Time before MIN_DATE should return False
# assert SourceName.available(datetime(1800, 1, 1)) is False
# FILL: Misaligned time should return False
# assert SourceName.available(datetime(2024, 1, 1, 13)) is False
# FILL: Test with np.datetime64 input
# assert SourceName.available(np.datetime64("2024-06-01T00:00")) is True
pass
# ======================================================================
# 6. (Optional) Validate time internals
# ======================================================================
@pytest.mark.timeout(5)
def test_source_validate_time():
# FILL: Only include if _validate_time has non-trivial logic worth testing
# directly. Otherwise the available() test covers it.
# FILL: Valid times pass without exception
# SourceName._validate_time([datetime(2024, 1, 1, 0)])
# SourceName._validate_time([datetime(2024, 1, 1, 6)])
# FILL: Invalid times raise ValueError
# with pytest.raises(ValueError):
# SourceName._validate_time([datetime(2024, 1, 1, 1)]) # off-grid
# with pytest.raises(ValueError):
# SourceName._validate_time([datetime(1900, 1, 1, 0)]) # too early
pass
Requirements and compatibility
Written for: Claude Code
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Claude Code frontmatter, Names Claude Code tools, Needs Python
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- NVIDIA Earth-2 Team
- Publisher
- NVIDIA (Official)
- Source
- NVIDIA/skills · skills/earth2studio-create-datasource · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by NVIDIA Earth-2 Team or NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download earth2studio-create-datasource.zip