Revolution #11: The Holiday Season

With the holidays soon upon us, I wanted to briefly reflect on the pattern of users we’ve seen over the year – it’s been very busy, and very exciting.  The takeaway is, we had 944 users put in 3,098 requests for data since we went live. Not just surprising, but shocking to us that we’ve seen […]

Revolution #10: System Resilience

One ongoing challenge we face is preparing for large amounts of system demand – which can be very spikey.  Because of the system design of GeoQuery, we effectively have three potential points of failure: Front end server – The website people see (geoquery.org and the data front-ends). Database server – What the front-end pings to […]

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 #6: Boundaries and Why They Matter

Today’s revolution focuses on an upcoming project at GeoQuery, the GeoBoundaries team, and dives into why administrative divisions aren’t boring and actually matter! Every place in the world has some sort of administrative hierarchy. I live in the 23236 zip code, which is located in Chesterfield County, in the state of Virginia, within the United […]

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 […]