maps-and-deliverableslisted
Install: claude install-skill wiatrek-kevin-s/columbus
# Maps and deliverables
A deliverable is finished when the person receiving it can use it without asking you
anything: right CRS, right format, right field names, sources and dates stated, and a map a
reader can interpret correctly. Get the spec first, then build to it, then check against it.
## General practice (with or without Columbus)
### 1. Get the spec before you start
Ask or look up, and write down:
- **CRS** (horizontal and vertical, with EPSG codes and units) and whether it is a hard rule.
- **Formats**: GeoPackage, file geodatabase, shapefile, CSV, KML, PDF, PNG; one file or a
zipped package; naming convention for files and layers.
- **Fields**: which to include, renames, order, types, whether coded fields go as codes,
labels or both, date format.
- **Metadata** required (title, abstract, sources, dates, contact, constraints) and in what
standard (ISO 19115/19139, FGDC CSDGM, or the recipient's own form).
- **Map products**: page size, orientation, resolution, logo and disclaimer text.
- Who receives it, by when, and how (shared drive, portal, email size limit).
### 2. Layout elements
| Element | Include when | Notes |
| --- | --- | --- |
| Title | Always | Says what, where and when ("Functional class, District 14 roads, October 2026") |
| Legend | Whenever symbols need explaining | Only layers shown; labels in plain words, with units; no "Layer1" or field names |
| Scale bar | Large and medium scales in a projected CRS | Units the reader uses (feet and