elasticsearch geohashes produce duplicate

[keithfraley]

Hello, I am almost certain this isnt an ngeohash issue, but I am hoping there is might be a way to leverage ngeohash to mitigate the problem.

I am using a 3rd party mapping js api to display elasticsearch aggregations. When a user selects an area of interest to display (by panning or zooming) the actual request that is sent thru the api to elasticsearch is broken into 8 separate bounding boxes, each with a distinct set of non overlapping coordinates. However, when I bring each each request back I am getting overlapping geohashes at the edges, see attached. The darker squares are actually two, overlapping records from separate requests. I am trying to show heatmaps and this really makes elasticsearch unusable because its not actually conveying the whole truth.

Is there anyway to make sure that the geohashes dont overlap with seperate requests?