← ClaudeAtlas

working-with-columbuslisted

How to work through a governed GIS server such as Columbus, from the first whoami call to describe, sample and query a dataset, pass ws:// handles between tools, read checks, wait for approvals and handle refusals or hidden fields, and how to work with tables of a million rows or more and build a local project database (keys, indexes, joins in SQL). Use it at the start of any GIS session with Columbus tools, or when someone asks to "query a layer", "pull features", "run a query on roads", "join these tables", "build a project database", "why was this refused" or "what do these checks mean".
wiatrek-kevin-s/columbus · ★ 2 · API & Backend · score 68
Install: claude install-skill wiatrek-kevin-s/columbus
# Working with Columbus Columbus is a governed GIS server. The agent can ask for anything; the server decides, and enforces its rules in its own code. This skill is advice on working well inside those rules. It never replaces them, and nothing here is a way around them. ## General practice (with or without Columbus) These habits apply to any GIS data source: a database, a file share, an API. 1. **Know who you act for and what is allowed** before touching data. Which sources can you read? Can you edit anything? Is there a row limit? Are there organization rules, such as "deliverables in EPSG:3081"? 2. **Read what the organization already wrote down** about a dataset before you query it: the data dictionary, the gotchas, coded domains, the owner. Guessing what `STATUS = 'R'` or `FUNC_CLASS = 3` means is how wrong answers get made. 3. **Describe, then sample, then query.** Look at the fields, geometry type and CRS. Then look at a few real rows to see how codes are spelled, whether keys are padded, and where the nulls are. Only then write the filter. 4. **Prefer structured queries to free SQL.** Name fields and give a filter. The less SQL you write by hand, the less there is to get wrong. 5. **Move data as files, not pasted text.** Keep each intermediate result as a layer and pass a reference to it to the next step. Do not paste thousands of rows into a prompt. 6. **Read every warning and say what it means.** A result with a warning is not a success.