todd ellis<p><a href="https://eldritch.cafe/tags/RStats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RStats</span></a> <a href="https://eldritch.cafe/tags/PostgreSQL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PostgreSQL</span></a> <a href="https://eldritch.cafe/tags/PostGIS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PostGIS</span></a> question!</p><p>Is there a sensible -- no, *ideal* -- way to store spatiotemporal raster/NetCDFs in a PostgreSQL database? Ideally one which can still be easily queried in R. </p><p>My default approach of just converting them into dataframes and pushing everything to a database a) seems very inefficient, and b) *definitely* takes up more space than we have available in the database.</p><p>I think we could technically ask for more space, and insert indices to make using that data faster, but...seems like the wrong direction and not worth the effort.</p>