Why does my Hillshade look different when I use a tool vs a function?

I’ve been getting questions from people asking why their
hillshade results display differently when they use the Hillshade function
(left) versus the Hillshade tool (right).

Hillshade function on a mosaic dataset Hillshade tool on a raster dataset


The Hillshade tool is applied at the source pixel size of the data; then the resulting raster is resampled as you zoom out of your display. In contrast, the Hillshade function is applied at the scale you are viewing the imagery at, first resampling the DEM to that resolution before applying the hillshade effect. When you apply hillshading at the same pixel size, the two hillshaded images will appear the same.

Functions are applied on your data after the images have been resampled to create the mosaicked image from the mosaic dataset, whereas geoprocessing tools are applied at the source pixel size of your data.


resampling + process ? process + resampling

Resampling the pixel size then applying a process, such as
hillshading, will not always provide the same results as applying the process
then resampling.

For more information, please see the new Help topic titled Why does my hillshade look different when I use a tool vs. a function?


Contributed by: Melanie Harlow

Posted in Analysis & Geoprocessing, Imagery | Tagged , , , | 2 Comments

Preparing a map for editing: Setting layer properties

To get the most out of editing in ArcGIS 10, use the
Layer Properties dialog box to (1) prepare symbology, (2) simplify attribute
fields, and (3) set a display expression. Doing these things for each layer you
plan to edit can help make your data compilation tasks easier and
straightforward. This post walks you through setting up a parcels land-use
layer so you can create and edit features in it.

Preparing the layer’s symbology

The Layer Properties > Symbology tab allows you to set the symbols
used to draw the layer. Since feature templates are based on the symbols used
in the map, be sure to symbolize your layers appropriately before you start
editing for the first time on a map since ArcMap creates feature templates for
you then, or anytime you create feature templates yourself. If you change the renderer
type after you create feature templates, you will end up with templates that do
not reflect the features you want to create.

When creating features, you should use either the Single Symbol or
Unique Values renderer. If you are symbolizing with unique values, make the
labels for your symbols meaningful, as the symbol labels become the names for
the feature templates. For example, the parcels layer has symbol category
labels taken from the raw attributes of AGR, COM, IND, RES, and UNK, which are
shortened versions of various types of land-uses. Expanding the text of the
symbol labels to Agricultural, Commercial, Industrial, Residential, and Unknown
will reduce the cleanup needed on your feature templates after they are created
and help other editors understand which features they are creating. The symbol
labels are also used in the entries in the table of contents and the map layout
legend, so there are additional reasons to do this. These graphics show the
Layer Properties > Symbology tab and the resulting feature templates in the
Create Features window.

When there is a problem with the symbol for a feature template, the
Template Properties dialog box displays an exclamation point icon in the
preview area. The template is also shown in the Create Features window as a
silver layer icon, rather than the symbol that will be assigned to the new
feature. This often happens when the symbology was changed dramatically after
the feature template was created, such as switching renderers or symbol
categories. If this occurs, look at the feature template’s default attributes
to ensure they match the current symbology or symbol category. You can also
simply delete the template and re-create it to synchronize the symbols.

Simplifying the attribute fields

When you look at your parcels layer in the Attributes
window, by default, all the fields are displayed in their original order and
with their names as they appear in the data source. The field names are hard to
read and understand since they use capital letters and underscores because
spaces are not possible in the actual field names. Fields that you cannot even
edit are displayed, which makes it harder to find the fields you want. This is
a lot of junk content to wade through when you want to edit these attributes! This
layer could benefit from some work on the Layer Properties > Fields tab.

The Fields tab is the central place for you to set up the
display properties of fields. Spending time organizing fields makes your
editing and overall ArcGIS experience more productive because the settings are
used throughout ArcMap, including in the attributes table, the Attributes
window, and the Identify window. In addition, they are maintained when you
share layers with others through layer files, layer packages, map packages, and
Web services.

The left side of the Fields tab contains a list of all
the fields in the feature class or table, including any fields that have been
joined to it. If you have a long list of fields but only plan to edit the
attribute values for a few fields, hide the ones you do not need to by
unchecking them in the list. For the parcels layer, you might be only
interested in seeing information about the land-uses and the IDs, so you can turn
off nearly everything else. To save even more space, hide system fields that
ArcGIS does not allow you to edit anyway, such as the Object ID, Shape, Shape_Length,
and Shape_Area. This does not delete the fields; it simply turns them off to
make it easier to access the fields you want. Many dialog boxes have option
buttons that allow you to view all fields in a layer if you need to see them
again temporarily.

