Knut-Frode, I've skimmed quickly through the driver code and if you are lucky, it is probably just a matter of changing a few lines (well, I can be wrong).
If you have a debug build of GDAL, you can first try to run "gdalinfo --debug on avhrr_20120227_235800_noaa19.hrp" . My guess (based on http://en.wikipedia.org/wiki/NOAA-19 saying that NOAA-19 = NOAA-N' and NOOA-N' appearing in commented code of the driver...) would be that you would see : "Unknown spacecraft ID "8"". If so, you could test the following patch : Index: l1bdataset.cpp =================================================================== --- l1bdataset.cpp (revision 24036) +++ l1bdataset.cpp (working copy) @@ -61,6 +61,7 @@ NOAA16, // NOAA-16(L) NOAA17, // NOAA-17(M) NOAA18, // NOAA-18(N) + NOAA19, // NOAA-19(N') METOP2 // METOP-2(A) }; @@ -1025,10 +1026,10 @@ case 7: eSpacecraftID = NOAA18; break; - /* FIXME: find appropriate samples and test these two cases: - * case 8: - eSpacecraftID = NOAA-N'; + case 8: + eSpacecraftID = NOAA19; break; + /* FIXME: find appropriate samples and test that case: case 11: eSpacecraftID = METOP-1; break;*/ @@ -1155,6 +1156,9 @@ case NOAA18: pszText = "NOAA-18(N)"; break; + case NOAA19: + pszText = "NOAA-19(N')"; + break; case METOP2: pszText = "METOP-2(A)"; break; Perhaps Andrey Kiselev, the author of the driver, would have better clues. Best regards, Even _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
