...
Just add a “points” parameter (e.g. “&points=4032”) to specify the number of data points that you want.
Data points are generated exactly 5 minutes apart.
Important Note: The tool includes a representative number “hashes” in the data, but these are random numbers, rather than properly computed hashes (to save compute resource). They should give a realistic model of hash storage for exposure notification performance testing - but they will not generate accurate exposure notifications
Some enhancements I’m considering:
Make timestamps a bit more variable: 5 mins +/- a random amount. This will make the data more realistic.
Allow data to be created up to time X, where X may be in the past. This will avoid overlapping data points in the case where someone installed the app some hours before they added the fake location data
Adding Make the hashes added to the import data correct (not random), so that the data can be used to test Exposure Notifications.
More control over the shape of the data that is generated - right now it’s a slow random walk. We could make it more predictable, follow specific paths/shapes etc.
...
There is no way to delete that data, other than explicitly deleting the app’s data (which will reset everything and require you to repeat onboarding), or a complet uninstall/reinstall of the app.
AFAIK there is no mechanism in the app to stop you overloading the database with far too many points, either from one upload with too many points, or from multiple uploads in sequence. If you put far more than 4000 data points in the app, it might start to behave oddly.
At the moment, Safe Places does not perform well with hundreds of location data points, and it is really really slow with 4,000 data points. This is reported as PLACES-492 - we understand the problem and are working on a fix, but until that fix is rolled out, you might want to keep data sets down to 1-2 days.
As per limitation above, the tool does not import compute the correct hashes into for the phone databasedata points. So it is not yet suitable for while it should offer realistic testing of exposure notification performance with a full data set, none of these points will actually trigger an exposure notification (and so you’ll need a few real points for that purpose).
Getting 14d Data into Safe Places
...