• Introduction
  • Vision
  • Mission
• Guides & Tutorials
  • 1. Our Indexes
    • 1.1. Wikidata+GeoNames Index (Augmentation)
    • 1.2. WHG Publication Index (Searchable Publication)
    • 1.3. WHG Union Index (Final Integration & Clustering)
  • 2. Workbench
    • 2.1. Individual datasets
    • 2.2. Multiple datasets
    • 2.3. Thematic place collections
      • 2.3.1. Instructional exercise in a class setting, or workshop
      • 2.3.2. Authored publication
  • 3. Publishing Data
    • 3.1. Create and publish a Place Collection
    • 3.2. Create and publish a Dataset Collection
  • 4. Uploading Data
    • 4.1. Choosing an upload data format: LPF or LP-TSV?
    • 4.2. Preparing data for upload
      • 4.2.1. The simple case
      • 4.2.2. The not so simple case: extracting places
      • 4.2.3. Linked Places format (LPF), a GeoJSON extension
    • 4.3. Getting the LP-TSV columns right
      • 4.3.1. Coordinates: lon and lat
      • 4.3.2. Place types: types and aat_types
      • 4.3.3. Feature classes: fclasses
      • 4.3.4. Updating a dataset
  • 5. Reconciliation & Accessioning
    • 5.1. What does closeMatch mean?
  • 6. Reviewing accessioning results
  • 7. Collection Groups
    • 7.1. Create and manage a Collection Group for a class or workshop
• WHG Staff
  • 1. Gazetteer Configurator
    • 1.1. Where to find it
    • 1.2. What you’ll see
    • 1.3. Attribution, licence & rights
    • 1.4. Common tasks
      • 1.4.1. Adding a “core” gazetteer
      • 1.4.2. Hiding a gazetteer from the Regions panel
      • 1.4.3. Disabling Explore mode for a polygon-only gazetteer
    • 1.5. Re-ingestion
      • 1.5.1. Triggering a re-ingest
      • 1.5.2. Status lifecycle
      • 1.5.3. What “completed” actually means
      • 1.5.4. If a re-ingest gets stuck
    • 1.6. Permissions
  • 2. User API Profiles
    • 2.1. Where to find it
    • 2.2. What you’ll see
    • 2.3. Common tasks
      • 2.3.1. Bumping a researcher’s daily quota
      • 2.3.2. Resetting a user’s counter
      • 2.3.3. Investigating heavy usage
    • 2.4. Permissions
  • 3. Site smoke test
    • 3.1. What it checks
    • 3.2. Running it
    • 3.3. Dev shares the production Elasticsearch index
    • 3.4. Interpreting results
  • 4. Atlas (staff notes)
    • 4.1. What the Atlas is and who can see what
      • 4.1.1. Staff: granting a tester access
    • 4.2. How it fits together (Staff)
    • 4.3. Licensing behaviour
    • 4.4. Failure modes and what users see
    • 4.5. Testing (Staff)
    • 4.6. Beta testing process
    • 4.7. Known limitations
    • 4.8. Not yet documented
  • 5. Restarting the gateway
    • 5.1. What a restart does
    • 5.2. Check what is actually running
    • 5.3. If the pull fails
    • 5.4. Checking Atlas before and after a deploy
  • 6. Gateway performance and operations
    • 6.1. The shape of a reconcile request
    • 6.2. What changed, and what it bought
    • 6.3. Settings
    • 6.4. Reading the stage timing
    • 6.5. Deploying from the Pitt clone
    • 6.6. What the host looks like (read-only survey, 13 November 2026)
      • 6.6.1. Switching between the serving and rebuild heap
    • 6.7. Capacity is a resourcing decision
    • 6.8. Near-miss tuning and its evaluation set
