arcgis-to-portaljs
Migrate a whole ArcGIS Hub site into a PortalJS Arc portal end-to-end. Harvests the Hub /data.json (DCAT-US) inventory, exports every FeatureService layer through the ArcGIS REST query API with resultOffset paging, converts each to the serverless dual tier (PMTiles render + GeoParquet query) with tabular items to Parquet, pushes everything to Cloudflare R2 via Git LFS, appends dual-tier datasets.json entries, and writes a source-vs-derived parity report. Use to move a City or sector ArcGIS Hub open-data portal onto PortalJS with no server-side compute.
npx skills add datopian/portaljs --skill arcgis-to-portaljs --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# ArcGIS Hub → PortalJS ## Overview Migrate an entire **ArcGIS Hub** open-data site into a **PortalJS Arc** portal in one pass. Every Hub site is machine-readable — a DCAT-US catalog at `/data.json`, with every dataset backed by an ArcGIS REST FeatureService — so migration is a **harvest → export → convert → publish → verify** pipeline that runs almost fully automated on the operator's machine, no server-side compute. The tooling is the reusable `arcgis-to-portaljs` migrator: input is one Hub URL, output is a ready-to-deploy PortalJS catalog plus a parity report. The skill is an orchestrator: it reuses the DCAT-US harvest from `portaljs-migrate`, the `ogr2ogr`/`tippecanoe`/`duckdb` dual-tier conversion from `portaljs-add-geo`, and the bulk Git-LFS → R2 push from `portaljs-migrate`. Its novel parts are the FeatureService REST export loop (paged features, not just a link) and the source-vs-derived parity report. ## Prerequisites - A scaffolded PortalJS portal whose template ships `components/MapPreview.tsx` and `components/GeoQuery.tsx` (PR #1647 or later). Run `portaljs-new-portal` first if none. - Native CLIs: **GDAL** (`ogr2ogr`, `ogrinfo`), **tippecanoe**, **duckdb** (with `spati
- Overview
- Prerequisites
- Instructions
- Output
- Error Handling
- Examples
- Example 1 — Migrate a City Hub (Lewisville)
- Example 2 — Dry-run inventory + plan only (no writes)
- Example 3 — Migrate a subset, one namespace per publisher
- Resources
What does the arcgis-to-portaljs skill do?
Migrate a whole ArcGIS Hub site into a PortalJS Arc portal end-to-end. Harvests the Hub /data.json (DCAT-US) inventory, exports every FeatureService layer through the ArcGIS REST query API with resultOffset paging, converts each to the serverless dual tier (PMTiles render + GeoParquet query) with tabular items to Parquet, pushes everything to Cloudflare R2 via Git LFS, appends dual-tier datasets.json entries, and writes a source-vs-derived parity report. Use to move a City or sector ArcGIS Hub open-data portal onto PortalJS with no server-side compute.
How do I install it?
Run `npx skills add datopian/portaljs --skill arcgis-to-portaljs --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.