Someone can do there own own GeoPoint Indexing using a hash for the
geopoint. I've used the java lib below and it works good.
http://code.google.com/p/geomodel/ - python lib
http://code.google.com/p/javageomodel/ - java lib
http://code.google.com/apis/maps/articles/geospatial.html - another
You can actually store a coordinate accurate to about 1 meter in a single
long value (32 bits each axis). This can be an important saving if you are
indexing a lot of locations. Think of the long value as pointing to a block
of earth at any degree of accuracy you want. You can then query for
Hi there,
What's the advantage, if any of using GeoPt (
http://code.google.com/appengine/docs/java/datastore/entities.html#Properties_and_Value_Types)
over using two float fields?
I've found the disadvantage is that Spring form beans are difficult to work
with when you have two hidden fields
I'm using GeoPt 'cause it might have improvements in the future, like nearby
search.
I'm not sure about Spring form beans. I would recommend VRaptor with Pico
and Objectify for better startup time.
On Tue, Oct 4, 2011 at 11:30 AM, Eliot Stock 1...@eliotstock.com wrote:
Hi there,
What's the
I don't recomend both VRaptor and Objectify, for business/enterprise
projects. And the advantage is that it facilitates for you , for example,
use libraries like GeoModel.
2011/10/4 Bruno Fuster brunofus...@gmail.com
I'm using GeoPt 'cause it might have improvements in the future, like
nearby
It really isn't a big deal. Store two floats if you want. The
reasons I use GeoPt a lot:
* GeoPt shows up nicely in the datastore viewer
* You can store arrays of GeoPt
* The storage cost should be slightly less than two floats because
there is metadata only for one field.
* Maybe some day
AFAIK, there aren't any plans to do Geospatial indexing via GeoPt anytime in
the near future. That being said, if we were to support this feature, it
would make sense for us to start there or at least provide an API supporting
GeoPt. Even if we didn't, you could just call getLatitude() and
