Calling jpylyzer in a command window without any arguments results in the following helper message:
||input JP2 image(s), may be one or more (whitespace-separated) path expressions; prefix wildcard (*) with backslash (\) in Linux|
||show this help message and exit|
||report test results in verbose format|
||when analysing a directory, recurse into subdirectories (implies –wrapper)|
||wrap output for individual image(s) in ‘results’ XML element|
||extract null-terminated XML content from XML and UUID boxes(doesn’t affect validation)|
||suppress pretty-printing of XML output|
||show program’s version number and exit|
Output is directed to the standard output device (stdout).
In the above example, output is redirected to the file ‘rubbish.xml’. By default jpylyzer’s XML is pretty-printed, so you should be able to view the file using your favourite text editor. Alternatively use a dedicated XML editor, or open the file in your web browser.
Overview of output elements
A jpylyzer output file contains the following top-level output elements:
- toolInfo: tool name (jpylyzer) + version.
- fileInfo: name, path, size and last modified time/date of input file.
- isValidJP2: True / False flag indicating whether file is valid JP2.
- tests: tree of test outcomes, expressed as True / False flags.
A file is considered valid JP2 only if all tests return True. Tree follows JP2 box structure. By default only tests that returned False are reported, which results in an empty tests element for files that are valid JP2. Use the
--verboseflag to get all test results.
- properties: tree of image properties. Follows JP2 box structure. Naming of properties follows ISO/IEC 15444-1 Annex I (JP2 file format syntax) and Annex A (Codestream syntax).
The following video gives an overview of what jpylyzer does, and how to use it:
Note that this video was based on an older jpylyzer version that didn’t support pretty-printed output. (From version 1.13.0 onward jpylyzer uses pretty-printing for its XML output.)
For more detailed information on the use of jpylyzer, there’s an exhaustive User Manual. It provides an in-depth coverage of the following topics:
- the installation process;
- usage of jpylyzer as a command-line tool, or as an importable Python module;
- an overview of the box structure of a JP2 file;
- jpylyzer’s output format;
- a description of every test that jpylyzer performs for validation;
- a description of every reported property.