Owen Embury

See attached for NSS.GHRR.NC.D81242.S0756.E0950.B0095859.GC (blue dots are the output from `_get_lonlat_from_file()`) Sorry, the "very incorrect results" was a bit excessive - I was originally looking at a file with a...

That should get the right swath width (assuming the offset term is also included). Though I think the code would be rather confusing to follow - especially if there is...

Yes - the first "scanline" is just the spare header bytes (and similarly for the last scanline read if there are an odd number of actual scanlines)

Yes - it is the yaw steering not being applied. Obviously that doesn't matter for the intended use of `_compute_missing_lonlat`, but it would be useful to verify compute_missing_lonlat against the...

Using the MetOp yaw steering corrections will fix the large shifts seen here. This does require a minor modification to pyorbital which currently only supports a constant yaw correction: pytroll/pyorbital#186...

You can calculate reasonable MetOp geolocation by using: ```python rpy = np.deg2rad(reader.scans['total_applied_attitude_correction']/1e3) * [1, 1, -1] reader._rpy = np.hsplit(rpy, 3) lon, lat = reader._compute_missing_lonlat(reader._times_as_np_datetime64) ``` This will return latitude/longitude coordinates...

I approve