SAR Technology - Tips & Tricks

Displaying 'Incident Commander Pro' Maps in other GIS Applications	Copying 'Incident Commander Pro' GIS Maps to another Computer
Up/Download 'Incident Commander Pro' GPS Routes, Tracks & Waypoints	Creating 'Incident Commander' Reports as Microsoft portable XPS files
Print 'Incident Commander Pro' maps in large format	Display 'CAD Files in Incident Commander Pro'
Display 'Incident Commander' Reports on your PDA	Store your Document & Image files within the 'Incident Commander' Folder
Creating 'Incident Commander' Reports as PDF files	Prepare Pre-Planned Missions using 'Operational Period Zero'
Sharing '‘Incident Commander' Data between Organizations	Expanded 'Help' features for 'Incident Commander' software
Program Backup of 'Incident Commander' software	Backup of 'Incident Commander' data

Displaying 'Incident Commander Pro' maps in GIS applications can be useful when other organizations wish to review the shapefile GIS maps created by 'Incident Commander Pro'.

The customized 'Incident Commander Pro' Areas Polygons, Routes, Lines and Labels, which are drawn on top of the base map layers, can be directly displayed by other GIS applications.
Adding projection files, from the table below, permits these customized features to be displayed, with their full geo-locating and scaling, in other GIS applications.

Instructions:
e.g. for an 'Incident Commander Pro' mission map called 'Mission1'
Right-click the Route projection file for your region and Save Target As...

C:\Program Files\SAR Technology\IC\Gis\Data\Mission\Mission1_ln.prj
Right-click the Area projection file for your region and Save Target As....

C:\Program Files\SAR Technology\IC\Gis\Data\Mission\Mission1_ply.prj
Right-click the Label projection file for your region and Save Target As....

C:\Program Files\SAR Technology\IC\Gis\Data\Mission\Mission1_pnt.prj

or
e.g. for an 'Incident Commander Pro' default map called 'YosemitePark'
Right-click the Route projection file for your region and Save Target As...

C:\Program Files\SAR Technology\IC\Gis\Data\Default\YosemitePark_ln.prj
Right-click the Area projection file for your region and Save Target As....

C:\Program Files\SAR Technology\IC\Gis\Data\Default\YosemitePark_ply.prj
Right-click the Label projection file for your region and Save Target As....

C:\Program Files\SAR Technology\IC\Gis\Data\Default\YosemitePark_pnt.prj

Common GIS applications will then be able to directly browse to and display these geo-located and scaled customized 'Incident Commander Pro' maps.

Alternatively the customized map feature files (.shp .shx .dbf .prj) may be copied to another computer for a GIS application to display:
e.g. Copy to [New Computer]

C:\Program Files\SAR Technology\IC\Gis\Data\Mission\Mission1_ln.shp Mission1_ply.shp Mission1_pnt.shp Mission1_ln.prj Mission1_ply.prj Mission1_pnt.prj Mission1.shx Mission1.dbf

Copying 'Incident Commander Pro' GIS maps to another computer can be useful for both backing up the maps and for displaying these maps on other computers. Sharing the GIS maps can be especially useful when other teams and organizations running 'Incident Commander Pro' are assisting with an incident.

Incident Commander Pro's GIS maps contain

background map layers and customized map features.
These layers and features can be copied to another computer as follows:

Example: Assuming the 'Incident Commander Pro' background map layers of states, rivers, roads and cities were added from

C:\Mapfiles\US\ ...

1. Copy the entire background layers folder [Original Computer]

C:\Mapfiles\US\ to [New Computer]

C:\Mapfiles\US\

2. For an 'Incident Commander Pro' default map called 'YosemitePark'
Copy the customized map features file-set (.map .shp .shx .dbf) to the same folder on the new computer...

Copy [Original Computer]

C:\Program Files\SAR Technology\IC\Gis\Data\Default\YosemitePark.map YosemitePark.shp YosemitePark.shx YosemitePark.dbf
to [New Computer]

C:\Program Files\SAR Technology\IC\Gis\Data\Default\YosemitePark.map YosemitePark.shp YosemitePark.shx YosemitePark.dbf

When Incident Commander Pro's GIS map module is then opened on the new computer the copied 'YosemitePark' default map will be listed for display.

