Project

General

Profile

Bug #8500

Geohash not calculated properly

Added by Dave Vieglais over 3 years ago.

Status:
New
Priority:
High
Assignee:
Category:
d1_indexer
Target version:
-
Start date:
2018-03-14
Due date:
% Done:

0%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

Description

The metadata with pid = {39A912EE-E2DC-4F50-A3DE-C0EF04BC1E88} has bounding coords correctly indexed:

    <float name="eastBoundCoord">166.657</float>
    <float name="westBoundCoord">-178.378</float>
    <float name="southBoundCoord">-14.5596</float>
    <float name="northBoundCoord">28.4536</float>

but the computed geohash is wrong:

    <arr name="geohash_9">
      <str>ec5zd8st0</str>
    </arr>
    <arr name="geohash_1">
      <str>e</str>
    </arr>
    <arr name="geohash_2">
      <str>ec</str>
    </arr>
    <arr name="geohash_3">
      <str>ec5</str>
    </arr>
    <arr name="geohash_4">
      <str>ec5z</str>
    </arr>
    <arr name="geohash_5">
      <str>ec5zd</str>
    </arr>
    <arr name="geohash_6">
      <str>ec5zd8</str>
    </arr>
    <arr name="geohash_7">
      <str>ec5zd8s</str>
    </arr>
    <arr name="geohash_8">
      <str>ec5zd8st</str>
    </arr>

Investigate if this is a systemic issue or peculiar to certain types of metadata or representation of coordinates within the metadata.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)