motamman - I have been experimenting with a Sig...
I have been experimenting with a Signalk web app/plugin/python API that archives paths as Parquet files based on a configurable regimen system that can be toggled on and off. For example, if the regimen's capturePassage is true, it would capture a custom list of paths, such as navigation.position and navigation.attitude, courseOverGround, speedOverGround, headingMagnetic, etc.
The list could be as long as the number of paths on the server. And the number of capture regimens is nearly infinite (captureAnchor, captureThisIsAFairyTale, etc.) This idea stemmed from a desire to capture AIS data of passing vessels and correlate various parameters, such as SOG, COG, distanceToSelf, to my boat’s heave, wave height, and period. I would like to present an empirical argument to local authorities, urging them to take action regarding no-wake enforcement and potential no-wake zone extensions. I soon realized I could do much more than that, and now use it for archiving and storing Signalk data for four or five regimens.)
I use Parquet/file-based system because InfluxDB is a horrible data storage system, imo. And the performance of SQL Server-type data storage, especially on small devices like RPIs, can't hold a candle to a parquet-based system.) @Teppo Kurki, @Scott Bender
The list could be as long as the number of paths on the server. And the number of capture regimens is nearly infinite (captureAnchor, captureThisIsAFairyTale, etc.) This idea stemmed from a desire to capture AIS data of passing vessels and correlate various parameters, such as SOG, COG, distanceToSelf, to my boat’s heave, wave height, and period. I would like to present an empirical argument to local authorities, urging them to take action regarding no-wake enforcement and potential no-wake zone extensions. I soon realized I could do much more than that, and now use it for archiving and storing Signalk data for four or five regimens.)
I use Parquet/file-based system because InfluxDB is a horrible data storage system, imo. And the performance of SQL Server-type data storage, especially on small devices like RPIs, can't hold a candle to a parquet-based system.) @Teppo Kurki, @Scott Bender
