One of the more confusing things for new ArcGIS users is that they probably need either Spatial Analyst or 3D Analyst to do their work. It’s almost a foregone conclusion that every ArcGIS for Desktop license will have at some point either one of those extensions. As I’m getting back into Server though I’m starting to take a look at those extensions as well. Specifically the GeoEvent Extension has caught my eye. Conversations on Twitter basically expose that it either works or it doesn’t and it’s either great or maddening. Sounds like typical Esri software.
The thing about Server extensions though is they mostly have a Windows requirement to run (thankfully GeoEvent doesn’t). As I’ve jumped back into ArcGIS for Server I’ve been impressed with it’s maturity but alas it’s still a windows only product which limits its use in hosted environments. I’m not oblivious to the reasons why these things go Windows only but it is a shame that Workflow and Data Reviewer require windows. Hopefully as Esri transitions into a more software agnostic development environment, they’ll start fixing these Windows only requirements.
At least GeoEvent Extension runs on Linux, wish me luck with that….
I’ve been playing with ArcGIS for Server 10.3.1 at Matrix and we’re all about running things with hosted services. So rather than spec out some hardware and install ArcGIS for Server on local legacy machines, we’re doing it all in the cloud. Because I’m new here there wasn’t any legacy AWS use so I was able to pick Azure for deployment. My logic:
While I’m experienced with AWS, Azure is mostly an unknown world to me. Given we’re running Windows servers with SQL Server, why not go native.
I really want to give SQL Azure a spin.
The portal for Azure is much nicer than AWS. They have those stupid panels in places1 but mostly it makes logical sense.
Esri has Cloud Builder to simplify installation which I though would be great for starting up prototypes quickly.
So logical, no? Well late yesterday this tweet went out by me.
I was stuck here:
You can literally hear the sad trombone sound. Now Sam Libby was helping troubleshoot but things were still a bit weird. Basically as you can see in the error above, I needed to accept an EULA. Now of course I went into the the Azure Marketplace and followed the instructions to allow the Esri VM to be deployed programmatically which is what Cloud Builder requires. But each time it errored out the same way.
Sam offered this:
Basically he hit upon it. Microsoft did something with the marketplace and for whatever reason the Cloud Builder app won’t install an Esri ArcGIS for Server VM until you actually install it first yourself.
The workaround to get the Cloud Builder app to run is actually just create a VM using the Azure Portal then delete it.
After that, the Esri Cloud Builder app runs perfectly without trouble.
Philip Heede basically confirms everything.
So the ArcGIS for Server Cloud Builder2 works great. While I don’t like wizards in general, it automates the processes that take time and let’s you focus on the settings for ArcGIS for Server you want to change. I honestly haven’t installed ArcGIS for Server since it was ArcGIS Server (without the for) 9.3.1 and it was interesting to see how things have changed and how little has actually changed.
We were talking this weekend about how much serving up GIS data has changed in the past 3 years. GIS Server used to be so important to many of my friends companies to the point they spent tens of thousands of dollars on it a year. But no longer, each one said that they stopped paying for server because they all use other options. Now before I go on, I want to say this isn’t about sales data of Esri products. It’s more about changes in how people are sharing spatial data. Feel free to replace ArcGIS Server with your favorite GIS server package (Title is a bit of SEO, right? Heck I’m not even talking about ArcGIS Server in this post).
I gave a talk years ago about something we did at the GNOCDC mapping recovery from Hurricane Katrina. You can see the slide deck here and watch the video here. Basically it was the seeds of what we are going through right now. It wasn’t that what we were doing back there was very unique, it was just a realization that GIS can’t be hosting “enterprise” data in a “workgroup” environment. Just like Katrina basically broke the GNOCDC GIS servers, it has become clear that there is almost no way for an organization to use classic GIS servers without putting a lot of load balancing and networking decisions in front of them.
For most companies this is just way too much infrastructure and licensing costs. We’ve seen the rise of CartoDB, Mapbox and ArcGIS Online (or whatever it is called these days). Each has pluses and minuses and while there is overlap, they all do things unique to themselves. But what the big attraction for each is that you don’t have to manage the constellation yourself.
The biggest drawback each said was the unknown in licensing. Most hosted GIS plans are costed in ways that GIS people aren’t familiar with. Mapviews? Nobody has analytics on that until you put it in these services. 100,000 map views sounds huge doesn’t it? But how do you really know? Service credits? We’ve wondered what that even means for years. But I’d wager beers that even with the unknown, you’ll still save money over your ArcGIS Server license or other maintenance you pay for hosting your own GIS server.
We’re at a crossroads here. People have begun to start realizing standing up ArcGIS Server, Geoserver or other map servers makes little to no sense in the new marketplace. Paying for hosting maps is cheaper in the long run, has more availability and is easier to use that classic self hosted mapping solutions. ArcGIS Online for all it’s confusion is beginning to be leveraged by users and everyone I knew at the Esri UC knows what CartoDB and Mapbox do. Back in the old days of WeoGeo, we had to prove what we know now every day. The cost of “doing it yourself” is magnitudes higher than paying for hosting.