...
The current lat/long/timestamp format is replaced by just a hash.
So this:
| Code Block |
|---|
"concern_points": [ |
...
{ |
...
"time": 1589224427000, |
...
"longitude": 1.00000919, |
...
"latitude": 2.00000943 |
...
}] |
becomes this:
| Code Block |
|---|
"concern_ |
...
point_hashes":[ |
...
“87e916850d4def3c”] |
and an example with multiple hashes looks like this:
| Code Block |
|---|
"concern_point_hashes": ["e090295d8e58b7de", "92c0e4f2d757c2a8", "755d22f05c13397a"] |
The value of the hash is computed in exactly the same was as on Safe Patths (see above). Note that changing the cost value will result in changes to the hash values produced, so as we tune the cost value to the optimal value, this will require careful co-ordination between Safe Places and Safe Paths.
...
For compatibility reasons as we work through this change, our plan is to add the hash first, and then remove the other points later - so for an interim period during MVP1 development, we may output data like this:
| Code Block |
|---|
"concern_points": [ |
...
{ |
...
"time": 1589224427000, |
...
"longitude": 1.00000919, |
...
"latitude": 2.00000943 }], |
...
"concern_point_hashes": ["e090295d8e58b7de"] |
This will allow both old & new versions of the app to work with Safe Places. But we aim to move to the final format before we launch MVP1.
...