There could be a vsipreload script that sets the environment variable
and then execs its parameters similar to how eatmydata [1] works.
[1] https://manpages.debian.org/testing/eatmydata/eatmydata.1.en.html
On 8/7/19 4:10 PM, Even Rouault wrote:
On mercredi 7 août 2019 20:58:54 CEST Joe Lee wro
Hi,
The last piece of the work planned per RFC 75 has now been pushed to master
with multidimensionnal support in the GRIB driver (time-based grouping for
GRIB messages of the same variable concatenated in a same file).
Even
--
Spatialys - Geospatial professional services
http://www.spatialy
On mercredi 7 août 2019 20:58:54 CEST Joe Lee wrote:
> Hi, Even!
>
> Is there a configure flag for enabling it by default without relying on
> LD_PRELOAD=...? (e.g., --with-vsipreload)
No,
- this needs to be loaded with LD_PRELOAD because it overrides very common
symbols of the libc (fopen, et
On mercredi 7 août 2019 20:36:48 CEST Joe Lee wrote:
> Hi, Even!
>
> I tested it and your new code works very well.
> Thank you for adding this new feature so quickly!
>
> Now I wish /vsis3 work on HDF4 like HDF5.
> That would be perfect because I tried /vsicurl as you suggested in [1] bu
Hi, Even!
I tested it and your new code works very well.
Thank you for adding this new feature so quickly!
Now I wish /vsis3 work on HDF4 like HDF5.
That would be perfect because I tried /vsicurl as you suggested in [1] but it
did not work.
[1]
http://osgeo-org.1560.x6.nabble.com/gdal
On mardi 30 juillet 2019 18:10:15 CEST Joe Lee wrote:
> I found the error. It was my token key in gdal.SetConfigOption().
> GDAL Multidimensional support is quite amazing and works well with AWS
> Lambda & HDF5 data on S3!
> I can't wait to see HDF4 multidimensional support.
This has just landed
I found the error. It was my token key in gdal.SetConfigOption().
GDAL Multidimensional support is quite amazing and works well with AWS Lambda &
HDF5 data on S3!
I can't wait to see HDF4 multidimensional support.
Thank you, GDAL development team for the new driver!
On Tue, Jul 30, 2019 at 12
Hi, Even!
1-D dataset handling in the new HDF5 multi-dimension code is fantastic!
I could convert 1-d swath into GeoTIFF using the new Python HDF5
multidimensional API.
Please see python code at the bottom of email.
However, I can't run it as an AWS lambda function.
The below is the e
On jeudi 25 juillet 2019 19:57:44 CEST Joe Lee wrote:
> Unsupported number of dimensions
Ah ok, when exporting to GeoTIFF or a "classic" 2D driver, the
multidimensional-to-classic bridge currently checks that the array is a 2D
one. Here you reduced it to a 1D-slice, hence it rejects it. The brid
Thanks, Even for the quick answer!
I tried it but I get "ERROR 6":
[nene:gdal/gdal/apps] hyoklee% ./gdalmdimtranslate -array
name='/HDFEOS/SWATHS/MOP02/Data
Fields/RetrievedSurfaceTemperature',view=\[:,0\]
~/NASAHDF/MOP02J-20131129-L2V17.8.3.he5 test.tif
ERROR 6: Unsupported number of dimen
On jeudi 25 juillet 2019 19:12:02 CEST Joe Lee wrote:
> I'm glad that this motion has passed!
>
> I got one question after reviewing Even's latest code and RFC.
>
> Does it consider a case that subsets 1d dataset from 2d dataset [1]?
> The organization of MOP02J (1-D SWATH) and its shape is like
I'm glad that this motion has passed!
I got one question after reviewing Even's latest code and RFC.
Does it consider a case that subsets 1d dataset from 2d dataset [1]?
The organization of MOP02J (1-D SWATH) and its shape is like below:
dset[2][n_points]
lat[n_points]
lon[n_points]
I wish I co
On jeudi 18 juillet 2019 11:37:08 CEST Even Rouault wrote:
> Hi,
>
> I motion to adopt RFC 75: Multidimensional array
>
> https://github.com/OSGeo/gdal/pull/1580
>
> ---
I declare this motion passed with +1 from PSC members NormanB, HowardB and
myself.
Even
--
Spatialys - Ge
+1 Howard
> On Jul 18, 2019, at 11:34 AM, Norman Barker wrote:
>
> Hi Even,
>
> thanks for the clarification around indexing and nodata. This works great and
> when I have availability and your changes last in master I will upgrade the
> tiledb driver.
>
> +1 from me.
>
> Norman
>
> On Thu
Hi Even,
thanks for the clarification around indexing and nodata. This works great
and when I have availability and your changes last in master I will upgrade
the tiledb driver.
+1 from me.
Norman
On Thu, Jul 18, 2019 at 10:48 AM Even Rouault
wrote:
> Hi,
>
> >
> > I am in favour of the work
Hi,
>
> I am in favour of the work on multi-dimensional arrays. There are two open
> PRs https://github.com/rouault/gdal/pulls with changes to the text.
Oh I didn't see them before. I've merged the first one from Edzer. Answering
yours now:
> Though
> I and my employer would like TileDB inclu
Even,
I am in favour of the work on multi-dimensional arrays. There are two open
PRs https://github.com/rouault/gdal/pulls with changes to the text. Though
I and my employer would like TileDB included in the list of formats (though
happy to wait until I have added the code to support this) the iss
Hi,
I motion to adopt RFC 75: Multidimensional array
https://github.com/OSGeo/gdal/pull/1580
---
Starting with my +1
Even
--
Spatialys - Geospatial professional services
http://www.spatialys.com
___
gdal-dev mailing list
gdal-dev@li
18 matches
Mail list logo
