shrug-l: Review of ESRI User Conference

Christopher McGarry ChristopherMcGarry@WilsonMiller.com
Fri, 19 Sep 2003 11:34:16 -0400


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C37EC3.7C4C8D20
Content-Type: text/plain;
	charset="iso-8859-1"

Greetings-<?xml:namespace prefix = o ns =
"urn:schemas-microsoft-com:office:office" />

 

Below is my review of the 2003 ESRI User Conference in San Diego. I have
mainly focused on the technology aspects (my background) of what I saw at
the user conference.  This however does not mean that all of the information
presented below will necessarily be released or implemented, as the products
are still being developed and tested.  Additionally, this information is for
general interest purposes only and should not be referenced in any official
capacity.  

 

Thanks

 

Chris McGarry

 

--------------------------------------------- 
Chris McGarry 
Sr. GIS Specialist 
WilsonMiller Inc. 

1311 Executive Center Dr. Suite 100 
Tallahassee FL 32301 
(850) 878-5001 
http://www.floridagis.com <http://www.floridagis.com/>  
--------------------------------------------- 

 

***Keynote:

 

The theme of this year's conference was "GIS - Serving Our World," which has
two different but related meanings for GIS professionals.  One meaning
refers to the way GIS professionals are serving their community; the other
refers to the way GIS (and much of technology in general) is moving towards
integrating data on ever-increasing scales.  

 

For more on the Keynote please see:

 

http://www.esri.com/events/uc/openingday.html#jacks_presentation
<http://www.esri.com/events/uc/openingday.html#jacks_presentation> 

 

***Plenary Session:

 

Several Products and enhancements were shown during the plenary session and
are detailed below.

 

--ArcGIS 9:

 

According to David Maguire, director of products, users of ArcGIS 9.x should
notice improvements in reliability, scalability, and interoperability.  The
user interface is not much different than ArcGIS 8.x, and existing tools and
extensions for 8.x should work in 9.x.  I will discuss each aspect of ArcGIS
in detail later.

 

--ArcGlobe:

 

ArcGlobe was the best wiz-bang demo of the whole conference and certainly is
the best realization of an all-encompassing global GIS data viewer thus far.
Imagine looking at the entire globe (these data come with the software) and
clicking a bookmark that says "Tallahassee - Monroe St." and instantly the
viewer starts to "fly" into the Northwest Florida area, then into the
Tallahassee Metro Area and then right into Monroe St. right in front of the
Capital Building with imagery so detailed that you can see a taxi waiting to
turn onto Apalachee Parkway.  Now imagine this whole scene flipping on its
side to reveal a 3-D view of downtown including photo-based renderings of
buildings, and CAD models of streetlights and cars (think ArcScene).  

 

ArcGlobe only loads the necessary data at the necessary resolution to show
what is needed at that moment, thus allowing the computer to actually draw
the information in an animated fashion. All of this is of course dependent
on what information has been added, which brings up the next part of the
demo.  Jack added a live ArcWeb data service, which I believe was provided
by the NOAA National Center for Atmospheric Research, of an animated raster
image showing the global vapor stream.  The result was a rotating globe with
an animated raster dataset of the global air stream.  

 

So here, in my opinion, we begin to see the beginning of Jack's ultimate GIS
viewer.  Imagine being able to plug in a multitude of ArcWeb services
(ArcIMS and ArcGIS Server), which were created from globally integrated
geodatabases (ArcSDE) based on Geodatabase data models (CASE Tools and
ArcCatalog) created from data collected in the field (ArcPad and Tablet PC),
into this global data viewer and you can begin to fully appreciate, or at
least understand, the way ESRI is transforming their product line to attain
the ultimate goal of global GIS.  

 

According to one of the product reps I spoke with, ArcGlobe should be able
to run on most desktops.  However, a 3D acceleration card is recommended as
well as ample RAM (I would recommend about 15 terabytes).  

 

For additional information see:
http://www.esri.com/news/arcnews/summer03articles/introducing-arcglobe.html
<http://www.esri.com/news/arcnews/summer03articles/introducing-arcglobe.html
> 

 

 

--ArcPublisher:  See below

--ArcToolbox and Modeling:  See below

--Network Analyst:  See below

 

 

***Keynote and Notable Awards

 

Peter Hillary, son of Sir Edmund Hillary, who with Tenzing Norgay was the
first to climb Mt. Everest 50 years ago, gave the audience a multimedia
presentation that included a 3-D fly-by of Mt. Everest itself using
ArcScene.  Since I could not even begin to give justice to this presentation
please see: http://www.esri.com/events/uc/openingday.html
<http://www.esri.com/events/uc/openingday.html>  or
http://www.nationalgeographic.com/everest/
<http://www.nationalgeographic.com/everest/>  for more information.  

 

 

--GeoData.gov:

 

The ESRI Presidential Award was given to the U.S. Department of the Interior
for the newly created GeoData.gov GIS data portal.  This is part of the
National Geospatial One-Stop initiative.  Please see http://www.geodata.gov/
<http://www.geodata.gov/>  for more information.  

 

 

***Technical Sessions:

 

I will describe each product individually giving as much information as
possible.

 

