gibheer
/
bleve
0
0
Fork 0
Code
bleve/geo
History
Marty Schoch 8df8d4e797 fix geo point distance search 
there was a bug where if the circle described by the point
distance query crossed the poles, then we incorrectly built
a box around it.  this resulted in incorrect searh results.
 		2017-04-27 17:28:07 -04:00
..
README.md several more items on the geo checklist 2017-03-29 14:21:59 -04:00
geo.go fix geo point distance search 2017-04-27 17:28:07 -04:00
geo_dist.go add support for customizing unit used in distance sorting 2017-03-29 16:04:30 -04:00
geo_dist_test.go add support for customizing unit used in distance sorting 2017-03-29 16:04:30 -04:00
geo_test.go fix geo point distance search 2017-04-27 17:28:07 -04:00
parse.go geo review comments from sreekanth 2017-03-31 08:41:40 -04:00
parse_test.go several more items on the geo checklist 2017-03-29 14:21:59 -04:00
sloppy.go fix geo point distance search 2017-04-27 17:28:07 -04:00
sloppy_test.go several more items on the geo checklist 2017-03-29 14:21:59 -04:00

README.md

geo support in bleve

First, all of this geo code is a Go adaptation of the Lucene 5.3.2 sandbox geo support.

Notes

  • All of the APIs will use float64 for lon/lat values.
  • When describing a point in function arguments or return values, we always use the order lon, lat.
  • High level APIs will use TopLeft and BottomRight to describe bounding boxes. This may not map cleanly to min/max lon/lat when crossing the dateline. The lower level APIs will use min/max lon/lat and require the higher-level code to split boxes accordingly.