|There is one issue that disturbs me though. I found an issue with the
|current driver code whereby if you have a data set in which the top y
|coord value is less than the bottom y coord value the image gets
|flipped. It's hard to explain but it happens with a very useful
|bathymetry file we have at CSIRO. With the old driver no matter what I
|did there is no way I could get the image coming up the right way. It's
|a long time since I looked into that issue so my recollection of the
|reason is not clear but there are comments in the code describing it.
| //Here we have arranged the transformation such that the maximum
| //y values are always top and the scale is always negative.
| //Stictly speaking this is clearly not necessary although I am
| //doing it this because I need to, as images of that type end up
| //being flipped for some reason that I'm unsure of.
| double dOrigin;
|The reason why I'm mentioning it to you is that my gut feeling is that
|the real source of the problem lies elsewhere but I don't understand the
|code well enough (and don't have the time to learn it in detail) to be
|able to fix it in the right place. The fix I wrote seems to work without
|side effect, and I did the re-write to the latest code base such that it
|does not utilise my fix if opening in the old way, only when you add
|extra parameters to the filename. Therefore, it should be safe for
|existing users. If you happen to figure out the "real" reason why this
|happens and the "best" fix then I'd be truly greatful.