mapcentia/gc2
GC2 (Geo Compute Cloud): the GC2 MCP server (tools generated from the GC2 OpenAPI spec) plus skills covering runtime SDK usage, provisioning, JSON-RPC, auth, OGC/OWS services, snapshots, scheduler, realtime and delivery rules.
Danish address and cadastral (matrikel) search component for GC2 apps. Covers installation, initialization, option configuration, result handling, and integration with GC2 SDK for spatial queries.
Authentication policy for GC2 BaaS across browser, backend, CLI, and provisioning contexts, including required SDK flows and environment variable usage.
Use when creating, listing, editing, publishing or deleting Vidi configurations (what the GC2 Dashboard calls "Configurations") in GC2 BaaS, or handing Vidi a published configuration URL — /api/v4/configurations endpoints, the getConfiguration/postConfiguration/patchConfiguration/deleteConfiguration/getPublicConfiguration tools, the Configurations SDK class, configuration_* keys, the body-as-JSON-text rule, the anonymous .json form, or CONFIGURATION_NOT_FOUND / SUPER_USER_ONLY errors.
Delivery and validation checklist for GC2 tasks, including required output sections, MCP tool reference, geospatial mapping library selection, and final self-check criteria.
Use when reading, creating, updating, or deleting individual geographic features (rows) as GeoJSON by primary key in GC2 BaaS tables, or when working with /api/v4/schemas/{schema}/tables/{table}/features endpoints, getFeature/postFeature/patchFeature/deleteFeature tools, the Features SDK class, WFS-T feature editing, or the srs/SRID of feature geometry.
Two-step GC2 file import workflow using MCP tools, covering upload, processing options, validation mode, geospatial projection settings, and supported input formats.
JSON-RPC method lifecycle for GC2 BaaS, including method creation, invocation, dry-run type inference, TypeScript interface generation, and runtime usage with createApi or Rpc.
Use when storing or reading small JSON state (app settings, feature flags, user preferences, drafts, snapshots) in the GC2 BaaS key/value store, or when working with /api/v4/keyvalue endpoints, the Keyvalue SDK class, keys, owner/public flags, or paths projection.
Map view configuration and layer cartography for GC2 BaaS, including per-schema map center/zoom/extent, layers, classes, styles, and labels, MapServer-backed rendering, id round-trip rules, and payload value conventions.
Use when reading features or rendering maps through the OGC API (OGC API Features Part 1/2, OGC API Maps Part 1) in GC2 BaaS — /api/v4/ogc/database/{database}/... routes, collections, items as GeoJSON with bbox/limit/offset/crs/datetime, map images, the getOgc* tools, CRS URIs and axis order, or the 401/403/404 semantics of collections.
OpenAPI and documentation fallback policy for GC2 BaaS, including source priority, local caching workflow, and rules for docs-backed endpoint usage.
Use when serving or querying layers through the classic OGC web services in GC2 BaaS — WMS/UTFGRID/MVT via /api/v4/ows, WFS and WFS-T via /api/v4/wfs, the authorizing MapCache (WMTS/TMS/XYZ) proxy via /api/v4/mapcache, the getOws/postOws/getWfs/postWfs/getMapcache/deleteMapcacheTileset tools, the FILTERS/labels parameters, srs and time-slice path segments, or Basic/Bearer/anonymous access to protected layers.
Sub-user privileges and rights inheritance for GC2 BaaS, including per-table privilege grants, group membership via user_group, transitive inheritance where the highest privilege wins, schema ownership, and layer authentication levels.
Provisioning and schema lifecycle guidance for GC2 BaaS, including schema/table/column/index/constraint operations, migration structure, SQL API limits, and destructive-change safety.
Realtime events via WebSocket for GC2 BaaS using @mapcentia/gc2-sdk, including broadcast connections, subscriptions with shapes, event handling, and enabling table-level change events.
Global hard rules for any work involving GC2 (Geo Compute Cloud) BaaS, @mapcentia/gc2-sdk or the GC2 MCP tools. Load this first on every GC2-related task — it sets tool priority (MCP > SDK > OpenAPI > docs), runtime-vs-provisioning boundaries, security and auth baselines, the destructive-operations confirmation policy, and routes to the task-specific gc2-* skills.
Runtime application guidance for GC2 BaaS using @mapcentia/gc2-sdk, including SDK client initialization, GraphQL/JSON-RPC/SQL method selection, HTTP fallback boundaries, and frontend tooling defaults.
Use when creating or managing automated data imports in GC2 BaaS — /api/v4/scheduler jobs and runs, the SchedulerJob/SchedulerRun tools, five-field cron schedules, WFS/file import jobs, starting or stopping runs manually, monitoring run status/heartbeat/stale, or queueing snapshots after imports.
Use when serving or configuring the merged per-schema tilesets in GC2 BaaS — one combined tile layer of ALL layers in a schema, the <schema>/<schema>.mvt tileset names, /api/v4/schemas/{schema}/tile settings (getSchemaTileSettings/patchSchemaTileSettings/deleteSchemaTileSettings), 403/empty/mis-stacked schema tiles, tile URL forms (TMS/gmaps @grid vs WMTS), or clearing a schema tileset's cache.
Use when exporting GC2 BaaS tables/views as Parquet or FlatGeobuf snapshots, or reading published snapshots for analytics — /api/v4/snapshots job endpoints, /api/v4/schemas/{schema}/relations/{relation}/snapshots read endpoints, the Snapshot tools, DuckDB/read_parquet over HTTP Range, presigned URLs, snapshot formats, or snapshot_date-based downloads.
Use when seeding, warming, or prerendering a MapCache tile cache in GC2 BaaS — "tiles are slow the first time", prerender/seed a tileset, /api/v4/tileseeder/jobs, the postSeedJob/getSeedJob/getSeedJobs/deleteSeedJob tools, mapcache_seed, UNKNOWN_GRID or TOO_MANY_PENDING errors, cancelling or monitoring seed jobs, or the v3 tileseeder.
PostgreSQL and PostGIS type guidance for GC2 BaaS, including SQL parameter casts, type_hints, type_formats, and supported output formats for SQL and JSON-RPC responses.