Cities API

Hey PH! 👋 I spent way too much time building a geographic API, but here's why: Most geo APIs are rigid - they expect you to know exactly what you're looking for. "Cities only" or "Airports only." But real questions don't work like that. Sometimes you need "distance from a lake to an airport" or "mountains near this city" or "what's the closest capital to these coordinates?" So I built something more flexible. Everything - cities, mountains, lakes, airports, parks - lives in the same system. Same search, same filters, same distance calculations. You're not locked into predefined queries. Here's a real example: "Find the climate zone and sunrise time at the nearest city to the exact opposite point of Mount Everest on Earth." That actually works - find Everest by elevation, calculate its antipode (lands in the Pacific), reverse geocode to nearest city (some remote island in Chile), then get climate + sun times. Try doing that with a traditional cities-only API. The idea is it's agnostic. Whether you're building travel apps, logistics tools, mapping software, or something I haven't thought of - the data structure doesn't get in your way. Free tier on RapidAPI if you want to mess around with it. What would you build with flexible geographic data? Genuinely curious. Docs: https://hthought.github.io/citie...