[Blog] Post-processing — when parsing alone is not enough

cooli4enko85

Parsing incoming data from hundreds of GPS tracker types into a unified JSON format is already taken for granted.

How about parsing the bits of data from millions of sensors and other peripherals connected to these telematics devices?

We’ve got you covered! Our post-processing technology enables you to handle incoming messages in a variety of user-defined ways and sequentially apply several lines of logic.

Learn more about the new concept in the dedicated blog post:

https://flespi.com/blog/post-processing-protocols

daniel_armenta

Excellent functionality !!! .. I would like to have more information about how to apply calculations and more detailed information about how to make the conversion when it is LBS using this functionality. Thanks.

shal

daniel_armenta At that moment we are developing such post-processing protocols with required logic upon requests from our users, based on SLA Advanced. If you want something please contact us in the builtin chat.

LBS functionality is just about the sample of technology usage, we do not have such protocol in the moment. Also it will rely on the external service (outside of flespi) and even may require separate paid subscription to it.

rafinewman

do you have existing post processing channels that may be selected by any user?
which?
any documentation?

thanks

dexif

rafinewman
We currently recommend using plugins instead of post-processing channels:

post-processing channel protocols started looking like a blind branch of evolution and may even become extinct…

https://flespi.com/blog/evolution-of-plugins