Input plugins: the `mpop.satin` package¶

Available plugins and their requirements¶

mipp_xrit¶

Reader for for hrit/lrit formats. Recommends numexpr and pyresample.

aapp1b¶

Reader for AAPP level 1b format. Requires numpy, recommends pyresample.

eps_l1b¶

Reader for EPS level 1b format. Recommends pyresample.

viirs_sdr¶

Reader for the VIIRS SDR format. Requires h5py.

viirs_compact¶

Reader for the VIIRS compact format from EUMETSAT. Requires h5py.

hdfeos_l1b¶

Reader for Modis data format. Requires pyhdf.

msg_hdf¶

Reader for MSG cloud products. Requires h5py, recommends acpg.

pps_hdf¶

Reader for PPS cloud products. Requires acpg.

hrpt¶

Reader for level 0 hrpt format. Requires AAPP and pynav.

eps1a¶

Reader for level 1a Metop segments. Requires AAPP, kai and eugene.

Interaction with reader plugins¶

The reader plugin instance used for a specific scene is accessible through a scene attribute named after the plugin format. For example, the attribute for the foo format would be called foo_reader.

This way the other methods present in the plugins are available through the scene object.

The plugin API¶

Changed in version 0.13.0: New plugin API

The mpop.plugin_base module defines the plugin API.

class mpop.plugin_base.Plugin(ppp_config_dir=None, default_config_filename=None, config_files=None, **kwargs)¶

The base plugin class. It is not to be used as is, it has to be inherited by other classes.

get_section_type(section_name)¶

load_config(conf)¶

Adding a new plugin¶

For now only reader and writer plugins base classes are defined.

To add one of those, just create a new class that subclasses the plugin.

The interface of any reader plugin must include the load() method.

Take a look at the existing readers for more insight.

Input plugins: the mpop.satin package¶