| Name | Date | Size | #Lines | LOC | ||
|---|---|---|---|---|---|---|
| .. | 24-Mar-2022 | - | ||||
| README.md | H A D | 24-Mar-2022 | 631 | 10 | 6 | |
| geo.go | H A D | 24-Mar-2022 | 5.8 KiB | 211 | 150 | |
| geo_dist.go | H A D | 24-Mar-2022 | 3.2 KiB | 99 | 61 | |
| geohash.go | H A D | 24-Mar-2022 | 2.6 KiB | 112 | 79 | |
| parse.go | H A D | 24-Mar-2022 | 4.7 KiB | 182 | 124 | |
| sloppy.go | H A D | 24-Mar-2022 | 7.3 KiB | 213 | 161 |
README.md
1# geo support in bleve 2 3First, all of this geo code is a Go adaptation of the [Lucene 5.3.2 sandbox geo support](https://lucene.apache.org/core/5_3_2/sandbox/org/apache/lucene/util/package-summary.html). 4 5## Notes 6 7- All of the APIs will use float64 for lon/lat values. 8- When describing a point in function arguments or return values, we always use the order lon, lat. 9- 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. 10