A place to cache linked articles (think custom and personal wayback machine)
Ви не можете вибрати більше 25 тем Теми мають розпочинатися з літери або цифри, можуть містити дефіси (-) і не повинні перевищувати 35 символів.

2 роки тому
12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970
  1. title: More on geo-tagging photos with a time element
  2. url: https://rachelbythebay.com/w/2022/06/20/exif/
  3. hash_url: 0ccfb99277e4fb33d213df05598df960
  4. <p>
  5. Some readers have written in with questions about my
  6. <a href="https://rachelbythebay.com/w/2022/06/15/places/">photo geotagging post</a>
  7. from last week. One common question is whether the place name has ended
  8. up in the file's metadata somehow. The answer is: I don't think so. I
  9. did an "export as original" on the photo in question and ran it through
  10. a bunch of exif dumper tools and didn't find anything that suggested a
  11. name like that.
  12. </p><p>
  13. The EXIF data looks like this:
  14. </p><p>
  15. </p><pre>
  16. Create Date : 2014:06:16 13:02:15.202
  17. Date/Time Original : 2014:06:16 13:02:15.202
  18. GPS Altitude : 5.2 m Above Sea Level
  19. GPS Latitude : 37 deg 29' 6.13" N
  20. GPS Longitude : 122 deg 8' 53.30" W
  21. Circle Of Confusion : 0.004 mm
  22. Field Of View : 57.2 deg
  23. Focal Length : 4.1 mm (35 mm equivalent: 33.0 mm)
  24. GPS Position : 37 deg 29' 6.13" N, 122 deg 8' 53.30" W
  25. Hyperfocal Distance : 1.89 m
  26. Light Value : 15.4
  27. Lens ID : iPhone 5 back camera 4.12mm f/2.4
  28. </pre>
  29. <p>
  30. (Side note: that's
  31. <a href="https://en.wikipedia.org/wiki/Circle_of_confusion">an interesting term</a>,
  32. huh? Today I learned.)
  33. </p><p>
  34. Anyway, it's just a bunch of numbers, as you would expect. Something in
  35. the actual Photos app on the Mac and the equivalent thing on my phone is
  36. translating it to a name.
  37. </p><p>
  38. What's kind of nutty is that the same picture still shows "Facebook -
  39. Headquarters" when viewed on my phone. Really. Check it out:
  40. </p><p>
  41. <a href="phone.png"><img src="phone.png" alt="iOS 15.something or other view" align="middle"></a>
  42. </p><p>
  43. So, not only is there some mapping going on, but the phone and the
  44. computers (both of them) are looking at two different sources of data.
  45. I have to assume the phone has it cached, while the Macs must have
  46. flushed it and picked up the new value in recent times.
  47. </p><p>
  48. Or, who knows, maybe Apple is running multiple backends with disjoint
  49. geographical data sources. It wouldn't be the first time they had
  50. <a href="https://rachelbythebay.com/w/2013/02/04/maps/">terrible</a>
  51. <a href="https://rachelbythebay.com/w/2013/04/02/maps/">map</a>
  52. <a href="https://rachelbythebay.com/w/2013/06/18/hospital/">data,</a>
  53. right?
  54. </p><p>
  55. So here's another fun problem: how do you do a "fourth dimensional"
  56. geo-tag (that is, adding a time system) without revealing all of the
  57. places a person's been and when they were there? In other words, how do
  58. you do that without compromising privacy?
  59. </p><p>
  60. The best I can figure so far is that you'd send back a list of ALL of
  61. the place names for a given area and let the device figure out which
  62. times apply to which photos, and just discard the rest. Also, it should
  63. probably be "zoomed out" pretty far, such that only very coarse bounds
  64. are given to the server. Just return all of the mappings for all of the
  65. polygons or whatever inside some giant swath of space, and do all of the
  66. nitty gritty stuff on their device.
  67. </p><p>
  68. Otherwise, hey, it becomes pretty easy to track people after the fact.
  69. </p>