Revolution #15: Code Spaghetti

I happened across a nice graphic over on codeproject.com that helpfully illustrates the types of development processes we use for GeoQuery. Enter “how much engineering does my software need”: Different elements of GeoQuery are engineered to different standards depending on two key factors: (1) if we believe it will be a long-term element of the […]

Revolution #13: “The Cloud”

We’ve had a lot of buzz around the office this week about the cloud, generally fostered by our discovery of paperspace (a cool startup that makes rolling your own computers in the cloud much easier).  We’ve dabbled with AWS, Google Compute, and a few other offerings before, but we’re constantly asked (at conferences and internally) […]

Revolution #8: Alternate Entry Points

Today’s revolution is a preview of a coming feature of GeoQuery we’ve been working on – the ability to “roll your own” entry points into the GeoQuery database. You can see an example (unless it crashes – beta!) at http://umd.geoquery.org . A big concern we have regarding the sustainability of GeoQuery is it’s ability to not […]

Revolution #5: The Pain of Projections

Projections in geographic nomenclature are the selected set of methods one uses to take things that exist on a 3D object (i.e., “The Earth”), and presents them on a 2D space (i.e., “Every satellite image ever taken”).  They are the bane of introductory courses, and computationally can be a beast to get right. Take, for […]

Revolution #4: Architecture

This Friday’s revolution is to go into a bit of depth on our system architecture. For the record – I am not, at all, a system architect. GeoQuery is built to, ultimately, provide a user with geospatial data aggregated to arbitrary boundaries.  While our public tool currently only enables pre-selected boundary files, behind the scenes […]

Revolution #2: From R to Python

I’ve been coding in R for most of my professional career – it’s flexible, quick, has a nice GUI (I love R Studio Server), and the volume of packages for statistical processing is amazing (even for spatial stats). …but I’m now making the transition over to Python. I’ve flirted with Python a few times in […]