Blog posts tagged placeholder

Geotagging at SFO Museum: Protomaps, search and reverse-geocoding

Title image for Geotagging at SFO Museum: Protomaps, search and reverse-geocoding

The bad news is that, when you look closely, there really are that many moving pieces when it comes to something like geotagging photos. The good news is that nearly all of those moving pieces, from the underlying data to the tools to operate on those data, are within the reach of cultural heritage as low-cost and open-source alternatives to the commercial offerings. We may still need to stitch those pieces together to meet the needs of a specific institution but at least they are within reach now.

This is a blog post by aaron cope. It was published on May 03, 2021 and tagged golang, geotagging, whosonfirst, geocoding, reverse-geocoding, placeholder and maps.

Geotagging at SFO Museum, Part 4 – Search

Title image for 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.

Using the Placeholder Geocoder at SFO Museum

Title image for Using the Placeholder Geocoder at SFO Museum

This is a long and technical blog post. The short version is: It is now easy, possible and inexpensive to install and operate a “coarse” geocoding service, with global coverage, support for multiple languages and stable permanent identifiers using openly licensed data, both locally and in ☁️ the cloud ☁️. We’ve made some additional tools to complement this reality and waded through some of the muck of modern software development so you don’t have to.

This is a blog post by aaron cope. It was published on November 04, 2019 and tagged aws, geo, geocoding, pelias, placeholder, sfo and whosonfirst.

Syndication feeds for this weblog are available in the Atom 1.0 and RSS 2.0 formats.