What is important about ArcGIS Explorer Build 410

Keith Fraley says:

I really think there are two notable points with this release, that aren’t prehaps getting that much attention in the blogosphere

You know what, he’s got a great point. Subsurface navigation is a huge deal because that is one of the biggest complaints I’ve heard about Google Earth from some clients. Of course keep in mind that ArcGIS Explorer doesn’t have anything subsurface to look at by default so you’ll need to get some data layers to play with to actually see something other than blue once you go underground.

Going a different direction

We’ve implemented more ArcIMS sites than I can recall over the past few years. The chief developer on my team has probably as much AXL experience as anyone I know. But times change and clients have different expectations than they did in 1999 or even 2006.

The Oracle
“Because you didn’t come here to make the choice, you’ve already made it. You’re here to try to understand why you made it.”

On one our latest projects, we are developing a site using SharePoint and what would have been ArcIMS. The difficulty we’ve had getting the WebADF to work the way we want has put a damper on our excitement that we had when it first showed up. It is just way too difficult for the “simple” and “quick” development that we have to do. Plus, as nice as the WebADF is, clients still are expecting a Google Maps type interface and the WebADF is not that (nor does it try to be). With the new licensing of Virtual Earth, we’ve decided that MapDotNet Server 2007 connecting to ArcSDE is the way to go. The front end will be based on Virtual Earth so folks will feel comfortable with the interface (it seems every ArcIMS web mapping site is different and that causes usability issues) and they’ll be able to work with the data rather than fighting the interface.

Now this isn’t to say that we are abandoning ESRI server products because that isn’t the case. We will continue to develop ArcIMS sites for clients who want them (I still say it makes sense to leverage existing licenses of ArcIMS or move over to ArcGIS Server Standard) than dump all that work and start new and ArcGIS Server applications for clients whose requirements need Geoprocessing. But for quick and simple web mapping I think MapDotNet and Virtual Earth will be the killer combination for ESRI .NET developers who are already familiar with the tools. The simple fact that folks won’t have to abandon any of their existing ESRI servers (ArcSDE is still there) and desktop clients, the ease of which we can develop applications and the speed of MapDotNet will give our clients that quick, easy to use, great looking web mapping tool that they have been clamoring for.

Maybe the ESRI REST API will change things for us (I wasn’t at the 2007 UC so I have no idea how it looks or works), but for now we are going in this direction. We’ll see what the 2008 Developer Summit brings for the REST API and rapid development of ESRI web mapping applications.

I find it interesting to see another ESRI developer look outside the ESRI stable for a replacement to MapObjects. There was some concern among many developers at the 2007 Dev Summit that ESRI was abandoning the smaller developers and focusing on enterprise level GIS tools. Steve, who posted on his blog about .NET SIG at the Developer Summit wrote:

Damian [Spangrud] talking ‘ discussion about pricing ‘ tension between large enterprise customers who expect it to cost more and smaller shops that think it is too much (like me).

That just scares me working with ESRI server software. I feel like I’m being priced out of the marketplace with their new tools. The days of writing simple and cheap Avenue or MapObjects application are over. Now you need superstars who know ArcObjects in and out and clients where price is no option. Maybe the RESI API will change this (or maybe not), but if you look around there are tons of tools available for you to use that won’t mess with your workflows and might just allow you to improve you output without spending tens of thousands of dollars.

So we’ll see where this all leads. We still may decide that MapDotNet isn’t for us and go back to trying to figure out the WebADF and its task framework.

James on REST

Since everyone is blogging about REST I was feeling left out, so here is my post.

Think about this as ordering a Domino’s Pizza.

You make a call and you get something in return. If you do it while lying down on the recliner, that is very RESTful.

If Howard Dean is screaming for a pizza, that isn’t very RESTful.

See how simple this all is? Ordering from a lazy-boy recliner, RESTful. Having Howard Dean order the pizza, not RESTful. All this talk about ATOM, COBRA, COM, HTTP, SOA, SOAP just confuses folks (if I wasn’t so hungry I probably would have used a Simpson’s example, but you’ll have to deal with this because I’m going to order a pizza right now).

SharpMap is the new MapObjects

Bill Dollins is talking about how SharpMap is giving him back his “old MO vibe again”. What caught me eye was:

The open source nature of SharpMap was a huge plus and I’m having fun doing things that I always wanted to do in MO.

I can’t think of another ESRI “product” that has generated more love than MapObjects. It is too bad that MapObjects was cast aside for ArcObjects and ArcGIS Engine (both fine products, but overkill for many applications).

SharpMap includes ASP.NET 2.0 and Winforms 2.0 controls. It features rendering objects that are distinct from the UI on which they are rendering. It’s a model that allows for great flexibility.

Sounds like a slam dunk to me. WPF is the direction that .NET developers are heading so WPF support in SharpMap could open up a whole new area for desktop GIS.

So if you’ve been looking to get your MO on again, SharpMap obviously deserves a look.

CAD Client for ArcSDE 9.2 released

I’m probably only one of a few people who actually use the CAD Client, but I’m very happy to see that it was released today. AutoCad 2007 support is not there (2006 and earlier) so it isn’t the perfect solution, but at least now we can work with data inside our ArcSDE with our Autocad users.

Wonder why they kept the name ArcSDE. Shouldn’t it be CAD Client for ArcGIS Server Enterprise?