![]() Upon clicking the OK button, the new exporting settings will be added to the instance. Once a format is chosen, a few additional options will be displayed that allow to control how and where to export the data. Two types of data can be exported: binary (for example the output image) and metadata (detections, events, etc.).įor binary data, the supported formats are mp4, jpg, png, RTSP, and RTMP.įor metadata, the supported formats are JSON files, json over mqtt, csv, and txt. The first step is to choose what data to exportĭepending on the choice, a list of different formats will be listed below. Custom Export Options ¶īy clicking the "Add Custom Export Options" button, you can add one or more exporting configurations, and enable/disable them as needed. For more information about parsing the inputs, see the Schemas or jsonexport.py in the exporters directory. Your program will then get required events as JSON strings through STDIN and you can parse it according to the available schemas. Then you just change the command field value to it. You can use any program written in any language of your choice (Python, C++, C#. Section E: Defines the name of the Exporter.The setting values can be used in the command. Section D: Defines the settings that will be displayed in the UI.Section C: Defines additional environment variables to be set for the command execution.Section B: Defines the command to run from CVEDIA-RT.0 stands for not registering (equivalent to a no line). Section A: Defines which events and versions to subscribe to.Their configuration is defined in a JSON file, that is loaded by RT: It is not required to write the exporter in Python, however, it is probably the easiest way of doing so.Įxporters are spawned as a separate process from the RT and communicate with RT through STDIN. Custom third-party integrations ¶Īs mentioned above, the JSON Exporter serves as an example for creating custom integrations. The JSON Exporter serves as a simple example of how to create custom integrations based on versioned JSON schemas. The exporters' settings are global and can be accessed from the main menu System -> Integrations:Įach exporter can be then enabled or disabled in the instance configuration: The JSON Exporter can also support image export on disk if numpy and opencv-python packages are provided.Įach exporter has a configuration file that allows exposing the required settings in the CVEDIA-RT UI. Integrations can be found in exporters directory.Ĭurrent exporters require Python3.6+ to run. To get the schemas, visit the following page: Schemas ![]() Each JSON schema is versioned and the exporters can negotiate with CVEDIA-RT the version to use. This enabled the implementation of specialized exporters used to integrate with external systems, by guaranteeing stability in the format also in future versions of RT. Starting from version 2023.3.0, CVEDIA-RT started supporting a standardized way of exporting events using JSON schemas. It's also possible to export data in various forms by clicking on Add Custom Export Options which would show you options to customize the name, data to export, format and so on.Ĭlick on the cog icon beside the instance name to access the Setup Window: ![]() You can also create your exporters to consume the events generated in the CVEDIA-RT. CVEDIA-RT provides the integration for third-party applications which would consume the data such as Video Management Systems (VMSs). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |