What is a SDSS and how is it different from a GIS?

IMAGE SOURCE: ABC

image source ABC

Lately I have been doing some work as a volunteer in the aftermath of the victorian bushfires. We have been using GIS a lot but there was always something missing during the emergency mapping and spatial analysis. This was a Spatial Decision Support System.

So what is a SDSS and how is it different from a GIS?

In order to understand SDSS and know the difference between GIS and SDSS it is important to understand what a GIS is. GIS is a piece of software that can perform generic spatial analysis and geoprocessing methods on geographic data. It requires an GIS Analyst or an expert to operate it. In contrast a Spatial Decision Support System is a domain or an industry specific software. It doesn’t require a GIS expert to operate but rather a domain expert. As the name suggests the software provides decision support but to do so makes use of spatial analysis, geo-statistics, geo-processing or other tools from spatial information sciences. To begin with a SDSS must be designed to answer some domain specific questions that have strong elements of geography.

This is best illustrated through an example: say, in coordinating the containment of a bush fire a sector coordinator needs to decide on where to deploy bulldozers to create a containment line or a barrier to the advancing fire-front. The job of the software is to provide the coordinator with a number of alternative answers that they can choose from based on their experience. In this instance the SDSS will take into consideration a number of information sources, perform a combination of spatial analysis and use sophisticated fire modeling to determine answers.

From the above example it is clear that a Spatial DSS must have access to relevant up-to-date spatial data, contain algorithms from spatial information science and domain-specifc models to answer domain-specific questions and a method for visualizing the answers. So for the sector coordinator the relevant data required would be topography, vegetation fuel maps, weather forecast, real-time weather measurements, verbal information from lookout towers and/or air surveillance, satellite reconnaissance, information from thermal cameras. All this would need to be geo-referenced and lie with in the spatial extent of her sector.

Next component is the algorithms that will convert raw data into useful knowledge. It is important to note that data and algorithms are closely linked since some of the data sources may be derivative products. For example vegetation fuel map may have been derived by applying a Normalized Difference Vegetation Index (NDVI) algorithm to multispectral remotely sensed satellite imagery.

Another example may have an algorithm to convert topography into slope. This slope may be used to rule out areas that are too steep for bulldozers to operate. This nicely leads us to the related component of domains-specific models. In this case the information from the slope, weather conditions (such as wind direction and humidity) as well as the vegetation fuel data may form inputs into a fire-model that predicts the future course of the fire. This information may then be combine with areas where bulldozers can operate to give deployment alternatives to the coordinator.

In a SDSS the above process would form a seamless chain of inputs and give an output. While in a GIS the above would be done by an expert spatial analyst who must be aware of all the pitfalls of combining different spatial data and deal with spatial coordinate systems. But above all a GIS will lack the modeling capability to predict the future course of the fire let alone understand what a bulldozer is. This brings us to another important difference between a GIS and SDSS. SDSS must deal with semantic information. In a SDSS spatial data cannot exist in isolation from its meaning.

Goodbye National Mapping, G’day Google!

Google MapMaker is out. There are several geowiki projects, but when someone like google decides to have a go at the problem you have to take notice. First thing to note is that the MapMaker is open for a limited set of countries, one of which I have blogged about earlier. So lets see what the uptake of MapMaker is by looking at Karachi (a city of ~20million, metropolitan and where locals are cultured with a strong entrepreneurial spirit) it appears there is very fast uptake from the locals. Here is what has happened in the course of a few hours

Google Map Maker
Uploaded with plasq‘s Skitch!

With local languages support:

Google Map Maker
Uploaded with plasq‘s Skitch!

The same location under OpenStreetMap looks like this:

OpenStreetMap
Uploaded with plasq‘s Skitch!

This shows what great usability can accomplish. There are a number of important differences between mapmaker and openstreetmap. The concept of confidence doesn’t exist in OSM. While mapmaker allows users to state the level of confidence by indicating how well they know this location.

Google Map Maker
Uploaded with plasq‘s Skitch!

The closest OSM gets to this idea is the tip about only mapping places you have been to.

OpenStreetMap
Uploaded with plasq‘s Skitch!

Mapmaker has a distinct peer-reviewed moderation process. Users have the ability to state the quality and confidence level of the data. This can allow the higher quality data to bubble up into googlemaps while work goes on on the lower accuracy/confidence data.

Another important difference is the separation of editing and browsing the map in mapmaker. In mapmaker note that you can select the data and pan around without the fear of accidently editing the features while in openstreetmap panning and editing are mixed.

MapMaker Browsing:

Google Map Maker
Uploaded with plasq‘s Skitch!

OSM Browsing/Editng:

OpenStreetMap
Uploaded with plasq‘s Skitch!

OSM has a “play” option to let you get confident before making the edits but moving between play and edit mode means an all or nothing choice. While in mapmaker you can browse, select a feature and choose to make edits if you want.

Mapmaker Pick Editing:

Google Map Maker
Uploaded with plasq‘s Skitch!

Another interesting feature is the ability to add events and specify their type and significance. This is an interesting paradigm shift in stating an event by going via its geographic attributes first.

Google Map Maker
Uploaded with plasq‘s Skitch!

Now the question is will google play nice and make their data available under a liberal licensing scheme? Will there be a REST API? Can OpenStreetMap learn from this and get even better? What does this mean for national mapping agencies and commercial data providers? Is google now a competitor? Is it time for other to build even better tools for crowd sourcing or should we be sharing and have a coordinated mapping effort? Lots of questions very interesting to see how it all plays out over the next few months.

There’s still hope for Australia’s spatial industry

The ASIBA last week release a set of recommendations for the Australian government. These recommendations were based on a economic study evaluating what the spatial industry in Australia is worth. A staggering 6-12 billion dollars is the figure mentioned.

But lets look at the recommendations: I quite like the aims of some of these: government initiatives to commercialise OZ spatial information R&D; government policy that improves the quality, quantity, currency and accuracy of spatial data; management of digital rights and information sharing and a whole-of-government approach to licensing of geodata.

There are a number of initiatives already in the pipe-line to address some of these issues for example to address constraints on information sharing, OSDM is developing a whole-of-government approach for licensing of spatial data. There is also a push to use existing standards for discovery of spatial data where applicable such as OGC‘s CSW whose most well known implementation is FAO’s GeoNetwork. There are also projects that look to make taxpayer funding research data free. The question now is how long will it be before we start seeing the fruits of all the good intentions from the government and traditional Spatial industry. How long is a piece of string?

Meanwhile neogeography projects such as OSM continue to flourish and so do the related standards such as GeoRSS. Another recommendation that will hopefully see greater support for such open and community driven initiatives in Australia is that

… priorities are user driven, not ‘producer’ driven

Hopefully this means that the OZ government’s inacceassable silo’s of geodata that’s currently begging to be freed may one day become available in formats that ease their use online and amongst the developer community. This would no doubt lead to the emergence of new industries, a responsibility that governments have towards their nation.