Thanks, I'll check this out in more detail tomorrow. Two quick thoughts:

1. It should probably also support Flip.BOTH
2. Would it deserve its own ImageServer implementation?

Currently we have RotatedImageServer, even though AffineTransformImageServer could also do the job. This avoids the need transform all x and y coordinates then build up the image pixel by pixel (or rely on Graphics2D rendering for RGB images). Here, you could instead extract rows and columns and simply reverse them.

To help answer, it would be worth checking performance with a large, multiplexed image, e.g., LuCa-7color_Scan1.qptiff or Patient_1.ome.tiff; you could benchmark tile reading using AffineTransformImageServer and RotatedImageServer to see if they are different enough to justify the latter.

See also how command line support is provided for rotation with --rotate (it has been a long time since I've used this, so I'm only guessing it still works....).

On LuCa-7color_Scan1.qptiff or Patient_1.ome.tiff, the benchmark script results are:

• Around 21 seconds with no rotation.
• Around 30.3 seconds with the following rotation:

server = new RotatedImageServer(server, RotatedImageServer.Rotation.ROTATE_180)

• Around 35 seconds with the following rotation:

var transform = new AffineTransform()
transform.rotate(Math.PI, server.getWidth() / 2, server.getHeight() / 2)
server = new TransformedServerBuilder(server)
    .transform(transform)
    .build()

So yes it might be better to create a new FlipImageServer.