The order of the fields list is the default order in
which they are displayed throughout ArcMap. You can change the order to promote
to the top of the list the fields you use most often. To reorder a field, click
it in the list and drag it to the position you want, or click the arrow buttons
to move it up or down the list. You can also select multiple fields and reorder
them at the same time. With the parcels layer, move up the IDs and land-use
code fields since you plan to edit them.

When you click a field in the list on the left, the individual field’s properties are displayed on the right side of the tab (the
right side will be blank when you have multiple fields selected). You can change
the properties that are shown in the Appearance section, which specify how the
contents of the field are displayed in ArcMap, but not the system information
under Field Details. When you click a row on the right side, an explanation of
the property is provided in the box at the bottom of the tab.

In the Appearance section, you should give your fields
aliases to specify an alternate field name that is descriptive and user-friendly.
Field aliases do not have to adhere to geodatabase naming conventions, so
aliases can have spaces between words or be as long as necessary. For example, for
the field, “LAND_USE,” set the field alias as, “Type of land-use.” The alias is
a lot simpler to read and understand than the source field name.

You can also set a field to be read-only, which means you
can view but cannot edit that field, regardless of the file or database
permissions. This is useful when you need to see the value of a field for
context, but do not want to inadvertently update its value. If you want to
distinguish certain fields-for example, to make them easier to see when editing
in the Attributes window-set the Highlight property to Yes. This will add
background shading so those fields will stand out from the others.

After a little cleanup, the list is a lot easier to
manage and edit. Only the most useful fields are shown, with clearer alias
names and a more appropriate order.

Two of the most popular requests on the ArcGIS Ideas site, where you can submit and
vote for ArcGIS software enhancements, are the ability to rename fields and
reorder them after they have been created. Although this functionality may not
be available in the underlying database, you can get the same result by
authoring your map and setting the field properties.

You should follow these guidelines when working with
stand-alone tables, since the field properties are used with tables, too. If
you create a relationship class to relate a table of landowner information to
the parcel layer, you can navigate through the related records to edit the
landowner table in the Attributes window. If you turn off unwanted fields, reorder
fields, and set other properties in the landowner table, it will be easier to find
and edit the table’s values, too.

Setting the display expression

The display expression is new with ArcGIS 10 and is found
on the Layer Properties > Display tab. Setting the display expression
ensures that the most useful information is displayed when representing a
feature in the Attributes window, the Identify window, in HTML Pop-ups, and
other places across ArcGIS. The display expression can simply be the contents of
a field by itself, which is similar to the primary display field from previous
releases. However, the display expression is more powerful because you can
customize the text. This allows you to enter your own text or combine the
contents of multiple fields. For example, you could write an expression that
would include the text, “Land-use type:” before the field value. This would be
entered on the Display Expression dialog box as, “Land-use type: ” + [Land-use
field name].


When editing, the display expression makes it easier to
navigate the Attributes window tree. Stand-alone tables have a display
expression property, so setting it on the table can help when viewing related
records, too. The display expression is also shown in the Edit tool selection
chip, which is a small pop-up that appears on-screen to help you select the correct feature when you click multiple overlapping features with the Edit
tool. For example, you are trying to select a road that overlaps a parcel
polygon. If you click the road, the selection chip appears, allowing you to
choose whether to you want to select the road line or the parcel polygon.

Content provided by Rhonda (Editing Team)

Posted in Editing | Tagged , , , , , | 1 Comment

The GeoServices REST Specification: An open standard for GIS Web services

At the plenary session of the 2010 Esri International User Conference, company president Jack Dangermond announced, “In a few weeks [Esri] will release a new REST API into the open world using a standards process”. Dangermond likened this to Esri’s release of the shapefile specification and promised that it “will pioneer open access in the Web environment.”

His promise was fulfilled with this week’s rollout of the GeoServices REST Specification, Version 1.0, a document on the Esri Web site which is freely available through the Open Web Foundation license agreement.

The GeoServices REST Specification describes a way to develop GIS Web services that follow an expected pattern of communication. The introduction of the document describes how you would implement the specification:

