Ah, my mistake then. I will switch to using the geohash field. When doing my query I did run it against geohash but when I got Russia that was more incorrect than point so I stopped using it.
Is there a timeline by which you expect the dateline issue to be addressed? I don't believe that will be an issue for me since I don't believe we have any information which will be from that area of the world but I'll have to verify. On Fri, Jul 22, 2011 at 3:35 AM, David Smiley (@MITRE.org) <dsmi...@mitre.org> wrote: > Jamie, > You are using the field named "point" which is based on PointFieldType. > Keep in mind that just because this field type is named this way, does *not* > mean at all that other fields don't hold points, or that this one is > especially suited to it. Arguably this one is named poorly. This field > type is loosely based on Solr's LatLonType but it doesn't yet fully > implement capabilities like crossing the dateline and shapes other than a > bounding box. I've enhanced the code to log a warning if the query shape is > expanded to the bounding box. Any way, it's a currently a 2nd class citizen > in LSP. > I recommend you use the field named "geohash" which uses a field type name > starting with "Recursive...". Note that the same query you did with this > field returned the polygon of Russia. There is an outstanding box in which > we don't properly handle polygons crossing the dateline; other shapes are > fine. > > ~ David > > ----- > Author: https://www.packtpub.com/solr-1-4-enterprise-search-server/book > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Geospatial-queries-in-Solr-tp3183374p3190762.html > Sent from the Solr - User mailing list archive at Nabble.com. >
