I went, I heard, I pondered, and now
I speak. Here is what I understand of the developments in the ESRI software line,
and what they mean to us. Point number one: there are changes afoot, big changes. Point
number two: it’s probably good news. Point number three: ESRI is finally falling in
line with the rest of the software industry.
Here it is in a nutshell: ESRI is essentially
rebuilding all of its core software (ArcInfo, ArcView, and MapObjects) around brand new
technology called ArcObjects. That buzzword, Objects, should sound familiar. MapObjects
was our introduction to GIS-for-programmers, as opposed to ArcInfo and ArcView,
GIS-for-end-users. ArcObjects replaces MapObjects technology, and is used by ESRI to build
the new components of ArcInfo 8.
When you buy or upgrade to ArcInfo 8, you will get
all of the ArcObjects, as well as the three end-user applications that ESRI has written
with ArcObjects: ArcMap, ArcCatalog, and ArcToolbox. So you will be able to use these
three applications out of the box, customize them with your choice of standard languages,
or build an entirely new GIS package with ArcObjects. Your choice.
You will recognize ArcMap – it looks very
similar to ArcView, only guess what? You can map in it and you can edit in it
– in the same environment! And not only edit coverages, but shapefiles and SDE
data directly as well. ArcCatalog, looking much like the Windows Explorer, is (finally)
ESRI’s data cataloging and metadata tool, fully integrated with ArcMap. ArcCatalog
also allows you to create GeoDatabases, which are a way to treat geographic data not
merely as points, lines, and polygons which you know are telephone wires, manhole
covers, or spotted owl nests, but that the software also knows are wires, covers,
and nests. And then the software can be taught never to connect a telephone wire to a
power line, never to place a manhole cover in the middle of a house, and to place two
nests at least a certain distance away from each other. ArcToolbox is a wizard- and
form-driven geoprocessing engine to be used for GIS analysis.
What about ArcView 4? My understanding is that it
will be a "lighter" version of ArcMap. And that MapObjects 3 will be a
"lighter" version of ArcObjects. So everything will be built on the same
software, which means that a user of ArcView will now be able to switch over to
ArcInfo’s ArcMap and immediately know what to do. And it means that an ArcInfo
programmer will be able to program MapObjects and ArcView without having to relearn it.
Now doesn’t that sound like a relief? Oh, by the way, that kid you just hired
straight out of college who knows Visual Basic, C++, Delphi, or PowerBuilder, will be able
to start programming for you without having first to learn AML or Avenue. And an ArcInfo
programmer who gets laid off will be able to find a programming job anywhere.
And did I mention that ArcInfo 8 comes with a free
version of Personal SDE? This is SDE implemented inside MS Access, through what is called
the JET 4 Engine. You will need to install it if you want to make use of the new
GeoDatabase tools. The cool thing is, you’ll be able to start migrating applications,
or write them in the first place, to be SDE compliant. Then, if and when you migrate to
"real" SDE, it will be a snap.
So that’s basically what there is. Now,
what does it mean?
Q: Will I have to learn all new ArcInfo when I
install version 8?
A: Only if you want to. Inside version 8 is also
the familiar ArcInfo 7.2.1 (black screen, Arc: prompt, command line interface,
ArcTools – gotta love it!). Don’t want the new tools? Don’t use them.
Q: Does AML go away?
A: It does in ArcObjects (which are COM objects
that can be used with Visual Basic, C++, etc.). But if you continue to use ArcInfo 7.2.1
(or whatever ESRI wants to call it), or ODE, AML remains.
Q: Will I need anything special to use
ArcInfo 8?
A: If you want to program the ArcObjects, you might
wish to spring for a copy of Visual Basic, but ArcInfo 8 will come with Visual Basic for
Applications, or VBA, bundled. This is the freebie version of VB that so many vendors are
now including with their software as their macro language.
I believe you will need to upgrade to Service Pack 4 of Windows NT, if you haven’t
already done so.
And if you want to use the new GeoDatabase tools, you will have to install the free
Personal SDE that comes with ArcInfo 8.
Q: When will ArcView 4 come out?
A: Later. 2000.
Q: Will Avenue go away?
A: In ArcView 4, yes. But, ESRI says they
will continue to support and develop the ArcView 3 architecture for "years to
come." So we might see a version 3.3 and a version 4 out at the same time. Version 4
will be built from ArcObjects, and therefore support VB, etc. Version 3.x will support
Avenue.
Q: Will the objects in MapObjects 1 and 2 be
the same as in MapObjects 3?
A: No. They will be the new ArcObjects, which are
different. But, ESRI says that they will continue to support and develop the
MapObjects 2 architecture for "years to come." In other words, the same story as
with ArcView 3 and ARCINFO 7.
Q: Should I learn VB, Delphi, or something
like it?
A: There’s an understatement!
Q: Should I still be developing applications
in AML, Avenue, or MO 1 or 2?
A: That’s the Million Dollar Question! I would
say yes, if it builds on an existing application or you can realize a quick return on the
investment in case it’s new. Otherwise, in most cases probably… not.
Q: Is all of this going to change again
next year?
A: I don’t think so. Since ESRI is now falling
in line with the rest of the software industry, changes should follow the rest of the
industry, not lag 3-5 years behind. So unless the rest of the industry hits a brick wall
suddenly, things should settle down to a somewhat predictable groove. This is not
to say that changes and innovation will slow down, but you’d be able to predict it
better just by reading PC World or Information Week.
