In an article “Why Geo Will Embrace The Cloud in 2010” in Direction Magazine, Brian Timoney of the The Timoney Group looks at the emerging cloud computing arena and poises the question, fad or not? Putting that question aside for the moment, part of Brian’s article really struck a chord with me – “IT is suffocating GIS.” As a former statewide GIS coordinator, I’ve seen all too many enthusiastic GIS professionals sucked down this path. Brian articulates something rarely discussed – issues like burn-out in the long since changed role of GIS managers. Are we properly preparing GIS professionals for this aspect of their GIS career? Here is an excerpt of Brian’s article: Continue reading
Today I’m getting on my soapbox. I’ve long been a vocal advocate of open public data in the geospatial arena. The “open” provides us all the opportunity to build shared spatial data infrastructures so critical to addressing public, private, and broader societal needs. I’m concerned that even with the most open of data, we may yet be compounding essential problems regarding a critical goal of spatial data infrastructures: authoritative and consistent data. Consistency is key.
For example, in Jonathan Feldman’s recent article “How To Fix The GIS Data Mess,” he pleads for consistent data shared among all potential users. In my own experience, beyond accuracy and unfettered access to geospatial data, consistency of those data among users is critical. When agencies and organizations rely on geospatial data for critical decision making and those data differ, the decisions based on those data will necessarily be different, notwithstanding the best intentions.
Are emergency responders and non-profit agencies looking at different authoritative data sources to deploy rescue efforts to save your pets and family members? Are construction crews, development companies, city officials, and recreational groups looking at different data sources when trails are cleared for a building project? Data consistency is vital – for public safety and for the public interest. Consistent data (and implied shared maintenance) is key to helping make consistent decisions and controlling costs.
I am a big fan of efforts such as Open Street Map (OSM) in democratizing geospatial data. OSM is an effort to be applauded. Clearly, its sweeping early successes, particularly in areas of the world where geospatial data are less public than the US, demonstrates that people are ready and eager to create and support open data sources. I am myself. But I lend a word of caution as well… What do we do when other authoritative data that are open already exist? How do we determine which is THE authoritative? How do we share maintenance? These questions remain largely unanswered.
Members of the National States’ Geographic Information Council (NSGIC) are working with public and private organizations at all levels to address these very questions.
In Indiana for example, the community is working together to overcome institutional obstacles and build a statewide spatial data infrastructure that is open and consistent (see the Indiana Geographic Information Council). Local agencies are providing data publicly, such as street centerlines and parcel boundaries, and the state is integrating and publishing rather than duplicating those efforts. The State is contributing as well, not only through coordination and infrastructure but also with statewide data sets such as aerial photography that make sense to maintain at broader coverage. And the effort doesn’t stop there. With university participation, those data are made public (view and download) through the IndianaMap. They are provided to federal agencies, such as U.S. Census for map modernization. In recognition that not everyone comes to government sources for their decision-making, statewide aerial photography (2005) was shipped to Google and Microsoft to integrate into their map services.
Such a model holds out a glimmer of hope that statewide, national, and international spatial data infrastructures are not only possible but also within reach. However, even with such open data, when the process is ill-defined and under-funded we may miss the target. How, for instance, will the IndianaMap data be incorporated into other open source efforts the likes of OSM? With a desire by all parties, how might maintenance be addressed? These questions remain unanswered.
We must continue to strive for solutions which focus on process. Consistent data are vital if geospatial data are used to solve problems at the most local to the most global of scales. While “any data” may be better than no data at all, the preponderance of inconsistent data may be our industry’s Achilles heel. There are inherent problems when local data (cities and counties) differ from state data, differ from federal, private, non-profit, and open data. That is why a National Spatial Data Infrastructure is necessary.
National and statewide GIS coordinating bodies have sought for some time to build statewide and nation-wide cadastre, or parcel, frameworks. The Mapping Science Committee – National Research Council cite the many benefits of having a national parcel database in its report, “National Land Parcel Data: A Vision for the Future.” In Indiana, a statewide parcel database may be used for such things as quickly identifying affected property during large natural disasters, such as flooding and tornados. A national (as well as statewide) fabric of land data has been elusive as it inherently relies on the most local of sources of those data – counties, parishes, cities, and towns. Reasons technical, political, financial, and institutional can all be cited as reasons why we don’t already have a national cadastre. While there is still a long row to hoe, Indiana appears to be slowly overcoming those hurdles with the IndianaMap.
With quiet announcement this week, the IndianaMap partners released the first view of a multi-county parcel database. The counties and the State have entered into IndianaMap partnership agreements, in which the counties provide parcels (limited attributes), address points, street centerlines, and administrative boundaries delivered through web map feature services (WFS), and the state provides a bit of seed funds to help establish the WFS, aggregate the data statewide, and channel it out through the IndianaMap to agencies, the original providers, and the public. It is important to note the state also provides a couple hundred statewide data layers available to local governments through the IndianaMap. This week’s view is the very first in what promises to still be a lengthy process, and I’m told it is provided “warts and all.” No matter how humble, it demonstrates a complete flow-through of the data in this process and proves the concept that a statewide (and I’d extend, national) public land parcel fabric is indeed accomplishable. This view shows parcels extending across Kosciusko and Wabash counties. In all, more than 70 (of 92) Indiana counties have agreed to participate.