09 May 2007 - Meltdown and the Maze - Toward a Real Time Geography
The defense community has long talked about "Situational Awareness" and the need for a common operating picture. While some might think this is only a matter for defense interests - there is increasing demand for a real time geography (e.g. see) "picture" of the world that we can readily access and which reflects the current state of the world - from the condition of our roadways to the state of the climate. Such a real time geography is the objective of the GeoWeb.
To create such a real time geography requires that we bring together a great diversity of kinds of data - sourced from a similar diversity of creators - from the man in the street to governments and corporations. No one has all of the data - or even a sizable slice of it. Furthermore, a great deal of data is generated from other data - traffic sensors update real time traffic models - meteorological sensors can update parameters in road weather models - and these in turn can provide estimates of possible and safe driving speeds. The richness and variety of the data and the data sources demands data integration - but data integration that can happen when we need and for the purpose in hand. Data appropriate to hurricane response will be substantially different than that required to respond to a traffic jam or a terrorist incident - at the same time much of the data will be the same or similar.
A real time geography is thus ONLY possible if we embrace open standards for representing geographic information of all kinds. This demands that we have a common framework and the basic primitives to represent the richness of the world around us. This is the intent of Geography Markup Language (GML) and it is promise that is being delivered as GML adoption increases in more and more fields. A real time geography is also only possible if we can move data from one place to another - GML assists with the integration - but we also need the means to ask the questions to get the data. Here the OGC/ISO WFS specification plays the key role - enabling changes to be propagated from source to end user in seconds and minutes rather than the situation today when it can be hours to months.
It is also essential that we have a means to integrate ALL kinds of information and not make artificial boundaries between say sensor data and geography, or between sensor data and imagery. GML can be used in all cases as reader's of this blog are aware. Of course people will say that this imposes performance restrictions and of course this is the case today - yet this is a weak argument in the face of the fact that existing technology cannot hope to provide us a real time geography - it just was not created with that objective in mind. Performance issues will be dealt with - partly through Moores law - partly through technology improvements - but there is no question that this will be a non-issue in very short order.
Others worry about the supposed complexity of these standards - and pine for a simplicity that anyone can grasp and understand. There is no doubt that we should not embrace complexity for its own sake - however - it is also overwhelmingly clear that the variety and complexity of the issues for real time geography are NOT going to be handled by simplistic and ad hoc solutions. KISS is a guiding principle - but it must match the problems at hand.
Many people will think that real time geography can be handled merely with the arrival of GPS. Indeed GPS is a key element as it enables us to sense our position accurately - or the position of a vehicle - a vessel or an aircraft. This information is no good however without the capacity to connect this position to other objects. It does no good to know where you are, if you don't know what is there.
Of course GPS, as important as it is - is just another piece of sensor data - but one that provides, along with time, the ability to integrate the other sensor information. Sensor data is key to the GeoWeb revolution and to the vision of a real time geography. The next decade will see the emergence of hundreds of thousands (millions?) of sensors that will monitor every aspect of our planet - and which tied with more conventional notions of "geography" will make the GeoWeb an ever present reality for all of us.
To understand the GeoWeb - the real time geography - will require good "pictures" - we are visual creatures - and tools like Google Earth and its successors will be key to communicating the state of the world - and our perception of it from one to another. This will require that our GeoWeb enable the easy flow of data from sensors - individuals - professional surveyors and technicians of all kinds - satellite and aerial imagery - in situ sensors in the atmosphere and the oceans - to the tools for presentation. Again this emphasizes the need for broadly accepted standards such as KML and GML (see).
The emergence of "situational awareness" for the individual - the corporation and all levels of government is going to have profound consequences in all spheres of our lives from the daily experience to the large scale enterprise of managing our impact on the planet. The GeoWeb will be an important factor in creating that awareness.
No Comments | Leave a comment»
Comments
No comments yet.
Leave a comment
Blog Entries:
08 May 2008 - Looking ahead to GeoWeb 200921 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