--ArcGIS 9.x

 

ArcGIS 9.0 will be the next release of ESRI's flagship software package.  I
begin by talking about the core program itself (ArcMap and ArcCatalog), then
I discuss the underlying components (ArcGIS Server and ArcGIS Engine), and
finally I talk about the new or updated extensions (Network Analyst,
Business Analyst, ArcGIS Schematics, Tracking Analyst, etc.).  

 

---ArcToolbox

 

The ArcToolbox as a unique program no longer exists; it is now simply a part
of ArcMap and ArcCatalog.  As many of you know, ArcToolbox was mainly used
for coverages, while the Geoprocessing Wizard was used for shapefiles and
geodatabases and was a holdover from the ArcView 3.x days.  

 

With the addition of geoprocessing functionality to the geodatabase (note:
geodatabases currently do not natively support geoprocessing; they are
converted to shapefiles on the fly), ArcToolbox will now support
cross-file-type geoprocessing functions allowing you, for example, to union
a Coverage and a Geodatabase Feature Class or a Shapefile and a Coverage.  

 

One of my questions regarded how topology would be preserved or specified
since each file type differs in how topology is enforced (if at all).  For
example, anyone who has unioned shapefiles with overlapping polygons (in the
same file) knows that the results are fairly confusing because you will
suddenly get multiple counts of overlapping polygons.  With coverages, this
is impossible because overlapping polygons are not allowed.  Therefore, I
asked, what will happen if you union a coverage with one of these
shapefiles?  I was told that there would be options for handling such
things.  What exactly that means, I can't say.

 

Modelbuilder has now been integrated into ArcToolbox.  Modelbuilder is a
program that allows the user to set up process-flow diagrams showing how
data will be processed and is currently only used in the Spatial Analyst
extension for ArcView 3.x.  Modelbuilder is now an integral part of
ArcToolbox and can use any combination of geoprocessing functions.  The
models are set up using process-flow diagrams (Squares and Ovals linked
together using flow lines) and allow the user to drag and drop datasets and
geoprocessing functions right onto the design area.  

 

For example, we could create a model that Unions Dataset A with Dataset B to
create Dataset X, which is then given a 2-mile buffer to create Dataset Y,
which is then clipped using Dataset C to create Dataset Z.  In this case we
have defined all of the variables even before the model is run; therefore,
if we run the model, the output will always be the same (if we haven't
modified the input files).  What you can easily do now is to define Dataset
A as a variable.  To do this, all you have to do is right click on the box
in Modelbuilder and select "set as variable."  The next time the model is
run, a pop-up window will allow you to choose which dataset you want to use
or will allow you to specify the buffer size or other some other variable.  

 

In ArcToolbox, a model looks just like any other geoprocessing tool.  To run
a model, you simply double click on it.  You can also use batch processing
with a model just like you can with a geoprocessing tool.  

 

Scripting is also something new in ArcToolbox.  In addition to Modelbuilder,
scripts can be written to perform a variety of tasks.  The language is
similar to AML and can be created in note pad or, if you prefer, scripting
programs like Python.  A model can be converted to a script allowing further
refinement, but a script cannot be converted to a model (although I assume
that a script can be called to run from within a model).  

 

 

---ArcMap:

 

ArcMap will look and behave much like ArcMap 8.x.  Several representatives
have said that all extensions and scripts written for 8.x will continue to
work at 9.x.  ESRI has also recently released a Production Line Tool Set
(PLTS) CD for ArcMap, which contains several tools to assist in managing
large datasets as well as the creation of map books.  The editing tools will
be further enhanced to bring more CAD-like editing to ArcMap.  Labeling will
be much improved at 9.x.  Many features only currently available using the
Maplex extension will now be standard.  

 

In future versions, ArcMap will support multi-view, multi-layout (multi-map)
projects (similar to ArcView 3.x).  Instead of a table of contents, you will
have a Map Dataset Manager which will maintain a hierarchical structure
showing maps, data frames, layers, templates, pages, etc. which is similar
to the project window in ArcView.  This was not talked about much, so it was
unclear which release version will contain this updated feature.  

 

Additionally, a command line will be added at ArcMap 9.0 allowing the user
to perform geoprocessing and other functions by typing right in the ArcMap
window.  Autocomplete popups will assist by showing available functions and
datasets.  

 

---ArcCatalog:

 

There are no major changes for ArcCatalog, other than the inclusion of
ArcToolbox.  

 

---ArcGIS Engine:

 

ArcGIS engine is basically the replacement of MapObjects with ArcObjects.
The engine itself is not an end user application but rather a toolkit for
developers.  The engine will come in two parts, the first being the
developer kit and the second being a redistributable install of the engine.
This two-part structure will allow a developer to write a custom application
using some of the core ArcGIS components and then distribute it without the
need of a license manager.  All installs of ArcGIS, ArcReader, and Custom
Apps will use this engine (the engine will be part of the automatic install
for ArcGIS).  

 

There will be three levels of functionality: Reader, View, and Editor.
Reader will allow the developer to use the components that are found in
ArcReader (read only data and map display); similarly, View will have the
components and features available in ArcView, and Editor will have the
components available in ArcEditor.  Extension components will also work with
ArcGIS engine.  The esriCore.olb object has been replaced with smaller
logical groups based on their functionality.  

 

