Agent skill · Data & Analytics

portaljs-add-geo

Auto-ingest a geospatial file (GeoJSON, Shapefile, GeoPackage, KML/KMZ, FlatGeobuf, CSV-with-geometry) into a PortalJS portal on the user's own machine, with no server. Normalizes CRS to EPSG:4326, derives a PMTiles render tier and a GeoParquet query tier, pushes all three artifacts to Cloudflare R2 via Git LFS, and appends one dual-tier datasets.json entry the showcase auto-renders. Use when the source is a vector geo format that needs a map or spatial-query view.

datopiangithub.com/datopianGitHub ↗
claude-codecan modify filesMIT
Install
npx skills add datopian/portaljs --skill portaljs-add-geo --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Version: 1.0.0
Declared author: Datopian <hello@datopian.com>
Allowed tools: ReadWriteEditBash(ogr2ogr:*)Bash(ogrinfo:*)Bash(tippecanoe:*)Bash(duckdb:*)Bash(git:*)Bash(curl:*)Bash(npx:*)Bash(node:*)Bash(mkdir:*)
Requires: Claude Code with PortalJS portals (Next.js 14, React 18/19, Node 18+). Requires native GDAL, tippecanoe, and duckdb on…
Path: skills/portaljs-add-geo/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,337
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# PortalJS — Add Geo ## Overview Turn one geospatial upload into a **dual-tier** PortalJS dataset entirely on the user's machine — **no server-side container compute**, keeping the zero-backend bet end-to-end. From a single source the skill derives two serverless tiers plus the preserved original: - **PMTiles** (render tier) — a vector-tile archive `<MapPreview>` renders with MapLibre GL over HTTP range requests; any dataset size pans and zooms with no tile server. - **GeoParquet** (query tier) — a GeoParquet 1.1 file (covering `bbox` column, Hilbert-sorted) `<GeoQuery>` runs spatial SQL over in place via DuckDB-Wasm. - **Original** — the untouched upload in its native CRS, kept downloadable. All three land on Cloudflare R2 (Git LFS → Giftless), and the skill appends **one** `datasets.json` entry whose `resources[]` match the shape the showcase auto-renders (the `@reference/world-boundaries` demo, PR #1647): `pmtiles` → `<MapPreview>`, `geoparquet` → `<GeoQuery>`, original → download. No page edits are needed. It automates the manual `tippecanoe`/`duckdb` recipes in the template README. ## Prerequisites - A scaffolded `portaljs-catalog` portal whose template ships `components/MapPr

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Instructions
  4. Output
  5. Error Handling
  6. Examples
  7. Example 1 — Ingest a GeoJSON into both tiers
  8. Example 2 — Zipped Shapefile from a URL
  9. Example 3 — GeoPackage with an explicit layer and namespace
  10. Resources
Ships with 1 file
  • references/reference.md
More from portaljs
All skills →
About this skill
What does the portaljs-add-geo skill do?

Auto-ingest a geospatial file (GeoJSON, Shapefile, GeoPackage, KML/KMZ, FlatGeobuf, CSV-with-geometry) into a PortalJS portal on the user's own machine, with no server. Normalizes CRS to EPSG:4326, derives a PMTiles render tier and a GeoParquet query tier, pushes all three artifacts to Cloudflare R2 via Git LFS, and appends one dual-tier datasets.json entry the showcase auto-renders. Use when the source is a vector geo format that needs a map or spatial-query view.

How do I install it?

Run `npx skills add datopian/portaljs --skill portaljs-add-geo --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From datopian/portaljs, a repository with 2,337 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going