4 ms·

If you are looking for some entertainment, read the City Attorney's attempt to explain the data that was being collected: https://timesofsandiego.com/wp-conten

If you are looking for some entertainment, read the City Attorney's attempt to explain the data that was being collected: https://timesofsandiego.com/wp-content/uploads/2020/01/streetlights.pdf https://timesofsandiego.com/wp-content/uploads/2020/01/stree...

munk-a 6y ago
I particularly like the "What does processed data look like" and they just have a picture of some random hexadecimal digits which is accurate I guess, but that's what all data looks like if expressed in hex.
- est31 6y ago
  Which now makes me wonder what the data behind the hex is. 09 00 ba 8a b6 f7 42 c8 8f d0 aa 8e bf f5 99 b6 5a f2 42 26 Oc 92 25 4a 14 2f 6d fc ee e7 c3 f3 e7 19 82 a0 14 6f dc 7b Oc b8 0e 11 e7 5d c5 0d a0 19 bb 97 32 79 13 11 d2 af 8e fc Oc ee 29 af c6 8d 3c 59 9f 73 23 ab f6 58 22 ae aa fd 30 c5 0e f5 fO d1 1f 31 00 ec 6d e6 7d 53 a9 36 2a 8d Of 46 8e 48 10 76 20 ee ac 87 af 7b 2a ec 85 f8 b9 88 43 60 78 6S a6 ea 13 b8 b8 93 d8 62 25 c2 d2 f4 c7 e4 7a ad 2d lb a6 00 b7 36 1f ca 1c 43 cf 5f c3 5b 7d 3f da 2a 41 6f 6b fb 05 ed ff cc Putting it into hex to ascii converters doesn't yield anything useful. Putting it into a frequency analysis tool [0] doesn't give any special patterns either. 8 bytes are present 3 times, 25 bytes 2 times, and 86 bytes 1 time (total 160 bytes). I inputted a 160 long sequence from hexdumping urandom and I got 5 bytes present 3 times, 27 bytes 2 times, 91 bytes 1 time. Not a statistician but it seems pretty close. [0]: https://www.dcode.fr/frequency-analysis https://www.dcode.fr/frequency-analysis
  - munk-a 6y ago
    It's way too little data to get anything useful out of unless it was intentionally seeded. I am a bit sad it didn't decode as "Yea we know this is just hex but it looks fancy" since that would've been a pretty good get from whoever prepared images for the document. Also yea - it's probably not going to text decode trivially since there are random null bits in the middle. My guess is that it's some random data from an image off the camera - but it could also be a snippet of environmental information.

munk-a 6y ago

I particularly like the "What does processed data look like" and they just have a picture of some random hexadecimal digits which is accurate I guess, but that's what all data looks like if expressed in hex.

est31 6y ago
Which now makes me wonder what the data behind the hex is. 09 00 ba 8a b6 f7 42 c8 8f d0 aa 8e bf f5 99 b6 5a f2 42 26 Oc 92 25 4a 14 2f 6d fc ee e7 c3 f3 e7 19 82 a0 14 6f dc 7b Oc b8 0e 11 e7 5d c5 0d a0 19 bb 97 32 79 13 11 d2 af 8e fc Oc ee 29 af c6 8d 3c 59 9f 73 23 ab f6 58 22 ae aa fd 30 c5 0e f5 fO d1 1f 31 00 ec 6d e6 7d 53 a9 36 2a 8d Of 46 8e 48 10 76 20 ee ac 87 af 7b 2a ec 85 f8 b9 88 43 60 78 6S a6 ea 13 b8 b8 93 d8 62 25 c2 d2 f4 c7 e4 7a ad 2d lb a6 00 b7 36 1f ca 1c 43 cf 5f c3 5b 7d 3f da 2a 41 6f 6b fb 05 ed ff cc Putting it into hex to ascii converters doesn't yield anything useful. Putting it into a frequency analysis tool [0] doesn't give any special patterns either. 8 bytes are present 3 times, 25 bytes 2 times, and 86 bytes 1 time (total 160 bytes). I inputted a 160 long sequence from hexdumping urandom and I got 5 bytes present 3 times, 27 bytes 2 times, 91 bytes 1 time. Not a statistician but it seems pretty close. [0]: https://www.dcode.fr/frequency-analysis https://www.dcode.fr/frequency-analysis
- munk-a 6y ago
  It's way too little data to get anything useful out of unless it was intentionally seeded. I am a bit sad it didn't decode as "Yea we know this is just hex but it looks fancy" since that would've been a pretty good get from whoever prepared images for the document. Also yea - it's probably not going to text decode trivially since there are random null bits in the middle. My guess is that it's some random data from an image off the camera - but it could also be a snippet of environmental information.