About the Author:  Sean Gorman founded FortiusOne in 2005 to bring location based analytics to the mass market. Sean brings over 10 years of experience at the forefront of the geospatial revolution as a researcher, practitioner, and entrepreneur at FortiusOne. Through both academic and entreprenurial efforts he has been working to make geographic data more accessible to the public since 1997 culminating in the creation of GeoCommons – a crowd-sourced repository of statistical data and social feeds that can be easily mapped, remixed and reused by non-technical users. Sean has been featured in media such as, Wired, Der Spiegel, ABC, Washington Post, Business 2.0, MSNBC, CBS and CNN. He also holds a PhD. From George Mason University in Public Policy where he was the Provost’s High Potential Scholar and was the recipient of the Fischer Prize. He has published dozens of articles on geographic data sharing and analysis, and authored the book Networks, Complexity and Security: The Role of Public Policy in Critical Infrastructure Protection. Read more from this author

Frank at the Google Earth Blog just leaked that Google will be announcing an API for Google Earth that will run in a browser. The short of it is you will be able to get GE’s 3D rendering capabilities and KML support to run in a browser. The first release will be just Windows, but will support IE, Firefox and other Mozilla flavors.

This looks to be a direct shot at Microsoft’s 3D Virtual Earth that also runs in the browser. The question mark in my mind will be if the Google Earth version has the same performance issues as MSVE. It is also interesting that Google released an API instead of a new version of GE that ran in a browser. Will this be a case of Google testing the waters with the API then releasing a product?

From a personal perspective I’ll be very interested to see how the new Google Earth API handles KML. Frank says the new API will be a, “subset of the Google Earth 3D graphics rendering engine and interfaces with KML support”. The question is will that KML support be robust like Google Earth allowing thousands of geometries to be drawn or less robust like Google Maps where you are limited to the low hundreds. I’m sure we’ll see soon enough, but congrats to Google on porting the technology to a browser, surely not an easy task. Although it begs one last question – does this herald the end of thick client geobrowsers?

Popularity: 12% [?]