+1 for geospatial features. Some ideas from three books:
Map Scripting 101, in http://www.amazon.com/gp/product/1593272715/ref=s9_simh_gw_p14_d5_g14_i6?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=center-7&pf_rd_r=023SASW38231TN3CV802&pf_rd_t=101&pf_rd_p=470938451&pf_rd_i=507846 It's about mapstraction (http://mapstraction.com/), the OpenSource javascript front end for using google, yahoo, and other map providers. Python Geospatial Development, in (http://www.amazon.com/Python- Geospatial-Development-Erik-Westra/dp/1849511543/ref=pd_sim_b5) and html5 geolocation features, as describe for example, in HTML5 Geolocation (http://www.amazon.com/HTML5-Geolocation-Anthony-Holdener- III/dp/1449304729/ref=sr_1_1?ie=UTF8&qid=1316597049&sr=8-1) On 20 sep, 18:27, Massimo Di Pierro <[email protected]> wrote: > I promised somebody geospatial features. That will probably come > before full text search but this is a good time to look into it. > Should we take an approach sqlite/mysql/postgresql only or outsource > it to Sphinx? > > On Sep 20, 9:00 am, Michele Comitini <[email protected]> > wrote: > > > > > > > > > +1 fulltext search > > > *Some* graph databases have already some good pythonic API. > > Do you think that DAL can be adapted to graphs also? Isn't the DAL > > too "relational oriented"? > > > mic > > > 2011/9/20 Vasile Ermicioi <[email protected]>: > > > > dal supporting graph databases and fulltext search
