files / 421_гис-2 / arcview 3.2a / readme

ArcView GIS 3.2a readme More Information About ArcView GIS 3.2a Note:     If you have a Language Supplement installed, the ArcView GIS 3.2a  setup 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.0     Known Issues

8.0     Projection Utility FAQs  Back to TOC 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.  Back to TOC 2.0 Description of ArcView GIS 3.2

There were several new functionalities released with ArcView GIS 3.2.  This information is provided in the ArcView GIS Help system as well as in the "What's New in ArcView GIS Version 3.2" book. The Help system does not include information about features and functionality introduced with ArcView GIS 3.2a. 3.0 ArcView GIS Documentation

The ArcView GIS 3.2 CD-ROM contains the following documentation that can be found in the AVDOCS folder.     -ArcView GIS 3.2 Installation Guide (av32inst.pdf)

    -What's New in ArcView GIS 3.2 (newin32.pdf)

    -Shapefile White Paper (shapefile.pdf)

    -Using ArcView Database Access (dbaccess.pdf)

    -A Crystal folder which includes Seagate Crystal Reports 7 User's Guide (usergde.pdf) and Technical Reference Guides (vol1.pdf, vol2.pdf, vol3.pdf and vol4.pdf)  All documentation is available in Portable Document Format (PDF) and requires Acrobat Reader for viewing. An installation of Adobe Acrobat Reader 4.0 is available on the ArcView GIS 3.2 CD-ROM in the Acrobat folder. You can also obtain the Acrobat Reader from Adobe's home  page at www.adobe.com.  Back to TOC  4.0 ArcView GIS Sample

 A new sample DLL, ScriptLog.dll, aids in Avenue application development and debugging. This DLL adds a new avenue class, ScriptLog, which provides the functionality to create a log file containing the name and run time of scripts. The ScriptLog output contains the script name, the cumulative run time (in seconds), and run time of the script (in seconds). Note that the cumulative run time includes wait time and non-script invoked runtime.  Class Requests for ScriptLog  ScriptLog.StartLog(aFileName)

  - Opens a new ScriptLog. The name of each script that is run is written to the log file.  ScriptLog.EndLog

 - Ends script logging.  The following five steps describe how to use ScriptLog.  1) Load the ScriptLog.dll in ArcView GIS using the following Avenue code.  _ScriptLogDll = System.LoadLibrary("$AVBIN\scriptlog.dll".AsFileName)

 if (_ScriptLogDll <> nil) then

 MsgBox.Error("Unable to load ScriptLog.dll", "")

 return nil

 end  2) Open a new log file using the StartLog class request.  logFileName = FileName.Make("c:\temp\scriptlog.txt")

 ScriptLog.StartLog(logFileName)  3) Run or debug your Avenue application as normal.  4) Close the log file by using the EndLog request.  ScriptLog.EndLog  5) Examine the log file contents.  An example log file is below. This log file was generated by calling StartLog, choosing File/Save As from the Project GUI, and then calling EndLog.  Note that the script name is followed by the log's duration and the script's run-time duration.  Project.CustomizeUpdate: 0 (0)

 Project.RenameUpdate: 0 (0)

 Project.DeleteUpdate: 0 (0)

 Project.AddTableUpdate: 0 (0)

 Project.ImportUpdate: 0 (0)

 Project.HasSQL: 0 (0)

 WindowMenuUpdate: 0 (0)

 Doc.NewUpdate: 0 (0)

 Doc.OpenUpdate: 0 (0)

 Doc.ActionUpdate: 0 (0)

 Project.UpdateButtons: 0 (0)

 Project.CheckForEdits: 2 (0)

 Project.SaveAs: 9 (7)

 Project.CustomizeUpdate: 9 (0)

 Project.RenameUpdate: 9 (0)

 Project.DeleteUpdate: 9 (0)

 Project.AddTableUpdate: 9 (0)

 Project.ImportUpdate: 9 (0)

 Project.HasSQL: 9 (0)

 WindowMenuUpdate: 9 (0)

 Doc.NewUpdate: 9 (0)

 Doc.OpenUpdate: 9 (0)

 Doc.ActionUpdate: 9 (0)

 Project.UpdateButtons: 9 (0)

   Additional Notes:

 -During debugging, it is best to call StartLog and EndLog from buttons added to the ArcView GUI. See the ArcView GIS Help system for additional information on adding buttons to the ArcView GUI. A third button can also be added to the ArcView GUI to display the contents of the log file a text editor such as notepad.exe.  -The ScriptLog class can only have one log file open at a time. Calling StartLog with a log file already open will close the existing log file and open a new one.  -Do not try to unload the ScriptLog.dll.  This library cannot be unloaded. If you need to unload ScriptLog.dll you must exit and restart ArcView GIS. -If any unexplained behavior is experienced when using ScriptLog.dll, exit and restart ArcView GIS without ScriptLog.dll loaded.  Back to TOC 5.0 Installed System Files

