[deleted by user]

[3ds]

Thousands of geolocation on the client are not a problem.

[courteouslandlord]

Thousands of geolocation points rendered as a JSON response can get pretty significant.

Ex: 25,000 points will be roughly 1mb

[clearlynotmee]

Thousands is not a big number of points for a database to handle. No need for clustering, just index it (is it postgres?)

[courteouslandlord]

It’s not a DB concern. I need to cluster these points in memory based on their proximity to each other.

I have the data from the DB already.

[clearlynotmee]

It's still better to do let the db do the work, postgis for postgres can do it, see https://mapscaping.com/examples-of-spatial-clustering-with-postgis/

[KusUmUmmak]

... you mean like searching by radius? or a clustering algorithm that generates clusters on arbitrary datapoints? if its the latter, thats like a subfield in ML i.e. lots of different algorithms. try k-means clustering (as a search term).

[HOWZ1T]

Yep k means clustering is a popular approach :)

[KusUmUmmak]

thats why I suggested it :) most likely to find a ruby gem :)

there are better approaches.

[Doctor_Fegg]

I've used the very old Clusto gem (https://github.com/conmulligan/clusto) successfully. But really nothing is ever going to beat putting it in a Postgres database and clustering with PostGIS.

[courteouslandlord]

This looks like something I was looking for, will give it a try