In practise the restituted orbits are of very high quality, you can try processing with them already now as the improvement the precise orbits will give you is rather minor.
I’m just wondering what’s the reason behind the 21 days lag of the precise orbit files? I cant find any clue on the web. Why cant the precise parameters be available immadiately? Is it some security issue?
I tried that do coregistration on them and in the Apply-Orbit-File tab, instead of select Sentinel Precise Orbits, I selected the Restituted orbits but I do not know why I got below error, although I did not select Sentinel Precise Orbits.
Please guide me.
Cheers,
But how can i choose which orbit file should be downloaded ? Because i am confuse about the POD file name, if any idea about the naming pattern pleas tel me.
I tried that do coregistration on them and in the Apply-Orbit-File tab, instead of select Sentinel Precise Orbits, I selected the Restituted orbits but I do not know why I got below error, although I did not select Sentinel Precise Orbits.
Please guide me.
Cheers,
I do not understand what is going wrong with the Orbit file dates, dates in year 2000 or 2027 are obviously not valid for Sentinel-1. @lveci@kraftek do you have an idea?
As far as I see from the screenshots, the problem is in the outgoing request from SNAP, not on the orbit files.
Not knowing the details of the products, I suspect there may be something related with the locale of the workstation. If I can have a look at the product metadata file (*.dim), I could tell more.
The default date of Jan 1 2000 means the product has no start date. How was the product created? Did you open the the GeoTiff files and created a subset? If that is the case, you need to open the product as a whole including metadata by selecting the manifest.safe file or the zip file.
