> How is "96.8 > 100" ever going to be true? ;p I believe that was from testing... don't worry this is still in 3 dimensional space. :)
> But anyway as pointed out you cant use inequality comparisons on more > than one property, you can do bboxes in this way. > > The solution is you need to encode both properties (lat/long) into one > property. For lat/long this is possible as you pretty much search > rectangles, it wouldnt work for arbitary pairs of properties. > > A common solution floated about on these forums is to use geohashes - > a search of 'geohash' should find them - there are even some working > implementations. I have a very rudimentory version I created in a > branch of geodatastore [1] but have never got round to merging into > the main project[2], but there are better implementations available. > > If geohashs are too coarse for you, then you will need to implement a > quadtree index, see [3] for an example. > > [1]http://code.google.com/p/geodatastore/ > [2]http://groups.google.com/group/google-appengine/browse_thread/thread/... > 4108ec9656602cf9 > > [3]http://labs.metacarta.com/blog/27.entry/geographic-queries-on-google-... I'll take a look at these indepth. I did see them mentioned however I was also wondering how to achieve this with other arbitrary values such as volume, weight or financial data. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
