Hi James, when we started to work with NetCDFs in Image Services a couple of years ago, we did have a bit of trouble with coordinate system definitions: our science data are recorded on a rotated pole coordinate system and then written into NetCDF format - that 'rotated pole' coordinate reference system was the first thing which had to change.
After using a more commonly understood projection system, we figured out that the way the scientists had defined that system was common in software clients in the climate science world, but couldn't easily be read into a mosaic dataset. After changing the definition to a common text string it started to work very well.
An example of that definition (from https://epsg.io/3851 ) - you want to use the one called "Esri WKT"
PROJCS["NZGD_2000_NZ_Continental_Shelf_2000",
GEOGCS["GCS_NZGD_2000",
DATUM["D_NZGD_2000",
SPHEROID["GRS_1980",6378137.0,298.257222101]],
PRIMEM["Greenwich",0.0],
UNIT["Degree",0.0174532925199433]],
PROJECTION["Lambert_Conformal_Conic"],
PARAMETER["False_Easting",3000000.0],
PARAMETER["False_Northing",7000000.0],
PARAMETER["Central_Meridian",173.0],
PARAMETER["Standard_Parallel_1",-37.5],
PARAMETER["Standard_Parallel_2",-44.5],
PARAMETER["Latitude_Of_Origin",-41.0],
UNIT["Meter",1.0]] Cheers,
Tilmann
PS: after reading the above, I notice that I should clarify that we _generate_ the NetCDFs that we work with using scripts written here, so obviously we were able to modify the code used to do that - whereas I'm not sure whether you can do that with TUFLOW, which I don't know.
