Martin Raspaud

> > I think using `.load()` would go against what we generally try to do in Satpy which is to delay loading data until it is actually being computed. >...

@adybbroe where are we at with this PR ?

The reason behind this is that when we started pyorbital, the use case was one observer, many satellite positions. But you're right, it should be made consistent. Pull request is...

@clmuddjr thanks for reporting this issue! I think the Deep space error comes when trying to use TLEs for computing geostationary or deep space orbits, with pyorbital doesn't support yet....

If someone wants to dive into a PR for deep space computations: deep space initialisation (https://github.com/pytroll/pyorbital/blob/master/pyorbital/orbital.py#L779-L780) should follow page 85 of https://celestrak.com/publications/AIAA/2006-6753/AIAA-2006-6753-Rev3.pdf and propagation (https://github.com/pytroll/pyorbital/blob/master/pyorbital/orbital.py#L779-L780) should implement the beginning of...

Hi, TLE is a good start, but you need more information than this to compute the observation area, in particular the characteristics of the sensor like the resolution and min/max...

Yes, the script might not be up to date, but if you have the sensor definition set properly, I'm sure you can adapt the example to your use case :)

I have no idea what sensor you are working with, so it's going to be difficult for me to give you a hint :sweat_smile: If you paste your sensor definition...

I'm not sure I understand. The plot shows north America, but the Basemap definition seems to be over Europe?

yes. Don't forget the time should be given in utc.  Here is the script I used to generate this image: ```python from pyorbital.geoloc_instrument_definitions import avhrr import numpy as np...