On 2 March 2014 14:51, Sajjad Anwar <[email protected]> wrote: [...] > Hey, you don't necessarily need geodjango for these. You can write simple > spatial queries in PostGIS. > And they aren't very expensive. For example - > http://postgis.refractions.net/documentation/manual-2.0/ST_Within.html
GeoDjango queries translate to postgis if one is using a postgresql back-end, so I do not think that there is much overhead there. GeoDjango also does a lot more, including providing an abstraction layer for GIS, so that I would prefer using it to coding directly in postgis. The alternatives that I was thinking of were along the lines of spatial search with Solr/Lucene. These should be faster in principle, but we have not yet benchmarked them against postgis/GeoDjango. I would again argue that the first thing to do would be to have a stable system that provides an API layer over raw data pulled from various sources. GIS, and such queries would be meta-queries over such raw data, and should be done later, IMHO. Regards, Gora -- For more details about this list http://datameet.org/discussions/ --- You received this message because you are subscribed to the Google Groups "datameet" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
