Blog posts tagged javascript

Updating (and reverse-geocoding) GPS EXIF metadata

When I save an image of this view of the runways at SFO, from 2017, the newly created image’s EXIF data contains not only the date and the permanent URL for the map but also the latitude and longitude coordinates for the map’s center point.

This is a blog post by aaron cope. It was published on April 26, 2021 and tagged golang, exif, javascript, wasm, flickr, reverse-geocoding and webassembly.

Updating EXIF metadata in JavaScript (and WebAssembly)

One question that’s been raised about the camera/save button in zoomable images is whether or not the new image contains, or preserves, existing EXIF metadata information stored in the original file. The answer yesterday was: No. The answer today is: Not yet, but only because we haven’t enabled it and we will do that soon.

This is a blog post by aaron cope. It was published on April 14, 2021 and tagged golang, exif, javascript, wasm, zoomable and webassembly.

zoomable.images.js

We’ve updated the user interface elements that control how a static image can be made “zoomable” making them easier to use and more portable across a number of different settings.

This is a blog post by aaron cope. It was published on September 14, 2020 and tagged iiif, javascript and zoomable.

Geotagging at SFO Museum, part 10 – Native Applications

In the same way that we can wrap a traditional web application in a Go program, can we wrap that Go program in a native macOS application? Each platform has its own unique affordances and tolerances. A larger goal for the museum is recognizing the possibilities that each platform affords so that we might be able to treat them as a kind of “kit of parts” to be reconfigured as needed for future projects.

This is a blog post by aaron cope. It was published on May 18, 2020 and tagged sfo, collection, geotagging, oauth2, golang, javascript and macos.