[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgis-users
Subject:    Re: [postgis-users] Handling N-d arrays in PostGIS
From:       Antonio Rodriges <antonio.rrz () gmail ! com>
Date:       2017-11-01 13:56:34
Message-ID: CAPrLoNc64EjCLuNvtCNzCPZL+_WxLJB-rhAvO+b-6Tm2N+B+TQ () mail ! gmail ! com
[Download RAW message or body]

Mike,

Thank you for the answer.
I will think it over.

Antonio

2017-10-31 3:17 GMT+03:00 Mike Toews <mwtoews@gmail.com>:
> On 31 October 2017 at 00:09, Antonio Rodriges <antonio.rrz@gmail.com> 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 parts, or 26 million
> single-part geometries. If you can't get raster2pgsql to recognize the
> .nc file, then try using gdal_translate to convert to a .tif file
> instead, and you should be able to load this into PostGIS as a raster.
>
> However, I'll suggest none of these as good options, as they will all
> have a much slower performance in an SQL environment compared to a
> native multidimensional environment (netCDF, HDF5, etc. and NCO,
> NumPy, etc.).
>
> It really depends on what you are doing with the data. If you are
> simply viewing it, then you can (e.g.) open the netCDF directly with
> QGIS (via GDAL), which should be very quick and easy to use. There are
> many tools that can efficiently process netCDF files which I'd expect
> to be much quicker.
> _______________________________________________
> postgis-users mailing list
> postgis-users@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
_______________________________________________
postgis-users mailing list
postgis-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-users
[prev in list] [next in list] [prev in thread] [next in thread]