foster/forgejo
1
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-11-24 08:57:03 -05:00
Code Issues Wiki Activity
forgejo/vendor/github.com/blevesearch/bleve/geo
History
6543 fdf750e4d4
[Vendor] blevesearch v0.8.1 -> v1.0.7 (#11360) 
* Update blevesearch v0.8.1 -> v1.0.7

* make vendor

Co-authored-by: zeripath <art27@cantab.net>
2020-05-10 06:40:54 +01:00
..
geo.go [Vendor] blevesearch v0.8.1 -> v1.0.7 (#11360) 2020-05-10 06:40:54 +01:00
geo_dist.go Improve issue search (#2387) 2017-09-16 23:16:21 +03:00
geohash.go Upgrade blevesearch to v0.8.1 (#9177) 2019-11-27 11:23:33 +02:00
parse.go [Vendor] blevesearch v0.8.1 -> v1.0.7 (#11360) 2020-05-10 06:40:54 +01:00
README.md Use Go1.11 module (#5743) 2019-03-27 19:15:23 +08:00
sloppy.go Improve issue search (#2387) 2017-09-16 23:16:21 +03: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.