Where I work, we have developed a nuanced philosophy to describe the niceties of collecting data, managing it, validating it, and preparing it for use: “Data is hard.”
This was brought to light in a very public manner by the vandalism that was displayed on basemaps produced by Mapbox. The responses by Mapbox and their CEO, Eric Gendersen, are good examples of how a company should respond to such incidents. Kudos to him and the team at Mapbox for addressing and rectifying the situation quickly.
Speculation quickly ran to vandalism of OSM, which is one of the primary data sources used by Mapbox in their products. That speculation was backed up by the edit history in the New York area, but it is interesting to note that the vandalism was caught early in OSM and never came to light is OSM itself. In this case, the crowd worked as it was supposed to.
The call for maps for the 2017 GeoHipster calendar has closed and review is underway. I haven’t begun collating the responses yet, so I have no idea how it will turn out, but I can say that, for me, the process so far has been personally rewarding.
I was not involved in the making of the 2015 calendar. When it came time to considering doing one for 2016, I volunteered to coordinate the process; with no idea what to expect. We had quite a response and I was impressed with the quality of the work received. Because it was my first time through, I was pretty consumed by the process and probably didn’t get to give as much consideration to the art that was before me.
Back in May, I had the honor of being appointed to the newly established Maryland Council on Open Data. The Council had its inaugural meeting in Baltimore yesterday and was heavily attended, including attendance by Governor Martin O’Malley. I’ll discuss his remarks to the group later.
As the first meeting of a new group, it went off largely as I expected. The agenda consisted primarily of an overview of the establishing legislation, a review of ethics requirements, demos of the existing open data portals, discussion of the history of open data in Maryland, and remarks from the Governor.
The first event was one of those serendipitous things that turned out to be pretty awesome. It was personally very influential on me and changed the focus of a lot of what I was doing with geospatial and with programming. It’s probably the best single geospatial event I’ve attended in the last five years. The fact that FOSS4G will have already drawn a like-minded crowd to Portland should bode well for JS.GEO. My own attendance is still in question due to a number of factors but I highly recommend adding this to your schedule if you can.
I got word today that Esri is planning a one-day [Developer Summit] in conjunction with the 2014 Federal GIS Conference. It appears that the DevSummit will happen on the Wednesday immediately following the Fed Conference (which runs on the Monday and Tuesday) and will be focused on the issues and challenges that are unique to developing applications with Esri technologies for the Federal Government. I spoke with Jim Barry, who told me the DevSummit has come together rather quickly and Esri hasn’t had time to do its usual data gathering to prepare for such an event. As a result, they are canvassing the developer community for input on topics they should cover. Here are some things I suggested:
UPDATE (12 March 2014): The situation with JS.GEO 2014 seems to be a bit fluid and the information originally posted here is no longer accurate. As indicated by Steve Citron-Pousty, the current goal is to have the event occur with FOSS4G in Portland, though that does not appear to have been finalized. In short, don’t book travel yet.
It’s been a while since I’ve posted as the usual wind-down of summer and wind-up of the school year has had me otherwise engaged. What follows are few developments over the past few months that have floated through the transom of my geo-awareness.