Child pages
  • C-CORE 1.12 Visibility



Challenge ID




Challenge originator:


General Description


What data/products do you use?

Visibility data are largely limited to surface-based observations from ships and buoys. The historical records of observed visibilities are available via UCAR (ICOADS) and NOAA (NDBC).

Real-time and near real-time observations of visibility data are available from many sources including NOAA (NWSTG), NOAA (MADIS), NOAA (NDBC), UCAR, and numerous other data distribution centers.

When do you use this kind of dataset?

Visibility  data are important in areas prone to frequent reduced visibility. Reduced visibility might slow down operations, tows, stop helicopter operations and other operations that require a certain visibility. Data are used to qualify and quantify the means and extremes of visibilities, and (b) managing risks related to visibility, safeguarding lives, protecting assets, and conducting operations.

What are your actual limitations and do you have a work around? 

The temporal and spatial resolutions of surface-based observations significantly limits the availability of visibility data. Unless ships or buoys observe and report visibility data, visibilities are not readily available for analysis over vast areas of the ocean.

Hard to use for other purposes than real-time observations, historical data are mostly ground observations, often manual and not very accurate. And when automatic, the cause of low visibility is not easily available (precipitation or fog?). Estimates have to be made.

Better resolution, more frequent observations (hourly, 15 mins), better algorithms to separate fog from cloud.

Needs and expectations on EO data

EO is used for this today and probably the best source to assess the geographical extent of for instance fog. However the resolution and frequency of observations in some regions needs improvement. Also, tools to distinguish for instance fog from other clouds needs to be improved.

Specific need: Time-series of surface-based visibility data. Better algorithms to distinguish fog from cloud etc.

Challenge classification


Pre license










Geographic context/ restrictions

Applies to all six areas of interest.

Seasonality: Applies to all seasons.

Topographic classification / Offshore classification


Activity impacted/concerned


Technology Urgency

Short term (2-5 years)

Information requirements


Update frequency

Hourly or 15 hourly.

Available: Geostationary: Real-time or near real-time observations are available sub-hourly. Polar orbiting rarer. Historical observations are generally updated once per month, for the previous month.

Temporal resolution

Sub-hourly and less frequently.

Spatial resolution

4 km
Available: Observations are available based on the location of the ship/buoy observation, therefore the spatial resolution varies greatly.

Data quality

The selected sources in this document are selected because they are known to have sufficient quality (after some work arounds and adaptations). In general separate indepth verification studies has to be made for each source planned to be used for analysis, and the analysis has to be repeated for each geographical area (since sources might be of sufficient quality in one area but not another).

Data Coverage and extent


Example format

Surface-bases observation: text, CSV and/or netCDF


Hourly/15 mins.

Existing standards

Paragraph C.6.11.3 of ISO 19901-1:2005(E) indicates that visibility below 1 km affects flying (e.g., helicopter operations in support of missions).



There is no content with the specified labels