Hi devs,
I've changed my Proj to ver. 8 (current master). Surprisingly, I'm not
able to compile Postgis anymore. I'm doing something wrong, but I can't
get it.
Compiling Proj:
cd ~/dev/PROJ
git pull
./autogen.sh
./configure
make -j8
sudo make install
sudo ldconfig
Compiling Postgis:
cd ~/dev/cp
It should be deterministic for most real data if the inputs are ordered
consistently, using the OVER() clause as you suggest. It's possible that
there may be a contrived situation involving duplicates in the input where
a result would be different (as GEOS STRtree is using std::sort instead of
std:
Hi Darafei,
Thank you for your answer!
Il giorno ven 22 gen 2021 alle ore 16:26 Darafei "Komяpa" Praliaskouski <
m...@komzpa.net> ha scritto:
> Hello,
>
> Cluster functions don't have cross-PostGIS-version stability guarantee.
> For many production applications that is equal to being non-determi
Hello,
Cluster functions don't have cross-PostGIS-version stability guarantee. For
many production applications that is equal to being non-deterministic.
While debugging KMeans I believe I've seen blinking tests on different
compiler flags as some optimizations may mean your distance computation
Hello,
I have a question about how the function ST_ClusterDBSCAN is implemented in
PostGIS: basically, the question is if I'm able to pass the same window of
geometries in input to the function, would it return the same clusters?
I tried to find an answer by myself having a look to the code: see
