ScanOrganic Schema about eddn HOT 5 CLOSED

It seems like it would be fairly simple to require that clients check that Analyse scans have the same SystemAddress and Body as a prior scan for the same Genus (as long as a prior values have been recorded during that play session). This may lead to some dropped Analyse scans but we'd probably still be able to capture the majority of them.

Or am I misunderstanding the nature of the bug?

from eddn.

I'm not 100% sure. I should be able to find some examples or reproduce the issue. I'll do that today

from eddn.

Three scan events are generated.

Log -- First scan
Sample -- Second scan
Sample -- Third scan
Analyse -- After the burn animation

The analyse event is triggered when the animation completes. If the CMDR boards their ship before the animation is finished, then the event will wait until next time the Organic Scanner is activated and the animation completes, which could be the other side of the galaxy.

In all cases the BodyId and the SystemAddress have the correct location recorded in the event.

Only the anaylse event can occur on a different planet.

So the sender needs to make sure that if they enrich the record with Lat/Lon BodyName and SystemName that they match with the BodyId and SystemAddress on the event.

It may be simpler to not send analyse events as the lat/lon cannot be trusted, because the position could be anywhere on the same planet. Without identifiying information its not all that useful and the data will already have been recorded in the second Sample Event so nothing is lost by skipping it.

from eddn.

With that info, the "analyse" scantype appears to me to be superfluous data which can be safely omitted altogether as well.

from eddn.

Agreed

from eddn.