Setup will install the following files into your Windows 95/98 SYSTEM or

Windows NT/2000 SYSTEM32 directories: comctl32.ocx   isunist.exe   msvcrt10.dll

comdlg32.ocx   mfc42.dll   oleaut32.dll

ctl3d32.dll   mscomctl.ocx   tabctl32.ocx

dforrt.dll   msvbvm60.dll   comcat.dll

mfc40.dll   msvcirt.dll

msvcrt20.dll   msvcp60.dll

msvcrt40.dll    msvcrt.dll (AV Reports)

asycfilt.dll   vb5stkit.dll   p2bbnd.dll

ccsdk32.dll   msjint35.dll   p2bdao.dll

comcat.dll   msjter35.dll   p2ctdao.dll

comct232.ocx   msrd2x35.dll   p2irdao.dll

comdlg32.ocx   msrepl35.dll   p2sevt.dll

crpaig32.dll   mstext35.dll   p2smon.dll

crpe32.dll   msvbvm50.dll   p2sodbc.dll

crwrap32.dll   msvcp50.dll   regsvr32.exe

crystl32.ocx   msxbse35.dll   st5unst.exe

expsrv.dll   odbcji32.dll   tabctl32.ocx

implode.dll   odbcjt32.dll   tdbg5.ocx

mscomct2.ocx   odbctl32.dll   threed32.ocx

msrdo20.dll   olepro32.dll   vb5db.dll

msjet35.dll   vbajet32.dll Setup will create a directory named 'Crystal' under your Windows directory, and install the following files: crxlat32.dll   p2solap.dll   u2fdif.dll

p2bact.dll   p2soledb.dll   u2fhtml.dll

p2bact3.dll   p2sora7.dll   u2fodbc.dll

p2bbde.dll   p2soutlk.dll   u2frdef.dll

p2bbtrv.dll   p2srepl.dll   u2frec.dll

p2bxbse.dll   p2ssql.dll   u2frtf.dll

p2ctbtrv.dll   p2ssyb10.dll   u2fsepv.dll

p2iract.dll   p2strack.dll   u2ftext.dll

p2ixbse.dll   p2swblg.dll   u2fwks.dll

p2lodbc.dll   u25200.dll   u2fwordw.dll

p2molap.dll   u25dts.dll   u2fxls.dll

p2sacl.dll   u25store.dll   u2l2000.dll

p2sdb2.dll   u2dapp.dll   u2lbar.dll

p2sfs.dll   u2ddisk.dll   u2lcom.dll

p2sifmx.dll   u2dmapi.dll   u2ldts.dll

p2sexsr.dll   u2dnotes.dll   u2lexch.dll

p2smapi.dll   u2dpost.dll   u2lfinra.dll

p2smcube.dll   u2dvim.dll   u2lsamp1.dll

p2smsiis.dll   u2fcr.dll NOTE:  If you proceed with the full install of Crystal Reports, this directory will contain additional files. The following files will be installed into your PROGRAM FILES\Common Files\Microsoft Shared\DAO directory: dao350.dll   dao2535.tlb

  Setup will install the following files into your Windows\fonts or

Windows NT\fonts directory: ESRI Cartography (TrueType)   esri_1.ttf

ESRI Environmental & Icons (TrueType)  esri_2.ttf

ESRI Geometric & Symbols (TrueType)  esri_3.ttf

ESRI Oil, Gas, & Water (TrueType)  esri_4.ttf

ESRI Transportation & Municipal (TrueType) esri_5.ttf

ESRI Weather (TrueType)   esri_6.ttf

ESRI Geology (TrueType)   esri_7.ttf

ESRI Crime Analysis (TrueType)   esri_8.ttf

ESRI Transportation & Civic (TrueType)  esri_9.ttf In addition to these system files, the ArcView GIS 3.2 Setup program launches Microsoft Data Access Components (MDAC) 2.5 on all platforms, and Microsoft's Distribution COM for Windows 95 on 95 platforms. For a list of specific files installed with these executables, please see the Microsoft Web Page. Additional system files installed for Hardware Key installations only: Rainbow Sentinel Driver files

