rundale-geo-tool

Realign Rundale world.json coordinates across real, manual, and fictional geo_kind types.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/dmooney/Rundale --skill rundale-geo-tool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rundale-geo-tool
Source: https://github.com/dmooney/Rundale/tree/main/.agents/skills/rundale-geo-tool
Command: npx skills add https://github.com/dmooney/Rundale --skill rundale-geo-tool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents Rundale world geography from drifting by providing a reliable workflow for computing and realigning lat/lon coordinates across real, manual (historical), and fictional locations.

Core Features & Use Cases

  • Geographic coordinate realignment for Rundale: Resolve absolute coordinates from geocoded real places, authoritative historical pins, and coherent fictionals that follow nearby anchors.
  • Cluster propagation via relative_to: Subordinate village/farm clusters to an anchor so future anchor edits carry the cluster with them rigidly.
  • Correct tool selection for 1820s Ireland: Decide between geo_kind values (real/manual/fictional) and understand why modern geocoders are the wrong primary source for physical 1820s settlement positions.

Quick Start

Use rundale-geo-tool to realign coordinates in mods/rundale/world.json with just realign-coords after updating pins or cluster relative_to offsets.

Frequently Asked Questions about rundale-geo-tool

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I realign historical map coordinates with modern lat lon data?

To realign historical map coordinates, run the realign pipeline to compute historical ENU offsets and apply relative_to edits. This process subordinates village clusters to anchors, ensuring historical OS map positions remain coherent and deterministic.

Why does modern geocoding drift historical settlement coordinates?

Modern geocoding drifts historical settlement coordinates because contemporary physical positions differ from 1820s Ireland settlements. Using geo_kind values like manual pins based on historical OS maps prevents this lat/lon drift and maintains geographic coherence.

What is the best way to subordinate village clusters to an anchor coordinate?

Subordinating village clusters to an anchor coordinate uses relative_to offsets, ensuring future anchor edits rigidly carry the entire cluster. This cluster propagation maintains deterministic world.json formatting and resolver resolution order during geographic realignment.

When do I need to use manual geo_kind pins instead of real geocoded coordinates?

Manual geo_kind pins are needed when modern geocoders provide incorrect physical positions for 1820s Ireland settlements. Assigning manual coordinates based on historical OS maps preserves accurate settlement locations that real geocoded data cannot resolve.

How do I run the parish-geo-tool realign pipeline for world.json updates?

Run the parish-geo-tool realign pipeline by executing realign_rundale_coords and supporting scripts after updating pins or cluster relative_to offsets in mods/rundale/world.json. This computes historical ENU offsets and applies edits deterministically.

Does rundale-geo-tool support fictional location coordinate realignment?

Fictional location coordinate realignment is supported by assigning the fictional geo_kind type. Fictional locations follow nearby anchor coordinates coherently, ensuring they propagate correctly via relative_to offsets when anchor pins are updated.