---ArcGIS Server:

 

ArcGIS Server is basically the opening of the majority of the non-user
interface objects available in ArcGIS to both Windows and UNIX.  All of
these components can be wrapped (accessed by) Windows (VB, C#, C++, etc...)
or in UNIX (Java).  This will allow thin clients to instigate complex
functions at a remote server and have the results returned.  It also allows
GIS groups to leverage UNIX technology.  This will certainly become part of
the ArcWeb services in the future.  Not only will there be streamable data,
but users could potentially plug into a service that performs complex
functions (geocoding, geoprocessing, modeling, etc...).

 

 

--ArcGIS Extensions:

 

--Network Analyst:

 

Network Analyst is probably the most anticipated extension that has yet to
be released for ArcGIS.  It is expected to be released at 9.1, although
during the keynote Jack mentioned that it could be released between 9.0 and
9.1.  

 

All of the functionality of the NETWORK extension for ArcInfo Workstation
(Location-Allocation, Path, Tour, etc...) will be available.  However, the
implementation of each of these tools will of course be different than the
ArcInfo versions because it will be based on the geodatabase model.  

 

In the geodatabase, there will be a new network class as well as a
turn-table feature class.  Instead of having a turn-table table with the
impedance for an arc-node-arc connection, turns will be represented by an
entity in a feature class.  In ArcMap, the user will see turns as physical
arrows, which snap to the adjacent arcs.  

 

Multiple network classes can be linked together.  For example, you could
link road networks, a train network, a subway network, and network of
airline flights to create a global network.

 

 

--Business Analyst:

 

Business Analyst for ArcGIS 8.3 is expected to be released in the next few
months.  However ESRI has not emphasized that this version will be crippled
by the current unavailability of Network Analyst.  Therefore, users will not
be able to perform drive time analyses.  Business analyst will rely heavily
on the data provided by the newly created ESRI Business Information
Solutions (ESRI BIS) group.  

 

--ArcGIS Schematics:

 

ArcGIS Schematics allows you to represent network datasets in a schematic,
geoschematic, or geometric fashion.  For example, with utilities data, in
certain areas the data overlap making it difficult to differentiate what is
connected to what.  With ArcGIS Schematics, you can visualize the same area
using a schematic diagram that maintains all of the relationships and
connectivity of the network features.  Users can edit the data directly in
the schematic view.  For more information please see:

http://www.esri.com/library/brochures/pdfs/arcgis-schematics.pdf
<http://www.esri.com/library/brochures/pdfs/arcgis-schematics.pdf> 

 

--ArcGIS Tracking Analyst:

 

Tracking analyst has been improved over the 3.x version.  At 3.x users could
display time-based point data on a map using a playback manager.  This was
useful for showing species' movements or the location of a hurricane over a
period of time.  A Windows service could also be created that would allow
the user to feed live GPS signals into the system to show live data.  At the
8.x version, Tracking Analyst will allow the user to show all types of data
(point, line, and polygon).  This will allow you to show things like zoning
changes over time having the polygons change color as time progresses.  I
spoke to one of the representatives for Tracking Analyst and was told that
polygon themes are difficult to draw because of the potential refresh rate
that may be needed.  

 

--ArcSDE:

 

At 9.0, ArcSDE will now support replication of individual databases due to a
change in the architecture of ArcSDE itself.  ArcSDE 8.x requires a database
called SDE to be located in the database.  The SDE database stores all of
the permissions, table registrations, and storage parameters for any SDE
data.  Although additional databases can be created in the RDBMS, the SDE
database still holds all of the information about the data in these other
databases.  This makes replication nearly impossible because to copy a
database to another SDE system (perfectly legal in the DBMS) causes
problems because the new system's SDE database would not have been notified
of the new data.  In order to replicate, you are required to move all of the
data, and the receiving database cannot already have its own data because
there would be a mismatch of what data actually exist and what data the
system thinks are there. 

 

To resolve all of these problems, ArcSDE 9.0 does away with the SDE database
and integrates all of its functions directly into every database.
Therefore, instead of having a single SDE service per machine you will
create a unique SDE service for each database.  This will also assist in the
problem of the CROSS_DB_QUERY, which is currently used to prevent users of
one database from seeing feature classes in another, but does not prevent
the user from seeing the feature datasets, relationship classes, and
annotation classes stored in the other databases.  Because each database
will be independent of the others this will no longer happen.  In addition
to providing more discrete storage areas, this will also assist with
permissions and management.  

 

At version 9.1 we will see the introduction of Unique Ids (UIDs) to the
database.  UIDs are long integer identification numbers based on a
combination of several factors (such as time, computer number, and a random
number).  Each ID is unique from all others (theoretically it can be unique
from any other UID ever generated).  As we all know with shapefiles,
coverages and geodatabases, each feature (point, line, polygon) has an ID.
However, for each dataset the numbers are reused (ID-1, 2, 3, 4...).  Using
UIDs provides a completely unique number for each feature.  This will assist
in the maintenance of extremely large geodatabases that could be spread over
multiple servers.  

 

 

--Geodatabases (Imagery and TIN storage plus Database Cartography):

 

Geodatabases will have better management tools for imagery and will support
the storage of TINs.  Image catalogs, historic time series of imagery, and
improved pyramiding will assist in the storage and management of large
raster datasets in SDE.  TINs will also be supported in SDE including the
ability to create multiple levels of detail (similar to pyramiding in
rasters), which will assist in drawing speed.  

 

Personal geodatabases at 9.x will allow the storage of imagery, which is
currently not available.  

 

Also, in future releases of ArcGIS 9 expect to see the ability to store
representations of data in the geodatabase.  Similar to layer files, each
dataset could be given multiple representations, which will be stored along
with the dataset itself.  A user could then choose which view of the data
they would like to add based on their needs.  

 

 

--ArcPad and ArcPad Application Builder:

 

StreetMap for ArcPad has been released for ArcPad.  This will allow the user
to display street data, geocode addresses and perform routing directly in
ArcPad.  

 

 

--ArcGIS support for TabletPC and GPS:

 

ESRI recently released a free add-on for ArcMap that enables the user to
utilize the TabletPC functionality of Microsoft's new Windows XP Tablet PC
Edition.  This includes the digital ink, voice recognition and pen input
capabilities.  A digital ink toolbar allows a user to sketch directly on the
screen and save these sketches to a georeferenced file.  This could be used
to create field notes rather than modifying the data directly in the field.


 

A GPS tool for ArcGIS is also available.  This will allow the user to
capture GPS data directly in the field and integrate it with other data such
as road centerlines to provide additional functionality.  

 

Having used ArcPad application builder for several projects, I inquired as
to whether there would possibly be a similar form editor for ArcGIS that
would allow the user to easily create custom data input forms.
Unfortunately there is currently no plan for something like this, but I have
spoken to several ESRI staff about this because I feel that an easy-to-use
form editor for ArcGIS is needed especially now that many organizations are
looking at Tablet PCs with ArcMap as an alternative to ArcPad.  In the mean
time, I would recommend making some generic VBA/ArcObjects based forms that
can be reused for data input in the field.  

 

ArcIMS

 

In potential future versions of ArcIMS the ArcMap-ArcIMS Service will run on
UNIX.  Other improvements will include better security and stability.  

 

ArcPublisher

 

When someone uses ArcPublisher on a CD they typically store the files in a
folder on that CD.  Currently, the only way to prevent someone from being
able to use that data for their own use would be to use an ArcIMS image
service that streams the data over the Internet as an image.  In a future
release of ArcReader there will be the ability to lock down the data in a
protected geodatabase.  This will allow users to publish an ArcReader CD but
still keep their proprietary data secure.  

 

Confidentiality Notice: This e-mail is for the sole use of the recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited.
------_=_NextPart_001_01C37EC3.7C4C8D20
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR></HEAD>
<BODY>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">Greetings-<?xml:namespace prefix=20
=3D o ns =3D "urn:schemas-microsoft-com:office:office" =
/><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">Below is my review =
of the 2003=20
ESRI User Conference in San Diego. I have mainly focused on the =
technology=20
aspects (my background) of what I saw at the user conference.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>This however does not mean =
that all of=20
the information presented below will necessarily be released or =
implemented, as=20
the products are still being developed and tested.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Additionally, this =
information is for=20
general interest purposes only and should not be referenced in any =
official=20
capacity.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><o:p><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><SPAN=20
class=3D134083015-19092003>Thanks</SPAN></FONT></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><o:p><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><SPAN=20
class=3D134083015-19092003></SPAN></FONT></o:p>&nbsp;</P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><o:p><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><SPAN class=3D134083015-19092003>Chris=20
McGarry</SPAN></FONT></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><o:p><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><SPAN=20
class=3D134083015-19092003></SPAN></FONT></o:p>&nbsp;</P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><o:p><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><SPAN class=3D134083015-19092003><FONT =
face=3DArial=20
size=3D2>---------------------------------------------</FONT> <BR><FONT =
face=3DArial=20
size=3D2>Chris McGarry</FONT> <BR><FONT face=3DArial size=3D2>Sr. GIS=20
Specialist</FONT> <BR><FONT face=3DArial size=3D2>WilsonMiller =
Inc.</FONT> </P>
<P><FONT face=3DArial size=3D2>1311 Executive Center Dr. Suite =
100</FONT> <BR><FONT=20
face=3DArial size=3D2>Tallahassee FL 32301</FONT> <BR><FONT =
face=3DArial size=3D2>(850)=20
878-5001</FONT> <BR><FONT face=3DArial size=3D2><A =
href=3D"http://www.floridagis.com/"=20
target=3D_blank>http://www.floridagis.com</A></FONT> <BR><FONT =
face=3DArial=20
size=3D2>---------------------------------------------</FONT>=20
</P></SPAN></FONT></o:p>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><o:p><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></o:p>&nbsp;</P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">***Keynote:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">The theme of this =
year's=20
conference was "GIS - Serving Our World," which has two different but =
related=20
meanings for GIS professionals.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>One=20
meaning refers to the way GIS professionals are serving their =
community; the=20
other refers to the way GIS (and much of technology in general) is =
moving=20
towards integrating data on ever-increasing scales.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">For more on the =
Keynote please=20
see:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><A=20
href=3D"http://www.esri.com/events/uc/openingday.html#jacks_presentation=
">http://www.esri.com/events/uc/openingday.html#jacks_presentation</A><o=
:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">&nbsp;<o:p></o:p></P>=

<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">***Plenary=20
Session:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">Several Products and =
enhancements=20
were shown during the plenary session and are detailed =
below.<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">--ArcGIS =
9:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">According to David =
Maguire,=20
director of products, users of ArcGIS 9.x should notice improvements in =

reliability, scalability, and interoperability.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>The user interface is not =
much different=20
than ArcGIS 8.x, and existing tools and extensions for 8.x should work =
in=20
9.x.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>I will discuss each =
aspect of=20
ArcGIS in detail later.<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">--ArcGlobe:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">ArcGlobe was the =
best wiz-bang=20
demo of the whole conference and certainly is the best realization of =
an=20
all-encompassing global GIS data viewer thus far.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Imagine looking at the entire =
globe=20
(these data come with the software) and clicking a bookmark that says=20
"Tallahassee - Monroe St." and instantly the viewer starts to "fly" =
into the=20
Northwest Florida area, then into the Tallahassee Metro Area and then =
right into=20
Monroe St. right in front of the Capital Building with imagery so =
detailed that=20
you can see a taxi waiting to turn onto Apalachee Parkway.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Now imagine this whole scene =
flipping on=20
its side to reveal a 3-D view of downtown including photo-based =
renderings of=20
buildings, and CAD models of streetlights and cars (think =
ArcScene).<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">ArcGlobe only loads =
the necessary=20
data at the necessary resolution to show what is needed at that moment, =
thus=20
allowing the computer to actually draw the information in an animated =
fashion.=20
All of this is of course dependent on what information has been added, =
which=20
brings up the next part of the demo.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>Jack added a live ArcWeb data service, which I believe was =
provided by=20
the NOAA National Center for Atmospheric Research, of an animated =
raster image=20
showing the global vapor stream.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>The result was a rotating globe with an animated raster dataset =
of the=20
global air stream.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">So here, in my =
opinion, we begin=20
to see the beginning of Jack's ultimate GIS viewer.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Imagine being able to plug in =
a=20
multitude of ArcWeb services (ArcIMS and ArcGIS Server), which were =
created from=20
globally integrated geodatabases (ArcSDE) based on Geodatabase data =
models (CASE=20
Tools and ArcCatalog) created from data collected in the field (ArcPad =
and=20
Tablet PC), into this global data viewer and you can begin to fully =
appreciate,=20
or at least understand, the way ESRI is transforming their product line =
to=20
attain the ultimate goal of global GIS.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">According to one of =
the product=20
reps I spoke with, ArcGlobe should be able to run on most =
desktops.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>However, a 3D acceleration =
card is=20
recommended as well as ample RAM (I would recommend about 15 =
terabytes).<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">For additional =
information=20
see:<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN><A=20
href=3D"http://www.esri.com/news/arcnews/summer03articles/introducing-ar=
cglobe.html">http://www.esri.com/news/arcnews/summer03articles/introduci=
ng-arcglobe.html</A><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">--ArcPublisher:<SPAN =

style=3D"mso-spacerun: yes">&nbsp; </SPAN>See below<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">--ArcToolbox and =
Modeling:<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>See below<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">--Network =
Analyst:<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>See below<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">***Keynote and =
Notable=20
Awards<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">Peter Hillary, son =
of Sir Edmund=20
Hillary, who with Tenzing Norgay was the first to climb Mt. Everest 50 =
years=20
ago, gave the audience a multimedia presentation that included a 3-D =
fly-by of=20
Mt. Everest itself using ArcScene.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>Since I could not even begin to give justice to this =
presentation please=20
see: <A=20
href=3D"http://www.esri.com/events/uc/openingday.html">http://www.esri.c=
om/events/uc/openingday.html</A>=20
or <A=20
href=3D"http://www.nationalgeographic.com/everest/">http://www.nationalg=
eographic.com/everest/</A>=20
for more information.<SPAN style=3D"mso-spacerun: yes">&nbsp;=20
</SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">--GeoData.gov:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">The ESRI =
Presidential Award was=20
given to the U.S. Department of the Interior for the newly created =
GeoData.gov=20
GIS data portal.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>This is =
part of=20
the National Geospatial One-Stop initiative.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Please see <A=20
href=3D"http://www.geodata.gov/">http://www.geodata.gov/</A> for more=20
information.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">***Technical=20
Sessions:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">I will describe each =
product=20
individually giving as much information as possible.<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">--ArcGIS =
9.x<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">ArcGIS 9.0 will be =
the next=20
release of ESRI's flagship software package.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>I begin by talking about the =
core=20
program itself (ArcMap and ArcCatalog), then I discuss the underlying =
components=20
(ArcGIS Server and ArcGIS Engine), and finally I talk about the new or =
updated=20
extensions (Network Analyst, Business Analyst, ArcGIS Schematics, =
Tracking=20
Analyst, etc.).<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">---ArcToolbox<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">The ArcToolbox as a =
unique=20
program no longer exists; it is now simply a part of ArcMap and =
ArcCatalog.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>As many of you know, =
ArcToolbox was=20
mainly used for coverages, while the Geoprocessing Wizard was used for=20
shapefiles and geodatabases and was a holdover from the ArcView 3.x =
days.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">With the addition of =

geoprocessing functionality to the geodatabase (note: geodatabases =
currently do=20
not natively support geoprocessing; they are converted to shapefiles on =
the=20
fly), ArcToolbox will now support cross-file-type geoprocessing =
functions=20
allowing you, for example, to union a Coverage and a Geodatabase =
Feature Class=20
or a Shapefile and a Coverage.<SPAN style=3D"mso-spacerun: yes">&nbsp;=20
</SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">One of my questions =
regarded how=20
topology would be preserved or specified since each file type differs =
in how=20
topology is enforced (if at all).<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>For example, anyone who has unioned shapefiles with overlapping =
polygons=20
(in the same file) knows that the results are fairly confusing because =
you will=20
suddenly get multiple counts of overlapping polygons.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>With coverages, this is =
impossible=20
because overlapping polygons are not allowed.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Therefore, I asked, what will =
happen if=20
you union a coverage with one of these shapefiles?<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>I was told that there would =
be options=20
for handling such things.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>What=20
exactly that means, I can't say.<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">Modelbuilder has now =
been=20
integrated into ArcToolbox.<SPAN style=3D"mso-spacerun: yes">&nbsp;=20
</SPAN>Modelbuilder is a program that allows the user to set up =
process-flow=20
diagrams showing how data will be processed and is currently only used =
in the=20
Spatial Analyst extension for ArcView 3.x.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>Modelbuilder is now an integral part of ArcToolbox and can use =
any=20
combination of geoprocessing functions.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>The models are set up using process-flow diagrams (Squares and =
Ovals=20
linked together using flow lines) and allow the user to drag and drop =
datasets=20
and geoprocessing functions right onto the design area.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">For example, we =
could create a=20
model that Unions Dataset A with Dataset B to create Dataset X, which =
is then=20
given a 2-mile buffer to create Dataset Y, which is then clipped using =
Dataset C=20
to create Dataset Z.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>In =
this case=20
we have defined all of the variables even before the model is run; =
therefore, if=20
we run the model, the output will always be the same (if we haven't =
modified the=20
input files).<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>What you =
can easily=20
do now is to define Dataset A as a variable.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>To do this, all you have to =
do is right=20
click on the box in Modelbuilder and select "set as variable."<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>The next time the model is =
run, a pop-up=20
window will allow you to choose which dataset you want to use or will =
allow you=20
to specify the buffer size or other some other variable.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">In ArcToolbox, a =
model looks just=20
like any other geoprocessing tool.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>To run a model, you simply double click on it.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>You can also use batch =
processing with a=20
model just like you can with a geoprocessing tool.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">Scripting is also =
something new=20
in ArcToolbox.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>In =
addition to=20
Modelbuilder, scripts can be written to perform a variety of =
tasks.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>The language is similar to =
AML and can=20
be created in note pad or, if you prefer, scripting programs like =
Python.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>A model can be converted to a =
script=20
allowing further refinement, but a script cannot be converted to a =
model=20
(although I assume that a script can be called to run from within a =
model).<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">---ArcMap:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">ArcMap will look and =
behave much=20
like ArcMap 8.x.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Several =

representatives have said that all extensions and scripts written for =
8.x will=20
continue to work at 9.x.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>ESRI has=20
also recently released a Production Line Tool Set (PLTS) CD for ArcMap, =
which=20
contains several tools to assist in managing large datasets as well as =
the=20
creation of map books.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>The editing=20
tools will be further enhanced to bring more CAD-like editing to =
ArcMap.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Labeling will be much =
improved at=20
9.x.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Many features only =
currently=20
available using the Maplex extension will now be standard.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">In future versions, =
ArcMap will=20
support multi-view, multi-layout (multi-map) projects (similar to =
ArcView=20
3.x).<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Instead of a table =
of=20
contents, you will have a Map Dataset Manager which will maintain a =
hierarchical=20
structure showing maps, data frames, layers, templates, pages, etc. =
which is=20
similar to the project window in ArcView.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>This was not talked about much, so it was unclear which release =
version=20
will contain this updated feature. <SPAN=20
style=3D"mso-spacerun: yes">&nbsp;</SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">Additionally, a =
command line will=20
be added at ArcMap 9.0 allowing the user to perform geoprocessing and =
other=20
functions by typing right in the ArcMap window.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Autocomplete popups will =
assist by=20
showing available functions and datasets.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">---ArcCatalog:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">There are no major =
changes for=20
ArcCatalog, other than the inclusion of ArcToolbox.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">---ArcGIS =
Engine:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">ArcGIS engine is =
basically the=20
replacement of MapObjects with ArcObjects.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>The engine itself is not an end user application but rather a =
toolkit for=20
developers.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>The engine =
will come in=20
two parts, the first being the developer kit and the second being a=20
redistributable install of the engine.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>This two-part structure will allow a developer to write a custom =

application using some of the core ArcGIS components and then =
distribute it=20
without the need of a license manager.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>All installs of ArcGIS, ArcReader, and Custom Apps will use this =
engine=20
(the engine will be part of the automatic install for ArcGIS).<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">There will be three =
levels of=20
functionality: Reader, View, and Editor.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>Reader will allow the developer to use the components that are =
found in=20
ArcReader (read only data and map display); similarly, View will have =
the=20
components and features available in ArcView, and Editor will have the=20
components available in ArcEditor.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>Extension components will also work with ArcGIS engine.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>The esriCore.olb object has =
been=20
replaced with smaller logical groups based on their functionality.<SPAN =

style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">---ArcGIS =
Server:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">ArcGIS Server is =
basically the=20
opening of the majority of the non-user interface objects available in =
ArcGIS to=20
both Windows and UNIX.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>All of these=20
components can be wrapped (accessed by) Windows (VB, C#, C++, etc...) =
or in UNIX=20
(Java).<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>This will allow =
thin=20
clients to instigate complex functions at a remote server and have the =
results=20
returned.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>It also allows =
GIS groups=20
to leverage UNIX technology.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>This=20
will certainly become part of the ArcWeb services in the future.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Not only will there be =
streamable data,=20
but users could potentially plug into a service that performs complex =
functions=20
(geocoding, geoprocessing, modeling, etc...).<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">--ArcGIS=20
Extensions:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">--Network =
Analyst:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">Network Analyst is =
probably the=20
most anticipated extension that has yet to be released for ArcGIS.<SPAN =

style=3D"mso-spacerun: yes">&nbsp; </SPAN>It is expected to be released =
at 9.1,=20
although during the keynote Jack mentioned that it could be released =
between 9.0=20
and 9.1.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">All of the =
functionality of the=20
NETWORK extension for ArcInfo Workstation (Location-Allocation, Path, =
Tour,=20
etc...) will be available.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>However,=20
the implementation of each of these tools will of course be different =
than the=20
ArcInfo versions because it will be based on the geodatabase =
model.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">In the geodatabase, =
there will be=20
a new network class as well as a turn-table feature class.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Instead of having a =
turn-table table=20
with the impedance for an arc-node-arc connection, turns will be =
represented by=20
an entity in a feature class.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>In=20
ArcMap, the user will see turns as physical arrows, which snap to the =
adjacent=20
arcs.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">Multiple network =
classes can be=20
linked together.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>For =
example, you=20
could link road networks, a train network, a subway network, and =
network of=20
airline flights to create a global network.<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">--Business=20
Analyst:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">Business Analyst for =
ArcGIS 8.3=20
is expected to be released in the next few months.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>However ESRI has not =
emphasized that=20
this version will be crippled by the current unavailability of Network=20
Analyst.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Therefore, =
users will not=20
be able to perform drive time analyses.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>Business analyst will rely heavily on the data provided by the =
newly=20
created ESRI Business Information Solutions (ESRI BIS) group.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">--ArcGIS=20
Schematics:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">ArcGIS Schematics =
allows you to=20
represent network datasets in a schematic, geoschematic, or geometric=20
fashion.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>For example, =
with=20
utilities data, in certain areas the data overlap making it difficult =
to=20
differentiate what is connected to what.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>With ArcGIS Schematics, you can visualize the same area using a =
schematic=20
diagram that maintains all of the relationships and connectivity of the =
network=20
features.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Users can edit =
the data=20
directly in the schematic view.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>For=20
more information please see:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><A=20
href=3D"http://www.esri.com/library/brochures/pdfs/arcgis-schematics.pdf=
">http://www.esri.com/library/brochures/pdfs/arcgis-schematics.pdf</A><o=
:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">--ArcGIS Tracking=20
Analyst:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">Tracking analyst has =
been=20
improved over the 3.x version.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>At=20
3.x users could display time-based point data on a map using a playback =

manager.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>This was useful =
for=20
showing species' movements or the location of a hurricane over a period =
of=20
time.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>A Windows service =
could also=20
be created that would allow the user to feed live GPS signals into the =
system to=20
show live data.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>At the =
8.x version,=20
Tracking Analyst will allow the user to show all types of data (point, =
line, and=20
polygon).<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>This will =
allow you to=20
show things like zoning changes over time having the polygons change =
color as=20
time progresses.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>I spoke =
to one of=20
the representatives for Tracking Analyst and was told that polygon =
themes are=20
difficult to draw because of the potential refresh rate that may be =
needed.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">--ArcSDE:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">At 9.0, ArcSDE will =
now support=20
replication of individual databases due to a change in the architecture =
of=20
ArcSDE itself.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>ArcSDE =
8.x requires=20
a database called SDE to be located in the database.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>The SDE database stores all =
of the=20
permissions, table registrations, and storage parameters for any SDE =
data.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Although additional databases =
can be=20
created in the RDBMS, the SDE database still holds all of the =
information about=20
the data in these other databases.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>This makes replication nearly impossible because to copy a =
database to=20
another SDE system (perfectly legal in the DBMS) causes<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>problems because the new =
system's SDE=20
database would not have been notified of the new data.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>In order to replicate, you =
are required=20
to move all of the data, and the receiving database cannot already have =
its own=20
data because there would be a mismatch of what data actually exist and =
what data=20
the system thinks are there. <o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">To resolve all of =
these problems,=20
ArcSDE 9.0 does away with the SDE database and integrates all of its =
functions=20
directly into every database.<SPAN style=3D"mso-spacerun: yes">&nbsp;=20
</SPAN>Therefore, instead of having a single SDE service per machine =
you will=20
create a unique SDE service for each database.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>This will also assist in the =
problem of=20
the CROSS_DB_QUERY, which is currently used to prevent users of one =
database=20
from seeing feature classes in another, but does not prevent the user =
from=20
seeing the feature datasets, relationship classes, and annotation =
classes stored=20
in the other databases.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>Because=20
each database will be independent of the others this will no longer =
happen.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>In addition to providing more =
discrete=20
storage areas, this will also assist with permissions and =
management.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">At version 9.1 we =
will see the=20
introduction of Unique Ids (UIDs) to the database.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>UIDs are long integer =
identification=20
numbers based on a combination of several factors (such as time, =
computer=20
number, and a random number).<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>Each=20
ID is unique from all others (theoretically it can be unique from any =
other UID=20
ever generated).<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>As we =
all know=20
with shapefiles, coverages and geodatabases, each feature (point, line, =
polygon)=20
has an ID.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>However, for =
each=20
dataset the numbers are reused (ID-1, 2, 3, 4...).<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Using UIDs provides a =
completely unique=20
number for each feature.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>This will=20
assist in the maintenance of extremely large geodatabases that could be =
spread=20
over multiple servers.<SPAN style=3D"mso-spacerun: yes">&nbsp;=20
</SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">--Geodatabases =
(Imagery and TIN=20
storage plus Database Cartography):<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">Geodatabases will =
have better=20
management tools for imagery and will support the storage of TINs.<SPAN =

style=3D"mso-spacerun: yes">&nbsp; </SPAN>Image catalogs, historic time =
series of=20
imagery, and improved pyramiding will assist in the storage and =
management of=20
large raster datasets in SDE.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>TINs=20
will also be supported in SDE including the ability to create multiple =
levels of=20
detail (similar to pyramiding in rasters), which will assist in drawing =

speed.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">Personal =
geodatabases at 9.x will=20
allow the storage of imagery, which is currently not available.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">Also, in future =
releases of=20
ArcGIS 9 expect to see the ability to store representations of data in =
the=20
geodatabase.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Similar to =
layer=20
files, each dataset could be given multiple representations, which will =
be=20
stored along with the dataset itself.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>A user could then choose which view of the data they would like =
to add=20
based on their needs.<SPAN style=3D"mso-spacerun: yes">&nbsp;=20
</SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">--ArcPad and ArcPad =
Application=20
Builder:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">StreetMap for ArcPad =
has been=20
released for ArcPad.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>This will=20
allow the user to display street data, geocode addresses and perform =
routing=20
directly in ArcPad.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">--ArcGIS support for =
TabletPC and=20
GPS:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">ESRI recently =
released a free=20
add-on for ArcMap that enables the user to utilize the TabletPC =
functionality of=20
Microsoft's new Windows XP Tablet PC Edition.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>This includes the digital =
ink, voice=20
recognition and pen input capabilities.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>A digital ink toolbar allows a user to sketch directly on the =
screen and=20
save these sketches to a georeferenced file.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>This could be used to create =
field notes=20
rather than modifying the data directly in the field.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">A GPS tool for =
ArcGIS is also=20
available.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>This will =
allow the user=20
to capture GPS data directly in the field and integrate it with other =
data such=20
as road centerlines to provide additional functionality.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">Having used ArcPad =
application=20
builder for several projects, I inquired as to whether there would =
possibly be a=20
similar form editor for ArcGIS that would allow the user to easily =
create custom=20
data input forms.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>Unfortunately=20
there is currently no plan for something like this, but I have spoken =
to several=20
ESRI staff about this because I feel that an easy-to-use form editor =
for ArcGIS=20
is needed especially now that many organizations are looking at Tablet =
PCs with=20
ArcMap as an alternative to ArcPad.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>In the mean time, I would recommend making some generic =
VBA/ArcObjects=20
based forms that can be reused for data input in the field.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">ArcIMS<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">In potential future =
versions of=20
ArcIMS the ArcMap-ArcIMS Service will run on UNIX.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Other improvements will =
include better=20
security and stability.<SPAN style=3D"mso-spacerun: yes">&nbsp;=20
</SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">ArcPublisher<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in =
0pt">&nbsp;<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt">When someone uses =
ArcPublisher on=20
a CD they typically store the files in a folder on that CD.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Currently, the only way to =
prevent=20
someone from being able to use that data for their own use would be to =
use an=20
ArcIMS image service that streams the data over the Internet as an =
image.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>In a future release of =
ArcReader there=20
will be the ability to lock down the data in a protected =
geodatabase.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>This will allow users to =
publish an=20
ArcReader CD but still keep their proprietary data secure.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></P>
<DIV><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C37EC3.7C4C8D20--