On Oct 5, 9:48 pm, Josh Haberman <[email protected]> wrote: > I was looking at GeoModel, which has nice functionality for bounding- > box geo > queries:http://code.google.com/apis/maps/articles/geospatial.htmlhttp://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.comhttp://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
Why is it slow? I use it and yes it's slow since making several queries for one match. You could try do it with your own algorithm. I try match points inside a polygon for arbitrary geography matches. When slow we usually have 2 alternatives a) faster platform b) make fewer calls and fewer objects You may benchmark my code matching stuff in Sao Paulo by long / lat: http://www.montao.com.br/li?lat=-23.33&lon=-46.38 Sincerely, Niklas -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
