Mike,
Thank you for the answer.
I will think it over.
Antonio
2017-10-31 3:17 GMT+03:00 Mike Toews :
> On 31 October 2017 at 00:09, Antonio Rodriges wrote:
>> The size of the array and its dimensions are below
>>
>> dimensions:
>> lat = 94 ;
>> lon = 192 ;
>> time = 1460;
>
> With
On 31 October 2017 at 00:09, Antonio Rodriges wrote:
> The size of the array and its dimensions are below
>
> dimensions:
> lat = 94 ;
> lon = 192 ;
> time = 1460;
With PostGIS, you can get this as a multidimensional raster with 1460
bands, or 18048 multipart geometries with 1460 par
Have you cansidered treating your data as multiband raster?
You can use raster2pgsql and then do data processing with the rest of
raster functions (map algebra, etc.).
giovanni
___
postgis-users mailing list
postgis-users@lists.osgeo.org
https://lists.o
Paul,
I suppose POINTM is the solution to get the data somehow into PostGIS but I
will have a handful of options to process them and millions of rows with
points,
PostGIS has raster data type tailored to 2-d arrays (please, correct me if
I am wrong):
https://postgis.net/docs/RT_reference.html
http
As others have noted, a POINTM or MULTIPOINTM will serve to store your data
just fine, but what you plan to *do* with that data after will determine
whether a relational database is really the correct tool for you.
ATB,
P
On Mon, Oct 30, 2017 at 4:56 AM, Antonio Rodriges
wrote:
> I suppose it h
I suppose it has a bit different purpose (like an efficient handling of
sparsity which is not the case with dense climate data) and I hope there is
an easier solution (I just have 3 dimensions...)
Antonio
2017-10-30 14:52 GMT+03:00 Stephen V. Mather :
> Ya, I’m not sure point clouds are at all t
Ya, I’m not sure point clouds are at all the fix. They just address the
dimensionality question well, though not the gridded data requirement.
Cheers,
Best,
Steve
[http://sig.cmparks.net/cmp-ms-90x122.png]Stephen V. Mather
GIS Manager
(216) 635-3243 (Work)
(216) 339-6347 (Cell)
--sent from phon
Thank you for pointing to this tool.
However, I thought that since PostGIS uses GDAL it may be easier to import
such arrays, e.g. just split them onto individual 2-d grids (since PostGIS
mainly understands 2-d grids).
2017-10-30 14:34 GMT+03:00 Stephen V. Mather :
> I don’t know if it’s the idea
I don’t know if it’s the ideal tool for the job, as it’s more flexible than you
need, not being a regularized grid but a point cloud, but you might look to the
pgPointCloud extension: https://github.com/pgpointcloud/pointcloud
Cheers,
Best,
Steve
[http://sig.cmparks.net/cmp-ms-90x122.png]Steph
Hello,
Thank you for the reply, however my data is slightly different. Sorry
that I did not make it clearer at the very beginning.
Actually I would like to import a dense, 3-d array of wind speed (a
time series of grids, each grid point contains the wind speed value)
The array is stored as a Net
Hi Antonio,
2017-10-29 12:31 GMT+01:00 Antonio Rodriges :
> Hello,
>
> Whether PostGIS allow importing 3-d, 4-d, etc. arrays or only 2-d arrays?
>
> Specifically, I have a 3-d array with axes (time, lat, lon).
> Does this mean that I need to split it onto 2-d bands (lat, lon) and
> import the num
11 matches
Mail list logo
