Clicking on a cluster marker does not always show co-located records

[leehart]

Sometimes works OK with some locations.

Ag1000G_Selection
Map Composer > {Markers: Samples}
Click on a few of the cluster bubbles, see that the table that opens in the popup is (sometimes) empty.

[leehart]

The query to fetch the co-located records depends on matching the latitude and longitude values exactly, but I suspect there might be some troublesome rounding or floating point data types...

For example, the API query:

{"whcClass":"compound","isCompound":true,"isRoot":true,"Components":[{"whcClass":"comparefixed","isCompound":false,"ColName":"Latitude","CompValue":11.890999794006346,"Tpe":"="},{"whcClass":"comparefixed","isCompound":false,"ColName":"Longitude","CompValue":-15.581999778747546,"Tpe":"="}],"Tpe":"AND"}

...will sometimes successfully fetch rows that include....

Latitude: 11.890999794006348
Longitude: -15.581999778747559

Notice there are discrepancies between the query criteria and the returned values.

[leehart]

The import logs show that Ag1000G's samples Longitude and Latitude (among others) are stored using the "real" data type, i.e. 32-bit floating point.

I think JavaScript stores all its numbers as 64-bit floats (IEEE-754).

I wonder if using FLOAT(24) or DOUBLE instead of REAL would solve this.

[leehart]

I was barking up the wrong tree! This bug is actually caused by the positions of cluster markers changing due to force layout, and consequently their latitudes and longitudes no longer match database records.
If there is a precision discrepancy, it doesn't actually cause a query mismatch.
A fix is in the pipe...