Thanks for the quick response! Would that require inserting duplicates of all records, with the only difference being the lat/lng? Feels odd doubling my data set but I am new to Sphinx and unfamiliar with the implications.
On Aug 12, 4:37 am, Pat Allan <[email protected]> wrote: > Sphinx only comprehends a single lat/lng value for a document/record - so, > you'll need a record for each point you want to match on. You could then have > a path_id for each point, and group by point_id - thus ensuring only one > record per point. > > -- > Pat > > On 12/08/2011, at 3:09 AM, zackham wrote: > > > > > > > > > We are implementing a search of paths where direction of the path is > > not relevant. The paths can be pretty long (hundreds of miles or > > more) so when we search for a path proximate to a particular location, > > we need to look at the start and end points of the paths and only use > > the more proximate of the two points for sorting/ranking. Any ideas > > how this can be accomplished? > > > -- > > You received this message because you are subscribed to the Google Groups > > "Thinking Sphinx" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/thinking-sphinx?hl=en. -- You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/thinking-sphinx?hl=en.