Windows 95/98

SENTINEL.VXD-73,728 bytes The following files are installed into \WINDOWS\SYSTEM\RNBOSENT

SENTSTRT.EXE-12,000 bytes

SENTW9x.EXE-32,768 bytes

SENTW9x.DLL-40,960 bytes

SENTW9x.HLP-10,240 bytes

Windows NT

RNBOVTMP.DLL-18,432 bytes

SENTINEL.HLP-10,240 bytes The following file is installed into \WINNT\SYSTEM32\DRIVERS

SENTINEL.SYS-73,728 bytes  Back to TOC 6.0 ArcView GIS 3.2 Font Changes

-ArcView GIS 3.2 installs updated ESRI fonts which are embeddable into presentations and files. For example if you make a Windows Meta File export from ArcView and insert it in Microsoft PowerPoint, within Microsoft PowerPoint you can choose 'Embed Fonts'. This ensures that others who do not have ArcView installed can see your WMFcorrectly. -Mapping Fonts in Adobe Illustrator Export Format:

ArcView uses /etc/comftnam.dat to map font names to standard font names.  In the past there was only support for the three standard font names already in the file.  For 3.2, we've changed logic so that any font name on the right side of the comftnam.dat will be treated as a standard font name.  Thus, users can map any font to any other font.  Note, font names should not include spaces (remove them—see example below).  Additionally, if users want text to be stored as outline, they should map the font name to "None" (example for font name "UserFont"):  UserFont  None

 TimesNewRoman Times

  7.0 Known Issues  Annotation and certain printers

 Under Windows 95/98, with some Annotation coverages and certain printers (HP650C, for example) selected in Print Setup, the error message "Unable to open feature source" may appear. Workaround: Set your printer to another printer.  General Hardware Known Issues

 -It has been reported that the following graphics card prevents ArcView GIS from running properly:

 16MB Revolution IV / 128 bit AGP Super VGA graphics card CM812 on Revolution IV (Standard - HawkEye, DirectX)  -After installing ArcView onto Windows NT 4.0, NT 4.0 crashes if the default printer is set to a fax modem.

 Workaround: Change the default printer to a printer.  Indexing a CAD Drawing Theme Table

 ArcView GIS creates spatial indexes only on visible CAD layers. In theme properties, the user can check on individual CAD layers to make them "Visible." Layers that are not checked are therefore not visible and will not draw with the theme. If a spatial index was created on several of the available layers, and all available layers are subsequently made visible, actions such as zooming  may result in certain entities disappearing from the view.

 To avoid this, make all layers visible, build a spatial index and then select only those layers you

 want to display.  Installation

 During the ArcView GIS 3.2a installation, a message may appear referring to Windows setting up the Control Panel. This occurs while ArcView GIS 3.2a setup installs MDAC 2.5. No user action is required, the message is informational only.  NITF Image Support

