We're in Alpha, heading to Alpha 2. Our requirements are simple: radius searching, and distance from center. Solr Spatial works and is current. GeoSpatial is almost there, but we're going to wait until it's released to spend time with it. We have other tasks to work on and don't want to be part of the debugging process of any project right now.
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: Erick Erickson <erickerick...@gmail.com> To: solr-user@lucene.apache.org Sent: Sun, December 12, 2010 11:18:03 AM Subject: Re: SOLR geospatial By and large, spatial solr is being replaced by geospatial, see: http://wiki.apache.org/solr/SpatialSearch. I don't think the old spatial contrib is still included in the trunk or 3.x code bases, but I could be wrong.... That said, I don't know whether what you want is on the roadmap there either. Here's a place to start if you want to see the JIRA discussions: https://issues.apache.org/jira/browse/SOLR-1568 Best Erick On Sun, Dec 12, 2010 at 11:23 AM, Adam Estrada <estrada.a...@gmail.com>wrote: > I am particularly interested in storing and querying polygons. That sort of > thing looks like its on their roadmap so does anyone know what the status > is > on that? Also, integration with JTS would make this a core component of any > GIS. Again, anyone know what the status is on that? > > *What’s on the roadmap of future features?* > > Here are some of the features and henhancements we're planning for SSP: > > - > > Performance improvements for larger data sets > - > > Fixing of known bugs > - > > Distance facets: Allowing Solr users to be able to filter their results > based on the calculated distances. > - > > Search with regular polygons, and groups of shapes > - > > Integration with JTS > - > > Highly optimized distance calculation algorithms > - > > Ranking results by distance > - > > 3D dimension search > > > Adam > > On Sun, Dec 12, 2010 at 12:01 AM, Markus Jelsma > <markus.jel...@openindex.io>wrote: > > > That smells like: http://www.jteam.nl/news/spatialsolr.html > > > > > 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 > > >
