chapter38_part1:/320_Geohashes/40_Geohashes.asciidoc #305
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
javasgl
reviewed
Sep 19, 2016
| of the entrance to Buckingham Palace--latitude `51.501568` and longitude | ||
| `-0.141257`—would index all of the geohashes listed in the following table, | ||
| along with the approximate dimensions of each geohash cell: | ||
| http://en.wikipedia.org/wiki/Geohash[Geohashes] 是一种将经纬度坐标对（ `lat/lon` ）编码成字符串的方式。((("geohashes")))((("latitude/longitude pairs", "encoding lat/lon points as strings with geohashes")))((("strings", "geohash")))这么做的初衷只是为了让地理位置在url上呈现的形式更加友好，但现在geohashes已经变成一种在数据库中有效索引地理坐标点和地理形状的方式。 |
javasgl
reviewed
Sep 20, 2016
| @@ -47,6 +28,5 @@ along with the approximate dimensions of each geohash cell: | |||
| |gcpuuz94kkp5 |12 | ~ 3.7cm x 1.8cm | |||
| |============================================= | |||
|
|
|||
| The {ref}/query-dsl-geohash-cell-query.html[`geohash_cell` filter] can use | |||
| these geohash prefixes((("geohash_cell filter")))((("filters", "geohash_cell"))) to find locations near a specified `lat/lon` point. | |||
| {ref}/query-dsl-geohash-cell-query.html[`geohash单元` 过滤器] 可以使用这些 geohash 前缀((("geohash_cell filter")))((("filters", "geohash_cell")))来找出与指定坐标点（ `lat/lon` ）相邻的位置。 | |||
There was a problem hiding this comment.
本地预览时没有下面这段内容，应该这段的格式有问题导致asciidoc编译有问题，再检查下。
|
LGTM |
|
LGTM |
pengqiuyuan
reviewed
Oct 21, 2016
| of the entrance to Buckingham Palace--latitude `51.501568` and longitude | ||
| `-0.141257`—would index all of the geohashes listed in the following table, | ||
| along with the approximate dimensions of each geohash cell: | ||
| http://en.wikipedia.org/wiki/Geohash[Geohashes] 是一种将经纬度坐标（ `lat/lon` ）编码成字符串的方式。((("geohashes")))((("latitude/longitude pairs", "encoding lat/lon points as strings with geohashes")))((("strings", "geohash")))这么做的初衷只是为了让地理位置在url上呈现的形式更加友好，但现在geohashes已经变成一种在数据库中有效索引地理坐标点和地理形状的方式。 |
There was a problem hiding this comment.
中英文空格 “让地理位置在url上呈现的形式更加友好，但现在geohashes已经...”
|
|
||
| 换句话说， geohash 的长度越长，它的精度就越高。如果两个 geohashes 有一个共同的前缀— `gcpuuz`—就表示他们挨得很紧。共同的前缀越长，距离就越近。 | ||
|
|
||
| 这也意味着，两个刚好相邻的位置，可能会有完全不同的 geohash 。比如，伦敦 http://en.wikipedia.org/wiki/Millennium_Dome[Millenium Dome] 的geohash是 `u10hbp` ，因为它落在了 `u` 这个单元里，而紧挨着它东边的最大的单元是 `g` 。 |
There was a problem hiding this comment.
中英文空格 "的geohash是 u10hbp..."
|
|
||
| Geohashes 把整个世界分为 32 个单元的格子 —— 4 行 8 列 —— 每一个格子都用一个字母或者数字标识。比如 `g` 这个单元覆盖了半个格林兰，冰岛的全部和大不列颠的大部分。每一个单元还可以进一步被分解成新的 32 个单元，这些单元又可以继续被分解成 32 个更小的单元，不断重复下去。 `gc` 这个单元覆盖了爱尔兰和英格兰， `gcp` 覆盖了伦敦的大部分和部分南英格兰， `gcpuuz94k` 是白金汉宫的入口，精确到约 5 米。 | ||
|
|
||
| 换句话说， geohash 的长度越长，它的精度就越高。如果两个 geohashes 有一个共同的前缀— `gcpuuz`—就表示他们挨得很紧。共同的前缀越长，距离就越近。 |
added 2 commits
October 21, 2016 16:38
|
LGTM @medcl |
tangmisi
pushed a commit
to tangmisi/elasticsearch-definitive-guide
that referenced
this pull request
Oct 31, 2016
…n#305) * chapter38_part1:/320_Geohashes/40_Geohashes.asciidoc * 按review修改 * 按review修改 * 添加空格
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.