08 May 2007 - GML, KML, Sensor Data, Imagery
GML has now become of age. It is used as a standard content encoding mechanism for all kinds of geographic information from commercial aviation to climatology and avalanche hazards. Nonetheless we have only begun to see the impact of this and related open standards on the world around us. GML can be used to make a wide range of geographic and geographically related data ubiquitous - including not only conventional "vector" features like roads and railways, but also sensor data (observations/measurements), and all kinds of coverages such as remotely sensed imagery and soil distribution. And now with the almost global acceptance of KML (formerly Keyhole Markup Language) we can readily turn that GML into visual presentations in Google Earth and a host of other mapping (e.g. ESRI tools) and visual presentation environments.
Think of the impact for agriculture. The growing population of the world, climate change, and restrictions on fossil fuel consumption are going to demand that our agricultural sector be more efficient and productive. This means measuring more parameters such as soil moisture, soil pH, detailed soil chemistry and measuring at a larger and larger number of locations. This information tied to measurements of biomass production and micro-terrain will lead to better models of plant growth and hence better management techniques including more effective use of water, fertilizers, pest control and other measures.
Sensors can provide GML observations directly to a standard "data logger" (WFS), located near the farm site, and this information can then be directly correlated with coverage information in GMLJP2 such as satellite imagery, terrain models, and hyperspectral imagery from aircraft or UAV's, this information being served from another WFS or WCS. A farm enterprise can then easily integrate or fuse this information to build a comprehensive picture of their farming enterprise.
Figure 1. shows the basic elements of the scheme, namely:
1. Sensors directly generate WFS transactions or respond to WFS requests - providing GML observations to the data logging WFS.
2. Higher level WFS aggregate and integrate this data with data from other WFS.
3. WFS/WCS serve coverage information such as satelite imagery, terrain models etc.
4. Enterprise level WFS provides an integrated picture of a farm or group of farms , including the farm geometry (extent/layout) and the various management parameters (e.g. crop production distribution by type)
5. Enterprise level FPS (Feature Portrayal Service) Web Map Service draws data from the various WFS to generate visual presentations in KML which can be viewed in Google Earth and similar tools.
6. The Web Registry Service (WRS) tracks the sensors and their descriptions (e.g. using SensorML , TML or IEEE descriptions) and provides ancillary information such as descriptions of the web services, the farms themselves, and the coordinate systems used to define the location of the farms and the sensor networks.
Figure 1: GML, KML - Geographic Features, Sensor Data and Imagery
Note that we have been able to deal with a very complex process using a comparatively small number of standards and by extension a small number of software components.
Of course, none of this is restricted to agriculture. The exact same standards apply equally well to homeland security, environmental protection, and urban infrastructure development - which is a good thing since these are all interrelated!!
2 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



