30 Jun 2008 - What is an SDI?
Overview
The most often quoted definition of a Spatial Data Infrastructure (see http://en.wikipedia.org/wiki/Spatial_Data_Infrastructure) is that it is “a framework of spatial data, metadata, users and tools that are interactively connected in order to use spatial data in an efficient and flexible way. Another definition is the technology, policies, standards, human resources, and related activities necessary to acquire, process, distribute, use, maintain, and preserve spatial data “[1].
The difficulty with this definition is that it provides little insight as to what the software component of the infrastructure might amount to, or what the benefits and objectives of the infrastructure might be.
If one looks at most SDI’s today they heavily emphasize a librarian view of the software infrastructure part (metadata collection and discovery are the primary points of focus), and as a result are inappropriate to support many of the use cases for which such an infrastructure might be deployed.
Why an SDI?
To address “what is an SDI” we need to think more on the function – the “why” of an SDI. Only then can we think more correctly about what such a thing might entail. Without being to grandiose, I think there are a number of reasons why government and the private sector might think to invest and build an SDI.
These include:
- It enables a local, regional, national or even a planetary accounting system on the state of the environment, by making visible the distribution and temporal variation in key environmental parameters from carbon emissions to deforestation.
- It enables the local, regional, national or even planetary response to emergency events whether caused by people or natural forces.
- It enables the more efficient interaction of corporations, government and citizens in the collaborative (and competitive) development of the built environment, from urban construction to mining, agriculture and energy production.
- It provides a vehicle by which government can meaningfully interact with its citizens at all levels on planned projects, programs and policies; enabling both the presentation of what is planned, as well as enabling direct feedback from the citizenry.
For many of you, much of this will sound like e-Government, and in fact one can simply look at SDI as no more than spatially enabling or geographically enabling e-Government. I prefer to think of it as e-Society, since while Government has a key role, so does the private sector and the agents of civil society.
What do we build?
With the objectives as above, what does that imply we should be building? Are the national and pan-national initiatives to build SDI such as the Canadian CGDI, the European INSPIRE, or the US NSDI being designed to address these objectives? Furthermore, with the rise of big search engines as players in the geo-space, what aspects should government and the private sector focus on in developing an SDI?
If we look at the “accounting system” view of SDI, we see that the key thing is to make the state of the environment locally, regionally, nationally, and globally, visible to all of us. This means it applies to a very wide range of data types over a wide range of scales. Most of this information is in some way spatially related, but this spatial relationship may be very implicit and not part of the actual data itself. So SDI must be concerned with access to all kinds of data that are only nominally spatial. Since much of this sort of data is to be found in government and private sector databases, an SDI must deal with data access for a wide range of databases and not just the nominally spatial ones. Furthermore, if we are to do the sort of “roll up” of information that is required in any sort of accounting system, we need access to the actual data, and not portrayals or presentations. Visualizations are important of course, but only if driven directly from the data, and only if available at various levels of the society and government. Finally, to make any sort of “accounting system” feasible, we will need appropriate models of the parameters that we are to report and measure – meaning we need public, shared schemas that deal with everything from forest cover, to floods, carbon emissions and water pollutants. This is a major undertaking, but so was the construction of a national highway system, a national broadcasting system or a national air transportation system.
If we look at the SDI as supporting the emergency response, we encounter similar issues, but with the additional requirements of tighter information security, and temporal responsiveness. Even more than in the case of the SDI as “accounting system”, we must see SDI as enabling the pushing of data change events to data consumers. A forest fire manager will of course want to request information, but that is of little use if first responders on the ground or in the air cannot supply new information “as it happens”. An SDI focused primarily on metadata and discovery cannot hope to support such activities.
SDI, as supporting emergency response, also entails the interaction of many levels of government and the private sector, including both national and international agencies. Recent events in Myranmar and Indonesia highlighted the need for quick and effective integration of information. This implies that information must be sourced in real time from a wide variety of locations, at a wide variety of scales, from citizens as well as professionals, and integrated on as needs basis. Again this cries out for common data models that are shareable across regions, provinces/states and nations. Some regions such as in the European INSPIRE are making encouraging moves in this direction. After all the parameters of a forest fire, flood or earthquake of interest to responders can readily be generalized over regions or nations. This is again not a small problem, but with costs for natural disasters in the hundreds of billions, and yearly losses in human life exceeding 100,000 people, the amount of money currently expended on SDI is still vanishingly small.
SDI, as supporting efficient collaboration of government, the private sector and civil society in the constructing the built environment, also calls for a re-thinking of traditional SDI initiatives. Fortunately, we are starting to see movement in this direction through the emergence and gradual adoption of Building Information Models (BIM). While nominally a “standard”, the key thing about BIM is a process that encourages early and continuous collaboration amongst all of the “actors” that contribute to the development of the built environment, including ordinary citizen, investors, construction companies, developers, owners, engineers (of many kinds), and architects. While most of these efforts have been focused on building design, there is no reason to draw such an artificial barrier. One can equally apply these ideas to the development of a highway, a mine, an airport or an entire city. SDI, as collaboration, again implies dealing with a wide range of information scales, spatial and non-spatial information, the need to support information push as well as information pull, and the development of common models for buildings, transportation systems, and entire cities. Big strides have been made in these areas by groups like the Smart Building Alliance, the German cityGML consortium and others. We need to see these initiatives as simply a part of the broader notion of SDI, and to think of how we provide direct support for things like projects, collaboration “spaces” and the integration of design information (buildings, transportation infrastructure etc) and what we nominally call “geography”. Governments and the private sector will spend close to $ 5 trillion dollars on construction in 2008. Even ignoring the immense soft benefits of spending this money in more environmentally sustainable and human friendly fashion, any improvements in efficiency must be measured in the billions of dollars annually.
SDI, as supporting communication with and amongst our citizens in relation to the actions of government, also requires a re-think of what SDI means. Many of the issues raised above are equally true for this use case. The notion of collaboration cannot be stressed enough. Government can use SDI to communicate new policies, new laws (e.g. changes in zoning or construction), and new projects to its citizens, and citizens can use that same SDI to make counterproposals, comments and suggestions. Again only some of this information need be explicitly spatial, but the spatial component is often the key to understanding how this information relates to you as an individual.
Many of you may look at this discussion and realize that these objectives are being better met today by the likes of Google Earth, Facebook and wide area games like Second Life. You may think that there is really no role, or only a diminishing role for government in the process, and I have had that view expressed to me by several members of national government agencies. I think this is not the case. Governments, the private sector and agencies of civil society have it their interest to work together to build information infrastructures that work for the betterment of the world. This cannot be left to just information companies as their ultimate interests must inevitably lie elsewhere. At the same time, we must recognize the immense contribution of these companies, and build them and their technologies into the SDI process itself.
Spatial information Infrastructures can make an important contribution to the security of our nations and the environment. We need to start thinking in the right direction.
No Comments | Leave a comment»
Comments
No comments yet.
Leave a comment
Blog Entries:
07 Oct 2008 - From the Age of Aerospace to… ?02 Oct 2008 - KML, GML and REST
16 Sep 2008 - GeoPresence
08 Sep 2008 - GeoEquilibria-There is no surplus in Nature
29 Aug 2008 - Geographic Entity Registries
01 Aug 2008 - GeoWeb and the State of the World
23 Jul 2008 - Virtual Globes as Essential Services?
07 Jul 2008 - Cascading and Federated WFS and the Concept of Geolinking
30 Jun 2008 - What is an SDI?
16 Jun 2008 - WFS - Schema Mapping is Key
05 Jun 2008 - KML Support
08 May 2008 - Looking ahead to GeoWeb 2009
21 Apr 2008 - Spatial Infrastructures, IFC & Collaborative Engineering
14 Apr 2008 - KML released as an OGC Specification
02 Apr 2008 - BIM/CAD/GIS Integration
13 Mar 2008 - Structuralism and Data Exchange
05 Mar 2008 - Building the GeoWeb in your own backyard
03 Mar 2008 - Davos of Geo in Vancouver
28 Feb 2008 - What are coordinates?
19 Feb 2008 - Does the invisible hand always get it right?
31 Jan 2008 - “Design for Test” in the GeoWeb
23 Jan 2008 - GeoWeb Local - GML in Local Government
15 Jan 2008 - GML Core and Extensions
04 Jan 2008 - GeoWeb 3D
21 Dec 2007 - What are the key issues for geographic information technology?
26 Nov 2007 - GML in the Back Office
19 Nov 2007 - CAD- BIM-GIS-Games Integration
07 Nov 2007 - What’s in a name? Searching for the right words
23 Aug 2007 - KML Placemarks as Observations
29 Jun 2007 - Where GML was right .. and wrong
17 May 2007 - From GML 1.0 onwards - a brief history
17 May 2007 - GML and Database Interoperability
10 May 2007 - GeoWeb Manifesto
09 May 2007 - Meltdown and the Maze - Toward a Real Time Geography
08 May 2007 - GML, KML, Sensor Data, Imagery
20 Apr 2007 - Transporting GML in KML
21 Mar 2007 - The Architecture of the GeoWeb
14 Feb 2007 - From Interoperability to Infrastructure
14 Feb 2007 - GML without Geometry
18 Dec 2006 - ebRIM gets the nod at the OGC
06 Oct 2006 - In praise of complexity
05 Oct 2006 - Infrastructure - the next step past interoperability
12 Jun 2006 - GML and ebRIM
21 May 2006 - Features, Observations and Authorization
21 Apr 2006 - Transfer and Transaction Models
12 Apr 2006 - Feature Catalogues/Dictionaries, GML and RDF/S
10 Apr 2006 - Genus Loci
04 Apr 2006 - GeoWeb and Survival Part II - Towards Environmental Security
04 Apr 2006 - GeoWeb and Survival
17 Mar 2006 - Schemas, Interoperability and RDBMS
14 Mar 2006 - SDI Concepts
05 Mar 2006 - GML Complexity Re-visited
05 Mar 2006 - Observations are for more than sensor data
05 Mar 2006 - Application Schemas Drive Profiles
25 Feb 2006 - The problem with XML
15 Feb 2006 - The importance of profiles
08 Feb 2006 - One person’s metadata is another person’s …
07 Feb 2006 - From Soup to Nuts
02 Feb 2006 - GeoRSS - GML in news feeds
31 Jan 2006 - Performance and the GeoWeb
27 Jan 2006 - Remote API’S, Web Services and the GeoWeb
19 Jan 2006 - GeoWeb 2006 - GeoWeb Grows Up
09 Jan 2006 - Dealing with time in GML
23 Dec 2005 - Dynamic
14 Dec 2005 - GML in the cockpit
01 Dec 2005 - SDI - What is it really?
25 Nov 2005 - GML is the same for all applications
25 Nov 2005 - Schemas and Profiles - whats the difference?
22 Nov 2005 - Schemas - why the big deal?
15 Nov 2005 - GML for Geographic Imagery
13 Nov 2005 - GML, and KML - Why the fuss?
10 Nov 2005 - Is GML a format?
09 Nov 2005 - Embedding GML in “foreign” grammars
03 Nov 2005 - Authentication and Access Control
03 Nov 2005 - OnStar in the era of the GeoWeb
03 Nov 2005 - Do we need to encode location in news feeds?
03 Nov 2005 - gMedia - Towards Geographically Aware Media
03 Nov 2005 - Where are we going?
02 Nov 2005 - Sample XSLT Style Sheet
02 Nov 2005 - Sample KML Output
02 Nov 2005 - Sample GML Data File
02 Nov 2005 - Styling GML to KML - XSLT
02 Nov 2005 - Simple Geometry Schema
01 Nov 2005 - Simple GML Geometry
18 Oct 2005 - Simple GML Geometries
18 Oct 2005 - Styling GML to KML for Visualization
18 Oct 2005 - Some Simple GML Profiles
17 Oct 2005 - Embedding GML in non-GML grammars
17 Oct 2005 - Geotags - the answer to everything?
20 Sep 2005 - GeoWeb 2006
20 Sep 2005 - GML Observations and Features
14 Sep 2005 - What is KML?
07 Sep 2005 - Time in GML
07 Sep 2005 - GML Observations
07 Sep 2005 - GML and KML Syntax
07 Sep 2005 - GeoWeb - Part II - GML and KML
07 Sep 2005 - GI Markup - Part I - Feeding the web with Geographic Information
06 Sep 2005 - GML Complexity
06 Sep 2005 - GML “Sucks”
24 Aug 2005 - Web Feeds and Geographic Information
23 Aug 2005 - What is the Geo-Web?
23 Aug 2005 - IS WGS84 Enough
04 Aug 2005 - Coordinates in GML
03 Aug 2005 - GML Profiles
03 Aug 2005 - GML and Coordinate Systems
03 Aug 2005 - Information Sources
03 Aug 2005 - Features and Geometry Properties
03 Aug 2005 - GML Geometries
03 Aug 2005 - GML FAQ for RSS Geeks and others



