You may completely ignore framing options. Framing is an operational way of cutting swaths in “scenes” See more here http://1.help.taitussoftware.com/SaVoir/help/content/6.advanced/frame%20numbering/framenumbering.htm
Author Archives: taitus
Little impact The bit rate is used to calculate data size of each acquisition. This will be used to “qualify” each swath with a Data size parameter. It can also be used in the quota constraint, to limit the amount of planned acquisitions according to cumulated aquired volume (GBytes) See more here http://1.help.taitussoftware.com/SaVoir/help/content/6.advanced/constraints/quota/quota.htm Polarisation is […]
It means that “planning will be performed by SaVoir” More information here http://1.help.taitussoftware.com/SaVoir/help/content/6.advanced/constraints/orbits/orbits.htm
No, they are not the same Look angle in “Define Sensor Geometries” defines the sensor field of view capabilities Look angle in “Define Sensor Constraints” allows to optionally limit the operational steering looking angles within a minimum and /or a maximum
This is used when doing coarse planning of acquisitions to provide convenient tolerance and avoid clipping an acquisitions because timing was not sufficiently accurate. We usually applied one or two second lead and trail times in ESA’s Envisat mission planning
Follow this explanation http://1.help.taitussoftware.com/SaVoir/help/content/6.advanced/constraints/gap/gap.htm
This is explained here http://1.help.taitussoftware.com/SaVoir/help/content/6.advanced/constraints/exclusivegrouping/exclusivegrouping.htm
See a deeper explanation here http://1.help.taitussoftware.com/SaVoir/help/content/6.advanced/constraints/duration/duration.htm
The cloud figure is a qualifier parameter, just that. The acquisition will not be planed if you have configured the sensor with a Cloud Constraint and the cloud figure is out of the defined bounds See more here: http://1.help.taitussoftware.com/SaVoir/help/content/6.advanced/constraints/clouds/clouds.htm