Reader for for hrit/lrit formats. Recommends numexpr and pyresample.
Interface to Eumetcast level 1.5 HRIT/LRIT format. Uses the MIPP reader.
Read data from file and load it into satscene. The calibrate argument is passed to mipp (should be 0 for off, 1 for default, and 2 for radiances only).
Read imager data from file and load it into satscene.
Reader for aapp level 1b format. Requires AHAMAP, recommends pyresample.
Reader for aapp level 1b data.
http://research.metoffice.gov.uk/research/interproj/nwpsaf/aapp/ NWPSAF-MF-UD-003_Formats.pdf
AAPP-level 1b data reader
Calibrate the data
Return the longitudes and latitudes of the scene.
Read the data.
Read data from file and load it into satscene. A possible calibrate keyword argument is passed to the AAPP reader. Should be 0 for off (counts), 1 for default (brightness temperatures and reflectances), and 2 for radiances only.
Read avhrr data from file and load it into satscene.
Show the stetched data.
Reader for eps level 1b format. Recommends pyresample.
Reader for thinned modis format (as send via Eumetcast). Require pyhdf.
Reader for msg cloud products. Requires pytable and acpg.
Reader for pps cloud products. Requires acpg.
Plugin for reading PPS’s cloud products hdf files.
Load data into the channels. Channels is a list or a tuple containing channels we will load data into. If None, all channels are loaded.
Reader for level 0 hrpt format. Requires AAPP and pynav.
Reader for level 1a metop segments. Requires AAPP, kai and eugene.
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.
Changed in version 0.13.0: New plugin API
The mpop.plugin_base module defines the plugin API.
The base plugin class. It is not to be used as is, it has to be inherited by other classes.
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.