This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-09-12
Channels
- # ai (1)
- # announcements (7)
- # babashka (32)
- # beginners (23)
- # biff (9)
- # calva (1)
- # cljs-dev (13)
- # clojure (32)
- # clojure-belgium (1)
- # clojure-chicago (15)
- # clojure-europe (24)
- # clojure-india (3)
- # clojure-nl (3)
- # clojure-norway (55)
- # clojure-uk (4)
- # clojurebridge (1)
- # clojurescript (5)
- # core-async (17)
- # data-science (9)
- # datomic (29)
- # events (3)
- # fulcro (16)
- # graalvm-mobile (4)
- # helix (15)
- # hyperfiddle (74)
- # introduce-yourself (1)
- # jobs (4)
- # kaocha (12)
- # leiningen (27)
- # lsp (16)
- # shadow-cljs (6)
- # spacemacs (20)
- # sql (27)
- # squint (7)
- # tools-deps (29)
- # vim (2)
- # xtdb (10)
I am wondering about custom indexing in tech.ml.dataset
. The repo history has a https://github.com/techascent/tech.ml.dataset/pull/214 that references the ability to add custom indices (including my use case, spatial indices) to a column, but as far as I can tell the functions implementing those capabilities were https://github.com/techascent/tech.ml.dataset/commit/bd47ec2f10e1f92e45a48d0e93b5d21c6d6f63bb when the project migrated over to HAMF. Is there a new way of using custom indices for a column?
I think the approach I described https://github.com/techascent/tech.ml.dataset/pull/214#issuecomment-804790512 is still valid. You can create an external index and use it to select data. For spacial data STRtree
structure may be helpful.
Yes, it seems like the approach you describe in this https://gist.github.com/genmeblog/18d6ed84224cbbef656adac4d85cc7ec can still work – seems much better than what i was doing before, which was storing the index object itself as Column metadata.
I guess the fact that joins aren't there is a useful exercise for the reader (me) 🙂
For stuff like point-in-polygon joins between point and areal data, yeah
tomorrow ☝️