-When an NITF file is used in ArcView 3.2a, it writes a temporary *.bsq file to the Working Directory.  The Working Directory can be checked and/or set by choosing "Set Working Directory" in a view's File pull down menu. If the NITF image contains compression, then the image must be decompressed as well.  This can result in another large temporary file being placed into your working directory, so ensure that you have plenty of free disk space on that drive (i.e. >250MB).  If you run out of disk space, ArcView will display a series of error messages.  In this scenario, simply click OK to these error messages, exit ArcView, and then manually delete the temporary files in your working directory. The new NITF Image Support extension does not support writing of NITF image files. The new NITF Image Support extension does not support NITF version 2.1 files. The new NITF Image Support extension is not a "certified" NITF reader/display tool (i.e.  it has not been through the JITC process). When the NITF Image Support extension and the TIFF 6.0 Image Support extension are loaded at the same time, attempting to use an NITF image containing annotation will result in a non-fatal error message. Non-annotated NITF image work will not display an error message.

   Online Help

 The Arcview GIS 3.2 Online Help includes outdated contact information for Lizard Tech.  The correct information is:  LizardTech Inc.

 The National Building

 1008 Western Ave

 2nd Floor

 Seattle, WA  98104  Ph: 206-652-5211

 Fax: 206-652-0880  Pathname limitations

 In addition to pathname and filename limitations already mentioned in the online help, there is a limit on Windows to 123 characters in the pathname. Longer pathnames may return errors. Workaround: Place your data into a location with a shorter path.  Printing

 -Layouts with several different fonts or font variations process, but do not print to HP DeskJet 1600CM/PS using enhanced PostScript.

 Limited memory on the printer may be the cause.

 Add more memory to the printer.

 Use fewer fonts or variations.

 Print with the basic PostScript option or the native driver.

 Print through ArcPress.  -Printing large MrSID images to large page sizes causes the printer to hang, fills up the disk with temporary files, or is very slow.   -A MrSID image of a few megabytes really represents hundreds of megabytes if not gigabytes of data. This data cannot be printed in its compressed form, so it needs to be uncompressed. This takes time and resources. The following suggestions are recommended for printing MrSID images.  To avoid hanging your printer always export a layout or view using the PostScript New (EPS) option and then use ArcPress to send the exported PostScript files to your plotter.  To avoid filling up your disk with temporary files obtain more disk space or use the AVMRSID_MAXSIZE environment variable to limit the size of temporary images that are created.  Using the AVMRSID_MAXSIZE environment variable to limit the size of a temporary image will result in the MrSID image having less resolution in your plot. The AVMRSID_MAXSIZE environment variable should be set to the maximum size of temporary image you have space for in bytes. The ideal value depends on the size of images you are working with, available system resources, and on the quality required for the printed imagery. We recommend you experiment with multiple value settings to find one that is ideal. It is best to never set the AVMRSID_MAXSIZE environment variable to greater than half of your available disk space. You will need room for both the temporary image and the plot file. The AVMRSID_MAXSIZE environment variable can also be used to speed up printing of MrSID images. Setting the AVMRSID_MAXSIZE environment variable to 0 is the same as not setting it at all.  Projection Utility

 Shapefiles of type MultiPoint are not projected by the utility. Workaround: Convert the shapefile from MultiPoint to Point using MultiPoint.AsList or PolyLine.Explode before projecting (since PolyLine inherits from MultiPoint). A sample script can be found in ArcView's help for the PolyLine.Explode request.  The fieldname FeatureID is reserved and will not appear on the output shapefile. Workaround: Make the shapefile a theme in ArcView, then open its table and alias or hide the field, then save your shapefile to a new shapefile.  DBase III format for .dbf files allows numeric fields a maximum precision of 19. The utility will display this error if it encounters numeric fields with a precision higher than 19: "An unknown error occurred in writing shapefile."  Workarounds:

 1) Use the Projector! extension.

 2) Modify the data in ArcView (hide the fields and save to a new shapefile) before processing with the Projection Utility.  Turning off virus checkers greatly improves the performance of the Projection Utility.  In some cases, specifying the GeoTransformation on the command line may cause the data to move in the opposite direction.

 Workaround: Perform the GeoTransformation using the interface (wizard).

   SDTS Utilities

 Shortcuts to the SDTS utilities are provided in the ArcView program group. The executables installed in the \bin32 directory, must be run from a command prompt.

   ShapeDXF

 To display information to the screen about a shapefile using the ShapeDXF program, the program must be run from a Command Prompt. To list information about a shapefile in a text file, you can use the ShapeDXF shortcut found in the ArcView GIS Program group.  See the ArcView GIS online Help for more information about the ShapeDXF program.

   SQL

 -Access number fields with decimals are being padded with extra zeros in ArcView GIS.  -The "*" character does not provide access to all available tables in the database in ArcView GIS Version 3.1 and remains a known limit for 3.2.  Views and Themes

 -Using extended image formats (ImgDLL)

 This information will help you properly use the extended image formats:

 1. When an image theme is added using ImgDLL, ArcView will ask the external DLL for a zero size image. This is necessary to set up the ImgDLL structure. This image is not used. The DLL should pass back a small image.

 2. When ImgDLL asks the external DLL for an image for a view extent that does not overlap the image, it still needs to pass back an image. A small image of the extent of the image should be passed back.  -Manage Data Sources does not support data sources with spaces in their names.  -Drawing a 1-bit TIFF (non-TIFF 6.0) with the TIFF 6.0 extension loaded causes drawing and memory problems. Workaround: change the image's legend to Grayscale.  -Spatial indexes for read-only data (such as shapefiles that are on a CD) are written to the current working directory. If the current working directory does not have write access, the files are written to the temporary (TEMP or /tmp) directory. The index file names are converted to an 8.3 naming convention if necessary, and have a .fbn/.fbx suffix. For example, the temporary spatial index files for a shapefile on a CD called Backgrnd.shp are called backgr1.fbn and backgr1.fbx. These files are deleted when you exit ArcView GIS.  -You may need to set the default printer to a valid printer to use the IMAGINE extension.  -If Image Analysis Version 1.0 is installed but the extension is not loaded, displaying a MrSID image may result in a "Error calling unlink for file C:\TEMP\ximg2.bil" type of error message. This occurs when you have both the MrSID Image Support extension and either the IMAGINE Image Support or TIFF 6.0 Image Support extension loaded at the same time and have installed the Image Analysis extension.  You can avoid this error by turning off the IMAGINE Image Support or TIFF 6.0 Image Support extensions or by displaying MrSID images as a "Image Analysis Data Source" via the Image Analysis extension.  This issue will be resolved in the next version of the Image Analysis extension.

   Crystal Reports for ESRI

 -ArcView GIS 3.2 will install Seagate Crystal Reports 7.0 for ESRI.  If you have Crystal Reports 6.0 installed, the Crystal Reports setup will display a dialog asking if you'd like to replace your previous version. You should respond “Yes” to continue with the installation.  -To run Seagate Crystal Reports on both operating systems of a dual boot machine (i.e., on both Windows NT 4.0 and Windows 98), you must install the software under both operating systems.  After you have installed Crystal Reports under one of the operating systems, during the installation on the other operating system, the Crystal Report's installation will inform you that an earlier version of Seagate Crystal Reports currently exists and asks you if you wish to replace it with the new version.  You must respond yes and proceed with the installation to install Crystal Reports in both operating systems.  -If the full Crystal Reports software is not installed, selecting Launch Crystal Reports from the Project File menu (with the Report Writer extension loaded) results in an error message.

   Sample Extensions

 There is a conflict between the ADRG and the sample DIGEST raster image extension when both extensions are loaded. The ADRG extension will attempt to load ASRP images due to the same .img file extension of the image files. Therefore, the ADRG and ASRP extensions should not be loaded at the same time.  Back to TOC 8.0 New Projection Utility FAQs

