Found a better example, which wraps everything up and works great:

http://code.google.com/apis/maps/articles/geospatial.html


On Apr 2, 1:17 pm, Danny Tuppeny <[email protected]> wrote:
> Hi all,
>
> I posted this on StackOverflow, but then thought that maybe it's
> better to post here...
>
> http://stackoverflow.com/questions/2566563/app-engine-precomputing-bo...
>
> I'm trying to implement proximity-searching (eg. find all items within
> 10-15 miles), but I'm struggling to understand this sample:
>
> http://code.google.com/appengine/articles/geosearch.html
>
> I don't understand how using "slices" differs from increase the
> resolution, or why there are multiple configs and not just one.
>
> Rather than blindly changing numbers until it looks correct, I'd like
> to understand how to decide on the best config. Eg.
>
> - Why should I use 5 configs and not 1?
> - Why should I increase slices and not resolution?
>
> Any help would be appreciated :-)

-- 
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.

Reply via email to