fíam

• Release early, release often: django-geonames-0.2

  April 3, 2008 at 14:56:04 CEST

  I've made some important changes to django-geonames, fixing get_parent() and get_children(), which were failing on some corner cases. For example: if a third level administrative division wasn't inside a second level administrative division, get_parent() was returning the same object passed as self.

  I'm currently working on improving import time, as well as experimenting with compressed tables for faster retrieval. Expect another release by tomorrow.

  django-geonames-0.2.zip

  Tags:

  • django

  Related entries (automatically generated):

  • django-geonames 0.3: Incremental updates support

3 comments for "Release early, release often: django-geonames-0.2"

• #1 Comment by hans April 4, 2008 at 09:14:20 CEST ( Permalink )

  Great to see such serious contributions to geo-ing django. I was wondering, though - do you think that your solution could be modified to instead cache retrieved geoname entries from the web service, as I am reluctant to fill my database with the full geonames database? I guess I might need to start this from scratch?

• #2 Comment by fiam April 4, 2008 at 12:09:11 CEST ( Permalink )

  Hi hans,
  That was my first approach, but it was terribly slow. Whenever you got a Geonames.DoesNotExist exception, you had to connect to the webservice for checking if the geoname existed and, in affirmative case, download some data and process it. That wasn't suitable for ffloat.it (the project I've developed django-geonames for).
  On the other hand, Geonames webservice works fine most of the time, but still isn't reliable enough.

• #3 Comment by hans April 4, 2008 at 13:52:05 CEST ( Permalink )

  Ok, I see.
  I will have a look at the code to see if it gives me any ideas as to how such an approach would work.
  Thanks!