Add UAS (drone) tracking event: Remote ID Activity
#1169
+440
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jonrau-at-queryai
added
enhancement
jonrau-at-queryai
requested review from
floydtree,
pagbabian-splunk,
Aniak5,
mikeradka and
zschmerber
as code owners
|
I would suggest to rename it to drone_flights_activity, remote_id_activity as a name is not clear for anyone who is not working directly with drones. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue:
N/A
Description of changes:
As discussed in an OCSF meeting on 3 SEPT 2024 - there was a desire to bring IoT and drone/UAS related normalization into the schema.
This PR creates the
Remote ID ActivityEvent which captures details from the Remote ID specific described in ASTM F3411-22a: Standard Specification for Remote ID and Tracking such as the specific UAS/drone platform, operating areas, the operator themselves, and other relevant information that could be captured or logged by dedicated Counter-UAS or UAS monitoring devices and software.While a majority of the attributes were repurposed, several new attributes and objects were added into the dictionary to support modeling this.