I was looking at GeoModel, which has nice functionality for bounding- box geo queries: http://code.google.com/apis/maps/articles/geospatial.html http://code.google.com/p/geomodel/
Unfortunately, the demo application is quite slow. Queries often take 2-4 seconds to return ~10 results. http://geomodel-demo.appspot.com http://geomodel-demo.appspot.com/speedtest I also see an open bug filed against GeoModel that proximity queries are slow: http://code.google.com/p/geomodel/issues/detail?id=20 Any ideas why this is slow? Glancing at the source, I notice it uses "IN" queries (eg. location_geocells IN <list of cells>) -- perhaps this is less efficient than range queries? But still, 2-4 seconds seems excessive to return 10 results. Hopefully the "next gen queries" which will apparently support space- filling curves will provide better performance for queries like these? http://www.youtube.com/watch?v=ofhEyDBpngM Josh -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
