My partner is using a publicly available plugin for GeoSpatial. It is used both during indexing and during search. It forms some kind of gridding system and puts 10 fields per row related to that. Doing a Radius search (vs a bounding box search which is faster in almost all cases in all GeoSpatial query systems) seems pretty fast. GeoSpatial was our project's constraint. We've moved past that now.
Did I mention that it returns distance from the center of the radius based on units supplied in the query? I would tell you what the plugin is, but in our division of labor, I have kept that out of my short term memory. You can contact him at: Danilo Unite <danilo.un...@gmail.com>; Dennis Gearon Signature Warning ---------------- It is always a good idea to learn from your own mistakes. It is usually a better idea to learn from others’ mistakes, so you do not have to make them yourself. from 'http://blogs.techrepublic.com.com/security/?p=4501&tag=nl.e036' EARTH has a Right To Life, otherwise we all die. ----- Original Message ---- From: George Anthony <pa...@rogers.com> To: solr-user@lucene.apache.org Sent: Fri, December 10, 2010 9:23:18 AM Subject: SOLR geospatial In looking at some of the docs support for geospatial search. I see this functionality is mostly scheduled for upcoming release 4.0 (with some playing around with backported code). I note the support for the bounding box filter, but will "bounding box" be one of the supported *data* types for use with this filter? For example, if my lat/long data describes the "footprint" of a map, I'm curious if that type of coordinate data can be used by the bounding box filter (or in any other way for similar limiting/filtering capability). I see it can work with point type data but curious about functionality with bounding box type data (in contrast to simple point lat/long data). Thanks, George