“To implement the GeoServices REST Specification, developers architect the back-end server to respond to specifically structured REST requests in an expected way. For example, if someone issues a request to the server to export a map image, such as http://<mapservice-url>/export?bbox=-127.8,15.4,-63.5,60.5, the server should return a map image with a lower left coordinate of (-127.8, 15.4) and an upper right coordinate of (-63.5, 60.5). How the server generated the image is not so important as the fact that it responded in an expected way when issued a URL whose structure followed the GeoServices REST Specification.”

Services that follow the specification will “speak the same language” as the REST-ful Esri Web services. That means clients can consume them with the popular ArcGIS APIs for JavaScript, Flex, Silverlight, iOS, and Android; as well as other Esri client APIs. However, you don’t have to own or use any Esri software in order to implement the specification or to build a client that works with the services.

As you examine the specification, you’ll probably notice that it looks like the ArcGIS REST API. This is deliberate. The pattern we have used at Esri for exposing REST-ful GIS services has been embraced by thousands of developers who use the ArcGIS Web APIs. It is a simple and intuitive way of structuring and talking to GIS Web services. We wanted you to feel free to implement services that follow the same pattern.

Posted in Services | Tagged , , | 2 Comments

Release of the Editing template for ArcGIS 10 – Part 2

Attribute Assistant

The attribute assistant has some significant changes for ArcGIS 10.  When you download it, you will not find the installer that you might be used to.  You will just see a simple ArcGIS Add-in.  This should help you deploy this extension to your organization.  We also modified some of the existing functions and added a few new ones.  The table below discus’s the different methods for this extension.

Value Method Value Info Details Requirements
GET_ADDRESS_USING_ARCGIS_SERVICE Url to a Geocoding service This method preforms a reverse geocode.  The default service is the ArcGIS.com geocoding service.  You can specify your own. String Field
TIMESTAMP None Stores current date and time. Date or String Field

W – stores full windows login name as domainusername

U – stores just the windows usernameD – stores the connected database user for the edit session  If you leave VALUE_DATA blank, it will store the database user name if available otherwise store full windows login.

Stores current user name. String Field
LAST_VALUE None Repeats the last value used for a field.  
X_COORDINATE None Stores the X coordinate in database units  
Y_COORDINATE None Stores the Y coordinate in database units  
LATITUDE None Stores the Y coordinate projected to WGS84 decimal degrees.  
LONGITUDE None Stores the X coordinate projected to WGS84 decimal degrees.  
FIELD Field Name Copies one field to another field in the same feature.  

A  - if you enter an A it will store the rotation using an arithmetic rotation.

If you leave VALUE_DATA blank, it will store the rotation using a geographic rotation.

Stores a rotation angle for a junction feature based on connected edge features by storing a rotation angle in the specified field.  Requires geometric network.  Target must be a point feature class that participates in the geometric network as a simple junction.  Requires ArcEditor or ArcInfo.   
LENGTH None Stores calculated length of line feature.   
SET_MEASURES If you leave ValueInfo blank, it will calculate the Ms starting with zero and ending with the length of the line.   If you enter a P for ValueInfo, it will calculate the Ms starting with zero and ending with 100. Populates the M coordinates in a line which enables using Add Route Events to point and line events dynamically along line features Requires a line with M’s turned on
TO_EDGE_FIELD <Field Name> Transfers a field value from a connected edge feature to a junction feature.  Must be assigned to a point feature class that participates in a geometric network.  Requires ArcEditor or ArcInfo. 
FROM_EDGE_FIELD <Field Name> Transfers a field value from a connected edge feature to a junction feature.  Must be assigned to a point feature class that participates in a geometric network.  Requires ArcEditor or ArcInfo. 
FROM_JUNCTION_FIELD <Field Name> Stores a value that is obtained from a specified field in the junction feature at the start of the currently edited line.  Must be assigned to a line feature class that participates in a geometric network.  Requires ArcEditor or ArcInfo. 
TO_JUNCTION_FIELD <Field Name> Stores a value that is obtained from a specified field in the junction feature at the end of the currently edited line.  Must be assigned to a line feature class that participates in a geometric network.  Requires ArcEditor or ArcInfo. 

<FieldName>| <optionalSequenceWidth>| <optionalFormatString>[seq]


Increments a column in an unversioned table and stores that newly incremented value. Uses an unversioned table that is typically called GenerateId (change in AttributeAssistant.config) to store and increment unique sequence numbers.     



