The main issue is that Frontier doesn't provide a way of scanning a body and generating a "zero signals" entry in the journal. Which means once a signal is attached to a body we have no way of removing it if that body changes to not have signals in the future.Here's an observation and some questions.
I visit Pueliae MJ-H d10-1 (https://www.spansh.co.uk/system/48628829915), and from direct observation (FSS) I learn that AB 1a has 1 bio and 3 geo signals, and that there are no other bio signals in the system..
When I check that with Spansh, I see that the data updates almost immediately, and the relevant page gets a 'updated X minutes ago'.
But I also find that the AB 1b entry (https://www.spansh.co.uk/body/288230424780541659) says '5 bio signals', which is not matched by the game information. This data also appears to be several years old.
I've seen this before, but I've never been entirely certain of the details that involve my own actions. But it seems like old information that has been changed (i.e. game info is no longer the same as the data stored in the database) doesn't get updated. Some seems to change: the AB 1a entry is said to have been updated shortly after my FSS, but the AB 1b does not appear to have changed.
Question: Is this actual and permanent behaviour or is it just something that happens close to new info being provided. (I'm thinking: some info may be easy/cheap to update and is updated on the fly, while other is more expensive, and isn't changed until a later batch run.)
Question: Is this easily fixable? (I suppose it may be technically fixable, but old content would probably remain affected by it, so I suppose the answer is 'yes/no but ...'.)
Question: If this is already known, how great deal of data is affected? I suppose I'm asking if there are any known error rates. That is, if I tried to count the number of known Electricae Radielem is some part of the galaxy, any result would need to be stated as 'X bodies ± Y bodies', where Y is the estmated number of changes that didn't lead to a database modification.
You can as an alternative filter on signals_updated_at in the search and make sure the signals only come from the last few months, that should filter out any old data which we can't easily fix.