More Information About ArcView GIS 3.2a

Note: If you have a Language Supplement installed, the ArcView GIS 3.2a will prompt for the language installed to install the appropriate files and maintain your language supplement.

This document contains important, late-breaking information on the following topics:

Contents

1.0 What’s new in ArcView gis 3.2a

2.0 Description of ArcView GIS 3.2

3.0 ArcView GIS Documentation

4.0 New ArcView GIS Sample

5.0 Installed System Files

6.0 ArcView GIS 3.2 Font Changes

7. Known Issues

8. Projection Utility FAQs

1. What’s new in ArcView GIS 3.2a

Installation

The ArcView GIS 3.2 setup did not allow installation to a full path with more than 10 characters. This limitation has been eliminated for 3.2a.

The ArcView GIS 3.2a setup will update 3D Analyst 1.0 to 1.0a and Network Analyst 1.0, 1.0a or 1.0b to Network Analyst 1.0b if they reside in the destination directory for the 3.2a installation.

CADReader

The CADReader has been updated to be compatible with AutoCAD 2000 (Release 15) DWG files.

Class Lists

To assist those developing and customizing ArcView GIS, a list of reserved class names has been compiled. These words should not be used as variables in Avenue scripts as ArcView reserves them as classes. The list can be found in the \AVDOCS installation directory (typically, C:\ESRI\AV_GIS30\AVDOCS). The file is installed in both Microsoft Excel and HTML formats (ClassList.xls and ClassList.htm).

Database Access 2.1a

Database Access 2.1a is included with ArcView GIS 3.2a. Database Access 2.1a provides support for ArcSDE 8. For more information about Database Access, see the Database Access Readme file available from the ArcView program group after installation.

ERDAS IMAGINE Data Reader

The IMAGINE Image Support extension has been enhanced at ArcView 3.2a to recognize and use, but not create, ERDAS's pyramid layer information on IMAGINE IMG images. Previously, the

only extension that took advantage of these time saving reduced resolution data sets that often accompany large IMAGINE IMG imagery was Image Analysis.

Internal or external pyramid layers, if present, are used to display large images in a quicker time frame. Many users will find that their IMAGINE IMG display increases dramatically when pyramid layers are built. If pyramids are not yet built for your large IMG file(s) and you would like to build them, several products from both ESRI and ERDAS are able to do this (i.e.: ArcView Image Analysis, ERDAS IMAGINE 8.4, and ArcInfo/ArcView 8.x).

NITF Data Reader

The NITF data reader has been updated to provide support for more current versions of NITF data. Several abilities have been added to this military data reader extension.

• ArcView can now read all of the NITF image tiles stored in the *.ntf file. In previous versions, only the top left single tile was read and displayed in the view.

• NITF now reads and displays (by default) annotation layers, if present, in the *.ntf file. A sample script, named "nitfanno.ave", can be used to control the display of the annotation. This script can be found in the \samples\scripts folder. To use the script, simply create a view button and attach this script to it. For help on adding a button and other ArcView customizations, please refer to ArcView's on-line help system.

-Support for rotation with the NITF image is now present. Previously, ArcView could not display an NITF image that contained rotation.

Projection Utility

The ArcView Projection Utility has been improved for ArcView GIS 3.2a. While no new projections have been added, many reported issues have been addressed, and some enhancements have been implemented.

-Specify output units on the command line

Being able to change the units of an output shapefile has always been available from the utility's interface. This feature has been extended to the command line. The new option is -OU for Output Units.

Usage example (entered on a single line in a DOS window):

C:\DATA> c:\esri\av_gis30\arcview\bin32\projutil.exe -if states.shp -id . -of output.shp -od . -ic 4267 -oc 26777 -ou 9001 -q

In this example, the ArcView sample shapefile, states.shp, is used. Its input geographic coordinate system is NAD27 (using its default values), and the output projected coordinate system is NAD27 Kansas North, using all the default values except changing the output units from US Survey Feet to meters.

-Spatial indexes

Spatial index files (sbx, sbn) are now created for output shapefiles.

-UNC Support

Universal Naming Convention (UNC) is now supported from the Browse dialog for input and output file names. This allows you to use Network Neighborhood to access any shapefile on your network. An example of UNC is \\networkpc\data\myshape.shp

-Hotine Oblique Mercator interface has been fixed

Users in Michigan use the Hotine Oblique Mercator coordinate system, which has a parameter for Longitude of Origin. However, the interface was using the Latitude of Origin instead. This has been corrected.

-GeoTransformations not working correctly in some cases

The utility was not properly transforming data from WGS84 to another coordinate systems. This has been fixed. Three examples of transformations that have been fixed are WGS_1984_1_To_OSGB_1936, WGS_1984_To_NTF, and WGS_1984_To_Pulkovo_1942.

-Copying associated files

Shapefiles may have other files associated with them, besides the files necessary to draw the shapes. Examples are avl (ArcView legend files), xml, and trx (Tracking Analyst legend files). The utility used to ignore these files - it was up to you to copy them to the new output shapefile.

Now these associated files will be copied to the output shapefiles by default. To include additional file types, simply add the extension of the files you want copied to the AVHOME%\bin32\projutil.txt file. Edit the projutil.txt file to add other file extensions, or to remove any of the default file extensions if you don’t want those files copied.

NOTE: Do not add the spatial index file extensions (sbx and sbn) to this file. New spatial indexes are automatically generated for the new shapefiles. You don’t want to copy over the old spatial indexes anyway – they are not relevant for the new shapefiles. The files with extensions you specified are copied after the shapefile is projected. If you add them to projutil.txt, the old spatial index files will be copied, thus overwriting the valid spatial index files and making your shapefile invalid.