On Apr 23, 9:23 am, Justin Bronn <[EMAIL PROTECTED]> wrote:
> > A PointField from that same model containing lat/long pairs obtained
> > from the Google geocoder.
Quick follow-up in case anyone else has a similar problem. The Google
geocoder annoyingly returns latitude and longitude as y/x instea
> > (1) What geographic fields are in your model, what type are they
> > (e.g., PointField, etc.), and their SRID.
>
> A plain PointField, e.g.: ``location = PointField()``. I
> believeGeoDjangodefaults to WGS84 for the SRID.
>
> > (2) The geometry type of the parameter you're passing to `distan
On Apr 22, 11:54 am, Justin Bronn <[EMAIL PROTECTED]> wrote:
> (1) What geographic fields are in your model, what type are they
> (e.g., PointField, etc.), and their SRID.
A plain PointField, e.g.: ``location = PointField()``. I believe
GeoDjango defaults to WGS84 for the SRID.
> (2) The geometr
> I'm calculating the distance between two plain PointFields in the GIS
> branch using the distance GeoQuerySet method [1] and I'm coming up
> with some confusing results.
>
I require more information before I can answer your inquiry:
(1) What geographic fields are in your model, what type are t
I'm calculating the distance between two plain PointFields in the GIS
branch using the distance GeoQuerySet method [1] and I'm coming up
with some confusing results.
The distance between nearby things is often about right, maybe off by
a mile or two. But the distance between farther locations is
5 matches
Mail list logo
