Monthly Archives: December 2007
The SOAP API provides a framework for working with ArcGIS Server using SOAP. Each ArcGIS Server service maintains a WSDL (Web Service Description Language) which defines how you can interact with the service using the SOAP API. The WSDL defines a SOAP proxy class, one for each service type (map, geocode, geoprocessing, and so on), and a set of value objects. You can use methods on the proxy, coupled with value objects as input parameters and returned results, to interact with ArcGIS Server services in a stateless manner.
The Web ADF includes pre-generated SOAP proxies and value objects which help you use the SOAP API with ArcGIS Server Web services (Internet connection) or with the server object directly (Local connection). These pre-generated objects are included in the ESRI.ArcGIS.ADF.ArcGISServer.dll. Merely browsing the contents of this assembly can be confusing because of the hundreds of classes it contains. Earlier this year we created an object model diagram for the SOAP API and put it online. We divided the diagram into eight logical areas:
- Network Analyst
Please leave us suggestions for this diagram as we are in the process of updating it for the 9.3 release.
-Sterling Quinn and Rex Hansen
By Charlie Frye, Esri Chief Cartographer
Using ArcMap to symbolize a hillshade raster layer (the output of the Spatial or 3D Analyst’s Hillshade tool) is pretty straightforward, and the default symbology (black to white ramp) doesn’t look too bad. In fact, if your hillshade layer is the only layer in your map, and if you don’t mind not seeing some of the details that have been visually absorbed into the darker tones, the default symbology is okay. To be fair, the default symbology for hillshades is useful for much more than just terrain depictions, so it’s good to know what might be helpful when depicting terrain with a hillshade. The image to the left is an example of a hillshade using the default color ramp. Continue reading
Just prior to this latest release a couple of the ArcGIS Online services which deliver content in several of the maps and layers available through the Contents tab on the Explorer Resource Center were updated. These changes include the following:
- World Shaded Relief: added additional levels of detail
- Physical World: added additional levels of detail, plus bathymetry at small scales
An ArcGIS Online Forum post also covers these changes, with a few additional details.
To view these updates, you’ll have to clear your cache for these layers. To do so, choose Tools, Manage Layers, and then select the layers above (if you are using them in your map) and click the Clear Layer Cache button.
If you don’t use these layers regularly, but want to make sure you’ve cleared their cache to see the updates, you can take your cache housekeeping a little further and delete all of your cache, and start afresh. This isn’t required, but you might want to do this from time to time just as a regular housekeeping task.
Remember that if you do clear all your cache, you’ll be fetching fresh cache from ESRI’s servers, as well as from any other servers that you may connect to, and generating new cache for your local data sources. Your performance will be a little slower while you fetch or generate cache again.
To clear out your cache, choose Tools, then Options, and choose Cache in the options list. Click Dick Cache, and under Cache Clean Up choose All Caches before clicking the Delete Caches button.
See the Help topic Cache Management in ArcGIS Explorer for additional details, and more information.
There will be other service updates during Q1 next year, and we’ll keep you posted as to when they’ll be happening.
By Aileen Buckley, Mapping Center Lead
The map excerpt shown at right (click on it to see the details) shows an example of hollow cased roads. The map is from a mosaic of USGS DRG image files. The map specification requires that the cased road symbol contains a transparent gap. The examples shown below were created with ArcMap 9.2 and used cartographic representations to re-create the effect on the USGS DRG map.
A simple two-layer cased line symbol won’t work, as there’s no way to define the center portion of the line as ‘no color’. A white center would not look right as it would block out any information below the roads in the map’s drawing order Continue reading
The ESRI Virtual Campus recently released a recording of the training seminar Authoring and Publishing Optimized Map Services. Excellently presented by Danielle Hopkins (ESRI Educational Services) and Tom Bole (ESRI Development), the seminar covers best practices for authoring maps that will be published on an ArcGIS Server. Our team reviewed the content before it was presented and we feel it is valuable for all ArcGIS Server users.
The next live training seminar on January 24 will discuss ArcGIS Server geoprocessing services.
The ArcGIS Explorer Team is pleased to announce that today, at approximately 1:58 p.m. PST, the newest version of ArcGIS Explorer – Explorer 440 – was released.
If the ESRI servers are your home servers, you’ll be notified that there is a new version available the next time you start the application. Just follow the instructions to download and install this new release.
For those that deploy Explorer from your own home servers, you’ll need to swap your versions and update your version.html to push out the new release to your users.
This release has lots of new features, check out the What’s New document for a detailed list of all the enhancements, changes, and fixes. At the top of our list are ArcIMS improvements, including the ability to access sub-layers, and the addition of new point symbols and the ability to add your own custom point symbols. We’ll be covering these in more detail here on the blog.
Feel free to send us your feedback, and let us know what you think. We’ll also be monitoring the Explorer support forum to help you with any questions that you may have.
- The ArcGIS Explorer Team
Tom Brenneman contributed this tip for .NET developers:
When creating a custom task or other component that will plug into a web application it is often useful to embed the resources for that component in the assembly itself. This greatly simplifies deployment because you will only need to deploy the assembly instead of all the external resources like JS files or images.
Here are some simple instructions for using embedded resources.
- Add the resource to the project (Right-click the project in the solution explorer and click Add > Existing item).
- Set the Build Action property of the file to Embedded Resource. (Right-click the file in the solution explorer and click Properties).
Add a WebResource attribute to AssemblyInfo.cs. Like this:
[assembly: System.Web.UI.WebResource("esri_samples.esriZoomIn.png", "img/png")]
Use the ClientScript manager to use the resource.
For images the GetWebResourceUrl method will get you a URL to the image. For example the following code gets a url for the esriZoomIn image embedded above.
string sZoomUrl = Page.ClientScript.GetWebResourceUrl(this.GetType(), "esri_samples.esriZoomIn.png");
protected override void OnPreRender(EventArgs e)
string scriptLocation = this.Page.ClientScript.GetWebResourceUrl(this.GetType(), "stl_samples.clipboard.js");
Some related reading you might find useful:
We’ve been a little quiet here on the blog for the last couple of weeks. The reason? We’ve had our heads down working on the next release, which we’re hoping to deliver very soon.
Here’s a quick peek at a few of the new point symbols that will be included with this new version. In addition to the ones we’ll provide, you’ll be able to add your own custom symbols by choosing .jpg, .bmp, or .png files from your local drives or network, or from the Web.
By Aileen Buckley, Mapping Center Lead
The illustration at left shows a map of the Paris Metro system (RATP). The routes are depicted in a schematic view and this kind of map is challenging to create because multiple routes may share the same path, for example multiple bus routes along a single road. When this happens, the coincident routes are offset in a fashion that makes it possible to understand the path each route is taking. When using ArcMap and line features for the routes, the coincident features draw on top of one another, making it difficult to visualize.