First of all, all wavelet-compressed raster file formats like ECW, MrSID, and JPEG 2000, will have internal pyramids. This indicates that pyramids cannot be created by any solution packages, including ArcGIS…
Secondly, let’s argue one statement on JPEG 2000 at http://desktop.arcgis.com/en/desktop/latest/manage-data/raster-and-images/raster-pyramids.htm :
(With ArcGIS), you can create pyramids for JPEG 2000. Geodatabase rasters with wavelet compression can also have pyramids built.
Personally, it is a confusing statement. In fact, when running the GP tool ‘Building Pyramids” on JPEG 2000, the resulted JP2 does not have the associated .ovr file. Also, the result JP2 does not have any performance improvement…
Finally, on JPEG2000 standard (http://www.jpeg.org/jpeg2000/applications.html ), it is well known that many solution vendors have different implementations on this standard JPEG2000; even though their JP2 can be compatible with each other…This fact indicates one implementation may have more advantages over others… However, many computer solution vendors extend the above JPEG2000 standard differently for different purposes.
For example, ERDAS Imagine supports the following supplements to the JPEDG2000 standard via the “Advanced” parameters:
Tile Dimensions, Precinct Dimensions, Progression Order (RPCL - Fastest loading from networks; Progression by resolution; LRCP - Slower loading from networks except when datastream is sent by quality layer; Progression by quality layer; RLCP- Faster loading from networks than LRCP option; Progression by resolution, and then by quality layer)…