I had a support ticket with FD about this, and they kindly referred me to this forum. So here we go 
Several community tools use E's journal files to listen for events.
When working with scan events, there's an inconsistency that makes bulk operations on the event log very cumbersome.
"Scan" events do not store a systemname, but the "BodyName"
"FSSAllBodiesFound" events do not store a "BodyName" but the "SystemName"
At a first glance, that makes sense for the "FSSAllBodiesFound" event. But this makes it really hard to correlate "Scan" events to the corresponding "FSSAllBodiesFound" event.
It looks as if the real problem is that "Scan" events do not store the system name. You now have to do crazy substring and contains operations to find scan events that belong to the same system.
Would love to see this fixed. Especially as we currently rely on tools to help us with the ongoing Trans-Galactic-Metalicity-Survey during the Distant Worlds 2 expedition!
I know, community and FD need to check for potential backwards compatibility issues, as this would change the signature of "Scan"-event objects, then again, it's JSON
So long, thanks for providing us with a great game and looking forward to hear from you!
Several community tools use E
's journal files to listen for events.When working with scan events, there's an inconsistency that makes bulk operations on the event log very cumbersome.
"Scan" events do not store a systemname, but the "BodyName"
"FSSAllBodiesFound" events do not store a "BodyName" but the "SystemName"
At a first glance, that makes sense for the "FSSAllBodiesFound" event. But this makes it really hard to correlate "Scan" events to the corresponding "FSSAllBodiesFound" event.
It looks as if the real problem is that "Scan" events do not store the system name. You now have to do crazy substring and contains operations to find scan events that belong to the same system.
Would love to see this fixed. Especially as we currently rely on tools to help us with the ongoing Trans-Galactic-Metalicity-Survey during the Distant Worlds 2 expedition!
I know, community and FD need to check for potential backwards compatibility issues, as this would change the signature of "Scan"-event objects, then again, it's JSON
So long, thanks for providing us with a great game and looking forward to hear from you!