Blog posts tagged geo

SFO Museum flight data records now available as GeoParquet exports

This is a short blog post to announce the availability of flight data for of the over 8.4 million (and counting) flights that have traveled in and out of SFO, since 2006, as GeoParquet files.

This is a blog post by aaron cope. It was published on January 07, 2025 and tagged flightdata, geoparquet, geo and duckdb.

Small focused tools for visualizing geographic data

This is a blog post about a series of small, purpose-fit web applications that can be run from your local desktop (or a remote server, if necessary) to visualize geographic data in a map. The first application lets you visualize GeoJSON files, the second SQLite databases containing MBTiles data and the third GeoParquet files. These are tools which were written to address specific use cases for SFO Museum but are sufficiently generalized, even though they each only try to do one thing well, that we are sharing them in the spirit of generosity.

This is a blog post by aaron cope. It was published on October 02, 2024 and tagged maps, geo, geojson, mbtiles, geoparquet and golang.

Updating the SFO Museum Wayfinding Service - Interface changes, WebShare and Nearby

Since the last blog post about adding custom publications for wayfinding routes we’ve made the following changes and improvements: Lists and thumbnail views for route steps, galleries and public art works along a route and objects from the SFO Museum Aviation Collection related to a flights; When supported by the browser the Web Share API has been enabled for linking to (and sharing) individual routes; The new “nearby” feature allows you to find galleries, public art works and other waypoints close to arbitrary points inside the SFO terminal complex.

This is a blog post by aaron cope. It was published on July 03, 2023 and tagged wayfinding, nearby, ios and geo.

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.