You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, thanks for your interest. The big problem is, that the code is very very bad...at time of release it was just a quick and dirty solution...and I hadn't the time to change this. I think the clusterer has to be rewritten entirely. Creating a good clusterer isn't an easy target and the current solution does only work for small datasets (~1000-5000 points). I've invented a better scaling python solution based on Scipy's KDTree. Unfortunately I don't have time to port this solution to qgis. How much experience you have in qgis development?
Sadly not much at all. Think this might be a bit ambitious for a first
project but the feature would definately be useful.
On Jan 19, 2016 4:01 AM, "Matthias Ludwig" [email protected] wrote:
Hi, thanks for your interest. The big problem is, that the code is very
very bad...at time of release it was just a quick and dirty solution...and
I hadn't the time to change this. I think the clusterer has to be rewritten
entirely. Creating a good clusterer isn't an easy target and the current
solution does only work for small datasets (~1000-5000 points). I've
invented a better scaling python solution based on Scipy's KDTree.
Unfortunately I don't have time to port this solution to qgis. How much
experience you have in qgis development?
—
Reply to this email directly or view it on GitHub #4 (comment)
.
How far away and how can I help?
The text was updated successfully, but these errors were encountered: