[Xapian-tickets] [Xapian] #481: Merge geospatial branch

[Xapian]

#481: Merge geospatial branch
-------------------------+--------------------------------------------------
 Reporter:  richard      |       Owner:  richard  
     Type:  enhancement  |      Status:  new      
 Priority:  normal       |   Milestone:  1.2.1    
Component:  Library API  |     Version:  SVN trunk
 Severity:  normal       |    Keywords:           
Blockedby:               |    Platform:  All      
 Blocking:               |  
-------------------------+--------------------------------------------------

Old description:

> We've had a few requests for the features in the geospatial branch, so
> I've put together a clean patch against trunk of what I think are the
> stable and reasonably "uncontroversial" parts of the geospatial branch.
> This patch omits several things from the geospatial branch:
>
>  - The LatLongDistanceMatchDecider, since this is superceded by
> functionality in the LatLongDistancePostingSource, and we're moving
> towards deprecating MatchDeciders.
>
>  - The parser for latitude-longitude coordinates.  This is quite handy to
> allow lots of arbitrary formats for coordinates to be parsed into numeric
> values, but is a bit complex, and is a second lemon parser to be
> maintained, so I'd rather consider merging it at a later date.  Without
> the parser, coordinates have to be supplied as a pair of doubles, rather
> than having the option of providing them as strings.
>
>  - The half-completed HTM based generation of "acceleration" terms.
>
> I've tidied up the documentation and tests, and fixed a few small issues
> in the patch, so I think this is ready to be reviewed and considered for
> merging to trunk.  I'd be happy if it went in for 1.2.1, or at least got
> considered for it, so marking that as the milestone for now.
>
> The patch doesn't include the

New description:

 We've had a few requests for the features in the geospatial branch, so
 I've put together a clean patch against trunk of what I think are the
 stable and reasonably "uncontroversial" parts of the geospatial branch.
 This patch omits several things from the geospatial branch:

  - The LatLongDistanceMatchDecider, since this is superceded by
 functionality in the LatLongDistancePostingSource, and we're moving
 towards deprecating MatchDeciders.

  - The parser for latitude-longitude coordinates.  This is quite handy to
 allow lots of arbitrary formats for coordinates to be parsed into numeric
 values, but is a bit complex, and is a second lemon parser to be
 maintained, so I'd rather consider merging it at a later date.  Without
 the parser, coordinates have to be supplied as a pair of doubles, rather
 than having the option of providing them as strings.

  - The half-completed HTM based generation of "acceleration" terms.

 I've tidied up the documentation and tests, and fixed a few small issues
 in the patch, so I think this is ready to be reviewed and considered for
 merging to trunk.  I'd be happy if it went in for 1.2.1, or at least got
 considered for it, so marking that as the milestone for now.

--

Comment(by richard):

 (Removed accidental start of sentence at the end of the description.)

-- 
Ticket URL: <http://trac.xapian.org/ticket/481#comment:1>
Xapian <http://xapian.org/>
Xapian