Re: Is GeoDjango Too Much For This?

I have two quick comments, check out geopy: http://code.google.com/p/geopy/ and this website http://www.movable-type.co.uk/scripts/latlong-db.html Geopy can give you lat/lng for a given address and that other website has formulas for using lat/lng to calculate a bounding box/circle. It may be

Re: Is GeoDjango Too Much For This?

On Mon, Feb 27, 2012 at 11:42 PM, DF wrote: > I'm on a Mac. The Django GeoDjango installation instructions are > somewhat obtuse and there aren't alternative sites I've found with > more straightforward instructions. It's lame that these are confusing > but, well, they

Re: Is GeoDjango Too Much For This?

Ethan: What a generous answer. Thank you so much. Here are my responses with a few other questions: > What is your operating system?  On Ubuntu I've found all the installation > to be very easy. I'm on a Mac. The Django GeoDjango installation instructions are somewhat obtuse and there aren't

Re: Is GeoDjango Too Much For This?

On Sat, Feb 25, 2012 at 7:50 PM, DF wrote: > GeoDjango though, to be honest, sounds frightening and extremely > advanced. I've been reviewing the installation requirements and, at > least according to how these were written, is intense and ripe for > many errors. What

Re: Is GeoDjango Too Much For This?

On Sat, Feb 25, 2012 at 7:50 PM, DF wrote: > Finally, > I want to provide users the ability to search for nearby posts or > within a certain boundary (from the documentation I've read, this is > what GeoDjango apparently excels at). that's the point. it seems easy, until

Re: Is GeoDjango Too Much For This?

Thanks for all the feedback. It is tremendously insightful. Here are my qualms: I'm a Django rookie, with basic Python knowledge. I'm using Django to work on my master's project, which is a specific web application that utilizes some form of geolocation, the latter of which is a mystery. I

Re: Is GeoDjango Too Much For This?

Whoops, quick correction: On Sat, Feb 25, 2012 at 5:03 PM, Ethan Jucovy wrote: > * You'll want to add a line ``objects = GeoManager`` on each model that > you will want to perform geospatial queries against. > That should be ``objects = GeoManager()`` (imported from

Re: Is GeoDjango Too Much For This?

Others have answered your other questions well, so just addressing this one: On Thu, Feb 23, 2012 at 8:13 PM, DF wrote: > Essentially, I'm looking to see what benefits GeoDjango would give > this project over using just the Google Maps API. If I've already > started a

Re: Is GeoDjango Too Much For This?

My english is not that great, but I'll try anyway. > I'm currently building my first Django-based app, which is proceeding > fairly well, thus far. One of the goals is to allow users to post > information (text, pics, video) and for the app to be able to > automatically detect the location where

Re: Is GeoDjango Too Much For This?

On 02/23/2012 09:54 PM, kenneth gonsalves wrote: On Thu, 2012-02-23 at 17:13 -0800, DF wrote: I've been reading a bit about GeoDjango and it sounds intriguing. A colleague, though, suggested everything that can be done using GeoDjango is equally efficient utilizing the Google Maps API with

Re: Is GeoDjango Too Much For This?

On Thu, 2012-02-23 at 17:13 -0800, DF wrote: > I've been reading a bit about GeoDjango and it sounds intriguing. A > colleague, though, suggested everything that can be done using > GeoDjango is equally efficient utilizing the Google Maps API with > JavaScript or JQuery to obtain the proper

Is GeoDjango Too Much For This?

I'm currently building my first Django-based app, which is proceeding fairly well, thus far. One of the goals is to allow users to post information (text, pics, video) and for the app to be able to automatically detect the location where they posted this information. That data would then ideally