Open KurtH96 opened 1 year ago
The event element of CoT messages is missing some fields. Those fields include: opex, qos, and access. I would like the qos field to be retained. Everything else is fine as is.
An example of expected CoT messages with redacted data:
<?xml version='1.0' encoding='UTF-8' standalone='yes'?> <event version='1.0' uid='...' type='...' time='...' start='...' stale='...' how='...' opex='...' qos='qos' access='access'> <point lat='0.0' lon='0.0' hae='9999999.0' ce='9999999.0' le='9999999.0' /> <detail> <marti> <dest callsign='ECHO'/> </marti> </detail> </event>
The CoT event provided from the server:
<?xml version='1.0' encoding='UTF-8' standalone='yes'?> <event version='1.0' uid='...' type='...' time='...' start='...' stale='...' how='...'> <point lat='0.0' lon='0.0' hae='9999999.0' ce='9999999.0' le='9999999.0' /> <detail> <marti> <dest callsign='ECHO'/> </marti> </detail> </event>
I am using the following versions of software:
The event element of CoT messages is missing some fields. Those fields include: opex, qos, and access. I would like the qos field to be retained. Everything else is fine as is.
An example of expected CoT messages with redacted data:
The CoT event provided from the server:
I am using the following versions of software: