In March of 2017, I gave the keynote address at TUgis, Maryland’s geospatial conference. Despite a few requests, I’ve been remiss about posting the text until now. The following lengthy block quote is the address as I had written it. It differs slightly from what I actually said, but I can no longer recall the on-the-fly changes I made. The original text is pretty close, though. It was written before some of the announcements by Microsoft and Amazon later in the year, but that simply serves to illustrate the pace with which trends discussed here are moving.
Continue reading “Belatedly, TUgis 2017 Keynote Text”
The year 2017 has been one of the most eventful of my career, but changes and developments were not limited to the professional sphere for me.
Continue reading “2017 Through the Rearview Mirror”
Over the summer, I wrote a post commenting on a piece of legislation known as the “Geospatial Data Act of 2017.” This legislation, or something similar to it, comes up every few years and has yet to get signed into law. In my post, I raised concerns about language that would have defined the use of private-sector entities in the collection of geospatial data assets covered by the legislation. I won’t re-hash the concerns I had at the time, but you can read my original post.
I am happy to say that the bill was re-introduced on 15 November 2017 (GIS Day 2017) as HR4395 and S2128. In this new version of the bill, the language that concerned me has been completely removed, and, with that, any serious objection I may have had with the bill.
Continue reading “Thoughts on the Updated Geospatial Data Act”
There was a time in my consulting career where I was providing GIS software and database support to the US federal critical infrastructure protection community. Part of that work involved ‘event response,’ which most often took the form of natural disasters. I never deployed, but a lot of my co-workers did.
Ground truth was always the biggest problem. We were always trying to get a sense of what conditions were like on the ground with as little latency as we could manage. With the technology of the 2003 – 2007 time frame, that was a significant challenge. Whether notepads or spreadsheets or custom data collection extensions deployed on ToughBooks, we tried just about everything we could think of. Some of my co-workers even managed a forward-deployed ArcIMS server to try to get anything useful out of the affected areas after Katrina.
Fast-forward to 2017 and we’re dealing with the unprecedented aftermath of Harvey in the Houston, Texas area. I find myself in the fortunate position of working for a company, Spatial Networks, that has a technology I wish we had back then. In addition to the technology, the company has the will to open it up and put it in the hands of whomever needs it.
Continue reading “Harvey and Fulcrum Community”
It’s been almost two weeks since I returned from FOSS4G 2017 in Boston, Massachusetts (USA), and I wanted to take a little time to regroup and get caught up before settling down to write about it.
It was a busy week, highlighted for me and the Spatial Networks team by the first-ever Fulcrum Live event. Held on the second day of workshops, it was our first user conference for Fulcrum, the mobile data collection platform by Spatial Networks. The event went off without issue, so we are very happy about that.
Continue reading “FOSS4G 2017 Recap”
Before delving into this topic, a big disclaimer is important: I am not a lawyer or a lobbyist or any sort of professional policy expert. The following analysis is based on 25 years experience providing geospatial consulting services to the federal government. You should read the full text of the bill yourself and draw your own conclusions.
On 23 June 2017, the American Association of Geographers (AAG) published a newsletter titled “A New Plot to Hijack GIS and Mapping,” which laid out AAG’s position on the Geospatial Data Act of 2017 . The title caught my attention, and, as is my preference, I stopped reading the AAG piece and went straight to the text of the bill.
Continue reading “Thoughts on the Geospatial Data Act of 2017”
I am following up my previous post with an extremely simple example using FME to kick off the refresh of a materialized view (matview) after a data import. I had never used FME prior to coming to Spatial Networks, but now I’m hooked. I’m having a really hard time finding things it can’t do.
As I mentioned in my last post, it’s really easy to refresh a matview in PostgreSQL using the REFRESH MATERIALIZED VIEW statement. This leaves open the possibility of automating the refresh as appropriate in an application or other process.
I decided to illustrate this using a basic FME example. Using the cellular tower data set from my past post, I extracted a table containing only the records for the state of Maryland. The towers data set contains the two letter abbreviation for the state, but not the full state name. So, I built a matview to join the state name to a subset of columns from the towers data set. The SQL for that matview is here:
I will use FME to append the records for the state of Virginia from a GeoJSON file to the PostGIS table containing the records for Maryland.
Continue reading “Refreshing a PostGIS Materialized View in FME”