data-workflows
Routes leafmap users to geospatial data conversion, readers, downloads, and remote-source helpers such as STAC, OSM, Planetary Computer, fire, and Terrascope.
- License 许可
- MIT
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- data-workflows
- license
- MIT
- metadata
- { "disco-role": "operating" }
- description
- Routes leafmap users to geospatial data conversion, readers, downloads, and remote-source helpers such as STAC, OSM, Planetary Computer, fire, and Terrascope.
- disable-model-invocation
- true
02 资源文件 3
- 参考文档references/api-reference.md3.4 KB
- 参考文档references/troubleshooting.md1.5 KB
- 参考文档references/workflows.md1.5 KB
03 SKILL.md 正文
Data Workflows
Purpose
Use this sub-skill when the task is about getting geospatial data into or out of leafmap workflows rather than drawing the map itself.
Read this when
- The user wants to convert between CSV, GeoJSON, shapefile, KML, GeoPackage, Parquet, or related formats.
- The user asks for STAC, Planetary Computer, OSM, fire, Terrascope, NAIP, or Overture-related helper workflows.
- The task is about raster/vector readers, download helpers, or tiny validation checks for data files.
What this sub-skill owns
leafmap.commonconversion and data-loading helpers.leafmap.stac,leafmap.download,leafmap.osm,leafmap.pc,leafmap.fire,leafmap.terrascope, andleafmap.plot.- Simple packaged sample data and smoke-friendly data checks.
What this sub-skill does not own
- Map rendering or widget layout.
- Backend selection.
- Standalone viewer CLI behavior.
- Optional backend-specific viewer details.
First place to look
references/api-reference.mdfor verified helper names and signatures.references/workflows.mdfor the shortest safe recipes.references/troubleshooting.mdwhen imports, CRS, bbox, or remote sources fail.../../scripts/check_leafmap_smoke.pywith--mode datafor a fast local sanity check.
How to route a request
- Use local conversion helpers for file-format questions.
- Use STAC / Planetary Computer / OSM / fire / Terrascope helpers when the user is asking for a data source rather than a map backend.
- If the request needs a visible map after the data step, hand off to
interactive-mapsormaplibre-viewers.
Typical workflow
- Identify the source type and target format or service.
- Confirm coordinate order, CRS, and file availability.
- Use the smallest helper that performs the conversion or query.
- Only add map rendering once the data step is proven.
- If the task depends on network access or credentials, call that out early.
Common decision points
- Prefer local, packaged fixtures or synthetic data for smoke checks.
- Prefer STAC / Planetary Computer / OSM helpers for discovery and small metadata queries.
- Prefer the root smoke helper before trying a live network source.
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).