n-lagomarsini / jai-ext Goto Github PK

Inside the roi-aware-op project all the modules should be renamed for a better comprehension.

Currently the test in jt-affine and jt-scale projects does not have a javaDoc.

In the jt-mosaic project ROI is not passed as a property. A possible improvement could be the creation of 2 properties called = JAI.Ext.ROI and JAI.Ext.NoData for passing these fields through a RenderedOp chain.

Inside the NearestTest class of jt-scale project, the registration Test is empty. It should be written.

TranslateOpImage should not be inside the jt-scale project.

The scale operation performed by ScaleNoDataOpImage needs optimization:

• The computeLoop() and computeLoopBinary methods should be divided for every image-type.
• The image creation inside the TestBase class needs to be accelerated.
• Data type conversions should be avoided if possible.

When the bicubic or the bilinear interpolation are performed during a scale or an affine operation, the borders show some artifacts. This could be due to a wrong weight assignment(for pixel out of the ROI or no data values) during interpolation.

ROI support should be added to the bandmerge operation

In jt-affine and jt-scale project not all the possible exception are hadled.

If the input interpolation object is not one of the 3 base interpolators defined by the jt-utilities project (Nearest, Bilinear, Cubic), background values is set by default to 0 and cannot be changed.

In the most of the project of the repository an header is not present.

jt-scale, jt-affine, jt-mosaic should have clearer class names for a better comprehension.

RandomIterators are too slow when they calculate the tile associated to the related pixel, because they request the tile from the cache that use synchronization. This behaviour could be changed by saving the tile eventually using threadLocal.

In jt-affine and jt-scale tests for Bicubic and Bilinear interpolation there is not always a borderExtender instance.

The AffineNoDataDescriptor and ScaleNoDataDescriptor should be compared to the AffineDescriptor and ScaleDescriptor classes inside the JAI core project.

TestData and SampleData class should be created and used like in GeoServer project.

For the jt-scale project, tests should not only increase the size of an image but also reduce it.

The class TestBase should be placed in the src/test/java folder and the project pom modified for test scope.

In NearestAffineTest, testImageAffinegBinary is ignored because it throws an exception that should be handled.

Jt-mosaic project needs an optimization for the ROI handling, because now it is too slow on calculating the ROI.getAsImage() method.

In MosaicNoDataOpImage the ROI support stores a PlamarImage representation of the ROI instead of a ROI object. Should be changed.