id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc 1249,JP2KAK Creation Options Needed,gregcoats@…,warmerdam,"{{{ 1. Although GDAL provides for the creation of tiled GeoTIFF images, and for the creation of tiled GeoJPEG2000 images via its JasPer based module, GDAL does not provide for the creation of tiled GeoJPEG2000 images via its JP2KAK Kakadu based module. This is a serious limitation that effectively limits the use of the JP2KAK module to relatively small images. This is especially bad because Kakadu can handle large images up to an order of magnitude faster than JasPer. Please add to the JP2KAK module Creation Options that allow the user to specify the JP2 image tile size, which is done natively within Kakadu using Stiles={kdutiley,kdutilex} 2. Additionally, beginning with Kakadu version 5.1 (Kakadu version 5.2 is now available), Kakadu uses the ""-num_threads "" option to support multiple processors, and multi core processors. This can greatly speed up processing. 3. Also, when processing large images I find it necessary to use the Kakadu option -flush_period without which the processing tries to hold the entire input and output images in RAM, and when that fails it gives up, and produces no JP2 file. Usually I set the -flush_period to the number of lines in the tile being created. There may be no good reason for setting -flush_period to exceed the number of lines in the tile, but setting it to less than the number of lines in the tile could possibly adversely effect image compression. Apparently JP2KAK tries to flush every 1024 lines. That is probably a good default, but it would seem advantages to allow the user to set -flush_period, particularly for large images. In summary, please add to the JP2KAK Creation Options the ability to pass to Kakadu Stiles={y,x} -num_threads -flush_period }}}",defect,closed,highest,,GDAL_Raster,unspecified,blocker,wontfix,,