Tip: Upload/Download 'Incident Commander Pro' GPS Routes , Tracks & Waypoints

GPS Waypoints:
Waypoint locations stored on the GPS can be downloaded and displayed as individual point locations on the GIS map, as either a 'dxf' or 'shape'-file. Garmin's Mapsource software will download and save these locations as a 'dxf' file, which can then be displayed as a

'dxf'-points layer on the GIS map.

Use the shape-file Comment, or the dxf-points file Description, map-layer property to display labels beside these map icons. This can be very useful for customizing local maps with specific local features such as landmarks, landing zones, repeater sites etc.

Tip: Creating 'Incident Commander' Reports as Microsoft portable XPS files

Creating 'Incident Commander’ reports as Microsoft XPS files.

Here is a convenient new way to view and share 'Incident Commander Pro' information.

These XPS files (.xps) may be printed immediately from the 'Incident Commander' Print menu, viewed directly in Internet Explorer, saved as permanent data backup, emailed to the responsible agency and shared with other applications.

'Incident Commander Pro's GIS

'Export Map Image' function permits the displayed map to be saved as a jpg image file. This image can be printed directly at the normal printer paper size.

Many image editors, such as Ulead Photo Express, permit images to be printed in a large-scale tiled 'poster' format.

Before exporting the map image increase the Scale Factor from 1 to 5, to increase the image resolution, and then print the saved image using a tiled 'poster' print utility. This permits multiple hard copy pages to be tiled together to create a large scale 'poster' map.

Tip: Display 'CAD Files in Incident Commander Pro'

'Incident Commander Pro' can display many common file types as

map layers within it's GIS map module. These file types including shape-files, coverages, tif, gif, jpg, bmp and MrSID images . 'Incident Commander Pro' also has the capability to display the vector-based .DXF and .DWG CAD drawing files.

Being able to display DWG and DXF files provides the unique opportunity to review geo-located buildings and site-plans - such as stadiums, conference centers, airports, public utilities, dams, power stations and other critical infrastructures - within the 'Incident Commander Pro' GIS map module. These CAD file types are displayed as true engineering drawings, with all of their associated properties - for example color, line-size, labels etc. - available for fully customizable display by 'Incident Commander Pro'. For more information see Displaying CAD Files in 'Incident Commander Pro' .

Printing 'Incident Commander' reports to a PDF printer driver permits the fully formatted report files to be saved on the local computer or a sent to a PDA. After transferring via the docking station, infrared port or cellular email connection, these fully formatted PDF reports may be viewed on a PDA for rapid use by the incident response team.

Tip: Store your Document and Image files within the 'Incident Commander' Folder

Running 'Incident Commander' over a network requires that your linked files, such as Portrait images, Pre-Plan documents, Route images and Area images, be available to all of the computers on the network. Storing these files in sub-folders of 'Incident Commander' on the host computer will ensure that all these user folders and files will be shared and accessible by all the client networked computers.

1. Create the new folders: My_Documents, My_Reports, My_Portraits, My_RouteImages and My_AreaImages under the shared host computer
C:\Program Files\SAR Technology\IC\    folder.
eg:
C:\Program Files\SAR Technology\IC\My_Documents      - for your Pre-Plan documents.
C:\Program Files\SAR Technology\IC\My_Reports             - for your exported reports and fully-formatted PDF print reports.
C:\Program Files\SAR Technology\IC\My_Portraits          - for your Personnel and Missing Person images.
C:\Program Files\SAR Technology\IC\My_RouteImages - for your Route Images.
C:\Program Files\SAR Technology\IC\My_AreaImages    - for your Area images.

2. Place your document and image files in these folders.
This will make them easy to find over the network and ensures that they can be shared and displayed by all of the networked computers running 'Incident Commander'.

Tip: Creating 'Incident Commander' Reports as PDF files
Creating 'Incident Commander’ Reports as PDF files.
Here is a convenient new way to share and archive 'Incident Commander' information. By installing a PDF printer driver ‘Incident Commander’ reports can be printed directly to the PDF (Personal Document File) format. This creates output to a PDF file that is an exact, formatted copy of the original report. These PDF files (.pdf) may be printed immediately from the 'Incident Commander' Print menu, saved as permanent data backup, emailed to the responsible agency and shared with other applications.