• Technical
  • 1. Repositories
  • 2. APIs
    • 2.1. Entity API
      • 2.1.1. Entity Endpoints
      • 2.1.2. Place Identifiers and Source Namespaces
      • 2.1.3. Persistent Identifiers (w3id.org)
    • 2.2. Reconciliation Service API
      • 2.2.1. What This Service Is For
      • 2.2.2. Reconciliation Endpoints
      • 2.2.3. The Query Model
      • 2.2.4. Batching, Quotas and Retries
      • 2.2.5. Query Parameters
      • 2.2.6. FamilySearch Mode
      • 2.2.7. Source Namespaces
      • 2.2.8. Result Format
      • 2.2.9. Interpreting confidence
      • 2.2.10. Deciding Whether a Result Is Ambiguous
      • 2.2.11. Filter Behaviour and Common Pitfalls
      • 2.2.12. Geometry Recovery When the Top Hit Has No Centroid
      • 2.2.13. Data Extension Properties
      • 2.2.14. Using the WHG Reconciliation API in OpenRefine
    • 2.3. Genealogy Place Strings API
      • 2.3.1. Endpoints
      • 2.3.2. Request
      • 2.3.3. Parsing
      • 2.3.4. The relaxation ladder
      • 2.3.5. Response
      • 2.3.6. Good practice
    • 2.4. Source Terms and Attribution
      • 2.4.1. Where it appears
      • 2.4.2. Shape
      • 2.4.3. redistributable — which matches you will be able to fetch
      • 2.4.4. Mapping a result to its terms
      • 2.4.5. namespaces_searched
      • 2.4.6. The tri-state flags — null does not mean false
      • 2.4.7. The flags that carry obligations
      • 2.4.8. The WHG overlay
    • 2.5. API Tokens
      • 2.5.1. Using an API Token
      • 2.5.2. Suggest Endpoint Example
      • 2.5.3. Entity API Example
    • 2.6. Workbench Projects API
      • 2.6.1. Authentication
      • 2.6.2. Cross-origin use (CORS)
      • 2.6.3. Limits
      • 2.6.4. Projects
      • 2.6.5. Sharing
      • 2.6.6. Teams
      • 2.6.7. The plato doc_type
      • 2.6.8. Errors
      • 2.6.9. Example
  • 3. Issues
• Development Roadmap
  • 1. v4.0: Atlas, Collaborative Workbench, Phonetics
    • 1.1. The data model
      • 1.1.1. Draft User Guide
      • 1.1.2. Beta Testing Plan
      • 1.1.3. Data Model
      • Toponym Phonetics: Technical Design
      • 1.1.4. System Architecture
  • 2. v4.1: Open Educational Resources
    • 2.1. Vision
    • 2.2. Strategic Goals
    • 2.3. Technical Requirements
      • 2.3.1. OER Metadata Schema
      • 2.3.2. Data Model Extensions
      • 2.3.3. API Endpoints
      • 2.3.4. Frontend Components
      • 2.3.5. Integration Points
      • 2.3.6. Workflow for Creating OERs
      • 2.3.7. Technical Implementation Checklist
      • 2.3.8. Success Metrics
      • 2.3.9. Sustainability Considerations
      • 2.3.10. Documentation Needs
  • 3. Archive: the 2025 v4 Design
    • 3.1. User Guide (2025 design)
      • 3.1.1. Quick Start Guide
      • 3.1.2. Understanding WHG Concepts
      • 3.1.3. Place Record Anatomy
      • 3.1.4. Contributing Data Overview
      • 3.1.5. Reconciliation Overview
      • 3.1.6. Tutorial: Creating a Historical Route
      • 3.1.7. Frequently Asked Questions
      • 3.1.8. Glossary
      • 3.1.9. Getting Help
    • 3.2. Implementation in ArangoDB
      • 3.2.1. Overview
      • 3.2.2. Document Collections
      • 3.2.3. Indexing Strategy
      • 3.2.4. Query Patterns in AQL
      • 3.2.5. Handling Temporal Nulls and Geological Time
      • 3.2.6. ArangoDB Capabilities Assessment
      • 3.2.7. Summary
    • 3.3. Kubernetes Configuration
      • 3.3.1. Overview
      • 3.3.2. Setup
    • 3.4. SSH Key Setup
      • 3.4.1. 1. Generate an SSH Key
      • 3.4.2. 2. Copy the Public Key to the Remote Server
      • 3.4.3. 3. Log in to the Remote Server
      • 3.4.4. 4. Automatically Switch to the gazetteer Account
      • 3.4.5. 5. Check Kubernetes Nodes
      • 3.4.6. Secrets Management
    • 3.5. Deploying the Management Pod
      • 3.5.1. Accessing Kubernetes Dashboard and Services Locally
    • 3.6. Deploying Services
    • 3.7. Service Configuration
      • 3.7.1. Proposed Subdomain Mapping
• License
  • What this licence does not cover
  • Earlier terms