On 4/19/07, jbronn <[EMAIL PROTECTED]> wrote:
>
> The GIS branch (GeoDjango) is interested in type coercion.
> Specifically, PostGIS returns geometries as hex strings to the client
> -- it would be preferable to have this come into the model as either a
> different type of string like WKT ("POLYGON ( .. )"), KML
> ("<Polygon>...</Polygon>") or as a GEOSGeometry() object. For
> example, say we have a 'ZipCode' model with a PolygonField ('poly'):
Ok. That's the sort of use case I was looking for.
I haven't looked at the GIS branch, and my GIS knowledge from
university is getting _very_ rusty, so you'll need to help me out a
little.
How do you handle data input of GIS types? What format is used during
assignment?
Are you using to_python at all in the GIS branch?
To date, the database backend maintains the philosophy that whatever
you put in (as a python type) is what you get back. If you put a
boolean in, you get a boolean out; you put a DateTime in, you get a
DateTime out. Is this still appropriate in the GIS setting?
Is there a use case for being able to get back data of more than one
type, or is it possible to get a WKT or KML representation from a
GEOSGeometry object?
Yours,
Russ Magee %-)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
