These events are also kept for
Posted: Tue Feb 11, 2025 3:43 am
Someone on the call asked whether that number could be reduced farther by normalizing the address components. That’s an idea, but in practice the component identifiers require more space than the actual values themselves. Best just to leave it denormalized (but multi-value compression can be used to reduce the table size).
The associative table linking Location and Individual requires 36 bytes per Individual per year. Assuming 14 years on the active list and the same 9x archive scaling, Location data requires 470 GB and archived location data 4.1 TB.
Finally, the Location Events are similar to the Naughty-Nice brazil whatsapp number data events. Many fewer are stored because the focus is on determining where an individual will be on a single day. Instead of 300 events per day, they get an average of less than 10 total. two years for research purposes, for a total of 3 TB. I presented my thoughts to the team and the feedback was overwhelmingly positive. They said that they could take it from there. I’ll admit I was disappointed that I wouldn’t be participating in the project through to its conclusion, but I was honored to be asked to consult at all.
Just before that final meeting concluded, I asked if I could share the experience through my blog. They said that it was fine, but that the story would have to be reviewed and approved first. There might need to be some redactions before it goes public. I was concerned but they told me not to worry about it. They told me not to worry about a lot of things. They said that I wouldn’t remember what had been redacted. I wouldn’t even notice.
The associative table linking Location and Individual requires 36 bytes per Individual per year. Assuming 14 years on the active list and the same 9x archive scaling, Location data requires 470 GB and archived location data 4.1 TB.
Finally, the Location Events are similar to the Naughty-Nice brazil whatsapp number data events. Many fewer are stored because the focus is on determining where an individual will be on a single day. Instead of 300 events per day, they get an average of less than 10 total. two years for research purposes, for a total of 3 TB. I presented my thoughts to the team and the feedback was overwhelmingly positive. They said that they could take it from there. I’ll admit I was disappointed that I wouldn’t be participating in the project through to its conclusion, but I was honored to be asked to consult at all.
Just before that final meeting concluded, I asked if I could share the experience through my blog. They said that it was fine, but that the story would have to be reviewed and approved first. There might need to be some redactions before it goes public. I was concerned but they told me not to worry about it. They told me not to worry about a lot of things. They said that I wouldn’t remember what had been redacted. I wouldn’t even notice.