gazetteer-testing

Audit genealogy place resolution against a SQLite database and bucket outlier mismatches.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/jonaseck2/slaktforskning --skill gazetteer-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gazetteer-testing
Source: https://github.com/jonaseck2/slaktforskning/tree/main/.claude/skills/gazetteer-testing
Command: npx skills add https://github.com/jonaseck2/slaktforskning --skill gazetteer-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It helps you audit and debug incorrect place resolution by identifying places that resolve to the wrong country, state, or sub-region when mapping genealogy locations.

Core Features & Use Cases

  • Outlier detection for place resolution: Finds systemic and one-off mismatches in resolved paths and match quality, including unresolved and ambiguous cases.
  • Audits what the user actually sees: Loads enabled gazetteers from the target database configuration so the test reflects the current UI behavior.
  • Actionable diagnostics for map pins: Buckets failures (e.g., wrong country, state mismatch, ambiguous matches) so you can trace likely root causes such as normalization, aliases, and tiebreaker logic.

Quick Start

Run the gazetteer testing script against your local database to identify and bucket outlier place resolutions for the region or filter you care about.

Frequently Asked Questions about gazetteer-testing

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

FAQPage Schema
How do I audit genealogy place resolution to find wrong country or state mismatches?

You can debug incorrect map pins by running resolver lookups against an SQLite database to identify outlier mismatches. The tool buckets failures like wrong country, state mismatch, and ambiguous matches to help trace root causes such as normalization or tiebreaker logic.

Why does my gazetteer place resolution fail for specific place strings?

Place resolution fails due to systemic or one-off mismatches in resolved paths and match quality. Common causes include normalization errors, alias conflicts, and tiebreaker logic issues, which are detected by bucketing unresolved and ambiguous results.

How do I validate a newly built gazetteer against existing place data?

Validate a newly built gazetteer by loading the enabled set from db_settings.gazetteer_config and iterating over a SQL-filtered place subset. Use resolvePlace() to bucket results by match quality and identify unresolved entries.

Can I test place resolution against the exact gazetteers enabled in my database?

Yes, place resolution testing loads enabled gazetteers directly from the target database configuration, ensuring the test reflects the current UI behavior and resolver logic that users actually see.

What is the best way to debug ambiguous matches when resolving genealogy locations?

Debug ambiguous matches by running resolver lookups against an SQLite database and bucketing results by resolution path quality. This isolates ambiguous cases from wrong country and state mismatch outliers for targeted investigation.

Do I need an SQLite database to run gazetteer outlier audits for map pins?

Yes, an SQLite database is required to run gazetteer outlier audits. The tool queries the database to load enabled gazetteer configurations and iterates over SQL-filtered place subsets to detect incorrect map pins.