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 in the future we will be able to do spatial indexing with GeoPt. I'll be honest though, the primary reason I use GeoPt is because it's more convenient to pass around one object than two floats. Jeff On Tue, Oct 4, 2011 at 7:30 AM, Eliot Stock <1...@eliotstock.com> wrote: > 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 on the UI (lat and long) but one GeoPt > field on the entity. > Cheers, > Eliot > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine-java/-/c8oRwyDMIIgJ. > To post to this group, send email to google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
