Thinking about adding to Q3e #557
ghost
started this conversation in
Ideas / Features
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Maybe I've finally found the right place for this. I was looking at:
http://postgis.net/workshops/postgis-intro/indexing.html
The problem I'm trying to solve: lvlworld.com has 3,000 BSP format files. I want to analyze every single one spatially,
then generalize the shape of the level, and compress all the necessary information into a 128x128 PNG image.
I don't even know where to start it is so much data and I can barely understand the 3D math behind it. But I had this idea,
if I could port part of this Vis system https://github.com/ec-/Quake3e/blob/master/code/qcommon/cm_trace.c#L154
to work on the GPU, then I could easily iterate on analyzing the data to create the image features I need.
I am well on my way to creating the feature maps. But each one takes about 10 seconds to generate. If I could somehow

combine PostGres with idtech3 clip map, I could generate feature maps much faster or use the usual database features
to organize the results in one place.
EDIT: I am looking at lwgeom_rtree.c from https://postgis.net/source/ But I don't understand if that has any connection to cuda_* from here.
Will pg-strom benefit postgis queries, or are the implementations completely disconnected?
All reactions