Tip: Prepare Pre-Planned Missions using 'Operational Period Zero'
'Many users have asked if they can create permanently-stored pre-planned missions. The answer is Yes! - and the process is very simple...

Step 1. Create a new (pre-plan) mission and give it a name that indicates it is a preplan e.g.: 'Terrorist-Response Pre-Plan'.
Step 2. Give the mission an Operational Period Number ''0'.
(The Operational Period Number '0' indicates that the mission is a pre-plan and not yet active).
Step 3. Enter all of the information that describes the mission - for example a Communications Plan and a list of expected Mission Trails and Mission Search Areas. An Operations Plan, consisting of a list of pre-prepared Assignments, is then created, followed by any additional support information, such as the standard ICS section forms, to complete the pre-plan.
Step 4. The stored pre-plan is then saved and kept ready to be used, whenever the plan has to be implemented.

Activation of the Preplan. The stored pre-plan can be immediately activated at any time by opening the pre-planned mission, renaming it slightly if required, and changing the Operational Period Number to '1' (the first active operational period). All of the pre-planned information previously entered for the mission may now be used to immediately respond to the incident.

In this way an unlimited number of pre-plans can be created and stored permanently for immediate response to any type of pre-planned incident.

Tip: Sharing '‘Incident Commander' Data between Organizations
Response teams often wish to share information, such as as their 'Incident Commander' software's Personnel and Organizations lists, with their neighboring teams. Sharing and combining their lists permits the rapid check-in of searchers from neighboring teams and provides an expanded Teams & Agencies resource list. Data can be shared between organizations using the three simple steps outlined below:

Step 1: Export the 'Incident Commander' data to a Spreadsheet:

Data can be exported using 'Incident Commander's' Export utility, found within the Print Reports function. For example; export the Personnel Names report to an Excel spreadsheet e.g. as 'PersonnelNames.xls'. This spreadsheet file can be given or emailed to the neighbouring teams.

Step 2: Simplify the Spreadsheet Display:
Open the Excel spreadsheet, select and then hide all of the columns you do NOT wish to import - for example all of the columns except those listing personnel names and telephone numbers. Use Excel's Format... Column... Hide... menu items to hide these unwanted columns. The simplified spreadsheet will now display only the personnel names and telephone numbers to be imported.

Step 3: Paste Data into 'Incident Commander'
Arrange your computer desktop with the 'Incident Commander's' Personnel window above the Excel window.

1. Create a new personnel record using the 'new' button.

2. Place the cursor over the Name record in Excel and press Ctrl-C to copy the name.

3. Place the cursor in the Name field in 'Incident Commander's Personnel window and press Ctrl-V to paste the name into the field.

4. Repeat this process for each of the phone numbers (home number, work number) etc.. and then save the record in 'Incident Commander'. Repeat this process for each personnel record.

This simple procedure will rapidly import the previously-exported data into 'Incident Commander'.

Tip: Expanded 'Help' features for 'Incident Commander' software
Many 'Incident Commander' users have asked for additional information on how to setup, network and backup their copies of 'Incident Commander'. To assist in these important functions the 'Incident Commander' Help facility has been expanded to include more detailed information on these topics. You may view and download the latest 'Incident Commander' Help files from the SAR Technology Downloads webpage.

Tip: Program Backup of 'Incident Commander' software
It is a good idea to make regular, dated backup copies of the entire 'Incident Commander' program.
Create backup copies of the entire 'Incident Commander' software program by copying to a separate (safe) location on a remote, large-capacity storage disk.

It is recommended that the Incident Commander program be backed up (copied) to another 'remote' (client) computers, or onto a CD or mass storage device, after each Operational Period, at the completion of the mission or after a major data entry session.

The best backup option for the 'Incident Commander' program is to copy the entire program onto a large-capacity removable-media drive such as a re-writable CD-ROM, portable hard drive, mass storage device, etc. These offer fast backup and simple restore capabilities through the Windows Explorer.

When backing up, first close Incident Commander and then COPY THE ENTIRE Incident Commander FOLDER STRUCTURE, INCLUDING ALL SUBFOLDERS, to the backup device. Do not attempt any selective or partial backup, as files in different folders are related to each other.

