Comments on: Django Geolocation http://www.givp.org/blog/2009/10/31/django-geolocation/ ::::..::..:::::::...:::::....::......:::::::::....::::......:::::::::::::::: Sat, 14 Aug 2010 13:09:14 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Giv http://www.givp.org/blog/2009/10/31/django-geolocation/#comment-3 Giv Sat, 31 Oct 2009 17:04:34 +0000 http://www.givp.org/blog/?p=87#comment-3 hi Bryan. Good point but then if the address is updated it will still show the old lat/long. The idea was to do a lookup for new entries AND updates. But checking self.id is a really elegant solution for inserts. hi Bryan. Good point but then if the address is updated it will still show the old lat/long. The idea was to do a lookup for new entries AND updates.

But checking self.id is a really elegant solution for inserts.

]]> By: Bryan http://www.givp.org/blog/2009/10/31/django-geolocation/#comment-2 Bryan Sat, 31 Oct 2009 16:58:58 +0000 http://www.givp.org/blog/?p=87#comment-2 To avoid going to Google every time you update the entity, you can check the self.id attribute. if (not self.id): # get geo lat/long from google -Bryan To avoid going to Google every time you update the entity, you can check the self.id attribute.

if (not self.id):
# get geo lat/long from google

-Bryan

]]>