Posts


Spatial data, software development, and flexible architecture
  • More is not always better

    My college years were spent studying rocks. While earning a degree in Geology, I was occupied with courses in physics, chemistry, and mathematics. These foundational sciences provided the context to begin to understand larger systems like climate, glaciology, and hydrogeology. I learned to deconstruct and explain outcomes by reducing them... [Read More]
  • Sometimes noise is the data

    In the mid 1960’s, two scientists from Bell Labs named Arno Penzias and Robert Wilson were trying to remove sources of interference in readings from a radio telescope to perform research. No matter what they did, a constant source of noise plagued their efforts. They went to great lengths in... [Read More]
  • Continually making myself obsolete didn't work

    I used to joke that my job was to continually make myself obsolete. In the current atmosphere of anxiety surrounding the threat posed by AI to job security, that old quip now sounds like an odd position to adopt. However, I think there’s a lesson to be learned. In spite... [Read More]
    Tags:
  • Simulating the 100 prisoners problem

    For this problem, there are 100 prisoners and 100 boxes in two separate rooms. Each box contains a slip of paper with a prisoners number in it. Each prisoner and box is numbered from one to 100. The numbers in the boxes are randomly shuffled. Each prisoner is then given... [Read More]
    Tags:
  • Dealing with GeoJSON feature collections in PostGIS

    One task I have come across repeatedly while building APIs or functions that accept GeoJSON is dealing with differing representations. The input data may be a geometry, a feature, or a feature collection. When utilizing PostGIS as a backend, I inevitably run into errors after naively feeding input data directly... [Read More]