This is typically called a “network service model.”
Typically, you will define a simple protocol. For your case, you could just say that the protocol is “one line per detection event, with zero or more coordinate pairs per line.”
The host would connect to the service, and receive the data. You can use simple TCP sockets for this.
More advanced mechanisms would use some RPC system (remote procedure call) or even try to expose the data over HTTP, but it sounds like that’s actually the wrong approach for your need.
You could do the same thing over USB if you could get the Jetson into Device mode (where it looks like a device to the PC.)
You would want the virtual device of the Jetson to expose either a virtual serial port, which would show up as /dev/ttyXXX (or COM#:) on the host PC, or some custom bulk transfer endpoint, which would have to use libusb (or the Windows 10 equivalent – Windows before 10 don’t have user-level generic USB access.)
I would go the networking path, because it is more flexible, allows multiple hosts to connect to the same device (if you want) and doesn’t depend on the under-documented “on-the-go” USB features of the Jetson.
Most languages (certainly C and Python) have simple tutorials for simple network servers and clients. Your Jetson would be a “server” creating a socket and listen()/accept()/send() to connections on some particular port (pick a number – 1234 is a fine port number for your server ;-) Your host would just call connect() and recv() to receive the data.
You will also want to familiarize yourself with socket() and perhaps getaddrinfo().