Geospatial Technology, Web Mapping and Spatial Services
August 10, 2011 Leave a Comment
One of the minor complaints about the File Geodatabase API was that there was no API wrapper for those who wanted to use it with .NET projects [ref]Where is the Avenue wrapper Esri?[/ref]. Clearly Esri heard the talk and rolled out a simple wrapper for .NET users. The File Geodatabase API 1.1 has all that and some bug fixes.
I can’t wait to start using the File Geodatabase API!
March 10, 2010 5 Comments
It looks like the powers that be at the ESRI Developer Summit have decided a .NET [ESRI/Microsoft SIG is a good idea after all](http://events.esri.com/bpc/2010/dev_agenda/index.cfm?fa=Session_Detail_Form&SessionId=174&ScheduleId=302). [Fears](http://www.spatiallyadjusted.com/2010/02/08/the-esri-developer-summit-and-the-net-sig/) (possibly all mine) that the DevSummit was changing and wouldn’t be able community anymore are tempered somewhat by this announcement. So if you work the ESRI/Microsoft angle to develop GIS applications, you can now share this fact with your brothers and sisters in code. Viva Palm Springs!
September 28, 2009 26 Comments
You Maniacs! You blew it up! Ah, damn you! God damn you all to hell!
So the news that ESRI ArcGIS 9.4 will be the last version that includes VBA support has really stirred up some emotions. So sum up a couple comments in that post, “I can’t believe they are dropping VBA, I use it all the time”. Many of us have moved beyond VBA to other languages, but there seems to be a large percentage of ESRI developers that still rely on VBA to customize ArcGIS Desktop. geoGraphika has even written a blog post outlining 7 reasons why ESRI shouldn’t drop VBA.
Now before VBA devs get all worried that they have no time to prepare for the change. Take a look at the time between when ArcGIS 9.3 arrived and when 9.4 will come. ArcGIS 9.3 shipped June 26, 2008 and ArcGIS 9.4 earliest possible release date would be right before the ESRI UC which is July 12, 2010. That is almost 2 years between releases. Lets assume 9.5 takes that long to arrive (let alone the mythical 10.x release) it will be summer 2012. That is a lifetime to get ready to migrate off of VBA. Plus if VBA is mission critical, you can stick on ArcGIS 9.4.
Hey, don’t worry about VBA being depreciated. The future’s so bright, you gotta wear shades.
June 16, 2009 5 Comments
Remember this post? Count that as the most popular post ever on my blog (so much for a positive post being my watermark). Anyway Doron Yaacoby has followed up almost a year and a half later with another look at where ESRI has taken the Web ADF since then.
Almost none of the issues I addressed in my original post were fixed. The API is still overly complex. Resources, functionalities and all these so-called abstractions remain in place, emphasizing the strength of the JavaScript API’s simplicity. And yes, there are still about a billion classes that are named “Converter†in the API. It seems like ESRI insists that you write the entire namespace before every class you use.
Yea that was probably predictable, but I don’t think any of it matters. We’ve all moved beyond the Web ADFs and on to the REST APIs (Flex, JavaScript and Silverlight). Really though I’m amazed at how much our web development platform has changed in that time, we all can agree developing with ESRI is much more enjoyable than it was and I’m wagering most of us forget there is a Web ADF out there anymore. I can’t wait until the ESRI UC to see what the future holds in store.
The killing of .NET and Java on the web continues unabated.
March 31, 2009 17 Comments
ArcGIS Code Challenge Winners Announced
Looks like Alper Dincer and Matthew Petre are the big winners. The mobile code challenge results are posted as well. I suppose they announce this after the DevSummit so the winners don’t have to buy everyone beer.
VBA and VB6 with ArcGIS: What’s the Story?
First off I bet you didn’t even know there was an ArcObjects blog. Second, please move off of VBA or VB6. Last year I said the writing was on the wall, this year the wall is falling down upon you. Python, Java or .NET; take your pick and enjoy. There is nothing you can’t do with those choices and in fact gives you much more freedom.
Silverlight API
Vish is taking it for a spin and he’s reporting back on its use. Bookmark or subscribe to Vish.
Virtual Earth and ESRI ArcGIS
This seems to be getting a ton of play. One thing to remember folks, yes VE is free with ArcGIS Desktop and ArcGIS Explorer 900, but you need a valid license. If you download AGX 900 and don’t have a valid ArcGIS Desktop license, you won’t be seeing VE imagery. Yea that sucks for the world, but every ESRI user should buy Jack a drink at the UC in San Diego for paying for this.
March 18, 2009 16 Comments
So Microsoft has released a Silverlight map control to developers:
Now, because we’re using Silverlight, .NET developers (all 6 million + of you) can leverage your skill set to build rich, killer apps that make your data bling and highlight media in a geo-contextual way as has never been seen before. VESL leverages all of the drawing tools that come with Silverlight, so for Silverlight developers you’re not relearning how to take your computer art and force it onto a map. Instead, you’re starting with a map-based canvas instead of a blank one.
Looks simple enough to leverage and I’m guessing since Microsoft developers are in love with Silverlight, it won’t be long before the JSAPI is pushed aside. It looks like people will start having to pick a side, Flash or Silverlight.
Silverlight is bling
December 1, 2008 2 Comments
Dave Bouwman has a great blog post on all the different choices available to ESRI centric developers for a web mapping front end. Not a bad primer for folks still trying to figure out all the new options we have available for visualization.
I'll take a side of RESTful with my mapping front end please.
October 22, 2008 11 Comments
I was just talking to someone today about web applications for ArcGIS Server 9.3 and they were surprised that I was using the Web ADF to create an application after my post earlier this week on the JavaScript API. I feel like I need to clarify some things about that post. It wasn’t so much a desertion of the Web ADF, but point that one should be looking toward the JavaScript API (and I suppose the Flex API) for most mapping situation and use the Web ADF (Java and .NET) when it best makes sense. I’m using the Web ADF on this project because the requirements of the end user is best met with the Web ADF. The great thing about the JavaScript API, the Flex API, the .NET Web ADF, the Java Web ADF and even the JavaScript extenders for the JavaScript API is that they all can be called on if needed. Of course the Web ADF does have licensing issues that ESRI needs to address that limit its appeal even when it is the best choice for the solution.
ESRI has given their developers choices that we aren’t accustom to and in turn ESRI developers should be looking at the choices when making a decision of what SDK to use. Also just because you use the JavaScript API or the Flex API doesn’t mean you’ll end up with a great application. So much more goes into it and there isn’t any reason why the Java Web ADF can’t give you a great application anymore than the Flex API can.
Et tu, James?
October 16, 2008 34 Comments
I find it interesting that most work I’m seeing these days is with the JavaScript API that ESRI released at ArcGIS 9.3. I assumed a couple months ago that people would really be looking at moving off of the WebADF (.NET or Java) for the JavaScript API and it appears that this trend is beginning to happen. Now before you think that I’m really sticking a fork in the WebADF, think again. The WebADF will continue to grow and be used where it makes sense, but probably not as the “default” mapping front end for ESRI web servers. The simplicity of the JavaScript API and the way it works, makes the classic WebADF and HTML viewers obsolete for most users (I’m still waiting to see what ESRI does with Silverlight, but that discussion is for another day).
Also, coupled with the JavaScript Extenders for Google Maps and Virtual Earth, there is probably very good reasons to be looking this way instead of deploying the WebADF. I’ve also seen people abandoning third party “helpers” for the WebADF such as Geocortex Essentials (I guess we’ll see JavaScript API tools from these companies soon, eh?) to move back to simpler JavaScript front ends. There are times and places for .NET or Java server solutions, but what the JavaScript API has done is allow ESRI customers and implementors to go with a more lightweight solution and in turn brings them to more cutting edge RESTful and JavaScript technologies that can be leveraged outside of the ESRI silo.
I’ve really started to try and point my clients (and anyone else who asks) away from the Java and .NET WebADF and toward the lightweight ESRI JavaScript API. Everyone who has moved in that direction has really been satisfied and given the 9.2 release of ArcGIS Server, that is really turning things around.
James seems to be pushing ArcGIS Server again
July 28, 2008 1 Comment
It looks like the Virtual Earth ASP.NET control has finally been released. Now no longer .NET developers have to worry about their JavaScript and can focus on pure .NET. Combined with other .NET technology we could see some very immersive Virtual Earth solutions integrated into existing .NET code.
The .NET crowd has been clamoring for a pure .NET Virtual Earth solution
