<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Spatial Search and Plotting Using Geohashes — v2.1.0-beta</title>
<link rel="stylesheet" href="../_static/dataone.css" type="text/css" />
<link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: '../',
VERSION: '2.1.0-beta',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true,
SOURCELINK_SUFFIX: '.txt'
};
</script>
<script type="text/javascript" src="../_static/mathjax_pre.js"></script>
<script type="text/javascript" src="../_static/jquery.js"></script>
<script type="text/javascript" src="../_static/underscore.js"></script>
<script type="text/javascript" src="../_static/doctools.js"></script>
<script type="text/javascript" src="//cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-MML-AM_CHTML"></script>
<script type="text/javascript" src="../_static/sidebar.js"></script>
<link rel="author" title="About these documents" href="../about.html" />
<link rel="index" title="Index" href="../genindex.html" />
<link rel="search" title="Search" href="../search.html" />
<link rel="next" title="Node Identity and Registration" href="NodeIdentity.html" />
<link rel="prev" title="Very Large Data Packages" href="VeryLargeDataPackage.html" />
<link media="only screen and (max-device-width: 480px)" href="../_static/small_dataone.css" type= "text/css" rel="stylesheet" />
</head>
<body role="document">
<div class="version_notice">
<p>
<span class='bold'>Warning:</span> These documents are under active
development and subject to change (version 2.1.0-beta).<br />
The latest release documents are at:
<a href="https://purl.dataone.org/architecture">https://purl.dataone.org/architecture</a>
</p>
</div>
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="../genindex.html" title="General Index"
accesskey="I">index</a></li>
<li class="right" >
<a href="../py-modindex.html" title="Python Module Index"
>modules</a> |</li>
<li class="right" >
<a href="NodeIdentity.html" title="Node Identity and Registration"
accesskey="N">next</a> |</li>
<li class="right" >
<a href="VeryLargeDataPackage.html" title="Very Large Data Packages"
accesskey="P">previous</a> |</li>
<li class="nav-item nav-item-0"><a href="../index.html"></a> »</li>
<li class="nav-item nav-item-1"><a href="index.html" accesskey="U"><no title></a> »</li>
</ul>
</div>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body">
<div class="section" id="spatial-search-and-plotting-using-geohashes">
<h1>Spatial Search and Plotting Using Geohashes<a class="headerlink" href="#spatial-search-and-plotting-using-geohashes" title="Permalink to this headline">¶</a></h1>
<div class="section" id="introduction">
<h2>Introduction<a class="headerlink" href="#introduction" title="Permalink to this headline">¶</a></h2>
<p>A geohash is an encoded character string that is computed from geographic
coordinates. For example the approximate latitude and longitude of The National
Center For Ecological Analysis and Synthesis is 34.419279, -119.698472 from
which the geohash of <em>9q4gu1y4z</em> can be derived. The geohash algorithm is
bidirectional, so geographic coordinates can be encoded into geohashes and
geohashes can be decoded to obtain coordinates.</p>
<p>Geohashes have the property that characters can be incrementally removed from
the right side of the geohash to represent a geographic location less
precisely. A geohash is an approximation of a point, where each length of the
geohash corresponds to a rectangle (a geohash tile) that is an approximation of
the original encoded geographic coordinate.</p>
<p>This feature of geohashes can be useful for searching and plotting at different
resolutions.</p>
<p>Table 1 shows the relationship between geohash length and the size of the
rectangle represented by that geohash at the equator.</p>
<table border="1" class="docutils" id="id1">
<caption><span class="caption-text"><strong>Table 1</strong> Geohash Tile Sizes</span><a class="headerlink" href="#id1" title="Permalink to this table">¶</a></caption>
<colgroup>
<col width="25%" />
<col width="75%" />
</colgroup>
<thead valign="bottom">
<tr class="row-odd"><th class="head">Length</th>
<th class="head">Tile Size</th>
</tr>
</thead>
<tbody valign="top">
<tr class="row-even"><td>1</td>
<td>5,009.4km x 4,992.6km</td>
</tr>
<tr class="row-odd"><td>2</td>
<td>1,252.3km x 624.1km</td>
</tr>
<tr class="row-even"><td>3</td>
<td>156.5km x 156km</td>
</tr>
<tr class="row-odd"><td>4</td>
<td>39.1km x 19.5km</td>
</tr>
<tr class="row-even"><td>5</td>
<td>4.9km x 4.9km</td>
</tr>
<tr class="row-odd"><td>6</td>
<td>1.2km x 609.4m</td>
</tr>
<tr class="row-even"><td>7</td>
<td>152.9m x 152.4m</td>
</tr>
<tr class="row-odd"><td>8</td>
<td>38.2m x 19m</td>
</tr>
<tr class="row-even"><td>9</td>
<td>4.8m x 4.8m</td>
</tr>
<tr class="row-odd"><td>10</td>
<td>1.2m x 59.5cm</td>
</tr>
<tr class="row-even"><td>11</td>
<td>14.9cm x 14.9cm</td>
</tr>
<tr class="row-odd"><td>12</td>
<td>3.7cm x 1.9cm</td>
</tr>
</tbody>
</table>
<p>Table 2 shows the relationship between a geohash and the resulting latitude and
longitude decoded from the different length geohashes. As characters are
removed from the original geohash ‘9q4gu1y4z’ the bounding rectangle and the
accuracy of the decoded geohash becomes less precise. The decoded geohash
corresponds to the centroid of the bounding rectangle.</p>
<table border="1" class="docutils" id="id2">
<caption><span class="caption-text"><strong>Table 2.</strong> Geohash length vs Accuracy</span><a class="headerlink" href="#id2" title="Permalink to this table">¶</a></caption>
<colgroup>
<col width="12%" />
<col width="33%" />
<col width="55%" />
</colgroup>
<thead valign="bottom">
<tr class="row-odd"><th class="head">Geohash</th>
<th class="head">Tile Center lat, long</th>
<th class="head">Tile minlat, minlong, maxlat, maxLong</th>
</tr>
</thead>
<tbody valign="top">
<tr class="row-even"><td>9</td>
<td>22.5, -112.5</td>
<td>0, -135, 45, -90</td>
</tr>
<tr class="row-odd"><td>9q</td>
<td>36.5625, -118.125</td>
<td>33.75, -123.75, 39.375, -112.5</td>
</tr>
<tr class="row-even"><td>9q4</td>
<td>34.45312, -120.23437</td>
<td>33.75, -120.9375, 35.15625, -119.53125</td>
</tr>
<tr class="row-odd"><td>9q4g</td>
<td>34.36523, -119.70703</td>
<td>34.27734, -119.88281, 34.45312, -119.53125</td>
</tr>
<tr class="row-even"><td>9q4gu</td>
<td>34.43115, -119.68505</td>
<td>34.40917, -119.70703, 34.45312, -119.66308</td>
</tr>
<tr class="row-odd"><td>9q4gu1</td>
<td>34.41741, -119.70153</td>
<td>34.41467, -119.70703, 34.42016, -119.69604</td>
</tr>
<tr class="row-even"><td>9q4gu1y</td>
<td>34.41947, -119.69810</td>
<td>34.41879, -119.69879, 34.42016, -119.69741</td>
</tr>
<tr class="row-odd"><td>9q4gu1y4</td>
<td>34.41922, -119.69861</td>
<td>34.41913, -119.69879, 34.41930, -119.69844</td>
</tr>
<tr class="row-even"><td>9q4gu1y4z</td>
<td>34.41928, -119.69846</td>
<td>34.41926, -119.69849, 34.41930, -119.69844</td>
</tr>
</tbody>
</table>
<p>Geohashes comprise a nested spatial indexing system with each level of
geohashes tile containing 32 tiles of the next smaller tile size. The level one
geohashes (length=1) divide the earth into 32 tiles. Each of these 32 tiles is
then subdivided into 32 level 2 tiles and so on.</p>
<p>Geohashes also have the property that all smaller tiles within the enclosing
geohash tile begin with the same leading characters, therefor for the level 1
tile ‘9’, all level 2 sub-tiles begin with ‘9’: ‘90’, ‘91’, ‘93’,..., ‘9z’.</p>
<p>For example the level 3 geohash tile that encloses much of Santa Barbara County
is ‘9q4’. Also contained in this bounding rectangle is the city center of Santa
Maria (geohash 9q4qg7j2hmdz), Goleta (geohash 9q4gckb5jxu7) and Santa Barbara
(geohash 9q4gu4n7y5b7) all of which begin with the characters ‘9q4’ and fall
within the ‘9q4’ geohash rectangle. This property is very useful for searching
and sorting datastores that contain geohashes.</p>
</div>
<div class="section" id="dataone-search-index-and-geohashes">
<h2>DataONE Search Index and Geohashes<a class="headerlink" href="#dataone-search-index-and-geohashes" title="Permalink to this headline">¶</a></h2>
<p>The DataONE search index contains geohashes that have been computed for each
geographic coverage associated with a PID containing geographic coverage
information, which currently includes metadata objects in EML and FGDC formats.
The search index is described here: <a class="reference external" href="SearchMetadata.html">SearchMetadata.html</a>. Each PID in the
search index has a geohash computed at nine different resolutions,
corresponding to the geohash lengths shown <em>Table 3</em>. The field names are
appended with the geohash length, so for example the field <em>geohash_1</em> has a
string length of one and corresponds to the largest tile size in <em>Table 1</em>.
Geohashes are added to the search index at different lengths to allow for
searching and plotting at different resolutions.</p>
<p>For EML documents, the geohashes are computed by determining the centroid of
the XML elements <em>northBoundingCoordinate, southBoundingCoordinatem,
eastBoundingCoordinate, westBoundingCoordinate</em> which are child element of
<em>//dataset/coverage/geographicCoverage/boundingCoordinates</em>. Because any number
of coverages may be defined with the EML format, the geohashes for these
coverages are stored in a Solr multi-valued field. EML allows for the four
bounding coordinates to specify a single coordinate (i.e.
westBoudingCoordinate=eastBoundingCoordinate and
northBoundingCoordinate=southBoundingCoordinate), in which case this location
is used to compute a geohash.</p>
<p>For FGDC documents, the XML elements <em>northBoundingCoordinate,
southBoundingCoordinate, eastBoundingCoordinate, westBoundingCoordinate</em>
(parent element //metadata/idinfo/spdom/bounding) are used to compute the
geohash using the same method as for EML.</p>
</div>
<div class="section" id="using-geohashes-for-plotting">
<h2>Using Geohashes for plotting<a class="headerlink" href="#using-geohashes-for-plotting" title="Permalink to this headline">¶</a></h2>
<p>Geohashes can be used to efficiently plot the location of the geographic
coverages. The following examples show different search and plotting strategies
that are possible using geohashes. Several public domain Javascript libraries
are available for assisting in developing web clients that could use geohashes.
For example, the Javascript library <em>node-geohash</em> (available at
<a class="reference external" href="https://github.com/sunng87/node-geohash">https://github.com/sunng87/node-geohash</a>) contains routines to encode and decode
geohashs in addition to other spatial operators using geohashes. This library
will be used for the examples that follow.</p>
<p><strong>Example: Retrieve geohashes as facets in Solr search</strong></p>
<p>In this example the Solr search index is queried for a particular field of
interest, with the associated geohash counts being returned as a field facet.
Used in this way, the facet field of geohashes becomes a spatial bin, with the
size of the geographic area and the spatial resolution of the binning selected
by the geohash level.</p>
<p>For example, if we are interested in plotting the location of PIDs that have
some associated with kelp, we could query the search index with the Solr query:</p>
<blockquote>
<div><a class="reference external" href="https://cn.dataone.org/cn/v1/query/solr?q=kelp&facet=true&facet.field=geohash_5&facet.mincount=1&rows=0">https://cn.dataone.org/cn/v1/query/solr?q=kelp&facet=true&facet.field=geohash_5&facet.mincount=1&rows=0</a></div></blockquote>
<p>The portion of the response that we are interested in are the facet counts:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="o"><</span><span class="n">lst</span> <span class="n">name</span><span class="o">=</span><span class="s2">"facet_counts"</span><span class="o">></span>
<span class="o"><</span><span class="n">lst</span> <span class="n">name</span><span class="o">=</span><span class="s2">"facet_queries"</span><span class="o">/></span>
<span class="o"><</span><span class="n">lst</span> <span class="n">name</span><span class="o">=</span><span class="s2">"facet_fields"</span><span class="o">></span>
<span class="o"><</span><span class="n">lst</span> <span class="n">name</span><span class="o">=</span><span class="s2">"geohash_5"</span><span class="o">></span>
<span class="o"><</span><span class="nb">int</span> <span class="n">name</span><span class="o">=</span><span class="s2">"9q4qx"</span><span class="o">></span><span class="mi">5</span><span class="o"></</span><span class="nb">int</span><span class="o">></span>
<span class="o"><</span><span class="nb">int</span> <span class="n">name</span><span class="o">=</span><span class="s2">"9q4ce"</span><span class="o">></span><span class="mi">4</span><span class="o"></</span><span class="nb">int</span><span class="o">></span>
<span class="o"><</span><span class="nb">int</span> <span class="n">name</span><span class="o">=</span><span class="s2">"9q4cf"</span><span class="o">></span><span class="mi">4</span><span class="o"></</span><span class="nb">int</span><span class="o">></span>
<span class="o"><</span><span class="nb">int</span> <span class="n">name</span><span class="o">=</span><span class="s2">"9q4ey"</span><span class="o">></span><span class="mi">4</span><span class="o"></</span><span class="nb">int</span><span class="o">></span>
<span class="o"><</span><span class="nb">int</span> <span class="n">name</span><span class="o">=</span><span class="s2">"9q4ge"</span><span class="o">></span><span class="mi">4</span><span class="o"></</span><span class="nb">int</span><span class="o">></span>
<span class="o"><</span><span class="nb">int</span> <span class="n">name</span><span class="o">=</span><span class="s2">"9q4gx"</span><span class="o">></span><span class="mi">4</span><span class="o"></</span><span class="nb">int</span><span class="o">></span>
<span class="o"><</span><span class="nb">int</span> <span class="n">name</span><span class="o">=</span><span class="s2">"9q4kj"</span><span class="o">></span><span class="mi">4</span><span class="o"></</span><span class="nb">int</span><span class="o">></span>
<span class="o"><</span><span class="nb">int</span> <span class="n">name</span><span class="o">=</span><span class="s2">"9q4s4"</span><span class="o">></span><span class="mi">4</span><span class="o"></</span><span class="nb">int</span><span class="o">></span>
<span class="o"><</span><span class="nb">int</span> <span class="n">name</span><span class="o">=</span><span class="s2">"9q4ez"</span><span class="o">></span><span class="mi">3</span><span class="o"></</span><span class="nb">int</span><span class="o">></span>
<span class="o"><</span><span class="nb">int</span> <span class="n">name</span><span class="o">=</span><span class="s2">"9q4g8"</span><span class="o">></span><span class="mi">3</span><span class="o"></</span><span class="nb">int</span><span class="o">></span>
<span class="o"><</span><span class="nb">int</span> <span class="n">name</span><span class="o">=</span><span class="s2">"9q4gb"</span><span class="o">></span><span class="mi">1</span><span class="o"></</span><span class="nb">int</span><span class="o">></span>
<span class="o"></</span><span class="n">lst</span><span class="o">></span>
<span class="o"></</span><span class="n">lst</span><span class="o">></span>
<span class="o"><</span><span class="n">lst</span> <span class="n">name</span><span class="o">=</span><span class="s2">"facet_dates"</span><span class="o">/></span>
<span class="o"><</span><span class="n">lst</span> <span class="n">name</span><span class="o">=</span><span class="s2">"facet_ranges"</span><span class="o">/></span>
<span class="o"></</span><span class="n">lst</span><span class="o">></span>
</pre></div>
</div>
<p>To display these search results each geohash can be decoded to obtain the
latitude, longitude of the geohash. For example, we can obtain the coordinates
of the first geohash returned from the search as shown in the following code
fragment:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="o">//</span> <span class="n">Use</span> <span class="n">the</span> <span class="n">node</span><span class="o">-</span><span class="n">geohash</span> <span class="n">Javascript</span> <span class="n">library</span>
<span class="n">var</span> <span class="n">geohashLib</span><span class="o">=</span> <span class="n">require</span><span class="p">(</span><span class="s1">'ngeohash'</span><span class="p">);</span>
<span class="o">//</span> <span class="n">Return</span> <span class="p">[</span><span class="n">minlat</span><span class="p">,</span> <span class="n">minlon</span><span class="p">,</span> <span class="n">maxlat</span><span class="p">,</span> <span class="n">maxlon</span><span class="p">]</span> <span class="n">of</span> <span class="n">geohash</span> <span class="n">tile</span>
<span class="n">var</span> <span class="n">coords</span> <span class="o">=</span> <span class="n">geohashLib</span><span class="o">.</span><span class="n">decode</span><span class="p">(</span><span class="s2">"9q4qx"</span><span class="p">);</span>
</pre></div>
</div>
<p>The variable <em>coords</em> now contains the latitude, longitude (coords.latitude,
coords.logitude) of the decoded geohash, which is center point of the geohash
tile, in this case for level 5 geohash tiles. We could then place a marker with
counts at these coordinates to indicate how many hits occured in this geohash
tile.</p>
<p>Care must be taken in selecting the right geohash tile level for the Solr
query, with the consideration of smaller geohash tiles providing more accurate
spatial results, but returning a greater number of facet results as each
greater resolution tile covers a smaller geographic area.</p>
</div>
<div class="section" id="using-geohashes-for-searching">
<h2>Using Geohashes for searching<a class="headerlink" href="#using-geohashes-for-searching" title="Permalink to this headline">¶</a></h2>
<p>Geohashes in the search index are multi-valued, so that geohashes have been
computed for each geographic coverage for a PID. Since the geohashes are
indexed at different resolutions, you can search all coverages at different
spatial resolutions.</p>
<p><strong>Example: Search using a bounding box</strong></p>
<p>One appraach to using geohashes for search is to retrieve all PIDs with
geohashes that overlap a search box. First determine which geohashes overlap a
bounding rectangle, in this case the bounding rectangle that encompasses Santa
Cruz Island in the Santa Barbara Channel:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="o">//</span> <span class="n">Use</span> <span class="n">the</span> <span class="n">node</span><span class="o">-</span><span class="n">geohash</span> <span class="n">Javascript</span> <span class="n">library</span>
<span class="n">var</span> <span class="n">geohashLib</span><span class="o">=</span> <span class="n">require</span><span class="p">(</span><span class="s1">'ngeohash'</span><span class="p">);</span>
<span class="o">//</span> <span class="n">Search</span> <span class="k">for</span> <span class="nb">all</span> <span class="n">geohashes</span> <span class="n">within</span> <span class="n">a</span> <span class="n">geographic</span> <span class="n">bounding</span> <span class="n">box</span>
<span class="o">//</span> <span class="n">which</span> <span class="n">might</span> <span class="n">be</span> <span class="n">the</span> <span class="n">current</span> <span class="n">browser</span> <span class="n">viewport</span> <span class="ow">or</span> <span class="n">alternatively</span> <span class="n">a</span>
<span class="o">//</span> <span class="n">region</span> <span class="n">of</span> <span class="n">interest</span>
<span class="o">//</span> <span class="n">Santa</span> <span class="n">Cruz</span> <span class="n">Island</span> <span class="n">bounding</span> <span class="n">coordinates</span> <span class="p">(</span><span class="n">approximate</span><span class="p">)</span>
<span class="o">//</span> <span class="n">lower</span> <span class="n">left</span>
<span class="n">minlat</span> <span class="o">=</span> <span class="mf">33.959878</span><span class="p">;</span>
<span class="n">minlon</span> <span class="o">=</span> <span class="o">-</span><span class="mf">119.914398</span><span class="p">;</span>
<span class="o">//</span> <span class="n">upper</span> <span class="n">right</span>
<span class="n">maxlat</span> <span class="o">=</span> <span class="mf">34.075341</span><span class="p">;</span>
<span class="n">maxlon</span> <span class="o">=</span> <span class="o">-</span><span class="mf">119.520264</span><span class="p">;</span>
<span class="o">//</span> <span class="n">Find</span> <span class="nb">all</span> <span class="n">geohashes</span> <span class="n">that</span> <span class="n">overlap</span> <span class="n">the</span> <span class="n">specified</span> <span class="n">bounding</span> <span class="n">box</span><span class="o">.</span>
<span class="n">var</span> <span class="n">geohashes</span> <span class="o">=</span> <span class="n">geohashLib</span><span class="o">.</span><span class="n">bboxes</span> <span class="p">(</span><span class="n">minlat</span><span class="p">,</span> <span class="n">minlon</span><span class="p">,</span> <span class="n">maxlat</span><span class="p">,</span> <span class="n">maxlon</span><span class="p">,</span> <span class="n">precision</span><span class="o">=</span><span class="mi">4</span><span class="p">);</span>
</pre></div>
</div>
<p>The geohashes that overlap the search bounding box are returned. These
geohashes can then be used to find PIDs that have a coverage that is within
these geohash tiles:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span>https://cn.dataone.org/cn/v1/query/solr?q=*:*&q.op=OR&fq=geohash_4:(9q4c 9q49 9q51)&fl=id
</pre></div>
</div>
<p>This Solr filter query will find all entries for which one of the level 4
geohashes matches any of the specified geohashes. Because the geohash_* fields
are indexed as Solr multivalued fields, all coverages for a PID are compared to
see if they match.</p>
</div>
<div class="section" id="geohash-algorithm">
<h2>Geohash algorithm<a class="headerlink" href="#geohash-algorithm" title="Permalink to this headline">¶</a></h2>
<p>A description of the geohash algorith is outside the scope of this document,
but an excellent description of the can be found at
<a class="reference external" href="http://en.wikipedia.org/wiki/Geohash">http://en.wikipedia.org/wiki/Geohash</a>.</p>
<p>One caveat of the geohash algorith that may be of interest to end users
however, is that because of the tile ordering (“Z” ordering) where tile
geohashes are incremented in a “Z” pattern and not strictly by row, column, it
is not gauranteed that adjancent tiles have similar geohashes, for example, the
level 1 geohashes at the equator, starting from the International Date Line,
are named “8”, “9”, “d”, “e”, “s”, “t” and so on.</p>
</div>
</div>
</div>
</div>
</div>
<div class="sphinxsidebar" role="navigation" aria-label="main navigation">
<div class="sphinxsidebarwrapper">
<p class="logo"><a href="http://dataone.org">
<img class="logo" src="../_static/dataone_logo.png" alt="Logo"/>
</a></p>
<h3><a href="../index.html">Table Of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">Spatial Search and Plotting Using Geohashes</a><ul>
<li><a class="reference internal" href="#introduction">Introduction</a></li>
<li><a class="reference internal" href="#dataone-search-index-and-geohashes">DataONE Search Index and Geohashes</a></li>
<li><a class="reference internal" href="#using-geohashes-for-plotting">Using Geohashes for plotting</a></li>
<li><a class="reference internal" href="#using-geohashes-for-searching">Using Geohashes for searching</a></li>
<li><a class="reference internal" href="#geohash-algorithm">Geohash algorithm</a></li>
</ul>
</li>
</ul>
<h3>Related Topics</h3>
<ul>
<li><a href="../index.html">Documentation Overview</a><ul>
<li><a href="index.html"><no title></a><ul>
<li>Previous: <a href="VeryLargeDataPackage.html" title="previous chapter">Very Large Data Packages</a></li>
<li>Next: <a href="NodeIdentity.html" title="next chapter">Node Identity and Registration</a></li>
</ul></li>
</ul></li>
</ul>
<div id="searchbox" style="display: none" role="search">
<h3>Quick search</h3>
<form class="search" action="../search.html" method="get">
<div><input type="text" name="q" /></div>
<div><input type="submit" value="Go" /></div>
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="footer">
<div id="copyright">
© Copyright <a href="http://www.dataone.org">2009-2017, DataONE</a>.
[ <a href="../_sources/design/geohash.txt"
rel="nofollow">Page Source</a> |
<a href='https://redmine.dataone.org/projects/d1/repository/changes/documents/Projects/cicore/architecture/api-documentation/source/design/geohash.txt'
rel="nofollow">Revision History</a> ]
</div>
<div id="acknowledgement">
<p>This material is based upon work supported by the National Science Foundation
under Grant Numbers <a href="http://www.nsf.gov/awardsearch/showAward?AWD_ID=0830944">083094</a> and <a href="http://www.nsf.gov/awardsearch/showAward?AWD_ID=1430508">1430508</a>.</p>
<p>Any opinions, findings, and conclusions or recommendations expressed in this
material are those of the author(s) and do not necessarily reflect the views
of the National Science Foundation.</p>
</div>
</div>
<!--
<hr />
<div id="HCB_comment_box"><a href="http://www.htmlcommentbox.com">HTML Comment Box</a> is loading comments...</div>
<link rel="stylesheet" type="text/css" href="_static/skin.css" />
<script type="text/javascript" language="javascript" id="hcb">
/*<! -*/
(function()
{s=document.createElement("script");
s.setAttribute("type","text/javascript");
s.setAttribute("src", "http://www.htmlcommentbox.com/jread?page="+escape((typeof hcb_user !== "undefined" && hcb_user.PAGE)||(""+window.location)).replace("+","%2B")+"&mod=%241%24wq1rdBcg%24Gg8J5iYSHJWwAJtlYu/yU."+"&opts=21407&num=10");
if (typeof s!="undefined") document.getElementsByTagName("head")[0].appendChild(s);})();
/* ->*/
</script>
-->
</body>
</html>