Coordinate Lookup

Geocode place names and addresses to GPS coordinates via OpenStreetMap Nominatim.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/oskar-dragon/claude-code --skill coordinate-lookup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Coordinate Lookup
Source: https://github.com/oskar-dragon/claude-code/tree/main/plugins/obsidian-location-notes/skills/coordinate-lookup
Command: npx skills add https://github.com/oskar-dragon/claude-code --skill coordinate-lookup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, and includes scripts (resource) components.

What problem does it solve?

This skill helps convert place names, addresses, and informal location descriptions into accurate GPS coordinates and resolves ambiguous or multiple search results so you can populate location fields reliably.

Core Features & Use Cases

  • Nominatim-based geocoding strategies: exact name, name plus region, structured address queries, and alternative spellings to improve match quality.
  • Result evaluation and selection using type relevance, importance score, display_name verification, and bounding box specificity.
  • Practical use cases: finding coordinates for landmarks, geocoding businesses with city/country context, validating coordinates for notes, and graceful fallback when lookups fail.
  • Operational guidance: enforce a 1 request/second rate limit, include a descriptive User-Agent header, and cache results to reduce repeated queries.

Quick Start

Use the skill to find the latitude and longitude for Eiffel Tower and return the best match with its display_name and bounding box.

Frequently Asked Questions about Coordinate Lookup

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

FAQPage Schema
How do I find GPS coordinates for an address or landmark using OpenStreetMap Nominatim?

OpenStreetMap Nominatim geocoding converts place names, addresses, and informal location descriptions into accurate GPS coordinates. It returns latitude, longitude, display_name, bounding box, type, and importance score for each matched location.

What is the best way to resolve ambiguous or multiple results when geocoding addresses?

Resolving ambiguous geocoding results involves evaluating type relevance, importance score, display_name verification, and bounding box specificity. Structured address queries and adding region context help narrow down multiple matches to find the most accurate coordinates.

Do I need curl and jq to look up coordinates with OpenStreetMap Nominatim?

Yes, curl and jq are required dependencies for coordinate lookup. Curl handles HTTP requests to the Nominatim API, while jq parses the JSON responses to extract latitude, longitude, display_name, and bounding box data.

Why does my OpenStreetMap Nominatim geocoding request fail or get blocked?

OpenStreetMap Nominatim enforces a strict 1 request per second rate limit and requires a descriptive User-Agent header. Exceeding this limit or missing the header causes request failures, so caching results helps reduce repeated queries.

Can I perform reverse lookups to find place names from GPS coordinates?

Reverse lookups are supported alongside forward geocoding. You can resolve GPS coordinates back to display names, types, and bounding boxes using the same OpenStreetMap Nominatim service, respecting the 1 request per second rate limit.

How do I geocode a business name when the query returns no exact match?

When exact name geocoding fails, alternative strategies include adding city or country context, trying alternative spellings, and using structured address queries. Graceful fallback handles failed lookups by refining search terms to improve match quality.