Q: My coordinate system is not listed in the utility.

A: Contact POSC (Petrotechnical Open Software Corporation) about getting your coordinate system added to their model. POSC is a consortium of oil and gas companies. This utility uses a model developed by POSC which simplifies the various pieces that compose a coordinate system. A related organization, EPGS (European Petroleum Survey Group), has compiled a large set of coordinate systems and the objects needed to define them. Coordinate systems defined by EPSG/POSC are added to the Projection Engine (on which the utility is built) on a regular basis. Contact them on the web at:

http://www.petroconsultants.com/products/geodetic.html Q: I added some extensions to the projutil.txt file. Why don’t my output shapefiles draw in ArcView?

A: Did you accidentally add the spatial index extensions (sbx and sbn) to this file? You do not want the old spatial index files copied over – the utility will generate new spatial indexes for the output shapefiles. Remove sbx and sbn from projutil.txt, and reproject your shapefiles. They should now draw in ArcView. Q: What does the Projection Utility do during initialization?

A: Here is a breakdown list of what happens. The list is divided into two parts:       Before the form is loaded

      While the form is visible  Part 1: Before the form is loaded (before the wizard is visible)     1. Check to see if the utility is running from a valid ArcView installation

    2. Parse the command line

    3. Determine if there are command line errors. If there are errors, ask user if they want to run the wizard or not

    4. If Quiet mode (-Q) was specified, do final checks and begin Quiet mode processing  Part 2: While wizard is loading and while splash panel is visible     5. Save command line parameters before Loading wizard

    6. Load/Create the MapObjects map object

    7. Load Resource Strings for wizard

    8. Initialize wizard appearance (which buttons are on, or off, etc.)

    9. Set a background timer to accomplish the rest of the initialization steps (while form is visible) At this point, the wizard initialization is complete and the splash screen becomes visible, but the controls on the wizard have not be initialized yet. The remaining tasks now deal with filling in the controls on wizard steps.    10. Turn off Buttons, Hide/Show Advanced tabs

   11. Create/Initialize the GeoTransformation description collection

   12.Fill in the MapObjects list controls (updating the progress bar after each control)

      a. Move some controls into correct position

      b. Create ListView control on Step 1

 c. Fill each MapObjects list control (16 controls

         [This is where most of the time is spent.]

   13. Turn off the Progress bar, turn on the Step 1 panel buttons, go to the first panel