Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

titleMetview now uses ecCodes

With version 4.8.0, Metview is being built by default with ecCodes instead of GRIB-API for GRIB handling. See November synchronised release news item for more information.


From version 4.5, Metview uses CMake for its compilation and installation. This is part of the process of homogenising the installation procedures for all ECMWF packages., in line with all other ECMWF packages. Note that there are other ways to install Metview from pre-built binary packages, or from a source bundle that includes many dependencies. See Releases.

Include Page
SUP:General CMake installation instructions
SUP:General CMake installation instructions


The following table lists the dependencies Metview requires to be built from source. Please note, if you install these package from source you also might have to install the respective "-devel" packages.





Third party packages

(best installed through system package manager)

Qt 5

if Metview's user interface is required

(version 4


6.2 or later of Qt is needed).

Note that on some systems it is also necessary to install the libQtWebKit-devel development package (it may have different names on different systems)

 ImageMagick Metview's user interface is requiredproj OPERA radar data support is required


netcdf 4

Please note: You also will need to install HDF5 and the legacy C++ interface

and HDF5

 if you wish to run the Single Column Model from Metview (ECMWF only)


Optional for web services support (WMS, Download module)


ECMWF libraries
grib-apiGRIB-API HomeAlternatively you can use ECCemoslibEMOS odb-apiODB-API Homeif ODB support needed
ecCodesecCodes Home
magicsMagicsif plotting support is needed. Note that Magics should be configured with the -DENABLE_METVIEW=ON option.

For a 'pure batch' installation of Metview with no user interface, it is possible to supply Magics with the option -DENABLE_METVIEW_NO_QT=ON


odb-apiODB-API Homeif ODB support needed
emoslibEMOSoptional and deprecated

CMake options used in Metview


CMake option
ENABLE_UIenables the Qt-based user interfaceON

build the Qt user interface using Qt5 libraries
(also requires that Magics is built with this option enabled)
might require the flag: -DCMAKE_PREFIX_PATH=/path/to/qt5/

OFFENABLE_PLOTTINGenables plotting capabilities using MAGPON
ENABLE_OPERA_RADARenables the Opera Radar Filter module (requires the proj4 library and headers)OFFENABLE_MARSenables MARS access (not required if using through the Web API)OFF
MARS_LOCAL_HOMEsets the path to where local MARS is installed 
ENABLE_ECCODESEnables ecCodes being used instead of GRIB_API. We recommend
to use ecCodes, but if require GRIB-API you can set this to OFF.
ONENABLE_ODBenables processing and plotting of ODB dataOFF
ENABLE_MARS_ODBenables ODB capabilities in MARS clientOFF
ENABLE_USAGE_LOGenables logging of Metview startup callsOFF
LOG_DIRpath to where to log the Metview startup calls 
METVIEW_SCRIPTname of the generated Metview startup scriptmetview
EXTRA_CONFIG_PATHpath to optional directory containing metview_local* script files 
ENABLE_QT_DEBUGoutputs additional log messages from Qt-based modulesOFF
EXTRA_TITLEbuild-specific title to add to the log entries 
ENABLE_INPEenables INPE modulesON
Path options - only required when support libraries are not installed in default locations
CMake OptionDescriptionNotes
ECCODES_PATHpath to where ecCodes has been installed 
GRIB_API_PATHpath to where GRIB_API has been installed 

MAGICS_PATHpath to where Magics has been installedOnly required if plotting is enabled
NETCDF_PATHpath to where netCDF has been installed 
ODB_API_PATHpath to where ODB_API has been installedOnly required if ODB is enabled
ODB_PATHpath to where the original ODB has been installedOptional if ODB is enabled
EMOS_PATHpath to where Emoslib has been installedAlso set EMOS_LIB_NAME
FDB_PATHpath to where fdb has been installedOnly required if MARS is enabled
PROJ4_PATHpath to where proj4 has been installedOnly required if OPERA Radar is enabled
FLEXTRA_PATHpath to where the FLEXTRA executable has been installedSee Tutorials for more on FLEXTRA


If you have installed Metview 3 before, then here are some things to note. Metview 4 5 does not use directly OpenGL for its on-screen graphics; therefore, it is not necessary to build your own Mesa library anymore. However, Metview 4 does not come with its own Emoslib; therefore, it will be necessary to install your own.

Metview 4 5 can be installed side-by-side with an existing Metview 3 installation. However, note that the default startup script will be


See also the Installation FAQ.