Hi Christian
Sorry for the late reply. I've just rerun your aggregations and your data should be available again. It's seems to be the same issue with our boundary conditions. We are working on a fix for our algorithms that handles these conditions but you should know that some of your features are reporting what seems to be uninitialized values (namely the value long.MinValue or -9223372036854775808) and when our fix is put into production these values will be accepted and will probably skew your resulting data a bit. Fair warning :)
Hope this helps and I apologize for not having a stable fix in place just yet.
Soren
EQATEC Team
Hi Christian
Thanks for forwarding this information, I have been in contact with Lukasz directly and given him a bit more context on the issue. We have a fix ready for deployment on this which should be rolled out tomorrow and that should bring an end to this inconsistency.
Would it be okay to skip the manual updating of your data until we have the fix in place? I'd like to avoid having to repeatedly go through these manual steps. You will not have updated data but you can still see existing data. If you need a manual update before the fix is in place, just let me know and I'll see that it gets done
Soren
EQATEC Team