<Layer Name> |<Layer Field Name>|<Sequence Field Name from GenerateID Table>| |optionalSequenceWidth|[id]optionalFormatString[seq]<any order of ID and SEQ> 


The result would look look like GRID5-0002, if the grid you intersected ID was 5 and the next number in the table was 2.

This tool requires you create fields in the Generate ID table that are a combination of the GRIDIDX(the Sequence Field Name) and the Grid ID. So the tools looks at the interesected grid, gets the ID from it, combines it with the <Sequence Field Name from GenerateID Table> to look for a field in the Generate ID table to get an seq for that grid. Say the grid you created a feature in was 5, you need a field called GRIDIDX5 in the generate ID table. 



Example:replace(([FROMMH] & “-” & [TOMH]),”MH-”,”")

Stores the results of an expression.   

Optionally enter one of the letters below to format the GUID as desired.

N – GUID  with no special characters – length 32 D – GUID with dashes – length 36 B - GUID with dashes and braces – length 38 P – GUID with dashes and parenthesis  - length 38 default – GUID with dashes and braces – length 38 Leave the ValueInfo Field blank to get the default GUID format.  Example: {3F2504E0-4F89-11D3-9A0C-0305E82C3301}

Stores a new GUID.  The target field must be a field type string field and must be long enough to store the desired format of GUID.

<Layer Name>,<Layer Name>,..|<Field Name>

Example: ssPressurizedMain,ssGravityMain|DIAMETER

Gets a value from an intersecting feature in the specified layer.  You can specify any number of layers to look for by listing them with commas between their names.   

<Layer Name>,<Layer Name>,..|Label

Example: FiveMeterSurface|Elevation:

Gets a value from an intersecting raster cell in the specified layer.  You can specify any number of layers to look for by listing them with commas between their names.   

<Layer Name>, <Layer Name>,..|<Field Name>

Example: ssPressurizedMain,ssGravityMain|FACILITYID

Gets a value from an intersecting feature in the specified layer and reports the distance along the line.  You can specify any number of layers to look for by listing them with commas between their names.   
NEAREST_FEATURE <Layer Name>,<Layer Name>..|<Field Name>|<Search Distance>

Example: wMeter,sLateralPoint|ACCOUNT|100 

Gets a value from the nearest feature in the specified layer.   

Posted in Water Utilities | Tagged , , , , , , , , , , , , , , | Leave a comment

Dude, What’s Your Segment?

by James Killick

Ever wondered what socio-economic segment you fall into? Well, now you can find out using our brand new ZIP Lookup App at esri.com/zipcodelookup!

This great new app allows you to check out any ZIP code in the USA and find out what kind of people live there based on their Esri Tapestry Segment. In my case, ZIP code 92373, the most prevalent segment, is “Connoisseurs” … woo hoo — I must be doing alright!

But that’s not all, the app will also give you facts about household income, growth rates, unemployment, age breakdown, race/ethnicity breakdown and more.

And the best thing of all – it’s completely free so check it out now!

Posted in Location Analytics | Tagged , , | Leave a comment

GeoRSS Feeds in ArcGIS

As access to real-time data becomes quicker, easier
and cheaper we’re going to need ways to consume and view it.  One example
is GeoRSS, where a service is hosted (like the USGS) that gives you a
formatted .xml file with coordinates and attributes.  There are many
web-based applications for reading in these feeds (SilverLight, Flex, and
JavaScript API’s for example) but I want to view this data in ArcMap natively,
query it and use it in my analysis.  

To accomplish this task it’ll require the use of the
Data Interoperability Extension for ArcGIS and access to a GeoRSS service.
 For this purpose, I’ll be using the USGS real-time worldwide
earthquake listing here.

The first thing I need to do is add a new
Interoperability Connection in ArcCatalog by double clicking on Add
Interoperability Connection;


Then, click on the ellipses button next to the Format
and browse to GeoRSS/RSS Feed;



Copy/Paste the GeoRSS link into the dataset dialog;



*Note* You can also
change some parameters of how the feed is parsed out by clicking on the
Parameters button.

Once the connection is created you can simply drag and
drop the Entry Point layer into the data frame of ArcMap to view the


Once in ArcMap you can symbolize the data as you see
fit and begin to query and analyze the data;


*Note* To handle data updates the data frame must be refreshed in order for the layer to call the service for new information.

Questions?  Comments?  Please post them below in the comments section of the blog.

Posted in Uncategorized | Tagged , , , , | 2 Comments

Release of the Editing template for ArcGIS 10

We are happy to announce the release of the Infrastructure Editing Template for ArcGIS 10.This new release takes advantage of some of the great additions to ArcGIS 10.  You will find a new datamodel which encompasses many new layers.  You will also see an updated symbol set, a symbol set designed to be overlaid on imagery, topographic, and parcel basemaps.&nbsp; The editing map document was updated to show you have to set up feature templates.  You will see how we reordered, highlighted and set some fields to read only, as well as hide a few.  We think you will like the new data model, symbology and the new mxd.  Now on to the tools!

We migrated the Editing and Reporting toolbars and the Attribute Assistant to ArcGIS 10 Add-ins.  Not only did we upgrade them to ArcGIS 10, but included a series of bug fixes, config changes and new functions, which all came from your suggestions, so please keep the feedback coming.  Lets breakdown the Add-In’s and discuss the changes.

Desktop Editing Toolbar – Changes and New Tools

The first thing you might notice is the Add Laterals icons are missing, but there is a new one that sort of looks like it.  We compressed the Add Lateral tools into one function that looks at the selected features and compares them to the config file and generates laterals from them.  This allows you to generate many types of laterals at once.  To the right of it, there is a new tool, Connect Closest.  This tool will connect a series of points, say a row of manholes, with a line, such as a sewer main.  If we look to the left you will see a a large red button with a ! in it.  This is simple layer inspector.  It looks at a feature class and lets you step through each feature one at a time.  Real handy for reviewing those redlines or field notes.  If we keep moving left, you will see an icon with a line and 123 in it.  This tool allows you to quickly calibrate a line that is M enabled.  Should help you plot your CCTV data on your sewer.  Next is the Merge Geometric Network Features, an ArcScript that has been around a while, so we thought we add it to the toolbar.  I agree, the icon looks like it is breaking features apart.  We will see if we can change this to something more meaningful.  On the far right, is a new tool included with the Attribute Assistant.  This tool triggers the change event for all selected features.  So you can manually fire out the Attribute Assistant rules.  The last new tool on the toolbar is the Incremental Network Loader.  You can find out about the new tool here

Desktop Reporting Toolbar – Changes and New Tools

We mainly enhanced the existing tools.  We had a bunch of request to return the edges of a trace in the selection set, so we added another trace button below each trace that does just this.  There is a new way to run the Isolation trace, in batch.  The Summary Isolation trace will loop through all selected water mains and run an isolation trace for each.  The results are stored into a feature class which you will find in the Capital Planning dataset.  I warn you against running this on all your mains, it takes a while(don’t worry, the tool warns you to if you make the mistake on clicking it without a selection set).  A new tool that we are all excited about is the Profile Graph tool.  This tool lets you pick two manholes, runs a find path trace between them, intersects the result with an elevation surface and plots the manholes, mains and elevation onto a graph for you.  We think you will really like this tool.  There is a known issue right now though.  When the chart opens, you have to turn off the manholes in the chart properties, then uncheck automatic from the left axis.  You can then turn the manholes back on.  The last tool on the toolbar, Attribute Transfer Loader, was a request from a user who was transferring data using the attribute transfer tools.  If you ever used these tools, you know you had to set them up each time you opened ArcMap.  You can now set up the mapping in the config and load it to the attribute transfer dialog.  

Desktop Tools – Config File Changes

If you changed the config file for 9.3.1, you will need to move these changes into the new config file.  You will see in the new config, we reworked a lot of the entries in a nested xml structure.  This allowed us to include some new options and load the config file faster.  For example, the Add Laterals Tools.  This was a long series of entries and you were limited to the 3 types we exposed.  Now you will see you can use these tools on any number features.  Here is a screen shot.

Also, you will see that there is an xml array that defines the points along.  We had a lot of request to allow the option to add more than one point along the line.  With this xml array, you can have it add any number of points along the line, I left a sample in the config to show how to do this, notice it is commented out. 

Desktop Tools – Construction Tools

You will also find an installer for a set of construction tools.  These construction tools call some of the functions on the toolbar and expose some new functions.  These new tools should further speed up editing and creating new assets with ArcGIS.  Note: at the moment, the construction tools and the toolbar use the same config, but they each have their own copy.  We are looking into how to share one config between them. 

Let’s take a detailed look at them.  

                Screen shot of the new construction tools for points and lines.


For lines, there is one new tool, Create a line with end points.  This tool will end two points at the end of the line you sketch.  The config file controls will points get added to what line.  So you need to modify the config to list the line layer and the ending point layer.  Using the new xml config file, you can specify any number of layers for this to work on.

For points, there are a number of new tools.  Some are samples that come with ArcGIS, some are new tools we added, let’s start at the top.  The Points along a line at is a great sample that comes with in the Developer Kit.  A great sample for creating a series of points at an interval.  Next is a custom tool, Add a connection and the lateral.  This tool does the same thing that the Add Lateral tool does on the toolbar, but this one lets you create the point and immediately connect it to the main.  The Create a point and line tool does the same thing Connect Closest tool does, but this does it as you click.  Imagine you are creating manholes.  Each time you drop one, it searches for the closest manhole and adds the main.  The last construction tool is the Add a point and split an intersecting line tool.  This does exactly what it says, split the line that you click on.

We are very happy and proud with this template for ArcGIS 10.  Let us know if you have any issues or any suggestions.   In the next blog, we will talk about some changes in the Attribute Assistant.

Posted in Water Utilities | Tagged , , , , , , , , , , , , , , | 9 Comments

9.3.1 Fiber Network Editing Template install updated

A few minor bugs fixes have been incorporated into the 9.3.1 version of the Fiber Network Editing Template. The bugs fixed are:

  • Device Connections Editor dialog not showing under certain circumstances.
  • Device Connections Editor connection information not being saved on clicking the update button.

The update is available here.

Keep the feedback coming telecom_templates@esri.com



Posted in Telecommunications | Tagged , | Leave a comment

ArcGIS Mobile and ArcGIS Desktop

You may have noticed when logging into the Customer Care Portal that you see ArcGIS Mobile available for download in more than one location (both ArcGIS Desktop and ArcGIS Server). That is because it is now licensed for use with both ArcGIS Desktop and ArcGIS Server! If you have an ArcView license, you can use ArcGIS Mobile to view your maps as well as collect and update GIS data!

In support of this license change, the Mobile team has uploaded a video on our resource center video gallery to guide you through the process of using ArcGIS Mobile with ArcGIS Desktop. We have also uploaded 2 additional videos on how to Create A Mobile Project and How to Use the Mobile Project Center.

To fully support the ability to use ArcView with ArcGIS Mobile, we had to update both ArcGIS Mobile and ArcGIS Desktop so there are two critical updates that you need to download if ArcView is the license that you plan to use:

  1. A general patch to ArcGIS Desktop that supports creating a Global ID column to a feature class (required for field editing)
  2. The latest software update (build 2475) of ArcGIS Mobile that is available through the Customer Care Portal (resolves a licensing restriction with the Create Mobile Map and Synchronize Geoprocessing Tools).

For more details on the licensing change, please visit the products page on our corporate web site for details.

Mobile Team



Posted in Mobile | Tagged , , , , | Leave a comment

ArcGIS Explorer Current User installations now available

The ArcGIS Explorer Team is pleased to announce that ArcGIS Explorer Current User is now available from the ArcGIS Explorer Resource Center on the ArcGIS Explorer 1500 download page.

ArcGIS Explorer Current User is a way for people who are not administrators on their system to use ArcGIS Explorer. It does not require administrator privileges to install, so anyone can download and install ArcGIS Explorer Current User for themselves.

Please note that ArcGIS Explorer Current User is not intended for users that have also installed other ArcGIS products – those users should install the standard ArcGIS Explorer setup (which does require administrative privileges).

See the ArcGIS Explorer Current User installation guide for more information.

In addition to ArcGIS Explorer Current User, there are two expansion packs created specifically for use with ArcGIS Explorer Current User that are available. Use the Data Access Expansion Pack for ArcGIS Explorer Current User to expand geodatabase functionality. With this expansion pack, users are able to make direct connections to multi-user geodatabases from ArcGIS Explorer Current User.

The Projection Engine Expansion Pack for ArcGIS Explorer Current User is also available. Use this expansion pack to add more projection and geotransformation options for use within ArcGIS Explorer Current User.

(Lindsay King – ArcGIS Explorer release manager)

Posted in Uncategorized | Tagged , | Leave a comment