EarthBrowser 3.0 is out

Congratulations to Matt Giger for pushing out EarthBrowser 3.0. I have been following Matt’s triumphs and struggles on his blog as he’s worked at getting the latest EarthBrowser release out on his blog. I was more than happy to purchase a license and I encourage everyone else to do the same as well. I am very interested to see how folks use the Adobe Air based digital globe moving forward.

EarthBrowser 3.0

Can I do the same GIS tasks with OS as with ESRI?

A thread has developed on the OSGeo email list (out of an “open source career” post in fact) asking how one can perform the same tasks using open source software as they do with ESRI.

Paul Ramsey as usual writes a spot on response to the question:

My general synopsis: for server-side, for scriptability, for automation, for web-based, open source wins for most use cases, given a technically savvy user; for ad hoc, for cartographic production, for a user who is used to a point-n-click experience end to end, proprietary still wins.

Nacho Libre

Nacho Libre – defender of open source

ESRI on Oracle Patch and ST_GEOMETRY

I’m sure most ESRI customers received the following email from ESRI regarding the Oracle patch and ArcSDE:

If you are a user of the ArcGIS Server 9.2 ST_GEOMETRY data type with Oracle, we would like to make you aware of the following issue:

The recently released Oracle patch version may make unexpected changes to the ST_GEOMETRY schema. ESRI is in contact with Oracle, and we are working together to understand and quickly resolve the problem in this Oracle patch upgrade.

ESRI strongly recommends that all Oracle-based customers not upgrade to the Oracle patch until ESRI has certified this Oracle patch release with ArcGIS Server 9.2.

If you have already upgraded to Oracle and think you may be experiencing this issue, contact ESRI Support.

What is humorous about the whole issue (well at least funny to those not caught up in it) is that Oracle includes the following statement on their readme for patch.

“Patch sets are a mechanism for delivering fully tested and integrated product fixes. Patch sets provide bug fixes only; they do not include new functionality and they do not require certification on the target system.”

Guess that isn’t the case, eh Oracle?


It seems that every time we meet, I have nothing but bad news. I’m sorry about that, I surely am.

A quick look at GETools

Brian Flood has apparently been busy.

Now that Google Earth 4.3 is officially out the door, I wanted to share another product that we’ve been working on. It started out as the framework for a standalone version of Arc2Earth but it quickly became apparent that the core functionality would be very beneficial to other Google Earth developers. So, we decided to create a custom tools harness that would load both .Net extensions (which the standalone version of Arc2Earth will be) and also runtime downloadable javascript.

Scripting in Google Earth? Now that is something that I really could take advantage of. Check out his videos on his blog post to see it all in action.

Google Earth is the AOL of the Geoweb

Non-Google Fanboy Look at Google Earth 4.3

Google Earth really is starting to remind me more and more of the AOL of the early 90’s. Loaded with tons of crap you have to wade through to find the good stuff.

While pretty, 4.3 is a performance dog. Of course all the other digital globes are dogs, but Google has taken a step back on ease of use and speed. I’m sure they’ll get it back at the next release, but for now it makes me want to downgrade to 4.2. Does Google Earth have Google Goo in its Google Gears?

Google Goo

MSR MapCruncher vs Virtual Earth MapCruncher

OK, the MSR MapCruncher team has contacted me with some clarification as to the difference between the versions and what that means for the future:

You are correct that one reason there are two versions is licensing. The other reason is branding and support: the VE team has quality standards and wants to ensure they don’t find themselves doing support for a buggy product. We in MSR, on the other hand, are more interested in shipping bleeding-edge tools, even if it means things break. Right now, there’s not much in the MSR branch that’s not in the VE branch (other than a few undocumented hacks). But we’ve got some really exciting stuff in the pipe, and having that MSR branch available means we can turn out experimental versions very quickly. Then, if it gets a positive reception, VE can decide to push it through the product-quality process.

Well there you go. Currently MSR MapCruncher is at version 3.2.4 and VE MapCruncher is at 3.2.0. We’ll see how things change when MSR MapCruncher makes a bigger jump ahead. But at least for now VE MapCruncher has a license that allows you to use it in a commercial setting so I suspect most would be better served with the more stable version.