Tuesday, January 31, 2012

Re: Dynamic runtime modeling: which is the best choice?

On Tue, 31 Jan 2012 17:02:43 +0100, Alessandro Candini <candini@meeo.it>

>Unfortunately I deal with very different shapefiles and I create models
>on the fly with ogrinspect tool.
>I cannot know the shapefile structure, before user upload: for this
>reason a table per shape is IMHO mandatory (as well as a clearer approach).

This sounds more like a need for shapefile translators (codecs, if
you will)... On input you'd convert the contents into a common database
format; reverse the process on output.

IOWs, my view is that you should be storing the "shape" and not the
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/

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 django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

No comments:

Post a Comment