Monthly Archives: September 2008
ESRI President Jack Dangermond’s presentation at the Western Governors’ Association meeting in Jackson Hole, Wyoming, has recently been posted in the Showcase area of the ESRI GIS for Conservation Web site.
We covered the elements of the ArcGIS Explorer presentation in an earlier post, but the entire presentation is now available online, and tells a compelling story about protecting wildlife habitat areas, managing natural resources, and how GIS can be used to solve and mitigate the sometimes competing issues and problems that arise.
Currently the most popular download on the
Parcel Notification List application written and submitted by Jeff
Archer from ESRI. In
this video Jeff takes a few minutes to show how the sample works and
gives a quick run-through of the code and components under the hood.
While local governments may be able use the application “as-is”, there is enough
starter material for any Web application that needs to select features based on
a distance from other features and return tabular attributes of the results.
Download it, use it, modify it… it’s up to you. And please leave comments on
the download page if you have any questions or suggestions you think might help.
Contributed by Jim Barry of the EDN team.
The Geostatistical Analyst (GA for short) uses sample points taken at
different locations in a landscape and creates (interpolates) a continuous surface.
The sample points are measurements of some phenomenon, such as radiation leaking
from a nuclear power plant, an oil spill, or elevation heights. Geostatistical
Analyst derives a surface using the values from the measured locations to predict
values for each location in the landscape. Continue reading
If you haven’t heard, the ArcGIS Development Team has just released a new .NET utility called the ESRI API Evaluator. This handy tool allows you to scan all of your ArcGIS .NET code and generate a complete set of API usage statistics. This will reveal the DLL dependencies, version information and the number of calls made to all ESRI assemblies, interfaces and members.
Help improve the product
One of the most important features of this tool is that it allows you to send your API usage information directly to the ArcGIS Development Team. Once received, this information will be used to:
1. Better understand the APIs that our customers are using (most popular).
2. Make improvements to focused areas of the SDK (documentation and samples).
3. Make decisions for future API development projects.
API Evaluator Scenarios
Scenario I – Help improve the SDK
You have been working on a number of ArcGIS projects and have had difficulty implementing various parts of the SDK. Use the API Evaluator to let ESRI know what areas of the API are most important to you by uploading the usage statistics without actually sending us the code!
Scenario II – Improve your code
You have been working on an agile development project with a team of developers. You would like to discover which parts of the API have been used the most by the team and if code reuse has been maximized. Use the API Evaluator to determine the number of calls to all interfaces, methods and properties in the .NET assemblies and look for areas of improvement.
Scenario III – Deployment
You would like to determine the .NET Framework version, and ArcGIS license and extension requirements for an application. Use this information to help determine the software and licensing requirements for deployment systems.
It’s easy to use!
Step 1. Start the tool and run a new scan.
Step 2. Select the folder(s) you wish to scan.
NOTE: If you are scanning a Visual Studio 2005/2008 web application, build and publish the website to generate the precompiled assemblies first.
Step 3. Optionally, supply your contact information if you plan to upload your scan to ESRI.
Step 4 – Confirm your selections.
Step 5 – Review the results.
Step 6 – Upload results to ESRI. Simply select the “Upload Scan” menu.
A few reasons to give it a try
I’m sure you can think of many different uses for this tool, but in general, you can use this tool to:
1. Determine the general API usage for larger or unknown code samples.
2. Determine the licensing required to run an application.
3. Locate redundant code sections and make improvements.
4. Detect library dependencies to help with deployment scenarios.
5. Detect .NET version dependencies.
6. And most importantly, help improve the product (see below).
Where can I download it? You can download the tool from the ArcGIS Engine Code Gallery.
Where can I find more information? You can find the documentation on the ArcGIS Engine Resource Center online.
We want your feedback!
Although the “Upload Scan” functionality is 100% optional, we do appreciate all feedback from the developer community, so we hope you find this tool useful and you can spend a few minutes uploading the results back to ESRI.
Let us know if you have any questions or feedback.
Thanks for your participation!
ArcGIS Development Team
Glacier National Park was named after the glaciers that carved and sculpted its landscape millions of years ago. But according to the Glacier National Park Web site by 2030 there will be no glaciers left in the park, the result of global climate change. The park originally had around 150 glaciers, but today there are 26.
Grinnell Glacier is one of those 26, and is a popular hiking destination. Here’s a recent photo, taken earlier this month during a stormy hike to the glacier’s edge. The photo shows Upper Grinnell Lake in the foreground, the edge of the Grinnell Glacier to its left, and the Salamander Glacier and Salamander Falls above the lake.
According to Wikipedia, Grinnell Glacier is one of the most photographed glaciers in the park. Photos dating back to the mid-1800s have been archived, providing documentation of the glacial retreat over the years (shown below from Wikipedia):
The USGS Northern Rocky Mountain Science Center has more details and photographs.
We can also take a look at Grinnell Glacier using ArcGIS Explorer. First we used the GeoNames Search task (covered in a previous post) to locate the glacier.
Here’s the glacier as seen in Explorer’s default map.
We can add the topo layer (from the layers tab on the ArcGIS Explorer Resource Center) for another perspective.
Comparing the imagery with the older topographic map using the transparency or swipe tools, we can see the change in the size of the lake and the glacier’s boundary.
By Charlie Frye, Esri Chief Cartographer
Most of us use digital elevation models (DEMs) which are raster data sets that represent a continuous elevation surface in which each cell represents the elevation at its location. DEM data are typically available in tiles that are sized to balance ease of data sharing with coverage so that those who need several tiles to cover their area of interest are not overburdened with extensive post-download data processing.
Just a few days ago we published a blog post on the NOAA imagery services and ArcGIS Explorer maps available for download.
Those services are regularly being updated on ArcGIS Online, and whenever you open the map or layer (that you can download from the post above) you’ll see the latest published imagery.
Here’s what it looked like a few days ago:
And here’s what it looks like today:
Comparing the two you can see that a lot of new imagery has been added to the mosaic.
The following post was contributed by Craig Gillgrass a product engineer on the geodatabase team who spends the lion’s share of his time working with geometric networks.
The topic of when to use the Connect and Disconnect commands when editing geometric network features came up a couple times during our Geometric Network session. Based on those discussions and other questions from users I’ve re-written the help topic on these commands. What follows is a variation of the new help topic which should be available online soon.
As covered in the topic About editing geometric network features; the geometric network automatically maintains connectivity between network features based on geometric coincidence. For example, when using the ArcMap snapping environment, if a junction is added along an edge, or one edge is added along another edge, they will automatically become connected to one another. The ArcMap snapping functionality will guarantee geometric coincidence when adding new network features amongst existing network features and ensure the proper connectivity is established. Therefore, it is generally not necessary to use the Connect and Disconnect commands with most network editing workflows, but there are some exceptions.
The Connect command creates topological relationships between the selected feature and the features to which it is geometrically coincident; if features are not geometrically coincident with the selected feature, connectivity will not be established. Connect will also honor the subsumption rules of the geometric network; orphan junctions will be subsumed by user defined junctions when connectivity is established.
The following diagram demonstrates how Connect works in certain situations; the dashed arrow indicates on which feature Connect is being used. The legend can be used for both diagrams:
The Disconnect command removes the topological associations a feature has to other features in the network. Disconnect does not delete the selected feature from the database or geometric network. It also does not remove the logical network information for the feature.
Disconnecting a connected junction will leave an orphan junction in its place. Disconnecting an edge honors the geometric network rule that an edge must always have junctions at its end points. Disconnecting an edge with user defined junctions at its end points will result in orphan junctions at the end points. Note that if orphan junctions are at the edge end points; new orphan junctions will not be created. Disconnecting an edge which has junctions that are only connected at mid-span along the edge will not result in the creation of an orphan junction.
The following diagram demonstrates how Disconnect works in certain situations; the dashed arrow indicates on which feature Disconnect is being used:
The Connect and Disconnect commands are designed to complement each other and should be used for transitory editing workflows which will be completed within a given edit session. You can think of them as bookends; used to start and end a workflow. Some examples of these kinds of workflows are:
- Moving a feature without moving the features to which it is connected
- Repositioning a junction or an edge along an existing edge
- Inserting an edge feature between two existing network features.
The general workflow for these edits is to disconnect the feature, perform the edit, and connect the feature. Keep in mind that disconnecting a feature is designed to be a temporary situation. Since the geometric network determines connectivity based on geometric coincidence, disconnected features may become connected during editing, such as when a new feature is created coincident to a disconnected feature, or when performing a reconcile operation in which a feature is inserted coincident with the disconnected feature.
Other things to note about he Disconnect and Connect commands are:
- Each works on the entire edge feature; not a section of the edge feature
- It is not possible to Disconnect or Connect one end point of an edge, but not the other end point. Connect and Disconnect work on the entire feature.
The Connect and Disconnect commands can be used to improve your editing experience with network features; but using them does require an understanding of rules that govern geometric network editing; which is available in the About editing geometric network features topic . I’ve gone over some examples of when Connect and Disconnect can and should be used and what to be aware of when using these commands.
My previous post about integrating 9.2 Web ADF controls in ASP.NET Web Parts discussed a number of workarounds required to successfully utilize ADF controls within a Web Part. For 9.3 the ArcGIS Server .NET development team took some time to evaluate and fix any issues encountered while using ADF controls in a custom user control, composite control or ASP.NET Web Part. We tested Web Part deployment within SharePoint 2007 and confirmed that it worked without any ADF specific workarounds. As a result, the 9.3 Web ADF provides a solid foundation for integrating GIS components in Web Parts designed for SharePoint deployment.
Click here to download a comprehensive Web ADF-Web Part sample (C# and VB.NET). The sample code includes two projects: a class library which contains Web Parts, and a Web application to assist in deployment and testing. The sample also includes a ReadMe.txt to get started and a Word document which steps through the SharePoint 2007 deployment process for ASP.NET AJAX-enabled Web Parts.
The class library project (ADFWebPart) contains two Web Parts: MapWebPart and MapGridViewWebPart. MapWebPart contains MapResourceManager, Map,Toolbar, and Toc controls. This sample illustrates how to add, structure, and initialize the aforementioned controls, add a custom tool, and expose properties for use in SharePoint.
MapGridViewWebPart contains a MapResourceManager and Map. It also contains an UpdatePanel with a GridView. It requires that a ScriptManager be in the page to enable asynchronous updates of the GridView (via the UpdatePanel).
All properties for setting the dynamic resource, data layer for display, feature limits and field aliases are public and presentable within SharePoint. An ArcGIS Online cached map service (StreetMap) is used as a background map resource to provide spatial context.
The following screenshot provides an example of both Web Parts deployed within SharePoint 2007.
To utilize either Web Part outside of SharePoint or to test before SharePoint deployment, use the file system Web application (CustomControlsWebSite) included with the sample. The Web application contains a simple aspx page designed to emulate a runtime scenario where an end user wants to add a Web Part within the current session. To personalize the page (e.g. add a Web Part at runtime) the current session must be associated with an authenticated user. By default, a file system Web site will use integrated authentication. If deploying as a Web application in IIS, you will need to disable anonymous access to the Web application in IIS. Enabling integrated authentication may offer the easiest solution since you do not need to configure or explicitly define authentication details; instead the authenticated user will be the user account under which the client (browser) is running.
The default personalization provider for ASP.NET 2.0 is SQL Express. If you do not have SQL Express installed, a personalization store will not be created (upon initial execution of the application) and an error will be returned when attempting to add the custom Web Part to the page at runtime. To alleviate this requirement, the Web site uses a custom personalization provider that stores information in text files. The code, markup, and discussion for this technique is provided in the Microsoft article Web Parts Personalization Providers.
Contributed by Rex Hansen of the ArcGIS Server .NET software development team
ArcGIS 9.3 does not provide a geoprocessing tool for creating ArcSDE
connection files (.sde files). Some of you have requested such a tool for security
reasons – typically because you do not want .sde connection files hanging
around on machines. Rather, you want to automatically create a connection file
in a temporary location, use it in your script or model, and then delete it
within the process you are running. Others need the ability to create .sde files
on the fly because the connection properties, such as what version to connect to,
are not known at the start of the process. Having to stop the process for someone
to manually create the .sde file with the correct properties really isn’t an
option anyone wants to entertain. Continue reading