[ https://issues.apache.org/jira/browse/IMAGING-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199714#comment-17199714
]
Gary Lucas edited comment on IMAGING-265 at 9/22/20, 12:20 AM:
---------------------------------------------------------------
Thanks for the information. The original authors of the Commons Imaging project put an enormous
amount of effort into creating the TIFF modules and I think they left the project with a pretty
good foundation. Nowadays, it's unusual to find an example of a format that Commons Imaging
doesn't support... unusual, but perhaps not quite unusual enough :)
In the case of the samples you provided, they were created using an "odd duck" specification
that we hadn't seen before. I knew there was something called a PlanarConfiguration, but
I had no idea what it was about. So your image provided a good opportunity to expand our
capabilities. Of course, nobody likes to learn about a new bug (or a new feature) that needs
to be addressed... But it definitely leads to more robust code when we do.
Gary
P.S. Just to make sure there's no confusion here, I am not properly speaking a member of
the Commons Imaging project and certainly do not speak for them. I help out with coding occasionally.
My post above makes it sound like I know a lot more than I actually do... Hope I didn't
give a false sense of authority.
was (Author: gwlucas):
Thanks for the information. The original authors of the Commons Imaging project put an enormous
amount of effort into creating the TIFF modules and I think they left us with a pretty good
foundation. Nowadays, it's unusual to find an example of a format that Commons Imaging doesn't
support... unusual, but perhaps not quite unusual enough :)
In the case of the samples you provided, they were created using an "odd duck" specification
that we hadn't seen before. I knew there was something called a PlanarConfiguration, but
I had no idea what it was about. So your image provided a good opportunity to expand our
capabilities. Of course, nobody likes to learn about a new bug (or a new feature) that needs
to be addressed... But it definitely leads to more robust code when we do.
> ArrayIndexOutOfBoundsException on reading simple GeoTIFF
> --------------------------------------------------------
>
> Key: IMAGING-265
> URL: https://issues.apache.org/jira/browse/IMAGING-265
> Project: Commons Imaging
> Issue Type: Bug
> Components: Format: TIFF
> Affects Versions: 1.0-alpha2
> Reporter: edgar soldin
> Assignee: Bruno P. Kinoshita
> Priority: Major
> Attachments: small_world.tif, small_world_split.jpg
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> hi,
>
> we on the OpenJUMP project cannot open some GeoTIFFs with commons.imaging . for details
you may find a ticket in our bug tracker [https://sourceforge.net/p/jump-pilot/bugs/498/] .
>
> the gist is: on loading the attached file getBufferedImage() fails with this stack
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 8000Caused by: java.lang.ArrayIndexOutOfBoundsException:
8000 at org.apache.commons.imaging.formats.tiff.datareaders.DataReaderStrips.interpretStrip(DataReaderStrips.java:196)
at org.apache.commons.imaging.formats.tiff.datareaders.DataReaderStrips.readImageData(DataReaderStrips.java:254)
at org.apache.commons.imaging.formats.tiff.TiffImageParser.getBufferedImage(TiffImageParser.java:665)
at org.apache.commons.imaging.formats.tiff.TiffDirectory.getTiffImage(TiffDirectory.java:254)
at org.apache.commons.imaging.formats.tiff.TiffImageParser.getBufferedImage(TiffImageParser.java:469)
at org.apache.commons.imaging.Imaging.getBufferedImage(Imaging.java:1442) at org.apache.commons.imaging.Imaging.getBufferedImage(Imaging.java:1335)
at org.apache.commons.imaging.Imaging.getBufferedImage(Imaging.java:1304) at com.vividsolutions.jump.workbench.imagery.graphic.CommonsImage.initImage(CommonsImage.java:108)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
|