Identify Files Affected by Truncated-Fuzzy JPEG2000

| *Title* | _The name of the solution. This should match the title of this page_ \\

Files ( \-lt ) 1Mb are definitely affected by truncation (and would also be identified by j2structCheck) \\
Files ( \-lt ) 1/2 average j2 filesize are likely to exhibit problems \\
\\
*evidence from original tif (converted to j2)* \\
if the tifs are available, there should be a one-to-one match of tiff to j2 \\
if the count of tiffs ( - ne ) ( not= ) count of j2 (most likely case is j2 cnt ( - lt ) tif cnt) \\
the j2 cnt should be even - except for rare circumstances where both sides have not been digitised \\
j2 cnt is very likely to be a multiple of 4 \\
\\
*potential enhancements to j2structCheck* \\
use a known bad file (such as the Belfast Newsletter 5Mb j2) and analyse the whole structure rather than the top level \\
see if there are any truncated markers or strange structure things (compared to an assumed good) \\
XnView refused to open any of the j2 files that were in the known bad set, but opened all of the assumed goods - so there has to be a structural difference that differentiates them for this tool. (XnView is built on jj2000, not clear how open source it is (although jad may reveal what is going on too)) \\ |
| *Solution Champion* | _Who owns the Solution? Include an email address if possible_ \\
[~libdms] |
| *Corresponding Issue(s)* | _A bulletted list of links to Issues to which this provides a Solution_ \\
[REQ:Truncated JPEG2000]\\ |

| *Evaluation* | _Any notes or links on how the solution performed_ |