Never attempt to copy Incident Commander will the program is running on any computer as data corruption of open files may occur.

Backup Tip: After the entire 'Incident Commander' directory folder has been copied to its backup location it is recommended that this backup folder be renamed to include the backup date, e.g. to a folder named: '[Drive]:SearchManager_23July2005'.

This backup folder contains a full copy of the latest data in the 'Incident Commander' program. It also ensures that this backup folder can be copied back onto the 'host' computer and used to run any future incident.

Tip: Backup of 'Incident Commander' data
Data backup is carried out using the Print... Export data function within the 'Incident Commander' software program - typically to text files (.txt), database (.dbf) files or Excel files (.xls). These files should be stored off the host computer onto a mass storage device, portable hard drive, floppy disk or CD.

Data Backup: Printing Reports
All of the reports listed in 'Incident Commander' may be printed out through the Print Reports function. It is strongly recommended that every report listed be regularly printed out and stored in a binder that is kept in a safe location. This hard-copy form will ensure that the data entered into 'Incident Commander' will always be recorded in a relatively permanent (paper), non-electronic format. Printing reports directly from the Print Report function will ensure that every record in each table's report will be printed. (Printing from an open form will typically only print the single, current record, or one page-length of records).

Data Backup: Exporting Reports
All of the reports listed in 'Incident Commander's' Print Reports function may also be exported in a variety of formats, including text files (.txt), database (.dbf) files or Excel files (.xls). It is strongly recommended that every report listed be regularly exported to at least one of these electronic formats. The files created during the Export process should then be copied and stored onto a floppy disk, CD, Zip disk, or copied onto another computer, this will keep this file data safe from the risk of a hardware or software crash on 'Incident Commander's 'host' computer. If there is ever a need to restore the data then these files can be opened, their data 'copied' and then 'pasted' back into the correct form's fields within 'Incident Commander'.

'Incident Commander Pro' Projection Files
ProjectionICProRoutes_WesternUSA_ln.prj ProjectionICProAreas_WesternUSA_ply.prj ProjectionICProLabels_WesternUSA_pnt.prj	ProjectionICProRoutes_CentralUSA_ln.prj ProjectionICProAreas_CentralUSA_ply.prj ProjectionICProLabels_CentralUSA_pnt.prj	ProjectionICProRoutes_EasternUSA_ln.prj ProjectionICProAreas_EasternUSA_ply.prj ProjectionICProLabels_EasternUSA_pnt.prj
ProjectionICProRoutes_WesternCanada_ln.prj ProjectionICProAreas_WesternCanada_ply.prj ProjectionICProLabels_WesternCanada_pnt.prj	ProjectionICProRoutes_CentralCanada_ln.prj ProjectionICProAreas_CentralCanada_ply.prj ProjectionICProLabels_CentralCanada_pnt.prj	ProjectionICProRoutes_EasternCanada_ln.prj ProjectionICProAreas_EasternCanada_ply.prj ProjectionICProLabels_EasternCanada_pnt.prj
ProjectionICProRoutes_Switzerland_ln.prj ProjectionICProAreas_Switzerland_ply.prj ProjectionICProLabels_Switzerland_pnt.prj	ProjectionICProRoutes_Baltic_ln.prj ProjectionICProAreas_Baltic_ply.prj ProjectionICProLabels_Baltic_pnt.prj	ProjectionICProRoutes_Romania_ln.prj ProjectionICProAreas_Romania_ply.prj ProjectionICProLabels_Romania_pnt.prj
ProjectionICProRoutes_NorthAfrica_ln.prj ProjectionICProAreas_NorthAfrica_ply.prj ProjectionICProLabels_NorthAfrica_pnt.prj	ProjectionICProRoutes_Australia_ln.prj ProjectionICProAreas_Australia_ply.prj ProjectionICProLabels_Australia_pnt.prj	ProjectionICProRoutes_NewZealand_ln.prj ProjectionICProAreas_NewZealand_ply.prj ProjectionICProLabels_NewZealand_pnt.prj
(The content of these geo-referencing projection files can be viewed in Notepad) ICPro_CreatingProjectionFiles.txt (Projected Coordinate System, UTM-NAD83, UTM-WGS84, UTM-WGS72, UTM Zone#, Metric)