Hello again,
I see some inconsistency (a bug?) in a way Geoserver handles GeoTIFF files with custom coordinate reference system.
See example file (CRS definition at the end of my e-mail):
http://geo.nebula.grid.icm.edu.pl/tmp/wrf_d02_T2_201504040600_001crs.tiff
In case you import it directly as a GeoTIFF:
- it is correctly displayed in Google Earth as a kml file
- Layer Preview shows empty image
If you import it as ImageMosaic layer:
- it is displayed upside down, both in Layer Preview and Google Earth
Differences starts from coverage.xml files: "scaleY" parameters have opposite sign, "translateY" value is different. I noticed also that org.geotools.gce.imagemosaic applies additional affine transform before displaying the image.
GeoTIFFs with other custom CRS have similar problems, so I think it's more general issue.
Regards
Maciej
100102=PROJCS["WRF Lambert",GEOGCS["WGS 84",DATUM["World Geodetic System 1984",SPHEROID["WGS 84",6378137.0,298.257223563,AUTHORITY["EPSG","7030"]],AUTHORITY["EPSG","6326"]],PRIMEM["Greenwich",0.0,AUTHORITY["EPSG","8901"]],UNIT[
"degree",0.017453292519943295],AXIS["Geodetic longitude",EAST],AXIS["Geodetic latitude",NORTH],AUTHORITY["EPSG","4326"]],PROJECTION["Lambert_Conformal_Conic_2SP"],PARAMETER["central_meridian",18.20199966430664],PARAMETER["latit
ude_of_origin",54.13700866699219],PARAMETER["standard_parallel_1",30.0],PARAMETER["false_easting",0.0],PARAMETER["false_northing",0.0],PARAMETER["standard_parallel_2",60.0],UNIT["m",1.0],AXIS["Easting",EAST],AXIS["Northing",NOR
TH]]