Skip to main content

New drivers for JAI. Dificulty.

3 replies [Last post]
Anonymous

Hi all,
at my proyect we've developed some brand new image drivers for java
(notably Lizardtech MrSID and a GDAL wrapper. I would like to know how
dificult will be to write new drivers but for JAI architecture. Also ...
what about georeferencing info on the format ... would be available for
the applications?.

Our main problem it's that due to the inmense size of the files
being used on Geospatial sector ( > 10 Gb with 1:50 compression ratio on
one image) the startegy of loading everything on memory its
unaffordable, and all the uses must be done 'by pieces'.

Thanks in advance
Luis

--
Luis W. Sevilla
gvSIG development Team
Conselleria de Infraestructuras y Transporte
Generalitat Valenciana
Valencia - Spain
http://www.gvsig.gva.es

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Brian Burkhalter

On Thu, 14 Apr 2005, Luis W. Sevilla wrote:

> at my proyect we've developed some brand new image drivers for java
> (notably Lizardtech MrSID and a GDAL wrapper. I would like to know how
> dificult will be to write new drivers but for JAI architecture.

By "drivers" I take it to mean reader and writer plug-ins? Is that correct? In
that case you would write wrappers conforming to the Java Image I/O Framework
specification:

http://java.sun.com/j2se/1.5.0/docs/guide/imageio/index.html

> Also ...
> what about georeferencing info on the format ... would be available for
> the applications?.

It should be if you write the plug-ins to supply metadata via the Java Image
I/O metadata tree abstraction:

http://java.sun.com/j2se/1.5.0/docs/api/javax/imageio/metadata/package-s...

> Our main problem it's that due to the inmense size of the files
> being used on Geospatial sector ( > 10 Gb with 1:50 compression ratio on
> one image) the startegy of loading everything on memory its
> unaffordable, and all the uses must be done 'by pieces'.

The Image I/O specification was designed to allow the efficient handling of
virtually any image file regardless of size. When reading, for example, you
can set the region of the source image to be read. Provided the source format
and the reader plug-in allow subsections to be read efficiently this should
solve your problem vis-a-vis memory.

Brian

----------------
Brian Burkhalter
Advanced Development, Graphics and Media
Software Chief Technology Office
Sun Microsystems, Inc.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Luis W. Sevilla

adding some complexity to our problem ... are support on JAI for writing
drivers for 16 bits images? ... and multibanded (> 4 bans per pixel)?
... and rasters (not really images) with float and double 'pixels'
(typicaly Digital Elevation Models?

Luis W. Sevilla wrote:

> Hi all,
> at my proyect we've developed some brand new image drivers for java
> (notably Lizardtech MrSID and a GDAL wrapper. I would like to know how
> dificult will be to write new drivers but for JAI architecture. Also
> ... what about georeferencing info on the format ... would be
> available for the applications?.
>
> Our main problem it's that due to the inmense size of the files
> being used on Geospatial sector ( > 10 Gb with 1:50 compression ratio
> on one image) the startegy of loading everything on memory its
> unaffordable, and all the uses must be done 'by pieces'.
>
> Thanks in advance
> Luis
>

--
Luis W. Sevilla
Equipo de desarrollo gvSIG
Conselleria de Infraestructuras y Transporte
Generalitat Valenciana
Valencia - Spain
http://www.gvsig.gva.es

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Brian Burkhalter

On Thu, 14 Apr 2005, Luis W. Sevilla wrote:

> adding some complexity to our problem ... are support on JAI for writing
> drivers for 16 bits images? ... and multibanded (> 4 bans per pixel)?
> ... and rasters (not really images) with float and double 'pixels'
> (typicaly Digital Elevation Models?

Imaging in JAI, Image I/O, and JAI-Image I/O) is designed to accomodate any
pixel depth which will fit in any of the supported data types: unsigned byte
and signed or unsigned short or int. Also, 32-bit (float) and 64-bit (double)
sample values are accomodated.

The number of bands is effectively unlimited with the maximum count being
Integer.MAX_VALUE.

Brian

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net