Geotagging at SFO Museum, Part 6 – Writers
So far, we’ve got a map and a camera, a global search endpoint, a simple way to query for and display images and enough information to display already geotagged images correctly. Importantly none of these things are specific to our museum or any other institution. In fact there’s nothing about go-www-geotag that is specific to the cultural heritage sector at all. You could use this tool to geotag any set of images. But what about saving the geotagging information that the Leaflet.GeotagPhoto extension produces?
This is a blog post by aaron cope. It was published on April 30, 2020 and tagged sfo, collection, geotagging and golang.
Geotagging at SFO Museum, Part 5 – Images
If the go-www-geotag application is designed to be agnotic to the details of any one user’s data sources how does it know where to find and load the images it’s meant to geotag? Isn’t this exactly the problem I described in the first post in this series, a scenario where the go-www-geotag application is required to know about an infinite number of image sources? Rather than trying to support a potentially infinite list of image sources we’ve decided to require the use of the oEmbed standard as the means by which images are identified and loaded in to the application.
This is a blog post by aaron cope. It was published on April 29, 2020 and tagged sfo, collection, geotagging, oembed and iiif.
Geotagging at SFO Museum, Part 4 – Search
But what if you want to center the map on a different place and don’t already know its latitude and longitude coordinates? What if you need to jump around to a bunch of different places all over the world?
This is a blog post by aaron cope. It was published on April 28, 2020 and tagged sfo, collection, geotagging, placeholder and search.
Geotagging at SFO Museum, Part 3 – What Is the Simplest Thing?
I call this the “building with two-by-fours” stage of development to highlight the importance of not just building things quickly but equally being able to disassemble and rearrange them just as easily. Sometimes this happens at the expense of elegance and finish but that doesn’t diminish their importance or a commitment to address those things.
This is a blog post by aaron cope. It was published on April 27, 2020 and tagged sfo, collection, geotagging and golang.
Geotagging at SFO Museum, part 2 – First Steps
In the end we may deploy this application for staff as a hosted website on the internet but we would like to have the ability and the flexibility for staff to also run the application locally, from their desktop. The majority of museum staff are not developers and won’t know how or be able, or want, to install the external dependencies that might be necessary for an application written in another programming language to run.
This is a blog post by aaron cope. It was published on April 24, 2020 and tagged geotagging, sfo, collection, golang and maps.
Geotagging Photos at SFO Museum, Part 1 – Setting the Stage
This is the first of multi-part blog post (11 in all!) about geotagging photos in the SFO Museum collection. It’s also a blog post about how we’re doing that work and why we’re taking a longer road than we might otherwise to get there. Over the course of the next couple weeks we’ll post one short blog post a day focused on a specific step, or area of concern, in that process. This first blog post will set the stage and outline some of our motivations for seeing geotagging photos in our collection as a chance to address larger issues in the cultural heritage sector.
This is a blog post by aaron cope. It was published on April 23, 2020 and tagged sfo, collection, geotagging and nypl.