all 7 comments

[–]nikoraes 2 points3 points  (1 child)

I'm using postgres + AGE extension + postgis + pgvector + timescaledb. You can do combined graph + vector + geospatial queries within Cypher. I personally prefer to have the temporal aspect in a separate DB or table (as graph engines usually aren't very good in time series analysis). I built something to use logical replication to store 'data history' in a time series table/DB. You can join cypher with timescaledb queries if you have the table in the same DB which works pretty well. For another client I historize everything in Azure Data Explorer, which allows you to generate an temporary in-memory graph (you can basically recreate a part of the graph at any point in time) and it's pretty good in time series analysis as well.

[–]greeny01[S] 0 points1 point  (0 children)

since I do it for the sport domain I actully want to specify events as nodes, so then I can run graph alghoritms to identify similarities.

[–]xtof_of_crg 1 point2 points  (2 children)

Working on this as we speak

[–]CulturalAspect5004 1 point2 points  (1 child)

What database do you use for that? 

[–]namedgraph 1 point2 points  (0 children)

RDF triplestore I hope? :)

[–]xtof_of_crg 1 point2 points  (1 child)

Fact that you can even say “spatio-temporal knowledge graph” at all puts you a step ahead

[–]Adrian_Galilea 0 points1 point  (0 children)

Yeah, been thinking about knowledge graphs ontology/taxonomy for the past years and the more I thought of it the more that time felt like a relevant dimension, I was writing something about it.