Closed Box88 closed 9 years ago
Hi Marco, Thanks for the but report. I'll have a look at it asap.
Best regards, Martin
@Box88 I just ran your script and can't reproduce the bug. I tested with both master and develop branches, but I don't see the line you mention... are you running on linux ?
I am running on windows 7, python 2.7.10 32 bit, pyorbital 0.3.2 (installed using pip install) I copied and pasted the script again and I still get that line. That's weird...
ok, could you try using the code from github instead ? Master branch first, develop branch if master doesn't work ? It's possible that the latest changes in master didn't make it to pypi...
Using the master branch I still get the bug but using the develop branch it is ok! Next week I will continue playing with pyorbital using the develop branch. Thank you very much!
@Box88 Ok, nice to hear. Fyi develop has now been merged to master, and v1.0.0 was just released.
Hi Martin,
I am developing an application to predict pass conflict of NOAA 19 and NOAA 18 blind orbits with METOP-A and METOP-B passes over EUMETSAT Svalbard ground station. I have been used pyephem as TLE propagator and some days ago I found out also this nice library: pyorbital. I checked the prediction results of both libraries (pyephem and pyorbital) against the data given by the EUMETSAT flight dynamics team and results from pyorbital seem more accurate. Then I would like to integrate also pyorbital in my tool but I found some unexpected results using the get_next_passes function.
Here is the code for verification:
If you run this code you will note that one pass has the following information:
which is clearly wrong, but if you then change the start to datetime(2015,9,1,0,0,0) and stop to datetime(2015,9,2,0,0,0) then you get the following correct results;
Any idea about this behavior? I also found the same problem over the same time period for METOP-B.
Thanks for your attention and congratulations for your project.
Marco Bosco