On Tue, Apr 15, 2008 at 2:03 AM, Nathaniel Whiteinge <[EMAIL PROTECTED]> wrote: > > I'm really new to GeoDjango myself, and I agree that jumping right in > is a bit of a shock. Hopefully someone more knowledgeable will also > pipe-up, but I think I can start you off in the right direction. > > > On Apr 14, 9:43 pm, Alex Ezell <[EMAIL PROTECTED]> wrote: > > The system would then show them trips which have start, end, or both > > points in common with the locations they have entered in the search. > > "In common" being defined as within a radius of say 100 miles or so. > > If I understand your question correctly, you're only interested in the > start and end points and not the points along that line between the > two.
Exactly. > So define a regular model with a ``PointField`` [1] to hold the > lat/long for a location and make sure to use a ``GeoManager`` [2] for > that model. This is precisely the kind of pointer I was looking for. I've read the documentation about a PointField, but wasn't sure what the application was or how it works with the rest. Here's a silly question: I can mixin these GeoDjango field types with the base field types from Django, right? So, my model could have DateTimeField, PointField, CharField etc.? > I've been using GeoPy [3] to obtain lat/long from > addresses and zipcodes. Yep, already using GeoPy for geocoding. > If you need to do complex lookups that you > would normally use a ``Q`` object for, make sure to use a ``GeoQ`` > object [4] instead. This is in the docs, I'm sure, but is that GeoQ subclassed from the "normal" Q object so that it has all the properties of Q combined with GeoQ? > Once you've done that and have a few items in your database you can > query proximity pretty easily [5]. You can search for other points in > the database that are within a certain radius using a regular queryset > filter like > ``yourmodel.objects.filter(point__distance_lte=(STARTINGPOINT, > D(mi=100))``. If you want to return the distance between your starting > point and a bunch of objects use the ``distance()`` manager method > [6]. Also, I've found the built-in Distance measure functions [7] > really helpful for doing conversions. This looks like it will be really great. Just to run these filters instead of the horribly nasty SQL I have right now. It will also make it easy to add other columns from my > So I just mentioned three completely different parts of GeoDjango all > named "distance", hopefully I didn't confuse you even more! :-P Thanks so much for your response. This is great info for anyone starting out. I certainly appreciate the specific pointers into the docs as well. It really helps to have a subset of this stuff to start to get familiar with. Thanks again, Alex --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
