GML was created to enable geospatial transactions on the web – that is the ability to change the content of a geospatial database in a vendor independent manner. While GML does enable traditional file based exchange of data . . . → Read More: From GML 1.0 onwards – a brief history

I would like to pick up on the issue of what GML can or cannot add to the interoperability between databases.

First I would note that the whole discussion (Savage et al) wrt GML 1.0 and . . . → Read More: GML and Database Interoperability

In the inaugural posting on the official Google LatLong Blog, John Hanke mused as to nature of the GeoWeb. I thought we might throw up some answers – not to claim to be definitive but to spark discussion. . . . → Read More: GeoWeb Manifesto

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 . . . → Read More: Meltdown and the Maze – Toward a Real Time Geography

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 . . . → Read More: GML, KML, Sensor Data, Imagery

In the past year, Google's KML has emerged as the dominant geographic visualization and annotation language on the planet. Millions of KML files are being used to describe places all over the globe from the troubles in Darfur, . . . → Read More: Transporting GML in KML