Ok, so now that 9.3 has been released and the http://resources.esri.com page has been released to the public (previously is was just for beta members) I thought it would be a good time to jump into some Javascript API samples. I wanted to make the examples as close the real world as I could think of. I also wanted to use just services that are currently hosted by esri online. That way we can make sure that everyone is on the same page.
My first example that I came up with is the following.
To change locations of the map, just edit the minx,miny,maxx,maxy values in the query string
This uses the dojo toolkit to create the graphics, you gotta love the dojo!
The esri JS API goes above on beyond most other JS libraries with its ability to leverage identify, query and custom geoprocessing tasks served up by ArcGIS Server
ESRI JS Methods Leveraged
*new esri.tasks.IdentifyTask> new esri.tasks.IdentifyParameters()> identifyResults
*new esri.Graphic> new esri.symbol.SimpleFillSymbol
I am so bummed, I know this is not a big deal for 90% of the world, but large companies often have legit reasons for not upgrading to latest and greatest.
Along with the iPhone, some of the newer devices like the LG Vue, the Samsung Instinct and about half a dozen others will serve to radically increase interest in LBS services. That will force the current device makers — namely Garmin and TomTom — to consider opening up their ecosystems to applications that offer more than just maps and traffic services.
I am pretty stoked about the new Samsung Instinct from Sprint. This phone among other things really has taken location based services to the next level. Powered with A-GPS the Instinct has everything in place to become a serious platform for consuming LBS.
This coupled with with the J2ME API and an Instinct API that has been promised to be “totally open” will give developers tools to drool over.
I got the chance to sit in on a 1 day seminar for ArcGIS Server 9.3 here at my work. There were about 20 energy companies represented in the 75+ people in attendance.
ESRI stated that 9.3 is done, and it ships first week in July.
Ismael Chivit has the ability to really drive home the importance of the 9.3 release. 1.5 years ago I was pretty discouraged with the direction that ESRI was headed and its flat out self denial of the geospatial revolution that was underway.
I am not sure what or who changed inside the company but it is abundantly clear that they have decided to embrace the change and not fight it. They now stand clearly poised to be a major factor in the geospatial web and traditional GIS for years to come. Which is a good thing, not just for them, but for all the GIS professionals that have made careers out of using, developing and selling services designed around ESRI technology.
I cant wait to start getting some ESRI 9.3 REST/JS samples up online here. I have been playing quite a bit with it and am very excited about its future…
Re: Cannot Create Web Application - No Services Listed
Author
Mark Bittner
Date
Feb 06, 2008
Message
ArcGIS Server is working properly now but not because of anything I did. We had a large electrical storm one night and when I came into the office the next morning, everything had rebooted and Server was working fine. During my problems, I had rebooted all my hardware at least 100 times and never solved the problem. Somehow the lightning fixed it. Go figure.
 For the most part the reviews have been very positive, its nice to see ESRI recognizing changes in our industry and I think 9.3 goes a long way to embracing those changes…
was demoed yesterday at noon. What initially was to be a small group was moved to a larger room to accomidate a lot of people. This turned out to be some very encouraging info for several of the people in attendance.
The flex api will not be available at the 9.3 and it will mirror the JS api.
Pretty much the hit of the conference thus far. Each session involving either the rest or JS portion of the 9.3 release have been packed. Really some good stuff.
One thing I noticed that I liked was the new geometry server in 9.3. This will reduce overhead on the server and it was involved in a ton of the demos.
Also, another thing of note. It appears that VE and the VE api extension for AGS can only use cached maps. This is important not because of any base services that might be coupled with VE from AGS, these should be easy enough to cache in 9.3. The issues come up when you are talking about GP Server results. Unlike AGS and the GMap API, in VE you will need to draw all those graphics on the client side, in a word, eek.
Also, if you are wanting to use your cached maps in Google or VE they will have to be cached in the same projection as google and VE. This should be easy enough but an important note none-the-less.
First day went well, it’s just a way better experience for developers than the UC. Lots of people here, not sure a total but seems to be more than last year. There is much more access to the people that write the code that you use on a day to day basis.
I will hit the plenary this morning and hopefully will have more to say. This summit is geared more towards the release of 9.3. I am pretty stoked to find that the REST API for 9.3 will not have any license restrictions, and from what I gathered can be used much like the yahoo and google APIs.
This just makes sense all the way around as it’s a win for ESRI and for the developers trying to convince bosses on why to go with ESRI as opposed to other options.