Just to throw this out there, we use UK postal data for locations, 9m records and do location lookups/searches by grouping on the first part of the post code.
Works really well, but apologies for going even more off-topic :) -----Original Message----- From: Jaeger, Jay - DOT <jay.jae...@dot.wi.gov> Reply-to: solr-user@lucene.apache.org To: solr-user@lucene.apache.org <solr-user@lucene.apache.org> Subject: RE: what is the recommended way to store locations? Date: Thu, 6 Oct 2011 16:13:06 -0500 We do much the same (along with name, address, postal code, etc.). However, we use AND when we search: the more data someone can provide, the fewer and more applicable their search results. JRJ -----Original Message----- From: Jason Toy [mailto:jason...@gmail.com] Sent: Thursday, October 06, 2011 10:28 AM To: solr-user@lucene.apache.org Subject: what is the recommended way to store locations? In our current system ,we have 3 fields for location, city, state, and country. People in our system search for one of those 3 strings. So a user can search for "San Francisco" or "California". In solr I store those 3 fields as strings and when a search happens I search with an OR statement across those 3 fields. Is there a more efficient way to store this data storage wise and/or speed wise? We don't currently plan to use any spacial features like "3 miles near SF".
