Skip to content
Snippets Groups Projects
Commit bb1d5a31 authored by Max Drexler's avatar Max Drexler
Browse files

Update README

parent 4102a319
No related merge requests found
# GRIB Processor
Ingest grib files and publish metadata on those files to RabbitMQ servers.
[![pipeline status](https://gitlab.ssec.wisc.edu/mdrexler/grib_rmq_stream/badges/main/pipeline.svg)](https://gitlab.ssec.wisc.edu/mdrexler/grib_rmq_stream/-/commits/main) [![coverage report](https://gitlab.ssec.wisc.edu/mdrexler/grib_rmq_stream/badges/main/coverage.svg)](https://gitlab.ssec.wisc.edu/mdrexler/grib_rmq_stream/-/commits/main) [![PyPI version shields.io](https://img.shields.io/pypi/v/quickmq.svg)](https://pypi.python.org/pypi/quickmq/)
[![Supported python versions](https://img.shields.io/badge/python-3.8%20|%203.9%20|%203.10%20|%203.11%20|%203.12-blue.svg)](https://shields.io/)
ETL pipeline for grib metadata.
## Description
Watch a directory for new or updated grib files and publish an AMQP payload for each message in the file. This event processor was made for use by the Satellite Data Services at the SSEC. To see the format of the AMQP payloads please check out [payload.md](/payload.md).
The grib processor extracts [metadata](/docs/payload.md) from grib files and can optionally publish it to RabbitMQ servers.
The main usecase of this package is for the SSEC with the main purpose being to source grib files by watching a directory and publish all new metadata.
### Limitations
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment