All Hail Google Earth Builder, Wait… What?
Inconceivable!
Inconceivable!
So yea, two weeks ago I was all excited about Google Earth Builder. What’s not to like? It handles geospatial data easily, has some awesome visualization tools and has a pricing model that seems reasonable (Disclaimer, I should say it scales reasonably. That of course doesn’t mean it will be reasonable in cost at the base line. Google Earth Enterprise isn’t cheap nor is licensing other Google Maps data). And of course everyone is totally excited about it on Twitter (Sewing circle they are) and I have to think Directions Magazine is happy that one of their webinars was so well received. So why do I have a problem with it?
First off, lots of things seem sexy and fun until you start playing with them. I mean watch someone with a Yo-Yo. How much fun does that all look? Then they hand it to you and you are bored before you can even put the string on your finger. GEB could be the same way. Yea it does some things really well, but once you actually want to start and do real work with it, you have to choose another tool. This isn’t to say GEB won’t become all that, just generally these things take time to build up to where other tools have been for 20/30 years.
My other issue with GEB is it seems like a Federal Government play. You know, the one where Google and Esri fight over government pork spending? GEB might be perfect for this world, but that doesn’t mean that those of us with our feet on the ground can actually use it for anything. Sort of like a Data.gov 2.0 thing. Sounds great in practice, but theory doesn’t pay the bills for most of us. Until I see actual use cases in commercial space, I’m going to chalk up GEB as a government tool that Google has thrown out there to fight Esri, Microsoft, Oracle and whatever other large Government technology implementor that uses “geo”.
MechaGodzilla
Which one is Esri and which one is Google?
Taking on Esri in the Federal Government space? That’s a pretty ballsy move by Google. Esri is a tough customer and they’ve shown time and time again they fight to win. In a way this is probably the best part of GEB for the “rest of us”. Think of Esri technology (Remember Geography Network, ArcIMS and the WebADF) before Google came along? Now they stuff is almost a joy to work with (almost). As long as Esri’s GEB response isn’t more ArcGIS for Explorer (Do I have that name right?) and ArcGIS for Server with Advanced Enterprise, I think we all win.
Tragic Esri
The tragic prelude to all us brothers getting together.
I’ve Come to Praise ArcObjects, Not Kill It
OK, I’m the first one to dance on ArcObjects grave (In fact I suspect I’ll take my anti-love of ArcObjects to my grave), but others seem to like it.
…This all comes from the following fact: being a complete ignorant about ArcObjects and the ArcGIS API, I have been able to create the corresponding SEXTANTE bindings from scratch in less time than I needed to create any other bindings before. That means less time than the gvSIG bindings (an application that I knew pretty well), and way less than the OpenJUMP or Geotools ones (both of them softwares that I had worked with before, at least once).
This is basically due to the clean, well designed and perfectly documented API of ArcGIS, which, along with the additional Eclipse plugins, makes it very easy to develop new plugins and extensions for the software.
Now, let me just tell you first off. Sextante coming to ArcGIS - awesome! But the real meat of the matter here is if there is a well documented API, developers just love it (No matter how crazy the ArcObjects API may be). That is the real lesson for any project, proprietary or open source. Documentation matters!
In API hell, as long as there is documentation we’ll all be fine!
I’ve Come to Praise ArcObjects, Not Kill It
OK, I’m the first one to dance on ArcObjects grave (In fact I suspect I’ll take my anti-love of ArcObjects to my grave), but others seem to like it.
…This all comes from the following fact: being a complete ignorant about ArcObjects and the ArcGIS API, I have been able to create the corresponding SEXTANTE bindings from scratch in less time than I needed to create any other bindings before. That means less time than the gvSIG bindings (an application that I knew pretty well), and way less than the OpenJUMP or Geotools ones (both of them softwares that I had worked with before, at least once).
This is basically due to the clean, well designed and perfectly documented API of ArcGIS, which, along with the additional Eclipse plugins, makes it very easy to develop new plugins and extensions for the software.
Now, let me just tell you first off. Sextante coming to ArcGIS - awesome! But the real meat of the matter here is if there is a well documented API, developers just love it (No matter how crazy the ArcObjects API may be). That is the real lesson for any project, proprietary or open source. Documentation matters!
In API hell, as long as there is documentation we’ll all be fine!
Apple Uses Mapping Data — For Reals?
Now With Hat
Apple iOS - Now with Mapping Data
Look, I totally get it. The big shiny object in the sky is Apple. Anything they do is “interesting” (Disclaimer: I give every other paycheck to Steve Jobs for his new shiny objects). I saw this news this morning about TomTom being in Apple’s Legal Doc (The amount of GNP devoted to reading Apple’s tea leaves has to be bigger than most eastern european countries) and let out a big meh. Clearly as location becomes more integrated in smartphone workflows, companies will start adding additional data sources for their customers to use. Since Apple uses Google Maps as the default mapping app on the iOS, we probably won’t see any changes to that for quite some time (if ever). TomTom/TeleAtlas data is used by many companies for many things so the possibilities that Apple would use their data isn’t that far fetched (I’m actually surprised that it wasn’t in there before, it is hard not to use TomTom or NAVTEQ these days).
Adena did a great job highlighting the companies that are now (or have been) part of Apple’s legal description. Let’s see… We’ve got parcel data, we’ve got neighborhood data, we’ve got routing data and we’ve traffic data. If I didn’t know any better, I’d be guessing Apple is trying to build a smartphone (Side note, I’m very happy for Waze and Urban Mapping here. Great job guys!).
The OpenStreetMap whining is already started with folks wondering why Apple didn’t use their data. Clearly Apple is picking and choosing what they need here. Apple is one of those companies that uses whatever makes best sense for them and their uses. That is why they still use Google Maps, it really is still the best solution out there and they can afford to pay Google the licensing costs. I still believe, as many of you do, it is only a matter of time for Apple to roll their own mapping solution. This is a company that loves to control everything and to think they allow a competitor to have a mapping app on iOS by default has got to hurt them. Of course how many years did Apple include Internet Explorer as the default browser on Mac OS X before rolling Safari. Yea, only a matter of time.
Mark Twain iPad
Many don’t remember, but Mark Twain was a big user of iOS mapping applications and thus a user of mapping data.
The Esri Ocean Basemap
I might have mentioned this a couple times on twitter yesterday, but I really like the new Esri Ocean Basemap. My only wish would be that it drops down one more zoom level. So close to being perfect. Here it is in all it’s glory…
The Esri Ocean Basemap
I might have mentioned this a couple times on twitter yesterday, but I really like the new Esri Ocean Basemap. My only wish would be that it drops down one more zoom level. So close to being perfect. Here it is in all it’s glory…