I would recommend splitting the code into two - one for imageio-ext and one
for geotools (so if you like you could set up the modules and package
structure ahead of time. They have different licenses so any code going
from ImageIO to geotools is fine (keep original Apache header and add
GeoTools LG
Hey thanks Jody! Ya I would love to contribute it. I just figured it
would be better to let it incubate in my repo until it's received enough
criticism. I will definitely need my hand held a little as I've never
contributed significant amounts of code to another project before. There
are also s
That is great josh! Is the goal to contribute this to imageio-ext? If you
can try and cite your sources in the header it will help ..
On Fri, Aug 2, 2019 at 1:03 PM Josh Fix via GeoTools-Devel <
geotools-devel@lists.sourceforge.net> wrote:
> So here is my first stab at the reader that supports V
So here is my first stab at the reader that supports VFS paths:
https://github.com/joshfix/gdal-vfs-reader
It is very much a prototype/WIP. I would guess that 95% of the code was
simply copied and pasted from various sources in imageio-ext and geotools
and reassembled into these new classes. I'
Thanks for the insite Andrea. I find myself getting mixed up quite a bit
between the imageio-ext classes, the geotools class, the image readers and
the coverage readers. I suppose my ultimate goal would be to support a
GridCoverage2DReader implementation that accepts vsicurl Strings (or likely
so
Hi Josh,
I am under the impression that things are getting mixed up, but have little
time to write this mail and none to check
what I'm writing, so please take it with a pinch of salt.
If you want to support visicurl directly from imageio-ext gdal based
readers, IMHO all the discussion about image
Thanks so much for the response and I'm excited to hear that there is
interest. Does any of the existing GDAL code specifically support COGs? My
imagery skills aren't very strong, but I would hope that we would be able
to use the request geometry to only request the specific range of bytes
require
With the current prevalence of cloud imagery, the fact that many core
GeoTools classes still strictly require files feels a bit outdated to me.
It would be good if we could move the base GeoTools reader classes (like
BaseGridCoverage2DReader and BaseGdalReader) to support a wider range of
inputs (e
Hi Josh,
I might be back with some more helpful feedbacks in the next few days but I
wanted to provide at least my reply right now, since I started
ImageIO-EXT/GeoTools/GeoServer - GDAL support/integration many years ago.
I think that supporting VFS would be a great and interesting contribution
to
