Documentation
GeoNames Global
GeoNames Global serves worldwide place names and location data from D1. Search defaults to India-first with strict geographic scopes and configurable fallback. Aliases come from allCountries.txt; country, administrative-area, and feature labels come from reference inputs. Integrating Workers call the service through a same-account Service Binding.
Guides
Section titled “Guides”- Getting startedInstall the local prerequisites and run the demo and docs.
- ArchitectureSee service ownership, data flow, and hierarchy joins.
- Data importLoad the supplied GeoNames data into local D1.
- SearchUnderstand matching, result ranking, and paging.
- API referenceBind and call get, getMany, search, and searchPage.
- BenchmarkingMeasure real MISS/HIT cohorts and interpret request timings.
- Wikidata mapping proposalStore only GeoNames ID to QID mappings; fetch metadata in the consuming API Worker.
Two parts, one local workflow
Section titled “Two parts, one local workflow”The interactive demo lets you search places, inspect their coordinates and population, and page through results. A separate Worker service owns the search and lookup contract; the demo calls it through an internal Service Binding rather than a public service endpoint.
Wrangler includes the existing remote D1, KV and Service Binding configuration; local commands use separate development state. Imports and deployments are user-authorized operations, not part of this documentation batch. Start with architecture and the RPC integration example; use data import for initial setup or reseeding.