coordinate-systems

coordinate-systems is a skill for Claude Code from iowarp/clio-kit. It costs 53 tokens per session (1,032 once invoked), scanned A, original, BSD-3-Clause.

A guide to interpreting geographic coordinates, map projections, distance units, and height reference systems. A coordinate reference system describes how locations on Earth are represented on a map or in data.

In plain words
What is it for?
Use it to check GeoJSON coordinate order, understand latitude and longitude, choose suitable distance calculations, and reason about projections and vertical datums.
Why use it?
It prevents maps and distance calculations from looking correct while placing features in the wrong location or using the wrong units. It highlights common longitude-latitude ordering mistakes.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the clio-geoscience-skills plugin — 3 skills shipped together

Good fit Use it to check GeoJSON coordinate order, understand latitude and longitude, choose suitable distance calculations, and reason about projections and vertical datums.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/iowarp/clio-kit/coordinate-systems
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add iowarp/clio-kit --skill coordinate-systems
Clone the repo
git clone --depth 1 https://github.com/iowarp/clio-kit

Made for: Claude Code.

Or install clio-geoscience-skills, the plugin that ships this one along with the rest of its 3 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for coordinate-systems

README.md
[![agentmods](https://agentmods.dev/badge/skills/iowarp/clio-kit/coordinate-systems/github.svg)](https://agentmods.dev/skills/iowarp/clio-kit/coordinate-systems)
Your own site
<a href="https://agentmods.dev/skills/iowarp/clio-kit/coordinate-systems"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/coordinate-systems/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for coordinate-systems

Your own site · 80×15
<a href="https://agentmods.dev/skills/iowarp/clio-kit/coordinate-systems"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/coordinate-systems.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,032 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00053 $0.01032
Opus 5.5 $0.00021 $0.00413
Sonnet 5.5 $0.00011 $0.00206
Haiku 4.5 $0.00005 $0.00103

Measured 9d ago against content hash 1a8920d37d08, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

coordinate-systems scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/clio-geoscience-skills/skills/coordinate-systems/SKILL.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Coordinate Systems

Nothing here raises an error. Data in the wrong reference system plots, computes distances, and returns bounding boxes — just in the wrong place. This is the class of bug that survives review because every step succeeded.

Longitude first, in GeoJSON

GeoJSON positions are [longitude, latitude]. Bounding boxes are [min_lon, min_lat, max_lon, max_lat].

Almost everything a human writes is the other way round — "41.8, -87.6" for Chicago is lat, lon. Reversed coordinates near the equator land in the ocean off Africa; at mid-latitudes they land somewhere plausible-looking, which is worse.

Sanity check any position before trusting it: longitude is in [-180, 180], latitude in [-90, 90]. A first value beyond ±90 is definitely longitude. Both under 90 and it is ambiguous — check against a known landmark.

Geographic degrees are not a distance

Latitude and longitude are angles. One degree of latitude is about 111 km everywhere; one degree of longitude is 111 km at the equator, about 78 km at 45°, and zero at the pole.

So Euclidean distance on lon/lat is wrong, and wrong by a factor that changes with where you are. Compare two things at different latitudes with it and the comparison is meaningless.

clio-geo:filter_points_by_radius computes great-circle distance, which is the correct thing on a sphere. Use it rather than differencing coordinates. When clio-geo:bounding_box pads by buffer_km it is doing the same conversion; a padded box is not a fixed number of degrees on every side.

Area is worse. A polygon's area in square degrees is not a physical quantity at all, and cannot be converted by one factor because the factor varies across the polygon.

Geographic versus projected

  • Geographic (WGS84, EPSG:4326) — angles on the globe. What GPS and GeoJSON give you. Good for storing and sharing position, bad for measuring.
  • Projected (UTM, State Plane, and so on) — linear coordinates (often metres, sometimes feet) on a plane, with controlled distortion within a defined zone and degrading outside it. Good for measuring, bad for spanning large areas.

Read the full file on GitHub · 103 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 103 lines · 53 tokens per session scan A 1a8920d37d08

Subscribe to this mod's changes

coordinate-systems is a skill published in the GitHub repository iowarp/clio-kit (30 stars, last pushed 8d ago), licensed BSD-3-Clause. It adds 53 tokens to every session and 1,032 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-08.

Related

Other skills, from other repositories

bio-ortholog-inference

Pull pre-computed ortholog calls from public databases (OrthoDB, Ensembl Compara, OMA browser, eggNOG, PANTHER, KEGG Orthology, HomoloGene) via their REST APIs. Use when orthologs are already curated upstream, when the question is "what is the X ortholog of Y" rather than "how to infer orthology de novo", when…

PKU-YuanGroup/OpenAI4S · 141 tokens

admet_genetic

ADMET-guided genetic molecule optimization workflow from seed SMILES; use when the agent needs to build or run an RDKit/SA-Score/ADMET-AI GA pipeline for molecule optimization, enforce molecule lineage logs, render optimization-history HTML dashboards, and write candidate triage reports.

PKU-YuanGroup/OpenAI4S · 63 tokens

paper-figures

Use this skill to produce standalone, publication-ready PNG graphics and reproducible matplotlib scripts from tabular data (CSVs or DataFrames). It renders numerical data into formal scientific visualizations—including scatter, line, bar, pie, ring, bubble, tornado, KDE, violin, box, heatmap, histogram, and area…

EvoScientist/EvoSkills · 197 tokens

paper-planning

Guides pre-writing planning for academic papers with 4 structured steps: story design (task-challenge-insight-contribution-advantage), experiment planning (comparisons + ablations), figure design (pipeline + teaser), and 4-week timeline management. Includes counterintuitive planning tactics (write a mock rejection…

EvoScientist/EvoSkills · 166 tokens

paper-review

Guides self-review of YOUR OWN academic paper before submission with adversarial stress-testing. Core method: three passes (adversarial deep read; 5-aspect checklist — contribution sufficiency, writing clarity, results quality, testing completeness, method design; mechanical consistency scans and experimental protocol…

EvoScientist/EvoSkills · 200 tokens

experiment-craft

Use this skill when the user wants to debug, diagnose, or systematically iterate on an experiment that already exists, or when they need a structured experiment log for tracking runs, hypotheses, failures, results, and next steps during active research. Apply it to underperforming methods, training that will not…

EvoScientist/EvoSkills · 172 tokens