Martin Raspaud
Martin Raspaud
@oembury could you provide an example of what "very incorrect results" look like? afaik, we have been using the pyorbital code for processing without major problems so far, so I'm...
@oembury thanks a lot for the explanation. I had a quick look, and I can indeed reproduce the issue. It seems to me that one solution is to replace this...
I agree that we need to make things easier to understand, but we need to make sure backwards compatibility between pyorbital and pygac is preserved (latest releases of pygac were...
@oembury the pyorbital changes have now been merged and released (v1.10.0)
@ameraner @ClementLaplace any comments about the last comment by @djhoese ?
Interresting! why is this not showing in the tests?
I'm happy with this. @djhoese can you just confirm that you are good with this being merged? (and feel free to merge it if that's the case)
Should we suggest this change to xarray, or is this too specific?
We just had a meeting on this topic, here are my notes: # Pytroll LI geometry meeting Last PCW Ro started implementing it. It's still a bit rough. Should satpy...
> > At the moment, the LI reader returns a "swath" which should really be a geometry: could we have a "get_vector_dataset" that the yaml reader (subclass?) could use? >...