Hi - as a person investigating django for managing metadata that will
also have a spatial/gis component (lat/lon bounding boxes), would the
reccommended approach be to create a new field for use in my models?
Admittedly this would be specific to the postgres+postgis backend.
I'd be looking to imp
Hi Nick,
On 6/15/06, nick <[EMAIL PROTECTED]> wrote:
> Hi - as a person investigating django for managing metadata that will
> also have a spatial/gis component (lat/lon bounding boxes), would the
> reccommended approach be to create a new field for use in my models?
> Admittedly this would be sp
On 6/15/06, nick <[EMAIL PROTECTED]> wrote:
> Hi - as a person investigating django for managing metadata that will
> also have a spatial/gis component (lat/lon bounding boxes), would the
> reccommended approach be to create a new field for use in my models?
> Admittedly this would be specific to
Hi thanks for the replies - I'm surprised this is the only way to do
it as using the model api would seem neater. Have you encountered many
problems separating out the geom fields like this (eg - not being
searchable in admin / whatever)?
Yes I'd be interested in an example of how custom sql is
4 matches
Mail list logo