[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgis-devel
Subject:    Re: [postgis-devel] Window-based Clustering
From:       Paul Ramsey <pramsey () cleverelephant ! ca>
Date:       2023-02-24 19:09:43
Message-ID: DD24DD7E-C325-4224-8FBD-586AC73B970F () cleverelephant ! ca
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


The strategy thing starts to get messy because each strategy has its own \
parameterization. Some need a tolerance, some need a K, some need a minpoints, etc). \
In some ways just having a lot of function sigs is cleaner. Each gets its own docs \
page, can completely explain its parameters, and have relevant examples and results.

P

> On Feb 24, 2023, at 10:53 AM, Darafei Komяpa Praliaskouski <me@komzpa.net> wrote:
> 
> Yay!
> 
> The "Win" part is not very pretty though. Do you think we can get it into maybe \
> something like ST_Cluster(geom, \
> strategy:='intersecting/within/dbscan/kmeans/xmeans/...')? I believe set of other \
> configuration options is not too wide between the methods.  
> пт, 24 лют 2023, 22:41 карыстальнік Paul Ramsey \
> <pramsey@cleverelephant.ca <mailto:pramsey@cleverelephant.ca>> напісаў: \
> Martin and I have repeatedly said "it would be nice if all the clustering \
> functionality was available as windowing functions", and here I have finally gone \
> and added that in. This adds ST_ClusterIntersectingWin and ST_ClusterWithinWin, as \
> windowing analogues to  ST_ClusterIntersecting and ST_ClusterWithin 
> https://github.com/postgis/postgis/pull/721 \
> <https://github.com/postgis/postgis/pull/721> 
> Unfortunately for backwards compatibility we can't (I think) just yank and replace \
> the existing functions in favour of the windowing ones, even though I think most \
> people will vastly prefer windowing as an approach to cluster functionality. 
> P
> _______________________________________________
> postgis-devel mailing list
> postgis-devel@lists.osgeo.org <mailto:postgis-devel@lists.osgeo.org>
> https://lists.osgeo.org/mailman/listinfo/postgis-devel \
> <https://lists.osgeo.org/mailman/listinfo/postgis-devel> \
> _______________________________________________ postgis-devel mailing list
> postgis-devel@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel


[Attachment #5 (unknown)]

<html><head><meta http-equiv="Content-Type" content="text/html; \
charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; \
line-break: after-white-space;" class="">The strategy thing starts to get messy \
because each strategy has its own parameterization. Some need a tolerance, some need \
a K, some need a minpoints, etc). In some ways just having a lot of function sigs is \
cleaner. Each gets its own docs page, can completely explain its parameters, and have \
relevant examples and results.<div class=""><br class=""></div><div class="">P<br \
class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 24, \
2023, at 10:53 AM, Darafei Komяpa Praliaskouski &lt;<a href="mailto:me@komzpa.net" \
class="">me@komzpa.net</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div \
class=""><div dir="auto" class="">Yay!<div dir="auto" class=""><br \
class=""></div><div dir="auto" class="">The "Win" part is not very pretty though. Do \
you think we can get it into maybe something like ST_Cluster(geom, \
strategy:='intersecting/within/dbscan/kmeans/xmeans/...')? I believe set of other \
configuration options is not too wide between the methods.&nbsp;</div></div><br \
class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">пт, 24 лют \
2023, 22:41 карыстальнік Paul Ramsey &lt;<a \
href="mailto:pramsey@cleverelephant.ca" class="">pramsey@cleverelephant.ca</a>&gt; \
напісаў:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div \
style="word-wrap:break-word;line-break:after-white-space" class=""><div \
class="">Martin and I have repeatedly said "it would be nice if all the clustering \
functionality was available as windowing functions", and here I have finally gone and \
added that in. This adds ST_ClusterIntersectingWin and ST_ClusterWithinWin, as \
windowing analogues to &nbsp;ST_ClusterIntersecting and ST_ClusterWithin</div><div \
class=""><br class=""></div><a href="https://github.com/postgis/postgis/pull/721" \
target="_blank" rel="noreferrer" \
class="">https://github.com/postgis/postgis/pull/721</a><div class=""><br \
class=""></div><div class="">Unfortunately for backwards compatibility we can't (I \
think) just yank and replace the existing functions in favour of the windowing ones, \
even though I think most people will vastly prefer windowing as an approach to \
cluster functionality.</div><div class=""><br class=""></div><div \
class="">P</div></div>_______________________________________________<br class=""> \
postgis-devel mailing list<br class=""> <a \
href="mailto:postgis-devel@lists.osgeo.org" target="_blank" rel="noreferrer" \
class="">postgis-devel@lists.osgeo.org</a><br class=""> <a \
href="https://lists.osgeo.org/mailman/listinfo/postgis-devel" rel="noreferrer \
noreferrer" target="_blank" \
class="">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a><br class=""> \
</blockquote></div> _______________________________________________<br \
class="">postgis-devel mailing list<br class=""><a \
href="mailto:postgis-devel@lists.osgeo.org" \
class="">postgis-devel@lists.osgeo.org</a><br \
class="">https://lists.osgeo.org/mailman/listinfo/postgis-devel<br \
class=""></div></blockquote></div><br class=""></div></body></html>



_______________________________________________
postgis-devel mailing list
postgis-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-devel


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic