Downloaded off device that image was taken with via Image Capture

  3942cf85f43282ece05ee01ef82f3b245e1638e6  IMG_2273.JPG

  0271267eb3fe02a27398e20e285cf14a26333510  IMG_2273.JPG

...

Running this through exiftool, the image downloaded via icloud.com/photos has the following EXIF stripped which is the likely cause of the above change:

  GPS Latitude Ref          
  GPS Longitude Ref         
  GPS Altitude Ref          
  GPS Time Stamp            
  GPS Speed Ref             
  GPS Speed                 
  GPS Img Direction Ref     
  GPS Img Direction         
  GPS Dest Bearing Ref      
  GPS Dest Bearing          
  GPS Date Stamp            
  GPS Altitude  
  GPS Date/Time 
  GPS Latitude  
  GPS Longitude 
  GPS Position

  exiftool -gps:all= IMG_2273.JPG

http://www.amazon.com/gp/help/customer/display.html?nodeId=2...

I have nothing else on my cloud drive.

While not on that list, it seems raw files are supported

Currently the unlimited photo storage benefit includes most major image file types: JPEG, GIF, (both animated and non-animated), most common TIFFs, RAW, PNG, and BMP.

This means at this time the .nef, .rw2 and .orf will be considered as unsupported format and will count against cloud drive storage limit.

For more information about Cloud Drive Photos & Videos file requirements, go to:

https://www.amazon.com/help/clouddrive/photos/filerequiremen...

I've forwarded your comments as feedback to our Amazon Cloud Drive team that you want .NEF file type images to be included in the unlimited photo storage benefit so that they aren't counted against your Cloud Storage quota. We're adding more file types to the unlimited photo storage feature, and file types not compatible now may become compatible in the future.

It's OneDrive for Business (i.e. SharePoint) that sometimes modifies uploaded files. To the best of my knowledge, OneDrive Consumer (http://onedrive.com) operates no differently than `rsync` would.

Yeah, I know. Sigh.

"The New Microsoft" seems to be making better decisions overall, but it apparently didn't learn anything from the early-2000s ".net branding clusterfuck" which conflated their runtime platform, development tools, consumer-facing single-sign-on, and a few dozen other things in the mind of the public.

Perhaps out of hope but more likely Stockholm syndrome, over the last decade I seem to have got stuck in a cycle of: Blind love and hope for a new product of theirs, utter disappointment at the resulting clusterfuck after a week, hatred, switch to something else, miss it, go crawling back.

Only just broken out of this loop but to be honest it knackered my productivity badly over the years.

Ultimately I'm a sucker I suspect but the revelation that FreeBSD hadn't actually poked me in the eye once in the last decade had turned my hand finally. That and ruby.

Yes I got tangled in DNA, ATL etc as well. Nothing but regret.