Blog posts tagged golang
Using IIIF (with AWS) at SFO Museum
At the end of that first blog post about go-iiif we wrote “An ideal scenario is one where a museum could upload a set of full-sized images to a AWS S3 bucket, wait for Amazon’s computers to process each image … and then find a new set of images to download (along with a reasonable bill for services rendered) in a different S3 bucket.” Today, that is possible.
This is a blog post by aaron cope. It was published on February 12, 2019 and tagged iiif, golang and aws.
Sweet spots between the extremes
This is a technical blog post about map tiles, caching, third-party services, so-called “serverless” computing and sustainability. It’s also about improvements to open-source software for managing all of that stuff.
This is a blog post by aaron cope. It was published on November 07, 2018 and tagged aws, golang, whosonfirst, maps, nextzen and rasterzen.
Maps (and map tiles) at SFO Museum
Maybe these maps are simply a fail-safe and only used when nothing else works. Their value then comes from giving us the confidence to try a more sophisticated approach while still having a way to get home safely, so to speak.
This is a blog post by aaron cope. It was published on July 31, 2018 and tagged maps, nextzen, sfo, aws, golang and rasterzen.
Using IIIF at SFO Museum
This is a technical blog post about image processing. The short non-technical summary is that not only were we able to use open source software to simplify our image processing workflow (and reduce costs) but we contributed our improvements back to the project so that hopefully others in the museum sector may benefit from our work. Yay!
This is a blog post by aaron cope. It was published on July 18, 2018 and tagged golang and iiif.