Visibility during operations
CLS_OFF.3.7 : Visibility during operations
1 |
Challenge ID |
CLS_OFF.3.7 |
||||
2 |
Title |
Visibility during operations |
||||
3 |
Originator of Challenge |
SHELL |
||||
|
General description |
|
||||
4 |
What data/products do you currently use ? |
Cloud cover and dust (aerosol index) : GOME/SCIAMACHY/OMI/ISCCP
|
||||
5 |
When do you use this kind of dataset? |
Mainly during Design phases of projects to help operations. |
||||
6 |
What are your actual limitations and do you have a work around? |
n/a |
||||
7 |
Needs and expectations on EO data |
n/a |
||||
|
Challenge classification |
|
||||
8
|
Lifecycle stage |
Pre license |
Exp. |
Dev. |
Prod. |
Decom. |
Score from impact |
|
|
4 |
|
|
|
9 |
Geographic context/restrictions |
• Global : offshore/coastal and onshore • Caspian sea, • Nigeria • Qatar, • Oman • West Australia • Mediterranean coastal and onshore, • South Africa Namibia, • Mozambique • South-China sea, • Philippines • Guyane • America • Venezuela • Brasil |
||||
10 |
Topographic classification / Offshore classification |
All topographic classifications
|
||||
11 |
Activity impacted/concerned |
n/a |
||||
12 |
Urgency (How quickly does the user need the solution) |
It depends on the project.
|
||||
|
Information requirements |
|
||||
13 |
Update frequency |
n/a |
||||
14 |
Temporal resolution |
For offshore a resolution of 20 – 25 km is OK. The main difficulties are located on coastal and onshore areas. |
||||
15 |
Spatial resolution |
n/a |
||||
16 |
Data quality |
Ok for the time being |
||||
17 |
Data Coverage and extent |
n/a |
||||
18 |
Example formats |
Matlab or Fortran would be fine. But most important, the tools to read the products are needed. |
||||
19 |
Timeliness |
Ok for the time being |
||||
20 |
Existing standards |
Matlab or Fortran |
There is no content with the specified labels