This repository has been archived by the owner on Jun 21, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
Provide GeoNames city db in API #1
Comments
How about having this in |
Coaster contains code patterns, not data. Baseframe has some data such as the country list, but that data doesn't quite belong there either. We don't have a sensible place to store frequently reused data. We need:
The geonames db shouldn't be in code at all because it changes often. It comes under use case 2, a shared webservice, and hence hascore. |
Makes sense. |
Will this architecture affect mobile user experience ? |
It shouldn't be any different from the web experience. |
Implemented in bc6736e. |
jace
added a commit
that referenced
this issue
May 31, 2014
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Addresses are a common feature on HasGeek sites. They appear on hasjob (city only), geekup, hacknight and eventframe.
Filtering by city is a frequently requested feature. It's currently text-only because the city is stored as a string. We don't have a database of city names.
The GeoNames project provides free databases of cities around the world, with a consistent
place id
. This place id replaces City, State and Country in our fields.Hascore should provide a copy of the GeoNames city db that other projects can use to provide an autocomplete field for city name. From their documentation, the
cities1000.zip
dump seems appropriate for our needs.Instructions for importing to PostgreSQL.
The text was updated successfully, but these errors were encountered: