SOCETSET User Man

SOCET SET User’s Manual
Version 5.5
April 2009
EXPORT CONTROLLED DATA: These commodities, technology or software are controlled for
export in accordance with the United States Export Administration Regulations. Diversion
contrary to U.S. law is prohibited.
SOCET SET i
Important Notices
Copyright ©1989 - 2009 BAE Systems
This manual, as well as the software described in it, is furnished under license and may only be
used or copied in accordance with the terms of such license. The information in this manual is
furnished for informational use only, is subject to change without notice, and should not be
construed as a commitment by BAE Systems. BAE Systems assumes no responsibility or liability
for any errors or inaccuracies that may appear in this book.
Manuals On-Line
Electronic versions of the manuals are available in PDF. The Acrobat Reader™ is required to
access the PDF version of the manuals. Internet Explorer or Netscape Browser are required for
viewing the online help. The following documents reside in <install_path>/doc:
• SOCET SET® User’s Manual
• System Administration Manual
• Installation Manual
• Release Notes
Except as permitted by such license, no part of this publication may be reproduced, stored in a
retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording,
or otherwise, without the prior written permission of BAE Systems.
Purchasing a license for this product, authorizes you to print one (1) copy of this manual.
If you have questions regarding SOCET SET software and/or hardware, please contact your
distributor.
Disclaimer
The information in this document is subject to change without notice. BAE Systems makes no
warranty of any kind with regard to this material, including, but not limited to, the implied
warranties of merchantability and fitness for a particular use. In no event shall BAE Systems be
liable for special or consequential damages arising from the use of this material or the products
described herein. BAE Systems assumes no responsibility for any errors that may appear in this
document. BAE Systems makes no commitment to update nor to keep current the information
contained in this document.
SOCET SET i
Important Notices
Export Controlled Data

These commodities, technology or software are controlled for export in accordance with the
United States Export Administration Regulations. Diversion contrary to U.S. law is prohibited.
Trademarks
SOCET SET is a trademark of BAE Systems
Portions of this computer program are copyright ©2003 LizardTech, Inc. All rights reserved.
MrSID is protected by U.S. Patent No. 5,710,835. Foreign Patents Pending.
Portions of this software are based in part on the work of the Independent JPEG Group.
All other trademarks are the property of their respective owners.
Typographic Conventions
STYLE DESCRIPTION
Italic New terminology, names of separate documents, command line argument

place holders.
<Text> Hovering over the word or phrase will provide additional information.
Typewriter Commands (followed by the manual section number in parentheses), Unix

command line examples (preceded by the %-character, which represents
the command line prompt), file names and directory paths, the contents of
a text file, accelerator keys (F1, <Ctrl>X).
Special warnings and other critical information for you to consider.
File > Exit Execution commands done by clicking on menus or buttons with the
cursor.
RMB click Will bring up a C o n t e x t M e n u dependent upon the area clicked.
See... on page... Hypertext to additional information.
ii SOCET SET
Table of Contents
TABLE OF CONTENTS
Important Notices - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -1
Chapter 1 Workstation Operating Instructions - - - - - - - - - - - - - - - - - - - 1-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-1
Operator’s Interface - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-3
Chapter 2 Workstation Description - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-1

Workstation Purpose - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-1
Other Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-3
Workstation Components- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-3
Software Description - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-5
Chapter 3 Workflow - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-1
Customizing Your Workflow - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-1
Job Queue Manager - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-3
Sample Workflows - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-7
Chapter 4 Main Workstation Window - Full Roam - - - - - - - - - - - - - - - - 4-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-1
Main Menu Bar - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-3
Primary Viewport - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-7
Image Enhancement - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-12
Image Enhancement File - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-24
Image Chipping - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-25
Chapter 5 Project Management - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-1
Creating a Project - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-3
Create/Edit Project Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-4
Reviewing and Editing a Project - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-14
Changing Coordinates, Units, or Datums - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-14
Copy Project - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-16
Data Review - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-19
Chapter 6 Backup, Restore and Delete - - - - - - - - - - - - - - - - - - - - - - - - - 6-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-1
Backup - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-2
Restore - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-5
Delete- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-7
Chapter 7 Image Import and Export - - - - - - - - - - - - - - - - - - - - - - - - - - 7-1
SOCET SET TOC-1

Table of Contents
Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-1
Image Import Overview- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-1
QuickBird/WorldView Image Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-8
Image import/Reformat - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-9
CIB Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-19
CIB Viewer - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-21
CADRG Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-22
Image Export - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-24
Image Export/Reformat - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-24
USGS DOQ Export - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-30
Fast Sensor Model - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-32
FORMOSAT 2 Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-35
ALOS PRISM Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-38
ALOS AVNIR 2 Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-41
EROS B Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-46
RADARSAT 2 Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-49
TerraSAR-X Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-52
ASTER Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-55
COSMO-SkyMed Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-60
Chapter 8 Frame and Panoramic - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 8-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 8-1
Frame Import- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 8-8
BINGO Frame Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 8-16
Panoramic Import/Edit - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 8-17
Next Step - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 8-26
Chapter 9 QuickBird WorldView Import - - - - - - - - - - - - - - - - - - - - - - - 9-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 9-1
QuickBird Basic Image Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 9-2
Execution - QuickBird/WorldView - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 9-3
Batch Processing - QuickBird/WorldView Import - - - - - - - - - - - - - - - - - - - - - - - - - - 9-3
Outputs - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 9-4
Triangulating QuickBird Images - - - - - - - - - - - - - - - - - - - - - - - - - - 9-4
Chapter 10 Landsat Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 10-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 10-1
Landsat Image Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 10-3
Execution - Landsat - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 10-4
Outputs - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 10-5
Chapter 11 SPOT, JERS and IRS Import - - - - - - - - - - - - - - - - - - - - - - - 11-1

Overview of SPOT, JERS, and IRS - - - - - - - - - - - - - - - - - - - - - - - - - 11-1
SPOT Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 11-4
TOC-2 SOCET SET

Table of Contents
JERS Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 11-9

Stereo JERS Imagery - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 11-10
IRS Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 11-13
Chapter 12 RADARSAT and ERS Import - - - - - - - - - - - - - - - - - - - - - - 12-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 12-1
RADARSAT Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 12-1
RADARSAT Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 12-4
ERS Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 12-6
Chapter 13 ADS40 Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 13-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 13-1
ADS40 Image Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 13-2
Execution - ADS40- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 13-3
Chapter 14 OrbView-3 Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 14-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 14-1
OrbView-3 Image Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 14-2
Execution - OrbView-3 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 14-3
Batch Processing - OrbView-3 Import - - - - - - - - - - - - - - - - - - - - - - - - 14-3
Chapter 15 GeoEye-1 Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 15-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 15-1
GeoEye-1 Image Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 15-2
Chapter 16 Data Import and Export- - - - - - - - - - - - - - - - - - - - - - - - - - - 16-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 16-1
ASCII Ground Point Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 16-3
ASCII Image Point Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 16-5
Chapter 17 Terrain Import and Export - - - - - - - - - - - - - - - - - - - - - - - - 17-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-1
ASCII DTM Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-1
NED GridFloat Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-8
ASCII ARC Grid Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-10
DEM Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-11
DTED Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-13
SDTS Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-16
GSI DEM Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-18
LIDAR Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-20
GeoTIFF Import- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-25
NITF Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-27
BIL Terrain Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-30
ASCII DTM Export - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-32
SOCET SET TOC-3

Table of Contents
NED GridFloat Export - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-35

ASCII ARC Grid Export - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-37
DEM Export - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-38
DTED Export - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-41
SDTS Export - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-51
DGN Data Format Conversions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-53
GeoTIFF Export- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-56
NITF Export - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-60
Chapter 18 Feature Import and Export - - - - - - - - - - - - - - - - - - - - - - - - 18-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 18-1
DXF Feature Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 18-1
Batch Processing - DXF Features Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 18-4
ARC_GEN Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 18-5
ASCII Feature Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 18-7
Shapefile Import- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 18-12
DXF Feature Export - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 18-16
ARC_GEN Export - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 18-18
ASCII Feature Export - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 18-23
MP ASCII Feature Export - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 18-26
Shapefile Export- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 18-27
DGN Feature Export - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 18-30
Chapter 19 SOCET for ArcGIS® - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 19-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 19-1
SOCET for ArcGIS - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 19-2
Execution - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 19-7
Tips and Tricks - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 19-19
Troubleshooting - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 19-20
Chapter 20 Visual Coverage Tool - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 20-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 20-1
Getting Started - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 20-2
Basic Functions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 20-3
Data Managers - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 20-10
Reference Backgrounds - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 20-17
Chapter 21 Image Minification- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 21-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 21-1
Minification- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 21-3
Batch Processing - Minification - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 21-5
Next Step - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 21-5
Chapter 22 Image Balancing: Dodger - - - - - - - - - - - - - - - - - - - - - - - - - - 22-1
TOC-4 SOCET SET

Table of Contents
Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22-1
Image Dodge and Balance - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22-3
Execution - Dodger- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22-9
Batch Processing - Dodger - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22-12
The Next Step - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22-14
Chapter 23 Control Point Editor - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 23-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 23-1
Control Point Editor - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 23-3
Execution - Control Point Editor - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 23-5
Adding Points by Measuring - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 23-6
Chapter 24 Interior Orientation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 24-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 24-1
Automatic Interior Orientation (AIO) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 24-3
Interior Orientation (IO) (Manual)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 24-6
Chapter 25 Multi-Sensor Triangulation - Overview and Workflow - - - - - 25-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 25-1
Sample Execution Scenarios - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 25-4
Batch Processing - Multi-Sensor Triangulation - - - - - - - - - - - - - - - - - - - - - - - - - - - - 25-9
Data Files - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 25-10
Automated Triangulation/Full Block - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 25-14
Tips for Triangulating Particular Sensors - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 25-23
Next Step - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 25-25
Chapter 26 Multi-Sensor Triangulation - Setup and GPS - - - - - - - - - - - - 26-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 26-1
Setup - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 26-1
GPS Information - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 26-18
Chapter 27 Multi-Sensor Triangulation - Point Measurement - - - - - - - - 27-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 27-1
Automatic Point Measurement - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 27-2
Interactive Point Measurement - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 27-14
Accuracy- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 27-22
Chapter 28 Multi-Sensor Triangulation - Solve - - - - - - - - - - - - - - - - - - - 28-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 28-1
Blunder Detect and Solve - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 28-1
Simultaneous Solve - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 28-10
Relative Orientation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 28-15
Chapter 29 DTM Registration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 29-1
SOCET SET TOC-5

Table of Contents
Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 29-1
DTM Registration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 29-2
Execution - DTM Registration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 29-3
Chapter 30 Feature Registration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 30-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 30-1
Feature Registration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 30-2
Execution - Feature Registration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 30-3
Chapter 31 Map Registration- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 31-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 31-1
Map Registration - Setup - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 31-2
Map Registration - Mensuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 31-2
Execution - Map Registration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 31-5
Chapter 32 Map Accuracy Assessment - - - - - - - - - - - - - - - - - - - - - - - - - 32-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 32-1
Execution - Map Accuracy Assessment - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 32-11
Chapter 33 Image Rectification - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33-1
Single Image Rectification - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33-3
Pairwise Rectification - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33-6
Batch Processing - Image Rectification - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33-8
Chapter 34 Image Scaling - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 34-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 34-1
Zoom/Scale - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 34-2
Execution - Scaling- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 34-3
Batch Processing - Image Scaling - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 34-4
Chapter 35 Terrain File Creation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 35-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 35-1
Creating a DTM - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 35-2
Create DTM - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 35-6
Executions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 35-10
Next Step - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 35-12
Chapter 36 Terrain Graphics- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 36-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 36-1
DTM and Overlay Range Windows- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 36-3
Executions Terrain Graphics - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 36-4
Batch Processing - Terrain Graphics - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 36-7
Chapter 37 Automatic Terrain Extraction - - - - - - - - - - - - - - - - - - - - - - 37-1
TOC-6 SOCET SET

Table of Contents
Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37-1
Automatic Terrain Extraction - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37-4
Executions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37-7
Batch Processing - ATE - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37-9
Next Step - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37-13
Chapter 38 Next Generation Automatic Terrain Extraction - - - - - - - - - - 38-1

Next Generation Automatic Terrian Extraction (NGATE) - - - - - - - - - - - - - - 38-1
Create a DTM for NGATE - NGATE Properties - - - - - - - - - - - - - - - - - - - 38-3
Batch Processing - NGATE - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 38-9
Chapter 39 Interactive Terrain Edit - - - - - - - - - - - - - - - - - - - - - - - - - - - 39-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 39-1
ITE Edit Tools - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 39-10
Execution - Interactive Terrain Edit- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 39-38
Chapter 40 ClearFlite - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 40-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 40-1
ClearFlite Main Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 40-5
Sketch Toolbar- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 40-12
Extract Obstructions Window in Manual Mode - - - - - - - - - - - - - - - - - - 40-12
Extract Obstructions Window in Automatic Mode - - - - - - - - - - - - - - - - - - - - - - - - - 40-13
Execution - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 40-18
Data Files - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 40-21
Chapter 41 Feature Specification Editor - - - - - - - - - - - - - - - - - - - - - - - - 41-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 41-1
Chapter 42 Feature Extraction- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-1
Feature Extraction - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-4
Polygon Topology - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-7
Feature Classes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-10
Draw/Snap Classes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-10
Feature Information - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-11
Feature and Element Attributes- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-11
Graphics Attributes- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-12
Retrieve/Manipulate - Feature Retrieval - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-14
Attribute Query - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-19
Attribute Validation Report - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-20
Mensuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-21
Texture Patch- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-24
Model Placement - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-27
Automated Population of Attributes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-29
SOCET SET TOC-7

Table of Contents
Simultaneous Collection - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-31

Generic Features - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-35
Batch Processing - A Feature Database - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-43
Chapter 43 Feature Database Merge - - - - - - - - - - - - - - - - - - - - - - - - - - 43-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 43-1
Feature Database Merge - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 43-1
Execution - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 43-10
Chapter 44 DTM/Feature Merge - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44-1
DTM Feature Merge - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44-4
View/Edit Boundary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44-7
Edit Class Algorithm Settings- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44-10
Executions - Merge- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44-11
Execution - Start Batch Job - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44-11
Batch Processing - DTM Feature Merge- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44-12
Chapter 45 Annotation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 45-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 45-1
Annotation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 45-4
Execution - Annotation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 45-11
Chapter 46 Orthophoto - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 46-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 46-1
Orthophoto Generation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 46-3
Execution - Orthophoto - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 46-15
Batch Process - Orthophoto - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 46-16
Next Step - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 46-18
Chapter 47 Multi-Spectral Image Sharpening - - - - - - - - - - - - - - - - - - - - 47-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 47-1
Execution - Multi-Spectral Image Sharpening - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 47-7
Chapter 48 Change Detection- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 48-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 48-1
Change Detection - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 48-2
Output Image- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 48-5
Execution - Change Detection - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 48-6
Chapter 49 Mosaic - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 49-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 49-1
Mosaic - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 49-3
Options - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 49-9
TOC-8 SOCET SET

Table of Contents
Execution - Mosaic - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 49-21

Batch Processing - Mosaic - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 49-22
Seamline Editor - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 49-26
Automatic Seam Polygons - - - - - - - - - - - - - - - - - - - - - - - - - - - - 49-30
Mosaic Sheet Cutter - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 49-32
Chapter 50 Perspective Scenes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50-1
Perspective Scene (Single Scene) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50-4
Getting Started - Single Scene Mode - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50-5
Perspective Scene (Multiple Scene) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50-7
Getting Started - Multiple Scene Mode - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50-10
Perspective Scene’s Advanced Features - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50-14
Eyepoint Route Setup and Aim Point Route Setup - - - - - - - - - - - - - - - - - - - - - - - - - 50-17
Route Feature File - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50-18
Eyepoint Route Editor - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50-18
Aim Route Editor - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50-24
Eyepoint Attribution - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50-27
Scene Content Selection - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50-30
Scene Parameter Setup - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50-32
Scene Rendering - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50-34
Animation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50-34
Chapter 51 Terrain Analysis - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 51-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 51-1
Terrain Analysis- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 51-2
Execution - Terrain Analysis - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 51-3
Chapter 52 Hardcopy Products and Image Maps- - - - - - - - - - - - - - - - - - 52-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 52-1
Image Previewing Tools - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 52-2
Screen Dumps - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 52-3
Printing Images on a Laser Printer- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 52-4
Anaglyph - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 52-6
Image Map - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 52-7
Executions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 52-20
Print Graphics - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 52-24
Batch Processing - Image Map - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 52-26
Limitations - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 52-27
Chapter 53 Line Of Sight- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 53-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 53-1
Line of Sight - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 53-2
Getting Started - Execution - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 53-8
SOCET SET TOC-9

Table of Contents
Chapter 54 CIB Generation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 54-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 54-1
Job Planning - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 54-1
Assessment Mosaic- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 54-13
Create Image Segments - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 54-15
Version History - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 54-18
Mosaic Production - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 54-20
CIB Image Source - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 54-22
Generate CIB- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 54-23
Merge 5-Meter Cells - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 54-26
Update Uncompressed Product - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 54-27
Chapter 55 DPPDB Generation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 55-1

Job Planning - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 55-1
File Structure for DPPDB - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 55-1
Segment Generation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 55-17
Create Image Segments - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 55-21
Quality Assurance - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 55-24
Feature Extraction - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 55-28
Generation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 55-28
DPPDB Update - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 55-31
Chapter 56 Geopositioning- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 56-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 56-1
Chapter 57 Export to Rendering Systems - - - - - - - - - - - - - - - - - - - - - - - 57-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 57-1
OpenFlight - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 57-1
Chapter 58 Sketch- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 58-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 58-1
Main Toolbar- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 58-3
Additional Toolbar - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 58-11
Examples - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 58-19
Chapter 59 Coordinate Measurement - - - - - - - - - - - - - - - - - - - - - - - - - - 59-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 59-1
Coordinate Measurement Interface - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 59-2
Chapter 60 3rd Party Tools - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 60-1

Condor Distributed Processing - - - - - - - - - - - - - - - - - - - - - - - - - - - 60-1
Chapter 61 Utilities - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-1
TOC-10 SOCET SET

Table of Contents
Command Line Tools - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-2

Graphics Terrain Settings - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-3
Camera Calibration Editor - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-5
Execution - Camera File - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-13
Report Editor - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-13
Radian / Degree Conversion- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-15
Cursor/Graticule Editor - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-15
Keyboard/Trackball Accelerator Mapping - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-18
Tracking Sensitivity - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-20
Y Parallax - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-22
Project Data Review - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-23
Stereo Model Manager - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-24
Quality Statistics - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-26
Batch Processing - Quality Statistics - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-32
Image Information - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-35
Flicker Images - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-36
Graphics Projection - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-37
Change Elevation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-38
Correlation Band Selector - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-39
DOQ Editor - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-40
Image Header Update - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-41
Configuration Editor - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61-43
Appendix A Glossary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A-1

Appendix B File Organization- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - B-1
Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - B-1
Appendix C Feature Database and Extraction Specification - - - - - - - - - - C-1

Feature Database - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - C-1
Appendix D Customizing Your Software Configuration - - - - - - - - - - - - - D-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - D-1
Establishing Image Locations - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - D-1
Grid Coordinate Systems - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - D-2
Choosing Text Fonts - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - D-2
Customizing Your User Interface - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - D-4
Tape Drives, CD-ROMS, and Printers - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - D-4
Appendix E Batch Processing - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - E-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - E-1
Stand-Alone Operation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - E-3
Batch Operation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - E-3
Batch Processing on the Windows Platform - - - - - - - - - - - - - - - - - - - - - - - - - - - - - E-14
SOCET SET TOC-11

Table of Contents
Applications - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - E-15
Examples - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - E-16
Appendix F Figures Of Merit - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - F-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - F-1
Appendix G Interpolation and Resampling - - - - - - - - - - - - - - - - - - - - - - G-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - G-1
Appendix H Limitations and Constraints- - - - - - - - - - - - - - - - - - - - - - - - H-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - H-1
Windows Platform Specific - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - H-6
Appendix I Internationalization - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I-1
Appendix J Accelerator Key Commands - - - - - - - - - - - - - - - - - - - - - - - - J-1

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - J-1
INDEX - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Index-1
The Basics- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-1
Advanced Procedures - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-1
Sketch Hotkeys - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-3
TOC-12 SOCET SET

Chapter 1
Workstation Operating Instructions

Workstation Operating Instructions introduces start-up and
shut-down procedures of the software, and user’s interface
with the workstation.
1.1 Overview
The workstation operating instructions cover the start-up and shut-down procedure for
SOCET SET. The interface with the workstation is through a GUI where you will be controlling
either a M o u s e C u r s o r or an E x t r a c t i o n C u r s o r . Various mouses are available, and are
explained more thoroughly in the System Administration Manual in the Hardware Reference
chapter.
1.1.1 System Administration

The system administrator plays a key role in the successful operation of SOCET SET. The system
administrator manages user access, brings up and shuts down the system, diagnoses system
problems, maintains system configuration and trouble reports, and ensures the system is available
to support users. A working knowledge of the operating system is helpful, but not required. The
documents listed in the Workstation Description chapter provide sufficient detail to perform
system administration and maintenance.
See the Windows and Solaris System Administration Manuals

for more information.
1.1.2 Workstation Power-Up

The startup sequence begins with powering on all the monitors and peripheral devices. Apply
power to the computer last. The computer should boot itself upon power-up. Booting takes a few
minutes and you will see some messages displayed on the screen during this time. If you do not
see bootup messages on the monitor, check the monitor brightness and make sure it is high
enough to see the messages on the screen. If there are no messages, the computer did not boot and
you should try to boot manually. When the system has completed booting, the operating system
displays the login prompt.
SOCET SET Page 1-1

Chapter 1 - Workstation Operating Instructions
Booting is relatively risky and should be performed only by the

system administrator. Booting is required only upon system
power-on or when the system is irrecoverably hung.
After the boot completes, you can log in and perform your image exploitation tasks. When you
have finished, you should exit the program and log off. Do not power off the computer when you
have finished your task.
To maintain system integrity, it is recommended that the

system remain powered up at all times.
1.1.3 Starting the Software

At the Login: prompt, perform these steps:
1. Enter your login name (as provided by the system administrator).
2. Enter your password (as provided by the system administrator). The system then starts a
windowing system.
3. On a Windows workstation, double-click on the SOCET SET application icon.
4. On a UNIX workstation, move the mouse cursor to the background area of the screen. Press
the LMB and hold it down. Drag the mouse cursor down to the SOCET SET selection and
release the LMB.
A large window appears on the screen. This is the SOCET SET application software.
5. Select a project and proceed as described. See “Workflow,” Chapter 3.
1.1.4 Exiting the Software

Exit SOCET SET as follows:
1. Exit SOCET SET by clicking File > Exit on the main workstation window.
2. Confirm your exit by clicking EXIT with the LMB (Left Mouse Button). The large
application window disappears and the systems returns to the windows environment.
1.1.5 Unresponsive Workstation

During operation you may encounter a situation where the computer seems to be unresponsive.
When in this situation, try the following steps:
1. Contact your system administrator.
2. If you just initiated a lengthy process, such as an Image Enhancement, wait a minute or two
for the process to complete.
3. Look at the status messages in the application windows. Are there any messages explaining
why the system is unresponsive? On a UNIX workstation look in the system console
window. This is the Unix xterm window usually located behind the application windows.
Does the console window contain messages indicating the cause of the problem?
4. Attempt to locate your mouse cursor by moving the mouse. If you cannot see it, try toggling
the cursor by pressing F3 on the keyboard or the MMB.
5. If you found the mouse cursor, try to exit the application by clicking File > Exit.
Page 1-2 SOCET SET

6. If Exit does not work and you are on a UNIX workstation, select Kill SOCET SET from the
workstation desktop root menu.
7. On the Windows system, press <Ctrl>+<Alt>+Delete to popup the Windows Security
window. Click Task Manager to popup the Task Manager. Use this utility to kill the
application. You may need to log into another workstation to find where the S/W is hung.
8. If you are on a UNIX workstation and cannot find your mouse cursor, log into another
computer on your network and kill the application using the UNIX kill(1) command.
9. If you do not have other computers on the network, reboot the computer.
10. If the reboot is unsuccessful, power down the computer as described in the Power Down
section below, then apply power to the workstation as described above.
1.1.6 Workstation Power-Down
The workstation should only be powered-down by the System

Administrator.
1.2 Operator’s Interface
See the SOCET SET System Administration Manuals for

detailed information regarding the keyboard, pointing devices,
and configuration.
1.2.1 Cursors
The software uses two cursors: the M o u s e C u r s o r and the E x t r a c t i o n C u r s o r .
Mouse Cursor Extraction/Graticule Cursors

The mouse cursor is the standard cursor for interacting with the windowing system. You use the
mouse cursor to interact with the application windows, menus, and buttons. The workstation
mouse controls the movement of the mouse cursor.
1.2.1.1 X, Y, Z Directions
Since SOCET SET operates in three-dimensional ground space, it makes use of a separate
extraction cursor to make three-dimensional measurements and to delineate three-dimensional
graphical features. The workstation mouse controls the movement of the extraction cursor in the
X and Y directions; the T r a c k b a l l controls the movement of the extraction cursor in the Z
direction. A 3D mouse or TopoMouse controls all three directional movements. See “Change
Elevation” on page 61-38 for Z direction, if the workstation only has a three-button mouse and
no trackball.
1.2.1.2 Moving the Extraction Cursor

The extraction cursor represents a single point in ground space. SOCET SET draws the extraction
cursor in its correct geographic location in all the images currently displayed. You must move the
extraction cursor to perform many SOCET SET operations, such as Feature Extraction,
Triangulation, and Interactive Terrain Editing.
SOCET SET Page 1-3

You can customize the speed of cursor movement by adjusting the sensitivity of the mouse or
trackball. You can also select whether you want the extraction cursor to move in a plane parallel
to the ground or parallel to your view plane. By default, the mouse will move the XY location of
the extraction cursor, and the trackball (if you have one) will move the Z location. These settings
and their sensitivities are programmable. See “Tracking Sensitivity” on page 61-20 for more
details.
If you are using the extraction cursor to measure points in the imagery (such as control points,
fiducials, or feature vertices), you may want to make high-accuracy measurements. In this case,
you should display the 1:1 image and zoom it by a factor of two or more. See “Rotation/Zoom”
on page 4-18 for details on the operation.
Alternatively, you can also use two trackballs: one for XY and one for Z. If you use two
trackballs, the mouse is not involved with extraction cursor movement and toggling is not
required.
1.2.1.3 Two-handed Controller

Using two devices to move the extraction cursor (one for XY and one for Z) is called “two-handed
movement.” You can also use a “two-handed controller” that includes X,Y, and Z controls. Such
devices are sometimes called a “3 D M o u s e .” If you use such a controller, then the computer
mouse is not involved with extraction cursor movement and no toggling is required. For
information about the 3D mouse, see the System Administration Manual.
For many operations, you need to adjust the Z coordinate of the extraction cursor so that it lies
on the ground. While doing this, you should be viewing the 1:1 imagery on the stereo monitor. If
your computer does not have a stereo monitor, you can view the imagery in split screen mode.
1.2.1.4 Grounding the Extraction Cursor

To put the extraction cursor on the ground, you can: (a) move the cursor manually with the
trackball; (b) use the Snap-To-Ground function (press the right trackball button and the computer
will automatically put the cursor on the ground, provided you have positioned it approximately);
or (c) provide a terrain data file and instruct the software to have the extraction cursor “hug” or
“track” the DTM. See “Terrain Tracking” on page 61-4 for more details.
1.2.1.5 Customizing the Extraction Cursor

You can customize the size, shape, and color of the extraction cursor. By default, the extraction
cursor is a green crosshair.
1.2.1.6 Toggling the Cursor

In the default configuration, the mouse controls both the extraction cursor and the mouse cursor,
but only one at a time. The action of switching the mouse control from one cursor to the other is
called “toggling the cursor.” Toggling is accomplished by pressing either the F3 key on the
keyboard or the middle trackball button. Here is a typical sequence of steps:
1. Upon startup, the mouse is toggled to the mouse cursor. You perform some actions in the
application windows, such as starting applications and doing data entry.
2. At some point, you will need to position the extraction cursor; for example, to locate
Ground Control Points (GCPs) or to delineate features, so you toggle the cursor with the
middle trackball button or the F3 key. The mouse cursor will disappear and you then use
the mouse to position the extraction cursor on the desired spot of the imagery.
Page 1-4 SOCET SET

3. Next you will then need to perform some actions in the application windows, such as
pressing a button. Press the middle trackball button and the mouse cursor will reappear. The
mouse then moves the mouse cursor.
Some people prefer to avoid toggling by using a two-handed controller instead of a trackball, or
you can attach two trackballs to your computer—one for XY and one for Z.
1.2.1.7 Zoom Toggle

You use the Zoom Toggle function to jump back and forth between two minification/zoom levels.
Normally you change the minification of the displayed image by using the zoom button on the
Display Utility window. However, if you are jumping back and forth between two zoom levels,
you can use the F6 hot-key or the “DB3” button on the 3D mouse. When new images are loaded,
the two minification/zoom levels selected for the previous images are retained. F6 on the
keyboard toggles between the last two selected zoom levels.
1.2.1.8 Recenter the Cursor

If you lose track of the extraction cursor, you may press the Home key to return the cursor back
to the center of the image display.
For topics such as Keyboard/Trackball Accelerator Mapping,

Tracking Sensitivity, and the Configuration Editor see the
Utilities chapter.
1.2.2 Selecting Files By Footprint

In addition to prompting you to pick file names from the list in the File Selection window, certain
applications will also draw rectangles representing the footprints (in ground space) of the files in
the workstation monitor imagery window.
When you use the mouse cursor to select the name of a file, the corresponding footprint is
highlighted in the imagery window. Conversely, you can use the extraction cursor to pick
rectangles in the imagery window. When you pick a footprint in this manner, the corresponding
file name is highlighted in the Files list.
If you encounter difficulty in picking a footprint with the extraction cursor, try adjusting the
elevation of extraction cursor so that it is at the same height as the footprint.
When you are finished selecting files, click OK in the File Selection window to return to the
previous window. This erases the footprint rectangles from the imagery display.
SOCET SET Page 1-5

Chapter 2
Workstation Description
Workstation Description explains the purpose, components,
and software description.
2.1 Workstation Purpose

The purpose of the Softcopy Exploitation Tool (SOCET SET®) software is to support image-
based softcopy applications such as map-making, mission rehearsal, and photo-interpretation.
SOCET SETgenerates databases and products such as Digital Terrain Models (DTM), reports,
vector databases, orthophotos, image maps, and image mosaics. SOCET SET supports a wide
variety of applications, including:
• Populating a GIS database (vector or raster)
• Producing image maps
• Civil engineering
• Mission planning
• Targeting
• Mission rehearsal
• Sensor research and development
The SOCET SET software consists of over sixty application functions that can be chained
together to form a processing flow that inputs imagery, performs the requisite analysis, and
produces the final hardcopy or softcopy products. This User’s Manual describes the application
functions in detail, including the following:
• Data import capabilities for imagery, feature, and terrain data
• Automatic extraction of Digital Terrain Model (DTM) elevation data
• Interactive graphical editing of DTM data
• Interactive two and three-dimensional feature data extraction
• Orthophoto generation
• Perspective scene generation
• Point positioning, three-dimensional mensuration, and targeting
• Image mosaicking
SOCET SET Page 2-1

Chapter 2 - Workstation Description
• Image enhancement
• Data export functions for softcopy databases (imagery, feature, and terrain data),
and hardcopy products (image maps)
2.1.1 Typical System Product Flow

Imagery is input to SOCET SET from either a digital softcopy source, such as SPOT or Landsat,
or by scanning film-based imagery. The workstation products are in either softcopy format (such
as DTMs, vector databases, orthophotos, etc.) or hardcopy format (such as image maps or photo-
realistic perspective scenes).
AERIAL SATELLITE IMAGERY

PHOTOGRAPHY (SPOT, LANDSAT,
(FILM-BASED) QuickBird, IKONOS, etc.)
Orthophoto Generation
IMAGE SCANNER Image Mosaicking
Report Generation
Annotation
Image Maps
Perspective Scenes
Geopositioning
SOCET SET Terrain Extraction
SOFTWARE Feature Extraction
Enhancement
SOFTCOPY
PRODUCTS
HARDCOPY Feature Databases
PLOTTER Enhanced Images
Orthophotos
Mosaicked Images
Perspective Scenes
PRODUCTS Image Maps
Terrain (DTM)
Grid or TIN
GIS
Simulations
Mission Rehearsal
OTHER SYSTEMS Perspective Scenes
OR APPLICATIONS Photo Interpretation
Industrial Mensuration
Page 2-2 SOCET SET

2.2 Other Documentation

This document is the SOCET SET User’s Manual. It contains detailed operating descriptions of
all workstation applications. In addition to this manual, the following documents are also
available:
DOCUMENT DESCRIPTION
SOCET SET Programmer’s Describes the SOCET SET Developers Kit, including the SOCET SET
Manual Application Programming Interface (API), Graphical User Interface
(electronic only) (GUI), and libraries. Available with purchase of DevKit in HTML.
SOCET SET System Instructions for configuring your Operating System and Network for
Administrator’s Manual SOCET SET. Available for UNIX or Windows’ operating systems.
(electronic only)
Release Notes Release Notes are organized into three sections: New Features, Open
(Platform specific) Issues and Tips, and Revision Notes. The notes in New Features are
(electronic only) identified by functionality; while, notes in Open Issues and Tips sections
are identified by the main window pulldown menu selection that activates
the affected function.
SOCET SET Training A step-by-step tutorial for common SOCET SET applications arranged in
Manuals an easy-to-read viewgraph format, with lab exercises designed to
familiarize you with operating SOCET SET. Available through a formal
training class.
On-line HELP This provides application driven help via your browser.
2.2.1 Typographic Conventions
The screen captures in this manual were taken on a Windows

Machine. The screen appearance may be different on a UNIX
machine.
Directory names in this manual are written using the Unix convention with slashes, such as
/a/b/c. When working on the Windows platform, the directory names actually contain backslashes
and are always prefaced by a disk name, such as d:\a\b\c.
2.3 Workstation Components

The SOCET SET Workstation consists of the following components:
• General purpose computer workstation, including color display, keyboard, and mouse
• The computer workstation operating system and support software
• Peripheral devices (tape drives, CD-ROM drives, disk drives)
• SOCET SETApplication software & technical documentation
• Stereo image board and extraction monitor (optional)
• 3D Mouse or trackball for floating mark control (optional)
SOCET SET Page 2-3

Major component characteristics of the workstation are described in the following paragraphs.
Network Tape
Drive
Disk Drive Console
Monitor
General Purpose CPU

Scanner or Mouse
Digitizer Keyboard
Trackball
Plotter or Image Processor

Printer Stereo
(Drives the
Extraction
Extraction Monitor)
Monitor
The Stereo Subsystem is Optional
SOCET SET Workstation
2.3.1 Stereo Extraction Monitor

Stereo digital imagery is viewed on the workstation using stereoscopic color display with a liquid
crystal polarizing shutter and glasses, or with synchronized glasses and the E x t r a c t i o n
M o n i t o r . The screen-sized liquid crystal modulator provides different polarization for the left
and right eye images. Special polarizing glasses decode the polarized images to provide the left
and right eye views. The liquid crystal modulator is synchronized with the graphics processor so
that it changes polarization at the same frequency as the two images are displayed on the screen.
When using synchronized glasses, an emitter is attached to the monitor to control the glasses.
2.3.2 Operator Controls

In addition to the keyboard and C o n s o l e M o n i t o r , the workstation provides a three-button
mouse and a trackball for interactive control of the workstation. The mouse controls the
horizontal (XY) movement of the cursor in the image display. It also provides an interface to the
application menus displayed on the console monitor. The trackball provides a separate control for
elevation (Z), independent of the horizontal movement of the mouse. You can configure the
behavior of the mouse and trackball according to your preference. Additional devices are also
available, and can be found in the System Administration Manual for your platform.
2.3.3 Operating Environment

Refer to the Hardware Reference Chapter of the System Administration Manual for additional
information.
Page 2-4 SOCET SET

2.4 Software Description

The workstation software includes the UNIX® or Windows operating system, window
management software, device drivers, and the SOCET SET software suites.
The multi-user, multi-tasking capability of the workstation allows multiple users to share the
system facilities and perform multiple tasks concurrently. The operating system includes many
utilities, such as text editors, calculators, and sorting tools. You may also purchase additional
software packages, such as spreadsheets and word processors.
Every peripheral device and image processing board requires a device driver. The drivers are
generally installed at the same time that the peripheral is attached.
The SOCET SET Developer’s Kit is available as a separate option. This kit enables you to write
software that interacts with SOCET SET and to access the data files.
Some of the major capabilities of SOCET SET include the ability to:
• Import data (imagery, features, terrain, ground points).
• Prepare imagery for extraction (interior orientation, triangulation, rectification).
• Display images and perform various image enhancement operations.
• Extract terrain and feature data from the imagery.
• Create products such as orthophotos, photorealistic perspective scenes, and image
mosaics.
• Export softcopy databases and hardcopy products.
See “Job Queue Manager” on page 3-3 for a detailed description of the workstation
functionality.
2.4.1 Image Management

SOCET SET imports 24, 16, 8 and 4-bit imagery.
Both the console and extraction monitors display 24-bit color. (SOCET SET can display 8-bit
color for hardware that does not support 24-bit color.)
Images can be stored in a variety of formats: TIFF, NITF, VITec, and others. The storage methods
increase the speed of the roaming and zooming operations.
Up to sixty separate images can be viewed simultaneously; up to 30 views can be displayed, and
each view can contain two images when in the split screen mode. The images need not be of the
same sensor type, and each of the sixty can be windowed and adjusted independently.
The workstation provides three modes for image viewing:
• Stereo mode (3D)
• Single image mode (monoscopic)
• Split-screen mode in which a pair of images are displayed side by side
Image windowing is performed by recentering and zooming operations. Image quality can be
adjusted by brightness and contrast slider bars, or by more flexible graphical editors that enable
the operator to directly sketch the tonal transfer curve or histogram.
SOCET SET Page 2-5

2.4.2 Sensor Models

A sensor model is a function that transforms from three-dimensional ground space into image line
and sample space. The input to the function is a ground point (latitude, longitude, elevation) and
the output is an image point (line, sample). Every sensor type (SPOT, frame, Landsat, etc.) has a
unique sensor model formula that reflects the physical characteristics of the sensor (optics, focal
length, scan mechanisms, and so forth). Every image has unique sensor model parameters that
reflect the location and orientation of the sensor at the time the image was collected.
The workstation supports many sensor models including: SPOT, Landsat, frame, panoramic, and
military sensors.
Three-dimensional cursor movement is controlled by a combination of mouse (XY) and trackball
(Z). Additional devices available include, Handwheels, Footdisk, Foot Switches, 3D Mouse and
others. Refer to the System Administration Manual for further information.
The sensor models used by SOCET SET are rigorous, meaning that the functions are exact
projective computations, rather than approximations (such as, polynomials or rational
polynomials). Approximate sensor models provide performance improvements for many
workstation operations, but degrade both relative accuracy and absolute accuracy. Generally,
accuracy degradation is minimal for low-oblique imagery, but can be severe for high-oblique
imagery. Performance improvement due to approximations, ranges from negligible to 100 times;
accuracy degradation ranges from negligible to 10 times.
2.4.2.1 Frame - Advanced Sensor Model

The Frame - Advanced sensor model replaces in its entirety the existing Frame sensor model. The
process of importing images for the new Frame - Advanced sensor model is exactly the same as
that for the previous Frame sensor model without any changes, including the use of the “Frame”
import button. All the previous import file formats for Frame sensor model are still supported
except the “SOCET SET GPS file” format which was substantially modified.
Sensor modeling is data driven. The data used in this new Frame - Advanced sensor model are as
follows:
1. Ground coordinates – This model accepts all ground coordinate types supported by SOCET
SET.
2. GPS antenna coordinate – The convention for ground coordinates apply. The previous
assumption in the Frame sensor model is that this is the same as the ground coordinates of
the camera lens center. This implies that the GPS antenna offset is zero.
3. Exterior orientation angles – These are the 3 rotation angles that aligns the ground
coordinate system with the IMU coordinate system. The chosen convention is ground-to-
image in the sequence of w, p, and k rotations in radians. It is assumed that the angles are
always referred to the reference coordinate system defined in the support file (note: very
important change). The previous Frame sensor model convention assumes that the angles
are always referred to the geographic coordinate system.
4. GPS antennae offset – This is the delta between the GPS antennae coordinates and the
camera lens center coordinates. This delta is usually measured based on the camera
coordinate system and is constant for all images taken with the same hardware.
5. Bore-sight angles – These are the 3 rotation angles that aligns the IMU coordinate system
with the camera coordinate system. This is the same for all images taken with the same
hardware. For un-calibrated systems, these small values are unknowns and are assumed to
have zero observed values. Conventions for the exterior orientation angles apply.
Page 2-6 SOCET SET

6. Principal point of symmetry – This is the origin of the images coordinates used in lens
distortion modeling. The location is in the fiducial (calibrated) coordinate system. The units
are in mm. For un-calibrated cameras, these are assumed to be zeros.
7. Principal point of auto-collimation – This is the origin of the image coordinates in the
collinearity equations. These values are subtracted from the measured image coordinates
prior to use in the collinearity equations. The conventions for the principal point of
symmetry apply.
8. Lens distortion – The lens distortion flag has 3 options: 0 = do not apply, 1 = distortion error
(default), and 2 = distortion correction. For option 1, the computed distortion error is added
to the ideal image coordinates. This option follows the same convention as the old Frame
sensor model. This usually applies if a table of distortion values is given. For option 2, the
computed distortion correction is added to the measured image coordinates. This last option
uses the K and P values directly defined in the Manual of Photogrammetry (the same as the
Australias convention and is also used by USGS). Both options use the measured (not
corrected) image coordinates in mm as argument in the distortion model. For digital
images, the image pixel coordinates are first converted to mm using pixel sizes.
9. Camera principal distance (focal length) – The units are in mm.
10. Bilinear transform coefficients to convert mm to pixel image coordinates – For digital
cameras, derived from pixel sizes in line and sample direction. For film cameras, derived
from calibrated fiducial coordinates.
See “Frame - Advanced” on page 25-25, and See “Frame - Advanced (modified)” on page 26-19.
2.4.3 Accuracy
The statistical error of the position of a ground point, stated in ground coordinates.
Absolute accuracy is the error with respect to ground truth (lat/long/elev).
Relative accuracy is the error with respect to another ground point (the error in the offset or
distance between the points).
High accuracy is a key aspect of every workstation product, including terrain files, feature files,
and orthophotos. Some sources of inaccuracy include:
• Improperly calibrated camera
• Atmospheric refraction
• Film shrinkage between exposure and scanning
• Imperfections or distortions in the scanner mechanism or optics
• Inaccuracies in ground control data
• Imperfect positioning of the cursor over control points
• Operator error
• Sensor model algorithm approximations
• Poor image correlation in certain areas by the automatic terrain extraction process
• Floating mark bias of the user during stereo visualization
• Imperfections or distortions in the hardcopy plotter device
The accuracy of the workstation output products (geopositions, orthophotos, perspective scenes,
terrain data, feature data, etc.) is measured in ground space. Two kinds of accuracy that are
measured— relative and absolute.
• Relative accuracy measures the accuracy of distances between objects.
SOCET SET Page 2-7

• Absolute accuracy measures the accuracy of locations relative to ground truth.

The accuracy of a workstation product is primarily a function of two factors:
• The resolution of the input imagery measured in meters per pixel.
• The precision of the control points used during triangulation.
The relative accuracy of a product is determined primarily by the image ground sample distance.
The absolute accuracy is determined primarily by the control data. Assuming perfect control data,
products generated after triangulation generally have relative accuracy of 0.5 times to 2.0 times
the ground sample distance, horizontal absolute accuracy of 1.0 times to 3.0 times the ground
sample distance, and vertical absolute accuracy of 0.4 times to 2.0 times the ground sample
distance.
Additional inaccuracies can be found in film-based imagery due to the variance in the quality of
scanners and lack of film flatness during the scanning operation in some types of scanners. To
obtain the best results, you should use a high-quality photogrammetric scanner.
Ground sample distance varies widely in a high-oblique image, and in these cases inaccuracies
will be proportionally larger in the look direction away from nadir. For example, consider a
situation where the workstation is provided with 10-meter SPOT imagery. The sensor model
supplied by SPOT typically contains parameters that are only approximately correct. Products
generated with this raw sensor model will have relative accuracies in the range of 5 to 20 meters,
and absolute accuracies of about 300 to 600 meters. These accuracies can be improved by
utilizing the workstation triangulation process. Triangulation uses operator-supplied control
points to improve the sensor model parameters. Control points are identifiable landmarks in the
imagery with known geolocations (latitude, longitude, and elevation above sea level). After the
operator supplies a minimum number of control points, the SPOT sensor model parameters are
updated to more accurate values. Products generated using this updated sensor model will have
absolute accuracies of 10 to 30 meters horizontal, and 4 to 20 meters vertical.
2.4.4 Coordinate Systems and Datums

The workstation products can be stored in any of the following coordinate systems: Geographic
(latitude and longitude), Universal Transverse Mercator (UTM), Local Space Rectangular (LSR),
or Grid / State Plane. Over 90 datums are supported. See “Coordinate Systems” on page 5-6 for
more details.
2.4.5 Stereo Imagery

Stereo image pairs enable the workstation to perform many functions that would be impossible
with only a single image, such as automatic terrain extraction, three-dimensional geopositioning,
three-dimensional feature delineation, and terrain editing. However, all other workstation
functions will operate on a single image, including image enhancement, triangulation, two-
dimensional feature extraction, rectification, orthophoto, and mosaicking. Geopositioning and
feature extraction can be performed in three dimensions on a single image, but you will not be
able to resolve the Z coordinate with certainty. In other words, you must select an arbitrary Z
coordinate to use when delineating. You can obtain elevations from a contour map, if one is
available.
The stereo extraction monitor facilitates three-dimensional terrain editing, feature delineation,
and geopositioning. If you do not have a stereo extraction monitor, you can still perform these
tasks, but you must use the split-screen mode on the console monitor to visualize the left and right
Page 2-8 SOCET SET

images simultaneously. Split-screen mode, although sufficient, is not as user-friendly as a stereo

display. All workstation functions, including automatic terrain extraction, will execute without
the E x t r a c t i o n M o n i t o r . A stereo scope for the split screen display is available as an option.
SOCET SET Page 2-9

Chapter 3
Workflow
Workflow is a sequence of applications, and covers a
management tool that tracks the progress of the project’s
work-flow.
3.1 Overview
SOCET SET consists of over sixty application programs invoked from the main workstation
window. Think of the SOCET SET applications as a collection of tools that can be run in various
sequences to generate output products. There is no single best or right process workflow; you
must choose a workflow that best suits your needs. You will find sample workflows in the
following sections.
Once you determine the best sequence of operations for your production workflow, you may use
the Job Queue Manager. This tool allows you to customize your own sequence of operations, and
keeps a record of task in the workflow as completed.
3.2 Customizing Your Workflow
3.2.1 Sample Workflow Diagram

The figure below illustrates a generic workflow sequence. This workflow is not intended to
represent a real process, but rather it illustrates the typical sequence in which steps are performed.
Not all steps or processes are represented. Each workflow name is followed by a letter which
identifies the workflow associated with the given step. For example, Import Imagery (B) means
that workflow B describes this step in detail.
SOCET SET Page 3-1

Chapter 3 - Workflow
Gather Data & Create Project (A)
Import Imagery (B)
Interior Orientation (D) Annotation & Photo

Interpretation (C)
Triangulation (D,F)
Geo-Positioning (G,E)
Image Sharpening
Change Detection
DTM Creation (H)
Building a MC&G
Product (T)
Automatic Terrain
Extraction (I) Feature Extraction (L,E)
Merge (J) Data Export
Interactive Terrain Editing (I,K)

Terrain Analysis
Data Export Othophoto Generation (M)

Perspective Scene
Terrain Visualization Generation (R)
Openflight (S)
Image Map Production (P)
Wrapping-Up a
Project (U)
SOCET SET Workflow Diagram

Detailed workflow instructions are indicated by letters (A-U)
Page 3-2 SOCET SET

3.3 Job Queue Manager

This section summarizes the SOCET SET Job Queue Manager module. This module lets the user
invoke specific SOCET SET applications in a specific order. It also lets the user work through a
list of features that need attention and drives the extraction cursor to the vicinity of those
features—usually this list would have been generated by a SOCET SET application. Furthermore,
the Job Queue Manager allows generic items which simply tell the user to do something that does
not necessarily have anything to do with SOCET SET. Finally, the user can create queue
“template” files which the software can use to generate a specific list of items to be worked
through. See “Creating a Job Queue Template” on page 3-5 for details.
The figure below illustrates the Job Queue Manager’s user interface with a sample job queue
loaded.
The Job Queue Manger window’s selections are as follows:
MENU CHOICES DESCRIPTION
File > Project Selecting a project to work in while in the stand-alone mode. Desensitized
if Job Queue is invoked while SOCET SET is running.
File > New… Lets you instantiate a new job queue based upon a template that the user
may choose from a list.
File > Open... Loads a job queue.
File > Save Saves the currently loaded job queue under the current name.
File > Save As… Saves the currently loaded job queue under a new name supplied by the
user, or the user may overwrite another job queue selected from a list.
File > Exit Exits the Job Queue Manager.
Options > Edit Options Invokes the Edit Options window described below.
Help > Contents... Starts the on-line documentation.
SOCET SET Page 3-3

SELECT TO
Queue (Un-editable) Displays Loaded Job Queue.
Name Display application title. Right-clicking on the Name column will invoke a
menu pop-up with one item: Delete. Selecting this item will remove the
item from the queue.
ID Display the ID of the queue item.
Status Display the completion status of the queue item—X means complete and a
blank cell means incomplete. Right-clicking on the Status dialog will
invoke a menu pop-up with two items: Finished and Not Finished.
Selecting one of these sets the completion status of that item accordingly.
If a cell has been marked as Finished, the Completed By column will be
updated with the user’s operating system user name, and the Completion
Date column will be updated with the current date. If the cell has been
marked as Not Finished, both columns will be marked with N/A.
Completed By Display the name of the user who marked the item as complete; N/A if not
complete.
Completion Date Display the date on which the item was marked as complete; N/A if not
complete.
Move to Location Drives the extraction cursor to the vicinity of the selected feature. LL for
Lower-Left, UR for Upper-Right.(This button is only sensitized when a
geographic task is selected from the queue.)
Handle Task Invoke the appropriate SOCET SET task. (This button is only sensitized
when a SOCET SET task is selected from the queue.)
Left-clicking on the row of the table will populate the two areas below the table. The left area
displays the coordinates of the MBR of the feature if the user has selected a feature queue item.
If any other type of item has been selected, the MBR area is greyed-out. The right area displays
any user-entered comments relating to the item, and the user may type comments into this area.
If a generic task has been selected, a description of the task will also be displayed in the comments
area. You can right click in the “Name” cell of a task to Delete it. You can also right-click in the
“Status” cell of a task to set it to “Finished/Not Finished”.
Left-clicking on the Name or ID column header will sort the table alternately in ascending/
descending order on that column.
If you have selected the “Auto Handle” option, then one of three things will happen when you
select a row. If you select a feature, then the extraction cursor will be driven to the vicinity of the
selected feature. If you select a SOCET SET task, then the appropriate SOCET SET application
will be invoked. Finally, if you select a generic task, the task to be done will simply be displayed
in the comments area.
If a generic task is selected, or if the software is running in

stand-alone mode (and thus unable to interact with
SOCET SET), then “Move to Location” and “Handle Task” will
be desensitized.
Page 3-4 SOCET SET

3.3.1 Edit Options Window

This window pops up when the user selects Edit Options from the Options menu. The table below
describes the functionality.
The Edit Options window’s selections are as follows:
SELECT TO
Display Time Display the time of day in the queue table’s date column.
Display Weekday Display the Weekday in the queue table’s date column.
Auto Handle Cause the extraction cursor to move to the vicinity of a feature or load the
appropriate SOCET SET application whenever an item is selected from the
table.
Disable Delete Dialog Disable the confirmation dialog which pops up when the user deletes a
queue item.
OK Apply the user’s selections and closes the window.
Apply Apply the user’s selections without dismissing the window.
Cancel Dismiss the window without applying the user’s selections.
3.3.2 Creating a Job Queue Template

Job Queue templates are files which the software uses to create (or instantiate) new job queues,
and are ASCII files which are easily created with text editors. The files consist of a one-line
validation code followed by a series of blocks of information. Each block represents an item in
the queue that is to be instantiated from the template, and specifies the type and information about
the block.
Example templates are provided in the internal_dbs/

WORKFLOW directory.
3.3.2.1 Template File Format

What follows is the specific format of the template file and the blocks of information. Text in the
Courier font represents the contents of the file, verbatim, while <text> is a place holder for user-
entered information. Pipes ( | ) are used to delineate fields within a line of the file, and at the end
SOCET SET Page 3-5

of each line. Single-line comments in the queue file are allowed, and must start with #. Carriage
returns are allowed in between fields (that is, between the | and the beginning of the next field).
First line of the file—validation code which the job queue software needs in order to trust that
this is the right kind of file:
Job Queue Template File Version1.0
Second line of the file—name of the user who last modified the queue, or N/A.
(The rest of the file consists of information blocks which represent queue items.)
The following describes the block for a feature type queue item (In all likelihood, the user would
have no use to put a feature item in a queue template, but the facility is there anyway):
GeographicTask|<Name of the item>|<ID of the item>|
<MBR LL Y/Lat>|<MBR LL X/Long>|<MBR LL Z/Elevation>|
<MBR UR Y/Lat>|<MBR UR X/Long>|<MBR UR Z/Elevation>|

The following describes the block for a SOCET SET task type queue item:
SocetSetTask|<Name of the item>|<ID of the item>|...

String which invokes the appropriate SOCET SET Module |
The following describes the block for a generic task type queue item:
GenericTask|<Name of the item>|<ID of the item>|<String

which tells the user what to do>|
3.3.2.2 Template File Example:

What follows is an example of a job queue template file and the results of instantiating the file in
the job queue software.
• This is a job queue template file example to show the correct format.
JobQueueTemplateFile version1.0
• The next line shows the format for a geographic item:
GeographicTask|Sears Tower|conv_0|
1997622.97|6319063.06|723.97|
1997762.51|6319104.33|723.97|
• The next line shows the format for a SOCET SET item:
SocetSetTask|Automatic Terrain
Extraction|socetTask_0|$(EXEDIR)/ate|
• The next line shows the format for a generic item:
GenericTask|Report|genTask_1|Call your boss.|
Page 3-6 SOCET SET

3.3.2.3 Execution - Job Queue

1. Select Project.
a. (Stand-Alone only) Click File > Project and select a project from the given list.
b. (Using SOCET SET) Project is provided from SOCET SET.
2. With a project selected, click File > Open and select a queue from the given list.
3. In the display area, the workflow will be viewable. To work through the workflow, refer to
The Job Queue Manger window’s menus, button, and fields for directions.
3.4 Sample Workflows

The following sections describe some typical workflows. Refer to the various chapters indicated
for detailed operational steps.
3.4.1 Workflow A: Gather Data & Create Project

Follow these steps when beginning any task on the workstation:
1. Plan your job. Determine what products you need, what accuracy you want, and what your
timelines are.
2. Gather the input materials. This may include imagery, DTED, maps, ground control data,
collateral data, etc.
3. Ensure you have enough disk space. You may have to archive old data files to tape and
remove them from your disk. See “File Organization,” Appendix B for detailed
information.
4. Decide on your project parameters. You must determine which C o o r d i n a t e S y s t e m (lat/
long, UTM, LSR, or Grid), what units (feet vs. meters), and which datum you will use. See
“Project Management,” Chapter 5 for detailed information.
5. Log in to your workstation and start up SOCET SET.
6. Create a project to contain your data. Specify a coordinate system, datum, and units.
See “Project Management,” Chapter 5 for detailed information.
7. Validate that the project was created by Opening it. Use the File pulldown in the main
workstation window. See “Main Workstation Window - Full Roam,” Chapter 4 for detailed
information. See “Project Management,” Chapter 5 for detailed information.
8. [Optional] If you want to customize the extraction cursor shape or color, click Preferences
> Cursor Editor on the main workstation window.
3.4.2 Workflow B: Importing an Image

Use these steps to quickly import and view a single, uncontrolled image.
1. Create a project as described in Workflow A.
2. Open the project. See “Project Management,” Chapter 5 for detailed information.
At this point, your actions vary depending on the nature of the image. If the image is a simple
image of uncertain origin, use flow B1. If the image is a frame image (with fiducials) use flow
B2. If the image is a satellite image (SPOT, Landsat, etc.) use flow B3.
3.4.2.1 Workflow B1: Import Imagery - simple Images

3. Load the image onto the computer disk. If the image is on tape, talk to your system
administrator for details about how to transfer the file from tape to disk.
SOCET SET Page 3-7

4. Create a support file for the image by using Convert Image Import. During this step, you
may wish to convert the image format to a tiled format, which can be processed faster than
non-tiled formats. See “Data Import and Export,” Chapter 16 for detailed information.
3.4.2.2 Workflow B2: Import Imagery - frame Images with fiducials

5. Get the image onto the computer disk. If the image is on tape, ask to your system
administrator how and where to mount the tape.
6. Create a camera calibration file for this camera. See “Camera Calibration Editor” on
page 61-5 for details.
7. Execute Frame Import. See “Frame and Panoramic,” Chapter 8 to create a support file.
8. Execute Interior Orientation. See “Interior Orientation,” Chapter 24 for details.
3.4.2.3 Workflow B3: Import Imagery - satellite Imagery

9. Mount the media containing the imagery onto the computer.
10. Execute ALOS PRISM, ADS40, EROS B, OrbView-3, GeoEye-1, Quickbird, SPOT, JERS,
FORMOSAT 2, RADARSAT 2, or Landsat Import. See “ALOS PRISM Import” on page 7-
38, See “EROS B Import” on page 7-46, See “FORMOSAT 2 Import” on page 7-35, See
“RADARSAT 2 Import” on page 7-49, See “ADS40 Image Import” on page 13-2, See
“OrbView-3 Image Import” on page 14-2, See “GeoEye-1 Image Import” on page 15-2,
See “QuickBird/WorldView Image Import” on page 7-8, See “SPOT, JERS and IRS
Import,” Chapter 11 for details. See “Landsat Import,” Chapter 10 for details.
11. Validate and adjust the image and support file you have created.
12. Build an image pyramid by executing Minify. If this was automatically done during the
import step, you do not have to repeat it here. See “Image Minification,” Chapter 21 for
details.
13. View the image in the main workstation window by clicking File > Load Images in the
Main Workstation window. See “Main Workstation Window - Full Roam,” Chapter 4 for
details.
14. [Optional] Adjust the extraction cursor movement by selecting Preferences > Tracking
Sensitivity on the main workstation window. See “Tracking Sensitivity” on page 61-20 for
details.
15. [Optional] To save a specific location as the center point whenever you load a particular
image into the main window, you may set its location by selecting File > Save Load Point
on the main workstation window. See “Saving Image Load Point” on page 4-3 for details.
3.4.3 Workflow C: Annotation & Photo Interpretation

Use these steps to generate a photo-interpretation product:
1. Import an image, controlled or uncontrolled, as described in Workflow B.
2. Load the image into the main window.
3. Execute A n n o t a t i o n . See “Annotation,” Chapter 45 for details.
4. Annotate the image by using Annotation in conjunction with Sketch. If desired, you may
save the annotation overlay in a permanent disk file.
5. Create a screen dump file by selecting Output > Screen Dump on the main workstation
window. See “Screen Dumps” on page 52-3 for details.
6. Print the screen dump file. Talk to your system administrator for details. See “Unix
Platform” on page 52-3 for additional details.
3.4.4 Workflow D: Interior Orientation - Triangulating a Single Image
Page 3-8 SOCET SET

These steps will control a single image (tie it to the ground):

1. Import a single image using an image import function (i.e. Frame, SPOT, Landsat, etc.) as
described in Workflow B.
2. If it is a Frame image, execute Interior Orientation. If no fiducials are present, skip this step.
See “Interior Orientation,” Chapter 24 for details.
3. Load the image in the main window. See “Main Workstation Window - Full Roam,”
Chapter 4 for details.
4. Execute Triangulation for the image. See “Multi-Sensor Triangulation - Setup and GPS,”
Chapter 26 for details.
5. Validate the control by either (a) using the Quality Statistics process—described in the
Utilities chapter; or (b) loading the image onto the main workstation window.
6. Execute the Coordinate Measurement process, and move the extraction cursor to ground
control points in the image and review the data in the Coordinate Measurement window.
7. [Optional] If the imagery is from a satellite (SPOT, Landsat, etc) you can create a fast
sensor model that approximates rigorous support data. This will cause all subsequent
operations (e.g. Automatic Terrain Extraction) to run much faster.
See “Fast Sensor Model” on page 7-32 for details.
3.4.5 Workflow E: Single Image Data Extraction

Use these steps to extract data from a single image:
1. Import and control a single image as described in Workflow B or D.
2. [Optional] If a DTED or DEM covering the region exists, import it and create a DTM. See
“Data Import and Export,” Chapter 16 for details.
3. Load the image by clicking File > Load Images in the main workstation window.
4. If you have a DTM as in step 2, turn the Terrain Tracking mode On. See “Terrain
Tracking” on page 61-4 for details. If you do not have a DTM, set the elevation (Z value)
of the extraction cursor to the approximate elevation of the ground in the region you are
extracting.
5. Execute the desired extraction process (Annotation, Feature Extraction, or Coordinate
Measurement) and proceed to extract data in ground space.
3.4.6 Workflow F: Triangulate a Stereo Pair

Use these steps to control a stereo pair of images (the two images are denoted Left and Right):
1. Import the left image as described in Workflow B.
2. Import the right image as described in Workflow B.
3. If the imagery is frame imagery, perform Interior Orientation separately on both images.
See “Interior Orientation,” Chapter 24 for details.
4. [Optional] If ground control points are available, build a Ground Point file (.gpf) for the
project. See “Multi-Sensor Triangulation - Setup and GPS,” Chapter 26 for details.
5. Load the left and right images in the main window. See “Main Workstation Window - Full
Roam,” Chapter 4 for details.
6. Execute Triangulation for the images. Use Setup to create a triangulation file containing the
names of the images. Use Automatic Point Measurement to generate and measure tie points.
Use Interactive Point Measurement to enter and measure ground control point data. If no
ground control points are available, perform a relative orientation. If ground control points
SOCET SET Page 3-9

are available, perform an absolute orientation. See “Multi-Sensor Triangulation - Setup and
GPS,” Chapter 26 for details.
7. Validate the control as described in Workflow D.
8. [Optional] If the Triangulation was successful, rectify the stereo pair by executing Rectify
in the pairwise mode. You can skip this rectification process if you plan on using on-the-
fly rectification for stereo viewing. See “Image Rectification,” Chapter 33 for guidance on
whether or not to skip rectification.
9. [Optional] Validate the rectification triangulation by loading the rectified images and the
original images in the main workstation window and visiting several control points with the
extraction cursor, and then reading the ground point location in the Coordinate
Measurement window.
10. View the controlled stereo image pair on a stereo monitor and remove the Y parallax, if any,
using the Y-Parallax tool. See “Y Parallax” on page 61-22 for details.
11. [Optional] If the imagery is from a satellite (SPOT, Landsat) you can create fast sensor
models that approximate the rigorous support data. This will cause all subsequent
operations (e.g. Automatic Terrain Extraction) to run much faster.
See “Fast Sensor Model” on page 7-32 for details.
3.4.7 Workflow G: Geo-Positioning

Use the following set of steps to perform mensuration and geo-location operations:
1. Import and control a stereo image pair as described in Workflow F.
2. Load the left and right images into the main window.
3. Execute Coordinate Measurement. See “Coordinate Measurement,” Chapter 59 for
details.
4. Move the extraction cursor to the points of interest in the imagery. See “Moving the
Extraction Cursor” on page 1-3 for details on moving the extraction cursor.
5. Use the Coordinate Measurement window to read point locations. Use the Reset button in
the Coordinate Measurement window to measure distances and angles between two points.
See “Execution - Coordinate Measurement” on page 59-4 for details.
To measure the ground space area of a polygon or the length of a linear feature, follow steps 6 to
9 below:
6. Execute the Annotation process. See “Execution - Annotation” on page 45-11 for details.
7. Delineate the area or line with Annotation in conjunction with the Sketch tool. Accept the
area or line by pressing the RMB. See “Sketch,” Chapter 58 for details.
8. Select the area or line with the Pick tool in the Sketch toolbox.
9. Measure the area or length with the Measure tool in the Sketch toolbox. The area or length
will appear in the status window of the Display Utility window.
3.4.8 Workflow H: DTM Creation

Use these steps to create a flat DTM:
1. Import and control two or more overlapping images as described in Workflow F.
2. Create an empty terrain file by executing ATE. Draw the outline (extent) of the DTM and
specify whether the DTM is Grid or Triangular format. Specify the post spacing. Save the
DTM. This DTM in this file is flat. Do not click the Start button in ATE yet. See “Terrain
File Creation,” Chapter 35 for details.
Page 3-10 SOCET SET

3. [Optional] To validate the flat DTM, execute Interactive Terrain Editing. See “Interactive
Terrain Edit,” Chapter 39 for details. Load the DTM you created by clicking File > Load
DTM on the Interactive Terrain Editing window. Use the Draw button to visualize the
DTM. It should be flat at this point.
SOCET SET Page 3-11

3.4.9 Workflow I: Automatic Terrain Extraction

Use these steps to automatically create a DTM (this workflow should not be used if the imagery
is large-scale photography of urban areas):
1. Import and control two or more overlapping images as described in Workflow F.
2. Create a flat DTM as described in Workflow H. Use the Add Images button to list all the
images you will use.
3. [Optional] If you have a feature database containing geomorphic features such as
breaklines, ridges or drains, you can merge the features into the DTM before running
Automatic Terrain Extraction. This will improve the quality of the DTM generated by
Automatic Terrain Extraction. See “DTM/Feature Merge,” Chapter 44 for details.
4. Execute Automatic Terrain Extraction (ATE). Click Start. Wait for the process to
complete. See “Automatic Terrain Extraction,” Chapter 37 for details.
5. [Optional] While Automatic Terrain Extraction is executing, you may use Feature
Extraction to delineate geomorphic features to be merged into the DTM after Automatic
Terrain Extraction completes. See “Workflow J: Merge Features and DTMs” on page 3-12.
Validate the DTM that ATE produces as follows:
6. Load the stereo image pair into the main workstation window. See “Main Workstation
Window - Full Roam,” Chapter 4 for details.
7. Load the DTM into Interactive Terrain Editing by clicking File > Load DTM on the
Interactive Terrain Editing window. See “Interactive Terrain Edit,” Chapter 39 for details.
8. Adjust the DTM graphics display as desired. See “Terrain Graphics,” Chapter 36 for
details.
9. Choose an appropriate graphical mode, such as Editable Contours. Click DTM Setup on the
Interactive Terrain Editing window.
10. Visualize the DTM by clicking Draw on the Interactive Terrain Editing window. Review
the quality of the DTM. At least eighty percent of the DTM should be satisfactory. If the
over-all quality of the DTM is not sufficient, return to step 2 and execute Automatic Terrain
Extraction again, using a different extraction strategy.
11. Use the Interactive Terrain Editing tools to manually touch-up those areas that were not
correctly extracted by Automatic Terrain Extraction. You can use Interactive Terrain
Editing tools to flatten lakes, remove buildings, eliminate hedgerows, extract ridges, etc.
See “Interactive Terrain Edit,” Chapter 39 for details.
12. If the over-all quality of the DTM generated by Automatic Terrain Extraction is acceptable,
use the Interactive Terrain Editing tools to manually touch-up those areas that were not
correctly extracted by Automatic Terrain Extraction. You can use Interactive Terrain
Editing tools to flatten lakes, remove buildings, eliminate hedgerows, extract ridges, etc.
13. If you have ground control points, you can quantitatively measure the accuracy of the DTM
using Quality Statistics. See “Quality Statistics” on page 61-26 for details.
14. Another good way to validate the quality of the DTM is to generate and view a shaded relief
image of the DTM. See “Terrain Analysis,” Chapter 51 for details.
3.4.10 Workflow J: Merge Features and DTMs

These step performs two distinct operations: (a) Merges together two or more DTMs; and (b)
Improves the DTM by forcing it to conform to geomorphic features.
1. Create one or more DTMs as described in Workflow I.
Page 3-12 SOCET SET

2. [Optional] Obtain a feature database containing geomorphic features such as breaklines,

ridges or drains. You can import a feature database from an external source. See “Data
Import and Export,” Chapter 16, or you can extract one yourself as described in Workflow
L.
3. Execute DTM / Feature Merge. If you have more than one DTM, Merge will combine the
input DTMs and will feather the overlap regions so the seamlines are not apparent in the
output DTM. In addition, Merge will modify the DTM so it conforms to the geomorphic
features in the input feature database. See “DTM/Feature Merge,” Chapter 44 for details.
4. Validate the output DTM using Interactive Terrain Edit. See “Interactive Terrain Edit,”
Chapter 39, or See “Workflow I: Automatic Terrain Extraction” on page 3-12 for details.
3.4.11 Workflow K: Terrain Extraction in Urban Areas

Use these steps to automatically create a DTM from large-scale photography of urban areas:
1. Create a flat DTM as described in Workflow H: DTM Creation.
2. Load the stereo image pair into the main workstation window.
3. Execute Interactive Terrain Extraction (ITE). See “Executions Terrain Graphics” on
4. Load the DTM into Interactive Terrain Editing by clicking File > Open on the Interactive
Terrain Editing window.
5. Adjust the DTM graphics display as desired. See “Terrain Graphics,” Chapter 36 for
details.
6. Choose an appropriate graphical mode, such as Dots or Mesh, by clicking Setup on the
Interactive Terrain Editing window.
7. Visualize the DTM by clicking Draw on the Interactive Terrain Editing window.
8. Build up the DTM manually by using any of the Interactive Terrain Editing tools. Use the
extraction cursor and the extraction monitor to determine the correct elevation of the DTM.
Use the Interactive Terrain Editing Area tool to pop-up buildings, if desired. Save the DTM
after you edit it. See “Interactive Terrain Edit,” Chapter 39 for details.
3.4.12 Workflow L: Feature Extraction

Use these steps to extract a feature database:
1. Import and control a stereo image pair as described in Workflow F: Triangulate a Stereo
Pair.
2. [Optional] Extract a DTM as described in Workflow F: Triangulate a Stereo Pair or
Workflow K: Terrain Extraction in Urban Areas.
3. Build an Extraction Specification to guide the feature delineation process. See “Feature
Database and Extraction Specification,” Appendix C for details. You can create the
Extraction Specification using any text editor, such as the Report Editor under the Tools
pulldown. See “Report Editor” on page 61-13.
4. Load a stereo image pair in the main workstation window.
5. Execute Feature Extraction. Delineate features using the various extraction tools as
necessary—volume tool, auto-create, lake tool, peaked-roof, rooftop, domed roof, splining,
etc.
6. [Optional] After delineating each feature, enter the feature’s attribute values, layer, and
name.
7. [Optional] Extracting buildings is much easier if you have a DTM and use the Auto-Create
tool in the DTM mode.
SOCET SET Page 3-13

8. [Optional] When delineating geomorphic features (rivers, roads, etc.) you may wish to turn
on the Terrain Tracking mode, if you have a DTM available.
9. Save the feature database when done.
3.4.13 Workflow M: Orthophoto Generation and Image Mosaicking

Use these steps to create an orthophoto or an image mosaic:
1. Import and control one or more images as described in Workflow B or D.
2. Create and populate a DTM as described in Workflow I or K. Alternatively, import a DTM
from DTED or DEM. See “Data Import and Export” on page 16-1 for details.
3. [Optional] If you want to remove building “lean” build a Feature Database as described in
Workflow L.
4. Review the size and extent of the imagery by loading it in the main workstation window.
5. Review the size and extent of the DTM. See “Interactive Terrain Edit,” Chapter 39 for
details.
6. [Execute this step only for Image Mosaicking] Run the Feature Extraction process, see
Workflow L: Feature Extraction and delineate the boundaries (seam lines) of the input
images and store them in a feature database.
7. Execute Orthophoto or the Image Mosaic process. You can specify one or many input
images. [Optional: If you want the orthophoto to remove building lean, you must input the
Feature Database you created above in step 3].
8. Validate the quality of the output orthophoto or mosaic by loading both the orthophoto and
one of the original images into the main workstation window (in split screen mode) and
executing Coordinate Measurement. Use the extraction cursor to validate the locations of
various points.
3.4.14 Workflow P: Image Map Production

Use these steps to generate an image map:
1. Generate an orthophoto as described in Workflow M: Orthophoto Generation and Image
Mosaicking. Alternatively, extract an orthophoto from a mosaic as described in Workflow
P: Image Map Production.
2. [Optional] Extract a feature database of the region.
3. [Optional] Build a feature database containing DTM contour lines. Use Interactive Terrain
Editing to draw the contours and to convert the DTM to feature database format. See
“Interactive Terrain Edit,” Chapter 39 for details.
4. [Optional] Create a margin template file with Annotation. See “Creating a Margin
Template File” on page 45-12.
5. [Optional] Extract a feature database of the region.
6. [Optional] Build a feature database containing DTM contour lines. Use Interactive Terrain
Editing to draw the contours and to convert the DTM to feature database format.
Alternatively:
7. [Optional] Activate Annotation and draw (a) the margin template; (b) grid lines and tick
marks; and (c) any other graphical overlays you want. Leave Annotation running during
step 6.
Page 3-14 SOCET SET

8. Execute Image Map. Specify all the input files named above. Use the Margin Setup window
to specify the output margin border widths. Click Start and wait for Image Map to
complete.
9. Validate the quality of the Image Map by (a) exiting Annotation; and (b) loading the image
map into the main workstation window. The support file name will be PREVIEW.sup.
10. Print the Image Map file on an image plotter, or export it to another system.
3.4.15 Workflow R: Perspective Scene Generation

Use these steps to generate a perspective scene fly-through:
1. Create and extract a DTM as described in Workflow I: Automatic Terrain Extraction or
Workflow K: Terrain Extraction in Urban Areas.
2. [Optional] Extract a feature database containing the buildings you want modeled in the
Perspective Scene. See Workflow L: Feature Extraction.
3. [Optional] If you extracted a feature database, you may attach image patches to the hidden
building sides as described in Workflow Q.
4. Execute Perspective Scenes. Specify as input the images and DTM. Optionally input a
feature database. Delineate a route for the imaginary viewer. Determine the number of
scenes that will be generated. Generate the scenes. See “Perspective Scene (Multiple
Scene)” on page 50-7 for details.
5. Validate the quality of the scenes by reviewing them with the Animation process.
Alternatively, if you specified that support data be generated during Perspective Scenes,
you can view individual scenes (and perform 3D geo-positioning) in the main workstation
window.
3.4.16 Workflow S: Openflight™

Use these steps to output to Openflight system:
1. Start up OpenFlight Output by clicking Output > Rendering Engines > OpenFlight on the
main workstation window.
2. Click Output File on the OpenFlight Output window. From the file selection box, select or
enter the output path and filename. It is recommended that you select a new directory for
output, as a large number of files may be generated. The File Selection box will create the
new directory.
3. Click DTM on the OpenFlight Output window. The Select DTM window prompts you to
select a DTM. After making your selection, click OK. Selection of a DTM is required for
all output operations.
4. If you wish to select a feature database, click Feature Database. Pick the name of a feature
database and click OK. The selected feature database must have been generated with the
AFX feature extraction specification file.
5. Click Image for DTM... on the OpenFlight Output window. The Select Image File window
prompts you to select an image file to be used for texturing the terrain. After making your
selection, click OK. Typically an orthophoto is used for the terrain. However an orthophoto
is not required. If no image is selected for the terrain, the terrain will have no texture and
will be gray shaded polygons in the OpenFlight format.
6. To select texture image files, click Add. An Image File Selection window appears. You can
pick more than one image file. The Select Image File window prompts you to select the
image files that are used to produce texture image files. All images are used for features.
Use the <ctrl> LMB to select the images in the order required. To remove images files from
the list, select the file, then click Remove.
SOCET SET Page 3-15

7. Click Output Options if you wish to adjust the output parameters: image patch size, level
of detail, image format, and feature & dtm output.
8. Click File > Save to save your selection.
9. Click Start. You will be notified when the OpenFlight Output application has completed.
3.4.17 Workflow T: Building a MC&G Product

These steps are used when you complete a job:
1. Determine the exact products that you need to build. Gather together the data (imagery,
maps, documents) that you will need. Obtain the hardcopy extraction specification from
N G A that defines the product (TLM, JOG-A, VMAP-2, or Foundation Feature Data) you
are building.
2. Create a project. The units must be meters. The coordinate system may be Geographic or
UTM, but not LSR or Grid. Determine which datum and which vertical reference are
needed for your product. See “Creating a Project” on page 5-3 for details.
3. Import imagery and run Triangulation to control it.
4. [Optional] Obtain a DTM by importing DTED or by running ATE.
5. Call SOCET SET customer support and get the password for the MC&G Socket. Decrypt
the MC&G Feature Extraction Specifications as follows:
a. On UNIX, repeat the following crypt command for all files that have suffix
encrypted to create files with spc suffix.
% cd <install_path>/internal_dbs/SPECS
% crypt <password> < ffd_geomorph.encrypted >

ffd_geomorph.spc
where <password> is the name obtained from Customer

Support.
b. On Windows, unzip the files enclosed
in<install_path>\internal_dbs\SPECS\MCG.zip.
6. [Optional] Copy the point icons from the mcg subdirectory up to the ICONS directory.
% cp <install_path>/internal_dbs/ICONS/mcg/*
<install_path>/internal_dbs/ICONS
7. [Optional] Import feature data from Arc/Info by running Shapefile Import.

8. [Optional] If you have a Feature Database that you want to use, but its Extraction
Specification is not one of the MC&G specifications (listed above) use the “Save with New
Spec” button to convert the feature DB to use a MC&G specification. This tool will keep
all attributes that have the same name, but will drop attributes that are not found in the
MC&G specification.
9. Run Feature Extraction and extract features. Use one of the Extraction Specifications that
are listed above. For example, use joga_vmap1oot.spc to build a JOG-A product.
10. [Optional] Use the merge_fdb tool to combine two feature databases into one. The two
feature databases must have identical Extraction Specifications. For example, you could
use this tool after two operators perform extraction in parallel. merge_fdb will copy all
features from the source DB into the destination DB. The command is:
% merge_fdb /<path>/destination.fdb /<path>/source.fdb
Page 3-16 SOCET SET

11. Perform final quality review of the feature DB before converting the DBs to Arc/Info.
Ensure that data extracted by different operators, or extracted over different stereo models,
is properly edge-matched at the seams.
12. Export feature DB to Shapefile.
3.4.18 Workflow U: Wrapping-Up a Project

These steps are used when you complete a job:
1. Review the products you have generated and ensure that you have completed your task.
2. Backup all data you have created in the project. Click File > Backup Entire Project on the
main workstation window. Alternatively, you can backup the files yourself using a Unix
backup tool—talk to your system administrator for details.
See “Backup” on page 6-2 for more details.
3. If you want to re-use the project for another task, remove the unneeded project data files
from your disk. Click Project > Delete and choose one of the various choices. Alternatively,
you can delete the files yourself using the UNIX rm(1) command — talk to your system
administrator for details. See “Execute - Delete” on page 6-8 for more details.
4. If you are finished with the project, remove the entire project from the disk by clicking
File > Delete Entire Project on the main workstation window.
See “Execute - Delete” on page 6-8 for more details.
3.4.19 Workflow V: Making NTM Mosaics

NTM Mosaic production is accomplished in five stages:
• Import the Images and DEMs
• Generate Fast Sensor models for the images
• Merge the DEMs
• Edit the DEMs if required (this is the most involved stage)
• Generate a mosaic
3.4.19.1 Workflow V1: Import the Images and DEMs

1. Import images using the appropriate Special Sensor menu.
2. Import THESIS or other DEMs for orthorectification. THESIS DEMs are in DTED format.
3.4.19.2 Workflow V2: Generate Fast Sensor models for the images
3. Build Fast Sensor support data for the NTM images using Multiple-Polynomial. To
generate individual Fast Sensor models, do the following:
a. Click Preparation > Fast Sensor Model on the main GUI.
b. Click File > Select Input Image.
c. Toggle method to Multiple-Polynomial. If you get an error message (unlikely) use
Cubic Rational instead.
3.4.19.3 Workflow V3: Merge the DEMs

4. If THESIS DEMs are used, merge the THESIS DEMs (up to 100 at a time) using
“Average.” Set feathering ON with 1 post. Give this merged DEM a name like
“THESIS_raw.”
SOCET SET Page 3-17

5. Review the merged “THESIS_raw” using ITE. Generate a TSR and inspect for shear, voids,
spikes or wells. You can also load overlapping images in the stereo monitor (or split screen)
and inspect contours as for S2. In general, you will have inadequate vertical exaggeration
for precise editing.
3.4.19.4 Workflow V4: Edit the Merged DEM

6. If necessary, edit the DEM. If your objective is to make a reasonably accurate mosaic, to
support visualization or orientation applications, little or no editing is required. If your
objective also includes production of the best possible DEM, then additional effort is
required. The most common flaws are voids and “low frequency” undulations. The
undulations will be greatly reduced when the DEMs are merged with Average.
a. Eliminating small voids
To eliminate a large number of small voids, export the “THESIS_raw” as an ASCII
DEM. Give this DEM a name like “THESIS_ascii.”
If you have large voids, you will have to collect additional images.
Re-import the ASCII DEM. Give this DEM a name like “THESIS_reimp.” The ASCII
DEM import function interpolates all void posts, and it does a nice job. For some
applications this is an impediment, but it is great for fixing THESIS voids. There is
one catch: if the DEM boundary is irregular, the indented areas will be filled with
interpolated posts. We must cut these off.
Load “THESIS_reimp” into ITE and generate a TSR. The TSR will auto-load in the
console. Click Clip Outside under area edit, and draw a rough polygon that includes
only the desired area.
To create your final DEM, merge “THESIS_raw” with “THESIS_reimp” using
ORDER OF INPUT. Be sure to have THESIS_raw on top! Set feathering to NO. This
will produce a DEM that has precisely the extent of the original THESIS data, and
only has interpolated posts in the voids. Give this DEM a name like “THESIS_filled.”
Steps 7-10 will eventually be replaced by a single area edit tool button in a future
release.
b. Eliminate spikes and wells
Narrow spikes and wells are easily edited by using second order fill. Set terrain
tracking on, Z Disabled. Draw polygons around the defect, and let second order fill
produce a better surface over the problem area
c. Eliminate shear
If strong shear is apparent in the TSR, then you have one or more DEMs with a vertical
bias. You may want to reject the individual DEMs that exhibit the problem and ask for
a re-collect. You may have sufficient overlap that you can delete the problem DEM
without loss of coverage. You can also use DEM Registration to remove the bias in
the offending DEMs.
If you want to use DEM registration to repair a vertical bias, you must first determine
the extent of the bias. Make a new merged DEM, but do not include the problem
DEM(s). Use Quality Statistics DTM vs. DTM to determine the bias. Load the new
merged DEM as the Master DTM, and the suspect DEM as Slave DTM. This function
will determine the bias of the suspect DEM in the area that it overlaps the Master
DTM. Note the magnitude and the sign of the bias.
Load the suspect DEM into DTM Registration. View the suspect DEM as a TSR or
contours. Using the LMB, sample a point somewhere on the DTM to populate the
column labeled “DTM.” Sample the same point with the middle mouse button to
populate the column labeled “Truth.” Or, copy the DTM entries to the Truth entries.
Be sure the coordinates are the same in both columns. Then edit the elevation value in
the Truth column to compensate for the bias determined in the preceding step. Toggle
the algorithm button to “Shift” (the default is “Shift, Rotate, Scale”). Hit start.
Try to merge all of the DEMs again and inspect the TSR for shear. There shouldn’t be
any.
Page 3-18 SOCET SET

d. Large bodies of water

Large bodies of water are easily corrected, if you know the elevation of the water
body. Use plane fill or constant elevation and draw a polygon around the shoreline.
If it’s the ocean, and MSL is your vertical datum, then the elevation is 0.
If you are using the E l l i p s o i d as the vertical datum, use the

coordinate conversion tool to find the correct sea-level height
in your project area!
If your water body is an inland lake or river, you can estimate the elevation by
checking surrounding posts on land. You can also try to perform a stereo drop in the
overlap area of two images that contain the water body.
If you are doing an area that includes a long river or stream, which changes elevation,
you will need to determine the slope of the river. Check the elevation of posts near the
water’s edge in the highland and lowland areas. You can create an inclined plane using
these elevation values. Save this plane as a DEM and load it in terrain tracking. Then
using an appropriate geomorphic tool to define the width of the river/stream, trace the
water body.
3.4.19.5 Workflow V5: Generate a Mosaic

7. When you are satisfied with your DEM, load it and up to 100 images into Mosaic.
8. The default mosaic will be as large as the DEM, if you want something smaller adjust the
footprint.
9. Change the following default parameters:
a. If land dominates the area, set Auto Range Adjust to Default (the default is actually
“Off”). If water dominates the area, leave Auto Range Adjust off.
b. Set Feather Width to 1
10. Select a GSD such that the output image will fit on an available disk!
3.4.20 Other Products

1. Make a stereo mate for your mosaic to really visualize the area. Load the finished DEM and
your mosaic into the Orthophoto. Select Stereo Mate. For flat terrain, set Base to Height at
1. For mountainous areas try Base to Height at 0.5. Export the pair as GeoTIFF, NITF, etc.
for viewing in other applications.
2. Use your DEM and mosaic in Openflight and Perspective Scene to create a fly-through.
3. Make image maps using your preferred application and print.
SOCET SET Page 3-19

Chapter 4
Main Workstation Window - Full Roam

Main Workstation Window explains SOCET SET’s
Graphical User Interface.
4.1 Overview
The Main Workstation Window, also referred to as the console monitor, consists of two major
components:
• Main Menu Bar
• Primary Viewport
The Main Menu bar is the horizontal menu with pulldowns across the top of the screen, which are
used to activate the various Software applications such as File, Project, Preparation, Extraction,
Products, Output, Preferences, Tools, and Help.
The Primary ViewPort is the large square window that the program uses to display imagery on
the console monitor. It also has toolbars used for manipulating the imagery. The toolbar is divided
into three groups: Standard Toolbar, Image Enhancement Toolbar, and Image Control Toolbar.
The best way to learn about this menu and toolbars is to select each of the items one at a time and
observe the result.
Most software applications require that you first load a project. If you do not have a project, you
must create one using Create Project, by clicking File > New Project on the main workstation
window. After you load a project, most of the items in the main menu are immediately available
to you.
Only one monitor is necessary to view both mono and stereo

imagery.
To set up your monitor to view stereo in CDE environment, run the following script:
# UNIX: install/cde_setup.ksh
SOCET SET Page 4-1

Chapter 4 - Main Workstation Window - Full Roam
4.1.1 Workstation Monitor

You load imagery onto the screen any time you want to review imagery or perform geolocation
or delineation. The computer screen is called the console monitor. Your workstation may also be
equipped with a stereo capability.
Alphanumeric Windows
Stereo Visualization
Split Screen
Single Image
General Purpose Tasks
Console Monitor
The console monitor supports multiple views for displaying imagery. The multiple view
capability allows the user to manipulate up to 25 views simultaneously. For each view, you can
load zero, one, or two images.
For stereo extraction, you load a S t e r e o P a i r of images onto the monitor. You may load any
two images in the monitor; and, you can view them in split-screen mode even if they are not a
stereo pair.
If you do not have an stereo capability, you can load stereo pairs of images onto the console
monitor and view them in split screen mode. In fact, you can perform 3D geopositioning and
delineation in the split-screen mode, although this approach is not as user-friendly as stereo
capability would be.
Certain SOCET SET applications utilize a large amount of your computer workstation’s
resources, so as a general rule you should minimize the number of applications you have running
at any given time. An exception to this rule is when you have started a lengthy process such as
Rectification, Automatic Terrain Extraction, or an image import, in which case you should
proceed with an interactive process while waiting for the lengthy process to complete.
4.1.1.1 Displaying Stereo Imagery

If stereo capability is available, toggle to View1 and load the stereo imagery. If the images are
not already pairwise rectified, you must turn on the on-the-fly rectification on the Image
Enhancement window. To do this, click (Pairwise Rectify) on the toolbar. See “Pairwise
Rectify / Rectify All” on page 4-20 for further explanation.
4.1.1.2 Roaming in the Imagery

The SOCET SET monitor provide a limited view to your imagery. If you wish to see the imagery
outside of this view, you must move the extraction cursor to the area of the image you are
interested in. SOCET SET provides several roaming methods:
Fixed Image — The simplest method is to toggle to the extraction cursor (with either the F3 key
or middle trackball button), move the extraction cursor by moving the mouse, and then
recentering the imagery (with either the F2 key or the left trackball button).
Page 4-2 SOCET SET

Fixed Image/Auto Recenter — Same as “Fixed Image” except that the image will automatically
recenter when the extraction cursor is moved “close” to the edge of the screen. The default is 30
pixels, but can be adjusted by setting the RT_AUTORECENTER_LIMIT environment variable
to a number other than 30.
Full Roam — In this mode there is no recentering of the imagery required. The imagery will roam
smoothly across the entire image as you move the extraction cursor.
See “Cursors” on page 1-3 for more information about cursor movement, including the toggle
operation.
4.1.1.3 Saving Image Load Point

To save a particular image’s load point for future use, you should call up this window by clicking
File > Save Image Load Point on the main menu. This window allows you to select a viewport
of interest, and then save the current cursor position as the new image load point. Clicking Apply
allows you to save many load points sequentially, if desired. Clicking OK saves and closes this
window.
4.2 Main Menu Bar

Above the menu bar is the SOCET SET version you are running.
Below the menu bar are four status boxes showing: the loaded project, the coordinate system, the
datum in use, and the displayed units of measurement. An additional three boxes are below them
to show the X, Y and Z coordinates of the cursor.
The Main Menu bar’s selections are as follows:
File > Load Project Prompts you to pick a project to load.
File > Load Images Prompts you to pick images to load on the workstation.
File > Auto Loader Enable loading of stereo models based on current ground point.
File > Save Image Load Saves current extraction cursor position as the location to display the next
Point time you load the image.
SOCET SET Page 4-3

File > Exit Exits SOCET SET.
Project > Create/Edit Project Creates a new project/Edits a project to hold SOCET SET images, terrain,
features, and other data.
Project > Data Review Allows you to interactively view project data.
Project > Backup Menu of workstation data to backup to tape. Menu includes: Entire Project,
(UNIX only) Image, Terrain, Feature, and Control.
Project > Delete Menu of workstation data to delete. Menu includes: Entire Project, Entire
Image, Minification, Levels, Terrain, Feature, and Miscellaneous.
Project > Restore Restores data from tape onto the workstation.
(UNIX only)
Project > Copy Copies data files.
Project > System Menu of user definable system information. Menu includes: Tape Drives,
Administration Image Locations, Text Fonts, and Grid Coordinate Systems.
Project > Job Queue Shows step-by-step processes for creating various products.
Preparation > Import Importing data into SOCET SET; includes choices for image, terrain,
features, ASCII Ground Points, ASCII Image Points & Visual Coverage
Tool.
Preparation > Import > Image menu includes: Import/Reformat, TIFF-RPC, Ortho, GeoTIFF,
Image DOQ, NITF, World File, Frame, BINGO Frame, Panoramic, QuickBird
Basic & Standard, WorldView Basic & Standard, ADS40, IKONOS,
LandSat, SPOT DIMAP, SPOT, JERS, IRS, RADARSAT1, RADARSAT2,
ERS, CIB, CADRG, FORMOSAT 2, ALOS PRISM, ALOS AVNIR 2,
EROS B, TerraSAR-X, ASTER, and COSMO-SkyMed.
Preparation > Import > Terrain menu includes: DTED, NED GridFloat, ASCII DTM, DEM, ARC
Terrain Grid, SDTS, GSI, LIDAR, GeoTIFF, NITF, BIL, and TERCOM.
Preparation > Import > Features menu includes: DXF, ASCII (ARC_GEN), ASCII, Shapefile.
Features
Preparation > Minification Starts Minification, which creates the image pyramid of reduced-resolution
versions of your imagery.
Preparation > Image Dodge Dodger performs radiometric balancing on one or more images.
& Balance
Preparation > Interior Enter camera fiducial coordinates and measure them in the imagery.
Orientation Includes options for both Automatic and Manual IO.
Preparation > Control Point Editing and reviewing ground control point files.
Editor
Preparation > Mult-Sensor Enter ground control coordinates and measure ground points in imagery;
Triangulation triangulation of image pairs and blocks.
Preparation > Registration DTM, Feature and Map file registration tools.
Preparation > Resample Single and pairwise image rectification, and Zoom/Scale resampling.
Preparation > Build Fast Creates polynomial approximations to SOCET SET’s rigorous sensor
Sensor Model models.
Preparation > Camera Enter camera calibration report data and distortion parameters.
Calibration
Page 4-4 SOCET SET

Extraction > Terrain Creating Digital Terrain Model (DTM) files; Automatic Terrain Extraction,
and Interactive Terrain Editing.
Extraction > Feature Feature Spec Editor, Feature Extraction & Feature Database Merge.
Creates database of three-dimensional vector data (lines, polygons,
volumetric models).
Extraction > ClearFlite Identifies and extracts various obstructions present in and around an
airfield.
Extraction > Merge Combines terrain files; merges feature data into terrain files.
Extraction > Annotation Graphical annotation overlays.

Counting
Extraction > SOCET for SOCET for ArcGIS is an extension that allows communication
ArcGIS between SOCET SET and ESRI's ArcMap.
Extraction > VrOne Refer to the VrOne User’s Manual for information.
Products > Orthophoto Removes distortion due to terrain relief from imagery; uses feature data to
Generation eliminate building layover.
Products > Multi-Spectral Enhances the resolution of a multispectral image by combining it with a
Image Sharpening high-resolution gray-level image.
Products > Change Compares two images taken at two different times, and generates an image
Detection showing where changes occurred.
Products > Mosaic Tools for creating and maintaining unbounded image: Mosaic, Seamline
Editor, and Sheet Cutter.
Products > Perspective Interactive perspective scene transformations.

Scene
Products > Terrain Analysis Terrain shaded relief and line-of-sight analysis.
Products > Image Map Produces hardcopy image maps.
Products > Map Accuracy Determines the accuracy of maps, charts and other geospatial data and
reports the resulting statistics.
Products > Quality Statistics Menu includes: Check Point File vs. DTM, Check Point File vs. Measured
Point File, and DTM vs., DTM.
Products > Anaglyph Produces red/blue simulated stereo images.
Products > Line of Sight Tool for visual analysis of linear paths in a model.
Products > DPPDB Interact with DPPDB generation process.

Generation
Products > DPPDB Update Update DPPDB.
Products > CIB Generation Interact with CIB generation process.
Output > Reports Editing and printing files; includes choices for text editing and printing
files.
Output > Screen Dump Menu includes: Full Screen, Single Window, and View Dump.
(UNIX only)
Output > Print Graphics Creates a Postscript file of the graphics displayed.
Output > File Export Exporting imagery, features, and terrain from SOCET SET.
SOCET SET Page 4-5

Output > Rendering Engines Exports data to OpenFlight.
Preferences > Cursor Editor/ Customizing the extraction cursor shape and color.
Graticule Editor
Preferences > Tracking Adjustment of sensitivity of input devices, such as mouse, trackball, etc.
Sensitivity
Preferences > Graphics/ Edit the Footprint, North Arrow and Terrain Tracking toggles.
Terrain Settings
Preferences > Graphics Modifies graphics display perspective when you have the
Projection GRAPHICS_ONLY.sup pseudo image displayed.
Preferences > Image Display Specify number of gray levels of imagery and number of graphical overlay
(UNIX only) colors for the workstation monitors.
Preferences > Printer Select printers for printing files and screen dumps.
(UNIX only)
Preferences > Keyboard/ Assign keys on keyboard to functions.

Trackball Accelerator
Mapping
Preferences > Correlation Used to establish band weights for correlation activities performed in
Weights Automatic Terrain Extraction.
Tools > Y Parallax Adjustment of Y-parallax.
Tools > Status Message Displays or hides the Status Message window.
Tools > Coordinate Three-dimensional mensuration and coordinate system conversion. Drives
Measurement extraction cursor to coordinate values you enter.
Tools > Animation For playback of multiple perspective scene images.
Tools > Radians <-> Conversions between radians and degrees.

Degrees
Tools > Flicker Images Provides a means of flickering between two images at various flicker rates.
Tools > Change Elevation Toggles the change elevation slider panel.
Tools > DOQ Editor Allows you to change information in the DOQ header.
Tools > Configuration File Configuration file editor creates and edits configuration files that contain
Editor environment variables needed to run SOCET SET.
Help > x.x Release Notes Displays the Release Notes for this release in PDF.
Help > User’s Manual Displays the Complete User’s Manual in PDF.
Help > System Admin Displays the System Adman Manual in PDF.
Manual
Page 4-6 SOCET SET

4.3 Primary Viewport

This viewport is found on the console monitor only. It is where the main viewing of the images
are projected. Most frequently used functions can also be accessed by clicking RMB on the
Viewport.
Only the active viewport will display the toolbars. Clicking on

the image area of another viewport makes it active.
Standard Toolbar
Image Enhancement Toolbar
Image Control Toolbar
RMB Pop-up Menu
Dashed lines are not available on non-Continuous Roam

Windows platform. When drawing dashed lines, they may
appear to be solid lines due to hardware limitations.
SOCET SET Page 4-7

4.3.1 Standard Toolbar
Standard toolbar selections are as follows:
SELECT TO
Minification Level Re-display the selected image at a different minification level (4X, 2X,
1:1, 2:1, 4:1, 8:1, 16:1,...). The available options will depend on the image
pyramid associated with the current image.
Screen Control Set the image display mode.

• Stereo superimposes the left and right images for stereo viewing.
• Split displays the left and right images side by side.
• Mono displays the left image only.
Screen Mode Set the screen display mode.

• Fixed Image is where the image is fixed and the extraction
cursor moves over the image. To toggle between the mouse and
extraction cursors, use the MMB or the F3 key on the
keyboard.
• Fixed /Auto is the same as Fixed Image except the image is
automatically recentered when the extraction cursor is moved
close to the edge of the screen.
• Full Roam allows full roaming throughout the entire image
without recentering.
Current Image Select which image(s) of a stereo image pair will be affected by subsequent
image manipulation operations (Left, Right, or Both).
Apply Min Level to All Apply same minification level to all viewports.
Viewports
Brightness and Contrast Adj. Adjust the brightness and contrast of an image by either using a slider or
an Auto button.
Auto Brightness and Automatically adjust the brightness and contrast when depressed.
Contrast On/Off
Zoom In Zoom in to image incrementally. Click and hold for continuous zoom.
Page 4-8 SOCET SET

SELECT TO
Zoom Out Zoom out of image incrementally. Click and hold for continuous zoom.
4.3.2 Image Enhancement Toolbar
Image Enhancement toolbar selections are as follows:
SELECT TO
Image Enhancement File • Load - Apply enhancement (MTFC, TTC Brightness &
Contrast) from an image in a project to another image in a
project.
• Save to File - Automatically creates a backup enhancement file.
. The backup file will have <support_file>_yymmddhhmmss.enh.
It stores your enhancement parameters in the image enhancement
file (enh).
• Commit to Disk - Applies the enhancements to an image file and
stores the file to disk. If Left or Both is selected, then the left
image stored on disk will be modified. If Right is selected, then
the right image stored on disk will be modified.
See “Image Enhancement File” on page 4-24 for details.
Dynamic Range Adjust Apply a dodger file to the image in the current viewport. See “Running
On/Off with Correction Files” on page 22-8 for details.
Invert On/Off Invert all the image pixel values.
Pairwise Rectification Turn Pairwise/Rectify On/Off.

On/Off
Other Image Enhancement Provide you multiple tab interfaces: Bands, TTC, Histogram, Rotation/
Tools Zoom, Pairwise Rectify All, and Filters.
NOTE: The Processing Histogram window will open. Once the
Histogram is processed, all the Image Enhancement Tools will be
displayed.
Image Enhancement Status Pop up a menu that shows the status of what is currently applied. A check
mark means on. Absent of a check mark means off. Clicking on the menu
item is a quick way to turn the enhancement On/Off.
NOTE: The Pairwise Rectify and Rectify All are not really 'image
enhancements.
SOCET SET Page 4-9

SELECT TO
Image Chipping Pop up a window that allows you to chip out a portion of an image. See
“Image Chipping” on page 4-25 for details.
4.3.3 Image Control Toolbar
Image Control toolbar selections are as follows:
SELECT TO
Graphics • Off - No graphics will be drawn.

• Limited - Graphics are loaded to fill the current screen only.
• Full - All Graphics will be drawn.
Move to Image Load Point Reload the current image.
Refresh Graphics Redraw the current graphics. (Useful for clearing old graphics.)
Recenter All Viewports Center all viewport images around their respective extraction cursor
locations.
Image Information Open the Image Information window.
Help Start the on-line documentation.
4.3.4 Displaying Imagery

After you setup a project and import imagery into the project (See “Project Management,”
Chapter 5), you can display the imagery by loading it into any one of the workstation’s multiple
views, including the stereo view, if available. To load an image, click File > Load Images on the
main menu bar. This action will bring up this Image Loader window.
Page 4-10 SOCET SET

The Image Loader window’s selections are as follows:
SELECT TO
Left/Right Filters Allow you to view certain images selectively
Left/Right scroll lists Display a list of images currently in your project.
Up/Down Arrows Select and load either the previous or next image in the scroll list.
Refresh Refresh the left and right image list.
Load Load image selected from the scroll list
View Control Panel BLANK SPACE

View_ Allow you to select the desired view.
Current Point/Load Load an image with a Default Load Point or Current Cursor Point
Point BLANK SPACE
BLANK SPACE BLANK SPACE
Create Create views (Only available with 24 bit video card)
Destroy Destroy views (Only available with 24 bit video card)
Close Close the window
Stereo Model Manager... Open the Stereo Model Manager window
The Image Loader enables you to load images into the available views, as well as create and
destroy views as desired. At any time, information about the images displaying on the screen can
be viewed by clicking Image Information .
The program remembers the last images displayed from the previous session or the last time a
project was loaded and loads them automatically. In this case, the names of the images are
displayed in the real-time Status window.
Depending on the scale of your imagery, you may wish to produce a set of reduced resolution
copies of your image. In SOCET SET, this process is called minification. Your minified imagery
is packaged with the original source imagery, and you can control which level of minification to
display with the Zoom control on the Image Enhancement tool.
SOCET SET Page 4-11

You can also zoom the imagery with Image Enhancement. See Rotation/Zoom for details.
4.3.4.1 Auto Loader

Auto Loader provide the capability to automatically change the stereo pair images as the you
move the cursor out of the area of the current stereo model. This will allow the you to digitize the
full extent of detail without having to stop and select appropriate stereo pairs.
When the entire model is first loaded, the stereo pair boundaries are analyzed up front. To obtain
this window, click File > Auto Loader on the Main Workstation window.
The Auto Loader window’s selections are as follows:
SELECT TO
Image Overlap % Enter the percentage of image overlap required to constitute a valid
model.
Switch Threshold % Enter the percentage of closeness to model boundaries before switching
pairs.
View Set the current viewport on which image manipulation operations will be
performed.
Auto Load Enable/disable the automatic capability of switching stereo models.

Load Manually loads the stereo models based on the current ground point.
Close Retain the setting and closes the window.
4.4 Image Enhancement

All other image enhancement operations are performed with the Image Enhancement window.
When you perform certain image enhancement operations, you will have a choice of area to which
the enhancement is applied:
• The displayed image
• The entire image by selecting the save option
The image enhancement operations involve image resampling and may take up to a minute to
perform if the hardware configuration is not equipped with a graphics accelerator. The Display
B/C operates very quickly if the hardware configuration is equipped with a color lot.
Page 4-12 SOCET SET

4.4.1 When to Use Image Enhancement

Image Enhancement operations are utilized to either improve the visual quality of an image or
extract features clouded by surrounding image pixels. All image enhancement operations are
optional; that is, no workstation function requires you to enhance an image before it will work.
Instead, you apply image enhancements for aesthetic reasons. Here are some of the situations
where you may apply an enhancement:
The Brightness and Contrast adjustments are likely to be the operations most frequently used.
These values can be adjusted to a preferred state and then the values saved.
If the image pixel values are bunched up in a small range, you can spread the pixel values over
the whole radiometric range by using the Tonal Transfer Curve (TTC) or the Histogram
equalization.
If you want to study the radiometric characteristics of an image, you can view the histogram.
If you want to rotate an image, you can use Image Enhancement, although to permanently rotate
an image, the Rectification process (in the single image mode) offers more options. See “Single
Image Rectification” on page 33-3 for instructions.
If you have an image that is blurry, you can generate a crisper image on disk by applying a
sharpening filter followed by clicking File button followed by Commit to Disk.
4.4.1.1 Choosing a Monitor and Image

If you currently have two images loaded (left and right), the image enhancements will be applied
only to the image you currently have selected. In other words, each image has a unique set of
enhancements, enabling you to customize the appearance of each individual image.
4.4.2 Getting Started

To use the image enhancement tools, click (Other Image Enhancement) on the Image
Enhancement toolbar. The Image Enhancement window appears. Multiple tabs will be across the
top of the window allowing you to select various image enhancements.
Bands Tonal Transfer Curve (TTC)
Histogram Rotation/Zoom
Pairwise Rectify / Rectify All Filters
4.4.2.1 Bands
Use this tool to:
• Change the image from B/W to Color if available
• Change the band mappings
• Change the brightness and contrast on the individual bands.
• B a n d mapping can be saved by selecting the File Image Enhancement button, then
selecting Save to... or Commit to...
SOCET SET Page 4-13

The Bands tab selections are as follows:
SELECT TO
BW/RGB Switch image between B/W and color if available.
Band Selectors Used for Hyperspectral Images. Select which band you want to view.
Sliders Adjust brightness and contrasts for that particular band. Use the brightness
and contrasts slider on the standard toolbar to adjust all three bands.
4.4.3 Tonal Transfer Curve (TTC)

The purpose of the Tonal Transfer Curve (TTC) Editor is to change the brightness values
associated with each value on the standard lookup table. This enables you to find objects that were
hidden due to surrounding pixels having values nearly identical to the object.
Individual TTCs are stored in files. These files are stored within the SOCET SET database. Pre-
existing TTC files can be loaded or new TTC can be generated and saved via the TTC editor.
The Apply Sensor Default option tells SOCET SET to automatically select a Tonal Transfer
Curve for the imagery currently displayed. This is called the “default TTC” for the imagery.
SOCET SET selects the default TTC by looking in the file:
<install_path>/internal_dbs/TTC/ttc_sensor.def
When SOCET SET is delivered, this file contains no default TTCs. To use this capability, add
data into the file to specify the default TTCs. Instructions on how to add TTCs into the file are
documented in the file.
Page 4-14 SOCET SET

The TTC tool provides for loading, altering, and saving TTC. The currently applied TTC is
displayed within the TTC editor window. Below the window, tools are provided for altering the
TTC.
The TTC tab selections are as follows:
SELECT TO
On/Off Toggle activates the TTC.
Apply Sensor Default... Tell the software to automatically select a TTC for the imagery currently
displayed.
Open Select a TTC file to be applied.
Save Overwrite the currently selected TTC file.
Save As Create a new TTC file.

Store Temporally save a current copy of the TTC file.
Recall Save the current TTC file before using the saved one.
Reset Restore the curve to the last saved curve.
Modify Band Select the particular band to be modified.
Range Boundary Setup and Adjust the boundaries of each range. Sliders are moved to do the adjusting.
Selection Selecting a Range (Low, Mid, High, Full) allows you to select the desired
range to modify. Only the portion of the curve that falls within the selected
range will be affected.
Toggle Slider On will activate the Log/Exp slider bars. A curve will be
drawn within the current range based on the settings of these slider bars
and the effect of the curve will be visible on the displayed image.
Edit Methods Utilize either the Sliders or RubberBand to create a user-defined curve.
SOCET SET Page 4-15

SELECT TO
Sliders
• Toggle Sliders On to activate the Logarithmic/Exponential
slider bars.
• Adjusting the left hand vertical slider bar to change the output
value at the low end of the current range.
• Adjusting the right hand vertical slider bar to change the output
value at the high end of the current range.
• Adjusting the middle horizontal slider bar to change the shape
of the curve within the current range. Moving the slider to the
left results in a logarithmic curve. A linear curve is produced
when the slider is in the center. Moving the slider to the right
results in an exponential curve. Small changes in the curve are
made by clicking in the slider bar to the left or right of the
slider.
RubberBand
• Create a unique freehand output value.
Monotonic/Non-Monotonic Enforce the shape of the curve.
TTC files can be loaded by clicking Open. A file selection box will appear from which TTC can
be chosen. When the TTC file is loaded, it is displayed on the TTC editor. If it is a color image,
you can select which bands to be modified by selecting the appropriate check boxes below the
TTC editor window. Modified TTC can be saved by clicking Save or Save As... options. The Save
option will overwrite the currently selected TTC file. The Save As option will create a new TTC
file.
Creating a user defined curve as follows:
Method 1
1. Clicking Rubber Band.
2. Click and drag the LMB and draw the new curve by dragging the cursor across the range to
the right.
3. Releasing the LMB will complete the task.
4. To redraw the curve, repeat steps 1-3.
Clicking on Reset will restore the curve to the last saved curve.
Method 2
1. Clicking Slide is On
2. Adjust the Log/Exp slider bars
4.4.4 Histogram
The purpose of the Histogram Editor is to map the input pixel values to different output values so
that a histogram of the output values approximates a desired shape. To obtain this tool, select the
Histogram tab on the Image Enhancement window. This will access the Histogram tools.
Instructions for each histogram function are as follows:
1. After selecting the Histogram tab the curve displayed in the window represents the
histogram of the current image, as determined by the settings.
2. The Generate histogram usingI:1 image button indicates whether the histogram displayed
is from the 1:1 image or a reduced resolution of the image. Click Generate histogram
Page 4-16 SOCET SET

using1:1 image to generate a new histogram from the 1:1 image or a minification of the
current image.
3. To use Equalization, click Equalization. A new histogram will be shown in the display
window and the effects of the equalization will be visible on the displayed image.
4. To use Normalization, click Normalization. A new histogram will be shown in the display
window and the effects of the normalization will be visible on the displayed image.
5. To clear the histogram display, click Reset. The original histogram for the image will be
refresh and the displayed image will be returned to its original condition (prior to any
histogram modifications).
6. Click and drag in the display window to identify specific Pixel and Percent values
The Histogram tab selections are as follows:
SELECT TO
On/Off This toggle activates the histogram.
Equalization Attempt to produce a flat curve distributed throughout the full range of
pixel values, thus spreading out the brightness values of a majority of the
image to allow you to see items that were previously invisible to the eye.
Normalization Attempt to fit the number of image pixels at each value to a normalized
(bell-shaped) curve: i.e., the number of pixels at the very black and very
white ends of the range will be fewer than at the center of the curve.
Reset Reset the histogram back to the original setting.
Display Band Display the histogram for particular band.
Generate histogram using Collects and displays the histogram using the 1:1 image or a reduced
1:1 Image resolution of the image.
SOCET SET Page 4-17

SELECT TO
Attributes BLANK SPACE

Pixel Identify the pixel value (0–255 for 8-bit imagery).
Percent Identify the histogram percentage at the above pixel value.
Mean Identify the histogram mean.
Std Dev Identify the histogram standard deviation.
4.4.5 Rotation/Zoom
Rotation defines the angle to rotate an image on the workstation monitor. If you wish to
permanently rotate an image, use Rectification. See “Rotating an Image” on page 33-3 for
details.
The purpose of the Zoom is to magnify image(s) by a factor you specify without having to
resample the entire image. If you wish to zoom or resample the entire image, use Zoom/Scale.
See “Zoom/Scale” on page 34-2 for details. In addition to magnification, zooming an image
makes it possible to make sub-pixel measurements on the image.
4.4.5.1 Rotation
There are two methods to define a rotation angle.
• Select the arm of the rotation dial and move the arm while holding the LMB. As the
arm moves, the current angle of the arm is displayed in the angle field. It is applied to
the image upon releasing the mouse button. The rotation angle is measured from the
original image.
• Enter the desired angle directly into the text box next to the dial. Once you define the
rotation angle, it will be applied to the image.
Selecting the Interpolation option will also be applied automatically. The Nearest Neighbor
technique is the faster of the two techniques, while Bilinear Interpolation results in a better
quality image.
4.4.5.2 Zoom
There are two methods to define a zoom factor.
• Click the Zoom Out (Up Arrow) button and the Zoom In (Down Arrow) button to zoom
out and zoom in, respectively
• Type the desired value in the text box. Once you define the zoom value, it will be
applied to the image.
Selecting the Interpolation option will also be applied automatically. The Nearest Neighbor
technique is the faster of the two techniques, while Bilinear Interpolation results in a better
quality image
4.4.5.2.1 Advanced
Clicking Advanced... will allow the user access to the advanced zoom settings. Currently, there
are two advanced settings, Zoom Increment and Use All Minification Levels.
• Zoom Increment: This is the increment at which the Zoom Out and Zoom In buttons
will change the zoom level. This zoom increment is applicable to the Zoom In/Out
Page 4-18 SOCET SET

buttons on the Rotation/Zoom as well as the Zoom In/Out buttons on the image
viewport toolbars. This value can be set from 0.01 to 2.0.
• Use All Minification Levels: This check box is used to state whether you want to
automatically change to the nearest minification level while zooming (checked) or
if you always want the zoom level to be applied to the current minification level
(unchecked). For example, assume the minification level was at 8:1 and we set the
zoom factor to be 2.0. If this box were checked, the minification level would change
to 4:1 and the zoom level would change to 1.0. If the box were not checked, the
minification level would remain at 8:1 and we would simply zoom in 2X on the 8:1
image. The resulting GSD would be the same either way, but the 4:1 would be
clearer as there is more information in the lower minification level.
Zoom enhancements are not currently saved by the “Save”

operation.
SOCET SET Page 4-19

The Rotation/Zoom tab selections are as follows:
SELECT TO
Rotation BLANK SPACE

On/Off This toggle activates the Rotation tool.
Interpolation There are two techniques:
BLANK SPACE • The Nearest Neighbor technique is the faster
BLANK SPACE • Bilinear Interpolation results in a better quality image.
Angle Indicator Allow you to indicate the angle by click and drag the arm of the
BLANK SPACE rotation dial, or entering a value in the box.
Apply to All Viewports Check this box to apply the rotation to all your viewports.
Zoom BLANK SPACE

On/Off This toggle activates the Zoom tool.
Zoom Factor Allow you to indicate the zoom factor either by using the slider, or
BLANK SPACE entering a value in the box.
Advanced Access the Zoom slider.
4.4.6 Pairwise Rectify / Rectify All

The purpose of Pairwise Rectification is to enable S t e r e o V i s u a l i z a t i o n of a stereo image
pair. Pairwise rectification will rectify the images on-the-fly, so you don’t have to pre-rectify the
images with Rectify. You should turn pairwise rectification On whenever you have a stereo image
pair and are doing 3D data extraction; for example, when you are running ITE, or Feature
Extraction.
The purpose of Rectify All Views is to orient and match the GSD of all of the images. When the
Rectify All Views is first applied, the orientation and GSD of the Master Viewport (always the
left image) will be used. While the Rectify All Views mode is active, any rotation, zoom, or
minification level change to ANY image will result in all other images matching this change.
Page 4-20 SOCET SET

The Pairwise Rectify / Rectify All tab selections are as follows:
SELECT TO
Pairwise Rectify BLANK SPACE

On/Off This toggle activates the Rectification tool.
Pixel Size in Ground Units View the Pixel Size in Ground Units
Rectify All BLANK SPACE

On/Off This toggle activates the Rectify All tool.
Master View BLANK SPACE
• The Nearest Neighbor technique is the faster
• Bilinear Interpolation results in a better quality image.
SOCET SET Page 4-21

4.4.7 Filters
Filter allows the user to select a predefined, sensor default, or user defined filter to the image.
Some applications of filtering allow the user to sharpen, smooth, detect edges, and provide anti-
aliasing.
The Filters tab selections are as follows:
SELECT TO
On/Off This toggle activates to Filter tool.
Select Sensor Default... Tell the software to automatically select a filter for the imagery currently
displayed.
Filter BLANK SPACE

Sharpen Detect and displays a high-frequency, enhanced version of the image
Vertical Edge Detect Apply vertical edge detection.
Horizontal Edge Apply horizontal edge detection.

Detect
Smooth Apply smoothing filter.
Speckle Remove speckles from Synthetic Aperture Radar (SAR) images.
Median Applies median filter.
Browse Allow you to select other user-defined filters that may already be on your
machine.
View/Edit Allow you to view and edit the values in the Kernel editor window.
4.4.8 User-Defined Filters

To apply a filter:
1. Click Browse.... A window will open from which the user-defined filters can be selected.
2. To apply a filter that appears in the list of existing filters, highlight the desired filter by
double-clicking on the filter name.
3. Click View/Edit... on the Filter window to display the values of the current filter. This will
be displayed in the Kernel editor.
To modify the kernel:
1. Enter new values in the Kernel Editor.
2. The size may also be modified by selecting a different option under Size.
Page 4-22 SOCET SET

3. You may save the currently defined kernel to disk by clicking:

a. File > Save on the Kernel Editor window to save the existing filter name.
b. File > Save As on the Kernel Editor window to create a new filter.
c. You may reset the Kernel back to zero by clicking File > Clear on the Kernel Editor
window.
The system manager will protect the standard kernel values from being modified.
4.4.8.1 Kernel Editor

The Current Kernel window’s selections are as follows:
File > Open Display the Filter Selection window.
File > Save Saves the kernel’s values in the same file
File > Save As... Saves the kernel’s values to a new file.
File > Clear Changes all the values in the current kernel to zero.
File > Exit Exits the Kernel Editor window.
Size > 3x3, 5x5, 7x7, 9x9, Changes the size of the kernel.
11x11
Help > Contents Starts the on-line documentation.
SOCET SET Page 4-23

4.5 Image Enhancement File
• Load —Displays a list of enhancement files. You select an image enhancement file,
with the same number of bands and bits as the current loaded image to apply (MTFC,
TTC, Brightness & Contrast) to the current loaded image.
When you perform an enhancement, the enhanced image appears on the monitor.
Unless you perform a save operation to permanently save the enhancements, the changes
will be forgotten after you exit SOCET SET.
There are two ways to permanently save an enhancement: Save to File & Commit to Disk.
• Save to File —Saves the current combination of enhancements, but does not change the
image disk file. For example, you may use this to capture a nice brightness/contrast
setting. There is only ONE enhancement file per image.
The next time you load the image, SOCET SET will remember the enhancement parameters
and will apply them to the display. However, if you then make modifications to the
enhancement parameters, and then do a RESET, the parameters will be reset to the ones you
saved previously.
Some applications including Orthophoto, Mosaic, and Image

Map use the enhancement parameters which are saved by this
method. In order to reset the enhancement parameters to their
initial state, you can remove the enhancement file for the
image (.enh) located in the project data directory,
<install_path>/data/<projectname>.
• Commit to Disk —This permanently changes the image on disk. This will resample the
entire image and may take a minute or more. You have a choice of overwriting the
original image or creating a new image.
Page 4-24 SOCET SET

4.6 Image Chipping

(Image Chipping) allows you to select an area from an image and create a chip of that area.
This chipping capability allows you to preserve enhancements from the original image, and in the
case where the output image format of the chip is specified to be NITF, it also saves
geopositioning information in the NITF header.
The Image Chipping window’s selections are as follows:
File > Exit Exits Image Chipping.
Options > Auto Minify Automatically creates a minified image pyramid after Image Chipping is
complete.
SOCET SET Page 4-25

SELECT TO
Lines / Samples to skip / Select the portion of the input image to be chipped by specifying the
process number of lines/samples to skip and process. This is an alternative to Draw
MBR.
• “Skip” is the offset in pixels from the upper-left corner of the
input image.
• “Process” is the size of the area that you want to chip.
If you don’t change these numbers from the defaults, the entire image will
be processed.
Draw MBR Select a portion of the input image to be chipped by delineating an MBR
on the image display. If a MBR is not delineated, the default is to process
the entire image.
Enhancement Options Select how enhancements are applied to the output image chip. The
BLANK SPACE following options can be selected.
Save Image Without Saves the raw image pixels to the output chip, without enhancements
Enhancements applied.
Commit Commits any enhancements to the output chip’s image pixels.
Enhancements to
Saved Image File
Input Support File Select the input support file for the image from which the chip will be
created
Output Image Identify the name, location and image format of the output image files.
Start Start Image Chipping.
4.6.1 Execution— Image Chipping

This section describes the procedure to create an image chip:
1. Click Image Chipping on the Image Enhancements toolbar of the image display viewport
to bring up the Image Chipping window.
2. Specify the area to be chipped. You have the following two options:
a. Click Draw MBR on the Image Chipping window. Make sure that the image you wish
to chip is loaded into the left side of the current viewport, then toggle to the Extraction
cursor. On the viewport that contains the image you wish to chip, delineate the MBR
of the area to chip. You delineate the MBR by pressing the LMB on the first corner of
the MBR, dragging the Extraction cursor while holding down the LMB, and releasing
the LMB on the final corner of the MBR. Toggle back to the mouse cursor before
proceeding.
b. Alternatively, you can enter the exact number of pixels you want processed by
entering numerical values in the Lines and Samples text fields on the Image Chipping
window. By default, these fields contain the total lines and samples in the image you
wish to chip. You can skip any of the first lines and samples of the image and continue
processing any number of lines and samples.
The sum of the skip and process values must be less than the
original lines and samples of the image.
3. Select an option for image enhancements by clicking one of the radio buttons in the
Enhancement Options area. The two options are explained below.
Page 4-26 SOCET SET

a. Save Image Without Enhancements.

This option creates a chip image from the raw pixel data, ignoring any image
enhancements that may be currently applied to the input image.
b. Commit Enhancements to Saved Image File.
This option commits to the output chip any enhancements that are currently applied to
the input image. The actual image pixels that are written to the chip will contain those
various enhancements.
Neither of these two options creates an enhancement file for

the chip.
4. [Optional] Select a different input support file by clicking the file chooser button in the
Input Support File area. A file selection window will appear, allowing you to choose a
different support file. Normally, the input image that will be chipped is the left image that
is loaded into the current viewport, and its support file name appears in the Input Support
File text box by default. You should rarely, if ever, need to change this input support file.
Note that if you do, the image displayed in the image display viewport will not change, and
the Draw MBR feature will not work correctly. In that case, you will only be able to specify
the chip boundaries by using the lines/samples skip/process text boxes.
5. [Optional] Change the output image location by clicking the file chooser button on the
Location area in the Output Image section. A selection window will appear, from which
you can select a different image location.
6. [Optional] Change the name of the output image chip by typing a different name into the
Name area of the Output Image section. The default output name is the base name of the
input image, with “_chip” appended to it.
7. [Optional] Change the output image format by selecting a different format from the image
format combo box. The default output image format is NITF 2.0.
8. Click Start to begin image chipping.
Please note the following additional information related to the Image Chipping capability.
• The output image chip will have similar characteristics to the input image, i.e. the
number of bands, image depth, security fields, etc. will generally be the same as those
of the input image.
• If an MBR for a chip is delineated on a displayed minification level for the input image,
the output chip will not contain pixels from the minification level, rather, it will contain
pixels from the 1:1 image for the entire geographic area that was delineated. This is a
useful feature, which allows you to delineate an area for chipping which is larger than
would fit on the screen for the 1:1 image.
• If the specified output image format is in NITF, the output chip will contain ICHIPB,
RPC00A, and RPC00B TRE’s. These TRE’s allow the chip to be ingested and correctly
geopositioned by third party software packages.
4.6.2 Batch Processing - Image Chipping

COMMAND LINE:
% start_socet -single chipping -batch -s setting_file
SOCET SET Page 4-27

EXECUTABLE NAME NAME IN SETTING FILE
chipping chipping
project Project filename (select from the .prj files in /usr/geoset/data).
input_sup Full pathname of input image support file.
output_location [Optional] Image location to which output chip image will be written.
Default is project image location.
output_name Base name (without suffix) of output chip image and its corresponding
support file.
output_format [Optional] Format of output chip image. See “Data Handling

Capabilities” Default is format of input image.
auto_minify [Optional] Specify whether to do auto minification. Possible values are

“YES” or “NO”. Default is not to perform auto minification.
lines_skip Number of lines to skip for image chipping. Do not use this keyword if you
specify chip boundaries with ground point vertex keywords.
lines_process Number of lines to process for image chipping. Do not use this keyword if
you specify chip boundaries with ground point vertex keywords.
samples_skip Number of samples to skip for image chipping. Do not use this keyword if
you specify chip boundaries with ground point vertex keywords.
samples_process Number of samples to process for image chipping. Do not use this keyword
if you specify chip boundaries with ground point vertex keywords.
ground_point_format Format of ground point vertices. Possible values are “geo_degrees”,

“geo_radians”, “grid” and “lsr_curved”. Format must match the coordinate
system of the project. Do not use this keyword if you specify chip
boundaries using lines/samples skip/process keywords.
ground_x_vertex_1 X value of the first ground point vertex of the image chip. Can specify as
geographic longitude value (decimal degrees or colon-separated
degrees:minutes:seconds), or cartesian coordinate for grid or lsr_curved
coordinate systems. Format must match ground_point_format keyword.
Do not use this keyword if you specify chip boundaries using lines/samples
skip/process keywords.
ground_y_vertex_1 Y value of the first ground point vertex of the image chip. Can specify as
geographic latitude value (decimal degrees or colon-separated
ground_x_vertex_2 X value of the second ground point vertex of the image chip. Can specify
as geographic longitude value (decimal degrees or colon-separated
Page 4-28 SOCET SET

ground_y_vertex_2 Y value of the second ground point vertex of the image chip. Can specify
as geographic latitude value (decimal degrees or colon-separated
ground_x_vertex_3 X value of the third ground point vertex of the image chip. Can specify as
ground_y_vertex_3 Y value of the third ground point vertex of the image chip. Can specify as
ground_x_vertex_4 X value of the fourth ground point vertex of the image chip. Can specify as
ground_y_vertex_4 Y value of the fourth ground point vertex of the image chip. Can specify as
SOCET SET Page 4-29

Chapter 5
Project Management
Project Management covers the creation and editing of
projects, which encompass a geographic area covered by
imagery and other data that can be exploited into build
products.
5.1 Overview
During workstation operation, you will create a large number of data files. These files include:
• T e r r a i n files
• I m a g e , I m a g e r y files
• F e a t u r e files
• G r o u n d P o i n t files
In order to organize these files in a manageable fashion, they are divided into projects. A project
encompasses a geographic area covered by imagery and other data that can be exploited to build
products for dissemination to a broad spectrum of users.
Projects are not limited in extent; in other words, there is no limiting bounding rectangle within
which all project data must fit.
5.1.1 When to use Project Management

Project Management is the initial step in creating a new project. It is also used when an existing
project needs to be modified.
5.1.2 Organizing Your Data With Projects

Before you can import or display imagery with the software, you must create a project. You can
think of a project as a container holding the data for a set of images you are going to utilize. The
data you extract from a set of imagery will be stored in the project directory that contains that set
of imagery. When you create a project, you specify the coordinate system and datum to use for
the project. You also will specify the disk directories of where the project and imagery data will
be stored. Most importantly, you give your project a name. The name of the project file is the
name you assigned to the project with the extension.prj when it was created. The software stores
the definition of a project in a special project file.
SOCET SET Page 5-1

Chapter 5 - Project Management
SOCET SET uses the computer file system to store its project data. The following figure depicts
the directory tree the software uses to store its data.
<install_path>
data/ images/(default
Image Location)
boulder/ escondido/ boulder/

boulder.prj escondido.prj
Most software applications require that you first load a project. Once you have loaded a project,
you can then operate on the imagery and other data contained therein. You can import images into
the project, triangulate the images, perform feature and terrain extraction, and create image
products to export. The locations of the image files are defined by entities called Image Locations.
See “File Organization,” Appendix B for more information on Image Locations.
You create a project by running Create/Edit Project, which is described later in this chapter.
Initially, the project is empty; you populate it with imagery and other files when you run any of
the Import applications (Image Import, Feature Import, etc.). After importing data, you will
typically execute one or more extraction applications (Automatic Terrain Extraction, Feature
Extraction, etc.). Next, build the products you desire (using applications such as Orthophoto or
Image Map). Finally, you should archive the project using Backup and then delete the project with
Delete.
Create Import Generate Archive

Extract
Project Data and Export and Delete
Data
Products Project
5.1.2.1 Project Parameters

The key constraint imposed by projects is that all data stored in a given project must conform to
that project’s parameters. This means that all data entry, data display, and imported data must
conform to the project parameters.
For example, if you create project XYZ and select the Geographic (lat/long) coordinate system
with feet units, then you must enter all data (such as ground control points) as lat/long values, and
all Z-units must be specified in feet. If you have any data in another coordinate system (e.g. UTM)
you must convert it to lat/long before entering it into project XYZ.
Every software project is characterized by the following parameters:
• Coordinate System (Geographic or UTM or LSR or Grid/State Plane)
• Horizontal Datum (WGS 84, NAD 27, etc.)
• Units (feet vs. meters)
• Vertical Reference (E l l i p s o i d vs. M S L )
Page 5-2 SOCET SET

Additional parameters may be required dependent upon various selections. Once the project is
created, the parameters you selected are displayed on the Main Menu window.
5.1.2.2 Parameter Exceptions

There are a few exceptions to this rule. For example, Coordinate Measurement allows you to
display the extraction cursor location in several coordinate systems. Also, T r i a n g u l a t i o n
allows you to enter ground control points in any datum.
After you create a project, you may need to convert some of the project data to other coordinate
systems or other units. To do this, use the Project Copy or Project Save As operations described
later in this chapter.
5.2 Creating a Project

You use Create/Edit Project to create your project. Since most SOCET SET applications require
a project to be loaded, you must create a project before you can proceed with importing and
extracting data. See “Execution for Create/Edit a Project” on page 5-13 for steps to create a new
projects.
Additional information about project organization is in “File

Organization.” See “File Organization,” Appendix B.
Create/Edit
Project
Geographic UTM Select LSR

Parameters Parameters Datum Origin
Computer
UTM Zone
SOCET SET Page 5-3

5.3 Create/Edit Project Window
The Create/Edit Project window’s selections are as follows:
File > New Initializes all project parameters to the default values, and allows you to
enter parameters for a new project.
File > Load Project Prompts you to select a project from a list of available projects, and then
loads that project into the Create/Edit Project for viewing or editing.
File > Save Saves the project currently in the Create/Edit Project. If the project is new
and does not yet exist, then you will be prompted for a project name, and
that project will be
created.
If you are editing an existing project, then that project will be updated.
File > Save As Prompts you for a project name to save the project in, and then saves the
project. The project you specify must not yet exist.
File > Exit Exits Create/Edit Project.
Options > Set LSR Origin Prompts you to enter an LSR origin. Use only for LSR and LSR With
Curvature projects.
Page 5-4 SOCET SET

SELECT TO
Project Select a unique one-word name for the project. This field is NOT editable.
Click File > New to open the Create/Edit Project window. Later when
you select Save or Save As, you will be prompted to enter a project name.
Project Path By default, Create/Edit Project will make a project data directory called
<install_path>/data/<project_name>, where project_name is the name you
entered when initially saving the project. This directory path is for all data
associated with the project.
If you wish to use a different directory to hold your project data directory,
you can specify a different parent directory instead of <install_path>/data;
however, you must create the new parent directory prior to running Create/
Edit Project.
NOTE: The project_name will be added to the end of the parent
directory you specify.
Do not include the project name subdirectory, as Create/Edit Project will
append it for you.
NOTE: This directory must exist and must be writable.
Datum You need two distinct datums to establish a coordinate system for
measurements on the earth’s surface: a horizontal datum and a vertical
datum. SOCET SET refers to Horizontal Datum as Datum, Vertical Datum
is referred to as Vertical Reference, and will be discussed later.
A horizontal datum is a smooth ellipsoid that establishes a reference
coordinate system for the X and Y coordinates of all locations and
measurements. WGS 72 and WGS 84 are examples of horizontal datums.
To select a Datum, click the button to the right of the field to open a list
of predefined datums.
Coordinate System When you create a project you must select one of the following
G e o g r a p h i c C o o r d i n a t e s System:
• Geographic, LSR (Local)
• LSR with Curvature, or Grid/State Plane.
• UTM is selectable under the Grid/State Plane menu.
You must select the coordinate system of your project carefully because
your choice has the following important consequences:
1. All input data must be represented in the project coordinate
system. Input data includes ground control points, orthophoto
bounding rectangles, camera locations, and any other data you
input, either through a disk file or interactively via a window.
2. All output data will be presented in the project coordinate
system. Output data includes terrain files, feature data,
orthophotos, support data, geopositioning information, and any
other output data either output to a disk file or to a window.
3. All grid-format terrain files in the project will have their post
array aligned on lines of the coordinate system (e.g. in a
geographic project, the terrain post array will be aligned
parallel to lines of latitude and longitude; in a UTM project the
terrain array will be aligned on lines of constant UTM values).
4. Orthophotos built within the project will have their boundaries
and their internal pixel rows aligned on lines of the coordinate
system (similar to the terrain post array described above).
SOCET SET Page 5-5

SELECT TO
Lat/Lon Format This field is only used when the Coordinate System is Geographic. It
specifies the display format for lat/long readouts. Your choice is either
DD:MM:SS (e.g. 72:30:10.25W) or decimal degrees DD.nnnnn (e.g. -
72.114). The format is used both for data display and data entry of latitude
and longitude. The format selection does not affect the Z coordinate
format. The selection is not used in coordinate systems other than
geographic.
All XY coordinates in a Geographic project are stored, imported, and
exported in radians, regardless of how the XY format is set. The choice of
XY format only affects the display of coordinates in windows.
If you select DD:MM:SS format you may enter data values in any of the
following formats: DDD:MM:SS.SSS; DDD:MM:SS; DDD:MM (you
must have exactly two digits for minutes MM and seconds SS). You may
preface any of these with “+” or “-” (or you may append any of the
characters E, W, S or N).
If you select decimal degrees format, you must enter data values as +/-
DDD.DD or as DDD:MM:SS.SSS. South and West are indicated by a
leading negative sign. Suffixes such as E, W, S, or N are not permitted.
Units Units specifies the project units for ground point coordinates. When you
create a project you should set the project units parameter to be either
meters, US Survey Feet, or International Feet. This will determine the
units in which elevations, distances, spacings, and intervals are entered and
displayed in the project. In addition, all file-based output data (e.g. DTMs
or feature data) will also be stored in the project units. If your project units
are in meters any conversions to feet will be US Survey Feet.
If your coordinate system is geographic, the units are used only for the Z
coordinate because the X and Y values are stored internally in radians and
displayed in degrees.
If your coordinate system is LSR and you have not anchored the LSR to
earth, then the units selection is not used.
Vertical Reference See “Vertical Reference” on page 5-11 for explicit details.
Min/Max Ground Elevation Select the approximate range of elevations, in select units, within the
project. Data that you store in the project may exceed these limits, so they
don’t have to be precise.
Image Location By default, Create/Edit Project will use a project image location called
DEFAULT. If you wish to use a different directory to hold your project
image directory, you can specify a different image location. This is storage
for all images associated with the project. This name must exist in the file
<install_path>/internal_dbs/DEVICE/location.list. See “Establishing
Image Locations” on page D-1 on how to add, remove image locations
from the system.
NOTE: This directory must exist and must be writable.
5.3.1 Coordinate Systems

5.3.1.1 Geographic
Horizontal locations are specified as latitude / longitude. Elevation locations are in feet or meters,
based on the project units parameter you choose. Data entry and data display are in degrees. If
you choose Coordinate System / Geographic, Create/Edit Project prompts you for a geographic
reference point by opening the Geographic Parameters window.
Page 5-6 SOCET SET

The location of the point is not important, but it should be near the region you are working. The
point does not have to lie on the ground, nor does it have to be in an image.
When you select a Geographic Coordinate System, you must also specify the format of latitude
and longitude values. See “Lat/Lon Format” on page 5-6 for details.
5.3.1.2 Local Space Rectangular (LSR)

LSR is a cartesian system. LSR may or may not be curved. LSR may or may not be anchored to
the ground. If anchored, it may be rotated from north. LSR is useful in the following
circumstances:
1. Close-range photogrammetry, including microscopy.
2. You have data in an unknown coordinate system, and you believe it can be represented by
a cartesian system.
3. You will be extracting data in SOCET SET and outputting the data to a system that only
understands cartesian coordinate systems (e.g some triangulation packages).
4. You want to store your data in a rotated coordinate system (i.e. +Y is not to North).
LSR coordinate systems are not map projections and do not

use false eastings and northings, so LSR should not be used
to model a grid coordinate system.
North Y
Pole
Z
Anchor
Point
X and Y are tangent to the Earth at the Anchor.
Point, Z is perpendicular (nadir).
Rotation Angle is 0.0 in this example.
Equato r
By default, LSR coordinate systems are not anchored to the ground. To anchor an LSR project to
the ground, you must select Options > LSR Origin, then type in the LSR Origin point (X and Y)
and a rotation angle (positive rotates Y clockwise from North). The rotation angle is normally
SOCET SET Page 5-7

zero. You do not type-in a Z value for the origin because the LSR origin point is set at the 0.0
elevation of the vertical datum you have selected (ellipsoid vs. mean sea level).
If you want to share data between an LSR project and earth-

based projects, you must anchor the LSR coordinate system to
the ground.
If you do not anchor LSR to the ground, the project units (feet vs. meters) are meaningless, since
the LSR coordinate system is relative. The units are simply established by convention: the units
could be miles or centimeters or millimeters. However, once you have determined what the units
are, then all data you enter into the project must be in those units. For example, you cannot enter
some data in centimeters and other data in millimeters. This is especially important during the
Triangulation and Frame Import. All data displays will show data in the units you have chosen.
Some windows may have labels such as feet or meters: you should ignore these labels, since the
data is displayed using your units convention.
Use LSR-Curved for earth-based projects, since surfaces of constant Z will follow the earth’s
ellipsoid. Select LSR (not curved) if you want a simple cartesian system where surfaces of
constant Z are flat planes, such as for close-range projects.
5.3.1.2.1 LSR Theoretical

The LSR coordinate system is just a right-handed 3D Cartesian coordinate system. Unanchored,
it is very useful for close-range photogrammetry. For example, the origin can be the lower corner
of a room; the X-axis can be the intersection of the floor and one wall; the Z-axis can be the
intersection of two adjacent walls; and so on.
Another way of interpreting the unanchored LSR coordinate system is that the origin is at the
center of the earth (default zero offset), the X-axis is on the equator passing through Greenwich
meridian, the Z-axis passes through the North Pole, and the Y-axis completes the right-handed
system (default zero rotation). This is the same as the USR coordinate system in SOCET SET.
The anchored LSR coordinate system, on the other hand, has a non-zero offset (origin of
translation) and non-zero rotations with respect to the USR coordinate system. The offset is just
the USR coordinates of the “input origin” (latitude, longitude). The rotations are defined such that
the LSR XY-plane is tangent to the earth ellipsoid at the “input origin” and the LSR Y-axis is
“input rotation angle” from the North clockwise. It follows that the LSR Z-axis is parallel to the
vertical at the “input origin”.
By definition, the elevation of points on the ellipsoid is always zero. As distance from the origin
of a point on the ellipsoid increases, the LSR Z-coordinate of that point decreases significantly.
The LSR Curvature coordinate system attempts to compensate for this systematic change. The
corresponding change in XY-coordinates is much smaller.
To properly use the LSR coordinate system for large area triangulation, on has to first convert
control points, aircraft GPS and sensor IMU angles into this coordinate system. An example of
this is what the ADS40 ground station software does to create L1 support files from L0 support
data.
5.3.1.3 LSR with Curvature

The LSR Origin should be set only for projects that are based on an LSR or LSR with Curvature
coordinate system. Clicking Option > LSR Origin ties the coordinate system to the to earth’s
surface. This allows the project to be converted to other coordinate systems such as geographic
Page 5-8 SOCET SET

or grid. Setting the LSR origin is optional, and if you don’t plan on converting your project to
other coordinate systems, then the LSR Origin need not be set. Close-range photogrammetry and
microscopy have no need to set the LSR Origin.
The LSR Origin window’s selections are as follows:
SELECT TO
Lat (Deg:Min:Sec) Enter Lat coordinate of origin point of LSR cartesian system.
Long (Deg:Min:Sec) Enter Long coordinate of origin point of LSR cartesian system.
Rotation Angle (degrees) Enter Rotation Angle.Positive = clockwise; (usually 0.0 which is +Y
pointing North)
SOCET SET Page 5-9

5.3.1.4 Grid / State Plane

Grid coordinate systems encompass a large class of coordinate systems. Grids are the most
common coordinate systems used for mapping. For example, S t a t e P l a n e C o o r d i n a t e
S y s t e m s in use in the USA are grid systems, and UTM is also a grid system. If you choose
Coordinate System / Grid/State Plane, Create/Edit Project prompts you by opening the Select a
Coordinated System window. By clicking the tab General or UTM will allow you distinguish
further.
Since grids are really a class of coordinate systems, you must define the characteristics of your
particular grid before executing Create/Edit Project. The steps you follow to create a grid-based
project are:
1. [Optional] Determine the characteristics of your grid. To add a new grid, you will need to
know the projection, the datum, and the False Easting and False Northing.
2. [Optional] Define your grid by adding an entry to the Grid Definition File,
<install_path>/internal_dbs/GEODETIC/grid_parameters. That file
contains complete instructions for how to add your grid definition, as well as numerous
sample grid definitions.
When defining your grid in the Grid Definition File, all latitudes
and longitudes are entered in radians (not degrees), and all
False Eastings and Northings are entered in meters (even
though your grid may be based on feet).
To select an existing Grid/State Plane coordinate system, do the following:

1. Select a Grid/State Plane coordinate system. This will open a Coordinate System list. Select
a Grid/State Plane from the General list. then click OK. This will update the Datum field
automatically.
2. If your grid is based on units of feet, be sure to set the project units parameter to feet (rather
than meters) in Create/Edit Project. This is acceptable, even though the distances in the
Grid Definition File are specified in meters.
Page 5-10 SOCET SET

5.3.1.5 UTM
This is the standard 60-zone U n i v e r s a l T r a n s v e r s e M e r c a t o r projection. Horizontal
locations are specified as Easting / Northing in meters. The project units parameter must be set
to meters (i.e. cannot be set to feet). Z-units are in meters. You must specify in which of the 60
zones (numbered 1 to 60) the project is located, or you can enter a longitude value and
SOCET SET will compute the zone for you.
If you select the UTM coordinate system, Create/Edit Project prompts you for a UTM zone. If
you don’t know the UTM zone in which your project resides, you can ask Create/Edit Project to
compute the UTM zone based on a known longitude value.
5.3.2 Vertical Reference

A vertical datum, also called vertical reference, establishes a reference for Z coordinates. The
choices are (1) the Mean Sea Level (MSL) Geoid, and (2) the ellipsoid. The MSL Geoid is an
irregularly-shaped surface that coincides with sea level over the entire earth, based on the 1996
N G A Earth Gravity model (EGM96). You can also select GEOID03, which is valid over the
conterminous United States, and JAPAN2000, which is valid over Japan. The ellipsoid is the
project horizontal datum. The vertical datum is not used if your coordinate system is LSR and is
not anchored to earth.
Selecting the vertical datum has the following consequences:
•Data (terrain and feature data) that you import into the project must share the same
vertical datum as the project.
•Data (terrain and feature data) that you export from the project will share the same
vertical datum as the project.
•All coordinate data in the SOCET SET windows will be displayed with its Z coordinates
referenced to the project datum.
•All coordinates that you enter into SOCET SETwindows must be entered with their Z
coordinates referenced to the project datum (there are a few exceptions to this rule,
discussed below).
•All internal SOCET SET data files (ground points, feature, terrain, etc) will store Z
coordinates in the project vertical datum.
SOCET SET Page 5-11

There are some questions that you should consider when deciding whether to select MSL or
ellipsoid:
1. In what vertical datum are your control points?
2. What vertical datum is used by the terrain/feature data that you will be importing?
3. In what vertical datum do you want to export terrain/feature data?
For example, if your control points are referenced to MSL, and you want to generate a terrain/
feature data that is referenced to MSL, then you should create your project with an MSL vertical
datum.
If your control points and your terrain/feature data are both referenced to ellipsoid, you should
create your project with an Ellipsoid vertical datum.
If your control points are referenced to Ellipsoid, but you have terrain or feature data (for import
or export) that is referenced to MSL, then the decision to use Ellipsoid or MSL as the project
vertical datum depends on how you are importing your control points: If you are importing the
control points using ASCII Ground Point Import, then you should set the project vertical datum
to Ellipsoid, import the control points, then convert the project to MSL (see details below), then
process your terrain/feature data in MSL. But if you will manually input the control points in the
Control Point Editor or in Multi-Sensor Triangulation Interactive Point Measurement (IPM), then
you should set the project vertical datum to MSL, and set the CPE (or IPM) window display to
Ellipsoid while you are entering the control points.
If your control data is referenced to MSL, and you want your terrain/feature data referenced to
ellipsoid, then Control Point Editor or in Multi-Sensor Triangulation Interactive Point
Measurement (IPM), then you should set the project vertical datum to Ellipsoid, and set the CPE
(or IPM) window display to MSL while you are entering the control points.
If you don’t know which vertical datum to use, you should select MSL rather than Ellipsoid.
If you create a project, then later decide to change the vertical datum, you can convert all the data
in the project to another vertical datum by using the Save As button on the Project Editor window,
or by using the Project Copy tool.
All coordinates displayed in SOCET SET windows are referenced to the project’s vertical datum.
For example, if the project vertical datum is MSL, the all Z values you see in the windows and
reports will be MSL. However, there are some SOCET SET modules that permit you to display
(and enter) coordinates in either MSL or ellipsoid vertical datum, regardless of the project vertical
datum. These modules are Coordinate Measurement, Control Point Editor, and Interactive Point
Measurement (in Triangulation). In these the modules, you choose which vertical datum you want
to use in the user interface. This selection does not affect the vertical datum used in the underlying
data storage or the import/export of terrain and feature files.
If you create a project and then you later determine that you need to import a data file (terrain or
feature) that has a differing vertical datum, you can either (1) create a new, empty project with
the same datum as the external file, and import the file into the new project; or (2) convert your
project to the same vertical datum as the external file using the Save As button on the Create/Edit
Project window.
Some sensors (such as DPPDB and special sensors) utilize ellipsoid as their internal vertical
datum. SOCET SET is aware of this and will properly process these images even in a project that
has a MSL vertical datum.
Page 5-12 SOCET SET

5.3.2.1 Using a local geoid

You can use a local geoid instead of geoid96 for your project by completing the following steps:
1. Convert the geoid data to a format that DTM ASCII import can read: ex. x y z. See “Terrain
Import and Export,” Chapter 17 for details. * The dtm must be imported as a grid.
2. Copy the DTMs of your local geoid from your project directory to internal_dbs/
GEODETIC after import.
3. Start Project Create/Edit.
4. In the Vertical Reference section choose MSL.
5. Click on the drop-down list below MSL and you should see your local geoid listed.
6. Select your local geoid and save a new project.
If you create a project with a local geoid, you can't use “Save
As...” to save a project to a new name (copy project does not
work).
5.3.3 Execution for Create/Edit a Project

Use the following set of steps to create a project:
1. Click Project > Create/Edit Project on the main workstation window.
2. Click File > New on the Create/Edit Project window.
3. Select the coordinate system. If additional data for the coordinate system is required, a
popup window will be displayed for the entry of a project-specific reference point. See
“Coordinate Systems” on page 5-6 for more details.
4. [Optional] Select the Units (feet vs. meters) to be used within this project.
5. [Optional] Select a Vertical Reference (Ellipsoid vs. MSL).
6. [Optional] Select Datum for the project. A list of datums will appear. Choose the correct
datum.
7. [Optional] For Geographic coordinate systems only: select the XY display format. This is
not used for coordinate systems other than Geographic.
8. Enter the approximate minimum and maximum elevation, in the selected units, within the
project.
9. Click File > Save As on the Create/Edit Project window. When prompted, enter a unique
one-word name for the project. Do not use spaces (you may use underscore characters
instead).
10. Click File > Exit on the Create/Edit Project window.
SOCET SET Page 5-13

5.4 Reviewing and Editing a Project

After you create a project, you can look at it and change it using the Create/Edit Project window.
5.4.1 When to Use Edit Project

After you have created a project, you can use Create/Edit Project to do the following:
• Review a project’s parameters (coordinate system, datum, etc.).
• Change coordinate system, units, or datum. This will convert the project’s data files to
utilize the new parameters.
• Copy Data Files From One Project To Another. Create a new project that is similar to
an existing project. You have the choice of which data files to copy from the original
project to the new project.
5.4.2 Reviewing a Project

To review an existing project it must first be loaded into the Create/Edit Project. When you first
run Create/Edit Project, the project that is currently loaded in the Main Workstation is loaded in
Create/Edit Project and its parameters are displayed for you. To edit a different project, click
File > Load Project, and you will be prompted for a project to load.
After selecting a project its parameters will be displayed in the Create/Edit Project window. You
may view the project parameters without changing them and then exit by clicking File > Exit on
the main workstation window.
5.4.3 Reviewing Parameters

To display the parameters of a project, load the project from the main workstation pulldown; you
can view the project parameters in the text fields at the top of the main workstation window.
Alternatively, you can load the project into Create/Edit Project and view the project parameters
as they were entered when the project was first created. This is explained later in this chapter.
See “File Organization,” Appendix B for additional alternative. You can look directly at the
project file.
5.5 Changing Coordinates, Units, or Datums

When data (feature, terrain, ground points) is stored in a project, the data is stored in the project’s
coordinate system, units, and datum. If you convert the data to another coordinate system (or
other units, or other datum) you have three options:
• Save
• Save As
• Copying Data Files From One Project To Another
Page 5-14 SOCET SET

5.5.1 Save
Edit the project, change the coordinate system, units and/or datum), then use the Save operation.
Save must be done with caution, because if you modify the

project's units, datum, or coordinate system, then all of the
files contained within the project will have to be converted to
the new parameters.
Save is used when you want to change any of the project’s parameters. If you have modified the
project's units, datum, or coordinate system and there are files within your existing project, then
you will be informed that the project requires conversions to be performed which may be lengthy.
You are asked if you want to continue.
Also, when modifying projects, you must make sure that no one is currently using the project on
another station for you could disrupt the work they are doing. Futhermore, if you update the
project currently loaded on your main workstation, then it will be reset, and any tasks you have
associated with the main workstation's project will be terminated.
After clicking OK, the project will be saved, overwriting the original data. When conversions are
required, the project is actually rebuilt in a temporary directory adjacent to the project's directory.
You may abort the save at any time while the project is being rebuilt. When the project
conversions are completed, the temporary project is renamed to your project's name and your old
project is deleted. This implies two restrictions. One, when updating projects which will require
conversions, you must have enough disk space to hold a copy of your project. Two, you must have
write permission on all the files within the project you are updating.
See “Execution for Create/Edit a Project” on page 5-13 for steps.
5.5.2 Save As
Edit the project, change the coordinate system (or units or datum), then use the Save As operation.
Save As is used when you want to change any of the project’s parameters and want to leave all
the original data untouched. You may load a project in the Create/Edit Project, edit if desired, and
then save it to a different project name. This allows the original project to stay the same, while
creating a new copy of the project with any modifications you specified.
To save a project currently loaded in the Create/Edit Project to a different project name, click
File > Save As. You will be asked for the project name in which to save the project. The project
name you specify must not currently exist. When you select OK, another project file (.prj) and another
project data directory will be created with the specific project name.
If you are editing an existing project and there are data files (terrain files, feature files, ground
point files, etc.) within that project, then you will be asked if you want to copy the project's data
files into the new project’s data directory.
Click NO if you want an empty project for you to populate with imagery and other files. This has
the same effect as creating a brand new project as described in the Creating a Project section.
Click Yes for the option of copying all of the project data files to the new project’s data directory.
For this option the image support files will be copied, however, the image pixel files will not be
copied. They will remain in their current location, and your image support files will still reference
them at that location. The image files for all imports you perform in your new project will be
placed in the image directory that you specified for your new project.
SOCET SET Page 5-15

If you have modified an existing project's units, datum, or coordinate system, then you will be
informed that the project requires conversions to be performed which may be lengthy. You are
asked if you want to continue. If you elected to copy the project's data files, you must make sure
that there is enough disk space to hold the project files.
Unlike updating an existing project, when you save a project to a different project name, you will
be creating a new project. This means that you need not be concerned about changing a project
that you or someone else on another station is currently using.After clicking OK, the new project
will be created and saved. See “Execution for Create/Edit a Project” on page 5-13 for detailed
steps.
5.6 Copy Project

Copy Project allows you to copy data files between two existing projects. It takes into account
differences in coordinate systems and units between the source and destination projects, and
performs any necessary conversions such as resampling terrain files and feature databases. When
you copy data to/from projects that have the Units set to “feet” the Z values of the output data
may be incorrect. Copy works properly if both source and destination projects have Meters units.
The following limitations are in effect for:
• converting a project to use a different coordinate system, datum, or units.
• transferring files from one project to another.
1. When transferring files between projects, necessary conversions will be performed on the
files to allow them to conform to the destination project's attributes. The types of files that
undergo conversions are terrain files, feature databases, ground point files, and automatic
triangulation files. All other file types are copied without any modifications.
2. If you wish to run Multi-Sensor Triangulation on a project which has been converted to a
different coordinate system, you must again import the images and start the Triangulation
process from scratch. Follow this procedure:
a. Load the converted project.
b. Import the images again with camera location unknown using the same camera
calibration file and naming images exactly the same as in the original project so that
the existing IPF file names will match properly.
c. Unless the interior orientation was done on a Leica/LHS scanner, rerun interior
orientation.
d. Select the converted triangulation (ATF) file in MST for setup (same name as in the
original project).
e. Verify that the converted GPF file is named in the Setup menu (same name as in the
original project).
f. Run Exterior Initialize.
g. Run Simultaneous Solve.
3. When converting a project to use different units the user must make sure that the project's
min. and max. elevations are correct for those units, and convert them if necessary. These
fields appear on the Project Create/Edit window. Failure to set these project attributes to
appropriate values for the selected units will have several undesirable results which are
known at this time to be:
a. In ITE, terrain files will be displayed in a mono color regardless of whether the user
has selected to set levels of elevation to different colors.
b. Footprints for terrain files, images, and feature databases will not be scaled properly
when drawn.
To use Copy Project, select Project > Copy on the Main Workstation.
Page 5-16 SOCET SET

If you copy a project and you change the coordinate system (e.g. from UTM to Geographic)
certain operations (including drawing of overlay graphics) may run slowly in the new project. A
work-around is to disable the fast sensor model within the Real Time image display by adding the
following line to your <install_path>/.socet_<computer_name> file:
% -setenv DO_NOT_USE_FAST_GRAPHICS 1
OR socet_config.bat file:
% set DO_NOT_USE_FAST_GRAPHICS=1
5.6.1 When to Use Copy Project

You use Copy Project when you have data files in a project that you want to use in another project.
You can use Copy Project to convert a project from one coordinate system to another (or from
one datum to another) by creating an empty project with the desired coordinate system and datum,
then copying into it.
An alternative to Copy Project is the Save As operation under the Create/Edit Project main menu.
The Save As operation will create a new project, copy all (or a selected subset) of the original
project files into the new project, and transform the project data into the new project’s coordinate
system, units, and datum.
The Copy Project window’s selections are as follows:
File > Exit Close window
SOCET SET Page 5-17

SELECT TO
Source Project Select the project from which data files will be transferred from.You can
use the button to the right of the field to open a file list.
Destination Project Select the project to which data files will be transferred to. You can use
the button to the right of the field to open a file list.
Copy Option Determine which project files are copied.
Start Start the copy operation.
5.6.1.1 Selecting the Source and Destination Project

Before you can transfer data files, you must select a source and destination project. Both the
source and destination projects must currently exist. The source project specifies where the
project data files are to be obtained from. When you first start Copy Project the current project
on the Main Work Station is loaded as the source project by default. If you want a different project
for the source, then click Source Project button. You will then be given a list of projects to choose
from.
The destination project specifies where the project data files are to be transferred to. There is no
default for this specification. To specify the destination project, click Destination Project button.
Again, you will be given a list of projects to choose from.
5.6.1.2 Selecting the Project Data Files to Copy

Before you select the data files to copy you must first select the source project (see “Selecting the
Source and Destination Projects” in this chapter). This is because the list of files presented to you
for selection will be obtained from the source project.
When transferring files between projects, necessary conversions will be performed on most of the
files to allow them to conform to the destination project’s attributes. The types of files that
undergo conversions are terrain files, feature databases, ground point files, and triangulation
(.atf) files.
Orthophoto-based images can be transferred and viewed in other projects. However, when
transferring orthophotos to a destination project with a different coordinate system or datum, the
software does not resample the orthophoto pixel file. To achieve accuracy, you must regenerate
the transferred othophotos in the destination project. Other image types (Frame, SPOT, etc.) can
be transferred without this problem.
To transfer all the files in the source project, select Whole Project on the Copy Option menu. This
is the default setting when you first start Copy Project.
To transfer a subset of files, select one of the option buttons on the Copy Option menu (DTM,
feature, image, etc). You will be presented with a list of files to choose from. To select one file
for copying, place the cursor over the filename and press the LMB. To select more than one file,
depress the <Ctrl> key while selecting filenames using the cursor. If the <Shift> key is pressed
while selecting filenames with the cursor, a range of files will be selected.
When image support files are transferred to the destination project, the image pixel files will
remain in their current location and the image support files will reference them.
Page 5-18 SOCET SET

5.6.1.3 Starting the File Transfer

Before you can start the file transfer, you must first specify the source project, the destination
project, and the files to transfer (or the whole project). Also, there must exist sufficient disk space
in the destination project’s data directory to hold the files that were selected to transfer. To start
the transfer click Start.
If any of the files that you have selected already exist in the destination project you will be warned
and asked if it is alright to overwrite these files. You may continue or abort the transfer.
During the transfer, the names of the files being copied to the destination project will be displayed
in the status window. Also, a Percent Complete window will be displayed. You may abort the
transfer at any time by clicking Cancel on the Percent Complete window. Large terrain files and
feature databases may take considerable time to transfer because these files must be resampled to
comply with the destination project’s attributes.
5.6.2 Execution for Copying Files

Use the following steps to copy files between two existing projects:
1. Click Project > Copy on the main workstation window.
2. The source project will default to the project currently loaded in SOCET SET. If this is not
the project you want to obtain data files from, click Source Project on the Copy window.
Select the desired source project and click OK.
3. Click Destination Project on the Copy window. Select the project that you want to transfer
the data files to, then click OK.
4. Select the type of transfer you want from the Copy Option menu. If you select any option
except Whole Project you will be presented will a list of files to choose from. Select one or
more files to transfer from the list. For Whole Project, you will be automatically
transferring all data files in the source project.
5. Click Start on the Copy Project window.
6. If any of the files you selected already exist in the destination project you will be asked if
it’s alright to overwrite these files. Click Yes to continue or No to abort the transfer).
7. When the transfer is complete, you may transfer additional files by repeating steps 4
through 6. If you need to switch projects you may repeat steps 2 or 3 or both, then repeat
steps 4 thru 6 to transfer the desired data files.
8. Click File > Exit on the Copy window.
5.7 Data Review

Data Review allows you to look at the recorded data for Images, Terrains, and Features of a
project. To open this window, click Project > Data Review and choose which file type you desire.
Image Information window is displayed; however, all three window are similar.
SOCET SET Page 5-19

This sampling of Data Review windows is displaying

information with Image data file in the forefront.
The Information windows’ selections are as follows:
SELECT TO
Items List of data files available for review
Process History Past events that occurred to the file.
Object Characteristics Display detailed information about the data file selected
Print Prints the window.
Close Closes the window.
5.7.1 Execution - Data Review

1. Ensure a project is loaded and displayed on the main workstation window.
2. Click Project > Data Review > Terrain (Image or Feature) on the main workstation
window.
3. Select a Terrain (Support or Feature) file from the list provided. Information will appear in
the Process History and Object Characteristics areas of the window. If Footprints is turned
on, you may click on the footprint to bring up the same information.
Select any additional files or footprints for further viewing, or click Close to exit the window.
Page 5-20 SOCET SET

Chapter 6
Backup, Restore and Delete

Backup, Restoring, and Deletion are tools for making or
working with archived data or projects.
6.1 Overview
Backup and Restore allow you to make archive copies of a project on magnetic tape. These files
can be restored to the original system. Backup can also be transported to another system and
restored there, thus providing the user with an effective way of transporting project data from
system to system. Backup and Restore of files greater than 2 GB in size are only supported for
local drives. Know your local drives constraints before working these procedures.
Delete allows you to delete individual items in a project or an entire project.
Backup and Restore are not available on Windows platform.
6.1.1 When to Use Backup, Restore, and Delete

The Backup program is designed to:
• Backup an entire project for archive purposes.
• Backup an entire project for transfer to another system.
• Backup any part or parts of a project for archive or transfer purposes.
The Restore program is designed to:
• Restore an archived project from tape.
• Restore archived items such as DTMs, Feature Files, and Fly Throughs from tape.
• Restore items from one project into another (Warning: Both projects must use the
same coordinate system or problems will occur).
Delete is designed to:
• Delete an entire project or individual items within a project.
Delete image objects if they are not being used by other projects or support files. Before deleting
image objects, Delete will check to see if the actual image files are being shared or used by other
projects or support files.The Backup program is not designed to act as a replacement for the
normal system backup which protects the user against accidental file erasure or disk crash.
SOCET SET Page 6-1

Chapter 6 - Backup, Restore and Delete
If you wish to do backups of only the data for your project, and not the images that are in it, use
the following commands. It is recommended that you do daily backups of your data.
For UNIX, to backup just the project data:
cd <install_path>/data
tar cvf <tape_device_name> <project_name.prj>

<project_name>
To restore the project data which was backed-up as above:
tar xvf <tape_device_name>
To delete the project data directory and .prj file:
rm -rf <project_name.prj> <project_name>
6.2 Backup
Available only on UNIX.
Page 6-2 SOCET SET

The Backup window’s selections are as follows:
File > Load Project Allow you to select the project to backup from a popup menu.
File > Exit Exits Backup program.
SELECT TO
Tape Device Allow you to select the tape device where the backup will be written.
NOTE: It is required that the tape device names be no rewind/
berkeley (/dev/rmt/0bn (SUN). See “Tape Drives, CD-ROMS, and
Printers” on page D-4 for instructions on how to add tape devices
to the system.
NOTE: Remote tape drives are not supported by backup.
Add All Add all the items in the project to the list of items to backup. The names of
these items will be shown in the Backup List window.
Add Image Add an image item to the list of items to backup and displays the name of
the selected item in the Backup List window.
Add DTM Add a DTM (Digital Terrain Map) to the list of items to backup and
displays the name of the selected item in the Backup List window.
Add FDB Add a FDB (Feature Database) to the list of items to backup and displays
the name of the selected item in the Backup List window.
Add Fly Through Add a Fly Through to the list of items to backup and displays the name of
the selected item in the Backup List window.
Add Other Add a miscellaneous file (a files that’s not a Image, DTM, FDB, or Fly
Through) to the list of files to backup and displays the name of the selected
item in the Backup List window.
Backup List Window Display a list of items to backup.
Start Start the backup. All the items displayed in the Backup List window will
be backed up.
Status Box Display the status in this window.
6.2.1 Tape format

The data is written to tape in the following format:
FILE NUMBER FORMAT DESCRIPTION
File 0 ASCII Table of contents (tape header)
File 1 Tar First set of files (The Project file)
File 2 Tar Second set of files (The Project data)
File 3 Tar Third Set of files (Image information)
SOCET SET Page 6-3

FILE NUMBER FORMAT DESCRIPTION
.... Additional data for the project
EOF
6.2.2 Execution - Backup

The following steps describe how to backup files to tape:
1. Click Project > Backup to open the Backup window.
2. Click File > Load Project and a list of projects will appear. Select a project name to backup,
then click OK to dismiss the window.
3. Click the button on the right side of Tape Device field and a list of tape devices will appear.
Select a device, then click OK to dismiss the window. The list of tape devices is controlled
by the device_config_file. See “Tape Drive Specification” on page D-6 for instructions on
editing this file.
4. If you want to backup everything in the project, click All. Otherwise, go to step 5.
5. Use the “Image,” “DTM,” “FDB,” “Fly Through,” and “Other” buttons to add items to the
list of things to be backed up.
6. To remove an item from the backup list, right click on the item in the backup list. It will
turn black, then click Remove.
7. Click Start to begin the backup. The backup program starts by writing a script to perform
the backup. Then it executes this script and captures the results in a log window. The output
will also be stored in the project data directory under the name backup.log.<n> where <n>
is a number. The full name of the backup.log file is displayed in the status window of the
backup window.
8. Inspect the log window to make sure that there were no tape errors and dismiss it by
clicking File > Exit.
Only one project may be backed up per tape. If more than one
project is backed up to the same tape, data will be lost.
Page 6-4 SOCET SET

6.3 Restore
Restore allows you to restore data archived on tape by the Backup process described above.
Restore allows you to restore an entire project or individual items within the project such as
images and other data files. To open this window, click Project > Restore on the main
workstation.
Available only
on UNIX.
The Restore window’s selections are as follows:
File > Load Project Displays a popup menu that allows you to select the project to which
images and data are to be restored. This option allows selected data and
image files to be written from a Backup tape to an existing project.
NOTE: When restoring data into an existing project you must
ensure that the project coordinates systems, units and datums are
identical.
This option is NOT needed when you are restoring an entire project,
including the project name and the project file (.prj).
If the project file (.prj) is selected in the list of items to be restored, the
project file from the Backup tape will be restored to the system, and the
selected data and images will be restored to that project, not the project
selected under this option.
File > Exit Exits Restore.
SELECT TO
Tape Device Prompt you to select the tape device to be used.

NOTE: Remote tape drives are not supported by backup.
SOCET SET Page 6-5

SELECT TO
Image Location Allow you to select the image location where the image files will be
stored.
NOTE: This location will be the actual location where image files
will be restored even if the image data was backed-up from another
directory.
Item List Select any one of the listed items on the tape, and causes the item to be
restored when Start is pressed.
NOTE: If you select a project file (.prj), the selected data will be
restored into that project. Otherwise the selected data will go into
the project selected by the Project Name button.
Start Start the restoration.
6.3.1 Execution - Restore

The following steps describe how to restore files from tape:
1. Click Project > Restore to open the Restore window.
2. If you want to restore only images or data files to an existing project, select the desired
project by clicking File > Load Project. A list of projects will popup. Make your selection
by placing the curser over the selection and pressing the LMB, then click OK to dismiss the
window. All selected project data and images will be restored to this project unless you
select the project file (.prj) in the Item List. Selecting the project file (.prj) in the item
list causes all selected data to be restored to that project.
3. Click the button on the right side of Tape Device. A window will appear containing a list of
tape devices. Select the tape device you want, then click OK to dismiss the window.
4. Click the button on the right side of Image Location to select the location for the image data.
A list of image locations appears. Select an image location, then dismiss the window by
clicking OK. Image data will be restored to this location regardless of where it was located
at the time of backup. Support files will be automatically updated to point to the chosen
image location. Image location can be edited by clicking Edit Locations. After editing the
file, click File > Exit to close.
5. Select the images or project data you want to restore by selecting the appropriate item in
the Item List. To choose all files, right click and select “Select All.”
6. Start the restore by clicking Start.
7. The Destination directory window will display the full path name of the project as read
from the tape. Change the path, or if this is correct, click OK. The Overwrite Files window
will then prompt you on overwrite procedures.
8. Restore will write out a script that performs the restore, then execute it capturing the output
in a log window.
9. Inspect the log window to make sure there were no problems and dismiss it by clicking OK.
Page 6-6 SOCET SET

6.4 Delete
Delete allows you to remove an entire project or individual items within the project such as
images and other data files. When deleting files, pick a maximum of 30 files at any one time. To
open this window, click Project > Delete on the main workstation.
The Delete window’s selections are as follows:
File > Exit Exits Delete.
SELECT TO
Project Name (Optional) Causes a popup menu to appear that allows you to select the project to
delete.
Delete Entire Project Delete all project files.
Delete FDB... Select a FDB (Feature Database) to the list of items to delete and displays
the name of the selected item in the Delete List window.
Delete Image... Select an image item to the list of items to delete and displays the name of
the selected item in the Delete List window.
NOTE: On Windows OS, the image file will not be deleted if loaded
onto RT; however, all accessory files associated with that image
will be deleted.
Delete Fly Select a Fly Through to the list of items to delete and displays the name of
Through... the selected item in the Delete List window.
Delete DTM... Select a DTM (Digital Terrain Map) to the list of items to delete and
displays the name of the selected item in the Delete List window.
SOCET SET Page 6-7

SELECT TO
Delete Other... Select a miscellaneous file (a files that’s not a Image, DTM, FDB, or Fly
Through) to the list of files to delete and displays the name of the selected
item in the Delete List window
6.4.1 Execute - Delete

The following steps describe how to delete files:
1. Click Project > Delete to open the Delete window.
2. [Optional] Clicking Project Name will provide a list of projects. Select the project to
delete, then click OK to dismiss the window.
3. If you want to delete everything in the project, click Delete Entire Project. Otherwise, go
to step 4.
4. Use the “Delete Image,” “Delete DTM,” “Delete FDB,” “Delete Fly Through,” and “Delete
Other” buttons to delete individual files.
5. When questioned if you want a file deleted, click Yes to delete or No to cancel.
Page 6-8 SOCET SET

Chapter 7
Image Import and Export

Image Import and Export enable you to transfer images and
their support data into and out of SOCET SET.
7.1 Overview
This chapter is primarily divided into two section, Imports and Exports. The individual Image-
data formats are listed as follows:
IMPORTS EXPORTS
Image Import Overview Image Export/Reformat
CIB Import USGS DOQ Export
CADRG Import Fast Sensor Model
7.2 Image Import Overview

Importing an image is the most sophisticated data conversion process because (1) it usually
involves a file with a relatively large size, and (2) it must create S u p p o r t D a t a (i.e. auxiliary
data) that describes the sensor model parameters. The technique you use to import an image
depends on the type of sensor that is associated with the imagery. There are several image import
tools available:.
IMPORT TOOL DESCRIPTION
The following are other Geo-Referenced Imports that utilize the Image Import/Reformat window.
Image import/Reformat Imports imagery with an unknown sensor model
TIFF-RPC Import (IKONOS Import the IKONOS GeoTIFF with RPC text file.
GeoTIFF with RPC text)
Ortho Import Import Ortho.
GeoTIFF Import Imports GeoTIFF ortho-rectified images
USGS DOQ Import Imports the United States Geological Survey’s digital orthophoto
quadrangle product. USGS DOQ Import is described below.
SOCET SET Page 7-1

Chapter 7 - Image Import and Export
NITF Image Import Imports NITF Images which have georeferencing information in the image
header
World File Import Import the World file.
NCDRD Import Import the NCDRD file. See “NCDRD Import” on page 7-17.
Frame Import Imports a digitized version of a photograph taken by a frame camera. A

frame camera is a conventional camera with simple projective geometry.
Most cameras, including surveying cameras and reconnaissance cameras,
are frame cameras. See “When to Use Frame or Panoramic” on page 8-2.
Panoramic Import/Edit Imports a digitized panoramic aerial photo. This uses Frame Import
running in a special mode.
QuickBird/WorldView Imports DigitalGlobe QuickBird satellite data. Imports WorldView

Image Import satellite data.
IKONOS® Image Import Imports IKONOS Space Imaging. See “IKONOS® Image Import” on
page 7-8
Landsat Import Imports Landsat imagery from CD-ROM and 8mm tapes. See “Landsat
Image Import” on page 10-3.
SPOT Import Imports SPOT imagery from CD-ROM and 8mm tapes, distributed by
SPOT Image Corporation. See “SPOT Import” on page 11-4.
JERS Import Imports JERS imagery from CD-ROM and 8mm tapes, distributed by
NASDA. See “JERS Import” on page 11-9
IRS Import Imports IRS imagery from CD-ROM and 8mm tapes, distributed by
various parties. See “IRS Import” on page 11-13.
RADARSAT Import Imports RADARSAT imagery from 8 mm tapes, distributed by
Lockheed-Martin Corporation® and other distributors.
RADARSAT 2 Import Imports RADARSAT 2. See “RADARSAT 2 Import” on page 7-49
ERS Import Import ERS imagery from 8-mm tapes and disk files, distributed by
ESRIN.
CIB Import CIB is a dataset of orthophotos, made from rectified grayscale aerial
images distributed by the government.
CADRG Import Compressed ARC Digitized Raster Graphics (CADRG) Import reads
CADRG imagery from CD ROMs into SOCET SET.
FORMOSAT 2 Imports FORMOSAT 2. See “FORMOSAT 2 Import” on page 7-35
ALOS PRISM Imports ALOS PRISM. See “ALOS PRISM Import” on page 7-38
ALOS AVNIR 2 Imports ALOS AVNIR 2. See “ALOS AVNIR 2 Import” on page 7-41
EROS B Imports EROS B. See “EROS B Import” on page 7-46
TerraSAR-X Imports TerraSAR-X. See “TerraSAR-X Import” on page 7-52
ASTER Import Imports ASTER. See “ASTER Import” on page 7-55
COSMO-SkyMed Imports COSMO-SkyMed. See “COSMO-SkyMed Import” on page 7-60
PPDB, DPPDB See DataThruWay.
ADS40 Imports ADS40. See “ADS40 Image Import,” Chapter 13
Page 7-2 SOCET SET

OrbView-3 Imports OrbView-3. See “OrbView-3 Image Import,” Chapter 14
GeoEye-1 Imports GeoEye-1. See “Overview” on page 15-1
7.2.1 Data Handling Capabilities

The following table summarizes SOCET SET’s image data handling capabilities:
GEO-
FORMAT BATCH NAME IMPORT EXPORT DISPLAYABLE REF.
Sun 24-bit img_type_sunraster Y1 Y Y N

blue/green/red,
band interleaved by pixel
Sun 8-bit img_type_sunraster Y Y Y N

(0=black, 255=white)
LHS 8-bit Plain Raster img_type_helava Y Y N N
LHS 24-bit Plain Raster img_type_helava Y Y N N
TIFF img_type_tiff_tiled Y Y Y N
TIFF Tile img_type_tiff_tiled Y Y Y N
TIFF Tiled img_type_tiff_tiled_ Y Y Y N

red/green/blue, chunky
band interleaved by pixel
(“chunky” Planar
Config)
TIFF Tiled JPEG img_type_tiff_tiled_ Y Y Y N

Compressed jpeg
TIFF Compressed img_type_tiff_ Y N Y N

(LZW/Packbits) compressed
JFIF img_type_jfif Y N Y N
JPEG 2000 img_type_jpeg_2000 Y Y Y N
VITEC Tiled 8-bit img_type_vitec Y2 Y Y N
VITEC Tiled 24-bit img_type_vitec Y2 Y Y N

red/green/blue,
band interleaved by tile
Targa 8-bit img_type_targa N Y3 N N
Targa 24-bit img_type_targa N Y3 N N

blue/green/red
COT 8-bit img_type_cot N Y3 N Y
COT 24-bit img_type_cot N Y3 N Y
DGN 8-bit img_type_dgn N Y3 N Y
NITF 2.0 img_type_nitf_2.0 Y Y Y N
SOCET SET Page 7-3

GEO-
FORMAT BATCH NAME IMPORT EXPORT DISPLAYABLE REF.
NITF 2.0 JPEG img_type_nitf_2.0_ Y Y Y N

jpeg
NITF 2.1 img_type_nitf_2.1 Y Y Y N
NITF 2.1 JPEG img_type_nitf_2.1_ Y Y Y N

jpeg
NITF JPEG 2000 img_type_nitf_jpeg_ Y N Y N

2000
USGS DOQ 8-bit img_type_usgs_doq Y Y3 Y Y

3
USGS DOQ 24-bit img_type_usgs_doq Y Y Y Y
MrSid n/a Y N4 Y N
ERDAS Imagine IMG img_type_imagine Y Y Y N
Plain Raster img_type_plain_ Y Y N N

raster
1. Sun color (24 bit) images must have an even number of pixels per line to import correctly.
2.Vitec Tiled images must have 128x128 pixel tiles for import.
3.This format can only be written by the Image Export / Reformat task.
4.Available only on Windows Platform
Format For a complete description of the various image data formats, consult
Graphics File Formats by David C. Kay and John R. Levine (McGraw-
Hill).
Batch Name The “Batch Name” column refers to the keyword you use when you
perform a batch operation. See “Batch Processing - Image Export/
Reformat” on page 7-29.
Import The “Import” column refers to whether SOCET SET Data Import tasks can
read the data.
Export The “Export” column refers to whether SOCET SET Data Export tasks can
write the data using the format and image creation tasks so that
applications like Mosaic can create their output in the format.
Displayable The “Displayable” column refers to whether you can view the image
format in the Main Workstation Window.
Georeferenced The “Georeferenced” column refers to whether the format contains any
georeferencing information which is read and used by SOCET SET.
SOCET SET can display pseudocolor (color table encoded) images.

In general, SOCET SET handles images one band at a time when reading or writing. This means
that it will process 3-band images which have bands stored separately per pixel (i.e.
RRR...GGG...BBB) much more quickly than if the bands are stored adjacently (i.e. RGBRGB).
The fastest formats for 3-band images are VITec, TIFF Tiled, and NITF 2.0. Other formats will
be considerably slower.
Page 7-4 SOCET SET

7.2.2 Image Depth

The depth of an image is the number of significant bits per pixel per band. For example, an image
with a depth of 12 bits would have pixel values from 0 to 4095. SOCET SET supports image
depths from 8 to 16 bits. Only the VITEC, uncompressed NITF, NITF JPEG 2000, JPEG 2000,
TIFF, TIFF Tiled image, and ERDAS Image IMG formats support greater than 8-bit depth (two-
byte).
All SOCET SET applications input two-byte imagery, with the exception of Perspective Scenes
and Anaglyph. These applications should only be used with one-byte imagery. All SOCET SET
applications which create imagery will create two-byte imagery if the input is two-byte. Image
Export / Reformat has special processing which allows you to map two-byte images down to one-
byte. Mosaic can accept mixed one byte and two-byte imagery; see“Mosaic” on page 49-1 for
details.
When displaying two-byte imagery, you may need to click Auto Brightness / Contrast to achieve
a visually pleasing display.
The VITEC pixel file format specifies the depth in bytes not in bits. When using two-byte VITEC
images, the histogram computations assume that 12 bits are meaningful. Therefore you should
select VITEC format only for images which have a depth of 8 or 12 bits. NITF and TIFF indicate
depth in bits, and the histogram logic will use the exact bit depth.
7.2.3 Mapping-down 2-byte images

In general, it is not necessary to ever map a two-byte image down to one-byte pixels because most
SOCET SET applications work well with two-byte data. However, if you need to map-down a
two-byte image to one byte, use Image Export/Reformat. Image Export/Reformat will generate a
histogram of the input image pixels, create a look-up table to transform the data, and rewrite the
image with one byte per pixel. You must have a support file for your image before starting. If you
do not have a support file, use Image Import/Reformat to create one first.
The mapping algorithm uses a linear transformation from the lower edge of the total histogram to
the upper edge. If the histogram shape is irregular, such as having two distinct peaks, the mapping
process may not yield a cosmetically pleasing image.
7.2.4 JPEG Compression

SOCET SET supports two types of JPEG compression: JPEG DCT and JPEG 2000. NITF JPEG
2000 and JPEG 2000 use the JPEG 2000 compression algorithm; all other JPEG formats use the
DCT algorithm. JPEG 2000 accepts up to 7 bands and 8-16 bits per pixel. DCT accepts up to 3
bands and 8 bits per pixel. The DCT algorithm has a quality factor, which is a number from 0 to
100 you enter on the GUI. 0 is the lowest image quality with the highest degree of compression
and 100 is the highest image quality with the lowest image compression. JPEG 2000 is always
created with the same compression factor, but you have the option of extracting with a variable
image quality when you view the image. The quality is measured in “layers” which range from 1
to 19, and higher values will take longer to display. The default layer value is 19. If you want to
display images faster, change the variable “JPEG_2000_LAYERS” to a value less than 19 with
the Configuration Editor.
SOCET SET does not display the 16:1 and 32:1 levels of certain JPEG 2000 images because they
take an excessive time to decompress. Specifically, these are large "NPJE" images. You can
generate the levels by running Minify on the images. If you wish to force the display of these
SOCET SET Page 7-5

levels from the original file, set the variable "USE_J2K_RLEVELS" with the Configuration
Editor.
7.2.5 TIFF Images

SOCET SET can read strip, tiled, grayscale, palette color, or RGB TIFF images. Multiple band
tiled TIFF is importable in either “chunky” or “planar” planar configuration. Strip-formatted
images must have uniformly sized and sequentially stored strips. Tiled JPEG, LZW, and Packbits
compression are supported.
If you create a one band TIFF image (“img_type_tiff”), it will have grayscale format
(Photometric Interpretation = 0), except for creation by Image Map or Terrain Shaded Relief.
When you select a pseudocolor output with Image Map or Terrain Shaded Relief, the TIFF image
will have palette color (Photometric Interpretation = 3). If you create a multiple band image it
will have RGB format (Photometric Interpretation = 2) and contiguous planar configuration
(Planar Configuration = 1). SOCET SET makes the endian of the TIFF file match the platform
endian where it is being created.
Tiled TIFF images (“img_type_tiff_tiled”) are created the same as regular TIFF, except tiling will
be enabled. The tile size for output is fixed at 128. Multiple band images will be in “planar”
format (PlanarConfiguration = 2). “Planar” format tiled images will read and display the fastest
in SOCET SET. The PlanarConfiguration is irrelevant for single band images.
Chunky tiled TIFF (“img_type_tiff_tiled_chunky”) are created the same as Tiled TIFF except
they will have “chunky” planar configuration (PlanarConfiguration = 1) if they have multiple
bands. This format is more common throughout image processing software packages for color
imagery.
TIFF tiled JPEG compressed (“img_type_tiff_tiled_jpeg”) are created the same as tiled TIFF
except tiles are compressed with the JPEG algorithm. The tile size is fixed at 512.
SOCET SET can also read and write from 8 to 16 bit per sample (two-byte) TIFF images. For
reading, the bit depth is determined from the MaxSampleValue TIFF tag, if present. If this tag is
not present, the BitsPerSample TIFF tag is used. To create two-byte data. select TIFF or TIFF
Tiled format on any of the SOCET SET applications which write two-byte data as shown above.
You can utilize TIFF files with multiple image pyramid levels within one file. In this case it is
not necessary to minify the image, just perform an import and select the Support Only option.
When the image is loaded into any application, the pyramid levels will be loaded automatically.
To confirm which pyramid levels are in your image, import and load it into the Main Workstation
Window and click on the minification level button. The pyramid levels available will be reflected
there. If you need to make smaller levels of minification to fill up the pyramid, run the image
through Minification.
SOCET SET uses the upper-left corner pixel as the origin of all
minification levels. If upper-left corners are not aligned with
the same spatial coordinate in all min. levels, processing
errors will result.
7.2.6 NITF Image Import

SOCET SET has the ability to read some NITF 2.0 and NITF 2.1 images in native form.
SOCET SET currently only reads the image data in these files and ignores any other data such as
TEXT, SYMBOLS, LABELS, CGM GRAPHICS, registered extensions, etc. This data can be in
Page 7-6 SOCET SET

the file, but it will be ignored. There can be more than one image in the file, but only the first
image is handled, and the subsequent images are ignored. SOCET SET has the capability to
produce NITF files, but they have not yet been certified by the JITC.
The following defines the subset of NITF 2.0 and 2.1 image types that can be read natively in
SOCET SET:
• Version 2.0 (NITF 2.00) or Version 2.1 (NITF 2.10)
• Integer Pixel Value Type (PVTYPE = INT) ONLY
• Image Mode of any valid type
• Image Mode Band Interleaved by Row (IMODE=R) is not supported.
• 8 to 16 bits per pixel per band (NBPP = 8 to NBPP = 16)
• Compression can be UNCOMPRESSED (IC = NC) or JPEG COMPRESSED
(IC = C3) ONLY
For JPEG compressed images, Default Quantization Tables (Q1 ... µQ5) are NOT supported.
Any NITF 2.0 or 2.1 image file that conforms to these rules should be readable.
SOCET SET NITF images support greater than 3 band input and output.
You set the NITF image classification level by setting the environment variable
“NITF_FSCLAS” with the Configuration Editor.
7.2.6.1 Options
T Top Secret
S Secret
C Confidential
R Restricted
U Unclassified
SOCET SET Page 7-7

7.2.7 MrSid™ Image

SOCET SET can read Grayscale or RGB MrSid images.
In order to convert a file to MrSid format, you can use the compression applications available
from www.lizardtech.com.
The MrSid format is currently only supported for the Windows platform.
7.2.8 Large Images

SOCET SET can create large (greater than 2 gigabyte) image files on both platforms. NITF
supports large images and TIFF supports large images up to 4 gigabytes. There are no special
operations necessary to create large files in any SOCET SET application.
7.2.9 ERDAS Imagine IMG

SOCET SET can create and read ERDAS Imagine IMG images. Only unsigned 8 and unsigned
16 bit image pixels are supported. Palette color and georeferencing are not supported.
7.2.10 IKONOS® Image Import

SOCET SET can import images from the Space Imaging IKONOS satellite. These are currently
available in GeoTIFF, GeoTIFF with RPC, and NITF format. IKONOS images have up to four
spectral bands, from eight to eleven bits of resolution, and come in compressed or uncompressed
format. SOCET SET supports all formats except for 11-bit compressed NITF. IKONOS NITF
images contain the Airborne Support Data Extension (ASDE) Rapid Positioning Capability
(RPC00B) NITF Controlled Extension. This defines an eighty-term polynomial sensor model
for ground to image conversion. To import IKONOS images, use Image Import. If you have
GeoTIFF with RPC, the same eighty-term polynomial that is within the NITF is stored in an
ASCII text file located with the image (TIFF_RPC). Image Import will automatically detect and
extract the georeferencing information and create a support file for you.
7.2.10.1 Triangulating IKONOS Images

You can use the IKONOS image immediately after importing, but the accuracy may not be
acceptable for stereo viewing or mensuration. If you wish to refine the accuracy of your IKONOS
images, run Multi-Sensor Triangulation on them. See “IKONOS Images” on page 25-25 for
details.
7.3 QuickBird/WorldView Image Import

SOCET SET supports imagery from the DigitalGlobe QuickBird satellite in both Basic and
Standard types.
• Use QuickBird Import to import Basic
• Use Image Import / Reformat to import Standard
Basic products are only radiometrically corrected and sensor corrected and are modeled with a
rigorous sensor model based on satellite ephemeris data. You can order Basic products with
GeoTIFF 1.0, NITF 2.0, or NITF 2.1 images. SOCET SET is compatible with any of these.
Multispectral Basic products have red, green, blue, and near-infrared bands in a single file. You
Page 7-8 SOCET SET

can view combination of bands by using the band selection interface in the Display Utility, but
you must adjust the band selectors to 3/2/1 to visualize the true image colors. Standard Products
are resampled to a projection and modeled with an 80-term (cubic rational) polynomial. To import
a Standard product, start Image Import and select either the NITF or TIFF file you want to import.
Quickbird Standard should always import with a cubic rational sensor model provided the RPB
and TIL files are present and have the proper naming convention. The example below shows two
NITF, RPB and TIL files.
02AUG28171521-S2AS_R1C4-000000046229_01_P002.NTF
02AUG28171521-S2AS_R2C1-000000046229_01_P002.NTF
02AUG28171521-S2AS-000000046229_01_P002.RPB
02AUG28171521-S2AS-000000046229_01_P002.TIL
Be sure to de-select the Geo-referencing check box “Identity Only,” so Image Import will use the
RPC information in the NITF header or the RPB file. To verify that Image Import is creating a
cubic rational sensor model, click on the Georeferencing button and look at the farthest right
column. It should read “RPC00B”. If it does not, check your images for the proper naming.
The following are a few rules for import:
1. If you have TIF, ATT, EPH, etc in the directory, you should import using BASIC with
README.txt as input. This file contains a list of all files needed.
2. If you have TIF, RPB only use STANDARD import. The input is still RPB.txt but this list
does not contain ATT and EPH files.
3. If you have TIF file only, then you can import using Image/Reformat using the 4-corner
model. You have to type in the corner ground coordinates.
7.4 Image import/Reformat

Use Image Import/Reformat when you want to bring in these types of georeferenced imagery:
• Ortho
• GeoTIFF
• USGS DOQ
• QuickBird Standard
• IKONOS TIFF with RPC text file
• NITF
• with RPC00A/B
• with IGEOLO
• World File
• Other Orthophotos
There are individual pull-downs on the Main Workstation

Window for these, but they all start Image Import.
Also use Image Import when you want to import images into the workstation and you do not have
knowledge of the sensor model. If the image does not fit any of the above georeferenced formats
SOCET SET Page 7-9

and you need a georeferenced support file, you should use one of the other imports. See “Image
Import Overview” on page 7-1.
Image Import/Reformat does two things:
• It creates a support file
• Optionally converts the pixel file format to a file format that SOCET SET can process.
After you run Image Import, the image will be usable in a project and you can display the image
on the main SOCET SET image display.
If you choose to import with “Identity Only”, the support file that is built will not be controlled
(i.e. will not be tied to ground space). If you obtain ground control data at a later time you can
create a sensor model by running Triangulation in the Polynomial mode.
If the input pixel file is already in a format that SOCET SET accepts, then no conversion is
necessary. Refer to the chart at the beginning of this chapter to see which formats can be displayed
in the Main Workstation Window without conversion.
Image Import/Reformat is very similar to Image Export/Reformat. The difference is that you use
Import when you have a new image file (pixel file) that has not yet been imported into
SOCET SET. Import will create a support file for the image. Export/Reformat is used after you
have imported an image into SOCET SET (and you have a support file), and you want to change
the format of the image pixel file. You may want to do this, for example, before printing the image
on a printer. To obtain this window, select Preparation > Import > Image > Import/Reformat
from the main window.
Page 7-10 SOCET SET

The Image Import/Reformat window's selections are as follows:
File > Load Project Prompts you to pick a new project to import the images into (only if started
stand-alone).
File >Open Prompts you to pick input files. You may pick more than one.
Options > Plain Raster Size Starts a window to enter lines and samples for a plain raster image. You
only need to use this window when your input image is plain raster. If you
have more than one plain raster image, import them one at a time and enter
the proper number of lines and samples in this window for each one. Image
Import assumes there is one band of pixel values with eight bits of data per
pixel. You must select Image and Support and set the output format to a
displayable format to use the output image in SOCET SET.
Options > Auto Load Image When toggled on, automatically loads the first successfully imported
image from the input images list.
SOCET SET Page 7-11

Options > Auto Minify When toggled on, enables minifications of the imported images.
SELECT TO
Input Image File(s) Name the input image file(s) you selected.
Right Click Add... Pick the name of an input image file. You can pick more than one input file
BLANK SPACE name in the file selection dialog.
Right Click Delete Delete input file names from the list. You can pick more than one to delete
at a time.
Identity Only Enable/Disable when images that do not have geo-reference information in
their header or companion file are imported without geo-reference. Un-
check this button to enable input of geo-referencing data.
RPC Enable check box to ensure that RPC data is used during import of NITF
imagery (particularly NCDRD imagery), even when rigorous data also
exists in the NITF header.
Georeferencing... Open the “Geo-reference Data” window (see below).
Support File Only Use this option when your input image is already in the desired format, but
you don’t yet have a support file.
Image and Support File Specify that you want to create an output and a corresponding support file.
You need a support file in order to display the image on the workstation.
Location... Prompt you to select the disk location for output image(s).
Image Format Select the Output format of the images.
JPEG Compression Quality Enter a JPEG image compression quality value. Enter an integer from 0
(worst) to 100 (best).
Prefix: String to add before the image name for output name creation. Related to
all output images and their support files.
Suffix: String to add after the image name for output name creation. Related to all
output images and their support files.
Output Name: Display the output name in the following format:

<prefix><image_name><suffix>. Related to all output images and their
support files.
Start Start importing.
Page 7-12 SOCET SET

7.4.1 Georeference Data

The Georeference Data window's selections are as follows:
SELECT TO
Georeference table List all images selected in the “Import/Reformat” window and their
georeferencing data. Each table row contains the following columns:
image name, X and Y coordinates for four corners, and georeferencing
data source. For images with “Other” source (white background rows),
corner coordinate data is provided by the user, either by selecting a World
file or typing in the corner coordinates. At least two corner coordinates,
Upper-Left and Lower-Right, must be entered.
NOTE: To delete an image from the table, place the mouse on the
respective row and use the RMB.
NOTE: To select a World file, place the mouse on the “Other” or
“World” text and use the RMB.
Load from file... Select the ImageList file prepared in advance. The images from ImageList
will be identified and added to the table.
At pixel center Select “At pixel center” when the manually entered coordinates refer to the
center of corner pixels.
At pixel outer edge Select “At pixel outer edge” when the manually entered coordinates refer
to the outer edge of corner pixels.
Cancel Close the “Georeference Data” window without saving the data.
OK Close the “Georeference Data” window and save the data.
7.4.2 Execution - Image Import

Use these steps to import an image:
1. Load the images that you want to import onto a disk on your network.
2. Click Preparation > Import > Image > Import/Reformat on the main workstation window.
3. If you run the tool in stand-alone mode, click File > Load Project... on the Image Import/
Reformat window. Pick the project you wish to import the image(s) into. Click OK.
4. Right click Add... in the Input Image Files(s) widget and pick the input images. Select input
image(s) and right click Delete to remove it (them) from the list, if needed.
5. [Optional] Click Options > Auto Load Image to load on RT the first image converted
successfully.
6. [Optional] Click Options > Auto Minify to minify all output images.
7. [Optional] Un-check the “Identity Only” button to import all images with georeferencing
data.
8. [Optional] Click Georeferencing... to enter/edit georeferencing information or to select
additional images from an text file.
SOCET SET Page 7-13

9. [Optional] Enter georeferencing information to “Other” images by selecting a World file or

by typing in the corner coordinates.
10. [Optional] Select an Image List file.
11. [Optional] Click Location... to change the output image location.
12. [Optional] Click Image Format: option menu to change the output image format.
13. [Optional] Select JPEG Quality.
14. [Optional] Click Create Files: option menu to change “Support Only” if needed.
15. [Optional] Enter the prefix and suffix for output file(s) naming. Press Enter on your
keyboard and check the resulting name in the “Output Name:” text field.
16. Click Start to begin importing. Upon completion you may view each image as described in
the Main Workstation window chapter.
7.4.3 Format Recognition

Image Import will recognize most of the georeferenced formats automatically based on either the
internal contents of the file or by finding a companion file for the image file. You can mix
different types of images if you want. World and IKONOS TIFF / RPC use companion files. All
others use data inside the file. Image Import uses the first georeferencing information it finds to
create support information. It looks first to see if a file is TIFF, DOQ or NITF format. If the file
is TIFF, it looks for GeoTIFF and then IKONOS / RPC companion RPC file. If the file is DOQ,
it uses the internal georeferencing there. If the file is NITF, it looks for georeferencing in the
header (see below). If all the preceding identification methods fail, it looks for an World
companion file. For details on the naming conventions for companion files, refer to the specific
image descriptions below.
7.4.4 TIFF-RPC Import (IKONOS GeoTIFF with RPC text)

Some Space Imaging imagery is issued as a GeoTIFF file with a companion RPC text file. Image
Import / Reformat will automatically recognize the companion file provided it is named properly.
The RPC file must be named the same as the TIFF file, but ending with “_rpc.txt” to be
recognized. For example, if the TIFF file name is
po_73072_pan_0000000.tif
then the RPC file must be named
po_73072_pan_0000000_rpc.txt
If this is not the case, you can rename one of the files before you start Image Import / Reformat.
Page 7-14 SOCET SET

7.4.5 Ortho Import

If you have an orthophoto file with no internal georeferencing or companion file, you can enter
the corners into the Georeferencing window spreadsheet or provide corner data from a text file.
A text file has a series of lines with each line containing comma-separated values for the image,
corners, and optional identification:
<img name>, <ULX>, <ULY>, <URX>, <URY>, <LLX>, <LLY>, <LRX>,

<LRY>, <corner coordinates>, <ignored>, [image id]
(typed on one line) or it can optionally refer to a World file
<img name>,<World file>,<ignored>,[image id]
The UR and LL corners are optional and if missing, a non-rotated ortho is assumed, i.e.
URX=LRX, URY=ULY, LLX=ULX, LLY=LRY. For example to import xyz.tif as an unrotated
orthophoto with lower-left of (483148.0, 3619522.0) and upper-right of (484148.0,3618522.0),
the line would look like:
d:\xyz.tif,483148.0,3619522.0,,,,,484148.0,3618522.0,,ID_1
The image ID is placed in the support file IMAGE_ID field.

If you have a text file you can skip selecting images from the main window, bring up the
Georeferencing window and click “Load from file...”, and select your text file. If you select image
files on the main window and also select a text file, Image Import will match the corner
information from each line of the text file to an image based on the image file name.
7.4.6 GeoTIFF Import

Image Import creates an image support file based on the header information in your GeoTIFF tags
file. GeoTIFF Import imposes the following restrictions on the imagery it imports:
• The image must be an orthophoto. It can be either north-up or rotated.
• If the project you import the image into is a LSR project, then the GeoTIFF
reference system will be ignored. The GeoTIFF tags cannot have angular units
(degrees, radians...) in this case.
• If the input image reference system is not supported by SOCET SET, then the
coordinate system of the project will be used as the reference system.
• Elevation data in the input image is ignored.
• “User-defined” types of coordinate systems are not supported.
GeoTIFF is currently defined for projected (grid) and geographic coordinate systems. GeoTIFF
Import supports many of these systems; however some defined in the specification are not yet
implemented. If you see an error message while importing your GeoTIFF which says the system
is not supported, first determine what the projection system or geographic datum in the GeoTIFF
is. There is a public-domain program available on the Internet at:
ftp://ftp.remotesensing.org/pub/geotiff
which has a utility for dumping GeoTIFF headers. The GeoTIFF type may also be documented
elsewhere by the data producer.
SOCET SET Page 7-15

Once you have the projection type and if your GeoTIFF is a projected coordinate system, you
have a choice of either creating a new project which matches the projection or modifying the
internal database to include the GeoTIFF’s projection system.
To match the projection using existing projection grids, start Create / Edit Project and create a
new project which is as close as possible to the GeoTIFF’s. For example, if the GeoTIFF
projection is “PCS_NAD27_UTM_zone_11N,” create a UTM zone 11 project with the datum set
to NAD-27 using Create / Edit Project. Then import the GeoTIFF into the new project. The error
messages will still occur, but the output support file can be properly used.
You can also enter a new projection system into the internal database to match a particular
GeoTIFF image. You can add the definition of the grid to the file internal_dbs/
GEODETIC/grid_parameters. The instructions for adding a grid are at the beginning of the
file. The last line in the grid entry defines the GeoTIFF code for the projection. Look in section
6.3.3 of the GeoTIFF specification to find your grid name and put its number on the line. Finally,
create a project with this new system and import your GeoTIFF. You should not receive any error
messages after doing this.
For geographic GeoTIFF images, you can check in the internal database file internal_dbs/
GEODETIC/datum.dat to see if the geographic datum is supported. If the line in this file
corresponding to your project has a non-zero code on the end of the line, then the datum can be
used with GeoTIFF. Create a project with the datum which matches your GeoTIFF file and
perform the import. There is no provision for entering new geographic datums.
7.4.7 USGS DOQ Import

Image Import can recognize both the 1996 specification format and the previous format. USGS
DOQ Import imposes the following restrictions on the imagery it imports:
• The project you import the image into must be a UTM project, with units of meters.
Furthermore, your project datum must match the primary datum stored in the DOQ
image header.
• The input DOQ image can be either a gray-scale or color raster image, with samples
ordered from west to east, and lines ordered from north to south. Color images can
be either band sequential or band interleaved by pixel (BIP). The entire image is
stored in the one and only one image file.
• The input image reference system is UTM, with ground XY units of meters.
7.4.8 NITF Import

Image Import automatically detects and reads the type of georeferencing present in the image
header. The types of georeferencing are:
7.4.8.1 RPC00A/B
Airborne Support Data Extension (ASDE) Rapid Positioning Capability (RPC00A or RPC00B)
NITF Controlled Extension, as defined in N G A STDI-0002. This contains an eighty-term
polynomial sensor model. This is used for many Space Imaging IKONOS images.
7.4.8.2 IGEOLO
IGEOLO tags. These define an orthophoto sensor model.
Page 7-16 SOCET SET

7.4.9 World File Import

Image Import / Reformat will automatically use a World file provided it is in the same directory
as the image file and named the same, but with a “w” appended, for example, “xyz.ntf” and
“xyz.ntfw”. For TIFF, the extension “.tfw” is also acceptable, for example “xyz.tif” and
“xyz.tfw”.
7.4.10 NCDRD Import

Image Import/Reformat is used to import NCDRD images. If the “RPC” check box is selected,
the RPC information from the NCDRD images will be used, if available. Otherwise, the data for
the rigorous NCDRD sensor model will be used.
When NCDRD is selected from Preparation > Import > Images, the Image/Reformat window that
appears will have the additional option of Atmospheric Refraction under the Options pull-down
menu. When the Atmospheric Refraction option is selected, the resulting sensor model will
include the effect of atmospheric refraction.
When importing NCDRD images in batch mode, atmospheric refraction can be selected by
including the keyword atmospheric_refraction with the value yes in the settings file.
7.4.11 Batch Processing

For the purposes of batch operation, the difference between Image Import and Export is that
Import does not specify an input support file or minification level. If output support file is
specified conversion will be executed in “old” fashion and only first input file will be converted.
Batch Image Import does not support entering image corner

coordinates at this time.
COMMAND LINE:
% start_socet -single data_convert -batch -s setting_file
data_convert data_convert
KEYWORD DESCRIPTION
conversion_type convert_image_import_export
project_file File name (with full path prefix) of project file you want to import.
input_file File name (with full path prefix) of 1st input image.
NOTE: Repeat for each input image.
SOCET SET Page 7-17

KEYWORD DESCRIPTION
num_vertices (Optional) Number of vertices in bounding polygon for input image

footprint. Keyword must appear in setting file in proper order, so that
each number of vertices entry appears in the same sequential position
as its related input image.
NOTE: If specified for any input image, then must be
specified for all input images (value is zero for input images
with no bounding polygon). Input image entries can be
grouped together and the number of vertices entries can be
grouped together, or the number of vertices entries can be
intermingled with input image entries (so long as sequential
position for related entries is the same).
input_vertex_x (Optional) Input bounding polygon x coordinate (in project units).

Keyword must appear in setting file in proper order, so that each x
coordinate set (with number of vertices entries) appears in the same
sequential position as its related number of vertices.
NOTE: Repeat number of vertices times for each vertex.
Related vertices x, y and z must appear in proper sequence.
As noted for number of vertices, the vertex coordinate
entries can be grouped together or intermingled with other
setting file entries (so long as sequential position for related
entries is the same). Input vertex x, y and z must be specified
only when the related number of vertices is not zero. Format
of supplied value must agree with project coordinate format.
input_vertex_y (Optional) Input bounding polygon y coordinate (in project units).

Keyword must appear in setting file in proper order, so that each y
coordinate set (with number of vertices entries) appears in the same
sequential position as its related number of vertices. See note for
input vertex x above.
input_vertex_z (Optional) Input bounding polygon z coordinate. Keyword must

appear in setting file in proper order, so that each z coordinate set
(with number of vertices entries) appears in the same sequential
position as its related number of vertices. See note for input vertex x
above.
output_format (Optional) Output image format.
create_files (Optional) IMAGE_AND_SUPPORT or SUPPORT. The default is

IMAGE_AND_SUPPORT.
make_identity_ (Optional) Set to “YES” to create an identity support file. Set to

support “NO” to have Image Import / Reformat search for georeferencing in
the image files or companion files. Default value is “YES.”.
output_prefix (Optional) String that will be inserted before the input name for
output file name creation.
output_suffix (Optional) String that will be inserted after the input name for output
file name creation.
output_location Name of the image location from the list in <install_path>/

internal_dbs/DEVICE/location.list. This keyword is not
required when keyword create_files specifies SUPPORT.
auto_min Specify “YES” to minify all output images.
plain_raster_lines (Optional) Number of lines in input files. This field is needed only if
the input files are a plain raster.
NOTE: This data is related to all input images.
Page 7-18 SOCET SET

KEYWORD DESCRIPTION
plain_raster_samples (Optional) Number of samples in input files. This field is needed only
if the input files are a plain raster.
NOTE: This data is related to all input images.
atmospheric_ (Optional) Set to “YES” to include the effect of atmospheric

refraction refraction for the NCDRD sensor model. Default value is “NO”.
7.5 CIB Import

Controlled Image Base (CIB) Import reads CIB imagery from CD ROMs into SOCET SET. CIB
is a dataset of orthophotos, made from rectified grayscale aerial images distributed by the
government. You would use CIB Import when you have CIB data, and want to view the image in
the data set. You run CIB Import after creating a project to hold the imagery. To open this
window, click Preparation > Import > Image > CIB on the main workstation window. CIB
Import works in projects with Geographic, UTM, Grid or LSR coordinate systems.
CIB Import works slowly with tiled image format outputs. To ensure imports run faster, use an
untiled format such as TIFF or SunRaster.
The CIB Import window’s selections are as follows:
File > Load Project... Load the project to hold the output image.
File > Exit Exit CIB Image Import
Options > Auto Minify Selection for image minification
SOCET SET Page 7-19

SELECT TO
Directory Path Specify the top level of the CD-ROM.
Draw Polygon Allow user to specify the area of interest by drawing a polygon.
Select Images Select resolutions, percentage of coverage (size of interested area

compared to size of entire data on the same resolution), number of lines (in
pixels) and number of samples (in pixels) of the interested area.
Output Name, Format and location of the output image.
Start Begin the importing of CIB images.
7.5.1 Using CIB images

Before importing your data, make sure your project has an origin near the center of your CIB. It
should be in the same hemisphere for Geographic projects, or the same UTM zone for UTM
projects.
7.5.1.1 Codes And Resolutions Supported

SOCET SET imports 10, 5, 2, and 1-meter CIB imagery.
7.5.1.2 Outputs
Outputs consist of an ASCII support file and a binary image file.
7.5.2 Execution - CIB Import

Use the following sequence of steps to import a CIB image:
1. Load an image into the workstation which covers at least the area of CIB you want to
import.
If you have no imagery, the GRAPHICS_ONLY image should be used.
2. Click Preparation > Import > Image > CIB on the main workstation window to start CIB
Import.
3. Click File > Load Project. and specify the project file.
4. Click Directory Path... and navigate to the CD-ROM. Go to the “RPF” directory and select
the “A.TOC file.” You can also import from a regular disk directory. The requirement for
“RPF/A.TOC” file are the same as for CD ROM.
5. Click Draw Polygon...
6. Toggle to the extraction cursor and delineate a polygon around the area for CIB images you
want by pressing the LMB. When finished, press the RMB to accept.
7. Select one or more of the CIB resolutions you want in the “Select Images” table.
8. Click in the Output Image field and type the output image support file name. Select the
image format and location you want for your output image.
9. Click Start to import the image.
Page 7-20 SOCET SET

7.6 CIB Viewer

CIB Viewer reads CIB data from disk or CDROM and presents it in a simple viewing window.
You can use CIB Viewer instead of CIB Import if you do not need to create a permanent image
of your CIB data on disk. CIB Viewer works with 1 to 10 meter CIB resolutions and with either
compressed or uncompressed CIB data.
The CIB Viewer window’s selections are as follows:
File > Open Prompts you to select the RPF directory which contains the CIB files you
want to display.
File > Exit Exits CIB Viewer.
Help > Contents Starts the online documentation.
SELECT TO
Open File Prompts you to select the RPF directory which contains the CIB files you
want to display.
Zoom In/Out Zoom display from 512X to 64:1.
Move Left, Right, Up, Down Moves the display area to a new area on the image. Each click shifts by
about one-half of a screen.
SOCET SET Page 7-21

SELECT TO
Click on Image Displays latitude and longitude of where you clicked on the window title
bar.
7.6.1 CIB Viewer Execution

1. Click either File > Open… or (Open File) and select the RPF directory which contains
the CIB files you want to display.
2. Move around and zoom in or out to see the parts of the image you want.
3. Click File > Exit to exit CIB Viewer.
7.7 CADRG Import

Compressed A R C Digitized Raster Graphics (CADRG) Import reads CADRG imagery from CD
ROMs into SOCET SET. CADRG is a general product, comprising of computer-readable digital
maps and chart images. CADRG imagery is distributed by the government. You use CADRG
Import when you have CADRG data and you want to view the image in the data set. You run
CADRG Import after creating a project to hold the imagery. To open this window, click
Preparation > Import > Image > CADRG on the main workstation window. CADRG Import
works in projects with Geographic, UTM, Grid or LSR coordinate systems.
100 1
CADRG import works slowly with tiled image format outputs. To ensure imports run faster, use
an untiled format such as TIFF or SunRaster.
The CADRG Import window’s selections are as follows:
File > Load Project... Load the project to hold the output image.
File > Exit Exit CADRG Image Import.
Page 7-22 SOCET SET

Options > Auto Minify Selection for image minification.
SELECT TO
Directory Path Specify the top level of the CD-ROM.
Draw Polygon Allow user to specify the area of interest by drawing a polygon.
Select Images Scale, percentage of coverage (size of interested area compared to the size
of the entire data on the same scale), number of lines (in pixels) and
number of samples (in pixels) of the interested area.
Output Name, format and location of the output image.
Start Begin the importing of CADRG image.
7.7.1 Scale And Data Series Supported

CADRG imagery is supplied in a variety of scales such as:
1:5,000,000, 1:2,000,000 or 1:1,000,000
Each CADRG chart type (based on scale) has its own code & series abbreviation associated with
it. For example:
CODE SERIES ABBR. SCALE DATA SERIES
GN GNC 1:5,000,000 Global Navigation Chart
JN JNC 1:2,000,000 Jet Navigation Chart
ON ONC 1:1,000,000 Operational Navigation Chart
For a complete of CADRG scales and data series, see MIL-STD-2411-1.
7.7.2 Using CADRG images

Before importing your data, make sure your project has an origin near the center of your CADRG.
It should be in the same hemisphere for Geographic projects, or the same UTM zone for UTM
projects.
7.7.2.1 Outputs
Outputs consist of an ASCII support file and a binary image file.
7.7.3 Execution - CADRG Import

Use the following sequence of steps to import a CADRG image
SOCET SET Page 7-23

1. Load an image into the workstation which covers at least the area of CADRG you want to
import.
If you have no imagery, the GRAPHICS_ONLY image should be used.
2. Click Preparation > Import > Image > CADRG on the main workstation window to start
CADRG Import.
3. Click File > Load Project. and specify the project file.
4. Click Directory Path... and navigate to the CD-ROM. Go to the “RPF” directory and select
the “A.TOC file.” You can also import from a regular disk directory. The requirement for
“RPF/A.TOC” file are the same as for CD ROM.
5. Click Draw Polygon...
6. Toggle to the extraction cursor and delineate a polygon around the area for CADRG images
you want by pressing the LMB. When finished, press the RMB to accept.
7. Select one or more of the CADRG images you want in the “Select Images” table.
8. Click in the Output Image field and type the output image support file name. Select the
image format you want for your output image.
9. Click Start to import the image.
7.8 Image Export

Use image export applications after you have created support files and you desire to change the
format of the image pixel file or convert the georeferencing information to a format readable by
other systems. Image Export / Reformat, Orthophoto and Mosaic automatically populate the
NITF IGEOLO header when the output is NITF and create World files. Mosaic and Orthophoto
Generation create GeoTIFF when the format is enabled.To make COT, DGN, or DOQ, use Image
Export/Reformat.
7.9 Image Export/Reformat

Use this tool to convert the format of an image pixel file from one format to another or to create
georeferenced image files. The list of possible formats is listed at the beginning of this chapter.
To open this window, click Output > File Export > Image Export/Reformat on the main
workstation window.
This tool does not affect the sensor model support data.
Image Export/Reformat is very similar to Image Import/Reformat. The difference is that you use
Import when you have a new image file (pixel file) that has not yet been imported into
SOCET SET. Import will create a support file for the image. Use Export/Reformat after you have
imported an image into SOCET SET and you want to change the format of the image pixel file.
You may want to do this, for example, before printing the image on a printer.
If the output format is NITF, Export Reformat will automatically embed georeferencing
information into the NITF header. Export Reformat also automatically creates a World file for
any georeferenced image. Since World is restricted to orthophoto sensor modeling, the file will
only be perfectly accurate if your image is an orthophoto.
Page 7-24 SOCET SET

When you export an image to COT or DGN format, your seed file must have a negative or zero
origin. If your seed file has an origin of zero (0, 0, 0), Export/Reformat may report error messages
such as:
The x-axis global origin = -2147483648.0
This will cause an overflow of data in MicroStation
Therefore translating data with a x-axis global origin of -2147483647.0
Please check seed file settings
These can be safely ignored. Also, COT files have their gamma settings set to zero. You must
adjust the gamma to a different value to view the images.
If you select JPEG 2000 as the output format, you must export
the 1:1 image minification level.
SOCET SET Page 7-25

The Image Export/Reformat window’s selections are as follows:
File > Load Project Open a file dialog box to select the project that holds the image to be
exported. Once a project is selected the project name will be displayed on
the GUI title bar. The default project is the project previously loaded into
RT.
File > Exit Exits the Image Export/Reformat window.
SELECT TO
Available (Images) List of images available to the particular project.
Selected (Images) List of selected images chosen from the available list.
Adds or removes files from the selected list.
Filter Filter for multiple file selection. Highlights filenames on the panels based
on the regular expression in the line edit box.
DGN Seed File Use only in conjunction with COT or DGN in Output image format.
Output Image(s) BLANK SPACE

Location Enter directory path name, location, and format of the output image file.
Image Format Specify the output image format. Supported files are:
BLANK SPACE Vitec (Default), SunRaster, TIFF, TIFF Tiled, TIFF Tiled Chunky, TIFF
BLANK SPACE Tiled JPEG, NITF 2.0, NITF 2.0 JPEG, NITF 2.1, NITF 2.1 JPEG, Imagine,
BLANK SPACE JPEG 2000, Targa, COT, DGN, USGS DOQ, and Plain Raster.
JPEG Quality Specify the JPEG image compression quality value. Possible values are
from 0 (worst) to 100 (best). Default value is 90.
BLANK SPACE
BLANK SPACE
BLANK SPACE
Specify the prefix and suffix of the output image files.
Prefix/Suffix/Name
Output Options Create a support file for each of the exported images when checked.
Create Support File Default value is checked.
Map-down to 8 bits Convert two-byte images to one-byte per pixel image when checked.
BLANK SPACE Default value is checked.
Apply Enhancements Apply image enhancements to exported image files when checked. This is
the same action as the “Image Enhancement tool Commit to Disk.”
BLANK SPACE Default value is un-checked.
Output Min Level Specified the output image Minification Level.
BLANK SPACE 1:1, 2:1, 4:1, … 2048:1. Default value is 1:1.
Select Bands... Select the desired bands for exported files. Default is to export all bands
Page 7-26 SOCET SET

SELECT TO
NITF RPC Update This option menu only appears when the output image format is NITF
Create New NITF Creates a new NITF image populated with RPC00A and RPC00B TRE’s
Image with Updated that are generated from the input image support data. This is the default.
RPC
Copy Original NITF Copies the original input image if it is in NITF format, adding RPC00A
Image and Replace and RPC00B TRE’s that are generated from the input image support data,
RPC or replacing those TRE’s if they already exist in the original image.
Update RPC in Original For input images in NITF format with RPC00A and/or RPC00B TRE’s,
NITF Image (No Image this option replaces the existing TRE’s in the original image with updated
Created) TRE’s that are generated from the input image support data. This option
does not create a new image.
Start Start exporting the images.
7.9.1 Exporting USGS DOQ Images
When exporting USGS DOQ images, Image Export/Reformat

will associate the name of the DOQ header files with its
corresponding input file.
You will put DOQ header files in the project directory. The project directory is also where the
input support files reside. The application will read both input files from this directory. Thus you
do not have to specify a path name for DOQ header files.
An example of the naming convention for USGS DOQ files follows:
INPUT SUPPORT INPUT DOQ

OUTPUT NAME
FILES HEADER FILE
abc.sup abc.doqh <prefix>abc>suffix>.doq
xyz.sup xyz.doqh <prefix>xyz>suffix>.doq
SOCET SET Page 7-27

7.9.2 Exporting COT & DGN Images

For COT format, the input DGN file is optional.
For DGN format, the DGN file is required.
When exporting Intergraph COT or Intergraph DGN formats, you need a DGN Seed input file.
For multiple input files, Image Export/Reformat will use one seed file for all input files.
Any image can be converted to Intergraph DGN and Intergraph

COT formats; however, only orthoimages will be
georeferenced. Images exported to the NITF format are
georeferenced based on the geographic location coordinates
of the four corners of the image that are written to the NITF
image subheader.
7.9.2.1 Image Bands Selection

When exporting multi-band imagery, Image Export/Reformat will export bands in the order
specified by the user using the Band Selection GUI.
When “All Bands” is checked, the edit box is disabled and the bands will be exported with no
change. The edit box is used to change the band order of the exported images.
7.9.3 Execution - Image Export/Reformat

The steps you execute for the Image Export/Reformat tool are as follows:
1. Click Output > File Export > Image Export/Reformat on the main workstation window.
2. [Optional] Click File > Open Project on the Image Export/Reformat window. Pick the
project you wish to export the image from and click Open. Project name can be found in
the Titlebar.
3. Select one or more support file names from the Available list and move them to the Selected
list.
4. [Optional] Select the Location, Image Format and the JPEG Quality desired values.
5. [Optional] Change the output image name, by setting the Prefix and Suffix fields.
6. [Optional] Check desired options
• Create Support File
• Map-down to 8 bits
• Apply Enhancements
• Output Min Level
Page 7-28 SOCET SET

7. Click Select Bands to choose bands, then click OK.

8. Click Start to begin exporting the image. Upon completion you may view the image as
described in the Main Workstation Window chapter.
7.9.4 Batch Processing - Image Export/Reformat

For the purposes of batch operation, the difference between Image Import and Export is that
Import does not specify a support file or minification level.
COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type convert_image_import_export
input_support_ File name (with full path prefix) of input support file.
file
input_file File name (with full path prefix) of input image.
output_file File name (with full path prefix) of output image.
output_format Output image format. See “Data Handling Capabilities” on page 7-3. If
the “Export” column says “Y” then the format can be used. Use the
keyword listed in the “Batch Name” column.
output_support_ File name (with full path prefix) of output support file. A support file is
file generated only if this field is within the settings file.
project_file File name (with full path prefix) of project file.
jfif_compression_ JPEG image compression quality value. Value must be in range

quality of 0 (worst) to 100 (best). Default is 90. This field is needed
only if the output_format is JPEG, e.g.: img_type_tiff_tiled_jpeg
or img_type_nitf_2.0_jpeg.
seed_file File name (with full path prefix) of seed file for COT, DOQ, or DGN
image export.
min_level Minification level of the input image to be exported. Enter 0 for the 1:1
image, 1 for the 2:1 image, 2 for the 4:1 image, up to 11 for the 2048:1
image. This field is only needed for an export operation
(input_support_file is specified). Make sure the input_file matches this
field, e.g. if min_level is 5, the input_file should be something like
<install_path>/images/xyz.img_32.
nitf_ User-definable one-character description of the classification of the image
classification when exporting to NITF. Valid values are S (Secret), C (Confidential) and
U (Unclassified).
SOCET SET Page 7-29

KEYWORD DESCRIPTION
map_down (Optional) Set to “NO” to preserve the pixel depth of the images. Set to
“YES” to map all output images down to 8 bits per pixel per band. Default
is “YES”.
apply_ (Optional) Set to “YES” to apply enhancements you have saved for an
enhancements input images to the output image. Default is “NO”.
select_band (Optional) Set to a band to extract from the input image and place in the
output image and repeat for each band. Make the order the same as you
wish them to appear in the output image.
7.10 USGS DOQ Export

USGS DOQ Export is an option within Image Export/Reformat which exports an orthophoto to
the USGS DOQ format. The limitations on exporting a DOQ image are summarized in the
following table:
CAPABILITY LIMITATIONS
Data Ordering Data is organized by line, each line containing a series of pixels from west
to east. The order of lines is from north to south.
Imagery Bands Single-band gray-scale, color band sequential (B S Q ), and color band
interleaved by pixel (BIP). Select between BSQ and BIP by editing the
DOQ header seed file before exporting.
Elevation Data DOQ Export does not support any type of elevation data output.
Projection The orthophoto must have a UTM projection.
Radiometric Resolution Output imagery is always 8 bits per pixel.
7.10.1 Data Flow

7.10.1.1 Size, Units and Resolution of the Input Orthophoto
INPUT ORTHO DOQ HEADER

IMAGE FILE SEED FILE
USGS DOQ
EXPORT
DOQ IMAGE FILE
Before running DOQ export, you must build an orthophoto. The project you build the orthophoto
in should use the UTM coordinate system, and meters units. The datum should be NAD 83, NAD
Page 7-30 SOCET SET

27, WGS 84, WGS 72, Puerto Rico or Old Hawaiian. NAD83 is the most commonly used DOQ
datum.
DOQs are either a full quadrant (7.5 x 7.5 minutes) or a quarter quadrant (3.75 x 3.75 minutes).
The pixel resolution of a quarter quadrant should be 1.0 meter. The resolution of a full quad may
be 1.0 or 2.0 meters (2.0 is more common).
DOQ Export will automatically determine whether you are generating a full quad or quarter quad
by examining the size of the input orthophoto.
The orthophoto you input to DOQ Export must be north-up, that is, the rotation should be zero.
A DOQ must cover the entire (full or quarter) quadrant area - this is a rectangle in lat/long space
and is called the neatline. The DOQ will also contain some “padding” pixels outside the neatline.
The size of the padding is not specified, but it should range from 50 to 800 pixels on a side. You
determine this padding when you create the input orthophoto.
DOQ Export will copy the entire input orthophoto into the output DOQ. DOQ Export will not clip
the orthophoto, and it will not add any padding around the edges.
7.10.1.2 DOQ Header Seed File

Before you can export a DOQ you must create a header seed file, which contains data to be
included in the header of the exported DOQ image. You must put the seed file in the project data
directory prior to exporting. A sample header seed file is in <install_path>/
internal_dbs/MISC/doq_seed_file_template. That sample file contains comments
explaining the content and format of the file.
7.10.2 Execution - USGS DOQ Export

1. Click Output > File Export > Image Export/Reformat on the main workstation window.
2. Copy a sample header seed file from <install_path>/internal_dbs/MISC/
doq_seed_file_template into the project data directory. Edit the copy in the project
so it describes the image you are exporting. See “Exporting USGS DOQ Images” for the
naming convention.
3. Click File > Load Project on the Image Export/Reformat window. Pick the project that
contains the orthophoto you wish to export. Click OK.
4. Pick the name of the image you wish to export.
5. Select USGS DOQ from the Output Image Format option.
6. Click Start to begin exporting. Upon completion you may view the image. See “Main
Workstation Window - Full Roam,” Chapter 4 for description.
7.10.3 Batch Processing - USGS DOQ Export

COMMAND LINE:
SOCET SET Page 7-31

KEYWORD DESCRIPTION
conversion_type export_usgs_doq
project_file Full path name of project file.
input_file File name (with full path prefix) of input image file.
output_file File name (with full path prefix) of output DOQ file
doq_header_file File name (with full path prefix) of input DOQ header file.
7.11 Fast Sensor Model

SOCET SET creates rigorous sensor models when importing images. These models may be used
for all workstation operations, but in the case of satellite sensors such as SPOT or Landsat, they
may result in somewhat slower workstation performance than desired. Workstation performance
can be increased by creating a polynomial sensor model that approximates the rigorous model,
and using the polynomial sensor model instead of the rigorous one.
7.11.1 When to Run Fast Sensor Model

The most appropriate time to run Fast Sensor Model depends on whether you will triangulate the
image or not. If you are not going to triangulate the image, you should run Fast Sensor Model
immediately after importing the image. Otherwise, you should run Fast Sensor Model
immediately after Triangulation. In any case, you should run Fast Sensor Model before you
perform ATE or interactive tasks that use graphical overlays, such as ITE, Feature Extraction, or
Annotation.
To obtain this window, click Preparation > Build Fast Sensor Model on the main workstation
window.
The Fast Sensor Model window’s selections are as follows:
File > Load Project Prompts you to pick the project that contains the support file that you wish
to build the fast sensor model for.
Page 7-32 SOCET SET

File > Input Support File Prompts you to pick the support file that you wish to build the fast sensor
model for.
File > Exit Exist Fast Sensor Model.
SELECT TO
Input Support File Name the support file that you wish to build the fast sensor model for.
Output Support File Name the output fast sensor model support file.
Polynomial: BLANK SPACE

Quadratic Rational Select polynomial approximation types.
Linear Rational Select polynomial approximation types.
Cubic Non-Rational Select cubic non-rational types.
Cubic Rational Used by DPPDB and Bridge.
Multiple Polynomial Used by N G A FPE program.

Start Start building the fast sensor model.
Start At... Display the Start Batch Job window and lets you initiate the batch job.
See “Start At Jobs” on page E-3.
Fast Sensor Model creates a polynomial approximation of a rigorous sensor model. The purpose
is to speed-up certain computational-intensive workstation operations such as Automatic Terrain
Extraction, Rectification, Terrain Graphics, and Interactive Terrain Extraction.
The polynomials are:
Quadratic rational Quadratic divided by quadratic. Medium accuracy.
Linear Rational Direct linear transform (linear divided by linear).

Good for Frame imagery only. Very fast.
Cubic non-rational Medium accuracy.
Cubic Rational Cubic divided by cubic. This is used by DPPDB and

RPC. Very accurate
Multiple Polynomial Recursively divides the image into regions and fits a
separate non-rational polynomial (usually quadratic)
to each region. Most accurate of all polynomials.
Also called “Universal Sensor Model” or USMSD.
7.11.2 Execution - Fast Sensor Model

To create a fast sensor model, use the following sequence of steps:
1. Import an image. This creates a rigorous sensor model.
SOCET SET Page 7-33

2. Perform Triangulation, if desired.

3. Click Preparation > Build Fast Sensor Model on the main workstation window.
4. Select the input image (the image you imported).
5. Enter an output image (support file) name. Make sure that the output directory is the project
data directory (usually <install_path>/data/<project_name>).
6. Select a polynomial type (linear rational, quadratic rational, cubic non-rational, multiple
polynomial, cubic rational).
The multiple polynomial generally gives the most accurate

results.
7. Click Start. This will build a new support file. The image files are not altered.
8. Use the new (output) sensor in subsequent operations such as geo-positioning, rectification,
Automatic Terrain Extraction, Terrain Graphics, or Interactive Terrain Editing. All these
operations will be faster with the new polynomial sensor model than with the original
(input) sensor model (except for Frame sensor models).
9. [Optional] Click Start At... to initiate a batch process job at a later time.
7.11.3 Execution - Start Batch Job

See “Execution - Start At” on page E-7.
7.11.4 Batch Processing - Fast Sensor Model

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type export_fast_math
input_sup_file File name (with full path prefix) of input support file.
output_sup_file File name (with full path prefix) of output support file.
sensor_type Setting file keyword is in all caps and the corresponding description from
the fast sensor model GUI is in parenthesis.
RATIONAL_POLYNOMIAL (Quadratic Rational),
DIRECT_LINEAR_TRANSFORM (Linear Rational),
GENERAL_3D_POLYNOMIAL (Cubic Non-Rational),
CUBIC_RATIONAL_POLYNOMIAL (Cubic Rational),
MULTI_POLYNOMIAL (Multiple-Polynomial)
Page 7-34 SOCET SET

7.12 FORMOSAT 2 Import

FORMOSAT 2 Import reads FORMOSAT 2 imagery from disk. It places the sensor information
given in a metadata file into a compatible support file that references either the original TIFF
image file provided or a new image file of a user specified format.
Use FORMOSAT 2 Import when you want to exploit an FORMOSAT 2 image. You run
FORMOSAT 2 Import after creating a project. After importing FORMOSAT 2 image, you can
proceed with triangulation See “When to Use Triangulation” on page 25-3 and then data
extraction. Interior Orientation is not required with FORMOSAT 2 images, since the sensor is a
digital camera, resulting in a known, fixed relationship between each image pixel and the sensor
lens.
7.12.1 Inputs Required for FORMOSAT 2 Import

FORMOSAT 2 imagery is provided via a TIFF image file and a DIMAP file that contains general
sensor model information.
FORMOSAT 2 image files are produced at two different ground stations, IPC and Kiruna, each
of which has its own file naming convention. Typically a FORMOSAT 2 image data set from the
Kiruna ground station will have 2 files with names similar to the following:
MS/R2_CAT_060126165034206_1_20050402/IMAGERY.tif
MS/R2_CAT_060126165034206_1_20050402/METADATA.dim
Typically a FORMOSAT 2 image data set from the IPC ground station will have 2 files with
names similar to the following:
FS2_112386000_1A_0001_PAN.tif
FS2_112386000_1A_0001_PAN.dim
Note that the file names above are examples. The first part of the file names vary depending on
the data set, but the suffixes are the same.
SOCET SET Page 7-35

7.12.2 FORMOSAT 2 Import window
File >Load Project... Selects a project.
File > Open... Selects a DIMAP file.
File > Exit Exits FORMOSAT 2 Import.
Options > Auto Minify As last import step minifies image.
Options > Atmospheric Includes atmospheric refraction in the sensor model.

Refraction
Page 7-36 SOCET SET

SELECT TO
FORMOSAT 2 Files Identify the names of FORMOSAT 2 files. You can view information on a
file by highlighting it, right-clicking, and selecting View Info. You can add
or remove file(s) by right-clicking and selecting Add or Remove.
Output Images Copy Images.

To enable or disable copying the pixel files to a new image location.
If you disable Copy Images, the images will remain in their original
location. If you enable Copy Images, use Location to select the image
location for the new image and Format to select the format you want the
new image to be. The output image will be named based on the dataset
name found within the DIMAP file.
Edit Names Change the name of the output image or support file.
Start Begin the import process.
7.12.3 FORMOSAT 2 Execution

Use the following set of steps to import a FORMOSAT 2 image:
1. Start FORMOSAT 2 Import by clicking Preparation > Import > Image > FORMOSAT 2
on the main workstation window.
2. [Optional] To import the image into a project other than the one currently loaded on the
workstation, click File > Load Project and select the new project.
3. Click File > Open... and then select the DIMAP file(s) you want to import. DIMAP files
are named with the extension of “.dim”. You can also select files by right-clicking on the
FORMOSAT 2 Files area and selecting Add.
4. [Optional] To view a display of certain data from the header record, right-click on the
DIMAP file and select View Info.
5. [Optional] In the Output Images section, select the location to copy the pixel file(s) and the
image format. If you wish to leave the pixel files in the same location, disable Copy Images.
6. Click Start to begin importing the image(s).
7.12.4 FORMOSAT 2 Batch Processing

COMMAND LINE:
% start_socet -single sat_import -a formosat2 -batch –s setting_file
sat_import sat_import
KEYWORD DESCRIPTION
project Project file name. Select from the .prj files in the Project Directory.
input_file DIMAP file(s) you want to import. Repeat for each image you want
to import.
SOCET SET Page 7-37

KEYWORD DESCRIPTION
copy_images Set to “YES” to copy the images to an Image Location. Default is”
NO.”
image_format If copy_images is YES, this should be set to the format you wish
[Optional] for the output images. See the table in the Image Import/Export
chapter for values.
output_location If copy_images is YES, this should be set to the name of the image
[Optional] location from the list in internal_dbs/DEVICE/location.list
auto_minify Set to YES to minify the output image.
atmospheric_ (Optional) Set to "YES" to include the effect of atmospheric
refraction refraction for the sensor model. Default value is "NO".
7.12.5 FORMOSAT 2 Next Step

After you have imported a single image, you may display it in the main image window. You may
perform image enhancement operations, and you may perform annotation and geopositioning. If
you have control data, you should run Triangulation.
If you have imported a stereo image pair, you should execute Triangulation next. Even if you have
no ground control points, you must run Triangulation to perform Relative Orientation. Next you
should run Rectification in the pairwise mode, usually followed by Automatic Terrain Extraction.
7.13 ALOS PRISM Import

ALOS PRISM Import reads ALOS PRISM level 1B1 imagery from disk. It can use the image,
supplementary, and leader files to create rigorous ALOS PRISM sensor model support files, or it
can use the image and RPC files to create Rational Polynomial Coefficient (RPC) sensor model
support files. It combines three to four overlapping image strips stored in separate files into a
single image file of a user specified format.
Use ALOS PRISM Import when you want to exploit an ALOS PRISM image. You run ALOS
PRISM Import after creating a project. After importing an ALOS PRISM image, you can proceed
with triangulation See “When to Use Triangulation” on page 25-3 and then data extraction.
Interior Orientation is not required with ALOS PRISM images, since the sensor is a digital
camera, resulting in a known, fixed relationship between each image pixel and the sensor lens.
7.13.1 Inputs Required for ALOS Import

ALOS PRISM level 1B1 imagery is provided via 3 or 4 image strip files with the prefix IMG-, a
leader file with the prefix LED-, a supplementary file with the prefix SUP-, and usually, a
Rational Polynomial Coefficient file with the prefix RPC- file. Generally three such sets will be
included together—one set for the forward look direction, one set for the nadir look direction, and
one set for the backward look direction.
Typically an ALOS PRISM image data set will include a number of files in addition to those
needed for import. The ALOS level 1B1 imagery file names that are necessary for import are of
the format:
<prefix>-ALPSM<view direction><id number>-01B1___<view direction>
Page 7-38 SOCET SET

<prefix> can be IMG-01, IMG-02, IMG-03, IMG-04, IMG-05, IMG-06, IMG-07, IMG-08 (where
the number corresponds to which CCD the image file was collected by), SUP, LED, or RPC.
<view direction> can be either B, N, or F (representing Backward, Nadir, or Forward,
respectively). <id number> is a nine digit identification number. A typical group of file names is
shown below.
IMG-03-ALPSMB044052925-O1B1___B
IMG-04-ALPSMB044052925-O1B1___B
IMG-05-ALPSMB044052925-O1B1___B
IMG-06-ALPSMB044052925-O1B1___B
SUP-ALPSMB044052925-O1B1___B
LED-ALPSMB044052925-O1B1___B
RPC-ALPSMB044052925-O1B1___B
It is important not to change the names of the input files and to have all the input files in the same
directory.
7.13.2 ALOS PRISM Image Import
SOCET SET Page 7-39

File >Load Project Selects a project.
File > Open Select file(s). (Only 1 file name per group is required. The rest of the file
names can be deduced from this one.)
File > Exit Exits ALOS PRISM Image Import.

Refraction
Options > RPC Sensor Produces a RPC Sensor Model.

Model
SELECT TO
ALOS PRISM Files Identify the names of ALOS PRISM input files. You can add or remove
file(s) by right-clicking and selecting Add or Remove. You can view
information about the image by right clicking on it and selecting “View
Info”. The application needs the name of just one of the file names in an
image group. The rest of the file names can be deduced from this one.
Output Images/Edit Name View and edit the name of the output image and support files.
Output Images/Location Shows the location of the new image(s).Use the … button to the right of
the Location text box to bring up a window to select the location for the
new image.
Output Images/Format Use the Format selection box to choose the format you want the new
image(s) to be.
7.13.3 ALOS PRISM Execution

Use the following set of steps to import ALOS PRISM images:
1. Start ALOS PRISM Import by clicking Preparation > Import > Image > ALOS PRISM on
3. Click File > Open and then select the file(s) you want to import. You can also select files
by right-clicking on the ALOS PRISM Files area and selecting Add. For each image, you
need to select only one of the several files associated with it.
4. [Optional] To view a display of the product identification, scene ID, scene center
coordinates and scene time, right-click on the input file and select View Info.
5. [Optional] In the Output Images section, select the location to place the pixel file(s) and the
desired image format.
Page 7-40 SOCET SET

7.13.4 Batch Processing - ALOS PRISM Import

COMMAND LINE:
% start_socet -single sat_import -a alosprism -batch -s
setting_file
KEYWORD DESCRIPTION
project_file Project file name. Select from the .prj files in the Project Directory.
input_file Name of one of the input files needed to produce the image and
support file you want. Reuse the keyword and add a new input file
name for each additional output image, support file pair desired.
image_format The format you wish for the output images. See the table in the
[Optional] Image Import/Export chapter for values.
output_location The name of the image location from the list in internal_dbs/
[Optional] DEVICE/location.list
auto_min Set to YES to minify the output image.
rpc Import the image using an RPC sensor model.
7.13.5 ALOS PRISM Next Step

7.14 ALOS AVNIR 2 Import

ALOS AVNIR 2 Import reads ALOS AVNIR 2 level 1B1 imagery from disk. It uses the image,
supplementary and leader metadata files to create rigorous ALOS AVNIR 2 sensor model support
files. If RPC metadata files should happen to be provided, it can use the RPC metadata files to
create Rational Polynomial Coefficient (RPC) sensor model support files. It produces one or
more images from the four input image files of different spectral bands. The images it produces
have from one to four bands within them according to the user’s specification.
Use ALOS AVNIR 2 Import when you want to exploit an ALOS AVNIR 2 image. You run ALOS
AVNIR 2 Import after creating a project. After importing an ALOS AVNIR 2 image, you can
proceed with triangulation (“When to Use Triangulation” on page 25-3) and then data extraction.
SOCET SET Page 7-41

Interior Orientation is not required with ALOS AVNIR 2 images, since the sensor is a digital
7.14.1 Inputs Required for ALOS AVNIR 2

ALOS AVNIR 2 level 1B1 imagery is provided via 4 image files with the prefix IMG-, a leader
file with the prefix LED-, a supplementary file with the prefix SUP-.
Typically an ALOS AVNIR 2 image data set will include a number of files in addition to those
needed for import. The names of ALOS level 1B1 imagery files that are necessary for import are
of the format:
<prefix>- ALAV2A<id number>-01B1___
<prefix> can be IMG-01, IMG-02, IMG-03, IMG-04, (where the number corresponds to the
spectral band of the image), SUP, or LED. <id number> is a nine digit identification number. A
typical group of file names is shown below.
IMG-01-ALAV2A095694290-O1B1___
IMG-01-ALAV2A095694290-O1B1___
IMG-01-ALAV2A095694290-O1B1___
IMG-01-ALAV2A095694290-O1B1___
SUP-ALAV2A095694290-O1B1___
LED-ALAV2A095694290-O1B1___
It is important not to change the names of the input files and to have all the input files in the same
directory.
Page 7-42 SOCET SET

7.14.2 ALOS AVNIR 2 Image Import
File >Load Project Selects a project.
File > Open Select file(s). (Only 1 file name per group is required. The rest of the file
names can be deduced from this one.)
File > Exit Exits ALOS AVNIR 2 Image Import.

Refraction
Options > All Bands Produces a 4 band output image.
Options > Select Bands Brings up a window to allow custom selection of the bands to produce
output images for.
SOCET SET Page 7-43

Options > RPC Sensor Produces a RPC Sensor Model.

Model
SELECT TO
ALOS AVNIR 2 Files Identify the names of ALOS AVNIR 2 input files. You can add or remove
file(s) by right-clicking and selecting Add or Remove. You can view
information about the image by right clicking on it and selecting “View
Info”. The application needs the name of just one of the file names in an
image group. The rest of the file names can be deduced from this one.
Output Images/Edit Name View and edit the name of the output image and support files.
Output Images/Location Shows the location of the new image(s).Use the … button to the right of
the Location text box to bring up a window to select the location for the
new image.
Output Images/Format Use the Format selection box to choose the format you want the new
image(s) to be.
7.14.3 Select Specific Bands window
Page 7-44 SOCET SET

ALOS AVNIR 2 images come in 4 Visual and Near Infrared (VNIR) spectral bands. These bands
can be placed into separate images or combined into multi-band images. This window allows you
to select one or more combinations of the four bands to store in output images. A combination of
bands is specified by selecting the checkboxes corresponding to the desired bands then pressing
the Add button to the right of the checkboxes. The text display box in the lower portion of the
window displays the combinations that have been selected. A combination can be deleted by
highlighting it in the text display box then pressing the Delete or Backspace key. The entire list
can be emptied by clicking the Clear button. Output file names generated by the application will
reflect the bands in the image via a suffix such as “_b1_2”.
DISPLAYS AND
PURPOSE
CONTROLS
VNIR Nadir - check boxes Select VNIR bands to combine in one image.
VNIR Nadir - add Add selected VNIR band combination to list.
Text box Display band combinations chosen so far. To remove an entry, highlight it
and press the Delete or Backspace key.
Clear Delete all combinations displayed.
OK Approve selections and close window.
7.14.4 ALOS AVNIR 2 Execution

Use the following set of steps to import ALOS AVNIR 2 images:
1. Start ALOS AVNIR 2 Import by clicking Preparation > Import > Image > ALOS AVNIR
2 on the main workstation window.
3. Click File > Open and then select the file(s) you want to import. You can also select files
by right-clicking on the ALOS AVNIR 2 Files area and selecting Add. For each image, you
need to select only one of the several files associated with it.
4. [Optional] To view a display of the product identification, scene ID, scene center
coordinates and scene time, right-click on the input file and select View Info.
desired image format.
7.14.5 Batch Processing - ALOS AVNIR 2 Import

COMMAND LINE:
% start_socet -single sat_import -a alosavnir2 -batch -s
setting_file
SOCET SET Page 7-45

KEYWORD DESCRIPTION
project_file Project file name. Select from the .prj files in the Project Directory.
input_file Name of input file—can be IMG, SUP, or LED file. Repeat
keyword with each input file.
[Optional] Image Import/Export chapter for values.
output_location The name of the image location from the list in internal_dbs/
[Optional] DEVICE/location.list
auto_min Set to YES to minify the output image.
bands Bands to include in output image. Numerals 1 to 4 separated by
spaces. Repeat keyword for each combination of bands.
rpc Produce an RPC sensor model (If an RPC metadata file is
available)
7.14.6 ALOS AVNIR 2 next step

If you have imported overlapping images, you should execute Triangulation next. Even if you
have no ground control points, you must run Triangulation to perform Relative Orientation. Next,
you should run Rectification, usually followed by Automatic Terrain Extraction.
7.15 EROS B Import

EROS B Import reads EROS B imagery from disk. It places the sensor information given in two
input metadata files into a compatible support file that references either the original TIFF image
file provided or a new image file of a user specified format.
Use EROS B Import when you want to exploit an EROS B image. You run EROS B Import after
creating a project. After importing an EROS B image, you can proceed with triangulation See
“When to Use Triangulation” on page 25-3 and then data extraction. Interior Orientation is not
required with EROS B images, since the sensor is a digital camera, resulting in a known, fixed
relationship between each image pixel and the sensor lens.
7.15.1 Inputs Required for EROS B Import

EROS B imagery is provided via a TIFF image file, a PASS file that contains general sensor
model information, and a TQR file that contains sensor position and orientation data.
Typically an EROS B image data set contains files with names similar to the following:
MBT1-e2025393.1A.16bit.tif
MBT1-e2025393.pass
MBT1-e2025393.tqr
Page 7-46 SOCET SET

Note that file names above are examples. The first part of the file names vary depending on the
data set, but the suffixes are the same. It is important not to rename the input files and to have
all the input files in the same directory.
7.15.2 EROS B Import window
File > Open... Selects a PASS file(s).
File > Exit Exits EROS B Import.
Options > Lens Aberration Resulting Sensor Model calculates lens aberration.
SOCET SET Page 7-47

SELECT TO
EROS B Files Identify the names of EROS B files. You can view information on a file by
highlighting it, right-clicking, and selecting View Info. You can add or
remove file(s) by right-clicking and selecting Add or Remove.

new image to be. The output image will be named based on the name of the
PASS file, e.g. MBT1-2025393.sup
7.15.3 EROS B Execution

Use the following set of steps to import an EROS B image:
1. Start EROS B Import by clicking Preparation > Import > Image > EROS B on the main
workstation window.
3. Click File > Open... and then select the PASS file(s) you want to import. PASS files are
named with the extension of “.pass”. You can also select files by right-clicking on the
EROS B Files area and selecting Add.
4. [Optional] To view a display of certain data from the PASS file, right-click on the PASS
file and select View Info.
7.15.4 EROS B Batch Processing

COMMAND LINE:
% start_socet -single sat_import -a erosb -batch –s setting_file
KEYWORD DESCRIPTION
input_file PASS file(s) you want to import. Repeat for each image you want
to import.
Page 7-48 SOCET SET

KEYWORD DESCRIPTION
copy_images Set to “YES” to copy the images to an Image Location. Default is”
NO.”
image_format If copy_images is YES, this should be set to the format you wish
[Optional] for the output images. See the table in the Image Import/Export
chapter for values. However, note that SGI and SunRaster do not
work for EROS B Import.
output_location If copy_images is YES, this should be set to the name of the image
[Optional] location from the list in internal_dbs/DEVICE/location.list
7.15.5 EROS B Next Step

7.16 RADARSAT 2 Import

RADARSAT 2 Import reads RADARSAT 2 imagery from disk. It places the sensor information
given in a metadata file into a compatible support file that references either the original TIFF
image file provided or a new image file of a user specified format. Use RADARSAT 2 Import
when you want to exploit a RADARSAT 2 image. You run RADARSAT 2 Import after creating
a project. After importing a RADARSAT 2 image, you can proceed with triangulation and then
data extraction. Interior Orientation is not required with RADARSAT 2 images, since the sensor
is a synthetic aperture radar.
7.16.1 Inputs Required for RADARSAT 2 Import

RADARSAT 2 imagery is provided via one or more TIFF image files and an XML file that
contains general sensor model information. A RADARSAT 2 image data set includes one XML
file called product.xml and one to four TIFF image files with names imagery_HH.tif,
imagery_VV.tif, imagery_HV.tif, or imagery_VH.tif. The H and V portions of the image names
denote polarization of the transmitted and received radar signals. For instance, HV indicates the
signal was transmitted horizontally polarized and received vertically polarized.
7.16.2 RADARSAT 2 Import window
SOCET SET Page 7-49

File > Open... Selects an XML file.
File > Exit Exits RADARSAT 2 Import.
Options > Separate Produce separate support and image files for each polarization.
Polarizations
Options > Combine Produce one support and image file with all polarizations combined in a
Polarizations multi-band image.
Options > RPC Sensor Produce a support file for a Rational Polynomial Coefficient (RPC) sensor
Model model.
Page 7-50 SOCET SET

7.16.3 RADARSAT 2 Execution

Use the following set of steps to import a RADARSAT 2 image:
1. Start RADARSAT 2 Import by clicking Preparation > Import > Image > RADARSAT 2
3. Click File > Open… and then select the product.xml file(s) you want to import. You can
also select files by right-clicking on the RADARSAT 2 Files area and selecting Add.
product.xml file and select View Info.
SELECT TO
RADARSAT 2 Files Identify the names of RADARSAT 2 files. You can view information on a
Output Images / Copy To enable or disable copying the pixel files to a new image location.
images to If you disable “Copy images to”, the images will remain in their original
location. If you enable “Copy images to”, use Location to select the image
new image to be. The output image will be named based on the dataset
name found within the product.xml file.
7.16.4 RADARSAT 2 Batch Processing

COMMAND LINE:
% start_socet -single sat_import -a radarsat2 -batch –s
setting_file
KEYWORD DESCRIPTION
input_file Project.xml file(s) you want to import. Repeat for each image you
want to import.
image_format Format of output image(s).
SOCET SET Page 7-51

KEYWORD DESCRIPTION
output_location Location for output images.

auto_minify Whether to minify images during import.
copy_images Whether to copy images into new files.
combine_ Whether to combine multiple polarizations in a multi-band image.
polarizations
separate_ Whether to have separate support and image files for each
polarizations polarization.
rpc Whether to produce a Rational Polynomial Coefficient (RPC)

sensor model support file.
7.16.5 RADARSAT 2 Next Step

you have control data, you should run Triangulation. If you have imported a stereo image pair,
you should execute Triangulation next. Next you should run Rectification in the pairwise mode,
usually followed by Automatic Terrain Extraction.
7.17 TerraSAR-X Import

TerraSAR-X Import reads TerraSAR-X imagery from disk. It places the sensor information given
in a metadata file into a compatible support file that references either the original TIFF image file
provided or a new image file of a user specified format. Use TerraSAR-X Import when you want
to exploit a TerraSAR-X image. You run TerraSAR-X Import after creating a project. After
importing a TerraSAR-X image, you can proceed with triangulation and then data extraction.
Interior Orientation is not required with TerraSAR-X images, since the sensor is synthetic
aperture radar.
7.17.1 Inputs Required for TerraSAR-X Import

TerraSAR-X imagery is provided via one or more TIFF image files and an XML file that contains
general sensor model information. A TerraSAR-X image data set includes one XML file with a
name such as
TSX1_SAR__GEC_SE___HS_S_SRA_20070904T105011_20070904T105012.xml and one or
two TIFF image files with names such as IMAGE_HH_SRA_spot_025.tif. The H and/ or V
portions of the image names denote polarization of the transmitted and received radar signals.
For instance, HH indicates the signal was transmitted horizontally polarized and received
horizontally polarized.
7.17.2 TerraSAR-X Import window
Page 7-52 SOCET SET

File > Open... Selects an XML file.
File > Exit Exits TerraSAR-X Import.
Options > Separate Produce separate support and image files for each polarization.
Polarizations
Options > Combine Produce one support and image file with all polarizations combined in a
Polarizations multi-band image.
SOCET SET Page 7-53

7.17.3 TerraSAR-X Execution

Use the following set of steps to import a TerraSAR-X image:
1. Start TerraSAR-X Import by clicking Preparation > Import > Image > TerraSAR-X on the
3. Click File > Open... and then select the TSX1_SAR...xml file(s) you want to import. You
can also select files by right-clicking on the TerraSAR-X Files area and selecting Add.
4. [Optional] To view a display of certain data from the header record, right-click on the xml
file and select View Info.
SELECT TO
TerraSAR-X Files Identify the names of TerraSAR-X files. You can view information on a
Output Images / Copy To enable or disable copying the pixel files to a new image location.
images to If you disable “Copy images to”, the images will remain in their original
location. If you enable “Copy images to”, use Location to select the image
new image to be. The output image will be named based on the general
header found within the xml file.
7.17.4 TerraSAR-X Batch Processing

COMMAND LINE:
% start_socet -single sat_import -a terrasarx -batch –s
setting_file
KEYWORD DESCRIPTION
input_file TSX1_SAR----.xml file(s) you want to import. Repeat for each
image you want to import.
Page 7-54 SOCET SET

KEYWORD DESCRIPTION

combine_ Whether to combine multiple polarizations in a multi-band image.
polarizations
separate_ Whether to have separate support and image files for each
polarizations polarization.
7.17.5 TerraSAR-X Next Step

you have control data, you should run Triangulation. If you have imported a stereo image pair,
you should execute Triangulation next. Next you should run Rectification in the pairwise mode,
7.18 ASTER Import

ASTER Import reads ASTER imagery from disk. It takes as input an HDF (Hierarchical Data
Format) file. Each HDF file contains 15 separate images and their associated sensor model
parameters. These 15 images cover essentially the same area on earth at different frequency
bands. ASTER Import allows you to select which of these images to convert into SOCET SET
support and image files.
Use ASTER Import when you want to exploit one or more of a set of ASTER images. Run ASTER
Import after you have created a project. After importing an ASTER image, you can proceed with
triangulation, and then carry out data extraction. Interior Orientation is not required with ASTER
images, since the sensor is a digital camera, resulting in a known, fixed relationship between each
image pixel and the sensor lens.
7.18.1 Inputs Required for ASTER Import

ASTER import requires at least one level 1A HDF file produced by an ASTER processing station.
The file’s name should end in “.hdf”. A typical file name is
AST_L1A_00308132003180013_20070514165520_3754.hdf.
7.18.2 ASTER Import Window
SOCET SET Page 7-55

File > Open... Selects one or more HDF file.
File > Exit Exits ASTER Import.

Refraction
Options > Stereo Specifies as output a stereo image pair - bands 3 and 3b.
Options > VNIR Specifies as output a multi-band image with visible and near infrared
bands 1, 2, and 3.
Options > SWIR Specifies as output a multi-band image with short-wave infrared bands 4,
5, 6, 7, 8, and 9.
Page 7-56 SOCET SET

Options > TIR Specifies as output a multi-band image with thermal infrared bands 10, 11,
12, 13, and 14.
Options > Select Bands... Brings up a window to allow custom selection of which bands to produce
images for.
SELECT TO
File List Text Box Display the names of ASTER HDF files. You can view information about a
Output Images - Location Select location for output images.
Output Images - Format Select format for output images.
Output Images - Edit Names Bring up window for editing the names of output support and image files.
Status Message Text Box Display status messages.
Start Initiate the import process.
7.18.3 Select Specific Bands Window
SOCET SET Page 7-57

The ASTER image bands belong to 4 different groups. These are the VNIR (Visible Near
Infrared) Nadir group with bands 1, 2 and 3, the VNIR-B (Visible Near Infrared Backward
Looking) group with band 3b, the SWIR (Shortwave Infrared) Nadir group with bands 4, 5, 6, 7,
8, and 9, and the TIR (Thermal Infrared) Nadir group with bands 10, 11, 12, 13, and 14. Any of
the images whose bands are within the same group are similar enough with regard to pixel size
and geometry to be combined into a single SOCET SET image. If the Stereo, VNIR, SWIR, or
TIR menu options do not provide the particular combination of bands you desire, you can bring
up the Band Selection window to specify exactly what you want. A combination of bands is
specified by selecting the checkboxes corresponding to the desired bands then pressing the Add
button to the right of the checkboxes. The text display box in the lower portion of the window
displays the combinations that have been selected. A combination can be deleted by highlighting
it in the text display box then pressing the Delete or Backspace key. The entire list can be emptied
by clicking the Clear button.
SELECT TO
VNIR Nadir - Check boxes Select VNIR bands to combine in one image.
VNIR Nadir - Add Add selected VNIR band combination to list.
VNIR Backward - 3b Check Select VNIR 3 backward looking band.

box
Page 7-58 SOCET SET

SELECT TO
VNIR Backward - Add Add selected VNIR 3b band to list.
SWIR Nadir - Check Boxes Select SWIR bands to combine in one image.
SWIR Nadir - Add Add selected SWIR band combination to list.
TIR Nadir - Check Boxes Select TIR bands to combine in one image.
TIR - Add Add selected TIR band combination to list.
Text Box Display band combinations chosen so far. To remove an entry, highlight it
and press the Delete or Backspace key.
Clear Delete all combinations displayed.
OK Approve selections. Close window.
7.18.4 ASTER Import Execution

Use the following set of steps to import one or more ASTER images:
1. Start ASTER Import by clicking Preparation > Import > Image > ASTER on the main
workstation window.
2. [Optional] To import the image(s) into a project other than the one currently loaded on the
3. Click File > Open... and then select the HDF file(s) you want to import. HDF files names
include the extension of “.hdf”. You can also select files by right-clicking on the ASTER
Files area and selecting Add.
4. [Optional] To view a display of the product identification, production date, and bounding
rectangle, right-click on the HDF file and select View Info.
output image format desired.
6. [Optional] Click Options to turn off auto minification or change the default band selections.
7. [Optional] Click Edit Names to modify the names of output support and image files.
7.18.5 ASTER Import Batch Processing

COMMAND LINE:
% start_socet -single sat_import -a aster -batch –s setting_file
KEYWORD DESCRIPTION
setting_file version number (1.1)
SOCET SET Page 7-59

KEYWORD DESCRIPTION
project Project file name. Select from the .prj files in the project directory.
input_file HDF file(s) you want to import. Repeat for each file you want.
Image Import/Export chapter for values.
output_location (Optional) Location from the list in internal_dbs/DEVICE/
location.list
bands Bands to combine in one image. Use combinations of 1, 2, 3, 3b, 4,
5, 6, 7, 8, 9, 10, 11, 12, 13, and 14 separated by spaces. For more
than one combination, repeat the keyword. Example:
bands 4 5 7
bands 10 12 13
bands 3b
atmospheric_ (Optional) Set to "YES" to include the effect of atmospheric
refraction refraction for the sensor model. Default value is "NO".
7.18.6 ASTER Import Next Step

After you have imported an image, you may display it in the main image window. You can
perform image enhancement operations, and you can perform annotation and geopositioning. If
should run Rectification in the pair wise mode, and then usually continue with Automatic Terrain
Extraction.
7.19 COSMO-SkyMed Import

COSMO-SkyMed Import reads COSMO-SkyMed imagery from disk. It places the sensor
information given in an HDF5 (Hierarchical Data Format 5) file into one or more support files,
and the image or images contained in the HDF5 file into one or more image files of a user
specified format. The support files reference their corresponding output images. Use COSMO-
SkyMed Import when you want to exploit a COSMO-SkyMed image. You run COSMO-SkyMed
Import after creating a project. After importing a COSMO-SkyMed image, you can proceed with
triangulation and then data extraction. Interior Orientation is not required with COSMO-SkyMed
images, since the sensor is a synthetic aperture radar.
7.19.1 Inputs Required for COSMO-SkyMed Import

COSMO-SkyMed imagery is provided via an HDF5 (Hierarchical Data Format 5) file that
contains both image and sensor model data. There may be a single image and a single sensor
model or up to 6 images and sensor models from multiple swaths. The HDF5 file ends with the
suffix .h5.
Page 7-60 SOCET SET

7.19.2 COSMO-SkyMed Import Window
File > Open... Selects an HDF5 file with suffix .h5.
File > Exit Exits COSMO-SkyMed Import.
7.19.3 COSMO-SkyMed Execution
SOCET SET Page 7-61

Use the following set of steps to import a COSMO-SkyMed image:

1. Start COSMO-SkyMed Import by clicking Preparation > Import > Image > COSMO-
SkyMed on the main workstation window.
3. Click File > Open… and then select the HDF5 (.h5) file(s) you want to import. You can
also select files by right-clicking on the COSMO-SkyMed Files area and selecting Add.
HDF5 file and select View Info.
image format.
SELECT TO
COSMO-SkyMed Files Identify the names of COSMO-SkyMed files. You can view information on
a file by highlighting it, right-clicking, and selecting View Info. You can
add or remove file(s) by right-clicking and selecting Add or Remove.
Output Images/Location Select the image location for the new image. The output image will be
named based on the product name found within the HDF5 file unless you
change the image’s name via Edit Names
Output Images/Format Select the format you want the new image to be.
7.19.4 COSMO-SkyMed Batch Processing

COMMAND LINE:
% start_socet -single sat_import -a cosmoskymed -batch –s
setting_file
KEYWORD DESCRIPTION
project Project file name. Select from the .prj files in the project directory.
input_file HDF5 file(s) you want to import. Repeat for each image you want
to import.
image_format The format of the output images.
output_location Location for the output images.
Page 7-62 SOCET SET

KEYWORD DESCRIPTION
7.19.5 COSMO-SkyMed Next Step

After you have imported a single image, you can display it in the main image window. You can
perform image enhancement operations, and you can perform annotation and geopositioning. If
you have control data, you should run Triangulation. If you have imported a stereo image set, you
should execute Triangulation next. Next you should run Rectification in the pairwise mode,
SOCET SET Page 7-63

Chapter 8
Frame and Panoramic

Frame and Panoramic Import allow you to use digitized
camera images in SOCET SET.
8.1 Overview
Frame Import reads a digitized frame camera image or a panoramic into SOCET SET. A frame
image is a digitized version of a photograph taken by a frame or panoramic camera. A frame
camera is a conventional camera with simple projective geometry. Most cameras, including
surveying cameras and reconnaissance cameras, are frame cameras. A panoramic camera can be
imported and is modeled as a cylinder.
If the image you want to import is not a frame or panoramic image, you should use one of the
specialized image import modules for a particular type of sensor imagery import such as SPOT
or Landsat, or Image Import/Reformat (for imagery with an unknown M a t h M o d e l ).
For more information See “Frame - Advanced Sensor Model” on page 2-6.
Film Focal Plane
Frame Camera Sensor Model
Focal Length
Pointing angle of camera

is usually measured as 3
angles
ω, ϕ, κ
measured relative to a
local cartesian coordinate
system.
Ground
SOCET SET Page 8-1

Chapter 8 - Frame and Panoramic
8.1.1 When to Use Frame or Panoramic

8.1.1.1 Frame Import
Importing imagery is usually the first thing you do after creating a project.
After importing a frame image, you typically perform Interior Orientation (if it was not done
during the scanning process) and then control the image using Triangulation. After the image is
controlled, you can utilize any extraction application, such as Feature Extraction or Terrain
Extraction.
If you have corrupted or lost your frame support file, you can recover it by importing the same
way as you originally did and click Reuse when prompted that the image file exists. If you used
“Image and Support” when you originally imported, use “Image and Support” again to re-create
the support file.
Frame Import can do several things for you, some of which are:
a. Reformat or copy the input image to the standard SOCET SET directory or format (to
improve image access time)
b. Creates a support file containing the frame math model parameters; and
c. Places the image into a Project file structure so it is known to SOCET SET and is
available for subsequent tasks.
d. Minify the image to create the reduced resolution images.
To use Frame Import, you must have the input image stored as a disk file available to
SOCET SET. The input image format may be any sort of raster image; however, if you are
importing a plain-raster image, you must select the Image and Support option of Frame Import
if you wish it to be minified or displayed on Main Workstation Windows.
• If the input image file is on tape, you must copy it from tape to disk before running
Frame Import.
• If the input image is on film, you must digitize or scan the image before running Frame
Import.
8.1.1.2 Panoramic Imagery

If your frame image is a panoramic aerial photograph, you should use Panoramic Import.
Panoramic Import creates a model with compensation for sensor movement.
8.1.2 User Interface

The inputs to Frame Import include raster image files and image support data. The input image
can be of any SOCET SET supported type (See “Data Import and Export,” Chapter 16 for types)
including types from the LHS Scanner. If the format is plain raster, the first N bytes correspond
to the N pixels in the first line of the image, from upper-left to upper-right corners; the next N
bytes are the pixels in the second line, and so forth.
The image support data can consist of triangulation data (camera position, attitude, focal length),
scanned photo data (image dimensions and photo to image transformation data), camera
calibration data (camera fiducial coordinates, lens distortion data, principal point offset), and
PATB, ALBANY or BINGO triangulation results data. These may come in file formats for certain
supported input types, or may be entered by keyboard.
You should supply the name of a camera calibration file. Creating a camera calibration file is
described fully in the Utilities chapter. See “Camera Calibration Editor” on page 61-5.
Page 8-2 SOCET SET

If you are importing JPEG compressed images, move the images and support files (if any) to the
directory you will be keeping them in permanently before running Frame Import. Then import
them using the “Support Only” option. Otherwise the images will be written to the new location
as un-compressed images.
8.1.3 Orientation Angles

One of the key inputs to the frame import process is camera orientation. This is generally
expressed as three angles such as omega, phi, and kappa but may be expressed in many ways.
Frame Import allows the orientation to be imported in the following ways:
1. You enter Omega, Phi, Kappa in the camera position table. These angles are defined in the
“Manual of Photogrammetry” and are the sequential rotations from ground coordinates to
image coordinates—more on these later.
You may enter Heading, Pitch, Roll in the camera position table. These angles are
sequential rotations from ground coordinates to image. The orientation angles may be
provided in the documentation accompanying the photo. In this case you must enter the data
in the Frame Import window. If the orientation angles are not in one of the supported
formats, you must convert them.
2. The orientation angles may be included in triangulation file such as from ALBANY,
BINGO, PATB, or a plain text file. See below for the format of a text file.
3. If the orientation angles are not provided with the photo, you can have SOCET SET
compute the orientation for you automatically during the Triangulation process. To do this,
leave all entries in the Camera Position table at their default values.
4. If the orientation angles are not provided with the photo, you can estimate the camera
azimuth and obliquity by simply looking at the photo, then enter the heading and roll angles
as described below. See “Estimating the Orientation Angles” on page 8-5.
8.1.3.1 Omega, Phi, Kappa

These angles define a transformation UP or GROUND Z
from ground space into fiducial (film)
space. These angles are not as intuitive as
NORTH or GROUND Y
heading, pitch, and roll, so you should KAPPA
avoid using omega, phi, kappa unless
you have reason to use them.
The three rotations are applied in the PHI
order omega, phi, kappa. Positive values
are right-hand rotations. Omega is a OMEGA
rotation about the X (East) axis. Phi is a
EAST or GROUND X
rotation about the once rotated ground Y
axis. Kappa is a rotation about the twice
rotated ground Z axis.
These orientation angles should not be confused with the alternative image-to-ground
transformation, which may use the same notation. The following figure shows a Kappa for a
vertical image. In this case omega and phi are approximately zero.
SOCET SET Page 8-3

CAMERA X
+X,-Y
+X,+Y
-X,-Y
KAPPA
-X,+Y
GROUND X
EXAMPLE A: You have a photo taken straight down, and the fiducial X axis is toward the North-
West. The omega and phi are near zero (vertical photo) and Kappa is about 120 degrees.
8.1.3.2 Heading, Roll, Pitch

These angles define a transformation from ground space to image space (fiducial or film). The
three rotations are applied in the order heading, roll, then pitch. Heading is the azimuth angle
from ground axis Y to film axis X normally the heading of the plane). It is positive clockwise
from Y ground axis. The roll angle is about the once-rotated ground X axis (typically parallel to
the fiducial X axis) and positive values are right-hand rotations. Pitch is positive (right-hand rule)
about the twice-rotated ground Y axis.
Page 8-4 SOCET SET

Camera x or heading GROUND Y
+x,-y
+x,+y
Positive Roll Angle
-x,-y
Heading
GROUND X
-x,+y
8.1.3.3 Estimating the Orientation Angles

Consider the situation when you have a digitized frame photo and you are preparing to run the
Frame Import module. If you have the orientation angles and camera positions, then you should
enter them during Frame import in the omega, phi, kappa format, or the heading roll, pitch format.
Alternatively, you can select Unknown and solve for the angles during triangulation. As a last
resort, you can estimate the orientation angles using the following steps.
Heading - Looking at the photo camera X axis (fiducial X), estimate the heading (Red) from your
ground Y axis. The ground Y axis is normally North (000). The heading angle should be between
0-360 degrees and is estimated from North clockwise to your assumed heading. The above
diagram shows a heading of about 320°, the direction of flight.
Roll - Estimate the roll angle. Picture the photo and plane aligned in fiducial x direction. If the
plane were rolled to the right (as shown above), you have a positive roll angle. If you picture the
plane rolled to the left, you have a negative roll angle. (Roll right is with the right wing down.)
Pitch - The pitch is very hard to visualize and is usually set to zero. Pitch is again pictured as if
the plane is pitching nose down (positive) or nose up (negative).
SOCET SET Page 8-5

8.1.3.4 Examples
EXAMPLE A: You have a photo taken straight down, and the top of the photo is towards the NW.
The roll and pitch are 0, and the heading is 45 degrees.
EXAMPLE B: You have a photo obliquely taken toward the south-west. The fiducial x axis is
toward the direction of flight (north-west). The photo appears to have a heading of 320 degrees
and a roll of about 30 degrees. Pitch is zero.
8.1.3.5 Camera Mounting Angle (Panoramic only)

Mounting omega, phi, and kappa are the angles of the sensor relative to the vehicle’s direction of
flight. If all three angles are zero, the view is straight down at the center of the scan with the X
coordinate (image samples direction) of the scan oriented along the line of flight. Omega is the
left or right deflection. A sensor pointing to the left of the vehicle has a positive omega. Phi is the
forward or backward deflection. A sensor pointing behind the vehicle has a positive phi. Kappa
is the rotation in the vehicle’s horizontal plane. A sensor rotated counterclockwise has a positive
kappa.
8.1.3.6 Start and End Scan Angle (Panoramic only)

Panoramic Import requires you to enter a start and end of scan angle. These angles are used to
initialize the internal timing of the sensor model. By default, the scan direction is perpendicular
to the direction of flight, with a positive angle to the left of the platform. The values are closely
related to the interior orientation coordinates. The interior orientation must match the scan angles;
i.e. if you enter non-symmetrical scan angles, then your IO coordinates must be non-symmetrical.
For example if your start and end scan angles were 10 and 20 degrees, the interior orientation Y
coordinates would be 100 and 200. (The exact values for interior orientation depend on the
camera parameters and scan rate.)
8.1.3.7 Camera Position

You have a choice of either entering a camera position during Frame and Panoramic Import or
leaving the camera position as “unknown.” If you leave the images as unknown, you must run
Multisensor Triangulation (MST) to control the images with ground control points. To make an
image unknown with Frame Import, leave the X and Y boxes on the Camera Position / Orientation
interface at 0.0. For Panoramic Import, the default is unknown and the position will remain
unknown unless you select and fill out one of the camera position options under File > Camera
Location pulldown. You can store position values in a text file (see below) and load them into the
interface directly.
8.1.3.8 Text File Input

You can provide camera position and orientation angles for several images by creating a text file
with one line of information in it for each image. The general format for each line is:
ID X Y Z Omega Phi Kappa

ID is the name of the image file or “dsup” file with the extensions stripped off. An alternate form
is to put the strip and image number on each line:
Strip_Number Image_Number X Y Z Omega Phi Kappa

You may also omit IDs, strip and image numbers, or omega, phi, and kappa, for example:
Strip_Number Image_Number X Y Z
Page 8-6 SOCET SET

X Y Z Omega Phi Kappa
ID X Y Z
Values may be separated by spaces, tabs, or commas. Frame Import compares the values in the
highlighted rows of the table with the values in the file. When it finds a match, the values are
transferred from the file into the table. Be sure to highlight the rows you want to fill before
importing the text file. If IDs, strip numbers and image numbers are omitted in the text file, the
values from the file are placed in the highlighted rows in the order they appear in the text file.
Load your orientation text files into the application from the Frame Import window:
1. Select the Review/Edit Settings button from the Frame Import window.
2. In the Review/Edit Settings window, select the Camera Position/Orientation tab.
3. Highlight rows of imagery files listed.
4. Press the Read From File... button, and open your file. The x, y, z, Omega/Heading, Phi/
Roll, Kappa/Pitch columns in the Review/Edit Settings window will auto-populate with
data.
5. Press Close to accept.
6. Continue with frame import in the Frame Import window.
8.1.3.9 PAT-B File Input

Frame Import can read exterior orientation from PAT-B files. Make sure your frame images
(without file extension) are named the same as one of the items in the PAT-B file. For example
if your image is named "6840154.tif", the PAT-B file must contain an item such as:
6840154 0.00000000 330560.51973 3056293.28534 1348.79095
0.7797929077 0.626034537 0.001944019 0.62515213071 0.778851362241
0.050748093 0.0332841618 0.0383576955 0.998709593319
8.1.3.10 Applanix File Input

If you have an Applanix file which specifies your camera positions, you should select it with the
“Read From File...” option. If your data is from a DSS system, use the “Applanix DSS EO data”
option; otherwise use the “Applanix EO data“ option. The Applanix file is required to contain
“POS/AV Computed Data at Camera Perspective Centre”, and each line of camera data must have
exactly 11 columns. The name of each image file, without extension, must match the first column
exactly. For example, if the image name is “12345.tif”, then the first column must be “12345”. If
you choose to run Triangulation on the images, be sure to select the Applanix file in the Setup >
Advanced > Airborne GPS option.
If your Applanix EO file contains ECEF coordinates, you must import your imagery into a
geographic project. If it contains UTM coordinates, you must import into a UTM project. ECEF
files contain "ECEF" in the file name, and UTM contain “standard” in the name. You can also
open the file into a text editor and look for the words “ECEF Coordinates” or “Universal
Transverse Mercator”.
SOCET SET Page 8-7

8.1.3.11 ISAT File Input

ISAT (Intergraph’s ImageStation Automation Triangulation) can be imported into SOCET SET.
With SOCET SET project file information, the application uses the data from ISAT photo and
camera files to generate support (.sup) files. The project file used for this triangulation import
option should be in the LSR coordinate system.
The following are steps to import ISAT data into SOCET SET:
1. Select Preparation > Import > Image > Frame (the Frame Import window opens).
2. RMB at Input Images and add... images to import.
3. Set Camera Calibration to isat.cam.
4. Make sure Digital Camera is checked.
5. Click Review/Edit Settings... button.
6. At Review/Edit Settings, select images to import.
7. Select Camera Position/Orientation tab.
8. Click on Read From File and select ISAT file option.
9. Select ISAT photo file.
10. Close the Review/Edit Settings window.
11. At Frame Import window, click Start.
8.2 Frame Import
Page 8-8 SOCET SET

The Frame Import window’s selections are as follows:
File > Load Project Choose a project file (only if started in stand-alone).
File > Open Choose input image files to add to project.
File > Exit Exits the application.
Options > Auto Minify When toggled on, enables minification of the image after import.
Options > OPH/HRP Angle • Omega/Phi/Kappa

System • Heading/Pitch/Roll
Options > OPH/HRP Angle • decimal degrees

Units • radians
• grads
• deg:min:sec
Options > XY Units • decimal degrees

• meters
• feet
• deg:min:sec
• radians
Help > Contents Starts the on-line documentation
SELECT TO
(Input Images) BLANK SPACE

right click > Add... Select input images.
right click > Delete Delete highlighted input images.
(Output Images) BLANK SPACE

Support File Only/ Create just a support file or create a support file and copy the image to the
BLANK SPACE selected location.
Image and Support Create Image and support files.
File BLANK SPACE
Location Identify image location where created images will be written.
Image Format Select the output image format.
JPEG Quality JPEG quality for the output image.
SOCET SET Page 8-9

SELECT TO
(Import Settings) BLANK SPACE

Camera Calibration Select camera calibration file.
Digital Camera Select if camera is digital. Digital frame camera import does not
BLANK SPACE require subsequent Interior Orientation.
Apply atmospheric Identify corrections.
refraction correction If Yes, a flag is set True in the support file. When the support file is
BLANK SPACE used on the workstation, a refraction correction is applied to every
BLANK SPACE ground height, based on the flying height and the ground height.
BLANK SPACE If No, the flag is set False and corrections are not applied.
Apply underwater Apply underwater refraction correction when the elevation drops below the
refraction correction minimum ground elevation (estimate) set during Create Project.
Review/Edit Settings Display the Review/Edit settings GUI (see below).
Automatic Interior Starts Automatic Interior Orientation for the images that were imported.
Orientation
Start Start creation of support files or support and image files.
Start at... Create a batch settings file and starts creation of support files or support
and image files at specified time in batch mode.
8.2.1 Review/Edit Settings
Page 8-10 SOCET SET

The Review/Edit Settings window’s selections are as follows:
SELECT TO
Support Name tab Display the support name table.

• Image Name - The input image name(s)
• Support Name - The output support name(s)
Right-clicking will bring up the following context menu:
• Prefix - Set the prefix for the selected images (First select the
rows of the images you want to change)
• Suffix- Set the suffix for the selected images. (First select the
rows of the images you want to change)
NOTE: You can also edit all fields in the tables by double clicking
on the cell you want to edit and typing in a new value. The
exception is Image Name.
Camera-to-Image tab Display the Camera-to-Image table.

• Image Name - The input image name(s)
• Size (X) - Size of the image dimensions, in millimeters.
• Size (Y) - Size of the image dimensions, in millimeters.
• Lines - Image lines.
• Samples - Image samples.
• Orientation - Image orientation (1-8)
Right-clicking will bring up the following context menu:
1. +x right
2. +x up
3. +x left
4. +x down
5. +x mirror right
6. +x mirror up
7. +x mirror left
8. +x mirror down
Selecting 1-8 will set the orientation for the selected images.
SOCET SET Page 8-11

SELECT TO
Camera Position/Orientation Display the Camera position/orientation table.

tab Image Name - The input image name(s).
Strip ID - The ID of the strip containing the current image.
Image ID - The ID of the current image.
X,Y,Z - the sensor XYZ positions of the current image
NOTE: Leave X and Y set to 0.0 to make your image have unknown
position.
omega/heading, phi/roll and kappa/pitch - The sensor omega, phi and
kappa values of the current image.
Clicking RMB will bring up the following context menu:

Strip/Image ID from name - Set the Strip/Image ID from selected
image names. (Determine if a strip ID is present based on whether
underscores are found in the name).
When values for XYZOPK are read from a text file, full floating point
accuracy (about 15 significant digits) is used.
When this tab is selected, the Read From File... and Clear All Values
buttons appear at the lower left corner of the tab display. If you press the
Read From File... button, a list of text file types that contain exterior
orientation data pops up. The text file types listed are: ALBANY file,
BINGO file, PATB file (left-handed), PATB file (right-handed), PATB file
(right-handed 180 kappa), Text file, Socet Set GPS file, Applanix EO data,
Applanix DSS EO data, and ISAT file.
Close Close the window.
Page 8-12 SOCET SET

8.2.2 Editing Multiple Table Fields

To edit multiple fields at once follow these steps:
1. Press the LMB with the cursor on the first row.
2. <Shift> LMB on the last row (be sure to click on the appropriate column for the parameter
you want to edit - ex. omega)
3. Type in new value in the last cell selected.
4. Press enter on the keyboard.
You can also use <Ctrl>LMB to select non-sequential rows.
8.2.3 Digital Camera

When the operator selects the digital camera button on the frame import window, the following
occurs:
1. The “Camera-to-Image” information for the Size(X) and Size(Y) gets set to that of the DSS
imagery.
2. The “Camera-to-Image Orientation” of the X camera axis gets set to that of DSS imagery.
3. The operator can change the Camera-to-image Size(X), Size(Y), and Orientation, if
desired. The Size(X) and Size(Y) are computed by the user from the digital image pixel size
in mm times the number of samples and lines in the image, respectively.
4. SOCET SET determines the IO of the frame camera based on Size(X), Size(Y), and
Orientation.
8.2.4 Execution - Frame Import

The following paragraphs contain two example sequences to follow for Frame Import. The first
is for importing a generic image type, with all support data entered by keyboard. The second is
for importing a LHS scanned image with ALBANY triangulation file.
8.2.4.1 Import Generic Image

1. Load the image file to be imported onto the workstation disk in the Import Image directory.
2. Click Preparation > Import > Image > Frame on the main workstation window.
3. [Optional] If you want to import the image into a different project from the one currently
loaded on the workstation, click File > Load Project on the Frame Import window. Choose
a project file and click OK. If the project you want to import the image into hasn’t been
created yet, you must use Create Project first to create a project.
4. Right click Add...in the Input Image box. Choose one or more image files and click Open.
5. Click Review/Edit Settings.
6. Select the Camera-to-image tab.
7. Enter values for the Image Size: number of Lines, and number of Samples per line (if not
filled in automatically).
8. Select the Camera position/orientation tab.
9. Enter the sensor position in the appropriate columns, then click Close.
SOCET SET Page 8-13

10. [Optional] Select the Image and Support File Radio button. Change the Output Image
location by clicking Location and choosing a file location from the File Location window.
Click OK. The format can be changed by clicking the format name.
11. [Optional] Select the Image Format and JPEG Quality desired.
12. The default Camera Calibration file can be changed by clicking Camera Calibration on the
Frame Import/Edit window. Select another file, and click OK.
13. [Optional] Set the Apply Atmospheric Refraction and/or Auto Minify options to No.
14. Click Start to begin importing.
8.2.4.2 Import LHS Scanner Image/ALBANY Pre-triangulation

1. Load these three files from the LHS Scanner onto the workstation disk in the Import
directory: image file (.d); support data file (.dsup) and ALBANY file (.opm).
Skip this step if the LHS scanner disk is mounted via Network
File System. Ask your System Administrator.
2. Click File > Load Project on the main workstation window. Choose a project file and click
OK.
3. Click Preparation > Import > Image > Frame
4. Right click Add... in the Input Image box. Choose one or more .dsup image files and click
OK.
5. Only the support file is selected. Frame Import locates the image file using the base name
of the support file. Therefore, the image file and the support file must have the same base
name and must be located in the same directory.
6. Change the Output File’s option, location, and format to values you want.
If you select Support only, your image must be in a directory

listed in the Image Location list. See “Customizing Your
Software Configuration,” Appendix D for details on updating
the list.
7. Click Review/Edit Settings.

8. Select the Camera position/orientation tab.
9. Enter the Strip ID and Image ID for each image (they have to match with the data in the
Albany file).
10. Select all table rows, then click Read From File and select ALBANY File.
11. Select the appropriate Albany file and click OK, then click Close.
12. Set the Output Files option to Image and Support. You may choose Support Only, but use
caution. A LHS scanner support file may refer to an image type not supported by
SOCET SET. If SOCET SET cannot display the image after you import it, try re-importing
it with the Output Files option set to Image and Support.
Page 8-14 SOCET SET

8.2.5 Batch Processing - Frame Import

COMMAND LINE:
% start_socet -single multi_frame -a frame -batch -s

setting_file
multi_frame multi_frame
KEYWORD DESCRIPTION
project Project filename (with full path prefix, select from the .prj files in
<install_path>/data).
cam_calib_filename Camera Calibration file name (with full path prefix).
create_files Specifies that only a support file will be created “SUPPORT” or image and
support files will be created “IMAGE_AND_SUPPORT”
atmos_ref None: “0”

Apply Atmospheric Refraction: “1”
Apply Underwater Refraction: “2”
Both: “3”
auto_min Auto minify “YES” or “NO.”
digital_cam Digital Camera “YES” or “NO”
input_image_filename Input image filename (with full path prefix).

NOTE: Repeat this entry for each input image.
output_format See the chart in the Image Import/Export chapter for values. If the
“Export” column says “Y” then the format can be used. Use the keyword
listed in the “Batch Name” column.
jpeg_quality JPEG quality for the output image.

output_name Name of the output support file. Specify a name only, not a full path, e.g.
“abc.”
prefix Prefix to be used for the output support name.

suffix Suffix to be used for the output support name.


internal_dbs/DEVICE/location.list.
cam_loc_ang_sys Camera location input angle system: Omega, Phi, Kappa: “OPK” or
Heading, Roll, Pitch: “HRP.”
cam_loc_ang_units Camera location Angle Units: “UNIT_DEGREES,” “UNIT_RADIANS,”

“UNIT_GRADS” or “UNIT_DDMMSS.”
SOCET SET Page 8-15

KEYWORD DESCRIPTION
cam_loc_xy_units Specifies the units for entered va lues (X,Y) or (Easting, Northing) or (Lat,
Long): “UNIT_FEET,” “UNIT_DEGREES,” “UNIT_METERS,” or
“UNIT_RADIANS.”
cam_loc_focal Camera Focal Length in mm.

cam_loc_y_or_lat Camera Y or Lat entered in the project ground coordinate system.

cam_loc_x_or_lon Camera X or Lon entered in the project ground coordinate system.

cam_loc_elev Camera elevation entered in the project ground coordinate system.

cam_loc_omega Camera location in omega or heading units.

cam_loc_phi Camera location in phi or roll units.

cam_loc_kappa Camera location in kappa or pitch units.

img_size_lines Image size: lines in pixels.

img_size_samps Image samples: in pixels per line.

sizex Size of the image dimensions, in millimeters.

sizey Size of the image dimensions, in millimeters.

orientation Image orientation (1-8)

strip The ID of the strip containing the current image.

image_id The ID of the current image.

8.3 BINGO Frame Import

BINGO Frame uses the interface as Frame Import. BINGO software is ideally suited for the
adjustment of large blocks of Frame images.
If the final desired mapping coordinate system is Geographic, it is recommended to first perform
image import and triangulation under an interim Project using a coordinate system such as UTM.
Then a new Project with Geographic coordinate system is created after and the contents of the
interim project are then copied into the new project using the Project Copy functionality in
SOCET SET.
Page 8-16 SOCET SET

Another difference exists in the use of the attitude data ingested during image import. Although
the BINGO Frame import module behaves in exactly the same manner as the Frame Import
module, the input attitude values are applied in the sequence phi-omega-kappa in the BINGO
Frame sensor model instead of the usual omega-phi-kappa sequence in the Frame sensor model.
Provided the attitude data are appropriate for the target sensor type, how the data is input into the
two import modules should be the same from the point of view of the user.
See “Camera Calibration Editor” on page 61-5 for additional information on BINGO.
8.4 Panoramic Import/Edit
The Panoramic Import/Edit window’s selections are as follows:
File > Load Project... Prompts you to choose a project file (only if started stand-alone).
File > Input Image Selects the input support file and image file.
Helava... Specifies that the input support file and image file are in LHS DSW-100
BLANK SPACE Scanner format. Displays a file selection window to select the support file.
TIES Image... Specifies that the input support file and image file are in TIES format.
BLANK SPACE Displays a file selection window to select the TIES support file.
Other... Specifies that input image is an unsupported format. The Review/Edit
Support window prompts you to enter the image support data.
SOCET SET Page 8-17

File > Load Support File Loads a support file for editing. The Fiducial data and the camera location
data may be changed. The interior orientation and triangulation data are
updated.
File > Exit Closes Panoramic Import/Edit.
Options > Auto Minify When toggled on, enables minification of the image after import.
Options > Auto Load When toggled on, the image you import will be loaded on the Main
Workstation Window after import.
Review/Edit > Photo Data Displays a window containing the image support data. You may review or
edit the data.
Review/Edit > Camera Data Displays a window containing camera support data. You may review or
edit the data.
Review/Edit > Date of Photo Displays a window to enter the date and time of the photo.
SELECT TO
Input Image Indicate the name of the input support file. The actual image name is
displayed when the image is of type “Other.”
Output Image Identify the name, location, and format of the output pixel file.
Page 8-18 SOCET SET

SELECT TO
Camera Location Reflect your choice of camera location: Unknown, Albany, BINGO, PATB
BLANK SPACE file or Enter Data.
Unknown Default. Specifies that the camera location parameters are unknown. After
BLANK SPACE you import the image, you must run Triangulation to generate an image
support file from ground control points (GCPs).
BLANK SPACE
BLANK SPACE
Albany
Choose the ALBANY triangulation file. The file is a result of triangulation
BLANK SPACE for a block of photos that has been performed outside of SOCET SET, using
BLANK SPACE ALBANY. The ASCII file contains two lines of data for each photo in this
BLANK SPACE order: line one has strip number (integer), photo number (integer), an integer
BLANK SPACE number (which is ignored during import), the three coordinates of the camera
position in the project units (floating point), and the focal length in
BLANK SPACE millimeters (floating point). The second line contains the strip number
BLANK SPACE (integer), photo number (integer), an integer number (which is ignored) and
BLANK SPACE the three camera angles omega, phi, and kappa, in grads units (floating
BLANK SPACE point). The ALBANY file is assumed to be located in the default Import
BLANK SPACE directory.
BLANK SPACE NOTE: Camera location data from PATB, BINGO, or ALBANY is only
compatible for importing in LSR or LSR with earth curvature
BLANK SPACE projects. If you used earth curvature correction in ALBANY, BINGO,
BLANK SPACE or PATB, you should use LSR with earth curvature during project
BLANK SPACE create.
BINGO Choose the BINGO triangulation file. The file is a result of triangulation for
BLANK SPACE a block of photos that has been performed outside of SOCET SET using
BLANK SPACE BINGO. The ASCII file contains one line of data for each photo in this
BLANK SPACE order: designation (string), photo number (integer), the three coordinates of
the camera position in the project units (floating point), the three camera
BLANK SPACE angles phi, omega, and kappa, in grads units (floating point), and the camera
BLANK SPACE number (integer), which is ignored. The BINGO file (usually “itera.dat”) is
BLANK SPACE assumed to be located in the default Import directory.
BLANK SPACE
PATB (Left-Handed) Choose the PATB triangulation file. The file is a result of triangulation for a
BLANK SPACE block of photos that has been performed outside of SOCET SET, using
BLANK SPACE PATB. The ASCII file contains the following data for each photo, in this
order: the photo number (integer), a floating point number (which is ignored
BLANK SPACE during import), the three coordinates of the camera position in the project
BLANK SPACE units (floating point), and 9 numbers which define the rotation matrix
BLANK SPACE (floating point). The PATB file is assumed to be located in the default Import
BLANK SPACE directory. The left-handed option indicates that the camera position and
rotation matrix data in the file is from a left-handed coordinate system. It
BLANK SPACE will be converted to a right-handed coordinate system upon import.
BLANK SPACE Choose the PATB triangulation file. The file description is the same as above
PATB (Right- for PATB file (left-handed), except in this case the data in the PATB file is
Handed) from a right-handed coordinate system.
Enter Data Specify that input triangulation data is in an unsupported format. Prompts
you to manually enter the camera parameters.
Camera Calibration Indicate the name of the camera location and calibration file you chose.
Location Provide camera location formats.
Calibration Choose the camera calibration file. The camera calibration file contains lens
distortion and fiducial coordinate information.
Apply Atmospheric Identify corrections.

Refraction - Yes, No If Yes, a flag is set True in the support file. When the support file is used
on the workstation, a refraction correction is applied to every ground
height, based on the flying height and the ground height.
If No, the flag is set False and corrections are not applied.
SOCET SET Page 8-19

SELECT TO
Sensor Type Select Airborne or Orbiting modes for the sensor.
Output Identify the name, location, and format of the output file.
Start Start creation of support file or support and image files.
8.4.1 Photo Data Window
You only need to enter this data when the image is of type
“Other.”
The Photo Data window’s selections are as follows:
SELECT TO
Upper-Left Coord. x, y Identify the photo coordinates of the upper-left corner of the image (first
line, first sample) in millimeters.
Lower-Right Coord. x, y Identify the photo coordinates of the lower-right corner of the image (last
line, last sample) in millimeters.
Image Size-Lines, Samples Identify the number of lines in input image, and number of samples
(pixels) per line.
Close Close the Photo Data window.
8.4.1.1 Rotation of Film When Scanned

When you scan an image, there are four possible rotations. The Camera Calibration window has
an option to choose one of four directions, however that selection does not work and you should
always set the choice to “Left Rotation.” Instead, the scan rotation must be specified in Frame
import, in the Photo Data (i.e. “Support Data”) window. These are the location- in film
Page 8-20 SOCET SET

(millimeters) space - of the upper-left and lower-right image (pixel) file corners. The film space
origin is the middle of the image. The four possible sign combinations are:
ROTATION UPPER-LEFT LOWER-RIGHT
up -X +Y +X -Y
+90 Deg. +X +Y -X -Y
+180 Deg. +X -Y -X +Y
+270 Deg. -X -Y +X +Y
For example, if the film was scanned in the normal “up” direction with the +Y film axis pointing
to the top of the digitized image (i.e. the negative lines axis), then the signs of the upper-left
corner values would be -X,+Y, and the signs of the lower-right corner would be +X and -Y.
If you will be importing the frame images as “unknown” and using the Exterior Init function in
Triangulation to establish the image orientation, then you must scan the film either “up” or +180
degrees (i.e. you must avoid 90 and 270 degree rotations). If you will be importing the imagery
“known” then you can scan the film at any rotation. For a typical metric camera, the corner
location values are usually around +/-114 mm.
8.4.2 Camera Location Window - Main

To open this window, first load a .dsup file by going to the directory of the images you wish to
import. Select the image, then click Open. Click in the Camera Location field and select Camera
Data under the calibration text box on the Panoramic Import/Edit window. Fill-in the applicable
data then click Close.
SOCET SET Page 8-21

The Camera Location window’s selections are as follows:
SELECT TO
Focal Length (mm) Identify the Focal Length in millimeters.
Location BLANK SPACE

X/Lon/Easting Identify the camera position in the Project ground coordinate system. For
BLANK SPACE longitude values, range is -180.0 to 180.0 degrees. Specify the units of the
BLANK SPACE entered values using the XY Units option.
Y/Lat/Northing Identify the camera position in the Project ground coordinate system. For
latitude values, range is -90.0 to +90.0 degrees. Specify the units of the
BLANK SPACE entered values using the XY Units option.
Elevation Identify the camera position in the Project ground coordinate system.
BLANK SPACE Specify the units of the entered values using the XY Units option.
XY Units Identify the units of coordinates in the Location.
Scan BLANK SPACE

Scan Rate Identify the camera sweep rate in degrees per second.
Start Scan Angle Identify the angle in decimal degrees of the first scan line relative to the
BLANK SPACE center aim point. A positive angle is to the left of the camera; negative to
BLANK SPACE the right.
End Scan Angle Identify the angle in decimal degrees of the last scan line relative to the
center aim point. A positive angle is to the left of the camera; negative to
BLANK SPACE the right.
Platform Ground (Airborne only) Identify the speed of the platform in project vertical units
Speed (feet or meters) per second.
Pass Designation (Orbiting only) Identify the direction of the sensor’s orbit. Orbits crossing
BLANK SPACE the equator north to south have a descending designation.
Orbit Inclination (Orbiting only) Identify the inclination of the sensor’s orbit in decimal
degrees relative to the equator.
Orientation Angle Enter the camera orientation angle here.

Omega/Heading BLANK SPACE
Phi/Roll BLANK SPACE
Kappa/Pitch BLANK SPACE
Angle System Identify the system of angles entered in the Orientation Angle. Can be
BLANK SPACE either Heading / Pitch/ Roll or Omega / Phi / Kappa.
Angle Units Identify the unit of angles in the Orientation Angle and Mounting Angle.
Mounting Angle Identify the angle of the camera relative to the platform. See “Camera
Mounting Angle (Panoramic only)” on page 8-6.
Close Close the Camera Location window.
Page 8-22 SOCET SET

8.4.2.1 ALBANY Triangulation Window
The ALBANY Triangulation window’s selections are as follows:
SELECT TO
Triangulation File Indicate the name of the triangulation file.
Strip Number Indicate the photo strip number.
Photo Number Indicate the photo number.
To gain access to this window click in the Camera Location field on the Panoramic Import/Edit
window.
8.4.2.2 PAT-B Triangulation Window
The PAT-B Triangulation window’s selections are as follows:
SELECT TO
Triangulation File Indicate the name of the PAT-B Triangulation File.
window.
SOCET SET Page 8-23

8.4.2.3 BINGO Triangulation Window
The BINGO Triangulation window’s selections are as follows:
SELECT TO
Triangulation File Indicate the name of the BINGO Triangulation File.
window.
8.4.3 Execution - Panoramic Import/Edit

1. Load the image file to be imported onto the workstation disk in the Import Image directory.
2. Click Preparation > Import > Image > Panoramic on the main workstation window.
3. [Optional] If you want to import the image into a different project from the one currently
loaded on the workstation, click File > Project on the Panoramic Import window. Choose
a project file and click OK. If the project you want to import the image into hasn’t been
created yet, you must use Create Project first to create a project.
4. Click File > Input Image > Other on the Panoramic Import window. Choose an image file
and click OK. The Photo Data window appears.
5. Enter photo coordinates of the Upper-Left corner of the image (first line, first sample) in
millimeters. If unknown, set Photo X to minus one half the number of Samples, times
Sample Pixel Size in microns, divided by 1000; and set Photo y to plus one half the number
of Lines, times Line Pixel Size in microns, divided by 1000.
6. Enter photo coordinates of the Lower-Right corner of the image (last line, last sample) in
millimeters. If unknown, set Photo X to plus one half the number of Samples, times Sample
Pixel Size in microns, divided by 1000; and set Photo y to minus one half the number of
Lines, times Line Pixel Size in microns, divided by 1000.
7. Enter values for the Image Size: number of Lines, and number of Samples per line. Click
OK.
8. Click Location to change the Output Image location by choosing a file location from the
File Location window. Click OK. The format can be changed by selecting the format name.
9. The Camera Location default is Unknown. This can be changed by clicking File >
Camera Location on the Frame Import/Edit window and choosing another type.
(ALBANY, PATB or etc.)
10. The default Camera Calibration file can be changed by clicking File > Camera Calibration
on the Panoramic Import/Edit window. Select another file, and click OK.
11. Set the Create Files option to Image and Support.
Page 8-24 SOCET SET

8.4.4 Batch Processing - Panoramic Import/Edit

COMMAND LINE:
% start_socet -single frame_import -batch -a pan -s

setting_file
frame_import frame
KEYWORD DESCRIPTION
project Project filename (with full path prefix, select from the .prj files in
cam_calib_ Camera Calibration file name (with full path prefix).
filename
create_files Specifies that only a support file will be created “SUPPORT” or image and
support files will be created “IMAGE_AND_SUPPORT”
atmos_ref Apply Atmospheric Refraction: “YES” or “NO.”
auto_min Auto minify “YES” or “NO.”
input_image_type Input image type: “HELAVA,” “TIES,” or “OTHER.”
input_image_ Input image filename (with full path prefix). The filename will be a
filename Scanner/Helava support file, e.g. “file.dsup,” a TIES file, e.g. “file.hdr,” or
an image file for type “Other,” e.g. “file.img.”
output_format See the chart in the Image Import/Export chapter for values. If the
“Export” column says “Y” then the format can be used. Use the keyword
listed in the “Batch Name” column.
output_name Name of the output image pixel and support file. Specify a name only, not
a full path, e.g. “abc.”

alb_strip_num Albany photo strip number.
albany_photo_num Albany photo number.
albany_xyz_units Albany XYZ units: “UNIT_FEET” or ‘UNIT_METERS” for ground

coordinates in the triangulation file.
patb_photo_num Patb photo number.
cam_loc_ang_sys Camera location input angle system: Omega, Phi, Kappa: “OPK” or
Heading, Roll, Pitch: “HRP.”
cam_loc_ang_units Camera location Angle Units: “UNIT_DEGREES,” “UNIT_RADIANS,”

“UNIT_GRADS” or “UNIT_DDMMSS.”
SOCET SET Page 8-25

KEYWORD DESCRIPTION
cam_loc_xy_units Specifies the units for entered va lues (X,Y) or (Easting, Northing) or (Lat,
Long): “UNIT_FEET,” “UNIT_DEGREES,” “UNIT_METERS,” or
“UNIT_RADIANS.”
cam_loc_focal Camera Focal Length in mm.
cam_loc_y_or_lat Camera Y or Lat entered in the project ground coordinate system.
cam_loc_x_or_lon Camera X or Lon entered in the project ground coordinate system.
cam_loc_elev Camera elevation entered in the project ground coordinate system.
cam_loc_omega Camera location in omega or heading units.
cam_loc_phi Camera location in phi or roll units.
cam_loc_kappa Camera location in kappa or pitch units.
cam_loc_type Camera location type: “UNKNOWN,” “ALBANY,” “PATB_L,”

“PATB_R,” “ENTER_DATA.”
cam_loc_filename The filename (with full path prefix) for the camera location: Albany
triangulation file or Patb file.
orbit_incl (Orbiting only) Inclination of platform orbit
pass_designator (Orbiting only) Orbit pass designation “ASCENDING” or

“DESCENDING”
platform_gnd_spd (Airborne only) Ground speed of the platform in project vertical units per
second
scan_rate Rate of scan (deg/sec).
start_scan Start angle for the scan
end_scan End angle for the scan
ul_img_x_mm Photo data of upper-left corner: photo X in millimeters.
ul_img_y_mm Photo data of upper-left corner: photo Y in millimeters.
lr_img_x_mm Photo data of lower- right corner: photo X in millimeters.
lr_img_y_mm Photo data of lower-right corner: photo Y in millimeters.
img_size_lines Image size: lines in pixels.
img_size_samps Image samples: in pixels per line.
8.5 Next Step

The Panoramic Import/Edit process creates two files: an image file and a support file. The next
step is usually Interior Orientation, although you may skip it if you provided the appropriate data
during Panoramic Import. After Interior Orientation, you should control the image using
Triangulation if you have ground control points (GCPs) or if you have tie points to a controlled
image. After the image is controlled, you can utilize any extraction application, such as Feature
Extraction or Terrain Extraction.
Page 8-26 SOCET SET

Chapter 9
QuickBird WorldView Import

Exploit DigitalGlobe QuickBird/WorldView imagery in
SOCET SET.
9.1 Overview
QuickBird Import reads DigitalGlobe QuickBird satellite data as WorldView Import reads
DigitalGlobe WorldView data. It loads the imagery onto the workstation disk and converts the
header information into a support file to accurately model the image.
9.1.1 When to Use QuickBird/WorldView Import

Use QuickBird Import function when you want to exploit a QuickBird image.
Use WorldView Import function when you want to exploit a WorldView image. (All
references to QuickBird also apply to WorldView.)
You run QuickBird Import after creating a project. After importing a QuickBird image, you can
proceed with triangulation and then data extraction. See “When to Use Triangulation” on
page 25-3. Interior Orientation is not required with QuickBird images since the sensor is a digital
9.1.2 QuickBird Imagery

This chapter is for QuickBird Import, which handles QuickBird Basic Products only. Use
ImageImport/Reformat to import QuickBird Standard Products. See “QuickBird/WorldView
Image Import” on page 7-8 for more details on QuickBird Imagery.
If your QuickBird images are on tape, you must extract them to disk before running QuickBird
Import. Use “tar” or whatever tape reading software came with your tape drive to extract the
information. You can then leave the QuickBird images in the same disk area or have QuickBird
Import copy them to a disk directory in the Image Location list.
SOCET SET Page 9-1

Chapter 9 - QuickBird WorldView Import
9.2 QuickBird Basic Image Import
The QuickBird Basic Image Import window’s selections are as follows:
File > Load Project... Selects a project.
File > Open... Selects a QuickBird README file.
File > Exit Exits QuickBird Image Import.
Options > Auto Minify Enables minification of the output images.

Refraction
Page 9-2 SOCET SET

SELECT TO
QuickBird Files Identify the names of QuickBird README files. You can view
information on a file by highlighting it, right clicking, and selecting View
Info. You can add or remove file(s) by right-clicking and selecting Add or
Remove.
Output Images Select Copy Images to enable or disable copying the pixel files to a new
image location.
new image to be. The output image will be named based on data from the
DIMAP file, e.g.55542820206151826141J.sup
Edit Names Change the new support file naming.
9.3 Execution - QuickBird/WorldView

Use the following set of steps to import a QuickBird tape, disk, CD-ROM:
1. Start QuickBird Import by clicking Preparation > Import > Image > QuickBirdBasic (or
Standard) on the main workstation window.
See the Image Import/Reformat section for how to import

QuickBird Standard imagery.
2. Click File > Open... and select the “readme” file(s) for the image you want to import. This
file typically contains the word “readme” and has a file extension of “.txt” and is in the
same directory as the image files. Do not select the README.TXT in the root directory of
the data set. You may select one or more files at a time. Do not select any of the other files
that came with the data set, only the readme file. QuickBird Import will find all the other
files automatically. You can also select readme files by right-clicking in the QuickBird
Files area and selecting Add...
3. [Optional] To view metadata from the header records, RMB click a file in the list and click
View Info...
4. [Optional] If you want the images to be minified, click Options > Auto Minify
5. [Optional] If you want to copy the images to another disk directory, click Copy Images
“ON” and select the image location and format for the copied images.
6. Click Start to begin importing the images.
9.4 Batch Processing - QuickBird/WorldView Import

COMMAND LINE:
% start_socet -single sat_import -a quickbird -batch -s

setting_file
% start_socet -single sat_import -a worldview -batch -s
SOCET SET Page 9-3

setting_file
KEYWORD DESCRIPTION
input_file “readme” file(s) for the images you want to import. Repeat for each
QuickBird image.
copy_images Set to “YES” to copy the images to an Image Location. “Default is NO.”
image_format [Optional] If copy_images is YES, this should be set to the format you
wish for the output images. See the table in the Image Import / Export
chapter for values.
output_location [Optional] If copy_images is YES, this should be set to the name of the
image location from the list in internal_dbs/DEVICE/
location.list
atmospheric_ (Optional) Set to "YES" to include the effect of atmospheric refraction for
refraction the sensor model. Default value is "NO".
9.5 Outputs
The import process creates a rigorous sensor model. Once you complete the import process, you
may wish to create a Cubic Rational Fast Sensor Model. The fast sensor model is a very good
approximation of the existing rigorous model and will speed up future image processing
operations, including image viewing.
If you plan to refine the accuracy of the rigorous sensor model through triangulation, create the
fast sensor model after performing triangulation. You can retain the original sensor model when
you create the fast sensor model. You cannot refine the accuracy of a fast sensor model. See “Fast
Sensor Model” on page 7-32 for additional information.
Outputs consist of an image support file and an image file which is tiled with a header in a tiled
format. The support file is created in the data directory used by the current project file.
9.6 Triangulating QuickBird Images

You can use the QuickBird image immediately after importing, but the accuracy may not be
acceptable for stereo viewing or mensuration. If you wish to refine the accuracy of your
QuickBird images, run Multi-Sensor Triangulation on them. See “QuickBird Images” on
Page 9-4 SOCET SET

Chapter 10
Landsat Import
Landsat Import covers the importing of Landsat imagery onto
the SOCET SET workstation from tapes, disks, or CD-ROMs.
10.1 Overview
Landsat Import reads Landsat imagery from disk, CD-ROMs, or tapes. It loads that imagery onto
the workstation disk, and converts the header information into a compatible support file.
Because Landsat imagery always has a nadir view, it cannot be

used for accurate geo-positioning or ATE or stereo
visualization.
10.1.1 When to Use Landsat Import

Use Landsat Import when you want to exploit a Landsat image. You run Landsat Import after
creating a project. After importing a Landsat image, you can proceed with triangulation (See
“When to Use Triangulation” on page 25-3) and then data extraction. Interior Orientation is not
required with Landsat images, since the sensor is a digital camera, resulting in a known, fixed
When creating your project, be sure that the project ellipsoid

matches the ellipsoid used by your imagery provider to geo-
correct the imagery. Failure to do so degrades the accuracy of
horizontal measurements.
10.1.2 Formats Supported

Landsat imagery is available in two processing levels: AT (geometrically raw) and PT (map
oriented, system corrected). SOCET SET only imports the PT level. The PT processing level is
analogous to rectified or orthorectified imagery.
For satellites before Landsat 7, SOCET SET imports L T W G C C T , and Fast Format data. The
LTWG CCT Landsat image format is described in the document User’s Guide for Landsat
Thematic Mapper Computer Compatible Tapes, Earth Observation Satellite Company (EOSAT),
1985.
SOCET SET Page 10-1

Chapter 10 - Landsat Import
SOCET SET also imports the U.S. Department of the Interior NLAPS format.
Landsat Import works in geographic / meters projects. If your

project is not this type, create a temporary geographic / meters
project, import the LandSat images, and copy the support files
to your project.
For Landsat 7, SOCET SET supports Fast Format and Hierarchical Data Format HDF in UTM or
SOM projections. For more information about Landsat 7 see:
http://landsat7.usgs.gov
Images must be imported into compatible projects (ex. SOM

must be imported into a geographic project).
Typically a Landsat7 Fast Format CD will contain files with names similar to the following:
L72041036_03619990920_HPN.FST panchromatic band header file
L72041036_03619990920_B80.FST band 8
L71041036_03619990920_HTM.FST thermal bands header file

L71041036_03619990920_B61.FST band 6L
L72041036_03619990920_B62.FST band 6H
L71041036_03619990920_HRF.FST VNIR/ SWIR bands header file

L71041036_03619990920_B10.FST band 1
L71041036_03619990920_B20.FST band 2
L71041036_03619990920_B30.FST band 3
L71041036_03619990920_B40.FST band 4
L71041036_03619990920_B50.FST band 5
L72041036_03619990920_B70.FST band 7
For Landsat7 HDF file naming conventions see the README.HDF file included on the CD.
For non-Landsat7 files, the naming convention is: BAND1.DAT... BAND7.DAT and
HEADER.DAT.
Note that file names above are examples. The first part of the file names will vary depending on
the data set, but the last part, such as “_HPN.FST” or “_HDF.L1R” will be the same.
Page 10-2 SOCET SET

10.2 Landsat Image Import
The Landsat Image Import window’s selections are as follows:
File > Load Project Prompts you to select the project file.
File > Open Input Device Prompts you to select the device and drive used for importing the imagery.
File > Exit Exits Landsat Image Import.
Options > Display Data Set Displays miscellaneous data from the header.
Parameters
SELECT TO
Band Chooser Select image bands for import in to a single image (Landsat 7 imports
multiple images depending on bands chosen).
Select Bands Allow user to select any of the 7 bands for input into a single image file.
Defaults to all 7 bands. (Must use output image file type that allows multi-
band images for resulting images other than 1 or 3 bands)
BLANK SPACE
Landsat 7 has 8 bands in 3 band groups (bands 1-5 and 7 VNIR/SWIR,
bands 6L and 6H thermal, and band 8 panchromatic). Each band group will
be imported as a separate file.
Create Visible Band Image Import Red Green and Blue bands into a single image file in the proper
band ordering.
Output Identify the name, location, and format of the output image.
SOCET SET Page 10-3

SELECT TO
Start Start importing the Landsat data
10.3 Execution - Landsat

Use the following set of steps to import a Landsat tape, disk, CD-ROM:
1. Start Landsat Import by clicking Preparation > Import > Image > Landsat on the main
workstation window.
workstation, click File > Load Project on the Landsat Import window. Select a file from
the list and click OK.
3. Click File > Open Input Device > (tape, disk, CD-ROM). Select the image location, then
click OK to start reading the header.
For Landsat 7 fast format, select one of the header files:
L7NNNN_NNNN_HRF.FST
L7NNNN_NNNN_HTM.FST
L7NNNN_NNNN_HPN.FST
For Landsat 7 HDF select:

L7fNNNNNN_NNNNNNNNNNN_HDF.L1R
4. [Optional] To view a display of certain data from the header records, click Options >
Display Data Set Parameters on the Landsat Import window. When complete, click Close.
The input devices listed in the Open Device Window are listed
in the Device Configuration File. See “Customizing Your
Software Configuration,” Appendix D for more information.
5. Set the Output Image name, location, and format to values you want. For Landsat 7, the
output name will be used for each band group if you import them all in at once (ex. if you
choose “image_name” the two other band groups will be imported as image_name2 and
image_name3).
6. Click Start to begin importing the image.
7. The import process creates a rigorous sensor model. Once you complete the import process,
you should create a Cubic Rational Fast Sensor Model. The fast sensor model is a very good
approximation of the existing rigorous model. Utilizing the fast sensor model will speed up
future image processing operations, including image viewing. If you plan to refine the
accuracy of the rigorous sensor model through triangulation, create the fast sensor model
after performing triangulation. You can retain the original sensor model when you create
the fast sensor model. You cannot refine the accuracy of a fast sensor model. See “Fast
Sensor Model” on page 7-32 for additional information.
Page 10-4 SOCET SET

10.4 Outputs
Outputs consist of an image support file and a binary image file which is tiled with a header in a
tiled format. The support file is created in the data directory used by the current project file. The
display of support data is provided though the Data Set Parameters window, which is popped-up
from the Landsat menu.
SOCET SET Page 10-5

Chapter 11
SPOT, JERS and IRS Import

SPOT, JERS and IRS Import covers the importing of imagery
onto the SOCET SET workstation from tapes, disks, or CD-
ROMs.
11.1 Overview of SPOT, JERS, and IRS

SPOT, JERS, and IRS Imports read imagery and geo-referencing information from CD-ROM,
magnetic tape, and disk media into SOCET SET. SPOT imagery is available from SPOT Image
Corporation and other distributors. JERS imagery is distributed by NASDA. IRS imagery is
available from various distributors.
Side-looking vs. Fore/aft

Pushbroom sensors can be
• This pictures shows a side-
looking pushbroom mounted in aircraft or in
• Some pushbrooms look satellites.
fore-and aft to obtain stereo
Ground
Track
Imagery is collected as
sensor moves forward
Pushbroom Sensor
SOCET SET Page 11-1

Chapter 11 - SPOT, JERS and IRS Import
11.1.1 When to Use SPOT Image Import

You use SPOT Import when you have SPOT data and you want to exploit the image in the data
set. You run SPOT Import after creating a project to hold the imagery. After importing a SPOT
image, you can the proceed with Triangulation and then data extraction.
SPOT Import works in projects with the Geographic, UTM, or Grid coordinate systems, but not
the LSR coordinate system.
11.1.1.1 Formats Supported

SPOT imagery is supplied in a variety of formats and processing levels. The various formats are
described below.
While SOCET SET handles many SPOT formats, including the

most common formats, you should ensure that your SPOT data
is in one of the formats accepted by SOCET SET before you
purchase the imagery.
Categorized by spectral type, SPOT comes in several types:

• Multispectral without short-wave infrared (SWIR) (known as MLA or Xs) (3 bands)
• Multispectral with SWIR (known as Xi or I) (4 bands)
• Panchromatic (known as PLA, PAN, P, or M)
SOCET SET imports all the above types of SPOT imagery.
SPOT multispectral imagery comes in two formats: Band Interleaved (B I L ) or Band Sequential
(BSQ). SPOT panchromatic imagery always comes in BSQ format. SOCET SET imports both
BIL and BSQ formats.
Your SPOT imagery may have been preprocessed by your supplier to assist with control or geo-
positioning. There are four processing levels available from SPOT:
• 1A – Raw. This is unrectified data and the pixels may have non-uniform GSD.
• 1B – Rectified. The imagery has been resampled and geo-coded to a uniform GSD.
• 2 – Controlled. Controlled support data is provided that is based on GCPs.
• S – Stereo. A relative orientation has been performed on this SPOT stereo pair.
SOCET SET accepts processing levels 1A and 1B only. Processing level 1B is the most common
type of SPOT imagery. SOCET SET only supports the full-scene product.
SPOT Image has introduced the DIMAP format. They are distributing all SPOT 5 data in this
format and will be transitioning data from previous satellites to DIMAP. If you have a DIMAP
data set, you must import it with SPOT DIMAP Import. SOCET SET supports the same SPOT
DIMAP products as with previous formats, that is, SPOT full-scene 1A and 1B in both
panchromatic and multispectral.
Finally, the SPOT tape format varies between SPOT distributors. SOCET SET accepts imagery
in the standard format of the SPOT Image Corporation and in the standard format of the Canada
Centre for Remote Sensing (CCRS) and Australian Centre for Remote Sensing (ACRES). The
image formats processed by SOCET SET are taken from The SPOT Scene Standard Digital
Product Format (S4-ST-73-01-SI), SPOT Image Corporation, 1995, and Standard SPOT MLA/
Page 11-2 SOCET SET

PLA CCT Format (DMD-TM85-428A), Canada Centre for Remote Sensing, 1985. SOCET SET
supports the “CAP” data format.
Some CCRS SPOT data sets have a defect which causes the image to be shifted to the east or west.
You can set a special environment variable when starting SOCET SET to fix the problem. There
are two ways to set the variable. One is to add -setenv_no_arg CCRS_ROLL_INVERT to
the file <install_path>/.socet_xxx, where “xxx” is the name of the machine you are
working on. This method will always perform the correction for all CCRS SPOT imports until
you edit the .socet_xxx file and take the instruction out. The other way is to start the SPOT
Import task manually by typing:
% <install_path>/bin/start_socet -setenv_no_arg
CCRS_ROLL_INVERT -single spot 1 xxx.prj
where “xxx” is the name of your project. This method only performs the correction for that
particular import session.
Some SPOT images in the CCRS (Canadian) format contain an error in the sensor attitude data
on the tape header, which make it impossible to control the image with SOCET SET. If you find
this to be true, ask your tape supplier for a replacement tape. This is not a problem with SPOT
tapes produced by the SPOT Image Corporation.
11.1.1.2 Using SPOT images

When creating a project which will include SPOT images, the geodetic datum must be based on
an earth-centered ellipsoid such as WGS 84. The reason for this is that the SPOT satellite
ephemeris and attitude data are based on an earth-centered system. Before importing your data,
make sure your project has an origin near the center of your SPOT or JERS data set. It should be
in the same hemisphere for Geographic projects, or the same UTM zone for UTM projects.
Interior Orientation is not required with SPOT images, since the sensor is a digital camera,
resulting in a known, fixed relationship between each image pixel and the sensor lens.
SOCET SET can accommodate images from different sensors simultaneously. From the user’s
point of view, there is little difference between triangulating a block of frame images, SPOT
images, or a mixture of both. When triangulating SPOT images, there are thirteen parameters
which can be adjusted: the focal length, the 6 parameters of position and attitude, and the 6 first
degree components of position and attitude with respect to time. Apriori estimates for these are
obtained from the SPOT header data.
The recommended number of ground control points is 4–6 per model (or per multiple image strip
if all images are from a single orbital pass.) Pointing accuracies range from 6–20 meters. If there
are no ground control points available, the expected absolute distance error is approximately 500
meters. A single control point can correct for model offsets due primarily to timekeeping errors.
Two control points can correct for offset and azimuth errors.
11.1.2 Outputs
Outputs consist of an ASCII support file and a binary image file which is tiled with a header in a
tiled format. The support file is created in the data directory used by the current project file. The
display of support data is provided by the window popped-up from the main SPOT menu.
SOCET SET Page 11-3

11.2 SPOT Import
The SPOT Image Import window’s menu choices are as follows:
File > Load Project Prompts you to select a project.
File > Open Input Device > BLANK SPACE

Disk Prompts you for the input disk file name.
CD ROM Reads the CDROM and prompts you for a scene number for import.
Tape Prompts you to select the tape drive used for importing the imagery.
File > Exit Exits SPOT Image Import.
Options > Display Displays the Tape Parameters window to display the tape parameters.
Parameters
Options > Atmospheric Include atmospheric refraction in the sensor model.

Refraction
SELECT TO
Tape/CD Displays the selected scene for import.
Input Files Displays the selected files for import.
Output Image Identify the name, format, and location of the output image.
Start Begin the importing the SPOT image.
Page 11-4 SOCET SET

11.2.1 Importing From CD-ROM

SPOT Import recognizes the data format for SPOT Scene and CCRS CD-ROM products. On
Unix, the CD-ROM must be mounted on the directory “/cdrom.” If this is not the case, ask your
system administrator to mount it there. The root directory of the CD ROM must have
subdirectories called “scene01,” “scene02,” etc. for each scene on the disk. If you have difficulty
importing, you can also try identifying the files with the Importing From Disk interface.
11.2.2 Importing From Disk

SOCET SET can use disk files for the SPOT data. There can be one single large file containing
the Volume Directory File, Leader File, Imagery File, Trailer File, and Null Volume Directory
File or these files can be kept separate. If the files have the SPOT Scene naming convention, e.g.
vold_01.dat, lead_01.dat, imag_01.dat, trai_01.dat, null_01.dat, then you can click on just one of
them and the rest will be filled in automatically. The disk file selection box also allows you to
select more than one file. You can use this feature if you are having difficulty in importing a set
of files and would like to try a different file ordering. The files are read in the order that you click
on them.You can specify multiple files by clicking on them while holding the Control Key.
11.2.3 Transferring Data From Tape to Disk

You might want to transfer your data from a tape to disk so that it can be subsequently imported
from disk on a different workstation. The steps to do this are as follows:
1. Mount the 9-track C C T on a tape drive. In this example the device name of the tape drive
will be /dev/rmt/7n.
2. Use the <install_path>/bin/tape_struct executable to determine the files and
record size.
% <install_path>/bin/tape_struct /dev/rmt/7n
As a result of this command the messages should reflect the file number and block size of
the records in each file.
3. Edit the <install_path>/bin/copy_spot_to_disk script to reflect the input record block
size. This script file should reflect the following commands which must be correct in order
to copy records verbatim to disk files
dd ibs=360 if=/dev/rmt/7n of=vold_01.dat
dd ibs=3960 if=/dev/rmt/7n of=lead_01.dat
dd ibs=8640 if=/dev/rmt/7n of=imag_01.dat
dd ibs=1080 if=/dev/rmt/7n of=trai_01.dat
dd ibs=360 if=/dev/rmt/7n of=null_01.dat
mt -f /dev/rmt/7n rewind
Some older SPOT images were on two tapes at 1600 bpi for a single image. If there is a
second tape involved, then repeat these first three steps for the second tape as well using
_02.dat in place of _01.dat for the output files.
Strip off the first 8640 bytes from part 2 of the image which is imag_02.dat using the
following command:
SOCET SET Page 11-5

dd if=imag_02.dat of=strip_02.dat bs=8640 skip=1

Second, you then concatenate the following input files into one output file:
cat vold_01.dat lead_01.dat imag_01.dat strip_02.da

trai_01.dat null_01.dat > scene1
4. Now proceed to import the disk image file, as described under importing from disk.
11.2.4 Importing a Color SPOT Image

If you are importing SPOT data with three bands, you will see a popup menu asking which bands
you want to import. If you select “All Bands (color)” the three bands will be merged into a single
color (3-band) image file. The name of the support file will be what you entered in the name box.
If you select “All Bands (grays)” the three bands will be put out as three separate monochrome
images. The name of the support file(s) will be what you entered in the name box concatenated
with “_band_n.sup,” where “n” is “1” “2” or “3” for the three bands. If you select “Band n only,”
it will behave the same as “All Bands (grays),” except only the single band you select will be
imported. For SPOT4, four bands are available.
11.2.5 Execution - SPOT Import

Use the following sequence of steps to import a SPOT image.
1. Click Preparation > Import > Image > SPOT on the main workstation window to start
SPOT Import.
workstation, click File > Load Project on the SPOT Image Import window.
3. If importing from tape, click File > Open Input Device > Tape on the SPOT Image Import
window. Select the name of the tape device and then click OK to start reading the tape
header.
If importing from CD ROM, click File > Open Input Device > CD ROM on the SPOT
Image Import window and then select the scene you want to import.
If importing from disk, click File > Open Input Device > Disk and then select the file(s)
you want to import.
4. [Optional] To view a display of certain data from the tape header record, click Options >
Display Parameters on the SPOT Image Import window.
The input devices list in the Open Device Window are listed in
the Device Configuration File. See “Customizing Your
5. In the Output Image section of the SPOT, set the file name, location, and format to values
you want.
7. If the SPOT Image Import detects the tape to be multispectral, a dialog will appear,
prompting you for either band 1, band 2, band 3, band 4, or all bands to be extracted from
tape.
8. If the SPOT tape is a multi-volume set, you will be prompted to click OK when each
successive tape has been loaded.
Page 11-6 SOCET SET

11.2.6 SPOT DIMAP Import
SPOT DIMAP Import’s menu choices are as follows:
File > Open... Selects a DIMAP file.
File > Exit Exits SPOT Image Import.
Options > Auto Minify Automatically creates a minified image pyramid from the resulting mosaic
after the processing completes.
Options > Atmospheric Includes atmospheric refraction in the sensor nodel.

Refraction
SELECT TO
DIMAP Files Identify the names of DIMAP files. You can view information on a file by
highlighting it, right-clicking, and selecting View Info. You can add or
remove file(s) by right-clicking and selecting Add or Remove.
SOCET SET Page 11-7

SELECT TO

new image to be. The output image will be named based on data from the
DIMAP file, e.g.55542820206151826141J.sup
11.2.7 Execution - SPOT DIMAP Import

Use the following sequence of steps to import a SPOT DIMAP image.
1. Click Preparation > Import > Image > SPOT DIMAP on the main workstation window.
3. Click File > Open... and then select the DIMAP file(s) you want to import. DIMAP files
are usually named with the extension of “.DIM” and contain XML text. You can also select
files by right-clicking on the DIMAP Files area and selecting Add. Repeat for each DIMAP
file you want to import.
DIMAP file and select View Info.
5. [Optional] In the Output Images section select the location to copy the pixel file(s) and the
11.2.8 Batch Processing - SPOT DIMAP Import

COMMAND LINE:
% start_socet -single sat_import -a dimap -batch -s

setting_file
KEYWORD DESCRIPTION
input_file DIMAP file(s) you want to import. Repeat for each image you want to
import.
copy_images Set to “YES” to copy the images to an Image Location. Default is” NO.”
Page 11-8 SOCET SET

KEYWORD DESCRIPTION
chapter for values.
location.list
atmospheric_refraction (Optional) Set to "YES" to include the effect of atmospheric refraction for
the sensor model. Default value is "NO".
11.2.9 Next Step

perform image enhancement operations, and you may perform A n n o t a t i o n and geopositioning.
If you have control data, you should run Triangulation.
The import process creates a rigorous sensor model. Once you complete the import process, you
should create a Cubic Rational Fast Sensor Model. The fast sensor model is a very good
approximation of the existing rigorous model. Utilizing the fast sensor model will speed up future
image processing operations, including image viewing. If you plan to refine the accuracy of the
rigorous sensor model through triangulation, create the fast sensor model after performing
triangulation. You can retain the original sensor model when you create the fast sensor model.
You cannot refine the accuracy of a fast sensor model. See “Fast Sensor Model” on page 7-32
for additional information.
11.3 JERS Import
SOCET SET Page 11-9

JERS Import is very similar to SPOT Import and most of the procedures described above for
SPOT are valid for JERS. Important differences are described below.
11.3.1 Image Bands

Each JERS image comes on an 8mm tape. The tape has 4 bands on it, numbered 1,2,3, and 4. Each
band is 4,000 x 4,500 pixels. Band 4 is pointing “forward” (south) at 15.33 degrees from nadir.
Bands 1,2, and 3 are pointing straight down (nadir).
If you want to make a color image, imports bands 1, 2, and 3 and assign them to Blue, Green, Red,
respectively.
SOCET SET processes both level 0 and level 1 products.
The satellite travels North-to-South, exactly. However, the

earth is rotating under it (West to east). So the North arrow on
the raw JERS image (any band) is pointing to the left about 20
degrees (i.e. it does not point straight up). In other words, the
footprint of the raw image is NOT a rectangle in ground space,
it is a parallelogram.
The GSD size of the raw image pixel is 18.3 m across track (E-W) and 24.03 m along track
(N-S). Thus each pixel is not square on the ground.
The raw image has north pointing roughly up. The size of a JERS image footprint is 96 km x 82
km.
11.4 Stereo JERS Imagery

In SOCET SET you will most commonly use bands 3 and 4 since they produce a stereo pair. Band
3 is looking straight down from the sensor, and band 4 is looking south from the sensor. Thus, to
get a stereo image pair, you must use band 3 from one image and band 4 from a second image.
Band 3 must come from the image that was taken at the more southerly latitude, and band 4 must
come from the image with the more northerly latitude.
Page 11-10 SOCET SET

You cannot make a stereo pair from bands 3 and 4 of the same image (they don’t overlap on the
ground).
For example, if you have a JERS image at latitude 35:40N and one at 36:59N, you would use band
3 from the 35:40N image and band 4 from the 36:59N image.
The raw images are oriented with north up. After you run pairwise rectify the images will have
west up and north to the right. (This assumes you designate the 35:40N image as the left image
and the 36:59N image as the right image; if you reverse the designations, east will be up.) After
you pairwise rectify the images, the pixels will be square on the ground, with a GSD of around
20 to 22 meters.
11.4.1 Execution - JERS Import

1. Click Preparation > Import > Image > JERS on the main workstation window to start
JERS Import.
2. Click File > Load Project (if not already selected) on the JERS Import window. Select a
project file from the list and click OK.
3. If your input is on disk, click File > Open Input Device > Disk. If it is on CDROM, click
File > Open Input Device > CDROM. If it is on tape, insert the tape into a drive on your
network. Make sure the tape is rewound by typing:
mt -f /dev/drive_id rew
4. Click File > Open Input Device > Tape on the JERS Import window to select the drive. If
the drive name is not in the list, add the drive to the list as described in the Customizing
Your Workstation appendix, then start again at step 1. After you select the drive, click OK.
JERS Import will read some information from the tape, this will take about a minute.
The tape drive you select must be a non-rewinding Berkeley-

compatible drive; for example under the Solaris operating
systems the drive should end with bn.
5. JERS Import prompts you to enter the output file name. Enter the output file name in the
Name Field of the Output Image section of the JERS Import window. Also, choose the
format for the file.
6. Decide which disk you want the output Image data to be placed on. You will need roughly
18MB per band you import. Click Location and choose the location for the output file. You
can click Edit Location in the File Location window to change paths. Click OK when done.
7. Click Start. JERS Import will read some data from the tape, then will pop-up a window
asking you to select bands. Four bands will be listed, 1, 2, 3, and 4. Select any combination.
Normally you will select bands 3 or 4 or both. Click OK on the band selection pop-up.
8. JERS Import will now process the entire tape. This will take 5 to 20 minutes. It will inform
you when it is done.
If you abort an import, the percent complete box may stay up.
You can dismiss the box by double-clicking in the upper left
corner.
9. Verify that the images were imported properly by loading them onto the main image
window.
11.4.2 Importing a Color JERS Image
SOCET SET Page 11-11

If you want to import a color JERS image, you should follow these steps:
1. Run JERS Import - as described above - specifying bands 1, 2, and 3. This will create three
grey-shade images, one for each of the three bands.
2. After the import completes, run start_socet -single img_join band3 band2
band1 color to merge the three bands into a single image file. Note that band 1 is blue,
band 2 is green, and band 3 is red.
3. Create a support file for the color image by copying one of the support files for the
individual bands, editing the copy, and changing the image name to identify the color image
you created in step 2.

11.5 IRS Import

IRS Import is very similar to SPOT Import and most of the procedures described above for SPOT
are valid for IRS. Important differences are described below.
IRS imagery is supplied in a variety of formats and processing levels. The various formats are
addressed.
While SOCET SET handles many IRS formats, including the most common formats, you should
ensure that your IRS data is in one of the formats accepted by SOCET SET before you purchase
the imagery.
SOCET SET supports imagery from satellites IRS-1C and IRS-1D. The IRS satellites carry three
sensors; PAN, LISS-III, and WiFS.
11.5.1 Panchromatic Sensor

The Panchromatic sensor (PAN) is a high resolution black-and-white camera with a ground
resolution of 5.8 meters and a swath of 70 kilometers. The image comes as three slightly
overlapping subframes called Left, Right, and Middle. The imagery you get may consist of one,
two, or all three subframes. The subframes are not registered to each other, and therefore each
sub-frames must have its own support file.
11.5.2 LISS Color sensor

The Linear Imaging Self-scanning Sensor (LISS-III) has four independent cameras operating
simultaneously. Each camera records a different spectral band. Three of the cameras operate in
the Visible/Near Infrared (VNIR) ranges (Bands 2, 3, and 4). These three cameras provide a
ground resolution of 23.5 meters and a swath of 141 kilometers. The fourth camera operates in
the Short Wave Infrared (SWIR) range (Band 5). This camera provides a ground resolution of
70.5 meters and a swath of 148 kilometers. None of the four image bands are registered to each
other, and therefore each must have its own support file.

11.5.3 WiFS Sensor

The Wide Field Sensor (WiFS) has two cameras recording optical ranges equivalent to bands 3
and 4. The cameras provide a coarse ground resolution of 188.3 meters and a wide swath of 810
kilometers.

SOCET SET imports the panchromatic sensor as well as bands 2, 3, and 4 of the LISS sensor.
• SOCET SET does not import band 5 of the LISS sensor.
• SOCET SET also does not support the WiFS sensor.
IRS imagery products are formatted two ways: “super structure format” and “fast format.”
SOCET SET imports only the “super structure format.” The “fast format” does not contain any
ephemeris information; thus has no practical photogrammetric application.
The pixel data of IRS imagery is recorded in two formats: Band Interleaved by Line (BIL) or
Band Sequential (BSQ). SOCET SET imports only the Band Sequential (BSQ) format.
Your IRS imagery may have been preprocessed by your supplier to assist with control or geo-
positioning. There are four preprocessing levels available for IRS imagery.:
• 0 - Raw. This is uncorrected data.
• 1 - Browse. Imagery which contains radiometric and geometric corrections only for
earth rotation.
• 2 - Standard. Imagery that has been radiometrically and geometrically corrected.
• 3 - Special. Imagery that contains special processing like merging, enhancements,
transformations, etc., after Level 2 corrections.
SOCET SET supports “raw,” “browse,” and “standard” preprocessing levels. The “special”
preprocessing level contains unknown and unmeasured corrections, thus practical
photogrammetric application does not apply. Although SOCET SET supports “raw,” “browse,”
and “standard” preprocessing levels, IRS Import currently does not apply radiometric corrections
on import. As a result of radiometric corrections not being applied, IRS imagery is likely to
contain streaks resulting in poor imagery. Therefore, until radiometric corrections are applied on
import, SOCET SET customers are requested to order radiometrically corrected imagery.
11.5.5 Execution - IRS Import

The process for importing an IRS image (color or panchromatic) is:
1. Clicking Preparation > Import > Image > IRS from the main workstation window to start
IRS Import.
2. Click File > Load Project (if not already selected) on the IRS Import window.
3. Clicking File > Open Input Device on the IRS Import window to select an input devices.
If importing from tape, select the name of the tape device and then click OK to start reading
the tape header.
If importing from CD ROM, select the IRS imagery you want to import. If the CD ROM
file selection does not work properly, try selecting the Disk Option, navigating to the CD

ROM directory, and selecting the file. If importing from disk, select the file(s) you want to
import.
If the input device selected is a tape drive, the tape drive must
be a non-rewinding Berkeley-compatible drive; for example
under the Solaris operating systems the drive should end with
bn. Also, make sure the tape is rewound
(“mt -f /dev/drive_id rew”).
4. [Optional] Click Options > Display Parameters on the IRS Import window to view a
display of certain data from the IRS imagery header record.
5. In the Output Image section of the SPOT, set the file name, location, and format to values
you want.
7. If the IRS Import detects the imagery to be multispectral, a dialog will appear, prompting
you for which bands to be extracted. Default is to import Bands 2, 3, and 4 as individual
grey images.
11.5.6 Creating a Color IRS Image

The LISS sensor has 4 bands on it, called bands 2, 3, 4, and 5. Bands 2, 3, and 4 can be used
together to form a color image.
If you are importing IRS data from the LISS sensor you must decide how you want the bands
stored on disk. A menu will pop-up giving you a choice of importing bands 2,3,4 as a color image,
or importing individual bands as grey-shade images.
Although it is tempting to import the LISS imagery as a 3-band color image, this is discouraged
because bands 2, 3, and 4 are usually not registered. Therefore, a special workflow is used to
create a color IRS image. The workflow is described below.
In general, the bands of an IRS image are not registered, so you

should import the bands as separate grey-shade images.
If you import the bands as a color image, the name of the support file will be what you entered in
the name box. If you import the bands as grey-shade images, the bands will be put out as separate
monochrome images. The name of the support file(s) will be what you entered in the name box
concatenated with “_band_n.sup”; where “n” is “2” “3” “4” or “5” for the respective bands. If
you select “Band n only”, only the single band selected will be imported.
11.5.7 Workflow for creating a color IRS image

1. Run IRS Import and import bands 2, 3, and 4 as separate grey-shade images.
2. Run Multi-Sensor Triangulation (MST) and create a setup file with one strip; put the 3
images into the strip.
3. Fix all the parameters of the middle band except the X-coordinate (that is, set the Adjust
flag to NO in the MST parameter window).
4. Run MST APM/Automatic to find common points between the bands. A 3x3 tie point
pattern should be sufficient.
5. Run MST APM/Interactive to fix unsuccessfully measured points.

6. Execute MST IPM if necessary to add some more tie points.

7. Run MST Simultaneous Solve. Save the final triangulation data.
8. Run Orthophoto for each band. The boundary and GSD must be exactly the same for all
bands.
9. Combine the three pixel files into one color pixel file. To run img_join, cd (change
directory) to the <install_path>/bin directory. The purpose of this program is to
create the merged color support and image file.Then execute the following command:
% start_socet -single img_join band4.img band3.img

band2.img merged.img
10. Create a support file for the color image by copying any of the single band orthophoto
support files, then edit the new support file to point to the pixel file you created in step 9.
11. Verify the color image by loading it on the main image display.
11.5.8 Merging a color image with panchromatic image

If you have a PAN and a LISS (color) image of the same region, you may wish to combine the
two into a high-resolution color image. See “Execution - Multi-Spectral Image Sharpening” on
page 47-7 to do that procedure.

Chapter 12
RADARSAT and ERS Import

RADARSAT and ERS imports imagery from various
distributors onto the SOCET SET workstation from tapes,
disks, or CD-ROMs.
12.1 Overview
RADARSAT Import reads RADARSAT (RADARSAT 1) imagery from 8 mm tapes and disk files
into SOCET SET. RADARSAT imagery is available from Lockheed-Martin Corporation® and
other distributors.
ERS Import reads ERS imagery from 8-mm tapes and disk files into SOCET SET. ERS imagery
is distributed by ESRIN.
12.2 RADARSAT Import
SAR sensors can be

mounted in airplanes
or in satellites.
Active SAR
pulse
Reflective
return Ground
Track
Lake
12.2.0.1 SAR
SOCET SET Page 12-1

Chapter 12 - RADARSAT and ERS Import
12.2.1 When to Use RADARSAT Image Import

You use RADARSAT Import when you have a RADARSAT imagery and you want to exploit the
image on the tape. You run RADARSAT Import after creating a project to hold the imagery. After
importing a RADARSAT image, you can then proceed with Triangulation and then data
extraction.
RADARSAT Import works in projects with the Geographic, UTM, or Grid coordinate systems,
but not the LSR coordinate system.
RADARSAT import does not work correctly in projects with feet as the vertical unit. To use a
feet project, import the data into a temporary meters project and use Edit Project to copy the data
to a feet project.
12.2.1.1 Formats Supported

RADARSAT imagery is supplied in a variety of processing levels and beam modes. The various
formats are described below.
While SOCET SET handles many RADARSAT formats,

including the most common formats, you should ensure that
your RADARSAT imagery is in one of the formats accepted by
SOCET SET before you purchase the imagery.
There are seven beam modes available for RADARSAT products, each defined by the area it
covers and the resolution available:
NOMINAL
NOMINAL AREA
BEAM MODE RESOLUTION
COVERED (KM)
(M)
ScanSAR Wide 500X500 100
ScanSAR Narrow 300X300 50
Extended Low 170X170 35
Wide 150X150 30
Standard 100X100 30
Extended High 75X75 25
Fine 50X50 10
There are six processing levels available from RADARSAT:

• Signal Data—Signal Data is an unprocessed matrix of time delays. The data have
been repackaged to fit into standard CEOS format. Otherwise the data is
unprocessed. Users will require SAR processing capabilities to use this
RADARSAT product. All beam modes can provide Signal Data.
• Single Look Complex—Single Look Complex data is stored in slant range. It has
been corrected for satellite reception errors, includes latitude/longitude positional
information, and is calibrated. Single Look Complex data retains the optimum
resolution available for each beam mode and the phase and amplitude information
Page 12-2 SOCET SET

of the original SAR data. Data from all beam modes, with the exception of
ScanSAR, can be processed to this product.
• Path Image—Path Image products are recommended for individuals and
organizations experienced in image processing or who do not require positional
accuracy. The image product is aligned parallel to the satellite’s orbit path. Latitude
and longitude positional information has been added to represent the first, mid and
last pixel positions of each line of data. The products are also calibrated. Data from
all beam modes can be processed to this product.
• Path Image Plus—The difference between Path Image and Path Image Plus lies in
the spatial sampling procedure used in calibrating the products. Path Image Plus
uses a smaller pixel spacing to retain full RADARSAT beam mode resolution which
will enhance your ability to measure point targets. However, it will create a digital
file which is considerably larger than a Path Image product. Data from all beam
modes with the exception of ScanSAR can be processed to this product.
• Map Image—Map Image products are oriented with North up and are corrected to a
user requested map projection. The positional accuracy of Map Image products
depends on the terrain relief and the beam mode. Data from all beam modes with the
exception of ScanSAR can be processed to this product.
• Precision Map Image—Precision Map Image products have even greater positional
accuracy than Map Image products. Ground Control Points as well as a map
projection are used to spatially align the image.
SOCET SET accepts:
• Path Image processing level
• Path Image Plus processing level
SOCET SET does NOT handle:
• Signal Data
• Single Look Complex
• Map Image
• Precision Map Image
SOCET SET accepts all beam modes except ScanSAR modes.
SOCET SET accepts imagery in CEOS format used by RADARSAT International.
The image formats processed by SOCET SET are taken from RADARSAT
Illuminated—Your Guide to Products and Services, preliminary version 07195.
12.2.1.2 Using RADARSAT images

When creating a project which will include RADARSAT images, the geodetic datum must be
based on an earth-centered ellipsoid such as WGS 84. The reason for this is that the RADARSAT
satellite ephemeris data are based on an earth-centered system.
Interior Orientation is not required with RADARSAT images, since the sensor has no lens.
One hallmark of SOCET SET is that it can accommodate images from different sensors
simultaneously. From the user’s point of view, there is little difference between triangulating a
block of frame images, RADARSAT images, or a mixture of both. When triangulating
RADARSAT images, there are 13 parameters which can be adjusted: the 3 parameters of position,
3 parameters of velocity, 3 parameters of acceleration, 3 squint angle parameters, and 1 range bias
parameter. Prior estimates for these are obtained from the RADARSAT header data.
SOCET SET Page 12-3

The recommended number of ground control points is 4-6 per model (or per multiple image strip
if all images are from a single orbital pass). Pointing accuracies range from 6-20 meters. If there
are no ground control points available, the expected absolute distance error is approximately 500
meters. A single control point can correct for model offsets due primarily to time keeping errors.
Two control points can correct for offset and azimuth errors.
12.3 RADARSAT Import
The RADARSAT Import window’s menu choices are as follows:
File > Load Project Prompts you to select a project.
File > Open Input Device > BLANK SPACE

Disk Prompts you for the input disk file name.
Tape Prompts you to select the tape drive used for importing the imagery.
CD ROM Reads the CDROM and prompts you for a scene number for import.
File > Exit Exits RADARSAT Image Import.
Options > Display Scene Displays the Scene Parameters window to display the scene parameters.
Parameters
SELECT TO
Output Image Identify the name, and location of the output image.
Start Begin the importing the RADARSAT image.
Page 12-4 SOCET SET

12.3.1 Execution - RADARSAT Import
Clicking OK in the “File Selection” dialog box, without first

selecting a file, may cause complications.
12.3.1.1 Importing From Tape

Use the following sequence of steps to import a RADARSAT image from a tape. You may import
all (the default) or a subsection of a RADARSAT image:
1. Click Preparation > Import > Image > RADARSAT on the main workstation window to
start RADARSAT Import.
workstation, click File > Load Project on the RADARSAT Image Import window.
3. [Optional] To view a display of certain data from the tape header record, click
Options > Display Tape Parameters on the RADARSAT Image Import window.
4. Click File > Open Input Device > Tape on the RADARSAT Image Import window. Select
the name of the tape device and then click OK to start reading the tape header.
The input devices list in the Open Device Window are listed in
the Device Configuration File. See “Customizing Your
5. Set the Output Image file name and location to values you want.
12.3.1.2 Importing From CD-ROM

SOCET SET recognizes the data format for RADARSAT CD-ROM products. The CD-ROM
must be mounted on the directory “/cdrom.” If this is not the case, ask your system administrator
to mount it there. Follow the same instructions for Tape Import, except click Open Input Device
> CD ROM instead of the tape selection. This will bring up a list of the available scenes on the
CD-ROM. The expected naming of the files are:
vdf_dat.001 (Volume Descriptor File)
lea_01.001 (Leader File)
dat_01.001 (Image File)
tra_01.001 (Trailer File)
nul_vdf.001 (Null Volume Descriptor File)
If you have difficulty importing, you can also try identifying the files in the above order with the
Disk Import interface.
12.3.1.3 Importing From Disk

The sequence of steps you follow to import a RADARSAT image from disk is identical to those
for importing from tape, except in step 4 you click Open Input Device > Disk instead of Open
Input Device>Tape, and you select the name of the input disk file rather than the input tape
device.
SOCET SET Page 12-5

If you have a set of RADARSAT Scene files which conform to the RADARSAT Scene CD-ROM
naming convention (see above), you can select them by selecting any one of them with the file
selection box. RADARSAT Import will determine the other files and read them automatically.
The disk file selection box also allows you to select more than one file. You can use this feature
if you are having difficulty in importing a set of files and would like to try a different file
ordering. The files are read in the order that you selected them.
12.3.2 Next Step

perform image enhancement operations, and you may perform A n n o t a t i o n and geopositioning.
If you have control data, you should run Triangulation.
no ground control points, you must run Triangulation to perform Relative Orientation.
12.4 ERS Import

ERS Import is almost identical to RADARSAT Import and all of the procedures described above
for RADARSAT are valid for ERS.

ERS imagery is supplied in a variety of formats. The various formats are described below.
While SOCET SET handles ERS imagery, you should ensure

that your ERS tape is in the format accepted by SOCET SET
before you purchase the imagery.
There are eight SAR Image Products available from ERS:

SAR Annotated Raw Data—Telemetry data corresponding to 16 seconds of data collection.
SAR Fast Delivery Image—Multi-look, ground range digital imagery intended for near real time
applications.
SAR Fast Delivery Image Copy—Offline copy of Fast Delivery Image product.
SAR Single Look Complex Image (quarter frame)—presents SAR data following preprocessing,
but retains each sample as complex data. The product is single look and in slant range.
Corresponds to just over one-half of range by one-half azimuth of the full image.
SAR Single Look Complex Image (full frame)—as above, but is a full scene product.
SAR Precision Image - multi-look, ground range, system corrected image. This product is
calibrated and corrected for the SAR antenna pattern and range-spreading loss. The image is not
geocoded and terrain distortion has not been removed. Accepted by SOCET SET.
SAR Ellipsoid Geocoded Image—multi-looked, ground range, system corrected image. It is
precisely located and rectified onto a map projection, but not corrected for terrain distortion.
Page 12-6 SOCET SET

SAR Geocoded Terrain Corrected Image—multi-looked, ground range, system corrected image.
It is precisely located and rectified onto a map projection and is corrected for terrain distortion.
SOCET SET accepts only the SAR Precision Image product,

but not the other products.
12.4.2 Execution - ERS Import

1. Click Preparation > Import > Image > ERS on the main workstation window to start ERS
Import.
workstation, click File > Load Project on the RADARSAT Image Import window.
3. Obtain the 8-mm tape you want to import. Set the write-protection on. Insert the tape into
a drive on your network. Make sure the tape is rewound by typing:
mt -f /dev/drive_id rew
4. Select the drive by clicking File > Open Input Device > Tape on the ERS Input window
5. [Optional] To view a display of certain data from the tape header record, click Options >
Display Tape Parameters on the ERS Import window. If the drive name is not in the list,
add the drive to the list. See “Customizing Your Software Configuration,” Appendix D,
then start again at step 1. After you select the drive, ERS Import will read some information
from the tape, this will take about a minute.
The tape drive you select must be a non-rewinding Berkeley-

compatible drive; for example under the Solaris operating
systems the drive should end with bn.
6. Set the Output Image file name and location to values you want.
8. ERS Import will now process the entire tape. This will take 5 to 20 minutes. It will inform
you when it is done.
9. Verify that the images were imported properly by loading them onto the main image
window.
12.4.2.1 Importing ERS from Disk

ERS Import will also import ERS imagery from a disk file. To read a ERS image from tape to
disk, follow the procedure described above for RADARSAT.
After the image is on the disk, execute the steps above, except specify the disk file name
(output_image_name) rather than a tape drive.
SOCET SET Page 12-7

Chapter 13
ADS40 Import
Use ADS40 Import when you want to exploit an ADS40
image.
13.1 Overview
ADS40 Import reads ADS40 imagery from disk, CD-ROMs, or DVDs. It loads the imagery onto
the workstation disk and converts the header information into a compatible support file.
13.1.1 When to Use ADS40 Import

Use ADS40 Import when you want to exploit an ADS40 image. You run ADS40 Import after
creating a project. After importing a ADS40 image, you can proceed with triangulation (See
“When to Use Triangulation” on page 25-3) and then data extraction. Interior Orientation is not
required with ADS40 images, since the sensor is a digital camera, resulting in a known, fixed

ADS40 imagery is available in two basic formats: Leica Geosystems and ISTAR. The basic
components are very similar, but the layout of the files on disk is different. The main files are
support (“sup”), orientation (“odf”), camera (“cam”), and image (“tiff” or “ads”). For Leica files,
they are often located in different directories, for example:
xyz/10_52_NA-A_L1.sup
xyz/odf/10_52_NA-A.odf
xyz/odf/10_52_NA-A.odf.adj
xyz/cam/ADS40_0/v002/NA-A.cam
images/10_52_NA-A.ads
SOCET SET Page 13-1

Chapter 13 - ADS40 Import
ADS40 Import expects the files in directories like the ones above. However if you have difficulty
importing, try copying all the files to a single directory and trying again. For ISTAR, the files are
usually in one directory, for example:
NA-A.cam
t001ndt001s2_10000NA-A.odf
t001ndt001s2_10000NA-A_L1.sup
t001ndt001s2_10000NA-A_L1.tif
To open this window, select Preparation > Import > Image > ADS-40 on the main menu.
13.2 ADS40 Image Import
The ADS40 Image Import window's selections are as follows:
File > Open… Prompts you to select the support file.
Page 13-2 SOCET SET

Chapter 13 - ADS40 Import
File > Exit Exits ADS40 Image Import.
Options > Auto Minify Enable this to minify the imagery while importing.
Options > Post Interval The default Post Interval is 1000 pixels. This means that if you triangulate
the images a spline correction for the exterior orientation parameters will
be recovered with a post every 1000 pixels.
Help > Contents… Starts the on-line documentation.
SELECT TO
Copy images to Location Use this to control whether and how ADS40 Import copies the image files
Format while importing. To leave the images in the original location, un-check the
box. Otherwise check the box and select where you want to copy the
images and the new format.
Edit Names Use this to change the new support file naming.
Right-click on ADS40 files Use this to add, remove, or view information about items in the table.
Start Start importing the ADS40 data
13.3 Execution - ADS40

Use the following set of steps to import a ADS40 disk, CD-ROM, or DVD:
1. Start ADS40 Import by selecting Preparation > Import > Image > ADS40 on the main
workstation window.
workstation, select File > Load Project on the ADS40 Import window. Select a file from
the list and click OK.
3. Select File > Open… or right-click on the ADS40 Files and select the support files
(“*.sup”) you want to import.
4. [Optional] To view a display of certain data from the header records, right-click on a file
and select View Info…. When complete, click Close.
5. Set the image names, location, and format to values you want.
SOCET SET Page 13-3

Chapter 14
OrbView-3 Import
Use OrbView-3 Import when you want to exploit an OrbView-
3 image.
14.1 Overview
OrbView-3 Import reads ORBIMAGE’s OrbView-3 satellite imagery from disk, CD-ROM’s, or
DVD’s. It loads the imagery onto the workstation disk and converts the header information into
a compatible support file.
14.1.1 When to Use OrbView-3 Import

Use OrbView-3 Import when you want to exploit an OrbView-3 image. You run OrbView-3
Import after creating a project. After importing an OrbView-3 image, you can proceed with
triangulation (See “When to Use Triangulation” on page 25-3) and then data extraction. Interior
Orientation is not required with OrbView-3 images since the sensor is a digital camera, resulting
in a known, fixed relationship between each image pixel and the sensor lens.
14.1.2 OrbView-3 Format

OrbView-3 data is available in one format. OrbView-3 main files are product information
(“.pvl”), attitude (“.att”), ephemeris (“.eph”), and image (“.jpg” or “.ntf”).
SOCET SET Page 14-1

Chapter 14 - OrbView-3 Import
14.2 OrbView-3 Image Import

To open this window, select Preparation > Import > Image > OrbView3 from the main menu.
The OrbView-3 Image Import window’s selections are as follows:
File > Open... Prompts you to select the .pvl file, e.g. 3V0223.pvl.
File > Exit Exits OrbView 3 Image Import.

Refraction
Help > Contents... Starts the online documentation.
Page 14-2 SOCET SET

SELECT TO
Copy Images to Location Use this to control whether and how OrbView-3 Import copies the image
Format files while importing. To leave the images in the original location, un-
check the box. Otherwise check the box and select where you want to copy
the images and the new format.
Edit Names Use this to change the new support file naming.
Right-click on OrbView-3 Use this to add, remove, or view information about items in the table.
files
Start Start importing the OrbView-3 data.
14.3 Execution - OrbView-3

Use the following set of steps to import an OrbView-3 disk, CD-ROM, or DVD:
1. Start OrbView-3 Import by selecting Preparation > Import > Image > OrbView3 from the
workstation, select File > Load Project on the OrbView-3 Import window. Select a file
from the list and click OK.
3. Select File > Open... or right-click on the OrbView-3 files and select the .pvl files (“*.pvl”)
you want to import.
4. [Optional] To view a display of certain data from the header records, right-click on a file
and select View Info... When complete, click Close.
5. Set the image names, location, and format to values you want.
14.4 Batch Processing - OrbView-3 Import

COMMAND LINE:
% start_socet -single sat_import -a orbview3 -batch -s

setting_file
KEYWORD DESCRIPTION
input_file “readme” file(s) for the images you want to import. Repeat for each
OrbView-3 image.
copy_images Set to “YES” to copy the images to an Image Location. “Default is NO.”
SOCET SET Page 14-3

KEYWORD DESCRIPTION
chapter for values.
location.list
atmospheric_refraction (Optional) Set to "YES" to include the effect of atmospheric refraction for
the sensor model. Default value is "NO".
Page 14-4 SOCET SET

Chapter 15
GeoEye-1 Import
Use GeoEye-1 Import when you want to exploit a GeoEye-1
image.
15.1 Overview
GeoEye-1 Import reads GeoEye’s GeoEye-1 satellite imagery from disk. It loads the imagery
onto the workstation disk and converts the header information into a SOCET SET compatible
support file.
15.1.1 When to Use GeoEye-1 Import

Use GeoEye-1 Import when you want to exploit a GeoEye-1 image. You run GeoEye-1 Import
after creating a project. After importing a GeoEye-1 image, you can proceed with triangulation
(See “When to Use Triangulation” on page 25-3) and then data extraction. Interior Orientation
is not required with GeoEye-1 images since the sensor is a digital camera, resulting in a known,
fixed relationship between each image pixel and the sensor lens.
15.1.2 GeoEye-1 Format

GeoEye-1 data is available in one format. GeoEye-1 main files are product information (“.pvl”),
attitude (“.att”), ephemeris (“.eph”), and image (“.jpg” or “.ntf”).
SOCET SET Page 15-1

Chapter 15 - GeoEye-1 Import
15.2 GeoEye-1 Image Import

To open this window, select Preparation > Import > Image > GeoEye-1 from the main menu.
The GeoEye-1 Image Import window’s selections are as follows:
File > Open... Prompts you to select the .pvl file, e.g. 3V0223.pvl.
File > Exit Exits GeoEye-1 Image Import.

Refraction
Page 15-2 SOCET SET

Chapter 15 - GeoEye-1 Import
SELECT TO
GEO-EYE-1 Files Identify the names of GEO-EYE-1 files. You can view information on a
Output Images / Copy To enable or disable copying the pixel files to a new image location. If you
images to disable “Copy images to”, the images will remain in their original location.
If you enable “Copy images to”, use Location to select the image location
for the new image and Format to select the format you want the new image
to be.
Edit Names Change the name of the output image or support.
Start Begin the import process..
15.2.1 Batch Processing - GeoEye-1 Import

COMMAND LINE:
% start_socet -single sat_import -a geoeye1 -batch -s

setting_file
KEYWORD DESCRIPTION
input_file Pvl file(s) you want to import. Repeat for each image.
15.2.2 GeoEye-1 Next Step

After you have imported a single image, display it in the main image window. You can perform
image enhancement operations, and perform annotation and geopositioning. If you have control
data, you should run Triangulation. If you have imported a stereo image pair, you should execute
Triangulation next. Run Rectification in the pairwise mode, usually followed by Automatic
Terrain Extraction.
SOCET SET Page 15-3

Chapter 16
Data Import and Export

Data import and export addresses data in and out of
SOCET SET to other systems or software packages.
16.1 Overview
Import and Export are the words used to describe the process of getting data files into or out of
the workstation. Such data files include the following:
• ASCII Ground Point Import files
• ASCII Image Point Import files
• Image files See “Image Import and Export,” Chapter 7.
• Terrain files (in digital format, also know as Digital Terrain Model or DTM)
See “Terrain Import and Export,” Chapter 17.
• Feature files (also known as vector files)
See “Feature Import and Export,” Chapter 18.
SOCET SET
Import
Other System Import /
(such as a GIS or Database in Export Internal
Simulator) interchange Software SOCET SET
format Export Process Databases
16.1.1 When to use Import and Export

Importing is required when a data file is available from another source and you wish to use the
data in the file on the workstation. For example, if you have some DTED terrain data you will
need to import it into the workstation before you can display or edit it.
Exporting is used when you have generated some data on the workstation and want to make it
available for use by another system or software package. For example, if you have populated a
SOCET SET Page 16-1

Chapter 16 - Data Import and Export
GIS with V e c t o r D a t a extracted by the workstation, you will need to export it from the
workstation to your GIS.
Importing and exporting are necessary because systems usually have unique internal data formats
and cannot directly process data from other systems. For that reason, data files must be converted
to common interchange formats in order to exchange the data between systems. The common
interchange formats include formats such as:
SENSOR SUPPORT DATA IMAGE (PIXEL FILES) TERRAIN VECTOR/FEATURE
• Frame • Sun Raster • DTED • DXF

(conventional • CVL • ASCII • Intergraph
camera; including DGN Feature
Albany and PAT-B) • Digital • NED
Orthophoto • DEM - • Arc Gen/Arc
• SPOT Quadrangle Lin
7.5
• Landsat (DOQ) minute • Shapefile
• JERS • Plain Raster UTM • ESRI SDE
• Panoramic • TIFF type
• Generic Polynomial • Tiled (VITec) • Intergrap
(Fast) h DGN
• TARGA Post
• Special Sensors • LHS Scanner • Arc Grid
• PPDB • NITF -
• DPPDB including JPEG
• ReconnaissanceMap compressed
Projections • Intergraph COT
• Terra Source
• Orthophoto
• DOQ
• IKONOS
Interchange formats are usually simple ASCII files that lend themselves to portability and
simplicity and are not optimized for response time or storage size. For these reasons, interchange
formats are generally not used as internal database formats by the workstation.
16.1.2 Locating Files on the Disk

If you are importing and exporting data between SOCET SET and other systems it can be
confusing keeping track of where the files are located on your disk. The following table will assist
you locating misplaced files:
FILE TYPE INTERCHANGE FORMAT INTERNAL FORMAT
Image Files These files can be in any directory you specify. These files can be in any Image
The default location is the directory indicated Location (see the “File
by the environment variable Organization” appendix for details).
IMPORT_EXPORT_PATH.
Non-Image Files These files can be in any directory you specify. These files must be in the project
(Terrain, Feature, The default location is your project’s data data directory of the current project,
Ground Points. directory, <install_path>/data/ <install_path>/data/
etc.) <projectname>. <projectname>.
Page 16-2 SOCET SET

16.2 ASCII Ground Point Import

Ground Point Import reads ground point data in an ASCII format into the internal Ground Point
File Format. The input ASCII file is restricted to one ground point per line. Each ground point
contains a point ID along with an (X,Y,Z) coordinate. This information can be in any order, but
it must all be on one line.Obtaining this window is as simple as clicking Preparation > Import >
ASCII Ground Point Import on the main workstation.
Ground point control types of horizontal, 3-dimensional, and vertical are used within
SOCET SET. Ground points which have a value of 0.0 exactly will cause the control point type
setting to change. If your data has a control point of 0.0 0.0 3.2, the point type will be set to
vertical (Z only). If your data has a value of 2456.8 23778.9 0.0, the point type will be set to
horizontal (X and Y only).
You use ASCII Ground Point Import to translate and import ground point data from an external
source into the native SOCET SET ground point file format. The units of the data can be either
decimal for UTM, grid, LSR, or Geographic projects (see below), or degrees minutes seconds for
any project. Degrees minutes seconds must be entered as “+-DD:MM:SS.SSS”. The presence of
two colons is mandatory. When you create a Geographic project, you specify a preference for
coordinate display. If you import a file with decimal numbers into a Geographic project whose
display preference is “dd.dddd” the numbers will be interpreted as decimal degrees. For all other
Geographic projects, decimal numbers will be interpreted as radians.
The ASCII Ground Point Import window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project to import the ground points
into (only if started stand-alone).
File > Save File Format Saves any changes made to the Input File format via the Create Input
Format option.
File > Exit Closes the ASCII Ground Point Import window.
Options > Edit Input Prompts you to specify the order of the ground point information in the
Format... input file.
Options > Set Accuracy... Prompts you to specify the values for the (X,Y,Z) accuracy in the internal
format. The defaults are zero.
SOCET SET Page 16-3

SELECT TO
Project Identify the name of the project into which the ground points will be
imported. By default, this is the name of the project that is currently loaded
on the workstation.
Input File Format Select the name of the format file.
Input ASCII Ground Point Select the name and path of the input file.
File
Output Ground Point File Identify the name and path of the output file. You can modify this field
directly to specify a different path and/or file name.
16.2.1 Edit Input Format Option

This window provides you with a way to specify the order of the information in the input file.
Click Options > Edit Input Format on the ASCII Ground Point Import window. You can save
this ordering in an input format file for later use with other ground point files.
The Fields column on the right of the ASCII Ground Point Import window (above), indicates the
current order. To change a field setting, select the desired format from Format Selection on the
left. Then click on the appropriate field on the right.
There are seven format settings from which to select: ID, X, Y, Z, Code, Ignore, and Illegal.
• “Code” has no meaning for ASCII Ground Points.
• “Ignore” is used to ignore any information that may be specified in a field.
• “Illegal” indicates that a field should not contain any information. The entire point
is discarded should any information be found in a field marked as “Illegal.” The
following are some examples of legal settings for the input fields.
EXAMPLE 1 EXAMPLE 2 EXAMPLE 3
1: ID 1: Y 1: Ignore
Page 16-4 SOCET SET

EXAMPLE 1 EXAMPLE 2 EXAMPLE 3
2: X 2: X 2: X
3: Y 3: Z 3: Y
4: Z 4: Illegal 4: Z
5: Ignore 5: Illegal 5: Code
6: Ignore 6: Illegal 6: Ignore
16.2.2 Execution of Ground Point Import

Use the following set of steps to import a file of ASCII ground points:
1. Click Preparation > Import > ASCII Ground Points on the main workstation menu to start
ASCII Ground Point Import.
2. Click File > Load Project on the ASCII Ground Point Import window if not already chosen.
Pick the project you wish to import the point data into. Click OK.
3. Click Input File Format on the ASCII Ground Point Import window. Pick the name of an
input file format. Click Save.
4. [Optional] Modify the input file format by doing the following:
a. Click Options > Edit Input Format... on the ASCII Ground Point Import window.
b. Enter the ground point format field and ordering information in the Edit Input Format
window. Click OK.
c. To save this format for future use, click File > Save File Format... on the ASCII
Ground Point Import window.
5. Click the Input ASCII Ground Point File on the ASCII Ground Point Import window.
Select the name of the point file you wish to import. Click OK.
6. Click Options > Set Accuracy... on the ASCII Ground Point Import window. The accuracy
is used in the bundle adjustment triangulation programs to “weight” the control points. You
should enter realistic X, Y, and Z accuracy values.
7. Type the output filename in the Output Grnd Pnt File field.
8. Click Start to import the ground points.
16.3 ASCII Image Point Import

Image Point Import reads image points (plate coordinates corrected for camera offsets and lens
distortions if appropriate) for the purpose of performing an automated triangulation or orientation
of an image or multiple images. You use Image Point Import to import plate coordinates into the
workstation’s internal format and used (in conjunction with ground points, which you can also
import) for immediate triangulation.
SOCET SET Page 16-5

Image Point Import creates a SOCET SET image point file (.ipf) image’s plate coordinates that
are supplied in the imported file. The base names of the image point files are automatically set to
the image names in the input image point file. See the figure in the “SPOT Import Chapter.”
Triangulation uses the convention that image support file

names .sup have the same base name as the image point file
.ipf names. Therefore, in order to make the image point files
usable by Triangulation, you must make sure that the base
names of the image support and image point files are the same
when you import your images and corresponding point file.
The ASCII Image Point Import window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project to import the ground points
File > Exit Exits the ASCII Image Point Import window.
Plate Format Type > patm See PATM format description below.
plates
Plate Format Type > stereo See STEREO format description below.
plates
SELECT TO
Project Identify the name of the project into which the image points will be
on the workstation.
Input File Identify the name and path of the input file of image points you selected.
Plate Format Type Select stereo, patm, patb, or albany plates. See further format description
below.
Page 16-6 SOCET SET

SELECT TO
Sig. X (um), Sig Y Identify the measurement accuracy values.
Pix Size (um) Approximate scan resolution.
16.3.1 PATB Image Point File Format

“Patb.exp” files are fiducial coordinate correcting film stretch only. The resultant .iop file
from import contain fiducial coordinates which are true plate coordinates corrected for film
stretch and principle point offset.
16.3.2 PATM Image Point File Format

If you choose the PATM image point file format, your input file must have the following format:
image_id1 dummy
point_id1 x_um y_um
point_id2 x_um y_um
...
point_idn x_um y_um
-99
image_id2 dummy
point_id1 x_um y_um
...
point_idn x_um y_um
-99
...
image_idn dummy
point_id1 x_um y_um
...
-99
Where image_id1-image_idn are 10-character image identification strings, and

point_id1-point_idn are the image point identifiers for each image. The coordinates, x_um and
y_um must be in micrometers. Fields labelled dummy must be present but are ignored.
This file is column independent except for the 10-character image identification string, which
must be in the first 10 columns of the first line of each image frame. An example follows:
111070152106.000 0
11107049 4342.6 -10571.8
11107009 2092.1 92375.2
11106909 87538.4 86812.4
11106949 88468.8 9120.0
11106989 94163.2 -80915.5
11107089 -4149.1 -90378.5
11107069 183.8 -47946.6
SOCET SET Page 16-7

-99
111.69152106 0
11106949 -6658.4 12936.1
11106909 -2724.2 91548.3
11106809 85649.5 73872.1
11106849 90207.4 3636.9
11106889 91799.6 -83895.8
11106989 -1543.0 -77301.7
11106969 -5618.3 -23556.6
11106929 2313.4 54003.6
-99
16.3.3 STEREO Image Point File Format

If you choose the STEREO image point file format, your input file must have the following
format:
idl1idr1 dummy dummy dummy dummy
dummy dummy dummy dummy dummy
point_id1 left_x_mm left_y_mm right_x_mm right_y_mm
point_id2 left_x_mm left_y_mm right_x_mm right_y_mm.
...
point_idn left_x_mm left_y_mm right_x_mm right_y_mm.
-99
idl2iidr2 dummy dummy dummy dummy
Page 16-8 SOCET SET

...
point_idn left_x_mm left_y_mm right_x_mm right_y_mm.
-99
idlniidrn dummy dummy dummy dummy
...
-99
Where idlx and iilx are the 4-character left and right image identification strings for the xth image
pair. point_id1-point_idn are the image point identifiers, and left_x_mm, left_y_mm, right_x_mm,
right_y_mm are the coordinates for each pair, in millimeters. Fields marked with dummy are
required but ignored.
This file is column independent.
An example of this format is as follows:
38763875 0.000 0.000 0.000 0.000
1000 0.000 0.000 0.000 0.000
2000 0.000 0.000 0.000 0.000
3000 0.000 0.000 0.000 0.000
4000 0.000 0.000 0.000 0.000
409387701 -13.721 98.906 -96.742 96.579
409387702 -12.556 99.704 -95.643 97.463
409387703 -7.405 -11.749 -83.830 -13.698
409387704 3.319 -14.133 -73.130 -15.541
409387705 -13.496 -108.518 -84.892 -109.714
409387706 -5.569 -82.818 -79.392 -84.092
409387707 -5.582 -82.956 -78.400 -84.230
-99
SOCET SET Page 16-9

38753874 0.000 0.000 0.000 0.000
1000 0.000 0.000 0.000 0.000
2000 0.000 0.000 0.000 0.000
3000 0.000 0.000 0.000 0.000
4000 0.000 0.000 0.000 0.000
9387601 -3.943 100.932 -86.283 102.304
99387601 -3.916 100.860 -86.254 102.233
9387602 12.716 92.576 -69.366 93.234
409387601 13.015 10.057 -70.755 11.207
409387602 13.078 9.686 -70.710 10.837
9387604 -1.154 -102.129 -87.541 -98.996
99387604 -1.223 -101.970 -87.600 -98.839
409387507 91.761 78.140 7.479 75.644
-99
16.3.4 ALBANY Point File Format

If you choose the ALBANYimage point file format, your input file must have the following
format:
column 0 :blank
columns 1-3: integer strip id
columns 4-6: integer image id
columns 7-13: integer point id
columns 14-27: double x coordinate
columns 28-40: double y coordinate
Strips are separated by -1
16.3.5 Execution of Image Point Import

1. Click Import > ASCII Image Points on the main workstation window to start ASCII Image
Point Import.
2. Click File > Load Project on the ASCII Image Point Import window. Select the project you
wish to import the point data into (stand alone only. Click OK.
3. Click Input File... on the ASCII Image Point Import window. Select the name of the image
point file you wish to import Click OK. Remember that the base name of this file should
match the base name of the corresponding image support file.
4. Select the Plate Format Type that you are importing.
5. Set the Sig. X and Y to a reasonable accuracy value (5 to 10 microns typical).
6. Set the Pix Size to the approximate scan resolution (25 microns typical).
7. Click Start to import the image points.

8. Verify that you now have an image point file (.ipf) for each image in your file. These
files are placed in your project’s data directory.
You can now proceed directly to Triangulation Solve.
16.3.6 Batch Processing - Import ASCII Image Points

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type import_asc_ip
input_file File name (with full path prefix) of input ASCII file.
plate_format Format of input file:

PLATE_STEREO, PLATE_PATM, PLATE_PATB, or
PLATE_PATB_LEFT, or PLATE_ALBANY.
sig_x X accuracy in microns. Values of 5 to 10 are typical.
sig_y Y accuracy in microns. Values of 5 to 10 are typical.
pix_size Scan resolution. Value of 25 microns are typical.

Chapter 17
Terrain Import and Export

Terrain Import and Export covers the import and export
conversion of several interchange formats.
17.1 Overview
SOCET SET performs DTM format conversions for several interchange formats. These formats
are divided into two section, Imports and Exports. The individual terrain data formats are listed
as follows:
IMPORTS EXPORTS
ASCII DTM Import ASCII DTM Export
NED GridFloat Import NED GridFloat Export
ASCII ARC Grid Import ASCII ARC Grid Export
DEM Import DEM Export
DTED Import DTED Export
LIDAR Import
SDTS Import SDTS Export
GeoTIFF Import GeoTIFF Export
NITF Import NITF Export
DGN Data Format

Conversions
GSI DEM Import
. BIL Terrain Import
17.2 ASCII DTM Import

ASCII DTM Import imports terrain data in ASCII format into the workstation’s internal DTM
format.
SOCET SET Page 17-1

Chapter 17 - Terrain Import and Export
Since there are a wide variety of ASCII DTM formats, you must define the format of the data in
the input file. The X, Y, Z, ID, and CODE fields can be in any position (with a maximum of six
fields per line); the ID and CODE fields are optional. You must make sure that the units of XYZ
in the ASCII DTM match the corresponding units in the project. For example, if the project has
XY coordinate unit “radian” and Z coordinate unit “feet,” the ASCII DTM must have exactly the
same units. To open this window, click Preparation > Import > Terrain > ASCII DTM on the
ASCII DTM DTM POINT CODE

INPUT DATA FILE FORMAT DEFINITION DEFINITION
ASCII DTM
IMPORT
SOCET SET
DTM
The ASCII DTM Import window’s selection are as follows:
File > Load Project Prompts you to pick the name of the project into which you will import the
DTM (only if started stand-alone).
File > Save File Format Saves changes to an input file format file that you made with the Create
Input Format option.
File > Save Code Saves changes to a code description file that you made with the Define
Descriptions Point Codes option.
File > Exit Exits the ASCII DTM Import window.
Options > Edit Input Format Displays a window which prompts you to define the format of the input
DTM.
Options > Define Point Displays Assign Code Descriptions window, which prompts you to define
Codes the point code values and code descriptions.
Options > Change X and Y Prompts you to specify the output DTM spacing.
Spacing
Options > Select ATE Prompts you to select images for ATE.
Images
Options > Display Number Displays the number of posts in the input DTM.
of Points
Page 17-2 SOCET SET

Options > Output DTM Prompts you to select the output DTM format.
Format For grid output, the type of file used as input must be specified.
NOTE: Most of the time, irregular input should be used as input
file. In very rare cases, you may use Grid Input if you are sure that
the post spacing in the ASCII file is the same as specified for the
output DTM, and the order of points in the ASCII file is starting
from the lower left corner and increment in the X direction first
SELECT TO
Project Name of the project into which the DTM will be imported. By default, this
is the name of the project that is currently loaded on the workstation.
Input File Format Name of the DTM format definition file you selected.
Code Description Name of the point code description file you selected.
Coordinate Format Allows you to choose either decimal degrees or radians as the input format
of the ASCII file. This is only sensitized while working with Geographic
projects.
Input ASCII DTM List of names of ASCII DTMs to be imported.
Right Click - Add Prompt you to pick the name of an ASCII DTM input file. You can pick
more than one input file name in the file selection dialog.
Right Click - Delete Remove the input file names from list. You can pick more than one file to
remove at a time.
Output DTM Type the name of the output image support file, followed by pressing
<Enter> on the keyboard.; the software will attach an extension.
Start Begin importing.
17.2.1 Executions
17.2.1.1 Execution - Defining an Input Format
Use the following set of steps to edit or create an input file format definition:
1. Start ASCII DTM Import by clicking Preparation Import > Terrain > ASCII DTM on the
2. Click the tool button next to File Format on the ASCII DTM Import window. Pick the name
of an existing format definition. Click Save. If you want to create a new file, you will
specify the new file name.
SOCET SET Page 17-3

3. Click Options > Edit Input Format on the ASCII DTM Import window. The dialog window
at right appears.
4. For each field in the input file, you must specify what type of data that field contains.
5. For example, to indicate that the fourth field contains a point code, first select the “Code”
item in the Format Selection list. This highlights the word “Code.” Then click “4:” line in
the Fields list. Note that the format word in the Fields list next to the “4:” changes to the
word “Code.”
6. Repeat this procedure for each of the fields present in your ASCII DTM input file.
Typically, a DTM input file will have X, Y, and Z fields; you should set the remaining fields
to “Ignore.”
7. When you are finished, click OK to accept the changes to the format definition. If you wish
to abort your changes, click Cancel.
8. Now, enter the name of the new input format definition file in the Input File Format field
on the ASCII DTM Import window. To write the new file, click File > Save File Format
on the ASCII DTM Import window.
17.2.1.2 Execution - Defining Point Codes

Point codes ensure that geomorphic features such as ridges and drains correctly map to the DTM
grid. If you are going to make use of the point codes in your input DTM, you need to create a file
that defines the meanings of the various point codes.
If you intend to use a point code definition file, only points with
defined codes will be imported.
Three possible point code descriptions are supported: Start Line, Continue Line, and Single Point.
Use Continue Line for point codes which mark the end of a line.
Use the following set of steps to create or edit a code description file:
1. Click (ellipse tool button) next to File Format on the ASCII DTM Import window. Pick
the name of an existing file.
2. Click Open. If you want to create a new file, you will specify the new file name later, prior
to saving your changes.
Page 17-4 SOCET SET

3. Click Options > Define Point Code on the ASCII DTM Import window. The Assign Code
Descriptions window appears.
4. To add a new point code to a description, first click the name of the description in the Code
Descriptions list. This highlights the name you selected, and displays the list of point codes
that are currently defined. Next, click in the Enter Code text field and type the point code
number to add, followed by a carriage return. The new point code you entered appears in
the Point Codes list. Repeat for each of the new point codes you wish to assign.
If you enter a point code that appears in the list for one of the
other code descriptions, it will be removed from the other list,
ensuring that you don’t accidentally assign the same code to
two different lists.
5. When you are finished entering the point codes, click OK to accept your changes and close
the dialog window. If you wish to abort your changes, click Cancel.
6. To save your changes to a new file, click File > Save Code Descriptions on the ASCII DTM
Import window. The Select New Description File window pops up to prompt you to enter
the name of file to save to.
7. [Optional] If you wish to clear out all code definitions, exit the Assign Code Descriptions
window by selecting <Shift>Cancel.
17.2.1.3 Execution - Changing the DTM Spacing and Selecting ATE Images
You can use the following set of steps to specify the output DTM spacing:
1. After you have specified your format file and your input DTM, click Options > Change X
and Y Spacing on the ASCII DTM Import window. The dialog window shown appears:
SOCET SET Page 17-5

2. Enter the new X and Y spacing (and the units of your spacing values). Click OK.
3. If you need to run ATE on the DTM, you must select images for ATE. You can use the
following steps:
a. Click Options > Select ATE Images from the ASCII DTM Import window.
b. Click ADD by clicking RMB within the selection window. Selection window will
open. Highlight appropriate support file, then click OK.
c. Either add additional files or removed support files from the list, then click OK
17.2.1.4 Execution - Importing an ASCII to DTM

Use the following set of steps to import a DTM:
1. Click Preparation > Import > Terrain > ASCII DTM on the main workstation window to
start ASCII DTM Import.
2. Click File > Load Project on the ASCII DTM Import window. Pick the project you wish
to import the DTM into and click OK.
3. Click the tool button next to File Format on the ASCII DTM Import window.
a. Pick the name of a format file which describes the format of your input DTM. Click
Save.
b. [Optional] Pick the name of a file which contains the point code descriptions for your
input DTM. Click Open.
4. [Optional] Click the tool button next to the Code Descriptions on the ASCII DTM Import
window. Pick the name of a file which contains the point code descriptions for your input
DTM. Click Save.
5. Type the name of the output DTM in the Output DTM field, by pressing [Enter] on the
keyboard.
6. Click Start to import the DTM. If the size of the output DTM is too large, you will get a
warning dialog telling you that you are about to create a “Large number of output DTM
points.” If you wish to continue processing, click OK. If you wish to abort without
importing, click Cancel.
17.2.1.5 Execution - Importing an ASCII Tie Point File to DTM

Using the following set of steps to import a ASCII Tie Point File to DTM.
1. Click Preparation > Import > Terrain > ASCII DTM on the main workstation window to
open the ASCII DTM Import window.
2. Click the tool button next to File Format on the ASCII DTM Import window. Select Seed
Point.dtm.
3. Right Click Add in the Input ASCII DTM selector. Select tie point file (file with extension
.agp) and click OK. See “Ground Point File (.gpf)” on page 25-11 on how to generate Tie
Point files with .agp extensions.
Page 17-6 SOCET SET

4. Click Options > Output DTM Format > Tin Triangles.

5. Enter Output DTM name by clicking in the text box and entering a file name.
6. Click Start.
17.2.2 Batch Processing - Import ASCII DTM

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type import_asc_dtm
input_asc_files List of file names (with full path prefix) of input ASCII files. File names
are separated by a semicolon (;).
output_dtm_file File name (with full path prefix) of output DTH file.
field_order Defines the columns of the input file. Five digit number with no spaces
between digits. Digits are: 1=X;2=Y; 3=Z; 4=code; 5=ignore. Example:
12354. See Terrain Import/Export chapter for more details.
x_accuracy (Optional) Variance in X (project units squared).
y_accuracy (Optional) Variance in Y (project units squared).
z_accuracy (Optional) Variance in Z (elevation units squared).

Accuracy values used to compute circular and linear errors.
code_file File name (with full path prefix) of input code description file.
x_spacing Number of spacing units between posts in the x direction.
y_spacing Number of spacing units between posts in the y direction.
output_spacing_ OUTPUT_TRIANGLES,
mode OUTPUT_GRID_INPUT_IRREGULAR,
OUTPUT_GRID_INPUT_GRID
spacing_units Character string specifying the spacing units. May be one of the following:
unit_feet, unit_meters, or unit_seconds.
input_units Units into which to export the DTM. Units can be radians
(UNIT_RADIANS) or decimal degrees (UNIT_DEGREES).
SOCET SET Page 17-7

17.3 NED GridFloat Import

NED GridFloat Import imports terrain data in the National Elevation Dataset format into the
workstation’s internal DTM format. To open this window, click Preparation > Import > Terrain
> NED GridFloat on the main workstation window. SOCET SET will import files in USGS NED
GridFloat format.
The NED GridFloatImport window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project to import the GridFloat into
(only if started stand-alone).
File > Exit Exits the NED GridFloat Import window.
SELECT TO
Input NED (FLT) File Prompts you to pick a NED file to import.
Output DTM Type in the name of the output DTM. Terminate your entry with a carriage
return.
17.3.1 Execution - NED GridFloat Import

Use the following set of steps to import a NED file:
1. Click Preparation > Import > Terrain > NED on the main workstation window to start
NED GridFloat Import.
2. [Stand Alone Only] Click File > Load Project on the NEDGridFloat Import window. Pick
the project you wish to import the NED into and click Open.
3. Click (ellipse tool button) next to Input NED (FLT) File on the NED GridFloat Import
window. Pick the name of the NED file you wish to import. Click Open.
4. Type the name of the output DTM in the Output DTM field, followed by a carriage return.
5. Click Start to import the NED.
Page 17-8 SOCET SET

17.3.2 Batch Processing - Import NED GridFloat

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type import_gridfloat
input_flt_file File name (with full path prefix) of input FLT file.
input_hdr_file File name (with full path prefix) of input HDR file.
input_prj_file File name (with full path prefix) of input PRJ file.
SOCET SET Page 17-9

17.4 ASCII ARC Grid Import

ASCII ARC Grid Import converts ARC/INFO’s ASCII Grid format into the SOCET SET
workstation’s internal DTM format.
When importing an ARC Grid file, it will be assumed that the coordinate system, projection,
datum, vertical reference, and units of the file match those same files you are importing into the
SOCET SET project. To open this window, clicking Preparation > Import > Terrain > ARC Grid
ASCII ARC
GRID DATA FILE
ARC GRID
IMPORT
SOCET SET DTM
The ASCII ARC Grid Import window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project to import the ARC Grid file
File > Input ARC GRID File Prompts you to pick an ARC Grid file to import.
File > Exit Exits the ASCII ARC Grid Import window.
SELECT TO
Project Identify the name of the project into which the ARC Grid file will be
on the workstation.
Input ASCII ARC Grid File Identify the name of the input ARC Grid file you selected.
Output DTM Type the name of the output DTM, followed by a carriage return.
Lower-Left / Cell size (Geographic projects only) Allow you to select the coordinate format of
Format the Lower-Left coordinate and Cell size in the input ARC Grid file. You
may select Decimal Degrees, Arc Seconds or Radians.

17.4.1 Execution - Importing an ASCII ARC Grid File

Use the following steps to import an ASCII ARC Grid file:
1. Click Preparation > Import > Terrain > ARC Grid on the main workstation window to
start ARC Grid Import.
2. Click File > Load Project on the ASCII ARC Grid Import window. Pick the project that
you wish to import the ARC Grid file into and click Open.
3. Click (ellipse tool button) next to Input ASCII ARC GRID File on the ASCII ARC Grid
Import window. Pick the name of the ARC GRID file you wish to import. Click Open.
4. [Optional] If you are importing the ARC Grid file into a Geographic project, select the geo-
coordinate format of the Lower-Left coordinate and Cell size in the ARC GRID file by
selecting either Radians, Decimal Degrees, or ARCseconds.
5. Specify where to write the output DTM by typing the file name in the Output DTM field on
the ASCII ARC Grid Import window, followed by a carriage return.
6. Click Start to import the ARC Grid file.
17.4.2 Batch Processing - Import ASCII ARC Grid

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type import_asc_arc_grid
input_grid_file File name (with full path prefix) of input ARC Grid file.
output_dtm_file File name (with full path prefix) of output DTM.
geo_coord_format (For Geographic projects only) Character string specifying the coordinate
format of the Lower-Left Corner and Cell size in the ARC Grid file. May
be one of the following: radians, degrees, or seconds.
17.5 DEM Import

To open this window, click Preparation > Import > Terrain > DEM on the main workstation
window. SOCET SET will import files in USGS DEM 7.5 minute and 1 degree formats. (No other
USGS formats are currently supported.)

The project you import the 7.5 minute DEM into must be in the UTM coordinate system. The
project you import the 1 degree DEM into must be in the geographic coordinate system.
The vertical reference of the project must be set to Mean Sea

Level, not ellipsoid.
The DEM file may have information in it specifying a datum for the elevation values. This is an
optional field. If it is present, DEM Import will convert the elevation values using the DEM datum
and the project datum. If it is not present, DEM Import will use the project datum to locate the
elevations.
USGS files do not always have the datum flag set correctly, thus ensure your project datum
matches the datum of your input DEM. For example, to import a NAD27 DEM into a NAD83
Project, perform the following.
Import the NAD27 DEM into a NAD27 project, then copy the NAD27 Terrain files into the
NAD83 project by clicking on Project > Copy on the main workstation window. See “Copy
Project” on page 5-16 for further details.
The DEM Import window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project to import the DEM into (only
if started stand-alone).
File > Exit Exits the DEM Import window.
SELECT TO
Input DEM Prompts you to pick a DEM file to import.
return.
DEM File Type Specify the input DEM file extent. (7.5 Minute & 1 Degree)

17.5.1 Execution - DEM Import

In order to import a DEM file from a tape, you must transfer it to a disk file before beginning
DEM Import. For example: cat /dev/rmt/0 > <install_path>/images/xyz.dem.
Use the following set of steps to import a DEM file:
1. Click Preparation > Import > Terrain > DEM on the main workstation window to start
DEM Import.
2. Click File > Load Project on the DEM Import window. Pick the project you wish to import
the DEM into and click Open.
3. Click the (ellipse tool button) tool button next to Input DEM File on the DEM Import
window. Pick the name of the DEM file you wish to import. Click Open.
5. Click Start to import the DEM.
The Absolute RMS Error (X, Y, Z) of the DEM will transfer over
to the DTM CE/LE accuracies. Relative RMS Errors in the DEM
will be discarded on import.
17.5.2 Batch Processing - Import DEM

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type import_dem
input_dem_file File name (with full path prefix) of input DTH file.
dem_type Name defining dem format. May be one of the following:

dem_7_5_minute, or dem_1_degree.
17.6 DTED Import

Digital Terrain Elevation Data (DTED) is a product of the National Geospatial-Intelligence
Agency (NGA) used to store digital terrain data. The data covers a single 1° by 1° region bounded
by the integer 1° latitudes and 1° longitudes of a geographic reference system. The data post
spacing is either 3 arcseconds (Level I) or 1 arcsecond (Level II).

DTED Import will import DTED files from the following media:
CD-ROM
Disk File
DTED DATA DTED SOCET SET
IMPORT DTM
8-mm Tape
(dd format) 9-Track Tape
DTED is supplied by the NGA on 9-track tape or CD-ROM, but you may occasionally find it on
8mm tapes if it has been transferred by an intermediary.
You may copy DTED from tape to disk (or vice versa). If you do this you should use the Unix dd
command, not the tar command.
If the DTED file is on a tar format tape, the file must be extracted onto disk using the “tar”
command. Only then can it be imported with DTED Import. To open this window, click
Preparation > Import > Terrain > DTED on the main workstation window.
The DTED Import window’s selections are as follows:
File > Load Project (only available if started stand-alone).
File > Read DTED from File Prompts you for the name of disk or CD-ROM file from which to read the
DTED.
File > Read DTED from Prompts you for the name of a tape device from which to read the DTED.
Tape NOTE: Not supported on Windows Platform.
File > Exit Exits the DTED Import window.

SELECT TO
Input DTED File Display the name of the selected tape device or file from which to read.
Output DTM Type the name of the output DTM, followed by a carriage return.
DTED Editor Pop up a GUI displaying the DTED Header information. It then allows you
to save the Header information to text file for later use in DTED Export.
Start Start importing the DTED.
17.6.1 Execution - DTED Import

Use the following set of steps to import DTED data:
1. Start DTED Import by clicking Preparation > Import > Terrain > DTED on the main
workstation window.
2. Depending on the source of the DTED data, click either File > Read DTED or File > Read
DTED for Tape (depending if the DTED is on disk or CD; or Tape) on the DTED Import
window. You must then make your selection in the pop-up File Selection. Click Open.
For CD-ROM, if it is not mounted, refer to section “CD-ROM -

How to Use” in the System Administration Manual for
SOLARIS; when the File Selection box pops up, enter the
filename on the CD-ROM. For Solaris the path is in lower case
and starts with /cdrom.
4. Click Start to import the DTED.

17.6.2 Batch Processing - Import DTED

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type import_dted
input_file Input file name with full path prefix if not from tape. Use with CD-ROM
or file.
hostname Hostname of computer device is mounted on, if not using input file.
driver Name (with full path prefix) of tape device, if not using input file.
code Single character specifying device type. May be one of the following: N
for 9 track tape, E for 8mm tape, Q for 1/4 inch tape, C for CD_ROM. Tape
media not supported for Windows platform.
17.7 SDTS Import

The software will import files in USGS SDTS format. The project you import the SDTS terrain
into, must be in UTM or geographic coordinate system.
The vertical reference of the project must be set to Mean Sea Level, not ellipsoid. In order to get
maximum accuracy, import SDTS terrain data into a project with matching coordinate system and
datum.
If your project is in a different coordinate system or datum, you have two alternatives to import
SDTS terrain data into your project:
1. Create a temporary project with coordinate system and datum same as in SDTS data. Import
SDTS into the temporary project. Then use Project > Copy to transfer the DTM from the
temporary project to your project.
2. Import SDTS terrain data directly into your project. The import will convert the terrain data
into the coordinate system and datum of your project. Be aware that the imported DTM may
be slightly different from the DTM created following alternative 1 above.

The SDTS Import window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project to import the SDTS into (only
if started stand alone).
File > Exit Exits the SDTS Import window.
SELECT TO
Input SDTS file Prompts you to pick up a SDTS file to import. You can choose any file
from the SDTS directory.
Output DTM Type the name of the output DTM. Terminate your entry with a carriage
return.
17.7.1 Execution - Import SDTS

Use the following set of steps to import a SDTS set of files:
1. Click Preparation > Import > Terrain > SDTS on the main workstation window to start up
SDTS Import.
2. Click File > Load Project on the SDTS Import window. Select the project you wish to
import the SDTS into and click Open.
3. Click the tool button next to Input SDTS File on the SDTS Import window. Select the name
of one of the SDTS files (*.DDF) you wish to import and click Open.
5. Click on the Start button to import the SDTS.

17.7.2 Batch Processing - Import SDTS

COMMAND LINE:
% start_socet – single data_convert –batch –s setting_file
KEYWORD DESCRIPTION
conversion_type import_sdts
input_sdts_file File name (with full prefix) of input SDTS file.
output_dtm_file File name (with full prefix) of output DTH file
Project_file File name (with full prefix) of project file.
See “SDTS” on page E-21 for an example.
17.8 GSI DEM Import

The Geographical Survey Institute (GSI) is a national surveying and mapping organization who
controls specifications in Japan. 50m GRID (Elevation) data, which is one of the GSI’s digital
map data, is a 50m MESH DEM extracted and calculated from the contour lines of exiting
1:25,000 topographical map. Although it is called 50m GRID or MESH data, the space between
posts is not evenly 50m for Latitude and Longitude.
They defined the so-called 2nd Mesh which, in most cases, exactly corresponds to each 1:25,000
map sheet. Then they divided this 2nd Mesh by 200 both in Latitude and Longitude directions,
which creates approximately 50m x 50m grids.
To open this window, click Preparation > Import > Terrain > GSI on the main workstation
window.

The GSI DEM Import window’s selections are as follows:
File > Load Project... Prompts you to pick the name of a project which the GID DEM files will
be imported.
File > Open Input GDI DEM Prompts you to pick GSI DEM files to import.
File > Exit Exits the GSI DEM Import window.
SELECT TO
Input GSI DEM List of input GSI DEM to be imported.
OUTSIDE_BOUNDARY Select this button, the system will set the FOM of the data which has no
value to OUTSIDE_BOUNDARY.
LAKE_FILLED Select this button, the system will set the FOM of the data which has no
value to LAKE_FILLED.
Start Begin importing the GSI DEM files.
17.8.1 Execution – GSI DEM Import

Use the following steps to import GSI DEM files:
1. Load the GSI DEM CD to the CD ROM
2. Click Preparation > Import > Terrain > GSI on the main workstation window to start GSI
DEM Import.
3. Click File > Load Project… on the GSI DEM Import window. Pick the project you wish to
import the GSI DEM files and click OK.
4. Specify where to read the input DXF file. Clicking File > Open Input GSI DEM... on the
GSI DEM Import window, or right click in the Input GSI DEM window and click Add.
5. Choose the name of the GSI DEM files you wish to import. Click OK. Or you can right click
on the Input GSI DEM input list and select Add, then pick the name of the GSI DEM files
you wish to import.
6. To remove GSI DEM files, highlight all the GSI DEM files that you wished to remove, then
right click on the Input GSI DEM list, select Delete.
7. Select the FOM for the no value data.
8. Click Start to start import.
GSI DEM Import works only on Geographic projects only.

17.9 LIDAR Import

LIDAR Import imports LIDAR terrain data in LAS format and ASCII format into the
workstation's internal DTM format.
The LAS file format is a public file format used to store LIDAR data. The data is stored in a binary
file with .LAS file extension and contains elevation data and information specific to LIDAR data.
When importing a LIDAR data, it will be assumed that the coordinate system, projection, datum,
vertical reference, and units of the files you are importing match with the SOCET SET project.
To open the LIDAR Import window, click Preparation > Import > Terrain > LIDAR on the main
workstation window
LIDAR Import GUI HERE
The LADAR Import window’s selection are as follows:
File > Load Project Prompts you to select the project for the LIDAR files imported.
File > File Type Displays “LAS Binary” for the LAS Format file type and ASCII for
the ASCII format file type.
NOTE: When selecting ASCII format, the Specify ASCII File Format
window pops up. You can specify the ASCII format using this
window. Make sure to set the correct Column Order for your
specific file.
File > Open … Prompts you to select the LIDAR files to import.
File > Exit Exits the LIDAR Import window.
Options > Import Options … Displays and prompts you to select options that will be used during
import.
Help > Contents … Starts the on-line documentation.

SELECT TO
LIDAR Files List of input LIDAR files to be imported. You can view information on a
file by highlighting it, right clicking, and selecting View Info. You can add
Output Terrain File Select DTM to enable creating a DTM from the input LIDAR files.
If you enable creating a DTM, use DTM to select the name of the output
DTM. You can select TIN or Grid to select the output DTM format.
Selecting Grid will prompt you to select the post spacing and spacing units
of the output Grid DTM.
The post spacing of the DTM defaults to the average spacing of the LIDAR
data from the LIDAR file(s).
Output Terrain Image Select Intensity Ortho to enable creating an orthophoto image from the
LIDAR intensities values. The format of orthophoto image is GeoTIFF.
NOTE: Not all LIDAR files will contain intensity data. ASCII format
does not output terrain image.
If you enable creating an orthophoto image you can select Intensity Ortho
to select the name of the output orthophoto and image file. You can set the
GSD of the output orthophoto image.
The GSD defaults to the average spacing of the LIDAR data from the
LIDAR file(s).
Select Location to select the location of the output image. The locations
are found in internal_dbs/DEVICE/location.list.
17.9.1 Import Options

The import options are applied to the LIDAR data during import and are used to create a DTM.
To open the Import Options window select Options > Import Options … from the LIDAR Import
window.
Import Options GUI

The Import Options window’s selections are as follows:
SELECT TO
Form Terrain from Return Select the laser return number to import from the LIDAR data for the
output DTM and/or output orthophoto image. The laser return number
values are 1, 2, 3, 4, 5, or Last.
Eliminate Trees/Buildings/ Select to enable eliminating trees, buildings, or any object with height
Other greater than the minimum height.
If enabled you can enter the minimum height of the objects you want to
eliminate, and the maximum slope of the terrain in degrees.
BLANK SPACE
The minimum height defaults to 10 meters or 30 feet. The units match the
project’s vertical reference units.
BLANK SPACE
The maximum terrain slope defaults to 10 degrees.
Thin TIN Points Select to enable thinning the LIDAR data during import. Thinning TIN
points option is only used if the output DTM format is TIN. If enabled
enter the DTM accuracy.
BLANK SPACE
The DTM accuracy defaults to the estimated accuracy in project vertical
units of the LIDAR data from the LIDAR file(s).
Reset to Default Resets the import option values to their default values based on the current
LIDAR file(s) selected for import.
OK Updates the import options to the values displayed and closes the Import
Options windows.
Cancel Closes the Import Options window. Cancel modifying the options for
import.
17.9.2 Execution - Import LIDAR

Use the following set of steps to import LIDAR data:
1. Start LIDAR Import by clicking Preparation > Import > Terrain > LIDAR on the main
workstation window.
2. Click File > Open … on the LIDAR Import window. You must then make your selection
in the pop-up File Selection. Click Open.
Default values for importing the LIDAR files are updated when you add
or remove LIDAR files. It is best to select the LIDAR files before
modifying values used to import the LIDAR data.
3. [Optional] Highlight the LIDAR file then right click and select View Info ... to view
information about the LIDAR file.
4. [Optional] Click Options > Import Options … to view or modify the options.
These options are updated if you add or remove LIDAR file(s)

if the import option has not been modified.
5. Click OK to update the import options and close the Import Options window.
6. Select output data to create from the LIDAR file(s) by doing the following:

a. Click DTM “checked” to create a DTM terrain file from the LIDAR data.
b. Click the DTM's … button. You must then type the name of the output DTM in the
pop-up File Selection window.
c. Click Save.
d. [Optional] Select Grid or TIN as the output DTM format. For Grid you can modify the
post spacing and/or the post spacing units of the output DTM in the pop-up Set Post
Spacing window.
AND/OR
a. Click Intensity Ortho “checked” to create an orthophoto image in GeoTIFF format
from the LIDAR data's intensity values.
The LIDAR file(s) might not contain intensity values.
b. Click Intensity Ortho's … button. You must then type the name of the output
orthophoto image in the pop-up File Selection window.
c. Click Save.
d. Click Location's … button in order to select the image location of the output
orthophoto image from the popup File Location window
e. Click OK.
f. [Optional] Type the value of the GSD of the output orthophoto image into the GSD
field.
7. Click Start to begin importing the LIDAR data.
17.9.3 Batch Processing - LIDAR Import

COMMAND LINE:
EXECUTABLE NAME NAME OF SETTING
KEYWORD DESCRIPTION
conversion_type import_lidar
project_file The project file name (with full path prefix).
input_files The input LIDAR file name(s) (with full path prefix).
input_file_type [Optional] The file type of the LIDAR data. Constant set to LAS for the
LAS Format. Defaults to LAS if this keyword is not given.
output_dtm [Optional] Flag (YES or NO) to indicate whether or not to create a DTM
from the LIDAR data. Defaults to YES if this keyword is not given.
output_dtm_file [Optional] The output DTM name (with full path prefix). This keyword is
required if output_dtm flag is set to YES.

KEYWORD DESCRIPTION
output_intensity_ortho [Optional] Flag (YES or NO) to indicate whether or not to create an

orthophoto image from the LIDAR data's intensity values. Defaults to NO
if this keyword is not given. This keyword is required with value YES if
output_dtm flag is set to NO.
output_intensity_image_file [Optional] The file name (full path name prefix) of image's support file.
This keyword is required if output_intensity_ortho flag is set to YES.
output_intensity_image_ [Optional] The full path of output orthophoto image location or image
location location found in internal_dbs_DEVICE/location.list.
This keyword is required if output_intensity_ortho flag is set to YES.
output_dtm_format [Optional] The output DTM format (GRID or TIN) to indicate DTM Grid
or DTM TIN. Defaults to TIN if this keyword is not given.
output_dtm_x_spacing [Optional] The floating point value of the x post spacing of the output
DTM. Defaults to the average x spacing of the LIDAR data if this keyword
is not given.
output_dtm_y_spacing [Optional] The floating point value of the y post spacing of the output
DTM. Defaults to the average y spacing of the LIDAR data if this keyword
is not given.
output_intensity_ortho_gsd [Optional] The floating point value of the GSD of the output orthophoto
image. Defaults to the average spacing of the LIDAR data if this keyword
is not given.
terrain_return_number [Optional] The return number (1, 2, 3, 4, 5, or LAST) of the LIDAR data
used to create the output DTM and/or output orthophoto. Defaults to LAST
if this keyword is not given.
thin_tin_points [Optional] Flag (YES or NO) to indicate whether or not to thin the TIN
points for the output DTM. Defaults to YES if this keyword is not given.
Thinning TIN points is only applied if TIN is the output DTM format.
thin_tin_points_dtm_ [Optional] The floating point value of the DTM accuracy parameter for
accuracy thin TIN points. Defaults the estimated accuracy of the LIDAR data in
project units if this keyword is not given.
remove_buildings_trees [Optional] Flag (YES or NO) to indicate whether or not to remove

building, trees, and other objects from the output DTM. Defaults to NO if
this keyword is not given.
remove_buildings_trees_ [Optional] The floating point value of the minimum height parameter for
minimum_height remove buildings, trees, and any object from the output DTM. Defaults to
10 meters or 30 feet if this keyword is not given. The units match the units
of the project’s vertical reference units.
remove_buildings_trees_ [Optional] The floating point value of the maximum slope of the terrain in
maximum_slope degrees for remove buildings, trees, and any object from the output DTM.
Defaults to 10 degrees if this keyword is not given.

17.10 GeoTIFF Import

GeoTIFF Import imports terrain data into the workstation’s internal DTM format. To open this
window, click Preparation > Import > Terrain > GeoTIFF on the main workstation window.
The sample format for the elevation data must be 32-bit float or 16-bit integer, and the orientation
of the GeoTIFF must be top left or bottom left.
On import, the Figure of Merit (FOM) for Null elevation posts is set to OUTSIDE_BOUNDARY.
Null elevation values are recognized as -32767 or less. ITE can be used to modify FOM values
as needed after import. Make sure the coordinate system in the GeoTIFF header matches with the
project coordinate system; otherwise the system will bail out.
SOCET SET’s GeoTIFF implementation does not distinguish between MSL and ellipsoid
information. You must be aware of the origin of the terrain when importing and exporting. For
example, if you receive a GeoTIFF file you know contains MSL elevations, you must import it
into an MSL SOCET SET project. As far as export to another system, you must set the other
system to match the MSL/ellipsoid setting of SOCET SET.
.
No other sample formats or orientations are supported. See the GeoTIFF Import section of the
Image import chapter for information on supported GeoTIFF tags.
The GeoTIFF Import window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project to import the GeoTIFF into
File > Exit Exits the GeoTIFF Import window.

SELECT TO
Input GeoTIFF File Prompts you to pick a terrain GeoTIFF file to import.
return.
Precision Input The precision input format that is stored in the GeoTIFF format. Possible
choices are None, 8-bit, and 32-bit float.
Precision Format The format the precision data is scaled under. This option is only available
for 8-bit precision input and can be inverse or non-inverse.
Precision Scaling Factor The scaling factor that the precision data uses. This factor is only
available for 8-bit precision input and must be known before importing the
precision data.
17.10.1 Execution - GeoTIFF Import

Use the following set of steps to import a GeoTIFF terrain file:
1. Click Preparation > Import > Terrain > GeoTIFF on the main workstation window to start
GeoTIFF Import.
2. [Stand Alone Only] Click File > Load Project on the GeoTIFF import window. Pick the
project you wish to import the GeoTIFF into and click Open.
3. Click (ellipse tool button) next to Input GeoTIFF file on the GeoTIFF Import window.
Pick the name of the GeoTIFF file you wish to import. Click Open.
5. Click Start to import the NED.
17.10.2 Batch Processing - Import GeoTIFF Terrain

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type import_geotiff_terrain
output_file File name (with full path prefix) of output DTH file.
input_file File name (with full path prefix) of input GeoTIFF file.

KEYWORD DESCRIPTION
precision_format (Optional) In batch mode, precision data can be imported from the second
image of a conforming GeoTIFF terrain file (if precision data does not
exist in the second image, precision is set to maximum values). The
precision_format keyword sets how the precision data is imported.
Possible values are “none”, “float”, “inverse”, and “non-inverse”.
Setting this to “none” will import no precision data and set the precision to
the maximum value.
Setting this to “float” will import the precision data as 32-bit float data
with a scaling factor of 1.0.
Setting this to “inverse” will import the precision data as 8-bit unsigned
characters with an inverse scaling factor. Setting this to “non-inverse” will
import the precision data as 8-bit unsigned characters with a non-inverse
scaling factor.
The default (when this keyword is omitted) is “none” - where precision
data format is not imported.
precision_scaling (Required when precision format has “inverse” or “non-inverse” specified)

_factor The precision_format value determines how the precision_scaling_factor
value is applied during import. For “inverse”, the precision scaling factor
is multiplied by the inverse of each individual precision value. For “non-
inverse”, the precision scaling factor is multiplied by each individual
precision value.
17.11 NITF Import

NITF Import imports terrain data into the workstation's internal DTM format. To open this
window, click Preparation > Import > Terrain > NITF on the main workstation window. The
orientation of the terrain NITF file must be top left and:
• ABPP=NBPP=32
• PVTYPE =R
• NPPBH=NPPBV=1024
• IC=NM (uncompressed and masked)
• ICAT=DTEM

File > Load Project Prompts you to pick the name of the project toimport the NITF into (only if
started stand-alone).
File > Exits Exists the NITF Import window.
SELECT TO
Input NITF file Prompts you to pick a terrain NITF file to import.
Output DTM Type in the name of the output DTM. Terminate you entry by pressing
[Enter] key on the keyboard,
Precision Input The precision input format that is stored in the NITF format. Possible
Precision Scaling Factor The scaling factor that the precision data uses. This factor is only
available for 8-bit precision input and must be known before importing the
precision data.
17.11.1 Execution -- NITF Import

Use the following set of steps to import a NITF terrain file:

1. Click Preparation > Import > Terraian > NITF on the main worktation window to start
NITF import.
2. (Stamd Alone Only) Click File > Load Project on the NITF Import window. Pick the
project you wish to import the NITF into and click Open.
3. Click Ellipse tool button next to Input NITF file on the NITF Import window. Pick the name
of the NITF file you wish to import. Click Open.
4. Click Start to imort the NITF terrain file.
17.11.2 Batch Processing -- Import NITF Terrain

COMMAND LINE
% START_SOCET -single data_convert -bath -s setting_file
KEYWORD DESCRIPTION
conversion_type import_nitf_terrain
output_file File name (with full path prefix) of output DTH file.
input_file File name (with full path prefix) of the input NITF file.
precision_format (Optional) In batch mode, precision data can be imported from the second
image of a conforming NITF terrain file (if precision data does not exist in
the second image, precision is set to the maximum value). The
precision_format keyword sets how the precision data is interpreted.
Setting this to “none” will not import any precision data and set the
precision data to the maximum value.
Setting this to “float” will import the precision data as 32-bit float data
with a scaling factor of 1.0.
Setting this to “inverse” will import the precision data as 8-bit unsigned
import the precision data as 8-bit unsigned characters with a non-inverse
scaling factor.
The default (when this keyword is omitted) is “float” – where the format is
floating point with identity scaling factor (i.e., scaling factor is 1.0).
precision_scaling (Required when precision format has “inverse” or “non-inverse” specified)

_factor The precision_format value determines how the precision_scaling_factor
value is applied during import. For “inverse”, the precision scaling factor
is multiplied by the inverse of each individual precision value. For “non-
inverse”, the precision scaling factor is multiplied by each individual
precision value.

17.12 BIL Terrain Import

BIL Terrain Import imports terrain data into the workstation's internal DTM format. BIL stands
for "band interleaved by line", and is a simple binary dump of the elevation data. To open this
window, click Preparation > Import > Terrain > BIL on the main workstation window. Only
Intermap's BIL format is supported at this time. Intermap typically delivers a set of 14 files:
n37w121f7dsm.bil n37w121f7dtm.html
n37w121f7dsm.hdr n37w121f7dtm.txt
n37w121f7dsm.html n37w121f7dtm.xml
n37w121f7dsm.txt n37w121f7ori.html
n37w121f7dsm.xml n37w121f7ori.tif
n37w121f7dtm.bil n37w121f7ori.txt
n37w121f7dtm.hdr n37w121f7ori.xml
Files with "dsm" or "dtm" contain terrain data and can be imported with this module. Files with
"ori" are the orthophoto image and can be imported with Image Import / Reformat. BIL Terrain
import requires the xml metadata file be present for each bil file you import.
The BIL Terrain Import window’s selection are as follows:
File > Load Project Prompts you to pick the name of the project to import the BIL into (only if
started stand-alone).
File > Exit Exits the BIL Terrain Import window.

SELECT TO
Input BIL File Prompts you to pick a BIL terrain file to import.
return.
17.12.1 Execution -- BIL Import

Use the following steps to import a BIL terrain file.
1. Click Preparation > Import > Terrain > BIL on the main workstation window to start BIL
Terrain Import.
2. [Stand Alone Only] Click File > Load Project on the BIL Terrain Import window. Pick the
project you wish to import the BIL into and click Open.
3. Click (ellipse tool button) next to Input BIL file. Pick the name of the BIL file you wish to
import. Click Open.
5. Click Start
17.12.2 Batch Processing --- BIL Terrain Import

COMMAND LINE:
% start_socet -single data_convert -bath -s setting_file
KEYWORD DESCRIPTION
conversion_type Import_bil_terrain
output_file File name (with full path prefix) of output DTH file
input_file File name (with full path prefix) of of input BIL file

17.13 ASCII DTM Export

ASCII DTM Export exports terrain data in the workstation’s internal DTM format into ASCII
format.
SOCET SET DTM

DTM FORMAT DEFINITION
ASCII DTM
EXPORT
ASCII DTM
OUTPUT DATA FILE
The ASCII DTM Export window’s selection are as follows:
File > Load Project Prompts you to pick the name of the project which contains the DTM to
export (only if started stand-alone).
File > Output File Format Prompts you to pick the name of a DTM format definition file, which
contains the definition of the format of the output ASCII DTM.
File > Save File Format Saves changes to a DTM format definition file that you made with the
Create Output Format option.
File > Input DTM Prompts you to pick a DTM to export.
File > Exit Exits the ASCII DTM Export window.
Options > Edit Output Displays a window which prompts you to define the format of the output
Format DTM.
SELECT TO
Project Identify the name of the project from which the DTM will be exported. By
default, this is the name of the project that is currently loaded on the
workstation.
Input DTM Name the input DTM you selected.
Output File Format Name the output DTM format definition file you selected.
Output ASCII DTM Name the output DTM, followed by a carriage return.

SELECT TO
Output Coordinate Format For geographic projects, select if you want the coordinate output to be
decimal degrees or radians. For all other project types, decimal degrees is
the default.
Thinned Points Output Select if you want points in the DTM marked.
If set to On (the default), all points in the DTM that were marked as
thinned with the ITE Area Thinning tool will be output.
BLANK SPACE
If set to Off, all thinned points are excluded from the output file; in
this way you can reduce the volume of data you will output.
Start Start to begin exporting.
17.13.1 Executions - DTM Export

17.13.1.1 Execution - Defining an Output Format
Use the following set of steps to edit or create an output file format definition:
1. Start up ASCII DTM Export by clicking Output > Export > Terrain > ASCII DTM on the
2. Click the tool button next to Output File Format on the ASCII DTM Export window. Pick
the name of an existing format definition. Click Save. If you want to create a new file, you
will specify the new file name.
3. Click Options > Edit Output Format on the ASCII DTM Export window. The dialog
window above appears.
4. For each field you want to export to the output file, you must specify what type of data that
field will contain.
5. For example, to indicate that the fourth field contains a point code, first click the “Code”
item in the Format Selection list. This highlights the word “Code.” Then click “4:” line in
the Fields list. Note that the format word in the Fields list next to the “4:” changes to the
word “Code.”
6. Repeat this procedure for each of the fields you want to export to the ASCII DTM.
7. SOCET SET DTMs contain the following information: ID, X, Y, Z, and a point code. For
GRID DTM, the point codes in a SOCET SET DTM contain the terrain figure-of-merit
(FOM) value. For TIN DTM, the point codes are:
MASS_POINT_CODE 0

START_BREAKLINE_CODE 1
CONTINUE_BREAKLINE_CODE 2
Terrain posts with a figure of merit (FOM) of

“OUTSIDE_BOUNDARY” are not exported.
8. When you are finished, click OK to accept the changes to the format definition. If you wish
to abort your changes, click Cancel.
9. Now, enter the name of the new output format definition file in the Output File Format field
on the ASCII DTM Export window. To write the new file, click File > Save File Format
on the ASCII DTM Export window.
17.13.1.2 Execution - Exporting an ASCII DTM

Use the following set of steps to export a DTM:
1. Start up ASCII DTM Export by clicking Output > Export > Terrain> ASCII DTM on the
2. [Optional] Click File > Load Project on the ASCII DTM Export window. Pick the project
that contains the DTM you wish to export. Click OK.
3. Click the tool button next to Output File Format on the ASCII DTM Export window. Pick
the name of a format file which describes the format that you want your output ASCII DTM
to have and click Save.
4. Click the tool button next to Input DTM on the ASCII DTM Export window. Pick the name
of the DTM you wish to export. Click OK.
5. Specify where to write the output ASCII DTM to by typing the file name in the Output
ASCII DTM field on the ASCII DTM Export window, followed by a carriage return.
6. Click Start to export the DTM.
17.13.2 Batch Processing - Export ASCII DTM

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type export_asc_dtm
input_dtm_file File name (with full path prefix) of input DTM.
output_asc_file File name (with full path prefix) of output ASCII file.

KEYWORD DESCRIPTION
thinned Character specifying if the points are to be thinned. Value may be 0 or 1.

(0—output thinned points; 1—do not output thinned points)
field_order Defines the columns of the input file. Five digit number with no spaces
between digits. Digits are: 1=X;2=Y; 3=Z; 4=code; 5=ignore. Example:
12354. See “Terrain Import and Export” on page 17-1 for more details.
output_units Units into which to export the DTM. Units can be radians
(UNIT_RADIANS) or decimal degrees (UNIT_DEGREES).
17.14 NED GridFloat Export

NED GridFloat Export exports terrain data from the workstation’s internal DTM format into the
National Elevation Dataset format.
To open this window, click Output> File Export> Terrain > NED GridFloat on the main
workstation window. SOCET SET will export files in USGS NED GridFloat format. (No other
USGS formats are currently supported.)
The NED GridFloat Export window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project to export the DTM from (only
if started stand-alone).
File > Exit Exits the NEDGridFloat Export window.
SELECT TO
Input DTM Prompts you to pick a DTM to export.
Output NED (FLT) File Type in the name of the output NEDGridFloat file. Terminate your entry
with a carriage return.
Resolution The resolution of the output file. 1/3, 1, or 2 arc-seconds.

SELECT TO
Horizontal Datum Select either NAD83 or NAD27 for the datum.
Start Begin exporting.
17.14.1 Execution - NED GridFloat Export

Use the following set of steps to import a NED file:
1. Click Output > File Export> Terrain > NED GridFloat on the main workstation window
to start NED Export.
2. [Stand Alone Only] Click File > Load Project on the NED GridFloat Import window. Pick
the project you wish to export the DTM from and click Open.
3. Click the toolbar button next to Input DTM on the NED GridFloat Import window. Pick
the name of the DTM you wish to export. Click Open.
4. Type the name of the output NEDGridFloat file in the Output NED (FLT) File field,
followed by a carriage return.
5. Click Start to export the NED GridFloat.
17.14.2 Batch Processing - Export NED GridFloat

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type export_gridfloat
input_dtm_file File name (with full path prefix) of input DTH file.
output_flt_file File name (with full path prefix) of output FLT file.
output_hdr_file File name (with full path prefix) of output HDR file.
output_prj_file File name (with full path prefix) of output PRJ file.
spacing Output spacing. Possible values for this field are 1/3_arc_second,
1_arc_second, and 2_arc_second. The default is 1_arc_second
horizontal_datum Output datum. Possible values are NAD27, or NAD83. The default is
NAD83.

17.15 ASCII ARC Grid Export

ASCII ARC Grid Export exports terrain data in the workstation’s internal DTM format into
ASCII format of ARC Grid.
SOCET SET
DTM
ARC GRID
EXPORT
ARC GRID
OUTPUT DATA FILE
The ASCII ARC Grid Export window’s selections are as follows:
File > Exit Exits the ASCII DTM Export window.
SELECT TO
Input DTM Name the input DTM you selected.
Output ASCII ARC Grid Name the output ASCII ARC Grid file, followed by a carriage return.
File
Use the DTM’s Identify either X or Y Spacing.

If set to Y_SPACING (the default), then the ASCII ARC Grid uses the
spacing in the Y direction of the DTM as the distance between cell values
when exporting the elevation data.
BLANK SPACE
If set to X_SPACING, then the spacing in the X direction.
Output Lower-Left/Cellsize (Geographic projects only) Allow you to select the coordinate format of
Format the Lower-Left coordinate and Cell size in the output ARC Grid file. You
may select Decimal Degrees or Radians.
17.15.1 Execution - Exporting an ARC Grid

Use the following set of steps to import a DTM:

1. Click Output > File Export > Terrain > ARC Grid on the main workstation window to start
ARC Grid Export.
2. Click File > Load Project on the ASCII ARC Grid Export window. Pick the project that
contains the DTM you wish to export. Click OK.
3. Click the tool button next to Input DTM on the ASCII ARC Grid Export window. Pick the
name of the DTM you wish to export. Click OK.
4. Specify where to write the output ASCII ARC Grid to by typing the file name in the Output
ASCII ARC Grid File field on the ASCII ARC Grid Export window, followed by a carriage
return.
5. Click Start to export the DTM.
17.15.2 Batch Processing - Export ASCII ARC Grid

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type export_asc_arc_grid
output_asc_file File name (with full path prefix) of output ASCII file.
spacing_to_use Character specifying if the Y spacing or the X spacing is to be used. Value

may be 0 or 1.
(0—Use Y Spacing; 1—Use X Spacing)
geo_coord_format (Geographic projects only) Character string specifying the coordinate

format of the Lower-Left Corner and Cell size in the output ARC Grid file.
May be one of the following: radians or degrees.
17.16 DEM Export

SOCET SET will export DTMs in the USGS DEM 7.5 minute and 1 degree formats. (No other
USGS formats are currently supported.) Your input DTM must have the following characteristics:
• The project in which the DTM resides must be a UTM project in units of meters.
• The input DTM post spacing must be 30 meters.
• The vertical reference of the project must be set to Mean Sea Level, not ellipsoid.
The DEM Export operation may use an optional header file. A sample DEM header file can be
found at <install_path>/internal_dbs/MISC/sample.demh. The header

specifies several miscellaneous fields in the DEM records “A” and “C” and desired corner
coordinates for the DEM. For a full description, refer to the USGS DEM specification. Make a
copy of this file into the project directory and edit the desired values before beginning the export
operation. If no header file is selected, these fields are filled with blank or default values and the
entire DTM is exported.
The DEM 7.5 minute format is specified to cover one 7.5 minute geographic quadrangle. The
corner coordinates in the header file would normally be set to match an exact multiple of 7.5
minutes for southwest and northeast coordinates, although any legitimate value is accepted. DEM
Export “masks” the DTM with this quadrangle and places the valid DTM posts into the output.
DEM Export will output grid-format DTMs but not triangular-format DTMs. If you want to
export a triangular DTM to DEM, you must first convert the triangular DTM to grid format with
Merge. See “DTM/Feature Merge,” Chapter 44 for details.
The NGVD 29 (National Geodetic Vertical Datum) is the vertical reference used for measuring
elevations inside the continental US. The MSL (Local Mean Sea Level) is the vertical reference
used for measuring elevations outside the continental US, such as Hawaii and Puerto Rico. The
DEM format uses integers to store elevation values.
To open this window, click Output > File Export > Terrain > DEM on the main workstation
window.
The DEM Export window’s selections are as follows:
File > Exit Exits the DEM Export window.

SELECT TO
Input DTM Name and identify the path of the input DTM.
NOTE: Only grid format DTM is supported.
DEM Header (Optional) Name and identify the path of the DEM header file.
Output DEM File Name the output DEM file.
DEM File Type Specify the output DEM extent. (7.5 Minute, 1 Degree)
Vertical Reference Specified the vertical reference of the DEM export. (NGVD 29, MSL)
17.16.1 Execution - DEM Export

Use the following set of steps to export a DEM file:
1. Click Output > File Export > Terrain > DEM on the main workstation window to start
DEM Export.
Be sure to check the accuracies and the quality/validity of the

DTM (using Interactive Terrain Edit and/or Quality Statistics)
before exporting to DEM.
2. Copy the sample DEM header file from <install_path>/internal_dbs/MISC/

sample.demh into your project. Edit the copy in the project so it describes the DEM you
are exporting.
3. [Optional] Click File > Load Project on the DEM Export window. Pick the project you
wish to export the DTM from and click Open.
4. Specify the output DEM by entering the file name in the Output DEM File field.
5. Click the tool button next to Input DTM on the DEM Export window. Pick the DTM you
wish to export. Click Open.
6. Click the tool button next to DEM Header on the DEM Export window. Pick the DEM
header file to use. Click Save.
7. Click Start to export the DEM.
The DTM CE/LE accuracies will transfer over to both the

Absolute and Relative RMS Errors (X, Y, Z) of the output DEM.
17.16.2 Batch Processing - Export DEM

COMMAND LINE:

KEYWORD DESCRIPTION
conversion_type export_dem
input_dtm_file file name (with full path prefix) of input DTH file.
output_dem_file File name (with full path prefix) of output DEM file.
dem_type dem_7_5_minute, dem_30_minute, dem_1_degree,

dem_15_minute_alaska, dem_7_5_minute_alaska
header_file dem header file (with full path) [optional].
17.17 DTED Export

DTED Export provides the ability to export a SOCET SET DTM to DTED format that meets
MIL-PRF-89020. DTED Export provides two output formats 1) Disk or 2)Magnetic media. The
disk output will either write a single DTED Level 0, 1, or 2 file. If the “Package” checkbox is
checked, then a DTED Level 0, 1, or 2 file is written to the disk in package format in the
appropriate DTED subdirectory as directed by MIL-PRF-89020. In addition the DTED Export
provides for the output of partial DTED 0, 1, or 2 cells which meet the standard DTED cell sizing
requirements. As an example a partial DTED cell (with incomplete coverage) can be output in a
1 degree by 1 degree format. Regions with no DTED are filled with VOID Posts. Per MIL-PRF-
89020 a void post is set to -32767; however you may change this value using the Socet Set
Configuration editor and reset DTED_VOID to some other value. Also upgraded in DTED Export
was the ability to efficiently enter sub-region (metadata) then draw and display the subregion
boundaries on the viewport. Operators should note that not all of the subregion rules are used to
validate subregions. The rules which are used in subregion validation display in a separate
window when Draw All is clicked and the Subregion validation process fails.
SOCET SET DTED

DTM EXPORT
DTED DATA
DTED Package
(Flat File System)
DTED Export will output grid-format DTMs but not triangular-format DTMs. If you want to
export a triangular DTM to DTED, you must first convert the triangular DTM to grid format with
Merge. See “DTM/Feature Merge,” Chapter 44 for details.
DTED Export only works in projects with a geographic

coordinate system.

DTED Level 0 DTED Level 1 DTED Level 2
DTED_root: DTED_root: DTED_root:

text Gazetter text
Read.me <country>.gaz Read.me
Onc.dir <country>.hsh Onc.dir
dted Gazette.dir dted
Long_Dir Gazette.key Long_Dir
-XXX.avg text - xxx.dt2
- xxx.min Read.me Dmed
Onc.dir
- xxx.max
dted
- xxx.dt0
Long_Dir
Dmed
- xxx.dt1
Dmed
DTED CDROM product composition and generated files.
Bold items are output when “Package” is enabled.
The DTED Export window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project from which the DTED will be
exported (only if started stand-alone).

File > Exit Exits DTED Export.
SELECT TO
Input DTM Type the name of the input DTM, followed by a carriage return.
NOTE: Only grid format DTM is supported.
Write DTED To Select Disk File or Tape
Output DTED File/Tape Name the tape device or file you selected to write the DTED to.
Device NOTE: Tape device not supported on Windows Platform.
ASCII Keyword Enter a text file with certain keywords such that certain records in the
header can be populated by the values provided by the keyword.
DTED Editor Pop up a GUI displaying the DTED Header information. Some fields are
available for the user to change inside the GUI to be written to the DTED
when exported.
Package If checked, will also create a folder in which the contents and format of the
folder is what you would find in a standard DTED CD package This would
include the dted file itself renamed to official specifications, the dmed file,
and the read.me file. The name of the folder is the name of the dted name
the user specified appended with the “_dted” in the project data folder.
• Package can only output one internal DTM file per DTED
package
Start Start exporting the DTED to the output destination.
17.17.1 Sample ASCII Keyword File

This Sample Keyword list is used both on the DTED Export window and in Batch Processing.
NOTE: # Characters are comments.
SECURITY_CODE T
UHL_ABS_VERT_ACC NA
#UHL_UNIQUE_REF
UHL_MULT_ACC 0
#UHL_RESERVE_24
#DSI_SECURITY_CONTROL
#DSI_SECURITY_HANDLING
#DSI_RESERVE_26
#DSI_UNIQUE_REF
#DSI_RESERVE_8

NOTE: # Characters are comments.
DSI_DATA_EDITION 01
DSI_MATCH_MERGE_VERSION A
DSI_MAINTENCE_DATE 0000
DSI_MERGE_DATE 0000
DSI_MAINTENANCE_DESCRIPTION 0000
DSI_PRODUCER_CODE USUSAETL
DSI_RESERVE_16 YOU
DSI_PRODUCT_SPEC_NUMBER 00
DSI_PRODUCT_SPEC_DATE 9505
DSI_VERT_DATUM MSL
DSI_COLLECTION_SYSTEM TIESDSPW
#DSI_RESERVE_22
DSI_ORIENTATION 0000000.0
DSI_PARTIAL_CELL 00
#DSI_NIMA_RES
#DSI_RESERVE_PRODUCING_NATION
#DSI_RESERVE_156
#ACC_RESERVE_4
#ACC_RESERVE_NIMA
#ACC_RESERVE_31
ACC_MULTIPLE_ACCURACY 00
ACC_ABSOLUTE_HORZ_ACCURACY_SUB NA
ACC_ABSOLUTE_VERT_ACCURACY_SUB NA

17.17.2 DTED Editor
The DTED Editor is divided into five tabs, User Header Label (UHL) shown, Data Set
Identification (DIS) Records, DSI-Reserved, Accuracy Description (ACC) Record, and ACC-
SubRegion. Each of these sections are divided as follows:

17.17.2.1 UHL Tab
SECTION HEADING DESCRIPTION
Header Info Label This would be by default UHL to indicate which part of the
tab you are on.
Security Security code for the DTED. Values can be T, S, C, U, R.
Unique Reference The unique number assigned to the DTED. This field is to be
Number defined by the producer but may be left blank as well.
Unique Reserved Unused portion of the header which has not been assigned to
Portion any particular specification. This has been saved for future
use.
Standard A fixed value by standard UHL specification.
Long/La Longitude of Origin The location of the lower left corner of the data set
Latitude of Origin The location of the lower left corner of the data set
Longitude Data The Data Intervals are measurements in tenths of seconds.

Intervals
Number of Longitude The Data Intervals are measurements in tenths of seconds.

Lines
Number of Latitude The count of lines for a full one-degree cell.

Lines
Accuracy Absolute Vertical Provides accuracy of assurance relative to mean sea level.
Accuracy
Multiple Accuracy This takes two values. 0-1 for single accuracy and 2-9 for
multiple.
17.17.2.2 DSI Tab
Header Info Label This would be by default DSI to indicate which part of the tab
you are on.
Match/Merge Version Values should be between A-Z for the version Id.
Security Security code for the DTED. Values can be T, S, C, U, R.
Security Control This if reserved for DOD use only.
Partial Cell Indicator Indicates coverage of the DTED cell. 00 is complete, 01-99 is
% of data coverage.
Vertical Datum MSL or E96 for the vertical datum
Product Amendment/ Values are in between 00-99. First number indicates the
Charge Number Product Specification Amendment Number. Second digit
indicates change number.
Data Edition Number 01-99 indicates the data edition number.
Maintenance Date To be filed by YYMM for year then month. Can be zero filled
until used.

Match/Merge Date To be filled by YYMM for year then month. Can be zero
filled until used.
Maintenance Can be 0000 or ANNN.

Description
Horizontal Datum The current version world geodetic system. (WGS84).
Compilation Date Enter most descriptive year/month.
Product Specification The date of Product specification. Format is in YYMM.

Date
Security Handling Other types of security description. Can be free text or blank
filled.
N G A Series N G A Series Designator for product level of the DTED. For

Designator example DTED0, DTED1, DTED2, etc.
Unique Reference For producing nations own use. Can be free text or zero
filled.
Producer Code Country free text. The 1st two characters indicate the country
codes used according to FIPS 10-4.
Product Specification Specification number for the product. This is an alpha

numeric field.
Digitizing Collection Free text.

System
Longitude/ Number of Longitude For Magnetic Tape, this is the actual count of the number of
Latitude Lines longitude points (columns containing data).
For CD-ROM, this is the count of the number of longitude
points in a full one-degree cell. The count is based on the
level of DTED and the latitude zone of the cell.
Number of Latitude For Magnetic Tape, this is the actual count of the number of
Lines latitude points (rows that contain data).
For CD-ROM, this is the count of the number of latitude
points in a full one-degree cell.
Longitude Intervals The Data Intervals are measurements in tenths of seconds.
Latitude Intervals The Data Intervals are measurements in tenths of seconds.
SW Longitude Longitude of SW corner of data, (use leading zero for values

less than 100). H is the hemisphere of the data.
NW Longitude Longitude of NW corner of data, (use leading zero for values

SE Longitude Longitude of SE corner of data, (use leading zero for values

NE Longitude Longitude of NE corner of data, (use leading zero for values

SW Latitude Latitude of SW corner of data, (use leading zero for values

NW Latitude Latitude of NW corner of data, (use leading zero for values


SE Latitude Latitude of SE corner of data, (use leading zero for values

NE Latitude Latitude of NE corner of data, (use leading zero for values

Longitude Origin Longitude of the origin.
Latitude Origin Latitude of the origin.
Orientation Angle Clockwise orientation angle of the data with respect to true
North. (Usually all zeros.)
Reserved Spaces N G A Reserved Reserved N G A use only.
Comments Your comments
Nation Reserved Reserved for producing nation use. Free text or blank filled.
Reserved Reserved for future use.

17.17.2.3 DSI-Reserved
Reserved Spaces Reserved Reserved for future use.
N G A Reserved Reserved N G A use only.
Source Type Code Number of coordinates in the accuracy sub region outline.
17.17.2.4 ACC Tab
Header Info Label This would be by default ACC to indicate which part of the
tab you are on
Multiple Accuracy Provides the number of accuracy subregions provided. This

Flag takes two values, 2 - 9 for multiple Accuracy.
Latitude-Leading Latitude leading zero for the coordinate pair description.

Zero
Longitude-Leading Longitude leading zero for the coordinate pair description.

Zero
Accuracies Absolute Horizontal Provides the absolute horizontal accuracy of product in

Accuracy meters.
Relative Horizontal Provides the point to point horizontal accuracy of the product
Accuracy in meters.
Absolute Vertical Provides the absolute vertical accuracy of the product in

Accuracy meters.
Relative Vertical Provides the point to point vertical accuracy of the product in
Accuracy meters.
Reserved Fields Reserved Reserved for future use.
N G A Reserved Reserved N G A use only.
Source Type Code Number of coordinates in the accuracy sub-region outline.
17.17.2.5 ACC-SubRegion
Accuracies Absolute Horizontal Provides the absolute horizontal accuracy of sub-region in

Accuracy Sub-Region meters.
Relative Horizontal Provides the point to point horizontal accuracy of the sub-
Accuracy Sub-Region region in meters.
Absolute Vertical Provides the absolute vertical accuracy of sub-region in

Relative Vertical Provides the point to point vertical accuracy of sub-region in


Coordinate Pairs There are 14 coordinate pairs each having a latitude and
longitude associated.
Buttons Previous Reverts to the previous sub-region
Next Advances to the next sub-region
Draw Draw the current sub-region the GUI is displaying.
Draw All Draws all nine sub-regions
17.17.3 Execution - DTED Export

Use the following set of steps to export a DTED file:
1. Click Output > Export > Terrain > DTED on the main workstation window to start DTED
Export.
Be sure to check the accuracies and the quality/validity of the

DTM (using Interactive Terrain Edit and/or Quality Statistics)
before exporting to DTED.
2. Click File > Load Project... on the DTED Export window. Pick the project you wish to
export the DTED from, then click OK.
3. Click the tool button next to Input DTM... on the DTED Export window. Choose the name
of the DTM you wish to export, then click OK.
We recommend that your input DTM be on a 1 or 3 second

boundary and has 1 or 3 second spacing.
4. (Optional) Click DTED Editor. This displays a new window with values that populate the
header record of the DTED file. If you wish, you may edit some of these fields with specific
user-defined values. Refer to Step 5 for an alternate method of editing the file metadata.
When finished click Done to save these changes.
Sub regions should be defined with orthogonal line segments.
a. To enable subregions, change Multiple Accuracy on the UHL tab from 0 to 1 and enter
the number of subregions 02-09 in the Multiple Accuracy Flag field.
b. Subregion number 1 must contain the SW coordinate of the DTED cell as its FIRST
coordinate/vertex
c. The first coordinate/vertex for ANY subregion must be the southern AND western
coordinate/vertex.
d. Subregions can be defined with as many as 14 coordinate/vertex pairs. Closure is
implied and may not lie outside the DTED cell limits.
e. Subregions which lie on the perimeter of a DTED cell must be entered in clockwise
order starting from the SW corner.
f. Interior subregions entered south to north and west to east. Southern takes precedence
over northern.
g. Use the Draw or Draw All buttons to ensure subregions are contiguous.
5. (Optional) Click the tool button next to ASCII Keyword, to import a list of pre defined
values into the DTED header from an ASCII keyword text file.

6. (UNIX Only) Click the Tape radio button on the DTED Export window. Pick a tape device
in the Select Device popup window, then click OK.
7. Click Start to export the DTED.
The DTM CE/LE accuracies will transfer over to both the Relative and Absolute Horizontal/
Vertical Accuracies of the output DTED.
17.17.4 Batch Processing - Export DTED

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type export_dted
output_filename File name (with full path prefix) of output DTED. This is used for
exporting to a file or CD_ROM.
hostname Hostname of computer device is mounted on. This is needed for exporting
to tape.
driver Name (with full path prefix) of tape device. This is needed if exporting to
tape.
keyword_file Create a text file with certain keywords such that certain records in the
header can be populated by the values provided by the keyword. See
“Sample ASCII Keyword File” on page 17-43.
17.18 SDTS Export

SOCET SET will export DTMs in the USGS SDTS format. The project in which the DTM resides
must be a UTM or geographic project.
The input DTM Spacing Units need to be in Feet or Meters.
SDTS Export will output grid format DTM but not triangular format DTM. If you want to export
a triangular DTM to SDTS, you must first convert the triangular DTM to grid format using
Extraction > Merge.
SDTS Export outputs 12 files. 11 files are ASCII files. One file, called the SDTS Cell Module,
which contains the elevation values, can be written in one of the following formats:
1. Binary Float (32 bit per post)

2. Binary Short (16 bit per post)

3. ASCII
It is up to you to choose in which format the Cell Module will be written.
In order to get maximum accuracy the user should use the Float format. The file is twice as big
in Float than in the Short format.
The SDTS Export window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project to export the SDTS into (only
if started stand alone).
File > Exit Exits the SDTS export window.
Home > Contents Starts the on-line documentation.
SELECT TO
Input DTM Name and identify the path of the input DTM.
NOTE: Only grid DTM is supported.
Output SDTS Dir Type the name of the output SDTS directory. Name can only be four
characters long. (All SDTS file names will start with these 4 characters as
prefix.) Terminate your entry with a carriage return.
Elevation Format Specify the output format: Float, Short, or ASCII.
Start Begin exporting

17.18.1 Execution - Export SDTS

Use the following set of steps to export a SDTS set of files:
1. Click Output > File Export > Terrain > SDTS on the main workstation window to start up
SDTS Export.
2. Click File > Load Project on the SDTS Export window. Select the project you wish to
export the SDTS from and click OK.
3. Click the tool button next to Input DTM on the SDTS Export window. Select the name of
the DTM you wish to Export and click OK.
4. Type the name of the output SDTS directory in the Output SDTS Dir field, followed by
pressing [ENTER]. (Dir name can only be four characters long).
5. Select the output format you wish the SDTS Cell module to be written (Float is the default).
6. Click Start to export the SDTS.
17.18.1.1 Batch Processing - Export SDTS

COMMAND LINE:
% start_socet – single data_convert –batch –s setting_file
KEYWORD DESCRIPTION
conversion_type export_sdts
output_sdts_dir Directory name (with full path prefix).
save_format Elevation data format: Float, Short, or ASCII.
See “SDTS” on page E-21 for an example.
17.19 DGN Data Format Conversions

SOCET SET provides translators converting digital terrain data and feature data into Intergraph
Microstation DGN format. DTM features and post data can be translated directly. Continuous
contours can be translated by converting them into features, and then translating the features.
During the translation of terrain data and features, several assumptions are made.
1. All features and seed files are three dimensional; thus it is assumed the seed files must also
be three-dimensional.
2. Ground points are converted from doubles to UOR longs by performing the following
procedure:

a. A ground point converted to SRG coordinates. SRG coordinates are a local coordinate
system which have a strong effect with geographic projects. In geographic projects the
coordinates are stored as radians, and the SRG coordinates are meters. For other types
of projects, the SRG coordinate transformation has no effect other than swapping the
X and Y coordinates.
b. From SRG coordinates, the groundpoints are multiplied by the conversion factor. The
conversion factor based on seed file sdmap3d.dgn has the value of 1000. This
represents the number of subunits per master unit of feet. If the SRG coordinates are
in meters and the seed file requires feet (as is the case with sdmap3d.dgn), the
coordinates are also multiplied by a meters_to_feet conversion factor.
c. Finally, the doubles are recast as longs, effectively truncating the converted
groundpoints.
3. You have to correctly set the seed file parameters for a given project. It is very likely that
a seed file for one project will not be correct for other projects. If you start getting “out of
range” error messages, it is likely that the seed file parameters are incorrect. In this case,
you should verify that the global origin and master units are properly specified. Consult
your MicroStation manual set for more information on the seed file.
17.19.1 DGN Post Export

DGN Post Export exports a SOCET SET DTM to the Intergraph MicroStation DGN format.
SOCET SET DGN TEMPLATE

DGN SEED FILE
DTM FILE
DGN POST
EXPORT
DGN FILE
The DGN Post Export window’s menu choices are as follows:
File > Load Project Prompts you to pick the name of the project from which the DTM will be
exported (only if started stand-alone).
File > Exit Exits the DGN Post Export window.
SELECT TO
Input DTM Name the DTM you selected to export.

SELECT TO
Output DGN File Specify the name and directory path of the output Intergraph DGN file.
You can edit this field to change the directory and/or file name.
DGN Seed File Name the seed file you selected.
DGN Template File Name the template file you selected.
Report File Specify the name and directory path of the output report file. You can edit
this field to change the directory and/or file name.
Start Start exporting the DTM into the Intergraph DGN format.
17.19.1.1 Seed File

Before you can export an Intergraph DGN file, you must set up a seed file in MicroStation. You
must carefully specify appropriate scale factors and global origins. If you attempt to export with
incorrect scale or global origin information, DGN Post Export will generate error messages
indicating that there is a problem.
17.19.1.2 Intergraph DGN Post Template File

The Intergraph DGN Template File is a five-line text file that contains the necessary information
to convert the SOCET SET DTM into an Intergraph MicroStation DGN file. Before you export,
you must create a template file in the project directory using a text editor. Give it the .dgn
extension.
The first line in the file indicates the file type and revision level. The next four lines contain the
level, color, weight, and style information.
The following example illustrates the contents of the Intergraph DGN post template file:
Template_File_Post a
level 3
color 2
weight 1
style 1
For definitions of the level, color, weight, and style values refer to the MicroStation User’s Guide
(Document DGA051410, Version 4).
17.19.2 Execution - DTM to DGN

Use the following set of steps to export a DTM in the Intergraph DGN format:
1. Click Output > File Export > Terrain > DGN Post on the main workstation window to start
DGN Post Export.
2. Click File > Load Project on the DGN Post Export window. Pick the project you wish to
export the DTM from and click OK.
3. Click the tool button next to Input DTM on the DGN Post Export window. Pick the name
of the DTM you wish to export. Click Open.

4. Click the tool button next to DGN Seed File on the DGN Post Export window. Pick the
name of the Intergraph DGN seed file you wish to export. Click Open.
5. Click the tool button next to DGN Template File on the DGN Post Export window. Pick the
name of the Intergraph DGN Template file you wish to export. Click Open.
6. Modify the name and/or output path in the Output DGN File field if you want the file to go
to a different directory and/or have a different name.
7. Click Start to export the DTM as an Intergraph DGN file.
17.19.2.1 Batch Processing - Export DGN Posts

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type export_dgn_post
input_dth_file File name (with full path prefix) of input DTH file.
output_dgn_file File name (with full path prefix) of output DGN file.
report_file File name (with full path prefix) of output report file.
seed_file File name (with full path prefix) of input seed file.
template_file File name (with full path prefix) of input template file.
17.20 GeoTIFF Export

GeoTIFF Export exports terrain data from the workstation’s internal DTM format. To open this
window, click Output > File Export > Terrain > GeoTIFF on the main workstation window. The
GeoTIFF tags of the output TIFF will be set according to the SOCET SET project coordinate
system. The orientation TIFF tag will be set to top left. If you would like to use a different tile
size, please set the environment variable TERRAIN_OUTPUT_TILE_SIZE to an appropriate
size.
If the project vertical reference is MSL, the system will use tag 5171 for VerticalCSGeoKey to
output to the TIFF file. If the project vertical reference is ELLIPSOID, the system will use tag#
5030 for VerticalCSGeoKey (WGS_84) to output the TIFF file.

The GeoTIFF Export window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project to export the GeoTIFF from
File > Exit Exits the GeoTIFF Export window.
SELECT TO
Input DTM File Prompt you to pick a terrain DTH file to export.
Output GeoTIFF File Type in the name of the output GeoTIFF. Terminate your entry with a
carriage return.
Elevation Format Select the sample format for the output elevation data. Possible options are
16-bit integer and 32-bit float.
Precision Output The precision input format that is stored in the GeoTIFF format. Possible
Precision Cutoff The number of standard deviations away from the average of the precision
data to scale the data. Use this to eliminate outlying precision data. Only
available with 8-bit precision.
Precision Autoscale Automatically scales the precision. Only available with 8-bit precision.

SELECT TO
Start Begin export.
17.20.1 Execution - GeoTIFF Export

Use the following set of steps to import a GeoTIFF terrain file:
1. Click Output > File Export > Terrain > GeoTIFF on the main workstation window to start
GeoTIFF Import.
2. [Stand Alone Only] Click File > Load Project on the GeoTIFF Export window. Pick the
project you wish to export the GeoTIFF from and click Open.
3. Click (ellipse tool button) next to Input DTM file on the GeoTIFF Export window. Pick
the name of the DTM file you wish to export. Click Open.
4. Type the name of the output GeoTIFF in the Output GeoTIFF field, followed by a carriage
return.
5. Click Start to export the GeoTIFF.

17.20.2 Batch Processing - Export GeoTIFF Terrain

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type export_geotiff_terrain
output_file File name (with full path prefix) of output GeoTIFF file.
input_file File name (with full path prefix) of input DTH file.
sample_format Sets how elevation data is stored in the GeoTIFF. Possible values are
“integer” and “float”. Setting this to “integer” will export the elevation
data as 16-bit signed integer. Setting this to “float” will export the
elevation data as 32-bit float (IEEEFP). The default is float.
precision_format (Optional) In batch mode, precision data is exported as the second image
of a GeoTIFF terrain file. The precision_format keyword sets how the
precision data is stored.
Setting this to “none” will not export any precision data.
Setting this to “float” will export the precision data as 32-bit float data.
Setting this to “inverse” will export the precision data as 8-bit unsigned
export the precision data as 8-bit unsigned characters with a non-inverse
scaling factor.
The default (when this keyword is omitted) precision data format is
“none”.
precision_cutoff (Optional) Identifies cutoff point for precision values, expressed as the
number of standard deviations from the mean. For inverse precision, all
precision values less than (i.e., better accuracy) or equal to the derived
cutoff point are converted to highest precision (255). For non-inverse
precision, all precision values greater than (i.e., worse accuracy) or equal
to the derived cutoff point are converted to lowest precision (255). The
default precision cutoff is 2.0 standard deviations. The value 0 results in no
cutoff being applied. The precision_auto_scale keyword value
must be “YES” for the cutoff to be applied.
NOTE: Proper use of precision cutoff can negate the effect of
outliers when exporting 8-bit precision data. Precision cutoff is
only enabled when precision format is specified and precision
auto-scaling is enabled. If the provided precision cutoff results in
a point beyond the minimum (inverse) or maximum (non-inverse)
precision, the cutoff point is set to the minimum (inverse) or
maximum (non-inverse).

KEYWORD DESCRIPTION
precision_auto_sc (Optional) Set to “YES” to determine and adjust scaling factor

ale automatically, based on precision_format, precision_cutoff
and precision data distribution. Set to “NO” to use existing DTM scaling
factor without adjustment. Default value is YES.
NOTE: The scaling factor can be read and modified using the API
DtmHeader functions precisionScaler() and setPrecisionScaler(),
respectively. Precision automatic scaling is only enabled when
precision format is specified and the value of keyword
precision_auto_scale is set to “YES”. If precision automatic
scaling is enabled, be sure to obtain the scaling factor value after
the GeoTIFF Terrain Export application is completed. For inverse
precision format, the precision scaling factor is calculated as (255
* cutoff). For non-inverse precision format, the precision scaling
factor is calculated as (cutoff / 255).
17.21 NITF Export

NITF Export exports terrain data from the workstation’s internal DTM format. To open this
window, click Output > File Export > Terrain > NITF on the main workstation window. The
coordinate of the output NITF file will be set according to the SOCET SET project coodinate
system. If you would like to use a different tile size, please set the environment variable
TERRAIN_OUTPUT_TILE_SIZE to an appropriate size. The orientation of the NITF file will be
top-left and:
• ABPP=NGPP=32
• PVTYPE =R
• NPPBH=NPPBV=1024
• IC=NM ) compressed and masked)
• ICAT=DTEM

File > Load Project Prompts you to pick the name of the project to export the NITF from (only
if started in stand-alone).
File > Exit Exit the NITF Import window.
File > Contents Starts the online documentation.
SELECT TO
Input DTM File Prompts you to pick a terrain DTM file to export
Output NITF Type in the name of the output NITF. Terimiate your entry with a clicking
the [Enter] key on the keyboard.
Precision Output The precision input format that is stored in the NITF format. Possible
Precision Cutoff The number of standard deviations away from the average of the precision
data to scale the data. Use this to eliminate outlying precision data. Only
available with 8-bit precision.
Precision Autoscale Automatically scales the precision. Only available with 8-bit precision.
Start Begin export.

17.21.1 Execution - GeoTIFF Export

Use the following set of steps to export DTM to a NITF file:
1. lick Output > File Export >Terrain > NITF on the main workstation window to start NITF
export
2. [Stand Alone Only] Click File > Load Project on the NITF Terrain export window. Pick
the project you wish to export the DTM and click Open.
3. Click ellipse tool button next to Input DTM file on the NITF Terrain Export window. Pick
the name of the DTM file you wish to export. Click Open.
4. Type the name of the output NITF in the Output NITF field, followed by a carriage return.
5. Click Start to export the DTM terrain file to NITF file.
17.21.2 Batch Processing - Export NITF Terrain

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type export_nitf_terrain
output_file File name (with full path prefix) of output NITF file.
input_file File name (with full path prefix) of the input DTH file.
precision_format (Optional) In batch mode, precision data is exported as the second image
of a NITF terrain file. The precision_format keyword sets how the
precision data is stored. Possible values are “none”, “float”, “inverse”, and
“non-inverse”.
Setting this to “none” will not export any precision data.
Setting this to “float” will export the precision data as 32-bit float data.
Setting this to “inverse” will export the precision data as 8-bit unsigned
export the precision data as 8-bit unsigned characters with a non-inverse
scaling factor.
The default (when this keyword is omitted) precision data format is
floating point with identity scaling factor (i.e., scaling factor is 1.0).

KEYWORD DESCRIPTION
precision_cutoff (Optional) Identified cutoff point for precision values, expressed as the
number of standard deviations from the mean. For inverse precision, all
precision values less than (i.e., better accuracy) or equal to the derived
cutoff point are converted to highest precision (255). For non-inverse
precision, all precision values greater than (i.e., worse accuracy) or equal
to the derived cutoff point are converted to lowest precision (255). The
default precision cutoff is 2.0 standard deviations. The value 0 results in no
cutoff being applied. The precision_auto_scale keyword value
must be “YES” for cutoff to be applied.
NOTE: Proper use of precision cutoff can negate the effect of
outliers when exporting 8-bit precision data. Precision cutoff is
only enabled when precision format is specified and precision
auto-scaling is enabled. If the provided precision cutoff results in
a point beyond the minimum (inverse) or maximum (non-inverse)
precision, the cutoff point is set to the minimum (inverse) or
maximum (non-inverse).
precision_auto_sc (Optional) Set to “YES” to determine and adjust scaling factor

ale automatically, based on precision_format, precision_cutoff
and precision data distribution. Set to “NO” to use existing DTM scaling
factor without adjustment. Default value is YES.
NOTE: The scaling factor can be read and modified using the API
DtmHeader functions precisionScaler() and setPrecisionScaler(),
respectively. Precision automatic scaling is only enabled when
precision format is specified and the value of keyword
precision_auto_scale is set to “YES”. If precision automatic
scaling is enabled, be sure to obtain the scaling factor value after
the NITF Terrain Export application is completed. For inverse
precision format, the precision scaling factor is calculated as (255
* cutoff). For non-inverse precision format, the precision scaling
factor is calculated as (cutoff / 255).

Chapter 18
Feature Import and Export

Feature Import and Export covers the conversion of several
feature data formats.
18.1 Overview
This chapter is primarily divided into two section, Imports and Exports. The individual feature
data formats are listed as follows:
IMPORTS EXPORTS
DXF Feature Import DXF Feature Export
ARC_GEN Import ARC_GEN Export
ASCII Feature Import ASCII Feature Export
MP ASCII Feature Export
Shapefile Import Shapefile Export
DGN Feature Export
18.2 DXF Feature Import

DXF (Drawing Interchange Format) is a standard AutoCAD ASCII file format used to port
feature data from one system to another. Only ASCII DXF files are supported. Feature and
Elements attributes are imported into the Feature Database. Further information on AutoCAD and
on the file formats used for the data interchange can be found in the on-line DXF Reference for
AutoCAD 2000. AutoCAD Release 2000 is currently supported by DXF Import.
DXF Import reads DXF data to the internal workstation feature database format. DXF Import
reads a DXF file from disk and converts all its features and writes them to a new feature file.
SOCET SET Page 18-1

Chapter 18 - Feature Import and Export
The DXF Feature Import window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project into which the DXF file will
be imported (only if started stand-alone).
File > Input DXF File Prompts you to pick a DXF file to import.
File > Exit Exits the DXF Feature Import window.
Project Name the project into which the DXF file will be imported. By default, this
is the name of the project that is currently loaded on the workstation.
Input DXF File Pick a DXF file to import.
Output Feature DB Type the name of the output feature file, followed by a carriage return.
Scale Factor Enter the factor by which the input features will be scaled before being
written to the output feature file.
• The default is 1.0 (no scaling).
• 0.0 to 1.0 will scale the features up.
• 1.0 and up will scale the features down.
Specification File Choose whether to use a specification file generated by the software or a
user-generated specification file.
Start Begin importing the DXF file.
Page 18-2 SOCET SET

If importing on a Windows system, make sure that the DXF file

is in DOS format and not UNIX format If not, then convert the
DXF file to DOS format. Do the same if on a UNIX system and
importing a DXF file in DOS format.
18.2.1 Execution - DXF Feature Import

Use the following set of steps to import a DXF file:
1. (Optional) Prepare an E x t r a c t i o n S p e c i f i c a t i o n file appropriate for the DXF file to be
imported. See “Feature Database and Extraction Specification,” Appendix C to create the
Extraction Specification. Make sure that the class names in your specification file match
the layer names (DXF Group Code 8) in your DXF file. If you do not wish to prepare an
Extraction Specification, either use “template.spc” during import and the DXF Import
function will attempt to create the appropriate classes in the specification file, or use the
“Generate New File” option on the GUI and the software will generate a specification file
tailored to your input.
DXF mesh data (3-D polygon mesh vertex and polyface mesh
vertex) do not get imported into the Feature DB.
2. Click Preparation > Import > Features > DXF on the main workstation window to start
DXF Feature Import.
3. Click File > Load Project on the DXF Feature Import window. Pick the project you wish
to import the DXF file into and click OK. The coordinate system and the units of the DXF
file should match that of the project.
4. Specify where to read the input DXF file from by clicking Input DXF File... on the DXF
Feature Import window. Pick the name of the DXF file you wish to import. Click OK.
5. Type the name of the output feature file in the Output Feature DB field, followed by a
carriage return.
6. Select whether you want a software-generated specification file or whether you want to use
your own specification file.
7. If the Output Feature DB does not exist, you will be prompted for an Extraction
Specification file. Pick the name of the Extraction Specification you wish to use and click
OK. If you do not have a specific Extraction Specification available, use “template.spc.”
If you receive warnings about proper classes not being available, you must add a class to the
Extraction Specification that corresponds to the DXF Layer Name (Group Code 8). The DXF
Layer Names should be identical to the class names in the Extraction Specification.
Consequently, the DXF Layer Names must comply with the class name conventions of
SOCET SET Feature DBs. If this is not so, you must re-export the DXF file from your third party
application with the compliant layer names, add the corresponding classes into the Extraction
Specification, and then re-import the DXF file into SOCET SET. SOCET SET classes each have
a single geometry whereas a DXF layer can contain entities with different geometries. If during
Import an entity is encountered that is a different geometry from previous entities in the same
layer, SOCET SET will give it a new class name consisting of the layer name with the appropriate
geometry appended.
Attributes from the .dxf file are imported into Socet Set feature/element attributes. Attribute
names are not case-sensitive, and attribute types must be compatible.
SOCET SET Page 18-3

Compatibility is as follows:
DXF ATTRIBUTE TYPE SOCET SET ATTRIBUTE TYPE
INT_TYPE Integer
ASCII_TYPE String
DOUBLE_TYPE Double
FLOAT_TYPE Float
ENUMER_TYPE Enum
Feature ID numbers are generated depending on the order of input.

Socet Set supports the geometry type POLYHEDRON and MULTILINE and DXF does not.
A user-generated specification file may have different attributes from the attributes in the input
file. If so, some of the attribute values will have default values that are specified in the user’s
specification file.
These, along with the layer differences mentioned above, are possible reasons why the imported
FDB may look slightly different from the original DXF data.
DXF exports of geographic projects will be in Scaled Relative

Geographic coordinates. This system allows latitude and
longitude to be output as values that are in approximate
project units from an arbitrary coordinate origin selected at the
time the project is created.
The formula for SRG coordinates is:
SRG_Y = (lat - GP_ORIGIN_Y) * GP_SCALE_Y
SRG_X = (long - GP_ORIGIN_X) * GP_SCALE_X
Where “lat” and “lon” are the latitude and longitude coordinates of the input point, SRG_Y and
SRG_X will be the values found in the exported file, and the other values will be found in the
project file (.prj).
18.3 Batch Processing - DXF Features Import

COMMAND LINE:
Page 18-4 SOCET SET

KEYWORD DESCRIPTION
conversion_type import_dxf_feature
input_dxf_file File name (with full path prefix) of input DXF file.
output_fdb_file File name (with full path prefix) of output feature database.
spec_file [option] File name (with full path prefix) of default feature database
specification file. This field is required only when the output feature
database does not already exist, and you want to use a specific spec file.
scale Scale factor to be applied to features. 0.0 to 1.0 scales the features up. 1.0
and up scales the features down. (Although a value of 0.0 is not valid.)
18.4 ARC_GEN Import

ARC_GEN is a simple ASCII vector format which you can use to import features into the
workstation.
ARC_GEN Import reads features from the input ARC_GEN file and appends them to the output
feature database; each imported feature is assigned to a feature class that you specify.
You can import as many AMS files as you desired, but each file should contain only one class of
feature data. ARC_GEN Import assumes that all features within a given file are of the same class,
and it assigns the data to the feature file accordingly.
For primitive and complex features, ARC_GEN Import uses the elevation stored in the input file.
ARC_GEN Import does not automatically set the elevation of point or text geometry features. To
set the elevation of point features, you should use a DTM or set the elevation value manually. To
set the elevation of text features, you should set the elevation manually.
Text and point features that contain +, -, white-space or

numeric characters(0-9) can be exported, but cannot be re-
imported.
When importing LIN files into Geographic projects, if the input LIN file contains points or text,
the Lat/Long coordinates are expected to be in units of arcseconds. If the input LIN file contains
lines or polygons, the Lat/Long coordinates are expected to be in units of arc seconds*PI/180. For
other project types, the project units are expected.
SOCET SET Page 18-5

The ARC-GEN Import window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project into which the ARC_GEN file
will be imported (only if started stand-alone).
File > Input ARC File Prompts you to pick an ARC_GEN file to import.
File > Output Feature Prompts you to enter the name of a feature database output file that the
Database features will be appended to. If the feature file does not exist, ARC_GEN
Import will prompt you to pick a feature specification file when you pick
the feature class; it will create the feature file for you according to the
feature specification file you chose.
File > Load DTM Prompts you to pick a DTM to provide an elevations for point features.
ARC-GEN Import interpolates an elevation for each point in the feature
from the DTM you picked. For setting elevations of text features see the
Feature Elevation field below. The default elevation is 0.000.
File > Exit Exits the ARC-GEN Import window.
Input Format > AMS, LIN Specifies the ARC_GEN input format.
SELECT TO
Project File Selected Name the project from which the ARC_GEN file will be imported. By
default, this is the name of the project that is currently loaded on the
workstation.
Input ARC File Name the input ARC_GEN file you selected to import.
Output Feature File Name the output feature file you selected as output destination.
Input Format Choose between AMS or LIN.
Page 18-6 SOCET SET

SELECT TO
Class Choose the feature class name to which the input features will be assigned.
DTM Name the input DTM you selected for setting feature elevations.
Feature Elevation Allow you to directly assign an elevation to a text or point feature. For
setting elevations, see also Load DTM above. The default elevation is
0.000.
Start Start importing the ARC_GEN file into the feature database.
18.4.1 Execution - ARC_Gen Import

Use the following steps to import ARC/INFO data into a feature database:
1. Click Preparation > Import > Features > ASCII (ARC_GEN) on the main workstation
window to start ARC_GEN Import.
2. Click File > Load Project on the ARC-GEN Import window. Pick the project you wish to
import the ARC_GEN file into and click OK.
3. Set the Input Format to either AMS or LIN.
4. Specify where to read the input ARC_GEN file from by clicking the tool button next to
Input ARC File on the ARC_GEN Import window. Pick the name of the ARC_GEN file
you wish to import. Click OK.
5. Select the name of your output feature file by typing a name in Output Feature Database
on the ARC_GEN Import window. This file can be an existing file, to which you will be
appending features at its end, or it can be a new file. If you choose to create a new file, you
will be prompted for a template file when you pick the feature class.
6. Click Class to select a Class. If the feature file you entered does not exist yet, you will be
prompted to pick a feature specification file first before it can be created. The Class
Submenu window pops up and prompts you to pick a feature class. Select the name of the
class you want to assign your input features to and click Close. Your selection appears in
the text box to the right of Class.
7. For setting feature elevations you have two choices: manually entering an elevation, or
taking elevations from an existing DTM.
a. To manually specify the feature elevation, click in the Feature Elevation field and type
the elevation value.
b. To specify a DTM to interpolate the elevations from, Click the tool button next to
DTM on the ARC-GEN Import window.
8. Click Start to import the ARC_GEN features.
To develop a complete feature file with multiple classes of data, it is necessary to repeat steps 6
through 8. If you are using a DTM to set your feature elevation(s), you do not need to change the
DTM name.
18.5 ASCII Feature Import

The ASCII Feature Import utilizes a copy of a feature database specification file and the export
file to import a feature database that was previously exported. Unlike the LIN and AMS exports
all of the features that are to be imported are contained in a single data file and will be imported
based upon the copy of the specification file.
SOCET SET Page 18-7

Unlike the LIN and AMS imports the ASCII Feature Import will import all data for the features
that were contained in the source database. This includes elevations for points and text as well as
element attributes for complex features.
The ASCII Feature Import window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project to import the ASCII features
File > Exit Exits the ASCII Feature Import window.
SELECT TO
File > Input ARC File Prompts you to pick an ASCII feature file to import.
Output Feature DB Type the name of the output feature database. Terminate your entry with a
carriage return.
18.5.1 AMS Export Files

The AMS format is recommended for most applications. This section discusses AMS export files.
Example AMS export file containing line features with CLASS = DRAIN, and with attributes of
NAME, CATEGORY, and SEASONAL.
1 NULL DITCH PERRENIAL 3 168
27307480.38 253548969.27 0 1847.65
27304416.86 253548586.46 0 1847.65
27303267.63 253548204.095 0 1847.65
...many more points...
27338261.72 253581932.66 0 1847.65
Page 18-8 SOCET SET

27339026.77 253581550.73 0 1847.65
27279008.25 253522979.77 0 1847.65
27231612.35 253512938.64 0 2056.93
27231611.69 253512556.54 0 2054.37
END
The first line contains the feature identifier number, feature attribute information, and the number
of points in the feature. This includes, in order of appearance, the feature ID (1), the feature name
(NULL), the type of drain (DITCH), the width of the ditch (3), and the number of points in the
feature (168). Subsequent lines give the coordinates. These are X and Y, followed by a zero
which indicates the value used by ARC/INFO for the elevation, and the actual elevation. This
form of ASCII data file does not contain an END statement at the conclusion of each feature. This
is an important difference between the LIN and AMS format.
Example AMS Feature Headers Extracted from an AMS File:
12 NULL DITCH INTERMITTENT 25 165
14 RIO CANAL PERRENIAL 59 0
In this example, feature headers were extracted from the AMS file. The most important thing to
note is that multiple elements of the same feature are assigned the same feature ID (as with feature
14 above). However, the characteristics of each element within a feature, in this case the width,
can vary. If you need more information about the attributes and features in a given AMS file, you
should refer to the .spc file associated with the translated data. This example was derived from
a feature file using the template.spc file.
Polygon data is translated into the same format as the lines; the first coordinate record is repeated
as the last coordinate recorded, in order to close the polygon. Thus, to get the polygon data into
ARC/INFO format, the GENERATE command should be used with the lines option. The
polygons can be reformed during the ARC/INFO CLEAN and BUILD options. Alternatively, you
can write an AML that reformats the polygon data into the required GENERATE format.
Example AMS Export File using points, with CLASS = SPOT:
default.icn 476666.078705 4424833.739162
SOCET SET Page 18-9

default.icn 476669.098302 4424920.033002
Text data is translated into the same format as for points, except the text data is in the first field
contains the text data (rather than the icon name).
Text containing +, -, white-space or numeric characters (0-9)

can be exported, but cannot be re-imported.
Elevation data are not exported for POINT or TEXT features.
18.5.2 LIN Export Files

This section discusses LIN export files. The major difference between AMS and LIN formats is
the format of the data files that each produces. As with the AMS option, LIN produces a data file
with the coordinate’s values. This data file has the file extension of .lin or .arc, depending
on whether an extension is specified in the output filename. If no extension is specified, the result
is a .lin file; else, if an extension is specified, a .arc file results.
Example LIN Export File For.arc and .lin Contents:
98306929369.528183 912776289384.554199 1847.653004
98295900708.755676 912774911267.470459 1847.653004
98291763471.875458 912773534744.520142 1847.653004
98413189263.776917 912653544701.644165 1847.653004
98414913310.948654 912654232883.402710 1847.653004
98416981929.339584 912654921144.866943 1847.653004
END
3 feature_id
98262309357.888733 912677926096.321289 1847.653004
98265752687.732635 912676551326.937378 1847.653004
98042081338.484909 912650707723.170410 2054.959473
98033804482.376343 912646579110.917480 2056.930664
98033802100.155960 912645203544.466919 2054.379395
END

END
In addition to the coordinate files, a descriptive file contains all the headers or variable
information associated with a given feature. As with the AMS case, multiple element features are
written with each element as a separate feature, but assigned the same feature ID.
Similar to the AMS mode of export, each class needs to be put into a separate data file to prevent
the ARC-GEN lines option from overwriting the output data. However, exporting text and point
data has the same limitations as mentioned above for AMS; namely, elevations for point and text
features are not exported, and features with +, -, or numeric characters can be exported but not
re-imported.
In the case of the LIN export, the feature attribute information and the line coordinate information
are separated into two files. The coordinate data is displayed above. The first line contains the
feature ID, subsequent lines contain the (x,y,z) information, and the feature continues until an
END statement is reached.
The following file contains an example of the attribute information associated with each feature.
Interpretation of this attribute information is done in a similar manner to the AMS export.
Example Attribute File for LIN Format:
$RECNO ID NAME CATEGORY SEASONAL WIDTH
1 1 DITCH PERRENIAL 3
18.5.3 Execution - ASCII Feature Import

Use the following set of steps import an ASCII feature file:
1. Click Preparation > Import > Features > ASCII on the main workstation window to start
ASCII Feature Import.
2. Click File > Load Project on the ASCII Feature Import window. Pick the project you wish
to import the features into and click OK.
3. Specify where to read the input feature file from by clicking the tool button next to Input
ARC File on the ASCII Feature Import window. Pick the name of the ASCII feature file
you wish to import. Click Open.
4. Type the name of the output feature database in the Output Feature DB field, followed by
a carriage return.
5. Click Start to import the features.

18.5.4 Batch Processing - ASCII Features Import

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type import_arc
input_arc_file File name (with full path prefix) of input ASCII file.
output_fdb_file File name (with full path prefix) of output feature database.
class_code Feature class code to be assigned to features during import. This value can
be determined by viewing the extraction specification file given by
spec_file. This is needed ONLY if the feature_type is an ARC_GEN
format - ams or moss.
feature_type Format of the ASCII file. May be one of the following: ams (for
ARC_GEN-AMS), moss (for ARC_GEN-LIN), or gams (for ASCII-
GAMS).
input_dtm_file File name (with full path prefix) of input DTH file. This is needed ONLY
if the feature_type is an ARC_GEN format—ams or moss. Specify NONE
if no DTM is to be used.
dtm_fill_value Number defining elevation of feature(s) if no input DTH file is specified.

The default elevation is 0.0. This is needed ONLY if the feature_type is an
ARC_GEN format—ams or moss.
spec_file File name (with full path prefix) of the default extraction specification file
used to create the output feature database.
18.6 Shapefile Import

A Shapefile stores non-topological geometry data and attribute data of a feature in a data set.
Shapefile is becoming a standard GIS file format used to port feature data from one system to
another. Further information on Shapefile can be found at:
http://www.esri.com
Shapefile Import reads 2D & 3D Shapefile data and writes them to SOCET SET feature database
(FDB). 2D Shapefiles can be imported into SOCET SET FDB which is always in 3D space. All
Z values in this case are set to 0. To populate the Z values from a DTM, you must use batch_fdb

which is a stand-alone application (See “Feature Database and Extraction Specification,”

Appendix C for detail).
The Shapefile Import window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project into which the Shapefile will
be imported (only if started stand-alone).
File > Open Shapefiles Prompts you to specify Shapefile directory. Normally, there may be one or
more sets of Shapefiles in a directory. Shapefile Import reads all sets of
Shapefiles in the directory and writes them all into feature database. You
must only select any one Shapefile after navigating to the directory. This
selection is used to determine the Shapefile directory instead of a specific
Shapefile because all Shapefiles will be imported regardless which
Shapefile you selected.
File > Exit Exits the Shapefile Import window.
SELECT TO
DTM Display the name of the Shapefile you selected to import.

SELECT TO
Shapefile Display the names of selected Shapefiles
Output FDB Display the name of the output feature database.

Map Integers to FACC Enumerated Names - Check to map integer values
to the enumerated value with that integer in the name. For example, integer
value 28 becomes the valid enumerated value of EXS028_Operational.
Specification File Generate New File will generate a feature database specification based on
information from all Shapefiles in the Shapefile directory.
Select Existing File prompts you to select an existing specification when
you Start.
Start Begin importing the Shapefiles.
18.6.1 Execution - Shapefile Import

Use the following set of steps to import Shapefiles:
1. Click Preparation > Import > Features > Shapefile on the main workstation window to
start Shapefile Import.
2. Click File > Load Project on the Shapefile Import window. Pick the project you wish to
import the Shapefile into and click OK. The coordinate system, datum, and the units of the
Shapefiles should match that of the project.
3. Specify where to read the input Shapefiles from by clicking File > OpenShapefiles, or by
right clicking Add in the Shapefiles display area, on the Shapefile Import window. Navigate
to the directory where all Shapefiles are going to be imported. Pick any one of the
Shapefiles and click Open.
Since all Shapefiles are going to be imported, it does not

matter which Shapefile you pick.
4. Specify output feature database by typing a name in the Output FDB line edit, on the
Shapefile window. Type a non-existing feature database name if you want to generate the
feature database specification from Shapefile information.
5. Specify how the feature database extraction specification should be determined by selecting
either the Generate New File or Select Existing File on the Shapefile Import window.
If you selected Generate New File, the extraction specification of the output feature
database will be created by the information from the Shapefiles.
6. Click Start to import the Shapefiles.
If you clicked Select Existing File, you will be prompted for an Extraction Specification
file. Pick the name of the Extraction Specification you wish to use. Click OK.
Feature geometry mapping between Shapefile and SOCET SET feature database are as follows:
SHAPEFILE SOCET SET FDB
Point/PointZ/MultipointZ/ Point/Text
PointM/MultipointM
Arc/ArcZ/ArcM Line/Multiline
Polygon/PolygonZ/ Polygon/Polyhedron
PolygonM

Each set of Shapefiles (.dbf, .shp, .shx) are imported to one class in SOCET SET feature database.
The shape name must be identical to class name. Otherwise, this Shapefile is not imported if you
selected Select Existing File. Attributes from .dbf file are imported into SOCET SET feature/
element attributes. Attribute name must be identical and type must be compatible. A string in .dbf
may be imported to NUMER_TYPE in SOCET SET if the names are identical.
Field type and attribute type compatible is as follows:
SHAPEFILE FIELD SOCET SET ATTRIBUTE

TYPE TYPE
Integer int
Double double/float
String string/enum
Feature ID numbers are regenerated depending on the order of inputs. In other words, if export
feature database to Shapefiles and then import them back to feature database, the feature ID
number may be different.
Shapefile extensions can be either lower case or upper case (i.e.: .SHP or .shp; .SHX or .shx;
.DBF or .dbf), but cannot be a mixture of upper and lower cases such as .Shp etc. Since Shapefile
does not have element attributes, the automatically created specification file will not have
element attributes as well as LINE and POLYGON geometry type. Also, the automatically
created specification will not have enum type attribute because Shapefile does not have enum
type field. If you select an existing specification file, then there may be all types of geometry and
attributes in the output feature database. If you export a feature databases into Shapefiles and then
import those Shapefiles back and you select the same specification file, then this process will get
exactly the same feature database back. When you select “Generate New File” option to generate
feature database specification based on data from shapefiles, the specification may have illegal
class names and attribute names. For example, WHITE is a reserved name and cannot be used for
attribute name. After shapefile import, if you use Feature Extraction to open the imported feature
database, you may get an error message stating that the name ‘WHITE” is illegal. If that happens,
you must use a text editor to open the specification file and change the name to something
different such as SS_WHITE. The specification is always located at your_project_data_directory/
your_feature_database_directory/spc.
18.6.2 Batch Processing - Shapefile Import

COMMAND LINE:

KEYWORD DESCRIPTION
conversion_type import_shape
input_shape_ Directory name (with full path prefix) of input Shapefiles.
directory
output_feature_ File name or directory (with full path prefix) of output feature database.
database
output_spec_file [option] File name (with full path prefix) of feature database specification.
18.7 DXF Feature Export

DXF Export converts SOCET SET native feature databases to AutoCAD 12 DXF format. This
format is compatible with Auto CAD 2000. DXF Export reads an entire feature database and
converts all features to DXF formaT.
The DXF Feature Export window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project from which the feature file
will be exported (only if started stand-alone).
File > Exit Exits the DXF Feature Export window.

SELECT TO
SelectFeature Database Display the name of the feature database selected to export.
Output DXF File Type the name of the output DXF file, followed by a carriage return.
Output Specify whether feature attributes should be written to the DXF File (select
Normal) or not (select CADMAP).
Start Begin exporting the feature file.
18.7.1 Execution - DXF Feature Export

Use the following set of steps export a feature file into the DXF format:
1. Click Output > File Export > Features > DXF on the main workstation window to start
DXF Feature Export.
2. Click File > Load Project on the DXF Feature Export window. Pick the project you wish
to export the features from and click OK.
3. Right click Add in the Select Feature Database area, on the DXF Feature Export window.
Pick the name of the feature database you wish to export. Click OK.
4. Specify where to write the output DXF file to by typing the file name in the Output DXF
File field, followed by a carriage return.
5. Select whether feature attributes should be output to the DXF file. If you wish attributes to
be included, click Normal, otherwise click CADMAP for no attributes.
6. Click Start to export the feature file.
If you experience problems importing a DXF file with attributes from SOCET SET into your
third-party application (such as Micro Station), re-export the DXF file from SOCET SET without
attributes by selecting CADMAP as your Output.
18.7.2 Batch Processing - DXF Features Export

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type export_dxf_feature
input_fdb_file File name (with full path prefix) of input feature database.
output_dxf_file File name (with full path prefix) of output DXF file.

write_attr_flag Character specifying whether attributes are written. Value may be 0 or 1.
18.8 ARC_GEN Export

ARC_GEN format is a simple ASCII vector format which you can use to export features from the
workstation.
When exporting ARC_GEN you have two output options: AMS and LIN. Selecting a particular
format (AMS or LIN) is project or application-dependent. Element attributes are not exported.
The ARC-GEN EXPORT window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project which contains the feature
database you wish to export (only if started stand-alone).
File > Exit Closes the ARC-GEN Export window.
SELECT TO
Input Feature Database Display the name of the feature file you selected to export.
Output ARC File Type the name of the output ARC_GEN file, followed by a carriage return.
Output Format Choose a format from AMS, LIN, or LIN FCODE.
Class Present a list of classes, based on the Input Feature File specified above,
from which you choose a single feature class to export.
Start Start the ARC-GEN Export.
18.8.1 AMS Export Files

The AMS format is produced on a per class basis and incorporates a description of the feature
along with ground points in a single file for primitive and complex features. The individual

features contained in these files are not delineated. The format of the file for complex and
primitive features is as follows:
feature_id_num ftr_attr_1 ftr_attr_2 ... ftr_attr_N

num_ground_points
groundPoint1.x groundPoint1.y 0 groundPoint1.z
... Many more points can exist here ..
groundPointN.x groundPointN.y 0 groundPointN.z
groundPoint1.x groundPoint1.y 0 groundPoint1.z (repeat 1st

if closed ftr)
feature_id_num ftr_attr_1 ftr_attr_2 ... ftr_attr_N

num_ground_points
groundPointN.x groundPointN.y 0 groundPointN.z
END (this line marks end of file)
The first line for each feature contains the feature identifier number, feature attributes, and the
number of groundpoints in the feature. The following lines give the coordinates of the feature.
These values are X and Y followed by a zero (0) and then the actual elevation.
The point and text features utilize two files for the export. The first file, the label file, contains
the text or icon file name and the ground points where the text or point are located. The format
of the file is:
text_string ground_point.x ground_point.y
(Additional entries as above)
END
The file extension for the label file must be .lbl. It should also be noted that both AMS and LIN
imports utilize the .lbl file extension but the format of these files are very different. The AMS
data is all contained on a single line for each feature. The LIN format uses two lines for each
feature.
The second file is the attribute file. The attribute file contains a description of each of the features
in the following format:
$RECNO ID ftr_attr_name1 ftr_attr_name2 ... ftr_attr_nameN

1 1 12 BUILDING ...
2 1 12 BUILDING ...
(additional records)
The first line in the file is a header. The header starts with the keyword $RECNO ID. The
keyword is then followed with the names of the feature attributes that are contained in the feature.
Following the header the data for the features is exported. For each feature there is a single line
of information.
There is no marker that denotes the end of the file.
18.8.2 LIN Export Files

The major difference between the AMS and LIN exports is the file formats that are produced. For
the primitive and complex features, the LIN export produces two files, an attribute file (.atr) and
a coordinate file (.lin). Like the AMS export only a single class can be exported at a time. When
exporting to LIN files in Geographic projects, the Lat/Long coordinates are output in units of
arcseconds. For other project types, the project units are used.
The attribute file contains a description of each of the features in the following format:
$RECNO ID ftr_attr_name1 ftr_attr_name2 ...ftr_attr_nameN
1 1 12 BUILDING ...
2 1 12 BUILDING ...
(additional records)
There is no marker that denotes the end of the file.
The coordinate file contains the coordinates of the feature. Each of the features has the word END
following the last coordinate for the feature. The file also has the keyword END to terminate the
file. The file is in the following format:
ftr_id
gnd_pt1.x grd_pt1.y grd_pt1.z
(Additional ground points go here)
gnd_ptN.x grd_ptN.y grd_ptN.z
gnd_pt1.x grd_pt1.y grd_pt1.z(first line is repeated for

closed ftrs)
END
(Additional entries as above)
END

For the point and text features, the LIN Export utilizes three files. A label file, a coordinate file,
and an attribute file:
The attribute file has the same format as the primitive and complex feature attribute file.
The label file contains the feature identifier for the feature and the text or icon file associated with
the feature. This file is similar to the AMS point/text label file but the information is contained
on two rows.
The file has the following format:
ftr_id
text_or_icon_filename
(Additional feature entries as above)
END
The coordinate file has a record for each point or text feature. The file has the following format:
ftr_id gnd_pt.x gnd_pt.y gnd_pt.z
(Entries for additional features)
END
18.8.3 LIN FCODE Export Files

LIN FCODE is a special mode for exporting features that were built with N G A feature code spec
files. This mode uses the NGA feature codes to specify the output filenames. LIN FCODE Export
is simply the LIN Export with a hard coded output filename. NGA feature codes consist of two
letters, three numbers, one underscore, and one of three letters – ‘A’, ‘P’, or ‘L’. ‘A’ is for an
A r e a F e a t u r e , ‘P’ is for a point feature, and ‘L’ is for a linear feature. For example,
BA040_A_OpenWater indicates that this is an area feature class. BA040_A is the feature code,
and OpenWater is a description of the class.
What LIN FCODE Export does is it takes the feature code, converts it into lower case, and then
outputs the features in LIN format, using the feature code as the filename. For example, if you
ARC GEN Exported the class “BA040_A_OpenWater” using LIN FCODE, the following files
would appear in your project directory: ba040_a.lin, ba040_a.atr, and ba040_a.lbl. The label
file(.lbl) only appears for POINT and TEXT features.
Only use this mode if you have N G A feature code spec files
and want these specific filenames!
18.8.4 Execution - ARC_GEN Export

Use the following steps to export ARC/INFO data from a workstation feature data file into an
ARC/INFO translation format:
1. Click Output > File Export > Features > ASCII (ARC_GEN) on the main workstation
window. The ARC-GEN EXPORT window appears.

2. [Optional] Load a project by clicking File > Load Project on the ARC-GEN EXPORT
window. Select a project name. Click OK.
3. Click the tool button next to Input Feature Database on the ARC-GEN Export window.
Select the feature database you wish to export. Click Open.
4. Type the name of the output file into the Output ARC File field.
Each class should be placed in a separate output file because

most classes will be imported into ARC/INFO as separate
coverages. If separate data files are not used for each class,
ARC-GEN Export will overwrite existing ASCII data files. Also,
multi-element features will be translated as separate features
with the same ID number.
5. Select your output format option, either AMS or LIN. The AMS option is recommended for
most applications.
6. Click the tool button next to All Classes. This brings up the Class Submenu window,
containing the list of feature classes in your input feature file. Pick one and click Close to
return to the ARC-GEN Export window.
7. Click Start to export the features.

18.9 ASCII Feature Export

The ASCII Feature Export function outputs a GAMS formatted ASCII feature file.
The ASCII Feature Export window’s selections are as follows:
database to export (only if started stand-alone).
File > Exit Exits the ASCII Feature Export window.
SELECT TO
Input Name and path of the input feature database.

Feature Database
Output ARC File Type the name of the output ASCII file.
18.9.1 GAMS Export Files

The GAMS format outputs all of the features that are contained in the feature database to a single
data file. A copy of the source feature database specification file will be created on the successful
export of the data. This copy will be utilized to re-import features into a new feature database.
See “Feature Database and Extraction Specification,” Appendix C for details.
The GAMS format will export all information about a feature. This includes the element
attributes contained in a complex feature. The information is contained in a single .gams file,
while the specification file will be copied into a .spc file, with the corresponding name. Note that
there is a formatting difference between certain geometries.The format of the ASCII Feature
Export file is as follows:
For the primitive and complex features:

ftr_id ftr_name class_code attr1 attr2 ... attrN num_pts

layer_value
ELEMENT_ATTRIBUTES ele_attr1 ... ele_attrN

END_OF_ELEMENT_ATTRIBUTES
grd_pt1.x grd_pt1.y 0 grd_pt1.z
grd_pt2.x grd_pt2.y 0 grd_pt2.z
(Many more points can exist here)
grd_ptN.x grd_ptN.y 0 grd_ptN.z
grd_pt1.x grd_pt1.y 0 grd_pt1.z (repeat 1st pt if closed

feature)
(additional features in same format as above)
END
For the point and text features:
ftr_id ftr_name class_code attr1 attr2 ... attrN num_pts

layer_value
ELEMENT_ATTRIBUTES END_OF_ELEMENT_ATTRIBUTES
text_or_icon_value
font_size font_type font_style rot_angle
grd_pt.x grd_pt.y 0 grd_pt.z
(additional features in same format as above)
18.9.2 Execution - ASCII Feature Export

Use the following set of steps export an ASCII feature file:
1. Click Output > File Export > Features > ASCII on the main workstation window to start
ASCII Feature Export.
2. Click File > Load Project on the ASCII Feature Export window. Pick the project you wish
to export the features from and click OK.
3. Click File > Input Feature Database on the ASCII Feature Export window. Pick the name
of the feature database you wish to export. Click OK.
4. Specify where to write the output ASCII feature file to by typing the file name in the Output
ARC File field, followed by a carriage return.

Performing ASCII Feature Export/Import on a feature database

containing texture patches will result in the loss of texture
patch image point information. Texture patches will not be
viewable with supported rendering engines until the texture
patch image points are resampled.
18.9.3 Batch Processing - ASCII Features Export

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type export_arc
input_feature_ File name (with full path prefix) of input feature database.
file
output_arc_file File name (with full path prefix) of output ASCII file.
class_code Feature class code of the features to be exported. This numerical value can be
determined by viewing the extraction specification file associated with the
input feature database. This is needed ONLY if your convert_mode is
export_arc.
convert_mode Conversion sub-mode of export_arc. May be one of the following:
export_arc (for ARC_GEN), export_ascii_feat
(for ASCII-GAMS), or export_mp_ascii_feat (for
MP)
feature_type Output format of ARC_GEN data This is needed ONLY if your
convert_mode is export_arc. May be of the following: ams
(for AMS), or moss (for LIN).

18.10 MP ASCII Feature Export

The MP ASCII Feature Export window’s selections are as follows:
database to export (only if started stand-alone).
File > Exit Exits the MP ASCII Feature Export window.
SELECT TO
Input Feature Database Name and identify the path of the input feature database.
Output MP ASCII File Type the name of the output MP ASCII file, followed by a carriage return.
The MP ASCII format is simple format for storing points, lines, and polygons. It originated many
years ago for transferring V e c t o r D a t a into and out of contouring and TIN programs. MP
ASCII is now the defacto standard for transferring data between photogrammetric systems. The
MP stands for Mass Points but this is no longer accurate because MP files can contain lines and
polygons as well as points. MP ASCII is stored in five columns, as shown below:
00036_1 484842.010 3619905.021 200.201 11
00060_2 484843.022 3619905.340 203.101 21
00060_2 484839.110 3619905.121 199.005 22
00060_2 484847.510 3619905.121 205.001 22
00060_2 484849.010 3619905.444 204.006 22
00060_2 484852.210 3619905.445 210.221 22
00060_2 484853.011 3619907.021 200.001 23
00075_3 484842.010 3619905.331 211.001 21

00075_3 484845.010 3619905.021 200.001 22
00075_3 484846.010 3619905.021 200.001 22
00075_3 484847.210 3619905.333 200.001 22
00075_3 484850.010 3619905.321 200.022 22
00075_3 484843.030 3619905.456 200.001 22
00075_3 484844.345 3619905.111 209.001 22
00075_3 484842.333 3619904.998 200.001 22
00075_3 484845.010 3619905.331 200.001 23
The element class code is first, followed by an underscore and the feature id number. The next
fields are the X and Y coordinates followed by the elevation. The final value is a code indicating
the type of point—11 indicates a single point element, 21 indicates the first point of a multipoint
element, 22 indicates an intermediate point of a multi-point element, and 23 indicates the last
point of a multi-point element. See “Feature Database and Extraction Specification,”
Appendix C for an explanation of element class code and feature ID number.
18.10.1 Execution - MP ASCII Feature Export

Use the following set of steps export an MP ASCII feature file:
1. Click Output > File Export > Features > ASCII (MP) on the main workstation window to
start MP ASCII Feature Export.
2. Click File > Load Project on the MP ASCII Feature Export window. Pick the project you
wish to export the features from and click OK.
3. Click the tool button next to Input Feature Database on the MP ASCII Feature Export
window. Pick the name of the feature database you wish to export. Click OK.
4. Specify where to write the output MP ASCII feature file by typing the file name in the
Output MP ASCII File field, followed by a carriage return.
18.11 Shapefile Export

Shapefile Export converts a SOCET SET feature database to a set of Shapefiles; however, when
export feature database to Shapefile, feature attribute names and element attribute names must be
unique.
Shapefile Export reads all classes which have at least one feature in the feature database and
converts each class into a set of Shapefiles. All sets of Shapefiles are exported into the same
directory. The name of the Shapefile is the same as the class name.

The Shapefile Export window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project from which the feature
database will be exported (only if started stand-alone).
File > Exit Exits the Shapefile Export window.
SELECT TO
Input Feature Database Display the name of the feature database selected to export.
Export Directory Type the name of the export Shapefile directory, followed by a carriage
return.
Convert FACC Enumerated When checked this will export the integer part of an enumerated name. For
Names to Integers example, enumerated name EXS028_Operational would be exported as the
number 28.
Exclude SS_ID Attribute SS_ID is an added special attribute during Shapefile export. It is only used
when you import the same shapefile you just exported.
This attribute is not a part of the feature database. This attribute is added
during the Shapefile Export process. If you do not want this added
attribute, you check the Exclude SS_ID attribute
Export Multiline and Export a complex SOCET SET feature into multi parts shape. You may
Polyhedron to Multi Parts export each element of a complex SOCET SET feature into an individual
single part shape if this option is off.
Start Begin exporting the feature database.
The m value in the Shapefile is not populated. An ASCII file with all project information is
created when exporting to Shapefile. The file name is socet_project and it resides in the same
directory as the rest of the Shapefiles.

By default, each element of a complex feature (Multiline or Polyhedron) is exported as one

PolyLineZ or PolygonZ. For example, a Polyhedron feature with 10 elements is exported as 10
PolygonZ shapes. Element attributes are exported to Shapefile .dbf as fields. In other words, they
are treated the same as feature attributes. The first field in .dbf is: SS_ID of Integer type with 4
byte width For TEXT type feature, the second field is: SS_TEXT of String type with 255 byte
width. The rest of the fields are feature attributes first followed by element attributes. The
mapping between SOCET SET attributes and Shapefile fields are:
SOCET SET TYPE DBF TYPE
int Integer
float Double
double Double
string String
enum String
For ASCII_TYPE, if the length in the feature database is more than 255, it is truncated to 255.
The reason is that .dbf file uses 1 byte to store the width/length of a field and 1 byte can only hold
255 as the max number. By default, Shapefile Export exports elements of complex features as
individual features to Shapefile. All elements of the same complex feature have the same SS_ID.
This is the way to tell which elements form a complex feature. SOCET SET graphic attributes are
not exported. SOCET SET image patch image coordinates are not exported. For text features, the
rotation angles are not exported.
To export complex features as multi part shapes rather than individual shapes, set the
EXPORT_MULTI_ELEMENT_SHAPES environment variable before exporting the feature
database. For example, with this environment variable set, a Polyhedron would be exported as a
multipart PolygonZ. Note that only feature attributes will be transferred to the shapefile. Element
attributes will not be preserved.
18.11.1 Execution - ShapeFile

Use the following set of steps export a feature database into Shapefiles:
1. Click Output > File Export > Features > Shapefile from the main workstation window to
start Shapefile Export.
2. Click File > Load Project on the Shapefile Export window. Pick the project you wish to
export the features from and click OK. This step is not needed if you start from the main
workstation window.
3. Click File > Input Feature Database on the Shapefile Export window. Pick the name of
the feature database you wish to export and click OK.
4. Specify where to write the output Shapefile directory to by typing the name in the Export
Directory field, followed by a carriage return.
5. (Optional) Check the Convert FACC Enumerated Names to Integers box to output integer
names to the Shapefile. For example, OHD002_5dot0_and_10dot0 becomes 2.
6. (Optional) Check the Exclude SS_ID attribute to add a special attribute during Shapefile
export, only if you import the same shapefile you just exported.
7. (Optional) Check the Multiline and Polyhedron to Multi Parts.

8. Click Start to export the feature database.
18.11.2 Batch Processing - Shapefile Export

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type export_shape
input_feature_ File name or directory (with full path prefix) of input feature database.
database
output_shape_ Directory name (with full path prefix) of output shapefile directory.
directory
18.12 DGN Feature Export

DGN Feature Export, exports a feature database into the Intergraph DGN format used by
MicroStation.
You can also use DGN Feature Export to export continuous terrain contours from SOCET SET
to the Intergraph DGN format. Exporting contours is a two-step process, consisting of the
following:
• First, use the SOCET SET Terrain Graphics tool to convert the DTM into a feature
database containing contours.
•Next, use DGN Feature Export to export the feature database containing the contours to
the Intergraph DGN format.

The DGN Feature Export window’s selections are as follows:
File > Load Project Prompts you to pick the name of the project from which the feature
database will be exported (only if started stand-alone).
File > Exit Exits the DGN Feature Export window.
SELECT TO
Input Prompts you to pick a feature database to export. Name the feature
Feature Database database you selected to export.
Output DGN File Specify the name and directory path of the output Intergraph DGN file.
You can edit this field to change the directory and/or file name.
Seed File Prompts you to pick an Intergraph DGN seed file. Name the seed file you
selected.
Template File Prompts you to pick an Intergraph DGN template file. Name the template
file you selected.
Report File Specify the name and directory path of the output report file. You can edit
this field to change the directory and/or file name.
Start Start exporting the feature database into the Intergraph DGN format.
SOCET SET provides translators converting digital terrain data and feature data into Intergraph
Microstation DGN format. DTM features and post data can be translated directly. Continuous
contours can be translated by converting them into features, and then translating the features.
Each of these conversions is discussed separately below.
During the translation of terrain data and features, several assumptions are made.
1. All features and seed files are three dimensional; thus it is assumed the seed files must also
be three-dimensional.
2. Ground points are converted from doubles to UOR longs by performing the following
procedure:
a. A ground point converted to SRG coordinates. SRG coordinates are a local coordinate
system which have a strong effect with geographic projects. In geographic projects the
coordinates are stored as radians, and the SRG coordinates are meters. For other types
of projects, the SRG coordinate transformation has no effect other than swapping the
X and Y coordinates.
b. From SRG coordinates, the groundpoints are multiplied by the conversion factor. The
conversion factor based on seed file sdmap3d.dgn has the value of 1000. This
represents the number of subunits per master unit of feet. If the SRG coordinates are
in meters and the seed file requires feet (as is the case with sdmap3d.dgn), the
coordinates are also multiplied by a meters_to_feet conversion factor.
c. Finally, the doubles are recast as longs, effectively truncating the converted
groundpoints.
3. You have to correctly set the seed file parameters for a given project. It is very likely that
a seed file for one project will not be correct for other projects. If you start getting “out of
range” error messages, it is likely that the seed file parameters are incorrect. In this case,

you should verify that the global origin and master units are properly specified. Consult
your MicroStation manual set for more information on the seed file.
18.12.1 Execution - DGN Feature Export

Use the following set of steps to export a feature database into the Intergraph DGN format:
1. Click Output > File Export > Features > DGN Feature on the main workstation window
to start DGN Feature Export.
2. Click File > Load Project on the DGN Feature Export window. Pick the project you wish
to export the feature database from and click OK.
3. Click the tool button next to Input Feature Database on the DGN Feature Export window.
Pick the name of the feature database you wish to export. Click OK.
4. Click the tool button next to Seed File on the DGN Feature Export window. Pick the name
of the Intergraph DGN seed file you wish to export. Click Open.
5. Click the tool button next to Template File on the DGN Feature Export window. Pick the
name of the Intergraph DGN Template file you wish to export. Click Open.
6. Modify the name and/or output path in the Output DGN File field if you want the file to go
to a different directory and/or have a different name.
7. Click Start to export the feature database as an Intergraph DGN file.
18.12.2 Seed File

Before you can export an Intergraph DGN file, you must set up a seed file in MicroStation. The
seed file is an existing Intergraph DGN file that contains information on the boundaries and setup
format used by Microstation. The entire seed file is copied into the new Intergraph DGN file
being created. SOCET SET features are appended to the end of this seed file.
You must carefully specify appropriate scale factors and global origins. If you attempt to export
with incorrect scale or global origin information, DGN Feature Export will generate error
messages indicating that there is a problem.
18.12.3 DGN Feature Template File

You need to provide an Intergraph DGN Feature Template file for translating the features to
Intergraph DGN elements. A sample template file is provided in <install_path>/
internal_dbs/SPECS/feature_template.dgn.
The Intergraph DGN Feature Template file is based on the template file used for developing
feature database; it has the following format:
The first contains the file identifier, which must be the string Template_File a.
The rest of the lines in the file contain the class definitions. A class definition is of the form:
class
class_name
class_code dgn_level line_style line_weight line_color elem_type
any other information desired (text is ignored)
end class

The following table defines the required data:
FIELDS DESCRIPTION
class_name Class name from the template.
class_code Integer, class code assigned in the feature database specification file.
dgn_level Integer between 0 and 63, MicroStation level assigned to class.
line_style Integer between 0 and 8, MicroStation line style, needed for all element
types.
line_weight Integer between 0 and 31, MicroStation line weight, needed for all element
types.
line_color Integer between 0 and 255, MicroStation line color, needed for all element
types.
elem_type Integer, MicroStation element type.
White-space is insignificant, but the order of the first two entries (class and class_name) are
critical.
The following is an example Feature Database Template File. The indentations shown are not
mandatory, but are included for the sake of clarity:
Template_File a
class
PROFILE
0 4 0 0 0 4
profile lines
end class
class
POST
1 4 0 5 2 POINT
terrain model post data
end class
class
CONTOUR
2 4 0 1 1 LINE

smoothed contour lines from dtm
end class
class
LABEL
3 4 0 1 3 TEXT
dtm labels
end class
class
CONTOUR_INDEX
4 4 1 2 4 LINE
index contours
end class
18.12.4 Batch Processing - DGN Features Export

COMMAND LINE:
KEYWORD DESCRIPTION
conversion_type export_dgn_ftr
input_fdb_file File name (with full path prefix) of input feature database.
output_dgn_file File name (with full path prefix) of output DGN file.
report_file File name (with full path prefix) of output report file.
seed_file File name (with full path prefix) of input seed file.
template_file File name (with full path prefix) of input template file.

Chapter 19
SOCET for ArcGIS ®

SOCET for ArcGIS embeds SOCET SET stereo viewport into
ArcMap such that SOCET SET Sketch tools and ArcMap
editing tools can be used to extract and edit 3D features in a
true 3D stereo environment.
19.1 Overview
SOCET for ArcGIS is an extension that allows
communication between SOCET SET and ESRI's
ArcMap. The extension gives the capability of
using SOCET SET sketch tools or ArcMap tools to
perform feature extraction in SOCET SET's stereo
viewport while storing the features in ArcMap.
SOCET for ArcGIS embeds the photogrammetry
into ArcMap. A new database can be populated
rapidly from the imagery. Also, because the
features are superimposed on the steroscopic view
of the imagery, it is easy to check the database for
completeness or update an existing database.
Since the stereo viewport is only used for
extraction and display of features, all of ArcMap's
features (such as topology validation rules,
versioning, symbology, etc.) can be used
transparently. This will also work with any custom
tools developed for ArcMap.
Once imagery has been loaded in a stereoscopic
window within the ArcMap environment, you can
select the familiar Editor tools in ArcMap (which
now work in 3D), or use the SOCET SET Sketch
tools, which include many functions for 3D
collection and editing. All that is necessary is a
single SOCET SET workstation to manage
projects, import imagery and carry out
triangulation.
SOCET SET Page 19-1

Chapter 19 - SOCET for ArcGIS®
19.2 SOCET for ArcGIS

To start the application select Extraction > SOCET for ArcGIS. This will launch the following
toolbar and start ArcMap if it is not already started. The entire set of tool bars will be disabled
until you connect to SOCET SET from ArcMap. The sketch toolbars can be customized, by right
clicking Customize.
The SOCET for ArcGIS window’s selections are as follows:
SELECT TO
Load DTM Loads a DTM. The DTM name will be displayed on the title bar of
the window. When displaying 2D features from ArcMap, all
vertices will get Z values from the DTM.
Update All Invalid Updates all invalid elevations for selected layers. The definition of
Elevations from a DTM invalid elevations is set in the preferences window. There is also
the option to set what MBR to use when selecting what features to
update.
Arcmap Tools On/Off Turns off the sketch tools and makes ArcMap tools active.
Preferences Spawns the preferences window.
Help Launches the online help.
The rest of the tool buttons are sketch tools. See “Sketch,” Chapter 58 for their usage.
19.2.1 ArcMap extension toolbar

If this is the first time using this extension you will need to add the toolbar to ArcMap. Right click
on the toolbars and select SOCET for ArcGIS. The following toolbar will now appear in ArcMap:
After connection
Page 19-2 SOCET SET

The SOCET for ArcGIS window’s selections are as follows:
SELECT TO
SOCET SET On-line Start SOCET for ArcGIS. This performs the connection to
SOCET SET.
SOCET SET Off-line Stop SOCET for ArcGIS. This severs the connection from
SOCET SET.
Zoom to Extent Zoom to SOCET Viewer extent. Make the canvas match the extent
of the viewable area in SOCET SET's viewport.
Synchronize Cursors Synchronize SOCET Cursor With ArcMap Cursor. This will toggle
on/off the preference of the same name in the Preference window
below. The best way to use this is to map an accelerator key to this
command in ArcMap. Right-click on the toolbar and select
'Customize…', Click on 'Keyboard...,' Select 'SOCET for ArcGIS
Extension' from the 'Categories' list-box, Select 'Synchronize
SOCET Cursor With ArcMap Cursor' from the 'Commands' list-
box, Type in a key (i.e. F3) and press 'Assign'. In SOCET SET, you
can toggle the extraction cursor On/Off. In ArcMap, you use an
accelerator key. This is useful when you want to move the ArcMap
cursor out of the canvas and do not want the SOCET extraction
cursor to move.
Refresh Visible Graphics in Refresh the visible area of graphics in the ArcMap Canvas to the stereo
ArcMap Canvas to SOCET view port in SOCET SET. This works much like the 'Refresh Graphics'
SET button on the stereo view port, but the extent of refreshed graphics is
controlled by what is visible in ArcMap. The 'Refresh Graphics' button on
the stereo viewport will refresh either it's visible extent or all graphics
depending on whether graphics mode is set to 'Limited' or 'Full'.
19.2.2 Preferences
By default the SOCET SET viewport will toggle to be on top of all other windows when the
extraction cursor is toggled in. Check this to disable this behavior.
The preferences can be set by clicking on the preferences tool button on the SOCET for ArcGIS
application. Most of the preferences deal with how the sketch tools behave. See “Sketch,”
Chapter 58 for more information.
SOCET SET Page 19-3

The SOCET for ArcGIS preferences are explained below.Setup / Operation Notes
OPTION BEHAVIOR
Viewport Always On This will cause SOCET SET's current, active, viewport to stay on
Top. top of all other windows.
Hide Status Box. When selected, the status box under the toolbars is hidden. Un-
select this to get hints about using sketch tools.
Synchronize SOCET With ArcMap Canvas. This will cause the cursor in SOCET SET's
Cursor With ArcMap viewport to track with the cursor movements in ArcMap's canvas.
Cursor. This only works if the ArcMap tools are active. You should map an
accelerator key in ArcMap to toggle this on or off.
Dynamically Match This will cause ArcMap's canvas to always zoom to the same extent
Viewable Extent. as the viewable area in SOCET SET's active viewport. Turn this off
for increased performance.
Page 19-4 SOCET SET

OPTION BEHAVIOR
Dynamically Refresh When this is on, ArcMap's canvas will automatically update
ArcMap Canvas whenever a change is made in the SOCET SET viewport. Turn this
off for increased performance.
Turn Off Polygon Fill Selecting this will turn off the fill for all polygons. This may help
performance with roaming in the viewport
Turn Off Vertex Icons Normally all vertices are drawn with a square icon. Selecting this will
cause them to be drawn without the icon.
Disable Coordinate Normally coordinate transformations are done in real time between the
Transformation SOCET SET viewport and the ArcMap canvas. If you know that you have
the exact same coordinate systems in SOCET SET and ArcMap you can
turn off coordinate transformations for a performance improvement. Note:
They are always off if either of the coordinate systems is unknown (ie.
LSR or User)
Disable Loading Map Cache By default the Map Cache will be built for the viewable extent when you
Upon Starting Editing start editing. This will speed up many functions when using a geodatabase,
including 3D snapping. Check this to eliminate building it. You can always
build it in ArcMap.
Use MMB for 3D Snapping ArcMap normally tries to snap whenever a mouse move event takes place.
with ArcMap Tools This can be rather slow when there are a lot of features in the area. When
this is checked, assuming you are using ArcMap tools and toggled into the
stereo viewport, ArcMap will only try to snap when the middle mouse
button is pressed. Notice that SOCET SET’s tools also use the MMB for
snapping. This doesn’t have any affect if the user is roaming in the
ArcMap canvas.
Disable Auto Attribution This will disable the auto-population of attributes, such as ARA,
LEN_BFR, ZV7, HGT, etc., while using SOCET SET extraction tools.
Measure HGT/Zxx This option allows you to measure two additional temporary points after
collecting a feature to calculate HGT and ZV2 or any of it's variants (ZV7,
Z7F, Z5F, Z5M). The first point should be on the ground and the second
point should be at the maximum elevation of the feature. HGT is calculated
from the second point minus the first and ZV2 from the second point. If the
feature is already collected at the appropriate height, and not at 'gutter
level', for example, the second sampled point will be ignored if it is at the
same elevation or below the first sampled point. In this case HGT is
calculated from the highest point of the feature minus the first extra
sampled point and ZV2 is the highest point of the feature. For point
features, if the AOO and the 'Measure HGT/Zxx' options are on, the first
extra point serves as both the ground measurement and the angle of
orientation calculation.
Disable AOO only This option will disable auto-populating the Angle of Orientation for point
features. This saves the you an extra click you are not interested in
populating the AOO value..
Definition of Invalid Normally the user should use the void value that is defined by ESRI.
Elevations in ArcMap Selecting 'Zero', will treat all elevations with a value of zero as invalid
elevations. They will then be displayed using either the DTM or the
extraction cursor, depending on what is selected below. This is also used
when determining which elevations to update when updating from a DTM.
Display of Invalid Normally void elevations from ArcMap will be displayed with the value
Elevations from ArcMap from the DTM, if one is loaded. Selecting 'Use Extraction Cursor', will use
the value of the extraction cursor to display all void elevations.
MBR for Updating Invalid This will select whether you want to use the DTM’s or the view port’s
Elevations from a DTM maximum bounding rectangle to select which features invalid elevations to
update.
SOCET SET Page 19-5

19.2.2.1 Coordinate Systems / Datums

The coordinates will be transformed between the SOCET SET viewport and the ArcMap canvas
as long as both systems are using a defined coordinate system, such as Geographic or Grid / State
Plane. Coordinate transformations will not occur while using a local LSR. In other words, it is
not required that the feature layer in ArcMap have the same coordinate system as SOCET SET,
except that LSR must match Spatial Unknown. This behavior can be disabled in the preferences
for a small performance increase. Only do this if you are sure that you have matching coordinate
systems in SOCET SET and ArcMap.
19.2.2.2 3D Snapping
To turn on 3D snapping, select Editor > Snapping in ArcMap. Put a check mark next to “SOCET
3D Snap” in the bottom of the widget, under “Miscellaneous”. The snap agent will be active only
when using an ArcMap tool in the SOCET SET viewport. The preferences for snapping should
be set from the “SOCET for ArcGIS” preference's window, under “SK-Snap.” Make sure the
“Sample” box is checked. The 3D snap agent supports snapping to vertices, and edges.
You should not select “Vertex”, “Edge”, or “End” in the ArcMap “Snapping Environment”
widget. These will override the “SOCET for ArcGIS” preferences in ArcMap not to mention
limiting the user to 2D snapping in the ArcMap canvas. Snapping to a specific layer can be
accomplished by turning off the unwanted layers in the Table of Contents (TOC) in ArcMap.
When using snap in the SOCET SET viewport, the circle in the cursor will be the size of the XY
pixel tolerance at a 1:1 zoom level. This is designed to help guide the user within the snapping
tolerance. See “Sketch Preferences” on page 58-14 or “Snapping to Another Object” on page 58-
21 for more information.
By default, a map cache for the viewable extent will be built when editing starts. This will speed
up many common functions, including 3D snapping when working with a geodatabase. There is
an option on the preferences dialog to turn this off. A new map cache can be built in ArcMap using
the Map Cache toolbar. You may want to do this if your viewable extent has changed and
snapping or roaming seems slow.
ArcMap normally tries to snap every time the mouse moves. If you want to try and speed up the
roaming performance, there is an option in the preferences window to use the middle mouse
button to snap. The snapping with ArcMap tools will now behave like SOCET SET Sketch tools.
The symbology of point features in the viewport will not always match exactly with what is
displayed in ArcMap. The color will be the same, though. If the symbology of a feature is changed
in ArcMap, during an active edit session, you must refresh the graphics to see the changes. If a
new map is loaded, the connection to SOCET SET will have to be started again, if it was already
active. Just press “Stop SOCET for ArcGIS” followed by “Start SOCET for ArcGIS”.
When editing with the ArcMap sketch tools, moving a vertex will result in the wrong elevation
being recorded. The tools interpolate elevation from the surrounding points.
19.2.2.3 Volumetric Features

To extract 3D volumetric features such as buildings, you can only use 3D Shapefiles. Personal
geodatabase and multi-users geodatabase do not support vertical polygons. When projecting a
vertical polygon into XY space, it becomes a line. As a result, 3D volumetric features with
vertical polygons are rejected. ArcMap editing tools cannot deal with vertical polygons. To edit
a 3D volumetric feature with vertical polygons, you must use SOCET SET Sketch tools.
Page 19-6 SOCET SET

19.2.2.4 Mapping hot keys or mouse buttons

From SOCET SET, select Preferences > Keyboard/Trackball Accelerator Mapping. By
selecting SOCET for ArcGIS you may map some sketch or ArcMap commands to your keyboard
or mouse. To emulate a double-click from a 3-D mouse map a button under “Main Image Display
- Emulate Mouse Double Click”. This will make it easier to accept features when using ArcMap
tools.
19.3 Execution
19.3.1 Basic Workflow for SOCET for ArcGIS

1. Start SOCET SET.
2. From the main SOCET SET window, load a project. Select File > Load Project.
3. From the Select Project File window, select your project and click OK.
4. From the SOCET SET main window, load your images. Select File > Load Images.
SOCET SET Page 19-7

5. The Image Loader displays. Select the left and right image for display by left-clicking one
on each image you would like selected. The image will appear highlighted in blue once
selected and then will appear highlighted in gray once you have moved the cursor outside
of the selection window.
6. Depending on whether or not you have a viewport open, do one of the following:
1 - If you have a blank viewport open, press the Load button once you have selected your
images for loading.
2 - If you do not have a viewport open, select Create and then load the images. You can
create more than one image viewport by clicking on Create again, which creates
viewport 2. Then you can load additional images or the same images into this new
viewport. Some users like to have a second viewport loaded with the same imagery as
viewport 1, but at a different minification level so an extraction overview port is
available.
7. The following settings are standard for stereo feature extraction, however you may decide
later to alter the settings depending on your personal preferences.
Page 19-8 SOCET SET

8. Initiate SOCET for ArcGIS. From the main SOCET SET window, select Extraction >
SOCET for ArcGIS.
9. The SOCET for ArcGIS toolbar appears and ArcMap launches automatically. Initially, the
SOCET for ArcGIS toolbar is grayed out and not selectable. To make it selectable, link
SOCET for ArcGIS and the ArcMap Canvas. This can be done after data is loaded into the
ArcMap Canvas.
10. Loading Data into the ArcMap Canvas. There are three options for loading data into an
ArcMap Canvas. Select the method (Options A, B, or C described below) you would like
to use and follow the associated instructions.
Option A
1. Select A new empty map.
SOCET SET Page 19-9

2. Add Data.
3. Browse to the data to add in the Add Data window and select Add. You can choose between
A Personal GeoDatabase or Shapefiles. Both contain the same data, so choose the format
you work with most regularly. NOTE: Load a project file of your choosing.

Option B
Load An existing map. Highlight the .mxd file and select OK.

Option C
1. Connect to an ArcSDE instance. Select A new empty map option and database connections
and connect to your multi-user database.
2. Initially, you may need to establish the connection by using the Add Spatial Database
Connection window. To establish the connection you need to know the correct settings for
the Server, Service, User Name and Password. Note that these are not standard settings and
are subject to change from project to project and between users. If you do not know these
settings, consult with your production manager or IT department before attempting to fill
this information.

3. Once you have connected to the database, create the version. In the ArcMap table of
contents, select the Source tab in order to view and confirm the following changes.
4. Select on New Version in the versioning toolbar.
5. In the New Version window, select your Parent Version and create your new version’s
name.
6. Under Permission select from Private, Public, or Protected depending on which is
appropriate for your work and then ensure that Switch to this new version is checked.
Select OK.
7. Verify the version change by looking under layers inside the table of contents on ArcMap.
The version you have just created should display.
8. Synchronize SOCET for ArcGIS and ArcMap. (If the SOCET for ArcGIS toolbar is not
visible, right-click in the open space in the ArcMap toolbar. Select the SOCET for ArcGIS
toolbar from the drop-down list.) Left-click on Start SOCET for ArcGIS in the ArcMap
toolbar.
When SOCET for ArcGIS and ArcMap are linked, the icon display changes to allow you to unlink
SOCET for ArcGIS and ArcMap.
9. Edit in ArcMap and Select Task and Target. To start editing, from the ArcMap Editor
toolbar click on Editor > Start Editing. (The Task Selection window and Target Selection
window are available for use at this point.) Select a Task of Create New Feature, and select
a Target of BUILDING_A.
During extraction, the correct TASK and TARGET must be selected from these selection
windows in order to ensure the correct feature is generated. It is a common error during extraction
to neglect to change the task to Create New Feature or to select the desired target such as
BUILDING_A when attempting to extract a new building. If you are attempting to extract a
feature and an entirely different feature appears during extraction, this is one of the first
conditions you should check your settings in.

10. Select the SOCET for ArcGIS collection tool. In this step, explore by extracting a building
using the Static tool first, and then the Square after accept tool to see how some of the
different collection tools work. From the SOCET for ArcGIS window, left-click and hold
the collection tools on the drop-down list.
Static collection tool – Draw an object by sampling sequential vertices. Each vertex is connected
to the previous vertex with straight line segments.
Square after accept – Draw an object by sampling sequential vertices. Upon feature accept, all the
connecting segments shall be forced to be perpendicular.
11. Coordinate Measurement Tool and Move to Point. In the scenario to extract a building,
continue with the Move to Point feature of the Coordinate Measurement tool to reach the
selected building.
a. From the main SOCET SET window, select Tools > Coordinate Measurement. Use
the coordinate measurement tool to move a specific point or to measure between
points.
b. From the Coordinate Measurement window, select Options > Move to Point.
c. In the Move to Point window. Type in the following coordinates, and then select the
Move to Point button:
Longitude: -117:14:19.315
Latitude: +32:42:05.183
Elevation: 6.893
This moves your cursor to the first building selected for extraction as an Area Building or
BUILDING_A.
d. Get the height, length, slope%, and other measurements using the coordinate
measurement tool by selecting Reset to drop a marker (the tool measures from the
marker to wherever you move the cursor). It is a dynamic measurement; meaning
measurements change as the cursor is moved. To drop a new marker, select the Reset
button.

12. Collect an area building using the Static collection tool. (As a review, the following should
be done – editing mode in ArcMap, ArcMap task is set to Create New Feature, ArcMap task
is set to BUILDING_A, and SOCET for ArcGIS collection tool is set to Static.)
a. Point 1: Place a vertex at the NE corner of the building with the cursor at the elevation
of roofline. How you place a vertex depends on your mouse type and personal settings.
Note that the line work does not appear until the feature is complete and populated in
the ESRI database.
b. Point 2: Move the cursor to the NW corner and place a vertex at the level of the
roofline.
c. Point 3: Move the cursor to the SW corner of the building and drop the third vertex.

d. Point 4: Move the cursor to the SE corner of the building and place the fourth and final
vertex of the feature.
e. After placing the last vertex, either double-click or select Accept Feature button from
the right-click menu. This automatically closes the feature, and the feature will
populate in both SOCET SET and in the ESRI database.

13. Collecting and area building using the Square after accept tool. Select the Square after
accept icon from the Collection tools drop-down list.
a. Point 1: Place a vertex at the NE corner of the building with the cursor at the elevation
of the roofline. How you place a vertex depends on your mouse type and personal
settings. Note that the line work does not appear until the feature is complete and
populated in the ESRI database.
b. Point 2: Move the cursor to the NW corner and place a vertex at the level of the
roofline.
c. Point 3: Move the cursor to the SW corner of the building and drop the third vertex.

d. Point 4: Move the cursor to the SE corner of the building and place the fourth and final
vertex of the feature.
e. After placing the last vertex, either double-click or select Accept Feature button from
the right-click menu. This automatically closes the feature, and the feature
automatically squares itself – which may cause a slight shift.

19.3.2 Editing with SOCET SET sketch tools

1. From SOCET SET's pull-down menu select Extraction > SOCET for ArcGIS.
2. If the SOCET for ArcGIS toolbar is not showing in ArcMap select it by right clicking on
the toolbar area.
3. Load the map or add layers that you want to work with in ArcMap.
4. Click (Start SOCET for ArcGIS) in ArcMap.
5. Choose Start Editing from ArcMap's editor toolbar.
6. Select the target layer that you want to extract in ArcMap.
7. Choose the appropriate sketch tool.
8. Make the SOCET SET viewport active and toggle in to begin extraction.
9. When you are done, select Stop Editing from ArcMap's editor toolbar.
10. Save your edits and click (Stop SOCET for ArcGIS in ArcMap).
19.3.3 Editing with ArcMap tools

1. From SOCET SET's pull-down menu select Extraction > SOCET for ArcGIS.
2. If the SOCET for ArcGIS toolbar is not showing in ArcMap select it by right-clicking on
the toolbar area.
3. Load the map or add layers that you want to work with in ArcMap.
4. Click (Start SOCET for ArcGIS) in ArcMap.
5. Click ArcMap Tools On/Off on the SOCET for ArcGIS toolbar, so that all of the sketch
tool buttons become disabled.
6. Choose Start Editing tool button from ArcMap's editor toolbar.
7. Select the target layer that you want to extract in ArcMap.
8. Choose the appropriate ArcMap tool.
9. Make the SOCET SET viewport active and toggle in to begin extraction.
10. Double-clicking will accept a feature and right-clicking will bring up the ArcMap context
menu. When right clicking, toggle off the extraction cursor, and then select the appropriate
menu choice. When finished, toggle on the extraction cursor.
11. When you are done, select Stop Editing tool button from ArcMap's editor toolbar.
12. Save your edits and click the (Stop SOCET for ArcGIS) in ArcMap.
19.4 Tips and Tricks

1. To increase performance while loading graphics, set the stereo viewport’s graphics mode
to limited. This will only draw features that can be seen within the current boundary of the
viewport. When set to full, any refreshing of the graphics will redraw every feature loaded
in ArcMap.
2. In order to quickly drive to a feature in the stereo viewport from the ArcMap canvas use the
synchronize cursor functionality. Map an accelerator key in ArcMap to the synchronize
cursor function. Toggle on ArcMap tools, press the accelerator key, and move to the feature
of interest in the ArcMap canvas. The stereo viewport will automatically drive to the
imagery as the cursor moves. Once you have reached the area of interest, press the
accelerator key again, to turn off tracking, and switch back to the stereo viewport to edit
the feature.

3. In order to learn more about any SOCET for ArcGIS preferences, press the “what’s this”
tool (‘?’), and click on any preference.
19.5 Troubleshooting
Problem: I can't see the 'SOCET for ArcGIS' toolbar when I right-click in the ArcMap toolbar.
Fix: Make sure the components are registered. In a command window, go to the lib directory of
your SOCET SET installation and run the following commands:
regsvr32 Socet_ArcMap_Marshalling.dll
regsvr32 SAM.dll
regsvr32 SAMps.dll
From the bin directory type:
socet_arcmap.exe /RegServer
Alternately you could right click on the toolbar area in ArcMap and choose Customize.... Click
on Add from file..., and select SAM.dll from the lib directory of your SOCET SET installation
folder.
Problem: The system seems unresponsive after pressing Refresh Graphics in the SOCET SET
viewport.
Fix: If there are a lot of features you can either turn off that layer in ArcMap, or zoom in to 1:1
on the SOCET SETviewport. The delay is in the drawing of the features in the viewport.
Problem: When I change the symbology of a layer in ArcMap, I do not see the changes in the
SOCET SET viewport.
Fix: Refresh the graphics in the viewport.
Problem: After accepting a feature created using SOCET Sketch Curve tool, the feature is not
inserted into ArcMap. You can observe this by pressing Refresh Graphics in the SOCET SET
viewport and the feature is gone.
Fix: Features created using SOCET Sketch Curve tool are densified before they are sent into
ArcMap. The densification may generate illegal tiny segments when the features have abrupt
turns during the Curve creation. The work-around is to avoid abrupt turns. For abrupt turns, you
must use the Static tool instead.
Problem: I have a layer in ArcMap with all zero elevation and I cannot edit them using SOCET
Sketch tool.
Fix: You export the layer into 3D Shapefile and then import the 3D shapefile into SOCET SET
feature database. You then use the batch_fdb batch command to compute the elevations for all
vertices. After that, you export the SOCET SET feature database back to 3D Shapefile and import
it to the ArcMap data layer.
Problem: I get an error when trying to connect of “Alt.Advise failed with error - 2147023174”.
Cause: One of the applications was restarted since an initial connection was made. This causes it
to lose the connection point. This is a known COM issue.
Fix: Quit both applications and start SOCET for ArcGIS again. This will bring up ArcMap also.
Once one application is exited the other should be exited also.

Chapter 20
Visual Coverage Tool

The Visual Coverage Tool allows you to graphically manage
and see the expanse of your image data .
20.1 Overview
The Visual Coverage Tool (VCT) provides the capability to graphically manage and view
coverage of the image data. Specifically, VCT shows coverage of and manages ARC-Digitized
Raster Graphics (ADRG), Compressed ARC-Digitized Raster Graphics (CADRG), Controlled
Image Base (CIB), Digital Terrain Elevation Data (DTED), Digital Point Positioning Database
(DPPDB), and Vector Product Format (VPF) data. VCT additionally displays coverage of TFRD
images, NITF 2.0 and 2.1 images with degree coordinates in the IGEOLO field, GeoTIFF images,
support (.sup) files, and shapefile vector files.
You can use VCT to import NITF 2.0 and 2.1, TFRD, DPPDB, and DTED data into a new or
existing project. You can also use VCT to run triangulation on imported images and create
mosaics.
In order to run VCT, you must have the Java Run Time Environment (JRE) installed on your
system.
The JRE is installed with SOCET SET. If you want to use a different version of the JRE, use the
SOCET SET Configuration Editor to set the JRE value to the full path to the JRE executables.
You can start the Configuration Editor from the SOCET SET main menu by selecting Tools >
Configuration Editor.
SOCET SET Page 20-1

Chapter 20 - Visual Coverage Tool
20.2 Getting Started

Start the VCT through SOCET SET main menu, Preparation->Import->Visual Coverage Tool. If
the VCT data directories have not yet been configured, this brings up a window showing a raster
map and no data coverage.
vct_VisualCoverageToolA GUI
After configuring the background and coverage directories and turning on some coverage layers,
the VCT application window will resemble the figure below.
vct_VisualCoverageToolB GUI
Below the VCT main menu bar are three toolbars that control the coverage displays.
• The top toolbar is the background toolbar. This toolbar allows you to switch between
backgrounds and indicates the current background.
Page 20-2 SOCET SET

• The second toolbar is the foreground toolbar. This toolbar allows the turning on and off
layers of image footprints and indicates which layers are currently visible.
• The third toolbar controls the center and zoom of the displays and provides a button to
export selected images to SOCET SET.
Below the toolbars are the three VCT displays: the nonpolar display (left), the north polar display
(middle), and the south polar display (right). The nonpolar display is used primarily for showing
coverage footprints between 80 degrees south and 80 degrees north latitude. The north and south
polar displays are used for showing coverage outside this region. Below the polar displays is the
selection information panel. This displays information about selected items such as image
metadata.
20.3 Basic Functions

The following sections are basic VCT functions without getting into the details of coverage or
background data types. If using a new installation of VCT without any data directories
configured, you may skip ahead to the Data Managers section to configure at least one data type.
This will allow experimentation with all of the basic functions.
20.3.1 Setting the Active Display

Most VCT controls apply only to the active display. There is only one active display, at any given
time. A display is active by the existence of a thin red border will be around it. To change the
active display, click on the display desired to make it active.
20.3.2 Cursor Tracking

The location of the mouse cursor is displayed at the lower-left of the VCT application window
when it is over any of the three coverage displays. The latitude and longitude are displayed on the
left and the pixel location is displayed on the right. This feature is not affected by the active
display setting; the cursor location is displayed no matter which coverage display is active.
20.3.3 Roaming
The center control fields in the third toolbar indicate the geographic center of the active display.
To re-center the active display, enter new values in these fields. While the center coordinates are
always displayed in DD(D):MM:SS.s[N|S|E|W] format, new center coordinates can be
displayed in different degree formats including [+/-]D.d… and
DD(D)MMSS.s…[N|S|E|W]. Enter the new latitude and/or longitude and press enter to apply
the new center. If the value in a field has been changed but has not yet applied it, press the <Esc>
key to restore the last value. You can re-center the active display by moving the mouse cursor to
SOCET SET Page 20-3

the desired location and click RMB. The background will shift so that the point under the mouse
cursor becomes the new center
The center values of both the nonpolar and polar raster map
backgrounds are limited based on the current zoom setting.
For example, the center latitude of the nonpolar raster world
map is always 0 degrees when the zoom setting is 100% and is
limited to values between 45 degrees south and 45 degrees
north when the zoom setting is 200%.
20.3.4 Zooming
The zoom control field is in the third toolbar, just to the right of the center control fields. It
indicates the zoom setting of the active display.
Change the zoom of the active display by entering a new percentage value in this field. Apply the
change by pressing enter. To abort changes before applying it, press <Esc> on the keyboard. To
the right of the zoom control field, are four magnifying glass buttons. The following explains each
choice:
• The minus sign in the magnifying glass is zoom out button. Clicking this button halves
the zoom setting of the active display. If the smart zoom feature is enabled and the
current background is any type of CADRG, clicking this button may change the
background to another type of CADRG or to the raster world map in order to best
provide the resolution needed.
• The plus sign in the magnifying glass, is the zoom in button. Clicking this button
doubles the zoom setting of the active display. If the smart zoom feature is enabled and
the current background is the raster world map or any type of CADRG, clicking this
button may change the background to a type of CADRG that best provides the
resolution needed.
• The text “IQ” under the magnifying glass, is the smart zoom button. Clicking this will
turn off/on the smart zoom feature. This feature affects the operation of the zoom in,
zoom out, and zoom-to-box, and background change functions. This feature does not
affect changing the zoom setting by entering a new percentage in the zoom control
field. The button indicates the enabled state of the feature. The smart zoom feature is
enabled when the button is shown with a darkened background and disabled when
shown with the normal background.
• The blue rectangle around the zoom in magnifying glass, is the zoom-to-box mode
button. Click this button to change the mouse mode to zoom-to-box mode. To indicate
button selection, the button’s background will darken. While in this mode, zoom in on
Page 20-4 SOCET SET

a specific region of the active display by dragging a rectangle around the region of
interest with the LMB. When the button is released, VCT will re-center and adjust the
zoom to show the region selected. The mouse mode will automatically switch back to
selection mode. As with the zoom in function, this may change the background if the
current background is the raster world map or any type of CADRG.
• The MMB allows you to use the zoom in functions more efficiently. To re-center and zoom in,
move the mouse cursor to the location of interest and click MMB. To zoom-to-box without ever
leaving selection mode, drag a rectangle around a region of interest with MMB.
Different backgrounds have different minimum and maximum

zoom settings. This will affect whether the zoom buttons are
on or off.
20.3.5 Changing the Background

Change the background of the active display using the background toolbar. The background
toolbar contains a button for each available background subtype for the active display. The
buttons are grouped by type. The button representing the current background is highlighted in
white.
If the background is changed while the smart zoom feature is on, VCT will choose a zoom setting
for the new background in an attempt to retain the resolution provided by the last background and
zoom setting. If the smart zoom feature is not on, VCT will set the zoom of the new background
to 100%.
In the Background Toolbar above, VCT indicates that the current background is the raster world
map and that the other available backgrounds include three types of CADRG data, two types of
CIB data, and rendered VPF data. This, however, does not mean that each of these background
types is available for all regions of interest. It means that there is at least some region of interest
that can use these backgrounds. If attempting to change the background to a type for which there
is no data at the current center of the view, VCT will provide a warning and allow either to
continue or cancel.
Buttons in the toolbar representing background data subtypes

are often abbreviated. To get the full name of the subtype
represented by a button, move the mouse cursor over the
button and wait a moment. The full name of the subtype will be
displayed as a tool tip.
SOCET SET Page 20-5

20.3.6 Showing Coverage Layers

Control the visibility of coverage layers using the foreground toolbar. The foreground toolbar
contains a button for each available coverage subtype. The buttons are grouped by type. The
buttons representing coverage layers that are currently shown are highlighted with the color in
which items of that layer are drawn. Click a button to toggle the display of a coverage layer.
Unlike the background toolbar, the foreground toolbar applies to all three displays. It is not
affected by the active display setting.
In the Foreground Toolbar above, VCT indicates that is has layers of CADRG, ADRG, CIB,
DTED, VPF, and Images available for display. It also indicates that it is now displaying CADRG
Jet Navigation Chart data in peach, CADRG data on CDROM in bright green, VPF Digital
Nautical Chart data in orange, cataloged VPF data in aqua, visible imagery in lime green, and
shapefiles in blue. As with the background toolbar, the existence of a button does not necessarily
mean that there is data for the corresponding layer in the current region of interest. Turning on a
coverage layer but do not see any footprints, zoom out or change to a less detailed background
such as the raster world map.
Buttons in the toolbar representing coverage layers are often

abbreviated. To get the full name of a coverage layer, move the
mouse cursor over the button and wait a moment. The full
name of the subtype will be displayed as a tool tip.
20.3.7 Selecting Data Items

Use the mouse to select one or more data items while in Selection Mode. Selection mode is on
when the menu button button is darkened. Select data items by clicking the LMB over the desired
items or by dragging a rectangle. Hold the <Ctrl> key down when selecting to add to the current
selections. From the selection choice dialog, select the desired item(s) from the list and click OK
to confirm the selection.
For selection choice dialog to appear, user options must

comply.
Page 20-6 SOCET SET

If the selection zone contains more than one data item, a prompt will ask to choose which of those
items to select. This behavior is configured through the selection options dialog. The selection
choice dialog is shown below in the following panel.
If prompted with the selection choice dialog, select the desired item(s) from the list and click OK
to confirm the selection. To select multiple non-contiguous items in the list, hold the <Ctrl> key
down while clicking to select or deselect items individually. To select a range of items, first click
the item at the start of the range and then hold down the <Shift> key and click the last item in the
range. Click Select All to quickly select all items. Click Cancel to abort the selection process.
Information about the selected data items is displayed in the selection information panel under
the polar displays. If only one item of a given type is selected, detailed information for that item
is displayed. If more than one item of a given type is selected, only the type, subtype, and quantity
of those items is displayed.
20.3.8 Exporting Selected Items

Transfer selected items to SOCET SET using the export function. To do this, first select the
item(s) desired in VCT. Then, click either Export SOCET SET or select Export > to SOCET
SET.
After you do this, you will be prompted with a dialog titled “Export to SOCET SET”. Set the
desired export options. Then click Start to run the export process. Or click Close to abort the
export process
SOCET SET Page 20-7

The Exporting Selected Items window’s selections are as follows:
SELECT TO
Select SOCET SET Project Select an existing project or enter a new project name.
Select MC&G Files Select an external support file to be used for all TFRDand NTM images.
Select Scratch Directory Select a location for temporary files and imported images.
Start Export the selected images to SOCET SET.
Close Close this dialog.
20.3.9 Options
The Options menu on the menu bar provides access to Select Options, Administration Options
and the ability to enable or disable the display of a center crosshair.
20.3.9.1 Selection Options

The details of how selection takes place are configured in the Selection Options dialog accessed
by clicking Options > Selection… from the menu. Using the LMB, select an item if the point is
within the boundary of the item or only if the point is on the boundary of the item. The latter
option provides more control when there are overlapping items. LMB click selection can also be
configured so that when more than one item is a candidate for selection that only the top item is
selected, all items are selected, or prompted to choose. Rubber-band selection is also configured
Page 20-8 SOCET SET

so that when more than one item is a candidate for selection, all items are selected or prompted
to choose which to select. After making changes, click OK to apply the changes or Cancel to close
the dialog without saving changes.
20.3.9.2 Administration Options

The saved state of the VCT is divided into two categories: user-preference settings and system-
related settings. The user preference settings include things like the current background and
which coverage layers are displayed. System-related settings include things like the data
directories. Administration options are provided for optionally coordinate sharing of the system-
related settings.
Bring up the Administration Options dialog by clicking Options > Administration… from the
menu. To share the system-related settings, set the system related state storage location to be the
VCT application directory. To keep individually owned system-related settings, set the storage
location to be your home directory.
The Enable administrative functions check-box above the system-related state storage location
controls whether to enable changes of the system-related settings. Uncheck this to prevent from
inadvertently modifying shared system-related settings. If this box is unchecked, and the storage
location for system-related settings is the home directory, the storage location will be
automatically changed to the VCT application directory. This is because there is no practical use
for disabling updates to system-related settings when they are stored in anyone’s home directory.
After making changes, click OK to apply the changes or Cancel to close the dialog without saving
changes.
SOCET SET Page 20-9

20.3.9.3 Startup Options

There are two startup options that can be used to improve the startup performance of VCT. The
first option, Initialization Order, allows you to choose the order in which VCT’s footprint
databases are initialized. The Initialization Order dialog is accessed by clicking Options >
Startup> Initialization Order.... Move the data sources you are most likely to use in a given
session to the top of this list. To change a data source’s initialization priority, select it and move
it up or down in the list with the arrow buttons.
The second option, Faster Startup, allows you to bypass the usual scan for new data that is done
by some data sources on VCT startup. That option is toggled by clicking Options > Startup >
Faster Startup. Currently, this only affects the databases of the DTED Data Manager and Image
Coverage Window. When this option is enabled, you must refresh those databases manually using
their respective windows to discover new or removed data. This option is useful when your data
set is slow to change.
20.3.9.4 Show Crosshair

The Options > Show Crosshair check-box from the menu toggles the display of a crosshair at the
center of the active display. This may aid you in determining graphically where the center of the
display is that corresponds to the latitude and longitude displayed in the center control fields of
the third toolbar.
20.4 Data Managers

All data types displayed in VCT are managed using Data Managers for each data type. The source
for each type can be a CD, DVD, or tape; and the destination is where VCT can store data on a
hard disk. The VCT Data Managers all follow approximately the same paradigm. There is a
source from which to load offline data, and a destination for where to load the data. Data loaded
at the destination path is considered online data by VCT and the data under the destination paths
populate the foreground toolbar. Bring up any VCT data manager by clicking File > VCT Data
Manager from the menu.
20.4.1 Setting Data Directories

All Data Managers follow the same steps to select Source and Destination locations.

Using the CADRG Data Manager as an example, the first step is to select the “Browse” button in
the “Source” section. The “Set CDROM Path” window appears. Navigate the directory structure
to set the path that contains “rpf” subdirectory. Usually this is /cdrom/cdrom0. Click Select
once the path is set.
To set the Destination location or to view data that is already on-line:

• Press the Browse button.
• From the destination side of the Data Manager, select a location to place the data, from
the Set Disk Path.
• Press Select.
Once a directory for a data type is set, the directory is scanned and the corresponding icons for
the data are displayed in the foreground line in the VCT. Toggle each icon on or off to see
footprints of the available data. If a CDROM is scanned, a CDROM icon is displayed next to
under the header for the data type it contains. The CDROM icon and its data footprints are bright
green.
Below the Browse button, the amount of available disk space for the selected directory is
displayed.
20.4.2 Sorting Table Items

Any column a Data Manager or Image Coverage table can be selected for sorting in ascending or
descending order. To sort in ascending order, move the cursor over the label and click LBM. A
sorted direction indicator appears >. To sort in descending order, move the cursor over the label
and press the <Shift> + LMB. The opposite <, direction indicator appears. The sorting is stable
so that sorting by multiple columns will result in the last sorting being the primary sort criteria
and the previous sorting being the secondary criteria.
20.4.3 Selecting Table Items

Selected data items may be copied or deleted by highlighting either the footprints or the data
items listed in the Data Manager. Select footprints with either a LBM on the footprint or by
clicking and dragging the LMB over an area to select numerous footprints. Also, pressing the
<Ctrl> key will allow for the individual selection of multiple tiles. The selected tiles will be
highlighted on the display as well as in the Data Manager list.
Under the Disk Selected area, the disk space required for the currently selected data is displayed.

To Select items in the Data Manager, use a LMB click to select one item. Use <Ctrl> + LMB to
select multiple non-contiguous items or <Shift> + LMB to select multiple contiguous items.
Explain that the amount selected is displayed above the table on the left. Explain selection in the
table and how it is tied to what’s in VCTs displays. However, the item will not be seen if the layer
containing that item is not visible.
Visibility of the selected item information in the selected item information panel on the right as
if the selected item is in VCT.
Selecting in VCT will also select items in the table. This allows
you to graphically manage your data.
20.4.4 Copying and Cataloging Data

To copy tiles from CD to disk, highlight the desired tiles and click the Copy button. To catalog
tiles from CD to disk, highlight the desired tiles and click the Catalog button. At anytime the
Cancel button can be pressed to stop the process. However, any data already transferred, will
remain in the Destination location.
The Overwrite check-box ensures that all data is copied from the source to the destination. Use
this option when existing data at the destination is corrupt or out-of-date.
Some data managers provide the ability to catalog offline data. Cataloging helps manage an
existing collection of data without keeping all the data online. Cataloged data of a given type is
shown in the foreground toolbar with a button labeled CAT. Cataloging data only copies limited
metadata to be able to provide footprints while conserving disk space. In data managers that
support cataloging, fully copied data items have a check in the Online column of the table in the
destination panel. Cataloged items do not have a check in that column.
Some data managers provide the ability to copy from the current destination to another disk
directory. This is useful for consolidating databases. To use this function, select one or more
items in the table of the destination panel and click the Disk to Disk Copy button. A prompt with
a dialog to choose the secondary destination path will display. Choose the secondary destination
path and whether to overwrite existing files. There will also be an option to catalog the data or
perform a full copy of the data if the data manager supports cataloging. After selecting the
options, click OK to start the copy process.
20.4.5 Deleting Online Data

To delete items, select the tiles and press the Delete button in the Data Manager. Once selected,
confirmation of deletion of the data is asked and the amount of disk space freed is reported. For
data managers that support cataloging, deleting catalog entries is possible.
20.4.6 Specifics
While the data managers work the same for the most part, there are some details that vary between
data managers. The following subsections discuss these differences.
20.4.6.1 CADRG Data Manager

The VCT displays the footprint of Compressed ARC Digitized Raster Graphics (CADRG) data.
Select File > CADRG Data Manager from the menu.

The CADRG Data Manager is divided up into a Source and Destination section as shown below.
20.4.6.2 ADRG Data Manager

The ADRG Data Manager provides for the ability to manage data from ADRG CDROM
distributions. Because of the large size of ADRG images (100 – 500 MB) the ADRG Data
Manager provides a function to catalog the data from the CDROM. This will allow the managing
of a shelf full of ADRG data using only a small amount of disk space.
The source panel, in addition to the CDROM path and amount of data selected, displays the
volume identification and classification of current ADRG CDROM.
ADRG images in the source panel are detailed by map scale (e.g. TL for Topographic Line Map
1:50k), upper-left corner in ground space, image size, and file pathname. ADRG images in the
destination panel are detailed by all fields previously mentioned plus the online status of the
image, the ADRG stock number (volume identification), and the edition number.
20.4.6.3 ASRP Data Manager

The ASRP Data Manager provides similar functionality to the ADRG Data Manager. Select File
> ASRP Data Manager....

20.4.6.4 CIB Data Manager

The VCT displays the footprint of Controlled Image Base (CIB) data.
Select File > CIB Data Manager from the menu.
20.4.6.5 DTED Data Manager

The VCT displays the footprint of Digital Terrain Elevation Data (DTED) data. Select File >
DTED Data Manager from the menu.
The DTED Data Manager is displayed with Source location listed on the left and Destination on
the right.
Source and Destination locations are determined by clicking Browse and defining a path to the
DTED data. Additionally, there is an Eject CD button to open the CD-ROM drive.
Once source and destination locations are determined, available data in these locations is
displayed in the VCT main window.
20.4.6.6 DPPDB Data Manager

Digital Point Positioning Database (DPPDB) is stored on 8mm tape or DVD. Since DPPDB data
is classified, you will need DataThruWay® installed in order to export the images to
SOCET SET. To start the DPPDB Data Manager, select File > DPPDB Data Manager from the
menu.
The Data Manager identifies the DPPDB Source Location and Destination directory plus
available disk space. To initially load images from tape or DVD, click Browse. The Select
DPPDB Device window appears. Select either tape or DVD as a device. Once selected the Device
Parameter is displayed, the parameter can be manually changed. Once complete, click OK. The
device is scanned, and the data is presented in the Source Area table. The DPPDB OFF icon is
visible on the VCT foreground line,which is an indication that DPPDB data is off-line on the tape
or DVD.

When loading from a tape, the first file on the tape is copied into a temporary location and read
in as the master product file. If the product ID and version number on the tape is not one of the
known products, then a directory is created and the Master Product File, CADRG tiles, and
images on the tape are copied off and into the DPPDB data directory.
When loading from a DVD, in the main directory, there will be a directory named D12345678,
which is the product ID. Under that directory, the master product file is named
D12345678_mpf.ntf, the images are named 1234LF.NTF, and the CADRG are named
cadrg_0002.ntf. This assumes that each DVD has only one product on it.
A DPPDB tape contains several files. The Master Product File (MPF) contains general
information about the DPPDB product and is written out as D12345678_mpf.ntf.
The CADRG Frame file stores the image segment footprints on a reference image. The image
segment files are the overview and full resolution DPPDB image in stereo pairs in NITF JPEG
compressed format. The full resolution DPPDB images are written as D12345678_0101LF.ntf.
All data is written to the D12345678 named subdirectory. This name is the tape or DVD
identification number.
The DPPDB Data Manager looks at each subdirectory directly under DPPDB data and loads the
first file matching “*_mpf.ntf” as the master product file. It then loads the product ID and version
from the master file along with the image information. If the master file fails to load, or is
missing, the directory is not included in the list.
Choose to delete images or products through the DPPDB Data Manager. Once images or products
have been unloaded, a DPPDB OFF icon appears on the VCT foreground line, indicating this
tape/DVD had previously been installed and the data has been removed. When loading or
unloading data, disk space required or acquired is reported in the Data Manager Window.
Additional Items in the DPPDB Manager window:
• Catalog: Read the DPPDB master product file without transferring any images. Allows
for VCT to see the items on the tape or DVD without having to use disk space to store
images.
• Overwrite: Write over any existing data of the same area.
• RSets: Generate Reduced Resolution Data Sets when the images are transferred from
tape or DVD.
20.4.6.7 VPF Data Manager

The VPF Data Manager displays the Vector Product Format (VPF) tiles. Select File > VPF Data
Manager from the menu.

The VPF Data Manager is displayed with Source location listed on the left and Destination on the
right.
20.4.6.8 Image Coverage Module

The Image Coverage provides a subset of the capabilities of the data managers for tracking
coverage of images that are not distributed in any standard way. These include NITF 2.0 and 2.1
images, TFRD images, GeoTIFF images, and shapefile vector files. While shapefiles are not
images, they are similar in that they have geographic footprints and they are not distributed in
standard packages. Note that this module will also detect CADRG, CIB, and DPPDB files
because they are all NITF. However, an appropriate data manager for these data types to see the
most information is recommended.
Select File > Image Coverage… from the menu to show the Image Coverage window.
The Image Coverage window, unlike the data managers, allows for specifying multiple coverage
directories. To add a directory to the list, click Add Directory. The file selector window appears
allowing the navigation to the desired directory. To delete a selected directory, highlight the
directory and click Remove Directory.
For each directory, the files are displayed in the table with their corresponding latitude, longitude,
image type, file size and file name. Each directory is recursively searched down through
subdirectories for valid image files. A recognized NITF image file is one that start with “NITF2.”
in the header, and has valid IGEOLO data in one of the images contained in the NITF file. If there
are multiple images with IGEOLO, the first image footprint is displayed. RSets are not shown in
the VCT.
Each column may be sorted in ascending or descending order. To sort a column in ascending
order, LMB click the label or <Shift> + LMB click to sort in descending order. Once the
directories have chosen, close the NITF Coverage window.
To copy the full pathnames of the selected items to the clipboard for transferring to another
application from the Image Coverage window, do the following:

1. Select the desired items.

2. Copy the pathnames to the clipboard pressing <Ctrl>C on the keyboard.
An icon appears on the foreground line of the VCT window, in the Images Grouping. VCT will
attempt to catalog images based on the entry in the ICAT field of the image header. The following
table shows the currently available ICAT options:
DISPLAYED CATEGORY ACTUAL CATEGORY
BP Black/White Photography
CP Color Frame Photography
EO Electro-Optical
FL Forward-Looking Infrared
HR High-Resolution Radar
HS Hyperspectral
OP Optical
RD Radar
SAR Synthetic Aperture Radar
SL Side-Looking Radar
TI Thermal Infrared
VIS Visible Imagery
SARIQ SAR Radio Hologram
IR Infrared
MS Multispectral
VD Video
MAP Raster Map
DTEM Matrix Data (elevations)
MATR Matrix Data (other)
LOCG Location Grid
GH-VIS GlobalHawk Visible Imagery
GH-EO GlobalHawk Electro-Optical
GH-IR GlobalHawk Infrared
GH-SAR GlobalHawk Synthetic Aperture Radar
TIFF GeoTIFF Images
SHP Shapefiles
20.5 Reference Backgrounds

Toggle the desired background data type as foreground first to be sure there is data available.
Zoom in and recenter the screen around the foreground footprints until the foreground data is in
the center of the screen. The world map background displayed at 100% zoom factor only recenters
in the horizontal direction. The mercator world map does not wrap around in a vertical direction.
20.5.1 Raster World Map Background

The VCT default background is the Raster World Map. The raster world map background has no
configuration options.
When zooming in on the world map, the resolution is not sufficient beyond 500%. Zoom settings
beyond 500% show pixilization of the image. The maximum zoom setting for the world map
background is 409600%. Zooming to very high percentages aids in viewing footprints of small
NITF image files or other data types.
If the world background is displayed at 100% zoom, recentering the background is only active in
the horizontal direction. The mercator world map does not wrap around in a vertical direction.
The latitude stays fixed at 00:00:00.0N. To recenter on a specific latitude and longitude, use the
zoom to box function to enable vertical roaming.

20.5.2 CADRG Background

To use the CADRG reference background:
• Configure the CADRG background data path.
• Click File > CADRG Background > Set Data Path… to display a dialog for setting the
path to CADRG data. The CADRG background data need not be loaded on the system,
it can reside on a CDROM.
• After you choose the desired directory, click Select to apply the directory.
If there is any data, buttons will appear in the background toolbar under a CADRG heading
indicating the subtypes CADRG data that were found.
Once the background directory is set, icons appear for all available background types.
CADRG or CIB data can optionally be used as backgrounds. It may be convenient to select the
same directory as the coverage directory, however this is not required. CADRG and CIB
background data may reside on hard disk or on CDROM. Of course, access will be faster if the
data is loaded on the hard disk. To set a directory for VCT to find CADRG or CIB data, select
File > CADRG/CIB Background from the menu. When the file dialog box appears, set the
directory containing the CADRG or CIB images. Below is an example of using ONC map as a
background and displaying the footprints of CADRG, CIB and Image data. Each data type is
color-coded. The background data type is seamlessly mosaicked to provide continuous coverage
when available. Black background indicates no coverage of that data type.
The CADRG background data can be displayed using the grayscale lookup table rather than the
color lookup table. All CADRG data is encoded with both color lookup tables. Displaying
CADRG in grayscale may improve contrast with the overlaid image footprints. Toggle this
feature by clicking File > CADRG Background > Grayscale.

vct_VisualCoverageTool1 GUI
The maximum zoom setting allowed for CADRG and CIB backgrounds is to 3200%; the
minimum is 3.125%.
20.5.3 CIB Background

VCT allows the display of CIB data (grayscale imagery) for the background. The CIB background
is configured in the same way as the CADRG background. The CIB background works with 10-
meter, 5-meter, 2-meter, and 1-meter CIB data.
20.5.4 VPF Background

The VCT Vector Product Format (VPF) background can provide a high definition reference
background with a relatively small data set as compared with raster imagery. The VCT includes
the VMAP Level 0 reference library for a sample VPF background. This provides a vector world
map that is clear at much higher zoom settings than the Raster World Map background. The
figures on the following page show how the VPF background looks at 100% zoom (entire world)
and zoomed in, with CADRG ONC footprints rendered over the background. To use this
background, click the button labeled VPF on the background toolbar.
The maximum zoom setting allowed for the VPF background is 6553600%. This provides
adequate zoom in for very detailed VPF data such as VMAP Level 2. The minimum zoom setting
is 100% in which the whole world is displayed, regardless of VPF type.
The VPF background can be configured in a number of ways by clicking File > VPF Background
> Configure Themes.... First, configure the set of themes rendered. Second, change the rendering
background color. Last, enable or disable the Adjusting Aspect Ratio feature.
The second and third configuration options are relatively basic. To change the rendering
background color (initially blue to represent water), click File > VPF Background > Set

Background Color... A color selection dialog will pop up to select a new background rendering
color.
The adjusting aspect ratio feature can be enabled or disabled by clicking File > VPF Background
> Adjusting Aspect Ratio. When enabled, this feature will cause the VPF background to be
stretched to eliminate high distortion at far north and far south latitudes. The aspect ratio will be
correct at the center of the view.
Click File > VPF Background > Configure Themes… to configure rendering of VPF features.
This window also provides a legend to the data rendered in the background. This offers you a high
degree of flexibility. Additional VPF data is available if configuring the VPF background to use
additional themes. VPF data used for the background can be loaded from CDROM or disk.
CDROM access will be considerably slower.
20.5.4.1 Setting the VPF Data Directory

The File menu pulldown in the VPF Background theme configuration frame gives you several
options: load a session, save a session, set the VPF Path, or close. Additionally, up to five recently
used VPF session files (*.vs) will be listed in the File menu for easy loading. Only the filenames
are listed. To see the whole pathname, move the mouse cursor over the file of interest and wait a
moment. The full pathname of the file will be displayed for about two seconds as a tool tip.
A VPF session consists of a data directory and a set of theme definitions. Loading a session file,
therefore, will cause the data directory it indicates to be scanned.
20.5.4.2 Available Feature Tables Panel

After setting the VPF background data directory or after loading a VPF session, the left panel will
contain an unexpanded tree of available feature tables. VPF data is hierarchical, so the feature
tables are organized to reflect this. At the first level are the available VPF type(s), such as
VMAP0, VMAP1, DNC, etc. At the second level are VPF databases for those types. At the third

level are VPF libraries. At the fourth level are VPF coverages, and at the fifth level are the VPF
feature tables.
20.5.4.3 Current Themes Panel

A theme can be created from a feature table by highlighting the desired feature table in the feature
table tree and clicking the Add button in the center panel or by clicking Themes > Add Theme
menu item. A theme can also be added by simply double-clicking on the feature table item in the
tree. After doing this, a theme will be added to the panel on the right. For some feature tables,

more than one theme will be created. This is because not all features in those feature tables
possess the same feature code. A theme is created to address each feature code.
Once a theme has been added to the right panel, it can be removed by selecting it in the panel and
either clicking the Remove button in the center panel or by clicking the Themes > Remove Theme
from the menu.
Themes from different subtypes of VPF data may coexist,

provided that all feature tables for those themes reside under
the current data directory.
20.5.4.4 Editing Themes

The theme name and rendering style can be edited by selecting the theme and clicking Themes >
Edit Theme, or by double-clicking on the theme. The theme may be one of four types: area, line,
point, or text. Each of these theme types has different attributes that can be configured. See
figures below.
The feature table filename is listed at the top of each edit dialog. To see the entire pathname, move
the mouse cursor over the filename and wait a moment. The full filename will be displayed as a
tool tip.
When finished editing the theme click OK at the bottom or Cancel to abort changes. The theme
display will be updated to reflect any changes you made.
Changes will not be applied to the VCT background until you

click the Apply button in the center panel.


Chapter 21
Image Minification
Minification creates a “pyramid” of sub-images from full-
resolution images.
21.1 Overview
Minification creates an image pyramid from a digitized image. The image pyramid consists of a
series of smaller versions of the original image. The image pyramid permits you to see an
overview of the image and to zoom in and out of the original image.
The original image is called the 1:1, and the minified images are called the 2:1, 4:1, and so on.
Every image is created by averaging the four corresponding pixels of the previous image. In
essence, minification provides you with a very rapid zoom capability.
4:1 image
2:1 image
1:1 image
SOCET SET Page 21-1

Chapter 21 - Image Minification
21.1.1 When to Run Minification

You usually run minification:
• After an image is imported.
• After an image is rectified.
• After an orthophoto is generated.
• After an orthophoto is extracted from a mosaic, or after you have created any new
image file.
Many of the SOCET SET applications which create images will automatically generate an image
pyramid if you ask for it by setting the Auto Minify option, if one is available. In these cases, you
do not have to run Minification afterwards.
21.1.2 Image Location

Minification decides where to place the minification levels by first looking to see where the
lowest existing level is located. If this directory is in the location list in internal_dbs/
DEVICE, then the new levels will be placed there. If the directory is not in the list, the levels will
go into the location you select in the Output Imagery interface. If you want the minification levels
to go somewhere else, create a new entry in the Image Location database for the directory and run
Minification again.
21.1.2.1 Create Single File

If you enable Create Single File, Minification will place all of the minification levels into the 1:1
image disk file. This has the benefit of less clutter on your disks and will not adversely affect any
other operations. Currently the only output formats which support this are the TIFF formats, i.e.
any of the ones in the chart at the beginning of the Image Import and Export chapter which have
“TIFF” in their name. If your input image is not TIFF, it will be converted to the format you select
on the format pull-down before minifying. In this situation, you may want to remove the old 1:1
image after minification completes to save disk space.
If your image is TIFF, using the Create Single File capability

will permanently change the content of the input image file and
cannot be undone. Be sure that this is compatible with your
workflow before selecting this option.
If you have difficulty creating single file output, try selecting a

different output format.
Page 21-2 SOCET SET

21.2 Minification
The Minification window’s selections are as follows:
File > Load Project Loads a project.
File > Open Select Images.
File > Exit Exits Minification.
SELECT TO
Select Images List the images you wish to minify.
Add Select images by clicking RMB in the window.
SOCET SET Page 21-3

SELECT TO
Delete Remove highlighted images from the list by clicking RMB in the window.
View Info Right click for a window with more detail about the highlighted image by
clicking RMB in the window.
(Resampling Method) BLANK SPACE

Bilinear Toggle “On” for B i l i n e a r R e s a m p l i n g . See “Bilinear
BLANK SPACE Interpolation” on page G-2 for details.
Nearest Neighbor Toggle “On” for Nearest Neighbor resampling. See “Nearest Neighbor
Interpolation” on page G-1 for details.

Create a single file Click “On” if you wish to create a single output file which contains all of
BLANK SPACE the minification levels for the output image. If “On”, also select a format
BLANK SPACE for the output image. If the input images are not the same format as in the
format pull-down, Minification will reformat the images before minifying.
BLANK SPACE
BLANK SPACE
BLANK SPACE
Toggle “On” to place the minification levels into the same file directory as
Same place as original the 1:1 images.
image
BLANK SPACE
BLANK SPACE
BLANK SPACE
BLANK SPACE
Toggle “On” and select an Image Location with the Location button if you
Location want all the minification levels to go to a specific disk location other than
the location of the 1:1 images.
Start Begin minifying the images.
See “Start At Jobs” on page E-3
21.2.1 Execution - Minification
While running Minification, you cannot change the project. If

you need to execute the Minification function on another
project, you have two options:
1. Use the main menu to change to the desired project, then run the
function again;
2. Activate the function from a command line (in a shell window) by
starting the minifier executable with start_socet -single... as
described in the Batch Processing section.
1. Click Preparation > Minification on the main workstation window.

2. Click RMB in the Image selection area and click Add. Select the images you wish to minify
and click Open.
If you wish to delete any images in the list, select to highlight them, then click RMB then
select Delete.
3. [Optional] Check “Create a single file” if you want all of the output images to be in a single
file. Select a format for the single file.
4. [Optional] Select a single location for all the minification levels.
5. Click Start to begin minifying the images.
Page 21-4 SOCET SET


21.3 Batch Processing - Minification

COMMAND LINE:
% start_socet -single minifier -batch -s setting_file
minifier min
KEYWORD DESCRIPTION
project Full path and project filename (select from the .prj files in
resampling_method BILINEAR for bilinear resampling or NEAREST_NEIGHBOR for
nearest neighbor resampling.
input_sup Input support file name(s) (select from the .sup files in your project
directory). Repeat for every support file you want to minify. Use the full
path.
create_single_ [Optional] Set to “YES” to create a single output file which contains all of
file the minification levels for the output image. Default value is “NO”.
single_file_ [Optional] If create_single_file is set to “YES”, set this to the format you
format wish for the output image. See the table in the Image Import / Export
chapter for values. Currently only the TIFF types are supported. If any of
the input images do not match this format, they will be reformatted before
minifying.
location_method CO_LOCATE to locate minification levels with the 1:1 image or

SINGLE_LOCATION to locate them at the location specified in the
output_location value.
output_location [Optional] Name of the image location from the list in
internal_dbs/DEVICE/location.list when
location_method is SINGLE_LOCATION.
21.4 Next Step

To view the images in the pyramid, load the image onto one of the workstation monitors. Use the
Zoom option on the Display Utility window to set the minification level of the image to display.
SOCET SET Page 21-5

Chapter 22
Image Balancing: Dodger

Dodger performs radiometric balancing on one or more
images. This is called balancing or dodging.
22.1 Overview
Dodger can be run interactively with a GUI or as a batch command line program. Its input is one
or more images and its output are radiometrically corrected images. Dodger also has optional
input parameters which cause the output to conform to given radiometric specifications. Dodger
can be used to correct black and white or color imagery.
Dodger operates in two main phases.
• Phase I statistically characterizes each input image. During this phase the mean and
standard deviation of each “tile” of each input image is computed. The tile size is
computed automatically or it can be specified by the user. If multiple images are
input, dodger uses all the images to gather statistics, and accomplishes a more
uniform output for a large set of images or project. At the end of phase I, Dodger
has a table of statistics for each image.
• Phase II, Dodger applies the statistics tables to the images using a correction
function. The correction function is driven by the statistics tables and the desired
outcome.
Dodger corrects brightness and contrast imbalances due to:
• Hot spots - bright areas which are usually caused by the sun position with respect
to the imaging lens
• Vignetting - dark areas in the image corners due to light “fall-off” occurring radially
as a result of the imaging system
• Differences in scanner quality or scanner settings
• Differing film types
• Images acquired at different times of day or year
Dodger is a stand-alone program which can be executed on imagery of typical types such as TIFF
files. It can also be executed in conjunction with SOCET SET. In this case it supports the use of
SOCET SET “.sup” files or DSW “.dsup” files. When operating with .sup files, Dodger can save
its corrections without saving the entire image.
SOCET SET Page 22-1

Chapter 22 - Image Balancing: Dodger
22.1.1 When to Use Dodger

You can run dodger any time you want to radiometrically balance one or more images. For
example, operators often run dodger before building a mosaic. Normally, dodger is run on a group
of images that will be input into Mosaic, but if you are going to make multiple mosaics in a
project, you will get more uniform results if you run dodger on all images in the project (before
making any mosaic).
22.1.2 Data Flow For Dodger
UNBALANCED SUPPORT FILE(S) PARAMETER FILE

IMAGE(S) (optional) (optional)
DODGER
BALANCED SUPPORT FILE(S) REPORT FILE

IMAGE(S) (optional) (optional)
Page 22-2 SOCET SET

22.2 Image Dodge and Balance
The Image Dodger and Balance window’s selections are as follows:
File > Load Project... Prompts you to pick the name of the project.
File >Open Images... Opens the images.
File > Exit Exits the Dodger application.
Options > Auto Minify Automatically creates a minified image pyramid for each dodged image
after the dodge processing completes.
SOCET SET Page 22-3

SELECT TO
(Input Image Type) BLANK SPACE

Image Displays a pixel file with no support information. It can be any supported
BLANK SPACE type of image (see Image Import and Export chapter for a list of supported
BLANK SPACE image types) and each image can be a different type.
Support File Dodge *.sup files from your project.
BLANK SPACE NOTE: This option is available only when Dodger is started
from SOCET SET or with a project file.
BLANK SPACE
DSUP File The processing of DSW 300/200 Image Scanner dsup files.
(Input Images)
Add... Prompt you to select image files to be dodged.
NOTE: You can add more than one file at a time in the selection list.
Delete Remove images from the dodge list.
NOTE: You can pick and remove more than one file in the selection
list.
View Info...
Provide details about the selected image.
Statistics Compute Causes Dodger to output the statistics for the input images but does not
apply any correction to them. This is useful to help you see or understand
what your input image characteristics are. This can be used in setting goal
parameters discussed below.
Process Minification Level Allow you to select which minification level to process. You may want to
evaluate the result of dodging a set of images, but don’t want to wait for
the 1:1. You can select a lower minification level to see the results faster.
NOTE: Minification levels are only valid for Support and DSUP
images.
Parameter File... Specify parameter file which controls the dodge and balance process. It
BLANK SPACE can also be specified by the environment variable
BLANK SPACE DODGER_PARAM_FILE. The format of parameter file is documented.
See “Batch Processing - Dodger” on page 22-12 for details.
BLANK SPACE
BLANK SPACE
BLANK SPACE
Bring up the parameter editor window, which is described below.
Edit...
Toggle Have dodger generate a report when depressed, which is described below.
Report File Prompt you to select a report file or enter the name.
View... Display the report file.

Write Correction File Create dodger correction file that can be applied via image enhancements
BLANK SPACE in RT and in Mosaic.
BLANK SPACE NOTE: The filename for each correction file will be
BLANK SPACE <image_name>.dra and will be stored in the project directory.
Write to Pixel File Write dodged image to a pixel file.
Page 22-4 SOCET SET

SELECT TO

Location... Allow you to select where the dodged images will go.
BLANK SPACE NOTE: When dodging *.sup files the images will go to the specified
BLANK SPACE location but the corresponding sup file will go in the selected
BLANK SPACE project directory.
Format Enter the image format for the dodged image(s).
JPEG Quality Enter the JPEG quality for the output image.
Prefix Enter the prefix for the resulting dodged image(s).
Suffix Enter the suffix for the resulting dodged image(s).
Name Enter the output name will be composed of prefix, base name of the input
image, e.g., if the input image name is 1_13.sup the base name is 1_13,
suffix and then the extension appropriate for that output format. This field
allows you to preview what the resulting name will be.
NOTE: When dodging *.sup or *.dsup files the support file for the
resulting dodged image will have the same name as the image but
the .sup file extension.
Start Start the dodge process.
See “Start At Jobs” on page E-3
SOCET SET Page 22-5

22.2.1 Dodger Parameters

You can, optionally, input a parameter file to Dodger. To open this window, click Edit... in the
Parameter File area on the Image Dodge and Balance window. The parameter file contains
parameters which tell dodger how to balance the images. If you do not input a parameter file,
Dodger will balance the images using default parameter values.
The Dodger Parameters window’s selections are as follows:
SELECT TO
Parameter File Select a parameter file which controls the dodge and balance process.
Color Match Enable color matching mode of Dodger.
Target Colors Number of colors that will be used to drive the output colors.
• This is the number of colors that will be used to drive the
output colors.
• This is not the number of colors in the output image - it is the
number of color regions.
Intensity Establish the intensity of the dodger images. If set to 0.0, the average
intensity of the input images will be used.
Page 22-6 SOCET SET

SELECT TO
Number of Tiles Characterize and correct the image based upon the number of tiles in line
Range 0-2000 and sample used by Dodger. Dodger corrects the image in a smooth piece-
default 10 wise fashion. Generally, a small number of tiles is used. This results in
good statistics per tile for changing the macro-systematic effects such as
hot spots and vignetting. A large number of tiles can be used for micro-
enhancements such as shadows. A value of zero will cause Dodger to
default to 10 tiles.
NOTE: The smaller the Number of Tiles the larger each tile will be.
Percent Skip Identify the percentage of the image that is skipped when Dodger
Range 0-20 computes the statistics of the input images. A value of 2 will cause Dodger
default 2 to NOT include 2 percent of the outer edge of the images when computing
the statistics. This helps prevent the image edge area from corrupting the
results of Dodger.
Band Independent Enable if you are processing color images and you want the colors to
change to be balanced across all images. You can also use this option when
you want to change the color of your imagery. When this toggle is pressed
each band is processed independent of the other bands although it is not
independent of the other images if the Balance Across Images toggle is
pressed.
Balance Across Images Enable Dodger to use averaging across all input images when deciding
how to modify the imagery. When depressed it will cause Dodger to adjust
all input images based on their combined characteristics. This generally
yields better results when used in conjunction with large numbers of
images with common artifacts.
NOTE: If the images are different in terms of where the hot spot is
then this toggle should be unpressed.
Mean Indicate the desired mean for the processed images. If you enter zero
Range 0-255 Dodger computes the new mean based on the average of all your input
default 0* images.
NOTE: If you want your output images to be brighter, you
should first determine the mean of your images and then enter
a larger value in this field. If you want your output images to
be darker, you should enter a value lower than the image’s
mean.
NOTE: Not used when Color Match enabled.
Standard Deviation Indicate the desired standard deviation for the processed images. If you
Range real enter zero Dodger computes and uses the standard deviation of all your
default 0* input images.
NOTE: If you want your output images to have more contrast,
you should first determine the standard deviation of your
images and enter a larger value in this field.
Minimum Grey Value Indicate the minimum allowed grey level. This can be used to reduce the
Range 0-254 range of the image’s grey level. A value of 10 will cause Dodger to move
default 0* all grey levels above 10.
Maximum Grey Value Indicate the maximum allowed grey level. This can be used to reduce the
Range 1-255 range of the image’s grey level. A value of 240 will cause Dodger to move
default 255* all grey levels below 240.
Minimum Contrast Indicate the minimum contrast compression (gain) that will be applied by
Range 0-2 Dodger. A value of 1.0 will not allow your image grey levels to be
default 1.0* compressed. This particularly helps prevent high contrast areas from being
compressed.
SOCET SET Page 22-7

SELECT TO
Maximum Contrast Indicate the maximum contrast (gain) that will be applied by Dodger. A
Range 0-10 value of 1.3 will limit the amount of gain applied to a factor of 1.3. This
default 1.3* particularly helps prevent low contrast areas receiving too much contrast.
Percent Adjustment Indicate the percentage of adjustment allowed to a grey level when trying
Range 0-100 to reach the Mean. A value of 100 will attempt to achieve the Mean
default 100* whereas a value of 80 will only attempt to reach 80 percent of the Mean.
Maximum Grey Shift Indicate the maximum allowed change in grey level. A value of 20 will
Range 0-255 keep Dodger from changing any value by more than 20 grey levels.
default 30*
Save Save displayed parameters to specified file. If no file has been selected it
prompts you for a file name.
Save As... Save the displayed parameters to a specified file.

Restore Defaults Restore the default dodger parameters
OK Close the window and uses the displayed values as the dodge parameters.
Cancel Close the widow ignoring any changes which were made.
22.2.2 Color Match

Dodger can operate in a “color match” mode which is designed to balance color (3-band) images
with varying tint. You must specify a number of target colors for this algorithm to use. The target
colors correspond to different colors of physical features in your imagery. For example if you
have an area with soil (brown), corn fields (green), and pavement (gray) you would set target
colors to 3. You can also specify an intensity value to guide the output intensity.
22.2.3 Determining Good Parameter Values

If you do not input a parameter file to Dodger it will use default values and will generate well
balanced output.
If you are running Dodger multiple times (on different groups of images) and you want the
outputs of all the groups to be balanced, then you must use a parameter file, and you must input
the same parameter file each time you run dodger.
If you want to build a parameter file by hand, but you are not sure which values to put in it, you
can either use the values suggested below or you can run Dodger in the “statistics only” mode
with the report option on, and it will output a report file that provides values you can input to a
parameter file.
22.2.4 Running with Correction Files

If you are running Dodger with .sup files and saving correction files, you can view the results
immediately in the Main Workstation window. The Image Enhancement “DRA” button controls
whether the corrections are in effect or not. The button is automatically enabled after running
Dodger, but you can toggle it off/on to see the before and after effects of dodging.
The status of the DRA button is saved in the enhancement file and used during Mosaic. Therefore,
if you click off the DRA button and save image enhancements, Mosaic will not apply Dodger
Page 22-8 SOCET SET

corrections. Be sure to turn off the Auto Range Adjust feature in Mosaic when using correction
files.
Use the Minification Level control to speed up the dodging process. Using 8:1 will speed up the
statistics collection significantly. Dodger works the same in every way regardless of the level you
select except for the pixel file used. The mean and standard deviation values may shift slightly
when using reduced levels. You can experiment to determine if the results are significant.
The “Statistics Only” control is not important when running with correction files. Its main benefit
is to avoid the time taken to write pixel files in the other modes.
22.2.5 Report File

Dodger will output a report file if you use the Report option when executing Dodger. The report
file is used when you run dodger in a two-step process: (1) Run dodger on a image that looks
appealing; output a report but do not balance the image. This is accomplished by clicking
Compute on Dodger’s window; (2) take the mean and standard deviation from the report file and
put the values into a parameter file and then run Dodger again (perhaps on multiple groups of
images) to correct the images so they appear similar to the first image.
22.3 Execution - Dodger

1. Select Preparation > Image Dodge and Balance.
2. Select input image type by clicking the RMB in the Image field.
3. Add image(s) of the selected type, then click Open.
4. (Optional) Select a minification level to process. This is only valid for Support and DSUP
files. The default is the first minification level all of the images have in common.
5. (Optional) Specify the parameter settings. Click Band Independent ON if your imagery is
color and you want to balance the bands independently.
If you are balancing color imagery, the Parameter window will

not reflect all the bands until after you make a run. It will only
contain multiple bands if Band Independent is ON.
6. (Optional) Toggle report option and specify report file name.

7. (Optional) Select a location for the dodged images.
8. (Optional) Select output image format.
9. Click Start.
10. (Optional) If running with correction files, check dodging in the Main Workstation
Window.
11. (Optional) Examine the parameter settings and change them.
12. (Optional) Click Start again.
22.3.1 Example Executions

22.3.1.1 Example 1: Quick and Easy Balancing of Multiple Images
To balance multiple images, you simply run Dodger on the input images. You do not need to input
a parameter file, because the default parameters used by Dodger will produce good results.
SOCET SET Page 22-9

22.3.1.2 Example 2: Balancing multiple groups of images

For a large mosaic project, you may need to balance a lot of images. When the images are
different due to time of day/year, type of film, flight direction, etc., you should balance them in
groups. An example would be if you scanned two flight lines of imagery and the hot spot was in
the top right corner for the first strip and in the bottom right corner for the second. In this case
the best way to eliminate the hot spot is to process all images in the first strip in one group and
the images in the second strip in another group. Then by using the Balance Across All Images
option, Dodger obtains a good statistical characterization of the hot spot. Since you want both
strips to end up being consistent with each other, you must set the Mean and Standard Deviation
to be the same for each execution of Dodger. Generally, it is best to obtain the Mean and Standard
Deviation from the first execution of Dodger. Thus it is useful to execute Dodger without a
parameter file or by clicking Compute on the first representative set of imagery from your project.
This will then tell you what the average mean and standard deviation of this representative group
of images is. These values can then be used for all subsequent executions of Dodger for this
project.
1. Execute Dodger without a parameter file for the first group of images. Use the images that
are most representative for your project. Click Compute to get the image statistics.
2. Build a parameter file containing the desired new mean and standard deviation from the
results in step 1. Toggle the Balance Across Image to depressed to get the best results.
3. Execute Dodger on the first group of images. Examine the resulting images. Make
adjustments in the parameter file as necessary, either with the Parameter Editor or by
editing the parameter file directly. For example: If they have too much contrast try lowering
the Maximum Contrast or Standard Deviation. If they are too bright try lowering the Mean.
4. Use the same Mean and Standard Deviation for each execution of Dodger for the entire
project. Use the Overwrite option if you want to save disk space and are confident of the
results.
22.3.1.3 Example 3: Balancing a single image

When attempting to balance a single image, you must be careful to use a small number of tiles
unless you are trying to enhance shadows and other small features. The reason for a small number
of tiles is so that the tiles themselves are large and will have a large number of samples with which
to compute a good statistic for the tile. Thus a lake or large forest is less likely to corrupt the
results. You may want to try to set the Number of Tiles to 4 or 6 for single images. If you want
to enhance the micro-detail, you can try a large number of tiles such as 2000.
22.3.1.4 Example 4: Balancing color images for brightness and contrast only
When attempting to balance color images, and you are only interested in a brightness and contrast
match, then be sure and not set the Band Independent toggle. In this case you need not enter three
values for each item. In the example parameter settings file below, the image is also processed to
have grey values between 10 and 245.
DODGER_DATA_FILE 1.0
# NOTES:
# Even though we are going to process color imagery,
# BAND_INDEPENDENT is FALSE so the images are
# balanced based on the combined bands.

BAND_INDEPENDENT FALSE
NEW_MEAN 128
NEW_STD_DEV 35
MAX_CONTRAST 1.300000
MIN_CONTRAST 1.000000
PERCENT_ADJUSTMENT 100.000000
MAX_GREY_SHIFT 30.000000
MIN_GREY 10
MAX_GREY 245
NUM_TILES 7
PERCENT_SKIP 2.000000
BALANCE_ACROSS_IMAGES TRUE
22.3.1.5 Example 5: Enhancing Shadows

When attempting to “pull” detail out of the shadow areas or low contrast areas you can execute
Dodger with a large number of tiles (small tile size). This will then enhance the image based on
small areas. To do this, set the Number of Tiles to a large number (e.g. Number of Tiles =
image_size/50). Set the Maximum Contrast to 6 to allow a lot of stretching. Set the Standard
Deviation to a large value like 60 to get more contrast. Set the Maximum Grey Shift to a larger
value like 50 to allow a significant change.
22.3.1.6 Example 6: Your images have incorrect contrast after Dodger

If you find that your images do not have enough contrast or too much contrast, the following items
can be changed to increase contrast and the reverse can be used to decrease contrast.
• Try reducing the Maximum Grey Shift: This value can cause all of the grey levels
to approach the mean.
• Try increasing the Maximum Contrast: This will allow more contrast.
• Try increasing the Standard Deviation: This will increase overall contrast.

22.4 Batch Processing - Dodger
22.4.1 Image Dodge and Balance

To execute, go to the <install_path>/bin directory and start it with the “start_socet”
script. On Windows systems you will need to bring up a “DOS Prompt” window. You must
supply parameters to dodger. The parameters are defined below under User Inputs sections. Here
is a sample way to start dodger:
COMMAND LINES:
% start_socet -single dodger -batch -s setting_file
dodger dodger
KEYWORD DESCRIPTION
project Project filename (select from the .prj files in <install_path>/data).

(Required if processing sup files.)
image_list_type This tells the software what type of images are in the image list.
(Acceptable values are PLAIN, SUP, and DSUP.) (Required)
input_image Name of an input image to dodge. Repeat for each input image.
output_image (Optional) Name of an output image to dodge. Repeat for each output
image. Only optional if “image_list_type” is “SUP”.
NOTE: Output names must be listed in the same order as the input
names.
parameter_file (Optional) Parameter file to use for the images in the image list.
write_parameter_ (Optional) Flag to tell dodger to create a default parameter file.

file If this flag is in your setting file no processing of the images will occur. It
simply writes the parameter file and exits.
report_file (Optional) Name of the report file. If omitted no report is generated.
output_format Output image’s format, e.g., img_type_vitec. (Optional: Default is the

same format as the input image.)
minify_output Creates a minified image pyramid for each dodged image after the dodge
processing completes. (Acceptable values YES or NO). (Optional: Default
is NO).
overwrite Setting this option allows the overwriting of existing imagery.

(Acceptable values YES or NO). (Optional: Default is NO).
verbose Print messages regarding the dodge process. (Acceptable values YES or
NO). (Optional: Default is YES).

KEYWORD DESCRIPTION
stats_only Setting this to generate image statistics only without applying to the
imagery. (Acceptable values YES or NO). (Optional: Default is NO).
min_level If dodging SUP or DSUP this value specifies which minification level to
process (Acceptable values 0 - 10) (Optional: Default is 0).
output_image_ If you are creating a new pixel file, set this to the image directory you want
location to use in your Image Location List.
write_to_pixel_ Set to “YES” to create a new pixel file or “NO” to create a correction file.
file Correction file is only valid if input is “SUP”.
22.4.2 Parameter File Format

To create a default parameter file create a setting file with the write_parameter_file
option in it. You can then edit the parameter file this created as appropriate for your imagery.
22.4.2.1 Sample parameter file for grey shade imagery

# NOTES:
# 1. All lines are optional except the first.
# 2. Keywords can be in any order.
# 3. Lines that start with ‘#’ are ignored.
# 4. Keywords that take 3 data values are for color imagery
# when BAND_INDEPENDENT is TRUE. Order is band 1,2,3
# (typically RED GREEN BLUE). For monochrome imagery
# or when BAND_INDEPENDENT is FALSE, only the first
# data value is used.
BAND_INDEPENDENT FALSE
NEW_MEAN 0.000000 0.000000 0.000000
NEW_STD_DEV 0.000000 0.000000 0.000000
MAX_CONTRAST 1.300000 1.300000 1.300000
MIN_CONTRAST 1.000000 1.000000 1.000000
PERCENT_ADJUSTMENT 100.000000 100.000000 100.000000
MAX_GREY_SHIFT 30.000000 30.000000 30.000000
MIN_GREY 0.000000 0.000000 0.000000

MAX_GREY 255.000000 255.000000 255.000000
NUM_TILES 10
PERCENT_SKIP 2.000000
22.4.2.2 Sample parameter file for color imagery with given mean and deviation
# NOTES:
# The NEW_MEAN and NEW_STD_DEV are entered as
# a representative value for the whole project.
# These values based on the desired values for the
# project.
BAND_INDEPENDENT True
NEW_MEAN 80 128 94
NEW_STD_DEV 22 33 30
MAX_CONTRAST 1.3 1.3 1.3
MIN_CONTRAST 1.0 1.0 1.0
PERCENT_ADJUSTMENT 100. 100. 100.
MAX_GREY_SHIFT 30 30 30
MIN_GREY 0 0 0
MAX_GREY 255 255 255
NUM_TILES 6
PERCENT_SKIP 2.0
22.5 The Next Step

After running Dodger, the next step is to input the balanced images into any application that
inputs imagery (Orthophoto, Mosaic, Perspective Scenes, etc.).

22.5.1 Image Balancing in Orthophoto, Image Map, and Mosaic

Orthophoto, Image Map, and Mosaic include some image balancing capabilities. If you run
Dodger prior to Orthophoto, Image Map, or Mosaic, you should not use the image balancing
capabilities of Mosaic or Orthophoto.
When inputting balanced images into Mosaic you should set

the Dynamic Range Adjustment option to “off”.
After running Dodger, you can display the output images on the main SOCET SET display, but
you should not save the Image Enhancement parameters.
If you save the image enhancement parameters of an image

output from Dodger, then Orthophoto, Image Map, and Mosaic
will apply those parameters, which may result in unbalanced
output images.

Chapter 23
Control Point Editor

Control Point Editor creates a file of control points, which are
used by Triangulation. Use the Control Point Editor to create,
view, edit, or change a file of control points.
23.1 Overview
One of the important features of the Control Point Editor is that it lets you input the control point
data in one coordinate system, and save the file in a different coordinate system. Selecting an
alternative datum changes the display and input values. These are converted to/from the
underlying project datum for storage in the .gpf file. This could be used, for example, when
you have a pair of well-controlled images in a UTM project, but you want to collect control points
for a State Plane project.
The major capabilities of the Control Point Editor are as follows:
• Creates a new ground point file or modifies an existing ground point file.
• Saves the ground control points to the current project or a different project.
If the destination project is of a different coordinate system,

the X/Y or lat/ long coordinates will be converted to the new
system. However, the Z or elevation coordinates in the new
destination project will always be the same as that from the
source project, i.e. Mean Sea Level elevation is assumed.
• Converts the list of points to any project’s coordinate system and datum.
• Measures (in three-dimensional space) ground points from controlled imagery.
• Drives the extraction cursor to a three-dimensional ground point location for any
point in the list.
• Displays and accepts control point data in the current project’s coordinate system
or an arbitrary coordinate system and datum.
SOCET SET Page 23-1

Chapter 23 - Control Point Editor
23.1.1 When to Use the Control Point Editor

There are four ways to build a file of control points:
• The Control Point Editor,
• The Interactive Point Measurement window of Triangulation,
• Ground Point Import, and
• Coordinate Measurement Log.
The following table summarizes the situations where one approach is better than the other:
TOOL APPLICATION
Triangulation You are triangulating a few images, and you are not interested in building a
permanent file of control points.
Triangulation You have no control points; during Triangulation you will use only tie
points.
Triangulation In order to save time, you want to measure the control points in the
imagery (sample the image points) at the same time that you type-in the
ground truth (lat/long) locations.
Triangulation You have a list of control points on paper; the list is short and you have
already imported some imagery that is ready to be triangulated.
Control Point Editor You are building a permanent file of control points that will be used over a
long period of time to triangulate many sets of images.
Control Point Editor You have a list of control points on paper, and you want to enter the points
into SOCET SET before running Triangulation; the list is long, or you do
not have any imagery imported yet.
Control Point Editor You have a set of well-controlled images (e.g. PPDB) and you want to
fabricate control points (to be used on other images) by pointing at features
in the controlled imagery.
Control Point Editor You have a file of control points, and you want to convert the points to
different coordinate system or datum.
Ground Point Import You have a disk file of ASCII ground points.
Coordinate Measurement You have a list of control points on paper, enter them and have
Logging SOCET SET convert them to a different datum or coordinate system.
If you decide to use Control Point Editor for inputting your control points, you should run it after
you create a project, but before running Triangulation. If you are going to use well-controlled
imagery (e.g. PPDB) to fabricate control points, you must import the well-controlled images
before running Control Point Editor.
You may also want to consider, when entering coordinate data in systems other than the current
project system, select the coordinate system before selecting datum. This will avoid incorrect
coordinate conversion within the Control Point Editor.
To obtain this window, click Preparation > Control Point Editor.
Page 23-2 SOCET SET

23.2 Control Point Editor

The Control Point Editor’s window’s selections are as follows:
File > Load Project... Prompts you to select the name of the project where the current ground
point file resides.
File > Save GPF Saves the list of ground control points to the file to the current ground
control point file.
File > Save As... Prompts you to enter the name of a new file to save the list of ground
control points into. Converts points to the coordinate system and
horizontal datum of the project for the new file.
File > Exit Exits the Control Point Editor. Prompts you to save the points if you made
any modifications since the last time you saved them. You have the option
of saving the changes to a file or quitting without saving any changes.
SELECT TO
Ground File Display the name of the current ground point file.
System Display list of available coordinate systems in which to display the ground
points. This affects the display only.
Datum Display a list of available horizontal datum in which to display the ground
points. This affects the display only.
SOCET SET Page 23-3

SELECT TO
Elev Specify the vertical reference for elevation points (MSL, Ellipsoid or
Unreferenced) and converts points to this reference if the project is in
another vertical reference.
Point list Display scrollable list of all points in ground point file. To select a ground
BLANK SPACE control point for editing, click on it in the scrolling list.
BLANK SPACE
Point ID Identify the ground point identification string.
BLANK SPACE
Type Display the menu of possible point types to be used in solution. Choices
BLANK SPACE are:
BLANK SPACE • Tie Point - All three coordinates are not known.
BLANK SPACE • Z Cntrl- A vertical control point. Only the Z coordinate is
BLANK SPACE known.
BLANK SPACE • XY Cntrl - A horizontal control point; X and Y coordinates are
known.
BLANK SPACE
BLANK SPACE • XYZ Cntrl- Full three-dimensional control point. All 3
coordinates are known.
BLANK SPACE
• Z Check Point - A vertical control point not to be used.
BLANK SPACE
BLANK SPACE • XY Check Point - A horizontal control point not to be used.
BLANK SPACE • XYZ Check Point - A full three-dimensional control point not
to be used.
BLANK SPACE
Use Modify the valid point flag. If set to Yes the point will be used during the
triangulation solution. If No the point will not be included in the solution.
Coordinates Identify the ground point location displayed in units, and determined by
the currently selected System and Datum values. This is not necessarily the
same as the current project’s system and datum values used to store the
ground points.
Accuracy Identify the ground point accuracy, given in the project units (in meters or
feet; for geographic projects, the value is in Z coordinate project units).
MoveTo Drive the extraction cursor to ground point location of current ground
control point.
Draw Points Toggle graphical display of a ground control point icon and label on the
workstation monitor.
SELECT TO
LMB or KP(/) Transfer current location of the extraction cursor to coordinates of the
current ground point.
Dn Arrow on Keyboard Select the next ground control point in the file.
Up Arrow on Keyboard Select the previous ground control point in the file.
Page 23-4 SOCET SET

23.2.1 View Datum

Special logic is used to correct conversions between the NAD (NAD 27, 83, etc.) datums that are
not used when converting from non-NAD datums. This may result in some confusion if the
converted values displayed by the Control Point Editor (CPE) are compared to values converted
using the Coordinate Measurement tool under certain conditions.
For example, if the original project datum is NAD 27 and a point is converted by selecting the
NAD 83 datum both CPE and CM will agree. However, if the original project datum is something
other than a NAD datum (e.g. WGS 84) and you select NAD 27 to input the coordinate data it
will be internally converted to WGS 84 and stored in the ground point file. If you then try to
display the point as NAD 83 the coordinate values will be slightly different between CPE and
CM. CM converts the NAD 27 point you enter directly to NAD 83 using the special corrections
however CPE converts the ground point from the internal WGS 84 value to NAD 83 resulting in
a slight difference.
If you need to convert points between NAD datums it is recommended that you work within a
NAD datum project and use either CPE or CM. If you are not in a NAD datum project and need
to convert or compare a ground point in one NAD datum with another use the Coordinate
Measurement tool.
23.3 Execution - Control Point Editor

To start up the Control Point Editor, click Preparation > Control Point Editor on the main
workstation window.
23.3.1 Loading An Existing File

1. By default, the Control Point Editor will use the ground point file associated with the
current project. You may select a different ground point file by clicking on the box to the
right of Ground File on the Control Point Editor window.
2. Select the name of the Ground Point File you wish to load by clicking on the ellipse tool
button and selecting a name in the Files list.
3. Click Save to proceed.
4. The Control Point Editor loads the ground point file you selected into the scrolling list. You
may now add, delete, measure, and review the points in the file by right clicking in the field.
5. To save any changes you made to the data, click File > Save GPF on the Control Point
Editor window.
23.3.2 Creating A New File

1. By default, the Control Point Editor will use the ground point file associated with the
current project. You may create a new ground point file by clicking on the ellipse tool
button on the Control Point Editor window.
2. Enter the name of the ground point file you wish to create by entering its name in the
Selection field.
3. Click Save to proceed.
4. The Control Point Editor creates an empty ground point file with the name you entered. You
may now add, delete, measure, and review the points in the file.
SOCET SET Page 23-5

5. To save any changes you made to the data, click File > Save GPF on the Control Point
Editor window.
23.3.3 Adding Points Manually

1. In the Control Point Editor window, right click and select Add to create a new ground
control point.
2. Enter a unique point identification string in the Point ID field.
Point ID names cannot be longer than 30 characters.
3. Set the point type, and indicate whether Triangulation should include this point in the
triangulation solution.
4. Enter the X, Y, and Z coordinate values in the X/Long, Y/Lat, and X/Elev fields. Enter
accuracy values for each coordinate according to the accuracy of your survey.
5. Press Enter on the keyboard accept the new ground control point.
6. Repeat the above steps for each point you wish to add.
23.4 Adding Points by Measuring

If you have already controlled imagery, you may extract the ground control points from that
imagery.
1. First, you must load the image(s) you wish to extract the coordinates from onto the
workstation monitor.
2. [Optional] Click Tools > Coordinate Measurement to display the extraction cursor
location while you are measuring. You may find it helpful to use the Move To Point
capability to drive the extraction cursor to be at or near the point you wish to measure.
3. In the Control Point Editor window, right click and select Add to create a new ground
control point.
4. [Optional] Enter a unique point identification string in the Point ID field. By default, the
Control Point Editor assigns a unique identifier for you, which you may override.
5. Set the point type, and indicate whether Triangulation should include this point in the
triangulation solution.
6. Toggle to the extraction cursor and move it to the ground point location.
7. Toggle back to the mouse cursor and sample with the LMB. This reads the current
extraction cursor location into the current ground control point coordinate display. You
may continue sampling until you have measured the coordinates correctly. The Control
Point Editor will record the last measurement you sampled when you accept the point.
8. [Optional] Enter accuracy values for each coordinate according to the accuracy of your
survey.
9. Press Enter on the keyboard accept the new ground control point.
10. Repeat the above steps for each point you wish to add.
23.4.1 Reviewing and Editing

1. To select a point to review, edit, or delete it, locate it in the scrolling list and click on it with
the LMB. This brings the data associated with the point into the Point ID, Pt. Type, Use,
and coordinate fields. Click File > Save GPF on the Control Point Editor to save points into
the project ground point file.
Page 23-6 SOCET SET

2. You can scroll through the list, moving from point to point, by clicking using the up/down
arrows on the keyboard.
3. Make any changes you wish to make by editing the contents of the Point ID, Pt. Type, Use,
Coordinate, and Accuracy fields. Remember to commit your changes by pressing Enter on
the keyboard.
4. To delete a point, first select it in the scrolling list by clicking on it. Right click and select
Delete.
5. If you have imagery loaded on the workstation monitor, you can drive the extraction cursor
to the ground location of the current point by clicking Move To.
6. If you have imagery loaded on the workstation monitor, you can graphically display the
location and identification of each point by toggling Draw Points on the Control Point
Editor window.
23.4.2 Selecting the Coordinate System or Datum

Click on the Control Point Edit for Coordinate System and Datum. Additional windows will
open to allow you to change the display coordinate system and datum types. This allows you to
enter and display coordinate data in a coordinate system and datum that are different from the
project coordinate system and datum. Click OK when complete. When the Control Point Editor
saves the ground control points, it always saves them in the coordinate system and datum of the
project in which the ground point file resides.
Although different datums can be selected with a USR or LSR

coordinate system, they will not affect the conversion
operation, since these coordinate systems do not depend on a
datum.
23.4.3 Loading and Saving Data in Other Projects

You can transfer ground control point data between projects. This automatically converts the
ground point coordinates from the original project to the new project’s coordinate system and
datum.
1. Load the ground control point data for the current project into the Ground Control Point
Editor.
2. Click File > Save As. Select the name of the project you wish to transfer the ground control
points to in the file selection window. Navigate the directory hierarchy to select the project
data directory of the project to receive the ground control point data.
3. You can either select a new ground control point file or an existing ground control point
file. Click OK to proceed.
4. The display now reflects the new project, file name, coordinate system, and datum.
5. Proceed with the nominal ground point editing scenarios given above to add and edit
ground control points. Remember to save your changes by clicking File > Save GPF.
SOCET SET Page 23-7

Chapter 24
Interior Orientation
Interior Orientation creates a transformation from film space
(camera focal plane space) to digitized image space.
24.1 Overview
Interior Orientation is a critical part of various import models. The units in film space are
millimeters; the units in digitized image space are pixels. This transformation is a key part of the
Frame and Panoramic sensor models.
Fiducial Points
Interior Orientation is a
mapping from film space
to image space
DIGITIZED IMAGE
FILM
The transformation created by Interior Orientation accounts for:

• Resolution used by the scanner (dots per inch).
• Film shrinkage or warping.
• Orientation of the film when it was scanned.
• The portion of the film that was scanned.
• The position (offset) of the film on the scanner.
SOCET SET Page 24-1

Chapter 24 - Interior Orientation
Interior Orientation performs the following processing:

• Provides you with the means by which you measure fiducial points or reseau marks.
• Calculates Interior Orientation coefficients according to the user-selected solution type.
• Automatically updates the solution whenever you measure or re-measure a point.
• Stores the measured point data in the Interior Orientation point data file.
• Stores the Interior Orientation coefficients in the image support file.
24.1.1 When to Use Interior Orientation

You normally perform Interior Orientation:
• After importing your imagery with Frame or Panoramic Import
• Before you perform Triangulation
• Before the image is rectified
• Before Automatic Point Measurement process
Interior Orientation is required for all images that have been created by scanning film. Interior
Orientation is not required for non-film-based imagery such as SPOT or Landsat imagery.
You may skip Interior Orientation if the Interior Orientation transformation is provided with the
digitized image, in which case the system obtains the Interior Orientation information when you
import your image. The Interior Orientation may also be skipped when employing special math
models (for S2 and S3) since the .sup file is generated by using Topographic Engineering Center
(TEC) translators on data block raster images prior to the orientation process.
24.1.1.1 If Fiducials are Not Present

If fiducial marks are not visible in the scanned imagery (because only a portion of the film was
scanned, or because the film never had fiducial marks) then you should skip Interior Orientation.
In this case, proceed directly to Triangulation and use a polynomial solution. See “Solution Type”
on page 26-15.
24.1.2 Interior Orientation Data Flow

IMAGE
POINT
MEASUREMENT
ORIENTATION
SOLUTION
INTERIOR SUPPORT
ORIENTATION FILE
POINT FILE
Page 24-2 SOCET SET

24.2 Automatic Interior Orientation (AIO)

Interior Orientation can either be performed manually or automatically. Automatic Interior
Orientation can be performed with multiple images at once either through the SOCET SET menu
bar to pop up the AIO window, or in stand-alone batch mode. AIO updates the .iop and .sup with
corrected measurements and generates a report file and a log file. If AIO fails, you can call
Manual Interior Orientation by click the Manual IO button to measure fiducials.
AIO supports the following camera types:
Jena LMK 1000 Jena LMK 2000 Wild RC 10
Wild RC 20 Wild RC 30 Zeiss RMK A
Zeiss RMK TOP
To access AIO from within SOCET SET, click Preparation > Interior Orientation > Automatic
Interior Orientation on the main workstation window
The AIO window’s selections are as follows:
File > Exit Exits Interior Orientation.
Options > RMS Set Set RMS threshold (default is EMPTY set by software, see below)
SELECT TO
Project Prompts you to select a project file. This choice is only available if you are
running AIO in stand-alone mode.
SOCET SET Page 24-3

SELECT TO
(Processing Tab) BLANK SPACE

Add Add image files.
Remove Remove image files.
Start Start Automatic Interior Orientation on image files in list.
(Results Tab) BLANK SPACE

Frame Display the Image ID.
Success Fids Display the Success (with a box checked), number of succeeded fiducials/
BLANK SPACE total fiducials, e.g.8 of 8.
RMS (pixel) Display the Root Mean square in pixels.
Resl (mcrs) Display the Scan Resolution in microns per pixel.
Camera Display the Camera type.
Manual IO Calls Manual IO with the highlighted image.
After clicking the Start button, the Processing page will automatically switch to Result page. A
small window showing the AIO progress will pop up. Check boxes in the column Success Fids
will be checked based on the success status.
The result page contains a table showing five columns - Image ID, Success Fids, RMS (pixel),
Resl (mcrs), and Camera. The table can be sorted by each column ascending or descending via
Page 24-4 SOCET SET

clicking the header of the column. The Manual IO button starts Manual Interior Orientation for
either measuring or viewing the results of the selected (highlighted) image.
24.2.1 Execution - AIO

1. Click Preparation > Interior Orientation > Automatic Interior Orientation on the main
workstation window.
2. Click Project File on the Interior Orientation window to provide a selection of project files
to load if one is not loaded previously. Click OK to close.
3. While running AIO, you cannot change the project. If you need to execute the AIO function
on another project, you have two options:
a. Use the main menu to change to the desired project, then run the function again.
b. Activate the function from a command line (in a shell window) by starting the
function’s executable, namely AIO, with start_socet -single aio -gui <project_name>
to pop up a single AIO GUI.
e.g. start_socet -single aio -gui
or start_socet -single aio -gui san_diego<.prj>.

4. [Optional] Click Options > RMS Set on the AIO window to set the desired RMS threshold.
In most cases, leaving it empty (default) is highly recommended. In the latter case, software
will set the RMS threshold based on the scan resolution of each single image, i.e. 25/(scan
resolution), e.g. if the scan resolution is 25 microns/pixel, the threshold is 1.
5. Click Add (or press <Alt> A) to pop up the Select Files window. Select files desired (hold
down <control> or hold down <shift> and click the first and last desired images to add
multiple files) to be added to image file, then click Open when done.
6. [Optional] Click Remove to remove any files from the list that you highlighted
7. Click Start when ready. The processing page automatically switches to Results page
showing the progress and the results.
8. Once the AIO operation is done, a small information window will pop up showing the
summary of the results. Click OK, then review the results. If there are any unchecked boxes
on the Success Fids (column 2), it means that AIO failed with theses images. If you would
like to manually measure the failed ones or just have a visual check, click Manual IO, then
Manual IO will pop up. The AIO window will disappear right away until exiting from the
Manual IO.
9. Click File > Exit to close the window.
10. [Optional] Examine the report file out put by AIO. It will be called <project_name>.io_rep
and will be located in the project data directory. You can also view the log file
<project_name>.io_log for the details of the AIO processing.
24.2.2 Batch Processing - AIO

You run batch AIO as follows:
1. Import the image with Frame import. Specify the camera calibration file that corresponds
to the camera that was used.
2. Run batch AIO
% start_socet -single <install_path>/bin/aio -batch

<project_name><.prj> <support.file>.
for example: start_socet -single <install_path>/bin/aio -
SOCET SET Page 24-5

batch san_diego.prj 2-14.sup

3. [optional] Examine the report file output by AIO. It will be called
<project_name>.io_rep and will be located in the project data directory. You can
also view the log file <project_name>.io_log for details of the AIO processing.
4. [optional] Run manual Interior Orientation and review or correct the fiducial
measurements.
24.3 Interior Orientation (IO) (Manual)

Manual Interior Orientation automatically detects the availability of the stereo monitor. If the
stereo monitor is available, Interior Orientation uses the left image for displaying imagery. If the
stereo monitor is not available, Interior Orientation uses the left image of the console monitor for
displaying imagery.
If there is an image already loaded on the monitor left image, Interior Orientation will attempt to
load the point file corresponding to this image. If there is no image on the monitor left image,
Interior Orientation will prompt you to select an image file.
Different images should not be loaded on the console and

extraction monitors.
The IO (Manual) window’s selections are as follows:
File > Open... Loads a new image onto the monitor. Loads point data, if available.
File > Save Saves both the measured points and the Interior Orientation coefficients.
File > Save As... Saves both the measured points and the Interior Orientation coefficients as
a different file name.
File > Exit Exits Interior Orientation.
Page 24-6 SOCET SET

The remainder of this section assumes that the reader has a working knowledge of general
photogrammetric practices and is familiar with measuring fiducials. Manual Interior Orientation
stores the point measurements in the Interior Orientation Point (.iop) file and stores the Interior
Orientation coefficients in the image support (.sup) file.
The paragraphs that follow describe in detail each of the major components of the Interior
Orientation window.
24.3.1 Point Editing Window

The Point Editing Window contains the fiducial point data for the current image. This window
displays up to four points at a time; if there are more than four points, Interior Orientation
provides scroll bars to support scrolling through the list of points.
SELECT TO
Point ID Editable point identification string.
Fiducial X/Y Editable fiducial X and Y coordinates (in millimeters). Coordinates are
measured from the center of the film, which is the point (0,0) in a
Cartesian system.
Average line/samp Identify the Average Line and Sample of the measurement of the point, in
pixels.
Residuals line/samp Identify the Residual in line and sample resulting from the computation of
the Interior Orientation Solution.
Use Toggle this button to either Yes or No to indicate whether Interior

Orientation should include or exclude the measurements for this point in
the calculation of the Interior Orientation solution.
Right click > Add Point Adds a new point to the Interior Orientation point file.
Right click> Delete Point Deletes the selected point from the Interior Orientation point file.
24.3.1.1 Point Navigation Controls

Use these buttons to take measurements and position the cursor within the image:
BUTTON ACCELERATOR MOUSE DESCRIPTION
Locate All Alt-A N/A Attempts to automatically measure the locations of all
Fiducials. fiducials, based on the calibration data. Sometimes it
may be necessary to manually measure two or more
fiducials in order for the algorithm to successfully find
all fiducials.
NOTE: If your fiducial is not symmetric, you
should not use this button.
Locate This Alt-F N/A Centers the cursor on the fiducial. This uses a
Fiducial. correlation algorithm based on the symmetry of the
fiducial to find the center.
NOTE: If your fiducial is not symmetric, you
should not use this button.
Sample KP(/) LMB Samples image points for valid fiducial points or reseau
marks. Repeated samples will cause Interior Orientation
to compute an average and standard deviation.
SOCET SET Page 24-7

BUTTON ACCELERATOR MOUSE DESCRIPTION
Accept KP(-) MMB Terminates the collection of a set of samples and

Sample performs a Next Point operation. If a sample has not
been made yet, this will cause a single sample to be
accepted.
Current Used to move directly to a fiducial Point or reseau mark.

Point Move the cursor to the corresponding image point on the
monitor; provides random access to the points when you
type the point ID and press the Return key.
Next Point - Dn N/A Displays the next image point along with its
Down corresponding fiducial point or reseau mark, then moves
Arrow the cursor to the next image point on the monitor.
Previous Up N/A Displays the previous image point along with its
Point - Up corresponding fiducial point or reseau mark, then moves
Arrow the cursor to the previous image point on the monitor.
24.3.1.2 Solve Type and Result
SELECT TO
(Solve Types) This component of the Interior Orientation Menu consists of a

BLANK SPACE menu to allow you to choose the solution type, and a text field
BLANK SPACE which contains a measure of how well the solution fits the data
4 Parameter Two translations, a rotation, and a scale change.
6 Parameter Two translations, a rotation, a non-perpendicularity, and a uniform scale
BLANK SPACE change in two directions; also known as A f f i n e T r a n s f o r m a t i o n .
This is the default choice.
BLANK SPACE
BLANK SPACE
BLANK SPACE
An 8-term polynomial warping from camera space to image space.
8 Parameter
BLANK SPACE
BLANK SPACE
Identify the root mean square of the residuals, in units of pixels. You use
RMS this to determine how well the Interior Orientation solution fits the
measurements. A value of less than one pixel is generally acceptable.
24.3.2 Execution - IO (Manual)

The steps to follow for measurement of fiducial coordinates are:
1. Click Preparation > Interior Orientation > Manual Interior Orientation on the main
workstation window.
2. Click File > Open... on the Interior Orientation window.
3. Select an image to display by picking its corresponding support file (.sup) name from the
list in the file selection dialogue.
4. If there is already a point file associated with the image you picked, Interior Orientation
loads it and displays the contents of the point file in the Interior Orientation window.
5. If there is no point file, Interior Orientation leaves the display blank. You can add points to
create a new file as described below.
6. If interior orientation coefficients were not supplied with your imagery when it was
imported onto the workstation, Interior Orientation will not attempt to pre-position the
Page 24-8 SOCET SET

imagery until two or more points have been measured. The easiest technique for measuring
the fiducials in this case is to follow a two-pass approach as given in the following steps.
a. Set the image minification level to the smallest level that will still display all the
fiducials on the monitor at the same time.
b. Measure each fiducial roughly at this minification level. This will result in an
approximation to the locations of the fiducials.
c. Next, set the minification level to the smallest value available (1:1, if possible).
d. Re-measure each fiducial in turn for a second time. This second iteration yields the
final, most accurate set of measurements.
7. Fiducial coordinates are typically defined by the camera calibration. You should make sure
to always measure the correct image fiducial for the current fiducial XY coordinate. Note
that the orientation of the fiducial X-axis in film space is not the necessarily the same as
the orientation of the image X-axis. For example, the film may have been rotated when it
was scanned.
8. To add a new point to the point file, right click Add Point on the Interior Orientation
window.
9. Interior Orientation adds a new point with a default point ID and blank fiducial/reseau
coordinates to the Point Editing window. You enter the X and Y coordinates in millimeters
in the corresponding fields. You may change the point ID, if you so desire.
If you add more than four points, scroll bars automatically

appear on the Point Editing window.
10. To move around the imagery and visit each of the points in the list, use the Next Point and
Previous Point buttons.
11. To visit a point out of sequence, type the point ID in the Current Point text field and press
the Return key.
12. At each fiducial/reseau, position the extraction cursor on the fiducial, then:
a. Press LMB to sample the cursor location (and repeat the measurement at least two
more times to mitigate operator error).
b. Press MMB to accept samples and to complete the measurement of the fiducial.
13. When you have measured enough points for the solution type you selected, Interior
Orientation computes the solution and immediately displays the results in the Residuals
column and the RMS field; subsequent measurements update the results automatically.
Clicking Calculate will simply calculates the Residuals Line/Sample and the RMS. It can
be used after toggling the “Use?” column for a Fiducial.
14. Upon accepting a measurement, Interior Orientation automatically pre-positions the cursor
to the next point to be measured.
15. You may adjust the mouse tracking sensitivity by clicking Preferences > Tracking
Sensitivity on the main workstation window. It is easier to position the cursor more
precisely if you decrease the mouse sensitivity.
16. Proceed to each point in sequence until you have measured all the points.
17. You may wish to re-measure the set of points iteratively until the RMS is satisfactory.
18. If the Interior Orientation solution is satisfactory, you save the fiducial coordinates and the
points you measured by clicking File > Save.
19. on the Interior Orientation window.
20. If you have not saved your points and solution at this point, Interior Orientation prompts
you to do so prior to exiting.
SOCET SET Page 24-9

24.3.3 Semi-Automatic Measurement

The steps to follow for semi-automatic measurement of fiducial coordinates are:
1. Click Preparation > Interior Orientation > Manual Interior Orientation on the main
workstation window.
2. Click File > Open... on the Interior Orientation window and select an image.
3. Add new points to the point file by right clicking Add Point on the Interior Orientation
window, as described above.
4. Make the first fiducial the current point, either by clicking Next/Previous point (Up/Down
arrows) or by entering the point ID of the first fiducial into the Current Point field.
5. Place the extraction cursor roughly near the center of the fiducial.
6. Click Locate This Fiducial. Interior Orientation attempts to re-position the extraction
cursor at the exact center of the fiducial. If it succeeds—“Correlation succeeded”—click
Accept Samples to accept the measurement. If it fails—“Could not find center of
fiducial”—you have two options:
a. Try to re-position the cursor closer to the center of the fiducial and try again.
b. Manually measure this point and continue on to the next point.
7. You can try to locate the rest of the fiducials automatically by clicking Locate All
Fiducials. Interior Orientation predicts the position of each fiducial based on the
calibration coordinates and then attempts to find each fiducial in turn. If this fails, you can
measure another fiducial either with the Locate This Fiducial, or manually if necessary.
Then click Locate All Fiducials again.
The automatic fiducial measurement algorithm may fail if the

film your image was scanned from is excessively warped.
However, a more common source of error are the calibration
coordinates themselves. Make sure you did not misplace a
minus sign or decimal point, and that you are measuring the
points in the correct order.

Chapter 25
Multi-Sensor Triangulation - Overview

and Workflow
T r i a n g u l a t i o n updates the S e n s o r M o d e l s of the
images and uses a mathematical formula which models the
relationship between G r o u n d S p a c e and I m a g e S p a c e .
25.1 Overview
Triangulation is a highly automated system for performing triangulation on a wide variety of
image sources:
• Large blocks of Frame Images
• Satellite imagery (single or overlapped)
• Stereo Image Pair
• Combinations of Frame and non-Frame imagery
• Imagery with or without initial support data
Triangulation automates the tedious procedure of selecting and measuring the image coordinates
of P a s s P o i n t s , T i e P o i n t s , and C o n t r o l P o i n t s . Triangulation automatically flags
unacceptable tie points and displays the required images for remeasurement without your
intervention. It also has the ability to automatically remove unacceptable tie points during the
solve process.
Triangulation executes the following major steps:
• Setup
• Tells Triangulation which images you wish to orient
• The type of adjustment you wish to perform
• The name of the ground point file you wish to use
• The general layout of the image block
• Automatic Point Measurement
• Automatically or semi-automatically measure existing points as well as add new
points to your chosen layout
SOCET SET Page 25-1

Chapter 25 - Multi-Sensor Triangulation - Overview and Workflow
• Automatically measure points for relative orientation of strips or blocks of

images
• Measure across different scales and sensor types
• Provides for automatically driving the extraction cursor to those points which
require interactive measurement
• Interactive Point Measurement
• Measure control and tie points in any of the images participating in the
triangulation.
• Initialize/Solve
• Provides blunder checking, relative, absolute, simultaneous, polynomial, and
Direct Linear Transform (D L T ) adjustments.
• Initializes blocks of images that you imported without a priori camera model
support data. After you solve the images, you must re-load them into the main
image display.
For frame camera imagery, you can start with image coordinates measured outside of
SOCET SET. You can import plate coordinates. You can also import camera position and attitude
data from programs such as ALBANY, PATB, or by entering this data manually. See “Frame and
Panoramic,” Chapter 8 for more details.
Triangulation can also export data for use outside of SOCET SET. For example, you can export
plate coordinates or model coordinates after measuring them with Triangulation.
Triangulation registers images to the ground and to other images. Generally, most images need
to be triangulated before you can perform accurate ground space measurements with the imagery.
Triangulation is sometimes known by other names such as image registration, geopositioning,
aerial triangulation, orientation, exterior orientation, and resection.
The primary inputs to Triangulation are ground points and tie points.
• Ground control points are identifiable objects in the image for which you have the
precise ground space location (lat/long/elevation).
• Tie points are points found in the overlap region of two or more images for which you
do not have the ground space location.
Sensor
Images Sensor
Image Points
Ground Control Points
Page 25-2 SOCET SET

When triangulating more than one image simultaneously, the images can come from a variety of
sensors. For example, Triangulation can orient a SPOT image simultaneously with a frame
camera image.After triangulation, images are said to be triangulated. Other words used for this
are controlled, registered, solved, oriented, and georeferenced
25.1.1 When to Use Triangulation

Triangulation may not operate properly if images are rectified. For best results, perform
Triangulation before R e c t i f i c a t i o n . You should also run Triangulation before you can
accurately perform image mensuration and data extraction.
• For digital satellite-based imagery, you should run Triangulation immediately after
importing your images.
• For digitized film-based images, run Triangulation immediately after Interior
Orientation.
• If there is no support data available when you import the image(s), then you must
run Triangulation before you can use the image for geopositioning.
You can skip Triangulation if the sensor model support parameters provided at import time are
sufficiently accurate. However, the support data provided with imagery is usually a mere estimate
so if you skip Triangulation, poor stereo visualization and inaccurate geopositioning may result.
Thus it is recommended that you run Triangulation even for images that have support data
provided during the Import process.
If you import an image with an unknown sensor model, you should run Triangulation in the
polynomial mode to create a sensor model for the image. See “Image import/Reformat” on
page 7-9 for importing images with unknown sensor models.
After Triangulation, you can run the tools that require controlled imagery, such as Rectification,
Automatic Terrain Extraction, Feature Extraction, Orthophoto, Mosaicking, and Coordinate
Measurement. See “Workflow,” Chapter 3 for more details.
You can run a few applications on uncontrolled imagery, such as Annotation (for making
annotated screen dumps), Minification, and Image Export Reformatting.
25.1.2 Before Starting Triangulation

You must perform the following steps in preparation for Triangulation:
1. Create a project to hold the imagery. See “Project Management” on page 5-1.
2. [Optional] If you are working with film imagery, digitize the images using an image
scanner and create a camera calibration file.
3. Import images into SOCET SET. You should use image names that follow the conventions
described below. See “What to Name Images When Importing” on page 25-4.
4. [Optional] For scanned imagery, run Interior Orientation. Sophisticated digitizing scanners
(such as the LHS Scanner) perform interior orientation during the scanning process. See
“Interior Orientation,” Chapter 24 for further information.
5. [Optional] If you have a file containing ground control points, convert the file into
SOCET SET format by using Ground Point Import. See “Data Import and Export,”
Chapter 16 for additional information.
6. [Optional] If you have some well-controlled imagery, and want to extract some ground
control points, run Control Point Editor. You can also use Control Point Editor to convert
SOCET SET Page 25-3

control points from one coordinate system or datum to another. See “Selecting the
Coordinate System or Datum” on page 23-7 for details.
If you wish to run Multi-Sensor Triangulation on a project

which has been converted to a different coordinate system,
you must re-import the images and start the Triangulation
process from scratch.
25.1.3 What to Name Images When Importing

If you are going to triangulate a large block of imagery, you should use the Triangulation naming
convention: ssss_iiii.sup, where ssss is the strip number and iiii is the image number.
If you are working with a small number of images (a single image pair, for instance) you may use
any names for the images.
Triangulation uses the name of the support file to create names for automatically creating tie
points. It does this by appending a decimal number to the support file name. If the support file
name does not have an underscore in it, the decimal number is added without an intervening
underscore. For example, if the support file name is “123.sup” a typical tie point name will be
“1235”. If the support file name does have an underscore, another underscore will precede the
decimal number. For example if the support file name is “1_1.sup”, a typical tie point name will
be “1_1_7”. This allows you to control the tie point name to some extent and generate IDs which
are all decimal numbers.
25.2 Sample Execution Scenarios

Triangulation is very flexible, and supports a large number of execution scenarios. Each scenario
has a unique set of steps. Simple scenarios, such as controlling a single image, do not require
execution of the more advanced Triangulation features.
25.2.1 Template for Most Workflows

1. Display the Triangulation main window by clicking Preparation > Multi-Sensor
Triangulation on the main menu.
2. Create a new Triangulation file by clicking File > Open Triangulation File in the
Triangulation main window.
3. Select the images you want to triangulate. Click Setup on the Automated Triangulation/Full
Block window and input the image names. See “Multi-Sensor Triangulation - Setup and
GPS,” Chapter 26.
4. [Optional] When triangulating two or more images, measure tie points using Automatic
Point Measurement by clicking Automatic Point Measurement on the Automated
Triangulation/Full Block window. See “Automatic Point Measurement Window” on
page 27-4. This is available only with triangulation.
5. [Optional; Frame only] Eliminate blunders and update estimates of Triangulation
parameters using Blunder Detection by clicking Blunder Detection on the Automated
Triangulation/Full Block window. Then click Start. Click Solve on the Automated
Triangulation/Full Block window, then Start to commence operation. At this stage, images
are relatively oriented with respect to each other. See “Blunder Detect and Solve” on
Page 25-4 SOCET SET

6. Measure ground control points using Interactive Point Measurement by clicking

Interactive Point Measurement on the Automated Triangulation/Full Block window. See
“Automatic Point Measurement” on page 27-2.
7. [Optional; Frame only] Eliminate remaining blunders and perform absolute orientation
using Blunder Detection. At this stage, images are absolutely oriented to the ground.
8. Perform the final triangulation by selecting Solve on the Automated Triangulation/Full
Block window. Click Start to begin iterating. To abort the computation at the end of the
current iteration, click Cancel.
9. [Optional] Click Display Parameters... on the Simultaneous Solve window. The Display
Parameters window appears. You can view the amount of adjustment made to each of the
parameters you selected for adjustment when you created the Triangulation file. There is
one set of parameters for each image in the list of images that you included in the solution.
You can use Prev Image and Next Image to view the parameters for each of the images.
Click Close to close the Display Parameters window. See “Display Parameters” on
page 28-14 for detailed information.
10. [Optional] Click Display Residuals... on the Simultaneous Solve window. The Display
Residuals window appears. You can view the residuals for each individual image point.
There are a set of residuals for each image in the list of images that you included in the
solution. If you find a point that you would like to exclude from the solution, toggle the On/
Off display under the State column to Off, and click Start on the Simultaneous Solve
window to run the solution again. Close the Display Residuals window by clicking Close.
See “Multi-Sensor Triangulation Residuals” on page 28-12
11. If you are satisfied with the solution, click Close on the Simultaneous Solve window. The
Done dialogue appears. (If you are not satisfied with the solution and wish to return to the
Simultaneous Solve window to make corrections, click Cancel.) Click Yes to update the
sensor model parameters in each of the images in the list.
12. [Optional] You can review the detailed Triangulation report by clicking Display Report...
on the Simultaneous Solve window.
13. Exit the Triangulation Solve window by clicking Close.
25.2.1.1 Single Image

To control a single image, perform the following steps:
STEP DESCRIPTION
1. Setup Create a single artificial strip and put the image into that strip.
2. Interactive Point Enter ground control points and measure them in the image.
Measurement
3. Simultaneous Run solve to generate an updated support file.

Solve
25.2.1.2 Two or More Images, Not Blocked

If you have satellite imagery, or a few frame camera images laid out in an irregular pattern,
perform the following steps:
STEPS DESCRIPTION
1. Setup Create a single artificial strip and put all the images into that strip.
SOCET SET Page 25-5

STEPS DESCRIPTION
2. Automatic Point Measure tie points in the overlap regions.

Measurement
(triangulation
only)
3. Exterior Initialize Only perform this step for frame imagery that is in strips. Computes Initial
exterior orientation parameter estimates from data in the Triangulation
File.
4. Interactive Point Enter ground control points. Measure image coordinates of control points
Measurement and tie points interactively.
5. Simultaneous Run solve to generate an updated support file.

Solve
6. Verify If the solution is bad (has high residuals) repeat steps 3, 4, and 5 as needed.
25.2.1.3 Block of Images

Use the following steps when you have a large number (four or more) B l o c k o f I m a g e s laid
out in a blocked fashion. Each row of images is called a “strip.” This process is normally used for
Frame camera images, but will also work for other sensor types that are imported with unknown
camera locations
Overlap
Image Strip 1
Sidelap
Image Strip 2
STEPS DESCRIPTION
1. Setup Creates a Triangulation File which contains the list of images and
describes the strip layout.
2. Exterior Initialize [Only for Frame images] Computes initial exterior orientation parameter
(skip for non- estimates. These estimates are automatically computed using data in the
Frame images) Triangulation File. Exterior Initialize will estimate position and attitude for
frame images if you do not enter this data. For panoramic images, and
images with large obliquities, you enter the information manually during
import; for satellite images (such as SPOT) the information is read during
image import directly from the tape that contains the imagery.
3. Automatic Point Measures tie points and performs control point transfer automatically;
Measurement prompts you to edit tie point measurement failures manually. You can use
this capability to drive to all missing measurements.
Page 25-6 SOCET SET

STEPS DESCRIPTION
4. Blunder Detection [Only for Frame images] Forms relative, strip and floating block
(skip for non- sequentially; automatically takes you to edit blunders. The exterior
Frame images) orientation estimates can be updated at this stage.
5. Interactive Point Enter ground control points. Measure image coordinates of control points
Measurement and any tie points interactively.
6. Blunder Detection [Only for Frame images] Transform floating block to ground and
(skip for non- automatically takes you to visit blunders. The exterior orientation
Frame images) estimates can again be updated at this stage. For just two image
orientations this phase results in the absolute orientation.
7. Simultaneous Perform simultaneous bundle adjustment. Blunders found at this stage are
Solve again automatically visited.
25.2.1.4 Large Block of Images - Cannot Fit All Images on Disk At Once
Use the following steps when you don’t have enough disk space to hold all images of the block
at the same time.
For example, assume that your block is 15 strips of 20 images each, and each image is 100MB,
and you have 11 GB of disk space. Thus you can fit 110 images on-line at once, or up to 5 full
strips. Thus each subblock will contain 5 strips. Since the subblocks must overlap by one strip,
your first subblock must contain strips 1 to 5; the second subblock has strips 5 to 9; third subblock
has strips 9 to 13; and the fourth subblock has strips 13 to 15.
STEPS DESCRIPTION
1. Create Project Create a project. Determine how many subblocks you will use and which
strips belong to which subblocks. Identify the overlap strips. You will start
the next step with the first subblock.
2. Load subblock Import the imagery for the current subblock.

Images
3. Setup subblock Create a new Triangulation (atf) File which contains the images (and only
the images) of the current subblock. Re-use the same gpf file for all
subblocks (the gpf file will grow with each subblock). Steps 3 and 4 are
performed on the current subblock.
4. Solve the current Triangulate the subblock as if it were a complete block. See “Block of
subblock Images” on page 25-6 for the procedure. The steps include: (a) Exterior
Initialize (only if the images were Frame images imported in “Unknown”
mode); (b) APM - automatic; (c) APM - interactive; (d) Blunder Detection
[Frame only]; (e) Interactive Point Measurement [measure control points];
(f) Blunder Detection [Frame only]; (g) Simultaneous Solve; (h) Verify
solution and make final corrections.
5. Remove subblock Remove the subblock pixel files from the disk. Caution: don’t remove the
imagery support files or the ipf files. To save time, you may leave the pixel files of
the images from the overlapping strip on the disk.
6. Do other Repeat steps 1 to 4 for each subblock.

subblocks
7. Setup whole block Run Setup and create a Triangulation (atf) file for the entire block. Put all
images into the ATF file. Reuse the *.gpf file (only one) and *.ipf files
(one per image) that were created for the subblocks.
8. Solve whole block Run Simultaneous Solve on the whole block. You may also run Blunder
Detection. Do not run Exterior Initialize, APM, or IPM.
SOCET SET Page 25-7

25.2.1.5 Parallel Processing of a Large Block

If you have a large block of images you can increase your throughput by performing the
triangulation on multiple computers in parallel. Parallel triangulation is a sophisticated procedure
that should be attempted only if you are an experienced SOCET SET operator. Parallel
triangulation requires the following operating system skills: File editing, file copying, and file
concatenating.
Divide the block of images into subblocks. The number of subblocks should equal the number of
computers you are going to use. For example, if you have 30 strips and four computers, you would
have four subblocks, containing strips 1-8, 8-15, 15-23, and 23-30 respectively. The subblocks
must overlap by one strip. In this example, strips 8, 15, and 23 are overlap strips.
Each subblock is processed simultaneously on a different computer. All subblocks are processed
in the same project. You must store all the pixel files on-line simultaneously. After all the
subblocks are separately solved, you merge all the subblocks into a single triangulation job and
solve the whole block.
Images in non-overlap strips must be named using the normal naming convention. For example,
image 5 in strip 2 should be named 2_5.sup.
Images in the overlap strips must be named as follows: when the overlap strip is the final (bottom)
strip in a subblock, the normal naming convention is used. But when the overlap strip is the first
(top) strip in a subblock, then the image names must end in “X”. The purpose of this rule is to
ensure that no two images share the same name. For example, when strip 15 is in subblock 2, then
image 7 in strip 15 is named 15_7.sup; but when strip 15 is in subblock 3, then image 7 in strip
15 is named 15_7X.sup. This rule only applies to images in overlap strips.
STEPS DESCRIPTION
1. Create Project Create a project. Determine how many subblocks you will use and which
strips belong to which subblocks. Identify the overlap strips.
2. Load Images Import all the imagery for this project.
3. Create special For all images in all overlap strips, create a second support file by adding
overlap images an “X” to the support file names. For example, if strip 15 an overlap strip,
copy 15_1.sup to 15_1X.sup; copy 15_2.sup to 15_2X.sup, etc. for all
images in strip 15. Do not copy the pixel files or the enhancement (enh)
files. Do not copy support files of images in non-overlap strips.
4. Start parallel Perform steps 4 to 5 in parallel for all subblocks. Each subblock should be
workflow processed on a separate computer for maximum throughput.
5. Setup a Subblock Create a new Triangulation (atf) File which contains the images of the
current subblock. Each subblock must have its own gpf file (e.g. subblock
3 could use sbblk3.gpf). DO NOT share gpf files between subblocks.
When selecting overlap images to be used in a subblock: use images with
an “X” in the name when the strip is the top (first) strip of the subblock;
use images without an “X” when the strip is the bottom (final) strip of the
subblock. You cannot have the same image name used in two (or more)
subblocks.
6. Solve a subblock Triangulate the subblock as if it were a complete block. Use the procedure
described above in the “Block of Images” section. The steps include: (a)
Exterior Initialize (only if the images were Frame images imported in
“Unknown” mode); (b) APM - automatic; (c) APM - interactive; (d)
Blunder Detection [only for Frame images]; (e) Interactive Point
Measurement [measure control points]; (f) Blunder Detection [only for
Frame images]; (g) Simultaneous Solve; (h) Verify solution and make final
corrections.
Page 25-8 SOCET SET

STEPS DESCRIPTION
7. Finish all Complete steps 4 to 5 for all subblocks before proceeding to step 8.
subblocks
8. Merge overlap ipf For all images in overlap strips: Merge the two ipf files (one with X and
files one without) by catenating the files (use the Unix cat command) and then
editing the resultant file to make the file header correct (the file header
must contain the correct number of points in the file). For example, for
image 7 in strip 15:
cat 15_7.ipf 15_7X.ipf > temp
mv 15_7.ipf 15_7.ipf.orig
mv temp 15_7.ipf
9. Merge gpf files Merge all the gpf files from all the subblocks into one large gpf file for the
whole block. Edit the file to make header correct (the file header must
contain the correct number of points in the file). For example:
cat subblk1.gpf subblk2.gpf .... subblk3.gpf >
wholeblk.gpf
10.Create ATF file Run Setup and create a Triangulation (atf) file for the whole block. Use the
for whole block large gpf file that you created in step 8. For overlap images: include only
one image, namely, the image that does NOT end in X. For example,
include image 15_7.sup; but do not include image 15_7X.sup.
11.Solve whole Run Simultaneous Solve on the whole block. You may also run Blunder
block detect. You may run IPM, but it may not work for images that are missing.
Avoid running Exterior Initialize or APM.
25.3 Batch Processing - Multi-Sensor Triangulation

In certain situations running Automatic Point Measurement and Solve in batch mode may be
beneficial. To operate in this mode type in one of the following at the command line:
% start_socet -single mst <-s settings_file> -batch

<atf_file> -apm

<atf_file> -solve

<atf_file> -apm solve
The <atf_file> must be a full path to an .atf file in the data directory of the project. The .atf file
must be a valid file that the Setup step of Triangulation produces.
Seven new options in the .atf file can affect Triangulation. The options are:
USE_GPS_FILE
USE_INPUT_COV_FILE
USE_TRI_CONSTRAINT_FILE
USE_DTM_FILE
TPP_FILE
SOCET SET Page 25-9

TRANS_TF_CTL_IMG
USE_UPDATE_ZERO_SIGMAS
USE_GPS_FILE, USE_INPUT_COV_FILE, and USE_TRI_CONSTRAINT_FILE are set
during Setup. USE_DTM_FILE, TPP_FILE, and TRANS_TP_CTL_IMG are set during APM.
USE_UPDATE_ZERO_SIGMAS is set during Simultaneous Solve.
Modification of the flags by editing the .atf file outside of SOCET SET is not recommended.
Following is a definition for each of the seven flags.
• USE_GPS_FILE is a boolean option that indicates if the gps file is to be used during
Triangulation. It has a default value of 0 (FALSE).
• USE_INPUT_COV_FILE is a boolean option that indicates if the input covariance file
is to be used during Triangulation. It has a default value of 0 (FALSE).
• USE_TRI_CONSTRAINT_FILE is a boolean option that indicates if the constraint file
is to be used during Triangulation. It has a default value of 0 (FALSE).
• USE_DTM_FILE is a boolean option that indicates if the DTM is to be used during
Triangulation. It has a default value of 0 (FALSE).
• TPP_FILE records the tpp file name during APM and has a default value of 3x3.tpp.
• TRANS_TF_CTL_IMG is a boolean option that records the possibility to transfer points
from control images during APM. It has a default value of 0 (FALSE).
• UPDATE_ZERO_SIGMAS is a boolean option that records the possibility to calculate
default sigma values during Simultaneous Solve. It has a default value of 0 (FALSE).
Triangulation saves the points and support files to the directory hats_backup in the project
directory at the beginning of the batch session. If the user uses both -apm and -solve in one
command, then only the files prior to APM will be backed up. Log data is written to hats.log
(during APM) and to <name>.rep (during Solve). <name> is the prefix of the .atf file name.
Providing a settings file to MST is optional. If used, Settings_file must specify the full path and
name of the setting file.
MST Setting file keywords:
KEYWORD DESCRIPTION
hats.use_adaptive_matcher Set this keyword to “Yes” to enable the Adaptive Tie-Point Matcher. By
default, the Adaptive Tie-Point Matcher is disabled.
MST settings file example:

setting_file 1.1
hats.use_adaptive_matcher yes
25.4 Data Files

Triangulation creates, updates, manipulates and uses the following files.
25.4.1 Triangulation File (.atf)

This file contains a list of images that will participate in the triangulation. It also contains the
necessary information to compute the initial estimates of the Triangulation parameters. Setup
creates and populates this file.
25.4.2 Ground Point File (.gpf)

This file contains the information about all ground coordinates of points involved in
Triangulation such as control and tie points. This file is updated by Automatic Point Measurement
(for tie points) and Interactive Point Measurement (for control points and tie points). You can
create a Ground Point File containing just control points by running Interactive Point
Measurement before you import any imagery. The residuals of each point are stored in the Ground
Point File; the residuals are updated by Blunder Detection and Simultaneous Solve.
Normally, you will use a single Ground Point File (.gpf) to control all images in your project.
Each point in the file has a unique identifier called the Point ID for use throughout Triangulation.
There are several ways to create the Ground Point File for your project:
• Interactive Point Measurement provides a Review/Edit mode in which you can enter
the ground control points regardless of whether you have imagery available.
• Run Automatic Point Measurement
• You can convert ASCII-formatted ground point files into the format that
Triangulation expects by using ASCII Ground Point Import, as described in the Data
Import/Export chapter. See “ASCII Image Point Import” on page 16-5 for details.
25.4.3 Image Point Files (.ipf)

Triangulation creates an Image Point File for each of the images participating in the triangulation.
Each Image Point File has the same base name as the corresponding image file, but with a suffix
of .ipf. The image point file contains the image point measurements and the point ID of the
corresponding ground point from the Ground Point File. Automatic Point Measurement initially
creates tie point data; Interactive Point Measurement creates and edits the ground control point
data as well as tie points. This file is updated by Blunder Detect and Simultaneous Solve. If you
somehow have points in IPF files which are not reflected in the GPF file, transfer them using the
Reset > Transfer Image Points menu selection.
25.4.4 Image Support Files (.sup)

A single Support File exists for every image that participates in Triangulation. The ultimate goal
of Triangulation is to build a support file that has accurate sensor model parameters. This file
contains information for relating ground and image points via the sensor’s math model. This file
is created during Image Import and updated by Exterior Initialize, Blunder Detection, and
Simultaneous Solve.
25.4.5 Image Files

A single Image File exists for every image that participates in Triangulation. The file contains the
pixel information for each image. This file is created during Image Import.
25.4.6 Constraint Files (.cns)

When images share common exposure parameters these must be treated together and not adjusted
as if they were independent. The constraint file defines which image parameters are shared
between which images and allows the solution to adjust them in all shared images at once rather
than independently for each image. GPS uses a constraint file.
25.4.7 Automatic Point Measurement Strategy Files (.apm_strat)

This file is used by Automatic Point Measurement (triangulation only) to guide the hierarchical
matching algorithm. You must select one of the existing Automatic Point Measurement Strategy
Files in the internal database. For Automatic point generation but manual point measurement, you
can use the manual.apm_strat file.
25.4.8 Solve Strategy Files (.solve)

Contains flag values and parameter limits used by the Solve bundle adjustment operation.

25.4.9 Tie Point Pattern File (.tpp)

Automatic Point Measurement uses this file to control the placement and number of tie points.
You can edit this file at will at the beginning of Automatic Point Measurement.
25.4.10 Input File Bundle Measurement (images.meas)

Contains image coordinate measurements. This file is used for Close Range Solve input. The file
is generated from the File Export function.
25.4.11 Object Coordinates (object.ini)

Initial object coordinates, usually control points, used for Close Range Solve. The file is
generated from the File Export function.
25.4.12 GPS File (.gps)

Contains accurate camera location data for each image at the moment of exposure and is used to
define the support file math model.
25.4.13 ASCII Ground Points (.agp)

Contains the same information as the .gpf file of the same name. It also includes accuracy
information for each point. The file is generated from the File Export function, and is designed
specifically for use by Terrain Import.
POINT
DESCRIPTION
TYPE
0 Tie Point
1 Vertical Control Point
2 Horizontal Control Point
3 3-D Control Point

4 Vertical Check Point
5 Horizontal Check Point
6 3-D Check Point
Each point takes up one line of text and is represented by eight fields: <point id> <x> <y> <z>
<x-accuracy> <y-accuracy> <z-accuracy> <point type>. The point id is an alphanumeric
identifier that is unique to the point. x, y, and z are the point’s coordinates. The accuracy fields
give the standard deviation or error along the corresponding axis. The point type distinguishes
among a T i e P o i n t s , C o n t r o l P o i n t s , and C h e c k P o i n t .
25.4.14 Graphical Attributes (.gra)

Contains values to set the color, font size, font type, line size, and line thickness for each of the
graphics types displayed during the triangulation process. These files are stored in the /

internal_dbs/HATS directory and may be customized and stored under different names
based on the user’s preferences.
25.4.15 .ocov file

The .ocov file is a binary file containing the posteriori (after adjustment) variance of adjusted
sensor model parameters and all types of ground points. It also contains the covariance between
any pair of there parameters and ground points. Of course it contains the ID of these parameters
and points as well. The specific parameters and points included in the .ocov file can be controlled
by the user through the .cns file.
25.5 Automated Triangulation/Full Block

The Triangulation main window is labeled Interactive Triangulation/Model when you do not have
a Block Triangulation license. To open this window click Preparation > Multi-Sensor
Triangulation on the main menu.
The Automated Triangulation/Full Block window’s selections are as follows:
File > Load Project Prompts you to pick an existing project.

<Ctrl>P

File > Open Triangulation Prompts you to open an existing project.

File
<Ctrl>O
File > Save Triangulation Saves the triangulation file using previously selected name.
File
<Ctrl>S
File > Save Triangulation Prompts you for new name of the triangulation file. The triangulation file
File As is not automatically saved. If the new name exists, its contents will be
overwritten. The new triangulation file will be loaded.
NOTE: If you wish to change your setup and save the results to a
different triangulaiton file, perform “Save As” BEFORE making the
changes.
File > File Export BLANK SPACE

ALBANY Image Exports file in a format for third party software. A file named
BLANK SPACE albany.exp is generated in the project data directory.
PATB (Old) Image Exports file in a format for third party software. A file named patb.exp
BLANK SPACE is generated in the project data directory. This file is stripped of all
underscores as required by the original PATB format
BLANK SPACE
BLANK SPACE
BLANK SPACE
Exports file in a format for third party software. A file named
PATB (New, BLUH) patb_new.exp is generated in the project data directory. This file
BLANK SPACE does not strip underscores and is compatible with the latest PATB format
BLANK SPACE which can be used by the BLUH software.
PATM Image Exports file in a format for third party software. A file named patm.exp
BLANK SPACE is generated in the project data directory.
Close Range Image Exports file in a format for third party software. A file named
object.im is generated in the project data directory.
BLANK SPACE
BLANK SPACE
BLANK SPACE
Exports file in a format for third party software. A file named
Close Range Ground image.meas is generated in the project data directory.
BLANK SPACE Exports file in a format for third party software. A file named
ISSBA Image object.im is generated in the project data directory.
ASCII Ground Points Exports file in a format for Automated Terrain Extraction. Its name is the
same as the current ground point file, except for the extension, which is
.agp. The file is generated in the project data directory.
File > Exit Prompts you to save the triangulation file if there are changes, before
exiting triangulation.
Settings > Graphical Display Pops up the Graphics Display Menu. The Graphics Display Menu is used
to turn individual graphics items on or off on the display.
Settings > Enable Multi- Turns on/off the multi-image display when measuring points in IPM, APM,
Image display Blunder Detect, and Solve. When a point has more than two rays,
triangulation will create a viewport for each ray.

Reset > Support Files BLANK SPACE

Restore From Previous Copies backup support files from the backup directory to the current
BLANK SPACE directory. The previous is saved automatically prior to any Init/Solve
BLANK SPACE operation.
Restore From Backup Copies the backup support file from backup directory to current directory.
A backup is made by selecting Backup Support. Whenever the
BLANK SPACE triangulation file is saved from the File menu a backup is also saved if one
BLANK SPACE does not already exist.
Backup Support Copies the current support files to the backup directory overwriting any
existing backup versions.
Reset > Measurement Files BLANK SPACE

Delete All Delete all tie points and changes control points to the unmeasured state.
Delete Tie Points Only Deletes all tie points.
Restore From Backup BLANK SPACE
BLANK SPACE Copies backup ground and image measurement files from the backup
BLANK SPACE directory to the current directory.
Backup Measurements BLANK SPACE
Copies the current ground and image measurement files to the backup
directory overwriting any existing backup versions.
Reset > MST Log Resets the continuous log of triangulation operations. The file hats.log in
the project directory is reinitialized. Each time triangulation is run a new
timestamp entry is made in this file before the data is accumulated.
Reset > Transfer Image Transfers any image points into the ground point file, if they are missing.
Points Also converts any image points in plate coordinates (mm) into line/sample
values. This conversion applies both the lens distortion and IO corrections.
SELECT TO
Triangulation File Name the current triangulation file.
Setup Execute Setup, which creates and populates the triangulation file. See
below for a detailed description of Setup.
Automatic Point Execute Automatic Point Measurement, which automatically measures

Measurement pass and tie points of blocks of images. See below for a detailed
(Triangulation only) description.
Interactive Point Execute Interactive Point Measurement (IPM). You use IPM to measure
Measurement the image coordinates of control points. See below for a detailed
description of IPM.
Blunder Detection Execute Blunder Detection.
Solve Create a window for launching the three types of solutions available in
Triangulation.

SELECT TO
Solve Bingo
25.5.1 Using the Main Triangulation Window

To select a triangulation file, click File > Open Triangulation File on the Triangulation main
window. A file selection dialogue will prompt you for the name of the file, which can be either
new or existing. Once you have selected the triangulation file it will be automatically loaded the
next time you return to triangulation.
To change the name of the current triangulation file, you click File > Save Triangulation File As
on the Triangulation window. A text input dialogue will prompt you to type in a new name. The
triangulation file is not automatically saved. If you selected an existing file as the new name, its
contents will be overwritten. Saving the triangulation file also updates the backup with any
image, ground, or support files that are not already in the backup directory.
25.5.2 Exporting Triangulation Information

Triangulation can export information to several formats. Refer to the descriptions under the File menu
for details. Some of these formats use the strip and image numbers created in Setup. If you have
images in the sss_iii.sup naming convention and wish to preserve the strip and image numbers, be sure
to use Auto Populate in Setup. This will make the strip and image numbers in the exported file match
the support file names.
25.5.3 Backing Up Data and Recovering from Errors

Sometimes when you run Solve, Triangulation will output a solution that is incorrect. The normal
workflow in this situation is to find the blunder, fix it in Point Measurement, and run Solve again.
But if the solution is very bad, you may not be able to properly visualize the images, because the
support data is corrupted. If this happens, you should use the Reset capability to get back to a set
of good support data.
There are two kinds of backup data created by Triangulation:
• Previous - This backup is created automatically every time you start Solve
• Backup - Data that you explicitly create by clicking “Backup Support” or “Backup
Measurements.”
If you think your data is bad, and you want to revert to an older copy, you can restore from either
the Previous version or the Backup version.
Whenever you get a good, reliable set of measurements (e.g. after IPM) you should click Backup
Measurements to save it. Whenever you get a good set of image support data (e.g. after a Solve
with low residuals) you should click Backup Support to save it.
25.5.4 Resetting Point Measurements

The image point files and ground point file can be restored from backed-up versions.

Current image measurements can be deleted either for all points or just tie-points. This can be
used to clear tie-points generated by APM automatically while preserving manually measured
control points for example.
25.5.5 Graphical Display Window

To obtain this window, click Settings > Graphical Display on the Automated Triangulation/Full
Block window.
The Graphical Display window’s selections are as follows:
SELECT TO
Attributes File Pop up list of graphics attributes files available for loading. The graphics
attributes file contains the current color, font size, font type, line type, and
line thickness values for each Triangulation graphics object.
Display Toggle ON or OFF to drawing of Triangulation graphics.
Rotate to First Strip Align the graphics overview display shown with the View button so that
the first strip in the block is left to right.

SELECT TO
Point Graphics BLANK SPACE

Tie Turn on/off all tie point related features (icons, ids, image residuals,
BLANK SPACE ground residuals).
Control Turn on/off all ground point related features (icons, ids, image residuals,
BLANK SPACE ground residuals).
Check Turn on/off all check point related features (icons, ids, ground residuals
ground residuals).
BLANK SPACE
BLANK SPACE
BLANK SPACE
Turn on/off the display of point graphics based on the number of images a
Filter by Number of point is measured in. The user enters either a number (4) to see all four ray
Rays points, or a range (3-5) which will display three, four, and five ray points.
BLANK SPACE Turn on/off the display of point graphics colored based on the number of
Color by Number of images a point is measured in.
Rays NOTE: The colors are specified in the DEFAULT.gra file in the $DB/
HATS directory.

SELECT TO
Select Graphics to Draw BLANK SPACE

Icons Turn on/off the display of point icon. Tie points are displayed as
BLANK SPACE rectangles. Horizontal control points are displayed as triangles. Vertical
BLANK SPACE control points are displayed as circles. Horizontal and vertical control
points combine both a triangle and circle. Check points use the same icons
BLANK SPACE as control points but are distinguished by their color.
IDs Turn on/off the display of the point id string adjacent to the point icon.
Ray Count Turn on/off the display of the Ray Count.
Image Residuals Turn on/off the display of the image residual “spoke”. This object is a
BLANK SPACE scaled representation of the actual line and sample adjustment calculated
BLANK SPACE by the Solve operation and shows both the magnitude and direction of the
BLANK SPACE error. When displayed before a solution is run it represents a vector
pointing to the center of images which contain the point. This allows quick
BLANK SPACE identification of “multi-ray” points. The point is displayed in one color
BLANK SPACE (default green) if the point has a valid measurement for the image and a
BLANK SPACE different color (default white) if the point does not have a valid
BLANK SPACE measurement for the image.
cm/pixels residual This value scales the image residual spokes on the graphical display. A
BLANK SPACE value of 1.0 means that a 1 pixel error is displayed as a 1 cm vector.
sigma threshold Value sets the limit for “unacceptable” residuals based on a factor of the
standard deviation reference Sigma of all computed residuals for the block.
BLANK SPACE Residuals greater than this Sigma factor are shown in red.
Ground Residuals Turn on/off the display of ground residuals for control and check points.
BLANK SPACE This vector represents the adjustment made in solve to fit the fixed control
BLANK SPACE point position. Their are two vectors displayed; a horizontal vector which
BLANK SPACE shows the magnitude and orientation of the horizontal (x,y) residual
components, and a vertical vector which shows the magnitude and sign
BLANK SPACE (up = positive, down = negative) of the vertical (z) residual component.
cm/meter residual Value scales the ground residual vectors on the graphical display. A value
BLANK SPACE of 1.0 means that a 1 m (ft) error is displayed as a 1 cm vector.
Block Connections Turn on/off the display of a vector connecting a point to the center of the
image in which it is identified. The vector between the point and the image
center is shown in two colors, representing measured and unmeasured. The
measured color is set to magenta as a default and the unmeasured color is
white.

SELECT TO
Image Graphics BLANK SPACE

IDs Turn on/off the display of the image name and sensor type string for all
BLANK SPACE images in the Triangulation file when either footprints or centers are
BLANK SPACE displayed. The ID is displayed in the lower left corner of the image
footprint when these are enabled or adjacent to the image center icon when
BLANK SPACE the center is displayed.
Footprints Turn on/off the display of all image footprints on the graphical display.
Centers Turn on/off the display of the image center icon on the graphical display.
Apply Redraw graphics using the current settings.
Close Redraw graphics using the current settings and pops down the Graphical
BLANK SPACE Display
View Load the GRAPHIC_ONLY image to the left console and draws the
graphics using the current settings. Use this function to generate an
overview display of the current triangulation task and point measurement
status.
25.5.6 How to Use the Graphical Display Window

The Graphical Display Window provides a convenient overview of the quality of the
measurements represented by the image and ground residuals of each measured point. Here are
some tips on using this information:
1. The display can be used after running APM to show where tie-points have been placed.
Multi-ray points that were left unmeasured have white unit spokes while those that were
measured are in green. The image footprints can also be displayed to show overlap areas
where multi-ray points may need to be added.
2. After Blunder and Simultaneous Solve, a quality review of the results can be done by
clicking Settings > Graphics Display on the Triangulation window to show the Graphics
Display data. Select Image Footprints, Tie-Points, and Image Residuals. The scale of the
residuals can be adjusted using the cm/pixel scale factor and clicking Apply to redraw the
display. When viewing the residual spokes the following guidelines are useful:
a. The direction of the spokes should be random and about the same length.
b. The spokes around any given point should be distributed and not aligned along a
similar direction. This alignment can suggest an uncorrected systematic error
somewhere in the solution.
Randomly Suggests Systematic

Distributed Uncorrected Error

c. If one spoke for a point is substantially larger than the other spokes and points in the
opposite direction from the other spokes this suggests that the point is badly measured
in this image. Select Image Centers and then click Apply on the Graphics Display
menu to point the spokes to their respective images and determine which image to
remeasure. Toggle the Image Centers and Apply to redisplay the spokes in their actual
X, Y orientation.
d. If all the spokes appear to be displaced in a common direction this can indicate that a
bad ground point may have been added.
Suggests Possible Bad Suggests Possible Bad

Image Measurement Control Point Entered
e. Image residuals exceeding the user selected Sigma Threshold will be displayed in red.
The reference standard deviation for all residuals in the solution is used with this value
to determine “excessive” residuals. The default is 3.0 sigma.
f. Select Ground Residuals on the Graphics Display menu to show the residual
adjustment error for control points.
X,Y,Z Control Point Icon

Z ground residual
component (+ North,
- South)
X,Y ground residual

component at angle
arctan (dy/dx)
3. Toggle to the Console Display, toggle to the Extraction cursor, and click on the residual or
point icon for the point you wish to remeasure. IPM will then move to the selected point.
These guidelines assume that a “reasonable” solution has been achieved. If large measurement
blunders still exist in the data and have not been otherwise removed the reliability of the residual
display is limited. Some common large blunders include inconsistent or misplaced control points,
control point elevations entered in feet for projects with units of meters, and inversion of X, Y
data when entering points by hand. Some of these errors can be detected by removing the control
points from the solution by deselecting the Use flag and re-solving. This will produce a relative
solution which can be checked for measurements. Control points can then be turned back on to
locate the erroneous control point.

25.6 Tips for Triangulating Particular Sensors
25.6.1 SPOT Images

Several sensor types are known generically as “pushbroom,” because of the method of collection,
have unique characteristics that the user should be aware of. This includes the SPOT sensor and
several of the National Technical Means (NTM) sensors. See “SPOT, JERS and IRS Import,”
Chapter 11. These sensors continuously collect imagery as the sensor passes over the ground.
Rather than store the entire image in one huge digital file, the data is broken into pseudo “frames”
with overlap regions created to allow later triangulation into a consistent block. The problem
develops because the overlap areas are, in fact, the same image with the same exposure station
parameters. To determine the elevation of a point (Z) the software projects a ray through an image
point in one image and intersects the ray with the same point in the overlapping image. In this
case the two rays are parallel and never intersect causing the z value calculation for the point
measurement to fail. The x,y values of the sample are still valid for connecting the images
together but the z is worthless. When the solution function attempts to adjust the ground positions
it fails as well. The problem can be avoided by changing the tie points between these pseudo
images to “Vertical” type control points. This treats the point as a Z control point and does not
try to adjust the Z image parameters. The x,y adjustments are done as usual to tie the pseudo
frames together. An additional tie point between strips is still needed (if there are multiple strips
in the block) to connect adjacent images, since these are independent and do not share the same
exposure location values.
If you have SPOT 5 images without control, try the second degree attitude (q0_0, q1_0, q2_0,
q0_1, q1_1, q2_1, q0_2, q1_2, q2_2) to a small sigma value, e.g. 0.00001. Disable all other
parameter adjustments.
25.6.2 Panoramic Images

Panoramic sensors collect imagery over a wide angular field nearly perpendicular to the sensor
track—except for a small adjustment to compensate for the vehicle motion during the sweep. The
main side effect of this is that the image footprints in ground space are curved and resemble a
“bow-tie.”
Image 2
Overlap
Area
Image 1 Sample Tie Points Here
This effect makes automatic tie point measurement very problematic, particularly for images with
minimal overlap at the edges. The best results are achieved by manually selecting tie points
between images as close to the image center as possible, given the overlap extents and doing an
initial solution. This should improve the math models to the point where APM has some chance

of finding additional tie points automatically. Initial solutions with only one tie point can be done
by fixing one of the two images (all adjustments set to NO) and fixing all the image parameters
except camera x, y on the second image to NO as well. This will generate three equations in two
unknowns, and should adjust the two images relative to each other to improve the APM
performance.
25.6.3 QuickBird Images

If you wish to refine the accuracy of your QuickBird images, run Multi-Sensor Triangulation on
them. You have a choice of two different parameter sets to solve.
The small set of triangulation parameters are labeled:
• Q0_CN
• Q1_CN
• Q2_CN
• Q0_LN
• Q1_LN
• Q2_LN
Solving for these are usually sufficient for monoscopic image viewing. To solve for these
parameters, you must collect twelve (12) or more control points in the image. This approach may
also work for stereo viewing, but you may experience y-parallax in the model. To see if y-parallax
is present, load the stereo pair in the Workstation window, turn on Pairwise Rectification, and
move the extraction cursor vertically throughout the image on the left side, the middle, and the
right side. If you cannot place the cursor on the ground without y-parallax, you should repeat
triangulation and solve for the large set of parameters.
The large set of triangulation parameters are labeled:
• Q0_00
.
• Q2_14
Due to the number of parameters you must have more points measured to solve the images. You
should measure at least twelve (12) XYZ Control Points and forty-five (45) Tie Points. Tie points
can be collected automatically with APM using the QuickBird strategy.

25.6.4 IKONOS Images

If you wish to refine the accuracy of your IKONOS images, run Multi-Sensor Triangulation on
them. To do this you will have to select which parameters you want to adjust. The six Space
Imaging IKONOS adjustable parameters are at the end of the list of adjustable parameters. They
are:
CL0 CS0 Turn on CL0 and CS0 only for strip lengths to 50
km.
CLL CSL For long strips, 100 km or greater in length, it

may require the addition of drift parameters, CLL
and CSL, for full accuracy.
CLS CSS The CLS and CSS parameters proportional to

sample are not normally required.
25.6.5 Frame - Advanced

For triangulation application, the set of adjustable parameters used for Frame - Advanced sensor
model are listed below. The initial values for all these parameters are zeros. The angular values
are in radians and the linear units are in meters, international feet or US survey feet. The 2nd set
of adjustable parameters below can be constrained to be the same within a given flight line while
the 3rd can be constrained to be the same for all images in a block as appropriate.
1. Unique for each image
a. GPS antenna coordinate correction – par[0]-par[2]
b. Exterior orientation angle correction – par[3]-par[5]
2. Common to a flight line
a. GPS antenna shift and drift correction – par[6]-par[11]
b. Exterior angular orientation shift and drift correction – par[12]-par[17]
3. Common to a hardware configuration
a. GPS antenna offset correction – par[18]-par[20]
b. Bore-sight angle correction – par[21]-par[23]
c. Principal point of symmetry correction – par[24]-par[25]
d. Principal point of auto-collimation correction – par[26]-par[27]
e. K and P lens distortion corrections – par[28]-par[33]
f. Principal distance correction – par[34]
g. Interior Orientation bilinear transformation coefficient correction – par[35]-par[42]
See “Frame - Advanced Sensor Model” on page 2-6, and See “Frame - Advanced (modified)” on
page 26-19.
25.7 Next Step

Triangulation updates the support file of the images being triangulated and outputs a report file
(.rep) containing the residuals in the ground and image point files.
You must reload the images on the main image display to see
the effects of the triangulation solution.

After you have created a triangulation solution, you can proceed with data extraction applications
such as Automatic Terrain Extraction, Interactive Terrain Editing, and Feature Extraction.

Chapter 26
Multi-Sensor Triangulation - Setup

and GPS
Setup covers the definition of a Triangulation job.
26.1 Overview
This chapter is divided into two section, Setup and GPS Information. Setup is used to define your
triangulation job. The definition is stored in the triangulation file (with an atf suffix).
The Global Positioning System (GPS) file (with a .gps suffix) contains accurate camera location
data for each image at the moment of exposure and is used to refine the support file math models
improving the footprint and overlap area accuracy. This in turn makes Automatic Point
Measurement more likely to succeed in determining valid tie points across the block.
26.1.1 When to use Setup and GPS

Triangulation Setup needs to be completed for any triangulation job. If a GPS file is available,
most of the setup information is updated automatically. If no GPS file is present, several strip
configuration parameters need to be set.
26.2 Setup
You use Setup to define your triangulation job. The definition is stored in the triangulating file
(with an .atf suffix). The definition includes the following information:
• List of images that you are triangulating
• [Optional] Which parameters of the sensor you want adjusted
• [Optional] How accurate are the initial sensor model parameters
• [Only for Frame imagery with GPS] GPS file name
• [Optional] Strategy for solution
• [Optional] Choice of rigorous solution vs. polynomial fit
Default values are provided for most of the triangulation job definition data, so the only data you
must enter is the list of images.
SOCET SET Page 26-1

Chapter 26 - Multi-Sensor Triangulation - Setup and GPS
Setup requires that every image belong to a strip. If the images are Frame images arranged in a
block, each strip is a set of images in one flight line. If the images are not laid out in a block (e.g.
you have only one or two images; or your images are not Frame images) you should create one
strip, and put all the images into that strip.
First you can get flight plan data from your flying contractor. The flight plan info should be in
the form of XYZ and heading. You can import the data as
Image_ID X Y Z 0.0 0.0 heading.

If you don’t have flight plan information you can form the block by setting up a relative strip or
block with excel by using the flying height and overlap to compute relative X and Y offsets in
ground space. If you have at least 3 control points per strip, you can do each strip individually
and use the “exterior initialize” to orient the strip to true ground. If you don’t then you will need
to compute both X and Y offsets.
As an example, if someone flew 5000 feet with 60% overlap the relative strip formation for XYZ
omega phi kappa would look something like this:
Image_ID1 10 10 5000 0 0 0
Image_ID2 3010 10 5000 0 0 0
Image_ID3 6010 10 5000 0 0 0
Image_ID4 9010 10 5000 0 0 0

The X direction is incremented by 3000 because the 60% overlap means that the flight moved
40% of 9 inches in ground X direction.
5000 ft / 6 inches = X / (9 inches * 40%)
3000 ft = X
If you have a second strip that is above the first strip with a 10% side lap, the second strip would
look like this:
Image_ID5 9010 6760 5000 0 0 180
Image_ID6 6010 6760 5000 0 0 180
Image_ID7 3010 6760 5000 0 0 180
Image_ID8 10 6760 5000 0 0 180
5000 ft / 6 inches = Y / (9 inches * 90%)
6750 ft = Y
The setup process is especially important for Frame imagery that was imported in the Unknown
mode. In that situation you must run Exterior Initialize, which uses the strip definition (forward
lap, flying altitude, image size, etc.) to make an initial estimate of the camera locations. If you
enter erroneous data in these Setup fields, Exterior Initialize will fail, and Triangulation will not
be able to process the Frame imagery.
Page 26-2 SOCET SET

26.2.1 MST Setup
The Setup window’s selections are as follows:
SELECT TO
Advanced Open Solution Type/Setup Files window. See “Solution Type/Setup Files”
on page 26-14 for details.
Ground Point File Prompt you to pick an existing Ground Point file or type the name of a new
file.
Auto Populate Populate strips with support files based on “sss_iii” naming
Strips BLANK SPACE

Strip ID Identify the strip ID. Strip ID must be integers.
Use Enable this strip to be used.
Kappa Identify the strip direction.
Reverse Order Reverses order of strips.
Add Remove selected strips. A Right click on a strip will also provide Add/
BLANK SPACE Remove.
Remove Add additional strips. A Right click on a strip will also provide Add/
Remove.
SOCET SET Page 26-3

SELECT TO
Images Identify the image IDs belonging to the current strip. Image IDs must be
Support File integers.
Use Enable this image to be used.
Sensor Identify the Sensor Model.
Reverse Order Reverses the order of the images.
Add Add additional images. A Right click on a Images Support File will also
BLANK SPACE provide Add/Remove/Image Data.
Remove Remove selected images. A Right click on a Images Support File will also
provide Add/Remove/Image Data.
BLANK SPACE
BLANK SPACE
Image Data
Open Image Data window. See “Image Data” on page 26-12
Help Starts the on-line documentation.
Exterior Init Initialize exterior orientation.
Setup Block Starts the Block Setup window which you use to set up strips of frame
images
OK Exit window. Closes Setup window.
Cancel Exit window without any action.
26.2.2 Setup Image and Strip ID Sequence

The naming procedure in Setup allows you to specify image names using a strip and image
number joined by an underscore (e.g. “2_3.sup”). “Auto Populate” will automatically find
support files in your project with this naming and insert them in the GUI.
26.2.3 How to Group Images into Strips

A block is a group of images that are triangulated together. The images in a block are subdivided
into strips. Strips are important only for frame camera imagery; if your images are not frame, all
the images should be put into a single strip. If your images are frame images, then the strips are
defined by the flight path of the airplane. If you import all the frame images as “known”, then the
strips are not very important, and you don’t have to worry about defining the strips properly. But
if you import the images as “unknown” then you must define the strips very carefully, because
Exterior Initialize uses the strip definitions.
For ADS40 blocks, images taken in one flight line should be assigned to the same strip. Following
this convention will guarantee that the images in this strip will only have one set of exterior
orientation after adjustment. It is also recommended that only the 3 BW images are used in
triangulation to ensure that tie-point measurements using APM will have very high success rates.
Page 26-4 SOCET SET

26.2.3.1 Strips of Frame Images and Naming Convention

Most blocks of frame imagery are collected by an airplane flying back and forth in opposite
directions called “strips.”
Three strips of
frame images
Flight
Path
The Triangulation naming convention for image files is ssss_iiii.sup, where ssss is the strip
number and iiii is the image number; for example: 3_5.sup is the fifth image in the third strip.
This naming convention is required for GPS; however, optional

for all others, but the setup operation will go much faster -
especially for large blocks - if you follow the convention.
26.2.3.2 Special Rules for Unknown Imagery and Exterior Initialize

The following diagram gives an example of a block of frame imagery consisting of three
horizontal strips of images, where each strip contains five or six images. Note that images within
a strip are always ordered from left to right.
For clarity, this
Strip 1 1_1 1_2 1_3 1_4 1_5 picture does not
show overlap
between the images.
Strip 2 2_1 2_2 2_3 2_4 2_5 2_6
Overlap is usually
50% to 80% fore-aft;
and 20% to 50%
Strip 3 3_1 3_2 3_3 3_4 3_5 side-to-side.
Strips do not have to have the same number of images in them.

If your imagery is imported in unknown mode, and you will run Exterior Initialize, then your
strips must follow certain rules: Cross strips are permitted, and should be entered after the normal
strips (that is, the strip ID number of a cross strip should be larger than the normal strip ID
numbers). Every strip must contain at least two images.
SOCET SET Page 26-5

6
4_
Example of a cross strip.
5
4_
4
4_
3
4_
2
4_
1
4_
26.2.4 How to Scan Strips of Frame Imagery

Because the plane is going in opposite directions in alternate strips, the film rotation (with respect
to the ground) is reversed in alternate strips. For example, if the plane is flying alternate strips
east - west, then west - east, the data strip side of the film will be on the east side in every other
strip and on the west side the other strips.
If you are importing the imagery in the “known” mode (that is, you will enter the camera positions
and orientation angles during Frame Import) then you can scan the film at any rotation angle, and
images within a single strip can have mixed scanning rotations. But if you are importing the
imagery in “unknown” mode (that is, you will use Block Setup to initialize the block) then you
must follow the instructions below.
26.2.5 How to Scan Imagery Imported in Unknown Mode

When you import imagery in unknown mode, there are two methods available for scanning: (1)
scan all the imagery so that the ground features are all oriented the same way in the digital image;
or (2) scan all imagery so that the data strip side of the film is in the same position on the scanner.
For example, if the plane was collecting strips east-west and west -east, then scanning method (1)
will produce digital images that all have north up; and method (2) will produce digital images that
have north up in every other strip and south up in the alternate strips.
You should never scan unknown imagery so that the top of the digitized image points parallel to
the flight lines. The top of the digitized image must always point perpendicular to the flight lines.
Page 26-6 SOCET SET

Strip 1 Right scan direction
Right scan direction

Strip 3
This picture shows scan method (1) which has all images up, and all scan directions right.
In this illustration, the rectangles represent the ground space footprints of the images. The
arrows point to the top of the digital (scanned) image. When the image is displayed on
the CRT, the arrow will be to the top.
See “Frame and Panoramic,” Chapter 8 for more details about the scanning process.
Strip 2 Left scan direction
This picture shows scan method (2) which alternates left and right scan directions.
In this illustration, the rectangles represent the ground space footprints of the images. Th
arrows point to the top of the digital (scanned) image. When the image is displayed on th
CRT, the arrow will be to the top.
This illustrates incorrect scanning for unknown mode. The

top of the digital image (represented by the arrow) should
never point parallel to the strip direction. The flip_image
tool will correct this problem.
SOCET SET Page 26-7

26.2.6 Block Setup

Block Setup lets you place your strips of frame imagery into a usable initial arrangement. You
should set up your strips and create and select a ground point file in MST Setup before running
Block Setup. Block Setup uses the first XYZ control point in the ground point file to anchor the
first strip. The first strip will be along the ground X direction with the first image at the minimum
(westernmost) position. Subsequent strips will be at smaller Y (farther south) positions. Keep this
in mind when you enter your image strips. For example, a block of images with strips in the east-
west direction should have the westernmost image first and the easternmost last, with strips
incrementing to the south. Once you have the proper strip order in Setup, you can start Block
Setup and change the strip positions in the Main Workstation Window to match your actual image
positions.
Block Setup modifies your support files when you click OK or Accept, so you should back them
up if you wish to revert them to their original condition.
You can use Block Setup in conjunction with or instead of Exterior Initialize. If you achieve an
acceptable alignment with Block Setup, you can skip Exterior Initialize; otherwise you can use it
to fine-tune the results.
The Block Setup window should preload with the contents from its last run every time you restart
it. However, you should check all the data if you have changed the image strips. If the number of
strips changes, Block Setup will return to a default strip layout.
You should not run Block Setup if your imagery is not from a
frame camera.
Page 26-8 SOCET SET

26.2.6.1 Block Setup Window
SELECT TO
Strips
Strip ID Identify the Strip ID from the Setup window.
Mean Flying Height Enter the camera height in project vertical units measured from ground
level.
Image Overlap Pct Enter percentage of image overlap (0-100).
Scan Direction. Select the direction of image pixels relative to flight line (Right, Left, Up,
or Down). Use the RMB to bring up the popup selection. See illustrations
above.
Move Icon Move strips in the Main Workstation Window.
Rotate Icon Rotate strips in the Main Workstation Window.
Apply Update your support files with the new strip locations.
OK Exit window. Closes Block Setup window.
SOCET SET Page 26-9

SELECT TO
26.2.6.2 Execution - Block Setup

1. Create a ground point file with at least one valid XYZ control point. The point does not have
to be an extremely accurate point, e.g. a surveyed position. It just has to be close to your
imagery and ground level.
2. Run MST Setup and create all the strips. The strips should have all the first images on the
same end relative to each other, as shown in the illustrations above.
3. (Optional) Set up MST graphics to display control point icons. This will help you locate the
proper strip positions.
4. Click on Block Setup.
5. Set Flying Height and Overlap cells to match your images. Multiple cells can be edited by
highlighting and typing. Height is measured above ground level.
6. Set Scan Direction of each strip to match your images. Use the RMB to select values. See
the illustrations above for the definitions of Right, Left, Up, and Down.
7. Click either the Move or Rotate icon.
8. Toggle into the Main Workstation Window and move or rotate the strips until they are
aligned properly. Click the LMB near the upper left corner of the strip and release it to
complete the edit.
9. (Optional) Click Apply and load a few images into a new viewport to check for a good
result.
10. Click OK. Support files will be rewritten according to the strip layout.
26.2.7 Exterior Initialize

Exterior Initialize (EI) creates approximate exterior orientations (camera locations and angles)
for a block of frame images from three or more control point measurements. You do not have to
run EI for non-frame images or if the frame images were imported with accurate locations.
Exterior Initialize creates a mosaic of the image footprints by using information from Setup and
transforms them to the measured control points. You should import your images as "known" in
Frame Import, i.e. camera positions set to something other than (0, 0, 10). You should lay the
images out during Frame Import in approximate strips with camera height and orientation as
accurate as possible. However, the absolute position of the strips is not important.
26.2.7.1 Backup before Exterior Initialize

It is strongly recommended that you create backup copies of the support files before running EI.
The reason for backups is that EI will overwrite the support data when it completes, and if EI
failed, then you must revert to the original (before EI) support files. To backup, click Reset >
Support Files > Backup Support on the Automated Triangulation/Full Block window. You can
also backup the support files manually using the computer operating system tools.
26.2.7.2 Inputting Control Points before Exterior Initialize

You must have three or more control points, in the .gpf file specified in Setup, and they must be
measured in the images before running Exterior Initialize. The control points translate the relative
image centers into an absolute ground space using an Affine Transformation process.

26.2.7.3 Validating the results of Exterior Initialize

After running Exterior Initialize, you should verify that it performed well before you run APM or
Solve. To verify the performance, load some of the images on the main image display. If EI was
successful, the cursor should be at approximately the same ground point in all images. If the
cursor is not at the same approximate ground point in all images, then EI has failed, which means
that some of the data you input into Setup was wrong. In this case re-run Setup and double check
your strip and image layout.
26.2.7.4 Execution - Exterior Initialize

Use the following sequence of steps to perform an Exterior Initialize:
1. Click Preparation > Multi-Sensor Triangulation on the Main Workstation Window to
display the Automated Triangulation/Full Block window.
2. Click Setup.
3. Create strips of imagery.
4. Close Setup.
5. Click IPM.
6. Measure at least three XYZ control points in the images.
7. Close IPM.
8. Click Setup.
9. Click Exterior Initialize and wait for the initialization to complete.
10. Validate the results as follows: Load some of the images onto the main image display (you
must re-load them if already displayed). Move the extraction cursor around and verify that
it is approximately on the same ground point object in all overlapping images. If it is not,
then you probably made a mistake in Setup and you must return to step (1).
11. The next step is to proceed to Automatic Point Measurement or Interactive Point
Measurement.
26.2.8 Restrictions for Block Setup and Exterior Initialize

Block Setup and Exterior initialize will only work if the following conditions are met. If these
conditions are not met, you must import the imagery with accurate camera location and
orientation angles during Frame Import.
1. Sensor Type is a Frame camera
2. Photography is approximately vertical
3. Strips are approximately straight
4. Forwardlap is reasonably constant
5. Scales are approximately uniform within each strip
6. Images are approximately the same size
26.2.9 Mixing Known and Unknown Images in a Block

In most cases, the images in a block are either all unkown or all known. Only Block Setup can
handle unknown imagery. You can mix known and unknown images in a block as follows:
Import all the images, known and unknown. Run Setup and define a block containing only the
unknown images. Run Block Setup, APM, IPM, and Simultaneous Solve on only the unknown

images. Run Setup again and add the known images into the block. Run IPM and APM, then
Simultaneous Solve.
The reason that you must wait until after Block Setup to add the known images into the block is
because Exterior Initialize discards all exterior orientation information of all the images and starts
over. Thus, EI would erase the camera location information of any known images.
26.2.10 Image Data
This window contains a list of sensor M a t h M o d e l parameters that can be estimated/adjusted

using triangulation. To obtain this window, do the following:
1. Click Preparation > MST on the main workstation window.
2. Click Setup on the MST window.
3. Select a row from the Images/Support File then click Image Data. The Image Data window
opens and provides the following information:
• The first column lists the names of all possible parameters.
• The second column determines whether a specific parameter is adjusted or not.
• The third column lists the accuracy of the initial estimates for each parameter.

You can change the last two columns, but be careful because Simultaneous Solve depends heavily
on these values. The default values are usually adequate.
If you do not have many tie points or control points, you may have to turn the Adjust flag to “No”
for some parameters so the solution has enough redundancy.
You can modify the Accuracy Factor of checked parameters for adjustment. Enter in a new
Accuracy Factor value and press OK (the Accuracy values will multiply to the new Accuracy
Factor value). To confirm your modification, re-open the Image Data window to notice multiplied
values in the Accuracy column. The Accuracy Factor text box display defaults back to 1.00.
There are three choices to apply:
• Selected Image(s) Only
• Images in Current Strip
• All Images

26.2.11 Solution Type/Setup Files
The Advanced window’s selections are as follows:
SELECT TO
Solution Type Identify the options radio buttons. See “Solution Type” below.
• Rigorous Simultaneous
• Direct Linear Transformation (DLT)
• 3D Polynomial
Setup Files Select strategy file for use by Solve Module.

Solve Strategy...
APM Strategy File
Auxiliary Data (Optional)

Input Covariance Identify file containing a priori covariance data.
BLANK SPACE
Airborne GPS Select the GPS Information file to provide GPS camera positional data (if
BLANK SPACE any) to Triangulation. The default is none. SOCET SET and Applanix
BLANK SPACE EDFE gps files are supported by this feature. This is only used for Frame
imagery.
BLANK SPACE
NOTE: Airborne GPS data is brought into SOCET SET during
Frame Import. See “Text File Input” on page 8-6 for details.
Constraints
Identify file containing GPS data.
USMSD See “USMSD Generation” on page 26-15 for details regarding USMSD.
OK Exit window.

26.2.11.1 Solution Type

Use the Solution Type to specify the sensor math model type Triangulation will create when it
computes the exterior orientation solution. Triangulation provides a choice of Rigorous
Simultaneous, Direct Linear Transform, or 3D Polynomial.
Use Rigorous Simultaneous in any of the following situations:
• Single Image Absolute Orientation—You wish to orient a single image using only
ground control points within the image area, or you wish to generate sensor model
parameters when support data is not available for the image (for example, you
imported the image with Frame Import and specified Unknown for the Camera
Location; note that this only applies to frame camera images, not SPOT or Landsat).
• Stereo Model Absolute Orientation—You wish to perform a bundle adjustment on
two or more images using both ground control points and tie points.
• Relative Orientation—You wish to orient two or more images simultaneously using
tie points only (but no ground control points). This generates sensor models that are
consistent but not tied to the ground, hence relative measurements will be accurate
but absolute measurements (ground space locations) will not necessarily be
accurate.
Use Direct Linear Transformation or 3D Polynomial math model in one of two circumstances:
• You have frame camera imagery without fiducial marks (e.g. you digitized just a
portion of the original film) so you cannot execute Interior Orientation.
• You do not know what kind of sensor the imagery is from, so you do not know which
sensor model to use.
Direct Linear Transform and 3D Polynomial math models require that you start with an identity
type support file. To create an identity support file, import your image with the Image Import/
Reformat application. See “Image import/Reformat” on page 7-9 for details.
Direct Linear Transformation and 3D Polynomial math models

only work with one image per triangulation setup.
26.2.12 USMSD Generation

The Universal Sensor Model Support Data (USMSD) file is a single support file for storing
triangulation parameters and other data from multiple SOCET SET images. A USMSD is
optionally generated from a “Save” in the Solve Window of Multi-Sensor Triangulation (MST).
Upon the save, each image is adjusted using the RPC math model and the new parameters are then
stored in the USMSD file format.
A USMSD is primarily used as input to DPPDB and CIB production jobs, but it may also be used
by customers who want an easy method of storing triangulation results without the need to archive
an entire SOCET SET project. Once a USMSD has been created, it can be imported into another
SOCET SET project. Upon the import, triangulated SOCET SET support files and other SOCET
SET data files will automatically be created.
This job flow guides you through the necessary steps to create a USMSD. Keep in mind that a
Geographic Ellipsoid project is required, and will automatically be created (in the Job Setup step)
by following the job flow steps. See “Job Setup” in DPPDB Generation for more information.

26.2.12.1 Import DTED

Import DTED is an optional process for use in Automated Point Measurement (APM). The
addition of DTED is helpful in imagery with dynamic changes in elevation. The mensuration
process uses the DTED as a reference for elevation changes which can help in finding conjugate
points between the images.
26.2.12.2 Merge DTED

Merge DTED is an optional process for combining two or more DTED files into a single file for
input into APM.
26.2.12.3 Import Image Support Data

This step is only required if you are starting with an AMSD(0) or USMD(0) support file as input
to the triangulation. Commercial data should be imported through the normal import image
process for the particular sensor type.
26.2.12.4 Generate USMSD

The Generate USMSD process is available as an advanced feature in MST Setup. If a stereo
USMSD is required, you must associate stereo mates for each image. Keep in mind that a stereo
USMSD (or AMSD) is required for DPPDB production. If image stereo mates are not selected,
a mono USMSD will be created by default.
1. Create a new triangulation file in MST
a. Preparation > Multi-Sensor Triangulation
2. Create a single strip in MST Setup and add all of the images
3. Select “Advanced…” from within the Setup window
a. Select a Solution Type:
• Recommend “Rigorous Simultaneous”
b. Select a Solve Strategy File
• Recommend “full_covariance.solve”
c. Select Create USMSD and use the push button to the right of the selection to name the
output file. The standard convention is USMSDT.<Rectangle_ID>. If the Rectangle
ID is unknown, any alphanumeric string may be used.
• USMSDT.(name)
• Select the appropriate stereo mate or mates for each image. Note that an
image can have multiple mates, though this is rare.
• Enter the Rectangle ID. The Rectangle ID is a way to uniquely identify the set
of images, and will be stored in the USMSD.
• Enter the security classification of the USMSD file.
d. Save the triangulation file
4. Use APM to triangulate and rework the solution with IPM until you get a suitable RMS.
5. On the solve menu select Save
• The new USMSD file is written to the project directory

26.2.13 Execution - Setting Up Blocks of Images

Use the following set of steps to set up a block of frame imagery:
1. Click Preparation > Multi-Sensor Triangulation on the main workstation window to start
MST. Automated Triangulation/Full Block window will open.
2. Click File > Open Triangulation file on the Automated Triangulation/Full Block window.
Select a file with an .atf extension. Click Save.
3. Click Setup on the Automated Triangulation window.
4. [Optional] Click the ellipse tool button for Ground Point File on the Setup window, to
choose a ground point file, then click Save.
5. [Optional] Click Advanced... on the Setup window. A Solution for solve strategy on the
Type/Setup Files window will open. Click the ellipse tool button for APM Strategy File on
the Solution Type/Setup Files window, and pick an Automatic Point Measurement strategy
file, then click Open, then close the Solution Type/Setup Files window by clicking OK.
6. In the Strip ID Sequence field, enter the range of strip ID numbers. For example, if you have
three strips, enter 1-3.
7. For each strip:
a. [Optional] If you did not follow the Triangulation naming convention when you
imported your imagery, select a support file name then click Image Data.... This will
provide image data corresponding to the current strip and image ID.
b. Press down arrow on the keyboard.
c. Press down arrow on the keyboard and repeat the previous steps (a-b) for each of the
strips in the block.
8. Click Advanced... on the Setup window if you wish to change the solution type or select
Covariance, GPS, or Constraints files. This brings up the Solution Type/Setup Files
window. Select an exterior orientation math model type. Click OK to return to the Setup
window.
9. If you are triangulating frame camera imagery (or other imagery) for which exterior
orientation parameter estimates are not available, click Exterior Initialize.
10. Click OK on the Setup window to return to Automated Triangulation/Full Block window.
11. Click File > Save Triangulation File on the Automated Triangulation/Full Block window.
26.2.14 Tips on How to Run Setup

After you run Setup, the best way to verify the setup is to load the images onto the main image
display and validate that the extraction cursor is located properly in the overlap regions.
A common error is specifying the aircraft altitude in the wrong units. The values should be in the
units of the underlying project, either meters or feet. This error results in either very small or very
large footprints usually distorted or tipped. The success rate of APM is sensitive to the correctness
of the aircraft mean altitude value because of its effect on the degree of footprint overlapping. It
also results in erroneous ground elevations during the measurement of tie points. If the error is
bad enough it may fail to converge to a solution or produce a degenerate solution, which is
evidenced by erratic motion of the extraction cursor when roaming the image.
You can view the image footprints graphically by clicking Settings > Graphical Display on the
main workstation window, enabling image footprints, and clicking Apply. This will display the
graphical footprints on the Console monitor. It may be necessary to zoom out to a higher
minification level to see the entire block. The block should be laid out as you expected, including
any cross strips or gaps. If one or more of the footprints is distorted or appears tilted, it can

indicate a problem with the control points used for Exterior Initialize. You can correct these with
IPM and run Exterior Initialize again. When the block looks correct you are ready to proceed to
measure tie points.
Triangulation of images using support files copied from other projects in other coordinate
systems or datums is not recommended. Although the processing succeeds, the support file that
results is not updated to the correct internal reference coordinate system. One fix to this problem
is to manually edit the adjusted support files and change the ELLIPSOID, VERTICAL_
REFERENCE, A_EARTH, E_EARTH, and ELLIPSOID_CENTER values to agree with the same
values in the project file if they are different. The best approach is to only triangulate images that
have been imported into the current project rather than copied in from another project.
Save the .atf triangulation file after creation or changes to preserve the settings. The last .atf file
will automatically reload into Triangulation when it is next executed.
26.3 GPS Information

GPS files contain accurate camera location data for each image at the moment of exposure and is
used to refine the support file math models improving the footprint and overlap area accuracy.
This in turn makes Automatic Point Measurement more likely to succeed in determining valid tie
points across the block. Triangulation accepts GPS files in both manual format and Applanix
POS/EO format.
26.3.1 Entering GPS Information Manually

You can create a text file from scratch with GPS information for MST to generate the initial block
of images. If you wish to add other non-GPS corrected images you can do so by running Setup
and adding strips and/or images to the block as defined. The individual support files contain a
flag that indicates whether they have been corrected with GPS data. When you begin the
simultaneous solution any adjusted parameters (from any previous solutions if any) are
overwritten by the GPS values taken from the GPS file. This is done because the GPS position
data is treated as fixed and is not repeatedly adjusted with each successive solution.
Images which are corrected by GPS are bypassed by Exterior Initialization and the support files
are not modified.
You must create the GPS file by hand (in an editor) or by writing a program to build the GPS file.
SOCET SET does not contain software to automatically create a GPS file.
26.3.1.1 Definitions of coordinate systems used in GPS

Project coordinate system—the coordinate system you chose when you created the project.
See “Project Management,” Chapter 5 for details.
Camera coordinate system—camera fiducial coordinate system defined during camera
calibration.
Aircraft coordinate system—the x-axis is parallel to and positive in the flight direction, the z-axis
is parallel to the vertical and positive upwards, the y-axis completes a right handed coordinate
system.
26.3.1.2 GPS File Format

For a description of the format and content of a GPS file see:

<install_path>/internal_dbs/HATS/sample_gps_file.gps
1. Strip IDs must be included in the image ID and must be separated from the image ID with
an underscore, (e.g. 2_13).
2. The format of the .gps file must be like the example:
• It must have three lines for each image
• It must have a 1 or a 0 at the end of each camera station line
• The image ids must match your support files
• Strip IDs must be included in the image ID and must be separated from the image
ID with an underscore, (e.g. 2_13) where 2 is the strip ID and 13 is the Image ID.
• Each GPS strip must be separated by the -9 line
• There must be a -9 line at the bottom.
• The file must have the GPS FILE 2 as the first line in the file
• The time for each exposure must be on each camera station line
• The time must go forward, not backward in time and must be in seconds
• There must be at least two images in each GPS strip (i.e. between -9 lines)
• The rotation angle in the GPS file must be in decimal degrees.
3. You do not need (don’t use) an input covariance file.
4. The constraint file is made automatically from the .gps file.
5. It does not matter if you start with “unknown” or “known” .sup files.
6. You must start with .sup files which match the names in your .gps file. When you select the
.gps file on the Setup menu, it will reinitialize all your .sup files and write them out to disk.
If the .gps file is good, you should be able to load any .sup file after selecting the .gps file
and it should be approximately oriented.
7. You must have done IO before starting with the .gps file.
8. The GPS file must be located in the project data directory.
If you are on a Windows platform and you want to turn the GPS solution off, you must edit your
.atf file and set the GPS_INFO_FILE to null. Make sure you exit MST first and then edit and then
go back into MST.
If you then want to turn GPS back on, go into setup and pick the file again.
26.3.1.3 Frame - Advanced (modified)

An example of the modified SOCET SET GPS file format is shown below. This file has two
purposes. It can be used to import images of the Frame - Advanced sensor model type, or it can
be used as input in MST to populate the Setup file and create the Constraint file automatically for
the proper exploitation of GPS/IMU data.
The # sign as the first character in a line signifies comment lines which will be ignored by the
reading program. The first 9 significant lines (non-# lines) contain default accuracies (sigmas) for
the 43 correction parameters of the Frame - Advanced sensor model which the user can modify
as needed.
The 10th significant line contains the default antennae offset and bore-sight values which are set
to zero. Again these values should be modified by you as needed. The last line with a # sign

contains the description of the GPS/IMU data themselves. The -9 string in a single line signifies
the end of a strip or flight line.
The format GPS File 1 cannot be used with the Frame - Advanced sensor model. For valid results
use the newer GPS File 2 format. Example:
GPS FILE 2
#sigma camera (position (X(m,ft) Y(m,ft) Z(m,ft)) attitude (Omega(rad) Phi(rad) Kappa(rad)))
1.000e+000 1.000e+000 1.000e+000 1.000e-002 1.000e-002 1.000e-002
#sigma strip position (shift (X(m,ft) Y(m,ft) Z(m,ft)) drift (dX/dt(m,ft/sec) dY/dt(m,ft/sec) dZ/
dt(m,ft/sec)))
1.000e+001 1.000e+001 1.000e+001 1.000e-001 1.000e-001 1.000e-001
#sigma strip attitude (shift (O(rad) P(rad) K(rad) drift (dO/dt(rad/sec) dP/dt(rad/sec) dK/dt(rad/
sec)))
1.000e-001 1.000e-001 1.000e-001 1.000e-003 1.000e-003 1.000e-003
#sigma (antenna_offset (X(m,ft) Y(m,ft) Z(m,ft)) boresight (Omega(rad) Phi(rad Kappa(rad)))
5.000e-001 5.000e-001 5.000e-001 5.000e-003 5.000e-003 5.000e-003
#sigma principal point (symmetry (x(mm) y(mm)) autocollimation (x(mm) y(mm)))
1.000e-003 1.000e-003 1.000e-003 1.000e-003
#sigma lens distortion (radial (K1(mm/mm^3) K2(mm/mm^5) K3(mm/mm^7)) asymmetric
(P1(mm/mm^2) P2(mm/mm^2) P3 (/mm^2)))
1.000e-009 1.000e-013 1.000e-017 1.000e-007 1.000e-007 1.000e-007
#sigma focal length (mm)
1.000e-003
#sigma interior orientation line (l0(pix) l1(pix/mm) l2(pix/mm) l3(pix/mm^2))
1.000e-002 1.000e-004 1.000e-004 1.000e-006
#sigma interior orientation sample (s0(pix) s1(pix/mm) s2(pix/mm) s3(pix/mm^2)
1.000e-002 1.000e-004 1.000e-004 1.000e-006
#antenna_offset (X(m,ft) Y(m,ft) Z(m,ft)) boresight (Omega(rad) Phi(rad) Kappa(rad))
0.000e+000 0.000e+000 0.000e+000 0.000e+000 0.000e+000 0.000e+000
#image_id X(m,ft,rad) Y(m,ft,rad) Z(m,ft) omega(rad) phi(rad) kappa(rad) time(sec)
1_1580 750312.57 232950.27 1317.25 0.0 0.0 3.141592653589793 459165.888992
1_1581 750618.68 232310.06 1314.87 0.0 0.0 3.141592653589793 459174.161450
1_1582 750906.07 231684.78 1310.05 0.0 0.0 3.141592653589793 459182.182756
-9
2_1624 749314.74 231711.31 1314.95 0.0 0.0 3.141592653589793 460369.544374
2_1625 749615.02 231071.55 1310.68 0.0 0.0 3.141592653589793 460378.237454
2_1626 749914.06 230431.19 1313 0.0 0.0 3.141592653589793 460386.930891

-9
3_1656 753684.76 229049.97 1317.02 0.0 0.0 3.141592653589793 460991.861095
3_1657 753391.15 229702.79 1317.24 0.0 0.0 3.141592653589793 461002.778260
3_1658 753096.67 230339.98 1317.25 0.0 0.0 3.141592653589793 461013.492369
-9
Besides the SOCET SET GPS file format, the Applanix EO/DSS EO data formats can also be used
to populate the Setup file and create the Constraint file automatically. The Applanix format comes
in multiple forms. SOCET SET only supports ECEF and Standard GRID formats. The former
contains camera positions in ECEF X, Y, Z coordinates and orientation angles Roll, Pitch and
Heading. The latter contains camera positions in Easting, Northing, and Height and orientation
angles Omega, Phi, and Kappa. See “Frame - Advanced Sensor Model” on page 2-6, and See
“Frame - Advanced” on page 25-25.
26.3.2 Importing Applanix POSEO Files

Triangulation can import Applanix POSEO format GPS files. SOCET SET supports both the DSS
422 and the DSS 439 cameras. The DSS 422 has a pixel size of 9 microns, while the DSS 439 has
a pixel size of 6.8 microns. After importing, the images may not need further triangulation. You
can check the results for excessive y-parallax and run Triangulation to obtain a better solution if
necessary.

26.3.3 Execution - Importing Applanix Files

1. Import your images using Frame Import. Use the “Read From File...” option on Camera
Position/Orientation to input the Applanix data. Make sure the support file names match the
image ID’s in the Applanix file. Interior Orientation settings are unimportant because
Triangulation will overwrite them.
2. Start Triangulation by clicking Preparation > MST on the main workstation window.
3. Create a new Triangulation File by clicking File > Open... and providing an file name.
4. Click Setup.
5. Click Advanced....
6. Check Airborne GPS then click the ellipse tool button the to the right of the field.
7. Select the Applanix POSEO file you want to import and click Open.
8. Click OK, then click Yes to overwrite backup files to current directory.
9. Exit Triangulation.
26.3.4 Image Parameter Weights

The image parameters to be adjusted can be viewed by selecting an image support file then
clicking Image Data on the Setup window. These parameters are sensor specific and each
includes a default accuracy. For most sensors these defaults are intrinsic to the design of the
sensor, and do not need to be modified by the user. They represent confidence weights that will
be applied during the bundle adjustment to control the degree of adjustment applied to the
corresponding parameter. A weight of 0 implies perfect accuracy, which effectively disables
adjustment of the parameter and is nearly equivalent to setting the Adjust flag to “No.”

Chapter 27
Multi-Sensor Triangulation - Point

Measurement
Point Measurement describes APM and IPM - all of which are
part of Triangulation.
27.1 Overview
There are four ways to measure ground points in imagery:
• Automatic Point Measurement (APM) (in Triangulation)
• Interactive Point Measurement for APM
• Interactive Point Measurement (IPM) for Blunder Detection
• Interactive Point Measurement for Simultaneous Solve
The decision of whether to run IPM before of after APM depends on the kind of ground points
you have. The following table gives some guidance:
WHAT TO RUN SITUATION
APM before IPM You have a few control points; and you want to
Solve (after APM) before running IPM so that it is
easier to find the control points in IPM.
IPM before APM You measure some control points and some tie
points in IPM (in one image only), then you run
APM to transfer these points to other images and to
measure additional tie points.
IPM only You have just one image. Or, you have lots of
control points and you don’t need tie points.
APM only You have no control points. To interactively review

the tie points measured by APM, you use IPM.
Neither APM or IPM You have measured the image points on an

analytical plotter, and imported them with ASCII
Image Point Import, and are using Triangulation
only for the Solve process.
SOCET SET Page 27-1

Chapter 27 - Multi-Sensor Triangulation - Point Measurement
27.2 Automatic Point Measurement

Automatic Point Measurement (APM) measures the image coordinates of tie points in
overlapping images. It also transfers measurements of manually measured tie and control points
to overlapping images. APM is only used when controlling two or more images. Note that this
functionality is only available when you purchase Triangulation.
APM uses the estimates of the exterior orientation parameters obtained during image import or
as computed by Exterior Initialize It also uses the Tie Point Pattern you created as a guide in
selecting the locations of tie points. How you create a Tie Point Pattern is discussed below. If you
have measured points in some of the images APM will transfer those points if possible to all
overlapping images with or without specifying a tie point pattern.
APM has two processing phases: automatic and interactive. You execute the automatic phase
first, followed by the interactive phase. The interactive phase of APM is also called “Interactive
Point Measurement for APM” and should not be confused with the Interactive Point Measurement
step of Triangulation.
The automatic phase attempts to locate and measure tie points for the whole block of images
without your intervention. The automatic phase now uses patterns of tie points which average 3
or 4 points in each desired area of a tie point location. This allows APM to be highly successful
even if it is only 50% successful for all points attempted. This philosophy, combined with the new
minimum tie point edit, permits the use of very dense tie point patterns but only requires the user
to edit the minimum number necessary for a good result.
In places where the automatic phase fails, the interactive phase will automatically display the
images that require remeasurement. All you have to do is make sure that the floating mark is on
the ground. You can run the automatic or interactive phases at any time or repeatedly. The
automatic phase will always try to measure all unmeasured points as well as add missing ones.
The interactive phase will always take you to all missing measurements.
During the second run of APM, only points in the tie point pattern that were not successfully
measured will be revisted. Therefore, the success rate of the second run will go down because the
points left to be processed in the second run will be in areas that are difficult to correlate. For
example, if 90 of the 100 tie points are measured successfully in the first run you will get a 90%
success rate. If 3 of the remaining 10 points are measured successfully during the second run you
will have a 30% success rate.
The automatic Point ID is constructed based on the “master image” and the point number from
the tie point pattern. Thus when a tie point is created (first occurrence on the master image), the
ID is constructed from the master image ID and the point pattern number. Thus a point ID tells
the user what image the point was defined in and the location in that image is based on the tie
point pattern. Existing point IDs are never changed and are checked for duplication.
APM uses the strip and image information from the .atf file and relative position information from
the .tpp tie point pattern file to create a list of likely locations for tie points. It then uses
correlation to precisely measure the pixel line/sample for each candidate point. The correlation
algorithm makes multiple passes at successively lower minification level to allow successful
measurement, even when the image patch locations are widely offset due to the initial state of the
math models. The measurements are stored in the ipf files for each image involved. A ground
point entry is generated for each point at the same time and stored in the .gpf file.
There is only one ground point entry for a given point, but it can have entries in one or more ipf
files; one for each overlapping image at the location of the point. The point id is used to reference
points between the .gpf and .ipf files.
Page 27-2 SOCET SET

27.2.1 APM Guidelines

When you run APM, all the images and their minification levels must be on disk. If you only have
the 1:1 image, you must run Minify before running APM. If you have a large block and do not
have enough room to store all your images on disk at once, you can use the “large block”
procedure. See “Exterior Initialize” on page 26-10 for details.
APM does not work well with JPEG images. You should
reformat JPEG images to TIFF tiled JPEG format before
importing them.
27.2.2 Automatic Point Measurement Execution Summary

You can use Automatic Point Measurement in several different ways. Some examples are as
follows:
1. Run Automatic Point Measurement immediately after Setup. Then run Solve. Then run
Interactive Point Measurement and add control points.
2. Run Interactive Point Measurement first to measure control points and tie points (measure
the tie points in only one image each). Then run Automatic Point Measurement which will
(a) transfer the tie points you measured into overlapping images; and (b) add more tie
points. This mode is particularly useful if the image has no outstanding features for
Automatic Point Measurement to find (e.g. the image is largely forested or the imagery was
purged). You will need to select the initial tie point locations.
3. Run Automatic Point Measurement and Solve iteratively. This may be helpful when the
first run is not very successful. Between runs of Automatic Point Measurement you may
run Exterior Initialize or Blunder Detection (frame only), or Simultaneous Solve. These
latter steps will update the sensor model, so you can re-run Automatic Point Measurement
and it will perform better.
27.2.2.1 Point Transfer Only

If you have some pre-existing points and you want APM to transfer them, but you don’t want
APM to create new transfer points, then you must set the Tie Point Pattern filename to blank.
SOCET SET Page 27-3

27.2.3 Automatic Point Measurement Window
The Automatic Point Measurement window’s buttons and fields are as follows:
SELECT TO
Strategy... Prompt you to pick a Strategy file used by Automatic Point Measurement
for automatic matching of points. This will override the Strategy file
picked in the Setup window.
NOTE: If you wish to automatically generate the tie points but do
not wish to automatically attempt to measure them, then select the
manual.apm_strat file. This permits rapid semi-automatic
measurement when very difficult image conditions exist.
NOTE: If you do not have all minification levels from 128:1 to 1:1
for a given image you can edit a copy of the strategy file to use the
available levels. See the digicam.apm_strat in <install_path>/
internal_dbs/HATS for an example.
Tie Point Pattern... Prompt you to pick an existing Tie Point Pattern. This will bring up the Tie
Point Pattern window (See description below). If you do not specify a file
name APM will transfer existing image and/or control points to
overlapping images.
DTM... Select an optional terrain file to help APM improve its success rate.
Adaptive Tie-Point Matcher Enable or disable the adaptive tie-point matcher. The adaptive tie-point
matcher will cause APM to run slower but may produce better results for
multi-sensor projects.
Page 27-4 SOCET SET

SELECT TO
Processing Results BLANK SPACE

% Rays Measured Display the instantaneous percentage of rays successfully measured by the
Successfully automatic phase of Automatic Point Measurement.
Percent Successful Display the instantaneous percentage of rays successfully measured by the
BLANK SPACE automatic phase of Automatic Point Measurement.
Points Unmeasured Display total number of ground points that contain unmeasured images.
Minimum Points Display the number of ground points that were unmeasured and did not
Requiring Edit have a measured point within a grid cell defined in the apm.apm_strat file.
MIN_GRID_VERT and MIN_GRID_HORIZ define the grid dimensions
used to test the minimum point criteria. It is recommended that at least
these points be manually measured to ensure a good distribution of points.
Additional unmeasured points may or may not be remeasured depending
on the degree of redundancy desired.
Start Automatic Start the automatic phase of Automatic Point Measurement. The Percent
Complete window provides an indicator of the progress of processing.
Start Interactive Start the interactive phase of Automatic Point Measurement. The
interactive phase automatically displays certain windows to prompt you to
measure individual points. (See description below).
Close Close the Automatic Point Measurement window. The state of the
Automatic Point Measurement when you click Done determines what
happens next.
Automatic Point Measurement performs the following processes:

• Clicking Cancel in the Automatic Point Measurement will only save the
measurements completed. Re-execute Automatic Point Measurement to restart.
• Clicking Start Automatic in the Automatic Point Measurement will start the
automatic phase, and all tie point measurements are saved. When you re-run
Automatic Point Measurement, you would normally skip the automatic phase and
proceed directly to the interactive phase.
• If you are in the middle of the interactive phase, all previously measured tie
points are saved. When you re-run Automatic Point Measurement and restart the
interactive phase, point measurement picks up where you left off. You only need
to measure the remaining unmeasured and unacceptable tie points.
• If you have completed both the automatic and interactive phases, all
measurements are saved.
• Clicking StartAt will provide a window where you can schedule the process at a
later time. If you have the Condor distributed processing software installed, it
may be used as well. See “Start At Jobs” for details.
SOCET SET Page 27-5

27.2.4 Tie Point Pattern

This window is for entering and editing tie point patterns and coordinates.
0, 0 100, 0
+x
+y
0, 100 100, 100
This window consists of a large square drawing area which represents the image, and a list of tie
points. The coordinate system origin is the upper-left corner of the drawing area, with the X axis
in the horizontal direction (from left to right) and the Y axis in the vertical direction (from top to
bottom) as shown in the following diagram, with units as the percentage of the distance along the
axis.
To add a tie point, click the mouse cursor in the drawing area over the approximate location of
the tie point within the image. A numbered icon will appear, which represents the tie point. At
the same time, a corresponding entry (consisting of the ID number and coordinates) will appear
in the tie point list on the right side of the window.
To move a tie point, position the mouse cursor on top of the point in the drawing area; then hold
the LMB down and drag the tie point to the new position, release the LMB. To manually edit the
exact positional coordinates of a tie point, click in the coordinate text field in the tie point list.
Type your changes with the keyboard, followed by a carriage return. The tie point in the drawing
area automatically moves to the new position you entered.
To delete a tie point, click on it in the drawing area with the RMB. The tie point disappears from
both the drawing area and the tie point list.
Page 27-6 SOCET SET

The Tie Point Pattern window’s selections are as follows:
SELECT TO
ID - row number Display the identification number of the tie points. The tie points are
numbered in the order you create them. You cannot edit this field.
X(%), Y(%) Display the X and Y coordinates of a tie point. You can edit these fields by
typing the new coordinate with the keyboard, followed by a carriage
return. The location of the point updates automatically.
Number of Points Display the current number of tie points in the drawing area.
Save As Save the tie point pattern file with a different name.
OK Record the tie point positions in the currently open tie point pattern file
and closes the window.
Cancel Close the window and ignores any changes you made.
27.2.5 Start Interactive

After you have finished the automatic phase of Automatic Point Measurement, you will proceed
to the interactive phase. Automatic Point Measurement for APM allows you to remeasure the tie
points that could not be measured automatically.
The Interactive Point Measurement for APM window has two scrollable tables. The upper table
lists all points that need to be interactively measured. The lower table shows the image associated
with each point. Pressing the LMB in the point table will load all measured and unmeasured
images for the selected point. Pressing the RMB in the image point table allows toggling of each
field in the table.
SOCET SET Page 27-7

The Interactive Point Measurement for APM window’s selection are as follows:
SELECT MOUSE DESCRIPTION
Point List N/A Lists the total number of points.
Find Point N/A Highlights the first match in the point table and moves the extraction
cursor to the point. This will move to the row upon typing.
Exact Match N/A Selects whether or not you are searching for an exact match in the Find
Point field. If this is off, it will find the first partial match.
Point ID RMB Name of point. Up to 30 alphanumeric characters, separated by

underscores with no spaces.
NOTE: To add or delete, use the RMB.
Type LMB Indicates type of point.

NOTE: To toggle to the desired point type, use the LMB.
Use LMB This filed is used to identify whether to use or not use this point.
NOTE: To toggle on and off, use the LMB.
Image ID RMB Name of Image.

NOTE: To add or delete, use the RMB.
Master RMB Determine which images are loaded left and right to the extraction monitor.
NOTE: To select, Left, Right, or switch Left with Right image, use
the RMB.
Lock LMB Toggles the image lock on or off. An X indicates Locked.

NOTE: To toggle Lock or Unlock, use the LMB.
Measured or LMB Toggles the image from measured to unmeasured.

<Alt> + M NOTE: To Remeasure, use the LMB
Auto Two N/A Automatically finds conjugate point between left master image and image
in active viewport. For example, if the current view is view3, Auto Two
will try to correlate the left master image with the imaged loaded in view 3.
Page 27-8 SOCET SET

Sample or KP/ N/A Records the position of the extraction cursor in the left master image and
the position of the extraction cursor in the active view.
Auto All or N/A If you lock one cursor in one image, and unlock the cursor in the other
<Alt> + A image, and click this button, Interactive Point Measurement attempts to
automatically find the conjugate point in all unmeasured images. Use this
capability to move a point after an initial solution is run or when the
accuracy of the underlying model is reasonably good. If the model is not
good, one or more images may fail to remeasure. These remain
unmeasured list and should be re-measured manually.
Save Save all image measurement and ground points to disk
Close Closes the window without saving.
27.2.6 Tie Point Pattern File

The [Optional] tie point pattern represents an initial set of search locations that will be tested
between each pair of overlapping images as APM proceeds. It is intended to give APM a hint on
where to look for tie points, but does not indicate the final arrangement of points that APM will
produce. The determining factors for selecting the arrangement of tie points are the amount and
orientation of the overlap regions between images.
In the simplest case of 60% forward lap and 30% side lap in a rectangular block, the standard 3x3
pattern can be used. This pattern directs APM to find three tie points along any of its sides. With
60% forward overlap the closest image will share six points with the first image, while the next
image over will share three with the first.
60% F
or ward O
verlap
Master Image
30% Side Lap

between Strips
Tie Point
Slave Images
Assuming the approximate math models are reasonable, APM should be able to find a sufficient
number of points in this minimum case to allow a relative solution. However, in reality the
approximate data may be inaccurate especially if the images were imported as “Unknown.” The
effect of this is that the overlap areas will contain areas outside the pixel data and points will fail
to correlate. In other cases, the overlap areas may be widely varied across or between strips—for
some sensors these areas may be irregular polygons or just barely clip the edge of an overlapping
image making correlation, which requires a 15 to 128 pixel “window,” impossible.
One approach is to add many more tie point candidate locations distributed across each image,
and try to measure as many points as possible regardless of the lap percentage and orientation.
This results in many redundant points and many failed points. Using this “shotgun” approach
trades computer processing time for manual editing and remeasurement time. Even if many points
fail to measure, if enough have been measured to reach a solution, the failures can just be ignored
SOCET SET Page 27-9

without remeasurement. Care should be taken to insure that a “reasonable” distribution of

successful points is achieved.
Even if a large number of points fail, the remaining number are usually more than sufficient to
allow reaching a solution. All points do not need to be measured before a solution can be
executed. Unmeasured points are ignored by the solution algorithm.
27.2.6.1 Non-Square Images

If you have images which are much longer in one dimension than the other, i.e. non-square, APM will
use the tie point pattern differently. This logic engages when a side is 20% larger than the other. In this
case APM automatically repeats the tie point pattern along the entire image. For example, if an image
is 10,000 pixels by 30,000 pixels, the pattern will be repeated three times along the longest dimension.
For ADS40 images, it is recommended that the ads40_1000.tpp tie-point pattern file be used. The
ads40_1000.tpp is designed to be compatible with the default value of 1000 pixels for the Post
Interval during Import. Also, available is ads40_5000.tpp tie-point pattern which is compatible
with Post Interval of 5000 pixels.
27.2.7 Required Points and Redundancy

How many points are required by the solution logic? The answer depends on the number of image
parameters adjusted for the particular sensor, the number of images the points have in common,
and the availability of ground control points. You can specify which parameters to adjust during
the solution. Normally you will adjust using the default parameters, but you may exclude
parameters from adjustment by toggling the Adjust button to No.
In Setup’s Image Parameters window you can specify the accuracies of each of the sensor model
parameters. In this manner, you can weight certain model parameters over others during the
solution. Setup provides default values for the sensor model parameter accuracies.
The solution logic uses a technique known as a least squares bundle adjustment, which solves a
set of n+1 linear equations in n unknowns. The unknowns in the equations that must be solved
are the image parameters (camera angles, location, etc.) and the adjusted ground locations for tie
points. To determine the minimum number of measured points required to reach a solution, you
first multiply the number of images in the block by the number of image parameters that are to
be adjusted for each image. Only the parameters turned on using the Adjust flag in the Image Data
window need to be counted. For example, a block with 4 Frame sensor images (6 parameters)
would contribute 24 unknowns. Each tie point contributes 3 unknowns (ground x,y,z) but
provides 2 knowns (line, sample) for each image it is measured on. So, for a tie point measured
on 1 pair it would contribute 4 knowns (2 x number of images) - 3 unknowns = +1 known.
Therefore, if you only measured tie points (no control) on just pairs of the 4 images you would
need 25 tie points to offset the 24 unknowns of the image parameters. If you measure multiray tie
points (3 or more overlaps) it reduces the number of required points since the point always
contributes three unknowns but contributes 2 knowns for each image it is measured on. A six ray
point would contribute 12 knowns - 3 unknowns = +9 knowns. Of course a six image Frame block
would contribute 6 x 6 = 36 unknowns. This would suggest that you could solve a six image
overlapping block with just 5 six ray tie points as a minimum. Usually there is not sufficient
overlap between all the images in a block to make this possible, but it illustrates the point.
Adding control reduces the number of needed points, since some or all the ground coordinates of
control points are considered known rather than unknown and do not need to be solved for. For
example, an XYZ control point measured on a pair of images contributes 4 knowns (2 x 2 images)
- 0 unknowns = +4 knowns. A vertical control point (Z is known) would contribute 4 knowns (2

x 2 images) - 2 unknowns (X,Y) = +2 knowns. The contribution of multiray control points adds
to the total of knowns just as in the tie point case.
Of course, these calculations give the absolute minimum number of points required to solve the
bundle, but it is recommended that at least 50% redundant points be measured to give a more
consistent and meaningful residual RMS value. The percent redundancy can be determined in
Simultaneous Solve by taking the number of redundant points reported on the menu, dividing by
the total number of ground points and treating as a percent.
Insufficient redundancy is evidenced by deceptively small residual RMS values when the number
of redundant points is less than 50%. As the redundancy exceeds about 50%, the RMS approaches
some RMS limit and additional points are not beneficial as shown in the graph below:
Worst (highest) residual RMS for a given set of measurements
Residual limit
Residual Diminishing benefit of adding more
points
Low value due

to low redundancy 50%
Percent Redundant Points
The recommended approach is to use a somewhat denser pattern than the minimum needed,
ignore any failed points, and solve with the resulting good points. In most cases you won’t need
to remeasure any points, but it’s worthwhile to interactively review the results from APM just to
insure that there weren’t some erroneous, false correlations measured.
27.2.8 Automatic Selection of Candidate Point Locations

The tie point pattern is just the starting point for APM. The pattern gives APM a proportional
line/sample location to begin its search for tie points but several more steps are first required. The
processing is guided by information in files located in <install_path>/internal_dbs/
HATS. These are known as strategy files and are designated as *.apm_strat and *.strat.
APM first compares each image footprint in the block with every other image and determines the
extent of every overlap area. It then begins to search forward from the first “master” image
through each overlapping “slave” image looking for good tie points at each of the tie point pattern
locations. It generates a coarse grid of candidate locations around each image position and
correlates these grid points until it finds points that give the best correlation results across the
overlap area. From this coarse grid of points, it determines the minimum set of best points and
generates a denser cluster of points around each best point. These clusters are further correlated
and the final best location of the point is determined from the interpolated results of the cluster.
The density of the coarse and cluster spacing and line/sample increments used between the
candidate points determines how many correlations are performed, and thus how long APM takes
to complete.
The performance trade-off is that with very dense spacing, APM will almost always find and
measure a valid point even with rough terrain or oblique imagery. The downside is that it will
take geometrically more time to execute as the density is increased in line and sample. Using
empirical methods the default strategy files have been adjusted to produce a reasonable
compromise between yield and speed. The parameters of the strategy files can be edited to suit
your particular needs.

27.2.9 Understanding APM Strategy Files

The apm.apm_strat file identifies the coarse and cluster strategy files used during the tie point
search. The coarse grid line and sample spacing and cluster grid spacing determines the distance
between each of the grid points and hence its size. The line and sample transfer distance
determines how far APM is allowed to move a tie point from its initial pattern position. With
smaller grids and tighter spacing APM can find points closer to the edges of images and in very
small overlap areas. Of course, the processing time increases as more candidate points are
generated.
A second apm_strat file (apm_fast.apm_strat) is available for use with conventionally overlapped
frame images. This strategy can reduce processing time by 75% with little decrease in yield when
working with flat to sloping frame imagery having minimal obliquity and standard 60–30%
overlap.
The coarse.strat and cluster.strat files control the hierarchical correlation of image patches to
locate conjugate image points with subpixel accuracy. Each file contains blocks of parameters,
one for each “pass” that it executes. A pass is defined as the correlation of a pair of images at a
specific minification level—also known as the Reduced Resolution Data Set or RRDS level.
Factors which control the performance of the correlation are the number of passes, the patch size,
and the search distance limits. Most of these parameters have been determined empirically and
should not need to be modified. 2D correlation is used throughout APM because it cannot make
any assumptions about the degree of Y-parallax in the image patches.
APM first does an initial check to insure that a full set of minified images exist for the images to
be correlated. A common error is to attempt APM without having the minified images available
(see the section on “Digicam Triangulation”). The coarse.strat strategy uses four passes from
128:1 to 16:1 while the cluster.strat currently uses five passes from 16:1 to 1:1. If particular
minification levels are not available, it is possible to copy and modify the strategy files to
accommodate the available levels. The number of passes can be reduced and/or the RRDS
parameter can be changed for each pass to reflect the available levels. The modified strat files
should be uniquely named, and a copy of the apm.apm_strat file should be edited to indicate the
new strategy files you create. Then the new apm.apm_strat file you copied can be selected in
APM before starting.
The remaining strategy file parameters should typically never need to be changed, they control
the logic that determines the acceptability of correlation, and have been determined empirically
to work with a variety of pixel data types. Modifying these parameters usually results in either a
decrease in the number of valid correlations or an increase in the number of false correlations that
get passed, both of which can reduce the utility of the correlation method.
For ADS40 images, it is recommended to use the

ads40.apm_strat strategy.
27.2.10 APM Performance

For most sensor types APM should be able to measure 80–100% of the candidate tie points. It
should not be necessary to remeasure points manually if a sufficient number of redundant points
were measured. In most cases, the unmeasured points are the result of APM attempting to locate
a point just off or very close to the edge of a slave image and failing to correlate—these failed
points are ignored during the solution.

After APM finishes the automatic phase, you use the interactive phase to manually correct
blunders. You do not have to correct every point that APM failed on: you only have to correct
enough points for the Solve process. The interactive process will automatically select points for
you to ensure that there is at least one measured point in each “cell” of a user-defined grid
overlaying the image. The cell dimensions are defined by two parameters in the xxx.apm_strat
file, “MIN_GRID_VERT” and “MIN_GRID_HORZ.” The default is a 3x3 grid but these can be
edited if a denser check grid is desired. For example, if you use a 3x3 grid (default) then each
image should have a measured point in each of the nine cells unless the image was at the boundary
of the block and is not overlapped in the cell area. If a cell has only one point and it is unmeasured,
you are positioned at that point and can remeasure it manually. Again, when a sufficient number
of redundant points are measured by APM, it should not be necessary to remeasure any points
manually based on this logic.
Performance profiling of APM shows that 70% of the processing time is spent performing the
correlation matrix operations. As the density of the grids is increased, or the spacing between
them reduced, the amount of processing increases geometrically.
A good recommendation is to make a few test automatic measurements using IPM before
executing APM. Use the Auto Meas function in IPM and sample a pair of images—then examine
the Z (elevation) for reasonableness. If the Auto Meas fails repeatedly, or the sampled ground
elevation is negative, or much above or below the mean elevation for the project, it may indicate
an error was made in the Setup parameters; typically the aircraft altitude or film size. The Exterior
Initialization may have generated a very bad set of approximate sensor models, which will
ultimately cause APM to fail to measure many points. It may be the result of a misplaced or
erroneous control point, if you have included these in the initial gpf. It’s better to discover this
early on rather than waiting for APM to complete only to find most of the points failed to
measure.
APM can experience problems when processing imagery that has been imported and rectified
prior to being controlled. This is due to the fact that the image pixel data is remapped dynamically
by the rectification coefficients within a non-rectified image footprint that circumscribes it. This
causes APM to try to locate points in the areas outside the pixel boundaries. If the rectification
does not rotate or remap the image too much, the footprint overlap problem is not significant. If
the initial images are very oblique or require significant rotation, it will effect APM adversely.
One way to check this is to load the rectified images and use the Image Information tool to view
the graphical footprints. If they do not fit the edges of the pixel data within about 15–20 degrees
of rotation, APM may have problems. APM of the unrectified images usually locates enough
points, even in somewhat oblique images, to get to an initial solution. Additional tie and control
points can be added afterwards to add redundancy and improve accuracy.
27.2.11 Using manual.apm_strat strategy file

APM can be optionally used with a special strategy file, manual.apm_strat, which will generate
tie point locations, but not correlate and measure them. This can be useful if you have a small
block and just want to distribute a small number of points in the image overlap areas for manual
measurement. With a reasonably good approximate M a t h M o d e l , the points should be close
enough to a common location to visually identify and measure quickly without relying on the full
correlation processing. If the math model is not very good, it may be difficult to find the
C o n j u g a t e P o i n t s visually without a lot of zooming and recentering. It is also useful for
generating tie point candidates when triangulating mixed sensor types which cannot be
automatically correlated due to the dissimilar image pixel characteristics.

27.3 Interactive Point Measurement

You use Interactive Point Measurement to review and measure control points and tie points used
by Triangulation. There are several situations where you run Interactive Point Measurement:
1. To review the results of Automatic Point Measurement.
2. To define control points (this action is independent of imagery).
3. To measure control points on imagery.
4. To measure tie points (to supplement Automatic Point Measurement) on imagery.
5. To review control points and tie points after Solve to fix blunders.
27.3.1 IPM Mode

IPM has several modes of operation that alter the default behavior. Several modes may be active
simultaneously. These modes are available from the IPM settings menu.
27.3.1.1 Model OFF / Model ON

Model ON mode is used to restrict IPM to ground points that fall within the stereo overlap of the
image pair loaded in the main image display. In Model ON mode, when the Up Arrow and Down
Arrow are pressed IPM skips points that are not in the current stereo model, and no new imagery
is loaded to the main image display. Additional viewports may be created if the Enable Multi-
Image Display option on the MST Main Menu is checked and review mode is off.
The Find Point option may be used to move to any points falling outside the model. Moving to a
point that is outside the stereo overlap causes IPM to load new imagery.
The default mode at IPM startup is Model OFF mode.
27.3.1.2 Review OFF / Review ON

Review mode causes IPM to visit each ground point without actually loading imagery and moving
the cursor to the ground location of the point. This allows you to quickly review the measured
and unmeasured images for a ground point, to determine what measurements have been
performed. Using Review mode in combination with Auto Image List mode allows you to easily
check if each ground point has been measured in all possible images. Point measurement cannot
be performed in Review mode.
The default mode at IPM startup Review OFF.
27.3.1.3 Automatic Image List

Auto Img List OFF requires that the user manually determine the images in which the ground
point appears, and add these to the Image Point list by clicking the RMB within the Image ID field
and selecting Add. Once the position and orientation of each image is initialized, and is
approximately known relative to the datum (usually defined by the ground control), Auto Img List
mode can be activated. This mode causes IPM to automatically compute which images the current
ground point appears in, and automatically adds the images to the Image Point list. The
computations are based on the current image position and orientation, so the results depend on
the accuracy of this information for each image. Activating Auto Img List mode before the
imagery is positioned and oriented relative to the datum may result in no images being found for
a ground point. However, images added by APM are always included in the list.

The default mode at IPM startup is Auto Img List OFF.
27.3.2 Terminology: Ground Points and Image Points

Before running IPM, you should have a clear understanding of the terminology.
Control Points are points with known ground coordinates (XYZ, or XY, or Z). You must enter
the location into the IPM window. Triangulation stores this data in the project Ground Point File.
You must also use the extraction cursor to identify the control point in all the images in which the
point is located. The image space positions are stored in the Image Point Files (IPF).
Tie Points are points on the ground that you can identify in two or more overlapping images, but
you don’t know the ground coordinate. You use the extraction cursor to identify the point in all
the overlapping images. The image locations are stored in the Image Point Files (IPF). An entry
is created in the Ground Point File (GPF) for each tie point. APM will create tie points
automatically. See “Tie Point Pattern File” on page 27-9 for details.
Check Points are points with known ground location (XYZ) that are not used in the solution, but
are provided to help the operator perform a quality control check after the solution is complete.
Check points are also called diagnostic points. See “Quality Statistics” on page 61-26 for details.
Ground Point is an umbrella term that includes Control Points, Tie Points, and Check Points.
Image points are the image space locations (in lines and sample coordinates) of Ground Points.
A single image point is stored for every instance of a ground point in an image. For example, if
a tie point is located in 4 overlapping images, and you measure it in 3 of the images, then 3 image
points are stored. Image points are stored in the IPF files. An image point must be associated with
some ground point. If you somehow have points in IPF files which are not reflected in the GPF
file, transfer them using the Reset > Transfer Image Points menu selection.
27.3.3 Control Point Editor

The Control Point Editor is an alternative way to measure control points.

27.3.4 IPM Window
The Interactive Point Measurement window is divided into two major sections, Ground Point, and
Image Point.
27.3.4.1 Ground Point Selection

Ground Point consists of two tables containing ground point information. The upper table lists all
ground points in the current Ground Point File. Clicking the LMB on any point in the table moves
the extraction cursor to that point and loads the measured and unmeasured images.
Interactive Point Measurement window’s selections are as follows:
Settings Clicking Settings will open the Settings for IPM window.
Find Point N/A Highlights the first match in the point table and moves the extraction
cursor to the point. This will move to the row upon typing.
Exact Match N/A Selects whether or not you are searching for an exact match in the Find
Point field. If this is off, it will find the first partial match.

Point ID or RMB Name of point. Up to 40 alphanumeric characters, separated by

Insert (to Add underscores with no spaces.
pt.) NOTE: To add or delete, use the LMB.
To change the point name, it’s better to use Review Mode.
Type LMB Indicates type of point.

NOTE: To toggle to the desired point type, use the RMB.
Use LMB This field is used to identify whether to use or not use this point in the
solution.
NOTE: To toggle on and off, use the LMB.
Coordinates N/A Ground point location. The column labels are consistent with the project
coordinate system. All values are editable.
Accuracy N/A Ground point accuracy, given in the project units (in meters or feet; for
geographic projects, the value is in Z coordinate project units). The values
are editable, and can be copied to all other control points in the current
ground point file.
27.3.4.2 Image Point Section

This area contains the image status list which displays all images containing the selected ground
point. The point status is either locked or unlocked, measured or unmeasured. An X in the
appropriate field indicates locked or measured. The Master field indicates which images are
loaded left or right. The left master image is always used as the master when Auto Two or Auto
All is selected.
Interactive Point Measurement window’s selections are as follows:
Image ID RMB Name of Image.

NOTE: Use the RMB to add or delete images.
Master RMB Determine which images are loaded left and right to the extraction monitor.
NOTE: To select, Left, Right, or switch Left with Right image, use
the RMB.
Lock or LMB Toggles the image lock on or off. An X indicates locked.

Left/Right NOTE: To toggle Lock or Unlock, use the LMB.
Arrows
Measured LMB Toggles the image from measured to unmeasured. An X indicates
measured.
NOTE: To Remeasure, use the LMB
Auto Two or N/A Automatically finds conjugate points between left master image and the
<Alt> + M image in the current viewport. For example, if the current view is view3,
Auto Two will try to correlate the left master image with the image loaded
in view3.
Sample or / N/A Records the position of the extraction cursor in the left master image and
the position of the cursor in the active view.

Auto All or N/A If you lock the cursor in one of the master images, and unlock the cursor in
<Alt> + A the other images, and click this button, Interactive Point Measurement
automatically finds the conjugate point in all unmeasured images, and
transfers the point to these images. Use this capability to move a point after
an initial solution is run or when the accuracy of the underlying model is
reasonably good. If the model is not good, one or more images may fail to
remeasure. These remain unmeasured and should be re-measured
manually.
Save Saves all image measurements and ground points to disk.
27.3.4.3 Settings for IPM

Settings for IPM is used to allow you to make changes to the Ground file, Coordinate system and
the Datum. Additional selections include changing elevation system, and mode selections. To
open this window, click Settings on the Interactive Point Measurement window.
Settings for IPM window’s selections are as follows:
SELECT TO
Ground File Allow you to select Ground Point File from the list provided. Selection
will be displayed. Once the file has been selected, the current ground point
file can be either merged or replaced with the selected file.
View System Prompt you to select an alternate coordinate system from the current
project for display and entry of the ground point coordinate data.
View Datum Prompt you to select an alternate reference datum from the current project.
Interactive Point Measurement will display the ground points in the new
datum, and will convert the ground points into the project datum before
writing them to the Ground Point File.

SELECT TO
Elevation BLANK SPACE

Ellipsoid Display and accepts Z coordinate data referenced to the current datum
BLANK SPACE ellipsoid.
MSL Display and accepts Z coordinate data referenced to Mean Sea Level.
Selects BLANK SPACE

Review Set the mode to only update the point information as you move point to
BLANK SPACE point. This can be used to quickly step through points without the image
BLANK SPACE loading delay.
Auto Img List Allow the system to automatically adds image(s) to the Image Point list,
otherwise you are required to manually add image(s) to the Image Point
BLANK SPACE list.
Copy Accuracy to All Enable this choice will change the accuracy of all Control Points.
Control Points
BLANK SPACE
BLANK SPACE
BLANK SPACE
Skip Valid Points
Use this feature to review all points not having the Use box checked.
BLANK SPACE
BLANK SPACE
Model On
Toggle this button to enable or disable the model checking feature. With
model check enabled the Up Arrow and Down Arrow buttons skip to the
next ground point that falls within either the current left or right image.
Use this feature to measure all points within a given pair of images.
Close Close window.
27.3.4.4 Execution - Interactive Point Measurement

This section describes the sequence of steps to follow when running Interactive Point
Measurement.
It is a good idea to find the ground control markers in the image before you start measuring. It is
very helpful to have a survey map or chart that shows the ground control locations. Surveyors
often use one of the following as ground control markers:
• A cross or T-shaped figure painted on the ground
• Some notable geographic feature, such as a bridge, hilltop, street intersection,
building, flagpole, walkways, etc.
27.3.4.5 Execution - Sequence

To start Interactive Point Measurement, click Interactive Point Measurement on the Automated
Triangulation/Full Block window.
On start-up, Interactive Point Measurement performs the following processing:
• Loads the Point Files previously specified in the Setup window.

• Displays the data for the points in the file, if any.

• Displays the coordinates and accuracies of the first point.
• Determines the images to load for the first ground point and displays their names in
the Image Point list. Images without an entry for the point in their image point file
are not shown.
• Loads images with their status to the master monitor and other viewports if your
system supports the multi-image display capability.
• Moves the extraction cursor to the ground point in the images if sensor parameters
are valid.
• If only one image is identified in the triangulation file this image is loaded to the
left eye and the right eye is ignored for measurement. This allows measurement of
one or two images at a time as desired.
27.3.4.6 Creating a Ground Point File List

1. Enter the Point ID for the current ground point.
Point ID names cannot be longer than 40 characters.
2. If the point is a control point enter the ground coordinates as required and check the use
box. If this is to be a tie-point you don’t need to enter any ground point coordinates since
they will be extracted from the controlled imagery.
3. Set the point type by clicking on the pull-down or clicking the mouse in the box.
4. If you know in advance what images you wish to measure, in the Image Point list select to
the Image ID and click Add... using the RMB. Select one or more images from the list, then
click OK.
5. Move the extraction cursor to the next desired location and point to Point ID and select
Add... using the RMB. Repeat steps 1-4 for each remaining point desired.
27.3.4.7 Measuring Images

1. If you are using an existing control point file for the first time the left and right loaded
images are added to the image list for each point by default. If you wish to measure
additional images Right click on Image ID and select Add... to display a list of images
available for measurement of control or tie points.
2. Select one or more images from the list then click OK. The selected image(s) are added to
the Image Point list.
3. Toggle the cursor from the mouse cursor to the extraction cursor. (Click the middle button
on the track ball or press the F3 key on the keyboard).
4. In the left image, position the extraction cursor on the point you want to measure.
5. To measure a ground control point, find the ground control marker in the image and
position the extraction cursor on it.
6. To measure a tie point, pick a piece of image detail in the left image and position the
extraction cursor on it.

Left Image Right Image
Extraction cursor in the

left image is on the
lower-left corner of the cursor cursor
triangular feature.
7. Lock the left image extraction cursor using one of the following methods:
a. Toggle back to the mouse cursor, and click LMB on the left image’s lock field and
check Lock in the Interactive Point Measurement window. Then toggle back to the
extraction cursor.
b. Press the left arrow key on the keyboard.
c. Click the RMB.
8. In the right image, position the extraction cursor on exactly the same piece of image detail
as in the left image (either the ground control point or the tie point).
Extraction cursor is
locked in the left
image; cursor
Extraction cursor in the cursor

right image is
positioned on the
corresponding piece of
image detail.

9. Sample the point using one of the following methods:

a. Toggle back to the mouse cursor, and click Sample in the Interactive Point
Measurement window. Then toggle back to the extraction cursor.
b. Press the “/” key on the keyboard
c. Click the LMB.
The fastest way to measure points is by using the mouse

buttons in the following order: Right (lock left image), Middle
(Auto All, automatic measure point).
27.3.4.8 Reviewing and Correcting Measurements

1. You can force Interactive Point Measurement to position the extraction cursor at any
measured image coordinate by entering the Point ID in the Find point field or by scrolling
through the ground point list. If you want to re-measure a point in an image select the
image, click the RMB in the measurement field, then click REMEASURE. Sample the
point using the technique described in the section on measuring images. See “Measuring
Images” on page 27-20. Only the unmeasured image point will be remeasured.
2. If you want to re-measure a point in all images, click LMB on the Point ID in the Image
Point list, multi-select the measured images by holding down the shift key and LMB on first
and last images. Then RMB click in the measured field and click REMEASURE.
3. If you want to automatically find the conjugate point in a pair of images, position the
extraction cursor on the desired point in the master left image and lock the cursor. See
“Measuring Images” on page 27-20, step 7.
Position the right extraction cursor over the conjugate point in the right eye and click Auto
Two if the multi-view mode is not available. Once the point has been automatically
remeasured, click Sample (or click LMB) to make the measurement, if acceptable.
Multiple images can be measured all at once by following the above procedure and clicking
Auto All rather than Auto Two. Images which fail to measure will remain on the
unmeasured list and can be manually measured as desired.
4. When reviewing a large list of ground points for errors, you may wish to first enable model
checking by clicking Model On from the Settings window. In this mode clicking the up/
down arrows skips over ground points that are not contained in the footprints of the
currently loaded left and right images.
5. To save work as points are measured, toggle the cursor from the extraction cursor to the
mouse cursor (press the center button on the track ball or press the F3 key on the keyboard)
and click Save. This is advised to prevent data loss from a system failure or other
unexpected events.
6. To exit IPM toggle the cursor from the extraction cursor back to the mouse cursor (press
the center button on the track ball or press the F3 key on the keyboard) and click Close. If
you have changed any of the ground or image point file data you will be prompted to save
the stored data to disk file.
27.4 Accuracy
Simultaneous Solve requires accuracy values for the image coordinates, ground coordinates, and
sensor model parameters. Both Automatic and Interactive Point Measurement provide these
values for the image coordinates; Interactive Point Measurement provides the accuracy values for
the ground coordinates, and Setup provides the accuracy values for the sensor model parameters.

27.4.1 Image Points

Interactive Point Measurement assigns the accuracy of an image point to 0.5 pixels. Automatic
Point Measurement assigns the accuracy of a tie point based on the performance of the matching
algorithms.
27.4.2 Control Points

In Interactive Point Measurement you can specify accuracy figures for control points. Higher
accuracies (i.e., small values) indicate that Simultaneous Solve should treat the data as more
reliable (hence adjust it less) than lower accuracy data. For example, Simultaneous Solve will
weight a ground control point with an accuracy of 5 meters more heavily than a ground control
point with an accuracy of 20 meters.
It is important that you input reasonable values for the ground

control point accuracies since they can influence the
correctness of the triangulation solution.
You can adjust the accuracy of each ground control point coordinate (X, Y or Z) individually. The
units of the accuracy values are in the project ground units (in geographic projects, these are the
Z-coordinate units). You can exclude a ground control point from the triangulation solution by
clicking LMB on column “Use.”
If you are getting your ground control points from a map, you should set the accuracies
accordingly. Horizontal accuracy is approximately 25m for a 1:50,000 scale map; vertical
accuracy is about one half the contour interval (1/10 the contour interval for benchmarks).
27.4.3 How to Remove Y-Parallax

Y-parallax is the vertical offset between the left cursor and right cursor. Ideally, you will have no
Y-parallax. However, if your sensor models are not yet properly controlled, you may encounter
non-zero Y-parallax during your point measurement operations.
Y-parallax does not prohibit you from performing point measurement, but it does reduce your
efficiency because you must compensate for the vertical offset in each point you measure.
This section provides some tips on how to negate the Y-parallax during your measurements.
27.4.3.1 Manual Y-Parallax Removal

The point measurement technique consists of first removing the X-parallax, locking the cursor in
one of the images, and then removing the Y-parallax. The specific steps for doing this are as
follows:

1. On the Display Utility window, set the Cursor control to Fixed Image.
cursor
Left and Right image
with x and Y-parallaxes.
Notice cursor position cursor
with respect to features.
2. Remove the X-parallax by moving the Z control (the track ball) up or down so that the
extraction cursor in each image lines up vertically with the same piece of image detail.
Left and Right image after
removing X-parallax.
cursor cursor
Notice there is no
X-displacement with
respect to the lower-left
corner of the triangular
feature.
3. In the left image, pick a piece of image detail and position the extraction cursor on it by
moving the mouse.
4. Lock the left image extraction cursor.
5. In the right image, position the extraction cursor on exactly the same piece of image detail
as in the left image.
Left and Right image after cursor

removing Y-parallax.
cursor
Notice cursor position is
on lower left corner of the
triangular feature.
6. Measure the point by clicking Sample in the Interactive Point Measurement window.
27.4.4 Automatic Y-Parallax Removal

Interactive Point Measurement provides an automatic parallax removal capability for use in
measuring conjugate pairs of points in stereo image pairs. The specific steps for doing this are as
follows:

1. In the left image, pick a piece of image detail and position the extraction cursor on it.
2. Lock the left image extraction cursor.
3. Click Auto Two. Interactive Point Measurement begins searching for the conjugate point in
the right image. Upon finding the conjugate point, Interactive Point Measurement locks
both images for you. The initial location in the right image should be approximately near
the same image detail in the left image to permit the automatic location to succeed. If the
distance is too great the automatic measurement displays a message that it was unable to
locate the conjugate point.
4. If you are satisfied with the position of the extraction cursor in the images, measure the
point by clicking Sample in the Interactive Point Measurement window. If you are not
satisfied with the position of the extraction cursor, unlock both images and go back to
step 2.
Automatic parallax removal uses a default image correlation strategy. You may specify a
different strategy by clicking APM Strategy File from the Setup, Advanced... Window. The
strategy file contains the parameters to the image correlation algorithm.
27.4.5 When to add control points

Control points can be measured either before or after executing APM. Control points will be
transferred to additional images by APM if they exist. The choice really depends on the accuracy
of the approximate math model generated when importing the images. If a control point gpf file
already exists, it can be merged with the tie points ground point file using IPM. Click IPM >
Settings > Ground File and select the desired control file. The dialog box will ask if you wish to
Replace or Merge the current and selected file. The merged file replaces the existing ground file
for the triangulation task.
If you have a large list of control points in a gpf file, you can use the Control Point Editor to create
a smaller list and save the results under a new gpf filename. This can be merged into the tie points
list as described above without modifying the original control gpf file.
Driving the cursor to the control points in IPM with Find Point may or may not work well
depending on the state of the underlying approximate math models. If the images were imported
as known and an absolute reference position for the image was specified, the ground points should
be fairly close to the cursor after the move. If the math model is only relative, the points may not
fall within the relative location footprints of the images. If a few control points can be manually
measured, you can then do an initial absolute solution which will adjust all the images into an
absolute space. Additional unmeasured ground control points can then be located more precisely
using the ground location prior to image measurement. If the initial absolute solution cannot be
executed due to insufficient points or other problems, you can still execute Exterior
Initialization—which will use the control points to offset the math model into absolute space.
This may be sufficient to allow driving to control points for measurement with more precision.
27.4.6 Adding new points

When manually adding new tie or control points, it is recommended that you first position the
cursor near the desired new location before selecting Add rather than first hitting Add and then
moving to the point.
When adding or removing images for a point, you may find the cursor is not correctly positioned
after the remaining images are redisplayed. This is due to the state of the math models before
solution. To return to the measured point locations, click on the up arrow and then the down arrow

to drive to the last measured line/sample locations which do not depend on the state of the math
models.
27.4.7 Entering Control Points in a Datum Other than the Project

Datum
By default, the datum you use to enter control points is the project datum. IPM supports user entry
of control data in any of the available SOCET SET projections, datums, and vertical reference
types. Select settings then the View System, View Datum, or Elevation format for the available
control data and enter the published x, y, z values. These are internally transformed to the format
of the current project for saving with the gpf file.
If your project has an LSR coordinate system, and the LSR is

not anchored to the earth, you should not use the datum
transformation capability.
Changing the View formats and saving does not transform the project gpf file into the displayed
format. This can be done using the Control Point Editor Save As function which will transform a
gpf file from one project format to another
27.4.8 Using Auto All

Auto All will automatically measure a point in all the images it is in. This saves a lot of time,
since you don’t have to take the time to locate the point in all images. Auto All requires that the
support data of the images be somewhat accurate, so if Auto All is not generating good tie points,
you should measure a few tie points by hand, run Solve, then return to IPM.
A second use of Auto All is to move a tie point that was generated by APM. You manually re-
sample the point in the first image of the image list, then click Auto All, and it will find the new
point in all the other images. This is useful, for example, for moving tie points on buildings or
trees to a ground position to reduce residual errors.
Auto All works as follows: it performs a single auto point measurement of the first pair of images
in the list. If this succeeds it uses the resulting new ground location to locate the new point in the
remaining images. These positions are then correlated to find the exact line/sample point location
which are updated if the correlation succeeds. The correlation processing uses a three pass
strategy. The Auto All function requires that at least two of the three passes succeeds before it
accepts the measurement. This prevents accepting erroneous points automatically. Any images
which fail to correlate will remain unmeasured and must be manually measured using Auto Two
and Sample or Sample only.
The Auto All function is dependent on the accuracy of the math model and may fail in cases where
the approximate model is imprecise. If the new ground location does not get close enough to the
correct image point to allow correlation, the point will fail. It is often used after an initial solution
is performed to move multiray points with high residuals to a better location prior to resolving.
The Auto Two function for a single point may succeed in cases where the Auto All function fails.
This is because the interactive Auto Two function only requires a single correlation pass to
succeed rather than two as required by Auto All.

27.4.9 Using Model ON

The Model ON mode in IPM is useful for measuring or reviewing points measured on a single
stereo image pair. Once you have loaded the desired pair of images, you can click Model ON.
This pair is then “remembered” as you move point to point and reloaded if necessary. IPM will
skip points that do not fall in the footprint of either of the pair.
To change the desired model pair, load the images to the left/right eye and toggle the model check
button off and on.
27.4.10 Graphical Display

The Triangulation graphical display draws point icons and residuals at the image location if
measured, or at the ground location if not measured. When Image Centers is selected, any residual
spokes will be drawn pointing to the center of the image to which it applies rather than at the angle
determined by the x,y residual components. This allows you to determine graphically which pair
of images may need to be remeasured. If IPM is active, you can drive to any tie or control point
by selecting it from the Graphics_Only display with the LMB. See “Graphical Display Window”
27.4.10.1 Execution - Sequence

Turn on Graphical Display
1. Click MST > Settings > Graphical Display
2. Start IPM.
3. Create a new view using Image Loader and load Graphics Only to it.
4. Make the Graphics Only view the active view in the display utility.
5. Toggle mouse cursor to the extraction cursor.
6. Click the LMB on a Tie or Control Point, and that point will be selected in IPM.

Chapter 28
Multi-Sensor Triangulation - Solve

Solve describes three solution types for the final
Triangulation process Initialize/Solve.
28.1 Overview
This chapter describes two parts of the triangulation process:
• Blunder Detect and Solve (4 ground points min. are needed to enable this selection)
• Simultaneous Solve (4 ground points min. are needed to enable this selection)
Blunder Detection is optional, and is only used for Frame imagery.
Simultaneous Solve is mandatory, and must be executed to finish the triangulation job. See
“Multi-Sensor Triangulation - Overview and Workflow,” Chapter 25 for instructions on when to
run these processes.
28.1.1 When to use Initialize/Solve

You use Initialize/Solve to instruct Triangulation to initialize, compute, or update the sensor
model parameters. The two solution types are:
• Blunder Detect and Solve—Updates the exterior orientation parameters by
sequentially forming the image blocks. Detects blunders during processing and
prompts you to correct them. Blunder Detect will not pass unless you have three full
(XYZ) control points measured.
• Simultaneous Solve—Updates the exterior orientation parameters using bundle block
adjustment techniques for each image’s M a t h M o d e l based on the ground control
point and tie point measurements made during Automatic Point Measurement and/
or Interactive Point Measurement. This mode is used for frame and non-frame
imagery, for single images, and for irregularly arranged image groups (not laid out
in a block formation).
28.2 Blunder Detect and Solve

Blunder Detect contains several statistical tools that access a block of imagery. Most blunder
tools only work on frame imagery, but one tool -- the Point Distribution Check, works on all
sensor types.
SOCET SET Page 28-1

Chapter 28 - Multi-Sensor Triangulation - Solve
The purpose of the Blunder Detect module is to catch and correct very large blunders that will
affect the convergence of the Simultaneous Solve module. Although it can also catch small errors
in measurement, these can be more efficiently and rigorously identified and corrected after the
Simultaneous Solve module. Also, more reliable estimates of the exterior orientation parameters
is a by-product of executing the Blunder Detect module.
This module is based on the sequential formation of the block as opposed to the simultaneous
approach in Simultaneous Solve. In this module, overlapping images are formed into
stereomodels (relative orientation), adjacent stereomodels are connected into strips, overlapping
strips are formed into a block in a floating coordinate system, and the floating block is
transformed into the ground coordinate system (absolute orientation).
Blunder Detect should be run prior to Solve only. Running

Blunder Detect after Solve can cause overwriting of the
remeasurement made during the Solve process.
Blunder Detect and Solve uses measured image coordinates to sequentially form a block of
images under a single coordinate system. It uses image measurements supplied by Automatic
Point Measurement and/or Interactive Point Measurement. It also exploits measured ground
coordinates if they are available.
Blunder Detect stores all image measurements in fiducial space in the .ipf file. The six parameter
transformation used to convert from image X and Y to film x and y is:
X = a1 + a2x + a3y Y = b1 + b2x + b3y
Where a1, a2, and a3 are the interior orientation coefficients for line and b1, b2, and b3 are the
interior orientation coefficients for sample.
Blunder Detect and Solve forms an image block sequentially with the following set of conceptual
steps:
1. Form the stereomodels (relative orientation).
2. Connect stereomodels into strips (strip formation).
3. Connect strips into a block (block formation).
4. Transform block into ground if control points are available (absolute orientation).
5. Update exterior orientation parameters (single image resection).
At each step, rigorous geometric and photogrammetric constraints are utilized to check for
blunders. They are interactively eliminated by using a semi-automatic approach with a minimum
effort on your part. As soon as you have addressed all the blunders, Blunder Detect and Solve will
prompt you to accept the results. If you do, it will automatically update the image support files to
reflect the better estimates of the exterior orientation parameters that Blunder Detect and Solve
generates.
Whenever Blunder Detect and Solve encounters a blunder it prompts you to remeasure the
erroneous points with one of four windows. The four windows correspond to the first four
processing steps given above. During image resection, erroneous points are displayed in the
triangulation message subwindow. You have to close Blunder Detect and Solve and remeasure
these points using Interactive Point Measurement (IPM).
Blunder Detect requires at least three full control points (XYZ).
Page 28-2 SOCET SET

28.2.1 Blunder Detect

Use this window to select steps you want to perform, and set all necessary thresholds for blunder
detection. The Point Distribution Check is optional and independent of all other steps: therefore
it can be skipped, while all other steps are dependent on each other, e.g. If you select Block
Transform, the other three steps - Relative Orientation, Model Connection and Strip Connection
will be automatically selected. Similarly, if you disable Relative Orientation, all steps except the
very first one (Point Distribution Check) will be automatically disabled.
The Blunder Detect & Solve window’s selections are as follows:
SELECT TO
Point Distribution Check (Optional) Select this button for point distribution checking on each image
in the block. Three radio buttons provide three patterns choices.
Relative Orientation Select this button for Relative Orientation check. The residual for
Y-parallax threshold in (mm) can be defined by the user.
Model Connection Select Model Connection between two adjacent models along a strip. This
will automatically enable the Relative Orientation check. Normalized
Residuals thresholds (X/Y/Z) and minimum points for connection of two
adjacent models can be defined by the user.
Strip Connection Select Strip Connection between adjacent strips. This will automatically
enable the previous two steps. Normalized Residuals thresholds (X/Y/Z)
and minimum points for connection of two adjacent strips can be defined
by the user.
Block Transform Select Block Transform (Absolute Orientation). This will automatically
enable the previous three steps. Normalized Residuals thresholds (X/Y/Z)
and minimum points for transformation from block to the ground can be
defined by the user.
Start Start the blunder detection for selected steps.
Cancel Return to the parent window.
SOCET SET Page 28-3

28.2.1.1 Blunder Detection Progress Report

Use this window to monitor the status of blunder detection for all steps you selected. The
percentage bar shows the processing progress of the current step. If any step fails with either
blunder existing or points needing measurement, the process will stop with the failed percentage
showing and the “Edit Failures...” button will be enabled for editing of point measurements.
The Blunder Detection Progress Report window’s selections are as follows:
SELECT TO
Functions Select and or all the following:

Point Distribution Check;
Relative Orientation;
Model Connection;
Strip Connection;
Block Transform.
Status Display one of the following:

• n/a - not selected
• PASSED - no blunders found for the step
• WORKING - is working on the current step; pending - will be
working later on
• %xx FAILED - blunder(s) exist, the process stops
Current function and Show which function is running and the percentage in progress.
Percentage bar
Stop Stop the process.
Edit Failures Pop up a report window.
Page 28-4 SOCET SET

28.2.1.2 Point Distribution Check Failure Report

Use this window to display and remeasure all images which are missing necessary points relative
to the pattern you selected.
Point Distribution Check Failure Report window’s selections are as follows:
SELECT TO
Summary Area Display the number of total images in Point Distribution Check. The table
shows the failed images with the area(s) missing points. The Point Index
map is the pattern you selected earlier.
Summary Table List Images and Missing areas, e.g 5, 6 means no point found in the area 5
and 6 of the Point Index map.
Detail Area Display a table with all points on the selected image from Summary Table.
The points on the table can be multiple selected for either toggling (On/
Off) or re-measurement.
Point ID Display the ID of points on the selected image.
State Turn On/Off, which can be toggled with the RMB.
Rays Identify the number of images the point appears on.
Point Index Display this number that refers to the area on the Point Index map.
Re-measure Point(s)... Select the point you want to re-measure, then click this button. The IPM
window will pop up for re-measuring. The Rays of the selected point
indicate how many images you will re-measure.
Close Close the window once you don’t need it any more.
SOCET SET Page 28-5

28.2.1.3 Relative Orientation Failure Report

Use this window to display all stereo pairs which exceeded the relative orientation threshold, or
are missing point(s) in the Von Gruber location(s) showed in the Point Index map. The toggle
button (State-On/Off) and Re-measure Point(s)... button in the Detail Area lets the user pick
points for remeasurement. Toggling any point(s) in the stereo pair On/Off will re-calculate
relative orientation. Multiple selection is available.
Relative Orientation Failure Report window’s selections are as follows:
SELECT TO
Summary Area Display the total number of stereo pairs in the block. The table shows
stereo pairs which either failed relative orientation or are missing point(s)
in the Von Gruber locations. The Point Index map shows the Von Gruber
location on the overlapping area of a stereo pair.
Summary Table List stereo pairs, number of points with a larger residual than the threshold,
and Von Gruber locations missed points.
Detail Area Provide an option to show Y-Parallax residuals in microns or Normalized

Parallax without unit.
Table displays all points on the selected stereo pair from Summary Table.
Button Re-measure Point(s)... is for re-measuring point. Points on the table
can be multiple selected for either toggling (On/Off) or re-measurement.
Point ID Display ID of points on the selected stereo pairs.
State Display On/Off, which can be toggled back and forth with the RMB.
Y Display residuals of Y-Parallax in microns or Normalized Y-Parallax

without unit.
Rays Display the number of images the point appears on.
Point Index Display the area of the Point Index map the point is located in.
Page 28-6 SOCET SET

SELECT TO
Re-measure Point(s)... Select a point you want to re-measure, then click this button. The Single
Point Measurement window will pop up for re-measuring. The Rays of the
selected point helps you to know how many images you will re-measure
Close Close the window once you don’t need it any more.
28.2.1.4 Model Connection Failure Report

Use this window to display all models with connection points that exceed the user-defined
thresholds. Multiple selection is available for points that need to be remeasured.
Model Connection Failure Report window’s selections are as follows:
SELECT TO
Summary Area Display the number of total models in the block. The table shows model
pairs which failed to connect to adjacent models.
Summary Table List model Pairs, number of points with a larger residual than the
thresholds.
Detail Area Provide an option showing X/Y/Z residuals in microns or Normalized

Parallax without unit.
Table displays all points on the selected model pair from Summary Table.
Button Re-measure Point(s)... is for re-measuring. Points on the table can
be multiple selected for either toggling (On/Off) or re-measurements.
NOTE: There is a built-in threshold residual in Model Connection
of 3mm. the purpose is to find large blunders and flag them for the
operator. In some cases, the default normalized residual of 10 is
satisfied but the absolute check of 3mm is not. This will result in
points showing up in the Model Connection Failure Report which
meet the Normalized residual threshold but exceed the built-in
threshold.
SOCET SET Page 28-7

SELECT TO
Point ID Display the ID of points on the selected model pairs.
State Display On/Off, which can be toggled back and forth with the RBM.
X/Y/Z Display the Residuals of X/Y/Z in microns or Normalized X/Y/Z without

unit.
Rays Identify the number of images the point appears on.
Re-measure Point(s)... Select point you want to re-measure, then click this button. The Single
Point Measurement window will pop up for re-measuring. The Rays of the
selected point helps you to know how many images you will re-measure
Close Close the window once you don’t need it any more
28.2.1.5 Strip Connection Failure Report

This window is similar to the “Model Connection Failure Report” window and is used to display
strips with connection points that exceed the user defined threshold. Multiple selection is
available for points that need to be remeasured.
28.2.1.6 Block Transform Failure Report

This window is similar to the “Model Connection Failure Report” window and is used to display
control points that exceed the user-defined threshold. Multiple selection of points for remeasuring
is available.
28.2.2 Tips for Blunder Detection

Blunder detection is one of the most complex and least understood functions for users within
Triangulation. The intent of blunder is to sequentially break down the individual adjustment steps
for Frame images only and test solution points at the earliest stage before they can corrupt the
final simultaneous solution. The bundle adjustment used in Simultaneous Solve will report
relative errors as residuals, but does not always pinpoint the mismeasured point that is skewing
the solution. It is not uncommon to find a point with a large residual that appears to be well
measured when inspected.
Some users never bother to run Blunder Detection, particularly if they rely on APM to
automatically measure tie points. The only potential for blunder errors then becomes the
measuring of control points. Usually if problems in the solution occur after adding control points,
it is more productive to turn off (set USE flag to NO) control points, resolve, then add back a few
control points at a time until the bad control is determined. This is also why some users prefer to
solve the relative block (tie points only) then go back and add control points before resolving the
absolute block. This may work better than mixing control and tie points together in the initial
solution.
28.2.2.1 Common Blunders

Based on extensive experience with the triangulation process, the most frequent reason for
generating degenerate solutions (assuming sufficient points exist to reach convergence) is the
mislocation or misidentification of control points. Checks are done during user input of ground
control points to determine if the x,y values are consistent with previous entered control points.
Page 28-8 SOCET SET

This prevents the most common error of transposing the x,y coordinate during entry. However, it
is not uncommon to mislocate a control point when using hardcopy survey sheets or maps as the
ground feature reference. These problems can sometimes be detected by viewing the image
footprints after adding the control points and running Exterior Initialization. If the strips are
rotated or the images no longer overlap, it can indicate that one (or more) control points may be
mislocated.
APM can generate potential blunder points by locating them on the tops of trees or rooftops which
are not on the ground. Less likely are blunders that result from correlation ambiguities due to
coherent patterns encountered in images. Waves on bodies of water and parking lot stripes are
sometimes mismatched by the correlation logic. If a visual review of any APM tie points is
practical, these anomalies are easily detected and removed before Blunder is run.
28.2.2.2 Blunder Processing

Images are formed into models, models into strips, strips into a floating block, and the floating
block into an absolutely positioned block. All photogrammetric and geometric conditions are
checked along the way. Images corresponding to unacceptable points are automatically displayed
for remeasurement of image coordinates. The ground point file (.gpf) is updated to reflect new
estimates for unknown ground points. Also, the support files (.sup) are updated to reflect
improved camera exterior orientation values.
Blunder Detect performs the following sequence of operations:
• Update project gp_origin using control points. It is unreliable at this point.
• Update geo_scalers
• Update line/sample and fiducial x,y to be consistent, if necessary.
• Perform image resection if block has only one image.
• Check consistency between image and ground points.
• Update support file’s exterior orientation.
• Find images common to a given point.
• Transform floating block.
• Check consistency between image and ground points.
• Update support file’s exterior orientation.
• Intersect tie points and update g0.z based on tie point or control point z’s.
• Store support files and image point files.
28.2.2.3 Absolute Orientation errors

Absolute orientation performs a least squares matrix solution using the image points common to
a pair of images and the calculated relative accuracy. If there are less than three common points
between a pair of images, the solution cannot be performed.
If there are less that three control points measured, only a relative solution is possible rather than
an absolute (georeferenced) solution.
If the solution fails to converge, it may be due to the relative distribution of points, the total
number of points, or both. In most cases the only option is to add more points manually, either tie
points or control points, if an absolute solution is desired. Most of the other error messages
SOCET SET Page 28-9

returned by blunder are of interest to the software designers and indicate internal inconsistencies
within the matrix processing logic.
The “Cofactor matrix singular in transforming” error message simply means that the inversion of
the solution matrix failed because the accuracies computed for the model points are zero. This
may happen if you have ground points in the gpf file but the corresponding ipf file image
measurements weren’t found. Check to make sure that all the ipf files are still in the project
directory and have not been accidentally deleted. If they have been corrupted you can restore
them from the hats_backup directory—assuming you saved them previously.
If the ipfs have been saved after APM, the accuracies (sig_l, sig_s) will be estimates computed
within APM while the number of observations may be 0 or greater. This is because APM uses this
field to save the number of forward overlaps detected for the given point. Manually measured
points will have zeros if only one measurement was made, or the standard deviation of the sample
errors if multiple samples were made. If multiple manual samples are made without repositioning
the cursor—as usually happens with the first image of a model—the standard deviation of the
measurements, and hence the accuracy, is reported as zero for the image point. In any case,
Blunder substitutes a default accuracy (0.5) for any zero point accuracies found before preceding
so the “Cofactor matrix...” error is almost certainly due to some corruption between the ipf and
gpf point files.
Since Blunder modifies the support files using Exterior Initialization, it is recommended that any
images loaded to the monitors should be reloaded prior to making further measurements or
displaying graphics. It also is a good idea to check the resulting solution by roaming the
extraction cursor and verifying that it behaves properly for a pair of images. The previous support
files are automatically stored to the hats_backup directory and can be restored from the Reset >
Support Files > Restore From Previous on the Automated Triangulation/Full Block window,
should the current math model solution be degenerate.
28.3 Simultaneous Solve

Simultaneous Solve performs a rigorous triangulation adjustment of a block of images to refine
the estimates of their Triangulation parameters. Simultaneous Solve uses the weighted least
squares method of adjustment in an iterative manner. It is capable of simultaneous adjustment of
blocks of images taken by different sensors such as frame, panoramic, etc. It is also capable of
recovering the interior geometry of the sensors via added parameters.
Simultaneous Solve requires the following input: image coordinates of control and tie points and
their accuracies (image point files), ground coordinates of control points and their accuracies
(ground point file), estimates of Triangulation parameters and their accuracies (support files and
Triangulation file), and the interior geometry of the sensors (support files). All these data are
automatically accessed by Simultaneous Solve without your intervention.
Simultaneous Solve uses a method known as “bundle adjustment” to determine the set of
individual image parameter coefficients that minimizes the relative line/sample differences
between points measured in overlapping images. The goal is to adjust the image parameters so
that the position of a point in one image corresponds to the same point position in the other. If
ground control is included, the parameters are adjusted so that the same image point corresponds
to the same absolute position on all the overlapping images.
The method constructs a matrix of the linear equations and iteratively adjusts each of the
independent image parameters until the solution converges below a pre-defined acceptance
threshold. There are generally two problems that can happen with Simultaneous Solve: failure to
converge, and excessive RMS residual error.

When you accept the solution, Simultaneous Solve will:

• Update the residual fields in the Ground Point File.
• Update the residual fields in each of the Image Point Files.
• Update the sensor model parameters in each of the Image Support Files.
• Write a Solution Accuracy Quality Report file (with extension .rep) in the project
directory summarizing the image points, residuals, and solution quality.
• Write a second, more detailed Accuracy Summary Data report
<atffilename>.atf.utri_rep. This contains information on QA statistics
not available under the regular solve bundle adjustment method.
This window controls the execution of Simultaneous Solve. You activate this window by
selecting the Simultaneous Solve Solutions Type option on the Initialize/Solve window, then
click Start on the same window.
The Simultaneous Solve window’s selections are as follows.
SELECT TO
Math Model Display the math model selected Setup (See Adjustment Options window
in Setup for complete description.)
Iteration_of_ Display the first field contains the current iteration number. The second
field contains the current maximum number of iterations initially set to 5
by Simultaneous Solve.
# of Ground Pts. Display the number of control points including partial control.
Redundancy Display redundancy or excess information in a least squares adjustment

sense.
Image (pixels) Display the RMS of image coordinate residuals in pixels.

NOTE: If only Z points are used for control, the solve window will
only show pixel RMS, no ground X, Y or Z RMS. This is because
you need a minimum of three Z and two XY points to do a 3D
coordinate transformation.

SELECT TO
X or Long. Display the RMS of ground X-coordinate (longitude) residuals in project

units. For geographic coordinates, unit of Z-coordinate.
Y or Lat. Display the RMS of ground Y-coordinate (latitude) residuals in project

units. For geographic coordinates, unit of Z-coordinate.
Z or Elev. Display the RMS of ground Z-coordinate (elevation).
Display Residuals Activate the Display Residuals window showing a list of all points and
their residuals (See description below).
Display Report Display the .rep file generated by Solve.
Start Prompt you to save all the active files and restarts Simultaneous Solution.
Useful for removing remaining blunders.
Abort Stop Simultaneous Solve at the current iteration.
Display Parameters Activate the Display Parameters window showing a list of all parameters
that can be recovered from the adjustment (See description below).
Done Prompt you to save all the active files and exits Simultaneous Solve.
28.3.1 Multi-Sensor Triangulation Residuals

This window displays the residuals of image coordinates of all points and the residuals of ground
coordinates of all control points. The residuals are displayed in a largest to smallest order based
on image residuals.
To open this window:
1. First, click Start on the Simultaneous Solve window.
2. Once the Display Residuals button is active, click Display Residuals to open the Multi-
Sensor Triangulation Residuals window.
2nd
1st

The Display Residuals window’s selections are as follows:
SELECT TO
Point ID Identify the ground point identification from the Ground Point File.
State ON/OFF To toggle the image point on and off with the RMB and re-execute
Simultaneous Solve. This is helpful if you want to exclude points from the
solution. The On/Off settings correspond to the settings of the Valid Point
button in the Interactive Point Measurement window.
TYPE Use the RMB to change the point type to:

• A full three-dimensional control point; all 3 coordinates are
known.
• A horizontal control point; X and Y coordinates are known.
• A vertical control point. Only the Z coordinate is known.
• A tie point; all 3 coordinates are not known.
• A full three-dimensional control point that is withheld from the
solution.
• A horizontal control point that is withheld from the solution.
• A vertical control point that is withheld from the solution.
Lon/X Display the Longitude residual, in project units.
Lat/Y Display the Latitude residual, in project units.
Elev/Z Display the Height residual, in project units.
Image ID Display the name of the current Image Support File.
State MEASURED/ Use the RMB to toggle the state from MEASURED to UNMEASURED
UNMEASURED and re-execute Simultaneous Solve. This is helpful if you want to exclude
individual rays form the solution
Line Display the Line residual, in pixels.
Sample Display the Sample residual, in pixels.
Re-measure Display the Activates the remeasure option on a highlight point ID.
Done Exit the Display Residuals window.
The display residuals window provides a flexible interface to perform the following procedures:
• View lists of residuals
• Change the ground point type
• Toggle ground points ON and OFF
• Toggle individual image measurements ON and OFF
• Re-measure points
All ground points in the project (both ON and OFF) that have been measured in at least one image
are included in the list. Ground points in the OFF state appear at the end of the list. Similarly, all
image measurements (both ON and OFF) for all images in the project are included in the list.
The Display Residuals window supports multi-selection, and most operations are performed
through additional popup menus that are activated with the RMB. Multiple ground and/or image
points can be selected and operated on using the Shift and Control keys in conjunction with the
left mouse button.

The ground point type can be changed by positioning the cursor over the table cell containing the
ground point type, press the RMB, and select a new type from the popup context menu. Similarly,
ground points and image points can be deactivated or reactivated by pressing the RMB over the
table cell containing the point state, and selecting a new state from the menu popup.
Deactivating individual image points allows image measurements to be eliminated from the
solution without completely eliminating the ground point.
Ground points and image points can also be remeasured from Display Residuals, by selecting
entries in the list, and clicking Remeasure. This activates the Interactive Point Measurement
window. Click Save before closing, or your changes will not be saved.
28.3.2 Display Parameters

This window displays the list of all parameters that can be recovered in the adjustment. The
display is arranged in an image by image basis. This window is activated by clicking Display
Parameters on the Simultaneous Solve window.
The Display Parameters window’s selections are as follows:
SELECT TO
Image __ of __ Show the first field is the image index number of the parameters currently
on display. The second field is the total number of images.
Sensor Type Display the sensor model type for the current image.
Parameter Display the names of the sensor model parameters.
Adjust? Tell whether Simultaneous Solve adjusted this sensor model parameter
during the solution.
Initial Accuracy Show the standard deviation of each individual sensor parameter.
Total Adjustment Show the difference between the previous sensor model parameter value
and the new value calculated during the solution.
Prev Image Display the sensor model parameters for the previous image in the list of
images that Simultaneous Solve adjusted.
Next Image Display the sensor model parameters for the next image in the list of
images that Simultaneous Solve adjusted.
Done Close the Display Parameters window.

28.4 Relative Orientation

You can control two or more images without ground control points by relying exclusively on tie
points. This technique is called relative orientation.
Because Relative Orientation does not utilize ground control points, the triangulation solution
will not be tied to the ground, so products you generate from the imagery will not be accurate in
an absolute sense. For example, known level areas on the ground may be slanted according to the
sensor model, and this in turn may cause any Digital Terrain Models (DTM) you extract from the
imagery to be likewise tilted.
There are two things you can do to improve the results of relative orientation and thus to improve
the quality of products and measurements made afterwards:
• Always constrain the parameters of one of your input images.
• Use pseudo-control points.
28.4.1 Constrain Parameters

Set some of the sensor model parameters to be constrained during the Setup process. Constrain
all the parameters of one image, using the Image Data window.
28.4.2 Pseudo-Control Points

The triangulation solution will be better if you input one or more pseudo control points. A pseudo
control point is a point that is treated by the Solve process as a real control point, but the point’s
coordinate is only a guess.
One technique for creating a pseudo control point is to take an existing tie point, enter a
coordinate, and change the point type to control point. A second technique is to measure a new
point and set the type to control point.
You should be careful when guessing the coordinates that you enter for your pseudo control
points. If possible, refer to a map to get approximate locations. If you don’t have a map, you may
be able to use the initial sensor models (as created during the image import process) to measure
approximate image point locations.
One simple technique (which will ensure that the triangulation solution is level) is to create
several pseudo-control points in a flat area (e.g. a shoreline or a rooftop) and give them the same
Z coordinate value.
You should give the pseudo control points more weight than tie points by giving them small
(good) accuracy values.
28.4.3 Relative Orientation Execution Summary

To perform a relative orientation, use the following steps:
1. Setup the images. During Setup, constrain all the parameters of one image to be not
adjusted (use the Display Parameters window for this). Constrain at least one parameter of
all images to be not adjusted.
2. [Optional] Run Automatic Point Measurement.
3. [Optional] Run Solve (use Simultaneous Solve with the Rigorous math model type).

4. Bring up Interactive Point Measurement and Review the tie points generated by Automatic
Point Measurement. Select 3 or more points to use as the pseudo-control points. Enter
reasonable values for the XYZ locations (usually, you should leave the X and Y values
alone and only enter Z). Set the point Type to XYZ or to Z-only.
5. [Optional] If you have a region in the imagery that you know is flat: Measure one point in
a known flat area, such as along a shoreline or building top. Assign a high accuracy to this
point. Use the Z control to remove the x-parallax for this point only. Measure several more
points in the flat area, assigning them a high accuracy. Do not adjust the Z control for the
rest of these points. Measure the rest of the points throughout the image and assign them a
low accuracy. Go ahead and remove the x-parallax with the Z control for these points.
6. Repeat steps 3 to 5 as needed.
28.4.4 Solution Strategy File (.solve)

There are multiple strategy files in the <install_path>/internal_dbs/HATS directory
that can be selected to obtain a solution tailored to the user’s needs.
The default.solve file contains extensive comments on it’s use and parameter settings. This
file contains control parameters and limits used during the Simultaneous Solution process. This
solution file has its parameters set to disable the automatic editing of blunder points during
solution and the output of a full covariance file at the conclusion of the solution.
Theoretically speaking, every field in the default.solve file can be adjusted by the user to
meet the needs of a particular situation. For the user’s convenience and as examples, a few
additional strategy files are made available in the same directory with special parameter
combinations. One of these files can be selected directly to obtain results that are needed in most
cases.
If the detailed_report.solve file is used, solve information on a per iteration basis will
be contained in the report at the conclusion of the solution.
The full_covariance.solve file will enable the output of the point editing and parameter
covariance information.
The NTM_solve.solve file is optimized for the use with NTM imagery. This file should not
be used with blocks of Frame Imagery containing more than 30 images. Some of the key features
of this strategy file are Automatic Blunder Detection, and full covariance information.
The auto_blunder_detect.solve file enables the detection and removal of blunders
among the automatically generated tie points. The last parameter in a strategy file,
BLUNDER_PERCENTAGE_ESTIMATE, can be adjusted to specify the approximate
percentage of blunders among tie points. It has to be less than 50.0 percent and should be kept
below 25.0 percent in usual situations. The default value is 10.0 percent. A smaller percentage
may lead to a quick solution. It usually takes three or four times longer to run a solve with this
strategy file than with default.solve.
Ads40.solve strategy is the same as the default.solve strategy except that a single new keyword
INPUT_COVARIANCE_MODE with value DIAGONAL is added.
28.4.5 Constraint Files

Constraint Files (.cns) are used only for GPS. When images share common exposure parameters
these must be treated together and not adjusted as if they were independent. The constraint file
defines which image parameters are shared between which images and allows the solution to
adjust them in all shared images at once rather than independently for each image.

28.4.6 Failure to Converge

The solution process terminates when either convergence is detected, or the maximum number of
iterations for the process defined in the solve file is exceeded. The actual mathematical rigorous
formula to detect convergence is defined as:
m
1⁄2
∑
2
((Z – (B × T)) × W ⁄ m)
i=0
where:
T = Block_Vector containing the adjusted parameters
B = numerical partials
W = image measurement weights
Z = image residuals
Z - (BxT) = the projected image residuals
m = total number of image measurements
It is assumed that W is a column vector.
This weighted residual sum is compared as a percentage change to the previous weighted residual
sum. If it is less than the value PCT_CHANGE_FOR_CONVERG in the solve file, convergence
has been achieved. If the MAXIMUM_ITERATIONS is exceeded, convergence has not been
achieved and the solution fails.
Failures to converge are generally due to either errors

introduced in the control point data or attempting to adjust too
many image parameters.
The best strategy is to turn off the control data with the USE flag and attempt to resolve with the
tie points only. If the relative solution fails, it will be necessary to review the measurements for
blunder points. If only a minimum number of points has been measured, it is also a good idea to
add redundant, additional points either manually or by selecting a denser tie point pattern for
APM and re-running the automatic measurement tool.
If the solution is oscillating (higher or varying RMS on successive iterations), it may be due to
the fact that too many of the image parameters are correlated and not really independent. In this
case, it is recommended that you return to the Setup > Image Data menu and turn off one or more
image parameters, then re-solve. You can add back image parameters and repeat the process until
the correlated parameter is determined, and the solution converges to a reasonable RMS residual
value.
If the solution is being executed with minimal redundancy, it is possible to initially reach
convergence, but experience a failure when additional points are added. This problem was
discussed in the section on determining the minimum number of points to measure. If adding
points produces a failure when fewer points succeeds, it may be due to some characteristics of the
sensor rather than the quality of the point measurements. Certain satellite sensors collect data
during adjacent or common orbital passes at different times resulting in zero or near zero

C o n v e r g e n c e A n g l e s between image pairs. The effect on the solution is that certain terms that
should be non-zero are very near zero and produce an ill conditioned (M x M-1 = I = ~0) solution
matrix. When this occurs the best approach is to turn off (Adjust = NO) one or more of the image
parameters in one of the images in the block. This locks its values and reduces the number of
unknowns that are being solved, thus improving the apparent redundancy in the solution. If this
initial solution reaches convergence, it should be possible to turn back on the unadjusted
parameters and attempt a further solution after saving the current solution.
28.4.7 Excessive RMS residual error

The RMS of all the image residuals for the block is reported once convergence has been achieved.
The acceptability of the RMS residual error depends on the sensor type and GSD but should be
less than 1.0 pixel in most cases. Values greater than this indicate that one or more points is
mismeasured and is skewing the solution excessively.
The Display Residuals menu can be selected to view the current image and ground residuals for
all the measured points sorted by magnitude. Unfortunately, the largest residual points may or
may not be the culprit in skewing the solution.
The first strategy should be to turn off all control points and attempt a relative solution first,
unless the bad tie point is obvious.
If you examine a point with a high residual and it looks like it was well measured, you can skip
it and try other points until you find one that is mismeasured. Examine points with even numbers
of image overlaps over 2 (4, 6) and check the points between the first, third, fifth, etc. images to
make sure that the point is measured at the same location.
Also, move and remeasure points which are on rooftops or in trees. Trees tend to move somewhat
in windy conditions, or are difficult to measure accurately and distort the solution when used for
tie point locations.
It is recommended that solutions with excessive RMS error should be discarded and not Saved.
It is likely that the resulting math models are degenerate, or at least worse than the existing
approximate math model. If the relative solution (control points OFF) shows good RMS error
results, the math model can be Saved and the control points can be later remeasured. Usually the
problem is not the measurement but the absolute ground position specified for the point. You
should confirm from the original hardcopy control database, or other sources, that you have the
right coordinates for the right image point, and that the elevation data is consistent with the
project units (feet vs. meters, MSL vs. Ellipsoid) as specified.
28.4.8 Redundancy
A negative redundancy is acceptable for Satellite Sensor Models; however, for Frame Sensor
Models, a positive redundancy is expected.

Chapter 29
DTM Registration
DTM Registration covers tieing a DTM to a true global
position.
29.1 Overview
DTM Registration warps a Digital Terrain Model (DTM) so it aligns correctly with the region’s
terrain. You use the DTM Registration window to select the DTM to register. After you have
chosen the DTM, you can begin to sample tie points to register the selected DTM
29.1.1 When to Use DTM Registration

DTM Registration is used in two situations:
1. After you have imported a DTM from an external source (DTED, DEM, or ASCII) and you
want to shift the DTM to conform to ground truth. This is commonly needed because the
DTM may contain data accurate in a relative sense, but it is not accurate in an absolute
sense.
2. You extracted a DTM from some imagery (using ATE), and you later received some better
ground control and were able to improve the triangulation solution of the imagery. You now
want to update the DTM to conform to the new image support data.
In order to register the DTM, you must have some ground truth data in the area of the DTM. The
truth data can be any controlled data file that contains distinguishable topographic features, such
as a controlled image, feature database, or another DTM. If you are using an image for ground
truth, you should control the image with Triangulation before running Terrain Registration.
DEM
ASCII DTM
DTED
} TERRAIN
IMPORT
ATE or
ITE
UNREGISTERED
DTM
DTM REGISTERED
REGISTRATION DTM
SOCET SET Page 29-1

Chapter 29 - DTM Registration
29.2 DTM Registration
The Terrain Registration main window’s selections are as follows:
File > Exit Exits the DTM Registration window.
SELECT TO
Input DTM Prompt you to pick the DTM to register. Click (ellipse tool button) on the
right.
X/Longitude Display the longitude and latitude, or X and Y respectively, and elevation
Y/Latitude coordinates of the DTM point and T r u t h P o i n t . These two points together
Elevation are known as tie points. The DTM point is a sampled point on the DTM that you
want moved. The DTM point is the coordinate where the Truth point should
reside.
Index Display the index of the tie points presently being edited.
Goto Change the displayed tie points to the tie points at the entered Index.
Previous Change the displayed tie point to the tie point at the previous Index.
Page 29-2 SOCET SET

SELECT TO
Next Change the displayed tie point to the tie point at the next Index.
Add Store the tie point information at the displayed Index, and advances the index for
further tie point input.
Delete Remove the tie point information at the displayed Index.
Post Spacing Indicate the spacing between posts of the generated Output DTM. The default is
the Input DTM’s post spacing.
Algorithm Indicate the mathematical model used when registering the output DTM: Shift
means a simple offset or translation; Shift-Rotate-Scale means a rigid
transformation that will rotate and resize.
Output DTM Indicate the name of the DTM generated by DTM Registration.
Input DTM Turn Input DTM Terrain file drawing on or off.
Output DTM Turn Output DTM Terrain file drawing on or off.
Setup DTM Open the Input/Overlay DTM Setup Preference window. (See “Setup DTM and
Setup Overlay Preferences” on page 36-1).
Draw Draw DTMs selected by Input DTM and Output DTM.
Cancel Terminate drawing of the DTM. Useful when you wish to halt drawing of a large
or high-resolution DTM.
Auto Draw Automatically redraws the DTM whenever you reload or center the image.
Start Start the registration of the Input DTM using the entered tie points.
29.3 Execution - DTM Registration

1. After importing a DEM, ASCII DTM, or DTED file (See “Data Import and Export,”
Chapter 16), click Preparation > Registration > DTM Registration on the main
workstation window.
2. Click the (ellipse tool button) by the Input DTM: on the DTM Registration window.
Select the name of your DTM and then click Open.
3. Sample a location on the DTM to be relocated. Do this by toggling to the extraction cursor
and clicking on a point on the DTM with the LMB or by entering the coordinate directly
into the DTM Registration window. This displays a yellow triangle on the DTM to denote
this point.
SOCET SET Page 29-3

4. Sample a truth point on the image where the sampled DTM point is to be relocated. Do this
by pressing the MMB with the extraction cursor at the image location or, if the coordinate
is already known, by entering the value directly into the Truth coordinate fields of the DTM
Registration window. A yellow circle will be displayed on the image to denote the sampled
truth point. A line will be drawn, connecting the DTM point to the tie point.
5. Press the RMB or click Add on the DTM Registration window and repeat steps 3 and 4 to
add further points. The tie points you are presently editing will be displayed in yellow,
while other tie points will be displayed in red. The number of tie points you need to select
Page 29-4 SOCET SET

depends on the selected algorithm. Shift needs only one tie point pair, while Shift, Rotate,
Scale needs a minimum of three tie point pairs.
6. You may traverse to another tie point index by clicking Previous or Next, or by entering
the index you wish to traverse to in the index field and clicking Goto on the DTM
Registration window. You may delete unwanted tie points by traversing to the tie point and
click Delete.
DTM Registration will not allow you traverse to another tie

point index if you do not fill in all coordinate fields for the tie
point pair you are presently entering. If you do not wish to
complete the tie point pair, click Delete.
7. Select the preferred DTM Registration algorithm from the algorithm option menu.
8. [Optional] If the default output DTM name is not acceptable, enter the Output DTM Name.
A Default output name is provided. Do not change the output

name to be the same as the input file, or else your input file will
be overwritten.
9. Click Start to register the DTM. This may be time consuming depending upon the size of
the Output DTM being generated.
10. If the DTM Registration is successful, you may display the Output DTM by clicking Draw
in the DTM Registration window. See “Setting Up the DTM Graphics” on page 36-5 for
drawing display instructions.
SOCET SET Page 29-5

11. [Optional] To relocate the output DTM, you may either resample your entered tie points,
or return to step 2 and select as your input DTM your output DTM and register the
generated output DTM.
Page 29-6 SOCET SET

Chapter 30
Feature Registration
Feature Registration is used to align a Feature Database
correctly with the region’s topography.
30.1 Overview
In order to register the Feature database, you must have some ground truth data in the area of the
features. The truth data can be any controlled data file that contains distinguishable topographic
features, such as a controlled image, a DTM, or another Feature database. If you are using an
image for ground truth, you should control the image with Multi-Sensor Triangulation before
running Feature Registration.
The feature database can only be opened by one application at

a time. You must not have the feature database selected in the
feature extraction window, if you wish to run feature
registration on it. Closing the feature extraction window is the
best way to prevent this problem.
30.1.1 When to Use Feature Registration

Feature Registration is used in two situations:
1. After you have imported a vector file from an external source (DXF, Shapefile, or ASCII)
and you want to warp the Feature database to conform to the topography. This is commonly
needed because the Feature file may contain data accurate in a relative sense, but it is not
accurate in an absolute sense.
2. You extracted a Feature database from some imagery (using Feature Extraction), and you
later received some better ground control and were able to improve the triangulation
solution of the imagery. You now want to update the Features to conform to the new image
support data.
SOCET SET Page 30-1

Chapter 30 - Feature Registration
DXF ASCII FEATURES SHAPE FILE
FEATURE
IMPORT
FEATURE
EXTRACTION
FEATURE DATABASE
FEATURE
REGISTRATION
REGISTERED
FEATURES
30.2 Feature Registration

You use the Feature Registration window to select the feature file to register. After you have
chosen the feature file, you can begin to sample tie points to orient the feature file. To display this
window, click Preparation > Registration > Feature Registration on the main workstation
window.
Page 30-2 SOCET SET

The Feature Registration main window’s selections are as follows:
File > Exit Exits the Feature Registration window.
SELECT TO
Input Feat.DB Prompts you to pick the feature file to register. Display the name of the
feature file to register.
X/Longitude Display the longitude and latitude, or X and Y respectively, and elevation
Y/Latitude coordinates of the Feature point and Truth point. These two points
Elevation together are known as tie points. The Feature point is a sampled point in
the feature file that you want moved. The Feature point is the coordinate
where the Truth point should reside.
Index Display the index of the tie points presently being edited.
Goto Change the displayed tie points to the tie points at the entered Index.
Previous Change the displayed tie point to the tie point at the previous Index.
Next Change the displayed tie point to the tie point at the next Index.
Add Store the tie point information at the displayed Index, and advances the
index for further tie point input.
Delete Remove the tie point information at the displayed Index.
Algorithm Display the mathematical model used when registering the output feature
file.
Output FDB Display the name of the feature file generated by Feature Registration.
Start Start the registration of the input feature file using the entered tie points.
30.3 Execution - Feature Registration

1. Import a DXF, ASCII feature, or Shapefile (See “Data Import and Export,” Chapter 16 for
details). This will generate the unregistered feature file.
2. Run Feature Extraction. Load the unregistered feature file into Feature Extraction. Draw it.
3. When done reviewing the feature, click File > Exit to close the Feature Extraction window.
This is necessary because the feature database can only be opened by one application at a
time.
4. Click Preparation > Registration > Feature Registration on the main workstation window.
5. Click File > Input Feature File on the Feature Registration window. Select the name of
the unregistered file and then click OK.
6. Sample a location on the features to be relocated. Do this by toggling to the extraction
cursor and clicking on a point in the feature file with the LMB or by entering the coordinate
SOCET SET Page 30-3

directly into the Feature Registration window. This displays a yellow triangle to denote this
point.
7. Sample a truth point on the image where the sampled feature point is to be relocated. Do
this by pressing the MMB with the extraction cursor at the image location or, if the
coordinate is already known, by entering the value directly into the Truth coordinate fields
of the Feature Registration window. A yellow circle will be displayed on the image to
denote the sampled truth point. A line will be drawn, connecting the feature point to the
truth point.
Page 30-4 SOCET SET

8. Press the RMB, or click Add on the Feature Registration window and repeat steps 4, 5 and
6 to add further points. The tie points you are presently editing will be displayed in yellow,
while other tie points will be displayed in red. The number of tie points you need to select
depends on the selected algorithm. Shift needs only one tie point pair, while Shift, Rotate,
Scale needs a minimum of three tie point pairs.
9. You may traverse to another tie point index by clicking on Previous and Next or by entering
the index you wish to traverse to in the index field and clicking Go. You may delete
unwanted tie points by traversing to the tie point and clicking Delete.
10. Select a Feature Registration algorithm from the algorithm option menu.
11. [Optional] Enter the output feature database name.
12. Click Start to register the feature file. This may be time consuming depending upon the size
of the feature file.
SOCET SET Page 30-5

13. To verify the output: run Feature Extraction; Load New (output) feature file; Display it.
14. [Optional] If the output features are not registered correctly, you may either resample your
entered tie points, or return to step 2 and select as your input feature file your output feature
file to re-register it.
Page 30-6 SOCET SET

Chapter 31
Map Registration
Map Registration generates image support data for a digitized
map.
31.1 Overview
The image support data enables you to perform geopositioning operations such as mensuration
and feature extraction with the digitized map.
31.1.1 When to Use Map Registration

You use Map Registration after you have
HARDCOPY
digitized your map. The digitized map by MAP
itself is not sufficient to perform
geopositioning operations. Geopositioning
requires registration data in the form of an DIGITIZER
image support file. OR SCANNER
Before running Map Registration, you must
create an initial support file to accompany the
map with Image Import/Reformat. This initial SOFTCOPY IMAGE IMPORT
support file will enable you to load the map DIGITIZED MAP (CONVERT)
into the main workstation window.
After you have registered the digitized map
with Map Registration, the image support file MAP INITIAL
will contain the information SOCET SET REGISTRATION SUPPORT FILE
needs to perform geopositioning and
extraction with the digitized map.
SOCET SET treats digitized maps exactly the GEO-REFERENCED
same as other images, so any of the actions SUPPORT FILE
that you can do to an image (Image Map,
Perspective Scenes, Rectification, etc.) you
can also do to a digitized map.
IMAGE
DISPLAY
SOCET SET Page 31-1

Chapter 31 - Map Registration
31.2 Map Registration - Setup

Map Setup page displays the source map information. It contains fields for the user to enter map
information like scale, Dots Per Inch (DPI), and projection parameters. Fields that can be
calculated during the map fit, for example projection parameters, map scale, and ground
coordinates. See “Additional Calculations” on page 31-5 for more details.
31.3 Map Registration - Mensuration

Point Measurement page displays the ground point either entered from the user or imported from
an existing ground point file. These ground points form the basis for sampling process. The
ground coordinates are computed for Tie, Z Cntl, Z Check, XY Check and XYZ Check if the map
scale, DPI, and one or more XY or XYZ Ctrl points are given.
Page 31-2 SOCET SET

The Map Registration window’s selections are as follows:
MENU CHOICE DESCRIPTION
File > Select Map... Prompts you to select an existing map to be registered.
File > Open Ground Point Prompts you to open an existing ground point file to be used during map
File... registration.
File > New Ground Point Closes the current ground point file or deletes the current point data
File displayed on the Point Measurement page.
File > Save Ground Point Saves the current ground point file.
File
File > Save Ground Point Prompts you to enter a ground point file name to save the ground point file
File As... information to.
File > Fit Fits the current map to the current sampled points.
File > Accept Save Map Support File will save the current registration parameters.
BLANK SPACE
Save Map Support File As... will prompt you to enter the map support file
name to save the current registration parameters to.
File > Exit Exits Map Registration.
SOCET SET Page 31-3

MENU CHOICE DESCRIPTION
SELECT TO
Image Support File Display the name of the current loaded map to be registered.
Map Scale Display the scale of the original map, which will be stored in the support
file for reference. This filed is needed for map registration if the DPI is not
given.
DPI Display the DPI resolution of the scanned map image. This filed is needed
for map registration if the map scale is not given.
Projection Allow you to select a projection to use in registering map. Selection of a

projection results in the display of attribute names in the Projection
Parameters table.
Attribute Display a series of locational baselines and scale factors used by the
currently selected projection.
Value Display the values associated with the corresponding projection attributes.
May be entered directly or automatically calculated using the Fit Button
(contained on the Point Measurement page).
Datum Allow you to select a datum for registration.
Points List Display the table in which you enter or edit point data for sampled points
BLANK SPACE and used during registration. The number of points contained in the list is
BLANK SPACE displayed. The current selected row is the point sampled when toggled into
the extraction cursor.
BLANK SPACE
BLANK SPACE
BLANK SPACE
Unique ID for the point.
Point ID
BLANK SPACE
BLANK SPACE
Type of Point.
Type
BLANK SPACE
BLANK SPACE
Flag to indicate whether the point is to be used in the fitting.
Use
Coordinate Display Display the table in which to enter or edit ground coordinates
corresponding to the current selected point in the Points List Table.
Fit Select the Fit menu choice from the file menu. See the menu description on
the previous table.
Accept Selecting the Save Map Support File As… sub menu choice from Accept
menu. See the menu description on the previous table.
Page 31-4 SOCET SET

31.3.1 Map Fitting

When you select Fit, Map Registration takes the points you have sampled and attempts a fit with
the selected projection. The points that are used as input to the fit must have the Use column
checked in the Point List Table. Map Registration then calculates and displays the value of the
projection’s attributes. You can override the automatic calculation of the attributes by manually
entering values into the attribute boxes before selecting Fit. Since Map Registration uses a purely
mathematical fit which may not necessarily match the actual location of the map, it may be better
in some cases to manually enter the projection’s attributes to obtain a good support file.
31.3.2 Additional Calculations

When you select Fit, Map Registration will fit the map and calculate map scale or ground
coordinates depending on what information you enter. To only have the map fitted, map scale
must be entered and four or more control (xy or xyz) points must be entered and sampled.
In order to have the map scale calculated, enter the DPI of the scanned map image, and enter the
ground coordinates or four or more control (xy or xyz) points, and sample the control points.
When you select map fit, the map scale will be displayed. In order to have the ground coordinates
calculated, the map scale, DPI, the projection, projection parameters, and the datum must be
entered. Also, one or more control points must be entered and sampled, and four or more points
that are not xy or xyz control points must be sampled.
The ground coordinates are calculated for the sampled points that are not xy or xyz control points.
You need at least two control points for rotation to be calculated. Rotation is assumed North if
only one control point is given. When you select Fit the ground locations points that are not xy
or xyz control points will be displayed when the point is selected on the Points List table.
31.4 Execution - Map Registration

1. Scan or digitize a map. The file format must be one of the formats that SOCET SET can
import (such as Sun Raster, TIFF, Tiled). See “Image Import and Export,” Chapter 7 for
details.
2. Use Image Import/Reformat (in the Support Only mode) to create an initial support file to
accompany the digitized map.
3. Load the map into the console workstation monitor by doing the following:
a. Click File > Load Images.
b. In the Image Loader, select View1.
c. From the left image selections, select the desired image and click Load.
d. Click Close when complete.
OR
a. Click Preparation > Registration > Map Registration on the main workstation menu.
This displays the Map Registration window.
b. Select File > Select Map … on the map registration GUI.
c. Select the image from the selection. Click Open.
4. If you haven’t started Map Registration: Click Preparation > Registration > Map
Registration on the main workstation menu. This displays the Map Registration window.
5. The Map Support File name is automatically displayed with the current loaded map. Using
the keyboard, enter the scale of the original map.
SOCET SET Page 31-5

6. Projection can be changed by clicking the Projection name and selecting the Projection of
your map from the list provided.
7. If available, enter the Attributes and Values of the project in the Projection Parameters
field.
8. Datum can be changed by clicking the Datum name and selecting the datum of your map
from the list provided.
9. Click the Point Measurement tab so that the Point Measurement page is displayed.
10. Enter in information for four or more points:
a. To add a point, right click in the table and select add. To delete a point select the row
to be deleted (the row should be highlighted), right click and select delete.
Note the minimum number of points is one so if there is only

one row in the table this row will not be deleted.
b. Double click the Point Id column and type in the point id of the point to be sampled
or accept the default point id.
c. Select XY CNTL or XYZ CNTL from the Type column so that the point will be used
to register the map.
d. Click the Use column so that the point will be used to register the map and be
displayed on the map during sampling.
e. Enter the ground coordinates of the selected point by double clicking in the field for
the coordinate in the Coordinate Display. Do this for X and Y values.
OR
a. Select File > Open Ground Point File. Select the ground point file from the displayed
ground point files. Click Open. The ground point file will be displayed in the Points
List table. Modify the ground point information or add more ground points as
necessary.
11. Sample four or more points. For each control point, do the following:
a. Select the row of the point to be sampled Click the title bar of the view the map is
displayed in. This window should now have focus. Toggle to the extraction cursor by
using the track ball or using accelerator key F3.
b. Move the extraction cursor to the control point and press the left mouse button. You
should now see the point id and point icon displayed where the point was measured.
Note the Use column must be checked for the points to be

displayed.
c. Press the RMB to accept the sample and toggle out of the extraction cursor.
To toggle out of the extraction cursor without accepting the

point you can click the MMB, toggle out with the trackball, or
use accelerator key F3. Four or more points must be sampled
to register the map.
12. Click Fit to register the map. Map Registration will report the mean error of the solution.
13. If the results are not satisfactory, you should resample your control points, or try different
control points. You may override the projection or any of the Project Parameter Value fields
by clicking on the field, entering a new value, and clicking Fit again. This will cause Map
Registration to bypass fitting that value.
Page 31-6 SOCET SET

14. If the results are satisfactory, click Accept. Then reload the new map support file into the
main workstation window. The extraction cursor will now track in ground space.
15. Click File > Exit or click to the close icon on the upper-left corner of the Map Registration
GUI to exit Map Registration.
The execution above is for only fitting the map, and not
calculating scale or ground coordinates.
SOCET SET Page 31-7

Chapter 32
Map Accuracy Assessment

Accuracy Evaluation determines the accuracy of maps, charts
and other geospatial data and reports the resulting statistics.
32.1 Overview
The Accuracy Evaluation Capability (AEC) is originally designed for the GDASII replacement
capability in the Integrated Exploitation Capability (IEC). The Map Accuracy Assessment
(MAA) is one of the major components of the AEC and will be based on the results of the Map
Registration, another component of the AEC.
Accuracy is defined as the degree to which information on a map or image matches true or
accepted values. Control is a data source of known or accepted value. Control sources include
stereo NTM imagery with support data, ground control points collected during a land survey, or
orthoimagery. A candidate is the geospatial product being evaluated. A candidate can be a map,
chart, or image-based product with embedded registration information.
An accuracy evaluation uses the measurement of common features found in the control and
candidate to determine relative and absolute error.
• Absolute error is the difference in the actual (control) position and measured
(candidate) position.
• Relative error is the measurement of internal product inaccuracy of the candidate.
The relative and absolute error of the candidate, as well as other information, is passed to the
IEC’s PMAA database. The information passed to PMAA includes:
• absolute and relative horizontal accuracy to 90% probability,
• absolute and relative vertical accuracy to 90% probability,
• mean differences for x, y and z axis,
• root mean square error for x, y, and z axis,
• standard deviation for x, y and z axis,
• Molodenskiy transformation parameters,
• datum shift information,
• shift notes and product specific information.
SOCET SET Page 32-1

Chapter 32 - Map Accuracy Assessment
32.1.1 When to Use Map Accuracy Assessment

This tool is used for evaluating images, maps and charts. Its function is to display the accuracy
statistics of the image, map or chart.
32.1.2 Sequence of Events

The Map Accuracy Assessment executes the following major steps based on the results of Map
Registration:
• Start
Tells Assessment it is a new assessment or an existing one.
• Setup:
Select a candidate.
Determine if using a special point as the transform point.
Select a Ground Point file as the control, or select Determine the type of the controls such
as Ground Point file only, Images / Maps / Charts only, or both. See “Sample Scenarios”
on page 32-3.
Load necessary control(s).
• Mensuration:
Measure points in candidate and any of the images / maps / charts participating the
assessment.
• Assessment:
Automatically display the accuracy of the evaluated candidate including 21 items of
statistics.
32.1.3 Before Starting Assessment

As the control source, the control imagery and associated support data must be available on the
file system, or the ground point file must be available. The candidate and control source must
have been registered. To prepare for this, perform the following steps first.
1. Create a project to hold the candidate and controls.
2. Import the candidate and controls into theSOCET SET.
3. Convert the file containing ground points (if any) into SOCET SET format by using Ground
Point Import.
Perform registration to candidate and all control images / maps / charts by using Map
Registration. See “Execution - Map Registration” on page 31-5.
Page 32-2 SOCET SET

32.1.4 Sample Scenarios

Assessment is flexible and supports different execution scenarios.
32.1.4.1 Ground Points as control only

• No control imagery
• The ground points are displayed on the Ground Point Table. Select one by click the row,
then the coordinates of this point are displayed on the coordinate table
• The candidate is displayed on the Extract or Console monitor. The cursor is
automatically driven to the area where the selected ground point is located
• Put the cursor at the most possible spot of the candidate image. Refer to whatever
available information to confirm the spot, then, check the Measured button to sample
this point.
• A new (.ipf) file and a new (.gpf) file associated with the candidate will be created. The
calculation will be performed by using the new (.gpf) file against the ground control
point file.
32.1.4.2 Images / Maps / Charts as control only

• No existing ground point file
• The control imagery (single or a stereo pair) displays on Extraction or Console monitor,
while candidate is displayed on the same monitor or an additional viewport.
• Visually identify cultural and physical features common to both the candidate and
control imagery.
• Move the cursor to the feature in candidate image, click its check box Measured. Then
move the cursor to the identified feature in control image, click its check box Measured.
• Until as many needed points are measured (the more the conjugate features are
measured, the better for the following accuracy assessment. According to AEC
requirements, 30 points are minimum), click the Next button to save the measurements
and perform the calculation.
• One or more (.ipf) files containing measurement information (pixel coordinates) for
candidate image and each control images are created. A (.gpf) file containing ground
coordinates is created.
32.1.4.3 Ground Points and Images / Maps / Charts as control

• Refer to above topics for details.
• One or more (.ipf) files containing measurement information (pixel coordinates) for
candidate image and each control images are created. The (.gpf) file containing ground
coordinates is updated.
SOCET SET Page 32-3

32.1.5 Data Files

Assessment creates, updates, manipulates and uses the following files.
32.1.5.1 Map Accuracy Assessment File (.maa)

This file contains a candidate and a list of images that will participate the Assessment. It also
contains the necessary information.
32.1.5.2 Ground Point File (.gpf)

This file contains the information about all ground coordinates of points involved in Assessment.
This file is created or updated by Mensuration of the Assessment.
For the existing file, you can convert ASCII-formatted ground point files into the format that
Assessment expects by using ASCII Ground Point Imports as described in the Data Import/Export
chapter.
32.1.5.3 Image Point Files (.ipf)

Assessment creates an image Point File for candidate and each of the images participating in the
assessment. Each Image Point File has the same base name as the corresponding image file, but
with a suffix of .ipf. The image point file contains the image point measurements and the point
ID of the corresponding ground point from the Ground Point File.
32.1.5.4 Image Support Files (.sup)

A single Support File exists for candidate and every image that participates in Assessment. This
file contains information for relating ground and image points via the sensor math model. This
file is created during Image Import and never updated during the Assessment.
32.1.5.5 Image Files (.ipf)

A single Image File exists for candidate and every image that participates in Assessment. The file
contains the pixel information for each image. This file is created during Image Import.
32.1.5.6 Results Files (.res)

A single Results File exists for an assessment. The file contains all accuracy statistics from the
Assessment including the Date, Absolute Horizontal Error, Relative Horizontal Error, Absolute
Vertical Error, Relative Vertical Error, Absolute with Bias Removed, Number of horizontal
points, Number of vertical points, Bias Mean X, Bias Mean Y, Bias Mean Z, Standard Deviation
X, Standard Deviation Y, Standard Deviation Z, Molodensky X, Molodensky Y, Molodensky Z,
Horizontal Unit and Vertical Unit.
32.1.5.7 PDR Point Distribution Report

Review this report for points which do not meet the 3 sigma tolerance test.
32.1.6 Using Map Accuracy Assessment

To open this window, click Product > Map Assessment on the main workstation window.
This application is designed in wizard format, thus it’s easy to use by following the instructions
on each page.
Page 32-4 SOCET SET

32.1.6.1 Start Page
The Map Accuracy Assessment window’s selections are as follows:
SELECT TO
New Assessment Start a new assessment.

Existing List all existing MAA (.maa) files for selecting.
Exit Exit the Assessment.
<Back Switch back to Start Page.
Next> Switch to the Setup Page.
For a new assessment enable the New Assessment radio button and then click Next.
For an existing assessment enable the Existing Assessment. Wait for the ‘maa’ file to display in
the window below. Select the appropriate assessment file. Once selected, the MAA file will
automatically be read. Click on Next button when it becomes activated.
SOCET SET Page 32-5

32.1.6.2 Setup Page
The Setup window’s selections are as follows:
SELECT TO
File Click button to display the Select Candidate window. Select the support
file associated with the candidate.
Projection Projection within candidate’s support file..
Datum Datum within the candidate’s support file.
Scale Scale of the candidate.
Select Transform Point The base point by which the accuracy is calculated. If this is not selected,
the first point will be used.
GCP File Click the button to display the Select GCP file. Select a ground point file.
Add Click the button to display the Select Image window. Select the Control
Support file(s).
Remove Select an image on the Images display panel on the Setup Panel and then
click the Remove button
Exit Exit Map Assessment.
Next > Proceed to the Mensuration Panel.
Page 32-6 SOCET SET

SELECT TO
< Back Proceed to the Start Panel.
For a new assessment, click File... and select the candidate support file.
For an existing assessment the Candidate Area is pre-populated with all the Map Assessment
information.
For a new assessment enable “Transform Point” (if checked the Select Transform Point box in
the Setup Page) or “1” will be displayed at the beginning with the coordinates of the candidates’
load point (normally at the center of the image).
In the Control Area of this panel, an assessment which will be using a pre-existing control points
file; click on the GCP File button and select the ground control point file. You may need to first
convert an ascii point file into an GCP file.
In the Image Area, click the Add button, an existing assessment, all points of the selected ground
point file will be displayed on the Point List Table associated with the coordinates and images of
the 1st point. To see any point, simply click it.
32.1.6.2.1 New Assessments

In Candidate area:
Click File.… Select the candidate. The Projection, Datum, Scale and DPI of the candidate
will be displayed.
If you want to select a special point as the Select Transform Point, click the check box
Select Transform Point.
In Control area:
If you want to use ground points as the control of the assessment, Click GCP File…, select
the file contains the points, then click Next. A new (.maa) file is created when switch to the
next page Mensuration Page.
If you want to use images / maps / charts as controls, click Add…,select them, then click
the Next button.
32.1.6.2.2 Existing Assessments

For the existing assessment, all information including candidate, GCP file and controls is
automatically displayed on the page.
SOCET SET Page 32-7

32.1.6.3 Mensuration Page

Use this page to measure as many points as needed.
The Mensuration window’s selections are as follows:
SELECT TO
(Point List)
Point ID The Point ID.

Add Click RMB, select Add to add a new point.
Delete Click RMB, select Remove to delete a point.
Point Type Point type. It can be Tie / Z Control / XY Control / XYZ Control / Z Check
/ XY Check / XYZ Check.
Use If enabled, the point will be used in the MapAssessment process.
Page 32-8 SOCET SET

SELECT TO
Coordinate Display Display the coordinates and the accuracy of the point.
Measure Status:
Image Display the image ID associates with the selected point.
Lock Locked the image by RT if the box is checked.
Measured Display the image is measured and the pixel coordinates are sampled if the
BLANK SPACE box checked.
Load Click RMB, select Load to load an image from the control list.
Delete Click RMB, select Delete to delete an image.
L<>R Click RMB, select L<->R to switch over the two control images on the
Extract or Console monitor.
Save Save the Assessment (.maa), (.gpf), (.ipf).
Exit Exit the Assessment.
<Back Back to the Setup Page.
Next> Switch to the Assessment Page, all files (.maa), (.gpf), (.ipf) are saved.
For a new assessment, only one point named “TransformPoint” (if checked the Select Transform
Point box in the Setup Page) or “1” will be displayed at the beginning with the coordinates of the
candidates’ load point (normally at the center of the image).
For an existing assessment, all points of the selected ground point file will be displayed on the
Point List Table associated with the coordinates and images of the 1st point. To see any point,
simply click it.
To add a new point, click the RMB on the Point List Table to display the [Add/Delect] context
sub menu, select Add. The new point will be named with its sequential number which can be
edited to any other name. Similarly the sub menu can be used to delete a point.
To add an image to the selected point, click the RMB on the Measure Status table in either the
Control-1 or Control-2, Image column cell to display the [Load/Delete/L<>R] context sub menu,
and click Load..., then on the image id context window select the specific image ID to be loaded
to that viewport. The sub menu also can be used for removing an image from the table, or switch
two control images to mitigate pseudo stereo when present.
To lock an image, simply check the Lock box of the table or drive to the point of interest on the
Control sources and issue a RMB click. In both the Image to Map scenario and the Map to Map
scenario the first RMB locks the control source at the desired point. In the Image to Map scenario
the second RMB click is performed in the Control image left eye to lock the left image.
In both scenarios a LMB initiates the mensuration process.
If the Measured box is checked, the associated Lock box will always be checked.
However, if the Lock box is checked, the Measured box can be either checked or not.
However, to efficiently speed up the point mensuration process, employ the following steps:
SOCET SET Page 32-9

The mensuration steps are as follows:

• Move the cursor to a desired location on the candidate viewport (typically View2);
clicking the RMB will lock it.
• Move the cursor to the conjugate location on the LEFT image eye of the Control
viewport; and click the RMB to lock it.
or
Move the cursor to the conjugate location on the LEFT image eye on the Control viewport and
click the LMB which will attempt to measure in both the Left and Right image eye viewport.
• If the RMB was used to lock the LEFT image eye the move the cursor to the conjugate
location on the RIGHT image eye of the Control viewport and then click the LMB to
mensurate the point.
Once the mensuration is performed, click Save. The current mensuration is saved to the
appropriate files which include Image Point (.ipf) and Ground Point (.gpf) files. Once all points
or enough points have been mensurated, click Next to advance to the Assessment Panel
Map Assessment will generate two additional output files. One has the same name as the map
support file with the “rep” [report] extension and the second is the name of the map support file
follow by the extension “pdr” [point distribution report] extension. The report (.rep) file has a list
of the output results, basically what is displayed on the MAA user interface so there is little need
to review it. The “pdr” file has a list of all the measured points including the computed deltas and
and residuals. Review this file to determine which points require re-mensuration. Points which
fail the three sigma test are flagged with an asterisk.

32.1.6.4 Assessment Page

The Assessment Page will display the final results.
The Assessment window’s selections are as follows:
SELECT TO
Description Map Assessment statistic type.
Value Map Assessment statistic for associated type.
Exit Dismisses the Map Assessment Window. No associated saving process

connected with this button.
<Back Return to Mensuration Panel.
32.2 Execution - Map Accuracy Assessment

The following execution sequence will satisfy most work flows:
1. Display the Assessment window by clicking Products > Map Assessment on the main
workstation window.

2. On the Start window, do one of the following:

a. For a new assessment, click Next to go to the Setup page;
b. For an existing assessment, display all available existing assessments by clicking the
check box Existing, select one and then click Next.
3. On the Setup window,
a. click File…, select a candidate from the “Select Candidate” window.
b. Select the check box Select Transform Point. The point named “TransformPoint” will
be used for transformation during the following calculation.
c. Click GCP File…, select a ground point file which will be used as control.
d. Click Add…, select all desired controls.
e. Click Next.
4. On the MAA filename window click Yes or No to use the default MAA name, (for example,
if the name of the candidate is sandiego.sup, the default MAA name will be sandiego.maa).
If No is clicked, give the file a name and click OK.
5. On the Mensuration window,
a. Select points from the candidate and measure them, either compared with the points
from the ground point file, or control images / maps / charts. Click Next.
6. On the Assessment window:
a. By clicking Next on the previous window, all measured points were automatically
saved into a (.gpf) file and different (.ipf) files (candidate and each control is
associated such a file).
b. The calculation is automatically implemented and the Statistics are displayed.
7. Click Done to exit the Assessment window.

Chapter 33
Image Rectification
Image Rectification covers the processes which reshape or
warp an image. It runs in two modes: Single Image
Rectification and Pairwise Rectification.
33.1 Overview
The word rectification describes any process which reshapes or warps an image. Typical uses of
rectification include: rotating an image so that north is up; removing distortions due to camera
obliquity or terrain relief; or rotating and scaling two overlapping images so that stereo
visualization is possible.
33.1.1 When to Use Rectification

It is probably not necessary to use Image Rectification in the normal SOCET SET production
work flow. You should try to use the “on the fly” pairwise rectification from the Image
Enhancement interface before deciding to use Image Rectification. If you can visualize stereo
using the “on the fly” method, you can skip using Image Rectification and save time and disk
space. Automatic terrain extraction performs its own rectification, so Image Rectification is not
necessary; however, you will still have to run Image Rectification to use Anaglyph, and you also
may need to run Image Rectification to produce stereo images to export to other systems.
Image Rectification process runs in two modes: Single Image Rectification and Pairwise
Rectification. Single Image Rectification is used to rotate an image so that North is “up,” to rotate
the image to an arbitrary direction, or to remove the obliquity of a high-oblique image. Pairwise
Rectification is used to generate a stereo image pair.
Triangulation may not operate properly if images are rectified. For best results perform
rectification after running Triangulation.
If you have a Vitec, TIFF Tiled, or NITF image which has missing areas after rectification, run
the original image through Image Export/Reformat and change it to a different format. Then redo
the rectification.
SOCET SET Page 33-1

Chapter 33 - Image Rectification
INPUT OUTPUT
IMAGE(S) IMAGE(S)
RECTIFICATION
INPUT OUTPUT
SUPPORT SUPPORT
33.1.2 Ways to Rectify an Image

In SOCET SET, there are several ways to perform rectification:
PROCESS DESCRIPTION
On-The-Fly Pairwise Rectification You can see 3-dimensional relief on the extraction monitor by
displaying a pair of stereo (overlapping) images. This is an on-the-
fly process and does NOT create new disk file images. This is
called E p i p o l a r R e c t i f i c a t i o n . See “Pairwise Rectify /
Rectify All” on page 4-20 for additional information.
Ortho-Rectification with DTM You can create a view of the image that is what you would see if
you were looking straight down; this requires the use of
topography (DTM) when reshaping the image. This kind of
rectification is called ortho-rectification and discussed in the
Orthophoto chapter. See “Rectifying with Orthophoto” on page 46-
7 for details.
Ortho-Rectification without DTM You can reshape an image to remove the distortion due to
obliquity. This is done with the Orthophoto process without
inputting a DTM. This will output an image that does NOT
have a rigorous sensor model, so the rectified image cannot
be used in any other SOCET SET process without loss of
accuracy. See “Rectifying with Orthophoto” on page 46-7 for
details.
Single Image Rectification You can reshape an image to remove the distortion due to
obliquity. This is done by Singe Image Rectification. This
will create a new disk file and will rotate the image to any
angle you specify. This does not remove distortions due to
topography. This will output an image that contains a
rigorous sensor model, so it can be used in any other
SOCET SET process without loss of accuracy. However, the
image is warped with an affine, or linear, transformation.
See “Single Image Rectification” on page 33-3 for this process.
Pairwise Rectification You can take a stereo (overlapping) image pair and create two new
images (permanent disk files) that are rotated and scaled so that
stereo visualization is possible. This is done by the Pairwise
Rectification process (don’t confuse this with the Pairwise
Rectification that is part of Image Enhancement). See “Execution—
Pairwise Rectification” on page 33-7 for this process.
Scale/Zoom You can zoom or magnify an image (no rotation is performed). See
“Image Scaling,” Chapter 34 for additional details.
33.1.2.1 Rectifying with Orthophoto

As an alternative to single image rectification, Orthophoto can also be used to generate a rectified
image. Conceptually, this is the same as Rectification, but Orthophoto uses a finite element
solution rather than an A f f i n e T r a n s f o r m a t i o n used by Rectification. See “Rectifying with
Orthophoto” on page 46-7 for more details on this approach.
Page 33-2 SOCET SET

33.2 Single Image Rectification

Single image rectification removes the distortion due to obliquity of the input image. A rectified
image has uniform scale in all directions, and is conformal (i.e. North-South lines are
perpendicular to East-West lines). Mathematically, rectification is the process of projecting the
image onto an ellipsoid of the earth. In SOCET SET, this projection is approximated in single-
image Rectification by a linear (affine) resample that approximates this projection. The linear
approximation does not alter the accuracy or quality of the workstation products. A higher order
(nonlinear) resampling can be achieved, if desired, by executing Orthophoto with a null (i.e. flat)
Digital Terrain Model.
33.2.1 Rotating an Image

You can use Rectification in the Single Image mode to rotate an image to any angle with respect
to north. The default rotation angle is zero degrees, which produces an image with North up.
The Rectification window’s selections are as follows:
File > Load Project Prompts you to pick the project file containing the desired support files
File > Input Support file Prompts you to pick the image(s) to rectify.
File > Exit Exits Rectification.
Options > Auto Minify Automatically creates a minified image pyramid after Rectification is
complete.
SOCET SET Page 33-3

Options > Auto Load Automatically loads the monitors with the rectified image.
Imagery
SELECT TO
Interpolation Method Select an interpolation method from the Interpolation Method option. The
default is Bilinear. See “Interpolation and Resampling,” Appendix G for a
complete explanation of these methods.
Bilinear - Weighted_Mean - Nearest Neighbor
Minification Left /Right Select a minification level from the Minification Level option. The
default is the 1:1 image. (1, 2, 4, 8, 16, 32, 64, ...)
Relative Rotation BLANK SPACE
(when rectifying singly) BLANK SPACE
Relative to North Rectify with the rotation angle (in the field below) CCW relative to north.
Current Orientation Rectify with the rotation angle CW to the current orientation of the input
image.
Relative Rotation BLANK SPACE

(when rectifying Pairwise) BLANK SPACE
Relative to North Rectify with the rotation angle (in the field below) CCW relative to north.
Epipolar Rectify the two images with a rotation relative to the epipolar alignment of
BLANK SPACE those two images.
Oblique Rectify the two images obliquely.
Rotation Angle Select a rotation orientation for the Relative Rotation option. The default is
Relative to North.
Draw MBR Select a portion of the input image to be rectified. If you do not, the default
is to rectify the entire image.
Lines / Samples to skip / Specify the subsection of the input images to minify. “Skip” is the offset in
process pixels from the upper-left corner of the input image. “Process” is the size
of the subsection of the input image that you want rectified. The default is
for the entire input image to be resampled. Enter numbers here only if you
want to process a subset of the input image.
Input Support File Name(s) the image(s) to be rectified.
Output Image Identify the name and location of the output image files.
Start Start Rectification.
Start at... Display the Start Batch Job window and lets you initiate the batch job. See
“Start At Jobs” on page E-3.
Page 33-4 SOCET SET

33.2.2 Rectifying a Portion of an Image

By default, Rectification will rectify the entire input image(s). However, there are times when you
only need to rectify a portion of the input image(s). For example, if you have a stereo image pair
with 60 percent overlap between the Left and Right input images, then you only need to rectify
the overlap region of both images
LEFT IMAGE RIGHT IMAGE

Sample Sample
L1
L2 L2
L1 L2
l L1
1 l
2
a1 a2
(A) (B)
line line
Sample Sample
Epipolar plane
L2 L1 L2
L1
line (C) line (D)

A) Scanned left digital image B) Scanned right digital image
C) Epipolar rectified left digital image D) Epipolar rectified right digital image
Generally, you should only rectify the portion of the image(s) that you need, so the rectification
algorithm will run faster and the output files will occupy less disk space. There are two ways to
tell Rectification that you only want to process a portion of the input images: (1) you can
graphically delineate the portion of the input image(s) by drawing a polygon with the extraction
cursor, or (2) you can manually enter the number of pixels (in the input image) you want to
process.
33.2.3 Execution—Single Image Rectification

This section describes the procedure to rectify a single image:
1. Click Preparation > Resample > Rectification > Single on the main workstation window.
2. Click File > Select Input Support File on the Rectification window.
3. Choose an image support file to rectify and click OK.
4. [Optional] Change the Output Image location, by clicking Location in the Output Image
section. Choose a file location and click OK.
5. [Optional] Select an interpolation method from the Interpolation Method option. The
default is Bilinear.
6. [Optional] Select a minification level from the Minification Level option. The default is the
1:1 image.
7. [Optional] Select a rotation orientation from the Relative Rotation option. The default is
Relative to North.
8. [Optional] You may select a portion of the input image to be rectified. If you do not, the
default is to rectify the entire image.
SOCET SET Page 33-5

The following paragraph describes how to select a portion of the image:

a. Load the image you wish to rectify.
b. Click Draw MBR on the Rectification window. Then toggle to the Extraction cursor.
On the viewport that contains the image you wish to rectify, delineate the portion of
the image to rectify by sampling points with the LMB. Press the RMB to accept the
polygon. The polygon is replaced by the minimum bounding rectangle, or MBR,
which contains the polygon you just delineated. Toggle back to the mouse cursor
before proceeding.
c. Alternatively, you can enter the exact number of pixels you want processed by
entering numerical values in the Lines and Samples text fields on the Rectification
window. By default, these fields contain the total lines and samples in the image you
wish to rectify. You can skip any of the first lines and samples of the image and
continue processing any number of lines and samples.
9. Click Start to begin rectification.

10. [Optional] Click Start at... to initiate a batch process job at a later time.
33.3 Pairwise Rectification

Pairwise Rectification operates on an overlapping stereo pair of images and performs single
image rectification on both of them, resampling the images to have the same ground sample
distance. The two images do not have to be from the same sensor or have the same type of sensor
model.
Page 33-6 SOCET SET

You have three options for rotation:

• Epipolar—rotates the two images so the epipolar direction is horizontal. In this case
the rotation angle is ignored.
• Relative to North—rotates the two images to an angle relative to north (by default
the angle is zero degrees).
• Oblique—rectifies the two images obliquely. The ground is assumed to be lying in
the YZ plane. Use this mode if your image has the sensor pointing along the X axis,
such as in close-range photogrammetry.
Pairwise rectification enables stereo visualization of stereo image pairs: without rectification you
cannot perceive stereo.
33.3.1 Skipping Pairwise Rectification

Some raw images you receive may have a scale and rotation that makes pairwise rectification
unnecessary. You can skip pairwise rectification only if the left and right images have the same
scale and if they are already oriented so the epipolar direction is horizontal. You can test for this
condition by displaying the images on a stereo monitor. If you can visualize good stereo, the
images are probably oriented correctly. As a general rule, the only time you get images in this
condition are when they were taken by the same sensor in a single collection pass, and if the
images were scanned in with the epipolar direction horizontal.
33.3.2 Execution—Pairwise Rectification

This section describes the procedure to pairwise rectify a stereo image pair:
1. Click Preparation > Resample > Rectification > Pair-Wise on the main workstation
window.
2. Click File > Select Left Support file on the Pairwise Rectification window.
3. Choose an image support file and click OK.
4. Repeat steps 2 and 3 for the right image.
Steps 5 through 9 are optional.
5. [Optional] Change the Output Image location, by clicking Location in the Output Image
section. Choose a file location and click OK.
6. [Optional] Select an interpolation method from the Interpolation Method option. The
default is Bilinear.
7. [Optional] Select minification levels from the Minification Level option button. The default
is the 1:1 image.
8. [Optional] Select a rotation orientation from the Relative Rotation option. The default is
Epipolar.
9. [Optional] You may select a portion of the input images to be rectified. If you do not, the
default is to rectify the entire images.
The following steps describe how to select a portion of the image.
10. Load the images you wish to rectify.
11. Click Draw MBR on the Rectification window; this toggles to the extraction cursor. On the
viewport that contains the images you wish to rectify, delineate the portion of the image to
SOCET SET Page 33-7

rectify by sampling points with the LMB. Press the RMB to accept the polygon. The
polygon is replaced by the minimum bounding rectangle, or MBR, which contains the
polygon you just delineated. Toggle back to the mouse cursor before proceeding.
12. Alternatively, you can enter the exact number of pixels you want processed by entering
numerical values in the Lines and Samples text fields on the Pairwise Rectification
window. By default, these fields contain the total lines and samples in the images you wish
to rectify. You can skip any of the first lines and samples of the images and continue
processing any number of lines and samples.
13. Click Start to begin rectification.

33.4 Batch Processing - Image Rectification

COMMAND LINE:
% start_socet -single rectifier -batch -s setting_file
If you are running rectify in the “scale” or “single” mode, you

should specify values for the keywords containing “left”. For
“pairwise mode, specify values for the keywords containing
“left” and keywords containing “right”.
rectifier rectify
KEYWORD DESCRIPTION
project Project filename (select from the .prj files in

auto_minify Perform minification of output image(s). Select “YES” or “NO.”
rectify_mode Select “scale” for Zoom / Scale, “single” for single image rectify,
or “pairwise” for pairwise rectify
input_name_left Input support filename (with full path prefix) for left image.
input_name_right Input support filename (with full path prefix) for right image. Only
applicable to pairwise mode.
output_name_left Name of the output image pixel and support file for left image.
Specify a name only, not a full path, e.g. “abc.”
output_name_right Name of the output image pixel and support file for right image.
Specify a name only, not a full path, e.g. “abc.” Only applicable to
pairwise mode.
Page 33-8 SOCET SET

KEYWORD DESCRIPTION
output_location Name of the image location for the output images from the list in
<install_path>/internal_dbs/DEVICE/
location.list.
skip_lines_left Number of lines to skip in the left image.
skip_samples_left Number of samples to skip in the left image.
process_lines_left Number of lines to process in the left image.
process_samples_left Number of samples to process in the left image.
skip_lines_right Number of lines to skip in the right image. Only applicable to

pairwise mode.
skip_samples_right Number of samples to skip in the right image. Only applicable to

pairwise mode.
process_lines_right Number of lines to process in the right image. Only applicable to

pairwise mode.
process_samples_right Number of samples to process in the right image.
orientation_mode Orientation of rectification. For single mode, select “current” or

“north”. For pairwise, select “epipolar”, “north”, or “oblique”. Not
applicable to scale mode.
orientation_angle Decimal angle of rotation in degrees. Only applicable if orientation

mode is “current”, “oblique”, or “north”. Not applicable to scale
mode.
zoom_factor Decimal zoom factor, only applicable for scale mode. Enter a
number less than 1.0 to shrink the image; greater than 1.0 to
enlarge.
resample_method Pixel resampling method. Specify either “BILINEAR”,

“NEAREST_NEIGHBOR”, “WEIGHTED_MEAN”. Refer to the
Interpolation and Resampling appendix for details on how these
work.
SOCET SET Page 33-9

Chapter 34
Image Scaling
Image Scaling takes an image as input and resamples it to the
resolution you specify.
34.1 Overview
Scaling generates an image file by resampling your input image. Your input image is not altered.
You specify the scaling factor in either of two ways: a numerical (possibly fractional) zooming
factor, or a map scale (such as 1:20,000) and an output device resolution (such as 40 pixels per
centimeter).
Scaling is different from Minification. Minification takes an image as input and outputs an image
pyramid consisting of a set of several progressively smaller versions of the input image. Scaling
takes an image as input and resamples it to the resolution you specify.
34.1.1 When to Use Image Scaling

You use Image Scaling when you wish to resize an image. This changes the image’s Ground
Sample Distance (GSD).
Normally you will not need to change the scale of an image for the following reasons:
• When you scan or digitize an image, you select the GSD as during the scanning or
digitizing operation.
• Pairwise Rectification automatically picks the best GSD for you when you are
rectifying a stereo image pair.
• When creating an orthophoto, Orthophoto prompts you to select the GSD.
Rectification is similar to Image Scaling and may be a useful alternative to Image Scaling. For
example, if you need to rotate an image, use Rectification in Single Image mode. See “Image
Rectification,” Chapter 33 for details.
SOCET SET Page 34-1

Chapter 34 - Image Scaling
34.2 Zoom/Scale
To obtain this window, click Preparation > Resample > Zoom/Scale on the main workstation
window.
The Zoom/Scale window’s selections are as follows:
File > Load Project Prompts you to select a project file (only if started stand-alone).
File > Select Input Support Prompts you to select the image to be zoomed/scaled.
File...
File > Exit Exits the Zoom/Scale window.
Options > Auto Minify If On, Zoom/Rescale will automatically invoke the minification tool on the
output image.
Options > Auto Load Loads the output image to the Main Workstation window after completion.
Page 34-2 SOCET SET

SELECT TO
Interpolation Method Select an interpolation method from the Interpolation Method option. The
default is Bilinear. See “Interpolation and Resampling,” Appendix G for a
complete explanation of these methods.
Bilinear - Weighted_Mean - Nearest Neighbor
Minification Select a minification level from the Minification Level option. The
default is the 1:1 image. (1, 2, 4, 8, 16, 32, 64, ...)
Map Scale (1 to...) Scale the output image. If you enter a value here, you must also enter the
resolution of the output device (Output Res.).
Output Res. Apply the resolution of the output device. For example, if you want 40
(pixels / proj unit) pixels per centimeter and your project is in meters, enter 4000 (40 pixels/
cm = 4000m).
Zoom Factor Apply the zoom factor of the scaling. This number equals the number of
(>1 = enlarge) output pixels per input pixel. For example, if the input image is 1K x 1K,
and the desired output image is 2K x 2K, then the Zoom Factor is 2.0.
Lines / Samples to skip / Define the rectangular subsection of the input image to be zoomed/
process rescaled. “Skip” is the offset in pixels from the upper-left corner of the
input image. “Process” is the size of the subsection of the input image that
you want scale. The default is for the entire input image to be re-sampled.
Enter numbers here only if you want to process a subset of the input image.
Draw MBR As an alternative, to hand-entering the values which define the subsection
rectangle, you can toggle this button to the On state and draw a polygon on
the image itself with the extraction cursor. Zoom/Scale will compute a
maximum bounding rectangle for the polygon and set the number of lines
and samples to skip and process to reflect the position and dimensions of
the maximum bounding rectangle.
Input Support File Name the input support file you chose. Defaults to the currently loaded
image.
Output Image Identify the name and location of the output image.
Start Start zooming/rescaling the image.
Start at... Display the Start Batch Job window and lets you initiate the batch job.
34.3 Execution - Scaling

1. Click Preparation > Resample > Zoom/Scale on the main workstation window.
2. Click File > Select Input Support Files... on the Zoom/Scale window. Select a Support
File, then click Open.
3. [Optional] Choose an interpolation method.
4. [Optional] Choose the Minification Level out of the list of available input image
minification levels to scale.
5. Enter the Output Resolution. There are two distinct ways to choose the scaling parameters.
Only one method may be used:
a. Enter the Map Scale. The Zoom Factor will automatically be calculated.
SOCET SET Page 34-3

b. Enter the Zoom Factor. The Map Scale will automatically be calculated.
Press “Enter” on the keyboard after inputting new values.
6. Edit the number of lines and samples to skip and process. The default process text boxes
contain the total lines and samples in the image. You may skip any of the first lines and
samples of the image and continue processing the process lines and samples you wish to
enter in the process text boxes.
The amount of skip and process values must be less than the
original lines and samples of the image. If this is not the case
Zoom/Scale will warn you.
7. [Optional] Enter the name and location of the output image in the Output Image field, if the
default is not correct.
8. Click Start to begin scaling the image.
34.4 Batch Processing - Image Scaling

You can run Image Scaling in batch mode. See “Batch Processing - Image Rectification” on
page 33-8 for further details.
Page 34-4 SOCET SET

Chapter 35
Terrain File Creation

Terrain File Creation discusses how to interactively create a
new DTM.
35.1 Overview
Digital Terrain Model (DTM) has two data formats: Grid and TIN.
• G r i d is a two-dimensional array of elevation data points called P o s t s . The array of
posts is always aligned North-South-East-West with the project coordinate system.
Further information is available in Project Management Chapter. See “Coordinate
Systems” on page 5-6 for details.
• T I N format stores critical points (M a s s P o i n t s )and breaklines which model the
terrain without redundant data.
Both Adaptive ATE and Non-Adaptive can generate both DTM formats. See “Adaptive vs. Non-
Adaptive ATE” on page 37-1 for more details.
You can create a DTM in SOCET SET in one of several ways:
• Interactively (the topic of this chapter) within Automatic Terrain Extraction (ATE) or
Interactive Terrain Edit (I T E )
• Importing ASCII DTM, DTED, or DEM files (See “Terrain Import and Export,”
Chapter 17.)
• Merging two or more DTMs (See “DTM/Feature Merge,” Chapter 44.)
35.1.1 When to use Terrain File Creation

The most common situation for creating a DTM is after importing and controlling (triangulating)
imagery.
SOCET SET Page 35-1

Chapter 35 - Terrain File Creation
35.2 Creating a DTM

You create a DTM within the ATE or ITE applications. Depending on which application you are
running, do the following to interactively create a new flat DTM:
Click Extraction > Terrain > Automatic Extraction
or
Click Extraction > Terrain > Interactive Edit
Click File > Create DTM... on the ATE or ITE windows.
To create a DTM, you must select an ATE Method (either Adaptive ATE or Non-Adaptive ATE)
and the images to be used when generating the DTM data (for explanations regarding Adaptive
ATE and Non-Adaptive ATE, see Choosing an ATE Method section below). See “Adaptive vs.
Non-Adaptive ATE” on page 37-1 for greater detail. If you select more than two images, the
images must not be rectified. You must also define the boundary of the DTM. The DTM boundary
can be:
• A polygon
• A minimum bounding rectangle around a polygon
• A rectangle defined by its Lower-Left and Upper-Right corner coordinates
If you are going to run ATE next, the DTM boundary should cover the overlapping area shared
by at least two images, as shown in the figure below (for the case of only two images: left and
right).
You specify the shape of

Total Extent of DTM: the DTM polygon with
Area is marked with an View/Edit/New DTM.
‘OUTSIDE_
BOUNDARY’
Right Image
Left Image
The DTM you create will always be rectangular. When using a polygon to define the DTM
boundary and the polygon is not rectangular, the posts outside of the polygon will be marked with
a Figure Of Merit (FOM) value of OUTSIDE_BOUNDARY and will not be considered as valid
posts by any SOCET SET application. For TIN DTM formats, there will be no mass points and
breaklines outside of the polygon. See the figure above for an illustration.
There are four ways to define DTM boundary:
Use Polygon Use Minimum Bounding Rectangle around Polygon
Use ATE Images Specify Lower-Left and Upper-Right Corner Coordinates
Page 35-2 SOCET SET

You must also specify the new DTM’s post spacing, and a strategy or a number of DTM Filter
parameters. You can then start Automatic Terrain Extraction to collect DTM data.
After you create a DTM, your next step is to run one of the following applications:
• ATE—For all rural imagery and for small-scale imagery of urban areas. After ATE,
you will run Interactive Terrain Editing or DTM/Feature Merge.
• ITE—For large-scale imagery of urban areas. You can use ITE to build the DTM
manually.
• DTM/Feature Merge—If you have a vector database containing features such as
drains, breaklines, and ridges.
You can run DTM/Feature Merge before or after you have run
Automatic Terrain Extraction.
35.2.1 How to Handle Trees and Buildings in Terrain

When there are buildings, trees, or similar objects in your imagery, you must decide your DTM
to be Digital Surface Model (DSM) or Digital Elevation Model (DEM). DSM models the top of
trees, and buildings. DEM models the bare earth.
For a DSM, you should try the following when you run ATE:
• Set the post spacing to a small value.
• Disable the “eliminate trees/buildings/other” in ATE.
• Run ATE in the adaptive mode.
For a DEM, you can try the following. The minimum height value is critical to the success of
eliminating trees/buildings/other. You can try different values in ITE to see which value is the
optimal one for your imagery.
• Set your post spacing to a small value.
• Enable the “eliminate trees/buildings/other” and specify the minimum height of the
trees and buildings.
• Build the terrain data by hand, as follows:
a. Run ATE and Create DTM, but do not click Start.
b. Save the DTM in ATE.
c. Exit ATE then run ITE.
d. Build the terrain using ITE tools (Post, Geomorphic, and Area).
This works especially well for TIN DTM format.
35.2.2 Choosing an ATE Method

There are two ATE Methods: Adaptive ATE and Non-Adaptive ATE and you must select the ATE
Method when creating a DTM. Adaptive ATE uses an inference engine to generate image
correlation strategies adaptively according to terrain type (flat terrain, hilly terrain, steep terrain,
etc.). When the terrain type changes within the DTM covered area, Adaptive ATE will use
different strategies accordingly. It is not required that the DTM covered area be of the same type
for Adaptive ATE. On the other hand, Non-Adaptive ATE will use whatever strategies you
specified and requires that the DTM covered area be of the same type. If you have tuned your
SOCET SET Page 35-3

customized strategies and they work very satisfactorily for you, you are encouraged to use Non-
Adaptive ATE with your strategies. Otherwise, you should use Adaptive ATE. ATE may use
multiple images in any order. When you select more than 2 images, all images must not be
rectified. When you select only 2 images, the 2 images can be either rectified or non-rectified.
ATE selects the best image pair for a post to perform image correlation and does image
rectification or epipolar resampling on the fly. In general, Adaptive ATE generates more accurate
DTM data and takes longer to run than Non-Adaptive ATE does. In some rare cases, Non-
Adaptive ATE with customized strategies may generate more accurate DTM data than Adaptive
ATE.
35.2.3 Populating the DTM with Valid Data

When you create a Grid DTM, the elevation data is initially flat: the heights of all the posts are
set to the average elevation computed from the vertices elevations of the polygon, the rectangle,
or the lower-left and upper-right corners of the DTM. When you create a TIN DTM, there are no
critical points and breaklines in the file. If you use ATE to extract critical points and breaklines,
you need to specify a reasonable post spacing. Normally, 10 to 15 pixel post spacing is
reasonable. Post spacing determines the number of critical points and breaklines. If you need
more critical points and breaklines, you must decrease DTM post spacing. If you need fewer
critical points and breaklines, you must increase DTM post spacing. There are two TIN control
buttons—TIN Breaklines and TIN Masspoints. You can use these two buttons to select the
desired values. For example, if you do not want any breaklines, select “None” under the TIN
Breakline button.
To fill the DTM with valid data, you can either run Automatic Terrain Extraction (See “Automatic
Terrain Extraction,” Chapter 37) or Interactive Terrain Editing (See “Interactive Terrain Edit,”
Chapter 39). After ATE has generated DTM data, you may want to smooth the DTM. Select None for
no smoothing DTM; select High for a very smooth DTM; select Medium for a medium smooth DTM;
and select Low for a DTM with little smoothing. High smoothing uses a 3X3 Smoothing
C o n v o l u t i o n twice and 5X5 Smoothing Convolution once and Plane Fill once (See “Area Editor”
on page 39-12 for more detail). Medium smoothing uses 3X3 Smoothing Convolution twice and
Plane Fill once. Low smoothing uses 3X3 Smoothing Convolution once and Plane Fill once. It is
recommended to use Low smoothing for both Regular Grid format and TIN format.
You use Automatic Terrain Extraction to populate the DTM if (1) you have a stereo image pair
or pairs that cover the region, and (2) the imagery does not contain too much clutter such as dense
trees and buildings which will disrupt the Automatic Terrain Extraction correlation algorithms.
Otherwise, you can use Interactive Terrain Editing to populate the DTM.
This guideline assumes that you do not want buildings modeled in your DTM. However, if you
want buildings modeled in the DTM, you are free to run Automatic Terrain Extraction, but you
should make sure that the DTM post spacing is sufficiently dense.
35.2.4 Automatic Terrain Extraction Strategies for Non-Adaptive ATE

If you are going to run Non-Adaptive ATE on the DTM, you should read this section, otherwise
you can skip it.
Automatic Terrain Extraction uses a correlation algorithm to compute the DTM from a stereo
image pair. The algorithm has a large number of input parameters that can be tuned to improve
the quality of the DTM. A given combination of parameters is called a strategy. You will be
provided with a choice of about a dozen strategies from which to choose. You should select the
Page 35-4 SOCET SET

strategy that is best suited to the imagery and its topography. The following table gives you
guidance on which strategy fits which conditions:
HIGH-ACCURACY
HIGH ACCURACY &
MAXIMUM HIGH- & REMOVES
HIGH-SPEED HIGH SPEED FOR
TERRAIN ACCURACY ARTIFACTS SUCH
EXTRACTION VERY DENSE DTM
SLOPE EXTRACTION AS BUILDINGS
GRIDS
OR TREES
20 deg. flat flat_1 flat_plus flat_dense

30 deg. rolling rolling_1 rolling_plus rolling_dense
50 deg. steep steep_1 steep_plus steep_dense
You select the strategy while you are running Create DTM. See Single versus Multiple Strategy
below for more details.
The table above shows the twelve most common Automatic Terrain Extraction strategies and
describes rules for when you should use each one. For example, if you want high-speed extraction
of a hilly area, you should use the “rolling” strategy. If you want high-accuracy extraction of a
fairly flat region, and you want Automatic Terrain Extraction to automatically remove any trees
(which would show up as “bumps” in the DTM otherwise) you should use the “flat_plus”
strategy.
A strategy named spot.strat is specifically developed for SPOT imagery and may be good for all
terrain types.
Note that Interactive Terrain Editing (ITE) contains tools to edit the DTM produced by Automatic
Terrain Extraction. Interactive Terrain Editing contains tools that will remove buildings, trees,
hedges, and other artifacts, tools that smooth the DTM, tools that remove forest canopies, tools
that set lakes to a flat elevation, and many other tools. Thus, if the DTM generated by Automatic
Terrain Extraction contains some areas of substandard quality, these areas can be corrected using
Interactive Terrain Editing. See “Interactive Terrain Edit,” Chapter 39 for more details.
35.2.5 Custom ATE Strategies for Non-Adaptive ATE

If you want to experiment with creating your own strategy files, see the “README” file in the
directory <install_path>/internal_dbs/DTM_STRATEGY for a complete explanation
of strategy options and strategy file naming convention.
35.2.5.1 Single versus Multiple Strategy

You must run Create DTM before running Automatic Terrain Extraction. One of the key inputs
to Non-Adaptive ATE is the strategy to use when correlating the images. There are two
approaches to selecting strategies for Non-Adaptive Automatic Terrain Extraction:
35.2.5.1.1 Single Strategy

Running Create DTM defines the DTM boundary and selects Non-Adaptive ATE Method and a
single strategy.
SOCET SET Page 35-5

35.2.5.1.2 Multiple Strategy

Running Create DTM defines the DTM boundary and selects Non-Adaptive ATE Method and
more than one strategy.
For most cases, you will use single strategy. However, you may use two or more strategies during
Non-Adaptive Automatic Terrain Extraction. With multiple strategies, Non-Adaptive ATE
generates DTM data using strategies one after another and the DTM data generated from the first
strategy are used as the initial data for the second strategy, and so on. With single strategy, Non-
Adaptive ATE stops after finishing the single strategy.
If you are not going to run Automatic Terrain Extraction (e.g. you do not have a stereo pair, or
the imagery is in an urban area with lots of big buildings), you should run Interactive Terrain
Editing immediately after running Create DTM.
35.3 Create DTM

Create DTM is divided into four tabs, ATE Images, DTM Properties, ATE Properties and Seed
DTM.
The ATE Images tab selections are as follows:
SELECT TO
DTM Name of the DTM currently selected. This field is not editable.
Available View the ATE Images available.
Selected View the ATE Images selected.
Save Save the DTM and close the Create DTM window. Only after having
completed all the Create DTM tabs, you press this button.
Save As... Save the DTM to a different file name. This button will bring up a dialogue
box and you must type a new DTM name. Only after having completed all
the Create DTM tabs, you press this button.
Close Closes the window without saving any changes.
Page 35-6 SOCET SET

35.3.1 DTM Properties
The DTM Properties tab selections are as follows:
SELECT TO
DTM Boundary Display the X/Long, Y/Lat, and Z/Elev of the DTM lower-left corner and
Lower-Left and Upper-Right upper-right corner. You can enter the lower-left corner and upper-right
corner coordinates.
Format Select DTM formats.
Spacing Units Display the units of the X and Y DTM post spacing: Feet, Meters, or
Seconds.
Posts Display the number of posts. It is computed from the DTM boundaries and
X, Y post spacing.
X/Y Spacing Display an editable text field containing the X and Y DTM post spacing in
the specified units.
BLANK SPACE
If you are generating a DTM as TIN, ATE will create TIN that have a
width approximately equal to the spacing you enter here.
Draw Polygon Draw a polygon with the extraction cursor. You must place the extraction
cursor on the ground when drawing the polygon.
Use Polygon Use the polygon as the DTM boundaries.
Use MBR Around Polygon Use the minimum bounding rectangle of the polygon as the DTM
boundaries.
SOCET SET Page 35-7

SELECT TO
Use ATE Image Select ATE images before you press this button. This will compute the
intersection areas of all images. When there are only two images (i.e. a
stereo image pair), this will compute a polygon of the intersection area of
the two images. When there are more than two images, this will compute
all possible intersection areas and union them to define DTM boundaries.
If there are isolated, intersection areas, they will be disregarded and you
get a warning message. You are not recommended to use the “Use ATE
Images” method to compute DTM boundary since the computed DTM
boundary may cover invalid imagery and cause problems for Automatic
Terrain Extraction.
35.3.2 ATE Properties
The ATE Properties tab selections are as follows:
SELECT TO
Adaptive ATE Use Adaptive ATE. You do not need to select a strategy.
Non-Adaptive ATE Select Non-Adaptive ATE Method, you must also select a strategy by
clicking ATE Strategies (See “Choosing an ATE Method” on page 35-3
for more information).
ATE Strategies Opens and ATE Strategies window. You add or delete strategies in this
window.
Eliminate Trees/ Eliminate objects like trees, buildings, artifacts, elevation blunders, etc.
Building/Other from the DTM after the ATE has completed.
Page 35-8 SOCET SET

SELECT TO
Maximum Number Image When the maximum number of image pairs per post is one (the default),
Pairs Per Post ATE selects the best image pair for every post to perform image
correlation. When the number is greater than one, ATE uses more than one
best image pair to perform image correlation. In this case, there are more
than one elevation per post and ATE performs elevation blunder detection
based on more than one elevation for the same post. In general, ATE
generates more accurate DTM at the cost of more computation.
Back Matching ATE uses back matching to reduce false image correlation and generates
more accurate DTM at the cost of more computation.
Minimum Height Enter minimum height of objects in elevation unit.
Smoothing Select None for no smoothing DTM;

Select Low for a DTM with little smoothing.
Select Medium for a medium smooth DTM
Select High for a very smooth DTM;
Precision Select High: ATE will perform image correlation down to minification
level (ml) 1:1;
Select Medium: ATE will stop at ml 2:1;
Select Low: ATE will stop at ml 4:1. This is used only by Adaptive ATE
Method. For Non-Adaptive ATE Method, they are found in strategy file.
TIN Breaklines Select Many, ATE will extract many breaklines.

Select Medium, ATE will extract some breaklines.
Select Few, ATE will extract few breaklines.
Select None, ATE will not extract any breaklines.
TIN Masspoints Select No thinning; ATE will select lots of points to TIN.
Select Medium thinning; ATE will select fewer points to TIN.
Select Heavy thinning; ATE will select even fewer points to TIN.
Select No masspoints; ATE will not select any points to TIN.
SOCET SET Page 35-9

35.3.3 Seed DTM
The Seed DTM tab selections are as follows:
SELECT TO
Seed Point BLANK SPACE

Automatic Use if the relative linear error of the seed DTM is known.
RSET Seed point usage will stop at the selected minification level.
Available View the seed DTMs available.
Selected View the seed DTMs selected.
See “Create a DTM for NGATE - NGATE Properties” for more information.
35.4 Executions
35.4.1 Define DTM Boundaries

There are four ways to define DTM boundaries:
• Enter X/Long and Y/Lat coordinates

• Draw Polygon using Polygon

• Draw Polygon using MBR around Polygon
• Use ATE Images
You must use them one at a time. If you use more than one way at a time, the results from the one
you selected last, will be the one used to determine the DTM boundaries.
A typical scenario would be as follows:
1. Click Draw Polygon in the Define DTM Boundaries section of the DTM Property tab.
2. Sketch is invoked.
3. An information dialog box pops up prompting you to proceed to draw polygon.
4. After toggling to the extraction cursor, draw a polygon with the LMB, then press the RMB
to accept.
5. The information dialog box goes away.
6. View findings on the Create DTM window.
When drawing a polygon, the cursor must be on the ground

such that a good initial average DTM elevation can be
computed. For very steep terrain, you must make sure that the
average elevation of the DTM boundary vertices is close to the
median elevation of the terrain. The left-most and right-most
DTM posts may be assigned OUTSIDE_BOUNDARY FOM and
therefore, not used by any application.

35.4.2 Terrain Creation

1. Load imagery onto the main image display if you want to draw a polygon to define DTM
boundaries. If you use ATE Images or Lower-Left and Upper-Right Corners coordinates to
define DTM boundaries, you do not have to load imagery.
2. Click Extraction > Terrain > Automatic Extraction or Extraction > Terrain > Interactive
Edit on the main workstation window.
3. Do one of the following on the ATE or ITE window: Click File > Create DTM.... Select
the ATE Images tab and select the images.
4. Select the DTM Properties tab.
a. Select DTM Format as TIN or Grid.
b. Define DTM boundaries and post spacings. If the DTM Format is TIN, the spacing
will determine the average size of the triangles.
c. Change Spacing Units to the desired units; change X and Y Spacings to the desired
spacings.
d. Use one of the four ways to define DTM boundaries.
• When using Use Polygon or Use MBR (Rectangle) Around Polygon, toggle
to the extraction cursor and delineate a polygon by pressing the LMB. At the
same time, adjust the Z at each vertex to lie approximately at ground level.
When all points of the new polygon are present, accept the polygon by
pressing the RMB. You must have loaded images to use these two methods
to define DTM boundaries.
• When using Use ATE Images, you must have selected images. This will
create a DTM that covers all overlapping areas of the selected images. If you
selected more than two images, DTM boundaries are defined by the union of
all the overlapping areas. You must use one the four methods in determining
DTM boundaries. See “Define DTM Boundaries” on page 35-10.
5. Select the ATE Properties tab to select an ATE Method and specify DTM filter parameters.
6. Click either Adaptive or Non-Adaptive. If you select Non-Adaptive, you must click ATE
Strategies, to select any strategies.
7. If you selected Adaptive, and you want to Eliminate Trees/Buildings/Other, you must click
Eliminate Trees/Buildings/Other and type their Height and Width values. You may also
specify Smoothing and Precision requirements for your DTM.
To eliminate an object, the number entered for height must be

smaller than the height of the objects AND the number entered
for width must be greater than the width of the object. Both
conditions must be met for the object to be eliminated.
8. [optional] Select Seed DTM tab to select seed DTMs and select Seed Point usage.
9. In the Create DTM window, click Save to save all changes; click Save As to save all
changes to a new DTM, and click Cancel to disregard all changes.
35.5 Next Step

After creating a DTM within ATE, you have two choices:
• Run the extraction phase of ATE to fill the DTM with valid topography

• Run Interactive Terrain Editing (ITE) to manually edit the DTM

Chapter 36
Terrain Graphics
Terrain Graphics covers displays onto imagery.
36.1 Overview
SOCET SET provides the capability to display Digital Terrain Model (DTM) data on the
workstation monitors. You can change several display parameters: DTM representation (mesh,
contours, profile, etc.), post spacing (every nth post), and color-coding technique.
36.1.1 When to Use Terrain Graphics

Terrain Graphics is not a stand-alone process. It is activated from within any one of the
SOCET SET applications listed below:
• Interactive Terrain Edit—Display DTM, Edit DTM, and Convert DTM to vector format.
• Terrain Analysis—Generate Line-of-Sight overlay.
• DTM Registration—Register or warp a DTM.
For detailed instructions, click the chapter corresponding to that application.
36.1.2 Setup DTM and Setup Overlay Preferences

The Setup DTM and Setup Overlay panels are identical, but function independently. They are
located in the applications’s preference window.
SOCET SET Page 36-1

Chapter 36 - Terrain Graphics
The Setup DTM window’s selections are as follows:
SELECT DESCRIPTION
Mode Dots are used to draw the terrain posts as dots. Use the Graphics Width
control to choose the size of the dots.
BLANK SPACE
Icon is used to draw each terrain post with the an icon. If the Graphics
Width is set to thin, then the icon <install_path>/
internal_dbs/ICONS/point.icn is used. If the Graphics
Width is set to thick, then the icon <install_path>/
internal_dbs/ICONS/big_point.icn is used.
BLANK SPACE
X-Profile interpolates a solid line through all the terrain posts in the X
direction. Draws Breaklines if the DTM format is TIN.
BLANK SPACE
Y-Profile interpolates a solid line through all the terrain posts in the Y
direction.
BLANK SPACE
Mesh is used to draw the terrain data as a grid, with the grid
intersections at the posts. Draws triangles if the DTM format is TIN.
BLANK SPACE
Editable Contours is used to draw contour lines with small line
segments cell by cell or triangle by triangle. Use this mode if you wish to
display contours during Interactive Terrain Edit.
BLANK SPACE
Continuous Contours is used to draw contour lines continuously, line
by line. Use this mode if you wish to capture the contours in a feature
database only.
BLANK SPACE
Editable Contours & Dots are used to draw contour lines with small
line segments and dots. Use this mode if you wish to display contours
during Interactive Terrain Edit.
Page 36-2 SOCET SET

SELECT DESCRIPTION
Line Style Sets the line style for the line drawing modes. Defaults to Solid.
Graphics Width Sets the width of editable contours and continuous contours, dots, and
icons. Defaults to Thin.
Contour Interval Set the vertical interval between contour lines (in the project Z units).
Index Interval Set the number of contour between each index interval.
X/Y Steps Draw every nth profile for profiles or mesh.
Auto XY Steps and Contour Set XY steps and contour interval automatically based on level of details.
Interval You use this option when viewing DTM only.
Color Source Monochrome uses the color specified in the Monochrome Color box to
draw the terrain file. Select the color by clicking on the monochrome
color box.
BLANK SPACE
Elevation uses the color assignment that are a function of elevation
data in the terrain file.
BLANK SPACE
Figure of Merit uses the color assignment that are a function of the
Figures of Merit in the terrain file. See “Figures Of Merit,” Appendix F
for more details.
216 Color Select this option, and ranges are drawn in 216 colors, instead of 8
colors. The default 216-color pallet is used. The colors cannot be
modified. The elevation color is selected based on a linear scale between
the minimum and maximum elevation values in the range window.
8 Color Select this option, and ranges are drawn in 8 colors. The 8 Colors and
color ranges can be edited with the Color Range Window.
Edit Ranges This button opens the color range window.

• In 216 color mode only the min and max range values are use.
• In 8 color mode, all ranges are used.
Default range values are based on the min and max elevation for the
project.
Cancel Close the DTM or Overlay Setup windows without saving changes.
OK Closes the Preference Setup windows. All modifications to the controls

remain in effect until you load a new file or exit the application.
36.2 DTM and Overlay Range Windows

Click Edit Ranges... in the DTM Setup or Overlay Setup windows to display the respective Range
window. You use this window when you want to color-code the data based on the elevation, or
Figure of Merit. You are provided with seven color bands. This window lets you set the elevation
limits of each band.
These range settings are saved between sessions in the Interactive Terrain Editor.
SOCET SET Page 36-3

The DTM and Overlay Range window’s selections are as follows:
SELECT TO
Set Ranges From DTM Set color range based on selected DTM and uniformly distributed ranges.
Set Ranges From Min To Set color ranges uniformly distributed from the minimum range to the
Max maximum range.
Done Close the DTM or Overlay Range window. All modifications to the
controls remain in effect until you exit the application.
Cancel Close the DTM or Overlay Range window without saving changes.
36.3 Executions Terrain Graphics
36.3.1 Displaying Terrain Graphically

1. Load one or more images in the main workstation window. If you have no imagery
available, or if you want to use Graphic Projection to view the DTM from an arbitrary
vantage point (that is, not overlaid on imagery), you should load the
GRAPHICS_ONLY.sup support file.
2. Click Extraction > Terrain > Interactive Edit on the main workstation window to bring up
the Interactive Terrain Edit window.
3. Click File > Open DTM on the Interactive Terrain Edit window. Choose the DTM you wish
to display and click OK.
4. Click Options > Preferences to open the Preference window, where you can select Setup
DTM, or you can click Setup DTM Graphics icon on the toolbar, so you can specify how
to draw the terrain data. See “Setting Up the DTM Graphics” on page 36-5 for more details.
Click OK to apply the changes and close the window.
Page 36-4 SOCET SET

5. Click Draw to draw the terrain on the display. You may need to recenter the image or
change the image’s minification level to see all the terrain data on the screen.
6. Toggle Auto Draw to On if you want to automatically redraw the terrain graphics every
time you refresh graphics or reload the image.
36.3.2 Setting Up the DTM Graphics

Use the following sequence of steps to set up the way Interactive Terrain Edit draws the DTM:
1. Click Options > Preferences to open the Preference window, where you can select Setup
DTM, or you can click Setup DTM Graphics icon on the toolbar.
2. Choose the mode to display DTMs: profiles, mesh, contours, etc.
3. Use the remaining features of the Setup panel to establish the characteristics of the
graphics, such as, contour interval, post spacing (i.e. draw every nth post), color, and line
width.
4. Click OK to apply changes and close the window.
36.3.3 Displaying an Overlay File

In normal use, you only load one DTM at a time. However, you may load a second DTM, called
an Overlay file. Use of the Overlay file is optional. It allows you to display two different DTMs
simultaneously.
If you wish to draw two terrain files simultaneously, load the second DTM by clicking File >
Open Overlay DTM on the Interactive Terrain Edit window. The graphical representation of the
Overlay file is set using the Setup Overlay Graphics button, which behaves just like the DTM
Setup procedure described above. The Graphics Setup mode of each of the two files is
independently adjustable. For example, the primary terrain file can be displayed in mesh, and the
secondary file (the Overlay file) can be contour lines. You can use the same file as both the
primary and secondary files. Use the Enable DTM/Overlay Graphics toggle buttons to turn the
displays of the two files on and off independently.
36.3.4 Converting Terrain Graphics to Feature Vectors

To make a hardcopy of terrain graphics, you can
• Draw the terrain graphics on the monitor and then make a screen dump
• Capture the terrain graphics to a feature file, run Image Map, and specify the feature
file as an input
• Run Image Map or Print Graphics concurrently while displaying terrain graphics to
transfer the graphics directly into Image Map. See “Image Map” on page 52-7 for
details.
Converting terrain graphics to feature vectors works for all types of terrain graphics, including
break lines and mass points, but is most commonly used for Continuous Contour Lines. It is not
recommended for other graphics types because of the size of the resulting feature databases and
the length of time required for the conversion.
The steps for converting terrain graphics to feature database are:
1. Click Extraction > Terrain > Interactive Edit on the main workstation window to start
Interactive Terrain Edit.
SOCET SET Page 36-5

2. Click File > Open DTM and choose the file you wish to convert. Interactive Terrain Edit
will convert the entire DTM to feature database for you.
Click Options > Preferences to open the Preference window, where you can select Setup DTM,
or you can click Setup DTM Graphics icon on the toolbar.
3. DTM Setup window will appear.
4. Set the terrain graphics parameters as desired. If you are drawing contours, set Mode to
Continuous contours, NOT the Editable contours. Click OK to close. See “Graphical
Options” on page 36-7 for an explanation of the options.
5. Load an image for preview purposes. Any image will do. Draw the DTM on the monitor
and verify that the graphics are satisfactory and complete.
6. Click File > Write DTM to Feature File on the Interactive Terrain Edit window.
Interactive Terrain Edit prompts you for the name of a feature database to write the output
to. Enter the name of a feature database to receive the contours and click OK to proceed.
7. Review and edit the feature database you just created using Feature Extraction. If it is
satisfactory you may make an image map or perform other processing.
36.3.5 Displaying Terrain without Imagery

If you want to display a DTM, but you have no imagery:
1. Load the GRAPHICS_ONLY support file onto the main image display.
2. Run ITE and load the DTM as described above. Turn on Auto Draw Terrain Graphics on the
toolbar.
3. Run Coordinate Measurement; select the Move To Point option and move to a point that is
in the vicinity of the DTM. (You may have to look in the DTM *.dth header file to find
point that is near the DTM).
4. Use the Graphics Projection window (under the Preferences menu) to adjust the scale and
viewpoint. You can also adjust the scale by changing the minification level on the Display
Utility window.
36.3.6 Shaded Relief

Viewing the shaded relief of a DTM is a good way to identify possible defects in the elevation
data. A shaded relief view often reveals artifacts that are not visible when the DTM is viewed as
contour lines, dots, or mesh.
The way to view a DTM as shaded relief and to save this Shaded Relief image is through the
Shaded Relief option within ITE. See “Terrain Shaded Relief (TSR) Options” on page 39-6 for
details.
36.3.7 Contour Lines

Continuous contour lines show lines of constant elevation. Thinning of continuous contour lines
by default, is on. To turn thinning off:
% setenv CONTOUR_THIN_WIDTH 0.0
To tune thinning enter the following:
% setenv CONTOUR_THIN_WIDTH <value>
Page 36-6 SOCET SET

where <value> is the width (in project units) of the thinning “tube.” An example would be if your
DTM has a post spacing of 5 meters, you might set the thinning to a value around:
% setenv contour_thin_width 1.5
Thinning widths must be positive. Smaller values do less thinning; larger values do more
thinning. A thinning value of zero means “do no thinning.”
Thinning does not apply to editable contours; however it does applies to both Grid and TIN
DTMs.
36.3.8 Spline of Continuous Contour lines

By default, spline is on. To turn spline off:
% setenv SPLINE no
Spline does not apply to editable contours; however, it does apply to both Grid and TIN DTMs.
36.4 Batch Processing - Terrain Graphics

This process will output terrain graphics, such as contour lines, to a Feature DB.
The start command is:
% start_socet -single ite -batch -s setting_file
36.4.1 Graphical Options

The “Drawing mode” parameter can have any value of 0 to 7, which is defined by the following
table:
DRAWING MODE BATCH GRID TIN GRAPHICS
dots 0 dots masspoints and breaklines
icons 1 icons masspoints only
x-profile 2 x-profiles breaklines only
y-profile 3 y-profiles breaklines only
mesh 4 mesh triangle edges
editable contours 5 contours contours and breaklines
continuous contours 6 contours contours only
contours and dots 7 contours contours, breaklines, and dots

and dots
The project, feature, and DTM names must include full path.
SOCET SET Page 36-7

Sample ITE settings file:
setting_file 1.1
ite.project <install_path>/data/zhang2.prj
ite.dtm <install_path>/data/zhang2/zhang_good
ite.feature_db_filename <install_path>/data/zhang2/ite_test
tg.underlay_contour_interval 100
tg.underlay_index_interval 5
tg.underlay_drawing_mode 7
tg.underlay_monochrome_color 3
tg.underlay_graphic_width 0
tg.underlay_line_style 0
Page 36-8 SOCET SET

Chapter 37
Automatic Terrain Extraction

Automatic Terrain Extraction covers the process of ATE in
relation to end products.
37.1 Overview
Automatic Terrain Extraction (ATE) is a very important SOCET SET application since terrain
data is the foundation of most digital photogrammetric products. End-products such as
orthophotos, perspective scenes, and image maps each require terrain data. The more accurate
your terrain data is, the more accurate your end-products will be.
37.1.1 When to Use Automatic Terrain Extraction

You use Automatic Terrain Extraction when you have one or more stereo image pairs and you
wish to create a Digital Terrain Model (DTM) in the overlap region.
37.1.2 Adaptive vs. Non-Adaptive ATE

There are two methods of computing elevation data: Adaptive ATE and Non-Adaptive ATE.
Adaptive ATE uses an inference engine to generate image correlation strategies adaptively based
on terrain, while Non-Adaptive ATE requires a user specified strategy.
You should use Adaptive ATE, unless you have a reason to use a particular strategy.
Non-Adaptive Terrain Extraction uses a correlation algorithm to compute the DTM post heights
from a stereo image pair. The algorithm has a large number of input parameters that you can tune
to improve the quality of the DTM. A given combination of parameters is called a “strategy.” You
will be provided with a choice of about a dozen strategies from which to choose. See “Automatic
Terrain Extraction Strategies for Non-Adaptive ATE” on page 35-4. You should select the
strategy that is best suited to the imagery and its topography. You select the strategy during
Create DTM. There are an environment variable USER_HIGHSLOPE_SPIKE which controls
which parameters are used for HIGH_SLOPE-and SPIKE detection. For non-adaptive, when you
set it to YES, ATE will use the parameters from the strategy file. See “Creating a DTM” on
page 35-2.
If you want to experiment with creating your own strategy files for use in non-adaptive ATE, see
the “README” file in the directory <install_path>/internal_dbs/DTM_STRATEGY
for a complete explanation of strategy options and strategy file naming convention.
SOCET SET Page 37-1

Chapter 37 - Automatic Terrain Extraction
Feature
Database
MERGE DTM
[OPTIONAL] IMPORT
LEFT IMAGE RIGHT IMAGE

SEED DTM
(OPTIONAL)
AUTOMATIC
TERRAIN
EXTRACTION
INTERACTIVE TERRAIN
DTM(S) WITH GRAPHICS
TERRAIN ELEVATION POSTS
EDITING DISPLAY
37.1.2.1 Steps to Execute Before ATE (Adaptive) Refer to figure above.

1. Import stereo pair(s).
2. Solve the sensor models of the stereo pair(s) (by running Interior Orientation and
Triangulation)
3. [Optional] Pairwise rectify the images (or epipolar resample the images).
4. Minify the rectified images if step 3 is performed or minify the raw images if step 3 is not
performed.
5. Create the DTM.
6. [Optional] Merge geomorphic features (if available) into the DTM before and/or after ATE.
37.1.2.2 ATE in Urban Areas

Generally, you should not run Automatic Terrain Extraction on large-scale imagery of urban
areas (where the buildings appear big) because Automatic Terrain Extraction will model the
buildings. In other words, Automatic Terrain Extraction does not distinguish between buildings
and ground so the DTM will climb up over the building roofs. In this situation, you may want to
bypass Automatic Terrain Extraction and proceed directly to Interactive Terrain Editing after
creating the DTM. However, if the imagery contains only a few buildings, it may be more
efficient to run Automatic Terrain Extraction and then remove the buildings using one of the
Interactive Terrain Editing area edit tools. The eliminate trees, building, and other options can
bring down the DTM from the tops of buildings and trees to the ground where the trees and
buildings are sufficiently apart from each other.
Page 37-2 SOCET SET

37.1.2.3 Grid vs. Triangular DTM format

There are two DTM data formats:
• DTM Regular Grid
DTM Regular Grid is a two-dimensional array of elevation data points called posts.
The array of posts is always aligned North-South-East-West with the project
coordinate system.
• DTM TIN Triangles

DTM TIN Triangles stores critical points (or mass point) and breaklines. Critical
points and breaklines can model the terrain very well without redundant data.
Both the Adaptive ATE and Non-Adaptive can generate both DTM data formats. On large-scale
imagery of urban areas, you may bypass ATE and directly use Interactive Terrain Editing tools
to generate a DTM TIN Triangles.
37.1.2.4 Algorithm
Automatic Terrain Extraction automatically creates a digital terrain model (DTM) from a stereo
image pair or stereo pairs. The DTM is stored in the project coordinate system. You specify the
density (the inter-post spacing) when you create the DTM with Create DTM (See “Creating a
DTM” on page 35-2 for more information). You can output the DTM as a digital end-product
(e.g. exported as a DTED file) or you can use the new DTM to support the generation of additional
products within the workstation, such as ortho-images, perspective scenes, and shaded relief
scenes.
Automatic Terrain Extraction determines elevations by measuring X-shifts (X parallax) in the
rectified images. Automatic Terrain Extraction is an iterative algorithm which begins with the
small scale minification level image and a sparse post spacing, and increases the post density for
each minification level, until the 1:1 minification level is reached. Upon completion, the height
and accuracy of every elevation post is stored in the output DTM.
37.1.2.5 Accuracy
When Automatic Terrain Extraction is complete, the accuracy of the resulting DTM will be
represented with 90% probability Circular (XY) Error and Linear (Z-elevation) Error. When there
is accuracy file from Triangulation such as the covariance file, the CE/LE accuracy values are the
absolute CE/LE including the errors from Triangulation as well as DTM image correlation errors.
When there is no accuracy file, the CE/LE accuracy values are error estimates of the DTM image
correlation only. So the CE/LE accuracy values are relative CE/LE. Before exporting the DTM
to another terrain format (such as DTED or DEM), be sure to review the DTM and its CE/LE
accuracies in Interactive Terrain Edit.
37.1.2.6 Successful Extraction

It is difficult to define a quality metric for automatic terrain extraction, but on the average 70%
to 95% of the posts generated by Automatic Terrain Extraction do not have to be edited by the
operator. For those posts generated by Automatic Terrain Extraction that are not satisfactory, you
can review and adjust them using the Interactive Terrain Editing edit tools. When DTM data
format is TIN Triangles, the Adaptive ATE extracts elevations of only critical points and
breaklines. Critical points are those points where terrain slope changes. When a point elevation
cannot be interpolated from its neighbor critical points with a specified accuracy, it is a critical
point. Breaklines are 3D polylines on which the DTM curvature is greater than some threshold
SOCET SET Page 37-3

value. Only points and breaklines with good FOM are written to TIN Triangles from ATE.
Therefore, you may need to add more critical points and breaklines to the TIN Triangles using
the Interactive Terrain Editing tools.
37.1.2.7 Data that is not Modified

ATE will not modify posts with FOMs of MANUALLY_MEASURED, OUTSIDE_
BOUNDARY, LAKE_FILLED, GEOMORPHIC, PLANE_FILLED, and DWI (See “Figures Of
Merit,” Appendix F for more information) when DTM format is Regular Grid. The Adaptive ATE
will not change any existing critical points and breaklines in the TIN Triangles. Run ATE only
once when DTM format is TIN Triangles.
37.1.2.8 Inputting Geomorphic Data to ATE

If you have a feature database that contains geomorphic features (such as drains, lakes, ridges,
and breaklines) you should run DTM/Feature Merge before or after Automatic Terrain
Extraction. DTM/Feature Merge will modify the DTM to conform to the features. After merging
the features, you should review the results with Interactive Terrain Editing.
Normally you merge features into the DTM after you run Automatic Terrain Extraction, but you
can also run DTM/Feature Merge before Automatic Terrain Extraction to help Automatic Terrain
Extraction generate higher-quality output. See “DTM/Feature Merge,” Chapter 44 for more
details.
Spot heights and planimetric data can be used to help ATE to generate more accurate DTM TIN.
You prepare spot heights and planimetric data in ASCII DTM format and then run ASCII DTM
import. You must select TIN Triangles as DTM format. When you Create DTM, you select the
imported spot heights and planimetric data DTM as seed DTM. ATE will keep the spot heights
and planimetric data in the final DTM TIN Triangles and use those data to generate more accurate
DTM.
37.1.2.9 Inputting a Seed DTM to ATE

If you have a DTM that you would like to use to help ATE producing more accurate DTM, you
may use it as a seed DTM. See “Using a Seed DTM” on page 37-8 for procedures.
37.1.2.10 Automatic Extraction of Breaklines

To extract breaklines, you must select an appropriate post spacing. A BSpline surface model is
used to fit into grid. When the curvature is greater than some threshold value, it is considered as
a breakline post. The BSpline surface model uses a 5x5 grid window for fitting. To extract a
breakline, you must make sure that there are at least 2 posts on either side of the breakline post
and the 5 posts form a bell shaped curve. This may require a very small post spacing if you want
to extract a lot of breaklines. To reduce the number of mass points, you can select HIGH
Smoothing and Heavy thinning.
37.2 Automatic Terrain Extraction

Automatic Terrain Extraction extracts the DTM data from the polygons you selected using the
method (either Adaptive ATE or Non-Adaptive ATE), the strategies, and the format (either
Regular Grid or TIN Triangles) you specified when you created the DTM with Create DTM. To
Page 37-4 SOCET SET

obtain this window click Extraction > Terrain > Automatic Extraction on the main workstation
window.
The Automatic Terrain Extraction window’s selections are as follows:
File > Load Project Prompts you to select a project file (available only in stand-alone).
File > Create DTM... Prompts you to create view or edit a DTM.
File > Open DTM... Prompts you to select a DTM.
File > Exit Exits Automatic Terrain Extraction.
Options > Display Statistics Displays the Automatic Terrain Extraction Statistics window. Automatic
Terrain Extraction updates the fields in this window continuously after you
click Start.
Options > Extraction Invokes the Extraction Options window. If your system has more than one
Options CPU, you can select more than one section. ATE will divide a large DTM
into smaller sections and compute elevations of different sections utilizing
multiple CPUs, and then merge them once all the sections have been
completed.
SELECT TO
DTM Display the name of the DTM you selected.
ATE Method Display the name of ATE method selected to generate DTM data.
Strategy File Display the name of strategy file selected. If you selected Adaptive ATE,
this field is always adapt.strat.
X/Lon Display the DTM Post spacing in the X (longitude) direction.
SOCET SET Page 37-5

SELECT TO
Y/Lat Display the DTM Post spacing in the Y (latitude) direction.
Percent Complete Display the percent of posts processed
Percent Measured Display the percent of successful correlation
Posts per Second Display the number of posts processed per second
Number Posts Display the number of posts in the DTM
Lower Left Display the lower-left corner of the boundary of the DTM (X, Y, and
elevation).
Upper Right Display the upper-right corner of the boundary of the DTM (X, Y, and
elevation).
Start Start ATE
Abort Abort ATE
37.2.1 ATE Statistics Window

The ATE Statistics window displays various pieces of information about the status of the terrain
extraction correlation algorithm while Automatic Terrain Extraction is running.
To obtain this window, click Options > Display Statistics on the Automatic Terrain Extraction
window. Click Done to close window.
Page 37-6 SOCET SET

37.2.2 ATE Extraction Options Window

You can use the Extraction Options window to speed up DTM generation if your system has more
than one CPU. You select the number of sections based on the number of CPUs your system has.
ATE will divide the DTM into sections and utilize multiple CPUs to compute elevations of
different sections, and then merge them after completion. You can specify the number of overlap
posts for dividing the whole DTM into sections. The “Cleanup temps” option deletes the
intermediate section files.
To obtain this window, click Options > Extraction Options on the Automatic Terrain Extraction
window.
37.3 Executions
37.3.1 Automatic Terrain Extraction
While running ATE, you cannot change the project. If you need
to execute ATE function on another project, you have two
options:
1. Use the main menu to change to the desired project, then run
ATE again.
2. Activate ATE from a command line (in a shell window) by
starting ATEs executable, namely ate, with start_socet -single...
as described in the Batch Processing.
The following steps define the sequence for you to follow when executing Automatic Terrain
Extraction:
When you selected more than 2 images, all images must NOT
have been rectified. ATE will rectify images on the fly. When
you have selected only 2 images, the image can be either
rectified or non-rectified.
Before you run Automatic Terrain Extraction, you must first

run Create DTM to specify the DTM boundary, post spacing,
images, and DTM data format.
1. Click Extraction > Terrain > Automatic Extraction on the main workstation window to
start Automatic Terrain Extraction.
2. Click File > Load Project on the Automatic Terrain Extraction window (stand-alone only)
to select a project file (or use the default project as displayed in the Project Field).
SOCET SET Page 37-7

3. Click File > Open DTM... on the Automatic Terrain Extraction window to select a DTM.
Make selection and click OK. To Create a new DTM click File > Create DTM....
4. [Optional] Click Options > Display Statistics... on the Automatic Terrain Extraction
window to bring up the ATE Statistics window. Click Close when done.
5. Click Start to begin extracting the terrain.
a. Statistics on both the Automatic Terrain Extraction Statistics window and the
Automatic Terrain Extraction window will be updated as Automatic Terrain
Extraction progresses.
b. The message DTM Collection Complete will be displayed when Automatic Terrain
Extraction finishes.
If your output DTM is poor quality (e.g. DTM is flat, or the GUI
indicates poor success percentage), try re-running Create DTM
and increase the number of posts.
See “Execution - Start At” on page E-7
37.3.2 Using a Seed DTM

Seed terrain data is topographic data that ATE can use to produce more accurate results. Seed data
can come from any source, such as:
• DTED files
• DEM files
• Pre-existing terrain data
• Triangulation ground points (including tie points)
If you ran Triangulation before ATE and want to use the ground points as seed data for ATE, you
must:
1. Run Triangulation, load the triangulation job, and click ASCII Ground Points (on the File
Export menu). This will create a text file with a *.agp suffix containing the ground points.
2. Run ASCII Terrain Import application and import the *.agp file. Use the Seed Point format.
See “Execution - Importing an ASCII Tie Point File to DTM” on page 17-6 for a detail
example.
ATE has two ways to use seed data: “Preserve Permanent” and “Preserve Until Last Pass”. You
choose which technique to use in the Seed option on the ATE Seed DTM window. Permanent
means that ATE will pass-through the elevation values from seed points without changing them.
Last Pass means ATE will keep the seed elevation values up until the final correlation pass, but
it will change the values on the final pass based on the imagery.
The steps for using seed data are:
1. Obtain seed terrain data. This could be a DTED file, tie points, or any other source.
2. Convert the seed terrain data into a SOCET SET terrain file by running any Terrain Import
application (such as ASCII Terrain Import).
3. [optional] Run ITE and review the seed terrain file. You may change any elevation data.
All data points with FOM values larger than 21 (also called START_GOOD_FOM - See
“START_GOOD_FOMS” on page F-3 for details) will be used by ATE as seed data. Points
with FOM less than 21 will not be used by ATE as seed data. If there are any data points
Page 37-8 SOCET SET

that you do not want to use as seed data, use the ITE Set FOM area tool to set the FOM to
value 3 (INSIDE_BOUNDARY).
4. Run ATE. Clicking File > Create DTM... Select a DTM; select Images, define DTM
Properties, and define ATE Properties. Select the Seed DTM tab in the window. Set the
Seed option. Select the seed DTMs. See “Seed DTM” on page 35-10
5. Click Save to save the DTM.
6. Click Start on the ATE main window. Wait for ATE to complete. (Alternatively, click
Start At... to run ATE in batch mode).
7. [Optional] Load the terrain file into ITE and review it. All the seed points will have a FOM
value of SEED_POINT.
37.4 Batch Processing - ATE

COMMAND LINE:
% start_socet -single ate -batch -s setting_file
ate ate
There are several ways to run ATE in batch mode. You can run the ATE in batch mode for the
following scenarios:
1. ATE with an existing .dth file that was generated previously with the ATE GUI.
2. ATE without a .dth file.
Keywords necessary for scenario #1 (with an existing .dth file):
KEYWORD DESCRIPTION
ate.project The full path of the project in which your DTM will reside.
ate.dtm The DTM to populate. No extension permitted. The DTM is selected from
the .dth files in you project directory, after a DTM polygon has been
created via the Extraction > Terrain > Automatic Extraction >
Create DTM.
The following are Extra Keywords available for multiple processor machines (the defaults are set
to handle the single processor case):
KEYWORD DESCRIPTION
ate.overlap For Multi-Processor Batch. The overlap in Y spacing posts between

sections of the DTM. Default is 1.
ate.sections For Multi-Processor Batch. The number of processors available for ATE.
Do not set this higher than the number of CPU’s you have available.
Default is 1.
SOCET SET Page 37-9

KEYWORD DESCRIPTION
ate.feather For Multi-Processor Batch. Feathering setting for the DTM’s (YES or
NO). Default is YES.
ate.precedence For Multi-Processor Batch. Precedence when merging DTM sections

(RESOLUTION, FOM, RES_FOM, FOM_RES, ORDER_OF_INPUT).
Default is FOM.
ate.union For Multi-Processor Batch. Merge will Union the DTM’s. No other option
is available in this scenario. Default is UNION.
ate.cleanup For Multi-Processor Batch. Cleans up temporary files after ATE completes
(TRUE or FALSE). Default is TRUE.
Below is an example of multiple processor ATE with a ,dth file. Notice that the “ate.sections” is
set to 2, which enables the batch process to utilize 2 CPU’s.
setting_file 1.1
ate.project C:\SS_DATA\Data\plains.prj
ate.dtm C:\SS_DATA\Data\plains\dth_existing
ate.overlap 1
ate.sections 2
ate.cleanup 1
Keywords available for scenario #2 (without a .dth file):
KEYWORD DESCRIPTION
ate.project The full path of the project in which your DTM will reside.
ate.dtm_output The name of the DTM to create with the .dth extension.
ate.format The DTM format (DTM_GRID or DTM_TIN). Default is DTM_GRID.
ate.strat The strategy to use, with the .strat extension. The default is no strategy.
ate.obstruction_height The maximum height for obstructions. Default is 0.0.
ate.obstruction_max_slope The maximum slope for obstructions. Default is 0.0.
ate.eliminate_obstruction The eliminate obstructions option (TRUE or FALSE). Default is FALSE.
ate.smoothing Smoothing option for the DTM (NONE_SMOOTHING,

LOW_SMOOTHING, MEDIUM_SMOOTHING, or
HIGH_SMOOTHING). Default is NONE_SMOOTHING.
ate.precision Precision option for the DTM (HIGH_PRECISION, MEDIUM

PRECISION, or LOW_PRECISION). Default is HIGH_PRECISION.
ate.breakline TIN Breaklines setting (DENSE_BREAKLINE, MEDIUM_BREAKLINE,

SPARSE_BREAKLINE, or NONE_BREAKLINE). Default is
NONE_BREAKLINE.
ate.masspoint TIN Masspoints thinning option (DENSE_MASSPOINT,

MEDIUM_MASSPOINT, SPARSE_MASSPOINT, or
NONE_MASSPOINT). Default is DENSE_MASSPOINT.

KEYWORD DESCRIPTION
ate.images Images which ATE will use. Each support file needs its own line with the
“images” keyword.
ate.post_spacing_unit Units which ATE will use (UNIT_SECONDS, UNIT_FEET,

UNIT_INTERNATIONAL_FEET, UNIT_US_SURVEY_FEET, or
UNIT_METERS). Default is UNIT_METERS.
ate.seed_dtm Specifies seed DTM with full path and.dth extension.
ate.num_verts The number of vertices that bound the DTM.
ate.x_post_spacing The post spacing in the X direction. Default is 10.0 X post spacing units.
ate.y_post_spacing The post spacing in theY direction. Default is 10.0 Y post spacing units.
ate.adaptive Use Adaptive ATE (1 or 0). Use 1 for on, and 0 for off.
ate.seed_point_option Seed Point setting (Automatic, RSET1, RSET2, RSET4, RSET8, RSET16,
RSET32, or RSET64). Default is Automatic.
ate.back_match Back Matching option. Use 1 for on, and 0 for off. Default is 0.
ate.num_image_pairs Sets the maximum number of image pairs used in computing each
elevation post. Default is 1.
ate.polygon_verts The polygon vertices of the boundary in XYZ. Each vertex must have its
own line with the “polygon_verts” keyword.
NOTE: The Z values of the polygon vertices are actually computed
from the GROUND_ZERO values of the selected support files.
Below is an example for running ATE batch without an existing .dth file:
setting_file 1.1
ate.project d:\data\t_sdap_utmMSLm_nad83.prj
ate.format DTM_GRID
ate.dtm_output junkBatchSet.dth
ate.images D:/data/t_sdap_utmMSLm_nad83/1_15.sup
ate.images D:/data/t_sdap_utmMSLm_nad83/1_16.sup
ate.polygon_verts 479886.0 3624483.0 16.5
ate.num_verts 4
ate.adaptive 1
ate.x_post_spacing 1.0
ate.y_post_spacing 1.0
ate.post_spacing_unit UNIT_METERS
ate.back_match 0
ate.num_image_pairs 1
ate.smoothing HIGH_SMOOTHING
ate.precision LOW_PRECISION
ate.breakline MEDIUM_BREAKLINE
ate.masspoint SPARSE_MASSPOINT
The following are Extra Keywords available for multiple processor machines (the defaults are set
to handle the single processor case):

KEYWORD DESCRIPTION
ate.overlap For Multi-Processor Batch. The overlap in Y spacing posts between

sections of the DTM. Default is 1.
ate.sections For Multi-Processor Batch. The number of processors available for ATE.
Do not set this higher than the number of CPU’s you have available.
Default is 1.
ate.feather For Multi-Processor Batch. Feathering setting for the DTM’s (YES or
NO). Default is YES.
ate. precedence For Multi-Processor Batch. Precedence when merging DTM sections
(RESOLUTION, FOM, RES_FOM, FOM_RES, ORDER_OF_INPUT.
Default is FOM.
ate.union For Multi-Processor Batch. Merge will Union the DTM’s. No other option
is available in this scenario. Default is UNION.
ate.cleanup For Multi-Processor Batch. Cleans up temporary files after ATE completes
(TRUE or FALSE). Default is TRUE.
Below is an example for a multiple processor scenario. Notice that the “ate.sections” is set to 2,
which enables the batch process to utilize 2 CPU’s:
setting_file 1.1
ate.project /data/projects/harbor.prj
ate.format DTM_GRID
ate.dtm_output dtm_example.dth
ate.images /data1/imagery/0603LF.sup
ate.images /data1/imagery/0603RF.sup
ate.polygon_verts -2.041985773 0.5760081041 485.000000
ate.num_verts 5
ate.seed_dtm seed.dth
ate.feather YES
ate.precedence ORDER_OF_INPUT
ate.adaptive 0
ate.strat flat.strat
ate.union UNION
ate.overlap 1
ate.sections 2
ate.x_post_spacing 2.0
ate.y_post_spacing 2.0
ate.post_spacing_unit UNIT_METERS
ate.back_match 1
ate.num_image_pairs 1

37.5 Next Step

The primary output of Automatic Terrain Extraction is a DTM containing posts extracted from
correlating the stereo image pair. Your next step is to display the DTM using Interactive Terrain
Editing to review the DTM. You can correct any erroneous posts with the Interactive Terrain
Editing tools. You can also run Quality Statistics to compare the DTM against control points. See
“Quality Statistics” on page 61-26.

Chapter 38
Next Generation Automatic Terrain

Extraction
Next Generation Automatic Terrain Extraction generates
dense and accurate digital terrain models.
38.1 Next Generation Automatic Terrian Extraction (NGATE)

NGATE is significantly different from ATE. ATE performs image correlation on each post.
NGATE performs image correlation and edge matching on each image pixel. You can control
ATE speed by using a large post spacing to reduce the number of posts. NGATE speed is not
dependent on post spacing or number of posts. You can control NGATE speed by stopping
NGATE at a different minification level using different Precision/Speed options. The most
significant advantage of using NGATE over ATE is for difficult areas such as large scale imagery
in urban areas. The DTM qualities from NGATE in those difficult areas are far better than those
from ATE. As a result, NGATE can significantly reduce DTM editing time. In terms of DTM
accuracy, NGATE almost always produces more accurate DTM than ATE. If speed is of
importance to your DTM production, you should set “Precision/Speed” to “Medium/Medium”.
With this setting, NGATE can generate DTM faster than ATE with slightly better accuracy. If
you need accurate and dense DTM, NGATE always performs better than ATE.
To obtain this window click Extraction > Terrain > Next Generation Automatic Extraction on
SOCET SET Page 38-1

Chapter 38 - Next Generation Automatic Terrain Extraction
The Next Generation Automatic Terrain Extraction window’s selections are as follows:
File > Load Project Select a project file (available only in stand-alone).
File > Create DTM... Create a new DTM or view and edit an existing DTM header file.
File > Open DTM... Select a DTM created by NGATE. You must not select DTM created by
ATE.
File > Exit Exits Next Generation Automatic Terrain Extraction.
SELECT TO
DTM File Display the name of the DTM selected.

Strategy File Display the name of strategy file selected.
Percent Complete Display the percent of the current pass processed.
Percent Measured Display the percent of successful matching.
Start Start NGATE
Page 38-2 SOCET SET

SELECT TO
Start at... Display the Start Batch Job window and initiate the batch job. See “Start
At Jobs” .
Abort Abort NGATE
38.2 Create a DTM for NGATE - NGATE Properties

To obtain this window, click File > Create DTM. The Images tab, the DTM Properties tab, and
the Seed DTM tab are the same as described in the Create DTM chapter. You must create DTMs
from NGATE. DTMs created from ATE cannot be used by NGATE. The NGATE Property tab is
as follows:
The Maximum Number Image Pairs Per Point has a default value of one. If there are more than
one image pairs, a value of two to three are recommended. The Number of Sections has a default
value of 1. If your computer has more than one CPU and you have more than one NGATE license,
then you can select a value greater than one. When you select a value greater than one, more than
one NGATE executes, and each NGATE generates a section of the whole DTM. After completing
all sections, NGATE merges all sections into one DTM. The Smoothing and TIN Masspoints are
the same as described in the Create DTM chapter.
There are three options under the DTM Filters: (1)DSM, (2)DEM, and (3)Both. The DSM option
is the default and NGATE will generate a digital surface model which includes trees, buildings
etc. The DEM option is the digital elevation model or bare earth model. The Both option will
SOCET SET Page 38-3

generate a DSM as well as a DEM. With the Both option, the DSM name is the name you select/
type while the DEM name has an addition “_dem” to it. When you select DEM or Both, NGATE
will attempt to eliminate structures/trees above the ground from the smallest size to the largest
size defined by two sets of parameters: the minimum height and maximum width. These two
parameters are well defined in the Interactive Terrain Edit chapter. NGATE tries to eliminate not
only the smallest and the largest structures/trees, but also anything in between. Some practical
recommendations are: (1) when your DTM covers mostly houses and single trees with only a few
large buildings, you should NOT use the large building as the largest size unless your DTM
covers really flat area. You can use the Interactive Terrain Edit to fix a few large buildings
instead. (2) NGATE cannot eliminate large patches of dense tree canopy areas. You should use
the Interactive Terrain Edit to fix dense tree canopy areas. (3) When your DTM covers really flat
areas such as urban areas, you may set the minimum height smaller and maximum width larger.
(4) When your DTM covers hilly or mountainous areas, you should set the minimum height larger
and maximum width smaller. Before you run a large DTM, you should run a small DTM to with
different parameters until it works well. And then, you use the appropriate parameters to run a
large DTM. NGATE should be able to eliminate single trees, houses, small buildings, or even
forest with sufficient clearings. The “Elevation Deviation” parameter is used to scale down the
elevation correction from DSM to DEM such that there are less “editing signature”. You should
use a value that is less than the relative LE of your DTM. The “Min Depth” parameter is used to
run a Bare Earth Histogram Well detection. “0” means not to use this option.
Three examples to help you choose the appropriate parameters. The first example is in urban areas
of moderate terrain with high resolution (GSD = 0.25 feet) and high quality frame digital camera
imagery. The parameters as well as the strategy are in the following figure. The unit is US survey
feet.
Page 38-4 SOCET SET

The second example is in steep suburban areas. The images are scanned frame films with medium
image quality. There are three bands (red, green, and blue). There are mostly houses and sparse
trees. There are a few large buildings. The GSD is 0.76 feet. The DTM has a relative LE of 1.9
feet. The parameters as well as the strategy are in the following figure. The unit is in US survey
feet.
The third example is in rural areas with a mixture of different terrain types. The images are from
digital frame camera and are of high quality. There are forests with sufficient clearings. The GSD
is 0.2 meters. There are 4 bands (red, green, blue, and IR). The parameters as well as the strategy
are as in the following figure. The unit is meters.
SOCET SET Page 38-5

The Precision/Speed selection has a default value of high precision and low speed (High/Slow).
If you want fast speed and do not care much of precision, you can select low precision and fast
speed (Low/Fast). When you select High/Slow, NGATE performs image and edge matching all
the way to minification level 1:1. When you select Medium/Medium, NGATE stops at
minification level 2:1. When you select Low/Fast, NGATE stops at minification level 4:1. The
speed of NGATE does not depend on the post spacing. NGATE always performs matching on
every image pixel regardless of post spacing.
To select a strategy, click the Strategies... button and the following window comes up.
Page 38-6 SOCET SET

There are several sample strategy files for NGATE provided by SOCET SET. They reside in the
internal_dbs/DTM_STRATEGY folder. Use the ngate_urban.strategy file for general cases. For
urban areas with tall buildings, use the ngate_urban_canyon.strategy file. For rural and easy
terrain, ngate.strategy is faster than ngate_urban.strategy. For desert or images without much
texture, use ngate_low_sp.strategy. The sample strategy files should be sufficient for most
applications. After you become an expert user of NGATE, you can create your own strategy. Get
more information from the existing strategy files on how to create your own strategy. Your own
strategy file must have the same format, with a file extension of “strategy”. Place your own
strategy in the same folder.
The Seed DTM tab is as follows:
SOCET SET Page 38-7

There are eight options to use a seed DTM. If the relative linear error of a seed DTM is known,
you can select the Automatic option. NGATE uses the precision values from the seed DTM to
determine how to use seed points from the seed DTM. You can also select any RSET or
minification level such that the seed point usage stops at the selected RSET or minification level.
For example, if you want to use seed points all the way to minification level 1, select RSET1.
The relative Linear Error (LE) computation in SOCET SET is defined as the error in elevation of
one point with respect to another point within one DTM at 90% probability. This definition is
used in both ATE and NGATE. The DTM header file (the dth file) has the RELATIVE LE
computed by ATE and NGATE. When importing a DTM from outside sources into SOCET SET
for use as a seed DTM, the relative LE is important. NGATE and ATE use the relative LE from
the seed DTM to compare with the relative LE computed from NGATE and ATE to determine
how to use the seed points. There are two issues: (1) the outside sources may have a different
definition of relative LE as SOCET SET has; and (2) the importing into SOCET SET may not
populate the RELATIVE LE in the header file correctly. For example, when you use the following
steps to import SRTM DTM as seed DTM into SOCET SET, the header file may not have the
RELATIVE LE. In this case, you can do the following:
1. Generate a very small DTM without using seed DTM using NGATE.
2. Look at the RELATIVE LE in the header file using a text editor.
3. Compute the ratio of RELATIVE LE of SRTM DTM and RELATIVE LE from the header
file. Assuming the relative LE of SRTM is 9 meters and the relative LE from the header file
is 1 meter. The ratio will be 9.
4. Select the RSET which is closest to the ratio. In the above example, the RSET should be
RSET8.
Page 38-8 SOCET SET

It is strongly recommended that you should use existing available DTM as seed DTM especially
in mountainous areas and steep slope areas. To down load free SRTM DTM, follow the following
steps:
Go to:
1. http://seamless.usgs.gov/
2. Click on the map.
3. Draw a square around the region of interest to zoom in.
4. Click on the Download tab on the right side. If the elevation category is not expanded, click
on the triangle to the left of ‘elevation’.
5. Check only the SRTM Finished 1 arc second checkbox.
6. Select the upper left box (arrow on rectangle icon) in the Downloads category on the left
side of the window.
7. Draw a rectangle around the area to be extracted for download. If the rectangle is green, it
can be downloaded.
8. A window appears saying: Seamless Data Distribution System SDDS Request Summary
Page
9. Click on the Modify Data Request link.
10. Next to the checked requested product “SRTM 1 arc sec - Shuttle Radar Topography
Mission [Finished]” click GeoTiff format from the dropdown list box
11. Click on the Save Changes and Return to Summary button.
12. Click on the Download button.
13. Another window appears: Current order status Adding your request to the queue... Please
wait for the data to be returned.
14. When you get the File Download dialog box, click Save and the location to save to.
15. Extract the GeoTiff file from the .ZIP file
16. Import the GeoTiff file using SOCET SET Preparation > Import > Terrain > GeoTiff
38.3 Batch Processing - NGATE

COMMAND LINE
% start_socet -single ngate -batch -s setting_file
ngate ngate
There are several ways to run NGATE in batch mode. You can run the NGATE in batch mode for
the following scenarios:
1. NGATE with an existing .dth file that was generated previously with the NGATE GUI.
2. NGATE without a .dth file.
3. NGATE without a .dth file and using the image footprints to determine DTM boundary.
SOCET SET Page 38-9

Please note that the keyword for scenario #1 is “ngate.dtm” while the keyword for scenario #2
and #3 is “ngate.dtm_output”.
Keywords necessary for scenario #1 (with an existing .dth file):
KEYWORD DESCRIPTION
ngate.project The full path of the project where your DTM will reside.
ngate.dtm The DTM to populate. No extension permitted. The DTM is selected from
the .dth files in your project directory after a DTM polygon has been
created via Extraction > Terrain > Next Generation Automatic Extraction >
Create DTM.
Keywords necessary for scenario #2 (without a .dth file):
KEYWORD DESCRIPTION
ngate.sections For Multi-Processor Batch. The number of processors available for
NGATE. Do not set this higher than the number of CPUs your computer
has available. Default is 1.
ngate.dtm_output The name of the DTM to create without path.
ngate.format The DTM format (DTM_GRID or DTM_TIN). Default is DTM_GRID.
ngate.strategy The strategy to use, with the .strategy extension. The default is
ngate.strategy.
ngate.obstruction_height The minimum height for buildings/trees.
ngate.obstruction_width The maximum width for buildings/trees.
ngate.eliminate_obstruction The eliminate obstructions option (TRUE or FALSE). Default is FALSE.
ngate.smoothing Smoothing option for the DTM (NONE_SMOOTHING,
ngate.precision Precision option for the DTM (HIGH_PRECISION, MEDIUM
ngate.masspoint TIN Masspoints thinning option (DENSE_MASSPOINT,
MEDIUM_MASSPOINT, or SPARSE_MASSPOINT). Default is
DENSE_MASSPOINT.
ngate.images Images that NGATE uses. Each support file needs its own line with the
ngate.post_spacing_unit Units that ATE uses (UNIT_SECONDS, UNIT_FEET,
ngate.seed_dtms Specifies seed DTM with full path and .dth extension. Each Seed DTM
needs its own line with the “seed_dtms” keyword.
ngate.num_verts The number of vertices that define the DTM boundary.

ngate.x_post_spacing The post spacing in the X direction. Default is 10.0 X post spacing units.
ngate.y_post_spacing The post spacing in the Y direction. Default is 10.0 Y post spacing units.

KEYWORD DESCRIPTION
ngate.seed_point_option Seed Point setting (Automatic, RSET1, RSET2, RSET4, RSET8, RSET16,
RSET32, or RSET64)
ngate.num_image_pairs Sets the maximum number of image pairs used in computing each
ngate.polygon_verts The polygon vertices of the boundary in XYZ. Each vertex must have its
own line with the “polygon_verts” keyword.
Keywords necessary for scenario #3 (without a .dth file and using image footprints to determine
DTM boundary):
KEYWORD DESCRIPTION
ngate.sections For Multi-Processor Batch. The number of processors available for
NGATE. Do not set this higher than the number of CPUs your computer
has available. Default is 1.
ngate.dtm_output The name of the DTM to create without path.
ngate.format The DTM format (DTM_GRID or DTM_TIN). Default is DTM_GRID.
ngate.strategy The strategy to use, with the .strategy extension. The default is
ngate.strategy.
ngate.obstruction_height The minimum height for buildings/trees.
ngate.obstruction_width The maximum width for buildings/trees.

KEYWORD DESCRIPTION
ngate.eliminate_obstruction The eliminate obstructions option (TRUE or FALSE). Default is FALSE.

ngate.smoothing Smoothing option for the DTM (NONE_SMOOTHING,
ngate.precision Precision option for the DTM (HIGH_PRECISION, MEDIUM
ngate.masspoint TIN Masspoints thinning option (DENSE_MASSPOINT,
MEDIUM_MASSPOINT, or SPARSE_MASSPOINT). Default is
DENSE_MASSPOINT.
ngate.images Images that NGATE uses. Each support file needs its own line with the
ngate.post_spacing_unit Units that ATE uses (UNIT_SECONDS, UNIT_FEET,
ngate.seed_dtms Specifies seed DTM with full path and .dth extension. Each Seed DTM
needs its own line with the “seed_dtms” keyword.
ngate.x_post_spacing The post spacing in the X direction. Default is 10.0 X post spacing units.
ngate.y_post_spacing The post spacing in the Y direction. Default is 10.0 Y post spacing units.
ngate.seed_point_option Seed Point setting (Automatic, RSET1, RSET2, RSET4, RSET8, RSET16,
RSET32, or RSET64)
ngate.num_image_pairs Sets the maximum number of image pairs used in computing each
The difference between scenario #2 and scenario #3 is that there are no “ngate.num_verts” and
ngate.polygon_verts” keywords in scenario #3.

Chapter 39
Interactive Terrain Edit

Interactive Terrain Edit covers various tools available to
review and edit a Digital Terrain Model.
39.1 Overview
You use Interactive Terrain Edit (ITE) to interactively review and edit Digital Terrain Model
(DTM). When editing a DTM, you should always edit one block at a time. The Edit DTM Block
under Options can help you to keep track of what has been edited. ITE performs better if you edit
one block at a time. ITE edits DTM in G r i d format and T I N format. You can edit data from
DTM using the following set of tools:
Post Editor - Grid DTM format
Post Editor - TIN DTM format
Area Editor
Geomorphic Editor
39.1.1 When to Use Interactive Terrain Edit

You use ITE in the following circumstances:
• To display a DTM graphically—You can draw the DTM with or without imagery
using a number of DTM graphics modes such as dots, mesh, or contours. See
“Displaying Terrain Graphically” on page 36-4 for more details.
• After NGATE/ATE—You use ITE to review the DTM created by NGATE/ATE. ITE
tools permit you to fill regions obscured by cloud cover, touch up shadow areas,
enhance ridge and drain features, edit out buildings and trees, and generally edit
areas that NGATE/ATE was unable to correctly correlate. In many cases, you want
a bare earth DTM, but DTM from NGATE/ATE may be a digital surface model
(DSM). ITE has many tools to bring down elevation points on top of trees and
buildings onto the ground.
• New DTM in large-scale urban imagery—When creating a DTM in imagery that
contains a lot of large buildings, you could build the DTM by hand using ITE
without running NGATE/ATE. You can create a new flat or empty DTM directly in
ITE.
SOCET SET Page 39-1

Chapter 39 - Interactive Terrain Edit
• Review imported DTM—You use ITE to review and edit DTM imported from other
systems.
• Image Map Overlays—You can burn-in DTM overlays (usually contour lines) into
an image map by running ITE at the same time you run Image Map. See “Image
Map” on page 52-7 for details.
39.1.2 Edit Tools

You can interactively edit terrain data from the DTM with the following set of tools (these edit
tools cannot be used on the Overlay File):
Area Editor - Changes all

posts within an area
delineated by a polygon. Post Editor - TIN DTM
Used for filling lakes, format - Post by post
smoothing, plane fill, review and edit. Used
interpolation, etc. Also for detailed editing
used to remove building operations. You move
artifacts. the floating mark to the
desired post with a
simple point-and-click.
Geomorphic Editor -
Force DTM to conform to
breaklines such as ridges
and drains, that you draw.
Also used to remove
hedgerow artifacts.
Terrain File Boundary
You cannot load a new DTM while one of the edit tools is active.
Exit the tool first before loading the new DTM.
Page 39-2 SOCET SET

Interactive Terrain Edit organizes these windows into the following hierarchy:
Interactive
Terrain Edit
Post Editor Geomorphic

Area Editor
Editor
39.1.3 Interactive Terrain Edit

To obtain this window, click Extraction > Terrain > Interactive Edit on the main workstation
window.
The Interactive Terrain Edit window’s selections are as follows:
File > Create DTM Invokes the Create DTM (see the ATE chapter)/DTM properties dialog.
File > Open DTM Prompts you to select the DTM to edit and/or display.
File > Save DTM Saves the current DTM to disk.
File > Save As Saves the current DTM to disk under a new name.
File > Write DTM to Prompts the user to enter a new name for the Feature DB.
Feature File Clicking OK will generate the new FDB.
File > Load Overlay DTM Prompts you to select a second DTM to display only.
File > Unload Overlay DTM Removes overlay from memory.
File > Exit Exits Interactive Terrain Edit.

Options > Auto Save Toggles Auto Save, asking you for the length of time between auto-saving.
SOCET SET Page 39-3

Options > Edit DTM Block Invokes the Edit DTM block dialog.
Options > Preferences Invokes the DTM preference dialog.
Options > Customize Invokes the toolbar dialog for customizing.
See “Setup DTM and Setup Overlay Preferences” on page 36-1 for descriptions of the Terrain Graphics
inputs.
SELECT TO
Create DTM Invoke the Create DTM (see the ATE chapter)/DTM properties dialog.
Open DTM Prompt you to select the DTM to edit and/or display.
Save DTM Save the current DTM to disk.
Draw Terrain Graphics Draw the set of currently enabled terrain graphics (DTM and overlay).
Draw TSR Generate a Terrain Shaded Relief image for the terrain file currently loaded
(Grid only), saves this image, and loads it to the left console window.
NOTE: The rotation of the Terrain Shaded relief image is
determined by the rotation of the extraction images. On systems
without an extraction monitor, the Terrain Shaded Relief image
may be drawn such that North is always up. If this happens, you
may reload the images and run ITE again. For Terrain Shaded
Relief to work properly, the console imagery must be displayed in
grayscale. You must turn off PAIRWISE RECTIFY from Tools >
Image Enhancement.
Enable DTM Graphics Instruct ITE to draw DTM graphics when drawing the terrain.
Enable Overlay Graphics Instruct ITE to draw overlay graphics when drawing the terrain.
Page 39-4 SOCET SET

SELECT TO
Auto Draw Terrain Graphics Set ITE to automatically draw the current DTM whenever the graphics in
RT are changed (e.g. refresh graphics).
Auto Draw TSR Toggle whether the Terrain Shaded Relief image is automatically
regenerated after area or geomorphic edits.
NOTE: For speed reasons, the images generated by auto relief may
occasionally not be of the same quality as those obtained by
clicking on the Draw Relief button. Also, the Terrain Shaded Relief
image must remain loaded for Auto Relief to work properly.
Setup DTM Graphics Control the way ITE draws the DTM. See “Terrain Graphics,” Chapter 36
for more details.
Setup Overlay Graphics Control the way ITE draws the Overlay file. See “Terrain Graphics,”
Chapter 36 for more details.
Post Editor Start up the Post Editor.
Area Editor Start up the Area Editor.
Geomorphic Editor Start up the Geomorphic Editor.
TIN Edit Edit GRID files with TIN tools. First delineate an area in the GRID to be
edited. After accepting the area the TIN Edit dialog will pop up. Use the
TIN Geomorphic and Area editors to edit the delineated area. When you
have finished editing the area click Save Edits on the TIN Edit dialog.
The edits you have made will be merge into the original GRID. To cancel
your TIN edits and restore the original GRID, click Cancel on the TIN
Edit dialog.
There are two preferences associated with TIN Edit.
• Start with empty TIN - Do not transfer elevation data from the
original GRID for editing.
• Tolerance - If “Start with empty TIN” is not set, this tolerance
will be used to thin the elevation data when it is converted from
GRID to TIN.
Undo Edit For DTM edits, undo the last Area Edit or Geomorphic Edit. Undo does
not apply to Clip Outside and Extract Patch.
For polygon drawing, undo the most recent sketch action.
SOCET SET Page 39-5

SELECT TO
Sketch Collection For Area Editor, delineate a polygon defining the area of interest.
For GRID Geomorphic editor, delineate a path for the selected
Geomorphic tool.
For TIN Geomorphic editor, draw a break line.
DLD Double Line Drain
Sketch Edit For TIN Geomorphic editor, edit a break line.
Parallel For TIN Geomorphic editor, draw parallel break lines. See “Sketch,”
Chapter 58 for more details
Sketch Monotonic Draw a monotonic line.
Measure For TIN Geomorphic editor, measure a break line.
39.1.4 Terrain Shaded Relief (TSR) Options

This window is used for setting the Terrain Shaded Relief parameters. To obtain this window,
select Options > Preferences on the ITE window and select TSR from the list.
A description of the selections in the Preferences list,

preceded by SK, can be found in the Sketch chapter.
Page 39-6 SOCET SET

The Terrain Shaded Relief (TSR) window’s selections are as follows:
SELECT TO
Output TSR File Name Name the support file you would like the TSR image saved to. The string
<terrain> is replaced by the name of your currently loaded terrain file. For
example, if your terrain file is named “sample”, then the output TSR will
be named sample_tsr.
Zoom (0.5 -> 20) Zoom to be performed on the TSR image.
Sun Azimuth (degrees) Enter the azimuth of the first sun in degrees clockwise from North (0-360).
Sun Elevation (degrees) Enter the elevation of the first sun in degrees (0-90).
Weight (0 -> 1) Enter the intensity of the first sun (0.0-1.0).
Weight (0 -> 1) Enter the intensity of the vertical sun (0.0-1.0).
Grayscale Select a grayscale TSR image.
Pseudocolor Select a pseudocolor TSR image. This format takes one third less disk
space than RGB, but has less color fidelity.
SOCET SET Page 39-7

SELECT TO
RGB Select a RGB TSR image. This format has the most image fidelity but uses
the most disk space.
Traditional Use for color TSRs. The color will not wrap. The color will progress from
min. elevation to max. elevation of the Region of Interest. (Original TSR
method.)
Fast Use for color TSRs. The colors will wrap according to the “Fast method
color range” setting. (Faster method for generating TSRs.)
Fast Method color range Select the size of the color range in project units. Only used for fast TSR
generation method.
Apply Apply preferences changes.
Page 39-8 SOCET SET

39.1.5 Edit DTM Block

This window is used to edit DTM within a designated block area. To attain this window, click
Options > Edit DTM Block... on the ITE window.
The Edit DTM Block window’s selections are as follows:
SELECT TO
Block Size This field relates to the number of post rows or columns in a square block.
The total number of post in a block would be Block Size * Block Size.
Change Size Displays a dialog that allows you to change the Block Size.
ID Displays the currently selected block ID. -1 indicates no block has been
selected for editing. When the button “Edit Block” is pressed, the block
number on which the extraction cursor is positioned is displayed in the ID
field. Note that if the extraction cursor lies outside of the DTM boundary,
the closest block number to the extraction cursor is displayed.
Change Block Displays a dialog that allows you to change the current block by entering a
block id.
Edit Block Selects a block of DTM for editing and display.
State Set the current block to Completed, In Progress, or Not Started.
Draw Draws the block boundaries. If a block state is completed a “X” is drawn
over the block.
Auto-Draw Set the auto-draw flag. If this is on, the block boundaries and completed
indicators will be automatically draw when a viewport is refreshed
Labels Set the draw labels flag. If this is on, the block ids will be drawn with the
block boundaries.
Edit Whole DTM Set the block size to the size of the DTM.
Close Closes the window
1. To edit DTM within a block, do the following:

2. Click Options > Edit DTM Block on the ITE window.
SOCET SET Page 39-9

3. With the Edit DTM Block window open, click Change Size to alter the block size (500 =
500 posts by 500 posts).
Changing the block size may have adverse affects on the

states of individual blocks. If an area of DTM is set to
completed before changing the block size, the software will
attempt to preserve the state of that area with the new block
size.
4. The DTM will be partitioned into blocks on the image, based upon the DTM block size.
5. Edit blocks:
a. There are two ways to select a block for editing. One method is to move the extraction
cursor into one of the partitioned blocks, and then, with the mouse cursor, click Edit
Block on the Edit DTM Block window. Another method is to click on the Change
Block button and enter a block ID in the dialog.
b. Click Edit Whole DTM on the Edit DTM Block window to change the block size to
the size of the DTM. This will put the entire DTM into one block.
Clicking Edit Whole DTM will change the block size.
6. Click Draw on the Edit DTM Block dialog to draw the block boundaries.
7. Edit or verify DTM.
8. When editing for a block is completed, change the state of that block to Completed. The
block states will be preserved between sessions.
9. Repeat steps 2 through 6 to edit or verify remaining blocks of the DTM.
10. Click Close when complete.
39.2 ITE Edit Tools
39.2.1 Post Editor - TIN DTM format

To add a new mass point: move the extraction cursor to a location on the earth’s surface and click
the RMB. To move an existing point (mass point or point on breakline), move the extraction
cursor near the point, click and drag the LMB.
Do not move a breakline point laterally more than one triangle.

If you want to adjust the Z elevation of the point, you must hold down the LMB while adjusting
the Z.
Use delete point and then add point to replace moving point.
Do not use continuous contour lines when editing TIN DTM.
To delete a point (mass point or point on breakline), move the extraction cursor near the point and
click the MMB.
To delete a point where two breaklines cross, you must first delete all the other points on the
breaklines, or you can use the “Delete Feature” action in Sketch when using Geomorphic editor.
To see the figure-of-merit and elevation of a mass point: move the extraction cursor near the mass
point and click (but do not drag) the LMB.
39.2.2 Post Editor - Grid DTM format

1. Click Post on the ITE window to obtain the Post Editor window.
2. Set POST SAVE to on or off. The toggle button appears to be pressed or unpressed to
indicate the current state. You can review the post heights without changing the DTM by
setting POST SAVE to OFF (unpressed).
3. Click GRAB POST to move the extraction cursor to the nearest post. GRAB POST will
appear to be pressed.
4. Use the arrow buttons or the arrow keys on the keyboard to move the cursor between posts.
5. You can adjust the elevation of the post by moving the trackball.
6. Un-click GRAB POST when you are finished, and click Close.

The Post Editor window’s selections are as follows:
SELECT TO
Elevation Elevation in project units (meters or feet) of the current post. Updates
continuously as you adjust the elevation with the trackball.
Change Change the elevation of a grabbed post by entering a new elevation in the
dialog.
Precision Precision in project units (meters or feet) of the current post. It is
computed based on the stereo image pairs on the screen.
FOM Figure of Merit of the current grabbed post. Describes how post was
measured. This is very useful for addressing problems with Automatic
Terrain Extraction since it has indicators for correlation failures and they
can be associated with the image detail that caused the failures.
Additionally, the FOM can be displayed using Terrain Graphics to aid the
quality control and edit process. You can find complete explanations of the
Figure of Merit values in the “Figures of Merit” appendix.
GRAB POST on Moves the cursor to the nearest post in the DTM grid. Cursor must be
within grid boundaries. Button toggles to RELEASE POST.
GRAB POST off Releases the cursor from the attached post. Button toggles to GRAB POST.
(or Up Arrow) Moves the extraction cursor up to the next post.
(or Down Arrow) Moves the extraction cursor down to the next post.
(or Left Arrow) Moves the extraction cursor left to the next post.
(or Right Arrow) Moves the extraction cursor right to the next post.
POST SAVE - On Saves all edits including elevation and FOM values. Sets FOM to
Manually Measured. Button toggles to POST SAVE OFF.
POST SAVE - Off Disables the above. Button toggles to POST SAVE ON.
Done Closes the Post Editor window.
39.2.3 Area Editor

The Area Editor provides you a variety of Algorithm selections.
The Area Editor window’s selections are as follows:
SELECT TO
Options Modify the options for the selected tool.

SELECT TO
Redo Apply the currently selected algorithm on the current polygon.

Done Close the Area Editor window.
AREA EDIT DTM

DESCRIPTION
TOOL FORMAT
Smoothing Grid Use weighted average of 5 X 5 window to remove elevation noise and
Convolution: 5x5 smooth DTM in the area.
Interpolate Grid Removes unwanted artifacts (such as buildings), or fills-in void areas or
Polygon: regions obscured by clouds. Fills area by interpolating from posts outside
1st order, the polygon perimeter. 1st order will interpolate elevation by distance.
2nd order 2nd order will interpolate elevation by distance squared. The area
delineation does not have to lie exactly on the ground. Comparing with
the Order Fill tool, this tool uses terrain elevation, while the Order Fill
tool uses the delineated polygon elevation.
Extract Patch Grid Creates a new DTM as big as the bounding rectangle of the area.
Elevation for the new DTM is copied from the original DTM.
Queue Suspect Grid Finds suspect posts and stores them in a Job Queue, where you can
Posts rapidly move to their locations for review and processing. Selecting “Run
Spike/Well detection only” performs an additional spike/well detection
that is useful for imported DTMs not generated in SOCET SET. You
select types of posts to look for based upon their Figure of Merit. See
“Figures Of Merit,” Appendix F for further details.
Plane Fill Grid Sets all posts within the area to lie on a plane (not necessarily horizontal)
determined by a planar best fit the perimeter delineation. Useful for
creating planar slopes and quickly editing problem areas. Compare with
the Plane Fill with Feather tool.
For plane_fill, SOCET SET computes the plane slope based on the
polygon vertices using least square algorithm. All posts within the
polygon are computed based on the first vertex elevation and the plane
slope. It is possible that for irregular polygon, the computed plane slope
may be slightly different from what you would expect.
Order Fill, Grid Removes artifacts (such as buildings) or to fill-in obscured areas (e.g. by
1st order, clouds). The posts within the area are filled by smoothly interpolating
2nd order from the perimeter delineation. You must ensure the perimeter
delineation is on the ground.
• 1st order will interpolate elevation by distance.
• 2nd order will interpolate elevation by distance squared.
Comparing with the Interpolate Polygon tool, this tool uses
the delineated polygon elevation, while the Interpolate
Polygon tool uses terrain elevation.
Plane Fill with Grid Same as Plane Fill except it feathers the outside edge of the area to the
Feather surrounding elevations. Compare with the Plane Fill tool.

AREA EDIT DTM

DESCRIPTION
TOOL FORMAT
Interpolate from Grid You typically use this tool after you edit a region with geomorphic tools
Good Points (ridges and drains) and/or the post editor (sets individual points). The
Good Points tool will interpolate the elevations of all posts within the
boundary that you have not edited, by using the posts that you have
edited (posts with FOMs of manually-measured, lake-filled, plane-filled,
geomorphic). For this tool, you should keep the cursor on the “ground”
when delineating the boundary since the boundary is used to help the
interpolation. This tool can be used to fix tree canopy areas, remove
buildings and/or generally help to fill-in obscurations.
Query Posts Grid Invokes the Post Query Editor. See “Posts Query Editor” on page 39-28.
Profile Editor Grid Invoke the Profile Editor. See “Profile Editor” on page 39-35.
Constant Grid/TIN There are several constant fill tools:
• constant polygon average - the average of all the post within
the delineated polygon
• constant polygon maximum - the highest elevation within the
delineated polygon
• constant polygon minimum - the lowest elevation within the
delineated polygon
• constant current cursor - the current elevation of the
extraction cursor
• constant user entered - the elevation entered by you when the
Constant_user_entered tool is selected
The elevation is set to a value based on one of several criteria: cursor

elevation, data entry, etc. Also sets the FOM of the posts to 23 LAKE
FILLED which are skipped by Automatic Terrain Extraction. This would
be useful for very small bodies of water such as ponds or lakes.
Smoothing Grid/TIN If for grid, use weighted average of 3 X 3 window; if for TIN, use the
Convolution weighted average of the adjacent points, to remove elevation noise and
smooth DTM in the area.

AREA EDIT DTM

DESCRIPTION
TOOL FORMAT
Bare Earth Grid/TIN Uses morphological operator to identify posts/masspoints on tree and
Morphology building tops. The identified Grid posts are lowered to the ground. The
identified TIN masspoints are removed. When digitizing the polygon, the
extraction cursor does not need to be on the ground. There are three
parameters: (1)Minimum Object Height; (2)Maximum Object Width; and
(3)Terrain Slope in Degree.
• The Minimum Object Height is in the project elevation unit
(meters/feet). Any posts/masspoints which are above the
ground by this parameter may be identified and then either
lowered or removed.
• The Maximum Object Width is in the project elevation unit
(meters/feet). Assuming the largest object within the polygon
is a building, this parameter is the largest dimension of the
building.
• The Terrain Slope in Degree is in degree unit (from 0 to 90
degrees). If the input value is negative, this indicates that the
software will automatically determine the terrain slope. It’s
always better to specify the actual slope if it is known. For
rough terrain, you may use any negative value.
If the terrain has a pretty uniform slope, the polygon can be large. For
rough terrain, you should use a smaller polygon. For example, in a hilly
forest area, you should use a smaller polygon to cover a small cluster of
trees at a time. When using a large polygon in a rough terrain, you may
switch to Post/Masspoint Editor to edit/add some posts/masspoints to
help the algorithm. You can switch between Post/Masspoint Editor and
Area Editor without re-digitizing the polygon unless you want to redefine
another area with a new polygon. In addtion to using the Post Editor, you
may use the Geomorphic Bulldozer algorithm with a "Interpolation
Distance" of one post spacing to edit many posts along a line. The
Bulldozer algorithm may be much more efficient than the Post Editor. For
TIN, you may insert a breakline, which may be more efficient than
adding lots of masspoints. For LIDAR TIN, you may need to run this
algorithm more than once by pressing the Redo button. This is because
there are redundant masspoints from LIDAR.

AREA EDIT DTM

DESCRIPTION
TOOL FORMAT
Bare Earth Grid/TIN The difference between "Bare Earth Morphology" and this algorithm is
Mophology Lay that digitized polygon edges and vertices are assumed to be precisely on
On Ground the ground. Those polygon edges and vertices are used to model the
terrain. This algorithm also feathers along the polygon edges such that
there will be no editing signature.
Example 1:
This DTM is generated by NGATE. There are three blunders labelled 1, 2

and 3 in RED. Blunders 1 and 3 are caused by moving trees due to wind.
Blunder 2 is due to moving vehicle. All three blunders are WELLS or
under ground. You should remove them first since other bare earth
algorithms may be based on the assumption that there are no WELLS.
Blunder 2 is on a street. There are several moving vehicles on the street.

We use the Geomorphic Editor to insert a breakline with a Buffer Width
of 4 meters and Densify Length of 8 meters. For blunder 1 and 3, we use
the Masspoint Editor to remove two WELL point.

AREA EDIT DTM

DESCRIPTION
TOOL FORMAT
We use Minimum Object Height of 2.5 meters, Maximum Object Width

of 30 meters, and Terrain Slope in Degree of 3. The result is shown
below.
Most of the building points have been removed. There are still some on
the upper side. We then use a Minimum Object Height of 1.5 meters. You
do not need to re-digitize the polygon. You press the Options button and
change the Minimum Object Height, then press the Redo button. We get
the results as shown below.

AREA EDIT DTM

DESCRIPTION
TOOL FORMAT
There are still a few points on buildings. Then we use Minimum Object
Height of 0.75 meters, we get a clean DTM without building top points.
When you set the parameters, you should set them more conservative at
the beginning. Like in this example, we use 2.5, 1.5, and 0.75 meters as
the Minimum Object Height in three operations. If the algorithm removes
too many points (points which are on the ground), you can always press
the Undo button and try a more conservative set of parameters.

AREA EDIT DTM

DESCRIPTION
TOOL FORMAT
Bare Earth Grid/TIN Uses X and Y profiles to identify tree and building posts/masspoints.
Profile This algorithm uses two parameters: Maximum Profile Width and
Minimum Profile Height. These two parameters are the same as for the
Bare Earth Morphology algorithm.
Bare Earth Grid/TIN The difference between "Bare Earth Profile" and this algorithm is that
Profile Lay On digitized polygon edges and vertices are assumed to be precisely on the
Ground ground. Those polygon edges and vertices are used to model the terrain.
This algorithm also feathers along the polygon edges such that there will
be no editing signature.
Bare Earth Grid/TIN Uses elevation distribution to identify blunders or spikes. For LIDAR
Histogram DTM, you should run this algorithm first because other algorithms such
Spikes as the Bare Earth Morphology may be based on the assumption that there
are no blunders in the DTM.
Bare Earth Grid/TIN Uses elevation distribution to identify blunders or wells. For LIDAR
Histogram Wells DTM, you should run this algorithm first because other algorithms such
as the Bare Earth Morphology may be based on the assumption that there
are no blunders in the DTM.
Bare Earth Grid/TIN This algorithm performs a downward smoothing convolution. The
Vegetation regular smoothing convolution uses all posts within a window such as
3X3 or 5X5 to smooth. This algorithm uses only posts that have lower
elevation within a window to smooth. As a result, it is a downward
smoothing convolution suitable for vegetation. The window size and
number of iteration is computed based on the "Vegetation Height"
parameter. To smooth downward more, you use a "Vegetation Height"
greater than a post spacing. To smooth downward less, you use a
"Vegetation Height" smaller than a post spacing.
Use this algorithm for two cases: (1)DTM is from LIDAR and there is
some vegetated area. You enter the vegetation height as the parameter in
the project elevation unit (meters/feet). (2)DTM is from NGATE/ATE
and the vegetation is not very dense. In other words, there are still a fair
amount of posts/masspoints on the ground. The algorithm can lower or
remove posts/masspoints on vegetation tops.
Bare Earth Grid/TIN This is the combination of Bare Earth Morphology and Bare Earth
Morphology Histogram Spikes.
Histogram
Bare Earth Grid/TIN This is the combination of Bare Earth Histogram Spikes, Bare Earth
Blunder Histogram Wells, and Bare Earth Morphology. Use this algorithm for
Morphology LIDAR DTM when there are blunders.
Histogram

AREA EDIT DTM

DESCRIPTION
TOOL FORMAT
Bare Earth Dense Grid/TIN Use this algorithm for dense tree canopy area and for large buildings in
Tree Canopy Lay an urban area. As long as the slope within the polygon is either flat or
On Ground uniform, this algorithm is very effective. This algorithm requires one
parameter: elevation deviation. For example, if your DTM product has a
relative LE requirement of 2 meters, you may use 1 meter here. To move
the canopy downward more, you should use a smaller elevation
deviation. However, too small an elevation deviation may leave some
editing signature.
When digitizing the polygon, you must place the extraction cursor on the
ground precisely. You must also digitize enough vertices such that each
segment/edge of the polygon follows the ground precisely. If the polygon
is not close to be planar, you may use the Post/Masspoint Editor to edit/
add some posts/masspoints within the polygon. And then apply this
algorithm. You can switch between Post/Masspoint Editor or
Geomorphic Editor and Area Editor without re-digitizing the polygon
unless you want to use a different polygon. In a ridge or valley area, you
must digitize two polygons dividing the area into two at the ridge or
valley line or use the Geomorphic Editor to digitize a line to split the area
into two areas first.

AREA EDIT DTM

DESCRIPTION
TOOL FORMAT
Bare Earth Dense Grid/TIN The difference between this algorithm and the Bare Earth Dense Tree
Tree Canopy Canopy Lay On Ground is that the polygon vertices and segments do not
Close to Ground need to be precisely on the ground as long as they are close to the ground.
When the elevation difference between the DTM and the digitized
vertices and segments is smaller than 2 times of the elevation deviation,
the software uses the elevation from the DTM. In cases that some vertices
and segments need to be inside the dense tree area such as following a
valley or ridge, the vertices and segments should be on the ground. In
practice, it is very hard to place the extraction cursor on the ground since
you cannot see the ground. You should look for openings and use your
educated guesses to place the cursor to the ground as precisely as
possible.
When the polygon covers a large rough area, you should use the Post
Editor or Masspoint Editor to edit some posts to the ground. These edited
posts will be used as seed points. If you have already digitized the
polygon, you do not need to re-digitize the polygon after using the Post
Editor or Geomorphic Editor. The software remembers the existing
polygon. You need then press the Redo button until you are satisfied with
the DTM. If there are editing signatures in the open area along the
polygon segments, this indicates that the polygon segments are not close
enough to the ground. You can either re-digitize the polygon or increase
the elevation deviation. In the example below, this is a rough area with a
valley. You should divide the area along the valley. Polygon segments
that are inside the dense tree area should be on the ground as shown in the
right. Polygon segments outside the dense tree area need to be close to
the ground as shown in the left. The left image is before applying the
algorithm. The right image is after applying the algorithm.

AREA EDIT DTM

DESCRIPTION
TOOL FORMAT
Bare Earth Dense Grid/TIN This algorithm only applies to cases that all polygon vertices and
Tree Canopy segments are outside of dense tree area. In other words, the polygon
segments and vertices must be in area where the DTM is already on the
ground because the software uses elevation from the DTM for the
polygon segments and vertices.
Example 1:
In this area, there is a valley. On both sides of the valley, there are dense
trees. First, we use the Geomorphic Editor Algorithm Bulldozer with an
Interpolation Distance of one post spacing to edit down posts in the
valley and set their FOM values to be Geomorphic. These Geomorphic
posts will then be used as seed posts or control posts for the Bare Earth
Dense Tree Canopy Algorithm.

AREA EDIT DTM

DESCRIPTION
TOOL FORMAT
As shown in the above image, the center white line is the Geomorphic
Bulldozer line which follows the valley. The white segments on the left
and right sides are the polygon. After applying the Bare Earth Dense Tree
Canopy, the contours in red look good. If you are still not satisfied, you
can switch to the Post Editor to edit down a few more seed posts. Then,
you switch back to the Area Editor and press the Redo button without re-
digitizing the polygon. Notice that the polygon segments are in open area
where the DTM is already on the ground. In the case that there is no open
area in the DTM, you can use other tools to edit a path as illustrated in the
next example.
Example 2:
In this case, there is no open area in the lower left corner. We use the
Geomorphic Bulldozer with an Interpolation Distance of three post
spacing to make one as shown below:

AREA EDIT DTM

DESCRIPTION
TOOL FORMAT
In the final step, we use the Bare Earth Dense Tree Canopy by digitizing
a polygon as shown below:
The polygon segments do not need to be on the ground as long as they are
in areas where the DTM is on the ground.
Example 3:
For large areas, as shown below, you should use the Geomorphic Editor
Bulldozer to provide some seed posts. Inside the dense tree area, there are
three visible open trails. We use the Bulldozer to add a number of seed
posts before we apply the Bare Earth Dense Tree Canopy.

AREA EDIT DTM

DESCRIPTION
TOOL FORMAT
After applying the edit, as shown below, posts within the white polygon
look good. There are no editing signatures along the polygon segments
and within the polygon.

AREA EDIT DTM

DESCRIPTION
TOOL FORMAT
Bare Earth Bias Grid/TIN This algorithm lowers all posts/masspoints within the digitized polygon
Lay On Ground by a bias. The bias is in the project elevation unit (meters/feet) and must
be positive. When digitizing the polygon, you must place the extraction
cursor on the ground precisely. You must also digitize enough vertices
such that each segment/edge of the polygon follows the ground precisely.
This algorithm performs feathering on the edges of the polygon such that
there should be no editing signature along the edges of the polygon. The
elevations of posts/masspoints close to the polygon edges are not lower
than the elevation from the digitized polygon vertices.
Set FOM Inside Grid/TIN Sets the FOM values of posts within the area. Can be used prior to
running Automatic Terrain Extraction so that Automatic Terrain
Extraction will not alter certain posts (those with FOMs set to Manually
Measured, Outside Boundary, Geomorphic DWI or Lake Filled). Also
used before running DTM Feature DTM/Feature Merge since posts with
FOM of “Manually Measured” will be kept over other types of FOMs.
See “Figures Of Merit,” Appendix F.
Bias Grid/TIN Moves all posts inside the area up or down by a given value. Used to
remove forest canopies. A positive value raises the posts, and a negative
value lowers the posts.
Area Thinning Grid/TIN Marks redundant DTM posts by setting the FOM value to THINNED for
Grid or eliminate points for TIN triangles. When you select this tool, it
asks you to enter the thinning criteria which is used to check the Root
Mean Square Error of the planarity within the DTM. If a region is planar
within the threshold you enter, then the center post is flagged as
THINNED for Grid or eliminated for TIN triangles. Normally, the
thinning criteria should be the expected DTM accuracy. For example, if
your expected DTM accuracy is 2 meters, you may enter 2 meters as the
thinning criteria. This tool is useful for reducing the amount of data. This
tool is also useful for smoothing areas, but it does not smooth rough
areas. Thus, it will help clean up contours in flat areas and uniform slope
areas.
Clip Outside Grid/TIN Reduces the size of a DTM. Sets FOM of points outside of the area to
OUTSIDE BOUNDARY. TIN points outside the area are deleted.

AREA EDIT DTM

DESCRIPTION
TOOL FORMAT
Snap to ground Grid/TIN Compute elevations using the snap to ground algorithm. You may use this
tool only for a small area with small elevation variation. As the cursor
visits each post, the algorithm will attempt to auto-correlate the images at
that post--snap the post to the ground. The result of this process with
display posts is either green or red.
• Red posts failed to correlate
• Green posts correlated successfully
DLD Grid/TIN Create a double-line drain. See “Sketch,” Chapter 58 for more details.
• For TIN, a breakline representing the boundaries of the DLD
will be inserted.
• For GRID, elevation values within the DLD boundaries will
be adjusted to the DLD elevations.
The preferences for DLD editing are Accuracy and Step Height.
The accuracy preference is used by the software when determining the

elevation of a terrain post with the DLD. If the accuracy preference is set
to 0.0, the software will automatically choose an accuracy. Otherwise the
value entered for the accuracy preference will be used. We recommend
that you do not modify the accuracy value. If you do enter in your own
accuracy value, you will want to keep the value greater than two times
the average GSD of the images. A small accuracy value may result in
more accurate elevations. But the computation time increases
dramatically with small accuracies.
The step height preference is used by the software to determine the

number of steps in the DLD. If the step height preference is 0.0, the DLD
will be generated without steps. To create a DLD with steps, enter a step
height in project Z units.

AREA EDIT DTM

DESCRIPTION
TOOL FORMAT
Make Visible Grid/TIN Makes area of a DTM visible or invisible. To run this tool: draw a small
Make Invisible polygon (any shape)—the centroid of the polygon will be used as the
starting point to spread the (in)visibility. The (in)visibility will spread
until it hits a breakline boundary. After you run the tool you must
recenter the main image display to see the effects of the tool. If you
accidentally make the entire DTM invisible, you can fix it by running the
Make Visible tool.
Delete Points TIN Deletes all mass points inside the polygon.
Inside
Delete Pts and TIN Deletes all mass points inside the polygon and creates a breakline.
Add Brkln “Lay on Ground” forces the breakline to lie on the DTM surface (ignores
[lay on ground] the Z elevations of delineation).
Closed Breakline TIN Creates a polygon breakline.
[lay on ground] “Lay on Ground” forces the breakline to lie on the DTM surface (ignores
the Z elevations of delineation).
Create Building TIN Models a building (or any other feature with vertical sides) in a TIN
DTM. The polygon you draw must be the roof of the building followed
by a single point anywhere at the building base elevation. For example, if
the building is rectangular, sample 4 points at the roof corners, then
sample a fifth point at the building base (only the Z value will be used, so
the XY position of the final point is unimportant), then accept the
polygon. This will create two breaklines in the DTM: one on the roof,
and one at the base of the building (slightly larger than the roof
breakline).
Clip Inside TIN Deletes breaklines and mass points inside polygon. Breaklines that pass
beyond the polygon are clipped outside the polygon’s edges.
Remove TIN Use this algorithm for imported DTM TIN such as LIDAR. Imported
Redundant DTM TIN may have redundant masspoints. These redundant masspoints
Points are stored in the TIN database. They may not display in ITE because
SOCET SET generates TIN on-the-fly. Redundant masspoints overwrite
each other during the TINing process.
Flatten Buildings TIN Use this algorithm to merge in feature classes that represent buildings.
(Merge Only) The algorithm will remove the buildings from the DTM and place a
single post to represent the bottom of the building. The feature class for
the buildings must be in the POLYHEDRON type.
1. Click Area on the ITE window to obtain the Area Editor window.
2. Toggle the mouse to control the extraction cursor. Sample the boundary of the area with the
LMB. Click the RMB to close the polygon and performs the selected algorithm.
3. [Optional] Select another area tool and click Redo to perform the second algorithm in the
same area.
39.2.3.1 Posts Query Editor

The Posts Query Editor lets you run queries on a group of posts selected from a GRID DTM, and
execute group edits on the result of those queries, for example changing the elevation and/or FOM
of each post in the result set, or writing out the posts to a job queue, text file, or overlay DTM.
Alternatively, you can visit each post separately; the software drives the extraction cursor to any
post you select and invokes the post editor. Those posts which are part of the query result set are
highlighted (in a color of your preference) on the image display window.
To view the Posts Query widow:

1. Click Area on the ITE window.

2. Select Query Posts from the Algorithm pull-down menu on the Area Editor window.
3. Keeping the Area Editor window open, draw a polygon with the extraction cursor, using
the RMB to close the polygon.
The Posts Query window will open.
The Posts Query Editor window’s selections are as follows:
File > Exit Exits the Posts Query Editor.

Options > Load Query Loads a previously saved query. Only sensitized when the “Query” text
field is empty.
Options > Save Query Saves the current query to a text file. Only sensitized then the “Query” text
field contains a complete query.
Options > Highlight Color Choose the highlight color for selected posts.
SELECT TO
Algorithm Initially, this pull-down menu is the only sensitized control. You select an
algorithm to select posts.
Elevation Select posts based on elevations.

FOM Select posts based on FOMs.
Elevation Change Specify elevation differences between the center post and its 8 adjacent
BLANK SPACE posts. These elevation differences are then used to select posts.
Average Delta Use the average elevation differences in a 3X3, 5X5, or 7X7 matrix with
Elevation respect to the center post as the criterion to select posts.

SELECT TO
Matrix Window This menu pull-down is sensitized only when you select the Average Delta
BLANK SPACE Elevation algorithm.
3x3 Execute the Average Delta Elevation algorithm on a 3x3 neighbor matrix.
BLANK SPACE (eight neighbors)
5x5 Execute the Average Delta Elevation algorithm on a 5x5 neighbor matrix.
(24 neighbors)
BLANK SPACE
BLANK SPACE
BLANK SPACE
Execute the Average Delta Elevation algorithm on a 7x7 neighbor matrix.
7x7 (49 neighbors)
Relational Operators Compare the results of an algorithm (except for Elevation Change) to a
user specified threshold value. See “Examples” on page 39-33 for an
example of their usage (EQUAL, NOT EQUAL > >= <= <).
Value Enter a value for the right hand side of a relational operator. See
“Examples” on page 39-33 for an example of their usage.
FOM Values Sensitize after you select “FOM” from the “Algorithm” menu pull-down
and then selects a relational operator; displays a list of FOMs from which
you can select one.
Logical Operators Detect posts with several properties (AND, OR, open/close parenthesis)
These are for stringing simple queries (relational comparisons and
Elevation Change algorithms).
UNDO Erases pieces or entire query.
Execute Query Execute constructed query.
When a post query is executed, the resulting posts are shown in a separate window called the
Posts Display” window. From this window, you can run various operations (described below) on
the resulting posts. Additionally, the resulting posts are highlighted.
39.2.3.2 Constructing and Executing a Query

Creating a query involves operating the group of pull-down menus, buttons, and the Value text
field in the correct order; groups of controls will be sensitized and desensitized to help guide this
correct order. The specific controls and their functions flows from left to right. In that order, the
control groups are:
• Algorithm—either Elevation, FOM, Elevation Change (See Elevation Change Algorithm
below), or Average Delta Elevation Algorithm (below). If you choose Avg Delta
Elevation, then the “Matrix Window” pull-down menu is sensitized. This is also
explained below.
• Relational operators—sensitized after you choose an algorithm (except for Elevation
Change). You compare the results of the selected algorithm to a specific value.
• Value field and FOM selection—sensitized after you choose a relational operator. You
enter a threshold value to be compared against the results of the selected algorithm. The
“FOM Values” button is sensitized if you chose “FOM” from the “Algorithm” pull-
down menu.
• Logical operators—you build complex queries by stringing together simple queries
with logical operators like AND and OR.

Once a complete query has been entered, the “Execute Query” button is sensitized.
39.2.3.3 Algorithms
As described above, the “Algorithm” pull-down menu contains four choices: Elevation, FOM,
Elevation Change, and Avg Delta Elevation. Elevation and FOM allow you to query those posts
whose elevation or FOM fall within a specified range (you can also query on specific elevations
and FOMs).
39.2.3.3.1 Elevation Change Algorithm

When you select this algorithm, the following window is displayed as a modal dialog:
The eight text fields surrounding the central field represent the differences in elevation between
the eight neighboring posts and the given post itself. The center text field represents the given
post, which is why it’s desensitized and fixed with an elevation difference of zero. The algorithm
compares this matrix of elevation differences to the actual elevation differences between a given
post and its eight neighbors. If all eight of the actual differences exceed the specified differences,
then post is flagged by the query and is displayed in the Posts Display window. The example
above would flag all the posts which are ten (or more) units higher than all eight neighbors; in
other words, it would detect spikes.
The sign (+ or -) of the values you enter are very important for this algorithm. A positive (+) sign
instructs the software to consider neighbors which are higher than the central post. A negative
(-) sign instructs the software to consider which are lower than the central post. The absence of
a sign is not the same as a positive sign. The absence of a sign instructs the software to consider
both higher and lower posts. In other words, the values would detect both spikes and wells:
In addition to detecting spikes and wells, this algorithm can be used for detecting edges; in fact,
this technique is similar to edge detection techniques used in image processing. See “Detecting
Edges using Elevation Change” on page 39-34 for an example.
This algorithm does not require a separate relational operator or comparison value, so those
controls do not become sensitized upon selecting Elevation Change, but the logical operators do,
so that you can select another algorithm after this one.
Altering the upper-left text field will cause all the other fields to
assume the value of the upper-left. If you don’t want all the
fields to have the same value, then enter the upper-left value
first.
39.2.3.3.2 Average Delta Elevation Algorithm

This algorithm is used solely for detecting spike and/or well posts. This algorithm compares the
elevation of a given post to the average elevation of its neighbors. When you select this algorithm,

the Matrix Window pull-down menu becomes sensitized. You specify the size of the matrix of
neighbors to be averaged. The choices are 3x3 (the eight immediately surrounding neighbors),
5x5 (24 neighbors), or 7x7 (48 neighbors). The center post is not included in the average.
After you select a matrix window, the relational operators are sensitized. After you select an
operator, the Value text field is sensitized, allowing you to select a comparison value. Posts
whose average delta deviation does not relate to the comparison value according to the selected
relational operator are flagged by the query and displayed in the Posts Display window.
The signs (+, -, or neither) work exactly as described above in the Elevation Change section.
Thus, the absence of a sign would detect both spikes and wells.
39.2.3.4 Posts Display

The figure below illustrates the window that pops up when you execute a query (by clicking the
“Execute Query” button after entering a complete query). When you select one of the rows of the
table, the extraction curser moves to the post associated with that row, and the individual post
editor is invoked. You can click on any of the column headers to sort the posts in descending order
of that column.
The Posts Display window’s selections are as follows:
SELECT TO
FILTER BLANK SPACE

All Show every resulting post from the query.
Top N Items Show the top N of the resulting posts from the query (see the note below).
BLANK SPACE Show the top N% of the resulting posts resulting from the query (see the
Top N% Items note below).

SELECT TO
EDIT BLANK SPACE

Change Elevation Assign a specified elevation to every post currently shown in the table
BLANK SPACE (either all of them, or the top N or N% according to what you specify).
Change FOM Assign a specified FOM to every post currently shown in the table (either
BLANK SPACE all of them, or the top N or N% as according to what you specify).
Write Out to GRID Write the posts currently shown in the table to a GRID DTM.
DTM BLANK SPACE
Write Out to ASCII Write information about the posts currently shown in the table to an ASCII
File file.
Write Out to Job Use the currently shown posts to create a Job Queue file in case you want
Queue to use SOCET SET’s Job Queue tool to visit and process each post.
Interpolate Posts Alter the elevation of each currently shown post by interpolating via those
neighboring posts with valid FOMs.
The Top N and Top N% filters sort the posts based upon the
results of an average delta operation (using either a 3x3, 5x5,
or 7x7 neighbor matrix). If an average delta operation was not
part of the query, then the filter functionality is disabled and all
the posts are displayed.
39.2.3.5 Examples
The following are examples for Interactive Terrain Edit. They are Querying for a range of
elevations, Detecting Convolutions (Spikes and Wells) using Average Delta Elevation, Detecting
Edges using Elevation Change, and Compound Queries Using Logical Operators
39.2.3.5.1 Querying for a range of elevations

This relatively simple query exemplifies the use of both the relational and logical operators.
Execute the following operations:
1. Select Elevation from the Algorithm pull-down menu.
2. Click >=.
3. Enter a value (e.g. 500) in the Value text field, then press [Enter].
4. Click AND.
5. Select Elevation from the Algorithm pull-down menu.
6. Click <=.
7. Enter a larger value (e.g. 502) in the Value text field, then press [Enter].
8. Click Execute Query.

Assuming any of the posts in the DTM fall within this range of elevations, the Posts Display
window will pop up with information about those posts. You can click on the any of rows to drive
the extraction cursor to their associated posts.
39.2.3.5.2 Detecting Convolutions (Spikes and Wells) using Average Delta

Elevation
Here, we will detect posts which deviate from their immediate neighbors (3x3) by plus or minus
three elevation units:
1. Clear any previous work from the GUI by either exiting and restarting the Post-Query
Editor or by repeatedly clicking the UNDO button until the Query text field is clear
2. Select Avg Delta Elevation from the Algorithm pull-down menu.
3. Select (3x3) from the Matrix Window pull-down menu
4. Click >=
5. Enter 3 in the Value text field.
6. Click “Execute Query”
39.2.3.5.3 Detecting Edges using Elevation Change

1. Clear your work from above by either exiting and restarting the Post-Query Editor or by
repeatedly clicking the “UNDO” button until the “Query” text field is clear
2. Select “Elevation Change” from the “Algorithm” pull-down menu.
3. The Convolution Matrix Editor will pop up; enter these values:
0 0 0
0 0 0
-5 -5 -5
4. Click OK on the Convolution Matrix Editor window.

5. Click Execute Query
This set of values should detect southward-facing walls or cliffs (or perhaps the sides of
buildings) with a height of five or more elevation units.
39.2.3.5.4 Compound Queries Using Logical Operators

By using the logical operators, all of these operations could be done together. For example, we
can detect spikes, wells, and edges within a particular range of elevations.

39.2.4 Profile Editor

The profile editor is used to edit and/or review individual posts along a profile in a GRID. To
invoke the Profile Editor, start the Area Editor, select the “Profile_editor” tool, and delineate an
area. After accepting the delineated area, the Profile Editor window displays. When you press the
Start button, the extraction cursor will automatically roam along the elevation profiles contained
within the delineated area.
• When ENABLED Automatic Profile Tracking is the cursor follows the elevation --
follows the post elevations.
• When DISABLED (unchecked) the cursor moves at a constant elevation from post
to post The constant elevation is the elevation at which the cursor was set at when
the area algorithm started. Note that if you do no intervene the process will
reposition the posts at that constant elevation.
The Profile Editor window’s selections are as follows:
SELECT TO
Roam Rate Change the extraction cursor roam speed.

Roam Style Change the extraction cursor roam style.
• Smooth roam will cause the cursor to roam smoothly between
post.
• Post to Post will cause the cursor to jump post to post.
Pause Upon Editing Set the extraction cursor to pause when a post elevation is changed while
roaming.
Automatic Profile Tracking Set the extraction cursor to follow the current elevation of the profile while
roaming.
If this option is disabled, the extraction cursor will not snap to the
elevation of the terrain. The post’s elevations will move to match to the
extraction cursor’s elevation. So you can easily edit a terrain profile by
adjusting the cursor elevation while the cursor is roaming.
Start/Resume/Pause Start, Pause, or Resume the extraction cursor roam.
Reset Move the extraction back to the start location.
Close Close the Profile Editor

39.2.5 Geomorphic Editor

39.2.5.1 TIN DTM format
The Geomorphic Editor is used to add and change breaklines in a TIN DTM. The Geomorphic
editor uses the Sketch tool (See “Sketch Toolbar” on page 58-1).
When you add a breakline, all mass points within the buffer width of the breakline will be deleted.
If you do not want to delete any mass points when inserting a breakline, you must set the buffer
width to 0.
The densify length is used to add additional vertices into the breakline when inserting it into the
TIN DTM. This can be used for two cases:
• avoid narrow triangles caused by a long sparse breakline.
• reduce the length of the crossing segment when the current breakline crosses the
existing breakline.
If you do not want to densify breakline, you must set it to 0.
The Feature Code is used only for TIN. The default feature code is 1.
The Geomorphic editor uses the Sketch tool to edit breaklines. The Sketch tool buttons are not
displayed, but the functions can be called through the accelerator keys, which are defined in
Preference > Keyboard/Tracking Accelerator Mapping menu with the Applications set to
Interactive Terrain Edit. These hot-keys can be assigned to user preference. The default
assignments are used in the explanations below. See “Sketch,” Chapter 58.
To delete a breakline, the Geomorphic Editor must be open and View 1 must be in focus. Use the
Sketch tool Delete hot-key (default: <Shift>F8). Click the LMB to select breakline to delete.Click
the LMB again to confirm or the RMB to abort the deletion.
To change the delineation of a breakline, you can use the Post Editor tool to delete or move
individual points on the breakline or you can use the sketch move or delete vertex functions. To
add points to a breakline use the sketch insert vertex function. See “Post Editor - TIN DTM
format” on page 39-10 for details.
It is not necessary that the entire breakline be inside the DTM boundary, because ITE will
automatically clip the breakline to the edges of the DTM. However, it is required that at least one
vertex of the breakline be inside a visible region of the DTM.

39.2.5.2 Grid DTM format

The Geomorphic Editor resets elevation points within the DTM, based on their distance from the
delineation.
1. Click Geomorphic on the Interactive Terrain Edit window. This will open the Geomorphic
Editor window.
2. Select the geomorphic editing tool to run from Edit Options.
3. Enter a value for the Interpolation Distance. This value specifies the distance to each side
of the delineation over which the geomorphic operation is applied. (If you want the tool to
act on a strip 200 meters wide, then enter 100.) Points within your entered distance will be
changed and their Figure of Merit is set to Geomorphic. The method of elevation change is
dependent on the Edit Options (Uniform slope, U Shaped slope, V shaped slope, bulldozer,
bulldozer with feathering, and Hedge Trimmer). You can draw a line with the extraction
cursor. Static or dynamic extraction capability is provided by Sketch. Use the LMB to
collect points or start dynamic extraction. Use the RMB to accept points and execute tool
(See “Sketch,” Chapter 58 for more information).
4. Click Redo to change the Interpolation Distance or click Close if you are finished.
The following diagram shows how contours in a grid format DTM might be affected using
geomorphic tools.
Prior to Running Geomorphic Tool After Geomorphic Tool
Ridgeline
DTM rendered as contours

The following diagram gives an elevation view of these tool options.
Existing terrain profile with an incorrect drain

elevation.
Enter the interpolation distance.
Place the extraction cursor where the actual drain
bottom is and draw a line along the drain bottom.
Resulting terrain profile from Uniform option.
Resulting terrain profile from U Shape option.
Resulting terrain profile from V Shape option.
Resulting terrain profile from Bulldozer tool.
Resulting terrain profile from Bulldozer with

feathering option (Similar to existing Bulldozer)
Before
The Hedge Trimmer tool can be used to fill in
valleys by placing the extraction cursor at the
After desired elevation and drawing a line along the
valley.
Before The Hedge trimmer tool can also be used to cut

down rises by placing the extraction cursor at
After the desired elevation and drawing a line along
the rise.
39.3 Execution - Interactive Terrain Edit

Prior to running an ITE tool, you must load imagery. If you do not have imagery covering the area
of your DTM, you can use the GRAPHICS_ONLY.sup pseudo image. While executing an ITE
tool, the results of the edit are immediately displayed in the topographically correct location. The
imagery may be displayed in any mode, stereo, split screen, or mono. Do not use continuous
contour lines when editing DTM.
The following sequence describes how to execute ITE:
1. Click Extraction > Terrain> Interactive Edit on the main workstation window.
2. Click File > Load DTM on the ITE window to select a DTM.

3. Click Setup DTM on ITE window. This prompts you to set the graphics display options.
For fast terrain graphics, you must limit the amount of

graphics by editing a block of DTM at a time. You set the Auto
XY Steps and Contour Interval in the Setup DTM window or the
Setup Overlay window when viewing terrain graphics without
editing.
4. Click Draw on the ITE window to display the DTM.

5. Select an ITE tool by clicking one of the Edit Tools. Refer to the detailed descriptions given
above on how to use each tool.
6. Review the graphical results and re-edit as necessary.
7. Click File > Save DTM on the ITE window to save edit changes.

Chapter 40
ClearFlite
ClearFlite identifies and extracts various obstructions present
in and around an airfield.
40.1 Overview
ClearFlite® is intended to enhance the productivity of airfield obstructions identification in order
to meet federal or military requirements for surveying airfield obstructions. ClearFlite takes
advantage of existing SOCET SET capabilities (Feature Extraction, Feature Export, etc.) with its
new capabilities to facilitate an efficient airfield obstruction extraction process. See “Data Files”
on page 40-21.
ClearFlite was originally designed to meet the requirements specified in the Ron Brown Airfield
Initiative Document, dated 16 June 2000, a National Geospatial-Intelligence Agency (N G A )
document. However, it has been redesigned to also support the FAR-77 and ANA survey
requirements from the FAA (document 405), the AC-18 survey requirements from the FAA AC
150/5300-18B document, and the International PANS-OPS surface geometries, as defined by the
International Civil Aviation Organization (ICAO). ClearFlite can also be used with other airfield
obstruction specifications by modifying certain files as specified in the data files. See “Data
Files” on page 40-21.
The following terms are used in ClearFlite and throughout this manual:
• Obstruction Identification Surface (OIS) - an imaginary three-dimensional complex
surface defining obstructions in airfield area. Any object higher than the OIS is an
obstruction. OIS definition may vary depending on requirements, documents, and
airfield.
• Surface - a single simple component of the OIS, such as primary surface, inner
horizontal surface, conical surface, approach surface, etc. In cases such as the approach
surface, having two disconnected parts at both runway ends, each part is considered a
distinct surface.
• Surface Model Library (SML) - SML is used for the creation of FAR-77, ANA, and
AC-18 OIS and to determine obstructions and display information in the cursor
tracking window.
For detailed specification of the OIS, the surfaces comprising it, and division of surfaces into
sections, refer to the government document applying to your work.
SOCET SET Page 40-1

Chapter 40 - ClearFlite
40.1.1 When to use ClearFlite

You run ClearFlite when you have the following data in your project:
• Geo referenced stereoscopic imagery covering the area in which obstruction data
identification is required
• Reflective surface DTM of the OIS is useful for determining “areas of interest”
containing potential obstructions
40.1.2 ClearFlite Workflow

The main steps in working with ClearFlite are:
• OIS Creation
• Obstruction Identification
• Obstruction Data Output
40.1.2.1 ClearFlite Operation Modes

When starting ClearFlite, you must select the Operating Mode from Options > Preferences. The
default is the FAA mode. There are three operating modes:
1. NGA mode:
For the NGA mode, the values being shown in the cursor tracking window will be different
from the FAA mode. One main difference will be the “Surface Name” value which will be
computed based on an ordered list of surfaces. Another difference in the cursor tracking
window is that it does not display SML tracking information. The SML tracking
information are values that help identify obstructions for FAR-77, ANA, and AC-18
surveys. For more information regarding SML tracking refer to the cursor tracking window
page. The last difference in the workflow process has changed where creating FAR-77,
ANA, and AC-18 surveys will be disabled.
2. FAA mode:
For the FAA mode, there are 3 major differences from that of the NGA mode.
• Displays SML tracking information in the cursor tracking window. See “Cursor
Tracking Window” on page 40-10 for more information regarding these values.
• The “Surface Name” value in the cursor tracking window is computed based on the
lowest surface elevation formula as opposed to an ordered list.
• Lastly, it can create FAR-77, ANA, and AC-18 surveys.
The FAA mode requires the SRP files. The SRP files are parameter files used by the SML
library to create surfaces for FAR-77, ANA, and AC-18 surveys. By default, SOCET SET
has a list of SRP files located in the MISC directory of its internal database folder. If you
choose to use an alternative set of SRP files, you must set the environment variable
SRP_DIR. When setting this variable use the full path to the location of the folder that
contains the set of SRP files.
3. PANS-OPS mode:
For the PANS-OPS mode, the values being shown in the cursor tracking window will be
different from the FAA mode. One main difference will be the “Surface Name” value
which will be computed based on an ordered list of surfaces. Another difference in the
cursor tracking window is that it does not display SML tracking information. The SML
tracking information are values that help identify obstructions for FAR-77, ANA, and AC-
Page 40-2 SOCET SET

18 surveys. For more information regarding SML tracking refer to the cursor tracking
window page. The last difference is the process workflow has changed where creating
FAR-77, ANA, and AC-18 surveys will be disabled.
40.1.2.2 OIS Creation

There are a number of ways to create an OIS surface depending on the Operating Mode. For the
NGA and PANS-OPS modes, you create OIS surfaces through an *.ois file. For the FAA mode,
you use an exchange file or an interactive method.
To create an OIS through an *.ois file, you select an *.ois file which specifies the OIS surface
parameters. The *.ois file is an ASCII file which can be edited. (See “Data Files” on page 40-
21). Once you sample the runway endpoints, ClearFlite automatically creates the OIS and saves
it both in vector form as a SOCET SET Feature Database (FDB) format and in raster form as a
grid DTM. The OIS can be displayed graphically as wire-frame or as any DTM graphics (dots,
mesh, contours, etc.).
The DTM-like representation of the OIS is not the same as the

area terrain reflective surface DTM.
Using the .ois method limits the ability to create OIS for multiple runways. There are two
methods, however, to group multiple runways together. The first method is through an exchange
file (*.exg, *.srv). The exchange file is FAR-77, ANA, or AC-18 survey ASCII text format that
contains information for each runway (See “Data Files” on page 40-21). Creating the surfaces
through an exchange file requires no sampling since all the information is in the exchange file.
Thus after specifying the exchange file and selecting Accept, the process will create multiple OIS
surfaces into your project data directory. Only one OIS can be loaded at one time for drawing.
The other method to create multiple OIS surfaces is using the interactive method. This method
has the same results as the exchange file method and is based on the same logic as the exchange
file method. However, this method is different in that it requires you to select and sample a
number of parameters and points. For example, for each runway, you must sample two distinct
runway end points. Also, for each runway, there are a number of fields that must be populated
before any creation process can begin. Once everything has been filled in, accepting the process
will create OIS for multiple runways.
40.1.2.3 Multiple Runways

When loading an obstruction surface and the Operating Mode is FAA, ClearFlite opens the
Surface Selection dialog. When the OIS was created by the Interactive method, the dialog has
three options: Continue, Reset, View/Edit Runway Data. When the OIS was created by the
Exchange File method, the dialog has two options: Continue, and Reset.
1. Continue: enables the SML Tracking information in the cursor tracking window. The
tracking information is in reference to the group of runways in the sml_cf.dat file. Pressing
continue button will pop up an Obstruction Surface dialog. You can only select FDBs that
are in the sml_cf.dat file.
2. View/Edit Runway Data: loads data from the exchange file into the interactive GUI to edit
and create new surfaces.
3. Reset: Enables you to change the exchange file in the sml_cf.dat file using one of the
following:
a. interactive method
b. exchange file method
SOCET SET Page 40-3

c. RBI (NGA)/FDB method: Which disables SML tracking and lets you load any Feature
Database for drawing.
40.1.3 Obstruction Identification

ClearFlite saves obstruction data as a SOCET SET FDB. To create a new obstruction FDB, you
must choose an obstruction specification file.
After creating an obstruction FDB, you can populate it with obstructions by viewing the area in
stereo and extract features that penetrate the OIS. You can extract point, line, and polygon
features according to the classes available in the obstruction FDB.
You can speed up the obstruction extraction by running extraction in automatic mode obstruction
identification. Automatic obstruction extraction compares the OIS with elevation data from a
reflective surface DTM and automatically extracts those terrain portions that penetrate the OIS.
The penetrating terrain perimeter is vectorized and saved in the obstruction FDB as points, lines,
or polygons, according to its shape. For lines and polygons, the most penetrating point is saved
as a separate point feature. You can run automatic obstruction extraction at any time, however, it
is recommended to run it prior to manual extraction so no obstructions are duplicated.
The automatic obstruction identification may not be fully

successful if the Obstruction specification file does not
contain at least one Point Class, one Line Class and one
Polygon Class.
It is recommended to treat the automatically extracted obstructions as potential obstructions and

review and edit them manually. You may want to run the automatic obstruction identification
with a separate obstruction FDB and display it as a reference FDB when populating the main
obstruction FDB.
When working manually, you may take advantage of the OIS division into areas (surfaces and
sections). Complete inspecting a full section or surface before moving to the next section or
surface. After you finish inspecting, you can mark each of the OIS wire-frame as inspected.
ClearFlite makes it possible to view inspected areas, unmark areas previously marked as
inspected, or reset all areas to not-inspected.
When looking for obstructions, you can track the terrain with the cursor, measure obstructions
elevation relative to the OIS, keep track of the cursor position parameters, and view changes on
the Cursor Tracking window. Cursor color and text color in the Cursor Tracking window change
depending on whether the cursor is below, above, or outside the OIS.
Upon sampling a feature you can immediately edit its attributes.
You can display a reference FDB. This reference FDB may be either an obstruction FDB or an
OIS FDB.
You can edit an obstruction FDB using SOCET SET Sketch.
At any time you can view data about the most penetrating obstructions found so far.
40.1.3.1 Obstruction Data Output

You can export the obstruction FDB using the regular feature export functionality in SOCET SET
such as Shapefile etc.
Page 40-4 SOCET SET

You can create a number of profiles using the Profile Tool and export the profiles using
SOCET SET feature export. The profile is stored in a feature database.
40.2 ClearFlite Main Window

This window is displayed when you start the application. It enables you to create and view the
Obstruction Identification Surface FDB and terrain model, track the airfield surroundings with
the cursor, and activate subordinate windows.
The ClearFlite Identification window’s selections are as follows:
File > Exit Exits the ClearFlite application.

Options > Preferences Pops up the preference window. You can set the Operating Mode and other
preferences in this window.
SELECT TO
Obstruction Surface... Prompt you to select an OIS FDB. If toggle button on the left toggles the
drawing of the OISFDB.
SOCET SET Page 40-5

SELECT TO
Reference Database... Prompt you to select a reference OIS FDB.

The toggle button on the left toggles the drawing of the Reference OIS
FDB.
Display Obstruction Surface sub-section

Draw Draw the OIS FDB and the Reference OIS FDB when the respective toggle
button is checked.
Auto Draw Automatically draws the OIS FDB and the Reference OIS FDB whenever
the image is re-centered.
View Inspected Areas Draw the OIS wire frame with different colors for inspected and not
inspected OIS sections.
Zone Limits Enable zone limit features of the OIS FDB to be drawn when checked.
Digital Terrain Model sub-section
Draw Draw the OIS DTM graphically.
Setup DTM Open the DTM Setup window. See Terrain Graphics chapter in
SOCET SET User’s Manual.
Auto Draw Automatically re-draws the DTM whenever you re-load or re-center the
image.
Enable Cursor Tracking Pop up/down the Cursor Tracking Window and activates/de-activates
cursor color coding.
Mark Areas As Inspected Enable marking/un-marking OIS areas as inspected. When enabled, select
the desired OIS sub surface and click the LMB to mark it as inspected, or
with the RMB to unmark.
Unmark All Unmark all areas previously marked as inspected.
Identify Airfield Enable obstruction extraction and related functions.
Obstructions
Obstruction FDB Prompt you to load an obstruction FDB.
Extract Obstructions Pop up the Extract Obstructions window.
Highest Above OIS Pop up the Highest Above OIS window.
Generate Report Pop up the Generate Report window.
Profile Tool Pop up the Profile window.
40.2.1 Interactive Create Obstruction Surface
ClearFlite has three different methods to create surfaces. The first two methods Interactive and
Exchange can create multiple surfaces at one time in the FAA mode. The last method can create
only one surface at a time in the NGA and PANS-OPS modes.
Page 40-6 SOCET SET

The Interactive Create Obstruction Surface window can create F77, ANA, or AC-18 surfaces
utilizing the SML library. This method will add runways, select the endpoints for the runways,
and specify specific parameters for the runway and each endpoint.
The Create Obstruction Surface window’s selections are as follows:
SELECT TO
F77 Check box Select the parameter file for the F77 type.
ANA Check box Select the parameter file for the ANA type.
AC-18 Check box Select the parameter file for the AC-18 type.
Surface Runways BLANK SPACE
Add Add a runway to the list of runways.
Delete Delete the runway highlighted in the runway list.
Length Ft Display the length of the runway in feet of the highlighted runway.
Profile Inc Ft Display the value that determines how much space in feet between profile
points.
SOCET SET Page 40-7

SELECT TO
Runway Information BLANK SPACE

End Point 1 When highlighted, LMB samples the first endpoint.
End Point 2 When highlighted, LMB samples the second endpoint.
Pavement Select the pavement value for the runway.
Runway Width Ft Determine the width of the runway in feet.
Info Tab BLANK SPACE
Info ID The ID of the runway endpoint.
Info F77 List of parameter value for F77.
Info ANA List of parameter value for ANA.
Info AC-18 List of parameter value for AC-18.
Position Tab BLANK SPACE
Position X X position of the runway endpoint.
Position Y Y position of the runway endpoint.
Position Z Z position of the runway endpoint.
Displace Threshold BLANK SPACE
Tab BLANK SPACE
Displace Display the X position of the endpoint’s displaced threshold value.
Threshold X BLANK SPACE
Displace Display the Y position of the endpoint’s displaced threshold value.
Threshold Y
BLANK SPACE
Displace
Threshold Z Display the Z position of the endpoint’s displaced threshold value.
Displace BLANK SPACE
Threshold Display the value that determines if the displace threshold exists for the
Exit endpoint.
Validate Determine if the values entered are all filled in enough to be valid
Accept Surface Create OIS surface.
Cancel Surface Cancel request to create OIS surface.
40.2.1.1 Profile Point Editor
The profile point editor window pups up when the accept surface button is pressed. If any
specified runway has a runway length greater than the profile increment, the profile point editor
window will run. The editor is a visual tool to help verify the elevations of profile points. Initially
ClearFlite will compute the elevation values for these points automatically. However, it is
important to verify that the ClearFlite computed elevation is on the ground of the runway. Using
the LMB to sample the elevation and confirm the elevation with a RMB. Use the arrow buttons
to go back and forth between points or between runways.
Page 40-8 SOCET SET

The Profile Point Editor window’s selections are as follows:
SELECT TO
X Display the profile point’s X value.

Y Display the profile point’s Y value.
Z Display the profile point’s Z value.
Left Arrow Go to the previous profile point.
Right Arrow Continue to the next profile point.
Up Arrow Go to the previous runway.
Down Arrow Continue to the next runway.
Accept Accept the profile points.
Cancel Cancel the profile points.
40.2.1.2 Exchange File Method
The exchange file essentially has all the information to create an OIS. Simply select the exchange
file and accept. Option all, you can auto-generate an obstruction FDB by checking the “Create
Obstruction” box and specify a specification file.
The Create Obstruction Surface - Exchange File window’s selections are as follows:
SELECT TO
Load Exchange File Bring up a file dialog to load an exchange file.

Create Obstruction FDB Select a specification file for the obstruction FDB.
Accept Start to create the surfaces.
Cancel Cancel.
A PDF file from NOAA NGS can be downloaded from the internet. It documents the Exchange
File format. See the following description:
The Exchange File Format documentation is a user’s guide for preparing and submitting data for
storage in the Federal Aviation Administration’s Airport Surveying-GIS Program and the
National Geodetic Survey’s Obstruction Chart Database (OCDB). It provides in detail the format
and structure of every field allowable by the OCDB. Also included are dependencies, field widths,
record order requirements and field choice lists. Please note that this document specifies format
SOCET SET Page 40-9

for the purpose of exchanging data but does not specify what data is required. Required data
should be specified by the organization requesting the data.
40.2.1.3 NGA and PANS-OPS Methods
The NGA and PANS-OPS methods creates obstructions using an ois file. This method can only
create one surface at a time and requires both end points of the runway.
The Create Obstruction Surface - NGA window’s selections are as follows:
SELECT TO
Surface Parameter File Prompt you to select a parameter file that fits your airfield specifications.
Airfield End Points Enable you to view and edit the sampled end point coordinates.
Accept Create the OSI FDB and terrain model, and saves the model. This button is
not sensitive until both endpoints have been sampled.
Cancel Cancel OIS creation.
40.2.2 Cursor Tracking Window

The Cursor Tracking window pops up automatically
when you load or create Obstruction Surface or click
Enable Cursor Tracking. The window displays the
current cursor elevation and the cursor position with
respect to the OIS. The Add to Log File button writes
the current data in the cursor tracking window into the
ois_cursor_tracking.log file for review. The
ois_cursor_tracking.log file resides in the project data
folder.
Cursor color and window text color change according
to cursor height with respect to OIS as follows:
• Red - the cursor is above the OIS.
• Green - the cursor is below the OIS.
• White - the cursor is outside of the OIS area.
40.2.2.1 SML Tracking

In addition to the standard values that the cursor tracking window displays, it can also display
another set of values that relates airport zone information to the cursor called SML (Surface

Model Library) tracking. When ClearFlite is in the FAA operating mode and tracking is on, the
cursor tracking window displays the following set of additional variables.
Distance Over: Distance over is the distance perpendicular to the extended

runway centerline. It will be designated as either “R” (right)
or “L” (left) of the extended runway centerline from the
point of view of a pilot approaching the runway.
Distance Out: Distance “out” is from the runway end which is along the
extended runway centerline.
Threshold: Distance to the threshold. The threshold is the displaced

threshold if there is one. Otherwise it is the runway end.
Required Any: Indicator that the current position would be a required point
for any zone, whether selected or not.
Required Select: Indicator that the current position would be a required point
for a zone with the selected surface.
To Edge: The shortest distance from the edge of the selected surface.
Approach Slope: The slope of the approaching surface.
40.2.2.2 Distance Tracking

Another set of values that the cursor tracking window displays are the distance tracking
information values. These values are shown/hidden through a check box on the Extract
Obstructions window labeled as a distance info check box.
Current Feature: Displays the feature id number of the “current” feature in

the feature retrieval list.
Closest Feature: Displays the feature id number of the feature that is closest
to the cursor excluding the current feature.
Current xy-Δ: Displays the xy distance from the current feature to the
cursor position.
Current z-Δ: Displays the z difference between the current feature’s

elevation and the cursor’s elevation.
Closest xy-Δ: Display the xy distance from the closest feature to the
cursor position.

40.3 Sketch Toolbar

Refer to the Sketch chapter.
40.4 Extract Obstructions Window in Manual Mode
The following menu choices are for Manual and Automatic modes.
Options > Save

Options > Set Closest Color Sets the color for the closest color
Options > Sketch Displays the Sketch Preferences window.
Preferences
The Extract Obstruction (Manual mode) window’s selections are as follows:
SELECT TO
Draw Obstructions Draw all the features in the Obstruction FDB. Three colors are used in the
drawing:
• RED - When the feature is the highest in an OIS sub-surface
and penetrates the OIS.
• GREEN - When the feature is the highest in an OIS sub-surface
but does not penetrate the OIS.
• YELLOW - Features that do not fit into the RED or GREEN
criteria.
Auto Draw Automatically re-draws the obstruction features whenever you re-load or
re-center the image.
Manual tab Change mode to manual extraction. [Default]
Automatic tab Enable automatic obstructions extraction.
Current Class... Prompt you to select the current obstruction class.
NOTE: To manually extract features, you must select an
obstruction class first.

SELECT TO
Auto Create Enable or disable the Auto Create mode, When enabled, after accepting a
feature with the RMB, you will be asked to sample the ground near the
obstruction. Only then will the feature be inserted into the Obstruction
FDB. When disabled, the feature will be inserted into the Obstruction FDB
when you accept it. By default, Auto Create is enabled.
Distance Info Shows or hides distance information of the obstruction FDB and cursor
that appears in the cursor tracking window. When checked, values will
appear in the cursor tracking window.
Feature Retrieval Pop up the Feature Retrieval window and let you edit any of the attributes
of the obstruction feature extracted.
Close Pop down Extract Obstructions window.
40.5 Extract Obstructions Window in Automatic Mode

The Obstruction Extraction (Auto mode) window’s selections are as follows:
SELECT TO
Draw Obstructions Draw all the features in the Obstruction FDB. Three colors are used in the
drawing:
• RED - When the feature is the highest in an OIS sub-surface
and penetrates the OIS.
• GREEN - When the feature is the highest in an OIS sub-surface
but does not penetrate the OIS.
• YELLOW - Features that do not fit into the RED or GREEN
criteria.
Auto Draw Automatically re-draws the obstruction features whenever you re-load or
Manual tab Changes mode to manual extraction. [Default]
Automatic tab Enable automatic obstructions extraction.
Reflective DTM... Prompt you to load a Reflective DTM.
Elevation Select an elevation threshold from 0 to 200 meters by moving this slider.
The default value is 1.0 meter. The program will extract obstructions that
are at least this elevation above the OIS.
Start Create an Obstruction FDB from the data in the Reflective DTM.

SELECT TO
Close Pop down Extract Obstructions window.
40.5.1 Automatic Extracted Features

• The Automatic Extraction process creates features of three types: Point, Line and Area.
It does so by intersecting the Reflective DTM with each of the OIS sub surfaces. Hence,
Each feature belongs to only one OIS sub surface.
• An area feature is a polygon that encircles a continuous area that penetrates at least the
Elevation threshold above the OIS. A line feature is a continuous line that penetrates
above the OIS, but its side points are either below the Elevation threshold (relative to
the OIS) or belong to another sub surface. A point feature is either an isolated point that
penetrates at least the elevation threshold above the OIS, or the highest point in an area
or line obstruction (see below).
• The attributes of each line or area feature (those features are composed of more than
one point), are taken from the first point in the feature. For each such feature, ClearFlite
finds the highest point, which is above OIS and inside the borders of that feature, and
adds it to the database as a separated point feature.
Be sure not to extract to a given obstruction DTM with the

same Reflective DTM more then once. This will just duplicate
features in the database.
• Using the default Elevation threshold can cause a lot of “noise” in the runway area,
where the OIS is on the ground. To eliminate that “noise”, use the slider in the Extract
Obstruction window and choose higher elevation.
40.5.2 Extract Obstructions Window in Edit Mode

To Delete: See “Sketch,” Chapter 58 for details.
To Edit Attributes: Go to the extraction manual mode. Select the class. Press the Feature Retrieval
button. Select the feature by either picking it in image display window or from the table. Edit the
attributes. When finished, save the changes to the attributes and exit.

40.5.3 Feature Retrieval Window

This window displays all the features and their attributes of the selected class with a set
automatically populated attribute fields.
The Feature Retrieval window’s selections are as follows:
File > Save Saves the changes.

File > Exit Exits the Feature Retrieval window.
Options > Select Class Changes the class that the Feature Retrieval window displays.
SELECT TO
Zone Info Displays AOC or ANA values of the features.

Fence Draw a minimum bounding polygon to select features.
Edit Z Bias Set height offset.
Collection For a class with the “Pt_Type” attribute, displays a list of check boxes that
determine the Pt_type attribute value.
Draw Features Draw all the features in the Feature Retrieval table.
Query Select a subset of the features in the OIS FDB.

40.5.3.1 Z Bias Actions

This window allows you to enter a height offset over either an object or a pre-defined object. This
window is obtained by click Edit Z Bias on the Feature Retrieval window.
The Z Bias Action window’s selections are as follows:
SELECT TO
Text Field Enter a height offset. Unit is the project Z unit (feet/meters).
Pre-Defined Values Make a selection:
Non-Interstate Road (15 Feet)
Interstate Road (17 Feet)
Railroad (23 Feet)
Add to Z Bias Add a height offset or a predefined value offset to the elevation. This also
BLANK SPACE allows you to add additional height offsets to previous established offsets.
Reset Z Bias Reset the height offset to 0.
Set Z Bias Set the height offset to your entry in either the Text field or the Pre-
Defined Value above.
NOTE: This selection does not add to any other previous height
offsets.
Apply Z Bias Execute your selected action.

Done Exit window.

40.5.4 Highest Above OIS Feature

The Highest Above OIS Feature window displays statistics about the highest feature relative to
the OIS (not necessarily the feature with the highest elevation). To display this window, click the
Highest Above OIS button in the ClearFlite main window.
The Highest Above OIS Feature window’s selections are as follows:
SELECT TO
Feature Class Display the class that the highest feature belongs to.
Surface Name Display the name of the OIS sub surface that the highest feature belongs
to.
Section Number Display the section number of the feature in the current OIS sub surface.
Feature Elevation Display the elevation of the highest feature relative to the project’s datum
of all obstructions extracted.
Height Above OIS Display the elevation of the highest feature relative to the OIS of all
obstructions extracted.
Close Pop down the Highest Above OIS window.
40.5.5 Report Generation

The Report Generation window’s selections are as follows:
SELECT TO
File Name Enter the name and path to the UDDF Report Generation file.
Automatically adds the extension F77 to the file name.
Start Start the Report Generation. Produces a UDDF report file from the
Obstruction FDB and the OIS file. Fields that cannot be deduced by
ClearFlite, are left empty.
Close Close the Report Generation window.

40.5.6 Profile Tool
Surface Profile window
The Surface Profile window’s selections are as follows:
SELECT TO
Grid Spacing X: The grid spacing in feet along the surface center line or the X axis.
Grid Spacing Y: The grid spacing in feet along the Y axis. The Y axis represents elevation.
Select Classes... Pops up the Select Classes window. Obstruction features belong to certain
feature classes. Using the Select Classes window, you can turn certain
feature classes on or off from the profile.
Load DTM... Pops up DTM Selection window. The selected DTM is used to compute the
terrain profile.
Save Profile... Saves the profile data into a feature database. You may export the feature
database using SOCET SET feature export.
Close Close the Surface Profile window.
40.6 Execution
40.6.1 Getting Started

1. Load airfield imagery, preferably a stereo pair, onto the main image display.
2. Activate ClearFlite by clicking Extraction > ClearFlite from main SOCET SET menu.
3. If you do not already have an OIS FDB and terrain model in your project’s data directory,
create them now by following instructions below in the Creating Surface Files section.
Otherwise, click Obstruction Surface... and select the surface file name.
4. [Optional] Click Reference Database... and select a reference FDB.
5. [Optional] Use the Preferences > Graphics/Terrain Settings from the main SOCET SET
menu pulldown, and load a DTM of the ground surface of the airfield area. This will help
to sample the runway end points and mensurate obstructions.

40.6.2 Creating Surface Files
1. Click Obstruction Surface.

a. If the new window title is “Surface Select” go to step 2.
b. If the new window title is “Choose Method” go to step 3.
c. If the window title is “Create Obstruction Surface” go to step 19.
2. Do one of the following:
a. If you click Continue, go to step 20.
b. If you click Reset, go to step 3.
c. If you click View/Edit Runway, go to step 4.
3. Do one of the following:
a. If you click Interactive, go to step 5.
b. If you click Exchange File, go to step 11.
c. If you click FDB/RBI, go to step 14.
4. The window shows the information that was used to create the last SML FDB. You can edit
the GUI and re-sample endpoints to create or modify the existing surfaces. When done, go
to step 19.
5. Move cursor to the runway’s first end point and sample it with the LMB. An icon will show
the point’s location. If you are not satisfied with it, sample again. Also fill in the ID field
on the GUI and select parameter files for F77, ANA, AC-18 field boxes. The other fields
are optional.
6. Move the cursor to the runway’s second end point (opposite runway end). Sample the point
the same way you have sampled the first one.
7. When the two endpoints are sampled and everything is filled in. You can repeat the process
by click ADD for adding another runway. Go back to step 5 and repeat the process.
8. Click Validate. If the runway information is valid, then the profile point editor will appear
and go to step 9. If its not valid, the preview pane will appear.
9. Sample through all the profile points to verify each of their elevation. Once done click
Accept. The preview pane will appear. Read the results of the preview pane and close the
window. Go to step 10.
10. Click Accept on the Interactive GUI. Depending on the parameters passed in one or more
OIS FDBs will be created. The Interactive GUI will disappear and the Main window will
appear. Go to step 19.
11. Click Load Exchange File to load an exchange file.
12. [Optional] Select an .obs specification file to tell ClearFlite that you want to create an
obstruction feature database as well.
13. Click Accept. The Exchange File GUI will disappear and the Main window will appear. Go
to step 19.
14. Enter the name of a new surface file. The “Create Obstruction Surface” window will be
visible. Go to step 15. Although an NGA (RBI) surface can be created with steps 14 and
15, the preferred method is to define the NGA Operating Mode from Options > Preferences
and proceed with that workflow.
15. Click Surface Parameter File... and pick a parameter file (*.ois) that fits your airfield.
16. Move the cursor to the runway’s first end point and sample it with the LMB, or sample hot-
key. An icon will show the point’s location. If you are not satisfied with it, sample again.
The icon will move to the new location. Accept the end point with the RMB, or accept hot-
key.

17. Move the cursor to the runway’s second end point. Sample the point the same way you have
sampled the first one.
18. When the two end points are sampled click Accept. An OIS FDB and an OIS DTM will be
created and saved on the disk automatically. The “Display Obstruction Surface” area will
be visible again and the Cursor Tracking window will pop up. Go to step 21.
19. Click Obstruction Surface, then Continue to load the recently created or loaded SML data.
Go to step 20.
20. Select a OIS FDB that among the list of OIS FDBs that was created through SML. Continue
on to step 21.
21. [Optional] Select Draw or Auto Draw in the “Wire Frame Model” area will display the OIS
feature polygons on the main image display.
22. [Optional] Use the drawing buttons in the “Digital Terrain Model” area in order to draw the
OIS terrain model on the main image display. See “Terrain Graphics,” Chapter 36 for an
explanation on how to setup the drawing. Using the Mesh Mode and the Elevation Color
Source in the DTM setup window, gives good view of the OIS.
40.6.3 Manual Extraction

1. Click Manual to select the Manual Extraction mode.
2. Click Current Class... and choose an obstruction class that describes the obstruction
feature.
3. Choose an OIS Section and scan it with the cursor. The cursor will become red if on top of
a feature that is higher than the OIS.
4. [Optional] If Auto Draw is not selected, click Draw Obstructions to display the
obstructions that have been created.
5. On the Sketch Toolbar, make sure that the create method is selected in order to enable
manually extracting features.
6. Sample the obstruction with the LMB. Make sure that the first sample is on the highest part
of the obstruction. The program will use the first sample as a basis for its attribute
calculating. If the obstruction is of a Point Class, it can be moved with additional sample
button clicks (like the end points).
7. Accept the obstruction feature with the RMB.
8. If the “Auto Create” button is pressed, sample the ground beneath the obstruction with the
LMB.
9. [Optional] If you wish to cancel some of the sampling actions, click undo action on Sketch.
10. When accepting the obstruction feature (and sample the ground if Auto Create is enabled),
the feature is automatically inserted into the Obstruction FDB. Six user attributes are
calculated automatically for the feature. These are:
• HGT - The feature’s height above the terrain in meters (only if Auto Create is
enabled).
• HGF - The feature’s height above the terrain in feet (only if Auto Create is enabled).
• ZV7 - The feature’s geoid elevation in meters.
• Z7F - The feature’s geoid elevation in feet.
• Z5M - The feature’s ellipsoid elevation in meters.
• Z5F - The feature’s ellipsoid elevation in feet.

40.6.3.1 Automatic Extraction

1. Click Automatic to select the Automatic Extraction mode.
2. [Optional] If Auto Draw is not selected, click Draw Obstructions to display the
obstructions.
3. Click Reflective DTM to select a DTM.
4. [Optional] Choose the elevation from 0 to 200 meter by moving the slider. The default
elevation is 1 meter.
5. Click Start and wait until the automatic extraction process is complete. If the Auto Draw
button in the Extract Obstructions window is checked, the program will draw the features
on the RT display as soon as it extracts them.
40.6.3.2 Obstruction Feature Editing

See “Sketch,” Chapter 58 for feature editing.
40.6.4 Mark Areas As Inspected

1. Click Mark Areas As Inspected if the “Identify Airfield Obstruction” button is selected.
2. [Optional] Click View inspected Areas to display all marked areas.
3. Press the LMB to mark the Obstruction Areas that have been inspected.
4. [Optional] Unmark the areas with the RMB.
5. [Optional] Click Unmark All to unmark all marked areas.
40.6.5 View Highest Above OIS Features

1. Click Highest Above OIS... to view the statistic characteristics of the highest feature. The
Highest Above OIS Feature window will pop up and display the feature’s data.
2. [Optional] Click Close to pop down the window.
40.6.6 Report Generation

1. Click Generate Report.... The Report Generation window will pop up.
2. Enter the name and path of the report. If the name does not contain an extension, the
extension F77 will be added automatically.
3. [Optional] If the entered name does not contain a leading path, press Enter on your
keyboard and the path to the project’s data directory will be added automatically.
4. [Optional] Click Close to pop down the window.
40.7 Data Files
40.7.1 OIS Parameter Files

The OIS Parameter files are used in the construction of the surface feature database. They define
the Obstruction Identification Surface.
An Example
OIS File 1.0

# AEM airport imaginary surfaces.
AIRPORT_CATEGORY AEM
INPUT_UNITS FEET
ARC_ANGLE_DEG 5.0
PRIMARY_WIDTH 2000
OUTER_HORIZONTAL_WIDTH 42532
40.7.2 General Structure

An OIS parameter file is a SOCET SET keyword file. By convention, it has the extension “ois”,
but this extension is not mandatory. The file is composed of a header line, blank lines, comment
lines and data lines. The order of the lines is not important, except the first line (header).
• The header is composed of the following string: “OIS File 1.0". This string is used as
a magic number. It must exist as the first line in every OIS parameter file.
• A comment line is a line that begins with ‘#’.
• Each data line in the file contains two words. The first word is a keyword. The second
word is a value for that keyword. Those values can be changed according to the OIS
specifications.
40.7.2.1 AIRPORT_CATEGORY Keyword

AIRPORT_CATEGORY RBAI
The AIRPORT_CATEGORY keyword defines an OIS structure. It defines what kind of sub
surfaces the OIS is composed of and what sections each surface has. Accordingly, most of the
keywords in the file depend on the airport category and are mandatory with respect to that
category. The current version supports eight airport categories, RBAI, AEM,
PANS_OPS_NON_INSTRUMENT, PANS_OPS_NON_PRECISION,
PANS_OPS_PRECISION, NON_PRECISION, PRECISION, and NON_PRECISION.
40.7.2.2 INPUT_UNITS Keyword

INPUT_UNITS FEET
The INPUT_UNITS is an optional keyword in any OIS parameter file. It defines the units of
values that describe elevations or lengths. The default units, if this keyword is not found in the
file, are feet. Using INPUT_UNITS METERS, will make ClearFlite use meters for the unit
values.
40.7.2.3 AIRPORT_ELEVATION Keyword

AIRPORT_ELEVATION4.0
The AIRPORT_ELEVATION is an optional keyword in any OIS parameter file. If this keyword
exists in the OIS parameter file, the value attached to it will be taken as the runway elevation.
This value is used as a base elevation for the construction of all OIS sub surfaces. If this keyword
does not exist in the OIS parameter file, ClearFlite will calculate the runway elevation as the
minimum of the two sampled runway end point elevations.

40.7.2.4 RBAI Category Mandatory Keywords

The following keywords must exist in every OIS parameter file that has the RBAI airport
category.
KEYWORDS DESCRIPTION
ARC_ANGLE_DEG ClearFlite simulates half circles that are used in construction of the outer
horizontal, conical and inner horizontal sub surfaces, by polygonal lines.
The ARC_ANGLE_DEG value gives the angle between each two adjacent
lines. Smaller values give better simulation, but the resulting polygons will
have more vertices and more time will be required for some of ClearFlite’s
calculations.
INNER_HORIZONTAL_ The elevation of the inner horizontal surface above the runway elevation.
ELEVATION
INNER_HORIZONTAL_ The radii of the inner horizontal surface half circles and the width of the
WIDTH inner horizontal surface where it is parallel to the runway centerline.
CONICAL_SLOPE The slope (it has no units) at which the conical surface expands from the
inner horizontal surface toward the outer horizontal surface.
CONICAL_WIDTH The horizontal width of the conical surface from the inner horizontal
surface until the outer horizontal surface (the distance is measured along X
and Y coordinates only, not Z).
OUTER_HORIZONTAL_ The elevation of the outer horizontal surface above the runway elevation.
ELEVATION
OUTER_HORIZONTAL_ The horizontal width of the outer horizontal surface from the conical
WIDTH surface until the outer horizontal surface end.
PRIMARY_WIDTH The width of the primary surface.
CLEAR_ZONE_LENGTH The distance from a runway end point to the end of the primary surface
along the runway centerline.
APPROACH_START The distance from a runway end point to the point where the approach
surface starts.
APPROACH_LENGTH The horizontal length of the approach surface along the runway centerline.
APPROACH_SLOPE The slope at which the approach surface expands along the runway center
line, from the approach start until it reaches the 500 feet elevation above
the runway elevation.
APPROACH_END_WIDTH The width of the approach surface at its far end.
TRANSITION_SLOPE The slope of all transitional surfaces, tangent to the runway centerline.
PRIMARY_SECTION_ The width along the runway centerline of a full sized primary surface
WIDTH section. The sections at the center of the runway may be smaller. ClearFlite
creates sections of size PRIMARY_SECTION_WIDTH starting at both
runway endpoints, until the remaining distance is less than two times
PRIMARY_SECTION_WIDTH. Then if the remaining distance is less
than or equal to PRIMARY_SECTION_WIDTH, one more section with
that width will be created. Otherwise, two more sections will be created.
The two section will have the width of half the remaining distance.
TRANSITION_SECTION_ The width along the runway centerline of a full sized primary/approach
WIDTH transitional surface section. The same algorithm as above, is used to create
those sections.
APPROACH_SECTION_ The length of the small section of the approach surface. This section starts
SMALL at the beginning of the approach surface.

APPROACH_SECTION_ The length of the first largest section of the approach surface. This section
LARGE_1 starts at the beginning of the approach surface.
APPROACH_SECTION_ The length of the second largest section of the approach surface. This
LARGE_2 section starts where the first large section ends.
APPROACH_SECTION_ The length of the third largest section of the approach surface. This section
LARGE_3 starts where the second large section ends.
APPROACH_SECTION_ The length of the fourth largest section of the approach surface. This
LARGE_4 section starts where the third large section ends.
PRIMARY_CODE The FACC code of the primary surface. This code is written to the f_code
attribute of the features that represent primary sections in the surface
feature database.
APPROACH_CODE The FACC code of the approach surface. This code is written to the f_code
attribute of the features that represent approach sections in the surface
feature database.
PRIMARY_TRANSITION_ The FACC code of the primary/approach transitional surface. This code is
CODE written to the f_code attribute of the features that represent primary/
approach transitional sections in the surface feature database.
INNER_HORIZONTAL_ The FACC code of the inner horizontal surface. This code is written to the
CODE f_code attribute of the features that represent inner horizontal sections in
the surface feature database.
CONICAL_CODE The FACC code of the conical surface. This code is written to the f_code
attribute of the features that represent conical sections in the surface
feature database.
OUTER_HORIZONTAL_ The FACC code of the outer horizontal surface. This code is written to the
CODE f_code attribute of the features that represent outer horizontal sections in
the surface feature database.
CONICAL_OUTER_ The FACC code of the primary/approach transitional surface. This code is
TRANSITION_CODE written to the f_code attribute of the features that represent primary/
approach transitional sections in the surface feature database.
40.7.2.5 AEM Category Mandatory Keywords

The AEM type OIS is composed of one outer horizontal surface that covers all the area within the
RBAI outer horizontal surface. It is used for training.
horizontal surface, by polygonal lines. The ARC_ANGLE_DEG value
gives the angle between each two adjacent lines. Smaller values give a
better simulation, but the resulting polygons will have more vertices.
PRIMARY_WIDTH The width of the primary surface. There is no primary surface in an AEM
OIS. It is used to calculate the outer horizontal surface sizes.
OUTER_HORIZONTAL_ The radii of the outer horizontal surface half circles and the width of the
WIDTH outer horizontal surface where it is parallel to the runway centerline.

AEM Category Optional Keywords
40.7.2.6 ois.spc File
OUTER_HORIZONTAL_ The elevation of the outer horizontal surface above the runway elevation.
ELEVATION The default is 0.
OUTER_HORIZONTAL_ The FACC code of the outer horizontal surface. This code is written to the
CODE f_code attribute of the feature that represents outer horizontal surface in
the surface feature database. The default value is empty string.
ClearFlite uses this specification file to create a surface database. The surface database has a
polygon class (OIS_PARTS) for OIS sections, a point class (END_POINTS) for runway end
points, a text class (PARAMETER_FILE) for OIS parameter file, and an optional
ZONE_LIMITS polygon class. ClearFlite creates the surface feature database automatically. You
must not alter the ois.spc file.
40.7.2.7 Obstruction Specification File

ClearFlite uses a specification file to create an obstruction feature database. The specification file
must have feature classes of type POINT, LINE and POLYGON. Refer to the Feature
Specification Editor chapter for more details.
Auto Attributes - ClearFlite automatically calculates the value of six attributes: HGT, HGTF,
ZV7, ZV7F, Z5M, and Z5F (HGT and HGTF need the Auto Create option on).
See “Execution” on page 40-18 for more of an explanation about those attributes.
40.7.2.8 PANS-OPS Category Mandatory Keywords

The following keywords must exist in every OIS parameter file that has the PANS-OPS airport
category.
horizontal, conical and inner horizontal sub surfaces, by polygonal lines.
The ARC_ANGLE_DEG value gives the angle between each two adjacent
lines. Smaller values give better simulation, but the resulting polygons will
have more vertices and more time will be required for some of ClearFlite’s
calculations.
INNER_HORIZONTAL_ The elevation of the inner horizontal surface above the runway elevation.
ELEVATION
INNER_HORIZONTAL_ The radii of the inner horizontal surface half circles and the width of the
WIDTH inner horizontal surface where it is parallel to the runway centerline.
CONICAL_SLOPE The slope (it has no units) at which the conical surface expands from the
inner horizontal surface toward the outer horizontal surface.
CONICAL_WIDTH The horizontal width of the conical surface from the inner horizontal
surface until the outer horizontal surface (the distance is measured along X
and Y coordinates only, not Z).

PRIMARY_WIDTH The width of the primary surface.

RUNWAY_MIN_LENGTH The minimum allowed runway length.
RUNWAY_MAX_LENGTH The maximum allowed runway length.
INNER_APPROACH_ The width of the approach surface within the inner surface.
WIDTH
INNER_APP_DIST_FROM The horizontal distance of the inner approach surface from the runway
_THRESH threshold.
INNER_APPROACH_ The length of the approach surface within the inner surface.
LENGTH
INNER_APPROACH_ The slope of the approach surface within the inner surface.
SLOPE
APPROACH_DIST_FROM The horizontal distance of the approach surface from the runway threshold.
_THRESH
APPROACH_ The value with which the approach surface diverges away from the
DIVERGENCE runway.
APPROACH_S1_LENGTH The length of the first largest section of the approach surface.
APPROACH_S1_SLOPE The slope of the approach surface within the first largest surface section.
APPROACH_S2_LENGTH The length of the second largest section of the approach surface.
APPROACH_S2_SLOPE The slope of the approach surface within the second largest surface
section.
APPROACH_ The horizontal length of the full approach surface.
HORIZONTAL_LENGTH
BALKED_LANDING_ The width of the balked landing surface at its inner edge.
LENGTH_INNER_EDGE
BALKED_LANDING_ The horizontal distance of the balked landing surface from the runway
DIST_FROM_THRESH threshold.
BALKED_LANDING_ The value with which the balked landing surface diverges away from the
DIVERGENCE runway.
BALKED_LANDING_ The slope of the balked landing surface.

SLOPE
TAKE_OFF_LENGTH_ The width of the take-off surface at its inner edge.
INNER_EDGE
TAKE_OFF_DIST_FROM_ The horizontal distance of take-off surface from the runway threshold.
THRESH
TAKE_OFF_ The value with which the take-off surface diverges away from the runway.
DIVERGENCE
TAKE_OFF_END_WIDTH The width of the take-off surface at its outer edge.
TAKE_OFF_LENGTH The horizontal length of the take-off surface.
TAKE_OFF_SLOPE The slope of the take-off surface.

APPROACH_LENGTH The horizontal length of the approach surface along the runway centerline.
APPROACH_SLOPE The slope at which the approach surface expands along the runway center
line, from the approach start until it reaches the 500 feet elevation above
the runway elevation.
APPROACH_END_WIDTH The width of the approach surface at its far end.
TRANSITION_SLOPE The slope of all transitional surfaces, tangent to the runway centerline.
PRIMARY_SECTION_ The width along the runway centerline of a full sized primary surface
WIDTH section. The sections at the center of the runway may be smaller. ClearFlite
creates sections of size PRIMARY_SECTION_WIDTH starting at both
runway endpoints, until the remaining distance is less than two times the
PRIMARY_SECTION_WIDTH Then if the remaining distance is less than
or equal to PRIMARY_SECTION_WIDTH, one more section with that
width will be created. Otherwise, two more sections will be created. The
two sections will have the width of half the remaining distance.
TRANSITION_SECTION_ The width along the runway centerline of a full sized primary/approach
WIDTH transitional surface section. The same algorithm as above, is used to create
those sections.
APPROACH_SECTION_ The length of the small section of the approach surface. This section starts
SMALL at the beginning of the approach surface

Chapter 41
Feature Specification Editor

Create and edit specification files for Feature Extraction.
41.1 Overview
The Feature Extraction Specification File Editor is used to create and edit specification files for
feature extraction. To start this application, click Extraction > Feature > Feature Specification
Editor. This application uses the same license as the Feature Extraction application. You must
have the feature extraction license in order to run this application. This application cannot run if
Feature Extraction is running and your system has only one Feature Extraction license.
SOCET SET Page 41-1

Chapter 41 - Feature Specification Editor
The Specification File Editor’s selections are as follows:
File > New Prompts you to select a new specification file.

File > Open Prompts you to select an existing specification file.
File > Save Saves the specification to disk.
File > Save As Saves the specification to a new file name on disk.
File > Exit Exits the Specification Editor.
Help > Content Starts the on-line documentation.
Help > About FACC Starts up the on-line document for FACC from N G A .
SELECT TO
Specification File Display the name of the specification file.

Acronym Display the acronym of the specification file such as VMAP1, FFD, etc. It
is optional.
Official Designation Display the official designation such as MIL-J-89 Joint Operation Graphic-
Radar. It is optional.
Author Display author’s name of the specification file. It is optional.
Product Scale 1: Display the product scale such as 24,000. It is optional.
Specifications Derived From Right click in the Specification Derived From area without selecting an
existing item first, the Add button pops up. Click LMB on the Add button
to select an existing specification file as the seed specifications. In most
cases, you use the FACC.spc from N G A as the seed specifications. You
can also use any other specification files as your seed specifications. The
Available Classes list updates accordingly. The Available Classes list is
determined by the specification files in the Specification Derived From
list.
Delete a file after highlighting a specification file in the Specification
Derived From area and click RMB, a Delete button pops up. Click LMB on
the Delete button to remove the highlighted specification file. The
Available Classes list updates accordingly.
Classes Displays classes that have been added. Clicking on the button will sort the
classes either ascending or descending.
Available Classes Lists the classes available. Clicking on the button will sort the classes
either ascending or descending.
Adds a class from the Available Classes list to the Classes list. You select a
class in the Available Classes list first, and then press the button to add it to
the Classes list. The Classes list displays the names of all classes of the
specification file. Class information is displayed in the Class Editor
window. You can arrange the order of classes by removing all the classes
from the Classes list to the Available Classes list, and then adding them
back in the desired order.
Remove a class from the Classes list to the Available Classes list. You
select a class in the Classes list first, and then press the button to add it to
the Available Classes list.
Page 41-2 SOCET SET

SELECT TO
New Create a brand new class. You use the Class Editor window to create a new
class. And then press the Save button in the Class Editor to save it.
41.1.1 Class Editor

The Class Editor window is used to create, edit, and view information of a feature extraction
class.
The Class Editor window’s selections are as follows:
SELECT TO
Class Name Name the class. Class name has a length limit of 80. Supported characters
are from [0-9], [A-Z], [a-z], and ‘.’. Other characters are removed.
Geometry Choose the Geometry of the class.
Monotonic Automatically enforce monotonicity of the features in the class. Monotonic
is only applicable to Line or Multiline geometry.
Polygon Topology Polygon topology is only applicable to Polygon or Polyhedron geometry. It
is recommended that you use polygon topology for your polygon feature
extraction because it is much more efficient.
SOCET SET Page 41-3

SELECT TO
Line
Color Select the line color.
Style Select a line style.
Width Specify the line width in pixels.
Opacity Specify the opacity of the line. 0 is transparent and 100 is solid.
Icon Spacing Designate the spacing in pixel between icons. Using 0 when you want to
display an icon at every vertex.
Icon: Enable the selection of icons.
Fill BLANK SPACE
Color Select a polygon fill color.
Pattern Select a polygon fill pattern.
Opacity Specify the opacity of the fill. 0 is transparent and 100 is sold fill.
Feature Attribute Indicate the Attributes list is for feature attributes instead of element
attributes. To display element attributes, you must set the Element
Attribute.
Element Attribute Indicate the Attributes list is for element attributes. Only polyhedron or
multiline geometry can have element attributes.
Adds an attribute from the Available Attributes list to the Attributes list.
You select an attribute in the Available Attributes list first, and then press
the button to add it to the Attributes list. The Attributes list displays the
names of all attributes of the class. Attribute information is displayed in
the Attribute Editor window. The available attributes list is ALWAYS
generated from N G A FACC.
Removes an attribute from the Attributes list. You select an attribute in the
Attributes list first, and then press the button to remove it.
Attribute Constraints... Display the Attribute Constraints window.
Save Save the edits.
Close Close this window without save any edits.
41.1.2 Attribute Editor

The Attribute Editor window is used to create, edit, and view information of an attribute.
Page 41-4 SOCET SET

The Attribute Editor window’s selections are as follows:
SELECT TO
Attribute Name The Name of the attribute. The length limit is 72 characters.
Attribute Type Select one of seven attribute types.
Numeric Tab Use for integer, float, and double attribute types.
Min Value Identify the minimum value for the numeric attribute.
Max Value Identify the maximum value for the numeric value.
Default Value Identify the default value for the numeric value.
Preferred Value Identify the preferred value.
Enum Tab Use for enum attribute only.
Enum Value The integer value stored in the feature database. The first element has the
BLANK SPACE enum value of 0, and the second has enum value of 1 etc.
Description Enter the description of the element. It has a length limit of 80 characters.
BLANK SPACE Supported characters are from [0-9], [A-Z], and [a-z]. Other characters are
removed.
Add
Add a new element, right click in the Enum Tab area and click on the Add
BLANK SPACE button.
Delete Delete an element, right click at the element to be deleted, and click on the
BLANK SPACE Delete button.
Undo Delete Undo delete, right click in the Enum Tab area and click on the Undo Delete
button.
String Tab Use for String attribute only.
Length Display the length of the string.
Default Value Display the default value for string attribute. Supported characters are
BLANK SPACE from [0-9], [A-Z], [a-z], and ‘.’. Other characters are removed.
Preferred Value Display the preferred value for a string attribute.
Date Tab Use for Date attribute only.

Default Value Display the default date.
Preferred Value Display the preferred date.
DateTime Tab Use for DateTime attribute only.
Default Value Display the default date-time.
Preferred Value Display the preferred date-time.
Save Save the edits.
Close Close this window.
41.1.3 Attribute Constraints

You use the Attribute Constraints window to create, edit, and view constraints of attributes within
a class. Attributes in a feature class may have dependencies. You can enforce attribute
dependencies using the Attribute Constraints. For example, a building class has an AREA
attribute and a REPRESENTATION attribute. When the AREA is smaller than 100, the
REPRESENTATION attribute should have a value of POINT_REPRENSENTATION. You use
the Attribute Constraints to enforce this dependency. In Feature Extraction, when the AREA
attribute value is smaller than 100, the REPRESENTATION attribute is automatically changed
SOCET SET Page 41-5

to POINT_REPRESENTATION. The Attribute Constraints are per feature class. Feature

Extraction will enforce Attribute Constraints to all the features in the same feature class.
The Attribute Constraints window’s selections are as follows:
SELECT TO
Class Name The name of the class.

Attributes A list of all attributes. When one of these is selected it is the constraining
attribute.
Constrained Attributes A list of all attributes. When one of these is selected it is the attribute being
constrained.
Type The type of the selected attribute.
Value The combo box allows selection of =, <, >, or range. The value under the
Attributes list is the value at which the selected attribute will constrain.
The value under the Constrained Attributes list is the valid value(s) for the
selected attribute if the constraining attribute is equal to or in the defined
value range.
Constraint Table This table shows all constraints that have been added.
OK Save the constraints and close this window.
Apply Save the constraints and continue editing.
Cancel Discard any changes made and close this window.
Add Add a new constraint.
Delete Deletes the highlighted constraint(s) in the constraint table.
Page 41-6 SOCET SET

Chapter 42
Feature Extraction
Feature Extraction is used to create and store a database of
three-dimensional point, polyline, and polygon objects which
can represent three-dimensional features in your imagery.
42.1 Overview
You perform F e a t u r e E x t r a c t i o n to create and store a database of three-dimensional point,
poly-line, and polygon objects which together or in combination represent three-dimensional
features in your imagery. Features that are useful to delineate and store include rivers, roads, are
buildings, ridgelines, lakes, targets, and lot boundaries.
Road – represented
Buildings – Each is as a line feature
represented as a
polyhedron feature,
consisting of 6
polygonal elements: a
roof, four sides, and a
floor Lake – represented as a
polygon feature
Target – represented as a point feature
SOCET SET stores the position and shape of feature data in three-dimensional ground space
(latitude, longitude, and elevation) rather than image space. This allows you to accumulate
features from multiple images, spanning a large geographical area regardless of the imagery
source.
When delineating a feature in stereo, you control all three dimensions using the mouse (X,Y) and
the trackball (Z) while tracing the feature in the imagery.
SOCET SET Page 42-1

Chapter 42 - Feature Extraction
Features are categorized into six geometry types: (1) Point (antenna, water tower); (2)Text
(labels); (3)Line (creek, utility line); (4)Polygon (lake, lot boundary); (5)Multiline (streets,
highway); and (6) Polyhedron (building). The difference between polyhedron features and
polygon features are that polyhedron features can have more than one polygon and each polygon
can have its own attributes while polygon feature can have only one polygon. The same is true
for multi-line features and line features. Polyhedron and multi-line features are called complex
features while line and polygon are called primitive features. Point and text features are called
point features. You may combine/group complex features of the same type, but you cannot
combine/group primitive or point features. Every feature has a unique serial number, and belongs
to a user-definable class.
The content and format of the Feature Database is described in

another section of the manual. See “Feature Database and
Extraction Specification,” Appendix C for details.
Feature delineations consist of individually digitized points or continuous curves and arcs you
trace with the extraction cursor and trackball. The feature database is a 3D winged-edge
topological feature database. However, checking and enforcing 3D T o p o l o g y is only available
for polygon and polyhedron feature classes in the current version.
A feature may have one or more attributes, which are numerical or textual characteristics of the
feature such as composition, age, size, purpose, and usage. When supplying attributes for a
feature, you are guided by a user-definable set of rules called the Extraction Specification.
The features you extract are color-coded, symbolized and superimposed on the imagery in mono
or stereo for editing and for checking consistency with terrain. During Feature Extraction, you
can use a Digital Terrain Model (DTM) to provide continuous elevation tracking, as well as to
automatically intersect building sides with the ground surface.
42.1.1 When to Use Feature Extraction

You use Feature Extraction any time you want to extract V e c t o r D a t a from imagery. However,
you may review and edit feature data without imagery, if you wish.
Before running Feature Extraction you should have imported and controlled some imagery.
Although not required, it is usually best to prepare a DTM before Feature Extraction for two
reasons:
• The DTM can be used to determine the bottom of buildings.
• You can use the Terrain Tracking mode when extracting geomorphic features (that
is, the extraction cursor will automatically hug the ground while you are delineating
rivers and roads).
After you build a feature database, you can imbed the features in an image using Image Map, or
you can convert features and export them to another system in a format such as Shapefile.
42.1.1.1 Comparing Feature Extraction with Annotation

A n n o t a t i o n is similar to Feature Extraction, but is much less sophisticated. Both permit you to
draw lines, polygons, points, text strings, and icons; both tools store the data in three-dimensional
ground space coordinates; both tools store data in disk files for export or later editing; and both
tools use Sketch for editing operations such as translate, move point, rotate, or scale. The
Annotation chapter contains a more detailed discussion of the differences. The most significant
Page 42-2 SOCET SET

difference between Annotation and Feature Extraction is that Feature Extraction stores the
features in a database that supports attributing, querying, and database manipulating capabilities.
Feature Extraction stores control points for Arcs and Curves and has an Undo capability; whereas,
Annotation stores only the vertices of Arcs and Curves and does not have an Undo capability.
42.1.1.2 Creating Feature Databases

SOCET SET stores features in a feature database which resides in a sub-directory in the project
data directory. Each feature database uses its own sub-directory with the same name as the
database name. There are three ways to create a feature database:
• Interactively delineating features with Feature Extraction
• Importing a vector database with Feature Import
• Converting terrain graphics (contour lines, for instance) into features (See
“Converting Terrain Graphics to Feature Vectors” on page 36-5)
42.1.1.3 Using Feature Databases

You can use a feature database for many purposes. Some of the more common uses are:
• Building features (and other polyhedron features) for input to Perspective Scenes
and other rendering engines to generate photorealistic scenes.
• Exporting the feature database to a vector exchange format (such as Shapefile).
• Merging geomorphic features such as drains and ridgelines with DTM/Feature
Merge to modify a DTM to conform to the features
• Using a DTM during feature import to add elevation to 2D features
• Using the features as color overlay graphics in a hardcopy image made by Image
Map
42.1.1.4 Protecting Feature Database

The feature database can be used by only one user at a time; it is protected with a lock to avoid
two users from writing over each others work. If for some reason power is lost or a system crash
to your workstation while the database is open, it will be impossible to reopen the locked files
once power is restored. In this case, you will need to copy the feature database into a different
new feature database, than open that new feature database. The locked files can then be deleted.
SOCET SET Page 42-3

42.2 Feature Extraction

The Feature Extraction window’s selections are as follows:
File > Open FDB... Prompt you to select a feature database to open. To create a new database,
you enter the new name in the Selection field.
File > Save FDB Saves changes to the currently open feature database
File > Save FDB As Saves the currently open feature database to a new different feature
database with the same specification.
File > Save w/ New Spec Saves the currently open feature database to a different extraction
specification.
File > Reference Databases Displays the Select Reference Databases window. You use this window to
manage reference databases. You can add or remove reference databases.
You can enable or disable classes within a reference database. You can
toggle the ability to draw a reference database. You can toggle the ability
to snap to a reference database. You can toggle the ability to draw a
reference database using specified class colors, and you can select a solid
color for display of a reference databases. The Draw, Snap, and Spec
Colors toggles and the Solid Color button will affect all selected reference
databases.
File > Exit Exits Feature Extraction. This button is only valid during the REVIEW
mode. You must cancel any editing or creating operations before you can
exit.
Tools > Mensurate Displays the Mensuration window. You use this window to create detailed
measurements of a feature, relative to reference points you specify.
Tools > Volume Create For generating volumetric polyhedron features from polygon features. The
feature list file must have polygon entries. The output class must be
polyhedron. See “Volume Create” on page 42-22.
Tools > Texture Patch Opens Texture Patch window. See “Texture Patch” on page 42-24 for a
detailed description of this capability.
Page 42-4 SOCET SET

Tools > Model Placement Displays the Model Placement window. Use this tool to place multiple 3D
generic features into the feature database.
Tools > Auto Attribute Used to automatically calculate and populate the set of reserved
dimensional feature attributes (area, length, width, height, elevation, angle
of orientation, ACE, ALE, ZV2, ZV7, Z7F, Z5M, Z5F) upon feature
accept. Select Enable to activate this mode. All reserved dimensional
attributes (except for Angle of Orientation) will then be automatically
computed. The current feature class must have these reserved dimensional
attributes. Select Populate AOO to allow population of the Angle of
Orientation dimensional attribute. A second mouse click will be required
to calculate the AOO of a point feature.
Select Measure HGT/Zxx to measure 2 additional temporary points after

collecting a feature to calculate HGT and ZV2 or any of it's variants (ZV7,
Z7F, Z5F, Z5M). The first point should be on the ground and the second
point should be at the maximum elevation of the feature. HGT is calculated
from the second point minus the first and ZV2 from the second point. If the
feature is already collected at the appropriate height, and not at 'gutter
level', for example, the second sampled point will be ignored if it is at the
same elevation or below the first sampled point. In this case HGT is
calculated from the highest point of the feature minus the first extra
sampled point and ZV2 is the highest point of the feature. For point
features, if the AOO and the 'Measure HGT/Zxx' options are on, the first
extra point serves as both the ground measurement and the angle of
orientation calculation.
Tools > Simultaneous Allows you to delineate more than one features simultaneously.
Collection
Generics > Load Generic Load the generic feature database.
FDB
Generics > List Generic You use this to copy complex three-dimensional generic features (such as
Features spheres, cars, tanks, etc.) into the feature database.
Generics > Add to Generic Places a feature into the generic feature database for later use.
FDB
Options > Preferences Displays the preference window.
Options > Customize Displays the customize window.
SELECT TO
New Prompt you to open a new feature database.
SOCET SET Page 42-5

SELECT TO
Open FDB Prompt you to select a feature database to load. To create a new database,
enter the new name in the Selection field.
Save FDB Save currently open feature database.
Display Features Toggle to display features onto the image window.
Information Display the feature info such as the feature id number, number of elements,
element id number, and number of vertices.
Draw Draws the contents of the feature database and reference database.
Auto Draw Toggle to automatically draw the contents of the Feature Database and
Reference Database(s).
Feature Attribute Display the Feature and Elements Attributes window. You enter attribute
values for a feature, as defined by the extraction specification.
Graphic Attribute Display Graphics Attributes window. You set the color, line, or font of a
feature.
Retrieve/Manipulate Display Feature Retrieval window with Fence tool, Attribute Query tool.
Use this to list the features in the feature database by class, attribute, or
fence. All database manipulating tools are in this window.
Draw/Snap Class Prompts you to select a subset of class in the Feature Database for drawing
and snapping. The default is all the available classes.
Copy Attributes Copy the attributes of any feature in the current/reference feature database.
Hold the cursor over any feature in the current/reference feature database.
Press this icon. The feature will be highlighted, the Current Class will
automatically be updated to this feature’s class, and the attributes will be
copied to the Attribute window. Delineate the new feature, press Accept
Feature, and the attributes will be saved in the new feature.
Page 42-6 SOCET SET

SELECT TO
Current Class Prompt you to select the current feature class. To extract features, you must
select the desired feature class first.
DTM Prompt you to select a DTM which is useful for feature extraction.
Preferences... Display the preference window. You use set/select your preferences in the
<Ctrl>P preference window.
Class Geometry Text Box Indicate the geometry of the current feature class. Geometries are: POINT,
TEXT, LINE, POLYGON, MULTILINE or POLYHEDRON.
Class Name Text Box Indicate the current feature class name.
Polygon Topology Text Box Indicate if the current feature class supports polygon topology.
Back to Sketch
42.3 Polygon Topology

Polygon Topology is a simple and rapid way to delineate polygons that share edges. The shared
edges are only stored once in a topological SOCET SET feature database; this capability
minimizes the memory needed to store the feature database, and makes editing shared vertices
much easier.
42.3.1 Specification File

In order to enable polygon topology for a specific polygon/polyhedron class, you must set
Polygon Topology on using the Feature Specification Editor for that class.
42.3.2 Creation
There are four possible actions you may use to draw polygons in polygon topology:
• Sample Creation
• Splitting an existing topo_polygon
• Attaching to an existing topo_polygon
SOCET SET Page 42-7

• Drawing a Multiple edged topo_polygon
Simple Creation Splitting an existing topo_polygon
Drawing a Multiple edged topo_polygon

Attaching to an existing topo_polygon (F/E button on Sketch must be on)
If you are using a POLYHEDRON class, SIMPLE polygons (called “holes” or “inner rings”)
within other polygons are also allowed.
In drawing a multi-element feature, make sure the F/E button on Sketch is ON. For each edge you
draw, press the RMB. To accept the entire feature, double click the RMB after the last element is
drawn.
When you want to share edges with another polygon in the same class, it is recommended that
you use the snap capability, with sample ON. Be sure to check that you have the snap tolerance
and the snap mode (Vertex/Perpendicular) set appropriately.
It is possible to share edges without the snap capability. The software will automatically trim/
extend your lines so that they will touch the edge you are trying to share. If you use this trim/
extend capability, you must set the Extend/Trim Tolerance in the Sketch Preferences menu.
Any arcs/curves that are delineated will be automatically interpolated and these interpolated
points will be stored in the feature database.
42.3.2.1 Edit
Edit allows you to Move, Add, and Delete Vertex in general. You may not add/delete nodes,
which generally hold two polygons together.
You may Delete entire Features. Edges may not be deleted by themselves. The F/E button in
Sketch must be turned OFF to delete features.
When changes are made to an edge, all polygons that share that edge will be automatically
updated. If auto-dimensional attributes are on, the attributes will be updated for all polygons
affected.
42.3.2.2 Intersection Rules

During polygon topology, your actions are limited to the four cases shown above. Any other
actions are considered illegal. All intersections are considered on a 2-dimensional basis.
Intersections should only occur at the endpoints of your delineation. No polygons should intersect
except at shared edges. Error checking is performed for each action, and is on-the-fly. If illegal
actions occur, either during creation or editing, the software will not allow that change to the
Page 42-8 SOCET SET

feature database, and an error message will be sent to you. The topology of your feature database
will never be corrupted.
During Creation, if you make a mistake, such as you forget to set your Extend/Trim tolerance, or
you have an unintended intersection, and you press the Accept (RMB) button, the software will
detect your error, beep, and will tell you the problem. The software will also allow you to backup
vertex-by-vertex using the Sketch Undo button to fix the problem. Then you can press Accept
(RMB) again. If you decide that you want to start your delineation over again, simply press the
Escape key, and the feature will disappear, getting ready for your next delineation.
42.3.2.3 Creating a Multiple-edged Polygon

TIPS:
1. When the Sketch F/E button is on, you must click the RMB twice to accept the feature: once
for the element accept, and once for the entire feature accept.
2. In the Sketch Snap Preferences, turn the Sample button on, and the Insert Vertex button off.
3. In the Sketch Extend/Intersect Preferences, change the Extend/Trim tolerance to suit you,
if you are going to take advantage of the extend/trim capability of Polygon Topology.
Start:
MMB for MMB for Snap,
Snap RMB to accept edge
B
LMB
A
MMB for Snap

End: MMB for Snap,
RMB twice for accept edge and feature.
New polygon with shared edges
In this Figure, Polygons A and B are pre-existing polygons.
42.3.2.4 Example
1. Draw a simple polygon A, by pressing the LMB to delineate points of the polygon, and
pressing the RMB to close and accept the polygon.
2. Draw another simple polygon B by repeating the steps above.
3. To create a new polygon that connects the two simple polygons you have just created, turn
the F/E button on.
4. Snap to the first feature with the MMB, delineate some points with the LMB, and snap to
the second feature with the MMB. Press the RMB once to accept the edge.
5. Again, snap to the first feature with the MMB, delineate some points with the LMB, and
snap to the second feature with the MMB. Press the RMB once to accept the edge. Press the
RMB again to accept the entire feature.
SOCET SET Page 42-9

42.4 Feature Classes

You use the Feature Classes window to set the class of the feature you want to delineate. All
classes defined in the current feature database are listed. See “Classes” on page C-2 for
information about feature classes. To display this window, click Current Class on the Feature
Extraction window.
To exit this window, click Close.
42.5 Draw/Snap Classes

You use, click Draw/Snap Classes... on FE window. Select a subset of classes in the Feature
Database for drawing and snapping. The default is all the available classes. You should select
only the classes that you want to draw and snap to. This also speeds up feature drawing.

42.6 Feature Information

The (feature) information window displays the current edit feature information. To display this
window, click Information icon on the Feature Extraction window. The window displays the
feature information such as the feature ID number, number of elements, element ID number, and
number of vertices.
To exit this window, click Close.
42.7 Feature and Element Attributes

The Feature and Element Attributes window consists of editable fields which define the current
feature attributes. To display this window, click (Feature Attributes) on the Feature
Extraction window. This window displays the attributes for the current feature’s class according
to the definitions in the extraction specification. Attribute ranges and defaults are also defined in
the extraction specification. If you enter an out of range attribute value, an error indication is
given and the attribute’s improper value is replaced with an in range value when you accept the
feature. The Feature ID and Element ID are not attributes and you can not edit them.

The Feature and Element Attributes window’s selections are as follows:
SELECT TO
Vertical Header Toggle If you do not want to display certain attributes, you can set the vertical
header toggle of each row on the left to ON and then press the Mask
button. This will hide the attributes you have checked.
Mask Mask or hide checked attributes. Once an attribute is masked, that attribute
will not show up in this window anymore for all features of the same
feature class.
Unmask Unmask or show all attributes.
Set All Instead of setting/checking the attribute ON one at a time, you use this
button to set/check all of them.
Apply to All Elements1 Apply a set of element attributes to all the elements within the same
feature. shade_flag and shade_value are two reserved element attributes
and they are not applicable to “Apply To All Elements”.
Unset All Unset/un-check all the attributes.
Close Close the Feature and Element Attributes window.
1. Element portion and the “Apply to All Element” button only displays if the class is of a
complex geometry type (polyhedron and multiline) and there are element attributes.
There are two ways to update attributes: (1) from this window, update attributes one by one; and
(2) from Feature Retrieval window, update attributes for a list of features. The list of features for
method 2 can be generated by Attribute Query and Fence. When using method 2 to update a
subset of feature attributes and element attributes, you use the vertical header toggle on the left
of each attribute to indicate which attribute you want to update. ON indicates this attribute will
be updated and OFF indicates this attribute will not be updated.
42.8 Graphics Attributes

Normally, you specify the graphical attributes of features according to their class in the
Extraction Specification. However, you can override certain graphical attributes of an individual
feature with the Graphics Attributes window, by clicking the Graphic Attributes icon on the
Feature Extraction window. Graphic attributes are stored per feature in SOCET SET. Font
attributes (Size, Type, and Style) are applicable only to TEXT features. Width, Style, Icon, and
Icon Spacing are not applicable to POINT or TEXT features.

The Graphics Attributes window’s selections are as follows:
SELECT TO
Line BLANK SPACE

Color Set the foreground color of a feature. You can set the foreground
BLANK SPACE color of a feature by picking the feature, setting the foreground
BLANK SPACE color, and then accepting the feature.
Width Select width, in pixels, that the lines of the feature will be drawn in.
Style Specify whether to draw the lines as solid or dashed.
Fill BLANK SPACE

Color Set the color of the fill, where applicable. The default is Transparent.
Font BLANK SPACE
Size Select text font size option.
Type Select text font family name.
Style Select text font style option.
NOTE: The text font sizes, types, and styles available to you
depend on your system configuration.

SELECT TO
Close Complete changes and close window.
See “How to Change the Fonts” on page D-3 for more information on how to configure text
fonts.
42.8.1 Copy Attributes

This allows you to copy the attributes of any feature in the current or Reference Feature Database.
This is immensely helpful for those of you who have broken up your feature delineation task into
parts, have feature database already done, and are continuing with a feature database adjacent to
the finished one.
42.8.2 Example
In a feature database A, there is Road1 that you need to continue delineating in a feature database
B. The steps would be as follows:
1. Move the Extraction Cursor to Road1.
2. Press Copy Attributes icon on the Feature Extraction window. This will highlight the
feature and set the Current Class to Road, and will automatically copy the attributes of
Road1 into the current feature that you are delineating.
3. [optional] Snap to the end of Road1, and delineate Road2.
4. Accept Road2 by pressing the RMB.
42.9 Retrieve/Manipulate - Feature Retrieval

To display this window, click Retrieve / Manipulate icon on the Feature Extraction window. You
can pick a feature in two ways: by pointing at the feature with the extraction cursor and picking
the feature with Sketch, or by selecting the feature from Feature List in the Feature Retrieval

window. You can filter the Feature List to show only a subset of the available features.The
Feature Retrieval window’s selections are as follows:
SELECT TO
Fence Options Display Fence Options.
Draw Fence Draw a fence polygon to select a list of features.
Attribute Query Display the Attribute Query window. You use the attribute query to select
features based on their attribute values.
Validate Attributes Display the Attribute Validation Report window. You use the report to
view violated attribute constraints for the displayed features.
Move To Feature Move the extraction cursor to the selected feature from the Feature List,
pick it for editing, and put Sketch into EDIT mode.
Move To Previous Move the extraction cursor to the feature above the selected feature from
the Feature List, pick it for editing, and put Sketch into EDIT mode.
Move To Next Move the extraction cursor to the next feature of the selected feature from
the Feature List, pick it for editing, and put Sketch into EDIT mode.

SELECT TO
Apply Action Apply the action specified in the Action Option to the Feature List. The
Action Option will not take place until you click Apply Action.
Apply Action Highlights Apply the action specified in the Action Option to the selected feature.
This Option will not take place until you click Apply Action Highlights.
Split Features Draw a fence. If the fence intersects a feature, the feature will be split
where the fence crosses it. New split features will be inserted into the
current feature database.
Intersect-Nodes Find the intersection points between the line and multiline features.
If an XY intersection occurs and the z-value difference between the
intersection points is greater than intersection z tolerance, there will be two
intersection points, one per feature, each one retaining its unique z-value.
These intersection points will be inserted as vertices into line/multiline
features.
BLANK SPACE
If the z-value difference is less than intersection z tolerance, there will be
one intersection point and its z-value will be derived from both features
with a weighted xy distance function. If the intersection point was found in
a line feature, the original line feature will be split according to its
intersection points. The intersection z tolerances are selected in the Sketch
Preferences window under Extend/Trim. If the intersection point was
found in a multiline feature element, the multiline feature element will be
split into several elements according to the intersection points.
BLANK SPACE
If there is a class called NODE in the specification file with geometry type
GEOM_POINT and attributes string FIDZ, the software will add the actual
intersection points to the feature database. FIDZ is a string in the format:
Feature ID:Z-value; Feature ID:Z-value.... The string consists of the IDs of
the Features that are connected to this node. The Z-value is the z-value of
the intersection point at the feature with the given feature ID. If deleting
one of the features whose ID is recorded in the FIDZ field, you should
update the FIDZ field of the node.
Trim/Extend Trim the features by checking the first and last segments of each line/
multiline element to see if the segments cross another line/multiline
feature in XY by < trim_tolerance. If this occurs and the z-value difference
between the two features at the intersection points is
< z-tolerance, that part of the end segment will be cut off.
Extend will extend a feature to touch another if it only needs to be
extended by < trim_tolerance and the z-value difference at the intersection
points is < z-tolerance. The Extend/Trim Tolerance and Intersection z
tolerance are selected in the Sketch Preference window.

SELECT TO
Change Class Change from one class (the from class) into another class (the to class).
Change features which are compatible to current class. Features which are
not compatible with current class will not be changed. Compatibility is
guided by the following rules:
TEXT <==> POINT
POLYGON <==> POLYHEDRON
LINE <==> MULTILINE
POLYHEDRON ==> LINE
POLYHEDRON ==>MULTILINE
POLYHEDRON ==>POINT
POLYGON ==> LINE
POLYGON ==>MULTILINE
POLYGON ==>POINT
LINE ==> POINT
MULTILINE ==> POINT
NOTE: When changing to POINT, the center point and lowest
elevation are used.
The from classes are the classes of features in the Feature List. Attributes
which do not match the current class attributes will get lost.
Create Group Create a group or combine features, the element attributes are retained in
the new feature. The feature attributes will be taken from the first feature
used during the combination process. Generally you will want to update
the feature attributes to reflect the characteristics of the new combined
feature. This operation is only applicable to complex feature.
NOTE: Once a group of features are combined, the new feature
cannot be reverted to the original component.
Apply Attribute Update graphic attributes, feature attributes and element attributes of all
features in the Feature List and belonging to the current class. You use
Feature and Element Attributes window to set the desired values. If you do
not want to update certain attributes, you toggle off that attribute. Apply
Attribute will only update attributes with the toggle On.
Draw Redraw the features displayed in the Features list.
Save Feature List Save the features into a file such that Volume Create and Model Placement
can use as input.
Source List BLANK SPACE
All List all available features from the current open feature database.
Class List all features in the current class.
Attribute List features selected by using Attribute Query.
Fence List features selected by Fence.

SELECT TO
Action BLANK SPACE

Copy Copy all features listed in the Feature Retrieval Feature List into another
BLANK SPACE feature database.
Copy w/ Clip Copy all features listed in the Feature Retrieval Feature List into another
BLANK SPACE feature database. You should draw a fence. If the fence intersects the
feature, the feature will be cut where the fence crosses it.
BLANK SPACE
BLANK SPACE
Delete
Delete all features listed in the Feature Retrieval Feature List.
BLANK SPACE
BLANK SPACE
BLANK SPACE
Delete all features listed in the Feature Retrieval Feature List. You should
Delete w/ Clip draw a fence. If the fence intersects the feature, the feature will be cut
BLANK SPACE where the fence crosses it.
Move Copy all features listed in the Feature Retrieval Feature List into another
BLANK SPACE feature database and then delete them from the current open feature
BLANK SPACE database.
Move w/ Clip Copy all features listed in the Feature Retrieval Feature List into another
feature database and then delete them from the current open feature
database. You should draw a fence. If the fence intersects the feature, the
feature will be cut where the fence crosses it.
Close Exit Feature Retrieval window.

42.9.1 Drawing Fence Polygon to Select Features

After you click Draw in the Fence section on the Feature Retrieval window, you will use the LMB
to draw a fence polygon with the extraction cursor.
To draw a fence polygon, press the LMB to denote the vertices of the fence polygon, and press
the RMB to accept the fence polygon. Then, it re-draws and highlights all the features that are
determined by the fence polygon and the topological operators.
The Fence tool is

restricted to clipping
only one section of
a polygon at a time.
Fence
42.10 Attribute Query

You use the Attribute Query window to select a subset of the features in the feature database. To
display this window, click Attribute Query icon on the Feature Retrieval window.
The scope of a query is limited to a single feature class. You must pick the class first. A query
consists of one or more tests of attribute values. You can link more than one test through the use
of logical AND and OR operators. A test consists of an attribute, a comparison operator, and a
value. You can use parentheses to build a complex query.
The Attribute Query window’s selections are as follows:
(File) Load Query Prompt you to load a query from a file.

(File) Save Query Prompt you to save the current query into a file for later use.

SELECT TO
Feature Class Display the name of the current feature class to query. Click the
(ellipse tool button) on the right of the field.
All Set your query to include all the features of the given class.
Attribute (button) Prompt you to pick an attribute to test.
Attribute (field) Display the name of the attribute to test.
() Add parentheses to use when building a complex query.
==, !=, >, <, >=, <= Add comparison operators.
Value View the value against which the attribute value will be compared. You
enter this value. If the attribute is an enumerated list, use the Enumerated
button to pick a value from the list of possible enumerated values.
Enumerated Prompt you to pick an enumerated value.
AND, OR Add logical AND and OR operators to use when building a complex query.
UNDO Undo the last part of the query.
Query Display the query you are constructing.
Execute Query Apply your query to the feature database, and opens the Matching Feature
window to display four operations you may apply. The matched features
are displayed in the Feature Retrieval window.
Clear All Query Remove all selected features by all previous queries in the Feature
Retrieval window.
Clear Last Query Remove selected features by the last query in the Feature Retrieval
window.
Close Close the Attribute Query window.
42.11 Attribute Validation Report

You use the Attribute Validation Report to view all constraint violations for the displayed
features. To display this window, click Validate Attributes icon on the Feature Retrieval window.
The report will show a row for each violation of the constraints that were set up in the
Specification Editor. The feature id, class, attribute, value, expected value, and the constraint on
the attribute is displayed for each violation.

The Attribute Validation Report window’s selections are as follows:
Validate Run the validation report.

42.12 Mensuration
You use the Mensuration window to print a wire-frame model of a feature and a text report of the
mensuration data (such as length of each side) for that feature. To display this window, click
Tools > Mensuration on the Feature Extraction window.
The Mensuration window’s selections are as follows:
SELECT TO
Output Filename Name the output report file (.rep).

Reference Point Display the primary three-dimensional coordinate from which all
measurements are made. You can enter this manually, or click the Sample
Reference Point to use the current extraction cursor coordinates.
Secondary Point Display secondary reference point from which all measurements are made.
Sample Reference Point Load the current extraction cursor coordinates into the Reference Point
field.
Sample Secondary Point Load the current extraction cursor coordinates into the Secondary Point
field.
Annotate Feature Draw indices onto the vertices of the currently selected feature.
Edit Text Report Bring up the mensuration report in the Report Editor window so that you
can review it and annotate it further, if you wish.
Auto Draw Current Feature Toggle On/Off to automatically draw the current feature.
Done Close the Mensuration window.

42.12.1 Execution - Mensuration

1. Use Feature Extraction to create a feature database of the features you wish to measure.
2. Load your feature database into Feature Extraction, and draw it by clicking Draw.
3. [Optional] Load the GRAPHICS_ONLY.sup image file on the main image display. You
can use this pseudo-image to adjust the angle and magnification with which you view the
features. See “Graphics Projection” on page 61-37 for details.
4. Pop-up the Mensuration window by clicking Tools > Mensuration on the Feature
Extraction window.
5. Select the feature you want to measure. There are two ways to do this:
a. Pick the feature in the Feature Retrieval window and move to the feature by clicking
Move To Feature.
b. Use the Sketch Select operation to highlight the feature.
6. [Optional] Edit the Output Filename field. This specifies the name of your output report.
7. [Optional] Enter the primary reference point coordinates into the Reference Point fields.
You can sample the current extraction cursor coordinates by clicking Sample Reference
Point.
8. [Optional] Enter the secondary reference point coordinates into the Secondary Point fields.
You can digitize the current extraction cursor coordinates by clicking Sample Secondary
Point.
9. [Optional] Click Annotate Feature to number the vertices of your feature.
10. [Optional] Click Edit Text Report to view and annotate the text report.
11. [Repeat steps 5 - 10] for each feature you wish to measure.
42.12.2 Volume Create

You use Volume Create to build three-dimensional features either manually, or from features that
are imported from another system. As an example, an ARC/INFO or other GIS database may
contain Building features, but they are only two-dimensional polygons represented at ground
level. The Volume Create tool converts them into three-dimensional features with height, and
therefore volume/polyhedron. Click Tools > Volume Create on the Feature Extraction window to
start Volume Create. To view the options available, click Options on the Volume Create window.

The Volume Create window’s selections are as follows:
SELECT TO
Output Feature Database Prompt you to enter or pick a name for the output feature database. The
edit feature database specification file is used for the new Output Feature
Database if it is a new one. If you want a different specification file, you
must select an existing feature database other than the edit feature
database. You can create an empty FDB with the specification file you
desire before you use this tool.
Feature List Prompt you to enter or pick a filename for the feature list file (.fls).
You must make sure the list file is generated from the current edit feature
database. Entries in the list file must be polygon features.
Feature Class Prompt you to pick a feature class to output. Attributes conversions
follows the following rules. Attribute name must be identical. Attribute
type must be identical/compatible. Attribute order does not matter. Non-
compatible attributes are not converted. STRING is only compatible to
STRING. Other types are compatible to all other types
Height Attribute Prompt you to pick a height attribute for the feature class, if the feature
class has one. This attribute must be of type numeric such as INTEGER,
FLOAT, or DOUBLE.
Options Bring up the Volume Create Options window.
Start Start the volume generation calculation.
Close Close the Volume Create window.
42.12.3 Options
To view the options available, click Options on the Volume Create window.

The Options window’s selections are as follows:
SELECT TO
(High Source) Different methods of determining how to set the height of the three-
DTM, Attribute, Manual dimensional volume feature.
Entry
(Feature Growth) Specifies what direction to add the sides of the feature in.
Up / Down from Polygon.
(Manual Entry) Specifies whether you want to be prompted for the height of each feature,
Once, Each Feature or if you want to apply the height to all features.
(Height Units) Units of the volume height you enter.

Meters, Feet
Close Closes the volume creation Options window.
42.13 Texture Patch

When you use Perspective Scenes or other rendering applications, the scene may look unrealistic
if the imaginary viewer is looking at building sides that are not visible in the input images. These
hidden building sides will either have a streaked appearance (if they were partially visible in the
original image), or will be shaded a solid gray color (if they were not visible at all in the original
image).
Texture patches of color imagery do not display correctly on

the console monitor with Feature Extraction.
If you want to create a more realistic scene, you can attach an artificial image patch (called a
texture patch) to the hidden building sides. You can also attach textures to visible building sides,
for example, to put a better facade on a building side that would otherwise be draped with poor
resolution imagery. You use Texture Patch in Feature Extraction to attach texture patches.
The optimal way to use Texture Patch is to build a repository of patches that you can re-use over
and over again, by storing texture patches in the common texture database
(<install_path>/internal_dbs/GENERIC_DBS/Texture). You can also store
textures within your individual project. There is only one specification file for texture patch
feature database. The file is always in $(DBDIR)/SPECS/texture.spc. For every texture patch
image, there must be a FEATURE_NAME (length 32) associated with it. This is useful such that
you can identify which patch image should be used. The FEATURE_NAME should be
meaningful such as brick, window, door, etc. In normal case, you should not modify the
texture.spc file.
The texture feature database can be in either the project data directory or the $(DBDIR)/
GENERIC_DBS directory. The texture feature database always have the name “texture”.
Therefore, this name is reserved only for texture feature database. In other words, you should not
have any other feature databases with this name. Press the middle mouse button to abort digitizing

an image point; the already digitized points for that element will not be recorded. Instead, you
need to digitize from the first point again. The TEXTURE geometry type must be POLYGON.
Texture Patch captures textures at the resolution of the image

you are capturing from.
This section describes how to create texture patches and how to attach them to a facade (i.e.
building side). To obtain this window, click Tools > Texture Patch on the Feature Extraction
window.
The Texture Patch window’s choices are as follows:
File > Delete Patch Deletes a previously saved texture reference window.
File > Close Closes the Texture Patch window.
Options > Working Dir Select either Project or Internal DB.
Options > Image Select either left or right image to create texture patch.
SELECT TO
Create Define and save a texture patch (an area in the currently displayed image
from which texture patches may be digitized).
Load Display an existing texture patch for sampling.
Apply Start sampling in the texture patch window.
42.13.1 Executions
42.13.1.1 Working with Texture Patches
1. [Optional] Copy the default SOCET SET texture patch database from the internal_dbs
directory to your project directory called “myproj”.
2. To view or remove patches from Feature Extraction:

a. Click Tools > Texture Patch on the Feature Extraction window.

b. Click Load on the Texture Patch window to view patches.
c. Click File > Delete Patch... to remove patches.
d. Click File > Close to exit the texture patch window.
3. To change texture patch attributes from Feature Extraction:
a. Click Feature Database, select the file named “texture”, and click OK.
b. Click Retrieve / Manipulate... to view the Feature List. Select the patch to be changed.
c. Click Feature Attributes to view the feature attributes. The file_name string attribute
may be edited to a new path for a different patch (.pat) file. The FEATURE_NAME
string attribute may be changed to a new name to be viewed in the texture patch list
in step 2.
d. Click File > Save FDB to save changes to disk.
42.13.1.2 Creating a Texture Patch

1. Load the project that contains the imagery you wish to capture.
2. Set the minification of the image to the resolution you wish to capture.
3. Click Extraction > Feature > Feature Extraction on the workstation window.
4. Click Tools > Texture Patch on the Feature Extraction window.
5. Load the image you wish to capture from on one of the workstation monitors.
6. Select File > Options > Working Dir > Project (or Internal DB) on the Texture Patch
window.
7. Select File > Options > Image > Left (or Right) image to extract the patch from.
8. Click the Create button and then toggle to the extraction cursor and digitize at least three
points with the LMB to delineate a polygon which defines the area of the texture patch.
Press the RMB to accept and close the polygon.
9. Texture Patch prompts you for the name of the patch file. Enter the name and click OK.
10. Texture Patch extracts the area defined by the minimum bounding rectangle of your
polygon, and displays the patch.
11. [Repeat steps 6–10] to continue gathering additional texture patches.
12. Click File > Close on the Texture Patch window.
42.13.1.3 Applying a Texture Patch

1. Using the extraction cursor, select the element of the feature you wish to apply a texture
patch. The Element Edit icon (F/E) in Sketch must be on. When selecting, put the extraction
cursor in the middle of the element.
2. If the complex feature has more than one elements, use Next Element to cycle through each
element of the feature until the element you wish to apply the patch to is highlighted.
3. Click Tools > Texture Patch on the Feature Extraction window to display the Texture Patch
window.
4. Select File > Options > Working Dir > Project (or Internal DB) on Texture Patch window.
5. Click the Load button and select the name of your texture in the Texture Retrieval window
scrolling list to display a texture reference window.
6. Click the Apply button and begin sampling reference points with the LMB in the texture
patch window.
Each reference point will correspond to the current location of the extraction cursor in the
main display window. Each time a reference point is entered, the extraction cursor moves

to the next corner of the feature surface to which the patch will be applied. Continue
entering reference points, defining an area in the texture reference window which roughly
corresponds to the shape of the feature surface, until all corners of the feature surface are
referenced. For example, if you are sampling a texture patch for a rectangular surface, you
will enter four reference points in the texture reference window.
7. If you wish to assign a patch to another element, use Next Element to cycle to the element
you wish to assign the patch to, then repeat steps 5–7. You do not need to repeat step 5 if
you wish to assign the same patch to the new element.
8. After you define and reference a texture patch feature surface, it is written to the feature
database.
9. Save your changes by clicking File > Save FDB on the Feature Extraction window.
Texture patches are not displayed in Feature Extraction. They are only displayed in the output
image when patched feature databases are included in the Scene Content Selection phase of
Perspective Scenes and other rendering applications.
42.14 Model Placement

You can use the Model Placement tool to generate a large number of features in one step, either
within a polygon or along a line. You can distribute the features at a regular spacing or randomly.
This tool is most commonly used to create forests, groves, orchards, and lines of lamp posts. To
open this window, click Tools > Model Placement on the Feature Extraction window.
Given a polygon outlining a forest, you can use Model Placement to automatically create tree
features inside the polygon. You can specify the number of trees, and you can specify whether
the spacing of them inside the forest polygon is regular or random.
You can dot a street feature (a LINE geometry) with lampposts using Model Placement. After
defining the lamppost you can specify either regular or random spacing for the lights along the
street.
A single copy of the feature you are going to place must already be defined in the Generic Feature
Database before you run the Model Placement tool.
Model Placement also provides for positioning its features along the terrain using values from a
DTM.

The Model Placement window’s selections are as follows:
SELECT TO
List File Prompt you to pick the name of a feature list file (.fls) which is
generated by Attribute Query.
Selected Generics Prompt you to pick a three-dimensional generic feature type.
Mode Select Random or Constant—controls the spacing of the placement of the
features.
Spacing Adjust the spacing.
If the Mode is set to Constant, this is the fixed spacing between features in
project units.
If the Mode is set to Random, the Spacing is used to compute the number
of features which are then placed randomly.
Height Min & Max Identify the minimum and maximum height that will be applied to a
feature. This value is only applicable to 3D generic features.
Width Min & Max Identify the minimum and maximum width that will be applied to a
Length Min & Max Identify the minimum and maximum length that will be applied to a
Orientation (deg) Select orientation of the features (in degrees).
Generate Start generating the features.
Use DTM Toggle whether model placement will use the elevations from a selected
DTM or from the first vertex of the fill polygon.
Sel DTM Prompt you to select a DTM.
Close Close the Model Placement window.
42.14.1 Execution - Model Placement

The execution steps are:
1. Delineate either a LINE feature to place your generics along or a POLYGON feature to
place your generics within.
2. Load the generic feature database by clicking Generics > Load Generic FDB on the
Feature Extraction window.
3. Bring up the Model Placement window by clicking Tools > Model Placement on the
Feature Extraction window.
4. Pick the feature that you want to fill. For example, if you are going to create a forest, pick
the polygon that represents the forest boundary. For constant spacing, the direction of the
rows will be defined by the direction of the first vector of the polygon that represents the
fill boundary. If you pick a line feature, the generics will be placed along the line.
5. Alternatively, you can select a list of features to fill by clicking List File button and picking
a feature list file which is generated by Attribute Query.
6. You must set the Current Class to the class you are going to place features into and that
class must have the same geometry as the 3D generic feature geometry.
7. Click Selected Generic. In the dialogue box, pick the generic feature to place.
8. [Optional] Pick the Mode for distributing the features: either Random or Constant.

9. [Optional] Enter a spacing.

10. [Optional] Enter a minimum and maximum height, width, and/or length as needed for your
generics.
11. Click Generate to place the features. If you selected a feature list file in step 5, you will
need to click Generate for each of the features in the feature list file.
12. Repeat steps 4 through 11 for each polygon or line or series of polygons or lines you want
to fill. Save your changes by clicking File > Save FDB on the Feature Extraction window.
42.15 Automated Population of Attributes
42.15.1 Non-Dimensional Attributes

This tool is used to automatically calculate and populate a set of reserved non-dimensional feature
attributes upon feature accept (from either create or edit). These non-dimensional attributes
include the left and right support file that was used to last create/edit the feature, and the average
circular and linear error of the feature. In order to compute the average circular and linear errors,
you must have one of the following data file: (1)Covariance file (Run Triangulation); (2) Master
Product file (DPPDB); (3) Sigma file; (4) ATF file.
A set of reserved attribute names have been set aside for the dimensional attributes. All
geometries are supported. In addition, these attributes must be FEATURE attributes. Listed
below are the non-dimensional attributes along with their corresponding reserved feature
attribute names.
NON-
ATTRIBUTE
DIMENSIONAL DESCRIPTION
NAME
ATTRIBUTE
Left Support File SUPP_L The last left support file that was used in the creation/edit of
the feature. (STRING type of length 256)
Right Support File SUPP_R The last right support file that was used in the creation/edit of
the feature. (STRING type of length 256)
Average Circular ACE The average circular error of the feature. (FLOAT, or DOUBLE
Error type, 90% probability level)
Average Linear Error ALE The average linear error of the feature. (FLOAT, or DOUBLE
type, 90% probability level)
42.15.2 Dimensional Attributes

This tool is used to automatically calculate and populate a set of reserved dimensional feature
attributes upon feature accept (from either create or edit). These dimensional attributes are
calculated from the feature delineation and include area, length, width, height, elevation, and
angle of orientation. In the feature extraction specification file, you will indicate which of these
dimensional attributes will be used and in which feature classes these dimensional attributes will
be used.
A set of reserved attribute names have been set aside for the dimensional attributes. Only the
attribute names are reserved; as with all other feature attributes, you are free to select the attribute
type (int, float, double), minimum and maximum value, and default value. Primitive feature class
geometries (point, line, polygon) and single element complex features are supported. Listed

below are the dimensional attributes along with their corresponding reserved feature attribute
names.
DIMENSIONAL ATTRIBUTE
DESCRIPTION
ATTRIBUTE NAME(S)
Area ARA Area of the feature. In Polygon Topology, any complex feature
with inner rings will have the area of only the outer ring. The
area shown does not include the area contained in the inner
rings.
Perimeter PERIMETER Perimeter of feature. In Polygon Topology, any complex
feature with inner rings will have a perimeter equal to the sum
of the perimeters of the inner rings and the perimeter of the
outer ring.
LEN_BFR Length of Best Fitting Rectangle (BFR) of minimal area around
the feature. (LINE and POLYGON features) BFR works best
on those objects where a rectangle truly portrays the basic
shape of a feature.
LEN_CTL Length along center line of feature. (LINE and POLYGON
features) CTL works best on area features like roads, rivers,
ditches, etc. where a rectangle would be a grossly inaccurate
portrayal of the object.
Width WID_BFR Width of Best Fitting Rectangle (BFR) of minimal area around
the feature. (LINE and POLYGON features) BFR works best
on those objects where a rectangle truly portrays the basic
shape of a feature.
WID_ARA Width based on feature area. (POLYGON features) ARA works
best on area features like roads, rivers, ditches, etc. where a
rectangle would be a grossly inaccurate portrayal of the object.
NOTE: Features that use WID_ARA should not contain
“branches” or “forks”, instead WID_BFR should be
used.
Z-Elevation ZV2 Maximum Z-elevation (above sea level) of the feature.

BLANK SPACE (POINT, LINE, and POLYGON features)
Z5F Ellipsoid height in feet. (POINT, LINE, & POLYGON features)
Z5M Ellipsoid height in meters. (POINT, LINE, & POLYGON
BLANK SPACE features)
Z7F Maximum elevation in feet of the feature above the ellipsoid
(sea-level). (POINT, LINE, & POLYGON features)
BLANK SPACE
BLANK SPACE
BLANK SPACE
Maximum elevation in meters of the feature above the ellipsoid
ZV7 (sea-level). (POINT, LINE, & POLYGON features)
Height HGT Maximum Z-height of the feature above the terrain (DTM).
(POINT, LINE, and POLYGON features)
Angle of Orientation AOO Angle of orientation measured clockwise from North in degrees
(0 to 360). (POINT features)

For angle of orientation (AOO) only, you will need to digitize an

additional ground point in order to properly calculate the
angle. A DTM will also be required to populate height (HGT).
You will not be required to enter additional inputs for any of the
other dimensional attributes.
42.15.3 Execution - Auto Attribute

1. Prepare an extraction specification file and ensure that the desired feature classes contain
any of the prescribed dimensional attributes.
2. Click Tools > Auto Attribute > Enable on the Feature Extraction window, to activate this
mode.
3. [Optional] Click Tools > Auto Attribute > Populate AOO to allow automated population
of the angle of orientation attribute (you will later be required to digitize an additional
ground point apart from the actual point feature).
4. [Optional] Click DTM icon on the Feature Extraction window. Optimally, the DTM should
cover the area of feature collection.
5. Click Current Class icon on the Feature Extraction window to select a feature class. Only
POINT, LINE, and POLYGON Class Geometries are supported.
6. Delineate a feature using the left mouse button and accept it with the right mouse button.
Alternatively, pick an existing feature, edit the feature, and accept it with the right mouse
button. The appropriate attributes should automatically be calculated and populated for the
feature in the feature database.
7. [Optional] If Populate AOO was selected and you digitized a point feature with the AOO
attribute, you will be prompted to digitize an additional ground point to calculate the angle
of orientation. The cursor will change to a red “bull’s-eye”, at which point you should use
the left mouse button to digitize the additional point.
8. Repeat steps 5 through 7 for additional features.
42.15.4 Batch Processing - Automatically Populate Dimensional

Attributes
See “Batch Processing - A Feature Database” on page 42-43 for details.
42.16 Simultaneous Collection

This tool allows you to delineate more than one features simultaneously.

In order to invoke this tool, open FDB, select current class and click Tools > Simultaneous
Collection in the Feature Extraction window. The Secondary Feature Classes window handles a
table of secondary features. At any time while extracting the vertices of the primary feature, it
will be possible to add up to 10 secondary features into the table and collect points for them
concurrently. To add a new secondary feature click in the table area (white area), but not on a row
in the table with the right mouse button, then click Add on the pop up. Click Close to close the
window.

42.16.1 Secondary Feature Classes

Select with left mouse button and click OK (or double click on the selected class) to select a class
and close the window.
After class selection, the class name and geometry will populate appropriate row in the table and
will identify the feature in the “Simultaneous Collection” table. At any time it is possible to add
a new feature, remove one or all secondary feature(s) and view/edit feature attributes. You have
to select the row and click in the Class Name or Class Geometry cell with the right mouse button,
then select the applicable option from the pop up. You may make graphics attributes depend on
enumerated feature attributes by clicking the right mouse button on an enumerated feature
attribute field, and making the Graphics Attribute “Dependent”. This means that if you collect the
first feature of the class “DRAIN”, and set the attribute value to “DITCH” and the color to
“BROWN”, all subsequent features in that class with that same attribute value “DITCH will have
that same color “BROWN” automatically. If the graphics attribute is “Dependent”, the algorithm
will search for the first feature in the Feature List that has the given attribute value, and will
assign it the color of that feature.
The Simultaneous Collection table will display available classes, according to the following
Geometry Dependency table.
PRIMARY FEATURE SECONDARY FEATURE

GEOMETRY GEOMETRY
Text or Point Point

Line Point, Line
Polygon Point, Line, Polygon
Multiline Point, Line
Polyhedron Point, Line, Polygon

42.16.2 Secondary Feature Creation

Secondary feature must be a primitive feature (excluding TEXT), that is POINT, LINE or
POLYGON.
While extracting a complex primary feature, the secondary feature is related to its element.
During primary feature extraction, all changes to the primary feature will affect the secondary
feature (e.g. deleting a vertex of a primary feature will delete the same vertex of the secondary
one)
In order to start a secondary feature collection, select the feature in the table and click Start with
right mouse button (on it’s “Extraction” cell). The status will be changed to ON. For a POINT
secondary feature, the first sample following setting the extraction status to ON, will
automatically accept the feature and turn it’s extraction status to OFF. For LINE and POLYGON
secondary features simultaneous collection will take place until either the secondary feature is
accepted in the GUI or the current primary feature (or element in case of complex feature) is
accepted on Sketch. To accept a secondary feature click in the Extraction cell with the right
mouse button then select Accept. Similarly, you can cancel a secondary features collection by
selecting Cancel. In case the primary feature (or element) is accepted, all the secondary LINE and
POYGON features that are ON, will be accepted automatically.
When Current Class or Feature Database in FEI application is

changed, the Secondary Features table will be re-set.

42.17 Generic Features

You use Generic Features when you want to create many instances of a feature with the same
shape, for example, if you want to create dozens of trees. The template or model feature is called
the generic feature. All generic features are stored in a special database called the Generic
Database. To instantiate a generic feature, you must open a generic database (in addition to the
database you are populating) and copy a feature from the generic database to the feature database
being populated.
The types of generic features that the software use are three-dimensional generic features which
are volume features such as buildings and water tanks. When you instantiate a generic feature,
you specify its location, size and orientation. 3D generic features usually are FML_POINT class
POLYHEDRON geometry.
The reasons of having 3D generic features are for the case that there are certain types of features
which have identical shape of geometry, but their actual size, orientation, and location are
different. To speed up feature extraction process, you can place the 3D generic features to the
desired location and then resize and rotate it such that it actually has the correct size and
orientation of the actual feature. There are two ways of generating generic features. One way is
to generate one at a time. The other way is to generate a number of generic features in one
operation -- Model Placement.
You can add generic features to the generic database by picking a feature and then selecting the
Add to Generic FDB... (the generic database must already be loaded). The Generic Features
window will pop up and give you a list of existing features for reference. Type in the name you
wish to use for the new feature and press OK. Or you can use the OpenFlight Output application
to create a generic database by clicking Output > Rendering Engines > OpenFlight > Utilities >
Import OpenFlight Point Features. See “Execution - Using Generic Features with OpenFlight”
42.17.1 Generic 3D Feature Placement

The following steps demonstrate the placement of Generic 3D features:
1. Click Generics > Load Generic FDB on the Feature Extraction window.
2. Click Generics > List Generic Features... on the Feature Extraction window. The Generic
Features window appears and displays a list of the available generic features.
3. Before loading a Generic 3D feature you must specify the class of the feature. Do this by
clicking Current Class icon on your Feature Extraction window and selecting a Polyhedron
class.

4. In the list of available features in the Generic Features window, select the name of the
generic feature you want to place.
5. Toggle to the extraction cursor using the center button on the trackball or F3, and record
the position to place the feature by pressing the left mouse button.
6. Toggle back to the mouse cursor and click Features Attributes icon on the Feature
Extraction window. In the Feature and Element Attributes window you can customize the
attributes (height, width, etc.) of the generic feature.
7. Toggle to the extraction cursor and accept the generic feature by pressing the right mouse
button.
8. Repeat steps 3-6 for each generic feature you want to place.
You can also insert Generic Features into the Feature Database by using Model Placement,
described above. See “Model Placement” on page 42-27
42.17.2 Execution - Feature Extraction

1. Click File > Load Project on the main workstation window to load a project file and load
the imagery of the area containing the features you wish to extract.
2. Click File > Images to load imagery after you have loaded a project. If no imagery is
available, load the GRAPHICS_ONLY.sup pseudo-image.
3. Click Extraction > Feature > Feature Extraction on the main workstation window.
4. Your next step depends on if you are creating a new Feature Database (step 4a) or editing
an existing one (step 4d).
a. New Database—Verify that you have a suitable extraction specification. See
“Feature Database and Extraction Specification,” Appendix C for details. The
template Specifications are in the directory <install_path>/internal_dbs/
SPECS. If none of the template extraction specifications are suitable, you must create
one with Feature Specification Editor (Extraction > Feature > Feature Specification
Editor) and place it in the <install_path>/internal_dbs/SPECS directory.
b. After you have a suitable Extraction Specification, click Open FDB...under File or the
New icon on the Feature Extraction window. Type the name of the new feature
database you are creating in the selection window, then click OK.
c. An list of extraction specification file appears; select your extraction specification
file, then click OK.
d. Existing Database—Click Open FDB...under File or the Open FDB icon on the
Feature Extraction window. Select the name of your feature database and click OK.
5. In the Feature Extraction window, Click Current Class icon. Select the class to which you
are about to extract features.
6. Start delineating the new feature by toggling to the extraction cursor; begin recording
vertices that delineate the feature by moving the extraction cursor to each vertex and
pressing the LMB. Hold down the LMB for curved edges. Continue recording vertices until
the you have delineated the entire feature.
If you are delineating building features that will be used during

Perspective Scene and Rapid Scene generation, you must
draw the roofs in a clockwise direction.
7. To add elements to a complex feature, press the RMB and begin delineating the next
element.
8. Press the RMB to accept a primitive feature. Double click the RMB to accept a complex
feature. Feature attributes will be stored in the database.

9. If desired, edit the feature’s attributes. To edit feature attributes, click Feature Attributes
icon on the Feature Extraction window. To edit graphic attributes, click Graphic Attributes
icon in the Feature Extraction window.
10. Repeat steps 6 through 9 for each feature you wish to add to the feature database.
11. To graphically edit an existing feature, click Select in Sketch. Toggle to the extraction
cursor and move it close to the feature; press the LMB. The feature’s information appears
in the Feature Extraction window. You may now edit the feature with Sketch.
Feature Extraction uses Sketch. See “Sketch,” Chapter 58 for

more detailed information on creating and editing features.
12. To display the contents of the feature database, click Retrieve/Manipulate icon on the
Feature Extraction window. To list all the features click List Filter All in the Feature
Retrieval window. You can also filter the display by class or by attribute.
13. To locate or edit a feature that is not visible on the screen, bring up the list of features in
Feature Retrieval window and select the feature you wish to edit in list by clicking on the
feature, then click Move To Feature icon in the Feature Retrieval window.
14. When you have finished extracting all the features, save the database by clicking File >
Save FDB on the Feature Extraction window.
42.17.3 Reference Database

To use the Reference Database, select File > Reference Database on the Feature Extraction
window. This displays the Select Reference Databases window. You use this window to manage
reference databases. You can add or remove reference databases. You can enable or disable
classes within a reference database. You can toggle the ability to draw a reference database. You
can toggle the ability to snap to a reference database. You can toggle the ability to draw a
reference database using specified class colors, and you can select a solid color for display of a
reference databases. The Draw, Snap, and Spec Colors toggles and the Solid Color button will
affect all selected reference databases.
The Select Reference Database window’s selections are as follows:
SELECT TO
Add Add FDBs to the list.

SELECT TO
Remove Remove FDBs from the list.

Editable Classes Display a window of classes that are selected for drawing and snapping.
Draw Enable all classes from being drawn to.
Snap Enable all classes from being Snap to.
Spec Colors Enable SPEC COLORS which will cause the reference database to be
drawn in its original colors.
Otherwise all features from the reference database will be drawn in the
color on the color indicator button.
42.17.3.1 Reference Database

To use a database as a Reference database, select File > Reference Database on the Feature
Extraction window. The Select Feature Database window’s selections are as follows:
1. Click Add and select a reference database.
2. Highlight the desired DB then click Enabled Classes to select which classes will be shown.
3. After making selections, click OK.

4. Check Spec Colors to use the colors that the DB was created with, or use the color selector
to draw all features in the same color.
5. Click Close on the Select Reference Databases window.

42.17.4 Preference Options

You can set your feature extraction preferences and customize the feature extraction window.
The Feature Extraction Preferences windows let you set your extraction preferences.
SELECT TO
Use Previous Feature For the next new feature you are going to create, use the attribute values
Attributes from the previous feature you created. You may still change the attribute
values manually.
Use Default Attributes from For the next new feature you are going to create, use the default attribute
Specification. values from the specification. You may still change the attribute values
manually.
Before Accepting Geometry The attribute values are captured from the Attribute Window for the new
Data from Sketch feature before you finish the geometry data extraction from Sketch.
After Accepting Geometry The attribute values are captured from the Attribute Window for the new
Data from Sketch feature after you finish the geometry data extraction from Sketch.
Auto Load Previous Feature When starting Feature Extraction, the system automatically load the
Database previous feature database you have worked on.
Show Instructions When performing certain actions, the system displays some instruction
dialogs to help you use the system correctly. If you already know how to
run the system, you may turn this option OFF.

The Customize window lets you remove or add tools to the Feature Extraction window.
42.17.5 Extraction Tips

42.17.5.1 Attribute Value Copying
To change the attribute values of a group of features to have a shared value: (1) pick a feature;
(2) pop-up the attribute window; (3) set the attributes to the values you want shared and set the
toggle on the left to ON; (4) pop-up the Retrieve/Manipulate window; (5) select the group of
features that will share attribute values (they must all be in the same class); (6) Select Attribute
action and press the Apply Action. For attributes without setting their toggle ON, their attribute
values will not change.
42.17.5.2 Changing the Extraction Specifications

The classes of a feature database are defined in the extraction specification file. See “Extraction
Specification” on page C-3 for details. After you create a database, you may want to change the
class definitions, or add classes, or remove classes. To do this, you (1) create a new extraction
specification file with the new class definitions using Feature Specification Editor; (2) open the
database; (3) click File > Save w/New Spec on the Feature Extraction window. This will create a
new database with the new specification. Features that are in classes that are not defined in the
new specification file will be deleted.
42.17.5.3 Copying Selected Features to a New Feature Database

If you need to perform feature selection in other application such as DTM Feature Merge, you
should use Attribute Query and Fence described in this chapter to select features. Copy the
selected features into a new feature database, and then use that new feature database without
needing to perform feature selection anymore.
42.17.5.4 Forcing Features to Lay on the Ground

To set the Z coordinate of all features in an existing database to lay on the ground, use the
batch_fdb command line tool. See “Batch Processing - A Feature Database” on page 42-43
for details. To force features to lay on the ground while you are delineating them, use the Terrain
Tracking tool.

42.17.5.5 Scale and Rotate

Scale and Rotate functions are highly sensitive and features can be lost if not used carefully.
42.17.5.6 Clockwise or Counter-Clockwise Orientation

If you are going to input the Feature database into Perspective Scenes or other rendering
applications, you must extract volume feature polygons in a either clockwise or counter-
clockwise manner. There is a preference in Sketch under AutoCreate that let you set the desired
polygon vertex order.
42.17.5.7 Sketch Support for Extracting Building Features

The Square sample mode in Sketch will help you when you are delineating a building rooftop by
forcing the sides of your roof polygon to be at right angles.
The A F E Rooftop sample mode uses computer vision techniques to fit your rooftop polygon to
the corners of the building rooftop. This works best for rooftops whose outline consists of right
angles. You must sample the lines of the polygon near the edges of the rooftop for this mode to
work.
42.17.5.8 Extracting Complex Features

From time to time you will encounter features that are too complex to extract as one simple
feature. These features are sometimes referred to as complex or compound features, meaning
several features are combined to represent a single complex feature.
One of the best ways to extract complex features is to break them down into simpler components.
The following figure shows a couple of ways this feature can be broken down. Either
decomposition is correct.
Complex Feature A 2 3
3
1 2 1 Features
Features
Decomposition A Decomposition B

Another example of a complex feature is a doughnut type feature, as shown in the figure below.
Doughnut type features may be buildings that might have a courtyard.
Overhead View
The same principles for extracting a complex feature apply for these types of features. The figure
below shows several examples on how to decompose these features.
Feature #1
Feature #1
Feature #4 Feature #2
Feature #3
Feature #2
Decomposition A
Decomposition C
Feature #1
Feature #2
Decomposition B
Any of these decompositions will work very well. Remember that you can use the Autocreate
tools to create each of the features.
Whenever you decompose features in this way, you should always be sure that each feature is
connected. This means you need to extract the features so that there are not any gaps introduced
into the complex feature that would make it look like several features when it is rendered.
One of the most significant side effects of extracting compound features are gaps between the
features that compose the compound feature. This is much more noticeable during the rendering
phase than the extraction phase. Decomposition A (in the above diagram) is an example of when
gaps can be introduced during Feature Extraction. The figure below illustrates an example of a
compound feature with gaps.

The features do not abut correctly.
These features do not have any gaps.
There are a couple of ways that you can extract compound features to avoid introducing gaps
between the features. One way is to enable Snap To Vertex under Sketch User Preferences. The
other way is to use Sketch’s Segment Operations to share common points from neighboring
features.
When attaching an extension of a

building as shown to the left, you
set the Snap Mode to Perpendicular
and Dimension to 2D.
After the snap, the Z coordinate will
be the same as the extraction cursor,
but the XY coordinates will change
to the perpendicular point on the line
in the main building.
42.17.6 Editing Features without Imagery

You can display and edit features without imagery by using the GRAPHICS_ONLY.sup image.
When you display this image on the main image display, you can view features from any angle,
and without imagery. See “Graphics Projection” on page 61-37 for more information.
42.17.7 Area Based Editing

Area based editing increases productivity by enabling extraction of features within a certain area.
It allows you to suspend extraction of a feature and collect a different feature type. For example,
if you are digitizing a very long street when you see a fire hydrant that you missed. Instead of
having to finish the street, you can switch to the fire hydrant class and extract it. When you
change back to the street class the cursor will jump back to the point where you left off and let
you finish the street. It will automatically remember which tool you were using, if you switched
tools, and put you back in creation mode. The number of classes that can be suspended part way
through extraction is unlimited.
42.18 Batch Processing - A Feature Database

FEI can perform these operations in batch:
•Automated Population of Dimensional Attributes (ADA)
•Make Features Conform to DTM (EA)
•Convert Feature Database from v50 to v44

42.18.1 Automated Population of Dimensional Attributes (ADA)

% start_socet -single batch_fdb 1 project feature_db_name
See “Dimensional Attributes” on page 42-29 for details.
42.18.2 Make features conform to DTM (EA)

This operation takes a 2-Dimensional (X,Y) feature delineation and assigns the elevation (Z-
Coordinate) to all feature vertices based on the interpolated value from the DTM. The Z-
coordinate will be assigned (or reassigned) to all features, replacing any existing Z-
coordinates.

dtm_filename
Assign Z value to all vertices of features. This process forces all features to lie on the
ground. As an example, this can be used after importing a feature file from a 2D (X &Y only)
GIS such as 2D shapefile.
42.18.3 Convert Feature Database from v50 to v44

This operation converts a SOCET SET Feature Database from v50 to v44. In v50, the
specification file format has changed to use XML, the XYZ coordinates have been changed to use
double precision.

Chapter 43
Feature Database Merge

Feature Database Merge merges two feature databases into
one feature database.
43.1 Overview
You use Feature Database Merge to merge two adjacent feature databases into one feature
database. You can perform geometry data edge matching and feathering, and attributes merging/
editing.
43.1.1 When to Use Feature Database Merge

You use Feature Database Merge after you have extracted two or more adjacent feature databases
and you want to merge them into a single merged feature database. When there are more than two
feature databases, you can merge two feature databases at a time, and then merge the output from
the previous merge with another non-merged feature database. To best utilize Feature Database
Merge, you may define the feature database boundary by adding rectangular polygon into the
SS_FDB_BOUNDARY class in your feature database. During feature extraction, you stop
extractions right at the boundary or extend a few pixels beyond the boundary. For example, you
have a large project which covers a 3 degree by 3 degree area. You may divide the area into nine
1 degree by 1 degree areas and create nine feature databases with the same specification file. For
each feature database, you define the database boundary by adding a rectangular polygon into the
SS_FDB_BOUNDARY class, which is the last class in your feature database and it is
automatically added by SOCET SET. The rectangular polygon should cover exactly 1 degree by
1 degree area.
43.2 Feature Database Merge

To start Feature Database Merge, you select Extraction > Feature > Feature Database Merge.
Typically, you open feature database 1, feature database 2, and the merged feature database and
in the above order. The merged feature database must be a brand new empty feature database.
You use the Draw button and the Auto Draw toggle to display both feature databases and locate
where the overlapping area of the two feature databases. You can select drawing colors in the
Preference window. Once you have identified the merge area, you click Merge. After that, you
must then define a bounding box. The center line of the bounding box is used to perform
automatic merge. The automatic merge uses parameters you have defined in the Preference
window such as feathering, XY tolerance, Z tolerance, attributes used for auto merge.
SOCET SET Page 43-1

Chapter 43 - Feature Database Merge
In some cases, you may need to define the bounding box in more than one area; you can do so by
finishing one area at a time. The bounding box center has to coincide with the boundary between
the two feature databases since the boundary between the two feature databases may not be one
single straight line. Once you have completed all the merges, you click Save Final Version. If
you have not completed all the merges and you need to stop the operation, you press Save. This
will save the results into temporary feature databases. Next time, when you start the Feature
Database Merge, the system will automatically open the temporary feature databases and let you
continue your work.
FDB1 FDB2
The red line is the boundary between FDB1 and FDB2. You need to define the bounding box in
three areas such that the center line of the bounding box coincides with the boundary between the
two feature databases.
The Feature Database Merge window’s selections are as follows:
File > Open Feature Prompts you to pick the first feature database to be merged.
Database 1...
File > Open Feature Prompts you to pick the second feature database to be merged.
Database 2...
File > Open Merged Feature Prompts you to enter the name of the merged feature database. The
Database... merged feature database must be a brand new empty feature database.
The order to open the three feature databases must be feature database
1, feature database 2, and the merged feature database.
Page 43-2 SOCET SET

File > Save Save partially merged features into temporary feature databases. This
should be used only when you cannot finish the merge in one session
and you want to continue the merge in the next session. In the next
session, when you start this application, the application will
automatically load the temporary feature databases and let you
continue the merge.
File > Save Final Version Complete merging the two feature databases.
Copy the rest of features from feature database 1 and feature database
2 into the merged feature database. After save the final version, you
can exit, or you can load another set of feature databases to merge.
File > Exit Exits Feature Database Merge.
SELECT TO
Feature Database 1 Select the name of the first feature database to be merged. You can use
the button on the right side to open feature database 1.
Feature Database 2 Select the name of the second feature database to be merged. You can
use the button on the right side to open feature database 2.
Merged Feature Database Select the name of the merged feature database. You can use the button
on the right side to open merged feature database.
FDB1 Draw the contents of feature database 1.
FDB2 Draw the contents of feature database 2.
Merged FDB Draw the contents of merged feature database.
Draw Feature Draws the contents of the feature database and reference database.
Cancel Drawing Stop drawing features.
Auto Draw Toggle to automatically draw the contents of the feature database and
reference database(s).
Preferences Display the preference window. You use set/select your preferences in the
<Ctrl>P preference window.
SOCET SET Page 43-3

SELECT TO
Merge Start merge. You must draw a bounding box to define the merge area
by holding down, dragging, and releasing the cursor. When merging
two feature databases in the order of up and down, the width of the
bounding box must be greater than the height. When merging two
feature databases in the order of left and right, the height of the
bounding box must be greater than the width. The center line of the
bounding box is used to perform automatic merge. Therefore, it is very
important to define the bounding box such that the center line is at the
center of the overlapping region of the two feature databases. In some
cases, you may need to merge a number of areas one at a time. After
you have defined the bounding box, the system will perform automatic
feature merges and brings up the Merge Features window with the
results from the automatic feature merge process. In the Merge
Features window, you can verify the automatic feature merge, perform
manual merge etc.
Save Save the file. Same as File > Save.
Save Final Version Save the final version. Same as File > Save Final Version.
Page 43-4 SOCET SET

43.2.1 Merge Features

This window is displayed right after you have defined the bounding box. The automatic merge
results are displayed in this window. If the results are unacceptable, you may close this window
by clicking Close and then change some of the parameters from the Preference window and then
redraw the bounding box. When a polygon intersects the center line exactly twice, the polygon is
broken up into two lines for merging. From the image window, you may see some nodes (a small
box). These nodes indicate that the automatic merge could not merge successfully. When you
click on the row header (left most gray column) of the Merge Features table, the system will drive
the cursor to that feature and highlight that feature as well. If you want to view and edit attributes,
you double click on the row.
Clicking on the Row Header will not bring up the Attribute

window. You must click on a cell within the row, but not the
State and Confirm cells.
The Merge Features window selections are as follows
SELECT TO
Sample Vertices Select, after setting the Sample Vertices option, you sample two or more
points starting from the line from feature database 1 (line 1) and ending at
the matching line from feature database 2 (line 2) using LMB or the
Sample button. You can also snap to line 1, sample a number of points, and
then snap to line 2. You accept or finish the sampling by pressing RMB or
the Accept button. The same procedure applies to Polygon, Line,
Multiline, and Polyhedron geometries. In this process, they are all
considered as lines regardless of their original geometry types. For Text
and Point geometries, you do not need to use this option.
Polygon Union Select, after setting the Polygon Union option, you first select both
polygons using the LMB by clicking on the polygons. Then press the LMB
to accept the union.
This tool is useful to merge polygon features that the automatic merge
fails. For Polygon and Polyhedron features, this option is more efficient
than the Sample Vertices option.
SOCET SET Page 43-5

SELECT TO
Delete After setting the Delete Features option, you delete a duplicated feature.
<Shift>F8 You place the cursor near the feature and press the LMB. You must click
the LMB a second time to confirm the delete.
Undo This tool undoes previous action such as delete feature, polygon union, and
<Ctrl>u sample vertices.
Unmatched Features Show unmatched features.
Matched Features Show matched features.
Confirmed Features Show confirmed features.
Unconfirmed Features Show unconfirmed features.
Set All Matched Features to Confirm all matched features.

Confirmed
Preference Bring up the Feature Database Merge Preference window.

<Ctrl>P
Print Merge Features Write Merge Features to the report file. The report file is an ASCII text file
with the file name of merge_feature_database.txt. For example, if the
merged feature database name is merge_fdb, the report file name will be
merge_fdb.txt.
Save Confirmed Features Save confirmed features to the merged feature database.
Available Classes You can select one class to merge at a time or all the available classes.
It is recommended that you select and merge one class at a time.
Page 43-6 SOCET SET

SELECT TO
Merged Feature Table BLANK SPACE

ID Entry ID in the Merged Feature Table. A feature can have more than one
BLANK SPACE entry in the Merged Feature Table if the feature intersects the center line
BLANK SPACE more than once.
Match ID Matching entry ID in the Merged Feature Table.
State State can be one of the following:
BLANK SPACE • AUTO_NOMATCH
BLANK SPACE • AUTO_DELETE
BLANK SPACE • AUTO_MATCH
BLANK SPACE • MANUAL_NOMATCH
BLANK SPACE • MANUAL_DELETE
BLANK SPACE • MANUAL_MATCH
BLANK SPACE • MANUAL_UNION
BLANK SPACE • COMPLETE
Confirm Confirm that the matching is correct by checking on the check box.
Class Name Class name
Geometry Class geometry
Close Completes the operation and closes the window.
43.2.2 Feature Database Merge Preference

You can bring up the feature database merge preference window from either the main feature
database merge window or the Merge Features window. This window lets you set the parameters
and colors.
SOCET SET Page 43-7

SELECT TO
Center Line Display color of the center line

Center Line Width Width of the center line. You can select a number from 1 to 3 pixels.
Nodes Display color of the nodes.
FDB1 SPEC If checked, draws features in FDB1 using the color defined from fea-
ture graphic attribute. If not, draws feature using selected color.
FDB2 SPEC If checked, draws features in FDB1 using the color defined by the
feature graphic attributes. If not, draws features using selected color.
Merged FDB SPEC If checked, draws features in merge FDB using the color defined from
the SPEC. If not, draws features using selected color.
Matched Features If checked, draws matched features using the color defined by the fea-
ture graphic attribute. If not, draws features using selected color.
XY Tolerance XY tolerance in project Z unit for automatic merge
Z Tolerance Z tolerance in project Z unit for automatic merge
Feathering Distance If checked, you may enter feathering distance or use the system
generated default value.
Show Info If checked, when pressing the Merge, Save, and Save Final Version
buttons, the system displays an information dialog. If not, the system
will not display the information dialog.
Use FDB MBR In most cases, you should use the FDB MBR to determine the merge
order. Merge order is the left and right, or up and down order of the
two databases. Only when the two databases MBRs cannot be used to
determine the merge order, you may try the not Use FDB MBR option
to determine the merge order.
Available Classes list All the classes in feature database 1 and feature database 2
Attributes Attributes of the highlighted class. You may select a subset of non-
metric attributes for automatic merge. For example, class ROAD has a
non-metric attribute of ROAD_NAME. If you select ROAD_NAME
for automatic merge, the matching feature must have exactly the same
attribute value for ROAD_NAME.
43.2.3 Attribute Window

To open this window, you double click on a row (but not on the row header, State cell, or the
Confirm cell) in the Merge Features Table to bring up the attribute window.You can view and
edit both feature attributes and element attributes in this window.
Clicking on the Row Header will not bring up the Attribute

window. You must click on a cell within the row.
Page 43-8 SOCET SET

SELECT TO
Feature/Element Attribute Display feature/element attributes.

Table
NOTE: Feature ID and Element ID are not editable.
Row Header Toggle If you do not want to see certain attributes, you can set the row header
toggle ON and then press the Mask button. This will hide the attributes
you have checked.
Name [Type] Display Name [Type] of attribute.
Value Display Value of attribute. You can change the values.
Mask Mask or hide checked attributes. Once an attribute is masked, that
attribute will not show up in this window anymore for all the features
of the same feature class.
Unmask Unmask or show all attributes.
Set All Instead of setting/checking the attribute on at a time, you use this
button to set/check all of them.
Unset All Unset/Uncheck all the attributes.
SOCET SET Page 43-9

43.3 Execution
1. Click Extraction > Feature > Feature Database Merge on the main workstation window
to start Feature Database Merge.
2. Click Feature Database 1 button or File > Open Feature Database 1... and open the first
existing feature database.
3. Click Feature Database 2 button or File > Open Feature Database 2... and open the
second existing feature database.
4. Click Merged Feature Database button or File > Open Merged Feature Database... and
enter the name for a brand new non-existing feature database. Make sure you open the three
feature databases in the above order.
5. Click the Draw Features icon and locate the overlapping/joining area between feature
database 1 and feature database 2. You can set different drawing colors for feature database
1 and feature database 2 using the Preferences window.
6. Click the Merge icon and draw a bounding box. You toggle the extraction cursor and hold
down the LMB and drag it to define a bounding box. When merging two feature databases in
the order of up and down, the width of the bounding box must be greater than the height. When
merging two feature databases in the order of left and right, the height of the bounding box must
be greater than the width. The center line of the bounding box is used to perform automatic
merge. Therefore, it is very important to define the bounding box such that the center line is at
the center of the overlapping region of the two feature databases.
7. In the Merge Features window, you merge one class at a time by selecting the class from
the box at the lower-left corner of the window.
8. You can view and edit the attributes by double clicking on a row, but not on the row header,
the State cell, or the Confirmed cell.
9. For those features which have been automatically matched, you visually check them and
then click the Set All Matched Features To Confirmed icon. For those features that have
not been matched, you follow steps 10-12 to manually merge them.
10. For Point, Text, and volumetric Polyhedron features, you use the Delete option to delete
duplicated features.
11. For polygon and element polygon of non-volumetric polyhedron features, you use the
Union option to union polygons from feature database 1 and the corresponding polygon
from feature database 2.
12. For Line and Multiline features, you use Sample Vertices option to merge them by
sampling two or more points starting from the line from feature database 1 (line 1) and
ending at the matching line from feature database 2 (line 2) using LMB or the Sample
button. You can also snap to line 1, sample a number of points, and then snap to line 2. You
accept or finish the sampling by pressing RMB or the Accept button.
13. Once all the features which need to be merged, have been merged either automatically or
manually, you click the Save Confirmed Features icon.
14. Repeat steps 7-13 for all the classes. And then click the Close button to finish the merge in
this area.
15. If you need to merge in another overlapping/joining area, you repeat steps 5-14.
16. Once all the merges are complete, you click the Save Final Version button.

Chapter 44
DTM/Feature Merge
DTM/Feature Merge covers modifying DTM from features
and merging them into a single DTM.
44.1 Overview
DTM/Feature Merge will run any of the following situations:
• Merge Multiple DTMs
• Update DTM with Features
• Change DTM Post Spacing
• Change DTM Boundary
• Converting DTM format from Triangular to Grid, or Grid to Triangular
44.1.1 When to Use DTM/Feature Merge

1. Merge Multiple DTMs—DTM/Feature Merge takes multiple DTMs and merges them into
a single DTM. The input DTMs can have different post spacings. This is commonly used
in two situations: (a) combining DTMs that were generated from multiple stereo models;
and (b) producing a DTM over a stereo model which has varying roughness. For a model
with varying roughness, it is sometimes useful to collect the data by regions where you
select the spacing appropriate to the terrain roughness. Then DTM/Feature Merge is used
to merge the regions to a single spacing DTM, usually the densest spacing of the input
DTMs.
Input DTM 2
Input DTM 1
Resulting DTM
2. Update DTM with Features—DTM/Feature Merge will adjust a DTM to conform to the
features (lakes, ridges, drains) in a given feature database. This will modify the DTM to
conform to the features such as lakes, ridges, streams, in your feature database into the
DTM. You can interactively extract features at the same time you are running Automatic
Terrain Extraction. After Automatic Terrain Extraction finishes, you can merge the features
into the DTM. After Merging the features, you should use Interactive Terrain Editing to
review the results. In addition, you can merge features into the DTM before running
Automatic Terrain Extraction, which often helps Automatic Terrain Extraction generate
SOCET SET Page 44-1

Chapter 44 - DTM/Feature Merge
better results. You can use DTM/Feature Merge to merge building features (i.e. rooftops)
into a DTM for line of sight analysis, orthophoto generation, or Voxel DTM creation. The
output DTM must be relatively dense to represent rooftops as elevated posts. See “Terrain
Analysis,” Chapter 51 for details of the Line-of-Sight function.
Before Merge After Merge
Ridge Feature
DTM rendered as contours
3. Change Post Spacing—DTM/Feature Merge resamples a given DTM to any post spacing
you choose. This is useful when producing sparse or dense DTMs. Sometimes it is useful
to automatically extract the DTM at a dense spacing (this helps Automatic Terrain
Extraction correlation) and then thin the data using DTM/Feature Merge before interactive
editing. Optionally, it is useful to automatically extract the DTM sparsely (to save time or
because the terrain is relatively flat), and then use DTM/Feature Merge to make the DTM
very dense before interactive edit. This may be desirable when only a few details need to
be interactively edited and a dense spacing is necessary to model the terrain.
4. Change DTM Boundary—DTM/Feature Merge will take a given DTM and create an
output DTM of any boundary that you specify. You could use this to crop-out erroneous
data at the edges of the input DTM.
5. Converting DTM format from Triangular to Grid, or Grid to Triangular. You can
perform one or more of these tasks simultaneously. For example, you can merge two DTMs,
resample them to a different post spacing, force them to conform to a given feature
database, and output a new DTM with a different boundary all in one single operation.
ONE OR MORE CLASS ALGORITHM

ONE OR MORE
FEATURE DATABASES SETTINGS FILE
DTMS
(OPTIONAL) (OPTIONAL)
DTM/FEATURE
MERGE
OUTPUT
DTM
Page 44-2 SOCET SET

DTM/Feature Merge gives you several options to control how the DTMs are merged together,
including:
• Which posts to output when multiple input DTMs overlap.
• The output DTM boundary.
• Whether to feather the edges of the DTMs, and the width over which the feathering
is performed.
• Format of output DTM
44.1.2 Data Flow

You control DTM/Feature Merge by interacting with the main application window. You can
select the Input DTMs, select the settings for the output DTM and select an output DTM name.
You can select feature databases, classes algorithms, and class algorithm setting files (.cas).
DTM/Feature Merge organizes these windows into the following hierarchy:
DTM
Feature
Merge
Select Select View DTM View/Edit

DTMs Feature DB Parameters Boundary
Class
Select .cas Algorithm
Edit
SOCET SET Page 44-3

44.2 DTM Feature Merge

To display this window, click Extraction > Merge on the main workstation window.
The DTM Feature Merge window’s selections are as follows:
MENU CHOICES DESCRIPTON
File > Load Project Pick a project to work in.

File > Exit Exits the DTM Feature Merge Window.
SELECT TO
DTM/Feature Merge To execute a DTM/Feature Merge.

DTMs Select a DTM. By clicking the RMB in the
(Click RMB to:) field will provide you the following choices:
BLANK SPACE Select the DTM to merge. Adds the DTM you
BLANK SPACE picked to the list of input DTMs.
BLANK SPACE NOTE: The maximum number of DTMs is
BLANK SPACE 80. For UNIX systems, the maximum
number of DTMs will also depend on the limit of file descriptors the
BLANK SPACE system allows.
BLANK SPACE
Add... If you run ATE on the merged DTM, you must select the DTM with the
images ATE uses first.
BLANK SPACE
BLANK SPACE
Delete
Delete the highlighted DTM from the selection list.
BLANK SPACE
BLANK SPACE
BLANK SPACE
Bring up the DTM Information window for the highlighted DTM. The
View Info... DTM Information window is a non-editable window that displays
BLANK SPACE information on the selected DTM. You can switch between files by
BLANK SPACE highlighting the DTM with a RMB click and select View Info....
BLANK SPACE The information in the window will be updated with the
information of the currently highlighted DTM.
BLANK SPACE
BLANK SPACE
Build List Using
Output MBR Will build a list of input DTMs that have an MBR which is inside of or
intersects with the MBR specified in the Output Footprint.
Page 44-4 SOCET SET

SELECT TO
Feature Database Build the list of input feature databases

(Click RMB to:) to merge. By clicking the RMB in the field
BLANK SPACE will provide you the following choices:
Add... Present a list of feature databases to pick from.
BLANK SPACE Add the feature database you picked to the list
of input feature databases.
BLANK SPACE
BLANK SPACE
BLANK SPACE
BLANK SPACE
Delete
Delete the highlighted feature database(s) from the list.
BLANK SPACE
BLANK SPACE
BLANK SPACE
BLANK SPACE
View Info...
Bring up the Feature Information window for the highlighted feature database.
BLANK SPACE
BLANK SPACE
BLANK SPACE
Display the Class Algorithm Edit window which allows you to customize
Edit Class Algorithms... merging algorithms for specific classes.
Select Algorithm Prompt you to pick a Class Algorithm Settings (.cas) file.
Settings File...
BLANK SPACE
NOTE: ALL features in the feature database will be merged into the
output DTM if they are within the output MBR. If individual feature
selection is desired, it must be done in feature extraction.
NOTE: If there are buildings which already have bottoms among
the features to be processed, they must be in a class named
“BUILDING.” If the class is not named “BUILDING,” the results of
the merge will be unpredictable (the merge may or may not be
successful). If the buildings do not have bottom elements, then
there is no constraint on the name of the class.
Output DTM Name Select the name of the output DTM.

NOTE: You cannot overwrite an existing DTM with a DTM of the
same name and with a different output format (TIN vs. Grid). You
must either choose a different name for the new DTM, rename the
first DTM, or delete the first DTM.
SOCET SET Page 44-5

SELECT TO
Precedence BLANK SPACE

Order of Input Merge the DTMs according to their order in the DTM List. The DTMs at
BLANK SPACE the top of the list have precedence over those at the bottom.
Resolution Merge the DTMs according to their resolution (post spacing). The DTM
BLANK SPACE with the higher resolution (smaller post spacing) has precedence over those
with lower resolution (larger post spacing). If more than one DTM has the
BLANK SPACE highest resolution, the Order of Input precedence is applied to those
BLANK SPACE DTMs.
FOM Merge the DTMs according to their figure of merit. The DTM with the
BLANK SPACE better figure of merit has precedence over those with worse figure of
BLANK SPACE merits. If no single DTM has a better figure of merit than all of the other
DTMs, the Order of Input precedence is applied to those DTMs.
BLANK SPACE
BLANK SPACE
BLANK SPACE
Merge the DTMs according to resolution first and then by figure of merit
Resolution-FOM when more than one DTM has the highest resolution. If a decision still
BLANK SPACE cannot be made based on better figure of merit, the Order of Input
BLANK SPACE precedence is applied.
FOM-Resolution Merge the DTMs according to better figure of merit first and then by
BLANK SPACE resolution when no single DTM has a better figure of merit than all of the
BLANK SPACE other DTMs. If more than one DTM has the highest resolution out of those,
the Order of Input precedence is applied.
BLANK SPACE
BLANK SPACE
Average
Merge the DTMs such that areas where overlap occurs will be an average
of all of the input DTMs. This results in smaller seams in the output DTM
than the other precedence choices allow.
Output Footprint BLANK SPACE
Union The output DTM boundary is the minimum bounding rectangle
BLANK SPACE encompassing all of the input DTMs. The output DTM spacing defaults to
BLANK SPACE the minimum spacing of the DTMs in the input list.
First DTM The output DTM boundary is the minimum bounding rectangle of the first
DTM in the list of input DTMs. The output DTM spacing defaults to the
BLANK SPACE spacing of the first DTM in the input list.
Extended The output DTM boundary is the minimum bounding rectangle of the first
BLANK SPACE DTM in the list extended by the number of posts given by the Feather
BLANK SPACE Width. The output DTM spacing defaults to the spacing of the first DTM in
BLANK SPACE the input list.
User Input Define the output DTM boundary and post spacing with the Output DTM
Properties window.
Define Properties Enable you to define the output DTM boundary.
Feathering Width (Posts) > Smooth the boundaries where the input DTMs overlap.
Feather Width Indicate the width, in number of posts, of the feathering region on each
side of a boundary when merging DTMs.
Include All Posts in TIN Merge all posts from the input DTMs to the output TIN DTM.
Start Start DTM/Feature Merge execution.
Start at... Displays the Start Batch Job window and lets you initiate the batch job. See
Page 44-6 SOCET SET

44.2.1 View Information

The DTM and Feature Information windows are non-editable windows that displays information
on the selected DTM or feature database.
44.3 View/Edit Boundary

This window will enable you to define the boundary of the output DTM.
See “DTM Properties” on page 35-7 for a full description of this tool.
44.3.1 Class Algorithm Settings

One of the inputs to Feature Database Selection is the name of the Class Algorithm Settings file
(.cas), which defines the algorithms which DTM Feature Merge will apply to the terrain as it
merges the features with the DTM data. The format of the Class Algorithm Settings file is defined
in <install_path>/internal_dbs/SPECS/README.cas file.
1. The first line in the file is Class Algorithm Settings Version 2.0.
2. Comment lines begin with the # character.
3. Each line defines which Interactive Terrain Editing algorithm to apply to each class of
feature. Each line consists of the feature class, followed by the Interactive Terrain Editing
algorithm definition. See “Interactive Terrain Edit,” Chapter 39 for details about each
algorithm. The Interactive Terrain Editing algorithm definitions you can specify in the
Class Algorithm Settings file are as follows:
The area tools and geomorphic tools work on Grid or Triangular DTMs as indicated by the DTM
format column in the table below.
DTM
GEOMORPHIC EDIT ALGORITHM PARAMETER
FORMATS
uniform_slope Grid First Value: Interpolation distance
u_shaped Grid First Value: Interpolation distance
SOCET SET Page 44-7

DTM
GEOMORPHIC EDIT ALGORITHM PARAMETER
FORMATS
v_Shaped Grid First Value: Interpolation distance
bulldozer Grid First Value: Interpolation distance
bulldozer_with_feather Grid First Value: Interpolation distance
hedge_trimmer Grid First Value: Interpolation distance
breakline Triangle First Value: Buffer Width

Second Value: Densify Length
DTM
AREA EDIT ALGORITHM PARAMETER(S)
FORMAT
smoothing_convolution_5x5 Grid N/A
interpolate_1st_order Grid N/A

interpolate_2nd_order
clip_outside Grid/Triangle N/A
set_fom_inside Grid/ First Value: Figure of merit value

Triangle (integer)
extract_patch Grid First Value: File name (string)
queue_suspect_posts Grid First Value: File name (string),

Spike detection (0=no, 1=yes),
FOM list (integer FOM values
separated by spaces and commas)
plane_fill Grid N/A

See “Plane Fill” on page 39-13
constant_polygon_average Grid/ N/A

constant_polygon_maximum Triangle
constant_polygon_minimum
constant_user_entered Grid/ First Value: Elevation (floating point
Triangle number)
smoothing_convolution Grid/ N/A

Triangle
bias Grid/Triangle First Value: Elevation bias (floating

point number)
1st_order_fill Grid N/A
2nd_order_fill Grid N/A
plane_fill_with_feather Grid N/A
interpolate_from_good_pts Grid N/A
Page 44-8 SOCET SET

DTM
AREA EDIT ALGORITHM PARAMETER(S)
FORMAT
area_thinning Grid/Triangle First Value: Vertical Deviation

(ft/m) floating point
eliminate_trees_and_ Grid/Triangle First Value: Minimum Object Height

buildings Second Value: Maximum Terrain
Slope in Degree.
eliminate_wells Grid/Triangle First Value: Minimum Depth
DLD Grid/Triangle First Value: Accuracy

Second Value: Step Height.
delete_points_inside Triangle N/A
delete_pts_and_add_brkln Triangle N/A
delete_pts_and_add_brkln_ Triangle N/A

lay_on_ground
closed_breakline Triangle N/A
make_perimeter_invisible Triangle N/A
delete_breaklines Triangle N/A
closed_polygon_lay_on_ Triangle N/A

ground
make_visible Triangle N/A
make_invisible Triangle N/A
create_building Grid/Triangle N/A
The following example Class Algorithm Settings file is for a SOCET SET feature file that
contains lake, road, and cover features:
Class Algorithm Settings Version 2.0
LAKE constant_polygon_average
ROAD u_shaped 20
COVER interpolate_from_good_pts
If you want to generate a digital elevation model, use the eliminate_trees_and_buildings
algorithm for class BUILDING. If you want to generate a digital surface model, use the
create_building algorithm for class BUIILDING.
SOCET SET Page 44-9

44.4 Edit Class Algorithm Settings

When DTM Feature Merge merges line and polygon features into the DTM, it applies an
algorithm to each feature class.
You control which algorithm to apply with the Edit Class Algorithm Settings window. To open
this window, right click on a feature database from the list on Feature Database Selection
window, then select Edit Class Algorithms.... For each line feature class, you choose one of the
geomorphic edit tools with a RMB click; Uniform Slope is the default. Point features are not
listed. Point features are merged into Triangular DTM only. For each polygon feature class, you
choose one of the terrain area edit tools.
Smoothing_conversion 3x3 is the default. See “Interactive Terrain Edit,” Chapter 39 for detailed
descriptions of the terrain editing algorithms. This table summarizes the algorithms available for
line and polygon classes.
The Class Algorithm Edit window’s selections are as follows:
SELECT TO
Class / Algorithm Table Open a scrolling window containing one entry per class in the feature
database. Point and Text feature class are not shown. Feature classes with
no features in them are not shown. Some algorithm requires one parameter.
You enter the value of the parameter in the First Value. Some other
algorithm requires two parameters. You enter the first parameter in the
First Value field and the second parameter in the Second Value field. Refer
to the GEOMORPHIC EDIT ALGORITHM table and the AREA EDIT
ALGORITHM table for details.
BLANK SPACE
For line features, the Algorithm is a menu of geomorphic edit tools:.
BLANK SPACE
For polygon features, the Algorithm is a menu of terrain area edit tools.
First Value Display the first parameter used for the selected algorithm.
Second Value Display second parameter used by the selected algorithm.
Close Close the Class Algorithm Edit window.

44.5 Executions - Merge
44.5.1 Merging DTMs and Features Files

1. Click Extraction > Merge on the main workstation window.
2. If you have not already loaded a project on the workstation, you must do so now by clicking
File > Project....
3. Right-click in the DTMs field and click Add... to select an input DTM.
4. [Optional] Remove any DTMs from the list by highlighting them with the RMB, then
clicking Delete.
5. [Optional] View the DTM information by highlighting a DTM from the list with the RMB
then clicking View Info....
6. If you have already defined an output DTM boundary, you can use Build List Using Output
MBR. This will build a new list of DTMs that have an MBR which falls inside or intersects
with the output DTM boundary you have defined.
This will remove any previously selected DTMs from the list.
7. [Optional] Right-click in the Feature Database field and click Add... to select a feature
database.
8. [Optional] Right-click in the Feature Database field and click Select Algorithm Settings
file....Choose the name of your Class Algorithm Settings (.cas) file and click Open.
9. [Optional] To edit the algorithms that apply to a feature class within a feature database, start
up the Edit Class Algorithm Settings window by right-clicking on a feature database and
selecting Edit Class Algorithms.... Edit the class algorithms and then click Close when you
are finished.
10. Select and/or edit the name of the output DTM by clicking the index to the right of the field.
11. Select the type of precedence used for merging overlapping DTMs on the DTM Feature
Merge main window by selecting the Precedence option. This is only available for GRID
DTM.
12. Select the footprint of the output DTM on the DTM Feature Merge window with the Output
Footprint option.
13. If you selected User Input for the Output FootPrint, click Define Properties.... This will
bring up the Output DTM Properties window. The density, or number of output posts may
be increased by either reducing the X and/or Y spacing values or reducing the boundary of
the output merged DTM in the View/Edit DTM Boundary window.
14. If you wish to perform feathering on the output DTM, toggle the Feathering option and
enter the Feathering Width (in number of posts) on the main DTM Feature Merge window.
15. If you want the output DTM footprint to be the footprint of the first DTM extended by a
certain number of posts, set the Output Footprint to Extended and toggle Feathering to On.
The output DTM footprint will be extended by the specified Feather Width and feathering
will be applied (with the same Feather Width) on the outside of the first DTM’s boundary.
If Output Footprint is set to Extended and the Feathering is toggled Off, there will be no
extension of the output footprint nor any feathering applied.
16. Click Start to begin merging.
44.6 Execution - Start Batch Job

44.7 Batch Processing - DTM Feature Merge

COMMAND LINE:
% start_socet -single dtm_ftr -batch -s setting_file
dtm_ftr merge
KEYWORD DESCRIPTION
project Project filename (select from the .prj files in /usr/geoset/data).
output_dtm Name of output DTM file.
feathering Feather overlapping DTM boundaries (YES or NO)
feather_w Width in pixels of the seam feathering.
output_format Format of output DTM (DTM_GRID or DTM_TIN)
dtm_file Input DTM (selected from the .dth files in the project directory). Use this
keyword repeatedly for multiple DTMs
ftr_file Input feature database. Use this keyword repeatedly for multiple FDBs
cls_algr Name of the Class Algorithm file (.cas).
precedence Output DTM merge algorithm (ORDER_OF_INPUT, RESOLUTION,

FOM, FOM_RES, RES_FOM, or AVERAGE).
spacing_units Post spacing units (UNIT_FEET, UNIT_METERS, UNIT_SECONDS).
x_post_spacing Space between x post
y_post_spacing Space between y post.
output_footprint Output DTM boundary (UNION, FIRST_DTM, EXTENDED or

USER_INPUT).
ll_x The x coordinate of the lower-left corner of the minimum bounding

rectangle of your output DTM.
NOTE: USER_INPUT must be the output_footprint keyword in
order to use the ll_x, ll_y, ll_z, ur_x, ur_y, and ur_z keywords.)
ll_y The y coordinate of the lower-left corner of the minimum bounding

ll_z The z coordinate of the lower-left corner of the minimum bounding

ur_x The x coordinate of the upper-right corner of the minimum bounding

ur_y The y coordinate of the upper-right corner of the minimum bounding


KEYWORD DESCRIPTION
ur_z The z coordinate of the upper-right corner of the minimum bounding

tin_include_all Include all the posts of the input DTMs in the output DTM. (YES or NO).
dtm_mbp_log_path Path string indicating where the DTM Merge by Precision log file should
be stored (e.g., /home/mydata/logfiles/). A log file containing technical
details of the merge is only created when this keyword is included and a
valid, writable path is defined. The log file name will be “dem_merge”
followed by a date/time stamp with a file extension of “log”.

Chapter 45
Annotation
Annotation draws pictures that can be overlaid on an image.
45.1 Overview
Annotation is a drawing tool that overlays vectors, icons, grid lines, and text on top of imagery.
It saves the graphics you create to a file for later editing and viewing. You have the choice of
anchoring your graphics to the ground (normally used for features like rivers and roads) or to the
margin (normally used for image map margin templates).
Annotation lets you draw overlay graphics on an image map, and permanently burn them into the
image map. See “Image Map” on page 52-7 for details.
Once you have created graphics, you can create annotated images for output by making a screen
dump or with Image Map. See “Hardcopy Products and Image Maps,” Chapter 52 for details.
45.1.1 When to Run Annotation

You run Annotation after importing an image into your SOCET SET project. If the image you
wish to annotate has no control data, you should import the image with Image Import/Reformat;
this will create a simple support file which will allow you to display the image.
If you want to save Annotation’s graphics in a file and re-display the graphics on top of another
second image, you should control the first image with Triangulation before running Annotation.
If you don’t control the image before annotating it, the graphics may not register correctly on
other images.
Before running Image Map you may build a margin template file with Annotation. The margin
template contains a standard margin layout that you can use on many image maps.
You should run Annotation while making an Image Map. Annotation lets you draw the following
items in the image map: grid lines and tick marks, margin templates, marginalia, and interactive
overlay graphics.
45.1.2 Counting
Annotation keeps track of the number of graphics you have drawn on the image. You can request
that Annotation report these totals to you; then you can include this data in a photo interpretation
report.
SOCET SET Page 45-1

Chapter 45 - Annotation
One simple approach to counting is to put an icon graphic on the image on top of each item you
want to count. Annotation will keep a separate count of each kind of icon. For example, you could
place house icons on houses and tree icons on trees; Annotation displays the number of house and
tree icons you have drawn by clicking the “Icon” column header.
45.1.3 Comparing Annotation with Feature Extraction

Feature Extraction is a more sophisticated tool which is similar to Annotation. However, Feature
Extraction and Annotation are intended for different purposes. See the table below.
Both tools permit you to draw lines, polygons, points, text strings, and icons; both tools store the
data in 3-dimensional ground space coordinates; both tools store data in disk files for export or
later editing; and both tools use Sketch for editing operations such as translate, move point, rotate,
or stretch.
You use Feature Extraction to define and create a database of three-dimensional graphical
features. You can assign names, layers, and other attributes to the members of the feature
database. Feature Extraction also provides searching, sorting, and retrieval operations.
Annotation provides you with all of the graphical creation and editing capabilities, but none of
the database capabilities. As a consequence, Annotation is easier to learn and is quicker to use for
simple graphical annotation tasks.
Annotation keeps counts of the number of graphics you have created of each geometry type. You
can use this capability to count items in an image, and include the total in a photo-interpretation
report.
Annotation permits you to specify the color of each graphic individually, whereas Feature
Extraction determines each graphic’s graphical attributes based on the class of the feature as
specified in the feature database extraction specification.
The following table summarizes the major differences between Annotation and Feature
Extraction:
FEATURE
ANNOTATION
EXTRACTION
Intended Usage Photo-Interpretation Map Making

Screen Dumps Orthophotos
Image Map Marginalia Site Modeling
Image Map overlays Perspective Scenes
Image Map overlays
Attributes No Yes
Classes and Layers No Yes
Queries No Yes
Data Can be Overlaid on Yes Yes
an Image Map
Database Format ASCII Binary
Supports Volume Features No Yes
and Perspective Scenes
One step Undo No Yes
Page 45-2 SOCET SET

FEATURE
ANNOTATION
EXTRACTION
Stores Arc/Curve control No Yes

points
Shared vertices Only two shapes can Two or more features can
share a vertex share a vertex
Operator Guidance via No Yes (See the “Feature
Extraction Specification Database and Extraction
Specification” appendix)
User-Selectable Icons Yes No
Counting Tools Yes No
Element-by-element Yes No
Coloring
Grid Lines and Tick Marks Yes No
Marginalia for Image Map Yes No
Sketch Icons Yes Yes
SOCET SET Page 45-3

45.2 Annotation
Back to Sketch
45.2.1 Menu Bar

The Annotation window’s selections are as follows:
SELECTION DESCRIPTION
File > Load Prompts you to pick the name of an annotation file (.obj) to load and
display.
File > Save Prompts you pick the name of an annotation file (.obj) to save the
current set of annotations to.
File > Graphic Attributes Brings up the graphics attributes window for selection of color, line style,
and font.
File > Select Icon Pops up a menu to allow icon selection.
Ground / Margin combo box Anchor graphical graphics to either the

(Anchor) • Ground (used for features like rivers and roads)
• Margin (used for building margin template files for Image
Map)
File > Exit Exits Annotation.
Page 45-4 SOCET SET

Options > Preferences Brings up the preference window for sketch options.
Options > Customize Allows customization of the sketch toolbars.
45.2.2 Geometry Tool Buttons

The Annotation window’s geometry button selections are as follows:
SELECT TO
Poly-Line Sets the graphic geometry to poly-line.
Polygon Sets the graphic geometry to polygon.
Text Sets the graphic geometry to point and indicates that you will place a text
string at the next point graphic you create.
NOTE: When entering text using Annotation, you must have the
cursor focus in the Main Image Display (RT) window; otherwise,
the text entered won’t appear.
North Arrow Creates a multi-graphic feature in the shape of an arrow. You set the
location and size of the arrow by dragging a bounding box with the
extraction cursor. Annotation aligns the body of the arrow to lie in the grid
north direction (which may be different from true north). You may scale
and translate the north arrow.
NOTE: Do not rotate the arrow, or else it will no longer point north.
Icon Sets the graphic geometry to point and indicates that you will place an icon
at the next point graphic you create.
Grid Lines Create a set of grid lines and/or tick marks. You can create any number of
grid lines and tick marks, each with a different interval and unique
coordinate system.
SOCET SET Page 45-5

45.2.3 Graphic Attributes

The Graphics Attributes window appears when you click on the grid icon on the main Annotation
window. You use the Graphic Attribute window to define the appearance of the graphics’ color,
lines, and font. You should proceed from top to bottom, setting the characteristics you want.
The Graphic Attributes window’s selections are as follows:
SELECT TO
Color BLANK SPACE

Foreground Set the foreground color of the feature you create. You can set the
foreground color of a feature by picking the feature, setting the foreground
color, and then accepting the feature.
Background Set the background color of the feature. The default is Transparent.
Line BLANK SPACE
Width Display the width in pixels, that the lines of the feature will be drawn in.
Style Specify whether to draw the lines as solid or dashed.
NOTE: Dashed lines are not available on the Windows platform.
Fill Polygon Fill drawn polygons with the background color if the box is checked.
This option only applies to polygons.
NOTE: Filled polygons are filled with the background color.
Font BLANK SPACE

Size Apply text font size option.
The text font sizes available depends on your system configuration.
Page 45-6 SOCET SET

SELECT TO
Type Apply text font family name.

The text font types available depends on your system configuration.
Style Apply text font style option.

The text font styles available depends on your system configuration.
Close Complete changes and close window.
See “Customizing Your Software Configuration,” Appendix D for more information on how to
configure text fonts.
45.2.4 Sketch
Annotation makes use of Sketch as its graphics drawing and editing interface. See “Sketch,”
Chapter 58 for the mechanics of creating and editing graphics (points, poly-lines, polygons, and
text).
45.2.5 Ticks and Gridlines

The Ticks and Gridlines window appears when you click on the grid icon on the main Annotation
window. You use the Ticks and Gridlines window to define the appearance of the grid lines. You
should proceed from top to bottom, setting the characteristics you want.
Grid lines only draw properly if in the same coordinate system

as the project.
The Ticks and Gridlines window’s selections are as follows:
SELECT TO
Margin Ticks Turn small tick marks in the margin on/off.

Grid & Intersection ticks Select how the grids appear in the image interior: as continuous lines or as
plus-sign shaped marks at the intersection points.
SOCET SET Page 45-7

SELECT TO
Grid Coords Select the coordinate system of the grid lines. If you select grid/state plane,
a list window will pop-up that lists all grids, including UTM zones, that are
available. This list is identical to the list of grids that are available when
you create a new project. You can add your own custom grids and
projections to this list, as described in the Project Management chapter.
NOTE: Before you use a grid in annotation, check the grids datum
and ensure that it is what you want.
Grid units Display the units associated with the grid spacing text fields.
X/Y Spacing Select the distance between adjacent gridlines or ticks. You can have
different spacings in the X and Y directions.
Grid Display the coordinate system grid you chose with the Grid Coords button.
Precision Determine how many digits appear to the right of the decimal point in the
grid coordinate labels.
OK Create a new grid and assigns to it the current attributes.
Cancel Create a new grid, but keeps whatever attributes the grid had before the
Ticks and Gridlines window was popped-up.
To create a grid, click grid icon on the main Annotation window, then set the grid characteristics
in the Ticks and Gridlines window, then click OK.
To change the characteristics of a grid you have created: move the extraction cursor near the grid;
pick the grid with the sketch select button, or hot-key <ctrl>m. This will cause the Ticks and
Gridlines window to appear; select the new characteristics in this window; then click Accept.
Clicking on Cancel will not delete the grid.
To delete a grid: pick the grid with the sketch delete button, then press the LMB twice.
You can create more than one grid. For example, you could have one set of grids in lat/long (i.e.
geographic) and one in UTM. Or you can have two sets of UTM lines, but each with a unique
datum.
After adding an additional grid, refresh the image to display all

grids. Failure to do so will result in only the last grid loaded
being displayed.
Every time you click the grid icon on the main Annotation window, a new grid is created. If you
click the grid icon on the Annotation main window, then click Cancel on the Ticks and Gridlines
window, a new grid is created with default values. So it is easy to inadvertently create two
“duplicate” grids with identical spacings, labels, and coordinate systems. If you do this, both
grids will be drawn on top of each other, and you may not even know that you have duplicate
grids.
Duplicate grids are harmless, but you should avoid them

because they will slow down your operations, especially if you
are running Annotation with Image Map.
Page 45-8 SOCET SET

If you think you may have two or more duplicate grids, you should delete all the grids (as
described above) then start over.
45.2.6 Tick and Gridline Markers

There are three kinds of graphical symbols you can use to demarcate intervals: Grid Lines, Tick
Marks, and Intersection Ticks.
31:30 31:45 32:00 32:15
40:45 40:45
Numerical labels are
drawn at every interval.
40:30 40:30
Intersection Ticks - are

drawn at regular intervals in 40:15 40:15
the image interior.

31:30 31:45 32:00 32:15
Tick Marks are small lines

that extend beyond the
image edge. Grid Lines are drawn inside the
image; you select the width and
color.
You can draw more than one set of grid lines. Each set has it own unique characteristics, including
coordinate system, line spacing, color, and line width. You set the grid’s attributes using the Ticks
and Gridlines window.
SOCET SET Page 45-9

45.2.7 Icon List

When you click the Select Icon button on the Annotation window, the Icon List popup menu
appears. This window contains a palette of the available icons. To select an icon, click on it with
the LMB. Notice that the face of the Icon geometry button changes to the icon you selected.
You can create your own custom icons by creating an .icn file in directory
<install_path>/internal_dbs/ICONS/annotation. On UNIX, create a .icn file
using the X windows utility bitmap. Type man bitmap for more information.
45.2.8 Saving Graphics in a File

After you draw graphics with Annotation you may save them to a file so they can be re-used later.
The file you save is called a margin template file. The margin template file will contain all
graphics that you drew, including margin-anchored and ground-anchored graphics. For example,
a Margin Template could contain five graphics anchored to the margin and twenty graphics
anchored to the ground.
Margin template files are most useful when making image maps.
See “Image Map” on page 52-7 for more details.

45.2.9 Anchoring
Some graphics that you draw will be features that are visible in the imagery, such as buildings,
creeks, and trails. Other graphics that you draw will be marginalia such as image map titles,
labels, and north arrows.
This distinction becomes important if you are going to save the graphics in a file and then re-
display them on another image. To ensure that the graphics are properly displayed on other
images you must set the Anchor combo button on the Annotation window:
SELECT TO
Ground Anchor topographic features in the image like buildings, rivers, roads, etc.
Margin Anchor marginalia like titles, notes, north arrows, context maps, etc.
Every individual graphic has its own anchor.

This image map is the second
one created. The Margin
My Title This graphic is anchored to Template from the first image
the Margin, so when it is remap is re-used here.
used its location is the same.
My Title
This graphic is anchored to
the ground, so when it is
re-used it appears at the
correct geographic
This image map is the first location in the image
Template file is created now
and contains two graphics.
If you don’t plan on saving graphics to a file and re-using them, you don’t have to worry about
anchoring.
45.3 Execution - Annotation
45.3.1 Starting Annotation

Click Extraction > Annotation & Counting on the main workstation window.
45.3.2 Creating, Editing, and Deleting Graphics

See “Sketch,” Chapter 58 for instructions on how to create and edit graphics.

45.3.3 Creating a Margin Template File

To create a new file, first make your annotations using the Annotation window and Sketch
operations. When you are finished annotating, click File > Save on the Annotation window. In
the file selection box’s Selection field, enter the new file name (with .obj extension) and click
OK to save.
45.3.4 Loading an Existing File

To load an existing margin template file, click File > Load on the Annotation window. Pick the
name of the .obj file to load and click OK.
45.3.5 Saving the Current File

To save your changes to a file you loaded, click File > Save on the Annotation window. Pick the
name of the file you wish to save your changes to and click OK.
45.3.6 Creating Icons on Image

1. Click Select icon on the Annotation window. A display of various icons available -
make a selection.
2. Click the Draw icon and using the Extraction Cursor place icons where desired.
3. Complete the task by clicking a different button on that same toolbar.
45.3.7 Creating a New Grid

1. Click the Grid icon on the Annotation window. The Tick and Grid line window will
pop-up.
2. Select the attributes of the grid by entering data in the Tick and Grid line window.
3. Click OK on the Tick and Grid line window.
45.3.8 Change the Attributes of a Grid

1. Click Select from the Sketch Main Toolbar.
2. Move the extraction cursor onto the grid; press the LMB. This will cause the grid to become
highlighted, and will pop-up the Tick and Gridline window.
3. Change the grid attributes then click OK on the Tick and Grid line window.
45.3.9 Deleting a Grid

Click Delete (x-shaped icon) on the sketch sub-window, then move the extraction cursor
onto the grid, and press the LMB twice.
45.3.10 Exiting Annotation

To exit Annotation, click File > Exit on the Annotation window.

Chapter 46
Orthophoto
Orthophoto creates a new image with no terrain relief.
46.1 Overview
An O r t h o p h o t o is an image that has had all distortion due to camera obliquity, terrain relief,
and features removed. An orthophoto represents what you would see if you were looking straight
down at the ground from an infinite distance above.
Original Image Camera
Orthophoto
DTM
Orthophoto generates orthophoto imagery and offers a wide variety of options. You select a
• Digital Terrain Model (DTM) file(s)
• Image file
• Boundary
to make a simple orthophoto. The ground footprint of an orthophoto is limited by the footprint of
the selected DTM(s) and can be no larger than the ground footprint of the first selected image file.
You can specify any ground sample distance (pixel size, in ground units) for the orthophoto, but
it does not make much sense to specify a ground sample distance that is a lot smaller than the
ground sample distance of your input image.
SOCET SET Page 46-1

Chapter 46 - Orthophoto
Orthophoto is N bands in, N bands out and up to 2 byte in 2 byte out. It will automatically generate
an orthophoto with the number of bands and bytes equal to the number of bands and bytes (up
to 2) in the input image.
Additional options include: eliminating building lean with feature data, embedding grid lines
within the orthophoto, minification, and a choice of image interpolation methods.
46.1.1 When to Use Orthophoto

Prior to running Orthophoto, you must import and control the original input image. You can run
Orthophoto with or without an input DTM. You can either import a DTM, or create one with
If you have a DTM, it should be large enough to cover the desired orthophoto area. If you have
several small DTMs covering the region, you can either select them all during run time or use
DTM/Feature Merge to merge them into a single DTM prior to running Orthophoto. If you do not
have a DTM, you must specify an elevation. Orthophoto rectifies the input images to the project
ellipsoid at the elevation you specify.
You can, optionally, input a Feature Database into Orthophoto. If you do so, Orthophoto will
remove the building lean for the buildings you modeled in the feature database.
After creating the orthophoto, you can use Image Map to add marginalia and overlay graphics.
You can also input the orthophoto into Mosaic to build a large image database.
46.1.2 Orthophoto Generation Data Flow
FEATURE
DATABASE
IMAGE(S) DTM (optional)
ORTHOPHOTO
OUTPUT OUTPUT
IMAGE SUPPORT FILE
Page 46-2 SOCET SET

46.2 Orthophoto Generation
The Orthophoto Generation window’s selections are as follows:
File > Load Project... Select a project file. This choice is only available if you are running
orthophoto in stand-alone mode.
File > Save Settings Saves the current options of the GUI.
File > Exit Exits the Orthophoto window.
SELECT TO
Start Tab BLANK SPACE

Orthophoto (or True Ensure that this radio button is selected.
Orthophoto)
SOCET SET Page 46-3

SELECT TO
Input Tab BLANK SPACE

Primary Image Select the primary image file to use
Image(s) Select the Image files to be use, by highlighting and moving to the
BLANK SPACE Selected box. Adds the file you picked to the list of input files. Example
BLANK SPACE would be Image A and Image B.
Right click ->View Bring up the Image Information window for the highlighted Image file.
Info... BLANK SPACE
Elevation Toggles Tell Change Detection whether to use a DTM file. If On, you must select a
BLANK SPACE DTM file(s). If Off, you must enter an elevation in the Elevation field.
BLANK SPACE This is also useful for making orthophotos in flat terrain or for running
orthophoto recursively.
BLANK SPACE
BLANK SPACE
BLANK SPACE
Move the DTM(s) to use to the Selected box.
DTMs
BLANK SPACE
BLANK SPACE
Reset all fields to blank.
Clear Selections
BLANK SPACE
BLANK SPACE
Prompt you to select the Feature Database file that contains the three
3D Feature dimensional models of the image detail to account for (in addition to DTM
elevation). This helps eliminate the building lean problem. The ground
footprint of the orthophoto is limited to the ground footprint of the first
selected image Additional images are used only as sources of regions
obscured by building lean.
Output Tab BLANK SPACE

Output Options Enter the Name, Location, Format, and JPEG Quality of the output image.
(Name, Location, NOTE: Change Detection places an extension of “.img” on the
Format, JPEG Quality) name regardless of the image format.
BLANK SPACE
BLANK SPACE
BLANK SPACE
Enter the (GSD) Ground Sample Distance to be used when generating the
GSD orthophoto image. Entry must be in the project units. You must enter the
BLANK SPACE GSD before processing can begin. Press the Return key to update the Lines
BLANK SPACE and Samples fields. This will update the footprint and the number of lines
BLANK SPACE and samples which will be output. Note that the footprint may change
slightly as the corners are made to be the nearest multiple of the ground
BLANK SPACE sample distance.
BLANK SPACE
NOTE: If you are building an orthophoto to input to Interactive
BLANK SPACE Mosaic, you must ensure that the GSD matches the mosaic layer
BLANK SPACE GSD, and that the orthophoto is not rotated from North.
BLANK SPACE
Lines Enter the number of lines to be output in the orthophoto.
Samples
Enter the number of samples to be output in the orthophoto
Output Boundary BLANK SPACE
LL-UR or For Lower-Left - Upper-Right, you enter the lower-left and upper-right
Four Corners corners. For Four Corners, you enter all four corners. See “Corner Point
BLANK SPACE Definition” on page 46-10 for additional information.
Upper Left, Orthophoto corners. You can either manually enter coordinates or use the
Upper Right, Method and Update buttons to set them. Use the radio buttons to control
whether you enter UR and LL or all four corners.
Lower Left,
BLANK SPACE
Lower Right
(You must press the Return key in each field after you enter data.)
NOTE: For DTMs, use the minimum bounding rectangle of the
selected DTM(s) to update the Output boundary.
Page 46-4 SOCET SET

SELECT TO
Calculate BLANK SPACE

Draw Polygon and use the corners as the Output boundary. See “DTM
Properties” on page 35-7 for a description on a typical drawing scenario.
NOTE: If you are in Lower Left - Upper Right mode, the MBR of the
polygon you draw will be used. If you are in four corner mode, the
first four corners you draw will be used to define the quadrilateral
and the first two corners will define the alignment Baseline.
Options pull-down box
• Primary Images uses the minimum bounding rectangle of the
footprints of the selected Image file to update the Output
boundary
• DTMs used for the minimum bounding rectangle of the selected
DTM file(s) to update the Output boundary.
• DOQ use a geographic upper-left corner to make Mosaic
compute a DOQ sized boundary. DOQs are spaced on regular
7.5 (quarter-quad) or 15 (quad) minute intervals.
BLANK SPACE
Update is used to calculate the output boundary based on the Primary
Images, DTM(s), or DOQ selection.
SOCET SET Page 46-5

SELECT TO
Options Tab BLANK SPACE

Options BLANK SPACE
Grid Lines Display the grid lines in the output image. Enter the grid line spacing.
BLANK SPACE • Spacing applies the distance between grid lines. Entered the
BLANK SPACE spacing in seconds for geographic projects and feet or meters
BLANK SPACE for other projects.
BLANK SPACE • Gray Level applies the gray level of the grid lines. Ranges from
0 for black, up to 254 for white.
Create World Creates an Arc-Info World file.
File
BLANK SPACE
BLANK SPACE
BLANK SPACE
Create Ortho
Info File Create an ortho info file.
Auto Minify Automatically create a minified image pyramid from the resulting
orthophoto after the processing completes.
BLANK SPACE
BLANK SPACE
Auto Load
Imagery Automatically load the image when processing is complete.
Construct BLANK SPACE
GeoTIFF Create GeoTIFF tags in the output.
Tags BLANK SPACE
Process TIN Treat a TIN terrain file as grid. This will speed up the processing, but the
DTM as Grid rigorous processing of the TIN shape will be lost. This button has no effect
BLANK SPACE if the input DTM is a grid type.
BLANK SPACE When checked, Orthophoto uses the DTM post spacing as a processing
Allow Dense increment. When unchecked, Orthophoto will not allow the processing
DTM increment to become too dense, which results in the best processing speed
BLANK SPACE and memory consumption.
Background Select the colors Black or White.
Color BLANK SPACE
Interpolation Method Bilinear or Nearest Neighbor. The interpolation method that is to be used
when resampling pixels into the orthophoto. Note that if you are
mosaicking ortho-photos recursively, you may want to use the Nearest
Neighbor method; otherwise, it is not recommended.
Stereo Mate Gives you the option of producing a stereo mate to an orthophoto.
Use Turn stereo mate on or off.
Base to Control the amount of vertical exaggeration in the stereo mate.
Height Ratio BLANK SPACE
Left Mate, Choose of which stereo mate to generate (left or right).
Right Mate
Start Start Orthophoto processing.
46.2.1 Image Support Files

Orthophoto normally requires one input support file. However, if you are using a feature file to
eliminate building lean (True Orthophoto), you need to select more than one support file. The first
Page 46-6 SOCET SET

image in the list of selected support files becomes the base orthophoto; the rest of the images in
the list are used as source imagery for building lean removal.
46.2.2 Rectifying with Orthophoto

As an alternative to single image rectification (See “Single Image Rectification” on page 33-3),
you can also use Orthophoto to generate a rectified image. Conceptually, this is the same as
Rectification, but Orthophoto uses a finite element solution rather than an affine transform used
by Rectification. To rectify an image in this manner, set the DTM toggle button to NO on the
Orthophoto window. Rectifying an image with Orthophoto has a drawback: the support data
associated with the output rectified image does not contain information about the original camera
station and hence cannot be used for subsequent processing such as Automatic Terrain Extraction
or Feature Extraction. In summary, to perform single image rectification on an image, you have
two choices: (1) Rectification and (2) Orthophoto. You should use Orthophoto only when you do
not need to use the rectified image for subsequent measurement processing and when the affine
transform is not sufficient (e.g. the input image is highly oblique).
SOCET SET Page 46-7

46.2.2.1 Removing Building Lean (True Orthophoto)

The problem of building lean is illustrated in the following diagram:
1. The raw image may be

oblique, panoramic, or
straight-down. 2. Rectification without a DTM
will resample the imagery so that
the output is North up, and the
vertical and horizontal scales are
equal. However, the DTM relief
will still be visible, and buildings
will be tilted. You can use either
Rectification or Orthorectification.
3. Rectification with a DTM

will remove distortion due to
DTM relief, but will leave
features (like buildings) tilted.
4. Providing a Feature file in addition to a DTM will pull 5. If you have supplemental imagery that
the buildings upright and put the buildings’ roofs over covers the shadow area, the shadow area
their footprints. A shadow will be left on two sides if no will be filled-in with valid imagery.
supplemental imagery is available.
If you do not input a Feature file when generating the orthophoto, the buildings and other artifacts
will lean when they are not exactly under the camera station (as in the illustration above). This
has two adverse effects:
• The roof of the building is portrayed in an erroneous location.
• The terrain that is occluded by the tilt (usually on two sides of the building) is not
displayed.
Page 46-8 SOCET SET

Orthophoto resolves the first problem (erroneous roof location) by inputting a Feature file that
models the buildings, bridges, or other artifacts. The orthophoto that results when a Feature file
is provided is shown in illustration 4 above.
Orthophoto will also solve the second problem (occluded terrain) if you supply one or more
supplemental images that have coverage in the hidden area. Orthophoto will automatically detect
the occluded region and select the best image to use to fill the hidden areas. The result is shown
in the illustration above.
True Ortho runs less quickly when there are a large number of
features in the feature file.
When generating a True Orthophoto, make sure the StereoMate option is turned off.
46.2.2.1.1 True Orthophoto Tips

If you see unexpected anomalies in your true orthophoto, such as black areas or misaligned or
mismatching pixels near the replacement area, try the following:
1. Make sure the nearby feature (roof) is accurately digitized. It usually works best to sample
each point just outside the edge of the roof. Misplaced points may cause ground imagery to
appear on roofs and vice-versa. You can correct the feature using Move Vertex in Feature
Extraction.
2. Check the DTM to see if it agrees with the actual ground level. Place the cursor on the
ground near the building. You can use Terrain Tracking or run ITE to do this. Make sure
the cursor is positioned at the same point on the ground in all the source images. An
inaccurate DTM can cause mismatches between the base image and the replacement pixels.
You can correct the terrain with ITE.
3. If there is a black area, place the cursor on it and set the elevation exactly to the DTM. Bring up
additional viewports to display all the source images. If the ground is not visible underneath the
cursor in any of the source images, then that is the cause of the black area. You must add an
image with the ground visible in this area to correct the problem.
46.2.2.2 Shape and Orientation of the Orthophoto

There are two ways you can specify the shape and size of the output orthophoto.
1. You can specify a rectangular orthophoto by entering the locations of two opposite corners
(upper-right and lower-left). This approach also yields a rectangle oriented along lines of
north-south and east-west.
2. You can create a rotated orthophoto by entering all four corners of the output boundary.
This permits you to output Mosaics that are rotated with respect to the project coordinate
system north-south lines. You might use this capability, for example, to generate
orthophotos that follow transportation routes. When you define the four corners of such a
quadrilateral, the definitions of the corners can be confusing. The following figure
illustrates the convention. The key point to remember is that the corners (UL, UR, LL, LR)
SOCET SET Page 46-9

are defined with respect to output image space, not ground space. Note that the generated
mosaic will be a rectangle, regardless of the shape of the quadrilateral that you enter.
Orientation of the Four Corners for Rotated Orthophoto

N Y (up)
UL UR
LL
LR
N UL Orthophoto
generated from
the quadrilateral N
Quadrilateral
formed by four
corners you LL LR
W UR enter
E X (Right)
S
Ground Space - Image Space -
You define a rotated orthophoto by entering four The orthophoto that is generated is aligned along
corner points. If the corners you enter are not a the baseline defined by the line between the UL
rectangle, the process will “round” them to a and UR corners. A rectangle is formed that
rectangle based on the UL-UR baseline. encompasses the quadrilateral you entered.
No matter how you choose the shape, you may specify an orthophoto boundary that exceeds the
extent of the input image(s). In this case, the orthophoto imagery is set to black where no input
imagery is available.
If you create an orthophoto using the four-corner method (not

“north-up”) and no DTM, you may get black areas in the
product. To circumvent this, create a flat DTM which covers the
area of your output image completely using ATE. Then select
this DTM in Orthophoto instead of the “None” option.
46.2.2.3 Corner Point Definition

In two-corner boundary mode, the lower-left corner you enter is the “origin” of the corner
definition. Orthophoto will always use the value you enter as the lower left corner of the lower-
left pixel of the orthophoto and the other corners will be an exact multiple of pixels (GSD
intervals) from this corner.
The corner locations represent the outer edges of the orthophoto pixels. For example, if you have
a ground sample distance of 4 meters and the lower left corner is (100, 200) then the lower-left
pixel extends from (100, 200) to (104, 204). And if the upper-right corner is (500, 700) then the
upper-right pixel extends from (496, 696) to (500, 700). The size of this orthophoto is 400 x 500
meters, and the number of pixels is 100 x 125.
A consequence of this convention is that you can create abutting orthophotos by entering the same
values for adjacent edges. For example, if your first orthophoto has a lower left corner of (100,
200) and an upper-right corner of (500, 700) then the abutting orthophoto of the same size to the
right (east) will have corners of (500, 200) and (900,700). The abutting orthophoto to the north
(of the same size) will have corners (100,700) and (500, 1200).

Upper-Right Pixel
N covers from (496,696)
to (500,700)
W E
Orthophoto with corners
S (100,200) and (500,700)
and GSD=4.0
Lower-Left Pixel covers from

(100,200) to (104,204)
46.2.2.4 Image Enhancement and Color Balancing

Orthophoto will perform color balancing on the input images, but you must define the necessary
enhancements for all of the input image before making the orthophoto. Here are the steps:
1. Display an input image on the main image display.
2. Use the Brightness and Contrast slider bars to achieve a visually appealing display. You
may also use the Tonal Transfer Curve (TTC) and Histogram operations. See “Image
Enhancement” on page 4-12.
3. Save these image enhancements with the Image Enhancement to File button. These are the
enhancements that Orthophoto will use.
Do not use the Commit to Disk option at this step.
4. Repeat steps 1 to 3 for all input images.

5. Run Orthophoto. It will apply the enhancements as it copies pixels from the input image to
the output image. If the image generated by Orthophoto is too bright or too dark, adjust the
brightness of the input image(s), save the parameters, then re-run Orthophoto.
The above technique will not apply a convolution, such as a sharpening filter. If you want to filter
the input image, you must resample the entire input image by using the Image Enhancement
Commit to Disk button (you may either overwrite the original image or create a new image)
before running Orthophoto. See “Image Enhancement” on page 4-12 for details.
46.2.2.5 Input DTM

You can run Orthophoto without a DTM, but—especially in hilly regions—the results will not be
as accurate as if you had a DTM.
Before running Orthophoto, you should run Interactive Terrain Editing to ensure that your input
DTM is accurate and that it covers the entire orthophoto region.

Orthophoto can accept multiple DTMs. You can also use DTM/Feature Merge to combine several
DTMs together.
If you select a DTM which has a TIN format, Orthophoto will perform special processing to
accurately transform the imagery exactly along the triangle boundaries. This provides a very
accurate rectification of the terrain in the orthophoto. However this processing takes extra time.
If you do not want the special TIN processing, disable it with the “Process TIN DTM as Grid”
button on the Options pulldown. Disabling the special TIN processing will cause the image to be
treated in small square patches and will not reflect the DTM triangle geometry.
46.2.3 Feature Database Considerations

Care must be taken when you are extracting the features so that the edges of your polygons lie
outside the buildings. If the edge is drawn such that part of the building is outside of the polygon,
that portion of the building imagery will remain in the orthophoto as an artifact. These artifacts
are usually seen as lines at the border between the original orthophoto and the areas where other
images were used to fill in.
It is only necessary to draw rooftops of vertical features. Drawing the sides is optional. Non-
planar surfaces must be subdivided into multiple planar elements.
46.2.3.1 GeoTIFF Output

You can generate GeoTIFF files directly by checking Construct GeoTIFF Tags on the Options
Tab, and selecting TIFF, TIFF Tiled, or TIFF Tiled Chunky on the image format pull-down
(Output Tab). If your project is LSR, the GeoTIFF will contain “Undefined” as the GeoTIFF
mode/type. Otherwise the GeoTIFF data will match the project.
GeoTIFF generation is possible for any project which has a GeoTIFF code defined in the internal
database. If your project is geographic, look at internal_dbs/GEODETIC/datum.dat and
find the datum of your project. If the datum has a non-zero number after it, then your project can
be used to generate GeoTIFF. For grid projects, find your project’s grid definition in
internal_dbs/GEODETIC/grid_parameters. If the last line of the definition has a
non-zero code for the GEOTIFF value, then you can use that project for generating GeoTIFF
images. You can also enter new grids and use them for generating GeoTIFF orthophotos. Follow
the directions at the top of the file and put the proper grid code on the GEOTIFF line.
46.2.3.2 Sample
Here is an example of a sample execution to create a UTM zone 14 project with NAD83 datum:
1. Edit internal_dbs/GEODETIC/grid_parameters.
2. Find the existing UTM zone 14 WGS84 grid entry.
3. Copy it to the bottom of the file (before “END”).
4. Edit the GRID_TYPE to a new name Note: Don't put “UTM” in the name or it won't appear
in the Create Project Menu.
5. Find another grid with NAD83.
6. Copy from “DATUM_NAME” to the end of the line into the new grid. Be careful that your
editor does not insert a line break. Everything from “GRID_TYPE” to “ERROR n n n”
should be on one line.
7. Find the GeoTIFF code in the GeoTIFF spec.
8. Change the code in the new grid. The entry should look like:

# utm: zone 14 northern NAD 83
GRID_TYPE Custom DATUM_NAME [NAR-C]_NAD_83(CONUS) DATUM

6378137.0
0.006694380022 OFFSET 0 0 0 ERROR 2 2 2
PROJECTION_TYPE UTM_PROJECTION
ZONE 14
F_NORTH_POS 0 F_NORTH_NEG 0 F_EAST_POS 500000 F_EAST_NEG

500000
GEOTIFF 26914
9. Run Create/Edit Project.

10. Select Grid/State Plane > General.
11. Find the grid you created above in the list and select it.
12. Save the project.
13. Use the new project to create your GeoTIFF products.
You can find the grid code in section 6.3.3.1 of the GeoTIFF specification. This is available at:
http://www.remotesensing.org/geotiff/spec/contents.html
The other TIFF characteristics of GeoTIFF images are the same as Tiled TIFF. See “Image Import
and Export,” Chapter 7 for details.
If you set up a UTM project with Create/Edit Project and change

the datum to non-WGS84, you cannot use the project for
GeoTIFF output. Create a new grid definition for this situation.
Here is a sample listing of GeoTIFF tags for an orthophoto in a geographic and grid project:
Geotiff_Information:
Version: 1
Key_Revision: 1.2
Tagged_Information:
ModelTiepointTag (2,3):
0 0 0
-117.215664 32.7434048 0
ModelPixelScaleTag (1,3):
0.000639935258 0.000541031466 0
End_Of_Tags.

Keyed_Information:
GTModelTypeGeoKey (Short,1): ModelTypeGeographic
GTRasterTypeGeoKey (Short,1): RasterPixelIsArea
GTCitationGeoKey (Ascii,21): “SOCET-SET Geographic”
GeographicTypeGeoKey (Short,1): GCS_WGS_84
GeogLinearUnitsGeoKey (Short,1): Linear_Meter
End_Of_Keys.
End_Of_Geotiff.
Geotiff_Information:
Version: 1
Key_Revision: 1.2
Tagged_Information:
ModelTiepointTag (2,3):
0 0 0
483277.5 3625173.5 0
ModelPixelScaleTag (1,3):
15 15 0
End_Of_Tags.
Keyed_Information:
GTModelTypeGeoKey (Short,1): ModelTypeProjected
GTRasterTypeGeoKey (Short,1): RasterPixelIsArea
GTCitationGeoKey (Ascii,18): “SOCET-SET UTM_11N”
ProjectedCSTypeGeoKey (Short,1): PCS_WGS84_UTM_zone_11N
ProjLinearUnitsGeoKey (Short,1): Linear_Meter
End_Of_Keys.
End_Of_Geotiff.
By default, if your input images have greater than 8 but less than 16 bits of resolution Orthophoto
will map up all pixels to 16 bit values. This ensures compatibility with other systems which only
import 8 or 16 bit values. If you wish to bypass this conversion, set the environment variable
“DONT_MAP_UP_MOSAIC” to “YES”. You can do this by adding a line to your initialization
file, which is “socet_config.bat” on Windows and “.socet” on Unix.
set DONT_MAP_UP_MOSAIC=YES (Windows)

-setenv DONT_MAP_UP_MOSAIC YES (Unix)
46.2.3.3 NITF Georeferencing

If you select NITF as your output format, Orthophoto automatically places georeferencing
information into the IGEOLO tags in the output file NITF header so you can export your product
to other systems.
46.2.3.4 World Files

Orthophoto automatically creates World files for the orthophoto. They will be co-located with the
output pixel file. The file name is the same as the pixel file with a “w” appended to the end, except
for TIFF, whose extension is “.tfw”.
46.2.3.5 Report File

Orthophoto generates a report file containing various data about the orthophoto for every run. The
report file is stored in the project data directory and is named the same as your mosaic, except
with a “.rep” file extension.
46.3 Execution - Orthophoto

The following steps define the sequence you follow to generate an orthophoto image:
1. Click Products > Orthophoto Generation on the main workstation window.
2. If you have not already loaded a project on the workstation, you must by clicking File->
Load Project....
While running Orthophoto, you cannot change the project. If

you need to execute Orthophoto function on another project,
you have two options:
1. Use the main menu to change to the desired project, then run the
function again;
2. Activate the function from a command line (in a shell window) by
starting the function’s executable, namely orthophoto, with
start_socet -single... as described in the Batch Processing.
3. To select input Image Support files, go to the input tab and move the desired files from the
Available list to the Selected list. Choose desired files (hold down <ctrl> to add multiple
files), then click the right arrow. Files selected will be displayed in the Image(s) Selected
section.
4. [Optional] Remove any files from the list that you highlighted, by highlighting them in the
Selected list and moving them to the Available list.
5. [Optional] View the Support file information by highlighting a file from the list and then
right clicking View Info....
6. Click Use DTM(s). to select the DTM file(s). Select a DTM file name from the Available
list and click the right arrow to move it to the Selected list Hold down control to select
multiple DTMs.
7. Click the Options Tab on the Orthophoto Generation window to select your options for
Stereo Mate, Interpolation Method, Grid Lines, Auto Minify, Auto Load Imagery,
Footprint Entry or Background Color.

8. [Optional] Click 3D Features... on the Input Tab to select a Feature Database. Select the
name of a feature database file and click OK.
9. Enter the name, location, and format of the output image in the Output Image field.
10. Enter the ground sample distance of the orthophoto, followed by a carriage return. The
Output Lines and Samples update to reflect your entry.
If you desire to achieve a specific scale on a particular

hardcopy output device, you may want to enter an exact
ground sample distance (units/pixel), which when printed on
the plotter will be a precise scale. If this is the case use the
formula below:
GSD = units/pixel = SCALE / (dpi * 12)
where SCALE = scale inverse (e.g., for a scale 1:5000 enter 5000)
dpi = dots per inch (e.g., IRIS accepts dpi of 200, 240, and 300)
12 = used for GSD entry in feet.
If you are in a project whose units is meters, the ground sample distance is entered in
meters. For the example here, multiply by 0.3048 if you want to convert from feet to meters.
11. Fill in the Output Boundary corners by selecting either DTM, Input Images, Draw
Polygon... or by editing the corner fields as desired. Remember the corners must be the
clockwise corners of your desired output orthophoto. Enter either two or four corners,
depending on the option you selected.
12. Click Start to begin generating the orthophoto. A percent complete display indicates the
status of processing.

46.4 Batch Process - Orthophoto

COMMAND LINE:
% start_socet -single orthophoto -batch -s setting_file
orthophoto ortho
project Project filename (select from the .prj files in <install_path>/

data).

image Input image support file (select from the .sup files in your project
directory). Repeat multiple times for the replacement imagery file in True
Orthophoto. Repeat once for the alternate image in Multispectral Merge or
Change Detection.
Select more than one support file only if you are running True Orthophoto,
Multi-Spectral, or Change Detection.
use_dtm Use DTM flag (YES or NO).
dtm Input DTM. (selected from the DTMs in your project directory).
elevation Elevation for flat DTM if use_dtm is NO (floating point, in project

units).
auto_boundary [Optional] Set this to DTM or IMAGES to automatically set the border to
match the footprint of the input DTM or the input image, respectively. If
you set this to DTM or IMAGES, you do not have to specify
foot_entry or any of the corner keywords.
BLANK SPACE
You can also set this to DOQ to make the boundary to a DOQ full or
quarter-quadrant and specify ul_x and ul_y in DD:MM:SS for the
DOQ quadrant you want to use.
foot_entry Footprint entry by lower-left/upper- right or by four corners (TWO or

FOUR). If you set this to “TWO” you only need to specify the lower-left
and upper-right output corners.
NOTE: If you set foot_entry to TWO, you only need to specify ll_x,
ll_y, ur_x, and ur_y.
ul_x Input MBR upper-left corner x coordinate (in project units). If

auto_boundary is set to DOQ, this will be the upper -left longitude in
DD:MM:SS.
ul_y Input MBR upper-left corner y coordinate (in project units). If

auto_boundary is set to DOQ, this will be the upper-left latitude in
DD:MM:SS.
ul_x Input MBR upper-left corner x coordinate (in project units).
ul_y Input MBR upper-left corner y coordinate (in project units).
ur_x Input MBR upper-right corner x coordinate (in project units).
ur_y Input MBR upper-right corner y coordinate (in project units).
ll_x Input MBR lower-left corner x coordinate (in project units).
ll_y Input MBR lower-left corner y coordinate (in project units).
lr_x Input MBR lower-right corner x coordinate (in project units).
lr_y Input MBR lower-right corner y coordinate (in project units).
doq_size [Optional] FULL for a 15 minute DOQ or QUARTER for a 7.5 minute
DOQ. Used when auto_boundary is set to DOQ.
doq_overedge [Optional] DOQ over-edge in meters. This is the extra area between the
geographic corners and the actual edge of the image. Used when
auto_boundary is set to DOQ.
fdb_file [Optional] True Orthophoto feature database (select from the feature
databases in your project directory).

gsd Output GSD value (floating point, in project units).
pix_size_x (Optional) GSD values for X and Y. These override the value for the “gsd”
pix_size_y keyword. Use radians in geographic projects, otherwise use project units.
file_format Output image format. See “Data Handling Capabilities” on page 7-3. If
keyword listed in the “Batch Name” column.
construct_geotiff Set to “YES” to add GeoTIFF tags to the output pixel file. Also set
file_format to img_type_tiff, img_type_tiff_tiled, or
img_type_tiff_tiled_chunky if you want GeoTIFF output.
output_file Name of output image and support file (no path or extension).
output_location Name of output image location from

auto_min [Optional] Automatically minify output orthophoto (YES or NO). Default
is YES.
interp Interpolation type (BILINEAR, NEAREST_NEIGHBOR, or

BI_CUBIC).
grid_btn [Optional] Draw grid lines flag (YES or NO).
grid_int [Optional] Output grid interval spacing (floating point, in project units).
grid_grey [Optional] Output grid gray level (integer, 0-255, where 0=black and
255=white).
background_color [Optional] Color for pixels not covered by input imagery or outside the
DTM (BLACK or WHITE). Default color is BLACK.
use_tin_map [Optional] Set to YES to enable rigorous TIN DTM processing. Set to NO
to treat TIN as a grid type (faster). Default is NO.
allow_dense_dtm [Optional] When “YES’, Orthophoto uses the DTM post spacing as a
processing increment. When “NO”, Orthophoto will not allow the
processing increment to become too dense, which results in the best
processing speed and memory consumption. Default is “NO”.
disable_multi_ [Optional] Set to YES to disable multi-threading processing. Set to NO to

threading run with multi-threading (faster for multi-CPU platforms). Default is
YES.
NOTE: Multithreading is a beta feature. It will work with most but
not all mosaic scenarios.
task Ortho type (CONVENTIONAL, TRUE_ORTHO, MULTI_SPECTRAL, or

CHANGE_DETECT). The default is CONVENTIONAL.
46.5 Next Step

You can review the orthophoto by loading it onto a monitor by clicking File > Load Images on
the main workstation window. Alternatively, you may toggle the Auto Load Imagery to on by
clicking Auto Load Imagery on the Options tab, prior to clicking Start and the orthophoto will
be automatically loaded when processing completes.

You can begin mosaicking the orthophotos you have produced thus far. See “Mosaic,”
Chapter 49 for more details.

Chapter 47
Multi-Spectral Image Sharpening

Multi-Spectral Image Sharpening is designed to enhance the
resolution of a Multi-Spectral (color) image.
47.1 Overview
Multi-Spectral Image Sharpening enhances the resolution of a Multi-Spectral (color) image by
combining it with a high-resolution gray-level (panchromatic) image.
47.1.1 When to Use Multi-Spectral Image Sharpening

You use Multi-Spectral Image Sharpening when you have two images of the same region, one
color and one gray-shade. The gray shade image should be higher resolution (that is, have a
smaller GSD) than the color image. At present, only the first three bands of the color image are
processed.
For example, say you have a SPOT color image with 20 meter resolution, and a panchromatic
aerial photograph with 5 meter resolution. Multi-Spectral Image Sharpening will combine these
two images to produce a color image with 5 meter resolution.
Before running Multi-Spectral Image Sharpening, you should register the two input images
together with Triangulation, although this may be skipped if you have high-quality support data.
If possible, you should obtain a DTM covering the region encompassed by the image; you can
either import a DTM or run ATE.
47.1.2 Registration
To get good results with Multi-Spectral Image Sharpening, you should triangulate the two input
images with Triangulation before running Multi-Spectral Image Sharpening. If you do not have
any control points, run Triangulation in the relative orientation mode. If you do not run
triangulation on the two input images, the results of Multi-Spectral Image Sharpening may
contain undesirable artifacts.
47.1.2.1 DTM Input

In areas that are hilly, you should input a DTM to Multi-Spectral Image Sharpening. If you do not
have a DTM and your imagery is oblique of a hilly area, the results of Multi-Spectral Image
Sharpening may contain undesirable artifacts.
SOCET SET Page 47-1

Chapter 47 - Multi-Spectral Image Sharpening
47.1.3 Multi-Spectral Image Sharpening Data Flow:
COLOR GRAY-SHADE DTM

IMAGE IMAGE (optional)
COLOR-GRAY
MERGE
OUTPUT OUTPUT
IMAGE SUPPORT FILE
Multi-Spectral Image Sharpening will accept any image as the

color image other than pseudocolor types.
47.1.3.1 Output Image

The image generated by Multi-Spectral Image Sharpening is a geo-referenced orthophoto. The
output image includes the support data necessary to perform geo-location, so you can display the
output image on the main image display and perform mensuration operations on it. The output
image will have North up.
You specify the resolution of the output image by entering a Ground Sample Distance (GSD) in
the Multi-Spectral / Gray Merge window.
The extent of the output image is determined as follows: If you input a DTM, the output image is
the size of the DTM; otherwise the output image is the size of the input images. In either case,
you can override this default size by simply typing in the corners you want in the Multi-Spectral
/ Gray Merge window.
The output of Multi-Spectral Image Sharpening is a Multi-Spectral image that is a combination
of the two input images. The color value of each pixel in the output image is obtained as follows:
the location of the output pixel is mapped back into both input images. A color value is obtained
by interpolating the neighboring pixels in the input color image, and an intensity is obtained by
interpolating the neighboring pixels in the input panchromatic image. This color and intensity are
combined to yield the output pixel value. This process is repeated for each pixel in the output
image.
47.1.4 User Inputs

The User Inputs of Multi-Spectral Image Sharpening are identical to the inputs of Orthophoto.
See “Orthophoto,” Chapter 46 for details.
Page 47-2 SOCET SET

47.1.4.1 Multi-Spectral Color Merge
The Multi-Spectral window’s selections are as follows:
orthophoto in stand-alone mode.
SELECT TO

Multispectral Image Ensure that this radio button is selected.
Sharpening
SOCET SET Page 47-3

SELECT TO

Info... BLANK SPACE
BLANK SPACE
BLANK SPACE
BLANK SPACE
DTMs
BLANK SPACE
BLANK SPACE
Clear Selections
BLANK SPACE
BLANK SPACE
Not used for Color Merge.
3D Feature
Name NOTE: Change Detection places an extension of “.img” on the
Location name regardless of the image format.
Format Enter the (GSD) Ground Sample Distance to be used when generating the
JPEG Quality orthophoto image. Entry must be in the project units. You must enter the
GSD GSD before processing can begin. Press the Return key to update the Lines
Lines and Samples fields. This will update the footprint and the number of lines
and samples which will be output. Note that the footprint may change
Samples slightly as the corners are made to be the nearest multiple of the ground
sample distance.
Mosaic, you must ensure that the GSD matches the mosaic layer
GSD, and that the orthophoto is not rotated from North.
Enter the number of lines to be output in the orthophoto.
Four Corners corners. For Four Corners, you enter all four corners. See “Output
BLANK SPACE Boundary” on page 47-4 for additional information.
Lower Left,
BLANK SPACE
Lower Right
Page 47-4 SOCET SET

SELECT TO

boundary
BLANK SPACE
Options BLANK SPACE
File BLANK SPACE
Create Ortho Create an ortho info file.
Info File BLANK SPACE
BLANK SPACE Automatically create a minified image pyramid from the resulting
Auto Minify orthophoto after the processing completes.
Auto Load Automatically load the image when processing is complete.
Imagery BLANK SPACE
Construct Create GeoTIFF tags in the output.
GeoTIFF
Tags BLANK SPACE
Color BLANK SPACE
BLANK SPACE Bilinear or Nearest Neighbor. The interpolation method that is to be used
Interpolation Method when resampling pixels into the orthophoto. Note that if you are
Stereo Mate Not used in Color Merge.
SELECT TO
Project... Prompt you to select a project file. This choice is only available if you are
running Orthophoto in stand-alone mode.
SOCET SET Page 47-5

SELECT TO
Input Images Prompt you to select the Image files to be use. Adds the file you picked to
Add... the list of input files.
NOTE: You can pick more than one file name in the selection list.
Only the first selected image is used unless a feature database is
named in the 3D Features field (True Orthophoto).
Remove Remove the highlighted Image files from the selection list.
NOTE: You can pick more than one file name at a time to be
removed.
View Image Info. Bring up the Image Information window for the highlighted DTM.
Build List Using Build a list of input Image files that have an MBR which is inside of or
Output Boundary intersects with the MBR specified by the user in the Output Boundary.
DTM Tell Orthophoto whether to use a DTM when producing the orthophoto. If
Toggle On, you must select a DTM(s). If Off, you must enter an elevation in the
Elevation field.
Use DTM... Prompt you to select the DTM to use.
NOTE: When starting Orthophoto stand-alone, you must toggle
the “Use DTM...” button to the value you want, even if it already
appears correct.
Elevation Enter the orthophoto elevation if you selected the No DTM option. This is
useful for making orthophotos in flat terrain or for running orthophoto
recursively.
Output Image Specify the name, location, and format of the output image.
Name, Location, NOTE: Orthophoto places an extension of “.img” on the name
Format regardless of the image format.
GSD Specify the Ground Sample Distance to be used when generating the
orthophoto image. Entry must be in the project units. You must enter the
GSD before processing can begin. Press the Return key to update the Lines
and Samples fields. This will update the footprint and the number of lines
slightly as the corners are made to be the nearest multiple of the ground
sample distance.
Lines Specify the number of lines to be output in the orthophoto.

Samples Specify the number of samples to be output in the orthophoto.
Output Boundary Specify Orthophoto’s corners. You can either manually enter coordinates
Upper Left, or use the Method and Update buttons to set them. Use the Footprint Entry
Upper Right, selection on the Options pulldown to control whether you enter UR and LL
or all four corners.
Lower Left,
BLANK SPACE
Lower Right
DTM Use the minimum bounding rectangle of the selected DTM(s) to update the
Output boundary.
Input Images Use the minimum bounding rectangle of the footprints of the selected
Image file to update the Output boundary.
Page 47-6 SOCET SET

SELECT TO
Polygon... Draw a polygon and use the corners as the Output boundary.
See “DTM Properties” on page 35-7 for a description on a typical drawing
scenario.
DOQ Use a geographic upper-left corner to make Mosaic compute a DOQ sized
boundary. DOQs are spaced on regular 7.5 (quarter-quad) or 15 (quad)
minute intervals.
Update Calculate the output boundary based on the DTM(s), Input Images,
Polygon, or DOQ selection.
47.2 Execution - Multi-Spectral Image Sharpening

The following steps define the sequence you follow to run Multi-Spectral Image Sharpening:
1. [Optional] Ensure that the two input images are registered by running Triangulation.
2. [Optional] Obtain a DTM of the region.
3. Click Products > Multi-Spectral Image Sharpening on the main workstation window.
a. If you have a DTM available, select it on the Input tab, under the DTM(s) group box
and move it to the Selected box.
b. If you don’t have a DTM, select the “Use Elevation” radio button and input an
approximate elevation in the Elev. field.
4. Add image files by highlighting them in the Available list and clicking the right arrow to
move them to the selected list. Files selected will be displayed in the Selected Images
section.
5. [Optional] Remove any files from the list by highlighting them, then clicking the left arrow
to move them to the Available box.
6. [Optional] View the Support file information by highlighting a file from the list, then right
click View Info....
8. Enter the ground sample distance of the output image, followed by a carriage return. The
9. [Optional] If you want to specify the extent of the output image, edit the Lower-Left and
Upper-Right Corners text fields.
10. Click Start to begin generating the output image. A percent complete display indicates the
12. Validate the output by Change Detection loading the output image onto the main image
display.
13. Repeat steps 3 to 11 as needed. When processing completes, click File > Exit to close the
Multi-Spectral Image Sharpening window.
SOCET SET Page 47-7

Chapter 48
Change Detection
Change Detection compares two images of an area and
generates a product that indicates where the two images
differ.
48.1 Overview
Typically, Change Detection is used to compare two images taken at two different times, so you
can see where major changes have occurred, such as building construction, forest clear-cutting,
and road re-routing.
48.1.1 When to Use Change Detection

You use Change Detection when you have two images of the same region, taken at two different
times, and you want to compare the two.
Before running Change Detection, you should register the two images together with
Triangulation, although this may be skipped if you have high-quality support data. If possible,
you should obtain a DTM covering the region encompassed by the image; you can either import
a DTM or run ATE.
48.1.1.1 Registration
To get good results with Change Detection, you should triangulate the two input images with
Triangulation before running Change Detection. If you don’t have any control points, run
Triangulation in the relative orientation mode. If you don’t run Triangulation on the two input
images, the results of Change Detection may contain undesirable artifacts.
48.1.1.2 DTM Input

In areas that are hilly, you should input a DTM to Change Detection. If you don’t have a DTM
and your imagery is oblique of a hilly area, the results of Change Detection may contain
undesirable artifacts.
SOCET SET Page 48-1

Chapter 48 - Change Detection
48.1.2 Change Detection Data Flow
IMAGE(S) DTM
(optional)
CHANGE
DETECTION
OUTPUT OUTPUT
IMAGE SUPPORT FILE
Change Detection only accepts 8-bit single-band images.
48.1.3 User Interface

The User Inputs of Change Detection are identical to the inputs of Orthophoto.
See “Orthophoto,” Chapter 46 for details.
48.2 Change Detection
Page 48-2 SOCET SET

The Change Detection window’s selections are as follows:
Change Detection in stand-alone mode.
SELECT TO

Change Detection Ensure that this radio button is selected.
Info... BLANK SPACE
BLANK SPACE
BLANK SPACE
BLANK SPACE
DTMs
BLANK SPACE
BLANK SPACE
Clear Selections
BLANK SPACE
BLANK SPACE
Not used for Change Detection.
3D Feature
Name NOTE: Change Detection places an extension of “.img” on the
Location name regardless of the image format.
Format Enter the (GSD) Ground Sample Distance to be used when generating the
JPEG Quality orthophoto image. Entry must be in the project units. You must enter the
GSD GSD before processing can begin. Press the Return key to update the Lines
Lines and Samples fields. This will update the footprint and the number of lines
Samples slightly as the corners are made to be the nearest multiple of the ground
sample distance.
Enter the number of lines to be output in the orthophoto.
SOCET SET Page 48-3

SELECT TO

Four Corners corners. For Four Corners, you enter all four corners. See “Output
BLANK SPACE Boundary” on page 48-4 for additional information.
Lower Left,
BLANK SPACE
Lower Right

boundary
BLANK SPACE
Options BLANK SPACE
File BLANK SPACE
Create Ortho Create an ortho info file.
Info File BLANK SPACE
BLANK SPACE Automatically create a minified image pyramid from the resulting
Auto Minify orthophoto after the processing completes.
Auto Load Automatically load the image when processing is complete.
Imagery BLANK SPACE
Construct Create GeoTIFF tags in the output.
GeoTIFF
Tags BLANK SPACE
Color BLANK SPACE
BLANK SPACE Bilinear or Nearest Neighbor. The interpolation method that is to be used
Interpolation Method when resampling pixels into the orthophoto. Note that if you are
Page 48-4 SOCET SET

SELECT TO
Stereo Mate Not used in Change Detection.

48.3 Output Image

The image generated by Change Detection is a geo-referenced orthophoto. The output image
includes the support data necessary to perform geo-location, so you can display the output image
on the main image display and perform mensuration operations on it. The output image will have
North up.
You specify the resolution of the output image by entering a Ground Sample Distance (GSD) in
the Change Detection window.
The extent of the output image is determined as follows: If you input a DTM, the output image is
the size of the DTM; otherwise the output image is the size of the input images. In either case,
you can override this default size by simply typing in the corners you want in the Change
Detection window.
The output of Change Detection is a gray-level image that is a pixel-by-pixel subtraction of the
two input images. Areas that have the same value in both input images are medium gray (pixel
value 128) in the output image. In areas where the input images differ, the output image will be
either darker gray (if the first image is darker than the second image) or light (if the first image
is lighter). The darkness/lightness of the out put pixels is a function of how much the input images
differ.
SOCET SET Page 48-5

48.4 Execution - Change Detection

The following steps define the sequence you follow to run Change Detection:
1. [Optional] Ensure that the two images are registered by running Triangulation.
2. [Optional] Obtain a DTM of the region.
3. Click Products > Change Detection on the main workstation window.
a. If you have a DTM available, select it on the Input tab, under the DTM(s) group box
and move it to the Selected box.
b. If you don’t have a DTM, select the “Use Elevation” radio button and input an
approximate elevation in the Elev. field.
4. Add image files by highlighting them in the Available list and clicking the right arrow to
move them to the selected list. Files selected will be displayed in the Selected Images
section.
5. [Optional] Remove any files from the list by highlighting them, then clicking the left arrow
to move them to the Available box.
6. [Optional] View the Support file information by highlighting a file from the list, then right
click View Info....
8. Enter the ground sample distance of the output image, followed by a carriage return. The
9. [Optional] If you want to specify the extent of the output image, edit the Lower-Left and
Upper-Right Corners text fields.
10. Click Start to begin generating the output image. A percent complete display indicates the
12. Validate the output by loading the output image onto the main image display. Since the
pixel values in the output image are clustered around medium gray (meaning no change)
you should increase the Contrast in the main image Display Utility window in order to
highlight the changes between the two images.
13. Repeat steps 3 to 11 as needed. When processing completes, click File > Exit to close the
Change Detection window.
Page 48-6 SOCET SET

These two images of San Diego

were taken about one minute apart.
Change Detection produces gray-

shade images that are a result of
pixel-by-pixel subtraction.
New aircraft positions appear as

bright regions; previous positions
appear as dark regions: medium
gray areas indicate no change.
SOCET SET Page 48-7

Chapter 49
Mosaic
Mosaic is a single function for the generation of ortho-
corrected and mosaicked images.
49.1 Overview
In SOCET SET, a mosaic is an orthogonally corrected image produced (resampled) from one or
more input images. An orthographic projection (parallel to Z axis) is used to project object space
(ground space) to the output mosaic space. The mosaic process corrects the input images for all
distortions due to camera geometry, terrain relief, radiometric adjustments, and radiometric seam
feathering. The output image represents what you would see if you were looking straight down at
the ground from an infinite distance above.
Camera Original Images

Camera
Seam Line
Ortho-Mosaic
DTM
Its typical inputs include one or more controlled (triangulated) images or ortho-corrected images,
a Digital Terrain Model (DTM) file, a feature database of seam polygons, and an output boundary.
Many of the inputs are optional and there are several options for radiometric balancing and
feathering.
Mosaic can be run in batch or through the user interface. It permits making mosaics a “sheet at a
time” from multiple images or single images as well as very large mosaic files. The options for
SOCET SET Page 49-1

Chapter 49 - Mosaic
joining the images include polygonal joining, most nadir joining, radiometric joining, and order
of input (precedence). The most nadir option minimizes errors due to relief displacement since it
uses the most orthogonal regions of each input image.
Mosaic has the unique capability to automatically balance the multiple input images for
systematic differences caused by vignetting and hot spots as well as histogram enhancements.
This is critical when mosaicking images of varying radiometric quality.
Mosaic is N bands in, N bands out and up to 2 byte in, 2 byte out. It will automatically generate
a mosaic with the number of bands and bytes equal to the number of bands and bytes (up to 2) in
the input imagery.
Mosaic permits the input of different types of images from different types of sensors and at
different Ground Sample Distances (GSD). Since you can choose the output pixel size or ground
sample distance, you can quickly create an overview of your mosaic for quality checking and
refining your inputs.
The following is a list of options/capabilities:
• Outputs any ground sample distance (pixel size).
• Constructs seamlines with “nearest nadir,” “radiometric,” or “input order
(precedence),” methods. Can also use a feature file containing seam polygons (a
polygon region for each input image).
• Crops the output on polygonal boundaries.
• Creates an output boundary of 2 or 4 points at any rotation angle.
• Re-samples images with nearest neighbor, bilinear, or bicubic methods.
• Can work without a DTM, using a single elevation for the correction surface.
• Inputs controlled images or orthophotos or mosaics.
• Automatically balances the images during mosaicking.
• Feathers imagery along the seams to reduce seam visibility.
• Combines black and white or color images from different sensor types and
resolutions.
• Uses any project coordinate system including geographic.
• Can cut the output mosaic into rectangular “sheets”
49.1.1 When to Use Mosaic

Prior to running Mosaic, you must import and control the input image(s).
You can run Mosaic with or without an input DTM. You can either import a DTM, or create one
with Automatic Terrain Extraction. If you have a DTM, it should be large enough to cover the
desired Mosaic area. If you have several small DTMs covering the region, you can use DTM/
Feature Merge to merge them into a single DTM prior to running Mosaic, or you may select
multiple DTMs during run time.
If you do not have a DTM, you must specify an elevation. Mosaic rectifies (corrects) the input
images to the project coordinate system at the elevation you specify.
If you want the mosaic constructed with polygonal join lines, you can use Feature Extraction, if
you have a Feature Extraction license, or the Seamline Editor to delineate a polygon for each
Page 49-2 SOCET SET

Chapter 49 - Mosaic
input image. This seam polygon database is then used by Mosaic to join the images in the output
space.
You can, optionally, input orthophotos or True orthophotos made from the Orthophoto
Generation function. After creating the Mosaic, you can use Image Map to add marginalia and
overlay graphics.
49.1.2 Data Flow
FEATURE
IMAGE(S) DTM DATABASE
(optional) (optional)
MOSAIC
OUTPUT OUTPUT
MOSAIC SUPPORT FILE
49.2 Mosaic
Mosaic has five tabs which will help guide you through the task. The tabs provide a logical work
flow as you progress from left to right.
49.2.1 Start
SOCET SET Page 49-3

Chapter 49 - Mosaic
The Mosaic window’s selections are as follows:
File > Load Project Load a new Project.

File > Save Settings Saves all the current GUI’s settings.
File > Exit Exit the application.
SELECT TO
Start Decide what task the user wants to complete.

Setup Enter Output Boundary and Sheet Setup information if creating multiple
sheets.
Input Choose Input images and DTMs. Preview all footprints.
Output Select output names of sheets, mosaic, seam file, ASCII sheet file, GSD,
format, location, and creation of World and Ortho Info files.
Task BLANK SPACE
Create Multiple Sheets Create multiple sheets during processing without making an entire mosaic.
Create Entire Mosaic Create a mosaic from all of your input images.
Create Seams Only Create a seam database only.
49.2.2 Setup
Page 49-4 SOCET SET

Chapter 49 - Mosaic
The Setup tab’s selections are as follows:
SELECT TO
Sheet Method Allows for entry of the coordinates and setup information for the mosaic
sheets.
Use Manual to allow entry of the Output Boundary and Sheet Setup
manually into the Setup GUI.
Use Input File to select a file containing defined boundaries for the sheet.
The ASCII text file contains one sheet per line with -99 between sheets.
An example of the format is as follows:
Where sheet1 and sheet2 are the output sheet image and support file
names. UL, UR, LR, and LL are the upper left, upper right, lower right
and lower left coordinates for sheet1 and sheet2. The X Y ground
coordinates in the project coordinate system and units for the sheet
boundaries follow UL, UR, LR, and LL. The ground coordinates must be
in X Y order. If the LR and UL coordinates are missing, they are computed
from the LL and UR coordinates.
Use Azimuth to enter a starting point and rotation azimuth for the sheets.
NOTE: This group only applies if you are creating multiple sheets.
Origin Select the upper left or lower left from which to calculate your sheets. You
must enter a coordinate from which to start calculating your sheets.
Output Boundaries Enter coordinates for the entire mosaic or all sheets. You can select either
Lower-Left, Upper-Right, or Four Corners.
Draw Polygon Use this to draw a polygon for the output boundary in the image display.
Update From Use this to update the boundary from: Input Image, DTM, DOQ, or Seams.
Update First select the method in the cascade, then click Update.
Sheet Setup Select either pixels or project coordinates and enter the size of each sheet,
the amount of overedge, and the number of tiles/sheets.
Size Enter the size of each sheet in the units you selected in Sheet Setup.
Overedge Enter the amount of overlap between sheets.
Number of Sheets Enter the number of sheets you want to make horizontally and vertically.
You can let Mosaic compute these values by clicking “Fill to MBR”.
Fill to MBR Calculate the number of sheets from the output boundary. Be sure to enter
a size and define the output boundary before clicking this.
SOCET SET Page 49-5

Chapter 49 - Mosaic
SELECT TO
Start Begin the processing.

Start At Begin the processing at a delayed time.
49.2.2.1 Origin and Azimuth

You can select an origin and azimuth for your mosaic sheets. The origin can be anchored either
at the Upper-Left or Lower-Left corner of the entire mosaic sheets in ortho space (north up). The
coordinates of the Origin are in ground space, i.e., project units. The coordinates can either be
user-defined or automatically generated by Mosaic when the Update button is pressed to
determine the Output Boundary.
If azimuth angle is specified, the origin will remain at the same anchor point, but the sheets will
be rotated by the specified azimuth angle. Positive (+) angles will rotate the sheet in the counter-
clockwise direction and negative (-) angle rotate in the clockwise direction.
Pivot for Lower-Left Pivot for Upper-Left
Upper-Left
Lower-Left
Azimuth = +15 Degrees LL Origin Azimuth = +15 Degrees UL Origin
Page 49-6 SOCET SET

Chapter 49 - Mosaic
49.2.3 Input
The Input tab’s selections are as follows:
SELECT TO
Images Section BLANK SPACE

Available All support files in the current project directory.
Selected Images that are to be used during processing.
Filter Do a regular expression match on all files in both available and selected
lists. These can be moved by clicking the arrows.
DTMs Section BLANK SPACE
Available All DTMs in the current project directory.
Selected All DTMs that are to be used during processing.
Filter Do a regular expression match on all files in both available and selected
lists. Theses can be moved by clicking the arrows.
Use DTMs Use elevation data from DTM during processing.
Elevation An elevation to use during processing. This is only used when Use DTM is
not selected. Mosaic will use a flat DTM to generate the product.
Select Using Boundaries Automatically populate the selected lists of the images and DTMs from the
Output Boundary.
Preview Use these to select which graphics you want to display on the Main
Images Window.
DTMs
Sheets
Draw Click this to start drawing the footprints of the checked fields graphically.
Auto Draw Enable this to automatically redraw graphics whenever graphics are
refreshed on the Main Window.
SOCET SET Page 49-7

Chapter 49 - Mosaic
49.2.4 Output
The Mosaic Output tab’s selections are as follows:
SELECT TO
Sheets Section Display the available section of sheets that could be created but have been
Available un-selected. The selected section show which sheets are to be created. The
Selected filter button will do a regular expression match on both sections.
Filter
Options Section BLANK SPACE
World File: Create World files.
Ortho Info File: Create Ortho Info files.
Location: The output destination for all created image files.
Format: The format of the output images.
JPEG Quality: The JPEG quality for the output image
GSD: The ground sample distance for the output image.
Lines: The number of lines in the output image.
Samples: The number of samples in the output image.
Output Mosaic File: The name of the output mosaic file.
Output Seam File: The name of the output seam database.
Output ASCII Sheet The name of the text file containing sheet boundaries.
File:
Calculate Sheets Calculate all of the sheet names from the Sheet Setup steps. The default
name will be sheet<x_coord>_<y_coord>.sup
Old Prefix: Identify the old prefix to match on for name replacement (e.g. sheet).
New Prefix: Identify the new prefix to replace the old prefix (e.g. LAX).
Replace Replace all matches of the old prefix with the new prefix.
Page 49-8 SOCET SET

Chapter 49 - Mosaic
49.3 Options
The Options tab’s selections are as follows:
SELECT TO
Mosaic Method Use this to select the mosaic method. See “Mosaicking Methods” on
page 49-13 for a detailed explanation.
Interpolation Method Select the interpolation method that is to be used when resampling pixels
into the mosaic (Bilinear, Nearest Neighbor, or Bicubic (Fleming))
NOTE: If you are mosaicking orthophotos recursively, you may
want to use the Nearest Neighbor method; otherwise, it is not
recommended.
The Bicubic (Fleming) method uses a combination of cubic resampling and
a convolution filter which optimally enhances the image depending upon
the input characteristics.
Clip Polygon [Optional] Select a polygon feature database to clip the edge of the mosaic.
To disable, erase the text in the box.
SOCET SET Page 49-9

Chapter 49 - Mosaic
SELECT TO
Dynamic Range Adjust Use this to set up automatic or custom dynamic range adjustment. See
“Dynamic Range Adjustment (DRA)” on page 49-15 for a description of
each parameter. For custom DRA, setting a check box causes Mosaic to
use the value you type in the text box. Otherwise Mosaic will calculate an
automatic value.
Seam Feathering Enable seamline feathering and enter a width if you want Mosaic to feather
Width the mosaic seam lines. See below for a description.
Seam Smoothing Use this to enable seam line smoothing. See below for a description.
Auto Minify Automatically creates a minified image pyramid from the resulting mosaic
after the processing completes.
Auto Load Imagery When set, Mosaic will automatically load the resulting image after
processing completes.
Construct GeoTIFF Tags Enable construction of GeoTIFF tags in the output file. Also make sure
your output format is one of the TIFF types. This has no effect if you select
any non-TIFF format.
Process TIN DTM as Grid Treat a TIN terrain file as grid. This will speed up the processing, but the
rigorous processing of the TIN shape will be lost. This button has no effect
if the input DTM is a grid type.
Trim Edges Enable this to have Mosaic trim the mosaic edges to the exact footprints of
the input images. This is useful to eliminate “stairstep” edges on rotated
input or when you want the mosaic extent to exactly match the input
footprints.
Fill Voids Enable this to have Mosaic fill black (zero) pixels with alternate imagery.
Allow Dense DTM When checked, Mosaic uses the DTM post spacing as a processing
increment. When unchecked, Mosaic will not allow the processing
increment to become too dense, which results in the best processing speed
and memory consumption.
Background Color Use this to set the color for pixels not covered by input imagery or outside
the DTM to black or white.
Processes Use this to set the number of processes running.
49.3.1 Shape and Orientation of the Mosaic

There are two ways you can specify the shape and size of the output Mosaic:
1. You can specify a rectangular mosaic by entering the locations of two opposite corners
(upper-right and lower-left). This approach also yields a rectangle oriented along lines of
north-south and east-west.
2. You can create a rotated mosaic by entering all four corners of the output boundary. This
permits you to output Mosaics that are rotated with respect to the project coordinate system
north-south lines. You might use this capability, for example, to generate orthophotos that
follow transportation routes. When you define the four corners of such a quadrilateral, the
definitions of the corners can be confusing. The following figure illustrates the convention.
The key point to remember is that the corners (UL, UR, LL, LR) are defined with respect
to output image space, not ground space. Note that the generated mosaic will be a rectangle,
regardless of the shape of the quadrilateral that you enter.
No matter how you choose the shape, you may specify an mosaic boundary that exceeds the extent
of the input image(s). In this case, the mosaic imagery is set to black where no input imagery is
available.

Chapter 49 - Mosaic
Orientation of the Four Corners for Rotated Mosaic

N Y (up)
UL UR
LL
LR
N UL Mosaic
generated from
the quadrilateral N
Quadrilateral
formed by four
corners you LL LR
W UR enter
E X (Right)
S
Ground Space - Image Space -
You define a rotated mosaic by entering four The mosaic that is generated is aligned
corner points. If the corners you enter are not a along the baseline defined by the line
rectangle, the process will “round” them to a between the UL and UR corners. A
rectangle based on the UL-UR baseline. rectangle is formed that encompasses the
quadrilateral you entered.
A polygon boundary or “clip polygon” can also crop the output

image when you use a feature file with seam polygons per
input image. See “Seamline Editor” on page 49-26.
If you create an orthophoto using the four-corner method (not

“north-up”) and no DTM, you may get black areas in the
product. To circumvent this, create a flat DTM which covers the
area of your output image completely using ATE. Then select
this DTM in Orthophoto instead of the “None” option.
49.3.1.1 Corner Point Definition

In two-corner boundary mode, the lower-left corner you enter is the “origin” of the corner
definition. Orthophoto will always use the value you enter as the lower-left corner of the lower-
left pixel of the orthophoto and the other corners will be an exact multiple of pixels (GSD
intervals) from this corner.
The corner locations represent the outer edges of the mosaic pixels. For example, if you have a
ground sample distance of 4 meters and the lower left corner is (100, 200) then the lower-left
pixel extends from (100, 200) to (104, 204). And if the upper-right corner is (500, 700) then the
upper-right pixel extends from (496, 696) to (500, 700). The size of this mosaic is 400 x 500
meters, and the number of pixels is 100 x 125.
A consequence of this convention is that you can create abutting orthophotos by entering the same
values for adjacent edges. For example, if your first mosaic has a lower-left corner of (100, 200)
and an upper-right corner of (500, 700) then the abutting mosaic of the same size to the right (east)
will have corners of (500, 200) and (900,700). The abutting mosaic to the north (of the same size)
will have corners (100,700) and (500, 1200).

Chapter 49 - Mosaic
N Upper-Right Pixel
covers from (496,696) to
(500,700)
W E
Mosaic with corners
S
(100,200) and (500,700)
and GSD=4.0
Lower-Left Pixel covers from

(100,200) to (104,204)
49.3.2 Seam Feathering and Smoothing

When multiple input images are mosaicked together, differences in the images can cause visible
seams to appear in the mosaic. In order to minimize the visibility of these seams, you can enable
feathering, which will cause a gradual variation of the image brightness near the seams. When
you enable seam feather, you also enter the distance (in pixels) over which to apply the change.
This allows you to control how far Mosaic will spread the gray value difference perpendicularly
across the seam.
You can also use seam smoothing to reduce the seam visibility. Seam Smoothing is available
under the Options tab on the Mosaic window. Smoothing does a pixel level blurring of the seam
between mosaic images. Seam Smoothing will reduce the visibility of the seam but it may cause some
distortion of the image close to the seam when viewed at high magnification.
If your input images have no overlap (“butt-matched”), your

output image may have spurious black lines at the seams. This
is because feathering requires some overlap. to correct this
situation use the “Most Nadir Narrow Overlap” mosaicking
option. You might also get black lines in the output image if
your input images are butt-matched images and you select an
output GSD which is larger than the GSD of the inputs. This
might happen even if feathering is disabled. You can prevent
this by making the output GSD approximately equal to the GSD
of the input images, making the mosaic, and then running
Zoom/Scale on the output to get the correct scale.

Chapter 49 - Mosaic
Output Mosaic
Boundary
image 1 feather width
image 2
image 3
seams
49.3.3 Mosaicking Methods

You have a choice of which algorithm Mosaic will use for image selection in overlap areas:
• Most Nadir—Mosaic will choose the most nadir input image to generate the mosaic for
each block. A block is approximately the size of the DTM spacing. Mosaic analyzes the
nadir angle from the block to each image sensor to determine which image is most nadir
to its sensor at the center of that block.
If you use the Most Nadir mosaicking method, you should not
allow the boundaries of your output mosaic to extend past the
areas of valid pixels in your input images. If you let the
boundaries extend too far, your mosaic may contain irregular
edges. If you have black areas in your input images, you
should either prepare seam polygons to exclude them, or clip
them from the image using the Zoom Scale tool.
• Most Nadir Narrow Overlap—This option uses the same logic as Most Nadir but
adds a pixel-wise algorithm to select the proper image in areas where images do not
overlap by much or are “butt-matched”. This prevents voids from appearing in the
overlap areas.
Most Nadir Narrow Overlap still creates a seam database file,

but the polygon edges will not necessarily match the actual
boundaries used to create the mosaic.
• Most Nadir Narrow with DTM—This option uses the same logic as Most Nadir but
the “tilt” of each image block caused by the DTM shape is taken into account to
determine the most nadir image. This may provide a higher quality mosaic in areas
with extremely steep terrain.
• Radiometric—Mosaic starts with the most nadir seams and refines them based on the
radiometric characteristics of the images. These seams are radiometrically delineated to
avoid discrete cultural and physical features, such as buildings, lakes, and so on. You
can input values of distance between vertices and constraining width to control the
behavior of the new seam.
• Input Order—Mosaic uses the first image in the Support Files list which covers the
given area to generate the mosaic. The order of images as listed in the GUI or batch file
determines the precedence.

Chapter 49 - Mosaic
• Seam Polygons— Mosaic uses the seam polygon database to determine the covering imagery.
You can create these polygons using Feature Extraction or Seamline Editor. See
“Seamline Editor” on page 49-26.
If you check the Centerline box, Mosaic will override the nadir angle algorithm with one that
places the seams close to the center of the images' overlap. This is useful if you have images with
inaccurate footprint data causing void pixels to appear in the mosaic. It is also probably a good
choice if you are mosaicking orthophotos. The Centerline option has no effect with any mosaic
method other than Most Nadir or Most Nadir Narrow Overlap.
49.3.3.1 Radiometric Seams

Mosaic can generate radiometric seams which delineate around discrete cultural and physical
features (such as buildings or rivers). These seamlines will therefore be much less visible. Seam
vertices are placed based on image radiometry for the immediate area in the overlap to minimize
visibility. The jaggedness of the line also reduces its visibility.
The Radiometric Seams Options selections are as follows:
SELECT TO
Vertex Spacing Establish the distance between each of the vertices (measured in pixels).
Constraining Width Identifies how far away the new seamline may wander away from the old
most nadir seam. It is allowed to meander half of the distance in one
direction and half of the distance in the opposite direction. This is also
measured in pixels.
49.3.4 Input DTM

You can run Mosaic without a DTM, but the results will not be as accurate as if you had a DTM,
especially in hilly regions.
Before running Mosaic, you should run Interactive Terrain Editing to ensure that your input DTM
is accurate and that it covers the entire mosaic region.
Mosaic can accept multiple DTMs. You can also use DTM/Feature Merge to combine several
DTMs together.
Mosaic can use TIN format terrain files to rectify images with greater accuracy. See “Input DTM”
49.3.4.1 DTM Post Spacing

The post spacing of the grid DTM you use can affect the Mosaic performance. For most SOCET
SET workflows, imagery goes through triangulation and then ATE. This results in terrain posts
which are spaced 5-15 pixels apart. Mosaic is designed to work best with this scenario. However,
some workflows get the DTM from a third party, not from ATE. In this case the post spacing may
be large or small. A small spacing will slow down mosaic processing and require more system
memory. This is because mosaic processes based on small squares of pixels, whose size is equal
to the post spacing. Smaller squares means there are more squares to process, so the mosaic will
run slower and consume more memory. To compensate for this, uncheck the “Allow Dense
DTM” option in Mosaic Options. This will override the post spacing and let Mosaic run at a
normal speed. A large post spacing is not a concern because Mosaic will automatically
compensate for it.

Chapter 49 - Mosaic
If your ATE file is TIN formatted and you leave the "Process TIN as Grid" option off, Mosaic
processes on fixed squares, so you don't have to be concerned with these tradeoffs. If "Process
TIN as Grid" option is on, then Mosaic will use the "SPACING_XY" value from the DTM header.
49.3.5 Image Enhancement and Color Balancing

Mosaic has an extensive capability to adjust the radiometry of the image data. There are three
phases that can optionally be applied by Mosaic: (1) a tonal transfer lookup table for each input
image, (2) Dynamic Range Adjustment, and (3) seam radiometric feathering. These radiometric
enhancements are each optionally applied and the order of application is as stated above, i.e. tonal
transfer table, Dynamic Range Adjustment, and then seam feathering.
49.3.5.1 Setting Up Image Enhancements

The first phase (setting up the tonal transfer lookup table) is done before running Mosaic. You
can balance each input image by defining the necessary adjustments using the standard
SOCET SET image enhancements and save function. Here are the steps:
1. Display an input image on the primary view port.
2. Use the Brightness and Contrast slider bars on the Display Utility to achieve a visually
appealing display. You may also use the Tonal Transfer Curve (TTC) and Histogram
operations. See “Image Enhancement” on page 4-12.
3. Save these image enhancements by clicking Save to File on the Image Enhancement
window. These are the enhancements that Mosaic will apply first.
Do not use the Commit Changes to Disk option at this step.
4. Repeat steps 1 to 3 for all input images.

5. Run Mosaic. It will apply the enhancements as it copies pixels from the input image to the
output image. If the image generated by Mosaic is too bright or too dark, adjust the
brightness of the input image(s), save the parameters, then re-run Mosaic or use the
automatic capability within Mosaic.
See “Dynamic Range Adjustment (DRA)” on page 49-15.
the input image, you must resample the entire input image by clicking Commit to Disk on the
Image Enhancement window (you may either overwrite the original image or create a new image)
before running Mosaic. See “Image Enhancement” on page 4-12 for details.
This phase is not required; you can use the Dynamic Range Adjustment phase instead of manually
setting up the tonal transfer table.
49.3.5.2 Dynamic Range Adjustment (DRA)

A second option for radiometric adjustment is called Dynamic Range Adjust (DRA). There are
two modes of operation; Classic and Intensity Filter.
Classic
Classic DRA can be used to “balance” your images. This capability will examine all of your input
images, collect statistics within subregions, and then dynamically adjust each subregion to match
a desired characteristic for the entire mosaic. It can also balance all your input images to a
common value to mitigate problems along the seams of a mosaic. These options are all done
automatically when you select the default mode. You can also input custom values to fit the way
you want the mosaic to appear. Custom values can be used to brighten or darken, stretch or

Chapter 49 - Mosaic
compress your output mosaic. To brighten the mosaic, raise the Desired Mean value on the
Custom Dynamic Range Adjust Parameters window. To increase the contrast, raise the value of
the Desired Standard Deviation on this same window. Several other effects can also be achieved
such as shadow enhancement, and the reduction of saturated areas.
The adjustment varies across the image based upon the brightness and standard deviation of gray
levels of the local area where the adjustment is being applied. The adjustments move the local
bias/gain values towards a single bias/gain value for all images. Since this is done adaptively, it
can reduce systematic effects caused by vignetting, sun angle, hot spots, shadows, etc.
It is better in most cases to gather statistics on the input images and use them to adjust the final
output. First collect statistics on the input images by clicking Custom, which will clear the
Desired Mean and the Desired Std Deviation text boxes. Then click Compute to make Mosaic
calculate new values. Change the values according to how you want the mosaic to appear.
The Custom Dynamic Range Adjust Parameters window’s buttons and fields for the Classic mode
are as follows:
SELECT TO
Off/Default/Custom Use this to select no DRA correction, default correction, or custom

correction values.
All toggle buttons Select each toggle button down the left side to activate the user override
for the named parameter, and causes the dynamic range process to use the
value specified in the associated text widget.
Percent Skip Skip a certain percentage of the image edge when computing the image
characteristics, because images may have undesirable radiometry around
their edges. This permits better balancing. Default: 2 percent. Range: 0–20
percent.
Number of Tiles This is the number of tiles (patches) the image will be split into, both
vertically and horizontally, for DRA computation.
Step Display the increment for computing the image statistics. For example,
specifying 3 will look at every third pixel in both dimensions of the image.
Max Contrast Limit the adjustment applied to image pixels so that the average gain
applied to the pixels will not exceed this value. This prevents making low
contrast areas to contrast. Default: 2.0. Range: 0–99999.
Min Contrast Limit the gain adjustment applied to image pixels so that the average gain
will not be less than this value. This prevents undesirable compression of
high contrast areas. Default: 0.9. Range: 0–99999.
Max Gray Level Shift Allow the maximum change to average pixel gray levels. For example,
DRA might calculate a gray level change of 70 but a value of 50 here
would cause the algorithm to only shift the gray level by 50. This helps
prevent radical changes in gray level that might occur in lakes or forested
areas. Default: 50. Range:0–255.
Percent Adjustment Control how much of the final adjustment is actually applied. For example,
if the original pixel value is 10, and the new pixel value is calculated to be
50, an 80% percent adjustment parameter would allow the pixel value to
change from 10 to 42, whereas a value of 100% would produce a final
value of 50. Default: 100%. Range: 0–100 percent.
Compression Limit Specify in sigmas, and specifies the number of sigmas around the mean
that will be used as a range check. This range check prevents clipping of
gray values at 0 or 255. To reduce clipping use a smaller number. To
increase contrast and allow clipping use a larger number. Default: 3.0
sigma. Range: 1–10.

Chapter 49 - Mosaic
SELECT TO
Desired Mean Identify the value is the mean gray level to which all images will be driven
toward. This would typically be about the average of your input images. If
you want the mosaic to be brighter...this value can be set larger. This value
can be calculated automatically. Default: Calculated from overall mean
values for all images. Range: 0–255 pixels.
Desired Std Deviation Identify the value is the standard deviation of all image pixels to which
each image will be driven toward. Like the Desired Mean, this would be
typically set to the average value of your input images. If you want the
mosaic to have more contrast...this value can be set larger. Default:
Calculated from the overall standard deviations for each image. Range: 0–
255 pixels.
Color Match Enable color matching mode of DRA.
Target Colors Number of target colors for color match DRA method.
Intensity Color intensity for color match DRA method. If set to 0.0, the average
intensity of the input images will be used.
Many of these parameters overlap in their effects, and it must be emphasized that you should not
use the Custom option unless you are very familiar with DRA process.
Intensity Filter
The Intensity Filter is used to equalize hotspots corresponding to large scale intensity variations
typically caused by glare from the sun. It includes:
Vignette Filter to equalize radial brightness variations due to lens distortion in frame images.
Color Match, matches the colors of an image to those of its adjacent images.
Outlier Reject, prevents extreme color match adjustments due to shadows or sun glint in the
image overlap areas. The percentage parameter determines how large an adjustment is allowed
before being rejected.
Global Intensity Match adjusts the average brightness of each image to the average of all images
in the mosaic. This is useful when some images are dark due to clouds.
Bright/Contrast Match, adjusts the brightness and contrast of the mosaic to match the brightness
and contrast of the input images. This corrects anomalies introduced when reducing the large
scale intensity variations reduces contrast. This compensates for the resulting dullness of the
mosaic.
Output Image Filter filters out large scale per hand intensity variations in the final mosaic which
can occur when images comprising the mosaic differ in brightness.
The Custom Dynamic Range Adjust Parameters window’s buttons and fields for the Intensity
Filter mode are as follows:
SELECT TO
Off/Default/Custom Use this to select no DRA correction, default correction, or custom

correction values.
All toggle buttons Select each toggle button down the left side to activate the user override
for the named parameter, and causes the dynamic range process to use the
value specified in the associated text widget.

Chapter 49 - Mosaic
SELECT TO
Percent Skip Fill a percentage of the image at the edges with intensity values from the
un-skipped edge, because images may have undesirable radiometry around
their edges. Default: 2 percent. Range: 0–20 percent.
Number of Tiles This is the number of tiles (patches) the image will be split into, both
vertically and horizontally, for DRA computation.
Hot Spot Size This is the size in meters of illumination variations that will be treated as a
hot spot .Default 2000 meters. Range 100-20,000.
Filter Order Controls the smoothness of transitions between hot spot attenuated areas
and non-attenuated areas. Default: 40 Range: 5-60
Percent Adjust Controls the effectiveness of the Intensity Filter. Smaller values reduce the
effect of hot spot attenuation in the case where it causes artifacts. Default:
100. Range: 0–200.
Vignette Filter Reduces intensity variations due to lens distortion in frame images.
Default: On for frame images; off for all others.
Color Match Matches the colors of images to the adjacent images at the seams. Default:
Off
Oulier Reject Limits the magnitude of the color match adjustment such that shadows and
sun glint in the image overlap regions are not propagated across the rest of
the mosaic. Default: Off
Reject Percentage The maximum percentage of adjustment allowed, meaning values greater
than X% of average are rejected when calculating the Color Match
adjustment. Default: 50% Range 0-100%
Global Intensity Match Adjusts the intensity of each input image to match the average of the
images comprising the mosaic. Useful when some images are very dark
due to shadows. Default: Off
Bright/Contrast Match Reducing large scale intensity variations can make the output mosaic
appear dim and dull. This option adjusts the brightness and contrast of the
output mosaic to match that of the input images. Default: Off
Output Image Filter Reduces per band large scale intensity variations in the output mosaic
image. Useful when there is significant glare or shadows which span more
than one image. Default: Off
49.3.6 Color Match

Classic
DRA can operate in a “color match” mode which is designed to balance color (3-band) images
with varying tint. You must specify a number of target colors for this algorithm to use. The target
colors correspond to different colors of physical features in your mosaic. For example if you have
an area with soil (brown), corn fields (green), and pavement (gray) you would set target colors to
3. You can also specify an intensity value to guide the output intensity.
Intensity Filter
DRA uses overlap regions to determine the color differences between adjacent images and
compute and apply a transform to match the colors across the images. Overlapping, ortho-
rectifiable images are required for this functionality. This works best with a good DTM.

Chapter 49 - Mosaic
49.3.7 Matching Mosaic Dynamic Range Adjust Parameters

You can have Mosaic calculate values for Dynamic Range Adjustment and reuse them for other
mosaics.
1. Decide which mosaic you think has the best radiometry. Set up Mosaic for this image. Click
Custom then Compute.Mosaic will calculate values for Mean and Standard Deviation.
2. Run the subsequent mosaics by leaving Custom enabled.
49.3.8 GeoTIFF Output

GeoTIFF is available for Mosaic. See “GeoTIFF Output” on page 46-12 for details.
49.3.9 NITF Georeferencing

If you select NITF as your output format, Mosaic automatically places georeferencing
information into the IGEOLO tags in the output file NITF header so you can export your product
to other systems.
49.3.10 World Files

Mosaic can create World files for the output. They will be co-located with the output pixel file.
The file name is the same as the pixel file with a “w” appended to the end, except for TIFF, whose
extension is “tfw”.
49.3.11 Report File

Mosaic generates a report file containing various data about the mosaic for every run. The report
file is stored in the project data directory and is named the same as your mosaic, except with a
“.rep” file extension.
49.3.12 Clip Polygon

You can clip the mosaic so that the edge has any shape you want by using a clip polygon. You
can draw a clip polygon with either Feature Extraction or Seamline Editor. Pixels inside the clip
polygon will be set to valid imagery; pixels outside will be set to the background color. Make sure
the database only contains one polyhedron feature. If you use Seamline Editor, you can draw the
clip polygon with any image -- Mosaic ignores the image name in the attribute.
Clip polygon only works if your mosaic contains at least two images and:
• Most Nadir and Feathering are enabled
• Most Nadir with DTM and Feathering are enabled
• Input Order and Feathering are enabled
• Radiometric is enabled
• Seam Polygon is enabled

Chapter 49 - Mosaic
49.3.13 Mixing Image Types

Mosaic can process input images with mixed values for bands and bits per pixel. For non-mixed
input, the mosaic will have the same number of bands and bits as the input images. For mixed
input, the following rules apply:
• If bits are mixed and any images are 8-bit images, the mosaic will be 8-bit. Images
greater than 8 bits will be mapped to 8 bits using a histogram method. Enhancements
are not applied to any images being mapped down.
• If bits are mixed and all are greater than 8 bits, there is no alteration of the pixel bit
depth.
• If bands are mixed and any images are less than 3 bands, the mosaic will have one band.
Multiple-band images will be mapped to one band by averaging all bands.
• If bands are mixed and all are greater than or equal to 3 bands, the mosaic will have 3
bands. Mosaic will select 3 bands based on which bands have been selected in the
Image Enhancement window for display. The default display is the first three bands.
• Auto Range Adjust will have unpredictable results with mixed input images.
49.3.14 Multiprocessing
If your computer has more than one processor (CPU), you can speed up your mosaic job by
running it with more than one process. For each process, Mosaic splits the output into a horizontal
“stript” and launches a batch mosaic job for it. After the processes finish, Mosaic joins the stripe
images into a final product. The operating system will automatically run the processes
concurrently on separate CPUs, producing the mosaic faster.
Here are some guidelines for producing mosaics with multiple processes:
1. Your mosaic must be at least 1024 lines (rows) long. Also, each stripe must be 1024 lines
long, so Mosaic will only launch enough processes to meet that criteria.
2. You must have enough disk capacity for about 50% greater than the mosaic size to
accomodate the temporary stripe mosaics.
3. The stripe mosaics will all be created in the same directory as the final output unless you
create special entries in the location.list file, located in internal_dbs/DEVICE. The special
entries are “MOSAIC_n” where “n” is a number starting at 1. For example, if you have 4
processes, modify location.list to contain:
MOSAIC_1 d:/images
MOSAIC_2 e:/images
MOSAIC_3 f:/images
MOSAIC_4 g:/images
Directory names can be any writable disk directory. Select “MOSAIC_1” as the output
location on Mosaic. Mosaic will automatically use the other locations for successive
stripes.
4. The processes for stripe mosaics will create log files in a subdirectory of the project
directory called “batch_dir”. This directory is also used for the “Start At” functionality. the
names will be based on the mosaic name with “_n”, representing the stripe number,
appended.
5. Mosaic DRA is not supported. Use Dodger or manually save enhancements to adjust your
images.

Chapter 49 - Mosaic
49.3.15 Void Fill

In some cases the final mosaic will have black pixels, or “voids”. This may occur because the
source imagery has voids or the image overlap was too narrow for most nadir seam line
processing. Mosaic can fill the voids with imagery if you enable the Fill Voids checkbox. Mosaic
will examine each output pixel and fill voids with pixels from another input image. The image
priority is the same order as listed on the GUI or in the batch file.
If voids are near seam lines, you might have to turn off Seam
Feathering and switch to Nearest Neighbor resampling for a
good result.
49.4 Execution - Mosaic

Here is an example sequence of steps to run Mosaic :
1. Load a project into SOCET SET.
2. Click Products > Mosaic > Mosaic on the main workstation window.
3. On the Start Tab select either Create Multiple Sheets, Create Entire Mosaic, or Create
Seams Only.
4. Click on the Setup Tab. Available fields here depend upon what was selected on the Start
Tab.
5. If you are creating an entire mosaic or seam database you only need to specify the Output
Boundary. If you are doing multiple sheets the Method needs to be either Manual, Input
File or Azimuth. If you are doing multiple sheets and know the full extent of the sheets,
you may enter the extent into the Output Boundary.
6. Depending on whether or not you are using an ASCII input sheet boundary file, fill out
Origin and Sheet Setup information.
7. Click on the Input Tab. You may select images and DTM’s manually or by pressing Select
Using Boundaries. You may filter file names with a regular expression by entering it next
to the Filter button and clicking it. You can graphically display the Image, DTM, and Sheet
footprints by selecting them and clicking the Draw or Auto Draw button.
Click on the Output Tab. If you are creating multiple sheets, click Calculate Sheets and
use the Update Sheet Names to change the names if so desired. Select the Output Location,
Format, GSD, Output File Names, etc. from the right side of the GUI.If you want a specific
scale on a hardcopy output device, you may want to enter an exact ground sample distance
(units/pixel), which when printed on the plotter will be a precise scale. If this is the case
use the formula below:
• GSD = units/pixel = SCALE / (dpi * 12)
• where SCALE = scale inverse (e.g. for a scale 1:5000 enter 5000)
• dpi = dots per inch (e.g. IRIS accepts dpi of 200, 240, and 300)
• 12 = used for GSD entry in feet.
If you are in a project whose units is meters, the ground sample distance is entered in
meters. For the example here, multiply by 0.3048 if you want to convert from feet to meters.
8. Click on the Options Tab. Select the Mosaic Method, Interpolation Method, Dynamic
Range Adjustment, and Mosaic Options.
9. Click on Start to begin mosaic generation.A percent complete display indicates the status
of processing. See “Batch Processing - Mosaic” on page 49-22 to execute Mosaic in batch.

Chapter 49 - Mosaic
49.4.1 Execution - Start At

49.5 Batch Processing - Mosaic

COMMAND LINE:
% start_socet -single mosaicmanager -batch -s setting_file
mosaicmanager mosaic
KEYWORD DESCRIPTION
project Project filename (select from the .prj files in

task Set to either “MULTIPLE_SHEETS”, “ENTIRE_MOSAIC”, or
“SEAMS_ONLY”.
num_processes If you wish to create your mosaic with multiple processess, set
this to the number of CPU’s in your computer. See
“Multiprocessing” on page 49-20.
image Input image support files (select from the .sup files in your
project directory). Repeat for every input file you want to mosaic.
The order of the files in the setting file will be the order used by
Mosaic. This is important when mosaic_method is
INPUT_ORDER.
use_dtm Use DTM flag (YES or NO).
dtm Input DTM polygon(s) (selected from the .dth files in your
project directory). Repeat for multiple DTMs.
elevation [Optional] Elevation for flat DTM if use_dtm is NO (floating

point, in project units).
auto_boundary [Optional] Set this to DTM, SEAMS, or IMAGES to

automatically set the border to match the footprint of the input
DTM, seams database, or the input images, respectively. If you
set this to DTM, SEAMS, or IMAGES, you do not have to specify
foot_entry or any of the corner keywords.
BLANK SPACE
You can also set this to DOQ to make the boundary to a DOQ full
or quarter-quadrant and specify ul_x and ul_y in DD:MM:SS
for the DOQ quadrant you want to use.
foot_entry Footprint entry by lower-left/upper-right or by four corners (TWO

or FOUR). If you set this to “TWO” you only need to specify the
lower-left and upper-right output corners.
NOTE: If you set foot_entry to TWO, you only need to
specify ll_x, ll_y, ur_x, and ur_y

Chapter 49 - Mosaic
KEYWORD DESCRIPTION
ul_x Input MBR upper left corner x coordinate (in project units). If
auto_boundary is set to DOQ, this will be the upper left longitude
in DD:MM:SS.
ul_y Input MBR upper left corner y coordinate (in project units). If
auto_boundary is set to DOQ, this will be the upper left latitude
in DD:MM:SS.
ul_x Input MBR upper-left corner x coordinate (in project units).
ul_y Input MBR upper-left corner y coordinate (in project units).
ur_x Input MBR upper-right corner x coordinate (in project units).
ur_y Input MBR upper-right corner y coordinate (in project units).
ll_x Input MBR lower-left corner x coordinate (in project units).
ll_y Input MBR lower-left corner y coordinate (in project units).
lr_x Input MBR lower-right corner x coordinate (in project units).
lr_y Input MBR lower- right corner y coordinate (in project units).
doq_size [Optional] FULL for a 15 minute DOQ or QUARTER for a 7.5

minute DOQ. Use this only if auto_boundary is set to DOQ.
doq_overedge [Optional] DOQ overedge in meters. This is the extra area

between the geographic corners and the actual edge of the image.
Use this only if auto_boundary is set to DOQ.
gsd Output GSD value (floating point, in project units).
pix_size_x [Optional] GSD values for X and Y. These override the value for
pix_size_y the “gsd” keyword. Use radians in geographic projects, otherwise
use project units.
file_format Output image format. See “Data Handling Capabilities” on

page 7-3. If the “Export” column says “Y” then the format can be
used. Use the keyword listed in the “Batch Name” column.
construct_geotiff Set to “YES” to add GeoTIFF tags to the output pixel file. Also
set file_format to one of the TIFF types if you want GeoTIFF
output.
output_file Name of output image and support file (no path or extension).
output_location Name of the image location from the list in

<install_path>/internal_dbs/DEVICE/
location.list.
sheet_input_file Name of the sheet file describing the sheets you want to generate.
This is required if and only if your task is
“MULTIPLE_SHEETS”.
auto_min [Optional] Automatically minify output orthophoto (YES or NO).

Default is YES.
interpolation Interpolation type (BILINEAR, NEAREST_NEIGHBOR , or

BI_CUBIC).

Chapter 49 - Mosaic
KEYWORD DESCRIPTION
mosaic_method Mosaic method for multiple images (MOST_NADIR,

MOST_NADIR_NARROW, MOST_NADIR_DTM,
RADIOMETRIC, INPUT_ORDER, SEAM_POLYGON). See
“Mosaicking Methods” on page 49-13
centerline_seams If the mosaic menthod is MOST_NADIR or

Most_NADIR_NARROW, you cab set this to “YES” to place the
seams close to the image overlap centerline instead of the best
nadir angle position.
vertex_spacing If the mosaic method is RADIOMETRIC, use these to control the

constraining_width vertex spacing and constraining width
input_seam_name [Optional] Seam polygon database (select from the feature

databases in your project directory). Use if mosaic_method
is SEAM_POLYGON.
output_seam_name Mosaic will create a seam feature database if feathering is
enabled and the mosaicing method is Most Nadir. Set this to the
name you want for this database. Do not include a full path -- the
database is always placed in the project directory.
feather_seams [Optional] Feather seam lines (YES or NO). Default is YES.
feather_width [Optional] Width in pixels of the seam feathering. Default is 20
seam_smoothing [Optional] Smooth seam lines (YES or NO). Default is NO.
smoothing_width [Optional] Width in pixels of the seam smoothing. Default is 3.
background_color [Optional] Color for pixels not covered by input imagery or

outside the DTM (BLACK or WHITE). Default color is BLACK.
void_fill [Optional] Set to “YES” to have Mosaic fill black (zero) pixels
with alternate imagery. (YES or NO).
arc_world [Optional] Create a World file for each mosaic or sheet (YES or
NO).
ortho_info [Optional] Create an ortho info file for each mosaic or sheet (YES
or NO).
clip_name [Optional] Clip feature database. Do not provide a full path. The
path is assumed to be the project directory.
use_tin_map [Optional] Set to YES to enable rigorous TIN DTM processing.

Set to NO to treat TIN as a grid type (faster). Default is NO.
allow_dense_dtm [Optional] When “YES”, Mosaic uses the DTM post spacing as a
processing increment. When “NO”, Mosaic will not allow the
processing increment to become too dense, which results in the
best processing speed and memory consumption. Default is
“NO”.
disable_multi_ [Optional] Set to YES to disable multi-threading processing. Set

threading to NO to run with multi-threading (faster for multi-CPU
platforms). Default is YES.
NOTE: Multithreading is a beta feature. It will work with
most but not all mosaic scenarios.
use_dra Dynamic Range usage mode (DRA_OFF, DRA_AUTO, or

DRA_USER). If you specify DRA_USER, you must specify one
or more of the DRA values below.

Chapter 49 - Mosaic
KEYWORD DESCRIPTION
dra_percent_gl Percentage of calculated adjustment to actually apply.

_change Range: 0.0-100.0.
dra_max_delta_gl Maximum allowed change to average pixel grey levels.

Range: 0.0-255.0 .
dra_percent_skip Amount of the image edge to skip when calculating the image
statistics. Range: 0.0-20.0.
dra_max_gain Maximum allowable gain. Range: 0.0-99999.0 .
dra_min_gain Minimum allowable gain. Range: 0.0-99999.0 .
dra_num_tiles Number of tiles in the correction grid horizontally and vertically.
dra_desired_mean The main grey level which all images will be driven toward
Range: 0-255.
dra_desired_std The standard deviation of all image pixels to which each image
will be driven toward. Range: 0-255.
dra_color_match Set to YES if you want DRA to run in color match mode.
dra_tgt_colors Set to the number of target colors if you are running DRA in color
match mode.
dra_intensity Set to the image intensity you want if you are running DRA in
color match mode.
use_dra_type Dynamic Range usage mode (DRA_CLASSIC or

DRA_HOMOMORPHIC for Intensity Filter)
use_dra_hm Dynamic Range usage mode (DRA_OFF, DRA_AUTO, or

DRA_USER). If you specify DRA_USER, you must specify one
or more of the DRA values below.
dra_percent_skip_hm Fill a percentage of the image at the edges with intensity values
from the un-skipped edge, because images may have undesirable
radiometry around their edges. Range: 0–20 percent
dra_hot_spot_size This is the size in meters of illumination variations that will be

treated as a hot spot. Range 100-20,000
dra_filter_order Controls the smoothness of transitions between hot spot

attenuated areas and non-attenuated areas. Smaller values create
sharper transitions. Range: 5-60
dra_percent_adjust Controls the effectiveness of the Intensity Filter. Smaller values

reduce the effect of hot spot attenuation in the case where it
causes artifacts. Range: 0–200.
dra_vignette_filter Reduces intensity variations due to lens distortion in frame

images. YES or NO
dra_num_tiles_hm Number of tiles in vertical and horizontal direction used to

compute color match transform values. These tiles need to be
small compared to overlapping regions’ sizes. Range 10-100.
dra_color_match_hm Set to YES if you want DRA to match colors in adjacent images.
YES or NO
dra_global_match Set to YES if you want DRA to filter per band large scale
intensity variations in the output mosaic. YES or NO

Chapter 49 - Mosaic
49.6 Seamline Editor

Seam Polygons allow you to explicitly select the imagery source for each region of the mosaic.
In order to use this feature, you must first create an Seam Polygon File (database) using Feature
Extraction or the Seamline Editor to specify the region boundaries on the input images. (See
“Feature Extraction,” Chapter 42 and See “Sketch,” Chapter 58 for a more detailed explanation
of how to use Seamline Editor.) The Seamline Editor is a restricted Feature Extraction which
operates only on Seam Polygons. You must extract one closed polygon for each input image. To
open this window, click Products > Mosaic > Seamline Editor on the Main Menu window.
The Seamline Editor window’s selections are as follows:
File > Open Prompt you to select a seamline database to load. If you wish to create a
new database, enter the new name in the Selection field.
File > Save Save Seamline database.
File > Save As Save Seamline database to a new file.

File > Reference Databases Prompts you to select a seamline database to load and be used as a
reference. This database will be displayed, but cannot be modified.
File > Customize Brings up the customize window to customize the Seamline Editor
window.
File > Exit Exits the Seamline Editor application.
SELECT TO
New Prompt you to open a new feature database.

<Ctrl>N

Chapter 49 - Mosaic
SELECT TO
Open Prompt you to select a feature database to load. To create a new database,
<Ctrl>O FDB enter the new name in the Selection field.
Save FDB Save currently open feature database.

<Ctrl>S
Display Seamlines Toggle to display seamlines in the image window.
Auto Load Image If selected, images will automatically load when it’s associated polygon is
selected in the polygon table or in the display.
Label Polygons If selected, each polygon is labeled with it’s associated image.
Check Boundaries Display a warning window when a polygon is edited and if any points in
the polygon lie outside the image.
Mark Bad Pts Seam polygon points which lie outside the associated image will be
marked with a “x”.
Footprints Display image footprints for the image(s) whose polygon contains the
vertex being edited.
Draw Draws the contents of the seamline database.
Auto Draw Automatically draws the contents of the Seamline Database whenever you
Add Prompt you to select the image you want to create a seam polygon for.
After you select the image the next step is to extract the polygon. Once you
accept the polygon it will be added to the table.

Chapter 49 - Mosaic
SELECT TO
Delete Deletes polygon from database.
Set Image Allows you select the image to associate with the polygon.
Seam Polygons List the polygons and their associated images.

Left click on Polygon ID to sort by ID (clicking a second time will reverse
sort).
Select that polygon by clicking LMB on a row to select. If Auto Load
Image is selected the associated image will be loaded.
BLANK SPACE
Display the following menu by clicking RMB on a row you want
displayed:
• Add - same functionality as Add button.
• Delete - deletes polygon from database.
• Set Image - allows you select the image to associate with the
polygon.
Sketch Toolbars See “Sketch,” Chapter 58 for a complete list of sketch tools. The “Edit
Shared Vertices”, “Share Segment”, and “Change Direction” sketch tools
are frequently used for editing and creating mosaic seam lines and are
included here.
Edit Shared Vertcies Edit Shared Vertices, when ON, edits will work on all objects that share an
<Ctrl>a edge. Includes Insert Vertex, Redraw, Delete Vertex and Move Vertex.
When OFF, edits only work on one of the objects.
Share Segment Copy vertices from a pre-existing “shared” object into the “current” object
<Ctrl>g being drawn. Steps are:
1. Start drawing the current object.
2. Move the cursor to the first point to be shared.
3. Press the MMB to Snap.
4. Digitize a vertex for the current object.
5. Move the cursor to the last point of the edge you want to share.
6. Click the Share Segment icon button. (Polylines Only - If share
segment does not succeed, it is because the start and end points
are not on the same element. The element with the start-point
will highlight in the “edit color,” and the cursor will jump to
the closest end point of that element. The user may then move
the cursor and click share segment again.).
7. If the shared object is a polygon, you choose between the two
possible segments by clicking the Change Direction icon
button.
8. Press the LMB to confirm the share segment.
9. Continue sampling.

Chapter 49 - Mosaic
SELECT TO
Change Direction Decide which of two segments to use in the Share Segment action. Only
<Ctrl>d useful when the shared object is a polygon.
49.6.1 Example
The following are some example steps involved in creating the source polygons:
1. Click Mosaic > Seamline Editor on the main workstation window.
2. Click File > Open on the Seamline Editor window.
3. Enter “seam” in the Selection box, then click OK.
4. Check the “Auto Draw, Auto Load Image, Label Polygons, and Check Boundaries” icons
on the Seamline Editor window.
5. Click Add. The “Select Image File” window pops up.
6. Select the image you want to draw a polygon for, then click OK. The image you select will
be loaded.
7. Toggle display cursor to the image cursor by pressing the center trackball button (or F3).
8. Delineate a polygon region that you want to be in the mosaic by clicking the LMB for
polygon vertices.
9. Press the RMB finish and accept polygon.
10. Click Add.
11. Select the second image you want to draw a polygon for and click OK. The image you select
will be loaded.
12. Delineate a polygon region on top of this second image. Use the Sketch functions (“Snap
to Vertex (MMB)” and “Share Segment”) to make sure your second polygon shares the
desired edges of your first polygon. Use “Change Direction” if the shared polygon segment
is the wrong piece of the first polygon. You will be able to see the shared segment as yellow
after selecting the “Share Segment” button. For details on how to draw polygons, and how
to share polygon edges, See “Examples” on page 58-19 .
Mosaic expects the shared edge between two seam polygons

to share vertices. When connecting to an existing feature the
only way to insert a vertex is by using the copy segment
operation after connecting to an edge.
13. Repeat steps 10, 11 and 12 for each additional image in the mosaic.
14. Select this resulting FDB for the Seam Polygons when you run Mosaic.
You should keep the cursor on the “ground” (correct Z) while

delineating the polygons. This will insure that the seam falls
where you think you are drawing it. You may want to use DTM
tracking or stereo to assist you with this. See “Terrain
Tracking” on page 61-4 in the Utilities chapter.

Chapter 49 - Mosaic
When making a mosaic using seam polygons, you should not

draw the seam vertices too close together. An acceptable
distance is at least three times the ground sample distance of
your mosaic. If you place vertices too close together, Mosaic
may create black pixels in the area. Additionally, you should
draw your seam lines using a minification level of the input
image which corresponds roughly to the ground sample
distance of your mosaic. Also avoid placing vertices closer
than 3 pixels apart. For example, if you have input images with
a 1:1 GSD of 1 meter and want to make a mosaic with a GSD of
4 meters, use the 4:1 minification level to draw the seam lines
and place the vertices at least 3 pixels apart.
Output Mosaic Boundary image 2
image 1
seam polygon 1 seam polygon 2
seam polygon 3 seam polygon 4
image 3
image 4
49.7 Automatic Seam Polygons

If you want to have Mosaic create an initial set of seam lines and then adjust them with Seamline
Editor there are two approaches. Mosaic always generates a seam database while creating a
mosaic with feathering or seam smoothing turned on. The database is named the same as the
mosaic with “_seams” appended, e.g. if your mosaic is named “my_mosaic_o”, the seam database
will be named “my_mosaic_o_seams”. A common scenario is to create a low resolution mosaic,
which allows you to display and edit the automatic seamlines on the low resolution mosaic as well
as on the original input images. To create a low resolution mosaic enter a GSD that is 10-20 times
larger than the GSD on the input images. Allow the output polygon to be determined from the
input images.
Alternatively, you can generate automatic seamlines without creating the mosaic using the
following steps”

Chapter 49 - Mosaic
1. Turn on either Options > Feathering or Options >Seam Smoothing.

2. Select either Mosaic Method > Most Nadir or Mosaic Method > Radiometric.
3. Enter the name of the feature database into the Generate Seams Only text box.
4. Click the Generate Seams Only button. This will create a seam database with your images.
5. Proceed to edit your seam database with Seamline Editor as shown above.
49.7.1 Example
1. Create an overview mosaic as discussed in the Automatic Seam Polygons section above.
2. Load the overview mosaic in View1.
3. Click Mosaic > Seamline Editor on the main workstation window.
4. Click File > Open on the seamline editor window.
5. Select the seamline file created in 1 above.
6. Click the Auto Draw, Auto Load Image, Check Boundaries and Edit Share Verticies icons
on the seamline editor window.
7. On View1, select rectify-all under the image enhancement pull down.
8. Change the Edit Sketch function to Select.
9. Toggle display cursor to the View1 image by pressing the center trackball button (or F3).
10. Move the extraction cursor close to the seamline you want to edit and select the seamline
with the LMB.
11. The image associated with the seamline will get loaded into View2 automatically, since
Auto Load Image was selected. The image will also be rotated and scaled to the overview
orthomosaic, since rectify-all is on.
12. Switch the Sketch edit tool to Redraw.
13. Toggle display cursor.
14. Snap to the seamline using the MMB. (the Sketch Snap Preferences must be set to Sample
and Insert Vertex.)
15. Sample new points for the seamline using the LMB.
16. Snap back to the seamline using the MMB.
17. Accept the new seamline with the RMB, the replaced section of the seamline will highlight
in white.
18. Confirm the new seamline with the RMB.

Chapter 49 - Mosaic
49.8 Mosaic Sheet Cutter
Mosaic Sheet Cutter automatically generates multiple image tiles from an orthophoto mosaic. To
open this window, click Products > Mosaic > Sheet Cutter on the main workstation window.
49.8.1 When to use Mosaic Sheet Cutter

You use Mosaic Sheet Cutter when you need to cut an orthophoto mosaic into multiple images of
the same size. You enter the starting coordinates, the tile size, and the output name template.
Optionally you can enter the x or y over-edge size, and the number of tiles in the x or y direction
Other options include whether your tiles are lower left or upper left corner based, and whether the
size and over-edge values are in pixels or the coordinate system of the current project.
If you use the convention for the seam polygon database name when you generate the mosaic, i.e.
the ortho name with “_seams” appended, then Sheet Cutter will populate each metadata file with
the names of the mosaic source images which intersect the tile.
Batch processing is available for this procedure. See “Batch Processing - Mosaic Sheet Cutter”
The Mosaic Sheet Cutter window’s selections are as follows:
File > Exit Exits the Mosaic Sheet Cutter application

Chapter 49 - Mosaic
Options > Select Meta Prompts you to select the meta files that are generated for each tile. The
Files... available meta files are World, Ortho Info, and GeoTIFF.
SELECT TO
Project Prompt you to select a project file.

Input Ortho Prompt you to select an orthophoto.
Position - Upper Left When selected, the starting position coordinates are for the upper left
corner of the first tile cut from the mosaic. Subsequent tiles are cut to the
right and below the first tile.
Position - Lower Left When selected, the starting position coordinates are for the lower left
corner of the first tile cut from the mosaic. Subsequent tiles are cut to the
right and above the first tile.
Coordinates - X/Long Identify the x coordinate of the starting position.
Coordinates - Y/Lat Identify the y coordinate of the starting position.
Units - Pixels Identify the size and overedge are in image pixels.
NOTE: The upper left corner of the image is the origin (0,0).
Units - Project Coordinates Identify the size and overedge are in the coordinate system of the current
project. If your project is in geographic coordinates, you will have to enter
the size and overedge in a DDD:MM:SS or ddd.dd format depending on
the project lat/lon format settings you selected during Project Create. ex.
00:00:05 or 0.001
If your project is grid or LSR, specify a decimal ground coordinate.
Size - X Identify the horizontal size of the tile.
Size - Y Identify the vertical size of the tile.
Overedge - X Identify the horizontal overedge of the tile.
Overedge - Y Identify the vertical overedge of the tile.
Number of Tiles - X Identify the number of horizontal tiles.
Number of Tiles - Y Identify the number of vertical tiles.
Output Image Identify the name, location, and format of the output images.
The name is a template that is used to name each image tile. The options
are:
 - replaced by the name of the input image.
<x> - replaced by the x coordinate of the tile.
<y> - replaced by the y coordinate of the tile.
NOTE: <x> and <y> are required.
Start Start cutting tiles.

Chapter 49 - Mosaic
49.8.1.1 Meta Files

Mosaic Sheet Cutter can optionally generate the following meta file formats:
• World Files
• Ortho Info
• GeoTIFF
Ortho Info format is as follows:
• Image Name:
• Image Date
• Lower-Left corner:
• Ground Sample Dist:
• Lines:
• Samples:
• Coordinate System:
• Datum:
• Projection:
• Source Image:
• Source Image Date:
Source image information is found by using the seams database of the input mosaic. If the seam
database is not available, source image information will not be available.
49.8.2 Execution - Mosaic Sheet Cutter

The following steps define one possible sequence you might follow to cut a mosaic into image
tiles:
1. Load a project into SOCET SET.
2. Click Products > Mosaic > Sheet Cutter on the main workstation window.
3. Click Input Orthophoto to select the input orthophoto mosaic. When the image is loaded,
the lower left coordinates of the image will appear in the coordinates X and Y fields. If
position is changed to upper left before loading the image, the upper left coordinates are
automatically filled in.
4. [Optional] Click File > Load Images on the main workstation window to load the same
image into the image view.
5. [Optional] Select the “Upper-Left” or “Lower-Left” radio button in the Position area of the
window.
6. Enter the coordinates of the starting position in the Coordinates area of the window.
7. [Optional] Select the Pixels or Project Coordinates radio button in the Units area of the
window.
8. Enter the tile size in the Size area of the window.
9. [Optional] Enter the overedge size in the OverEdge area of the window.

Chapter 49 - Mosaic
10. [Optional] Enter the number of tiles in the Number of Tiles area of the window. Entering 0
or leaving the fields blank will cause the application to calculate the number of tiles based
on the size and starting position.
11. Click Location to select the output location of the generated image files.
12. Enter a name template for the output tiles in the Name field. Naming is flexible but requires
that your template contain <x> and <y>.
Example names:
<x>_<y>
mytiles<x>_<y>
<y><x>_ortho
pre<x>middle<y>moreend
13. Select the image format from the Output Image section.
14. [Optional] Click Options > Select Meta Files... on the Mosaic Sheet Cutter window. In the
Meta File window select the Meta files you would like to generate by selecting its
associated check box. Click Close when done.
15. Click Start to begin cutting tiles
49.8.2.1 Preview
Whenever the minimum amount of parameters have been entered, a preview will be shown as a
red grid over the image display. The parameters needed for preview are the starting position
coordinates and the tile size. The preview will update whenever a parameter is changed. To force
an update of the preview change the number of tiles to 0, or reset the display (F2), recenter the
image, or change the minification level. The application will update the preview and recalculate
the number of tiles if necessary.
49.8.3 Batch Processing - Mosaic Sheet Cutter

COMMAND LINE:
% start_socet -single cutter -batch -s setting_file
cutter cutter
KEYWORD DESCRIPTION
project Project filename (select from the .prj files in <install_path>/data).
input_ortho Input support filename (select from the .sup files in your project directory).
output_name Output name template [optional, will default to <x>_<y>].
output_location Name of the image location from the list in <install_path>/internal_dbs/

DEVICE/location.list.
coord_x The x coordinate of the starting position [optional, defaults to the lower
left or upper left corner of the input image based on the value of use_ll].

Chapter 49 - Mosaic
KEYWORD DESCRIPTION
coord_y The y coordinate of the starting position [optional, defaults to the lower
left corner or upper left corner of the input image based on the value of
use_ll]
size_x The size of the output tiles in the x dimension.
size_y The size of the output tiles in the y dimension.
overedge_x The size of the overedge in the x dimension [optional, defaults to 0].
overedge_y The size of the overedge in the y dimension [optional, defaults to 0].
tiles_x The number of tiles in the x dimension [optional, defaults to 0, software

will calculate the number of tiles].
tiles_y The number of tiles in the y dimension [optional, defaults to 0, software

will calculate the number of tiles].
proj_coords Specify YES for project coordinates. [optional, defaults to NO]

NOTE: If your project is in geographic coordinates, you will have
to enter the size and overedge in a DDD:MM:SS or ddd.dd format
depending on the project lat/lon format settings you selected
during Project Create. ex. 00:00:05 or 0.001
If your project is grid or LSR, specify a decimal ground coordinate.
Specify NO for image pixels.
NOTE: The upper-left corner of the image is the origin (0,0).
use_ll Specify YES to use the lower-left corner [optional, defaults to YES].
NOTE: The starting position coordinates are for the lower-left
corner of the first tile cut from the mosaic. Subsequent tiles are cut
to the right and above the first tile.
Specify NO to use the upper-right corner.
NOTE: The starting position coordinates are for the upper-left
corner of the first tile cut from the mosaic. Subsequent tiles are cut
to the right and below the first tile.
img_type Output image format. See the chart in Chapter “Image Import/Export”. If
keyword listed in the “Batch Name” column [optional, defaults to
img_type_vitec].
arc_world Generate a World file for each image (YES or NO) [optional, defaults to
NO].
create_geotiff Generate GeoTIFF information in each image (YES or NO) [optional,
defaults to NO]. Be sure the img_type is one of the TIFF formats.
ortho_info Generate Ortho Info file for each image (YES or NO) [optional, defaults to
NO].

Chapter 50
Perspective Scenes
Perspective Scenes creates photo-realistic three-dimensional
scenes from a user-specified viewpoint in single and multiple
scene modes.
50.1 Overview
After the location and orientation of an imaginary viewer is specified, Perspective Scenes renders
a scene by draping imagery over the DTM and features that are visible to the viewer. The most
common features utilized in Perspective Scenes are building features, but other features may be
used as well.
Perspective Scenes provides many options:
• You can render a single scene, or an animated flythrough consisting of hundreds of
scenes.
• You can drape imagery over DTM alone, or over DTM and features.
• You can specify that features be rendered from imagery, or with artificial textures,
or with solid colors, or shaded based on a given sun angle.
• The imagery draped over the DTM and features can come from several distinct
images. You can specify which image to use for each feature, or you can let
Perspective Scenes automatically choose for you.
• On a flythrough path, you can specify eyepoints that follow a simple tangent line
along the flight vector, that pivot to the left or right, or that lock onto target points.
• You can output scenes with or without accompanying support data (support data
permits geolocation operations in the output scenes).
• You can vary the field-of-view angle of the scenes, as well as the resolution (pixel
size) of the scenes.
• You can generate an automated route about the area covered by one or more DTMs.
SOCET SET Page 50-1

Chapter 50 - Perspective Scenes
50.1.1 When to use Perspective Scenes

Imagery and DTM are the two essential inputs to Perspective Scenes. First, you must import and
control the images you are going to use. Second, you must extract or import a DTM covering the
region.
If buildings or other volume features are present in the scene and you want them modeled in the
Perspective Scene, you must extract them with Feature Extraction. See “Feature File
Preparation” on page 50-14 for a summary of this complex process.
After the input files are prepared, you can run Perspective Scenes. You can delineate a flythrough
route from Perspective Scenes, use a pre-existing route from a Feature file, or generate an
automated flyaround about the area covered by your selected DTMs.
Perspective Scenes is best used to generate a large number of scenes that can be viewed as an
animated flythrough, but it can also generate a single scene.
After the scene(s) are generated, you can view them with Animation (See “Animation” on
page 50-34). Alternatively, if you generated support files to accompany the scenes, and you can
view individual scenes in the Main Workstation window.
50.1.2 Terminology
50.1.3 Data Flow
Eyepoint The location of the viewer’s eye for the perspective scene.
Aim point The location the viewer is looking at.
Eye route A list of eyepoints used to generate a flythrough.
Aim route The list of aim points for the flythrough.
Generated eyepoints A set of points generated by the computer using a spline. The initial data
for this set of points comes from the eyepoints specified by the user.
Generated aim points A set of points generated by the computer using a spline. The initial data
for this set of points comes from the aim points specified by the user.
Eyepoint spline The curve through the eyepoints along which the viewer’s eye will travel.
Aim point spline The curve through the aim points where the viewer is looking.
Scene Content File A file that describes the DTM’s, images and feature files to be used in
generation of a perspective scene.
Scene Parameter File A file containing the parameters that control the perspective scene
generation. This include such things as the size of the output images, the
field of view, coloring and other parameters.
The “Scene Content File” contains all the element to describe the scene itself. These include:
• DTMs (one or more are required)
• Images (one or more are required)
• Feature files (optional)
• Feature files with texture patches (optional)
Page 50-2 SOCET SET

The “Scene Parameter File” contains all the miscellaneous parameters such as field of view,
Clipping planes, Background generation and other parameters.
The “Eyepoint Route” determines the location of the viewer’s eye during a flythrough. For a
single scene, this is one point.
The “Aim Point” determines where the viewer is looking during the flythrough. This must be
specified for a single scene. For a flythrough, it will be automatically generated if it is not
explicitly specified.
ROUTE
SETUP
ROUTE 0 OR MORE 1 OR MORE IMAGE AND

FEATURE FILE FEATURE FILES DTMs SUPPORT FILES
EYEPOINT CONTENT PARAMETER

SETUP SELECTION SETUP
EYEPOINT SCENE SCENE

FILE CONTENT FILE PARAMETER FILE
SCENE
RENDERING
1 OR MORE
PERSPECTIVE SCENE
IMAGE FILES
ANIMATION
SOCET SET Page 50-3

50.2 Perspective Scene (Single Scene)

To open Perspective Scene in the Single Scene mode, click Products > Prospective Scene on the
main workstation window. Then select the Single Scene tab on the Perspective Scene window.
The Perspective Scene window will readjust to single scene mode. The window displays the
names of the files currently open.
This window provides fields for the View Point and the Aim Point of the Single Scene.
Located at the bottom of the window is a status box in which status messages, error messages,
and/or instruction messages are displayed. These messages come from the Perspective Scenes and
its various subwindows.
The Perspective Scenes (Single Scenes) selections are as follows:
File > Exit Exits Prospective Scenes.

Options > Generate Support Toggle on to generate a support file for each Perspective Scene generated.
Files
Options > Display Scenes Toggle on to display the scenes during generation.
Page 50-4 SOCET SET

Tools > Automated Route Generates a series of aim and route points based on the location of the
input image file.
SELECT TO
Setup File Display the name of the current Perspective Scene Setup File.
Scene Content File Activates the Scene Content File menu. See “Scene Content Selection” on
page 50-30.
Scene Parameter File Activate a dialog which allows you to change the scene parameters. See
“Scene Parameter Setup” on page 50-32.
Route Feature File: Prompt you to open an existing route feature file. If the file you specify
does not exist, Route Setup will created a new route feature file for you.
You will use the Aim and Eyepoint Route Editor windows to create one or
more route features, which will be stored in this file.
Eyepoint Identify the location of the viewer’s eye for the perspective scene. in X, Y,
Z or Lat/Lon/Z.
Aim Point Identify the location the viewer is looking at in X, Y, Z or Lat/Lon/Z.
Render Scenes Start the Scene Rendering.
Generation option Select Imagery, Wire Frame, or Shaded. Imagery generates a perspective
scene based on the images you have selected. Wire frame draws a wire
frame version of the perspective scene.
NOTE: The back clipping plane parameter (on the Scene
Parameter Setup menu) should be set to the farthest point you
want included in the scene, otherwise perspective scenes will
render very slowly.
Shaded uses a set of shaded polygons to represent the scene.
50.3 Getting Started - Single Scene Mode

A single scene contains one eyepoint and one aim point:
Eyepoint
Aim
Aim Point
This section will take you through the basic steps needed to generate a simple perspective scene
using Perspective Scenes quick look or Single Scene Generation feature.
SOCET SET Page 50-5

Before starting, you will need a project with at least one image and a DTM that covers the area
we are going to look at.
First, load the image into the left console window. (See “Color Imagery” on page 50-16 for an
explanation of color usage.) Start Perspective Scenes using the Products > Perspective Scenes
menu. The Perspective Scene window is displayed.
Start by selecting Single Scene tab on the Options Perspective Scenes window. The minimum
information that Perspective Scenes is an image (what the ground looks like) and a DTM (where
the ground is). Click Scene Content File to start defining this information. The Scene Content
Selection dialog appears.
One the left hand side of the dialog is a set of buttons for defining feature information to be
included in the scene generation. Since you are generating a simple scene, you won’t be defining
any features. You will need at least one DTM however, so click Include DTM.
Select a DTM from the list either by clicking on the name in the file list window or by using the
extraction cursor to click on the bounding box in the console window. Click OK to return to the
Scene Content Selection window.
You have gotten a DTM, you now need to define what images this DTM covers. Click LMB on
the DTM to highlight it, then click Select Images.
When the Image Selection dialog appears, click Include Image and select an image from the list.
Click OK to exit the file section. Click Done to exit the Image Selection. Click Done to exit the
Scene Content Selection.
One thing you must be aware of when creating perspective scenes is the location of the ground.
It is possible to place the eyepoint or the aim point underground. Perspective scenes does not
detect this and will generate an erroneous perspective scene. Looking at the ground from
underground can produce strange results. Make sure that both the “Eyepoint” and the “Aim Point”
are both above ground.
Move the extraction cursor to where you want the “Eyepoint” (where you are looking from) and
pressing with the LMB. (You probably want to make the “Eyepoint” higher than the “Aim Point”
so you are looking down on the scene.) The coordinates will be deposited in the Eyepoint blanks
in the dialog and a yellow dot appears on the console.
If the View point is directly above the Aim point (i.e., the viewer
is looking straight down) the scene will be rendered
incorrectly. As a work-around, change the aim-point so the
viewing direction is not exactly straight down.
Move the extraction cursor to where you want the “Aim Point” (where you are looking at). Press
the MMB. A green dot appears at the “Aim Point.” Perspective Scenes draws a red line from the
Page 50-6 SOCET SET

“Eyepoint” to the “Aim Point.” An approximation of the field of view is drawn in yellow with a
green line across the top.
Aim Point
Eye Point
If you want to be able to load the image into the main image window, you need to turn on the
support file option under Options > Generate Support files before rendering the scene.
Click Render Scenes. A single perspective scene will be generated (this takes some time). This
image is called SingleScene.img and can be viewed with the Animation tool or by loading
it on the main image window.
50.4 Perspective Scene (Multiple Scene)

The Perspective Scene window displays the names of the files currently open and the name of the
currently selected route. To open this window, click Products > Prospective Scene on the main
workstation window. If a Single Scene window is open, select Multiple Scene tab to open this
window.
This window also provides buttons for starting the Eyepoint Route Editor and the Aim Route
Editor, generating the eyepoints, drawing the eyepoints on the image display, and for individually
editing the attributes of each eyepoint.
Located at the bottom of the window is a status box in which status messages, error messages,
and/or instruction messages are displayed. These messages come from the Perspective Scenes and
its various subwindows.
SOCET SET Page 50-7

The Perspective Scenes (Multiple Scenes) selections are as follows:
File > Exit Exits Prospective Scenes.

Options > Generate Support Toggle on to generate a support file for each Perspective Scene generated.
Files
Options > Display Scenes Toggle on to display the scenes during generation.
Tools > Automated Route Generates a series of aim and route points based on the location of the
input image file.
SELECT TO
Setup File Name of the current Perspective Scene Setup File.
Page 50-8 SOCET SET

SELECT TO
Scene Content File Activates the Scene Content File menu. See “Scene Content Selection” on
page 50-30.
Scene Parameter File Activate a dialog which allows you to change the scene parameters. See
“Scene Parameter Setup” on page 50-32.
Route Feature File Prompt you to open an existing route feature file. If the file you specify
does not exist, Route Setup will created a new route feature file for you.
You will use the Aim and Eyepoint Route Editor windows to create one or
more route features, which will be stored in this file.
Eyepoint File Prompt you to open an existing eyepoint file. If the file you specify does
not exist, Route Setup will create a new eyepoint file for you.
# of Eyepoints Display the number of eyepoints generated along the eyepoint route.
Total # of Scenes Display the total number of scenes generated by the eyepoint route.
Eyepoint Route Edit Open the Eyepoint Route Editor window that prompts you to edit
eyepoints, spline parameters, or default yaw, pitch, and roll values.
Aim Route Edit Open the Aim Route Editor window that prompts you to enter aim points.
Generate Eyepoints Generate the generated eyepoints and generated aim points based on the
eyepoints and aim points, spline parameters, and yaw/pitch/roll values you
entered
Eyepoint Attribute Examine and modify the attributes of individual eyepoints.
Routes Control whether the eyepoint and aim routes are drawn. When drawing the
routes, Route Setup connects the points input by the user with straight line
segments. The eyepoint route is drawn in purple, and the aim route is
drawn in cyan.
Eyepoints Control whether the individual points comprising the eyepoint and aim
routes are drawn. The points are represented with small squares.
Splines Control whether the eyepoint and aim splines are drawn. Route Setup
draws the eyepoint spline in red and the aim spline in green.
Gen. Pts. Control whether the individual generates points of a route are drawn along
the eyepoint and aim splines. If your routes are dense with many eyepoints,
you may want to disable drawing them. The eyepoints are represented with
small yellow squares.
Rays Control whether the line segments connecting the eyepoints and aim points
are drawn. The bottom Rays button controls whether the line segments
connecting the eyepoints to the aim points are drawn. If your routes are
dense with many eyepoints, you may want to disable drawing of the rays.
Route Setup draws the rays in blue.
Draw Draw graphics on the imagery representing the following:
• eyepoint and aim routes,
• eyepoint and aim splines,
• eyepoints and aim points,
• line segments (called “rays”) connecting the eyepoints to the
aim points.
Abort Abort the current drawing operation you initiated by clicking the Draw
button.
Auto Draw Automatically re-draw the graphics if you re-center or reload the imagery
if set to “on.” Default is “off.”
SOCET SET Page 50-9

SELECT TO
Starting Scene Display the number of the scene which is the beginning of the range of
scenes to be rendered. Initially, this field will contain the value read from
the currently open scene parameter file, or 0 if one is not open.
Ending Scene Display the number of the scene which is the end of the range of scenes to
be rendered. Initially, this field will contain the value read from the
currently open scene parameter file, or 0 if one is not open.
Generation Rate Indicate at what rate to generate scenes. A value of ‘5’ would render every
fifth scene.
Scenes to Render Display the number of scenes to be rendered.
Render Scenes Start the Scene Rendering.
Generation option Select Imagery, Wire Frame, or Shaded. Imagery generates a perspective
scene based on the images you have selected. Wire frame draws a wire
frame version of the perspective scene.
NOTE: The back clipping plane parameter (on the Scene
Parameter Setup menu) should be set to the farthest point you
want included in the scene, otherwise perspective scenes will
render very slowly.
Shaded uses a set of shaded polygons to represent the scene.
50.5 Getting Started - Multiple Scene Mode
Viewing Directions -
one scene is generated
Eyepoint spline - at each eyepoint; the
The path of the default direction is
viewer’s eye is a tangent to the eyepoint
spline through the route.
view waypoints.
Eyepoints - are
the vertexes of
the eyepoint
route feature
delineation.
Generated
eyepoints - are
interpolated
User defined points between the user
selected Image and
Computer generated points eyepoints. Features.

The user can select a set of aim points. These aim points will then be used to create an aim point
spline along which a set of generated aim points will be placed.
Eyepoint route
Aim point route
User defined Point

Image and
Computer generated point Features
You can use Perspective Scenes to generate a flythrough of multiple scenes. After the flythrough
sequence is generated, you can view it with Animation.
Generating a flythrough involves the following steps:
1. Eyepoint setup—Delineation of the viewer’s eyepoint route and aiming route. Also
includes refinement of the viewer’s look angles along the route, such as pivot actions.
If the View or eyepoint is directly above the Aim point (i.e., the
viewer is looking straight down) the scene will be rendered
incorrectly. Move the aim-point so the viewing direction is not
exactly straight down.
2. Scene Parameter Setup—Establishment of the size and appearance of the rendered scenes.
3. Scene Content Selection—Selecting the DTMs and Feature files to be used as models of
the world that the viewer is seeing. Imagery to be draped over the DTM and Features is also
specified.
4. Scene Rendering—Actual creation of the output scenes. The scenes will be displayed one
at a time as they are being rendered, and will be saved as individual image disk files.
The first three steps result in parameter files which may be edited and reused to generate other
sets of perspective scenes. The final step, Scene Rendering, creates the scenes and stores them in
disk files. The scenes are conventional image files and may be printed on hardcopy devices or
reviewed on the screen.
You can view the scenes you generate with the Animation tool by clicking Tools > Animation on
the main workstation menu. You can view individual scenes, one-by-one or you can play them in
sequence in an animated fashion.
Alternatively, you can generate image support files for your scenes so that you can load the
images onto the workstation monitors. As a consequence, you can also perform ground space
operations on the output image. A multiple scene flythrough will have many eyepoints and many

aim points. The eyepoints are used by the user to create generated eyepoints along the eyepoint
spline. If no aim points are specified by the user, the default aim points are created tangent to the
generated eyepoint path.
50.5.1 Sample Execution: Flythrough Generation

This section illustrates a sample execution of Perspective Scenes to generate a simple flythrough.
The sample is rather simple and does not demonstrate some of the advanced features such as aim
points or pivot-points.
50.5.1.1 Initialization
1. Before you start prepare at least one DTM and image.
2. If you desire, prepare a feature file.
3. Click Products > Perspective Scene on the main workstation window.
4. Click (ellipse tool button) to the right of Setup File on the Perspective Scene window.
5. Enter a new filename for the perspective scenes list file (.lst), then click OK.
This filename will also apply to the resulting perspective

scene.
50.5.1.2 Route Setup

1. Click (ellipse tool button) to the right of Route Feature File on the Perspective Scene
window. Enter a new filename for the route feature file, then click OK.
This file will contain the eyepoint route and aim route. Another
feature file will specify which features appear in the final
scene.
2. Click Eyepoint Route Edit on the Perspective Scene window. This brings up the Eyepoint
Route Editor window.
3. Click Create on the Route Editor window. Enter the new Eyepoint Route name, then click
OK.
4. Click Append on the Route Editor window. This brings up the Edit Point window. Sample
coordinates for two Eyepoints; the first point is the one and only one Eyepoint for this route,
while the second point is the one and only aim point for this route.
a. Toggle to the extraction cursor and set its location with the mouse. Remember to set
the elevation of the cursor with the Z control. It is best to always be looking somewhat
down, so make sure the eyepoint is above the aim point.
b. For this example, make sure the Aim Type is set to Tangent.
c. Sample the point by (1) clicking the LMB, or (2) toggling back to the mouse cursor
and clicking Sample on the Edit Point window. This reads the cursor position in
ground space and enters the data into the list of points on the Route Editor window.
5. If you wish to cancel the last point you sampled, you can click Cancel on the Edit Point
window. This will delete the last point you sampled.
6. When you have finished sampling the new points, toggle back to the mouse cursor and click
Done on the Edit Point window. You can also close the Edit Point window while toggled
to the extraction cursor by clicking the RMB.
7. Review the point list in the Route Editor window.

8. Click Done on the Route Editor window to return to the Route Setup window.
9. Click Generate Intermediate Eyepoints. You are warned that any previously generated
eyepoints will be over written. Click OK to proceed.
50.5.1.3 Scene Content Selection

1. Click Scene Content. This brings up the Scene Content Selection window.
2. If you have not prepared a feature file skip to step. Click Include Feature File on the Scene
Content Selection window. Pick the name of the file that contains the features that are to
appear in your perspective scene, then click OK. By default, all the features in your feature
fill will be included in the perspective scene.
3. Click the name of the feature file in the Selected Feature Files list. Click Select Images on
the Scene Content Selection window. This brings up the Image Selection window.
4. Click Include Image on the Image Selection window. Select one or more images then click
OK. The names of the images you picked appear in the Selected Images list in the Image
Selection window.
5. Click Done on the Image Selection window to return to the Scene Content Selection
window.
6. Click Include DTM on the Scene Content Selection window. Select a DTM from the list,
then click OK. The name of the DTM you picked appears in the Selected DTMs list on the
Scene Content Selection window.
7. Click the name of the DTM in the Selected DTMs list. Click Select Images on the Scene
Content Selection window. This brings up the Image Selection window.
8. Click Include Image on the Image Selection window. Select one or more images, then click
OK. The names of the images you picked appear in the Selected Images list in the Image
Selection window.
9. Click Done on the Image Selection window to return to the Scene Content Selection
window.
10. Click Done on the Scene Content Selection window to return to the Perspective Scene
window.
50.5.1.4 Scene Parameter Setup

1. Click File > Scene Parameter Setup on the Perspective Scene window.
2. Use the default parameter settings. Click Done on the Scene Parameter window to return to
the Perspective Scene window.
50.5.1.5 Scene Rendering

1. Enter ‘1’ in both the Starting Scene and Ending Scene fields.
2. Click Render Scenes, then OK to any warning messages.
50.5.1.6 Scene Display

1. Click Tools > Animation on the main workstation window. This brings up the Animation
window.
2. Click File > Input Image File on the Animation window. Select your image file from the
list (.img) then click OK.
3. Click Start on the Animation window.
4. Animation pops up a window containing your scene.
5. When you are finished viewing your scene, click File > Exit on the Animation window.

50.5.1.7 Sample Execution: Automated Route

Perform Route Setup, Scene Content Selection, and Scene Parameter Setup as described above.
The automated route will be generated around the area

delineated by the selected DTMs.
Click Tools > Automated Route on the Perspective Scene window. This will create view and aim
route features in your selected route feature database and automatically generate the eye point
file.
50.6 Perspective Scene’s Advanced Features
50.6.1 Feature File Preparation

If the region contains buildings or other objects that you want to model, you must build a Feature
File containing the buildings stored as volume features. All building roofs must be delineated in
a clockwise direction. See “Clockwise or Counter-Clockwise Orientation” on page 42-41.
In addition, you should delineate your eyepoint route (as a line feature) using Feature Extraction
before running Perspective Scenes. Then, during Perspective Scene, you can select the route from
the Feature database and the route will be used to generate your eyepoint route. If you delineate
the route in Feature Extraction, the feature class of the route must be PS_ROUTE. See “Feature
Database and Extraction Specification,” Appendix C for more details.
Building surfaces hidden from input images can be determined by viewing the features. You may
then (optionally) use Feature Extraction to attach artificial texture patches (such as brick walls or
false store fronts) to the hidden building sides. If you want to attach special textures or images to
the building sides, the building feature class must have special attributes, including
shade_flag and shade_value. See “Texture Patch” on page 42-24. Texture Patch must be
available to you for use. You do not have to attach hidden facets to hidden building sides: they
will be rendered a shade of gray if no texture patch has been attached.
50.6.2 Terrain File Preparation

Perspective Scenes does not support insets and does not do Z buffering. If you have DTMs with
different resolutions, select the DTMs in descending order of resolution from highest to lowest
resolution.

The basic Perspective Scene algorithm takes an image and drapes it over a DTM and performs
the calculations to turn the result into a perspective scene.
Side View
Generated Scene’s Contour

DTM Posts Building
Ground
From this side view you can see that the generate scene closely follows the ground, except at the
building. This illustrates one of the limitations of generating a scene with DTM data only.
To solve that problem, Perspective Scenes allows you to include feature database in the scene
content file. This gives Perspective Scenes the precise location of features such as building so that
it can generate a more accurate scene.
Side View

DTM Posts
Building
Ground
The sides of a building present a special problem. Since they are normally photographed at an
extreme angle, it is difficult to construct what they look like from the image alone. In order to
create better quality scene, Feature Extraction allows you to specify a “Texture Patch” for a
feature. This means that you can take a photograph of the side of a building, attache it to the
building as a texture patch and Perspective Scenes will use it when generating the scene
containing the building.

Feature’s Texture Patch

Side View

DTM Posts
Ground
50.6.3 Color Imagery

In order to get good-looking colors on an 8 bit color display, the software must create a color table
based on the colors in the image. When SOCET SET loads an image into the console window, a
new color table is created. The brightness and contrast of the image can be adjusted by the
controls at the bottom of the screen. Adjusting these controls makes subtle changes in the color
table.
Perspective Scenes will always create optimum colors on a 24-

bit display system.
Perspective Scene Generation and Animation use the color table generated for the console
window. This means that you need to load an image into the console window which is similar to
the image you are generating or viewing. Problems can occur if this is not done.
For example, suppose you load a color image in the console window. The color table is now filled
with the best colors from the image. You then try to use Perspective Scene Generation to generate
a grayscale image. When Perspective Scene Generation tries to display the image, it finds the
color table filled not with gray values, but with colors. An attempt will be made to map the
grayscale values to their nearest color value, however the results will display poorly.
Perspective Scene Generation and Animation can be run stand alone, that is without the main
SOCET SET image display. In this case, they will construct the best general purpose color
translation possible. For gray scales this looks very good, however the quality of color images is
rather limited.
In summary, for best results you should do the following:
1. Before you run Perspective Scenes or Animation, you should load an image onto the Main
View Port on the console monitor (the extraction monitor is not involved).
2. The image that you load on the main view port should be one of the images you are
inputting to Perspective Scenes or Animation, especially if the image is color.
3. If the image is color, you should use the Image Display Preferences tool (See “Image
Information” on page 61-35) to set the console display mode to Pseudo Color, and then
reload the image to the console monitor. This causes the color cube to be computed.
4. If the perspective scene is a wireframe, either load a grayscale image on the console
monitor or set the Image Display Preferences to display any grayscale band on the console
monitor.

5. Changing the Image Display Preferences while the Perspective Scenes or Animation
display is already up may cause the scenes to look awkward on the display. If this occurs,
change the Image Display Preferences to the settings used when the Perspective Scenes or
Animation display was first activated.
WHAT IS ON THE COLOR

CONSOLE IMAGE PERSPECTIVE PERSPECTIVE SCENE COLOR HANDLING
DISPLAY? SCENE?
An image used in the No Best results.

generation of the scene Grayscale output based on the Console windows colors.
Brightness and Contrast Controls change the image.
An image used in the Yes Best results.
generation of the scene Perspective Scenes uses the color cube computed by.
This is designed to make the best use of the color table
for the scene.
An image having No Poor results.
nothing to do with the Grayscale based on the wrong image (the one in the
perspective scene Console window). In general this will look OK.
An image having Yes Very poor results.
nothing to do with the The colors table is loaded with colors for the RT
perspective scene. console window. The Perspective Scene display will try
to use this as best it can, but since the colors are
customized for another image, the results look very
bad.
SOCET SET Not No Good results.
Running A default grayscale color table is loaded.
SOCET SET Not Yes Fair results.
running Perspective scenes will load a default color, generic,
8 bit display color cube. The results will look OK, but are limited by
the small number of colors available. Better results can
be obtained by using Image Display Preferences to
compute a custom color cube.
SOCET SET Not Yes Best Results.
running Perspective scenes makes full use of the 24 bit display.
24 bit display
50.7 Eyepoint Route Setup and Aim Point Route Setup

You use Eyepoint Route Edit to define the path that the imaginary viewer will fly along (called
the eyepoint route). The Aim Route Edit buttons allows you to edit the path that the viewer will
look at (called the aim route) along the flythrough.
Route editing makes use of the eyepoints and aim points that you delineate to calculate the
generated eyepoints and the generated aim points with which the perspective scenes will be
generated. The eyepoints are stored in an eyepoint file for use during the Scene Rendering phase.
You can specify the aim points and eyepoints with one of two different methods: (1) you can
delineate the routes interactively within the Route Edit window; or (2) you may select a pre-
existing linear feature from a feature database.

Route editing generates the generated eyepoints and generated aim points using the Spline
Parameters you specified on the Route Editor window. The Spline Parameters consist of a
splining algorithm option (Cubic or Uniform Cubic) that generates variably spaced eyepoints,
Velocity (assuming a 30 frame per second playback), and Distance between eyepoints (both for
evenly spaced eyepoints).
If an aim route is not specified, the default aim direction is along a tangent to the eyepoint route
or is given by the default angles for yaw, pitch, and roll, if specified, on the Route Editor window.
It is also possible for separate segments of the eyepoint route to look at separate segments of the
aim route. Segments of the eyepoint route that are not assigned to an aim route segment will look
in the default aim direction.
50.8 Route Feature File

The Route Feature File Window prompts you to choose the route feature file that contains both
the eyepoints and aim points.
50.9 Eyepoint Route Editor

Click Eyepoint Route Edit to start the Eyepoint Route Editor. You use the Eyepoint Route Editor
window to edit the eyepoints for the eyepoint route of your set of perspective scenes. This
window allows you to select, create, edit, draw, and/or erase a specific route. The Eyepoint Route
Editor window displays the currently selected route and all the eyepoint coordinates that comprise
that route. You may also add, insert, edit, or delete points within the eyepoint list.

The Eyepoint Route Editor window’s selections are as follows:
SELECT TO
Selected Route Display the name of the route feature in the feature file that you selected
(with the Select button) for editing. If you have not created any route
features yet, you must create one by clicking the Create button and
entering the name of the new route.
Route BLANK SPACE
Select Prompt you to pick an existing route feature from the route feature file.
Create Prompt you for the name of a new route feature.
Assign Assign all eyepoints between a BEGIN (B) and END (E) to be
INTERMEDIATE (I). For more information, See “Execution - Specifying
the Eyepoint Route’s Aim Information” on page 50-24.
Way Pt BLANK SPACE

Append, Insert, Edit Prompt you to enter the coordinates and elevation of the point.
Delete Delete the point from the point list.
List Display a scrolling list of points, one per line. Includes point index
number, latitude, longitude, elevation, point type (T for tangent, B for
begin segment, I for intermediate, E for end segment), and aim point index.
Algorithm Have two options:
• Through Points
• Tangent to Segments
Smoothness Determine the number of eye points that are created. This is the ratio of
view points to eye points. For example, smoothness of 0.25 will create 4
eye points for each viewpoint. Smoothness 1.0 will make one eye point for
each view point. 0.1 makes 10 eye points per view point. Values must be
between 0.0 and 1.0.
Velocity/Distance Enter the velocity and distance between eyepoints for eyepoints to be
generated with a constant spacing.
Yaw, Pitch, and Roll Display the default rotations for a eyepoint if you did not specify a
corresponding aim point.
Close Close the Eyepoint Route Editor window.
50.9.1 Specifying the Spline Parameters

The Spline Parameters will directly apply to the eyepoint path and may or may not apply to the
aim point path. If an aim segment is specified for part of the eyepoint path, the software will
attempt to match the number of eyepoints on the aim segment with the number of those on the
eyepoint segment by using the same spline parameters. If the number of eyepoints do not match,
the aim point segment will be calculated with a constant spacing algorithm using an automatically
chosen spacing value.
50.9.1.1 Algorithm
Algorithm used to calculate the eyepoint and aim points is a two-step procedure. The first step
produces variably spaced eyepoints. These variably spaced eyepoints are then used to calculate
constantly spaced generated eyepoints. You can elect to run both steps or disable one of the two
to generate eyepoints. To run both steps, choose the desired spline algorithm.

50.9.1.2 Smoothness
Set the Smoothness field to a value from 0.001 to 1.0. 0.001 produces the smoothest spline and
1.0 produces the roughest spline. Set either the Velocity or Distance fields to the desired value.
50.9.1.3 Velocity/Distance
The Velocity input field indicates that eyepoints are to be generated along the route at a spacing
that will reflect that velocity when viewed at 30 frames per second. The Distance input field
indicates the spacing between the eyepoints to be generated. Velocity and Distance are
interrelated; therefore, if you update one of these input fields, the other will be updated and
displayed by the software. Running both steps produces constantly spaced eyepoints.
To disable the constant velocity step and run only the variable velocity step, specify a value of
0.0 for either the Velocity or Distance input fields. Choose the desired spline algorithm and
specify the desired Smoothness in the input field. Disabling the constant velocity step produces
variably spaced eyepoints.
To disable the variable velocity step and run only the constant velocity step directly on the
eyepoints, choose the Cubic spline algorithm and specify a Smoothness of 1.0. Set the Velocity/
Distance to the desired value. Disabling the variable velocity step produces constantly spaced
eyepoints.
50.9.2 Execution - Specifying Default Rotations

The default rotation fields of Yaw, Pitch, and Roll are used to manually define where each
eyepoint is looking. The default Yaw and Pitch are given to every eyepoint that is not assigned
to an aim point. The default Roll is given to every eyepoint generated regardless of where it is
aiming. A default Yaw and Pitch of 0.0 degrees allows eyepoints without an aim point assigned
to look at a tangent.
50.9.3 Execution - Route Setup

1. Click Route Feature File to select a Route Feature File. A Feature File Selection window
is displayed. To use an existing file, select the name of the desired feature file in the file
list, then click OK. To create a new feature file, type a new name in the text box of the
Feature File Selection window, then click OK. The file name will be displayed on the
Perspective Scene Production window and the Route Selection window for reference only.
2. Click Eyepoint Route Edit to open or create an eyepoint route. See “Eyepoint Route
Editor” on page 50-18 for instructions on the Eyepoint Route Editor window.
3. [Optional] Click Aim Route Edit to open or create an Aim Route. See “Aim Route Editor”
on page 50-24 for instructions on the Aim Route Editor window.
4. Click Generate Eyepoints on the Route Setup window. You are warned that any previously
generated eyepoints will be overwritten. Click OK to proceed.
5. The # of Eyepoints field and the Total # of Scenes field on the Route Setup window will be
updated with the results of Eyepoint Generation. The numbers displayed in each field will
differ if any of the eyepoints are defined as Pivot Points (See “Eyepoint Attribution” on
page 50-27).
6. [Optional] Click Eyepoint Attribute to customize the eyepoints generated in step 4.
7. Draw the route by clicking Draw. You may toggle the Splines, Eyepoints and Rays on or
off. See “Perspective Scene (Multiple Scene)” on page 50-7 for descriptions of Splines,
Eyepoints and Rays.
8. Click Done to save the route files and close the Route Setup window.

50.9.4 Edit Point

You use the Edit Point window to specify the coordinates, elevation, and type of a new or existing
point.
The Edit Point window’s selections are as follows:
SELECT TO
Point # Identify the point index number. To edit a different point, enter its index in
this field, followed by a carriage-return. This will load the data for the
point into the window, and will recenter the image at the location of the
point. You can also use the Next and Previous buttons to cycle through the
list of points.
Latitude or Y Identify the point latitude coordinate.
Longitude or X Identify the point longitude coordinate.
Elevation Identify the point elevation value.
Aim Type Choose the Aim Type from the pulldown.
• TANGENT—All generated eyepoints between this eyepoint
and the next eyepoint will look along the tangent to the route.
• BEGIN—All eyepoints starting from this eyepoint will look at
the aim points starting from the aim point indicated in the Aim
Point # Field.
• INTERMEDIATE—All generated eyepoints between this
eyepoint and the next eyepoint will continue to look at the aim
point segment started by a Begin Segment and finished by an
End Segment.
END—All generated eyepoints before this eyepoint will look at the aim
points before the aim point indicated in the Aim Point # Field.

SELECT TO
Aim Point # This is the index of the point in the aim route that this point in the eyepoint
route will be looking at.
Next, Previous If you are currently editing an existing point (as opposed to appending a
new one) you can cycle through the list of points by clicking the Next or
Previous buttons. The image is recentered at the location of the point.
Sample You use this button to directly sample the coordinates of the extraction
cursor. This enters the latitude, longitude, and elevation fields of the Edit
Point window. To use this capability, follow these steps:
1. Toggle the to the extraction cursor.
2. Use the mouse and trackball to move the extraction cursor to
the desired location.
3. Toggle back to the mouse cursor.
4. Click Sample.
Optionally, you can also use the LMB to sample the point. In that
case, steps 3 and 4 become:
3. Press the LMB.
4. Toggle back to the mouse cursor.
Cancel Cancel the last sample operation you performed.
Close Commit your changes to the point and closes the Edit Point window.
Optionally, you may press the RMB (while toggled to the extraction
cursor).
50.9.5 Execution - Editing an Eyepoint Route

A route feature is a multi-segmented line represented by a set of 3-D points. Complex routes, such
as aircraft flight paths, should be generated using the spline tools within Feature Extraction, or
by setting the spline parameters on the Eyepoint Route Editor window. For simple routes, such
as a straight view from a rooftop, it may be simpler to use the route creation and editing tools on
the Eyepoint Route Editor window. This section describes the steps used to generate routes using
the Eyepoint Route Editor.
The first time you create a perspective scene with the name specified on the main perspective
scene window, the Route Feature File field will be blank. You can select a route which was
created in Feature Extraction, or you can create a new route using the Eyepoint Route Editor
window. In subsequent sessions, the Selected Route will default to the most recently used route.
However, you may still select other routes, or create new ones as described below. Any number
of routes can be created and stored in the Feature File; but only one may be selected at a time to
generate a set of perspective scenes. When choosing or creating new routes, the previously
displayed route information will be saved before the new route is opened.
1. Click Route Feature File to choose an existing route. The Route Feature List window will
be displayed with a list of features which have the class attribute of PS_ROUTE.
If no PS_ROUTE features are available for the selected Feature

File, the system will beep and a message will be displayed on
main Perspective Scenes window. You must create a new route
(see step 2).
2. Highlight one of the routes and click Done to accept the route and close the window.

3. If the route requires no modifications, skip to step 4. If you do not have an existing route,
proceed to step 2.
4. Click Eyepoint Route Edit and click Create to create a new route. The Create Route Feature
window will be displayed.
5. Type a name for the new route and click OK to accept the route and close the window. The
new name will be displayed on the main Perspective Scene window and on the Route Setup
window for reference.
6. Add new points to the route by clicking Append. This brings up the Edit Point window. A
route must consist of at least two (2) points.
7. There are four ways to enter the coordinates and elevation data for a point:
a. Type the coordinates/elevation in the text boxes on the Edit Point window. Click Done
after each point is entered.
b. Bring up Coordinate Measurement window—move the image cursor to the desired
point. Cut and Paste the values from the Coordinate Measurement window to the Edit
Point window. Click Done after each point is entered.
c. Toggle to the extraction cursor and move to the desired point in the image using the
mouse; use the Z control to adjust elevation. Toggle back to the mouse cursor and
click Sample in the Edit Point window. Repeat for each point. Click Done when you
are finished adding points.
d. Toggle to the extraction cursor and move it to the desired point in the image using the
mouse; use the Z control to adjust elevation. Sample the desired point by pressing the
LMB. Repeat for each point. Press the RMB when you are finished adding points.
8. The list of points will be displayed on the Eyepoint Route Editor window. You may edit,
delete or insert additional points as described in steps below.
Make sure that each point in the route is above ground level.
The initial extraction cursor position may be at or below
ground level; you must re-position it using the Z-control.
Scenes generated at points below ground level will not display
any imagery.
Each eyepoint may point to an aim point.
9. On the Route Setup window, set the Routes option to Yes and then click Draw. Route Setup
draws your eyepoint route (and the aim route, if you have one at this point).
10. [Optional] Edit a point by first selecting it in the scrolling list; then click Edit. The point
you chose is displayed in the Edit Point window. You can modify the coordinates and
elevation of the point by any of the four methods described above for appending points.
11. Click Done to close the Edit Point window and return to the Eyepoint Route Editor window.
12. [Optional] To insert a new point within the route, select the point you want to insert the new
point BEFORE by clicking on it. Then click Insert. The Edit Point window is displayed;
you can specify the coordinates and elevation of the new point by any of the four methods
described above for appending points.
13. Click Done to close the Edit Point window and return to the Eyepoint Route Editor window.
14. [Optional] To delete a point, select the point you want to delete by clicking on it. Then click
Delete. The Delete Point window is displayed, requesting confirmation before deleting the
point. Click OK to delete the point from the list.
15. [Optional] If you already have aim information specified for your eyepoints, and you wish
to assign all eyepoints between a BEGIN (B) and END (E) to be INTERMEDIATE (I) click
Assign.

16. Close the Eyepoint Route Editor window by clicking Done.
50.10 Aim Route Editor

You start the Aim Route Editor window by clicking Aim Route Edit on the Route Setup window.
You use the Aim Route Editor window to edit the aim points for the aim route of your set of
perspective scenes. This window allows you to select, create, edit, draw, and/or erase a specific
route. You also use this window to assign a segment of the eyepoint route to look at a segment of
the aim route. The Aim Route Editor window displays the currently selected route and all the
point coordinates that comprise that route. You may also add, insert, edit, or delete points within
the point list.
The Aim Route Editor window’s buttons and fields are identical to those in the Eyepoint Route
Editor window (See “Eyepoint Route Editor” on page 50-18.) with the exception that the Spline
Parameters and Default Rotations controls which do not apply to aim routes and are therefore not
modifiable in the Aim Route Editor window.
50.10.1 Execution - Specifying the Eyepoint Route’s Aim Information

You can edit the aim information for the eyepoint route at any time during the aim route editing.
However, it is easier to edit this information after you have created both the eyepoint and aim

routes. By default, the aim points will look at a tangent to the eyepoint route. To override this,
you can specify the whole aim path or segments of the aim path for the eyepoints to look at. To
accomplish this, there are four Aim Types that you can assign to a eyepoint:
AIM TYPE DESCRIPTION
Tangent All eyepoints between this eyepoint and the next eyepoint will look at a
tangent.
Begin Segment All eyepoints starting from this eyepoint will look at the aim points
starting from the aim point indicated in the Aim Point # Field.
Intermediate All eyepoints between this eyepoint and the next eyepoint will continue to
look at the aim point segment started by a Begin Segment (B) and finished
by an End Segment (E).
End Segment All eyepoints before this eyepoint will look at the aim points before the
aim point indicated in the Aim Point # Field.
I
I
B
Eyepoint Route
Aim Route
All eyepoints between a eyepoint with type (B) and a eyepoint with type (E) will look at all aim
points between the aim point that is numbered with the (B) and the aim point that is numbered
with the (E). For assigning a eyepoint segment that spans over several eyepoints, the eyepoints
between the (B) and (E) must be marked with an (I). The points in a eyepoint segment and an aim
segment will always have a one-to-one correspondence.
Every Begin Segment (B) must have an End Segment (E). Only Intermediate (I) points are
allowed between a B and an E.
To set the aim information for any existing eyepoint, follow the directions for editing a point as
described above (See “Execution - Editing an Eyepoint Route” on page 50-22). Before sampling
the point, set the Aim point type by selecting the desired value from the Aim Type option in the
Edit Point window. The eyepoint list in the Eyepoint Route Editor window is updated
automatically. If the Aim Type is either BEGIN or END, you must also enter the desired aim point
number in the Aim Point # field, followed by pressing the Return key on the keyboard. Click
Done to record the changes.
You can also specify aim information while you are appending or inserting a eyepoint. First
follow the directions above for appending or inserting a point, but before sampling the point, set
the Aim Point Type on the Edit Point window. If the aim point type is either BEGIN or END, you

must also enter the desired aim point number in the Aim Point # field, followed by pressing the
Return key on the keyboard. This input field can also be set later if you have not yet created any
aim points.
50.10.2 Execution - Editing an Aim Route

1. Choose an existing route by clicking Select. The Route Feature List window will be
displayed with a list of features which have the class attribute of PS_ROUTE.
2. Highlight one of the routes and click Done to accept the route and close the window.
3. If you wish to create a new route proceed to step 4, otherwise go to step 9.
4. To create a new route, click Create. The Create Route Feature window will be displayed.
5. Type a name for the new route and click OK to accept the route and close the window. The
new name will be displayed on the main Perspective Scene window and on the Route Setup
window for reference.
6. Add new points to the route by clicking Append. This brings up the Edit Point window. A
route must consist of at least two (2) points.
7. There are four ways to enter the coordinates and elevation data for a point:
a. Type the coordinates/elevation in the text boxes on the Edit Point window. Click Done
after each point is entered.
b. Bring up Coordinate Measurement window - move the image cursor to the desired
point. Cut and Paste the values from the Coordinate Measurement window to the Edit
Point window. Click Done after each point is entered.
c. Toggle to the extraction cursor and move to the desired point in the image using the
mouse; use the Z control to adjust elevation. Toggle back to the mouse cursor and
click Sample in the Edit Point window. Repeat for each point. Click Done when you
are finished adding points.
d. Toggle to the extraction cursor and move it to the desired point in the image using the
mouse; use the Z control to adjust elevation. Sample the desired point by pressing the
LMB. Repeat for each point. Press the RMB when you are finished adding points.
8. Click Done on the Route Editor window when you are finished adding points to save the
points and close the Edit Point window. The list of points will be displayed on the Aim
Route Editor window. You may edit, delete or insert additional points as described in steps
below.
9. On the Route Setup window, set the Routes option to Yes and then click Draw. Route Setup
draws your aim route (and the eyepoint route too).
10. [Optional] Edit a point by first selecting it in the scrolling list; then click Edit. The point
you chose is displayed in the Edit Point window. You can modify the coordinates and
elevation of the point by any of the four methods described above for appending points.
11. Click Done to close the Edit Point window and return to the Aim Route Editor window.
12. [Optional] To insert a new point within the route, select the point you want to insert the new
point BEFORE by clicking on it. Then click Insert. The Edit Point window is displayed;
you can specify the coordinates and elevation of the new point by any of the four methods
described above for appending points.
13. Click Done to close the Edit Point window and return to the Aim Route Editor window.
14. [Optional] To delete a point, select the point you want to delete by clicking on it. Then click
Delete. The Delete Point window is displayed, requesting confirmation before deleting the
point. Click OK to delete the point from the list.
15. Close the Aim Route Editor window by clicking Done.

50.11 Eyepoint Attribution

Eyepoint Attribution provides the means by which you specify attribute eyepoints along the
selected route at which perspective scenes will be generated.
The default direction of view for eyepoints tangent to the eyepoint route is from eyepoint to aim
point. In this case, the Pivot Point and Aim Eyepoint values are set to “no” (n). The Yaw, Pitch
and Roll values default to zero (0) or to the values entered in the Eyepoint Route Editor window
as default rotations for the eyepoints. By using the Eyepoint Attribution window, any of these
eyepoints may be defined as a Pivot Point or their Yaw, Pitch and Roll settings may be modified.
However, if an aim route was specified and the points were defined to use the aim route points as
the look direction, then the viewing direction of each eyepoint corresponds to the points on the
aim route. Thus, the angles for Yaw and Pitch are derived from the direction of view from the
eyepoint to its corresponding aim point.
All Roll values default to zero (0) regardless of where the eyepoint is aiming.
The Eyepoint Attribution Window is used to customize the viewing angles of each individual
eyepoint. Yaw, Pitch and Roll values can be modified to simulate the actual flight path of an
aircraft. Pivot points can be set to provide the viewer with a panoramic look at the scene from a
single eyepoint. The Latitude, Longitude and Elevation values can also be modified, if desired,
to obtain a specific look from a given eyepoint.
The Eyepoint Attribution window’s selections are as follows:
SELECT TO
Eyepoint Number Indicate the current eyepoint number you are setting the attributes for. To
access a particular eyepoint, type its number in this field and then press the
Return key. You can also step through the list of eyepoints with the Next
Eyept and Prev Eyept buttons.
Pivot Point Set Indicate whether this eyepoint is set to be a pivot point (y/n).
Aim Point Set Indicate if this eyepoint was generated from a eyepoint route and aim
route. Eyepoints cannot be both aim points and pivot points.

SELECT TO
Latitude or Y, Display the coordinates of the location of the eyepoint. You can modify
Longitude or X, Elevation these values.
Yaw, Pitch, Roll Show the orientation of the eyepoint, as calculated from the eyepoint route
and aim routes. You can modify these values.
Field of View Describe the horizontal and vertical extent of the view volume. You cannot
modify these values from this window; use the Scene Parameter Setup
window instead.
Clipping Planes Describe the locations of the front and back of the view volume. You
cannot modify these values from this window; use the Scene Parameter
Setup window instead.
Next Eyept, Prev Eyept Move sequentially through the list of eyepoints.
Set Pivot Start up the Set Pivot Point window, which prompts you for the pivot
parameters.
Move to Pnt Move the extraction cursor to the location of the current eyepoint.
Draw View Draw the view volume for the current eyepoint.
Close Close the Eyepoint Attribution window.
50.11.1 Execution - Modifying Eyepoint Attributes

1. To edit the attributes of individual eyepoints, click Eyepoint Attribute on the Route Setup
window. This displays the Eyepoint Attribution window.
2. Enter an eyepoint number in the Eyepoint Number input field. This displays the parameters
for the eyepoint.
3. Modify the numerical parameters (location, orientation).
4. [Optional] You step through the list of eyepoints by clicking Next Eyept and Prev Eyept.
5. Click Close to return to the Route Setup window.

50.11.2 Execution - Attributing An Eyepoint As A Pivot Point

1. First, click Eyepoint Attribute on the Route Setup window. This displays the Eyepoint
Attribution window.
2. Enter number of the eyepoint in the Eyepoint Number input field. This displays the
parameters for the eyepoint.
A eyepoint cannot both be set to an aim point and also be a

pivot point. For this reason, the Set Pivot Point is dimmed for
eyepoints that have a corresponding aim point.
3. Click Set Pivot. This displays the Set Pivot Point window.
4. Enter the Pivot Start Angle in degrees. This is the angle where your pivot scenes will begin.
A start angle of 0 degrees starts your pivot looking straight ahead. The pivot start angle
increases in a counter-clockwise direction.
5. Enter the Pivot Delta Angle in degrees. This is the total angle of your pivot scenes. The
pivot scenes will rotate in a counter-clockwise direction specified by this angle.
6. Enter the Number of Pivot Scenes. This is the total number of scenes you wish to display
for the pivot. The pivot begins at the Pivot Start Angle and will rotate in a counter-
clockwise direction specified by the Pivot Delta for the number of scenes indicated in
Number of Pivot Scenes. For example, with a Pivot Start Angle of 20 degrees, Pivot Delta
of 90 degrees, and Number of Pivot Scenes of 4, the pivot scenes are generated at 20, 50,
80, and 110 degrees counter-clockwise.
7. Select YES or NO for Pivot Back to Start. If YES is selected, the pivot will rotate back to
the original Pivot Start Angle in a clockwise direction. For the above example, with YES
selected, the pivot scenes are generated at 20, 50, 80, 110, 110, 80, 50, 20 degrees counter-
clockwise.
8. To save the modifications, you click Accept. Click the Done button to return to the
Eyepoint Attribution window.
50.11.3 Execution - Drawing The View Volume Of An Eyepoint

You may draw the view volume of the current eyepoint by clicking Draw View.
The view volume is generated based on the field of view values and clipping plane values
displayed on the Eyepoint Attribution window. These fields are displayed on this window for
reference only but can be modified through the Scene Parameter Setup window. Any
modifications you make to these values through the Scene Parameter Setup window will be

reflected in this window as well. The view volume is also based on the current eyepoint's
coordinates and yaw, pitch, and roll angles.
50.12 Scene Content Selection

Scene Content Selection is the procedure you use to select the data to be included in the
renderable database. This data includes feature files, selected features from those feature files,
DTMs, and images to be associated with the feature and DTMs.
The Scene Content Selection window displays the selected feature and DTMs which will populate
the renderable database. You may choose to include or remove files from either list.S
The Scene Content Selection window’s selections are as follows:
SELECT TO
Scene Content File Prompt you to open an existing scene content file or create a new one.
FDBs Prompt you to add/delete FDBs to the Selected FDB list with a RMB click.
DTMs Prompt you to add/delete DTMs to the Selected DTM list with a RMB
click.
Select Images Prompt you to choose which images will be associated with a selected
FDB or DTM.
NOTE: The total number of unique images specified for all the
feature databases and DTMs should not exceed 10.
Select Features Prompt you to choose which features in the selected FDB will be used by
Scene Rendering. An additional window will open displaying features.
Done Close the Scene Content Selection window.
50.12.1 Executions
50.12.1.1 Selecting a Scene Content File
Click (Ellipse Tool) next to Scene Content File on the Perspective Scene window to view a list
of selections. Click Open to display the Scene Content File Selection for processing. If the file is
successfully opened or created, the file name will be displayed on the Perspective Scene
Production window for reference only.

50.12.1.2 Including a File In The Scene Content

Initially, the FDBs and DTMs specified in the currently open scene content file will be displayed
after adding them. To include a file in the scene content, right click and select Add to display
either the FDB list window or DTM list window. In the file selection dialog, you may pick more
than one file at a time.
50.12.1.3 Removing a File From Scene Content

To remove a file from the scene content, you highlight a file from either the FDBs or the DTMs,
right click and select Delete to remove them. The file will be removed and the appropriate list
will be updated. Only one file may be deleted at a time.
50.12.1.4 Selecting Images for Feature or DTMs

Typically, you will next want to select images to associate with the feature and DTMs being used
in the scene content. First you highlight a feature or DTM on the Scene Content Selection
window, and then click the appropriate Select Images button. Only one file can be highlighted on
the Scene Content Selection window during the Select Images operation. The Image Selection
window will then be displayed with the file type of the current file, either Feature or DTM,
displayed in the Filetype field, the name of the current file in the Filename field, and a list of
images currently associated with that file in the Selected Images list. The displayed list of images
for the selected feature or DTM is obtained from the currently open scene content file.
50.12.1.5 Including an Image

You include an image for the selected FDB or DTM by right clicking in the field and selecting
Add. An image list window will then be provided. You may then select a directory path and/or
image name using the mouse. The image name will be included at the end of the Selected Images
list on the Image Selection window.
50.12.1.6 Removing an Image

You may remove an image from the selected FDB or DTM by right clicking in the field and
selecting Remove. The image name will be removed and the image list updated on the Image
Selection window.
50.12.1.7 Selecting Features for Scene Content

Next, you may choose which features of a feature file are to be included in Scene Rendering:
1. Select the name of the feature file in the Selected Feature Files list on the Scene Content
Selection window.
2. Click Select Features on the Scene Content Selection window. This brings up the Feature
Selection window.
3. Set the Feature Selection option to ALL. Click Remove. This clears the list of Selected
Features.
4. Set the Feature Selection to Feature, then click Include. This brings up the Feature List
window. Select the names of the features you wish to include. When you are finished
picking features, click Done on the Features List window to return to the Feature Selection
window.
5. The Selected Features list on the Feature Selection window reflects the features you picked.
6. Click Close on the Feature Selection window to return to the Scene Content Selection
window.

50.12.1.8 Sorting Feature Lists

Either the Selected Features list on the Feature Selection window or the Features list on the
Feature List window can be sorted alphabetically by feature name or numerically by feature
number. You can specify the type of sort to perform from Sort Option. If the Feature List window
is displayed, the sort will be performed on the features list of that window. Otherwise the sort will
be performed on the Selected Features list of the Feature Selection window.
50.13 Scene Parameter Setup

Scene Parameter Setup sets the parameters which will apply to the entire set of perspective scenes
to be generated. To obtain this window, click Scene Parameter File. This window set allows you
to specify a specific set of scene parameters, and to modify the values for those parametrized.
The Scene Parameter Setup window’s selections are as follows:
SELECT TO
Scene Parameter File Open an existing scene parameter file, or creates a new one.
Scene Resolution BLANK SPACE
Horizontal (pixel) Display the horizontal size of the scene (in pixels).
Vertical (pixel) Display the vertical size of the scene (in pixels).
Field of View BLANK SPACE
Horizontal Display the horizontal size of the field of view (in degrees).
Vertical Display the vertical size of the field of view (in degrees).

SELECT TO
Clipping Planes BLANK SPACE

Front Display the distance (in feet or meters) in front of each eyepoint that the
BLANK SPACE front of the view volume is placed. A negative value (such as
BLANK SPACE -100) is recommended to insure that the terrain and features nearest the
viewing position are rendered.
BLANK SPACE
BLANK SPACE
Back
Display the distance (in feet or meters) to the end of the viewing volume.
Features and terrain further than this value from the viewing position are
not rendered.
NOTE: If you are rendering a wire frame scene, this value should
be set to the farthest point you want included in the scene;
otherwise Perspective Scenes will render very slowly. For non-
wire frame scenes, the speed will not be affected by this
parameter.
Default Shading/ BLANK SPACE

Texturing Method BLANK SPACE
Terrain Shading Identify the method of shading or texturing that is used for DTM data if the
BLANK SPACE area being processed is not adequately represented in any selected image.
BLANK SPACE The values for this field include SUN SHADE, GRAY SHADE, and
RANDOM SHADE.
BLANK SPACE
BLANK SPACE
Terrain Gray Level
Identify the value of the gray shade used for default terrain shading if the
BLANK SPACE method chosen is GRAY SHADE.
Feature Shading Identify the method of shading or texturing that is used for feature data if
BLANK SPACE the feature being processed is not adequately represented in any selected
BLANK SPACE image. The values for this field include SUN SHADE, GRAY SHADE, and
BLANK SPACE RANDOM SHADE.
Feature Gray Level Identify the value of the gray shade used for default feature shading if the
method chosen is GRAY SHADE (0–255).
BLANK SPACE
BLANK SPACE
BLANK SPACE
Determine if the output images are to be in color. “Force Color” causes
Color Output color output to be generated. “Force Gray” causes gray shaded images to
BLANK SPACE be output. “Automatic” will cause color images to be output if any of the
BLANK SPACE input images is in color. (It will not check features or texture patches.)
Background Gray Identify the value of the gray shade used for the background shading of the
Level sky (0–255).
Face Vis Threshold Display the angle (deg) used as a tolerance point to determine when to
(deg) drape an input image over a polygon or when to shade the polygon using
BLANK SPACE the default shading/texturing method. This angle specifies the maximum
BLANK SPACE allowable angle between a polygon’s normal vector and a vector from the
polygon to the input image’s sensor position.
BLANK SPACE
BLANK SPACE
BLANK SPACE
Display the angle (relative to North in the horizontal plane) of the sun used
Sun Azimuth (deg) during rendering.
Ambient Light Display the minimum value (0–255) of light to apply to the rendered
image.
NOTE: Shading values are from 0 (black) to 255 (white).
Close Close the Scene Parameter Setup window.

50.13.1 Execution - Modifying the Scene Parameters

If a new scene parameter file has been created or changes are required to an existing set of scene
parameters, you will make all of the desired changes on the Scene Parameter Setup window. The
values in each of the input fields are read from the currently open scene parameter file. If you are
creating a new file, default values will be displayed. To modify any of the input files, you select
the desired input field with the mouse. This causes the input field to accept any keyboard input
that is typed. The scene resolution indicates the output size of each of the rendered images, or
perspective scenes, in pixels. The field of view indicates the volume of area around the eyepoint
to be contained in the perspective scene.
The horizontal and vertical fields of view should have the same
ratio as the horizontal and vertical components of the output
scene resolution. If not, the output scenes will appear to be
stretched.
The clipping planes define the front and back scene limitations to the perspective scene within
the view volume. The shade flags and values indicate what type of shading to apply to those areas
of scenes rendered where feature or DTM polygons may not have adequate imagery coverage.
The background color will be applied to any unrendered areas within the perspective scene.
50.14 Scene Rendering

Once you have selected all the input data and defined a route, Scene Rendering generates your
perspective scenes.
Scene Rendering may require large amounts of virtual

memory. You should close all unnecessary windows and
menus (i.e. close all windows and other applications) prior to
starting Scene Rendering.
50.14.1 Execution - Scene Rendering

Click Render Scenes, and the Scene Rendering displays a popup window containing a sliding bar
which indicates the percentage of processing completed, and an Abort button. If you do not select
Abort during processing and the scenes are generated successfully, the generated files will be
located in the specified destination system and directory path. During the Scene Rendering, you
cannot perform any other operations in Perspective Scenes until the rendering completes.
After the scenes are generated, you may preview them with a variety of tools, as described in the
Output Products chapter. The two most useful previewing mechanisms are (1) the Animation tool
(described below), and (2) Load the scenes one at a time into the main workstation window (this
works only if you created support files to accompany the scenes).
50.15 Animation
Animation plays back your Perspective Scene images in a window on the workstation console
monitor. The images may be displayed either singly or in an animated flythrough fashion.
To obtain this window, click Tools > Animation on the main workstation window.

The Animation window’s selections are as follows:
File > Exit Closes the Animation window.
SELECT TO
Rewind Rewinds to the first image in the flythrough.
Back One Display the previous frame in the flythrough.
Play Backward Play each scene in the flythrough starting with the last and ending with the
first.
Stop Stop the playback of images.
Play Play each scene in the flythrough starting with the first and ending with the
last.

SELECT TO
Forward One Advance the flythrough by one frame.
Fast Forward Display the last image in the flythrough.
Close Remove the image window from the screen.
Flythrough File: Use the currently image or flythrough being displayed.

Frames: ___ to ____ Identify the first and last frame number to be displayed. These can be
edited by the user.
Current Display the frame number we are currently displaying.
Speed Identify the frame increment. A speed of 2 will display every other frame.
Delay Identify the amount of time to delay between frames in milliseconds.
Display Scenes During Identify animation loads each image into memory when loading a
Loading flythrough. This can be a time consuming process. If you want to view the
images as they are loaded, set this option.
Loop Cause play and play backwards to loop continuously until Stop is pressed.
50.15.1 Frame Numbering

When preparing to generate a flythrough, you can select a generation rate. You can, for example,
generate a quick overview of the flythrough by generating every fifth scene. The frame numbers
used by Animation are for the generated frames starting with 1 and ending with the number of
frames generated.
50.15.2 Adjusting Image Appearance

If you have a Unix system which is set up with an 8-bit console, then you can use the brightness
and contrast controls on the Main Workstation window to adjust the appearance of the Animation
image window. For other systems and other display settings, you must adjust the appearance of
the images before the perspective scene generation by saving the image enhancements for all of
the source images. See “Image Enhancement” on page 4-12 for details on how to do this.
50.15.3 Producing .fly files manually

When you generate perspective scenes with SOCET SET, it will generate a fly file automatically.
The fly file contains a list of all the image disk files that constitute the flythrough. There may be
times when you want to view images in the Animation process but you do not have a fly file, for
example:
• Perspective scenes generated within another system

• Perspective scenes from SOCET SET version 3.0 or older

• Using Animation to display arbitrary image files (not perspective scenes)
To view such images in Animation, you must build a fly file manually by using a text editor, such
as text edit. The fly file contains a list of the individual image files in the exact sequence that you
want them to appear. Each file name in the fly file must contain the full directory path. Here is a
sample fly file:
/usr/geoset/images/my_project/anim1.img

Chapter 51
Terrain Analysis
Terrain Analysis covers visibility analysis using a DTM.
51.1 Overview
Terrain Analysis computes a viewshed based on a Digital Terrain Model (DTM). You attain this
window by clicking Products > Terrain Analysis.
51.1.1 When to Use Terrain Analysis

Terrain Analysis creates a viewshed mask. Before running Terrain Analysis you should create a
DTM either by importing it (DTED, DEM) or by running ATE. Then, before running Terrain
Analysis, use Interactive Terrain Editing to view the DTM and ensure that the DTM is accurate
and complete.
51.1.2 Data Flow

DTM(s) FEATURE FILE(S)
(optional)
MERGE
(optional)
TERRAIN
ANALYSIS
VISIBILITY ANALYSIS
DTM
SOCET SET Page 51-1

Chapter 51 - Terrain Analysis
51.2 Terrain Analysis

The Terrain Analysis main window’s selections are as follows:
File > Open DTM... Prompts you to pick a DTM for the use by Visibility Analysis.
File > Exit Exits the Terrain Analysis window.
SELECT TO
Open Input DTM Prompts you to pick a DTM for the use by Visibility Analysis.
Setup DTM Graphics Allows you to customize DTM Graphics preferences.
Page 51-2 SOCET SET

SELECT TO
Draw DTM Graphics Allows you to draw your DTM data graphically on top of the imagery on
the workstation monitor. This is useful for displaying terrain graphics on
top of the terrain shaded relief image and for displaying the Visibility
Analysis mask that Terrain Analysis produces. See “Terrain Graphics,”
Chapter 36 for a complete description.
Cancel Drawing Tool Cancels the drawing of the DTM on the imagery.
Auto Draw Terrain Graphics Toggles automatic drawing of terrain graphics ON or OFF.
Lower Left Display the latitude and longitude, or Y and X respectively, of the lower-
left corner of the area covered by a loaded DTM.
Upper Right Display the latitude and longitude, or Y and X respectively, of the upper-
right corner of the area covered by a loaded DTM.
Observation Point Display the editable observer position.
Mask Type Select option specifying whether the output mask highlights all visible
areas or invisible areas from the observer perspective.
Output To Select option specifying whether output is directly to the main Workstation
window or to a DTM disk file, designated in the Output VA File Name text
field.
Output File Name Display Output Visibility Analysis DTM name.
Start VA Generation Generate the Visibility Analysis model.
Terrain Analysis generates viewshed information. The input is a DTM and the location of an
imaginary viewer. The output is a Visibility Analysis data base that indicates what portions of the
DTM the viewer could or could not see. The output data is stored as a DTM and may be viewed
and processed like any other DTM.
If the region you are analyzing contains buildings, you may wish to model the buildings in the
input DTM before executing Visibility Analysis. You can model the buildings using several
techniques:
• Run Automatic Terrain Extraction with a dense post spacing.
• Manually extract the buildings using Interactive Terrain Extraction area editing
tools.
• Run Feature Extraction and extract the buildings, then merge the building features
into a ground-level DTM using DTM/Feature Merge.
51.3 Execution - Terrain Analysis

1. Open a project and load imagery in the main workstation window.
2. Activate Terrain Analysis by clicking Products > Terrain Analysis on the main
workstation window.
SOCET SET Page 51-3

3. Click File > Open DTM on the Terrain Analysis window to choose a DTM.
4. Set the VA Mask Type to Visible. This will color all points within the input DTM that are
Visible or ~Visible (not visible).
5. Select the output as either: (1) File—this will permanently save the results; you use
Interactive Terrain Editing to view the file. (2) Screen—the results will be immediately
displayed in the main workstation window; you adjust the display with the Terrain Graphics
buttons.
6. Click Setup DTM Graphics in the Terrain Analysis toolbar. See “DTM and Overlay Range
Windows” on page 36-3 for details.
7. Set the location of the viewer (the observation point) by either: (1) editing the values in the
text fields, or (2) by toggling to the extraction cursor, moving the extraction cursor to the
desired point, sampling the location with the LMB, and accepting the location with the
RMB.
8. Click Start VA Generation on the Terrain Analysis window.
9. If your output is to a file, you must load it into Interactive Terrain Editing and draw it. If
your output is to the screen, the graphics will be drawn as they become available.
If the output seems incorrect (too sparse or inaccurate), try

densifying the input DTM with DTM/Feature Merge and re-
executing Visibility Analysis.
10. You may repeat steps 7 through 9 to vary the location of the viewpoint
Page 51-4 SOCET SET

Chapter 52
Hardcopy Products and Image Maps

Anaglyph, Image Map, and Print Graphics allow you to print
your SOCET SET products.
52.1 Overview
Since imagery can be stored in a variety of formats, you need to be sure that the operation you
want to perform is compatible with the format of the image. For example, the preferred format
for handling large images in SOCET SET is a tiled format, since the disk access time is
substantially faster for a tiled format than for raster formats such as Sun raster or TARGA.
SOCET SET uses the VITec tiled format as its native image format. For this reason, importing an
image into SOCET SET (Frame Import) generates imagery in a tiled format. Note that many
hardcopy output devices can only accept certain image formats. For instance, the Kodak 7700
color printer will accept images only in a Sun raster format.
If you need to convert imagery from one format to another, you should select Preparation >
Import > Image > Import/Reformat on the main workstation window. See “Data Import and
Export,” Chapter 16 for details. In addition, there are a variety of off-the-shelf programs
available on Internet such as XV, ImageMagick, and Ghostscript that will convert image
formats.
This chapter describes the following methods for creating, viewing, and printing hardcopy
products:
Image Previewing Tools Utilities for previewing imagery on the workstation monitor.
Screen Dumps Copies the screen contents into a disk file which you can print or export.
Printing Images on a Laser Instructions on how to print Sun raster files on a Kodak 7700 color printer
Printer or a PostScript laser printer.
Anaglyph Creates anaglyph pseudo-stereo images.
Image Map Creates an image map file by surrounding the imagery with marginalia and
superimposing grid lines. You can then export the image map file or print it
on a plotter.
Print Graphics Writes SOCET SET graphics to a PostScript file.
SOCET SET Page 52-1

Chapter 52 - Hardcopy Products and Image Maps
52.2 Image Previewing Tools

Before printing a hardcopy of an image, you need to preview it on the workstation monitor so you
can detect and correct any quality problems.
The utilities for previewing an image or image map in SOCET SET are Animation, XV
(shareware available on Internet), imagetool (delivered with Solaris), and loading imagery into a
workstation window. Which previewing tool you use depends on the format and size of the image,
and whether or not you want to display color and roam through the image. The following table
summarizes the capabilities of these tools:
WORKSTATION
ANIMATION XV GHOSTVIEW
WINDOW
BLANKSPACE SunRaster Yes Yes Yes No

BLANKSPACE B&W
BLANKSPACE
BLANKSPACE SunRaster No Yes No No
BLANKSPACE Pseudo-Color
Display Tiled Format Yes Some Yes Some
Formats
Multi- No Yes Yes No
Spectral
Other No Yes Yes Yes
Formats
Post-script No No No Yes
BLANKSPACE Roam No No Yes No
BLANKSPACE
Capabilities Large Image No No Yes No
Fly-Thru Yes No No No
You use Animation to review one or more perspective scenes that you generated with Perspective
Scenes. See “Animation” on page 50-34 for details.
XV is copyrighted by the University of Pennsylvania and is not

distributed with SOCET SET. It is available over the Internet via
anonymous FTP from ftp.cis.upenn.edu.
See “Displaying Imagery” on page 4-10 for a description. You use this window when you want
to perform ground space measurements or when you want to use any of SOCET SET’s image
enhancement operations (See “Image Enhancement” on page 4-12 for a description). The
ghostview and ghostscript PostScript utilities are also available on the Internet.
Page 52-2 SOCET SET

52.3 Screen Dumps
52.3.1 Windows Platform

A screen dump is a disk file containing an image of what is on the entire screen. Making a screen
dump is the simplest way to generate a hardcopy product. To capture the entire screen, simply
press the “Print Screen” key on the keyboard. To capture just a window on the screen, just press
<Alt> Print Screen. This will store the screen image to the system clipboard. To retrieve the
image, simply open an application such as the imaging program provided under the accessories
menu under the start button and paste the image into the document. Once in the document, you
may save the image and/or modify to fit your specifications.
52.3.2 Unix Platform

A screen dump is a disk file containing an image of what is on the screen. Making a screen dump
is the simplest way to generate a hardcopy product. The screen dump file is stored in the
X-windows dump format. After you have made a screen dump, you can print it on a printer.
Arrange Display on
the Screen
Make the Screen Dump
Screen dump image file

in X-Dump format
Convert to PostScript ImageMagick
format with xpr Convert Tool
Preview image
with xwud tool
Screendump Screendump
In PostScript format In SunRaster format
Laser Printer
Print PostScript
file with 1pr
The steps to make a screen dump are:

1. Arrange your imagery and other windows you wish to include in your screen dump on the
screen. Use Annotation to annotate imagery or to add comments and notes.
2. Make the screen dump by selecting Output > Screen Dump on the main workstation
window. You have two choices:
a. Full Screen—captures and prints the entire screen.
SOCET SET Page 52-3

b. Single Window—after selecting this option the mouse cursor will change shape to a
plus sign; move the mouse cursor to the window you want to capture and press the
LMB. In both cases, the screen dump will be automatically be printed on the laser
printer. The screen dump will be stored in the file $IMAGE_DATA_PATH/
screen_dump.xwd.This file will be overwritten if you make another screen dump,
so if you want a permanent copy, you will have to rename the file with the mv(1)
command.
3. View the screen dump by clicking Output > Screen Dump > View Dump on the main
workstation window.
4. If the screen dump is satisfactory, you can print it on any printer as described below.
Depending on which printer you are using, you may have to convert the file format before
you print it. Note that a copy of the screen dump was automatically printed on your laser
printer in step 2.
In addition to the above procedure, you can make a screen dump with the xwd tool which is part
of X-Windows. The file created by xwd will be in X-dump format. You can convert this to
PostScript format with the xpr tool. The xwd and xpr tools are described in detail in the
X Window System User’s Guide, volume 3 of the O’Reilly X-window series. You can also use
man(1) to read the on-line manual pages for xwd and xpr.
FUNCTION UNIX COMMAND
Capture a single window % xwd -nobdrs -out

<output_file_name>.xwd -frame
Capture the whole screen % xwd -root > output_file_name

Preview before printing % xwud -in output_file_name
Print % xpr -device ps output_file_name | lpr
52.4 Printing Images on a Laser Printer
52.4.1 Unix Platforms

If you wish to print an image file on a Unix system laser printer, you must first convert the image
file to a PostScript file. You perform the conversion with either the xv tool or the ImageMagick
convert tool. For example, if the image file is in X-dump format, you would convert it with the
command:
% /usr/geoset/vendor/bin/convert xwd:x_dump_file.xwd
ps:postscript_file.ps
After converting to postscript, you print the file with the lpr command, as shown:
% lpr postscript_file
You can also use this command.
% lp -d print_device postscript_file
If the image file is in X-dump format you can print it with the following command:
% xpr -device ps x_screen_dump_file | lpr
Page 52-4 SOCET SET

You can also print an image from the main SOCET SET menu under the Output pulldown. This
will use the lpr print command by default, but you can customize this menu to use custom print
commands. See “Printer Configuration File for Unix Platforms” on page D-7 for instructions on
customizing the image printing action.
52.4.2 Windows Platform

You can print a PostScipt file two ways on Windows. You can bring up a Command Prompt
window and type “print abc.ps”. You can also set up the Explorer to recognize the file type and
print it. To add a new type for PostScript to the Windows Exploring window, do the following:
1. Click View > Options...
2. Click the File Types tab
3. Click New Type...
4. On the Add New File Type menu, enter
Description of type: PostScript
Associated extension: .ps

5. Click New... under Actions:
6. On the New Action menu, enter:
ACTION PRINT
Application used to perform action: c:\winnt\system32\print.exe “%s”
Now you can find the file you want to print in the explorer, click RMB and select Print, and the
document will be printed. You can also print using third-party software packages, such as
Ghostview.
52.4.3 Printing Reports

SOCET SET allows you to print various project files as reports to a selected printer. In order to
print a report, the following steps must be taken.
1. Ensure that the printer configure file is updated.
See “Printer Configuration File for Unix Platforms” on page D-7 for information on
setting up this file.
2. Select a printer. This is done by selecting the Preferences Printer menu item and then
selecting the appropriate printer in the Select Printer dialog box.
3. Lastly, to print the report, click Output > Reports > Print Files menu item and select the
file(s) you wish to print. Upon clicking OK, the selected file(s) will be printed.
SOCET SET Page 52-5

52.5 Anaglyph
Anaglyph generates color images which you can view in stereo with specially colored glasses
(one blue lens, one red lens). You can use this tool with any stereo image pair. To obtain this
window click Products > Anaglyph on the main workstation window. Anaglyph creates an output
file, which you can then print on a color hardcopy output device.
The Anaglyph window’s selections are as follows:
File > Exit Exits Anaglyph.

SELECT TO
View# - 0, 1, ... Select available view for image capture.

Lines Enter the number of lines to include in output anaglyph.
Samples Enter the number of samples to include in output anaglyph.

Location Select the output location.
Name Enter the name of output anaglyph image file.
Start Start creating the output anaglyph.
Page 52-6 SOCET SET

52.5.1 Execution
1. Import, control, and pairwise-rectify a stereo image pair. See “Image Rectification,”
Chapter 33.
2. Load the stereo image pair into a viewport and set the minification level you wish the output
image to have.
3. Recenter the imagery on the area you wish to include in the output image and make sure to
move the extraction cursor to the ground.
4. Click Products > Anaglyph on the main workstation window.
5. Enter the anaglyph name into the Name box and select an image location and format.
6. Enter into the Lines and Samples fields the number of lines and samples you want to include
in the output image.
7. For the output setup, select the viewport you loaded the imagery into for step 2 above.
8. Click Start on the Anaglyph window to begin creating the output anaglyph stereo image.
9. See “Image Previewing Tools” on page 52-2 to preview the output anaglyph image with
the xv tool.
52.6 Image Map
52.6.1 Overview
You can use Image Map to overlay or burn-in graphics on top of an image. There are two ways
to do this:
• Interactively, by drawing with Annotation while Image Map is running
• By extracting a feature database and providing it as input to Image Map
Image Map will process both color (3-band) images and gray-shade (1-band) images. The margin
that Image Map puts around the image can be either white or black.
You can overlay DTM contour lines in the image map. This process is described later in the
chapter.
Image Map does not print the output image map file on a hardcopy output device. To print it, you
must use a driver suitable for your printer. The format of the output image file is either Sun raster
or VITec tiled format, allowing export to a variety of printers and plotters.
SOCET SET Page 52-7

Image Map builds a rectangular image surrounded by marginalia and overlaid with graphics.
Margin Text—from
Annotation, can be re- Survey Map November 1994
used by storing in a 31:30 31:45 32:00 32:15
Margin Template file.
40:45 40:45
Feature Database—you can
“burn-in” graphical overlays
from a feature file. You must
extract the feature file
before running Image Map.
40:30 40:30
Interactive graphics—you
can use Annotation to draw
overlay graphics while
running Image Map, giving 40:15 40:15
you a “what you see is what
you get” preview capability. 31:30 31:45 32:00 32:15
Margin—surrounds the image Imagery—you must ensure Margin Ticks and Labels—drawn
on four sides; each side can that the input image is the outside the image; labels are
have a different width; the desired size before starting placed adjacent to the tick marks.
margin may be black or white. Image Map. You can specify the number of
digits in the labels.
52.6.2 When to Run Image Map

You run Image Map after you have imported an image, and you want to put a margin around it
and/or you want to overlay graphics on top of it. Before running Image Map, you should prepare
all the files you will input to it:
1. The input image file is mandatory; usually this is an orthophoto, but any image with a
support file will do. You must set the brightness and contrast of the input image and save
the values with the Image Enhancement Tool Save Parameters button.
2. If you want to burn-in terrain contour lines, you should convert the DTM to the feature
database format using Interactive Terrain Editing. This is described in detail later in this
chapter.
3. If you want to burn-in feature database graphics, you must create a feature database using
Feature Extraction, or import the feature database from another system.
4. If you want utilize margin templates, you must build the margin template with Annotation.
After you have prepared your input files, you then run Image Map as described below. Image Map
generates a disk file containing the Image Map in a format of your choice.
While Image Map is creating the output image and Interactive

Graphics is On, do not manipulate the imagery loaded in the
main workstation windows. This would include roaming,
moving to points, or re-centering. After Image Map finishes
creating its image, you may then use the workstation windows
normally.
Page 52-8 SOCET SET

After the output file has been built, you can preview the output image map file on the workstation
monitor by using the support file. After you have determined that it is satisfactory, you can then
print the file on your printer.
52.6.3 Inputs
Image Map has a large number of inputs. All inputs are optional except for the input image. The
inputs include: An image, a margin text file, a feature database, a terrain file, interactive overlays,
and grid line/margin tick specification.
The image you provide as input to Image Map can be any kind of image, although orthophotos
are most commonly used. The input image must have a support file.
52.6.4 Data Flow
Feature Interactive Terrain

Extraction Editing (Optional)
MARGIN
TEMPLATE Contour Lines DTM
FEATURE FILES
(optional)
Annotation Input Interactive Terrain
(optional) Image Editing (Optional)
Overlays
Gridlines
Tick Marks Terrain Contours
IMAGE MAP (Interactive)
or
PRINT GRAPHICS
OUTPUT
IMAGE FILE
MAIN Any Printer

IMAGE lpr
WINDOW
POSTSCRIPT
LASER PRINTER
SOCET SET Page 52-9

52.6.5 Graphical Overlays

Use Annotation, or a Feature Database to include graphical overlays in the output image map.
To overlay graphics from a feature database, you must extract the overlay data with Feature
Extraction and save it into a feature database. Then when you run Image Map, select the feature
database.
The extent of any graphical overlay is limited to the first 32767

lines or samples of your image map. Any overlays outside of
that area will not be placed into the map.
52.6.5.1 Interactive Graphical Overlays

The interactive approach to overlays lets you draw graphics and text in the main image window
in a “what you see is what you get” fashion. The main image window will display the outer border
of the margin, so you can accurately see where text and other graphics should be placed in the
margin. After you are satisfied with the graphics, you then run Image Map. Image Map will output
an image file, which you can then preview.
Detailed step-by-step instructions are given later in this chapter.
You can use the interactive technique with any vector extraction application, including
Annotation, Feature Extraction, or PRO600. The step-by-step instructions later in this chapter
will refer to Annotation because it is the simplest, but any similar task may be used.
SOCET SET applications which have Auto-Draw, such as ITE

and Feature Extraction must have Auto-Draw ON to operate
with Image Map Interactive Graphics.
52.6.5.2 Margin Templates

After you draw interactive graphical overlays with Annotation you may save them so they can be
re-used later. The file you save is called a Margin Template file. All graphics, whether located in
the margin or over the image, can be saved.
When you re-use a Margin Template on another image, you have two choices of how the graphics
will appear: (1) they can be located on the same ground-space objects (this is called Ground
Anchoring); or (2) they can re-appear at the same point in the margin (this is called Margin

Anchoring). Normally you use Ground Anchoring for features in the imagery like rivers and
roads, and you use Margin Anchoring for graphics in the margin like titles and notes.
This image map is the second

My Title Template from the first image
This graphic is anchored map is re-used here.
to the Margin, so when it
is re-used its location is
the same.
My Title
This graphic is anchored

to the ground, so when it
is re-used it appears at the
This image map is the first correct geographic
one created. The Margin location in the image
Template file is created now
and contains two graphics.
Every graphical object has its own anchor. For example, a Margin Template could contain five
graphics anchored to the margin and twenty graphics anchored to the ground.
52.6.5.3 Grid Lines and Tick Marks

There are three kinds of graphical symbols you can use to demarcate intervals: grid lines, Tick
Marks, and Intersection Ticks. Each of these is drawn by Annotation. You must run Annotation
concurrently with Image Map in order to get these symbols overlaid in your image map. See
“Annotation,” Chapter 45 for details.
Intersection Ticks - are

drawn at regular intervals
Grid Lines are drawn inside

the image; you select the
width and color.
Tick Marks are small

lines in the margin.
52.6.5.4 Text Fonts in Image Map

Text strings from Annotation, or Feature Database will be overlaid in an image map. For each of
these sources of text strings, you have a choice of fonts that are used when overlaying the string
in the Image Map. The font characteristics are size, family, and style.
You select the characteristics of a string at the same time that you create the text string. For strings
in Annotation, you choose the characteristics in the Annotation main window; for Feature
Extraction, you use the graphics attributes sub-window.

The fonts that are available to you are specified in the font configuration file /usr/geoset/
internal_dbs/PREF/fonts.config. Default fonts, suitable for most purposes, are
provided with the system. If the default values are not satisfactory (for example, you need larger
fonts), you can customize the font characteristics by editing the file /usr/geoset/
internal_dbs/PREF/fonts.config.
See “Customizing Your Software Configuration,” Appendix D for more details about how to
select fonts.
If you change any values in the font configuration file, you must re-start SOCET SET for the new
values to take affect.
52.6.5.5 DTM Contour Lines

Run ITE concurrently while you run Image Map— ITE will overlay its DTM graphics into the
image map, just like Annotation does—or run ITE to convert the DTM graphics into a Feature
DB, then input the Feature DB into Image Map. When you select the DTM graphics mode in ITE,
select Continuous Contours—do not use Editable Contours. Be sure to enable Auto Draw in the
ITE window before generating the Image Map.
52.6.5.6 Resampling Image Maps

Because overlay graphics on an Image Map are actually burned into the image, any resampling
done the image will tend to distort and/or discolor the graphics. Therefore, image maps should
not be rotated, zoomed, or modified in any way that will cause the pixels to be resampled.
52.6.6 Printer Resolution Considerations

Before making an image map, you should know the resolution of the printer you will be printing
the image map on. You enter the print resolution into the Resolution field in the main Image Map
window. If you do not know the resolution of your printer, you can use the default value provided.
The resolution is expressed as Dots Per Inch (DPI). Most printers have a resolution between 100
DPI and 600 DPI. The resolution affects the appearance of the output image in two ways: (1) The
size of the output image (in inches), and (2) The size of text strings.
52.6.6.1 Size of Output Image

The size of the output image, in inches, can be determined by dividing the size of the image (in
pixels) by the resolution. For example, if the input image is 3,000 x 4,000 pixels, and the margin
is 600 pixels on all four sides, then the output image is 3,600 x 4,600 pixels. If the printer
resolution is 100 DPI, then this image, when printed, will be 36 x 46 inches. If the printer
resolution is 200 DPI, then the image will be 18 x 23 inches.
Image Map copies the input image directly to the output without any scaling or rotation. So for a
given printer (that has a fixed DPI) the only way to change the size of the printed image is to
change the size of the image (in pixels). To change the size of the input image, you must re-create
the image with a different size or scale (for example, by running Orthophoto or Image Zoom /
Scale) and then re-run Image Map.
52.6.6.2 Font Size

The printer resolution is also used to ensure that text strings appear with the correct size. When
you created the text strings you specified the text string size (height) in points, which are 1/72
inch (see the “Font” section in the “Customizing Your Software” appendix for more details). For
example, if you want your text string to appear 1/2 inch high when printed, you must create a

string with a size of 36 points. Image Map will automatically scale the text to the correct size,
provided that you enter the correct printer resolution in the Image Map resolution field. Some
fonts have extra space above and below the characters which will cause the characters to be
shorter than the size you might expect. You can adjust the font to be larger by editing the
fonts.config file. See “Choosing Text Fonts” on page D-2 for details.
The font size will be scaled correctly only if you have specified
the 1:1 image minification level as input to Image Map and have
entered the correct value for printer dots per inch.
52.6.7 Image Enhancement and Color Balancing

If you want Image Map to enhance the input image, you must define the enhancements to the
input image before making the image map. Here are the steps:
1. Display the input image on the main image display.
2. Use the Brightness and Contrast slider bars on the Display Utility to achieve a visually
appealing display. You may also use the Tonal Transfer Curve (TTC) and Histogram
operations.
3. Click “Image Enhancement” button on the viewport window, then click Save to File.
These are the enhancements that Image Map will use.
4. Run Image Map. Image Map will apply the enhancements as it copies pixels from the input
image to the output image.
If the image map generated by Image Map is too bright or too

dark, adjust the brightness of the input image, save the value,
then re-run Image Map.
the input image, you must resample the entire input image by clicking “Image Enhancement”
button on the viewport window, then click Commit to Disk (you may either overwrite the original
image or create a new image) before running Image Map.
See “Image Enhancement” on page 4-12 for more details.
52.6.8 Image and Graphics Clipping

Normally, the output image map will contain the rectangular input image, surrounded by a
margin. However, you can clip the image to a non-rectangular shape by inputting a polygon
boundary in a feature database. Note that Image Map does not resize the total dimension of your
product if the polygon is much smaller than the original image. If you want the map to be smaller,
first run Zoom / Scale on the input image to clip it to the dimensions you want and then run Image
Map.

The input image is

rectangular.
The size of the output
image is simply the size
of the input image plus
Each of the four the margins.
margins can have a
different width.
Input
You can clip the image to any

polygonal shape by inputting a Image Map will clip the
Feature Database that contains a input image to the
polygon-shaped feature. polygonal boundary. Output
You can also choose to clip graphics to the image area. With the Image Map window open, to do
this, click Yes to the Clip Graphics to Image in the Margin subwindow to “Yes.” This only clips
graphics from feature files you have selected; graphics from interactive graphics clients such as
PRO600 or ATLAS software are not clipped since they are generally used for margin data outside
the image. Clip these graphics in PRO600 or ATLAS before making the Image Map. If you have
also selected the image polygon clipping, the graphics will be clipped to within that polygon.
52.6.9 Image Formats

52.6.9.1 One-band
If your image has one-band and burn in color graphics, Image Map will create a pseudocolor
output image. A pseudocolor image has a color lookup table used to map the single band into
multiple colors. Only SunRaster, TIFF, and TIFF Tiled formats support pseudocolor. You can
only view the pseudocolor image in SOCET SET by loading it into the Console Window. If the
Console Window is on a 256 color video board, you must select the pseudocolor mode for the
window, as described in the “Utilities” chapter. However, on the Windows platform, the output
image will have 3 bands if your input image is one band and your video card is set up for less than
24 bits of color.
52.6.9.2 Three-band
If your image has three bands, Image Map will create a 3-band output image. All of the formats
on the pulldown support 3-band output. If you want to see the full color image, you can load it to
any SOCET SET window. If you load it into the Console Window and the Console has a 256 color
video board, you must select the pseudocolor mode for the window (See “Image Information” on
page 61-35).
You can also view output images by using the image viewing tools, such as XV, described earlier.
See “Image Previewing Tools” on page 52-2.
You should display the output Image Map on the console

monitor, not the extraction monitor, because Sun Raster
images are not displayed correctly on the extraction monitor.

To view the output of Image Map in the Workstation Main Window, first make sure the display
mode is not in “Auto Brightness / Contrast,” and then load the image. Changing the brightness
and contrast will result in the graphics changing to incorrect colors.
52.6.9.3 Image Map Interface
The Image Map window’s selections are as follows:
File > Load Project Prompts you to pick the project that contains the input data.
File > Open Image... Opens the input images from a list provided.
File > Open FDB... Brings up a FDB list from which to choose your Feature Database(s).
File > Exit Closes the Image Map window.
SELECT TO
Input Image Prompt you to pick the input image file.

SELECT TO
Minification Level Select the minification level of the input image. (1:1, 2:1, 4:1,...)
Feature Files Display the scrolling list of feature databases you have selected to overlay
BLANK SPACE onto the image map.
Add Feature File Prompts you to pick feature databases to overlay. You can pick more than
BLANK SPACE one.
Remove File Remove File deletes file from list.
View Info... Bring up the Feature Information window for the highlighted feature database.
Interactive Graphics Toggle On or Off. If set to On, Image Map will copy any graphics currently
drawn on the monitor and overlay them onto the output image.
Printer Resolution (DPI) Select resolution of the hard copy output device you are preparing the
image map product for.
Margin Setup Bring up the Margin Setup window, which you use to specify the image
map margin widths, color, and clipping.
PostScript BLANK SPACE
Select Device Prompt you to pick the PostScript device file.
Show/Edit Device Bring up the PostScript Device Configuration window.
Create Calibration Creates a calibration page in the output raster path directory. File name is
Page calibrationpage.ps.
Output Identify the Location, Name and format of output image.
Start Start creating the output image map.
52.6.10 Margin Setup

This window is used to establish the margins for your image. Obtain this window by clicking
Margin Setup... on the Image Map window.
The Margin Setup window’s selections are as follows:
SELECT TO
Margin Border Widths Establish the Top, bottom, left, and right margin border widths, given in
pixels.

SELECT TO
Clip Image to Polygon Pick the name of the feature database that contains the polygon you wish to
clip the output image to.
Clip Graphics to Image Select Clip Graphics to Image button clips SOCET SET graphics; graphics
BLANK SPACE from PRO600 or ATLAS software are not clipped, since they are generally
BLANK SPACE used for margin data outside the image; clip these graphics in PRO600 or
ATLAS before making the Image Map.
BLANK SPACE
BLANK SPACE
BLANK SPACE
If set Yes (the default), features from the feature database are clipped so
Yes that they do not extend beyond the boundary of the input image; if you
BLANK SPACE selected a polygon to clip the image to with Clip Image to Polygon, the
BLANK SPACE graphics will be clipped to be within the polygon.
BLANK SPACE
No If set to No, graphics may extend beyond the boundary of the input image
and into the margin.
Margin Color Choose White or Black—Color of the output image border.
Close Close the Margin Setup window.
52.6.11 Image Map: Show/Edit Device

You can obtain this window by clicking Show/Edit Device... on the Image Map window.
The Output Image Format must be toggled to Postscript

The Image Map: Show/Edit Device window’s selections are as follows:
SELECT TO
Print Command Line Click in the Print Command Line field and type the print command. If (nil)
is specified, the PostScript output is written to the Output Raster File you
specified in the Image Map Main Window. On UNIX systems, if you
specify a print command, it is executed by a bourne shell and the
PostScript output is fed to its standard input. For Windows systems, leave
this field set to (nil). You can use lp to print to the PostScript printer.
NOTE: Do not specify a file name, just specify the command.
Effective Device Resolution This entry is not implemented. Do not use.

[pixels per inch]
Calibrated Output space Click in the four text input fields and type in the floating point numbers
[PS-dots in PostScript which are measured in PostScript dots. The four fields specify the
system] printable media space in PostScript (user space) coordinates. The printable
space is smaller than the media size. Most printer manuals are not very
precise in specifying these values and you should specify these fields. The
xmin/ymax input fields (left/top) are used as the origin of the internal line/
sample coordinate system. You can use an A4 page, which has a nominal
size of 595 PS-dots * 842 PS-dots (210 mm * 297 mm). The calibration of
a HP LaserJet 4 SIP results in xmin=13 ymin=13 xmax=581 ymax=830.
This is a size of 568 PS-dots * 817 PS-dots (200.4 mm * 288.2 mm).
NOTE: Instead of specifying the printable, these settings may also
be used to define the origin to a specific position relative to the
media border.
Scale Correction Enter a value in these fields when the size of a line is not printing out
correctly. You can input two floating point numbers to correct the scaling
problem. The numbers create the horizontal and vertical corrections. There
is a range for these numbers: 0.5 to 2.0. You should create a calibration
page and measure the longest vertical and horizontal distances with a ruler.
You can change the field size to correct for scaling problems.
Width of Thinnest Line Adjust your preferred linewidth.
[ps-dots] This field is a positive floating point number with a default of 0.24. The
default is the basic linewidth, the width for a line of internal width 1.
The lines are printed with internal_linewidth * width of the thinnest line.
The internal linewidths are 1,2,3... An internal linewidth of 0 is treated as
1. Dashing is done proportional to this linewidth. You must adjust to your
preferred linewidth. The Width of Thinmost Line field is unlike the raster
formats of ImageMap. The linewidths are device specific and have no
relation to the image pixel size. One example of a line width is: calculated
line width = 72/(Printer resolution in dpi). For a 300 dpi printer, 72 / 300
=.24.
Pixel Size for Raster Icons Adjust for the icon size.
[ps-dots] This field is a positive floating point number with a default of 0.96. You
can adjust it for the icon size you prefer. Unlike in the raster formats of
ImageMap, icon sizes are device specific and have no relation to the image
pixel size. Currently only coarse raster icons are available. For the
PostScript format, they should be replaced by higher resolution raster
icons or by vector icons.
EPS Margin Make a selection.
“Underlay” File You must enter a filename or (nil). An empty line is equivalent to (nil). The
default is (nil). The Encapsulated PostScript file here is transferred to the
output before the image and all other graphics. This means the image and
all graphics will be painted over the contents of this file. The main use for
the underlay is for externally created margin information.

SELECT TO
Position for EPS Underlay Input four floating point values. You should only do so when an underlay
[pixels in PsOutput system] file is specified. The Encapsulated PostScript (EPS) underlay file is scaled
to fit this bounding box.
EPS Overlay File Enter a filename or (nil). An empty line is equivalent to (nil). The default
is (nil). The Encapsulated PostScript file here is transferred to the output
after the image and all other graphics. This means that it will paint over
everything. The main use for the overlay is externally created image
annotation.
Position for EPS Overlay Input four floating point values. You should only do so when an overlay
[pixels in PsOutput system] file is specified. The Encapsulated PostScript (EPS) overlay file is scaled
to fit its bounding box.
Directory for Choose a directory with enough space for a complete PostScript output as
Temporary Files the PostScript output may be large. All temporary files go here and are
automatically erased when the output is complete. The default directory is
/tmp.
Graphics Only Toggle the Graphics Only button. The default is off. When you click to on,
the image is not transferred to the output. You may use this to split the
image and graphics output. Run once with this toggle clicked to off (all
feature files and interactive graphics turned off) to get an image output.
Run again with this clicked to on (feature files and interactive graphics
turned on) to get a graphics-only file in the same scale.
Reset Transfer Identify the internal transfer function of the PostScript interpreter. The
Function default is off. If you switch it on, the internal transfer function of the
PostScript interpreter is reset. You may use this to correct some strange
behavior of less expensive printers, especially when a gamma table is
specified.
Color Identify greyscales. The default is on. If you switch it off, Image Map will
produce a grayscale output. You should always switch to off for greyscale
output devices as well as for all pure greyscale (both, image and graphics)
data.
Binary Image Select representation of the image. The default is on. If you switch it off,
Image Map will create an ASCII-only (HEX) representation of the image.
Some binary image formats have less than half the size of ASCII format
and will not work over 7-bit serial lines. Some PostScript interpreters are
not able to handle it.
Compress This entry is not implemented. Do not use.
Minimum Paper This entry is not implemented. Do not use.
Gamma Table Display outputs triples. The default is an ascending linear transformation.
The table represents 256 RGB output triples in the PostScript range 0.0 to
1.0 for input values in the range 0 to 255. The table is read only. To change
it, edit the PostScript device file in internal_dbs/DEVICE. You can change
the table to define the color mapping from the input range (0 <= R,G,B <=
255) to the PostScript range (0.0 <= R,G,B <= 1.0).
Save As... Close the PostScript Device Configuration Window. When you click this
button you will be prompted to save the changes to a PostScript Device
File.
OK Close the window and makes the changes.


52.6.12 Calibration Procedure for PostScript Output

A calibration should be done for all PostScript output devices and media sizes. You can use the
default PostScript Device Configuration files which are supplied by SOCET SET in the
internal_dbs/DEVICE directory or you can create a PostScript Device Configuration File for each
device and media size. At least one PostScript Device Configuration File is required for each
device/media combination. You may decide to create more than one file for each combination if
you are going to use different linewidth, icon size, underlay/overlay or flags settings with one
device. You have to go through this calibration procedure for each device/media combination
The PostScript Device Configuration Files go to SOCET SET internal_dbs/DEVICE directory,
by default their names end in .psd. We recommend not changing this.
52.7 Executions
52.7.1 Execution - Calibration of PostScript Output
Instructions for the device/media calibration:
1. Click Products > Image Map on the main workstation window.
2. In the Output Image area, click on the toggle and select the PostScript option from the list
provided, to create a PostScript Output Format.
3. In the Output Image section, click Location and choose the Output File Location. The file
Calibration Page.ps will be created in this directory.
4. Click Select Device... in the PostScript section of the Image Map Window. A file selector
pops up. Select one of the supplied configuration files. If you have your own (working)
working device configuration, you may save some work by using this as the starting point.
5. Get the nominal output page size (width, height) for the device/media combination.
Check the documentation of the output device. You might be able to find some information
about media size and/or printable space. Otherwise use the supplied configurations for A4
or letter size devices or measure the output media for other sizes. Convert these
measurements to PostScript-dots. Multiply values in millimeters by 2.8346 to get
PostScript-dots. Multiply values in inches by 72.0 to get PostScript-dots. Some popular
sheet sizes in PostScript-dots:
FORMAT NAME WIDTH HEIGHT FORMAT NAME WIDTH HEIGHT
A0 2380 3368 Tabloid/11x17 792 1224

A1 1684 2380 ledger/17x11 1224 792
A2 1190 1684 Letter 612 792
A3 842 1190 Statement/Halfletter 396 612
A4 595 842 10x14 720 1008
A5 421 595 Legal 612 1008
A6 297 421 Note/Executive 540 720
B0 2836 4008 ArchE 2592 3456

FORMAT NAME WIDTH HEIGHT FORMAT NAME WIDTH HEIGHT
B1 2004 2836 ArchD 1728 2592

B2 1418 2004 ArchC 1296 1728
B3 1002 1418 ArchB 864 1296
B4 709 1002 ArchA 648 864
B5 501 709 Folio/Foolscap 612 936
B6 355 501 Quarto 610 780
Most printers have some unprintable margin space.
6. In the PostScript section of the Image Map Window, click Show/Edit Device. The Image
Map: Show/Edit Device Window pops up.
7. Check the displayed device configuration. There is no need to enter a correct Print
Command Line. The calibration page output will always go to a file. Enter the desired
values Calibrated Output Space: set xmin and ymin to 0.0, xmax to the media width and
ymax to the media height, all in PostScript-dots. Set both horizontal and vertical Scale
Correction to 1.0. Define the linewidth to use for the calibration page by setting the Width
of Thinmost Line. The default of 0.24 PostScript-dots (1/300 inch) will be appropriate for
all devices with a resolution of 300 dpi or better. Do not touch anything else yet. If you have
done something wrong, press the Cancel button and start Show/Edit Device again.
8. Click Done; a file selector pops up. Select a name and save your configuration. Remember,
you should not change the directory and the filename should end in .psd. Both, the file
selector and the editor window are popped down and the new PostScript Device filename
is displayed in the Image Map Window. You can click Cancel if no changes were required.
9. Click Create Calibration Page... in the Image Map Window. A file CalibrationPage.ps is
created in the Output Raster Path directory. The existing CalibrationPage.ps is overwritten
without requesting a confirmation, rename the file immediately after creation, if you want
to keep it permanently.
10. If you would like to have a look at the calibration page before printing it, use “/usr/openwin/
bin/imagetool” in UNIX or another PostScript previewer.
11. Send the calibration page to the PostScript output device.
12. The way to print a PostScript file depends on your local configuration. See “Printing
Images on a Laser Printer” on page 52-4 for details.
13. Fine-adjust the output scale. The calibration page contains some horizontal and vertical
calibration distances (10mm, 0.5", 20mm, 1", 50mm, 2", 100mm...). Use a good ruler to
take the lengths of the longest ones and calculate new horizontal and vertical Scale
Corrections by new_scale_correction = current_scale_correction * printed_length /
measured length. Remember, you have initially set both corrections to 1.0 in step 7.
For high-ended output devices, there will probably be no need

to use the corrections. Do not use the scale corrections to
scale your image map output to the desired size, only values
close to 1.0 are allowed here.
14. If you have a new scale corrections, select Show/Edit Device on the Image Map Window.
The Image Map: Show/Edit Device window pops up again. Type in the new values, save
the new configuration and restart at step 10.

15. Now that the output scale is correct, you have to decide how to configure the output page.
There are at least three ways to do this:
a. Adjust the output page to the printable media space. This ensures that none of your
image maps will be clipped off by the output device. (Image Map displays an error
message and creates no output whenever your map exceeds the configured output page
border.) Continue with step 16a) if you want to use this method. (This is what we
recommend for real output.)
b. Set the origin of the output system to the top left corner of the media.This makes it a
simpler to get the image output to a certain location on the media; the image location
can later be calculated just from top and left margin and Printer Resolution and you
do not need to be concerned about the output page offsets. Continue with step 16b) if
you want to use this method, but you must take care later on because parts of your
image map output may fall into the unprintable margins of your output device.
c. Create a virtual device for previewing or Encapsulated PostScript export. Continue
with step 16c) if you want to this.
16. Three ways to configure the output page:
a. Adjust the output page to the printable media space. There are rulers from the center
of the current PostScript output page to all four borders. They have long (every 20 PS-
dots), medium (every 10 PS-dots) and short (every 5 PS-dots) marks. The printed
values near the long marks are offsets from the current output page border. The rulers
are either clipped by the output device or extend to the border of the media. Estimate
the end of each ruler as good as possible and use these values for the new Calibrated
Output Page settings. Look at a calibration page which was printed with xmin=0,
ymin=0, xmax=300, ymax=300. For the ends of the rulers, you read: xmin-22, ymin-
23, xmax+20, ymax+24. So you get the new values: xmin=0-22=-22, ymin=0-23=-23,
xmax=300+20=320, ymax=300+24=324. If you have new Calibrated Output Page
setting, select Show/Edit Device on the Image Map Window. The Image Map: Show/
Edit Device window will pop up again. Type in the new values and save the new
configuration. Create and print the calibration page and check it again. You are
finished when the output page border rectangle is printed all around the page and the
rulers are clipped right at or a little bit outside the rectangle.
b. Set the origin of the output system to the top left corner of the media. This is done very
similar to 16a). The only difference is that you do not read the top left (ymax, xmin)
values at the ends of the rulers but at the border of the media. You will have to
extrapolate over the unprintable margin.
c. Create a virtual device for previewing or Encapsulated PostScript export. The output
of real PostScript devices goes to absolutely defined positions on the media. This is
not useful for post processing programs like desktop publishing systems, which
should be able to shift and scale the imported PostScript data. The “Encapsulated
PostScript” (EPS) format makes this possible: it contains a bounding box for the data,
to which the importing programs refer. The Image Map output contains the basic EPS
definitions and can be imported into post processing: EPS previewers. Its bounding
box contains the image and margin data. As the real media size does not care for EPS,
you may define a huge media area for export and previewing purposes. If you choose
the top left (xmin, ymax) corner so that it matches a real output media, you will also
be able to produce some output (at least the top left part) on real devices. Define xmin
to the xmin of a real device, set ymin to a huge negative value (-10000 will do), set
ymax to a huge positive value (10000 will do) and define ymax to the ymax of a real
device. Example, if you want to use SUN's imagetool (/usr/openwin/bin/imagetool)
for previewing, define your virtual device for the largest real format imagetool can
handle (this is A3): xmin=0, ymin=-10000, xmax=10000 and ymax=1190 (this is the
height of A3).
52.7.2 Execution - Image Map

1. Prepare your input data (See “Inputs” on page 52-9 for summary of input data).
2. Load the project in which you are working if not previously loaded. File > Load Project.

3. Load the input image (the image you are going to turn into an image map) onto the console
monitor image window. This is accomplished by either clicking File > Open Image... or
click the (ellipse tool button).
You should display the image on the console monitor, not the
extraction monitor.
4. Click Extraction > Annotation on the main workstation menu. Leave Annotation running
throughout the remainder of these steps.
If you use a third-party mapping package for interactive

overlays, you should activate it at this point and skip steps 5
to 8.
5. [Optional] If you have a Margin Template that you want to re-use, click File > Load on the
Annotation window. If necessary, edit the Margin Template graphics with Annotation.
6. [Optional] If you want to draw any interactive graphics, use Annotation to do so.
7. [Optional] If you want grid lines, tick marks, or intersection ticks, draw them with
Annotation. Adjust the grid parameters until they are satisfactory.
8. Start whatever applications which draw graphics you want to print, such as Annotation,
Feature Extraction, Interactive Terrain Edit, etc.
Applications which have Auto Draw must have it turned on for

graphics to transfer to Print Graphics.
9. Click Products > Image Map on the main workstation window.

10. Click Input Image on the Image Map window. Select the input image file. This must be the
same image that you currently have displayed on the console window.
11. [Optional] Click Location in the Output Image section, if you want to change Location,
Name and format to values you want.
12. [Optional] By default, Image Map will use the 1:1 minification level of the input image. If
you wish, select a different minification level.
13. [Optional] If you wish to overlay graphics from a feature database on the image, click Add
Feature File.... This prompts you to pick feature databases from your project. You can pick
more than one feature database. Click OK to continue.
14. [Optional] If you are going to be creating a scaled image map for later output onto a hard-
copy output device, enter the resolution of the output device in the Printer Resolution field.
15. [Optional] Setup the margins in the Margin Setup window by clicking Margin Setup on the
Image Map window. If you skip this step, no margins will be created.
a. [Optional] Specify the top/bottom/left/right margin widths, in pixels. Image Map
draws the margin border in red on the console monitor image window. Visually verify
that the margin border is correct.
b. [Optional] Click Clip Image to Polygon. Pick the name of the feature database that
contains the polygon you wish to clip the output image to.
c. [Optional] Set Clip Graphics to Image to On or Off. When clipping is on, Image Map
always clips graphics from the feature database at the image border. When clipping is
off, features are drawn to the margin border.
d. [Optional] Set the Margin Color.
e. Click Done to return to the Image Map window.
16. Click Start to generate the output image map.

17. Review the output by loading the image into the main image window using the output
support file name you specified above (default name is your output image name
with a _i.sup appended). Exit Annotation while you are viewing the image map.
You may need to increase the number of overlay colors for the console monitor with
Monitor Image Preferences in order to see all the overlay colors. Alternatively, you may
use an image viewing tool like xv.
18. Repeat steps 3 to 17 until the output image map is satisfactory. Remember to re-load the
original input image onto the main workstation display.
52.8 Print Graphics

Use Print Graphics to create a PostScript file of the graphics displayed in the Main Workstation
Window. Print Graphics works similarly to Image Map in most respects, so refer to the Image
Map section for details on items not described here.
The Print Graphics window’s selections are as follows:
File > Exit Closes the Print Graphics window.

SELECT TO
Device Prompt you to pick a PostScript device file.

View/Edit... Bring up a window to show details about the current PostScript device.

SELECT TO
Create Calibration Page... Create a calibration page which you can print to test your device file and
printer.
Boundary BLANK SPACE
Full Display Gather all graphics currently active in the Main Workstation Window.
Polygon Toggle on to only gather graphics from the area of the polygon you draw.
Draw... Prompt you to draw a polygon to contain the graphics to print.
Scale BLANK SPACE
Fit to page Automatically scale the output to fit on the PostScript device.
1: Enter a scale into the text box to select a specific scale. The scale is
measured as the ratio of the size of the PostScript device to the ground
dimensions of the graphics area.
Output BLANK SPACE
Location Select a location for the output PostScript file.
Name Enter the name of the output file here.
Start Start creating the output Print Graphics.
52.8.1 Execution—Print Graphics

1. Prepare your input data (See “Inputs” on page 52-9 for summary of input data).
2. Ensure you have a project loaded in the Main Workstation Window.
3. Load any input image which covers or partially covers the area you want to print graphics
onto a workstation window.
4. Start whatever applications which draw graphics you want to print, such as Annotation,
Feature Extraction, Interactive Terrain Edit, etc.
5. Set up the graphics on the applications so they look the way you want them to print.
Applications which have Auto Draw must have it turned on for

graphics to transfer to Print Graphics.
6. Click Output > Print Graphics on the main workstation window.

7. [Optional] Change the PostScript device to the device you want. Edit the parameters and
create calibration pages to check it.
8. Click Full Display Boundary if you want all active graphics to be printed or click Polygon
and Draw... to draw an area of graphics to print.
9. Click Scale Fit to Page if you want Print Graphics to compute a scale for you or Scale 1:N
and enter a number if you want to compute the scale yourself.
10. [Optional] Click the (ellipse tool button) for Location in the Output File section, if you
want to change the location to the location you want the PostScript file to go.
11. Click Start to generate the output image map.
12. Review the output by viewing the output with a PostScript viewing program or by printing
the output.

52.9 Batch Processing - Image Map

You can run Image Map in batch to burn-in graphics from one or more feature files. Batch mode
does not support interactive graphics or PostScript format output.
COMMAND LINE:
% start_socet -single hardcopy -batch -s setting_file
hardcopy image_map
KEYWORD DESCRIPTION
project Project filename , e.g. “xyz.prj”
support_file Name of the support file you want to place into the image map, e.g.
“abc.sup”
feature_file Name of the feature file(s) whose graphics you want to burn into the output
image. Repeat for every feature file.
clip_polygon [Optional] Name of the feature file which will be superimposed over the
image.
min_level [Optional] Minify level of the support file to use. 0 = 1:1, 1 = 2:2, 2 = 4:1,
etc. Default value is 0.
output_name Name of the output image. Do not supply a file extension. .
output_location [Optional] Name of the image location from the list in

internal_dbs/DEVICE/location.list.Default
value is “DEFAULT”.
output_format [Optional] Image format you want the output to be in. Use the chart in
Image Import Overview to find the format names. The default value is
“img_type_tiff_tiled_planar”.
printer_resolution {Optional] Printer resolution for scaling text in the output. Default is
“300.”
margin_left Width of margin around the image, in pixels.

margin_right
margin_top
margin_bottom
margin_color [Optional] Margin color, “BLACK” or “WHITE”. Default is “WHITE”.
clip_features [Optional] Specify “YES” to clip features at the start of the margin.
Specify “NO” to make features extend into the margin area. Default value
is “NO”.
map_to_three_bands Set to “YES” if you want a 3-band output and your input image is one
band. Set to “NO” for all other situations.

52.10 Limitations
Image Map does not currently support creating a pseudocolor image. Therefore the 24-Bit Color
button is disabled.

Chapter 53
Line Of Sight
Line of Sight allows you to evaluate potential placements of
objects that are sensitive to line-of-sight obstructions.
53.1 Overview
When you run LOS, you are evaluating line-of-sight vectors that are straight lines between a start
point and an end point. This is called a LOS vector. You can create several candidate LOS vectors
for evaluation. For each LOS vector, you can identify one or more possible obstructions. For each
obstruction you must select a point on the obstruction called an obstruction measurement. All
LOS vectors and obstruction measurements are displayed and manipulated graphically over
imagery. When you are evaluating LOS vectors, it is best if you have stereo image pairs displayed
on the main image display: this will give you the three-dimensional visualization that you need
to accurately identify and resolve obstructions. As another aid to identifying obstructions, you
can display features and terrain at the same time you are examining the candidate LOS vectors.
If you want to continue your work at a later time, you can save all of your data (LOS vectors and
obstructions) to a LOS database. To generate a hardcopy report of the LOS data, you can capture
the LOS graphics onto a screen dump, or by using Image Map, you can generate a textual report.
See “Hardcopy Products and Image Maps,” Chapter 52 for details.
Line of Sight (LOS) is a tool that allows you to evaluate potential placements of objects that are
sensitive to line-of-sight obstructions. For example, if you are deciding where to place antennas,
you can use LOS to determine if there are any obstructions between two candidate positions. If
you detect obstructions, you can adjust the antenna positions until no obstructions are present.
End Point
V ector
LOS
Start Point
Obstruction
Measurements
SOCET SET Page 53-1

Chapter 53 - Line Of Sight
53.1.1 When to Run Line Of Sight

You run LOS when you are deciding where to place objects that are sensitive to line-of-sight
obstructions, such as antennas and transmitters. Before running LOS you must create a project
and import imagery. If possible, you should have stereo image pairs. Optionally, you should have
a DTM (either imported or generated by ATE). If the area contains buildings that may be
obstructions, you should build a Feature DB, but it is not required.
You perform LOS analysis by interacting with the following set of windows
Line Of Sight
LOS Vector LOS Vector LOS Vector LOS Vector Obstruction Obstruction
Information Annotation Comparison Ring Marker Measurement Measurement
Information Annotation
53.2 Line of Sight

The Line of Sight window is LOS’s main window. It pops up when you click Products > Line of
Sight on the main workstation’s window. This window is divided into two main sections, where
one section provides interactions with vectors, and the other section provides interactions with
obstruction measurements.
The Line Of Sight window’s selections are as follows:
File > Save; Save As Saves the LOS data that you are editing to a disk file.
Page 53-2 SOCET SET

File > Report Generates a textual report summarizing the LOS vectors.
File > Exit Exits the LOS analysis tool.
Options > Draw Annotations Turns the display of textual annotations on or off.
Options > Set Vector Ring Pops up the LOS Vector Ring Marker window.
Options > Compare Vector Pops up the LOS Vector Comparison window.
SELECT TO
LOS Database Loads a pre-existing or new LOS database.

Vector ID Identity of the currently selected LOS vector.
Display Turns on or off the display of the individually selected vector.
# of Vectors Serial number of currently selected LOS vector.
Start Point (^S) Moves the extraction cursor to the start point of the selected vector.
Closest Point [KP(+)] Moves the extraction cursor to the closest point on the selected vector.
End Point (^E) Moves the extraction cursor to the end point of the selected vector.
Add Vector Adds a new LOS vector to the LOS database. Press the LMB at the vector
start point, then the RMB at the vector end point. Press ESC to abort.
Delete Vector Removes the currently selected vector from the LOS database. Note that
deleting a vector will also delete all obstruction measurements associated
with it.
Next Vector Steps forward through the vectors in the database.
Prev Vector Steps backward through the vectors in the database.
Annotate Vector Pops up the LOS Vector Annotation window.
Vector Infor Pops up the LOS Vector Information window.
OM ID Identity of the currently selected obstruction measurement.
# of OMs OM number of currently selected obstruction measurement.
Add OM [KP(Ins)] Adds an obstruction measurement to the LOS database for the currently
selected vector. Clicking this button sets LOS into an add-OM mode, and
while in this mode a perpendicular rubber band type line will be
maintained from the current vector to the extraction cursor. You can then
specify an OM by positioning the extraction cursor on the point of
obstruction and pressing the LMB. This accepts the obstruction
measurement for the vector. To exit out of the add-OM mode press the
escape (ESC) on the keyboard.
Delete OM (^X) Removes the currently selected obstruction measurement from the LOS
database.
Next OM (Dn) Steps forward through the OMs on the vector.
SOCET SET Page 53-3

SELECT TO
Prev OM (Up) Steps backward through the OMs on the vector.

Annotate OM Pops up the Obstruction Measurement Annotation window.
OM Info Pops up the Obstruction Measurement Information window.
53.2.1 LOS Vector Information

The LOS Vector Information window provides detailed numerical data about the vector you have
selected or are in the process of creating. You popup this window by clicking Vector Info in the
vector portion of the LOS window. This window is non-model, and you may leave it up for as
long as you desire. The information in this window will be updated for each vector that you select
or create. While delineating (creating) a vector, the current position of the extraction cursor will
be displayed in the Curr LOS Loc field. The rest of the fields will be updated after delineating the
vector.
The LOS Vector Information window’s selections are as follows:
SELECT TO
Vector ID Identify of the currently selected LOS vector.

Start Point Display the coordinates of the start (initiation) point of the vector.
End Point Display the coordinates of the end (termination) point of the vector.
Curr LOS Loc Display the coordinates of the extraction cursor when delineating
(creating) a vector. When viewing an existing vector, this field displays the
coordinates of the point on the vector nearest the extraction cursor.
Slope Len Display the length of the vector from the vector start point to the end point.
Horz Len Display the length of the projection of the vector into the XY plane.
Azimuth Display the azimuth, in degrees, of the vector relative to model north.
Elev Ang Display the elevation angle, in degrees, of the vector relative to the model
horizon.
Done Remove the LOS Vector Information window.
Page 53-4 SOCET SET

53.2.2 LOS Vector Annotation

The LOS Vector Annotation is brought up by clicking Annotate Vector on the LOS window. It
allows you to store informational text about the current vector. You can type a maximum of 127
characters of text.
53.2.3 Obstruction Measurement Information

The Obstruction Measurement Information window provides detailed numerical data about the
obstruction you have selected or are in the process of creating. You pop up this window by
clicking OM Info in the OM portion of the LOS window. This window is non-modal, and you
may leave it up for as long as you desire. The information in this window will be updated for each
OM that you select or create. While delineating (creating) an OM, the current position of the
extraction cursor will be displayed in the Obstruction Loc field. The rest of the fields will be
updated after delineating the OM.
The Obstruction Measurement Information window’s selections are as follows:
SELECT TO
OM ID Identify the currently selected obstruction Measurement. This field is not

editable. You use this ID as an aid for keeping track of OMs.
Offset Select which offset segment to measure. Select Origin to Obstruct to
measure the segment from the vector starting point to the point of
obstruction. Select Origin to Depart to measure the segment from the
vector starting point to the projection of the obstruction point on the vector
(i.e. vector departure point). Select Depart to Obstruct to measure the
segment from the projection of the obstruction point on the vector to the
point of obstruction. This selection will affect the Offset coordinates (X, Y,
Z), Length, Azimuth, and Elevation fields within this window.
Offset Display the relative coordinates of the offset specified in the Offset option
menu. This is an LSR type coordinate with the origin set by the Offset
option menu selection.
Obstruction Loc Display the coordinates of the extraction cursor when delineating
(creating) an OM. When viewing an existing OM, this field displays the
coordinates of the point of obstruction.
SOCET SET Page 53-5

SELECT TO
Slope Len Display the distance from the offset start point to the end point. The offset
is selected via the Offset option menu.
Horz Len Display the length of the projection of the offset in the XY plane. The
offset is selected via the Offset option menu.
Azimuth Display the azimuth, in degrees, of the offset selected relative to the model
north.
Elev Ang Display the elevation angle, in degrees, of the offset selected relative to the
model horizon.
53.2.4 Obstruction Measurement Annotation

The Obstruction Measurement Annotation Window is used to store textual information about the
current obstruction measurement. You pop up this window by clicking Annotate OM on the LOS
window.
53.2.5 LOS Vector Ring Marker

The LOS Vector Ring Marker Window is brought up by clicking Options > Set Victor Ring on
the LOS window. This window lets you set the radius of the ring marker. If you want the ring
marker to vary in size, as if it is on the surface of a cone, you set the angle to a non-zero value (in
degrees).
You can adjust the speed with which the marker moves by setting the speed. The higher the speed
is set, the less often the ring will be redrawn as it is moved along the vector. Speed is an integer
from 0 to 30.
The Line of Sight vector ring may have random colors when
displayed in projects with color images.
Page 53-6 SOCET SET

53.2.6 LOS Vector Comparison

The LOS Vector Comparison Window is brought up by clicking Options > Compare Vector on
the LOS window. It displays comparative information about vectors which share a start point or
an end point.
The LOS Vector Comparison Window’s selections are as follows:
SELECT TO
Select Related Vector To List the vectors which share common starting or ending points with the
Compare source vector. You select which vector to compare to the source vector by
clicking on one of the vector ID’s in this list.
Source Vector Source vector with which to compare related Vector vectors.
Compare Vector Select current related vector. This Vector field is non-editable. It is set by
selecting a vector ID in the Related LOS Vectors list.
Slope Len Display the longest distance from the source vector to the compared vector
(i.e. distance between their non-shared starting or ending points).
Horz Len Display the length of the projection in the XY plane of the line segment
connecting the non-shared points of the source vector and the related
vector.
Horz Ang Display the horizontal angle (XY plane only), in degrees, between the
source vector and the related vector.
Vert Ang Display the difference between the angles, in degrees, with respect to
horizontal of the source vector and the related vector.
Done Close the window.
SOCET SET Page 53-7

53.3 Getting Started - Execution

1. Load imagery, preferably a stereo pair, onto the main image display.
2. Activate LOS from the main menu by clicking Products > Line of Sight.
3. [Optional] Display the DTM with ITE.
4. [Optional] Display the Feature database with Feature Extraction.
5. Click LOS Database on LOS window. This brings up the database selection window.
6. Select or enter file name from the LOS file selection window. (It is not permitted to choose
a name already given to a feature database.)
53.3.1 Creating a LOS Vector

1. [Optional] Click Vector Info to pop up additional information on LOS vectors. While
adding an LOS Vector this window will track the current coordinates of the extraction
cursor and display the start and end points of the vector.
2. Click Add Vector.
3. Position the extraction cursor at the desired starting position for the LOS Vector, then press
the LMB.
4. Position the extraction cursor at the desired end position for the LOS Vector, then press the
RMB. The LOS Vector is accepted.
5. [Optional] Click Annotate Vect and enter desired description of vector.
53.3.2 Picking a Vector

Move the extraction cursor near the vector and press the LMB, or use the Next/Prev buttons on
the main LOS window.
53.3.3 Creating Obstruction Measurements

1. Select the LOS vector you want to evaluate.
2. [Optional] Click Options > Set Vector Ring on the LOS window and set the desired radius
around the vector to examine for obstructions. This will control the radius of the ring
appearing around the vector during motion along the vector, and is an aid for locating
possible obstructions within a defined distance. Default value for ring radius is 20 project
units.
3. Move the extraction cursor along the length of the vector. The Vector Ring and bead will
move along the vector maintaining the closest point to the extraction cursor. While
traversing the vector search for an obstruction.
4. [Optional] Click OM Info to pop up additional information on Obstruction Measurements.
While adding an Obstruction Measurement this window will track the current coordinates
of the extraction cursor and display offset information of the obstruction from the LOS
Vector.
5. Click Add OM (or press the Ins key on the keyboard).
6. Position the extraction cursor at the desired location of the obstruction, then press the LMB.
If the specified location is near a previously defined obstruction a window will pop up
asking whether to use the same obstruction location. Answer Yes if the obstruction is the
same, or No if they are actually two separate obstructions that are near each other.
7. [Optional] Click Annotate OM and enter desired description of Obstruction Measurement.
Page 53-8 SOCET SET

SOCET SET Page 53-9

Chapter 54
CIB Generation
Controlled Image Base (CIB) is a product composed of
orthorectified digital images stored on a CD ROM.
54.1 Overview
Controlled Image Base (CIB) is a product composed of orthorectified digital images. Each CIB
product, as defined by MIL-STD-89041, covers a pre-defined region of the Earth, termed a CIB
“cell.” SOCET SET currently support the creation of CIB cells with a resolution of either one
meter of five meters. For a one-meter CIB, the size of each cell is a quarter degree (i.e. 30 minutes
by 30 minutes), and for five-meter CIB, the size of each cell is a one-degree square.
The final CIB product is provided on CD-ROM. For one-meter CIB, each CD-ROM contains a
single cell. For five-meter CIB, each CD-ROM contains a pre-defined number of cells, usually
six. The SOCET SET software automatically determines the correct number of CIB cells per CD-
ROM.
During the CIB generation process, an intermediate product known as uncompressed CIB is
created. If required, uncompressed CIB may be output to 8-mm tape.
Each CIB cell, as contained on CD-ROM, is broken up into a set of 1536 by 1536 pixel frames.
Each frame is compressed and formatted according to the NITF 2.0 standard. Additionally, each
CD-ROM contains a Reference Graphic, Overview Image, and Table of Contents (TOC) file.
The SOCET SET CIB generation process is composed of a series of steps that will be referred to
as the CIB Job Flow. The SOCET SET “CIB Generation” pull-down lists the CIB Job Flow in the
logical order that it should be performed.
54.2 Job Planning

The first step of the CIB Job Flow is referred to as Job Planning, which is a sequence of steps that
provide an initial set of digital imagery for assessment purposes. Once Job Planning has been
completed, the images may be reviewed for their suitability for CIB creation. Each of the Job
Planning sequence of steps is described in the following sections.
54.2.1 Job Planning - Review/Edit Image Locations

Each CIB cell is created using a separate SOCET SET project, and each SOCET SET project
requires an image location to be defined and created. Selecting Review/Edit Image Locations
SOCET SET Page 54-1

Chapter 54 - CIB Generation
invokes a text editor that allows the user to define an image location directory. For CIB
Generation, this directory will contain source imagery, as well as the intermediate uncompressed
CIB. The directory that will contain the compressed CIB is defined later in the CIB Job Flow.
The Review/Edit Image Locations text editor only defines the image
location directory, it does not create it. It is the user’s responsibility
to create the directory. For more information on this process, See
Establishing Image Locations in the SOCET SET Online Help.
54.2.2 Job Planning - Job Setup

Job Setup is used to create a new SOCET SET project, specifically for CIB. Not only is a new
SOCET SET project created, but CIB-related data files are also created.
54.2.2.1 Job Setup Description
The CIB Job Setup Window, shown below, is used to create a new SOCET SET project for CIB
Generation.
The JobSetup window’s selections are as follows:
File > Exit Closes the Job Setup window.

Page 54-2 SOCET SET

SELECT TO
Name Enter the name of the project in this text field. The project name must be
11 characters.
Location: Display a File Location window. After OK is selected on that window, the
logical name of the image location is displayed in the field next to this
button. This is the same text entered in the previous step, “Review/Edit
Image Locations.”
Lat (Y) Enter the southwest and northeast latitudes of the CIB cell.
Lon (X) Enter the southwest and northeast longitudes of the CIB cell.
GSD Select the Ground Sample Distance (GSD) of the CIB cell. Options are 1
meter and 5 meter.
Edition Select the Edition Number of the CIB Cell.
Foreign Project Identify this project as a “foreign” project. This toggle only applies to five-
meter products. It should only be toggled if the project will only be used to
import five-meter cells for later merging with generated cells.
Start Accept inputs and create a new CIB SOCET SET project.
Status Window View status and error messages for Job Setup.
54.2.2.2 Job Setup Execution
The following steps are preformed to create a CIB job using the Job Setup Window:
1. On the SOCET SET menu, select Product > CIB Generation > Job Planning > Job Setup.
2 Type in the 11-character name of the project.
Notice that Start is not enabled until exactly 11 characters have been
entered.
3 Select the project image location name. This should be the same name created during the
previous step, “Review/Edit Image Locations.”
4 Type in the four corner coordinates for this CIB project. The tab key may be used to move
from one coordinate field to the next.
5 Select the GSD for this CIB job.
6 Select the Edition Number for this CIB job. For 1-meter CIB, this number is used in the
name of the product. For 5-meter CIB, it is basically ignored by the software.
7 If this is a 5-meter project, and will be used only to import “foreign” CIB cells, click the
“Foreign Project” toggle button. This will tag the project as a “foreign” project.
8 Select Start. This will initiate the Job Setup process for CIB. This includes the following:
9 Automatic import of WMED data covering the CIB cell.
10 Automatic import of CADRG data covering the CIB cell (optional if on-line CADRG
database is present).
11 Automatic creation of a Task MBR (PRODUCTION_CELL_XXXXXX) covering the CIB
cell, as defined in MIL-STD-89041.
12 Automatic creation of neighboring CIB cells (5-meter CIB only).
SOCET SET Page 54-3

13 Automatic creation of a CIB working area, known as a Task Assignment Area (TAA).
54.2.3 Job Planning - Import Geopositioning Job

The Import Geopositioning Job window is used to import the results of a geopositioning job into
a CIB job and create the necessary files required by CIB Generation. It allows the user to bypass
the creation of a USMSD file.
54.2.3.1 Import Geopositioning Job Description

The Import Geopositioning Job window, shown below, is used to create the files necessary for
CIB Generation without the need to create a USMSD file. It replaces the Import USMSD step in
the CIB job flow.
The Import Geopositioning Job window’s selections are as follows:
SELECT TO
Source Project Select the source geopositioning project.

ATF File Select the desired ATF file in the source project. If only one ATF file
exists in the source project, it will be automatically selected and read when
the source project is selected.
Rectangle ID Create the name of the rectangle ID that will be used to create the CIB
product.
Select Stereo Pairs Since CIB does not require stereo imagery, this is an optional step. See the
DPPDB Import Geopositioning Job (section 54.2.3) for further details.
Start Import the geopositioning project into the currently loaded CIB project.
54.2.3.2 Import Geopositioning Job Execution

The following steps are performed to import a geopositioning job into a CIB job:
Page 54-4 SOCET SET

1. Make sure that a successful triangulation has been performed in another SOCET SET
project (using the Geopositioning job flow).
2. On the SOCET SET menu, select Products > CIB Generation > Job Planning > Import
Geopositioning Job.
3. Select the source geopositioning project. If only one ATF file exists in the source project,
it will be automatically selected and read.
4. If multiple ATF files exists in the source project, select the ATF file.
5. Type in the Rectangle ID. The Start button will now become activated.
6. Optionally, select the stereo pairs for the imagery used in the triangulation. This will cause
the support files that are created by this process to be in the legacy FPE naming convention.
If stereo pairs are not selected, the support files will have the same naming convention as
the source project.
7. Press the Start button to initiate processing. All the files that were previously created by
importing a USMSD will be created by this process.
54.2.4 Job Planning - Import DTED

To obtain the proper accuracy for the CIB product, Digital Terrain Elevation Data (DTED) is
required. DTED is generally available in one-degree increments, and may be imported from CD-
ROM or from files on disk. For more information on the Import DTED window, See “DTED
Import” on page 17-13.
54.2.5 Job Planning - Merge DTM

Since CIB product areas are pre-defined by MIL-STD-89041, they do not match exactly to the
area of an imported DTED cell. Therefore, to cover the entire CIB product area, adjacent DTED
cells are imported and merged together into a single DTED file. For more information on the
Merge DTED window, See “DTM/Feature Merge,” Chapter 44.
54.2.6 Job Planning - Review/Edit DTM

After DTED has been imported and merged, it is a good idea to review the merged DTED file for
correctness. This may be done by creating a Terrain Shaded Relief (TSR) file, using Interactive
Terrain Edit. For more information on the Merge DTED window, please See “Interactive Terrain
Edit,” Chapter 39.
54.2.7 Job Planning - Import Image Support Data

The CIB Job Flow requires that adjusted image support data be imported during the Job Planning
stage. The Import Image Support Data window supports both AMSD(1) and USMSD(1) support
data types. Both of these support data types are generally available over a one-degree cell.
Importing either of these files will create image footprints, as well as other data files that are
required to complete the CIB Job Flow. For more information on the Import Image Support Data
window, See “DPPDB Generation,” Chapter 55.
The following describes how to use batch import on support data:
USMSD
start_socet –single import_usmsd -p <project name> -f <usmsd filename> -e <cib | dppdb> -s
IMPORT_SUPPORT_DATA_BATCH_FILE_USMSDT.txt
SOCET SET Page 54-5

AMSD
start_socet –single ImportAmsd -p <project name> -f <amsd filename> -e <cib | dppdb> -x < 1 |
0> where x indicates control or non-control –s <…../internal_dbs/DPPDB/
IMPORT_SUPPORT_DATA_BATCH_FILE_AMSDT.txt>
-r < 1 | 0> where x indicates adjacent or non- adjacent
54.2.8 Job Planning - Generate Footprints

During the import of image support data, footprints are generated for each image located in the
AMSD or USMSD file. These footprints are not elevation adjusted (i.e. contain only four vertices,
each with an average elevation). The CIB Job Flow requires that each image footprint that is to
be included in the CIB product be elevation adjusted using the imported and merged DTED. For
more information on the Review/Edit Footprints window, See “DPPDB Generation,”
Chapter 55.
54.2.8.1 Editing Production Cell

CIB production allows you to edit the production cell boundaries. You do this when imagery of
interest extends outside the standard production cell boundaries and you want to include that
imagery in the current CIB product instead of incurring the expense of creating a second CIB
product that covers the extra imagery. Note that editing the production cell will result in a non-
standard CIB product, so it is not recommended except in unusual circumstances.
Highlight the production cell in the Task MBRs table and then click on the Edit Production Cell
button to initiate editing of the production cell boundaries. Clicking this button invokes the Edit
Polygon Utility.
Page 54-6 SOCET SET

You can stretch the production cell boundaries by grabbing their vertices on the image display
and dragging them to their new desired values. Click the up arrow button on the Edit Polygon
Utility to accept the new boundaries and click the down arrow button to exit the Edit Polygon
Utility.
Note that editing the production cell so that it extends across zone boundaries is not supported.
If you attempt to do this, the edited polygon will be cropped at the zone boundary.
54.2.9 Job Planning - Import Imagery From D2C

CIB source imagery is sometimes contained on D2C tape. The Import Imagery From D2C
window extracts the imagery from tape and renames it according to the CIB naming convention.
Note that this window only supports the import of TFRD imagery.
This capability is only support on Unix platforms.
54.2.9.1 Import Imagery From D2C Description

The Import Imagery From D2C Window, shown below, is used to extract and rename TFRD source
imagery from D2C tape.
SOCET SET Page 54-7

The CIB Import window’s selections are as follows:
File > Exit Closes the Import Imagery From D2C window.
SELECT TO
Directory Select the directory in which to place the images.

Device Select the D2c tape device.
Start Start the import and rename process.
54.2.9.2 Import Imagery From D2C Execution
The following steps are preformed to use the Import Imagery From D2C Window:
1. On the SOCET SET menu, select Products > CIB Generation > Job Planning > Import
Imagery from D2C.
2. Select the D2C device by selecting (Ellipse Tool) in the device section of the window.
3. Press the “Start” button to begin the import and rename process.
4. Select File > Exit to close the window.
54.2.10 Job Planning - Import Assessment Imagery

A large amount of imagery is required to fill a CIB product area. Therefore, to save time and disk
space, the CIB Job Flow calls for the creation of an assessment mosaic, using reduced-resolution
images. The assessment mosaic is created using reduced-resolution imagery imported during this
step. For more information on the Import Assessment Imagery window, See “DPPDB
Generation,” Chapter 55.
Import Assessment Imagery uses the Condor® distributed processing software. For more
information See “Condor Distributed Processing” on page 60-1.
54.2.11 Job Planning - Stage CADRG

Each CIB product contains a Reference Graphic, which is a grayscale map that covers the CIB
product area. The Reference Graphic is created using CADRG files contained on CD-ROM. The
Stage CADRG window is used to import files from CD-ROM, chip them to the CIB product area,
and “stage” them to a pre-defined area, so that a later CIB application (CIB Generation) may
create the Reference Graphic.
Note that the Stage CADRG Window may be used for other purposes besides staging CADRG
for CIB. Only those items that specifically support CIB will be covered in this section.
Page 54-8 SOCET SET

54.2.11.1 Stage CADRG Description

The Stage CADRG Window, shown below, is used to import CADRG files from CD-ROM and
chip them out to match the CIB product area. The files are then “staged” in a pre-defined area so
that later CIB processes may create the CIB Reference Graphic.
The Stage CADRG Window includes the following selections for CIB:
File > Exit Exit the application
SELECT TO
Define MBR… Select and display the MBR. Defaults to the TRA. For CIB, the
COVERAGE_TREE MBR, which defines the CIB product area,
should be selected.
Margin Percentage Define the percentage (0-50%) to expand the MBR (area of interest).
Default is set to 50%. For CIB, this should be set to 0% so that only the
CIB product area is used to create the CIB Reference Graphic.
Job Type Selector for DPPDB or CIB.
Stage... Invokes the Stage Charts Window, described in the following section.
Import From Staging Creates a SOCET SET image and support file from the staged CADRG.
This allows the CADRG to be reviewed.
Select CIB Overview Chart The Stage CADRG process for CIB creates two different charts from
which to select. This button invokes a file selector, allowing the user to
choose the most appropriate chart (e.g. the chart that best depicts the
geographic context of the CIB product area).
SOCET SET Page 54-9

54.2.12 Stage Charts Description

The Stage Charts Window, shown below, provides a means of staging a chipped CADRG image
for later use in creating the CIB Reference Graphic. This window is invoked when the “Stage
Charts...” button is pressed on the Stage CIB window.
The Stage CADRG Window includes the following selections for CIB:
Options - Eject CD Ejects the CD (Unix only).
SELECT TO
Chart Type Select the chart type. For CIB, the chart type defaults to ONC.
% Coverage The percent coverage available for the selected chart type.
Charts List This table displays a list of the CD-ROMs required to stage CADRG for
the full CIB product area.
Chart ID Identifier of the chart. (i.e. name of the CD-ROM).
Latest Edition The latest edition available for the chart.
Edition Staged Show which edition you have staged. -1 indicates nothing staged for chart.
Staged Indicate whether or not the chart is staged.
% Total Coverage for Staged Percent coverage for the charts staged.
Charts
Stage... Stage the current CD.
Report Display a text report. The report may be printed and used to retrieve the
proper CD-ROM(s).
Done Close the window.

54.2.13 Execution for Stage CADRG

1. On the SOCET SET menu, select CIB Generation > Job Planning > Stage CADRG.
2. Click Define MBR.... This defines the MBR over which the CADRG will be chipped. For
CIB, select the “COVERAGE_TREE” MBR, which defines the CIB product area.
3. Select CIB as the Job Type.
4. Click Stage... to invoke the Stage Charts window.
5. The Stage Charts window is defaulted to ONC for CIB. Check the % Coverage to ensure
that it is 100%. If not, a different chart type may be selected.
6. The Charts List table lists all the CD-ROMs required to fill the CIB product area. Retrieve
the CD-ROM(s) listed in the table.
7. Insert a CD-ROM and click Stage. When the CD-ROM is successfully read, the “Edition
Staged” column in the table will change from -1 to the edition of the staged CD-ROM. The
“% Total Coverage for Staged Charts” will update as each CD-ROM is staged. Continue
inserting CD-ROMs until all those listed in the table have been staged. The “% Total
Coverage for Staged Charts” should read 100% when all have been staged.
8. Click Done on the Stage Charts window and return to the Stage CADRG window.
9. On the Stage CADRG window, click Import From Staging. This will create a pair of
SOCET SET images and support files from which to choose. Use “Load Images” to load
each of them and select the appropriate overview image (probably the one that shows the
more appropriate geographic detail).
10. Press the “Select CIB Overview Chart” button. This will invoke a file selector window used
to choose one of the two CADRG images.
11. Press File->Exit to close the Stage CADRG window.
54.2.14 Job Planning - Import CIB

The Import CIB Window is used for a variety of reasons in creating the CIB product. The
window includes four types of import:
1. Boundary Frames (Partial Frame Fill): Sometimes the available source imagery does not
completely cover the CIB product area. In this case, boundary frames from previously
produced CIB products may be used to fill in the gaps. This is referred to as Partial Frame
Fill, and must be done at the uncompressed level. Therefore, boundary frames are only
currently available on 8-mm tape.
2. Adjacent Frames (Radiometric Balance): The CIB being produced should match, as much
as possible, previously produced adjacent cells. This option is used to import edge frames
from adjacent cells for comparison purposes. When this option is selected, the “Cell
Margin” option becomes available, defining what percent of the edge frames will be
imported. Note that the import of adjacent frames is done at the compressed level, from a
CD-ROM.
3. Compressed CIB Cell: As mentioned previously, five-meter CIB includes several one-
degree cells. The CIB Job Flow allows merging of new one-degree cells with previously
produced one-degree cells to create a five-meter product on CD-ROM. This option provides
a means of importing previously produced five-meter cells for later merging with those
cells currently being produced.
4. Uncompressed Product: When Partial Frame Fill is required, adjacent uncompressed cells
on 8-mm tape become outdated. This is because their boundary frames have now been
merged with the frames currently being produced, resulting in new boundary frames. This
option is used to import adjacent uncompressed cells for merging with those frames current
being produced. For more information about the merging, see the Update Uncompressed
Product section later in this chapter.

54.2.14.1 Import CIB Description

The Import CIB window, shown below, provides several means for importing CIB.
The Import CIB Window contains the following selections:
File > Exit Closes the window.

Options > Eject Ejects the CD-ROM (Unix only).
SELECT TO
Import Type Allow the selection of one of the four import types described below.

SELECT TO
Boundary Frames This selection invokes the import of uncompressed CIB from a CD-ROM
device (can also be a DVD reader or disk location on the system) or an
8mm tape. This option is used for Partial Frame Fill. When the tape opiton
is run on Windows, the application displays a list of frames to extract from
tape. You need to manually extract the files to the specified location.
Adjacent Frames This selection invokes the import of compressed frames from CD-ROM.
This option is used to radiometrically (i.e. tonal balance) compare adjacent
cells with the cell currently being produced.
Compressed CIB Cell This import is used in a CIB five-meter job to import compressed CIB
Cells. These cells will later be merged with the cell(s) currently being
produced to create a five-meter product.
Uncompressed Product This import is used to import an entire uncompressed product, that will
later be updated to include Partial Frame Fill. This option can be done
from a CD-ROM device (can also be a DVD reader or disk location on the
system) or an 8mm tape. The the tape option is run on Windows, the
application prompts you to manually extract files from the tape to the
specified location.
Cell Margin This selection is used to define the percentage of boundary frames that will
be imported.
... (Device or directory) If the CD/DVD/Disk radio option is selected, clicking this button displays
a file selection window, from which a CD-ROM device or disk directory
can be selected. If the tape radio option is selected, clicking this button
displays a Select Device window, from which a tape device can be
selected. The selected device or directory appears in the text field to the
left of this button.
Start This button initiates the import processing.
54.2.14.2 Execution for Import CIB

1. On the SOCET SET menu, select CIB Generation > Job Planning > Import CIB.
2. Select one of the four CIB import options. If “Adjacent Frames” is selected, also select the
desired margin percentage.
3. Select the input device. This is either a CD-ROM (can be a DVD reader or disk directory),
or an 8-mm tape.
4. Select the output location. Since the location is defaulted to the project image location, it
should not be necessary to press this button unless disk space is an issue.
5. Select the Start button to import the selected type of CIB.
6. Once the import has finished, select File->Exit.Assessment Mosaic Production
54.3 Assessment Mosaic

During the assessment mosaic phase of the CIB Job Flow, the user will generate a reduced-
resolution mosaic, then edit the seamlines and tonal balance until the desired results are achieved.
Since the full-resolution mosaic is unwieldy in terms of size and processing time, the use of the
assessment mosaic has been provided as a time-saving mechanism in creating the CIB product.
Once the user is satisfied with the seamlines and tonal balance of the assessment mosaic, they are
automatically saved into SOCET SET data files, and will be applied to the final mosaic later in
the job flow.

54.3.1 Assessment Mosaic - Assessment Mosaic Production

The assessment (e.g. reduced resolution) mosaic is created to cover the area of the product and to
evaluate the imagery prior to creation of the full-resolution final mosaic. Because of its reduced
size, the assessment mosaic is easier to work with than the full-resolution final mosaic.
Once the assessment mosaic is generated the user will evaluate it (in terms of seamlines and tonal
balancing) and regenerate it as many times as necessary to achieve the desired result.
54.3.1.1 Assessment Mosaic Production Description

The Assessment Mosaic Production Window is the same as the basic SOCET SET Mosaic
window, with added capabilities for CIB. Since these capabilities are located on the “Output” tab,
only this tab, shown below, will be included in this section. For additional mosaic capabilities,
See “Mosaic,” Chapter 49.
The Assessment Mosaic Window contains the following selections for CIB:
SELECT TO
Resolution Select 5 Meter or 1 Meter.

Type Select Assessment or Final.
Classification Select UNCLASSIFIED or SECRET
54.3.1.2 Execution for Assessment Mosaic Production

1. On the SOCET SET menu, select CIB Generation > Assessment Mosaic > Assessment
Mosaic Production.
2. On the Input tab, select the assessment images and DTED.
3. On the Setup tab, toggle the “Update From” selector to “Input Images.” Press the “Update”
button. The coordinates of the input images will now be displayed.
4. On the Output tab
a. Select NITF 2.0 as the format. This is per the CIB spec.
b. Select either 5 Meter or 1 Meter as the resolution.
c. Select Assessment for Type.

d. Select the classification.

5. Change the name of the Output Mosaic File to assessment_mosaic.
6. It is recommended that the initial assessment mosaic be created “Most Nadir.” This
selection is located on the Options tab. Subsequent iterations should be created using
“Seam Polygons.”
7. Click Start to run the process.
8. Iterations of the above steps should be performed after adjusting the tonal balance and
editing the seamlines.
54.3.1.3 Assessment Mosaic Evaluation Process

The purpose of the assessment mosaic is to save processing time while performing adjustments
to the mosaic. Any adjustments made to the assessment mosaic will later be applied to the final
mosaic.
Once the first assessment mosaic has been generated, it should be loaded into the SOCET SET
display and reviewed. If brightness and contrast differences between mosaic images is visible
(e.g. the mosaic looks striped), this must be fixed on an individual image basis, using the SOCET
SET brightness and contrast slider bars. If the entire mosaic is too bright or too dark, this may be
corrected with the mosaic loaded, using the brightness and contrast slider bars.
Several iterations may be performed until the desired result is achieved. After the first iteration,
it is recommended that Seam Polygons be utilized to create each additional assessment mosaic.
54.3.2 Assessment Mosaic - Seamline Editor

When the initial assessment mosaic is created, a set of seamline polygons is also generated. These
polygons will generally need to be edited to remove bad points, or to ensure that seamlines are
hidden to the greatest extent possible. For more information on the Seamline Edit, See “Seamline
Editor” on page 49-26.
54.4 Create Image Segments

Once the user is satisfied with the assessment mosaic, full-resolution CIB image segments are
created. Later in the job flow, these image segments will be used to create the CIB final mosaic.
Each CIB image segment corresponds to a seamline polygon created and edited during the
assessment mosaic stage.
Create Image Segments uses the Condor distributed processing software. For more information
See “Condor Distributed Processing” on page 60-1.

54.4.1 Create Image Segments for CIB Description

The Create Image Segments for CIB Window, shown below, is used to create full-resolution CIB
image segments.
The Create Image Segments for CIB Window contains the following selections:

SELECT TO
Select File Select a seamline feature database. This database contains the seamline
polygons defined during the assessment mosaic stage.
Location Select an image location. This is where the CIB image segments will be
placed.
Review Request... Invokes the Review Request Window, described in the following section.
54.4.2 Execution for Create Image Segments for CIB

1. On the SOCET SET menu, select CIB Generation > Create Image Segments > Create
Image Segments for CIB.
2. Press the button associated with the “Select File” text box. This will invoke a Feature
Database Selector Window. Select the “assessment_mosaic_seams” feature database and
click OK.
3. It should not be necessary to change the image location, which defaults to the project image
location defined during Job Planning.
4. Click Review Request.... The Review Segment Request Window will appear.

54.4.3 Review Segment Request Description

The Review Segment Request Window, shown below, displays a list of the full-resolution CIB
image segments that will be created. The user may review the list, then create any or all of the
segments.
The Review Segment Request Window contains the following selections:
SELECT TO
Submit Request Submit the job via the Batch Scheduler Window.
Done Exit the window.
54.4.4 Execution for Review Segment Request

1. Examine the image segments located in the table. Select the images to create. If desired,
click Select All Segments to select all segments.
2. Click Submit Request.... This invokes an information window so that available and
required disk space may be reviewed. If satisfied, click Done. This invokes the Batch
Scheduler Window.
a. On a Windows system, immediately click OK. This will start the segment creation
process on the local machine.
b. On a Unix system, segment creation is run as a batch process that may be scheduled
at any time in the future. The operator also has the option of running the process on a
particular machine, or of allowing the software to determine the machine on which to
run (referred to as “Any Host”).
54.4.5 Segment Status Description

The Segment Status window, shown below, allows you to track the status of CIB segment orders.

SELECT TO
Image List Select the image list associated with the segment order to be tracked. This
will cause the segment table to be updated.
Update Update the segment table with the latest segment status.
Update Time Modify the time in which the software polls the status of the segment
order.
54.4.5.1 Segment Status Execution

1. Invoke the window by selecting Products > CIB Generation > Segment Status.
2. Select an image list. The image list is created by the Create Image Segments window, and
will be called SEGMENTS_<user>.list, where <user> is the current user logged into the
system. Once the image list is selected, the segment table will be updated with the latest
results.
3. To update the contents of the table, press the Update button. This will update the segment
table with the latest results.
4. To modify the polling time, select a new time on the Update Time pull-down menu.
54.5 Version History

For various reasons, it is often necessary to re-create a CIB product. The CD-ROM product itself
is tracked by the edition number. There is additional tracking, however, for each CIB frame (1536

x 1536 pixel block). The NITF header for each frame includes a section that details the complete
history of the frame, including producer and date.
The SOCET SET CIB Version History process allows the version history for each newly created
CIB frame to be updated appropriately. This involves obtaining prior version history from
previously produced CD-ROMs, then updating it with new production information.
If previously produced CD-ROMs are not available, the previous version number is obtained from
an NGA-supplied data file, then updated by one. If no previous CIB product has been created, the
version number will default to one.
54.5.1 Version History Description

The Version History Window, shown below, provides a means of obtaining version history from
previously produced CIB products.
The Version History Window contains the following selections:

SELECT TO
Update Update the version history file on disk with the current CD-ROM. If no
CD-ROM is in place, a base version history file will be created.
54.5.2 Execution for Version History

1. On the SOCET SET menu, select Product > CIB Generation > Version History.
2. The window contains two tables: one for the current cell under production, and one for the
cells adjacent to the current cell. For one-meter CIB, the top table will always contain a
single cell, while it will contain multiple cells for five-meter CIB.

3. Each row in the two tables signifies a previously produced CD-ROM that may be read by
the version history process (since border frames are shared by more than one CIB product,
they may be required as well). Insert one of the listed CD-ROMs and press the “Update”
button. Continue until all the available CD-ROMs have been used.
4. Press File > Exit to close the window.
The CIB Version History Window creates a version history file located in
the CIB subdirectory of internal_dbs. This file must exist prior to the final
CIB generation process.
54.6 Mosaic Production

Mosaic Production is used to create the final mosaic (full-resolution) that will be used to generate
the uncompressed CIB frames. The Mosaic Production Window is identical to the Assessment
Mosaic Production Window, described in an earlier section.
54.6.1 Execution for Final Mosaic Production

1. On the SOCET SET menu, select CIB Generation > Final Mosaic > Final Mosaic
Production.
2. Since a settings file was created during the assessment mosaic process, most of the setting
should already be correct. However, the following settings on the Output Tab do need to be
changed:
a. Select “final_mosaic” as the Output Mosaic File.
b. Select Final for Type.
c. Select Classification.
3. Click Start to run the process.
For final mosaic production, the mosaic is forced to exactly cover the CIB
product area. Therefore, any changes to the Output Boundary on the Setup
Tab will be ignored by the software.
54.6.2 Final Mosaic - Sheet Cutter

The Sheet Cutter process is used to cut the CIB Final Mosaic into smaller frames. These
temporary frames will later be used by the CIB Generation process to create uncompressed CIB
frames. For addition information, See “Mosaic Sheet Cutter” on page 49-32 for commands and
basic execution.
54.6.2.1 Sheet Cutter Description

The Sheet Cutter Window, shown below, cuts the Final Mosaic into temporary (raster format)
frames that will later be used to create the CIB frames.

The Sheet Cutter Window contains the following selections for CIB:

SELECT TO
Start Starts the Sheet Cutter process for CIB.
54.6.2.2 Execution for Sheet Cutter

1. On the SOCET SET menu, select Product > CIB Generation > Final Mosaic > Sheet
Cutter.
2. The final mosaic process creates a settings file for Sheet Cutter. Since this settings file is
tailored specifically for CIB, it should not be necessary to make any changes to the window.
Press Start to initiate processing.
The result of Sheet Cutter is a set of raster files located in the project
image location. These raster files will later be used to create the
uncompressed CIB frames. No CIB frames are actually created by this
process.

54.7 CIB Image Source

SOCET SET allows CIB-Like products to be created from a variety of commercial image sources.
There may be several different commercial image sources, as well as NTM, in a single product.
The CIB Image Source window allows you to select the image source for each image included in
the final mosaic image. The selections made from this window will be reflected in the ISORCE
and RPF Attribute sections of the CIB NITF metadata.
54.7.1 CIB Image Source Description

The CIB Image Source window, shown below, is used to populate required metadata fields in the
final CIB product. Right-clicking on the “ISORCE” and “License” columns displays a
configurable set of source imagery and licensing options.
The CIB Image Source window’s selections are as follows:
SELECT TO
ISORCE Select the source image type for this image. This data will fill the ISORCE
field in the CIB NITF Image File subheader. Multiple rows can be selected.
License Select the license type for this type of imagery. This data will fill the
Image Source field in the RPF Frame File Attribute section of the CIB
NITF metadata. Multiple rows can be selected.
Save Save the data to the cib_image_source.txt file in the SOCET SET project
directory (cib sub-directory).

54.7.2 CIB Image Source Execution

The following steps are performed to select CIB image source for inclusion in the NITF metadata:
1. Verify that the desired ISORCE and License options are set. This is accomplished by
editing the CIB_ISORCE.txt and CIB_license.txt files in the CIB directory of SOCET SET
internal_dbs. Any new image sources or licenses should be added to the files.
2. On the SOCET SET menu, select Products > CIB Generation > CIB Image Source.
3. Right-click on any cell in the ISORCE column. A list of possible CIB image sources will
be presented. Use the left mouse button to select an image source. Note that the list of CIB
image sources is read from the configurable CIB_ISORCE.txt file.
4. Right-click on any cell in the License column. A list of possible CIB licenses will be
presented. Use the left mouse button to select license. Note that the list of CIB licenses is
read from the configurable CIB_license.txt file.
5. Once all the cells in the table are filled in, Click the Save button. This writes out the
cib_image_source.txt file in the cib subdirectory of the SOCET SET project. The CIB
Generation step then reads this file and places the appropriate image sources and licenses
in the CIB metadata.
54.8 Generate CIB

Now that the CIB Final Mosaic has been cut into CIB-sized raster frames, the CIB Generation
process is used to create both the uncompressed and compressed CIB products.
54.8.1 Generate CIB Description

The Generate CIB Window, shown below, provides a framework for the creation and QC of both
uncompressed and compressed CIB.

The Generate CIB Window contains the following selections::

SELECT TO
Final Mosaic Select the final mosaic support file. This text field will default to
“final_mosaic.sup.”
Generation Generate uncompressed or compressed CIB.
Quality Control Inspect uncompressed or compressed CIB. The Overview Image and
Reference Graphic may also be inspected.
Review Metadata... Review and edit a subset of the CIB metadata.
Output… Invoke the Product Output window.
Classification Select the classification level of the product. This allows the uncompressed
product to be at one classification and the compressed product to be at
another classification.
54.8.2 Execution for Generate CIB

1. On the SOCET SET menu, select Product > CIB Generation > Generate CIB.
2. If the name of the final mosaic is incorrect, select it by clicking (Ellipse Tool) at the top
of the window.
3. Toggle the classification to either UNCLASSIFIED or SECRET.
4. Click Review Metadata..., then select “Uncompressed” from the popup window. Review
and make any required changes to the metadata prior to generating the uncompressed CIB.
5. Toggle the Generation Selector to “Uncompressed,” then click Generate.
If uncompressed boundary frames have previously been imported, the

software will automatically use them to perform what is referred to as
“Partial Frame Fill.”
6. Once the uncompressed frames have been generated, toggle the Quality Control Selector to
“Uncompressed,” then click QC. This will invoke the CIB Viewer, which may be used to
zoom in and out and move from left to right. Inspect the uncompressed CIB, then select File
> Exit on the CIB Viewer.
7. Toggle the Quality Control Selector to “Ref Graphic,” then click QC. On the popup
window, select “Uncompressed.” This will load the uncompressed CIB Reference Graphic
into the SOCET SET display. Review the Reference Graphic.
8. Toggle the Quality Control Selector to “Overview,” then click QC. On the popup window,
select “Uncompressed.” This will load the uncompressed CIB Overview Image into the
SOCET SET display. Review the Overview Image.
9. Once satisfied with the uncompressed CIB product, again press the “Review Metadata...”
button. On the popup window, select “Compressed.” Make any required changes to the
compressed CIB metadata and close the window.

10. Toggle the Generation Selector to “Compressed,”’ then click Generate. This will invoke
the Batch Scheduler Window.
a. On a Windows system, the compression can be run using the Condor distributed
processing software. For more information on setting up and using Condor, See
“Condor Distributed Processing” on page 60-1. To maximize throughput for CIB
generation, the “Any Host” option on the Batch Scheduler Window should be
selected, allowing the Condor software to select the machines to be used for VQ
Compression. Since the compression of each CIB frame is done separately, this will
allow frames to be compressed in parallel on different machines. If a particular
machine is selected, all frames will be compressed serially on the selected machine.
After selecting the desired machine or “Any Host,” select OK on the Batch Scheduler
Window.
b. On a Unix system, immediately click OK on the Batch Scheduler Window. This will
start the compression process on the local machine.
11. Once the compressed frames have been generated, toggle the Quality Control Selector to
Compressed, then click “QC. This will invoke the CIB Viewer, which may be used to zoom
in and out and move from left to right. Inspect the compressed CIB, then select File > Exit
on the CIB Viewer.
Since classified imagery is often used as an input to an unclassified CIB

product, the QC process for compressed CIB also performs a “Dirty Word
Check.”
12. Toggle the Quality Control Selector to “Ref Graphic,” then click QC. On the popup
window, select Compressed. This will load the compressed CIB Reference Graphic into the
SOCET SET display. Review the Reference Graphic.
13. Toggle the Quality Control Selector to “Overview,” then press “QC.” On the popup
window, select Compressed. This will load the compressed CIB Overview Image into the
SOCET SET display. Review the Overview Image.
14. For Unix systems, the CIB Generate Window provides the capability to create an
uncompressed CIB product on 8-mm tape. This is done using the Product Output Window,
described in the next section. To invoke the Product Output Window, select the “Output...”
button.
15. Once satisfied with the compressed CIB, select File > Exit on the Generate CIB Window.
Once the compressed CIB product has been created on disk, third-party
CD-ROM writing software may be used to create the CD-ROM product.
One-meter CIB: The product is now ready for output to CD-ROM.

Five-meter CIB: The Merge 5-Meter Cells Window must be used to create the final product.
54.8.2.1 Product Output Window

The Product Output Window is used only to write the uncompressed CIB product to 8-mm tape.
To create a compressed product, third-party CD-ROM writing software is required.
Uncompressed CIB is written to 8-mm tape on a sub-cell basis. In other

words, each 8-mm tape will include only a single one-degree cell.

54.9 Merge 5-Meter Cells

As mentioned earlier, a five-meter CIB product consists of multiple one-degree cells. Since each
of these cells is represented by a different SOCET SET project, the Merge 5-Meter Cells Window
is required to create the final five-meter product that will be written to CD-ROM.
Sometimes, only a subset of the five-meter product is actually generated. In this case, a previously
produced five-meter product is used to fill the remaining cells in the merge process. The process
for merging previously produced cells is as follows:
1. Create a new SOCET SET project using the CIB Job Setup Window. Make sure to toggle
Foreign Project on the Job Setup Window.
2. Use the Import CIB Window to import the compressed CIB product into the new SOCET
SET project.
3. Use the Merge 5-Meter Cells to merge the foreign project with the generated project(s).
54.9.1 Merge 5-Meter Cells Description

The Merge 5-Meter Cells Window, shown below, creates the final five-meter CIB product that
will be written to CD-ROM.
54.9.2 Execution for Merge 5-Meter Cells

1. On the SOCET SET menu, select CIB Generation > Merge 5-Meter Cells.

2. The window contains a table listing each of the one-degree cells required to create the
applicable five-meter CIB product. The window also displays the Cell Index and number
of sub-cells.
When the window is first invoked, one of the rows in the table
will be populated. This row corresponds to the SOCET SET
project from which the window was invoked.
3. Select the CIB output directory by clicking (Ellipse Tool) near the top of the window.
This will invoke a directory selector window. Select the directory and press “OK.”
The merge process will create an “RPF” directory in the

selected directory. To avoid problems, ensure that no “RPF”
directory already exists in the selected directory. It is
recommended that a new directory be created and used for the
output location of the five-meter CIB product.
4. Each of the rows in the table corresponds to a sub-cell in the five-meter product. Prior to
creating the product, each of the rows must be assigned to a SOCET SET project. To assign
a project to a row, right click on the row and select “Assign Project.” A file selector window
will appear. Select the appropriate SOCET SET project file (signified with the “.prj”
extension) and click OK to close the window. Continue until all rows have been assigned
to a project. The shift key may be used to select and assign multiple projects at the same
time.
Only one foreign project may exist. However, if more than one cell from
a foreign project is being merged, the foreign project will appear in
multiple rows of the table. In other words, each row in the table that is
NOT being generated must be assigned to the same foreign project.
5. Click Start.
The five-meter product is now ready for output to CD-ROM.
54.10 Update Uncompressed Product

As mentioned earlier, the pre-defined CIB product boundaries do not always match up with the
available imagery. In this case, Partial Frame Fill is performed to fill in missing border frames.
Since border frames are shared by adjacent CIB cells, the adjacent cells are now out of date.
The “Update Uncompressed Product” capability is used to update the uncompressed imagery on
disk so that it now contains the Partial Frame Fill. Once it is updated on disk, the data can be
written to a DVD by the user. The “Update Uncompressed Product” window also provides the
option for writing the data to an 8mm tape device after updating has completed. The 8mm tape
capability is only available on UNIX systems.

54.10.1 Update Uncompressed Product - Import Uncompressed

Product
The first step in updating the uncompressed product is to import it into SOCET SET. This is
simply a copy of the data from a CD or tape to disk.
54.10.1.1 Import Uncompressed Product Description

The Import CIB Window is used to import the uncompressed product into SOCET SET. For more
information, see the CIB Import Section of this chapter.
54.10.2 Update Uncompressed Product - Output Updated

Uncompressed Product
The second step in updating the uncompressed product is to merge in the modified border frames
and output them to disk. An optional third step on UNIX systems allows the updated data to be
output to an 8mm tape device. This is done using the Output Updated Uncompressed Product
Window.
54.10.2.1 Output Updated Uncompressed Product Description

The Updated Uncompressed Product Window, shown below, is used to update the uncompressed
product and, optionally, to output it to 8mm tape on UNIX systems.
The Updated Uncompressed Product Window contains the following selections::


SELECT TO
Uncompressed Directory Select the directory in which the uncompressed product was imported.
ExportUpdated Product to Specify writing to 8mm tape, if checked (UNIX only).
Tape
Tape Device... Select the 8mm tape device to be written to.
Start Start the update and output process.
54.10.2.2 Execution for Output Updated Uncompressed Product

1. On the SOCET SET menu, select Products > CIB Generation > Update Uncompressed
Product > Output Updated Uncompressed Product.
2. Select the directory for temporary storage of the data read from CD/DVD/Disk or tape. This
is done by selecting the (Ellipse Tool) in the “Uncompressed Directory” area of the
window. A directory selector window will appear. Select a directory and click OK to close
the window. Normally, this directory will already be populated on the window when you
bring it up, and will be the directory that you chose when you previously ran CIB Import
to import the uncompressed product.
3. [Optional, UNIXonly] If you want to output your data to an 8mm tape device, check the
“Export Updated Product to Tape” check box. Then, use the Tape Device selector to select
your 8mm tape device.
4. Click Start. The data will automatically be merged and, if specified, the updated product
will be written to tape.
This process is performed at the sub-cell level. In other words,

each updated tape will only contain a single one-degree cell.

Chapter 55
DPPDB Generation
Digital Point Positioning Database (DPPDB) is a product
composed of stereoscopic images stored on a DVD or 8mm
tape.
55.1 Job Planning

The Job Planning phase of the DPPDB production flow initiates the job and gathers the needed
files and support data for DPPDB Generation. This is obtained by selecting Products > DPPDB
Generation > Job Planning.
Components of Job Planning are:
• Review/Edit Image Location
• Job Setup
• Stage CADRG
• Import DTED
• Import Image Support Data
• Generate Footprints
• Import Imagery from D2C
• Import Assessment Imagery
• Check Assessment Image Status
55.2 File Structure for DPPDB
55.2.1 Review/Edit Image Locations
SOCET SET Page 55-1

Chapter 55 - DPPDB Generation
A new image location will be created for each project created for the purpose of DPPDB
Production.
Image Location
File Path
A SOCET SET image location with sufficient disk space (approximately 30 gigabytes) is
required prior to creating a DPPDB production job.
55.2.2 Job Setup

Job Setup is required for all DPPDB production jobs. All DPPDB projects are created as
Geographic Ellipsoid with a product specific directory structure unique to DPPDB. An 11
character project name is required in Job Setup to assist in the tracking process throughout the
job flow.
Job Setup will create a SOCET SET project and automatically import JNC/GNC reference
graphics and available WMED data into the project if available. Environment variable CADRG-
TOP will need to be set in the .socet file to point to the appropriate storage location for these files.
Access Job Setup by selecting Products > DPPDB Generation > Job Planning > Job Setup.
Page 55-2 SOCET SET

The Job Startup window’s selections are as follows:
File > Exit Exits the application

SELECT TO
Project Name 11 Character project ID

Image Location Location of the project image data
Triangulation Rectangle Area Northwest corner of the rectangle. This data can be pulled out of the
Northeast X/Y USMSD file.
Southwest X/Y Southwest corner of the rectangle.

Start Creates project files and imports WMED and CADRG reference graphics
if available.
55.2.3 Job Planning - Import Geopositioning Job

The Import Geopositioning Job Window is used to import the results of a geopositioning job into
a DPPDB job and create the necessary files required by DPPDB Generation. It allows the user
to bypass the creation of a USMSD file.
55.2.3.1 Import Geopositioning Job Description

The Import Geopositioning Job Window, shown below, is used to create the files necessary for
DPPDB Generation without the need to create a USMSD file. It replaces the Import USMSD step
in the DPPDB job flow.
SOCET SET Page 55-3

The Import Geopositioning Job Window’s selections are as follows:
SELECT TO
Source Project Select the source geopositioning project.

ATF File Select the desired ATF file in the source project. If only one ATF file
exists in the source project, it will be automatically selected and read when
the source project is selected.
Rectangle ID Create the name of the rectangle ID that will be used to create the DPPDB
product.
Select Stereo Pairs Since DPPDB is a stereo product, this is a required step. See the next
section for details.
Start Import the geopositioning project into the currently loaded CIB project.
55.2.3.2 Import Geopositioning Job - Select Stereo Pairs

The Select Stereo Pairs Window, shown below, provides the user with a means of selecting the
stereo pairs that will be used to create the DPPDB product. By right clicking on a cell in the table,
the user may select, change, or delete a stereo mate.
Page 55-4 SOCET SET

When right clicking on an empty cell in the above table, the Select Stereo Mate Window, shown
below, will appear. Each overlapping image will be presented, sorted by percent overlap.
55.2.3.3 Import Geopositioning Job Execution

The following steps are performed to import a geopositioning job into a CIB job:
1. Make sure that a successful triangulation has been performed in another SOCET SET
project (using the Geopositioning job flow).
2. On the SOCET SET menu, select Products > DPPDB Generation > Job Planning >
Import Geopositioning Job.
3. Select the source geopositioning project. If only one ATF file exists in the source project,
it will be automatically selected and read.
4. If multiple ATF files exists in the source project, select the ATF file.
5. Type in the Rectangle ID.
6. Select the stereo pairs for the imagery that will be used to create the DPPDB product. This
will cause the support files that are created by this process to be in the legacy FPE naming
convention. After stereo pairs are selected, the Start button will become activated.
SOCET SET Page 55-5

7. Press the Start button to initiate processing. All the files that were previously created by
importing a USMSD will be created by this process.
55.2.4 Import Support Data

Import Support Data converts triangulated support data in the form of an AMSD(1) or USMSD(1)
into SOCET SET support files for a selected project. A copy of the file is retained and stored in
the project directory for use by other applications later in the job flow.
Note: The Import Support Data window also supports the import of untriangulated support data
in the form of AMSD(0), USMSD(0), or MSD(i). However, since they are untriangulated, these
support files are not suitable for DPPDB.
The Import Support Data window’s selections are as follows:

Options > Set Control Selecting this option will turn off parameter adjustment for the imported
support data. This allows the imported support data, and its associated
imagery, to be used for control purposes.
SELECT TO
Input File File selection window that enables you to browse to the storage location of
the AMSD or USMSD and select the file.
Adjacent Rectangle This toggle flags the selected support data, and all its related SOCET SET
project files, as an adjacent rectangel rather than a geopositioning
rectangle.
Page 55-6 SOCET SET

SELECT TO
Start Imports the support data into the project and creates .sup files for each
image in the AMSD or USMSD. Image lists and a blank adverse area FDB
file are also created. The original AMSD or USMSD is copied into the
dps_input_files directory for use in RPC Generation.
Triangulated SOCET SET support files (AMSD(1) or USMSD(1)) are required to create a
DPPDB product. If an AMSD(1) or USMSD(1) is not provided along with the source imagery, a
USMSD(1) may be created using VCT batch.
The following describes how to use batch import on support data:
USMSD
start_socet –single import_usmsd -p <project name> -f <usmsd filename> -e <cib | dppdb> -s
IMPORT_SUPPORT_DATA_BATCH_FILE_USMSDT.txt
AMSD
start_socet –single ImportAmsd -p <project name> -f <amsd filename> -e <cib | dppdb> -x < 1 |
0> where x indicates control or non-control –s <…../internal_dbs/DPPDB/
IMPORT_SUPPORT_DATA_BATCH_FILE_AMSDT.txt>
-r < 1 | 0> where x indicates adjacent or non- adjacent
55.2.5 Import DTED

DTED is necessary in the DPPDB flow to ensure that segment footprints are properly displayed
within the final product. WMED is automatically imported into the project during job setup and
may be used to create the product, however Level 1 or better DTED is recommended.
The Import DTED window’s selections are as follows:
SELECT TO
Input DTED File The original DTED file used for input.
Output DTM File The name of the SOCET SET DTED file desired for output.
DTED Editor Allows an interface to edit the imported DTED file.
Start Begins the import and conversion process for the DTED file.
DTED is important in a DPPDB product because it can have a dramatic effect on the placement
of segment footprint boundaries. Exploitation systems use the footprint boundaries as validation
SOCET SET Page 55-7

lines in the product and will not let a cartographer drop any points outside of the segment
footprints identified in our product. Although all levels of DTED may be utilized for segment
footprints, Level 1 or better is always recommended.
55.2.6 Review/Edit Footprints

Review/Edit Footprints provides a graphical interface that allows a cartographer to visually
review and manipulate image and model footprints in the project. This application provides a
variety of functions that are utilized by DPPDB. An image list, created upon import of the
AMSD(1) or USMSD(1), is required, along with a specific strategy file for the job type.
The Review/Edit Footprint window’s selections are as follows:
Page 55-8 SOCET SET

SELECT TO
Strategy File DPPDB.strat is required.

Graphic Attributes File Currently Defaults.lwugra is used.
Graphics Toggles the Draw in RT function on/off
Footprint Type Change the desired application to invoke via Review/Edit
Review/Edit Access the individual footprint applications
TOGGLE TO
Draw Graphics Enable automatic graphic updates to the RT Display. Toggle this off if you
need to use another graphics application such as ATE.
Graphics Selection Enable the sketch graphics interface between Review/Edit footprint
applications and RT.
Adverse Area Display adverse areas and void areas created for the DPPDB product.
Apply Filters Filter the display of adverse areas on Parent and Retask images
Task MBR Draw the Task MBR footprint once it has been invoked from the Review/
Edit Footprint type. Use the Footprint Fill to color the inside of the
selected rectangle and IDs to display the name of the listed features.
Image Footprints Draw the Image footprints once it has been invoked from the Review/Edit
Footprint type. Use the Footprint Fill to color the inside of the selected
rectangle and IDs to display the name of the listed features.
Model Footprints Draw the Model footprints once it has been invoked from the Review/Edit
Segment Footprints Draw the DPPDB Segment footprints once it has been invoked from the
Review/Edit Footprint type. Use the Footprint Fill to color the inside of the
Footprint Fill Shades in a selected feature
IDs Displays the name of a selected feature.
SOCET SET Page 55-9

55.2.7 Review Task MBR Footprint

This displays the bounding box of the working areas and image lists for the project.
The Review Task MBRs window’s selections are as follows:
SELECT TO
Select All Graphically display all of the Task MBRs in RT.

Task MBR Report Review the text file containing all of the Task MBR information for the
selected project.
Close Exit the gui

55.2.8 Generate Image Footprints

This provides the elevation data necessary to project accurate image footprints that eventually
make their way into the IGEOLO field of the product. DTED level 1 or better is recommended.
However, WMED will suffice if a more accurate DTED file is not available.
The Review Edit Image Footprint window’s selections are as follows
SELECT TO
Image Source Select individual images or an image list imported from the AMSD or
USMSD to create image footprints.
DTM File Select an Imported DTED file for use in generating the image footprints at
the correct elevation.
Elevation Tolerance Set a tolerance level for elevation when generating the image footprints.
Not recommended for use in DPPDB Generation.
Constant Elevation Sets all of the generated footprints to a set elevation. Not recommended for
use in DPPDB generation.
Auto Generate/Draw Automatically updates the footprint display if the Constant elevation or
Elevation tolerance is changed. Not recommended for use in DPPDB
generation.
Vertices Change the number of vertices created for each image footprint

SELECT TO
Thinning Criteria Generate the image footprint with the thinning option enabled. The number
of vertices are traversed, for three consecutive vertices, if the middle
vertex is within the thinning criteria of the other two, it is eliminated.
Selected Enable the Generate/Draw or Erase options for only the selected images in
the list.
All Enable the Generate/Draw or Erase options for all of the images in the list
Generate/Draw Create image footprints based on the input criteria selected above and then
display the footprints in RT.
Draw Display image footprints that have already been generated in the RT
display. Used as a refresh option.
Erase Remove footprints from the RT Display.
Save Footprints Save the generated footprints and updates the image support files to reflect
the new elevations.
Close Exits the gui
55.2.9 Edit Model Footprints

This allows the cartographer the capability to remove excess overlap between models. This
process is extremely helpful in DPPDB segment generation because it decreases the amount of
individual segment editing required and provides the cartographer a nice clean view of the
rectangle to be segmented.

The Review Edit Model Footprint window’s selections are as follows
SELECT TO
TAA Filter Check to filter the graphics display to draw only TAA1.
Rectangle Filter Filter the graphics display to draw only the selected rectangle if more then
one AMSD/USMSD is imported into the project.
Deselect All Deselect any images highlighted in the Model Name list.
Recreate Footprint Crop the model footprints around the outside of the TAA. DPPDB requires
a 1000 ft minimum external boundary.
Edit Footprint Manually adjust each vertex of an individual stereo pair.
Crop Footprint Crop a stereo pair by drawing a bounding box around the rectangle. This is
used to reduce excess overlap between models.
Close Exit the gui

55.2.10 Recreate Model Footprints

This allows the cartographer to quickly trim the model footprints to the size recommended in the
DPPDB production specification. The default setting for this process is 1000ft around the outside
of the TAA. This setting can be changed by the cartographer if necessary.
The Recreate Model Footprint window’s selections are as follows
SELECT TO
Pixels Change the crop criteria to be based on pixels. This option is not used for
DPPDB.
Selected Only Allows the cartographer the option to individually adjust the size of the
TAA in the N, S, E, or W directions.
None Select when not creating a DPPDB.
Feet Change the crop criteria to be based on Feet. The default setting for this
option is 1000ft as required by the DPPDB production specification.
Current Selection Only Recreate the footprints for a single selected model.
All Selected Models Recreate the footprints for only the selected models.
All Models Recreate the footprints for all models in the TAA.
OK Start the crop
Read Defaults Reset the gui to the original settings
Cancel Exit the gui without recreating the model footprints.
55.2.11 Import Assessment Imagery

The cartographer uses assessment images to assess the suitability of the area to create a DPPDB.
Assessment imagery is used as a reference in creating segment boundaries to ensure that major
cities are not split or that islands not appearing on the reference graphic are omitted. It is also used

as a reference in drawing adverse areas and as an initial step in the DRA adjustment for the final
segments. Images can be ordered at a number of RRDS levels, however we recommend R3 or R4
to save space and still meet the needs of the process.
Import
Assessment
Imagery GUI
The Import Assessment Imagery window’s selections are as follows:

SELECT TO
Image Source Select the type of input for the request. An image list is the most
commonly used Image Source. However, selecting an individual image is
an option and can come in handy if only one or two images are required.
Images Provides a visual reference for the images to be imported.
MBR Setup Allows the cartographer a graphical interface to chip the images included
in the list over a geographic area.
Image Retrieval Setup Specifies the starting minification level of the imported images and
provides access to the image location for the specified project.
Review Request Provides sizing information on the images requested.
Submit Request Invokes the batch scheduler gui to begin image processing.
TFRD Imagery for DPPDB production in SOCET SET is assumed to be in the compressed image
format, prefixed with ‘R0_,” and the project name appended to the end of the image name and
before the.cmp extension. The imagery must reside in the project image location for the order to
be successful (e.g. R0_ImageName_project.cmp). Unclassified imagery must retain the original
image name as it is stored in the accompanying USMSD(1).

55.2.12 Stage CADRG

CADRG at the JGA or TPC level is required as a reference graphic for all DPPDB products. The
graphic is imported with a margin of about 15% around the outside of the working area of the
product. It is included as an entry in the Master Product File and as individual NITF images on
the product DVD. Although SOCET SET does provide the capability of creating a reference
graphic that spans multiple zones, existing exploitation systems will fail to read the product if
these exist. The CADRG_TOP environment variable must be pointed to the CADRG_DB folder
containing the “index.ntf” file.
If your DPPDB product spans one of the CADRG zone boundaries (latitude 0, 32, 48, 56, 64, 72,
76 or 80 degrees), you can set the environment variable ALLOW_MULTIPLE_CADRG_ZONES
to the value “TRUE”. This allows CADRG frame files from multiple zones to be included in the
final DPPDB product. Stage CADRG removes the frame files from one of the two zones if this
environment variable is not set. Note that DPPDB products with CADRG’s that cross zone
boundaries are non-standard and most software packages will not be able to ingest them.
The Stage CADRG window’s selections are as follows:
File Exits the application

Options > Auto Minify Creates Min levels for the image for use in the SOCET SET RT display
Image only.
Options > CD-ROM to Creates the online CADRG database. Not for use in DPPDB.
CADRG Database
Options > Update CADRG Updates the online CADRG database. Not for use in DPPDB.
database using Update CD-
ROM

SELECT TO
Output Setup Adjust the requested dimensions of the CADRG to import.

On-line Charts Available View available ONC/JNC files in the On-line database. Not for use in
DPPDB.
DPPDB/CIB Chart Staging Select the DPPDB processing option for creating a reference graphic
Stage Invoke the Stage CADRG gui used to identify the JGA or TPC files
required for import.
Select CIB Overview Chart Not used for DPPDB.
Import from Staging Convert the staged CADRG data from CD into .ntf format required for the
DPPDB reference graphic. Creates .sup files for review in the RT display.
55.3 Segment Generation

This is obtained by selecting Products > DPPDB Generation > Segment Generation.
GUI Needed
55.3.1 Geometric Validation

Geometric Validation is the initial process of creating DPPDB segments. Default criteria is used
to automatically generate segments and validate them based on the geometry of each segment.

Segments that successfully validate are outlined in blue and segments that fail are identified by a
dashed brown line.
Auto Segment Generation window’s selections are as follows:
SELECT TO
Criteria Adjust the minimum and maximum size of the segments and to establish
the size of the East/West overlap area.
Technique Change to way that a model is divided into segments. Even partitioning is
the recommended setting.
Input Determine which models to include in generating segments.
55.3.2 Edit Segments

DPPDB products are flexible by design. The cartographer has the ability to adjust the size and
position of each stereo segment within the confines of the triangulated rectangle. This flexibility
allows the cartographer the ability to adjust segment boundaries to completely enclose cities or

other points of interest. Parent image Segments can be replaced by Retask image segments or vise
versa to improve the quality of the final product.
The Review/Edit Segments window’s selections are as follows:
SELECT TO
Models Select models in the model list that will display the associated segments
below in the Segments list. The model list contains all of the models
created for the TAA in Recreate/Model footprints.
Segment Alignment Adjust Angle and Auto Align are not used in DPPDB production.
Segments Display a list of the segments generated for a selected model. Highlighting
a segment and using the right mouse button enables the cartographer to
select several available editing options for the segment.
Edit From right-click menu - Adjust individual vertices of a segment. This
option is used most often to adjust the overlap area of retask segments.

SELECT TO
Split Segment From right-click menu - Split a selected segment into two segments. The
left mouse button selects the area to split and a right mouse button accepts
the feature.
Shift Overlap From right-click menu - Move the overlap area between two segments. The
first selection of the left mouse button selects the overlap area to move. A
second selection of the left mouse button moves the overlap area. The right
mouse button accepts the feature.
Add Create a freehand segment using sketch funtionality. This is a tricky way to
add a segment and takes some practice. A freehand segment must be drawn
within the bounds of a stereo model and be within the tolerance of the
strategy file.
Delete Delete a single segment or several segments at once.
Reset All Revert back to the last save.
Save All Save all segments.
Snap to Model Edges Enable the Snap functionality during edits. This feature reduces the
frustration of creating freehand segments.
Draw Display graphics for the specified selection.
Auto Generate Create segments across the entire rectangle or a selected area based on
criteria identified by the cartographer.
Validate Criteria Review/edit the criteria used to establish a valid segment.
Auto Generate RPC Always attempt the RPC fit when an edit or new segment is accepted. This
can add a significant amount of time to the editing process if toggled on.
Generate RPC Start the RPC fit for all of the geometrically valid segments in the
rectangle.
Generate Statistics Create the statistics required for the reports that populate the text files in
the master product file. This is a required step and could result in an
invalid product if not selected.
Review RPC Statistics Review the statistical data generated in the previous step.
Generate FDB Create FDB file to display final segment boundaries and names.
Close Exit the gui
The editing process is a combination of custom editing commands and existing Feature Extraction
functionality. The cartographer should be able to select segments for edit from either the GUI list
or from the graphical display. Segments will display as geographically invalid if the MBR does
not cover a stereo model footprint. Keep an eye on your segment list. Inexperienced cartographers
will often create two layers of segments directly on top of one another.
55.3.3 RPC Validation

RPC Validation is the process of creating a Rational Polynomial Coefficient fit for the
triangulated rectangle. This basically translates to “the math that makes a DPPDB the accurate
product that it is.” Each geometrically valid segment is mathematically compared to every other
geometrically valid segment in the rectangle. A series of algorithms are used to generate synthetic
points and calculate the accuracy of the final product. a .jsf file is then created for each segment
and stored in the project dppdb directory for use in image processing. RPC valid segments are

graphically represented by yellow (parent), pink (retask1), or green (retask2) segment

boundaries. Invalid segments are displayed as dashed brown lines. If an AMSD(1) or USMD(1)
is not present in the project dps input files directory, the RPC validation will automatically fail.
The RPC Validation selections in the Review/Edit Segments window are as follows:
SELECT TO
Auto Generate RPC Automatically attempt to generate the RPC fit for any segment that is
edited or added.
Generate RPC Manually start the RPC generation process.
Generate Statistics Create the statistics required for input into the master product file. These
statistics include the product accuracy and CE/LE values for each segment.
Review RPC Statistics Visually display the RPC Statistical data generated for the segments.
RPC validation is a math intensive process that can take up to 45 minutes for a full rectangle (65
segments). Iterations of running the RPC fit will not take as long because segments already
validated are excluded from the process
55.3.4 RPC Results

RPC Results will display a report listing the results of the RPC fit. Additionally, several files
associated with the creation of the accuracy text files will be created and stored in the project
dppdb directory.
The RPC results report contains valuable data about the accuracy of your DPPDB product.
55.4 Create Image Segments

Create Image Segments is used to chip out the individual DPPDB image segments from the source
imagery. The option to create assessment segments is available as a time-saving step. Assessment
segments are created at an RRDS level so that radiometric balancing and segment editing may be
performed without having to work with the 1:1 segment.
Assessment segment creation is invoked by selecting Products > DPPDB Generation > Create
Image Segments > Create Assessment Segments.
The final DPPDB image segments are created by selecting Products > DPPDB Generation >
Create Image Segments > Create DPPDB Product Segments. These segments are rectified,
remapped to 8 bits (if necessary), and JPEG compressed to meet the DPPDB specification. In
addition, any enhancements applied to the assessment segments will be automatically applied to
the final segments.

55.4.1 Create Assessment Segments
The Create Assessment window’s selections are as follows:

Help Accesses the online help
Source Type Select either “All Segments” or “Rejected Segments”, depending on the
situation.
SELECT TO
RRDS Level Change the starting minification level of the assessment segments. R3 or
8:1 would mean that the base size of the assessment image will be 1/8th the
size of the original image.
Location Select the image location of the project.
Review Request Verify the number of images in the request and that sufficient disk space is
available.
55.4.2 Apply Enhancements

Enhancements are made using the DRA adjustments from the RT display. The left and right
images in a DPPDB segment should be very similar in tonal balance to improve the quality of the
stereo display. Enhancements applied to assessment segments will be applied to the final DPPDB

image segments. See the chapter on Brightness and Contrast Adjustment for detailed instructions
on adjusting the DRA for images.
55.4.3 Create DPPDB Product Segments
The Create DPPDB Product Segments selections are as follows:
SELECT TO
Location Select the image location of the project.

Review Request Display a list of all of the segments created during segment generation.
Done Closes the window.
The Review Request Window Selections are as follows:
SELECT TO
Submit Selected Submit only the segments highlighted in the e Review/Request window.
This option allows you to stagger the image orders through the batch
scheduler in order to maximize the processing power of the network.
Submit All Submits all of the segments as a single order.
Done Exits the application.
55.4.4 Segment Status

The Segment Status window, shown below, allows you to track the status of DPPDB segment
orders.

SELECT TO
Image List Select the image list associated with the segment order to be tracked. This
will cause the segment table to be updated.
Update Time Modify the time in which the software polls status of the segment order.
Update Update the segment table with the latest segment status.
55.5 Quality Assurance

This is obtained by selecting Products > DPPDB Generation > Quality Assurance.
Quality Assurance is a verification process designed to help prevent flaws in the product. The
cartographer can see which segments have been ordered, who ordered the segments, and then
annotate whether a segment meets quality standards.
SELECT TO
Status Display the status window.

Tracking Display the tracking window
Visual Review Display the Visual Review window. You can accept or reject a segment in
this window by right clicking on the review options for a segment.

SELECT TO
Comments Add comments about a segment. These comments are not included in the
product, but they can provide insight to another cartographer as to why you
rejected or accepted a particular segment.
Report Display a printable status of the state of the job. All of the information
provided in the Quality Assurance window will be included.
Load Load the Full resolution or Overview segment to the RT display. If stereo
is not available, then use split screen to review the imagery.
The Quality Assurance window consists of three “tabs”: Status, Tracking, and Visual Review.
55.5.1 Quality Assurance - Status

The Status tab provides information on the processing state of each segment.

55.5.2 Quality Assurance - Tracking

The tracking tab will identify the cartographer who created the segment and provide information
on the date and time the segment was processed.
55.5.3 Quality Assurance - Visual Review

The visual review tab allows the cartographer to annotate whether or not a segment has met the
criteria for a valid segment based on the Quality Assurance categories listed on the tab. By right
clicking over a category for a segment, the cartographer can validate or reject a segment. Rejected
segments are stored in a separate image list that can be used to reorder the segments.

REJECT TO
DRA Identify segments with problems in the tonal balance.

JPEG Blocking Identify segments that have problems during JPEG compression. JPEG
blocking can be identified by noticing groups of pixels that stand out from
the others. The outline of each pixel will be noticeable to the naked eye.
Y-Parallax Identify segments that have Y-Parallax. When displaying the segment in
stereo, the cursors should line up directly on top of one another when the
cursor is placed on the ground.

55.6 Feature Extraction
55.6.1 Create Adverse Areas

SOCET SET Feature Extraction is used to identify adverse areas in the project. The cloud covered
class is used to identify areas obscured by clouds and are drawn just as any other feature using
Feature Extraction. Feature attributes must be associated with each feature to be included in the
master product file. See “Feature Extraction,” Chapter 42 for details.
The Create Adverse Areas window’s selections are as follows:
SELECT TO
Class: Parent Cloud Covered Draw cloud polygons for an image. The Rectangle ID and Image ID must
be associated with the feature for it to be included in the product.
55.6.2 Create Void Areas

SOCET SET Feature Extraction is used to identify void areas in the product. Area without image
coverage is used to identify areas of the product that require image coverage, but are void because
of excessive water or image defects. To draw a void area, delineate a polygon around the open
area of the product extending out to the 1000ft border around the TAA. Be sure to associate the
Rectangle ID with the feature when you are down so that it can be included in the product. See
“Feature Extraction,” Chapter 42 for details.
The Create Void Areas window’s selections are as follows:
SELECT TO
Class: Area without image Draw a void area using Feature Extraction. The Rectangle ID must be
coverage associated with the feature for it to be included in the product.
55.7 Generation
This is obtained by selecting Products > DPPDB Generation > Generation DPPDB.
55.7.1 Review/Edit Metadata

DPPDB metadata contains valuable security and producer information that is necessary for all
DPPDB products. The default values for these fields can be customized for each site and are
contained in the DPPDB.mdt file located in the internal_dbs directory.
The Review/Edit Metadata window’s selections are as follows:
CATEGORY DESCRIPTION
File Version Always NITF2.00 as required by the specification.

Compliance Level Automatically calculated by the software based on the input images used
for the product.

CATEGORY DESCRIPTION
Classification This field sets the classification of the product in the metadata.
Downgrade Instructions Always set to 999999 as required by the specification.
Class Authority Identifies the Classification Authority based on the input to the product.
Control Number This is a reserved field usually left blank.
Release Instructions EG or NF are the only two options for this field.
Handling Instructions Occasionally special handling instructions are required for a product.
However, in most cases this field is left blank.
Stock Number The Stock Number is assigned by the customer. This field must contain 8
alphanumeric characters.
Edition Number The version of the product (3 numeric characters).
Country Code Two letter digraph of the country the product is produced over.
Item Number This field is automatically populated by the software based on the
coordinates of the product.
Producer Name The name of the organization producing the product
Producer Code The code of the organization producing the product.
55.7.2 Review/Edit Text Files

Nine Text files are included into the DPPDB product. The text files are comprised of either
canned data included in every product or valid segment data derived from the RPC fit or the
adverse area file created earlier in the job flow.
The Review/Edit Text Files window’s selections are as follows:
Review The review option allows the cartographer to review the canned or derived
data produced for each text file.

Review/Edit The review/edit section allows the cartographer the ability to add or review
comments made on a particular text file.
55.7.3 Review CADRG

The Review CADRG tab provides a sanity check for reviewing the source of the reference graphic
imported for the product.
The Review CADRG window’s selections are as follows:
SELECT TO
CADRG Staging Location Direct the software to the location of the CADRG Staging Directory.
55.7.4 Generate DPPDB

The DPPDB product is made up of a Master Product File, NITF image files, and a set of reference
graphics. All of this data is stored within both the project and image location and must be
assembled and blocked before it can be written to media. The Master Product File contains
metadata information about the product and contains the nine text files that provide exploitation
systems the information needed to process a DPPDB. NITF image files are the DRA adjusted
images that have been rectified and compressed. The reference graphics are color CADRG
reference images that are used by exploitation systems to project product footprints and adverse
areas in the form of CGM graphics. All of this data is assembled during the Generate DPPDB
process.
The Generate DPPDB window’s selections are as follows:
SELECT TO
Generate (DVD) Generate the DPPDB product in a format suitable for DVD. SOCET SET
does not provide a DVD burning software suite. A third party burning
package must be used to create a DVD.
Generate (Tape) Generate the DPPDB product with a 32K blocking factor suitable for
output to an 8mm tape.
Hardcopy Manifest Create a hardcopy manifest file with summary data for the product. This
file is stored in the project archive directory.

55.8 DPPDB Update

This is obtained by selecting Products > DPPDB Update.
The DPPDB Update flow is used strictly for updating metadata information on a previously
produced product. Image defects cannot be repaired in this job flow. Three easy steps are all that
required for to Update a DPPDB.
1. Job Setup
2. Import DPPDB
3. Generate DPPDB
55.8.1 Job Setup

Job Setup will create a SOCET SET project and automatically import JNC/GNC reference
graphics and available WMED data into the project if available. A SOCET SET project is
required to support the DPPDB Update flow.
55.8.2 Import DPPDB

Import DPPDB removes all of the files from a tape or DVD and stages them into the project
exactly as they would be if you generated the product on SOCET SET. Since source imagery is
not included on a product, segments cannot be regenerated or changed.
The Import DPPDB window’s selections are as follows:
SELECT TO
Input Filter to the location of the product to be input.

DVD Identify that the imported DPPDB is on DVD.
Tape Identify that the imported DPPDB in on Tape.
Location Identify the image location for the project.
Start Begin the import

55.8.3 Generate DPPDB

The DPPDB Generate process for an update is identical to the generation of an original DPPDB
product on SOCET SET. Fix any metadata that may have been in error, add one to the edition
number, and then regenerate the new product.

Chapter 56
Geopositioning
Measure specific locations over large-scale compressed
images.
56.1 Overview
Geopositioning is an organized job flow used for measuring specific locations over large-scale
compressed TFRD images. The process allows the cartographer to chip imagery from several
different areas of interest and use MST to measure points on the chips. Once the measurements
are complete, the cartographer redirects the measurements back to the original support files from
the larger images and produces a solution. This process saves decompression time and/or storage
space required by the larger images yet still allows the customer to produce a valid solution over
a given area.
56.1.1 Job Flow

The geopositioning job flow can be found under Products > Geopositioning from the SOCET
SET main menu display. The flow is designed to step through the process in an organized manner.
Each step is logically laid out on the menu so the customer can easily transition through the job.
56.1.2 Job Planning

The job planning phase of the geopositioning production flow initiates the job and gathers the
needed files and support data for geopositioning. The steps in the job planning area should be
followed sequentially because of the dependencies in the job flow. Images should be named
correctly before support data is imported, support files are required to import the imagery, and
both the imagery and footprints are required to drop points in feature extraction. Select Products
> Geopositioning > Job Planning.
56.1.2.1 Review/Edit Image Location

A new image location is required for each project used in geopositioning production.
SOCET SET Page 56-1

Chapter 56 - Geopositioning
A SOCET SET image location with sufficient disk space is required prior to creating a
geopositioning production job.
56.1.2.2 Job Setup

Job setup is required for all geopositioning production jobs. All geopositioning
projects are created as geographic ellipsoid with a product specific directory structure
unique to geopositioning. An 11 character project name is required in job setup to
assist in the tracking process throughout the job flow.
Job setup will create a SOCET SET project and automatically import JNC/GNC
reference graphics and WMED data into the project if available. Environment
variable CADRG_-TOP will need to be set in the socet_config file to point to the
appropriate storage location for these files. Access job setup by selecting Products >
Geopositioning > Job Planning > Job Setup.
Page 56-2 SOCET SET


The job startup window’s selections are as follows:
SELECT TO
Project Name 11 character project ID.

Image Location Location of the project image data.
Triangulation Northwest corner of the rectangle. This data can be pulled out of the
Rectangle Area USMSD file.
Northeast X/Y
Southwest X/Y Southwest corner of the rectangle.
Start Creates project files and imports WMED and CADRG reference graphics
if available.
56.1.2.3 Edit TRA

After completing Job Setup, if you wish to modify the triangulation area, the Edit TRA window
can be used. This window allows input of new triangulation coordinates, and creates new
CADRG and WMED over the modified area of interest.
SELECT TO
Lat (Y), Lon (X) Select new TRA coordinates.

Save Save the modified TRA coordinates. This will also create a new TAA,
import new CADRG, and import new WMED over the modified TRA.
Close Close the Edit TRA window.
SOCET SET Page 56-3

56.1.2.4 Rename TFRD Images

Rename TFRD Images simply copies images with a base name format into the FPE image name
format required for TFRD decompression.
56.1.2.5 Import Support Data

Import support data converts support data (AMSD(0), USMSD(0), MSD(i), RMSD(i), IDF,
AMSD(1) or USMSD(1)) into SOCET SET support files for a selected project. A copy of the file
is retained and stored in the project directory for use by other applications later in the job flow.
MSD(i) and RMSD(i) imports require the use of an image list.
The Import Support Data window’s selections are as follows:

Options > Set Control Selecting this option will turn off parameter adjustment for the imported
support data. This allows the imported support data, and its associated
imagery, to be used for control purposes.
Options > Change Settings Selecting this option will let you change the behavior of the import.
File Typically support files, image/model lists, and rectangle data are generated
from the import. Changing the settings file will allow you to limit this to
just an image list if you so desire.
SELECT TO
Input File File selection window that enables you to browse to the storage location of
the support data and select the file.
Page 56-4 SOCET SET

SELECT TO
Start Imports the support data into the project and creates .sup files for each
image in the support data. Image lists and a blank adverse area FDB file
are also created. The original support data is copied into the
dps_input_files directory for use in RPC Generation.
56.1.2.6 Import Assessment Imagery

The cartographer uses assessment images to drop points using feature extraction in preparation
for measuring points with APM. The images are displayed in stereo and used in conjunction with
the model footprint graphic overlay to provide a template for the creation of a feature database
(FDB). The FDB is used to chip patches in the bulk patch import and automatically generate ATF
files suitable for use in APM. Images can be ordered at a number of RRDS levels, however we
recommend R3 or R4 to save space and still meet the needs of the process.
SOCET SET Page 56-5

The Import Assessment Imagery window’s selections are as follows:

SELECT TO
Image Source Select the type of input for the request. An image list is the most
commonly used image source. However, selecting an individual image is
an option and can come in handy if only one or two images are required.
Images Provides a visual reference for the images to be imported.
MBR Setup Allows the cartographer a graphical interface to chip the images included
in the list over a geographic area.
Image Retrieval Setup Specifies the starting minification level of the imported images and
provides access to the image location for the specified project.
Review Request Provides sizing information on the images requested.
Submit Request Invokes the batch scheduler gui to begin image processing.
TFRD Imagery for Geopositioning production in SOCET SET is assumed to be in the compressed
image format, prefixed with `R0_," and the project name appended to the end of the image name
and before the.cmp extension. The imagery must reside in the project image location for the order
to be successful (e.g. R0_ImageName_project.cmp). Unclassified imagery must retain the
original image name as it is stored in the accompanying USMSD(1).
56.1.2.7 Review/Edit Footprints

Review/edit footprints provides a graphical interface that allows a cartographer to visually review
and manipulate image and model footprints in the project. This application provides a variety of
functions that can be utilized by during the job flow. An image list, created upon import of the
support file, is required.
Page 56-6 SOCET SET

The Review/Edit Footprint window’s selections are as follows:
SELECT TO
Strategy File default.strat is sufficient. This file determines the default settings for
options in recreate model footprints.
Graphics Attributes File Currently Defaults.lwugra is used. This file can be adapted to change the
thickness or color of the lines.
SOCET SET Page 56-7

SELECT TO
Graphics Toggles the Draw in RT function on/off

Footprint Type Change the desired application to invoke via Review/Edit
Review/Edit Access the individual footprint applications
TOGGLE TO
Draw Graphics Enable automatic graphic updates to the RT Display. Toggle this off if you
need to use another graphics application such as ATE.
Graphics Selection Enable the sketch graphics interface between Review/Edit footprint
applications and RT.
Adverse Area Display adverse areas and void areas created for the DPPDB product.
Apply Filters Filter the display of adverse areas on Parent and Retask images.
Task MBR Draw the Task MBR footprint once it has been invoked from the Review/
Edit Footprint type. Use the Footprint Fill to color the inside of the
Image Footprints Draw the Image footprints once it has been invoked from the Review/Edit
Model Footprints Draw the Model footprints once it has been invoked from the Review/Edit
Segment Footprints Draw DPPDB Segment footprints once it has been invoked from the
Review/Edit Footprint type. Use the Footprint Fill to color the inside of the
Footprint Fill Shades in a selected feature
IDs Displays the name of a selected feature.
56.1.3 FDB to GPF Import/Export

FDB to GPF Import/Export allows a Ground Point File to be imported into a Feature Database,
or a Feature Database to be exported to a Ground Point File. It uses the “fpe_fdb.spc”
specification file to define ground point types that are used in the Feature Database.
Start this window by selecting Products > Geopositioning > Tie Point Planning > FDB to GPF
Import/Export.
Page 56-8 SOCET SET

The FDB to GPF Import/Export window’s selections are as follows:

SELECT TO
Feature Database Select an existing Feature Database when you are exporting a Feature
Database to a Ground Point File, or specify a name for a new Feature
Database when you are importing a Ground Point File to a Feature
Database File.
Ground Point File Select an existing Ground Point File when you are importing a Ground
Point File to a Feature Database, or specify a name for a new Ground Point
File if you are exporting a Feature Database to a Ground Point File
Conversion Type Select which type of conversion you want to do, either importing a Ground
Point File to a Feature Database, or exporting a Feature Database to a
Ground Point File
Start Start the specified conversion
56.1.4 Review/Edit Mensuration Plan

The Review/edit mensuration plan uses feature extraction to create a FDB file. The FDB file is
built for the purpose of generating a ground point file used for both generating patches and as
input to APM. Points are categorized by their function and have specific naming conventions that
SOCET SET Page 56-9

are used by 3rd party triangulation packages. The FPE_FDB.spc file contains all of the valid point
types for geopositioning and should always be used in this job flow.
The Feature Extraction window’s selections are as follows:
File > Open FDB... Prompt you to select a feature database to open. To create a new database,
you enter the new name in the Selection field.
File > Save FDB Saves changes to the currently open feature database.
File > Save FDB As Saves the currently open feature database to a new different feature
database with the same specification.
File > Reference Databases Displays the Select Reference Databases window. You use this window to
manage reference databases. You can add or remove reference databases.
You can enable or disable classes within a reference database. You can
toggle the ability to draw a reference database. You can toggle the ability
to snap to a reference database. You can toggle the ability to draw a
reference database using specified class colors, and you can select a solid
color for display of a reference databases. The Draw, Snap, and Spec
Colors toggles and the Solid Color button will affect all selected reference
databases.
File > Exit Exits Feature Extraction. This button is only valid during the REVIEW
mode. You must cancel any editing or creating operations before you can
exit.
Tools > Mensurate Displays the Mensuration window. You use this window to create detailed
measurements of a feature, relative to reference points you specify.
Tools > Volume Create For generating volumetric polyhedron features from polygon features. The
feature list file must have polygon entries. The output class must be
polyhedron. See “Volume Create” on page 42-22.
Tools > Texture Patch Opens Texture Patch window. See “Creating a Texture Patch” on page 42-
26 for a detailed description of this capability.

Tools > Model Placement Displays the Model Placement window. Use this tool to place multiple 3D
generic features into the feature database.
Tools > Auto Attribute Used to automatically calculate and populate the set of reserved
dimensional feature attributes (area, length, width, height, elevation, angle
of orientation, ACE, ALE, ZV2, ZV7, Z7F, Z5M, Z5F) upon feature
accept. Select Enable to activate this mode. All reserved dimensional
attributes (except for Angle of Orientation) will then be automatically
computed. The current feature class must have these reserved dimensional
attributes. Select Populate AOO to allow population of the Angle of
Orientation dimensional attribute. A second mouse click will be required
to calculate the AOO of a point feature. Select Manually Measure HGT/
Zxx to measure an additional point to populate the HGT and all Z auto-
attributes. This works for polygon buildings that must be collected at
ground level, but need the elevation automatically calculated. After
collecting the building perimeter, sample one more vertex at the highest
point on the roof. This point will be used for the attribute calculations and
not be included in the completed feature.
Tools > Simultaneous Allows you to delineate more than one features simultaneously.
Collection
Generics > Load Generic Load the generic feature database
FDB
Generics > List Generic You use this to copy complex three-dimensional generic features (such as
Features spheres, cars, tanks, etc.) into the feature database.
Generics > Add to Generic Places a feature into the generic feature database for later use.
FDB
Options > Preferences Displays the preference window.
Options > Customize Displays the customize window.
56.1.5 Import Patches

Importing patches is done to help alleviate the strain of having to decompress and store large
TFRD images on the system. The most common is the import bulk patch. This option will
decompress image chips around every ground point in the selected file. FDB files are also used
as input, but are converted to ground point files during the process. The other method is the Adhoc
ad hoc request. Individual points can be dropped on the fly and then manually added to an existing
ATF file. Select from Products > Geopositioning > Import Patches.
56.1.5.1 Import Bulk Patches

The Import Bulk Patch window uses a feature database file or ground point file as a point of
reference for chipping patches from a source image. Points are used as a central chipping location
and the size can be adjusted in meters around the point in both an East to West or North to South
direction.


SELECT TO
Select Patch Locations By > Uses a FDB file as seed points for chipping patches. The FPE_FDB.spc
Feature Database should be used when creating the FDB file in feature extraction.
Select Patch Locations By > A SOCET SET ground point file (.gpf) can also be used to create patches.
Ground Point File
Triangulation Setup > Determines the number of ATF files that will be created during the patch
Number of Automatic import.
Triangulation Files
Minimum Patch Size > E-W Adjust the size of the patch in the East to West direction.
Minimum Patch Size > N-S Adjust the size of the patch in the North to South direction.
Enable Patch Graphics Draws the requested patch footprints in the viewport once Review Request
is selected. This option can slow performance if a large number of patches
are being requested.

SELECT TO
Review Request Displays a list of the requested patches based on the images that cover the
points in the FDB or GPF file. Individual patches may be deleted or
resized.
56.1.5.2 Ad Hoc Patch Import

The ad hoc patch import allows the cartographer to drop individual points for chipping and
include them in a ground point file. MST can then be used to add the new image chips to an
existing ATF file using the add image option from the MST Setup window. APM is then run again
to add the new points into the solution.


SELECT TO
Image Source An image list generated from the import support data application or
individual images may be selected. The images selected must cover the
area where points will be placed.
Elevation Source High quality DTED is recommended to ensure proper overlap of the
requested patches.
Other elevation sources may be used, but care must be taken to accurately
place the point on the ground. The size of the patches may also need to be
increased in high elevation areas.
Selected Location > Select Used to select a ground point from the image loaded in the viewport.
Position
When selected, toggle to the mensuration cursor in the viewport and use
the left mouse button to retrieve the desired ground point.
Note: Ensure the point is on the ground by using terrain tracking with
accurate DTED or by visually verifying the location in a stereo display.
Ground Point Setup > Add Adds the selected point to the ground point file.
Ground Point
Ground Point Setup > Identifies the ground point file to add the selected points.
Ground Point File
Points may be added to a new ground point file or an existing ground point
file.
Ground Point Setup > Point Point type naming convention used in the solution.
ID Prefix
Note: SOCET SET treats most point types as standard tie points, but some
3rd party triangulation packages use specific naming conventions to parse
points in the solution.
Ground Point Setup > ID Prefix appended to the tie point name
Prefix
Ground Point Setup > Point Standard SOCET SET point type. See MST section for details.
Type
Minimum Patch Size > E-W Adjust the size of the patch in the East to West direction
Minimum Patch Size > N-S Adjust the size of the patch in the North to South direction.
Patch Retrieval Setup > Image Location of the project
Location
Patch Retrieval Setup > Add Includes the selected point in the patch request and allows a new point to
be selected.
Multiple points can be added to a single request.

SELECT TO
Patch Retrieval Setup > Exits the request without saving the accumulated points.
Cancel
Patch Retrieval Setup > Displays a list of the requested patches based on the images that cover the
Review Request points in the FDB or GPF file. Individual patches may be deleted or
resized.
56.1.5.3 Patch Status

The Patch Status window is used to track the status of Bulk or Ad Hoc patch orders. It allows you
to select an ATF file, created by the patch order. Once the ATF file is selected, the status of each
patch in the ATF file is displayed on the window.
SELECT TO
ATF File Select an ATF file created by the patch order. After selecting the ATF file,
it will be read and the number of patches and their associated status will be
displayed on the window.
Update Update the status of the patch order.

SELECT TO
File > Exit Exit the window.
56.1.5.4 ATF Merge/Split

The ATF Merge/Split window is used in conjunction with the import bulk patches. ATF files
generated from the patch import may contain large numbers of points and using the split function
can help the cartographer manage the triangulation over a large area. The merge capability is
necessary to redirect the measured points on the patches back into the original support files before
the final solution is run.


SELECT TO
Merge > Available Displays ATF files stored in the project location.
Merge > Selected Builds the list of ATF files to be merged.
Note: Only measured ATF files with patches should be merged.

Output ATE >Triangulation The name of the single ATF file that will be created during the merge.
ATF
Measurements done on the patches will now be included in the .ipf and
.gpf of the single file and point to the original source image.
Start Merges the selected ATF files into one ATF file.
Split > ATF The ATF file to be split.
Note: An ATF file should have at least 10 points to run split.

Split > Number of ATFs The number of ATF files to generate from the selected file.
Split > Split Splits the selected ATF file into the desired number of ATF files.
Split > Delete Deletes the currently selected ATF file.
56.1.6 Multi-Sensor Triangulation

For information regarding multi-sensor triangulation, See “Overview” on page 25-1describing
MST overview and workflow, See “Overview” on page 26-1 describing MST setup and GPS, See
“Overview” on page 27-1 describing MST point measurement, and See “Overview” on page 28-
1 describing MST solve.
56.1.7 Generate SPC

Generate SPC generates a *.spc file and creates an unblocked AMSD file from a blocked AMSD
file. These files are both required as inputs to perform triangulation using the external GDAT
software tool.
Start this window by selecting Products > Geopositioning > Generate SPC.

The Generate SPC window’s selections are as follows:

SELECT TO
ATF File Select a *.atf file

GPF File Select a *.gpf (ground point file)
AMSD File Select an AMSD file
Rectangle ID Type in the Rectangle ID
Start Start generation of *.spc and unblocked AMSD files

Chapter 57
Export to Rendering Systems

Export to Rendering Systems covers rendering system exports
from SOCET SET.
57.1 Overview
SOCET SET performs conversions for several rendering systems. The rendering systems are
listed below, but are described in more detail in the following paragraphs.
• OpenFlight
57.2 OpenFlight
SOCET SET terrain and feature datasets can be exported for use in many commercial real-time
visual simulation applications by using the OpenFlight Output capability.
57.2.1 OpenFlight
OpenFlight is available only on Windows platforms.
OpenFlight is an industry standard, real-time 3D scene description format developed by

MultiGen, Inc. It was developed in response to a need for database transportability within the
visual simulation community. OpenFlight is the most widely used file format for visual
simulation databases and is supported by dozens of vendors of real-time 3D tools. In visual
simulation, OpenFlight is the defacto standard format. MultiGen OpenFlight databases run on
multiple systems including: Silicon Graphics, Evans & Sutherland, CAE, FlightSafety, REAL
3D, Sony, Nintendo, Sega, Macintosh, PCs, and other popular real-time 3D platforms.
The MultiGen OpenFlight database format supports both simple and relatively sophisticated real-
time software applications. OpenFlight supports multiple levels of detail, degrees of freedom,
sound, instancing—both within a file and to external files—replication, animation sequences,
bounding volumes for real-time culling, scene lighting features, light points and light point
strings, transparency, texture mapping, material properties, and other features.
57.2.2 When to use OpenFlight
SOCET SET Page 57-1

Chapter 57 - Export to Rendering Systems
OpenFlight Output exports data files from the SOCET SET format to the MultiGen OpenFlight
format. You run OpenFlight after you have created a SOCET SET project, imported terrain
(DTM) imagery, and extracted feature data.
You control OpenFlight by interacting with the following set of windows:
• SOCET SET to OpenFlight
• File Selection Widgets
• Area of Process
• Output Options
57.2.3 Summary
OpenFlight Output exports SOCET SET database files in the MultiGen OpenFlight format. The
SOCET SET database files can be any combination of feature data, terrain data, or image data.
OpenFlight works on all project coordinate systems. The exports of geographic projects will be
in Scaled Relative Geographic coordinates. This system allows latitude and longitude to be
outputted as values that are in approximate project units from an arbitrary coordinate origin
selected at the time the project was created. The formula for SRG coordinates is:
SRG_X = (lat - GP_ORIGIN_X) * GP_SCALE_X
SRG_Y = (long - GP_ORIGIN_Y) * GP_SCALE_Y
where “lat” and “long” are the latitude and longitude coordinates of the input point, SRG_X and
SRG_Y are the values found in the exported file, and the other values are found in the project file
(.prj).
OpenFlight may have limitations on the size of image files they can display. OpenFlight Output
allows you to specify the image patch size to produce for both terrain and feature data.
OpenFlight Output gives you control over export parameters including:
• The path and filename for the export data set.
• The area of the database files to export.
• Whether or not to include terrain and/or features from the SOCET SET database in
the export database.
• Output level of detail when processing the feature or terrain data.
• Format of image files to produce as export (currently SGI, Sun raster, and TIFF
formats are supported).
To run OpenFlight Output, you must select the input files including the project, feature database,
DTM, and image files.
Page 57-2 SOCET SET

57.2.4 OpenFlight
The OpenFlight Output window’s selections are as follows:
File > Load Project Identify the name of the software project where the data to be output
resides. If the workstation is running, by default this is the name of the
project that is currently loaded on the workstation. In this case the
selection is desensitized, and the project should be loaded/changed using
the workstation.
File > Open Setup Files Selects an existing setup configuration file, (*.ofc).
File > Save Setup File Saves the configuration file containing setup parameters.
File > Save Setup File As Prompts you to pick or type in the filename to be used for writing the
current configuration.
File > Exit Exit application.
Utilities > Import Imports OpenFlight generic point features to the Generic Feature Database
OpenFlight Point Features (FDB). You use Feature Extraction to insert features from the Generic FDB
into the scene FDB.
SELECT TO
Output Path Enter a fully qualified path and name of the output database file. This path
is used for storing output files produced by OpenFlight Output.
DTM Identify the name of the terrain file to use.
Feature Database Identify the name of the feature database to use. The selected feature
database must have been created with an AFX feature extraction
specification file.
SOCET SET Page 57-3

SELECT TO
Image for DTM... Identify the name of the image to use for texture for the terrain. Typically
an orthophoto, although orthophoto is not required. If no image is selected
the terrain will be gray colored polygons with no texture.
Images for Features: Displays the image files that are used to produce texture image files.
Area To Process Invoke the Area To Process window.
Output Options Invoke the Output Options window.
Start Begin the OpenFlight database creation process.
57.2.5 Area To Process

The Area To Process window’s selections are as follows:
SELECT TO
Center X Display the fields that are used when the height and width fields are non-
Center Y zero. They give the coordinates of the point in the center of the area
selected for output. They are type-in fields, whose value is also updated
when using the Sketch tool to select the output area.
Height/Width Define these values. The height and width are in project units of the area to
output. If these fields are both zero, the entire DTM will be output and all
features will be included. They are type-in fields, whose value is also
updated when using the Sketch tool to select the output area.
Use Cursor To Select Area Instruct the OpenFlight Output application to get bounding box dimensions
from the Sketch tool (See “Edit Mode” on page 58-6). After clicking this
button, use F3 to obtain the Sketch cursor. Use the LMB to select the four
corners of the bounding box, and use the RMB to accept the bounding box.
If desired, the bounding box may be redrawn. The last accepted bounding
box is the one that will be used to define the output area.
OK Close the Area to Process window.
Cancel Closes the window without and action.
Page 57-4 SOCET SET

57.2.6 Output Options

The Output Options window’s selections are as follows:
SELECT TO
Terrain BLANK SPACE

Output DTM? Direct OpenFlight Output to include or not include terrain data in the
BLANK SPACE output database.
Sub-image size Request a size for the output image files produced for the terrain data.
BLANK SPACE Output files will be rectangular, sized on powers of 2.
Level of detail Enables the use of detailed and 4:1 textures for OpenFlight Output.
SOCET SET Page 57-5

SELECT TO
Feature BLANK SPACE

Output Features? Direct OpenFlight Output to include or not include feature data in the
BLANK SPACE output database.
Sub-image size Allow you to request a size for the output image files produced for the
BLANK SPACE feature data. Output files will be rectangular, sized on powers of 2.
One feature per file Allow you to request that each feature be exported as a separate
OpenFlight file. A master feature OpenFlight file that contains external
BLANK SPACE references to the individual OpenFlight file will also be exported. The
BLANK SPACE origin (0,0) of the individual OpenFlight files will be the bottom/center of
BLANK SPACE the feature’s geometry while the origin (0,0) of the master feature
BLANK SPACE OpenFlight file will be the lower left corner of the input DTM.
BLANK SPACE NOTE: This option is only used for OpenFlight Output.
BLANK SPACE Draw the backface of the polygon, if Yes is selected. If No, the backface of
BLANK SPACE the polygon is not drawn resulting in lower polygonal load for rendering.
Draw Backface BLANK SPACE
BLANK SPACE Set bottom facets (if available) as footprints, if Yes is selected.
Footprint Polygon Set the number of LODs for the features. Only texture resolution is
BLANK SPACE changed between LODs. The geometry of features is not changed.
Level of detail Request an image min-level for the 1st LOD. Subsequent LODs will have
lower resolution. For example if Image Min-Level 2:1 is selected, then
BLANK SPACE LOD #1 will contain 2:1 imagery, LOD #2 will contain 4:1 imagery, and
BLANK SPACE LOD #3 will contain 8:1 imagery.
BLANK SPACE
BLANK SPACE
Image Min-Level
Sub-image type Specify which image file format will be used to produce output image
files. Currently supported formats are: SGI, Sun raster, and TIFF.
OK Close the Output Options window.
Cancel Close the window without any action.
57.2.7 Output
Upon completion of OpenFlight Output the output directory will contain the following:
a. Main OpenFlight file
b. Main terrain OpenFlight file
c. Individual terrain OpenFlight files
d. A directory containing all of the images for the terrain.
e. Main feature OpenFlight file
f. A directory containing all of the images for the building features
g. Individual generic feature OpenFlight files
h. A directory for each generic feature type. Each of these directories will contain the
images for that specific generic feature.
i. If the “One feature per file” option was selected then the output directory will also
contain a OpenFlight file for each feature outputted.
Page 57-6 SOCET SET

j. If the “One feature per file” option was selected then the output directory will also
contain an index file that holds the location, scale, and rotation of all of the features
and generic features outputted.
k. If the “One feature per file” option was selected then the output directory will also
contain a point Shapefile (.shp, .shx, and .dbf). This Shapefile will contain points that
correspond to the location of the origin of the individual feature OpenFlight files.
l. If the “One feature per file” option was selected then the output directory will also
contain a footprint Shapefile named <FDB name>_fp (.shp, .shx, and .dbf). This
Shapefile will include building footprints as identified in the feature database.To
identify a footprint polygon in FEI you can either use the auto-create functionality
with “bottom_facet” enabled. Or you can manually set the BOTTOM_FACET
element attribute of the polygon to TRUE.
57.2.7.1 Execution - OpenFlight

To select the input data files to include in the conversion, use the following set of steps:
1. Start up OpenFlight Output by clicking Output > Rendering Engines > OpenFlight on the
2. Click Output File on the OpenFlight Output window. From the file selection box, select or
enter the output path and filename. It is recommended that you select a new directory for
output, as a large number of files may be generated. The File Selection box will create the
new directory.
3. Click DTM on the OpenFlight Output window. The Select DTM window prompts you to
select a DTM. After making your selection, click OK. Selection of a DTM is required for
all output operations.
4. If you wish to select a feature database, click Feature Database. Pick the name of a feature
database and click OK. The selected feature database must have been generated with the
AFX feature extraction specification file.
5. Click Image for DTM... on the OpenFlight Output window. The Select Image File window
prompts you to select an image file to be used for texturing the terrain. After making your
selection, click OK. Typically an orthophoto is used for the terrain. However an orthophoto
is not required. If no image is selected for the terrain, the terrain will have no texture and
will be gray shaded polygons in the OpenFlight format.
6. To select texture image files, click Add. An Image File Selection window appears. You can
pick more than one image file. The Select Image File window prompts you to select the
image files that are used to produce texture image files. All images are used for features.
Use the <Ctrl> LMB to select the images in the order required. To remove images files from
the list, select the file, then click Remove.
7. Click Output Options if you wish to adjust the output parameters: image patch size, level
of detail, image format, and feature & dtm output.
8. Click File > Save to save your selection.
9. Click Start. You will be notified when the OpenFlight Output application has completed.
57.2.7.2 Execution - Using Generic Features with OpenFlight

To import generic features:
1. Click Utilities > Import OpenFlight Point Features on the OpenFlight Export main menu.
2. Select OpenFlight files you wish to import from the Import OpenFlight Point Features
window.
3. Click OK. If the files are imported successfully, the message “Successfully Imported...”
will be displayed.
Make sure the filenames of the imported files are unique because the filename will become
the name of the generic feature. If you import an OpenFlight file that has the same name as
SOCET SET Page 57-7

an existing generic feature, then the existing generic feature will be replaced. The imported
generic features and their textures will be copied to your Internal_dbs/
GENERIC_DBS/openflight/ directory. Generic OpenFlight features cannot contain any
external references. These external references will not be imported along with the rest of
the generic feature.
To insert generic OpenFlight features into a scene feature database, follow the instructions
in the Features Extraction section of this manual for inserting generic features. The name
of the generic feature displayed in the FEI generic features list will be the name of the
generic feature OpenFlight file.
To export generic OpenFlight features follow the same procedure as outlined above. The
generic features and their textures will be copied to your output directory.
Page 57-8 SOCET SET

SOCET SET Page 57-9


Chapter 58
Sketch
Sketch provides vector, text and icon drawing and editing
capabilities for SOCET SET.
58.1 Overview
Sketch is a collection of drawing and editing tools designed for use within SOCET SET. Sketch
provides convenient drawing and editing capabilities to the various software modules including
Feature Extraction, Annotation, and Interactive Terrain Edit.
v5.0 Annotation uses the old sketch interface. The look of that
interface may be different but the functionality of the sketch
tools remains the same. In v5.0 Annotation, Sketch
preferences can be accessed with the preferences icon button
in the sketch toolbox.
58.1.1 Sketch Toolbar

Sketch consists of a set of three toolbars of icon logically organized.
• Navigation Toolbar
• Main Toolbar
• Additional Toolbar (Advanced Drawing Tools)
A picture of the Sketch toolbars is shown below. Each icon button represents a particular Sketch
functionality. The Main Toolbar consists of Collection (Draw), Edit, and Volumetric buttons
contain menu pop-ups that provides you select, edit, or create tools. The Navigation toolbar’s
makeup is that of direction arrows allowing you to move within the image. The Additional
Toolbar provides additional tools, that which are toggled either on/off.
The remaining icon buttons represent either toggles or actions. Sketch also provides tool tips for
user convenience.
SOCET SET Page 58-1

Chapter 58 - Sketch
Refer to Quick Reference Guide for a complete listing of Sketch Hot-keys.
Back to Feature Extraction Back to Annotation
58.1.2 Toolbox Tip

If the user settings file gets corrupted, it is possible that all of the toolbars will disappear from the
application GUI. To make the buttons visible again, use the “Customize Toolbars” dialog to add
the buttons back onto the GUI.
Page 58-2 SOCET SET

Chapter 58 - Sketch
58.2 Main Toolbar
58.2.1 Collection (Draw)

Sketch allows you to perform two main functions: Draw and Edit. If the sketch cursor preferences
are set to systems-defined cursor, the extraction cursor will look like this while in Draw mode.
To draw an object on the image display, you must:

1. Choose a Draw mode by clicking the Draw mode icon in the application toolbar
2. Press the LMB to digitize new vertices (unless Stream/A F E ).
3. Press the RMB to accept the new object.
4. If you are drawing a multi-element object and want to accept one element at a time, pressing
the RMB of step (3) will finish an element, and you should repeat steps (2) and (3) for each
element. When done with the final element, press RMB again (twice in a row) to finish the
full object. If you want to only press the RMB once to finish the entire feature, set the
Element Edit button (F/E) to “off”.
Some important tips to keep in mind when drawing are:
• You can cancel a current draw object process by pressing the Cancel Create button,
which is default mapped to the Escape button on the Keyboard. When you Cancel
Create, all new vertices that have not been accepted shall be erased from the display.
• You can press the Undo icon button to remove each previously digitized vertex, one
by one.
• You can use the Snap button, the MMB, to connect, or jump onto, to a pre-existing
object at any time during a draw process. The Snap behavior is determined by
several preference parameters. You can customize these parameters by pressing the
Preferences icon button in the Sketch toolbox, selecting Snap in the list, and making
the desired modifications.
58.2.1.1 Draw Tools

To draw a graphical object on the display, you must press any one of the mutually exclusive icon
buttons on the Draw or Volumetric mode popup menus. Some of the following Draw options have
associated preference parameters. You can customize these parameters by displaying the
application’s preference dialog, selecting the appropriate item in the list, and making the desired
modifications. The Draw and Volumetric icon buttons along with their behavioral descriptions
are provided in the following table.
SOCET SET Page 58-3

Chapter 58 - Sketch
The Sketch Toolbox window’s selections are as follows:
SELECT TO
Static Draw an object by sampling sequential vertices with the LMB. Each vertex
<Ctrl> F6 is connected to the previous vertex with straight line segments.
Curve Draw an object by sampling sequential vertices with the LMB. Each vertex
<Ctrl> F2 is connected to its adjacent vertices with a spined line segment passing
through each vertex.
Arc Draw an object by sampling three sequential vertices with the LMB. These
<Ctrl> F3 three points shall define a portion of a circle.
Stream Draw an object by moving the extraction cursor with the LMB held down.
<Ctrl> F4 The sampling frequency is based on the Sketch stream parameters. Each
vertex shall be connected to its adjacent vertices with straight line
segments.
On-the-fly square Draw an object by sampling sequential vertices with the LMB. The first
<Ctrl> F8 two vertices shall determine the baseline for the squaring algorithm. Each
subsequent vertex shall be connected to its adjacent vertices with two
perpendicular straight line segments.
Square after accept Draw an object by sampling sequential vertices with the LMB. Upon
<Ctrl> F9 feature accept, all the connecting segments shall be forced to be
perpendicular.
Rectangle Draw a rectangle by pressing the LMB, and dragging the cursor from one
<Ctrl> F5 corner to the diagonal corner. The rectangle is aligned in ground space, not
image space.
2-Point Rectangle Draw a temporary line that you want the rectangles to be parallel to. Start
collecting rectangles by sampling opposite corners. After sampling both
corners the feature will automatically be accepted. Right or double-click to
reset the temporary parallel line. A new parallel reference line can then be
drawn for subsequent rectangles to be oriented to.
3-Point Rectangle Extract three corners of a rectangle and the feature will be automatically
accepted.
3-Point Circle Draw a circle by selecting 3 points along the circle’s perimeter. The circle
is aligned in ground space, not image space.
Page 58-4 SOCET SET

Chapter 58 - Sketch
SELECT TO
AFE Rooftop In this Automatic Feature Extraction (AFE) Draw mode, you can use
<Ctrl> F10 computer vision techniques instead of precise delineation to fit a polygon
to the corners of a flat building rooftop with straight edges.See “AFE
Roof” on page 58-18.
Before accepting After accepting
AFE Lake In this Automatic Feature Extraction (AFE) Draw mode, you can use a
<Ctrl> F11 special region-growing algorithm to outline features of homogeneous gray-
level value. This algorithm comes in three flavors: high, medium and low
contrast, and is particularly effective for the extraction bodies of water
such as lakes. The currently active algorithm is determined by the Sketch
lake contrast parameter. This tool requires three points, two points outside
the feature which define two corners of a rectangle large enough to contain
the feature and one point inside the feature. You should use the LMB to
enter the required seed points, and the RMB to accept them. See “AFE
Lake” on page 58-18.
Lake
2
AFE Refine In this Automatic Feature Extraction (AFE) Draw mode, you can use a
<Ctrl> F12 special algorithm, or refine method, to outline any linear feature of
interest. There are a total of six possible refine methods. These methods
are named: same_num_pts, spline, spline_and_straight, arc_and_straight,
road_center, and edge follower. The currently active refine algorithm is
determined by the refine method parameter. The following are descriptions
of each method. See “AFE Refine” on page 58-18.
SOCET SET Page 58-5

Chapter 58 - Sketch
Image Input Delineation After Refinement
Create with Direction This mode allows you to rotate icons that are used in POINT geometries.
Extract the first point to define the origin of the icon. Extract the second
point to define the angle of rotation.
58.2.2 Edit Mode

Sketch allows you to perform two main functions: Draw and Edit. To edit graphical objects,
Sketch must be in Edit mode. If the sketch cursor preferences are set to systems-defined cursor,
the extraction cursor will look like this while in Edit mode:
To edit an object:
1. Choose an Edit tool by clicking an Edit mode icon button in the Sketch toolbox.
2. Follow the specific instructions (listed in the table below) for the particular edit.
3. Confirm the new object by pressing the LMB (unless confirm is automatic, such as in move/
rotate/scale).
Some important tips to keep in mind when editing are:
• To increase the speed of editing features in Sketch, turn off the Display Vertices toggle.
• You should set the snap dimension appropriately before editing.
• You can cancel a current edit or escape the current edit process by clicking Reset, which
is default mapped to the RMB.
• You can click Undo icon after the edit has been accepted to un-edit your new object.
• During an edit and before an edit is accepted or confirmed, the object may appear in a
temporary grey color. The object color will change back to the original color when
either the edit is confirmed or cancelled.
• Refer to Quick Reference Guide for a complete listing of Sketch Hot-keys.
Page 58-6 SOCET SET

Chapter 58 - Sketch
58.2.2.1 Edit Tools
SELECT TO
Select Select an object, place the cursor near the object and press and release the
<Ctrl> q LMB. The selected object drawn is the highlighted color.
< After you select an object, you can perform some post-creation edits on it,
including (a) Make Monotonic; (b) Force corners square; and (c) Thinning.
To do any of these, set the desired Sketch mode/preference, select the
feature, and press the RMB.
Move Vertex Move a vertex, place the cursor near a vertex, press the LMB, hold it down
<Ctrl> l and drag the vertex by moving the mouse. Release the LMB to position the
vertex to its new place.
Move Feature Move a feature, place the cursor over any part of the feature and press the
<Ctrl> f LMB. Hold the LMB down and drag the feature to move the entire feature,
when finished let go of the LMB to set the feature.
Delete Delete an object, place the cursor near the object and press the LMB. The
<Shift> F8 object color will change to edit color. You must press the LMB a second
time to confirm the delete. If you press the confirm LMB near another
object, the previous delete will be automatically confirmed and the nearest
object color will change to edit color. This behavior provides convenient
multiple delete capability. Press the RMB to reset this edit mode.
Pressing the LMB three times may delete two objects.
Copy Copy an object, first place the cursor near the object and press the LMB. A
<Ctrl> c temporary copy of the object will appear in an edit color attached to the
cursor. As you move the cursor, the copy shall follow. To place a
permanent object copy onto the display, you press the LMB a second time.
The copied object will be placed at the cursor location in the original color.
If you press the LMB again, another copy will be placed in the display.
This behavior provides convenient multiple copy capability. Press the
RMB to reset this edit mode.
Rotate Rotate an object, place the cursor near the object, press the LMB, hold it
<Ctrl> r down and rotate the object by moving the mouse. A coordinate axes
display shall appear positioned at the object centroid. The object shall
rotate around the ground Z axis, centered on the object’s center of gravity.
SOCET SET Page 58-7

Chapter 58 - Sketch
SELECT TO
Scale Scale an object. There are two ways to scale; check the scale preferences
<Ctrl> s for more information.
BLANK SPACE
1. About the centroid (SOCET Defined) - Place the cursor over
the object and hold the LMB. Move the mouse while holding
the LMB and the object will be scaled about the centroid.
Release the LMB and the object will stop scaling.
BLANK SPACE
2. About the anchor point (User Defined) - If the preferences are
set to User Defined, then the cursor will turn to red indicating
that the next click is for an anchor point. Place the cursor over
a point on the object and click the LMB. The cursor will move
to the nearest vertex from the point you clicked which will be
the anchor point. After the anchor point has been selected, the
cursor will turn to yellow indicating the need for a scale point.
Find a point on the object and hold the LMB while moving the
mouse. This will scale your object according to the anchor
point. Once you release the LMB, scaling will be done. The
process will repeat itself with the cursor turning back to red.
Delete Vertex Delete a vertex, place the cursor near the vertex and press the LMB. The
Delete vertex will be tentatively removed and the line color connecting two
adjacent vertices will change to edit color. You must press the LMB a
second time to confirm the vertex delete. If you press the confirm LMB
near another vertex, the previous delete will be automatically confirmed
and the nearest vertex will deleted as well.
Insert Vertex Insert a vertex into an existing object, move the cursor to the position
Insert where the new vertex will go; press and release the LMB; the vertex will
be inserted and object color will change to grey; move the new vertex to its
new location by moving the mouse; press and release the LMB a second
time to confirm the vertex insert. To snap the new vertex to an existing
vertex, move the cursor to the existing vertex and press the MMB.
Split Split a linear object, first place the cursor near the object and press the
<Ctrl> x LMB. The object will be tentatively split and object color will change to
edit color. You must press the LMB a second time to confirm the split. If
you press the confirm LMB near another object, the previous split will be
automatically confirmed and the nearest object will be split as well. This
behavior provides convenient multiple split capability. Press the RMB to
reset this edit mode. You can only split a linear object.
Redraw Redraw portions of a feature, insert multiple vertices, and extend line
<Ctrl> n segments. To redraw you must first press the MMB to snap to the feature.
This can be on any part of the feature. Next you must sample more points
for the redraw request using the LMB. You can also use the MMB to
sample a point on the same feature as well. For polygons you must end the
sample session with a MMB snap back to the polygon. For line types there
is no restriction. When done sampling, press the RMB to highlight the
portion of the feature that will be replaced. To confirm this, press the RMB
for the edit action to occur. If SOCET SET does not choose the highlighted
portion you want then press the Change Direction button to highlight the
other side of the feature. Note for line extensions, the initial MMB press
must be over the first or last vertex of the line. Continue sampling with the
LMB and when finished press the RMB. The cursor will snap back to the
vertex you snapped too. To confirm this extension press the RMB again.
BLANK SPACE
This tool supports Share Segment capability. See “Additional Toolbar” on
Page 58-8 SOCET SET

Chapter 58 - Sketch
SELECT TO
Stretch Stretch an object, the first thing to notice is the color change to red in the
cursor. This will indicate that the cursor is searching for an anchor point.
Place the cursor on a point near the feature with the LMB. This will move
the cursor to the nearest vertex on the feature. This will be your anchor
point. Once the anchor point is selected, the cursor turns to yellow
indicating a change from the anchor point to the stretch point. Now with
the LMB, find another point on that same feature and begin to stretch by
moving the mouse and holding the LMB. The process is finished once you
release your LMB. Once the LMB is released, the process repeats itself
with the cursor turning back to red.
Polygon Union Join two POLYGONS, first select both POLYGONS. Then press the LMB
to accept the union. If the results of the union are unacceptable, click the
undo button. The union tool only works with POLYGONS that have the
same class.
58.2.3 Volumetric Draw Tools

Remaining tools on the Main Toolbar.
SELECT TO
Conical Draw a cone or dome shaped feature. First select 3 points along the
<Alt> F7 perimeter of the base circle. Then select a height elevation. The shape of
the created feature depends on the conical preferences.
Top-Bottom Create a volumetric feature by selecting the top polygon and the bottom
<Alt> F8 polygon. The sides of the feature will be automatically generated. The
original bottom polygon will be removed. This tool works well for typical
building shapes. It may return unexpected results for leaning or oddly
shaped buildings.
DLD Double-line Drain Create a double-line drain by delineating the two banks. After the banks
are delineated the system will automatically adjust bank elevations to
assure mononticity and across bank consistency.
See “Executing a Double-line Drain” on page 58-22.
Flat Roof Create a building with a flat roof. In most cases, you use the Static tool.
However, you can also use the 3-Point Circle tool to create a cylinder kind
of feature. You can use Arc tool to create a partial cylinder kind of feature
as well. You set the Create tool to either Static, 3-Point Circle, or Arc first.
And then you select the Flat Roof tool.
SOCET SET Page 58-9

Chapter 58 - Sketch
SELECT TO
Peaked Roof Create a building feature with a peaked roof; used in conjunction with the
Default Peak Height field.
Peaked Roof—If you enter a value in the Default Peak Height text
field, you define the height “h” for the building, and you must
digitize exactly three points. (The three points are identified in the
next diagram as 1, 2, and 3.) The building feature that is created by
this operation has four square sides and a peaked roof. The order of
the digitized points is important to Feature Extraction, Perspective
Scenes, and Hidden Facets. You must delineate the roof in a
clockwise direction, as described in the diagram. The peak will
always be parallel to the line connecting points 1 and 2 in the
following diagram, and the value in the Default Peak Height text
entry area is “h.”
Same Building,
h Front View,
Building With Peaked = “h”
Roof, “3D” View Where
1 2
4 3
Same Building,
Top View
If you do not enter a value in the Default Peak Height text field, or the
value is 0.0, the peak height is taken from the Z-elevation of point number
4. (This point is shown inside a dotted-line circle in the previous diagram.)
You must digitize exactly four points. The order of the first three digitized
points is the same as the case above, and in both cases point 3 is forced to
be square. The peak will again be parallel to the line connecting points 1
and 2, and is centered.

Chapter 58 - Sketch
SELECT TO
Gabled Roof Create a building with a gabled roof. See the following paragraphs for
more details.
Gabled Roof—Any entry in the Default Peak Height text field is
ignored. You must digitize exactly 6 points, in the order specified
in the diagram below. The first 4 points are the outside corners of
the building, and they are not required to be either parallel or
square. digitize point 5 is the top of the gabled roof on the side
between points 1 and 4. digitize point 6 is the top of the gabled roof
on the side between points 2 and 3. The peak is in the same general
direction as the lines through points 1 and 2 and through points 3
and 4. Note that the collection order for points defining this style
roof are also in clockwise order. You can create a single or double-
bayed roof using this option.
6
Top View of a
Similar Building
5 2
3 With a Double Bay Roof
1 4
Building With
Gabled Roof, 1 2
Showing Point Collection Order.
5
6
Same Building,
Top View, with 4 3
Corresponding Point Collection Order
Automatic Building Creates volumetric buildings from 2D footprints. When you have a DTM
Extraction loaded, this tool will create volumetric buildings from any 2D footprints of
polyhedron type geometry. This is most useful when you have footprints
from another source without any elevation values. They can be imported
as polyhedron types for Feature Extraction, or used natively from an
ArcMap source for Socet for ArcGIS. You need to be sure that a DTM is
loaded and that the footprint class or layer is selected.
Note: This tool works best with a dense DTM.
SELECT TO
Undo Undo allows the user to undo multiple edit/create actions. The user may
<Ctrl> u press the Undo button multiple times to perform multiple undo actions.
Note: You may not undo an undo.
Online/Offline Allows sketch tools to be toggled from use in FE (Online) to use in ITE
(Offline) when Feature Extraction (FE) and Interactive Terrain Edit (ITE)
are both running.
58.3 Additional Toolbar

Sketch allows you to do more than just draw simple graphical objects. Sketch also allows you to
draw specialized objects such as parallel and/or monotonic linear features. Sketch also allows you

Chapter 58 - Sketch
to create a shared object edge. Some of the following Additional Draw options have associated
preference parameters. You can customize these parameters by clicking the Preferences icon
located on the Feature Extraction toolbar, selecting the appropriate item in the list, and making
the desired modifications. See “Preference Options” on page 42-39 for details. These additional
drawing options are listed and described in the table below.
SELECT TO
Parallel Will draw parallel lines if set to on, based on the parallel preference
= parameters. You have the choice of drawing up to four parallel lines. The
offset from the baseline to the parallel lines can either be typed-in or
digitized, or draw to the left or right on the imagery. To draw parallel lines:
1. You must digitize the start point of the baseline.
2. Digitize the start points (if any) of the digitizable parallel lines.
3. Digitize vertices along the base line. The parallel line graphics
shall be drawn after the first three vertices of the baseline are
digitized. Parallel cannot be turned on/off during the drawing
of a single graphic object.
Monotonic Forces objects to flow uphill or downhill. Typically used for water features
\ like creeks, rivers and streams. Changes the Z elevation values of points
after pressing RMB to make the object monotonic. If set to on while
delineating a line feature, Sketch will take the most recently digitized
vertex as the starting point for monotonic sloping. When set back to off,
the most recently digitized vertex will become the ending point and
monotonic sloping will be performed on the indicated line segment.
Edit Element Edit Element turns edit element function On/Off. This is useful when
<Ctrl> e editing objects made up of more than a single element. If the edit element
toggle is ON, the following edit operations will act only on the element:
select/move/copy/delete/rotate/scale. Additionally, the next and previous
action buttons will act only on the element. If the edit element toggle is
OFF, the following edit operations will act on the entire feature: select/
move/copy/delete/rotate/scale. Additionally, the next and previous action
buttons will act on the entire feature.
BLANK SPACE
When drawing (creating) a multi-element object, the Edit Element toggle
determines the behavior of the RMB: when ON, RMB accepts the element
and double RMB accepts the object. When OFF a single RMB will accept
the object.
Edit Shared Vertices Edit Shared Vertices, when ON, edits will work on all objects that share an
<Ctrl> a edge. Includes Insert Vertex, Redraw, Delete Vertex and Move Vertex.
When OFF, edits only work on one of the objects.

Chapter 58 - Sketch
SELECT TO
Share Segment Copy vertices from a pre-existing “shared” object into the “current” object
<Ctrl> g being drawn. Steps are:
1. Start drawing the current object.
2. Move the cursor to the first point to be shared.
3. Press the MMB to Snap.
4. Digitize a vertex for the current object.
5. Move the cursor to the last point of the edge you want to share.
6. Click the Share Segment icon button. (Polylines Only - If share
segment does not succeed, it is because the start and end points
are not on the same element. The element with the start-point
will highlight in the “edit color,” and the cursor will jump to
the closest end point of that element. The user may then move
the cursor and click share segment again.).
7. If the shared object is a polygon, you choose between the two
possible segments by clicking the Change Direction icon
button.
8. Press the LMB to confirm the share segment.
9. Continue sampling.
Change Direction Decide which of two segments to use in the Share Segment action. Only
<Ctrl> d useful when the shared object is a polygon.
Measure Clicking Measure after selecting an object will display the size (area,
<Ctrl> z length) of the object in the application’s status window.
58.3.1 Action Tools

Preference Panel When drawing: provides a preference window to custom tailor various
<Ctrl> p tool’s values. See “Sketch Preferences” on page 58-14 for details.
LMB or When drawing: adds a new vertex into the object.

/ When editing: selects an object and starts the edit, or selecting an object a
second time will confirm the edit.
MMB or When drawing: jumps the cursor onto a closest pre-existing object. Snap is
<Alt> F7 available in the Create Mode only.
RMB or When drawing: finishes an object and starts a new one.
* When editing: will reset the shape to pre-edit condition.
When selecting: will apply the currently chosen advanced edits (thin,
square, parallel, monotonic) to the selected object.
Esc When drawing: will erase the shape.

Chapter 58 - Sketch
58.3.2 Navigation Tools
SELECT TO
Next Next traverses forward through this list of objects near the cursor. Picking
PgDn a feature creates an invisible list of features, ordered by closest distance
from the cursor when the Pick occurred.
Previous Previous traverses backwards through this list of objects near the cursor.
PgUp Picking a feature creates an invisible list of features, ordered by closest
distance from the cursor when the Pick occurred
Next Vertex Next Vertex is used after selecting a vertex, traverses the vertex in a
<Ctrl> PgDn Feature/Element forward.
Previous Vertex Previous Vertex is used after selecting or being on a vertex, will traverse
<Ctrl> PgUp the vertex in a Feature/Element in reverse
58.3.3 Sketch Preferences
Sketch preferences are accessed though the application preference window. The Sketch
preference panels are as follows:
SELECT TO
Feature Extraction Set attribute value and order of preferences.

AFE Determine how the AFE drawing tools will behave. These are explained on
the following page.
Circle Determine how smooth the circle is.

Chapter 58 - Sketch
SELECT TO
Conical Determine the shape of a created conical feature. Circumference Segments

sets the number of segments around the circumference of the feature.
Height Segments set the segments from the base to the top of the feature.
Setting Height Segments to 1 would create a cone. Setting Height
Segments to 20 would create a smooth dome. Drop Base toggles wether or
not to extend the base of the feature to a specified elevation. The base of a
feature may be dropped to an entered elevation, a measured elevation, or
an elevation offset from the terrain.
Double-Line Drain Determine convergence requirements for Double-Line Drains. These
requirements are the max across bank deviation, the max mononicity
deviation, and the max change in elevation.
Extend/Trim Extended/Trim/Intersect tolerance is an x y-distance that determines how
far to extend/trim the feature. This tolerance is only used in Feature
Extraction’s Trim and Extend Tool, from the Feature Retrieval GUI. There
is a preference check box which allows this algorithm to be applied after
each feature is accepted.
NOTE: Note: For complex features all elements will be trimmed/
extended only after the feature is accepted.
Parallel Determine how many parallel lines are drawn, if any. Sets the offset mode:
“digitized” means you must use the cursor in the imagery to set the offset;
“constant” means you type-in the offset (in ground units) in the text field.
The Parallel toggle icon must be turned ON for the parallel preferences to
take effect. See “Additional Toolbar” on page 58-11 for additional details.
Rotate/Scale Determine how SOCET SET will scale features. There are two options.
1. User-Defined Anchor Point - SOCET SET will scale by an
anchor point which will be set or picked by the user with the
LMB. The anchor point must be a vertex on the feature to be
scaled. Once this preference is selected, the user can begin
choosing their anchor point by selecting the scale icon on the
Edit menu.
2. Socet Defined Anchor Point - This is SOCET SET’s own
anchor point. The anchor point here is the centroid of a feature.
Thinning Determine how much thinning is applied when a object is accepted. A
smaller tolerance does more thinning. Can be used to thin a pre-existing
object by thinning after selecting the object.
Display Edit color is the color of a selected object.
• Cursor Color determines whether the cursor color is set by the
user via the Cursor Editor, or whether the cursor color is set by
Sketch.
Display Vertices
• Turns display vertices function On/Off. If display vertices is
ON, large dots are drawn on each vertex of the current feature.
Rubberbanding
• Turns rubberbanding function On/Off. If the rubberbanding is
ON, the segment between the most recently digitized vertex
and the extraction cursor will be dynamically displayed in the
color currently being drawn. If rubberbanding is OFF, this
connecting tentative dynamically displayed segment will not
be drawn.
Cursor Shape
• Cursor Shape determines whether the cursor shape is set by the
user via the Cursor Editor, or whether the cursor shape is set by
Sketch.

Chapter 58 - Sketch
SELECT TO
Share Segment Set the highlighting characteristics of the shared segment with a color,
style and line thickness. Thickness must be between 1 and 7.
See “Additional Toolbar” on page 58-11 for additional details.
Square Set smallest edge length in the on-the-fly squaring draw mode.
Stream Minimum distance - determines how close together vertices are digitized
when dragging the cursor in the stream drawing (creation) mode.
Maximum distance - if the digitize point is greater than the “maximum
distance,” the digitize point is kept.
Bend angle - is the angle created from the last two vertices, extended to
the digitize point.
There are three rules to keeping a sampling point:
1. If the difference between the last point and the digitized point
is LESS than minimum distance then do not record the
digitized point.
is GREATER than the maximum distance then record the
digitized point.
is in between the minimum and maximum distances then use
the bend angle. If the bend angle is GREATER than the user-
specified angle record it. If the bend angle is LESS than user
specified angle don’t record it.
Thus for a given stream, bend angles preferenced at 0 degrees tend to have
more vertices at a distance between the minimum and maximum values
while bend angles at 45 degrees tend to have more vertices that are over
the maximum distance between themselves
Digitize Point
Bend Angle
Sample/Digitize Not used.

Snap Determine how snap MMB performs. X, Y, and Z tolerance sets the search
radius, which is shown as a circle in the extraction cursor. The Mode
vertex, perpendicular, or midpoint determines where the cursor jumps to.
The digitize toggle determines if a new vertex is automatically added to the
current object. If digitize toggle is OFF, you must press the LMB button
after Snap. The Insert Vertex toggle determines if a new vertex is added
into the object that is snapped to and is useful when sharing a segment.
Dimension determines when snapping whether Z is included in the snap.
• In 3D snap, the X, Y, and Z coordinates are changed to the new
snapped points X, Y, and Z coordinates.
• In 2D snap, the X and Y are changed to the new snapped points
X, and Y coordinates. Z is not effected and remains unchanged.
AutoCreate Use when you are delineating building features.You draw the roof, and
when you accept the roof, the sides of the building will be created
automatically.
58.3.4 Autocreate Parameters

You use Auto Create mode when you are delineating building features. To display this window,
click the preference button on Feature Extraction window and select SK-Auto Create. Click OK.

Chapter 58 - Sketch
You draw the roof, and when you accept the roof, the sides of the building will be created
automatically. You have three choices of how the height of the building is determined: user-
entered, DTM, or measured. You make the choice in the Autocreate Parameters window before
beginning the delineation.
If you select “Enter” for Height Entry Mode, and a 3D peripheral

device (EK2001, 3D Mouse, etc.) is used, the window in which
you can enter building height won’t come up after an Accept
until the X mouse is moved.
The Autocreate Parameters window’s selections are as follows:
SELECT TO
(Height Entry Mode) BLANK SPACE

Enter Enter the height of the building, after a feature’s top is collected, and you
BLANK SPACE are prompted.
DTM Select a DTM, after a feature’s top is collected. If one has not yet been
BLANK SPACE loaded or the DTM loaded does not cover the feature area. The elevation is
computed by using the lat and long of the feature’s top to index into a
BLANK SPACE DTM and then interpolating to that point to define the height of the
BLANK SPACE building.
Measure Select a point at ground level, after the feature’s top is collected. The
height of the feature is then computed and the object drawn.
Default Peak Height Enter the default height when the rooftop type is peaked.
DTM extension Determines how far below the DTM to extend the building sides. (Used
only in Auto Create mode when Height Entry technique is DTM). A value
of 0 just touches the DTM; values greater than 0 extend beneath the DTM
for a basement effect.

Chapter 58 - Sketch
SELECT TO
Vertex Order Force the orientation of building polygons.

Don’t Change
Force Clockwise
Force Counter-
Clockwise
Done Close the Autocreate Parameters window.
58.3.4.1 AFE Roof

There are a total of nine possible AFE rooftop methods. The currently active AFE rooftop method
is determined by the combination of the two Sketch AFE rooftop parameters: “Roof Side
Constraints” and “Roof Z Method”.
ROOF Z METHOD
ROOF SIDE
CONSTRAINTS AVERAGE
FIND USER
Perpendicular X X X
Parallel X X X
Align to Edges X X X
The possible side constraints are Parallel, Perpendicular, and Align to Edges. You can use Align
to Edges for roofs that do not have parallel or perpendicular sides. You can use Perpendicular to
force the roof edges to be orthogonal. You can use Parallel to force the roof opposite edges to be
parallel. The possible z methods are Average, Find, and User. You need to use one of these
methods to calculate the z coordinates of the resulting rooftop corners. The find method uses the
parallax of two images to calculate new values for the z coordinates of the rooftop corners. The
user method sets the Z coordinates of the rooftop corners to the Z coordinates of the seed data.
The average method finds the averaged value of the z coordinates of the rooftop corners found
using the find method, and sets the z coordinates of the rooftop corners to this value.
58.3.4.2 AFE Lake

There are three possible methods available, High, Medium, and Low. The High contrast mode
works best for features that stand out from the background. The Medium contrast mode works
best for features that are non-distinct, and the Low contrast works best for features that blend into
the background. It is strongly recommended that you use the High contrast mode for the majority
of your lake extraction.
58.3.4.3 AFE Refine

There are seven possible methods available. They are listed below along with their usage. You
will notice immediate feedback from the algorithm while you are digitizing.
1. Road Center method is used to delineate the center line of roads and similar features. Lay
down a set of points that roughly follow the center line of the road-like feature. The
algorithm will use the first point as a model of the “road” cross-section, so it is important
to place the first point at a point in the road which is fairly typical. As with the Edge
Follower method, you may designate some points asfixed template points. To designate a
template point, double-click on any point of the delineation. This point will be a fixed

Chapter 58 - Sketch
template point, and all subsequent seed points (single-clicked) will have this radiometric
pattern applied to them. This can be useful if the appearance of the “road” changes over its
length. Algorithm parameters are set for roads of width 10-20 pixels wide. Adjust the
minification level to set the feature width to meet this requirement.
2. Edge Follower method is useful for outlining fairly irregular linear features of interest.
Examples of features for which this method is suitable are trails, tree lines, coast lines, and
lakes. To delineate a feature using this method, use the LMB to click on a series of points
that roughly follow the feature’s edge. When these points have been entered, press the RMB
to accept the feature. Extra points will automatically be added to more accurately delineate
the feature. To bypass the algorithm for a certain segment and instead draw a straight line,
double-click on the vertex.
3. Same # Pts method is useful for outlining features with a number of approximately straight
sides. To delineate a feature using this method, use the LMB to click on a series of points
near the corners of the feature. As with the refine_more_pts method, it is possible to
designate certain points as fixed template points by double-clicking. The method is
described above.
4. Spline Same # Pts method is useful for outlining features with smooth curves. To delineate
a feature in this method, use the LMB to click on a series of points that roughly follow the
feature’s edge. When these points have been entered, press the RMB to have the feature
accepted. The method will move points closer to edges and add extra points to form a
smooth cubic spline curve.
5. Spline and Straight method is useful when you wish to delineate a feature which has some
straight segments connected to curvilinear segments. These points may or may not form a
closed polygon. When delineating a feature you will designate some points as being along
straight segments and others as being along curvilinear segments. You will designate the
curvilinear segment points by double clicking. When transitioning from a straight segment
to a curvilinear segment double click on the transition point. When transitioning from a
curvilinear segment to a straight segment single click on the transition point. It should be
unnecessary to place points exactly on the edge, the algorithm will refine them to follow
the feature. Try to place your seed points within three pixels of the feature edge.
6. Arc and Straight method is useful for delineating a feature which has some straight
segments connected to arcs. The points of this feature may or may not form a closed
polygon. You will designate the arc points by double clicking. When transitioning from a
straight segment to an arc double click on the transition point. When transitioning from an
arc to a straight segment single click on the transition point. It should be unnecessary to
place points exactly on the edge, the algorithm will refine them to follow the feature. Try
to place your seed points within three pixels of the feature edge.
58.4 Examples
This section covers the various aspects of running Sketch, including creating and editing
elements, as well as the various modes of Sketch.

Chapter 58 - Sketch
58.4.1 Creating an Object in Annotation
1) Press LMB
2) Press LMB
Closed automatically
3) Press LMB
4) Press RMB
1. Click Extraction > Annotation & Counting on the main workstation window.
2. Click Polygon icon in the Annotation window. This indicates to Annotation that the next
feature you draw will be a polygon.
3. Toggle F/E to OFF (this means that a single RMB click will accept the full object).
4. Select a draw mode in the Sketch draw icon list. You can select, stream, static, arc, curve,
etc.
5. Move the extraction cursor to the location where you want the polygon located.
6. Press the LMB.
7. Continue moving the extraction cursor and pressing the LMB for each point of the polygon
you are creating.
8. Press the RMB to close the polygon and accept the feature.
58.4.2 Creating a Multi-Element Feature in Feature Extraction

1. Click Extraction > Feature on the main workstation window.
2. Open an existing feature database, or create a new one.
3. Open the Feature Extraction window by clicking Extraction > Feature on the main
workstation window. Click Current Class and select a polyhedron or multiline class.
4. Toggle F/E to ON (this means that a single RMB button will accept an element, and double
press RMB accepts the feature).
5. Select a draw mode in the Sketch draw icon list. You can select, stream, static, arc, curve,
etc.
6. Toggle to the extraction cursor. Move it to the location where you would like to place the
first vertex of the element, and press the LMB.
7. Continue moving the extraction cursor and pressing the LMB for each point of the element
you are creating.

Chapter 58 - Sketch
8. Press RMB to finish the element.

9. Repeat steps 6 to 8 for each element. Use MMB (Snap) to share vertices between elements.
10. After drawing the final element, double press the RMB to accept the feature.
58.4.3 Snapping to Another Object

1. Activate Feature Extraction or Annotation.
2. Draw an object as described above. Press the RMB to accept.
3. Set the draw mode to Static.
4. Start drawing a second object: digitize a few vertices.
5. Move the cursor near to the first object (so the object passes inside the extraction cursor
circle). Press the MMB button to Snap. The cursor will jump onto the first object.
6. Press LMB to sample and add a vertex into the second (current) object.
7. If the cursor does not snap properly, activate the Preference window, and select the Snap
preferences. Enlarge the XY threshold so snap will search farther. Set the digitize toggle to
ON if you want sketch to digitize a vertex for you automatically upon snap. Change the
mode from vertex to perpendicular or midpoint if you want the cursor to jump to a different
point on the object. Set the Insert toggle to ON if you want a new vertex inserted in the first
object at the snap point.
58.4.4 Sharing an Edge between Two Objects

2. Draw and press the RMB to accept a polygon, as described above.
3. Start drawing a second object. Digitize some vertices.
4. Move the cursor close to the first object, and press the MMB (Snap) button.
5. Digitize a new vertex with the LMB (not necessary if you have “Digitize” toggle ON in the
Snap preferences)
6. Move the cursor to another location on the first shape. Click Share Segment. The segment
of the first object spanning from the first snap point to the current point will be highlighted.
7. Click Reverse Direction to alternate the two portions of the first polygon.
8. Press the LMB to copy the vertices from the first object into the second object.
9. Move the cursor away from the first shape and continue sampling vertices for the second
object. Press RMB when done.
58.4.5 Editing an Edge Shared by Two Objects

2. Create and press the RMB to accept an object.
3. Create a second object which shared several vertices with the first object (use the Share
Segment icon as described above)
4. Click Edit Shared Vertices icon toggle so it is ON.
5. Click Move Vertex icon.
6. Move the cursor near a vertex on the shared edge.
7. Press down the LMB and drag it. The vertex will move on both objects.

Chapter 58 - Sketch
8. Release the LMB, both objects will have their vertices moved.
9. Press the Delete Vertex edit tool icon.
10. Move the cursor near a shared vertex and double press the LMB. The shared vertex is
deleted from both objects.
11. Click Insert Vertex icon.
12. Move the cursor near a shared vertex and double press the LMB. A new vertex is inserted
into both objects.
58.4.6 Changing the Shape of an Object

2. Draw and press the RMB to accept an object, as described above.
3. Click the Move Feature edit tool icon.
4. Move the cursor near the midpoint of a line segment of the object. Press the LMB down,
and drag the mouse. The object will move. Release the LMB when the object is at the
desired location.
5. Move the cursor near a vertex of the object. Press the LMB down, and drag the mouse. The
vertex will move. Release the LMB when the vertex is at the desired location.
6. Click Rotate icon.
7. Move the cursor near the object. Press the LMB down, and drag the mouse. The object will
rotate around its center. Release the LMB when the object is rotated to the desired
orientation.
8. On the application’s window, select a draw mode. Click Text (Annotation window) or click
Current Class (Feature Extraction) which brings up a class having Text as the Class
Geometry. Move the cursor to a certain location, press the LMB, and type some text. The
text will appear over the imagery. Press the RMB to accept the text.
9. Click Select’s icon. Move the cursor near the text string and press and release the LBM.
The string will turn the highlighted color, and is selected. Type additional text. The new
text will be added to the end of the text string. Press RMB to accept the new text.
58.4.7 Changing the Attributes of an Object

2. Before drawing any object, set the attributes in the main application window (e.g. in
Annotation set the color, font, line width, etc.).
3. Draw an object and press the RMB to accept. It will have the attributes you set in (2).
4. Click Select’s icon. Move the cursor near the object. Press and release the LMB. The object
is now selected and will turn the highlighted color. Change the attributes on the main
window (e.g.set the feature attributes with the Feature Extraction Attribute window). Press
the RMB to accept the object.
58.4.8 Executing a Double-line Drain

1. Start Feature Extraction
2. Modify DLD preferences as needed for this project. The DLD preferences can be found in
the application preferences window.
3. Create/Load a FDB that contains a class with POLYGON geometry
4. Select a class with POLYGON geometry

Chapter 58 - Sketch
5. Select the DLD tool from the sketch panel

6. Delineate the first bank of the DLD. Click LMB to sample. Click RMB to accept. Make
elevation measurements as accurate as possible.
7. Delineate the second bank of the DLD. Delineate the second bank in the same direction as
the first bank was delineated (upstream or downstream).Click LBM to sample. Click RMB
to accept. Make elevation measurements as accurate as possible.
8. During delineation of the first or second bank, using the middle mouse button to snap to an
existing feature will cause that inserted vertex to be a control point. Any elevation
adjustment required for control points is minimized by the bank adjustment algorithm.
9. The system will generate the DLD polygon. Vertex elevation values for both banks will be
automatically adjusted to assure monotonicity and across bank consistency.
Typically, secondary Double-Line Drains should be generated first, and the main Double-Line
Drain generated last. When delineating the main DLD banks, snap to the end points of the
secondary DLDs. This helps assure that the secondary DLDs remain flat in cross-section and that
main DLD is monotonic.
If the message “Invalid DLD Banks” is displayed, the elevation adjustment algorithm was unable
to generate a DLD that met the constraint preferences. To fix this, re-delineate the DLD banks
more accurately and/or increase the values of the constant preferences.

Chapter 59
Coordinate Measurement
Coordinate Measurement is a tool for three-dimensional
measuring and changing coordinate systems.
59.1 Overview
Coordinate Measurement provides a variety of three-dimensional ground space measurement
tools.
Measuring Areas and Lengths
Coordinate System and Datum Conversions
Move to Point
59.1.1 When to Use Coordinate Measurement

Before running Coordinate Measurement, you must load a controlled image into the main
workstation window. Coordinate Measurement performs a variety of jobs, including:
• Displays the current extraction cursor location continuously
• Displays the current image space location of the extraction cursor
• Converts the current extraction cursor location to other coordinate systems
• Measures (in three-dimensional space) distances and angles between two points
• Moves extraction cursor to a three-dimensional ground point location you enter
• Converts ground points you enter from one coordinate system and datum to another
• Displays the absolute accuracy (CE/LE) of an image.
To view more detailed information about the images you are displaying, use Image Information,
by clicking Tools > Coordinate Measurement on the main workstation window.
SOCET SET Page 59-1

Chapter 59 - Coordinate Measurement
59.2 Coordinate Measurement Interface

The Coordinate Measurement window’s selections are as follows:
}
Viewed only when
Options > Absolute
Accuracy is selected
File > Exit Closes the Coordinate Measurement window.

Options > Coordinate Prompts you to convert a 3D coordinate in one coordinate system and
Conversion datum to a 3D coordinate in another coordinate system and/or datum.
Options > Move to Point Prompts you to enter the coordinate and elevation to move the extraction
cursor to.
Options > Absolute Toggles the Absolute Accuracy area on the main window.
Accuracy • If the image has accuracy available, the CE/LE will be
displayed.
• If the currently loaded image does not have accuracy
information available, an error message will appear.
Page 59-2 SOCET SET

SELECT TO
Coord. System: Specify the units in which the coordinate measurements are given. The
Geo labels and content of the coordinate fields change to reflect the coordinate
UTM system you select.
Image: Center 1:1,
Image: UL minified
Mensuration BLANK SPACE
Height Display the difference in elevation between current and initial extraction
BLANK SPACE cursor locations. (Initial location was cursor position when last Reset.)
BLANK SPACE Units specified by selected System.
Length (X,Y) Display the distance in X,Y plane between current and initial extraction
cursor locations. (Initial location was cursor position when last Reset.)
BLANK SPACE Units specified by selected System.
BLANK SPACE Display the slope between current and initial extraction cursor locations, as
Slope Percentage a percentage. Units specified by selected System.
Slant Length Display the vector distance (X,Y,Z) between current and initial cursor
BLANK SPACE locations. (Initial location was cursor position when last Reset). Units
BLANK SPACE specified by selected System.
Azimuth (Deg.) Display the angle from North to the vector with basepoint at initial cursor
location and endpoint at current location. (Initial location was cursor
position when last Reset.) Units are degrees.
Position: Displays Position:
X&Y 1 and 2 are the ground space coordinate of the current extraction cursor
location. Units are specified by the System option setting.
BLANK SPACE
BLANK SPACE
3 is the image position in line/sample of the current ground position of the
specified monitor/image at the 1:1 minification level.
Absolute Accuracy Identify the CE & LE reflect circular and linear error of the image.
Displayed only when Options > Absolute Accuracy is selected.
Reset Alt-R Resets relative measurement origin to current extraction cursor location.
Capture Point KP(*) Capture Point coordinates in the scrollable window at the bottom of the
Coordinate Display window. You may then cut and paste the coordinates
into the Report Editor (under the Output pulldown on the main workstation
window) from which you can be edit, save, or print them.
59.2.1 Absolute Accuracy

The absolute circular error (CE) and linear error (LE) accuracy of an image can be viewed in
Coordinate Measurement by clicking Options > Absolute Accuracy. The accuracy displayed is
for the current selected image loaded into SOCET SET. If there is one image selected, only the
CE accuracy value is displayed. The accuracy is displayed only if there is accuracy information
available for the image. The accuracy displayed is calculated from one of the following sources:
• Covariance File (this would be created during Triangulation)
• Master Product File for DPPDB images
SOCET SET Page 59-3

• Sigma File (this file is imported into SOCET SET)

• The GPF file contained in the Triangulation File
• The default accuracy of the Sensor Model (this is only available for certain Sensor
Models).
If the previous source is not available, then the next source is used to calculate accuracy. If there
is no accuracy information available then the CE and LE values are displayed as “NA” and an
error message is displayed. In most cases there will be no accuracy information available unless
triangulation has already been completed. The Triangulation File and Covariance File are created
during Triangulation. See “Multi-Sensor Triangulation - Overview and Workflow,”
Chapter 25for more details on Triangulation. The default Sensor Model accuracy, and
Covariance File are used to calculate the accuracy at the cursor's ground location. The accuracy
values are updated when you move the extraction cursor. If there is one image selected the LE
accuracy value is assumed perfect for the absolute CE accuracy calculated using the default
Sensor Model accuracy and Covariance File accuracy. This will improve the LE accuracy value
slightly. The default Sensor Model accuracy may not always indicate the accuracy of the image.
If you triangulated the image and you don't have a Covariance File or Triangulation File
containing a GPF, the default Sensor Model accuracy will be worse that the actual accuracy of
the image. If you triangulated the image with ground points that were not very accurate, the
default Sensor Model accuracy could be better than the actual accuracy of the image.
59.2.2 Execution - Coordinate Measurement

The following steps define an execution sequence for the Coordinate Measurement:
1. Click Tools > Coordinate Measurement on the main workstation window.
2. Select the desired System for displayed values.
3. Move the extraction cursor. The values on the window update accordingly. Record them if
desired, or add them to a file if the Report Editor window is displayed. See “Report Editor”
on page 61-13.
4. Click Reset to zero the mensuration values. The coordinates of the cursor remain
unchanged.
5. Move the extraction cursor. The values on the window are now relative to the position of
the cursor when Reset was clicked.
59.2.3 Measuring Areas and Lengths

Coordinate Measurement is good for measuring the location of a point or the distance between
two points, but if you want to measure the length of a line or the area of a polygon (in ground
space) you should use the Measure operation in Sketch, as follows:
1. Start up Feature Extraction or Annotation by clicking Extraction > Feature or Annotation
& Counting on the main workstation window.
2. Delineate the area or line with the application, in conjunction with Sketch. Accept the area
or line with the RMB.
3. Pick the area or line with the Sketch Pick operation.
4. To measure the area or length, click Measure in the Sketch window. The area or length
appears in the status window of the Display Utility window.
Page 59-4 SOCET SET

59.2.4 Coordinate System and Datum Conversions

There are three ways to convert a ground point from one coordinate system to another:
1. Use the Control Point Editor.
See “Selecting the Coordinate System or Datum” on page 23-7.
2. Copy a Ground Point File from one project to another using the Project Copy tool.
See “Copy Project” on page 5-16.
3. Use the Conversion subwindow of Coordinate Measurement.
You should use the Control Point Editor or Project Copy when you want to convert a large number
of points. The Conversion subwindow of Coordinate Measurement is handy for converting a few
points.
The Conversion subwindow of Coordinate Measurement is handy for converting a few points. To
obtain this window click Options > CoordSys/Datum Conversions on the Coordinate
Measurement window.
The CoordSys/Datum Conversions window allows you to select a source and a destination
coordinate system and horizontal datum as well as a vertical datum for height values (MSL or
ellipsoid). The coordinate system and datum of a three-dimensional coordinate entered on the
source side is automatically converted to the coordinate system and datum of the destination side.
The CoordSys/Datum Conversions window’s selections are as follows:
SELECT TO
Source BLANK SPACE

CoordSys Displays the name of the currently selected coordinate system. Clicking
this button brings up the Select the Source Coordinate System and prompts
you to select a coordinate system.
Datum Displays the name of the currently selected datum. Clicking this button
brings up the Select the Source Datum window and prompts you to select a
datum.
Latitude, Longitude, Enter the coordinate of the source point. The units are those of the
Height currently loaded project.
SOCET SET Page 59-5

SELECT TO
Height Select the vertical datum for source height values (MSL or Ellipsoid)
Destination Displays the name of the currently selected coordinate system.
CoordSys This button functions identically to the Source Coord Sys button for the
Destination coordinate system.
Datum Displays the name of the currently selected coordinate system.
This button functions identically to the Source Datum button for the
Destination datum.
Latitude, Longitude, Enter the coordinate of the destination point. The units are those of the
Height currently loaded project.
Height Select the vertical datum for destination height values (MSL or Ellipsoid).
Output Destination Points to Record all the converted destination coordinates to a file named
File coord_meas_pt_log.gpf in the project data directory when toggled ON.
The ground point data is saved to this file after each coordinate is
converted.
OFF - No logging of points occurs.
Sample points at the location of the extraction cursor with the

LMB. The point is displayed in source and destination coordinate
systems.
Close Exit Coordinate System/Datum Conversion.
The SOURCE side of the window provides for the input coordinate system and coordinate values.
The DESTINATION side of the window controls the output coordinate system and displays the
result of the conversion of the input coordinates.
You can enter source coordinates in one of two ways:
1. Type in the x/y/z or lat/lon/elevation using the keyboard; the entered values will be
interpreted to have the same units as the currently loaded project.
2. Press the LMB in the image displayed in the image window. The coordinates will appear
on the SOURCE side and the conversion results will appear on the DESTINATION side.
The coordinate systems you may select are defined as follows: They include Geographic (lat/
long), UTM, and State Plane systems. To choose a UTM or State Plane system, select the Grid
option on the Coordinate System option button; a window will pop-up with a list of all available
UTM and State Plane systems. You may add your own coordinate systems to this list.
See “Coordinate Systems” on page 5-6.
The units of the points displayed in the Coord Conversion window (of both source and output
points) are the Project units. You can always tell what these units are be referring to the top of
the main workstation menu. For example, if you are in a Meters project and convert coordinates
to a State Plane grid, the State Plane coords will be in meters. To convert from meters to feet
multiply by 3.2808334. Alternatively, create a Project which has Feet units, and do your work in
that project.
When doing a datum conversion between NAD 27 and NAD 83 (and the reverse) the NADCON
method is used. The NADCON method is dependent on the availability of provided data files in
the internal database ($db/GEODETIC/*.[las,los].txt). These data files only allow
conversions for certain regions. If a conversion is specified outside of one of these regions, a
warning is issued and the Molodensky conversion method is used. When entering data into the
conversion window, the conversion is calculated after every text string is entered. This can result
Page 59-6 SOCET SET

in conversions attempted for data points located outside any of the available data files. You may
disregard warnings in this case. If the warnings persist when the data is fully entered, you must
verify that the appropriate data files are accessible.
59.2.4.1 Execution - Coordinate/Datum Conversion

Load a project, and display at least one image on the console monitor. The following steps define
the execution sequence for Coordinate/Datum Conversion.
1. Click Options > CoordSys/Datum Conversion on the Coordinate Measurement window.
The CoordSys/Datum Conversions window is displayed with the current project coordinate
system and datum displayed for both the source and destination. The current extraction
cursor location is displayed for the source and destination points.
2. If a different source coordinate system is desired, click the field next to CoordSys on the
SOURCE side of the window to bring up a list of selections. Select a new coordinate
system, then click OK. The new source coordinate system name is displayed, and the Datum
on the SOURCE side of the window will changed to display the new default datum name if
it is different. The source point values will change to display the same point in the new
coordinate system and datum.
3. If a different source datum is desired, click the field next to Datum on the SOURCE side of
the window to bring up a list of selections. Select a new Datum, then click OK. The new
datum name is displayed. The source point values will change to display the same point in
the new datum.
4. If a different destination coordinate system and/or datum is desired, click the fields Coord
Sys and/or Datum on the DESTINATION side of the window to bring up the corresponding
list of selections. Select a new CoordSys and/or Datum, then click OK. The new names are
updated as described above, and the destination point values change to display the source
point converted to the destination system.
If both the coordinate system and the datum are to be changed,

change the coordinate system first, because this action resets
the datum to the default for that coordinate system.
5. If a different vertical datum is desired for the source, click Height on the SOURCE side to
select a different vertical datum. If a different vertical datum is desired for the destination,
click Height on the DESTINATION side to select a different vertical datum.
6. Enter the points to be converted in the SOURCE point fields. As each element is entered,
(press Return on the Keyboard, or click the mouse outside the field), the destination point
is recomputed and displayed.
7. To sample points for conversion, select the extraction cursor using the F3 key and position
it at the desired point. Press the LMB and the source and destination displays are updated
for that ground point. If logging is enabled, the point will be stored to a file for later printing
or review.
8. Toggle Output Destination Points to File to ON if you want to record the destination points
to a ground point file. Alternatively, press the LMB on an image location of the displayed
image.
9. Toggle Output Destination Points to File to OFF and preview the file selected
coord_meas_pt_log.gpf.
10. Click Close to exit window or click Options > Coordinate/Datum Conversion on the
Coordinate Measurement window.
SOCET SET Page 59-7

59.2.5 Move to Point

The Move to Point Display window provides you with the means to jump the extraction cursor to
a specific coordinate. To obtain this window, click Options > Move to Point, on the Coordinate
Measurement window.
The Image Display Parameters window’s selections are as follows:
SELECT TO
Longitude Enter the longitude of the desired point in this field.

Latitude Enter the latitude of the desired point in this field.
Elevation Enter the elevation of the desired point in this field.
Move to Point Move the cursor to the point whose coordinates you entered in the fields
above.
Done Close the Move to Point Display window.
Page 59-8 SOCET SET

Chapter 60
3rd Party Tools

Use 3rd Party Tools in conjunction with SOCET SET.
60.1 Condor Distributed Processing

Condor distributed processing software has been integrated into selected portions of ATE,
NGATE, MOSAIC, MINIFY, DPPDB and CIB processing for Windows. This will increase
throughput by allowing parallel processing on multiple machines, rather than relying on a single
machine for compute-intensive jobs.
Condor is a specialized workload management system for compute-intensive jobs. It provides a
job queuing mechanism, scheduling policy, priority scheme, resource monitoring, and resource
management. Users submit their serial or parallel jobs to Condor, Condor places them into a
queue, chooses when and where to run the jobs based upon a policy, monitors their progress, and
ultimately informs the user upon completion. Condor is a freeware product of the Condor
Research Project at the University of Wisconsin-Madison, and it was first installed as a
production system in the early 1990s.
Condor does not provide a Graphical User Interface (GUI). A suitable third-party status window
is described below - GDI-Queue Status Window.
• The installation of Condor involves the following steps, described in the following
sections:
• Installing Condor from the third-party website
• Personalizing the Condor configuration files
• Storing an encrypted password for Condor
• Verifying that the Condor daemons are running
• Installing the GDI Queue Status Window [optional]
60.1.1 Installing Condor

The condor project homepage is located at: http://www.cs.wisc.edu/condor/. The software, as
well as user’s manuals, can be downloaded from this site. Please choose the latest “stable series”
release for installation. The MSI version for “Windows 2000 or XP” should be selected. The
Microsoft installation wizard will then guide you through the installation process.
The condor installation software (via the installation wizard) will lead you through a series of
questions that are straightforward, but may require the assistance of a Systems Administrator.
SOCET SET Page 60-1

Chapter 60 - 3rd Party Tools
The installation will require that a pre-determined host machine (e.g. server) be selected to install
the central manager. Each additional client machine on the condor network will require a separate
installation of the software.
60.1.1.1 Central Manager

1. Install condor on the box that will be the central manager.
2. Stop the condor service (net stop condor).
3. Configure condor central manager correctly.
Condor will be configured to run jobs as the submit user. In order to do that condor must be setup
to run a credd server. The credd server should always be run on the same server as your central
manager. The following are variables in your condor_config to pay special attention to:
CONDOR_HOST - This is the name of your central manager. Make sure it is set to the fully
qualified host name of your central manager.
CONDOR_ADMIN - SMTP_SERVER - These need to be set to the email address of your admin
and the smtp server for your site. If you don't have these, you can leave them blank. They let
condor send out an alert if something goes wrong. The same information is in the log files.
UID_DOMAIN - This should be set to the same value as the environment variable
USERDNSDOMAIN.
COLLECTOR_NAME - Any arbitrary name. Ex: SOCET_SET You must use a different name
for different pools.
It's very important that you get these HOSTALLOW_* variables; the security of your condor pool
depends on it. Settings below are defaults:
HOSTALLOW_ADMINISTRATOR - should be set to $(FULL_HOSTNAME).
HOSTALLOW_OWNER - should be set to $(FULL_HOSTNAME),
$(HOSTALLOW_ADMINISTRATOR)
HOSTALLOW_READ - should be set to *.
HOSTALLOW_WRITE - should be set to all machines that you'd like to be join your pool, submit
jobs, etc. You can set this to *.example.net where example.net is your dns domain.
HOSTALLOW_CONFIG - should be set to $(FULL_HOSTNAME)
TRUST_UID_DOMAIN - should be set to True. If your domain is not an internet domain set this
to True. Otherwise false.
START - should be set to True.
SUSPEND - should be set to False.
PREEMPT - should be set to False.
DAEMON_LIST - should be set to MASTER.
JAVA - this should be set to the full path to JAVA.EXE.
CREDD_HOST - This should be uncommented and should be set to
$(CONDOR_HOST):$(CREDD_PORT).
Add these next variables at the bottom on condor_config:
Page 60-2 SOCET SET

STARTER_ALLOW_RUNAS_OWNER = True
CREDD_CACHE_LOCALLY = True
SEC_CLIENT_AUTHENTICATION_METHODS = NTSSPI, PASSWORD
SEC_DEFAULT_AUTHENTICATION = REQUIRED
SEC_DEFAULT_ENCRYPTION = REQUIRED
SEC_DEFAULT_INTEGRITY = REQUIRED
SEC_DEFAULT_NEGOTIATION = REQUIRED
In condor_config.local on the central manager here are some variables to set:

##### central manager
DAEMON_LIST = $(DAEMON_LIST) COLLECTOR NEGOTIATOR CREDD
SEC_CREDD_SESSION_TIMEOUT = 10
CREDD.SEC_DEFAULT_AUTHENTICATION = REQUIRED
CREDD.SEC_DEFAULT_ENCRYPTION = REQUIRED
CREDD.SEC_DEFAULT_INTEGRITY = REQUIRED
CREDD.SEC_DEFAULT_NEGOTIATION = REQUIRED
CREDD.SEC_DAEMON_AUTHENTICATION_METHODS = PASSWORD
CREDD.ALLOW_DAEMON = condor_pool@$(UID_DOMAIN)
CREDD.SEC_WRITE_AUTHENTICATION_METHODS = NTSSPI
CREDD.SEC_DEFAULT_AUTHENTICATION_METHODS = NTSSPI
These last 2 also go in the condor_config.local, but may not be necessary. These should be set if
condor starts slowly after starting the service. The explanation is; when condor runs, it tries to
call into the firewall to add an exception for itself. If the firewall service isn't started, this will
appear to hang for a very long time and other condor services will fail to start up or won't work
correctly. Only use these variables if you see those symptoms.
ADD_WINDOWS_FIREWALL_EXCEPTION = FALSE
WINDOWS_FIREWALL_FAILURE_RETRY = 10
4. Start central manager (net start condor)

5. Add pool password.
This password allows other condor machines to get credentials from the credd server. After
typing the command below, it will ask you for a password. Remember the password, because you
will need to use it later.
condor_store_cred add -c
6. Stop central manager (net stop condor)
7. Start central manager (net start condor)
SOCET SET Page 60-3

At this point you should be able to run commands, condor_status and condor_q and get
information. Run condor_status -long [MACHINENAME] where [MACHINENAME] is
replaced by the full host name of the machine. Look for LocalCredd, make sure it is set.
60.1.1.2 Submit and Execute Node

After condor is set up and working on the central manager, you can start installing condor on
computers that will be submit and execution hosts.
1. Install condor on the box that will be a submit and execute node.
2. Stop the condor service (net stop condor).
3. Configure condor submit and execution hosts correctly.
The condor_config on this host should an exact copy (except for JAVA) of the condor_config on
the central manager. Just copy it over, and pay attention to the JAVA; ensure it is set to the right
place.
In condor_config.local on the submit and execution hosts; the following are variables to set:
##### execution host
DAEMON_LIST = $(DAEMON_LIST) STARTD
##### submit host
DAEMON_LIST = $(DAEMON_LIST) SCHEDD
These last 2 also go in the condor_config.local, but may not be necessary. These should be set if
condor starts slowly after starting the service. The explanation is; when condor runs, it tries to
call into the firewall to add an exception for itself. If the firewall service isn't started, this will
appear to hang for a very long time and other condor services will fail to start up or won't work
correctly. Only use these variables if you see those symptoms.
ADD_WINDOWS_FIREWALL_EXCEPTION = FALSE
WINDOWS_FIREWALL_FAILURE_RETRY = 10
4. Start submit and execute hosts (net start condor)

5. Add pool password. This is the same password that you used for the central manager.
condor_store_cred add -c
6. Stop submit and execute host (net stop condor)
7. Start submit and execute host (net start condor)
At this point you should be able to run commands, condor_status and condor_q and get
information. Run condor_status -long [MACHINENAME] where [MACHINENAME] is
replaced by the full host name of the machine. Look for LocalCredd, make sure it is set.
After this is setup correctly, you can start adding users to the credd server. Add these by using
condor_store_cred command.
condor_store_cred add
On a Windows machine, the “condor_store_cred –add” command must be run for each user to
store the password of a user/domain pair securely in the Windows registry. Using this stored
password, condor is able to run jobs with the user ID of the submitting user. The password is
Page 60-4 SOCET SET

stored in the same manner as the system does when setting or changing account passwords. The
password is stashed in a permanent manner, and is maintained across system reboots.
To stash your password, simply open up a DOS command window, and type in the
“condor_store_cred –add” command. You will then be prompted for your password.
This will add the credentials of the current user to the condor pool. After that you should be able
to run jobs as the current user.
60.1.2 Condor Daemons

Condor runs a set of daemons (i.e. continually running programs) on each machine. On the
condor host machine, the following five daemons are required:
1. condor_master: This program runs constantly and ensures that all other parts of Condor are
running. If they hang or crash, it restarts them.
2. condor_collector: This program collects information about all computers in the pool as well
as which users want to run jobs.
3. condor_negotiator: This program decides which jobs should be run on which computers.
4. condor_startd: If this program is running, it allows jobs to be started up on this computer.
5. condor_schedd If this program is running, it allows jobs to be submitted from this
computer.
In addition, the condor_shadow program is run once for each job submitted to condor.
6. condor_shadow (Not a persistent daemon) For each job that has been submitted from this
computer, there is one condor_shadow running. It will watch over the job as it runs
remotely.
On a condor client machine, the following three daemons are required:
1. condor_master.exe
2. condor_schedd.exe
3. condor_startd.exe
Once condor is installed on the host machine (as well as any client machine), the required
daemons should automatically start up. This can be verified by using the Windows Task
Manager.
60.1.3 GDI-Queue Status Window

Since condor does not provide a graphical user interface, the following third-party status window
can be downloaded:
http://www.cirquedigital.com/products/gdiqueue/
The GDI Queue Status window allows you to graphically track your jobs run through condor.
This window displays all available machines, as well as the jobs that are currently being run
through condor.
60.1.4 Additional Condor Commands in DOS

The GDI Queue Status window should provide adequate details concerning a condor job.
However, the following DOS commands can be run to ascertain similar information.
• condor_status displays a list of machines in the condor queue and their associated status
SOCET SET Page 60-5

• condor_q displays a list of the jobs currently running in the condor queue
• condor_rm <job name> allows you to remove a current condor job (by supplying the
job name available by the condor_q command).
Please consult the condor user’s manual (available via the website) for additional useful condor
commands.
If information is required on jobs no longer in the condor queue, the condor log files described in
the following section can be utilized.
60.1.5 Condor Log Files

Condor maintains one log file per daemon. The log files are located in the “log” sub-directory
inside the condor installation directory.
Page 60-6 SOCET SET

Chapter 61
Utilities
Utilities contains descriptions of numerous SOCET SET
tools.
61.1 Overview
This chapter covers various utilities used while running SOCET SET. Each section will cover its
usage, and examine the intricate parts, along with its execution.
Command Line Tools Graphics Terrain Settings
Camera Calibration Editor Report Editor
Radian / Degree Conversion Keyboard/Trackball Accelerator Mapping
Cursor/Graticule Editor Y Parallax
Tracking Sensitivity Stereo Model Manager
Project Data Review Image Information
Quality Statistics Change Elevation
Graphics Projection DOQ Editor
Correlation Band Selector Flicker Images
Configuration Editor
SOCET SET Page 61-1

Chapter 61 - Utilities
61.2 Command Line Tools

The tools listed in the table below are command-line programs and do not have a window. Most
of the tools will give you instructions if you do the following:
• Go to <install_path>/bin directory
• Enter the following:
% start_socet -single <tool_name>
TOOL FUNCTION
apmstats Prints out various statistics about gpf and ipf files.
conv_spec converts a v5.0 spec file into v4.4 format or vice-versa

type conv_spec -h for help
copy_spot_disk Copies files on SPOT 1A PAN tape to disk
copy_spot_to_tape Copies files on SPOT 1A PAN files to tape in SPOT format
dtm_compare Subtracts the elevation values of two DTMs and outputs the differences
into a third DTM
dump_screen Makes, displays, and prints screen dumps
flip_image Flips an image vertically, horizontally, or rotates 90 degrees
ftr_to_dst Converts SOCET SET fdb, particularly contours, to an ASCII format

readable by SysScan software
img_band_merge Converts RGB 24-bit color image to 8-bit grey level image
img_cut Cuts a piece or band from an image
img_join Joins 3 separate band files into a single-3 band image file
make_arc Makes an ASCII ArcInfo “world file” with orthophoto geo-reference

info
make_shortsup Makes a short ASCII informational file from a .sup file
media_state Used by DPPDB to determine if remote tape drive is rewindable
mp_asc_import Converts a ASCII Mass Point file into a SOCET SET feature db file
nitf_rpc_chip Creates a chip from an image. Chip will be in NITF format with RPC
TRE’s included.
nitf_rpc_modify Replaces RPC TRE’s in an existing image, or copies existing image to

a new image, replacing the RPC TRE’s
ortho_qa_file_read Checks orthos within a given MBR and generates a report
ortho_qa_make_sup Makes a SOCET SET ortho .sup file from a sample ASCII .1st file
ortho_qa_merge_ Merges orthos of the same GSD and size into a single image
orthos
ortho_qa_stats Generates a quality statistics report of points measured in at orthophoto
Page 61-2 SOCET SET

TOOL FUNCTION
pgmkill Kills UNIX processes using the process name as input
platform_swap_grid_ Converts grid DTM between UNIX/Windows platforms

dtm
ss_hostid Gets the hostid required to obtain a SOCET SET license
start_socet Script used to start SOCET SET
tape_struct Reads a tape and reports record sizes of all files found
tiffy Reads a TIFF file and reports all TAG info
tkbtest Diagnostic program for the trackball
You can read additional information on some of these tools in the doc/readme_files
directory.
61.3 Graphics Terrain Settings

61.3.1 Footprint, North Arrow, Sub Pixel Roam, Anti-Aliased Lines,
and Terrain Tracking Settings
This window allows you to set various options: Footprints, Display items, and Terrain Tracking
of the Z motion.
The Graphics/Terrain Settings window can be opened by clicking Preferences > Graphics/
Terrain Settings on the main workstation window. The window can be hidden by clicking Close
or by again selecting Preferences > Graphics/Terrain Settings. The Graphics/Terrain Settings
window allows you to modify the North Arrow, Terrain Tracking, and Footprint toggles.
All changes in the Graphics/Terrain Settings Window are

applied immediately.
SOCET SET Page 61-3

61.3.1.1 Footprints
Footprints identifies the outer edges of Images, Terrains, and/or Features. They will display an
colored outline of the boundaries of each of the footprints.
To activate Footprints, click the desired footprint: Image, Terrain Feature. The Footprint will
appear on the main viewing port.
To de-activate the footprint, un-select the footprint name.
61.3.1.2 North Arrow

The north arrow identifies the north direction in each monitor you have imagery loaded. The north
arrow is displayed (in yellow) in the lower-right corner of each image.
In UTM and grid coordinate systems, the North Arrow reflects

grid north, which may be different than true north.
The North Arrow works best when you have the Cursor option in the Display Utility window set
to Fixed Image—Toggle.
To activate the north arrow, click North Arrow from the Graphics Display section.
To de-activate the north arrow, re-select North Arrow.
61.3.1.3 Sub Pixel Roam

Turns on/off the ability to roam less than a single pixel. Uses bilinear interpolation to calculate
the RGB values of the imagery as it moves in sub-pixel increments.
61.3.1.4 Anti-Aliased Lines

Turns on/off hardware support for Anti-aliased graphics. Graphic images that have curved or
diagonal edges to them will have a jagged, stair-stepped edges. The larger the image, the more
apparent this problem is. Anti-aliasing will smooth out these rough edges. This is done by
changing some of the pixels along the edge of the graphic, which causes the edge to blend with
the background.
61.3.1.5 Terrain Tracking

Terrain Tracking provides the means by which you can lock the elevation of the extraction cursor
onto the surface of a DTM. You can also set a bias distance above or below using the Z control.
Terrain Tracking can be particularly useful, as it relieves you from the burden of having to
manually set the elevation of the extraction cursor on the ground every time you move the cursor
in the image. This can be of great use to you in the following situations:
• Three-dimensional coordinate measurement.
• Delineating geomorphic (ground conforming) features such as ridges, drain lines,
and roads.
• Interactively editing terrain data such as contours and posts.
• Defining a sequence of terrain-hugging view and aim waypoints for a Perspective
Scenes fly-through.
Page 61-4 SOCET SET

• Visualizing the correct extraction cursor elevation on the console monitor during
three dimensional measurement and extraction operations.
In order to utilize Terrain Tracking, you must first choose a DTM. The name of the selected DTM
is shown in the text field. There are two possible modes in which to run Terrain Tracking: Z
motion enabled and Z motion disable. When Z motion is disabled, you cannot change the
elevation of the extraction cursor using the trackball. When Z motion is enabled, you can use the
trackball to change the elevation.
To activate the Terrain Tracking, do the following:
Select the box next to Terrain Tracking on the Graphics/Terrain Settings window. With Terrain
Tracking selected, two modes are available: Z Motion Enabled and Z Motion Disabled.
The Z Motion Enabled mode allows you to impart a bias above the elevations in the DTM
with the Z control. To reset the bias to zero, turn Terrain Tracking off by un-selecting
Terrain Tracking.
The Z Motion Disabled mode disables the Z control such that the elevation of the extraction
cursor is always set exactly on the DTM surface.
If the DTM you use does not cover the entire image, no warning
is given when you roam outside the boundary of the DTM.
61.4 Camera Calibration Editor

The Camera Calibration Editor provides the means by which you enter and save frame camera
calibration data. Calibration data includes focal length, lens distortion, and principal point
offsets. The camera calibration file is selected for frame images during Frame Import. See
“Frame Import” on page 8-8 for details.
The camera calibration file is also used for BINGO Frame images. See “BINGO Frame Import”
on page 8-16 for details. One subtle difference for BINGO Frame camera calibration files is the
entry of radial lens distortion data. For triangulation of BINGO Frame images, the Radius Unit
must always be in millimeters, the Radius interval must be uniform, the Radius must be input in
increasing order, and the Zero Radius must be included in the input Distortion table.
You can edit an existing camera calibration file, or you can create a new one. The editor provides
two ways for you to enter data:
• A graphical drawing area that you click the mouse in.
• Labelled text fields that you type data into with the keyboard.
Your calibration data is saved in a camera calibration file with the .cam extension in the
<install_path>/internal_dbs/CAM directory.
To edit fiducial coordinates and distortion parameters, you have to bring up the Fiducial
Coordinates and Distortion Parameters sub-windows, respectively. These sub-windows are
directly accessible from the Camera Calibration Editor.
The camera calibration data is used in the frame sensor model along with exterior and interior
orientation parameters forming the ground-to-image transformation. The chief component of the
transformation is known as the collinearity equations:
x = -focal_length * f[Xg, Yg, Zg, Xc,Y c,Z c,omega c,phi c,kappac]
y = -focal_length * f[Xg, Yg, Zg, Xc,Y c,Z c,omega c,phi c,kappac]
SOCET SET Page 61-5

where,
x and y are the film coordinates or CCD array coordinates (for digital framing cameras) in
millimeters with respect to the principal point of autocollimation (PPA) as the origin of the
coordinate system.
focal_length is the calibrated focal length given in the camera calibration report in millimeters.
Xg, Y g, Z g are the current ground coordinates being transformed.
Xc,Y c, Zc,omega c,phi c,kappa c are the exterior orientation parameters of the frame camera.
61.4.1 When to Run the Camera Calibration Editor

You run the Camera Calibration Editor each time you begin receiving imagery for the first time
from a new frame camera. Once you enter the camera’s calibration data, you do not have to enter
it again. You should run this editor prior to running Frame Import.
If no calibration information is available, you do not have to use the Camera Calibration Editor,
but you will have to enter the camera’s focal length manually during Frame Import and Interior
Orientation.
61.4.2 Principal Point Offsets

The Principal Point of autocollimation X-Offset field requires the x-offset of the principal point
of autocollimation (PPA) from the origin of the fiducial coordinate system, in millimeters
(XPOFF).
The Principal Point of autocollimation Y-Offset field requires the y-offset of the principal point
of autocollimation (PPA) from the origin of the fiducial coordinate system, in millimeters
(YPOFF).
The Principal Point of Symmetry X-Offset field requires the x-offset of the origin for determining
the radial and decentering distortion corrections from the origin of the fiducial coordinate system,
in millimeters (XSOFF).
The Principal Point of Symmetry Y-Offset field requires the y-offset of the origin for determining
the radial and decentering distortion corrections from the origin of the fiducial coordinate system,
in millimeters (YSOFF).
The origin of the fiducial coordinate system is typically represented by the intersection of the
(imaginary) lines joining the fiducial marks. It is commonly known as the fiducial center or
indicated principal point (IPP). For digital frame images there are no fiducial marks, but the
“fiducial center” origin is of the middle CCD array. The center for digital frame images is
determined during Frame Import by entering the CCD array size in millimeters into the Size(X)
and Size(Y) fields.
The principal point offsets are applied to the x and y frame coordinates prior to determining the
corrections for lens distortions. The x and y frame coordinates reference the PPA as the origin for
the ground-to-image transformation. The PPA offsets are added back into the computed
coordinates resulting in xp and yp, whose coordinates reference the fiducial center or IPP.
xp = x + XPOFF
yp = y + YPOFF
where,
Page 61-6 SOCET SET

xp and yp are the frame coordinates in millimeters with respect to the fiducial center as the origin.
x and y are the frame coordinates in millimeters with the principal point of autocollimation as the
origin (the results of the ground-to-image transformation using the collinearity equations).
XPOFF, YPOFF are the principal point of autocollimation offsets in millimeters entered into the
Camera Calibration Editor window from the camera calibration report.
SOCET SET includes an additional correction known as the principal point of symmetry (PPS)
offset. The principal point of symmetry offset is expressed in millimeters defining the origin for
the radial lens distortion. The offsets (XSOFF and YSOFF) are subtracted from the fiducial
center origin prior to correcting for radial and decentering lens distortion.
xs = xp - XSOFF
ys = yp – YSOFF
where,
xs and ys are the frame coordinates in millimeters with respect to the origin for the symmetric
radial lens distortion.
XPOFF, YPOFF are the principal point of symmetry offsets in millimeters entered into the
Camera Calibration Editor window from the camera calibration report.
61.4.3 Lens Distortion

The lens distortion parameters are entered as radius / distortion pairs. Radius may be entered
in millimeters from the origin, or in degrees. Distortion values are entered in micrometers.
In cases where the camera calibration report indicates “corrections” for lens distortion
instead of the measured “errors” of the distortion, you must change the signs of the correction
values to be consistent with what is expected in SOCET SET. An example using the USGS
camera calibration report is referenced throughout this section.
The radius / distortion pairs are used to compute the coefficients (K0, K1, K2, K3) of an odd-
powered polynomial also known as a Taylor series polynomial. In the case of the USGS
camera calibration report, a tabular list of “errors” is given in microns. The USGS camera
calibration report also includes the associated K-values that are used to compute
“corrections”. Entry of the tabular values from the USGS camera calibration report allows
SOCET SET to compute the equivalent K-values for the “errors”. If entry of the K-values
from the USGS camera calibration report is desired instead of entry of the table values, then
the signs of the K-values from the USGS camera calibration report must be reversed before
entering them into the SOCET SET Camera Calibration Editor window. This is a result of
the table values being measured “error” values and the K-terms on the USGS camera
calibration report being polynomial coefficients used to compute the “correction” values. In
SOCET SET the table of values and associated K-terms, either computed or entered, in the
Camera Calibration Editor Distortion Parameters window are both considered “error” values.
Corrections for radial lens distortion are computed based on the radial distance of image
coordinates (x s and y s ) from the principal point of symmetry origin. If XSOFF and YSOFF
are zero, then the origin for the radial lens distortion is the fiducial center. If XSOFF and
YSOFF are entered as the same values as XPOFF and YPOFF from the camera calibration
report, then the origin for the radial lens distortion is PPA. In the case of the USGS camera
calibration report, XSOFF and YSOFF values should be entered as the same values entered
for XPOFF and YPOFF as the radial lens distortion is computed from PPA as the origin.
SOCET SET Page 61-7

In addition to radial lens distortion, some calibration reports like the USGS have a
decentering distortion table along with associated P-values (P1, P2). SOCET SET does not
allow entry of the decentering distortion table values, but does allow for entry of the P-
values. Just like radial lens distortion, the table represents “errors” and the P-values
represent “corrections”. Therefore, the signs of the P-values must be reversed from the
USGS camera calibration report before entry into the SOCET SET window.
For completeness, the equations used to compute the correction values and subsequent
corrected x c and y c film or CCD array coordinates in millimeters in SOCET SET are:
r = sqrt (x s 2 + y s 2 )
dx r = x s * (K0 + K1*r 2 + K2*r 4 + K3*r 6 )
dy r = y s * (K0 + K1*r 2 + K2*r 4 + K3*r 6 )
dx c = P1 * (r 2 + 2 * x s 2 ) + 2 * P2 * x s * y s
dy c = P2 * (r 2 + 2 * y s 2 ) +2 * P1 * x s * y s
x c = x p + dx r + dx c
y c = y p + dy r + dy c
where,
r is the radial distance of the image coordinates x s and y s .
d x r and d x r are the radial lens distortion corrections in millimeters computed from the odd
ordered polynomial.
K0, K1, K2 and K3 are the coefficients of the odd ordered polynomial.
d x c and d x c are the decentering corrections in millimeters computed from the P1, P2
coefficients.
P1 and P2 are the decentering polynomial coefficients from the camera calibration report.
x c and y c are the frame coordinates in millimeters corrected for radial and decentering lens
distortion with respect to the fiducial center as the coordinate system origin.
As a final note, in order to complete the transformation from frame coordinates in millimeters
to line and sample coordinates for the digital image, the x c and y c are transformed by the
interior orientation coefficients that are determined by measuring the fiducial marks for
frame imagery or entered as Size(X) and Size(Y) for the CCD array chip size for digital frame
images during Frame Import.
61.4.4 Camera Calibration Editor

To obtain this window, click Preparation > Camera Calibration on the main workstation
window. This is the main window you see when you first invoke the editor. This window contains
Page 61-8 SOCET SET

fields for entering the camera focal length and the principal X and Y offsets. There are buttons
for accessing the Fiducial Coordinates and Distortion Parameters sub-windows.
The Camera Calibration Editor window’s selections are as follows:
File > Open... Prompts you for the name of a camera calibration file to load into the
editor. You can pick an existing file by clicking on its name, or you can
create a new file by entering a name into the Selection text field of the file
selection dialogue window.
File > Save Saves your changes to the camera calibration file. If you did not open an
existing file or create a new one by opening a file, you will be prompted to
pick a file to save your changes to. To create a new file, enter a name into
the Selection text field.
File > Save As... Prompts you to pick a file to save your changes to. To create a new file,
enter a name into the Selection text field.
File > Exit Exits the Camera Calibration Editor. If you modified data but did not save
it at this point, you will be warned. To exit without saving, click the OK
button. To return to the window so that you can save your changes, click
the Cancel button.
SELECT TO
Camera Calibration File Display the name of the currently loaded camera calibration file. If you
haven’t loaded or saved a file, this field is blank. This field is not editable.
Focal Length (mm) Enter the focal length for your camera in millimeters.
SOCET SET Page 61-9

SELECT TO
Principal Point Enter the X coordinate of the principal point offset for autocollimation and
X-Offset (mm) symmetry.
Principal Point Enter the Y coordinate of the principal point offset for autocollimation and
Y-Offset (mm) symmetry.
Fiducial Coordinates... Bring up the Fiducial Coordinates window.
Distortion Parameters... Bring up the Distortion Parameters window.
61.4.5 Fiducial Coordinates

This window is for entering and editing the camera fiducial coordinates.
This window consists of a large square drawing area and a list of fiducials. To add a fiducial point,
position the mouse cursor over the approximate location of the fiducial within the camera frame.
A numbered button will appear, which represents the fiducial. At the same time, a corresponding
entry (consisting of the ID number and coordinates) will appear in the fiducial list on the right
side of the window. Note that the coordinate system origin is in the center of the drawing area.
The units are in millimeters.
The Fiducial Coordinates window’s selections are as follows:
SELECT TO
Data Strip Indicate which side of the Side drawing area is the actual data strip side.
ID Display the identification number of the fiducial marks. The fiducials are
numbered in the order you created them. You cannot edit this field.
X(mm), Y(mm) Display the X and Y coordinates of a fiducial mark. You can edit these
fields by typing the new coordinate with the keyboard, followed by
pressing return on the keyboard. The location of the point updates
automatically.
Number of Points Display the current number of fiducial marks in the drawing area.

SELECT TO
OK Record the fiducial positions in the currently open file and closes the
window. To commit these changes to disk, you will have to click File >
Save on the Camera Calibration Editor window.
To move a fiducial point, position the mouse cursor on top of the point in the drawing area; then
click and hold the LMB and drag the fiducial to the new position, release the LMB. To manually
edit the exact positional coordinates of a fiducial, click in the coordinate text field in the fiducial
list. Type your changes with the keyboard, followed by pressing return on the keyboard. The
fiducial in the drawing area automatically moves to the new position you entered.
To delete a fiducial, click on it in the drawing area with the RMB. The fiducial disappears from
both the drawing area and the list of fiducials.

61.4.6 Distortion Parameters

This window is for entering and editing the camera distortion parameters.
To add a distortion pair to the list, press the LMB in the No. of Distortion Pairs text field. To enter
the radius and distortion values, press the LMB in each text field in the list, and enter the
numerical values with the keyboard.
To delete an entry from the list, press the RMB in any field for that entry.
The Distortion Parameter window’s selections are as follows:
SELECT TO
Options Select to use either Distortion Pairs or K and P Values.

No. of Distortion Pairs Add pairs in this field, max 20.
Radius Unit Indicate the unit of the radius value.
ID Display the id of the distortion pairs in numerical format. This field is not
editable.
Radius Enter the radius values.
Distortion Enter the distortion values.
Symmetric Radial Distortion Enter the values for K0 through K4.
Parameters
Decentering Distortion Enter the values for P1 through P3.
Parameters
OK Save the radius/distortion pairs in this window such that when this window
is exited and re-entered, the current fiducial marks are retained.

SELECT TO
Cancel Delete all changes made in the window once the window is exited. The last
condition when the window was brought up will be retained.
61.5 Execution - Camera File

Use the following set of steps to create a new camera file from the information contained in a
typical Camera Calibration Report. The camera directory <install_path>/
internal_dbs/CAM contains numerous examples of completed camera calibration files. This
example uses the default.cam file as a starting point.
1. Start the Camera Calibration Editor by clicking Preparation > Camera Calibrations on the
2. Click File > Open... on the Camera Calibration Editor window. Pick the default.cam file,
then click OK.
3. Enter the focal length by clicking Fiducial Coordinates...; this brings up the Fiducial
Coordinates window. Update the camera fiducial coordinate values according the values
given in you camera calibration report.
4. Toggle the Data Strip Side option to indicate which side the data strip is on.
Currently, only one option is implemented: Left.
5. Click OK to save your entries and return to the main Camera Calibration Editor window.
6. Enter Principal Point X/Y Offsets directly into the filed using the keyboard.
7. Click Distortion Parameters...; this brings up the Distortion Parameters window. Click in
the No. of Distortion Pairs field to increase the number of distortion pairs you wish to enter.
To decrease the number of distortion pairs, press the RMB on the pair in the list.
8. Set the Radius Unit option to indicate degrees or millimeters.
9. Now enter the radius and distortion values from your camera calibration report.
10. Click OK to save your entries and return to the main Camera Calibration Editor window.
11. Click File > Save As...; enter the name of the new camera calibration file, then click OK.
12. Click File > Exit to exit the Camera Calibration Editor.
61.6 Report Editor

Report Editor creates, edits, reviews, and prints reports and text files. All Report data is saved in
the project data directory of the current project file. Selecting a different project file will cause
textual report to be saved in the project data directory of the newly selected project file. Many of
the SOCET SET applications make quality assurance reports that have the extension .rep. You
can use Report Editor to view and print those reports. To open an Editor window, click
Output > Reports > Edit.

61.6.1 Execution - Opening a New Text File

1. Click File > New. Enter a file name for the report, then click OK.
2. Start entering text via the keyboard.
3. To close the text being edited, click File > Exit. If the file has not been saved, you will be
prompted to do so or lose all changes that have been made since the last save.
61.6.2 Execution - Opening an Old Text File

1. Click File > Open. Select an existing file, then click OK.
2. The text will be displayed and is editable.
61.6.3 Execution - Saving a text file

1. Click File > Save to save the file using the name entered.
2. To save the file using a different name, click File > Save As and enter a new file name.
61.6.4 Execution - Editing a text file

A word or a group of words can only be edited via the Edit pulldown if they have been
highlighted. Highlighting is done by moving the cursor on top of a word and double clicking the
LMB. It can also be done by clicking the LMB down and dragging the cursor to the end of the
word or words to be highlighted, then releasing the LMB. A highlight can be erased by clicking
the LMB once.
To move text, select the text, then click and hold the MMB and drag the text to the new location,
then release the MMB.
To copy a word or group of words to another area of the note pad, highlight the area and select
Edit > Copy. Move the cursor to the desired area and press the LMB once. A cursor marker should
appear on the screen. If the marker is in the correct area, click Edit > Paste and the text
highlighted will appear after the cursor marker.
To cut a word or group of words and paste them to a specified location, perform the above
substituting Cut for Copy or use the move text.
To delete the highlighted text, Click Edit > Cut.
61.6.5 Execution - Printing a text file

1. To print a file, the file must first be displayed in the window.
2. Click File > Print.

61.7 Radian / Degree Conversion

The Radian / Degree window gives you a quick calculator to convert a value from radians to
degrees or from degrees to radians. To obtain this window, click Tools > Radian<->Degree on
the main workstation window. To perform a conversion, type in a known value in the one of the
fields in the window. When you press the Return key at the end of the value, the conversion to
the other units appears in the other window. Click the X to close the Radian/Degree window.
61.8 Cursor/Graticule Editor

The (Extraction) Cursor/Graticule Editor allows you to change the shape or color of the extraction
cursor. This is very helpful for accommodating various image gray level conditions.
The Cursor tab permits you to interactively change the cursor until you like what you see, and
then save the characteristics. To obtain this window click Preferences > Cursor Editor on the
The Graticule tab permits you to interactively change the cursor into two different measuring
devices: Concentric Circles or Compass Rose.
The Cursor tab’s selections are as follows:
File > Load Loads an existing cursor file (.crf).

File > Save Cursor/Graticule Saves the modifications you made to the file loaded.

File > Exit Exits the Cursor Editor window.

SELECT TO
Color Bar Choose from the color pallet; there are 108 choices available.
Cursor Style Specify cursor style—a horizontal cross, a diagonal cross, or a solid square
dot.
Center Point Specify whether the center pixel of a cross cursor is visible.
Cursor Size Specify the size, in pixels, of a cross cursor or the solid dot.
Break Size Specify the number of pixels (counting from the center pixel), to leave out
from the cross cursor.
Circle Radius Specify the radius, in pixels, of a circle to draw around the cursor.
61.8.1 Graticule Selection

The Graticule tab allows you to select one of two various types: Compass Rose or Multiple
Concentric Rings. The Color and Center Mark choices are similar to those of the Cursor. The
choices are described below.
Concentric Rings Only
The Graticule tab’s selections are as follows:
SELECT TO
Number of Rings Enter 1-5 for Concentric Rings only.

SELECT TO
Center Radius Indicates the radius of the center mark on the Compass Rose.
Rose Radius Indicates the radius of each ring using Concentric Rings, or the outer most
marker using Compass Rose. Distance units between tick marks are the
same used in project units.
Tick Mark Spacing Indicates the distance between marks using Compass Rose. Distance units
between tick marks are the same used in project units.
Distance units between tick marks are the same used in project
units.
Execution
1. To activate the Extraction Cursor/Graticule Editor, click Preferences > Cursor/Graticule
Editor on the main workstation menu.
2. Click on the appropriate tab.
3. Adjust the cursor shape and color as required.
4. If you want to save the cursor for later sessions, click File > Save (Cursor... or
Graticule...).
61.8.2 Changing the Default Cursor

In order to set the default cursor in Socet Set, you must set the CURSOR_PREFERENCE
environment variable in the socet_config.bat (Windows) or .socet (UNIX) configuration file to
the full path to a cursor file (.crf).
For details on how to setup a configuration file see your platform specific SOCET SET System
Administration Manual. For Windows see section Setting up a SOCET SET Configuration
“socet_config.bat” File, or for UNIX see section Setting up a SOCET SET Configuration “.socet”
File.
WINDOWS
Once you have created your configuration file add the following line to it.
set CURSOR_PREFERENCE=<cursor_file>
where "<cursor_file>" is the full path name to the file. For example, a common cursor that
could be used is shown below:
set CURSOR_PREFERENCE=<install_path>/internal_dbs/PREF/red_circle.crf
UNIX
Once you have created your configuration file add the following line to it.
-setenv CURSOR_PREFERENCE <cursor_file>
where "<cursor_file>" is the full path name to the file. For example, a common cursor that
could be used is shown below:
-setenv CURSOR_PREFERENCE <install_path>/internal_dbs/PREF/red_circle.crf

If SOCET SET is running, exit via the File > Exit selection. Start up SOCET SET again and load
a project and image. The above default cursor should appear on the appropriate display.
61.9 Keyboard/Trackball Accelerator Mapping

The Keyboard/Trackball Accelerator Mapping window allows you to customize the hot-keys
used by SOCET SET. Hot-key refers to a key, mouse button, trackball button, or combination
which is associated with an event. For example, in Coordinate Measurement, <Alt> r on the
keyboard is the equivalent to clicking on the reset button.
To obtain this window, click Preference > Keyboard/Trackball Accelerator Mapping.
The Keyboard/Trackball Accelerator Mapping window’s selections are as follows:
Application Select the application to customize.

• Control Point Editor,
• Line of Sight,
• Coordinate Measurement, Triangulation,
• Interior Orientation
• PRO600/Microstation,
• Main Image Display
• Sketch
• Interactive Terrain Edit
• Main Menu
Change Mapping Change the current hot key for the selected event to a new one, or create a
new hot key for a previously unmapped event.
Add New Mapping Add a new hot key for the selected event. More than one key can be
associated with a particular event. For instance, by default, both F2 and the
left trackball button are associated with the “Recenter Image” event.

Remove Mapping Remove the selected hot key.

Mapping Window View a list of all the events currently available to the application and the
accelerators assigned to them. Selecting an item in this window sets the
current event for the Add/Remove/Change buttons.
Apply Apply changes. Does not close window.
OK Save and exit.
Cancel Exit; don’t save.
Restore All System Defaults Restores default settings for all applications.
Print Mappings Prints the mappings for the selected application.
61.9.1 Assigning an Accelerator

You can assign an accelerator by selecting the event name in the list and then pressing the Add
Mapping or Change Mapping button. A window appears telling you to press a key or trackball
button. The key you press will be assigned to the event.
There are three special events in the Main Image Display / Sketch application. These are Emulate
LMB, MMB, and RMB. These events can only be assigned to trackball buttons. Assigning a
trackball button to one of these events makes the trackball button act just like the X Mouse button.
The clutch button on the 3D Mouse allows the mouse to be moved without moving the extraction
cursor. When the clutch button is pressed, no movement information is sent to the applications.
The clutch button can be reassigned by setting the

environment variable NO_3D_MOUSE_CLUTCH and then using
the Accelerator Mapping GUI.
61.9.2 Keyboard Information

The software limits accelerator mapping to the keys common to most keyboards. The Find and
Cut keys on the Sun can not be assigned. If you attempt to use these keys, an error message will
appear asking you to select another key.
The Sun keyboards have two special keys, labelled Alt and <>. SOCET SET uses both these keys
as Alt.
61.9.3 Event Handling

When an accelerator key or trackball button is pressed the current application looks to see if it is
one of its accelerators. If it is not, then the accelerator is dispatched to RT. RT will then look
through the list of currently running applications (in reverse order of creation) and dispatch the
accelerator to the appropriate application.
61.9.4 Configuration Files

Accelerator information is stored in the file $HOME/.socet_keys.<hostname>. If this file does
not exist, then the following files are read:

<install_path>/internal_dbs/CONFIG/socet_keys
<install_path>/internal_dbs/CONFIG/
socet_keys.1.<trackball-name>
(First trackball)
<install_path>/internal_dbs/CONFIG/
socet_keys.2.<trackball-name>
(Second trackball)
61.9.5 Execution - Accelerator Mapping

1. To activate the Keyboard/Trackball Accelerator Mapping window, click
Preference > Keyboard/Trackball Accelerator Mapping on the main workstation menu.
2. Select the application you want to customize from the Application option menu. The events
for which hot-keys can be assigned will appear in the list box.
3. Select the event whose hot key you want to change in the box. Use the Change Mapping,
Add New Mapping, or Remove Mapping buttons as desired. When you select Change
Mapping or Add New Mapping, a dialog box will appear instructing you to press the key
you wish to assign to the event.
4. Repeat step three until the application is configured to your liking.
5. Repeat steps 2 through 4 for each application you wish to customize.
6. Click OK to save mappings or Cancel to exit without saving.
61.10 Tracking Sensitivity

The Tracking Sensitivity window controls the motion of the extraction cursor. To obtain this
window click Preferences > Tracking Sensitivity on the main workstation window.
You use this window to control the speed and direction of the extraction cursor, as well as to
determine which devices (mouse, trackball, etc.) are used for the motion.
Determine which of your devices (mouse, trackball, etc.) cause horizontal and vertical (XY), and
(Z) motion. By default, the mouse controls X and Y, while the trackball controls Z motions. But
you can reverse these roles, or achieve other custom configurations, by entering non-zero
numbers in the XYZ fields. Make sure you enter zeros in the XYZ fields where you want the
device to have no effect.

Changing the numbers on the window will speed up or slow down the extraction cursor: larger
numbers will speed the cursor up, and smaller numbers will slow the cursor down. A slow moving
cursor may be desirable when making fine measurements during Interior Orientation and
Triangulation.
Each new sensitivity value that you enter takes effect as soon as you enter it followed by pressing
the Return key on the keyboard.
See the Tracking Sensitivity sections in the System

Administration Manual for specific pointing device types and
examples on how to set the tracking sensitivity.
Tracking Alignment gives you a variety of choices for alignment.

• Ground (Object)
• Oblique
• Oblique XY-Object Z
• Close Range
These alignments determine whether the movement of the extraction cursor is relative to the
ground (i.e. object) or relative to the camera’s viewpoint. For aerial photography that is looking
downward (nadir) you should use the “Ground” alignment (this is the default). However, if you
are viewing oblique imagery, perspective scenes, or close-range photogrammetric images you
may choose to use one of the Oblique alignments
Close Range tracking allows you to change align the depth perspective when the Z ground
coordinate axis is not parallel to the depth perspective of the input imagery. The Z ground
coordinate axis is parallel with the depth perspective for vertical imagery. The change allows you
to move in and out of the screen (depth) using cursor interaction..
When using an oblique alignment, movement of the XY motion

device (e.g. mouse) may move the extraction cursor in Z
direction; and movement of the Z motion device (e.g. trackball)
may move the extraction cursor in the XY direction. Therefore,
if you need to move the extraction cursor perfectly vertical or
perfectly horizontal (in ground/object space) you should use
the “Ground” alignment.
The motion of some alignments are illustrated in the figure below:

Camera
Film
Ground Oblique Oblique XY
(Object) Object Z
Ground

61.10.1 Execution - Close Range Tracking

1. Open Control Point Editor, and define three points in the viewport.
2. Save selected ground points as a .gpf file. The new .gpf file is defined in the Control Point
Editor.
3. Select Preferences > Tracking Sensitivity. Under tracking alignment, select the Close
Range option from the drop down combo box.
If the previous setting was not Close Range, SOCET SET prompts you via the Select Ground
Point File for Close Range window to select a .gpf file for Close Range tracking. If the previous
setting was Close Range, a new .gpf file can be selected by clicking any other alignment option
first, then re-selecting the Close Range option.
61.11 Y Parallax
Some stereo models will exhibit excessive Y parallax, resulting from errors during Triangulation.
Such errors can arise during point measurement from incorrect ground control, insufficient
number of ground control points, etc. Your tip-off to these types of problems will take the form
of unusually high RMS values in the exterior orientation solution.
You will notice Y parallax when the extraction cursor is at ground level (i.e. X parallax has been
removed), but the cursors are not lined up vertically relative to the same piece of image detail.
This will assist you in generating a ground bias to account for the difference which will be applied
to the math model for each image.
61.11.1 Execution - Y Parallax

1. To adjust the Y parallax, first clear the X parallax by using the Z control to put the cursor
on the ground. Putting the cursor on the ground consists of adjusting the Z control until the
extraction cursor is positioned horizontally on the same piece of image detail in each of the

two images. Once you have removed the X parallax, you will notice any Y parallax if the
extraction cursors are not aligned vertically on the same piece of image detail.
2. Click Tools > Y Parallax on the main workstation window. This will lock the left image.
The other image can be moved in X and Y ground until the Y parallax is cleared.
3. Now select Y Parallax once again to turn Y Parallax off.
61.12 Project Data Review

The Data Review tool is obtained by clicking Project > Data Review, and choosing one of three
modes which provides a means to quickly review all available images, DTMs, or feature
databases in the current project. The three modes are: Image Information, Terrain Information, or
Feature Information.
This sampling of Data Review windows is displaying

information with Feature data file in the forefront.
When the Project Data Review window appears, the footprints of all the available objects of the
selected type are graphically displayed in the main console window. You may select a particular
item by either clicking on its footprint with the extraction cursor, or highlighting its name in the
“Items” list. When an item is selected, information about its physical characteristics will appear
in the “Object Characteristics” list, and an audit trail of processes applied to the selected object
will appear in the Process History list.
The Data Review tool determines and graphically draws the ground area covered by image,
terrain, and feature files within a project.
Images, DTMs, and Feature Files created with versions prior to

V3.2 will have incomplete audit trails.

The footprint for each file type is drawn in a different color according to the following table:
FILE TYPE COLOR
Image file Yellow
Terrain files Orange
Feature files Blue
61.13 Stereo Model Manager

You use the Stereo Model Manager when you want to sequentially display a series of images on
the main image display. It is an alternative to the “image load” action you use on the File
pulldown of the main menu. The Stereo Model Manager will save you a lot of time when you have
a large number of images that you want to display over and over, or when you want to repeatedly
go back and forth between two image pairs. To obtain this window click File > Load Stereo
Model, or click File > Load Images, then click Stereo Model Manager... on the Image Loader
window.
A stereo model consists of a pair of images. You assign a name to each model. The Stereo Model
Manager maintains the list of models you have created in your project, called the model list.
You can select a model from the list models and tell the Stereo Model Manager to display it; the
Stereo Model Manager will load the pair of images that comprise the model onto the monitor.
When working with large strips or blocks of imagery you will accumulate a number of models in
the model list. You can use the Stereo Model Manager to identify a sub-set of models for a work
session, called the display list. The display list is a circular list of models that you can display
sequentially by clicking a single button or single key on the keyboard.
The support files that make up the currently selected model in the Model List are displayed at the
top of the window.
The Stereo Model Manager window functions are as follows:

FUNCTION DESCRIPTION
Support Files Left/Right Display the names of the left and right image support files that comprise
the current model. You can create a model that consists of only one image
if you wish.
Model List Display a scrolling list of the models you have created for the current
project.
Create Pop up the image selection dialogue to prompt you to pick the images for
the new model. The default name for the model is comprised of the two
images you selected; you can edit this name if you desire.
Delete Delete the selected model from the model list.
Load Model Load the images associated with the model you selected in the model list
onto the monitor. Pressing the Numeric Key Pad (5) on your keyboard will
do this also. See “Accelerator Key Commands,” Appendix J.
Display List Display a scrolling sequential list of images to display. This is a subset of
the images in the project model list.
Add Add the selected model to the display list. Double-clicking a model name
in the model list will do this also.
Remove Remove the selected model from the display list. Double-clicking a model
name in the display list will do this also.
Next Load the images associated with the next model in sequence in the display
list onto the monitor. Pressing the Up (up-arrow) key on the numeric
keypad will do this also. See “Accelerator Key Commands,” Appendix J.
Prev Load the images associated with the previous model in sequence in the
display list onto the monitor. Pressing the Dn (down-arrow) key on the
numeric keypad will do this also.
Save Model Data Saves the Model and Display lists to the project model file.
Close Exits the Stereo Model Manager window.
61.13.1 Execution - Stereo Model Manager

1. Start by clicking File > Load Images on the main workstation menu.
2. Start the Stereo Model Manager by clicking Stereo Model Manager on the Image Loader
window.
3. To create a new entry in the Model List, press Create.
4. In the Create Stereo Model window, pick a left and a right image. Enter a model name, then
click OK. Cancel will return you to the Model Manager window without creating a model.
5. To delete a model, select the model name in the Model List, then press Delete.
6. To load a model on the workstation, select a model name in the Model List, then press Load
Model. The Stereo Model Manager loads the images associated with the model onto the
workstation.
7. To add a model to the display list, select a model name in the Model List, then press Add.
Alternatively, double-click on a model name in the Model List window.

8. To remove a model from the display list, select a model name in the Display List, then press
Remove. Alternatively, double-click on a model name in the Display List window.
9. To save the lists of models, press Save Model Data on the Image Loader window.
10. To cycle through the models in the Display List, press Next and Prev.
11. To exit the Model Manager, press close on the Stereo Model Manager window.
61.14 Quality Statistics

Quality Statistics provides a way to generate various statistical data to check and assist in assuring
the accuracy and integrity of your orthophoto and DTM products.
61.14.1 When to run Quality Statistics

You run the Quality Statistics immediately following Triangulation, Automatic Terrain
Extraction, or Interactive Terrain Editing. Quality Statistics measures the accuracy of the sensor
model solution or the DTM. Some of the modes of Quality Statistics require you to prepare a
Check Point file (containing known good ground points) before running Quality Statistics.
CHECK MEASURED
POINT POINT
FILE FILE
QUALITY
STATISTICS
File
Statistical
Report
This can be done by clicking Preparation > Import > ASCII Ground Points on the Main
Workstation window. A check point file contains ground coordinates whose locations in the
image are known. ground control points are often used as check points. The format of the check
point file is the standard workstation ground point file format (.gpf extension). To obtain the
Quality Statistics window, click Products > Quality Statistics, and choose which comparison you
desire.
See “File Organization,” Appendix B for more details.

61.14.2 Comparison of a Check Point File to a Measured Point File

You can run a comparison of a check point file to a measured point file to generate a statistical
report of the ground coordinate differences (mean, standard deviation, and RMS). You typically
use this to check the accuracy of the sensor model of images, especially orthophotos.
Prior to running Quality Statistics, you must first have a check point file, a measured point file,
and the image in which you want to measure the points.
To create a measured point file, you interactively measure the check point locations within the
image or orthophoto and save the measurements to a file. Then you run Quality Statistics to
compare the measured point coordinates to the original check point coordinates.
For comparisons of check point file to measured point file, if the status of the point is invalid
(USE? YES/NO flag is set to NO) in either the check point file or the measured point file, the
point is ignored and not used in the statistics.
61.14.3 Comparison of a Check Point File to a DTM

You can run a comparison of a DTM to a check point file to generate a statistical report of the
elevation differences (mean, standard deviation, and RMS). You typically use this check to test
a DTM against a set of known ground points that are randomly located within the footprint of the
DTM.
CHECK
POINT DTM
FILE
QUALITY
STATISTICS
File
Statistical
Report
Prior to running Quality Statistics, you must first import or generate a DTM. You must also
import or create the check point file. Since a check point file is in the standard ground point file
format (.gpf file), it is easy to create one by running Control Point Editor.
For comparisons of a DTM to a check point file, the elevation is interpolated from the DTM. If
the check point XY coordinates lie outside of the DTM, the check point is ignored and not used
in the statistics, and an error message is displayed.

61.14.4 Comparison of Two DTMs

You can run a comparison of two DTMs to generate statistical elevation differences (mean,
standard deviation, and RMS). You typically use this to check a DTM of known accuracy against
a new DTM of unknown accuracy. You may also want to run this type of comparison when you
have generated two DTMs using different strategies and want to compare the results.
DTM DTM
QUALITY
STATISTICS
File
Statistical
Report
Prior to running Quality Statistics, you must either import or generate the two DTMs.
When comparing two DTMs, the DTMs do not have to have the same spacing or boundary. The
X and Y coordinates of points in the first DTM are used to interpolate an elevation from the
second DTM. Areas of the DTMs that do not overlap are ignored. To eliminate blunders, after the
first set of statistics is computed, outliers are removed and the statistics are recomputed.
61.14.5 Check Point File vs. Measured Point File
The Check Point File vs. Measured Point File window’s selections are as follows:
File > Exit Exits Quality Statistics.


SELECT TO
Project File Select the name of the project that you want quality statistics performed.
Report File Select the name of an existing quality statistics report file, or to enter the
name of a new file. Automatically appends the .qsr extension. This field
is not available until you have selected a project. You can use the button
to the right of the field to open a file list.
Check Point File Prompt you to pick a check point file. You can use the button to the right
of the field to open a file list.
Measured Point File Prompt you to pick a measured point file. You can use the button on the
right side to open a file list.
Edit Report Start up the Report Editor and loads the quality statistics report file so that
you can edit or annotate it further
Start Start the comparison of the two input files. This button is not available
until you have specified both input files. Quality Statistics writes the
output report to the large scrolling window, as well as saving a copy in the
output quality statistics report file you specified. If the output report file
already exists, Quality Statistics prompts you to ask if you would like to
append to the existing file or if you would like to overwrite it.
61.14.6 Check Point File vs. DTM
The Check Point File vs. DTM window’s selections are identical to those of the Check Point File
vs. Measured Point File window, with the following exceptions:
SELECT TO
DTM Prompt you to pick a DTM. You can use the button to the right of the
field to open a file list.

61.14.7 DTM vs. DTM

The first DTM is “master” and only the posts in it that have FOM > = START_GOOD_FOMS
are utilized in the computation. The second DTM is the “slave” and for each post in the master
DTM, a post is interpolated in the slave DTM. The slave DTM post is always used, even if the
FOM < START_GOOD_FOMS (except slave post is ignored if OUTSIDE_BOUNDARY).
The DTM vs. DTM window’s selections are identical to those of the Check Point File vs.
Measured Point File window, with the following exceptions:
SELECT TO
Master DTM Prompt you to pick the master DTM to compare. You can use the button
to the right of the field to open a file list.
Slave DTM Prompt you to pick the slave DTM to compare.You can use the button to
the right of the field to open a file list.
You may invoke Quality Statistics from the main workstation menu or directly from a command
line prompt.
61.14.8 Executions
61.14.8.1 Execution - Invoking from the Main Workstation Window
1. Load your project onto the workstation by clicking File > Load Project on the main
workstation menu.
2. Click Products > Quality Statistics on the main workstation menu. Pick one of the three
comparison types to perform.
3. When the Quality Statistics window appears, click Report File if you would like to change
the default report file name, then click Open.
4. Select the two files to compare by selecting the next two buttons and picking the input file
names in turn.
5. Click Start to begin comparing the files. If the output report file already exists on disk, you
will be prompted to append to it or to overwrite it.
6. When the comparison is complete, you can view the entire report by adjusting the scroll bar
control at the right edge of the report window.

7. To edit the report file text, click Edit Report. The report file comes up in the Report Editor
window.
8. To exit, click File > Exit on the Quality Statistics window.
61.14.8.2 Execution - Invoking from the Command Line

There are 4 different ways to run Quality Statistics from the command line:
1. Running in interactive STAND ALONE:
% start_socet -single qstat -a <mode>
2. Running in INTERACTIVE with a setting file as input:
% start_socet -single qstat -s <setting_file> -a <mode>
3. Running in INTERACTIVE with a setting file as output, for preparing the setting file
interactively:
% start_socet -single qstat -output <setting file> -a <mode>
4. Running in BATCH with a setting file as input:
% start_socet -single qstat -batch -s <setting file> -a

<mode>
(See “Format of Setting Files” on page -4 for setting file formats)
61.14.8.3 Execution - Quality Statistics for an Orthophoto using Check Points

This execution sequence requires a check point file, a measured point file, and an orthophoto
image.
To create the measured point file, perform the following steps:
1. Copy the check point file (e.g. orth1_check.gpf) into another file for the measured
point values (e.g. orth1_meas.gpf). For Unix platforms, copy using the following
command:
% cp orth1_check.gpf orth1_meas.gpf
2. Load the orthophoto into the Console or Extraction monitor.

3. Click Preparation > Control Point Editor on the main workstation window.
4. Load your measured point file into Control Point Editor by clicking File > Select GPF on
the Control Point Editor window. Pick the name of the measured point file you created
above in step 1, then click OK.
5. In Control Point Editor, highlight the first point and click Move To. The extraction cursor
moves to the location of the first point.
6. Set the USE flag for the ground point to YES. Measure the point by toggling to the
extraction cursor and moving it to the check point on the image; toggle back to the mouse
cursor and click Sample and Accept. The ground coordinates update to the new measured
location, and the Valid flag resets to Yes. If you cannot measure a point, set its VALID flag
to NO so it will be ignored in the quality check.
7. Repeat the previous step for each check point. When you have measured all the check
points, select Save GPF from the File pulldown on the Control Point Editor window. This
saves all the measurements you just made to your measured point file.

8. Now invoke the Quality Statistics tool with the set of steps described in the section entitled
Invoking from the Main Workstation window.
61.15 Batch Processing - Quality Statistics

COMMAND LINE:
% start_socet -single qstat -batch -s setting_file -a 1
qstat qstat
KEYWORD DESCRIPTION
project_file Project filename (select from the .prj files in /<install_path>/data)
report_file Report filename (select a .qsr file in data directory or create a new
one). By default, the name of the report file is qualstat.qsr (with full
path to your project directory)
input_check_point_ Check point file, selected from .gpf files in your project directory
file (include full path name)
input_dtm_file DTM, selected from .gpf files in your project directory (include full
path name)
append YES or NO. YES appends the statistics results to the report file; NO
overwrites the file. The default is NO.
COMMAND LINE:
qstat qstat
EXECUTABLE NAME DESCRIPTION
qstat qstat
project_file Project filename (select from the .prj files in /
<install_path>/data)
input_check_point_ Check point file, selected from .gpf files in your project directory
file (include full path name)

EXECUTABLE NAME DESCRIPTION
input_meas_point_file Point measured file, selected from .gpf files in your project directory
(include full path name)
COMMAND LINE:
qstat qstat
KEYWORD DESCRIPTION
project_file Project filename

(select from the .prj files in /<install_path> /data)
input_dtm_file Master DTM, selected from .dth files in your project directory
input_dtm_slave_file Slave DTM, selected from .dth files in your project directory

61.15.1 Outputs
The primary output of Quality Statistics is the quality statistics report file. Quality Statistics
displays the results of its comparisons in the scrolling window in addition to writing the results
to the quality statistics report file in the project data directory. You can then use the Report Editor
to further edit and annotate the quality statistics report.
The contents and format of the quality statistics report file are as follows:
1. Name of the type of quality statistics check.
2. Project Name.
3. Names of the two files compared.
4. Results of the statistical comparisons.
Error messages. In each of the reports, the statistics are generated using the following formulas:
STATISTIC DESCRIPTION
Diff Difference in elevation.

d i = Z checkpoint – Z measured
Ave Diff Average difference.
⎛ n ⎞
⎜ ⎟
⎜ ∑ d i⎟ ⁄ n
⎝i = 1 ⎠
rms Root mean square difference.

⎛ n ⎞
⎜ 2⎟ ⁄ ( n – 1 )
⎜ ∑ i⎟
d
⎝i = 1 ⎠
std Standard deviation.

2
⎛ n ⎛ n ⎞ ⎞
⎜ 2–⎜ d ⎟ ⁄ n⎟ ⁄ ( n – 1 )
⎜ ∑ i ⎜ ∑ i⎟
σ = d
⎟
⎝i = 1 ⎝i = 1 ⎠ ⎠
outliers Differences that have absolute value greater than three times of std.
⎛ n ⎞
⎜ ⎟
⎜ ∑ d i⎟ ⁄ n + 3 σ
⎝i = 1 ⎠
percent blunders Percentage of blunders removed.

61.16 Image Information

Image Information displays information about any image currently displayed in any viewport.
When an image is selected, information about its physical characteristics will appear in the
“Header Data” section.
The Image Information window’s selections are as follows:
SELECT TO
Header Data Display the image path, format, bits/pixel, number of lines an samples,
number of bands, minification level, support file name, project name,
image ID, project coordinate system, datum, units, GSD, footprint vertices
load point, sensor type, and focal length.
Retrieve Line/Sample Display the current line/sample values at the extraction cursor.
Pixel Value Display the current pixel values at the extraction cursor.
Image Selection Toggle the Left/Right selection to display the image information for the
desired image.
Close Exit the Image Information window.
61.16.1 Execution - Image Information

1. Load one or more images onto the workstation monitors by clicking File > Load Images
on the main workstation window. Select the name(s) of the image(s) you want to load, then
click Load.
2. Start Image Information by clicking on the viewport workstation window.
3. Select the view and image that you want to display the image information for using the
option menu and the radio buttons on the Image Information window.
4. Toggle to the extraction cursor and move it to a new location to display the new line,
sample, and pixel values at the extraction cursor.

5. Click Close on the Image Information window to close the window.
61.17 Flicker Images

Flicker Images alternates between two images you have previously loaded in a stereo viewport.
This is useful when you want to compare two images to identify areas of change between the two
images. To obtain this window, click Tools > Flicker Images. You can flick back and forth
between the two images manually by clicking Flick; or you can let Flicker Images flick the
images for you by either entering a non-zero value in the Flicker Period field, or by adjusting the
Flicker Period slider.
The Flicker Images window’s selections are as follow:
File > Exit Exits Flicker Images and restores the images in the stereo viewport.
Help > Content Starts up on-line documentation.
SELECT TO
Flicker Period field Alternate back and forth between the images manually with the
Flick button, enter a zero here. To have Flicker Images alternate the
images for you, enter the number of seconds to dwell on each image
or use the slider to obtain the desired time.
Flicker Period slider Adjust this slider to vary the flicker period.
Flick Manually alternate between the two images.

61.17.1 Execution - Flicker Images

1. Load the two images you wish to compare into the stereo viewport by clicking File > Load
Extraction Images on the main workstation window. Select the names of the images you
want to load, then click OK.
2. Start Flicker Images by clicking Tools > Flicker Images on the main workstation window.
3. Click Flick in the Flicker Images window. The extraction displays the other image. Click
Flick several times in rapid succession.
4. With the mouse cursor, drag the Flicker Period slider to 2 seconds. The images begin to
alternate back and forth every two seconds.
5. Enter a zero in the Flicker Period field to stop the alternating.
6. Click File > Exit on the Flicker Images window.
61.18 Graphics Projection

Graphics Projection displays graphics overlays (such as terrain, features, or control points) from
an arbitrary viewpoint. This allows you to visualize a data file without requiring imagery to be
present on the main image display. The Graphics Projection uses a fictitious image named
GRAPHICS_ONLY.sup.
61.18.1 Execution - Graphics Projection

1. Select the Viewport you desire to view the graphics.
2. In the Viewport window, set the display to Mono.
3. Load an image which is approximately in the area of interest to the left image display. Click
Move to Image Load Point in the Viewport window. This is required to get the
extraction coordinate in the neighborhood where you will be drawing graphics.
Ensure the image is loaded into the left image.

4. Start the process that you will be viewing graphics from. This is usually Interactive Terrain
Editing (ITE), Feature Extraction, Annotation, or Triangulation. If possible, turn
“Auto Draw” on in this process. Draw the graphics over the image.
5. Load GRAPHICS_ONLY.sup to the left image display.
DO NOT press the Move to Load Point button. This would

cause GRAPHICS_ONLY.sup to use the default load point for
reloading and may not be near the area of interest.
6. Click Preference > Graphics Projection on the main workstation window. A window will
appear that controls the display angle and zoom for the GRAPHICS_ONLY image.
When you are using the GRAPHICS_ONLY pseudo image, you

must set the viewpoint to be near the objects you are trying to
visualize (terrain or features). For features, use the “MOVE TO”
operation in the feature extraction window; for terrain, use the
“MOVE TO POINT” operation in the Coordinate Measurement
window.
7. Move the extraction cursor to the center of the region you are interested in. Click Set
Viewpoint on the Graphics Projection window.
8. Adjust the Azimuth, Elevation Angle, Zoom Scale and Vertical Exaggeration slider bars to
achieve the viewpoint that you desire. You can also change the minification level on the
Display Utility.
9. Refresh the image display by clicking Recenter on the trackball or “F2” on the keyboard.
10. Repeat steps 7 to 9 if you want to change the viewpoint.
61.19 Change Elevation

The change elevation tool provides a graphical slider bar so you can adjust the Z coordinate of
the extraction cursor without using the trackball. The change is based on a scale value and can be
as precise as the changes made with the real trackball. Furthermore, keyboard arrows can be used
to make fine changes to the elevation. To obtain this window, click Tools > Change Elevation
on the main workstation window. To close the window, reselect Change Elevation.
The Scale text field is used to control the scale of the Z slider. Higher scale values result in greater
change in elevation for every change on the slider. Lower scale values result in smaller changes
in elevation for every change of the Z slider.

61.20 Correlation Band Selector

The Correlation Band Selector is used to establish band weights for correlation activities
performed in Automatic Terrain Extraction, Automatic Point Measurement, and Interactive Point
Measurement. To obtain this window, click Preferences > Correlation Weights.
The calculation of correlation values is performed by merging the equally weighted pixel values
of all bands contained in an image. This equal weighting of all bands may not be the desired value
for all correlation activities.
The Correlation Values are stored in the Enhancement File of the selected image.
61.20.1 When to Run Correlation Band Selector

Run the Correlation Band Selector before ATE or APM when you have an image with two or
more bands, and you don’t want to use the default equal weights. This utility may be used when
an image contains more than one band to establish a unique weighting for the individual bands
contained in the image.
By establishing unique weights for individual bands, the effects of a band may be filtered to
improve the performance of the correlator.
The Correlation Band Selector window’s selections are as follows:
SELECT TO
Add Add files to the Image Files area

Remove Remove the currently selected file from the Image Files area with a RMB
click.
Band Weights View the Band Number, Correlation Value, and Weight for each band
contained in the image. The number of rows will adjust to the number of
bands contained in the image.

SELECT TO
Save Weights To Current Apply the Correlation Value to the file selected in the Image Files Area.
File
Save Weights To All Files Apply the Correlation Value to all files in the Image Files area with the
same or more bands than the selected file.
Close Close the Correlation Band Selector dialog window.
61.20.2 Execution - Band Selector

To use the Correlation Band Selector, use the following sequence of steps:
1. Load the desired project.
2. Click Preferences > Correlation Weights on the main workstation window.
3. Select Image Support file names to be weighted by right clicking for Add.
4. Select an image to be weighted by highlighting the name in the Image Files area.
5. Enter the desired weight in the Correlation Value column for each band. (The weight
column will automatically adjust when another band is selected).
61.21 DOQ Editor

Use DOQ Editor when you have created a 1996 format DOQ file and wish to change information
in the file header. DOQ Edit extracts the header of the DOQ file, starts a text editor with the
information, and saves the edited data back into the DOQ file. DOQ Editor enforces the proper
size on the header information so you do not have to worry about the proper header size when
increasing or decreasing the length of the lines or adding or subtracting lines. However, the
maximum line length for any header line is 80 characters, so do not extend lines beyond that
value.
DOQ Editor uses the text editor as defined in the system variable “EDITOR”. On Unix systems,
this can be defined in the configuration file in your home directory, e.g. “.socet_xxx” where
“xxx” is the name of your computer. For example, you may add a line such as this:
-setenv EDITOR /usr/local/bin/emacs

Good choices for Unix editors are Emacs, dtpad, or vi. On Windows stations, you can define the
EDITOR variable in “socet_config.bat”. For example, you may add a line such as this:
set EDITOR=c:\winnt\notepad.exe
Good choices for Windows editors are Notepad or Wordpad.
DOQ Editor saves the original header information in a backup file named after the original DOQ
file with a “_save” inserted in the file name. For example, if the DOQ file was named “xyz.doq”
the original header will be stored in “xyz_save.doq”.

61.21.1 Execution - DOQ Editor

1. Click Tools > DOQ Editor on the Main Workstation Window.
2. Navigate to the directory which contains the DOQ file you wish to edit, then click DOQ
file, then click OK.
3. The DOQ header information will be loaded into a text editor.
4. Edit the information you need to change.
5. Save the file and quit the editor.
6. The “Keep Changes?” dialog will appear. Click Yes or No.
61.22 Image Header Update

The image header update allows you to update verification information in the image file.
Use to know if the data you are viewing has been verified, the updated fields are available to allow
the verification information to be communicated to you. This will be used in the dissemination of
DEM’s and Orthophotos. These datasets will be stored in GeoTIFF and in NITF formats.
61.22.1 When to Use Image Header Update

After a GeoTIFF or a NITF file has been created, you are allowed to update the internal data items
to identify if the data has been verified, if the data is for system test, if the date the image was
verified, and the name of the location performing the verification.
61.22.2 NITF Fields

The verification information is located in the NITF Image Subheader. To allow ease of use,
ICOM1 is displayed as “Type”, which identifies the type of data stored in the individual image
subheader. The updates are then applied to ICOM2, ICOM3, and an ICOM4. ICOM2 contains the
verification information; this is displayed as “Quality Control”. ICOM3 contains the date; this is
displayed as “Review Date”. ICOM4 contains the name of the location; this is displayed as
“Organization”.
61.22.3 GeoTIFF Fields

The verification information is stored in the GeoAsciiParams tag number 34737. The KeyID’s are
used to access the verification information. KeyID 33028 contains the verification information,
and is displayed as “Quality Control”. KeyID 33029 contains the date, and is displayed as
“Review Date”. KeyID 33030 contains the name of the location, and is displayed as
“Organization”.
61.22.4 Starting Image Header Update

To start Image Header Update, select Tools > Image Header Update. Typically, you would open
the image file, view the existing information, update the items that you desire, and then save the
updated image file.
The image file must already have allocated space to store this information, if the storage has not
been allocated the information can not be updated. A GeoTIFF file must contain keys 33028,

33029, and 33030. A NITF file must contain at least four image comments in the NITF image
subheader.
The verification information can be one of these four values.
• Verified
• Unverified
• Test Verified
• Test unverified
The date information will be stored in the yyyymmdd format.
The Update Image Header window’s selections are as follows:
File > Open Prompts you to pick the image file and then opens the image file.
File > Save Saves the imge file.
File > Exit Exits Update Image Header window.

SELECT TO
Segment If more than one image segment is available, this will allow you to select
the individual image segment, or select “All” to allow changing all the
image segments.
Type Displays ICOM1 information if a NITF file was selected.
Quality Control Allows you to view existing verification information, or to update the
verification information.
Review Date Allows you to view existing date information, or to update the date
information.
Organization Allows you to view existing location information, or to update the location
information.
Message Box Displays operation information if needed.
61.22.5 Example Execution - Image Header Update

1. Select File > Open
2. Browse the file selection dialog window to the appropriate folder, select the desired
GeoTIFF or NITF file, and click OK.
3. View the information displayed in Type, Quality Control, Review Date, Organization
information.
4. (Optional) Select Segment if more than one segment is available to be viewed. If “All” is
selected, then any updates done to Quality Control, Review Date and Organization will be
applied to all the image segments (when the save is selected).
5. (Optional) Update the Quality Control, Review Date, and Organization information.
6. (Optional) Select File > Save to save the updates.
7. Select File > Exit to exit the application.
61.23 Configuration Editor

Configuration Editor creates and edits configuration files that contain environment variables
needed to run SOCET SET. Only a small set of the environment variables is required to run
SOCET SET. But many are provided for user preference and configurability.
It is important to understand the naming convention of the configuration files and how they are
used when starting up the software before you start editing the configuration files.
When starting the software, it reads the configuration file(s) to set up the environment variables.
The configuration files have the following naming convention and are read in the following order:
On UNIX, the file name has the format of .socet_<host> or .socet. The order in which they are
read is:
/<install_path>/.socet_<host>
/<install_path>/.socet

$HOME/.socet_<host>
$HOME/.socet
On Windows, the file name has the format of socet_config_<machine_name>.bat or
socet_config_<username>.bat or socet_config.bat. The order in which they are read is:
$HOME\socet_config_<machine_name>.bat
$HOME\socet_config_<username>.bat or $HOME/
socet_config.bat or any file name in the $HOME directory
(need to use –config option when start up SOCET SET to
specify the file).
If the same environment variable appears in multiple files, the value that is read last will override
all previously set values.
The Configuration File Editor is invoked automatically after the software is installed and anytime
while running the software. To invoke it while the software is running, click Tools >
Configuration Editor on the main workstation window.
The Configuration Editor windows’s selections are as follows:
File > New Open a new configuration file.

<Ctrl>N
File > Open Open an existing configuration file.

<Ctrl>O
File > Save Save the modifications you made to the current opened file.
<Ctrl> S
S

File > Save As... Save the current opened file under a different file name.
File > Exit Exit the Configuration Editor window.
Edit > Add Add new variables to the file. This will popup another window which lists
all the available environment variables to choose from. From this Add
window, you can also add variables that are not from the list.
Edit > Delete Delete the current highlighted variable.
Edit > Find Search for a variable.

<Ctrl>F
Edit > Sort Sort the variable list. Click this again to reverse the sort order.
Edit > Undo All Undo all changes made since opening the file.
SELECT TO
User Settings Variable Identify a variables in the current opened file. This also reflects newly
added variables that have not been saved.
Description Describe the highlighted variable. If the current highlighted item maps to
more than one variable, there will be more than one entry in the box.
Edit Edit the value of the current highlighted variable. Under the description
box, you will see the environment variable name that is being edited along
with a explanation of the variable. If there are multiple environment
variables being edited, you will see multiple boxes.
OK Accept the changes made to the current highlighted variable.
Cancel Cancel the changes made to the current highlighted variable. This will
restore the value back to the original form.

This is the Add window that shows the available environment variables to be added. This window
is popup by clicking on the Edit > Add or clicking on the Add action button.
The Add window’s selections are as follows:
SELECT TO
Available User Settings Select from the list of available environment variables to be added.
Added User Settings Select from the list of the variables that have been moved from the
available list to be added to the current opened file.
Move the highlighted variable from the available list to the added list.
Return the added variable to the available list.
Sort Sort the variable list.
Find Search for a variable.
New Add new variable that does not exist in the available list. This will popup
another window that allows you to enter the variable name you want
added.
Delete Delete the current highlighted new variable which was added using the
New button.
Edit Edit the current highlighted new variable which was added using the New
button.
Description Describe the highlighted variable. If the current highlighted item maps to
more than one variable, there will be more than one entry in the box.
OK Accept the changes made in this window and return to the main window.
All variables that are in the Added variables box will be removed and
inserted into the Variables box in the main window.
Cancel Cancel the changes made in this window and returns you to the main
window.
61.23.1 Execution
61.23.1.1 Open a New Configuration File
1. Click File > New or click on the New action button.

2. Click Edit > Add or click on the Add action button to start adding new variables
3. Highlight each variable and click on the Edit button to edit the value for each variable.
Some variables may have default values. In that case, you don’t have to edit it if you can
accept default value.
4. Click File > Save or click on the Save action button to save the file. You will be prompted
to enter the file name. If you are saving into an existing file, the existing file will first be
backup before the saving takes place. The backup file will have the same file name with the
suffix .keep.
5. Click File > Exit to exit the application. If the changes have not previously been saved
when exiting the application, you will be prompted to do so or loose all changes made.
61.23.1.2 Open an Existing Configuration File

1. Click File > Open or click on the Open action button. Select an existing file, then click
Open.
2. Modify the list of variables by either:
a. Adding: click Edit > Add or click on the Add action button to start adding new
variables
b. Changing: highlight the variable to be changed, then click the Edit button to edit its
value.
c. Deleting: highlight the variable to be deleted, then click Edit > Delete or click on the
Delete button to delete the variable.
3. Click File > Save or click on the Save action button to save the file. Before the saving takes
place, the file will first be backup. The backup file will have the same file name with the
suffix .keep. Alternatively, you can click File > Save As to save under a different file name.
4. Click File > Exit to exit the application. If the changes have not previously been saved
when exiting the application, you will be prompted to do so or loose all changes made.

Appendix A
Glossary
Context Menu
Right clicking your mouse either on the image or in the toolbar area will provide a menu of options.
<Text>
Here you will see an explanation of the term you are hovering over.
3D Mouse
This mouse has 10 buttons and a thumbwheel for Z movement of the extraction cursor.
Accelerator
Also known as Hot-Keys, are a keyboard key(s) used to perform an action that normally takes several
steps or that would require a mouse button action
Accuracy
The statistical error of the position of a ground point, stated in ground coordinates.
Absolute accuracy is the error with respect to ground truth (lat/long/elev).
Relative accuracy is the error with respect to another ground point (the error in the offset or distance
between the points).
Affine Transformation
A uniform stretching that carries straight lines into straight lines and parallel lines but may alter
distances between points and angles between lines.
Aim Points
In Perspective Scenes: these are optional points that can be placed along the path the viewer will look at
from each eyepoint. (See Aim Route)
Aim Route
In Perspective Scenes: a curved line used to enable the view direction to smoothly vary as the viewer
moves along the View Route. The viewer looks at Aim Points along the Aim Route.
Aliasing
Degradation of image quality during a resampling operation caused because the output image pixels are
too far apart. Aliasing can be ameliorated by increasing the resolution of the output image.
AAM
Adverse Area Map
AMSD
Adjusted Mapping Support Data
Annotation
An application used to draw graphical overlays quickly and without the constraints of the Feature
Extraction Tool. The task presents selectable icons, counting tools, and custom coloring. See also
Feature Extraction.
ARC
Equal Arc Second Raster Chart/Map—A map projection used by the NGA for ADRG and ADRI
products. Lines of latitude are perfectly horizontal and lines of longitude are perfectly vertical. The
latitude and longitude scales in arc-seconds are constant (but different) through the product. The earth
is divided into several zones, each with a different longitude scale, to keep distortion to a minimum.
AFE
SOCET SET Page A-1

Appendix A - Glossary
Automated Feature Extraction. Software tools that use computer vision techniques to automatically
delineate features.
Area Feature
A polygonal vector object, such as a lake or field. Contrast with line or point features.
ASCII
American Standard Code for Information Interchange.
Attribute
A characteristic of a feature. Attributes may be numbers, text strings, or enumerated types.
ATE
AutoSOCET
AutoSOCET is a fully automatic software that runs SOCET SET functions in the background.
Band
An image representing the data from a single portion of the spectrum. Two or more bands together
comprise multispectral imagery.
Bilinear Resampling
A method of resampling an image whereby each output pixel is derived from a weighted average of the
four nearest input pixels.
BIL
Band Interleaved. A storage technique for multi-spectral imagery in which all bands of a given line are
stored consecutively (e.g. Line 1 Red, line 1 Green, line 1 Blue, line 2 Red, etc.).
Block of Images
(1) A group of images processed by a single Triangulation job. A block consists of one or more strips.
The images in a block may or may not be arranged in a rectangular pattern. (2) A group of images
arranged in a more-or-less rectangular pattern collected by an aircraft making several parallel flight runs.
Breakline
A line on the ground that indicates a sudden change in terrain gradient, such as a ridge or stream.
BSQ
Band Sequential. A storage technique for multispectral imagery in which each band is stored
contiguously (e.g., entire Red band, then entire Green band, then entire Blue band); contrasted with BIL.
CADRG
Compressed Arc Digitized Raster Graphic
CCT
Computer Compatible Tape. Nine-track reel-to-reel magnetic tape media, 2,400 feet long.
Check Point
A ground point with a known location used to verify the quality of a Triangulation solution. Also called
a Diagnostic Point.
Console Monitor
The main computer screen used when operating the workstation. Used to display all alphanumeric
windows. May also be used to display imagery. Contrast with Extraction Monitor.
Control Points
Points on the surface of the earth that has its geodetic location known with a certain degree of accuracy.
Used as input to the Triangulation process.
Conjugate Points
The image points in two or more images that correspond to a single ground feature. Tie points are always
conjugate points. If a ground control point appears in both images of a stereo pair, then the two image
points are conjugate points.
Convergence Angle
For a stereo image pair: the angle formed by the two rays pointing from a point on the ground up at the
two camera stations. The convergence angle should be in the range 20 to 60 degrees to obtain good stereo
visualization.
Page A-2 SOCET SET

Convolution
A technique used to enhance an image. Can be used to sharpen, smooth, or detect edges in an input
image. Uses a ‘kernel’ which is a small matrix of numbers applied to each input pixel to yield a
corresponding output pixel.
Coordinate System
A system used for representing geodetic locations. Coordinate systems include UTM, Geographic, LSR,
and Grid / State Plane systems.
CVL
Computer Vision Laboratory. Refers to an imagery interchange format.
DAT
Digital Audio Tape.
Datum
A smooth ellipsoid approximating the surface of the earth, used as a standard coordinate reference
baseline for geopositioning. A datum is specified by five parameters: semi-major earth radius,
eccentricity (or flatness), and XYZ center offset. WGS 84 is the most common datum in use today, but
there are dozens of others, usually created on a per-country basis to support national mapping efforts.
All geolocations (i.e., the lat/long/elevation of a ground point) make sense only when related to a datum.
To avoid confusion, all locations within a given SOCET SET project must be specified relative to the
same datum. To compare two locations from two different datums you must perform a conversion.
Sometimes it is useful to utilize two separate datums: a horizontal datum for the XY measurements, and
a vertical datum for the Z measurements.
Datum, Horizontal
An ellipsoidal surface used as a basis for referencing XY location coordinates.
Datum, Vertical
A surface used as a basis for referencing Z location coordinates. There are two types of vertical datums:
ellipsoidal and geoid. An ellipsoidal vertical datum is a smooth spheroid, just like a horizontal datum.
The geoid is an irregular surface covering the earth that approximates mean sea level.
DCW
Digital Chart of the World—A vector product available from the NGA. A DCW contains information
from 1:1M scale ONCs and includes topological information.
DEM
Digital Elevation Model—USGS terrain file format.
DGN
The “DesiGN” file format.
Diagnostic Point
See Check Point.
DLT
Direct Linear Transform—A rational polynomial that may be used to approximate sensor models.
DOQ
Digital Orthophoto Quadrangle—A USGS product consisting of a digitized orthophoto image and
ASCII support data.
DPI
Dots Per Inch.
DPPDB
Digital Point Position DataBase.
DPS
Digital Production System—A digital mapmaking system of the NGA.
DRG
Digitized Raster Graphics—A digitized map.
DTED
SOCET SET Page A-3

Digital Terrain Elevation Data—NGA terrain file interchange format. DTED Level 1 spacing is 3 sec x
3 sec but changes above 50 degrees latitude. Each DTED Level 1 file covers a 1 degree x 1 degree cell.
DTM
Digital Terrain Model (or Matrix). A grid of elevation data points. The grid is aligned along the
coordinate system axes of the project.
DTM Point
Sampled point on DTM to be relocated. A DTM point together with a truth point is known as a tie point
pair.
DXF
Data Exchange Format—AutoCAD vector exchange format created by Autodesk, Inc.
Easting
The horizontal (X) coordinate of a grid coordinate system.
Element
A polygonal component of a volume feature (e.g., the side of a building is an element of the building).
Ellipsoid
An oblate spheroid used to roughly model the surface of the earth. There are many possible ellipsoids
available, parameterized by eccentricity and semi-major axis. When used as a datum an ellipsoid also
has an XYZ offset from the center of the earth. See Datum.
Epipolar Line
A lined formed by the intersection of the epipolar plane with (1) a horizontal ground space plane; or (2)
one of the images used to compute the epipolar plane. To visualize stereo, both the left and right images
must be oriented so the epipolar line is horizontal. Pairwise rectification will resample a pair of images
to achieve this orientation.
Epipolar Plane
For a given ground point visible in each image of a stereo pair: the plane passing through the point and
the two camera stations.
Epipolar Rectification
Given a pair of stereo images, epipolar rectification (or simply rectification) determines a transformation
of each image plane such that pairs of conjugate epipolar lines become co-linear and parallel to one of
the image axes (usually the horizontal one).
EPJE
Exploitation Preferred JPEG 2000 Encoding
ESD
Describes the location and orientation of the sensor.
Extraction Cursor
The cursor overlaying imagery on the Extraction Monitor used for geopositioning, feature delineation,
interactive terrain editing, point measurement, and other ground space pointing operations. Contrast
with the X cursor.
Extraction Monitor
A stereo-capable CRT dedicated to displaying imagery. Contrast with the Console monitor. The
Extraction monitor can display imagery in several modes, including stereo, split-screen, and single
image (i.e., mono).
Extraction Specification
A file that guides the operator during the feature extraction process and provides the proper data entry
fields. Extraction Specification also defines the types of features that an operator may put in a given
feature database.
Extrapolate
To Estimate a value.
Eyepoints
In Perspective Scenes: the location of the imaginary viewer for each frame in a fly-through route. For
example, a route with 500 scenes will have 500 eyepoints. The exception is that in the case of a route
Page A-4 SOCET SET

that has one or more pivot points, a route with 500 scenes will have less than 500 eyepoints. See also:
Way Points.
FAF
Fast Access Format.
False Easting / Northing
These are horizontal distance offsets added to raw coordinates in a Grid coordinate system (such as
UTM) that cause all coordinate values to be positive. Without False Eastings and Northings, some
coordinate values may be negative, which could be confusing in some circumstances.
Fast Format
An image format used on Landsat image tapes. Has less header information than the LTWG format.
FDB
Fast DataBase.
Feature
Objects located on the surface of the earth, such as rivers, roads, buildings, targets, lot boundaries, and
lakes.
Feature Attribute
A characteristic of a feature. For example, a road may have attributes such as width, number of lanes,
and material.
Feature Extraction
The process of graphically delineating and attributing features, and storing them in a feature database.
Feature Orientation
The process of adjusting the positions of features within a feature database so that they align with the
underlying objects in the imagery. This is used when a feature database of relatively poor accuracy is
displayed with imagery that has been well controlled.
Fiducial Points
These are special marks in an image which have known coordinates (usually in millimeters) relative to
the sensor frame which are used to solve for the image’s interior orientation. These are typically
embedded along the edge of a frame camera image, but sometimes appear in panoramic camera and
digital satellite images.
Figure of Merit
A quality metric assigned to each DTM post. Numbers range in value from 0 to 255 and indicates either
(1) the source of the post (ATE vs. area tool vs. geomorphic tool, etc.) or (2) the relative accuracy of the
output of ATE.
FOM
Figure of Merit is a numerical value assigned by the terrain extraction process.
FPE
Front-end Processing Environment.
Frame
A conventional camera, or the film or imagery produced by such a camera. Includes surveying cameras,
hand held cameras, and most reconnaissance cameras.
FSB
File Selection Box. A popup window in which the operator is prompted to select a disk file from a list.
GCP
Ground Control Point.
Geocoded
Rectified or ortho-rectified. For example, an orthophoto is a geocoded image.
Geodetic
Pertaining to the size and shape of the earth. A geodetic location is a 3-dimensional coordinate in an
earth-referenced coordinate system.
Geographic Coordinates
The coordinate system in which ground points are represented as latitude and longitude.
SOCET SET Page A-5

Geoid
The surface of the earth at mean sea level, idealized to pass through the continents. The geoid is not an
ellipsoid, but rather is an irregularly shaped surface approximating a pear. The geoid may be used as a
vertical datum.
GIS
Geographic Information System. A database system for storing and analyzing information about the
earth’s surface and objects on the earth’s surface.
GPS
Global Positioning System. A set of satellites that provide accurate ground control information.
Triangulation will use GPS-derived locations of Frame imagery.
Grid
A local coordinate system formed by flattening the surface of the earth using a map projection such as
Transverse Mercator (for areas with long N-S extents), Lambert Conformal (for areas with long E-W
extent), or Stereographic (for squarish areas) and establishing a rectangular grid coordinate system on
the flattened projection. State Plane Coordinate systems and UTM are grid systems.
Ground Point
An umbrella term including control points, tie points, and check points.
Ground Point File
A file containing ground points for a given project.
Ground Space
The space in which points on the surface of the earth are represented. Contrast with Image Space.
GPF
Ground Point File.
GSD
Ground Sample Distance—The horizontal distance (in ground space) between the centers of two
adjacent pixels in an image. The GSD may not be constant throughout an image, especially if the image
is oblique.
GSI
The Geographical Survey Institute is a national surveying and mapping organization of the Ministry of
Land, Infrastructure and Transport, and was established in 1869. The GSI is the only national
organization that conducts basic survey and mapping and instructs related organizations to clarify the
conditions of land in Japan
GUI
Graphical User Interface.
Histogram
An array of numbers which represent the pixel value distribution in a given image. The histogram is
often drawn as a graph in which the horizontal axis are the pixel values, and the vertical axis is the
number of pixels. The histogram is needed to perform certain image enhancement operations. For
multiband imagery, the histogram is called a scattergram or scatterplot.
HRC
Hierarchical Relaxation Correlation. The algorithm used by the Automatic Terrain Extraction process.
Icon
A small graphic symbol which represents a location, object, or button.
Image, Imagery
A digital aerial photograph stored as a two-dimensional array of pixels. An image may be single band
(i.e. monochrome) or multiband (i.e. multispectral). Imagery may be stored in a variety of formats
including TIFF, Tiled, CVL, and raster. Imagery may be digitized by the sensor (e.g., SPOT or Landsat)
or it may come from digitized film. Every image used by the workstation must be accompanied by a
Support File.
Image Enhancement
Page A-6 SOCET SET

The process of improving or altering the appearance of an image, usually to assist the operator with
feature extraction. Image enhancement operations include convolutions, histogram equalization, and
tonal transfer curve alterations.
Image Map
A hardcopy product consisting of a rectangular image surrounded by marginalia and overlaid with
graphics and tick marks.
Image Location
A directory in which pixel files are stored.
Image Point
The pixel in an image that corresponds to a given ground control point. Both the image point and GCP
are used during the triangulation process.
Image Pyramid
A set of overview images built from an original image. The original image is called the 1:1 image, and
the other images are created by averaging every four pixels to recursively create smaller overview
images, denoted as 2:1, 4:1, etc. Each minification level occupies 1/4 the disk space of the next higher
minification level. Also called an RRDS.
Image Space
The space in which pixels in an image are located. Contrast with ground space.
Interior Orientation
The process of computing a transformation from film space to image space that accounts for the position
and orientation of the photo when it was digitized or scanned. Requires the measurement of fiducials.
Interpolation
The process of determining the value of a function at a given point by extrapolating from neighboring
values. Used when resampling imagery during rectification. The two most common interpolation
techniques are Nearest Neighbor and Bilinear.
IO
(1) Input / Output. (2) Interior Orientation.
ITE
Interactive Terrain Extraction (or Editing). The process of manually reviewing and correcting a DTM,
usually performed after the ATE process is completed.
JFIF
JPEG File Interchange Format.
JNC
Jet Navigation Chart—1:2M scale maps produced by the NGA.
JOG
Joint Operations Graphic—1:250,000 scale maps produced by the NGA.
JPEG
Joint Photographic Experts Group.
KB
Kilobyte. 1,024 bytes.
Landsat
Imagery collected from one of several satellites operated by EOSAT.
Layer, Mosaic
A large, virtual image of indefinite extent. Populated with orthophotos during the mosaicking process.
Layer, Feature
A group of related features within a feature database.
LAE
Local Area Enhancement (similar to ROI).
LCR
Local Curvilinear Rectangular. A coordinate system.
LGSOWG
SOCET SET Page A-7

Landsat Ground Stations Operator’s Working Group.

Line Feature
A linear vector object such as a river, road, or fence. Contrast with area or point feature.
LOS
Line of Sight.
LSR
Local Space Rectangular. A coordinate system.
LWU
Logical Work Unit.
LTWG CCT
LGSOWG Technical Working Group. A generic tape format (nine-track reel-to-reel) magnetic media in
2,400 foot lengths, used for distributing imagery such as SPOT and Landsat.
Mass Points
Mass points can occur at any location, the more carefully selected, the more accurate the model of the
surface. Well-placed mass points occur where there is a major change in the shape of the surface, for
example, at the peak of a mountain, the floor of a valley, or at the edge (top and bottom) of cliffs.
Math Model
For a given image, the formula that converts between ground space and image space. The sensor model
embodies the sensor (i.e. camera) location, orientation, optics, and geometry.
MBR
Minimum Bounding Rectangle. The smallest rectangle enclosing a given object or set of points.
MB
Megabyte. 1,048,576 bytes.
MC&G
Mapping, Charting, and Geodesy. The application of SOCET SET to generate NGA-compliant feature
and terrain databases. Specifically, the use of special feature extraction specification files to generate
vector files for NGA products like JOG-A, TLM, VMAP-2, and Foundation Feature Data
MC&GFDES
MC&G Feature Data Exchange Standard. A vector interchange format used in the DPS.
Minification
The process of generating an image pyramid from an original image.
Minification Level
One of the images in an image pyramid.
MLA
Multispectral Linear Array. The multispectral SPOT sensor. Same as XS.
Model
(1) An image and its sensor model. (2) A stereo pair of images and their sensor models.
Monoscopic
A single image viewed by itself (without a corresponding stereo mate).
Mosaicking
The process of creating a large image by merging several smaller images. Involves blending the seam
lines in the geometric sense (warping to eliminate discontinuities) as well as in the radiometric sense (to
eliminate sudden shifts in brightness).
Motif
An Windowing system built upon X Windows. Includes a window manager, a library of convenience
routines, and a GUI look-and-feel standard.
MSE
Multiple Strategy Extraction (a mode of ATE).
MSL
Mean Sea Level. See Geoid.
MWM
Page A-8 SOCET SET

Motif Window Manger.

Mouse Cursor
The cursor is used for pointing and clicking on the alphanumeric windows of the Console Monitor.
Contrast with the Extraction Cursor.
MSD(i)
Mapping Support Data (per image).
MTFC
Modulation Transfer Function Correction—A sharpening filter applied to a raw image that removes any
smoothing effects caused by the sensor’s inherent design.
Multispectral
Imagery consisting of two or more bands.
N/A
Not Applicable.
NDCDB
National Digital Cartographic Database - the USGS’s digital map database, including DEM and DLG.
Nearest Neighbor
A method of resampling an image whereby each output pixel value is derived from a single
corresponding input pixel.
NGA
National Geospatial-Intelligence Agency (Formally NIMA (National Imagery and Mapping Agency))
NIIRS
National Imagery Interpretability Rating Scale—A system used to rate the level of detail discernible on
an image. The scale ranges from 0 to 9, with 0 the lowest rating. Generally speaking, an improvement
of GSD by a 2:1 ratio increases the NIIRS rating by 1.
NITF
National Image Transmission Format.
NITFS
Preferred JPEG 2000 Encoding (NPJE)
Northing
The vertical (Y) coordinate of a grid coordinate system.
NPJE
NITF Preferred JPEG 2000 Encoding
Obliquity
The angle formed by two rays emanating from a camera: one ray out the camera lens and one ray pointing
straight down; an image with zero obliquity is one looking straight down; an image with high obliquity
is looking off towards the horizon.
ONC
Operational Navigation Chart - 1:1M scale maps. There are 270 ONCs covering the world.
Orientation
(1) Triangulation, exterior orientation; (2) The three angles that define the viewing angle of a given
Frame image.
Orthophoto
The process of creating an orthophoto requires an input image, an accurate sensor model for the input
image, and a DTM for the image region.
Ortho-rectification
The process of generating an Orthophoto.
OSF
Open Software Foundation.
OTS
Off-the-Shelf.
Pan
SOCET SET Page A-9

Panchromatic; Panoramic.
Panoramic
A wide-angle image derived from film exposed in a cylindrical focal plane.
Panchromatic
Single band imagery in which the band covers most of the visual spectrum. Conventional black and
white photographs are panchromatic.
Pass Points
Tie Points connecting exactly two overlapping images.
Path
A directory on a computer disk.
Perspective Scene
An artificial image created by generating a view of what a camera would see if it were located at a given
point and looked in a given direction. The process of generating a perspective scene requires imagery,
sensor models for the imagery, terrain data and (optionally) feature data. Several perspective scenes,
each taken from a slightly different position, may be viewed in rapid sequence to create an animated ‘fly-
through’ effect.
PIDIDOP
Partial Image DIDOP. A portion of a full section DIDOP, recorded on CCT. The maximum size of a
PIDIDOP is 64 megapixels. Each pixel is 16 bits, uncompressed.
PLA
Panchromatic Linear Array—a SPOT sensor. Also denoted ‘P’.
PM
Point Measurement.
Point Feature
A feature represented by a single XYZ vertex, such as a water tower, target, or antenna. Contrast with
area or line feature.
Point Measurement
The process of sampling points in imagery to support a computational process such as Interior
Orientation, Feature Orientation, Image Registration or Triangulation. The points may be identified in
image space or ground space, depending on the intended purpose.
Polygon
A closed polyline that encloses an area.
Polyline
A set of connected line segments.
Posts
A single elevation data points. A DTM is a rectangular grid of posts.
PPDB
Point Position Data Base.
Project
A collection of data files (imagery, DTM, feature, control points, etc.) relating to a single geographic
area. When a project is created, the operator specifies a coordinate system and a datum, and all data in
the project must utilize that coordinate system and that datum. Projects are used to partition data,
simplify file management, and organize task flow.
PT
A Landsat preprocessing level. The imagery has been rectified.
Radiometric
Concerning image appearance. Specifically, a quantitative analysis of the visual quality of a digitized
image, using measures such as brightness, contrast, and histogram.
Raster Data
Any data which may be stored or represented as a two-dimensional array of data points as opposed to
vector data. Terrain grids and imagery are both examples of raster data.
Page A-10 SOCET SET

Rectification
The process of reshaping imagery to a vertical perspective by removing distortion due to camera
obliquity. Rectification is most often performed on a pair of overlapping images prior to stereo
visualization, in order to ensure that the images have the same scale and are rotated in the proper epipolar
direction. Sometimes the word rectification is used to mean ortho-rectification. Rectification involves
resampling.
Registration
The process discovering the correct ground location of data (terrain, feature, or imagery) whose location
is initially unknown or uncertain.
Registration, Image
This can mean either: (1) Triangulation; or (2) the process of resampling an image to align with another
image or with ground truth. SOCET SET accomplishes this latter operation using several techniques,
including Rectification (registers a single image to ground truth), Pairwise Rectification (registers two
images to each other and to ground truth), Orthophoto (registers a single image to ground truth utilizing
DTM), and Mosaicking (mosaics several orthophotos into a single output image).
Resampling
The process of reshaping an image by warping the image in a rubber sheet fashion. Rectification, ortho-
rectification, and minification are examples of resampling. Resampling uses interpolation to determine
output pixel values.
Reseau Mark
See Fiducial Point.
Residual
An error measure which is an indicator of the quality of the results of a process such as Interior
Orientation or Triangulation. Small residuals indicate that the solution is accurate.
RMS
Root Mean Square.
RPC
Rational Polynomial Coefficients.
RRDS
Reduced Resolution Data Set. See Image Pyramid.
SDTS
Spatial Data Transfer Standard—A data exchange standard for vector and raster data established by the
Federal government and used primarily by the USGS. SDTS is very general purpose.
SEA
Subtask Extraction Area.
Sensor
An aerial camera or satellite that collects imagery.
Sensor Models
For a given image, the formula that converts between ground space and image space. The sensor model
embodies the sensor (i.e. camera) location, orientation, optics, and geometry.
Sensor Model Parameters
The variables of a Sensor Model formula. For a given image, the values that—when plugged into the
Sensor Model—determine the ground-to-image transformation. For example, the sensor model
parameters of a Frame image are camera location (X, Y, and Z) and camera orientation (omega, phi, and
kappa). Sensor model parameters are usually provided with the image, but these values are usually
inaccurate and must be improved by triangulating the image.
Spline
A curved line fit through a set of discrete points.
SPOT
Satellite Pour l’Observation de la Terre. The corporation that manages the SPOT imaging satellites.
State Plane Coordinate Systems
SOCET SET Page A-11

Local coordinate systems used by county and state mapping agencies. There are about 130 state plane
systems, each one using a Grid coordinate system tailored for the region.
Stereomate
An image that will yield stereo visualization when viewed in conjunction with a compatible orthophoto.
Stereo Pair
Two overlapping images used to extract terrain and feature information. The convergence angle must be
large enough (usually greater than 20 degrees) to support geolocation.
Stereo Visualization
A method of visualizing three-dimensional objects by simultaneously displaying two images—left and
right—on a single CRT. The images may be wireframe figures or imagery. Stereo visualization requires
custom hardware to simultaneously display the two images. Stereo visualization is the only reliable
technique available to perform precise geolocation from imagery.
Strategy
A set of parameters used to tune an algorithm to a particular data set. For example, the ATE algorithm
has about ten strategies available. Each strategy is tailored to a certain kind of topography (e.g. rolling,
mountainous, flat, etc.).
Strip of Images
(1) A group of images whose footprints form a more-or-less straight line. A strip usually results from a
single flight run of an aircraft. Adjacent images in the strip overlap by a certain amount, such as 60%.
(2) A group of images input to the Triangulation process. One or more strips comprise a block. If the
imagery being triangulated is not arranged in a rectangular fashion (e.g. satellite imagery) then all the
images are stored in a single strip, even though their footprints may not be in a line.
Support Data
Generally, any data accompanying an image that describes the image size, source, history, or other
characteristics. Often stored as a header to the image. The format and content depends on the source of
the imagery. Also called Auxiliary Data. See Support File.
Support File
An ASCII text file that contains auxiliary information about an image, including footprint, sensor
parameters, ground sample distance, sensor type, photo date, and image size. Every image file must be
accompanied by a support file.
TARGA
Truevision Advanced Raster Graphics Adapter—an image file format.
TA
Task Analysis.
TAA
Task Assignment Area.
Terrain
Files containing information on the contour of the imageries surface.
Tie Points
Image points located in two or more overlapping images and used to solve the sensor model(s) during
the triangulation process. Depending on the context, Tie Points may mean that exactly four overlapping
images are involved. See Pass Point. In the context of DTM registration, a tie point consists of a point
on a DTM (DTM point) and a point to where this point should be relocated (truth point).
TIFF
Tagged Image File Format.
Tile
A method of arranging raster data or imagery on disk that stores small rectangular patches of data
contiguously. Tiled format generally yields faster retrieval time than the more straightforward raster
storage technique.
TIN
Page A-12 SOCET SET

Triangulated Irregular Network - The TIN model represents a set of DTM posts arranged arbitrarily.
When posts are joined with lines, the surface is a set of contiguous, non-grid patterned, non-overlapping
triangles. Within each triangle the surface is represented by a plane. The triangles are made from a set
of points called mass points.
TIP
Task Implementation Area.
TM
Thematic Mapper. A Landsat imagery product.
Toggle
The action of switching the mouse control between the Extraction Cursor and the X Cursor.
Topology
Optional information stored in a feature (i.e. vector) database. Topological information describes
relationships between neighboring features such as adjacency, overlap, and intersection.
TRA
Triangulation Rectangle Area.
Trackball
An input device, similar to a mouse, used to move the extraction cursor.
Transfer a Point
The action of measuring a point (either a Control Point or a Tie Point) in one image, and having
Triangulation automatically locate the point in other images.
Triangulation
The process of calculating sensor model parameters for one or more images based on control points and
tie points provided by the operator. Also called Exterior Orientation or Image Registration.
Truth Point
Sampled point where a DTM point is to be relocated. A truth point together with a DTM point is known
as a tie point pair.
TTC
Tonal Transfer Curve. A function that maps image pixel value to CRT pixel brightness. The TTC’s
horizontal axis is the input pixel value (often ranging from 0 to 255) and the vertical axis is the CRT
brightness.
TTD
Tactical Terrain Data—A vector product produced by the NGA. The scale is 1:50,000 and the format is
VPF.
Units, Project
Either feet or meters. The project units are used for vertical (Z) ground coordinate values. Also used for
horizontal (XY) values for all coordinate systems except in Geographic.
Universal Transverse Mercator
A grid system designed so that any point on the map can be designated by its latitude and longitude or
by its grid coordinates, and a reference in one system can be converted into a reference in another
system.
USGS
United States Geological Survey.
UTM
Universal Transverse Mercator. A 60-zone global coordinate system.
UIAF
Universal Image Assessment File
Vector Data
Geometrical data such as points, lines, and polygons. A Feature database contains vector data. Raster
data is alternative representation technique to vector data.
VITec
Visual Information Technologies Inc. A manufacturer of image processing products.
SOCET SET Page A-13

VPF
Vector Product Format. The vector database format used in VPS and TTD.
VPS
Vector Product Standard—a NGA vector database format and interface, used by the DCW product and
containing topological information.
USMDS
Universal Sensor Model Support Data.
Volume Feature
A three-dimensional vector object such as a building. Each polygonal side (including the roof) is called
an element.
Way Points
In Perspective Scenes: The vertices of the fly-through route. The imaginary viewer’s path is a splined
curve fit through the Way Points. See Eyepoints.
Weighted Mean
Weighted Mean interpolation uses the location in the input image to determine which neighboring pixels
should contribute to the output pixel. The output pixel is computed as the average of 1, 2, 3 or 4 input
pixels. Weighted Mean does not result in artifacts like nearest neighbor and does not smooth the output
as much as linear interpolation. It also executes faster than bilinear interpolation.
WDB
World DataBase—a high-level vector database of country coastlines; distributed by the CIA.
WGS
World Geodetic System. A horizontal control datum based upon a framework of marked points or
objects on the surface of the earth, the positions of which are commonly known with respect to the earth's
center of mass.
WVS
World Vector Shoreline—A high-level vector database containing country boundaries and shorelines
distributed by the NGA. The WVS scale is approximately 1:250,000.
XS
Multispectral (a SPOT image format). Same as MLA.
X Window System
GUI windowing system developed by MIT.
Y Parallax
The component of the horizontal distance between two ground positions, determined for the same
ground point and elevation using the point position in two images, in the direction orthogonal to the
epipolar direction.
ZX
An image processing board used in Sun computers.
Page A-14 SOCET SET

Appendix B
File Organization
File Organization covers various types of files SOCET SET
uses for inputting and outputting data.
B.1 Overview
A large number of data files are used in the workstation. Generally, they can be divided into four
groups:
1. Project data files. Data files such as DTMs or feature databases. These files are grouped
together based on projects.
2. Internal databases. These are static data files used by SOCET SET, usually for internal
purposes. These are described in See “Customizing Your Software Configuration,”
Appendix D for an explanation.
3. Image files and Layer files.
4. Settings files.
B.1.1 Project Data Files

A project is a set of data files related to a single geographic area. The data files include image
data, terrain data, feature data, as well as other related data (see below for a complete list). In
order to simplify file organization, files of two projects are never mixed within a single directory,
hence every project has a dedicated project subdirectory that contains all of its data files with the
exception of image files and mosaic files, which are stored in another directory due to their large
size. Storage for image files are called Image Locations. See detailed description of Image
Locations later on in this Appendix. See “Project Management,” Chapter 5 for more information
about projects.
The project directories can be located by looking at the project file directory which is found in
the environment variable PROJECT_FILE_PATH. The project file directory serves as an index
for the projects and it contains (1) all the project subdirectories; and (2) a project file for each
project.
For example, if a system has ten projects, the project file directory will contain ten project
subdirectories and ten project files. The project files always have the suffix .prj and they
define the project name, project parameters, and identify the corresponding project’s
subdirectory. The project name is the same as the project subdirectory name; for example, the
Carlsbad project would have a project file called carlsbad.prj, and a project directory called
/usr/geoset/data/carlsbad.
SOCET SET Page B-1

Appendix B - File Organization
oceanside.prj This is the carlsbad image location. It

contains image pyramids for the carlsbad
san_diego.prj project. Every image pyramid must have a
corresponding support file in the project data
directory. Image pyramids and support files
carlsbad.prj are created by the SOCET SET import
This project definition file applications.
contains:
1) project parameters (coord. Image Image
system, datum, units)
2) project image directory Pyramid A Pyramid B
pointer
3) project data directory pointer
This is the project directory /<install_path>/data .
It contains project definition files (.prj). Each project Support File Support File
has its own image and data directory. Using multiple A
directories to store data enables you to spread your B
data across your disks and to manage your data more
flexibly.
Each project definition file contains a pointer to an DTMs Feature Files
image directory and a pointer to a data directory. You
specify these directories when creating the project.
By default, the data directory for a given project is / This is the carlsbad project data directory.
<install_path>/data/project_name. Each project has its own data directory. The
data directory contains DTMs, feature files,
Images for a project, when imported, will be placed support files, and all other files unique to the
in the project’s image directory by default, unless you project. Each support file contains a pointer to
specify otherwise during the import process. the image pyramid in the project’s image
directory.
B.1.1.1 Project Data File Naming Conventions

Most SOCET SET applications use files for inputting and outputting data. For a given project,
the files are usually stored in the project’s data directory. The type of file (Feature file vs. DTM
vs. GCP file, etc.) is indicated by its suffix, as defined in the table below:
FILE TYPE (SUFFIX) DESCRIPTION
Automatic Contains list of files to participate in Triangulation.

Triangulation File (.atf)
Automatic Point List of parameters for tuning automatic point measurement in
Measurement Strategy Triangulation. For a complete description of the parameters, see the file
(.apm_strat ) <install_path>/internal_dbs/HATS/README.
Camera Contains definition of a camera, including its focal length and principal
Calibration (.cam) point offsets. Also contains location of fiducials and lens distortion
coefficient.
Class Algorithm Settings Tells DTM/Feature Merge what algorithm to perform on the feature classes
File (.cas) in the input feature database(s).
Page B-2 SOCET SET

Code File (.cds) Point codes are stored in files with an extension of .cds. All such files
are stored in the <install_path>/internal_dbs/MISC
directory. This file contains pairs of numbers, one pair per line. The first
number of each pair corresponds to a point code that is expected to be
found in an ASCII point file. The meanings of these numbers are user
defined and unimportant for DTM Import. The second number is a code
that identifies the function of that point. The current codes are: 0 (start of
a line); 1 (continuation or end of a line); 2 (single DTM point).
Any line starting with a # is ignored.
The first line is reserved for a comment line that provides the current
version number in the form:
# version: version_number
Enhancement (.enh) An ASCII text file containing image enhancement information about a
given image, including histogram, bias, gain, and operator preferences for
convolutions and Tonal Transfer Curve.
Extraction Cursor Definition Contains the definition of the extraction cursor shape, size, and color.
(.crf)
Feature Database (.ftr, A single feature (i.e., vector) database has these three files as well as a
.pnt, .txt) Feature Extraction Specification file (with suffix .spc). Feature files are
created by Feature Extraction and are used to delineate, store, and review
and change feature data for buildings, rivers, and roads.
Feature Extraction An ASCII text file that determines the kinds of features that may be stored
Specification (.spc) in a feature database. This file defines the types of attributes each feature
may have, and also defines the available feature classes. Templates of
commonly used extraction specifications are stored in the Internal
Database directory. When a feature database is created, the operator must
choose one of the available templates which is copied to the feature
database. The Extraction Specification templates are created or edited
using a simple ASCII editor.
Feature Extraction Feature Contains optional codes for identifying feature codes. Used in ARC_GEN
Attribute Code (facs.code export. The file must be present in /usr/geoset/internal_dbs/SPEC
directory. If it is not needed, it can consist of one line containing the value
0 to indicate no codes used.
Feature List File (.fls) A list of features resulting from a query operation.
Ground Points (.gpf) Ground space coordinates for a set of points, using the project’s coordinate
system and units. This is an ASCII text file. Points are identified by point
ID. The .gpf files are generated by Triangulation Point Measurement
and are used by Triangulation Solve. Standard deviations of multiple
measurements are also in the file.
Histogram Break Points Defines image histogram re-mapping points. Used by some image import
(.bps) functions to modify the image histogram during image import.
Image (.i, .ir, .il) Image pixel file in the workstation’s tiled format. Tile size is normally 128
x 128 pixels, but is selectable and must be in powers of two. Pixel size is 8
bits. Data is stored in a binary stream format. First pixel in first tile
corresponds to the first line, first sample in the image (upper left corner).
Pixels within a tile are ordered sample direction primary, line direction
secondary. Tiles in the image file are ordered sample direction primary,
line direction secondary. Image files with .i extension have either not
been rectified on the workstation, or have been ortho-rectified by
Orthophoto. Those with extensions .ir or .il appended have been
rectified on the workstation using Orthophoto. If a single image has been
rectified, the extension .il is used. If a pairwise (epipolar) rectification
has been performed, the left image has extension .il, and the right image
has the extension .ir.
SOCET SET Page B-3

Image Pyramid (.i_2, Minified images in workstation tiled format (see above). Minified images
.i_4, .i_8, . . ., .ir_2, are reduced resolution versions of the full resolution (.i, .ir, or .il)
.ir_4, . . ., il_2, il_4, images, .i_2 are reduced by half in both line and sample dimensions,
. . .) .i_4 are reduced by four in both line and sample, etc. Minified images
are generated by the Minification.
Image Support (.sup) ASCII text files that contains support (i.e., auxiliary) data for an image.
Each image used on the workstation must have a support file. This file
contains information about the imagery other than the pixel data itself
(which is stored in the image or image pyramid files). Support file data
includes: camera parameters, photo date, image file name, number of
minified images, image file size, rectification coefficients, interior
orientation coefficients, triangulation coefficients, coordinate system,
units, and other data. Support files are created by various SOCET SET
Import applications.
NOTE: You should never edit or change a support file.
Image Points (.ipf) An ASCII text file containing image points used during Triangulation.
Points are identified by point ID. Corresponding photo film coordinates
may be recorded as well. Image point files are generated Triangulation
Point Measurement. The number of observations and standard deviations
for multiple measurements are also in the file.
Interior Orientation Points Image coordinates (line and sample) and photo film coordinates (x, y) of a
(.iop) set of points used for interior orientation. (Typically, these are the
coordinates of the fiducial marks that are marked along the edges of the
photo by the camera.) Default .iop files are generated by Frame Import,
and are updated by Interior Orientation. Number of observations and
standard deviations for multiple measurements are also in the file.
Main Window Specifies the configuration of the main pulldown control window. This is
Configuration (.cnf) an ASCII file you can edit to customize the workstation look-and-feel.
Margin Template File Created interactively with Annotation. Used to overlay graphics on Image
(.obj) Map. Graphics are anchored either to the margin or to ground.
See “Annotation,” Chapter 45.
Model Data The model data for a project is stored in a file named
(model_data.txt ) model_data.txt located in the project directory. This file contains
definitions of models, and defines a model display list.
Any blank line or line starting with a # is ignored.
A line beginning with MODEL_NAME must be followed by a legal model
name (no blanks). A line beginning with LEFT_SUPP must be followed
by a legal file name designating the left support file associated with the
previous model name. A line beginning with RIGHT_SUPP must be
followed by a legal file name designating the right support file associated
with the previous model name. A line beginning with DISPLAY must be
followed by a previously defined model name. The Display list is created
from these designators in the order that they are found in the file. A file
generated by the model manager will create DISPLAY lines in the order
of the Display List when the file was created.
The first line is reserved for a comment line that provides the current
version number in the form:
# version: version_number
Perspective Scenes (.epf, These files are created and used by Perspective Scenes. They contain the
.psg, .scf, .spf) fly-through path that the operator has defined, as well as lock-on points,
pivot points, eyepoints, and look angle. These files generally appear as a
group.
Page B-4 SOCET SET

Project (.prj) An ASCII text file located in the project file directory indicated by the
PROJECT_FILE_PATH environment variable. This file contains the
project data path, information on the coordinate system type, unit of
measure types, the footprint of the project data expressed in radians, the
ellipsoid datum, and datum associated parameters. This file is generated by
Create Project.
Portable Document Format These files are documents for On-line Help.
(.pdf)
Report Text File (.rep) ASCII text files created by various SOCET SET applications within
SOCET SET. You can view, edit, and print these files using the standard
Unix text processing utilities.
Text Report: Text file you create with the Report Editor.
Feature Mensuration Report: Created by Feature Mensuration in Feature
Extraction.
Triangulation Solution Accuracy Quality Assurance Report: This file is
generated by Triangulation when you accept the solution result. It contains
lists of the input image points and their associated residuals for each image
you selected to participate in the adjustment.
Strategy List (.msl) This file is built by Create DTM. A Multiple Strategy List file contains the
polygons used to create the DTMs and the multiple extraction strategies
that are assigned to each DTM.
Terrain-DTM (.dth, DTM (Digital Terrain Model) files are created by Create DTM and are
.dte, .dtp, .dtf) populated by Automatic Terrain Extraction and Interactive Terrain Editing.
The .dth file is ASCII text, containing information about the DTM such
as boundaries and post spacing. The .dte file is a binary file of
elevations for all posts in the DTM grid, starting in the southwest (or
minimum X, Y) corner, ordered X primary, Y secondary. Elevations are
stored as 32-bit floating point values. The .dtf file is a binary file of
Figures Of Merit (FOMs) for all posts in the DTM grid, in the same order
as the .dte file. FOMs are stored as 8-bit values ranging from -127 to +100.
The .dtp file contains precision information about each post.
Text (.txt) Text files containing the on-line help data. Use this suffix when creating
textual reports or memos with a text editor.
Texture Patch Data (.atp) Feature database texture patch data.
Texture Patch (.pat) Feature database texture patch images.
Tie Point Pattern (.tpp) Contains coordinates of tie points used by automatic tie point measurement
in Triangulation.
Unbounded Layer Header Header file that describes the unbounded mosaic layer database. Contains
File (.unb) fields indicating location of the layer data subdirectory, bands, depth,
image type, tile size, etc.
B.1.2 Image Locations

A single image consists of a support file and one or more pixel files. The support file is always
stored in the data directory of its project. However, the pixel files are not necessarily stored in
the project data directory. Because pixel files can grow to be quite large, it is usually not feasible
to keep all pixel files in one directory or even on one disk. Therefore, a special mechanism—
Image Locations—is used to manage the storage of pixel files.
The purpose of Image Locations is to make it easier to store imagery:
• Image Locations make it easy to move pixel files around on your disks.
SOCET SET Page B-5

• Image Locations make it easy to restore project data from backup tapes.
• Image Locations make it easy to send project data from one site to another.
• Image Locations eliminate the need for you to manually edit support files.
Without Image Locations, you would have to spend a lot of time managing pixel files and
interacting with confusing operating system procedures. Image Locations do all the difficult
operating system work for you, so you can focus on more important tasks.
Image Locations are directories in which pixel files (images) are stored. Each image location
consists of a directory and a shorthand name. When you run SOCET SET, you only see the
shorthand names.
Your site must have a list of one or more image locations.
All image (pixel) files are stored in an image location (there are some unimportant exceptions to
this, discussed below).
You can store other kinds of files in image locations besides image files.
The images of a single project can be put in more than one image location.
An image location can contain images from more than one project.
B.1.2.1 Establishing Image Locations

The list of image locations for your site is in the file called <install_path>/
internal_dbs/DEVICE/location.list. You need to put at least one directory in this
list before you start SOCET SET the first time. Thereafter, you do not have to worry about this
file, unless you run out of room for storing your pixel files. If you want to put the new pixel file
into a directory that is not listed in the image location list, you must edit the image location list
and add the directory into the list. Then run the application again and select the Image Location
button and the new image location will appear in the list.
See “Customizing Your Software Configuration,” Appendix D contains detailed instructions on
how to create and change your list of image locations.
B.1.2.2 Selecting an Image Location for New Images

Image Locations are used when you import a new image (Frame Import, SPOT Import, etc.), or
generate a new image (Orthophoto, Perspective scene, Image Map, etc). The main windows of
these applications contain an Output Image Location button which, when clicked, displays a list
Page B-6 SOCET SET

of the image locations. You use the Output Image Location button to select an Image Location
where the new image will be placed.
B.1.2.3 An Example
You decide that you will store your pixel files in directory /x/y/z. You add this directory to your
image location list and you give this directory the shorthand name BIG.
You then create a project San_Diego. You import several SPOT images. The SPOT Import
window contains an Output Image Location button that allows you to select a location for the
imported pixel files. You select the location BIG, and the SPOT pixel files go into the /x/y/z
directory.
You can now use this imagery in all SOCET SET applications.
Later, the BIG image location fills up. Your System Administrator adds a new disk to your
network. A directory on the new disk is added to the image location list and given the name
EVEN-BIGGER. To make room on BIG for other data, the system administrator then moves all
of the pixel files from BIG to EVEN-BIGGER.
The next time you try to use the imagery, SOCET SET looks in the BIG image location and tries
to get the pixel files. It notices that they aren’t there, so it then searches all the other directories
in the image location list until it finds the files in EVEN-BIGGER. It then updates the information
in the image support file to reflect this change in location and reads in the pixel files.
You now run Orthophoto. To select the directory for the output orthophoto to go in, click
Location in the Orthophoto window. A window will pop-up that contains a list of all the available
image locations and how much free disk space they have. You select an image location that has
enough space to hold the imported images.
B.1.2.4 Moving Images Around

If you move a pixel file from one directory to another, you do not have to edit the associated
support file, provided that the new directory is in the image location list.
If you move a pixel file from an image location to a directory that is not in the image location list,
you will not be able to use that image (support file) in SOCET SET until you add the new
SOCET SET Page B-7

directory to the image location list. Alternatively, if the support file contains the exact name of
the pixel file’s directory, then you do not have to add the directory to the image location list.
If you back up a project to tape, then restore it to disk, you can put the pixel files in any
directories, provided that the directories are in the image location list.
If you receive an SOCET SET project from another site and put the project data onto your disks,
you can put the pixel files in any directories, provided that the directories are in the image
location list.
If you move an image from one directory to another, then the first time that SOCET SET tries to
access the image, it will pop-up a window asking you to confirm the new location.
B.1.2.5 Images With Identical Names

You can store images from two or more projects in a single image location.
However there is one important exception to this rule: you cannot store two images with the same
name in a single image location. This limitation arises because the operating system prevents you
from storing two disk files with identical names in a single directory.
If you run Triangulation on strips of Frame imagery, you may encounter this limitation frequently
because Triangulation often utilizes a uniform naming convention whereby the images are named
1_1, 1_2, 1_3, etc. For example, if you are running Triangulation in projects PROJ_A and
PROJ_B, both projects may have an image called 1_2.
When you have images with identical names in two projects, you must store the images in two
different image locations. For example, if you have an image named 1_2 in project PROJ_A and
PROJ_B, and you have two image locations LOC_X and LOC_Y, you cannot store images from
both projects in LOC_X. Instead, you could store image 1_2 from project PROJ_A in LOC_X
and image 1_2 from PROJ_B in LOC_Y.
If you run Triangulation a lot, this situation arises frequently and it may be confusing trying to
keep track of all the imagery. One way to simplify the management of your imagery in this
situation is to always store all images from a single project in a dedicated image location. If you
elect to do this, there are two approaches that you can take:
a. Have a permanent set of image locations (have at least as many image locations as the
maximum number of projects you expect to work on simultaneously); every time a
project is created, select an unused image location and store all images from that
project in that location; when the project is completed, the image location may be used
by other projects.
b. Every time you start a new project, create a new image location that has the same name
as the project; store all images for that project in this new image location; when the
project is completed, delete the image location.
B.0.1 Finding Images Quickly

Some operators prefer to be able to quickly and easily access all pixel files of all projects. The
simplest way to achieve this is to have a single directory, such as <install_path>/images,
with softlinks pointing from it to all the image locations. For example, if you have an image
location called loc_a defined as follows:
% loc_a /export/home/tiger2/disk_a
Then you can create a soft-link with the following command:
Page B-8 SOCET SET

% ln -s /export/home/tiger2/disk_a /usr/geoset/images/loc_a
This command, if performed for every image location, will allow you to quickly access all pixel
files from the <install_path>/images directory.
These softlinks are optional, and are not supported in

Windows.
SOCET SET Page B-9

Appendix C
Feature Database and Extraction

Specification
Feature Database and Extraction Specification identifies
characteristics and class of a feature in the database.
C.1 Feature Database

A feature database contains information about features. Features are objects located on the
surface of the earth, such as rivers, roads, buildings, targets, lot boundaries, and lakes. For each
feature the feature database contains:
• Delineation (i.e. shape and location)
• Attributes (i.e. characteristics; see description of Extraction Specification below)
• ID Number
Feature Databases are stored in the Vector Product Format (VPF). A feature database may have
up to 9 files. They are:
1. specification file -- in ASCII format (spc)
2. index file -- spatial index (quadtree) on feature mbr (ind)
3. Multipolyline -- tables for multipolyline feature classes (mlf)
4. Polyhedron file -- tables for polyhedron feature classes (phf)
5. Polygon file -- tables for polygon feature classes (pgf)
6. Polyline file -- tables for polyline feature classes (plf)
7. Point file -- tables for point feature classes (ptf)
8. Text file -- tables for text feature classes (ttf)
9. geometry file -- ring table, edge table, vertex table, connected node table for 3, 4, 5, and 6,
and image table for 4 (which is optional) (geo)
A feature database supports 6 feature geometries:
1. TEXT -- text feature geometry
2. POINT -- point feature geometry
3. LINE -- line, route feature geometry
4. POLYGON -- area, polygon, face feature geometry
SOCET SET Page C-1

Appendix C - Feature Database and Extraction Specification
5. POLYHEDRON -- 3D volumetric feature geometry consisting multiple faces or a group of

element polygon features
6. MULTILINE -- a complex feature geometry with a number of polyline features
For each geometry, there are a number of classes with the same geometry, but different attributes.
The mandatory attributes are the same for all feature classes of the same geometry. Within each
feature class, attributes for all features must be the same (of course attribute values are different).
The Feature ID are a system generated attribute for all feature. You cannot alter feature ID
number.
A feature database has a logic name which is used as the directory name. For each feature
database, there is a subdirectory with the logic name. All feature database subdirectories reside
in the project data directory. Byte Swapping is performed if needed. A feature database created
on a UNIX platform can be used on the Windows platform and vice versa.
C.1.1 Classes
Every feature belongs to a “class” that determines it’s graphical characteristics and it’s data
attributes. Typical classes are buildings, creeks, highways, roads, towers, ground cover, forest,
lake, etc. All features of the same class have the same attributes (of course, the attribute values
may be different). Each feature or class can have different graphic attribute values. Every feature
class has a geometric characteristic that defines the expected delineation.
C.1.2 Attributes
An attribute is a characteristic of a feature. For example, features of the class Building may have
attributes of Height and Usage, while features of the class Road may have attributes of Width,
Material, and Speed Limit. The kinds of attributes attached to a feature are defined by the feature
class. For example, if the class Road has attributes of Age and Width, then all features of the class
Road will have those attributes.
A feature class may have any number of attributes. Each attribute must be one of the following
kinds: integer, floating point (single or double precision), text string, or enumerated type.
Feature #1 Feature #2
Class: Building Class: Building
Attributes: Attributes:
Height = 70m Height = 40m
Usage = Office Usage = Condo
Graphical Characteristics Feature #3

Class: Building Class: Road
Color: Blue Attributes:
Line Style: Solid Width = 20m
Class: Road Material = Asphalt
Color: Red Num. Lanes = 4
Line Style: Dashed
Page C-2 SOCET SET

C.1.3 Elements
Complex feature types (POLYHEDRON and MULTILINE only) have elements. For example, a
POLYHEDRON feature can have a number of polygons and each polygon is an element. There
is no limit to the number of elements in a complex feature. You can group a number of complex
features into one complex feature. Primitive feature types (POINT, TEXT, LINE, and
POLYGON) cannot have elements. You cannot group primitive features.
All elements in a complex feature must be of the same geometry of the class. For example, if the
Lake class is a POLYHEDRON class, then all elements in a Lake feature must be polygons.
Elements can have their own attributes called element attributes. The difference between feature
attributes and element attributes are that feature attributes are per feature and element attributes
are per element. Feature attribute values are the common attribute values for all elements while
element attribute values are unique for each elements.
C.1.4 Extraction Specification

An E x t r a c t i o n S p e c i f i c a t i o n is a file which defines the classes of features in a feature
database. An Extraction Specification must be created and selected before a feature database can
be created or populated. The Extraction Specification defines the kinds (classes) of features that
are permissible in the feature database, and defines the types of attributes associated with each
class of feature. The benefits of an Extraction Specification during Feature Extraction are:
• Assists you in selecting the feature class by providing a list of permissible classes
• Characterizes feature databases based on the product with which they are associated
• Prohibits you from creating improper features
• Guides you in attributing the features
• Makes it easy to define the attributes associated with feature classes
An Extraction Specification is a XML file. Sample Extraction Specifications are provided in the
directory <install_path>/internal_dbs/SPECS. You should create your own custom
Extraction Specification that is appropriate for your application, but you may use the sample
specifications until you have enough experience to create your own. Typically, an Extraction
Specification is named after the map product you are generating. For example, you may have
individual specifications for each of the following products:
• 1:50,000 Topographic
• 1:25,000 Urban
• Harbor Chart
• Order-of-Battle
• Perspective Scene Generation
• Utilities, Sewer, and Power
When you create a new (empty) feature database you must select an extraction specification from
the list of templates. At that time a copy of the template spec is stored with the new feature
database in the project data directory. You cannot change the instantiated spec after creating the
feature database. In other words, all customizing of the extraction specification must be done
before creating your feature database, not after. If you need to change your spec file after you
SOCET SET Page C-3

have created the feature database, you can run “Save w/ New Spec” function in Feature
Extraction.
C.1.5 Changing the Extraction Specification of an Existing Database

After you have created a feature database, you may need to change the extraction specification.
You can replace an entire extraction specification of a feature database by running “Save w/ New
Spec” in Feature Extraction
C.1.6 Reserved Classes and Attributes

Certain SOCET SET applications reserve certain class attribute names for internal purposes.
These names are reserved and cannot be used for other purposes. Most of the reserved names are
related to Perspective Scene generation or to generic features. See the sample Extraction
Specification below for an example of how some of these reserved classes and attributes are used.
The reserved class names are:
PS_ROUTE (view route features must have this class)
TEXTURE (used for texture patches)
GENERIC_POINT (all features in the generic database must be one of these “generic”
classes)
GENERIC_2D_ROTATING
GENERIC_LINE
GENERIC_MULTILINE
GENERIC_POLYGON
GENERIC_POLYHEDRON
GENERIC_2D_FIXED
SS_FDB_BOUNDARY
tin_point
tin_breakline
The reserved attribute names are shade_flag and shade_value. These attributes are used in
Perspective Scene generation to identify the technique to use to shade a polygon element. These
attributes only have meaning when attached to classes with a Polygon geometry type. The most
common use of these attributes is in the Building feature class. The possible values of these
reserved attributes are:
shade_flag - possible values are:
AUTOMATIC—The polygon will be shaded from the most nadir image in the list of images
you provide in perspective scenes.
SELECTED_IMAGE—The polygon will be shaded from the image you specify in the
shade_value attribute. The shade_value is the name of an image support file from the project
Page C-4 SOCET SET

you are working in (the full pathname of the support file should NOT be provided, ONLY
the support filename).
PATCH_IMAGE—The polygon will be shaded from the texture patch image you specify in
the shade_value attribute. The shade_value is the name of any texture patch image support
file from one of your directories. In this case, the full pathname of the support file should be
provided. Additionally, you must tie the texture patch to the polygon using the Texture Patch
tool in Feature Extraction. The Texture Patch tool will also automatically set the
shade_value.
GREY_SHADE—The polygon will be fully shaded using the grey level (0 to 255) that you
specify in the Perspective Scenes Scene Parameter Setup menu under the Feature Grey Level
field.
SUN_SHADE—The polygon will be fully shaded using a grey level (0 to 255) that is
calculated from the Sun Azimuth, Sun Elevation, and Ambient Light parameters in the
Perspective Scenes Scene Parameter Menu. The orientation of the polygon with respect to
the sun location is what determines the grey level.
RANDOM_SHADE—The polygon will be fully shaded using a grey level (0 to 255) that is
calculated using the SUN_SHADE method and then added to a random number determined
by Perspective Scenes.
SHADE_VALUE—string used to name an image file name; used only if the shade_flag is
PATCH_IMAGE or SELECTED_IMAGE.
SOCET SET Page C-5

Appendix D
Customizing Your Software

Configuration
Customizing Your Software Configuration is designed for
tailoring SOCET SET to your liking.
D.1 Overview
This appendix describes several modifications you can make to tailor the SOCET SET software
configuration to your own site. Additional information, especially about hardware issues and
operating system issues, is contained in the System Administration Manual.
D.2 Establishing Image Locations

Image Locations are directories used to store imagery. See “File Organization,” Appendix B for
an explanation of how to use Image Locations. The list of image locations for your site is stored
in the file:
<install_path>/internal_dbs/DEVICE/location.list
The Image Location list file must contain one or more image locations. There must be at least one
entry in this list before starting SOCET SET the first time.
The list of image locations is a plain text file. You can edit the list of image locations with a text
editor, or by clicking Project > System Administration > Image Locations on the main
workstation window.
The image location list file contains two columns: the left column is the shorthand name for each
location, and the right column is the full directory path of the location.
The first image location in the list must be the default image location: it will be used as the default
location to store new image files. Step 3 below explains how to create the default image location.
Use the following procedure to create or change to the image locations list file:
1. Click Project > System Administration > Image Locations on the main workstation
window.
2. If this is the first time the image location list file is being edited, you may see several
sample image locations in the file. These sample locations were provided on your
SOCET SET installation media. You should remove any sample image example locations
that may be in the list.
SOCET SET Page D-1

Appendix D - Customizing Your Software Configuration
3. The first image location in the list must be the default image location. If it is not in the file,
enter it. The first word must be DEFAULT. The directory of the default location may be any
directory on your disks, but /<install_path>/images is commonly used. Here is a
sample first line:
DEFAULT /<install_path>/images
4. Add additional image locations. If your site works on just one project at a time, a single
image location (the default) may be sufficient. But most sites have between 2 and 20 image
locations. Here is a sample image location line:
Disk_A /home/disk_a/images
5. Save the image location list file.
6. If you are running SOCET SET when you edit the image location list file, you must exit
SOCET SET and restart it to recognize the new image locations.
D.3 Grid Coordinate Systems

The Grid Coordinate Systems file defines various grid coordinates that the operator may select
when a SOCET SET project is created. This file is in:
<install_path>/internal_dbs/GEODETIC/grid_parameters
The description of the format is at the beginning of this file. To edit the Grid Coordinate Systems
file, follow the procedure below:
1. Click Project > System Administration > Grid Coordinate Systems on the main
workstation window.
2. Edit the file as needed.
3. Save changes to the file.
D.4 Choosing Text Fonts

There are several situations within SOCET SET where text strings are drawn over imagery,
including Annotation and Feature Extraction. When displaying text strings you have a choice of
fonts that are used when overlaying the string. Each font has three attributes: size, family, and
style.
The place where you select the characteristics of a string depends on the source of the string. For
strings in Annotation, you choose the characteristics in the Annotation main window. For Feature
Extraction, you use the graphics attributes sub-window.
The default values that are available for the three text attributes are:
• Size: Tiny, small, medium, large, extra large, or huge
• Family: Arial, Courier_New, Times_New_Roman, Impact, Lucida, or Verdana
• Style: Plain, Bold, Italic, or Bold-Italic
Page D-2 SOCET SET

If the default values are not satisfactory (for example, you need larger fonts), you can customize
the font characteristics by editing the file <install_path>/internal_dbs/PREF/
fonts.config. The fonts.config file looks like this:
FAMILIES 6
Arial Courier_New Times_New_Roman Impact Lucida Verdana
SIZES 6
8 10 14 36 72 144
STYLES 4
Plain Bold Italic Bold_Italic

For example, to change the font sizes available, you change the six numbers on the fourth line of
this file. The numbers are the font sizes (heights), corresponding to the font sizes tiny, small,
medium, large, extra large, and huge, respectively. The sizes are measured in points; a point is 1/
72 of an inch. For example, in the fonts.config file above, the size of the tiny font is 8 points,
or 1/9 inch. The size of the “large” font is 36 points, or 1/2 inch.
You can change the size of the fonts by simply editing the fonts.config file and then re-
starting SOCET SET. All text strings that you create from this point forward will use the new
sizes. In addition, any text strings that you delineated before the change (in Annotation, Feature
Extraction, or in a Margin file) will also adopt the new sizes.
D.4.1 How to Change the Fonts

Fonts are specified by configuration files in the
<install_path>/internal_dbs/PREF directory. File name are:
• For Windows systems use the file fonts_WIN.config
• For UNIX systems use the file fonts.config
1. Before you edit,<filename>.config, you should save a backup copy to a unique name
such as <filename>.original.
2. Edit the configuration file. Click Project > System Administration > Text Fonts on the
main workstation window. Change the sizes to desired values. Remember, the units are
points or 1/72 inch.
3. Change the families to have the desired values. To see which families are available on your
computer on a Unix platform use the command xfontsel or xlsfonts, or look in the
directory /usr/X11*/lib/X11/fonts/* or in /usr/openwin/lib/X11/
fonts/*.
4. Save the <filename>.config file.
You cannot change the styles (plain, bold, etc.).
5. After you edit the <filename>.config file, make a backup copy of your changes to a
unique name, possibly <filename>.config.my_custom. The reason you need to do
this is that <filename>.config is overwritten when you install a SOCET SET
software upgrade, so after you install the upgrade, you should restore your font file.
6. Your changes will not take effect until you restart SOCET SET.
SOCET SET Page D-3

D.5 Customizing Your User Interface

This explains how you can add or change buttons to the main window menu.
D.5.1 The Main Window Menu

To layout of the Main Window menu is defined in the file
<install_path>/internal_dbs/CONFIG/standard.cnf.
You can edit this file and cause any of the following changes:
• You can change the labels on any of the menu buttons.
• You can re-arrange the menu hierarchy in any way you want.
• You can add your own menu buttons to activate your own programs or script files.
For details, refer to the instructions contained in the standard.cnf file. After you edit the file,
you must restart SOCET SET for the change to take effect.
D.5.2 Hot-keys
You can change your hot-keys by clicking Preference > Keyboard/Trackball > Accelerator
Mapping on the main workstation window.
Hot-keys will not function if the Caps Lock or Num Lock is

activated on your keyboard. If you find that your hot-keys do
not work, check to see if Caps Lock or Num Lock is activated.
If so, deactivate them.
D.6 Tape Drives, CD-ROMS, and Printers

This section describes how to configure SOCET SET so it knows about the tape drives, CD-
ROMs, and printers that you have on your network.
D.6.1 Tape Configuration File for Unix Workstations

You must build a tape configuration file when you first install the SOCET SET software on your
system. Afterwards, you do not need to modify the file unless you add or remove devices from
your network. The file should list all tape drives and CD-ROM devices on your network, both
local and remote.
The tape configuration file must have the following name and location: <install_path>/
internal_dbs/DEVICE/device_config_file. You will find a sample tape
configuration file in that location after you install the SOCET SET software.
To edit the tape configuration file, click Project > System Administration > Tape Drives on the
main workstation window. Modify the entries in this file by following the format guideline.
For example, the tape configuration file is used by SPOT Import. You mount the SPOT tape on
a tape drive on the network, then run SPOT Import. SPOT Import will read the tape configuration
file and present you with the list of devices to pick from. You must then select the drive that you
mounted the tape on.
Page D-4 SOCET SET

D.6.1.1 Format of the Tape Configuration File

A sample tape configuration file follows:
HOSTNAME DEVICE NAME DEVICE

DEVICE LABEL
TYPE
saturn /dev/rmt/18 N saturn - SUN 9-track tape (6250 bpi)
neptune /dev/rmt/0bn E neptune - SUN 8mm tape

Berkeley, no rewind
mars /dev/rdst1,1 Z mars - SUN D2C tape
pluto \\.\Tape1 E pluto - Windows - 8mm tape
jupiter /dev/rmt/1bn Q jupiter - SUN 1/4 inch tape

Berkeley, no rewind
The first column lists a hostname of the computer to which the device is attached. You may use
the name localhost for devices located on the same computer you are running SOCET SET
on, but it is always safer to explicitly name the host computer in this column.
If you use local host, make sure the host files are set up properly.
See “Remote Devices for Unix Platforms” on page D-8.
The second column contains the name of the device.

The third column identifies the device type and contains one of the following one letter codes:
LETTER DEVICE TYPE
N 9-track tape drive
E 8mm tape drive (Exabyte)

4mm tape drive (DAT)
Z DZC tape device (AMPEX)
Q Quarter-inch tape drive
C CD-ROM
The fourth column is the device label. The fourth column starts with a nonspace character and
continues to the end of the line. This fourth column is only used for displaying the list of devices
and can contain any descriptive comments.
There must be at least one space or tab between columns.
SOCET SET Page D-5

D.6.1.2 Tape Drive Specification

Most tape drives support a variety of access methods, including:
• rewind vs. no-rewind
• whether or not to automatically skip past End-Of-File marker after a read
• automatic file compression (when writing)
• low density vs. high density (when writing)
In order to support tape access on all computer models, SOCET SET applications expect a non-
rewinding Berkeley-style tape device. The specification of this type of device depends on the
operating system you are running. For example, for device one (1) the device name will be:
OPERATING SYSTEM DEVICE SPECIFICATION
Solaris /dev/rmt/1bn
Windows \\.\Tape1
The tape drive specification that you put into the tape configuration file must follow this
convention.
D.6.2 Preferences
For your convenience, the current state of most SOCET SET applications is stored in various
preference files upon exiting the applications—these preference files are summarized below.
(When you restart the applications, the states are restored to point where you left off.)
Sometimes the Preference files can become corrupted. If you

are having trouble starting the software, you might try
removing the file .proj<username>set from your home
directory or the files .cur<username>set and
.mem<username>set from the current project’s data directory.
SETTINGS FILE LOCATION DESCRIPTION
.projusernameset User username’s home directory Project Settings File — contains the
name of the last project you loaded.
.curusernameset Project data directory, Project Data Settings File — contains

<install_path>/data/ the names of the image(s) you loaded,
<projectname> plus various Display Utility settings.
.memusernameset Project data directory, Memory Settings File — stores the

<install_path>/data/ states of the various software
<projectname> applications.
gen_username.set Preferences directory, General Settings File — contains

<install_path>/ Sketch and tracking sensitivity
internal_dbs/PREF settings.
gen_prefs.set Preferences directory, Default General Settings File —

<install_path>/ contains the default settings for the
internal_dbs/PREF gen_username.set file.
Page D-6 SOCET SET

D.6.3 Printer Configuration File for Unix Platforms

The Printer Configuration file is used during the printing operations that you access from the
Output menu on the main workstation window. The printer configuration file contains the list of
available printers. The printers are divided into two categories: (1) text printers for printing text
files; and (2) image printers for printing images, such as screen dumps.
When you first install SOCET SET it will print text files and image files to the default printer
using the lpr command. If this is satisfactory, you do not have to build a printer configuration
file. You should create your own printer configuration file when you have multiple printers, or
when you want to print with a command other than lpr, such as enscript. After you create a
printer configuration file, you do not need to modify the file unless you add or remove printers
from your system.
The printer configuration file must have the following name and location: <install_path>/
internal_dbs/DEVICE/printer_config_file. You will find a sample printer
configuration file in that directory after you install the SOCET SET software. In the configuration
file, printers are distinguished according to type. A printer may be a text printer, an image printer,
or both.
To edit the printer configuration file, click Project > System Administration > Printers on the
main workstation window. Modify the entries in this file by following the format guideline.
For example, if you have a color printer on your system and wish to use it for printing screen
dumps, you may add it to the printer configuration file, as described below.
D.6.3.1 Format of the Printer Configuration File

A sample printer configuration file follows:
QMS-PS810 T lpr
The_printer_in_the_ T /some/path/text_print
lab_behind_the_door
QMS-PS810 I lpr
Kodak_7700 I $EXEDIR/rasterprint
The first column contains the name of the printer and any other pertinent information you may
wish to include, e.g., printer location. There must be no white space in this field. Use an
underscore (_) as a separator instead. The underscores will be converted to blanks when the
printer selection list is created.
There must be at least one space or tab between columns.
The second column identifies the printer type and contains one of the following one letter codes:
LETTER PRINTER TYPE
I Image
T Text
SOCET SET Page D-7

For printers that can print both images and text, a given printer name may occur twice in the
configuration file: once as an image printer and once as a text printer.
The third column contains the name of an executable file or command that will be executed for a
particular printer. Use of full pathnames is encouraged. Environment variables, such as
$EXEDIR, in the example above, may be used in path specifications. Here is a sample script for
printing text:
# !/bin/sh
# one or more files may be selected for printing
# the $@ on the next line means to print all files
lpr “$@”
Here is an example script for printing screendumps on a color printer:
# !/bin/sh
convert $1 sun:$IMAGE_DATA_PATH/screen_dump.ras
rasterprint $IMAGE_DATA_PATH/screen_dump.ras
D.6.4 Remote Devices for Unix Platforms

A remote device is one located on a computer other than the computer on which you are running
SOCET SET. Referring to the picture below, if you are running SOCET SET on computer A, then
the tape drive attached to computer A is a “local device” and the tape drive attached to computer
B is a “remote device.” Handling remote devices is somewhat more complex than handling local
devices. The special considerations for remote devices are described below.
Computer Computer Computer

A B C
Tape Drive A Tape Drive B
D.6.4.1 Access to the Remote Computer

In order to utilize a device that is on a remote computer, you must have one or more of the
following three files: hosts.equiv, .rhosts, and .netrc. These files are described below.
To guarantee access to the remote drives, you should have all three files. See your System
Administrator for details.
Page D-8 SOCET SET

D.6.4.2 The hosts.equiv File

The remote computer (the one with the tape drive) should have a /etc/hosts.equiv file.
This file should contain the name of the computer on which you are running SOCET SET, that is,
the computer that will attempt to access the remote tape drive. For further information, see the
System Administration Manual.
D.6.4.3 The.rhosts File

The remote computer (the one with the tape drive) should also have a .rhosts file. This file is
located in your home directory on the remote computer, in ~yourname/.rhosts. This file
should contain the name of the computer on which you are running SOCET SET, that is, the
computer that will attempt to access the remote tape drive. For further information, please see the
System Administration Manual.
D.6.4.4 The .netrc File

You should have a .netrc file in your home directory. The format of the file is:
machine machine_name login login_name password plaintext_password

Because .netrc contains a readable version of each user’s password, file permissions should
be set to 400 (user read only). For further information, please see the System Administration
Manual.
D.6.4.5 Verifying Remote Access

After you have built the files described above, you should verify the access by logging-onto the
remote computer with the rsh command. If you can logon to the remote computer without having
to type your password, then you will be able to access its tape drives while running SOCET SET.
On the other hand, if you have to type your password, then you may not be able to access the tape
drives on that computer.
Under some circumstances, you will be prompted for your password in the system console
window at the time you try to open a remote device. For example, you are running SPOT Import
and you select a remote tape drive in the SPOT window and the system appears to suspend, look
in the console xterm window (an alphanumeric shell window behind the main SOCET SET
windows). If you see a prompt Password: you should enter your password in this window and
SPOT Import will then proceed.
D.6.5 Internal Database Configuration

Static data files used by the workstation are stored in the internal databases directory,
<install_path>/internal_dbs. These internal files contain invariant data such as
ellipsoid definitions or the main window menu layout. You generally will not need to view or
change the internal database files, except for extraction specifications and certain user preference
files under the PREF subdirectory. See “Feature Database and Extraction Specification,”
Appendix C.
As a general rule, you should never edit or change any files in

the <install_path>/internal_dbs directory, since this could
result in workstation malfunction. You should only edit a file in
this directory if the User Manual instructions explicitly instruct
you to do so.
SOCET SET Page D-9

A brief description of static data file use by the workstation is given below. The path name for
each of these directories is <install_path>/internal_dbs.
DIRECTORY MODIFIABLE DESCRIPTION
ATM Don’t Touch Contains coefficients used to compute atmospheric

refraction corrections for Frame and Pan sensor models.
BREAK_POINTS Don’t Touch Contains histogram break point files. Used when
importing image files that have pixels with more than 8
bits per pixel; contains information to map down to 8-
bits per pixel. Enables you to use the same mapping for
multiple images.
CAM Don’t Touch. Camera calibration files for various metric cameras.
The files contain data to correct for certain errors in
film imagery, like lens distortion and film shrinkage.
Use Camera Calibration to add or change files in this
directory.
COLLECTION_ Yes, you can edit Contains parameters used for automated feature
STRATEGY these files. extraction.
COLOR_MAP Don’t Touch. Contains color lookup tables for viewing digitized
maps (DRG).
CONFIG Yes, you can edit Contains configuration files. These files determine the
these files. layout of the main window menu pulldowns. See above
under Main Menu in this Appendix for details.
DEVICE Yes, you can edit Contains a list of peripherals available on your system
these files. network. See Peripheral Devices above in this
Appendix.
DTM_STRATEGY Don’t Touch. Contains strategy files that define the parameters that
guide Automatic Terrain Extraction.
GENERIC_DBS Don’t Touch. Contains feature files which hold generic (i.e.,
template) features. Also contains texture patches. You
can add or change generic features with Feature
Extraction.
GEODETIC Yes, you can add Contains files defining standard earth reference datums.
your own datums Also contains definitions of grid and state plane
and grids. coordinate systems. Refer to the README file for
details.
HATS Don’t Touch. Contains files used by Triangulation and Automatic

Mosaic.
HELP Don’t Touch. Contains on-line help files.
ICONS Yes you can add Contains icons used by workstation user interface and
your own icons. Annotation. The only icons that you should edit are the
icons used by Annotation which are stored in the
directory <install_path>/internal_dbs/
ICONS/annotation.
ICONS/FILLS Yes you can add Contains icons used by Feature Extraction for fills. You
your own icons. may add your own 32x32 bit icons if you desire more
fill options. The icons contained in this directory must
be in the xbm format, with a height and width of 32
bits.
Page D-10 SOCET SET

DIRECTORY MODIFIABLE DESCRIPTION
KERNELS Don’t Touch. Contains image enhancement convolution kernels. You

can add or change kernels using the Filter option within
Image Enhancement.
LAYER_DB Don’t Touch. Contains a list of the defined mosaic layers.
LOGOS Don’t Touch. Contains large bitmaps that may be placed in the CRT
background (i.e., in the X root window).
MARGIN Don’t Touch. Contains sample margin files which are used by the
Image Map task. Copy the template file (save.mar) into
the project directory then edit it there. See “Image
Map” on page 52-7 for details.
MISC Don’t Touch. Contains miscellaneous files, including a support file

for viewing graphics only rendering and format layouts
for DTM and feature importing/exporting from/to
ASCII files.
PREF Don’t Touch. Contains miscellaneous files, including a support file

for viewing graphics only rendering and format layouts
for DTM and feature importing/exporting from/to
ASCII files.
SPECS Yes, edit these Contains templates (boilerplates) of Feature Extraction

files. Specification files. Before creating a feature database,
you must create an extraction specification. You may
either copy an existing specification, or create a new
one by modifying an existing file.
VITEC Don’t Touch. Contains data files needed for the VITec image
processing board.
D.6.6 Environment Variables

Environment variables used by SOCET SET source code that you may set or modify can be edited
in the Configuration File Editor. See “Configuration Editor” on page 61-43 for details. The
variables should be used with utmost caution.
SOCET SET Page D-11

Appendix E
Batch Processing
SOCET SET operations can run without user interaction.
E.1 Overview
Batch means running an application from a script, without a window interface. It can be run
immediately, or in some cases at a designated time. The benefits of batch processing are:
• Reduce production costs: no operator required
• Run multiple jobs from a queue
• Designate a time to optimize workload: run jobs at night, when computers are under-
utilized
• Distribute processing: run jobs on server computers, which are faster than
workstations
• Customize user interface: write your own window application, and call SOCET SET
from it
Batch applications take a license, just like interactive applications. Batch works on both Unix and
Windows platforms.
When creating a batch setting file, type all keywords carefully.

If you misspell a keyword, the batch process might not
function properly.
Batch applications get their instructions from textual “setting files.” You must create setting files
before running batch jobs. Several batch applications can be executed in series. Textual “script”
files define the sequence of applications. Each application must finish before the next begins. You
can also run several applications in parallel. SOCET SET does not have a proprietary scripting
language or macro language, instead we use your computers native scripting tools.
If you run data_convert or minifier in batch on UNIX systems,

you must be logged in and have the X server running.
E.1.1 Batch Applications

Nearly every SOCET SET application can be run in batch, including:
• Data Imports/exports (terrain, feature, image)
SOCET SET Page E-1

Appendix E - Batch Processing
• Interior Orientation
• Triangulation - Automatic Point Measurement (APM)
• Triangulation - Solve
• Automatic Terrain Extraction (ATE)
• Orthophoto
• Image Mosaicking
• Convert terrain contour lines to feature DB
• Set feature size attributes
• Force river/stream features to run downhill
• Image balancing (Dodger)
• Create a polynomial sensor model to fit a physical model
• Quality Statistics
E.1.2 Non-Batch Applications

What is NOT a batch application? Anything that requires a window such as:
• Feature editing
• Interactive terrain editing
• Control point measurement
• Quality control and accuracy assessment
E.1.3 Start At Button

In some applications, after defining the job in the window, you can click the “Start At” and a
Batch Creator window will open with your options.
There are two ways to start batch jobs:
• Schedule a job either for 'now' or later.
• Start a queue (a queue is per project per user) that allows the jobs to be executed
sequentially. A queue can contain many jobs. Each time the user does 'add to queue', it
adds a job to the end of the queue. After the user accumulates enough jobs, he can do
'begin queue' to schedule the queue to be kicked off 'now' or 'later'. All jobs in the queue
will be executed sequentially. After the queue is scheduled, the queue is deleted. The
order of the jobs in the queue can be changed using 'modify queue' function.
E.1.4 Quality Control

Most quality control processes require human interaction to validate accuracy. You should not
rely exclusively on batch processing for mission-critical data. Interactive review by an operator
is required for accuracy validation. For example, after running ATE in batch, you should run ITE
to verify it the terrain data. Or, after running Triangulation in batch, you should look at the
residual report to validate the results.
Page E-2 SOCET SET

E.2 Stand-Alone Operation

Running stand-alone means that you run an application, such as ATE or Rectify, without the
SOCET SET main window. To start an application in the stand-alone mode, you activate it from
a shell command line as follows:
% <install_path>/bin/start_socet -single application_name
If you want to run an application on a remote computer, yet have the windows appear on your
local computer, do the following:
% rsh remote_computer
% setenv DISPLAY local_computer:0.0
% <install_path>/bin/start_socet -single application_name
If you are unable to log-onto the remote computer with the rsh command, you should check the
hosts.equiv and rhosts files. See “Remote Devices for Unix Platforms” on page D-8 for
further instructions.
To start an application in the stand-alone mode in Windows, you activate it from a MS-DOS
command line as follows:
% <SOCET SET DRIVE>:<SOCET SET DIRECTORY>\bin\start_socet -

single app_name
E.3 Batch Operation

Some applications can take a long time to process their data. Time is wasted when these
applications have to be run repeatedly with different data sets.
Running an application in batch mode is useful for running the application overnight, or running
the application on a server (that other people are also using), or running several applications
consecutively from a script file. When running in batch mode, the application will not display its
graphical user interface; instead, the application will get its input parameters from the command
line arguments and any setting files you specify.
To activate an application in batch, you type the following command line from a shell prompt:
% start_socet -single <application_name> -batch -s

setting_file.set
E.3.1 Start At Jobs

The Start At tool lets SOCET SET application run in Batch mode. You can prepare all the data
required for a batch task interactively, without writing a setting file. SOCET SET applications
that use the Start At have an additional button labeled “Start at....” When selected on the
SOCET SET Page E-3

application window, it displays the Batch Creator window and lets you choose the batch process
option you desire.
If you plan to use Start At with Windows 2000, make sure you
have installed Windows Service Pack 3 from Microsoft first. It
contains important fixes to the Task Scheduler.
Clicking on the appropriate process will either bring up a Batch Scheduler or Modify Batch
Queue window.
E.3.1.1 Batch Scheduler
The Start Batch Job window’s selection are as follows:
SELECT TO
System Prompt you to choose a computer system where the batch job will run.
Now Start the batch job “immediately” after you click OK.
Later Allows you to select when to start the job. You are prompted to choose the
preferred date and time to run the batch job.
Page E-4 SOCET SET

SELECT TO
OK Set up a batch job to run your application at the specified time. The
window will close if the specified settings are correct.
Cancel Close the window. No batch job is set-up.
E.3.1.2 Condor Batch Scheduler
SELECT TO
Any System Run on any system on the condor pool.

Selected System Prompt you to choose a computer system where the batch job will run.
Now Start the batch job immediately after you click OK.
Later Allows you to select when to start the job. You are prompted to choose the
preferred date and time to run the batch job.
OK Set up a batch job to run your application at the specified time. The
window will close if the specified settings are correct.
Cancel Close the window. No batch job is set-up.
SOCET SET Page E-5

E.3.1.3 Modify Batch Queue
This allows the jobs to be executed sequentially. A queue can contain many jobs. Each time the
user does “add to queue”, it adds a job to the end of the queue. After the user accumulates enough
jobs, he can do “begin queue” to schedule the queue to be kicked off “now” or “later.” All jobs
in the queue will be executed sequentially. After the queue is scheduled, the queue is deleted.
The order of the jobs in the queue can be changed by selecting the job and moving it using the
up/down arrows, or even deleted from the queue. To start the batch job, click OK, then Begin
Queue on the Batch Create window. Make the proper entries in the Batch Scheduler and click
OK. The job will then start at the designated time.
E.3.1.4 Remote Startup Requirements

When you execute jobs on remote systems, you must make sure the name of the remote system
is in the file internal_dbs/DEVICE/network_config_file. You must also ensure the required
system directories are consistent between the machine you set up the batch and the remote
machine. The most critical locations are the internal_dbs directory, the image directory, and the
project directory. The most reliable way to achieve this is to mount the file systems in exactly the
same way on both systems.
E.3.1.4.1 Windows Requirements

You must make sure the following conditions are met to use Start At on the Windows platform.
• Your login account must have Administrator privilege.
• You must have the Task Scheduler service running on the computer which is going to
run the process. The status of the Task Scheduler service can be checked by selecting
Administrative Tools > Services on Control Panel and it should look like:
Service Status Startup
Task Scheduler Started Automatic
If the Task Scheduler is not started, perform the following:

The startup user for the Task Scheduler service must be the same user as the one you used to set
up the batch job. To set this up, perform the following:
• In Control Panel, double-click the Services icon.
• Click the Task Scheduler service, and then click Startup.
Page E-6 SOCET SET

• Click Automatic, then OK.

• Restart the service by clicking Stop (if it is already running) and Start, so the
changes take effect.
E.3.1.4.2 UNIX Requirements

The system MUST have correct configuration so that remote shell can be done without requiring
the user to enter a password. See “Remote Devices for Unix Platforms” on page D-8 for more
details.
E.3.1.5 Execution - Start At

1. [Optional] Click the System to select a computer system.
The file internal_dbs/device/network_config_file contains the list of the
computers names in your network. By default, Start At will use your local computer.
2. [Optional] In order to run the batch job immediately, click Now, then OK.
3. Select/verify Date and Time.
4. Click OK to register the new batch job in queue.
5. [Optional] View/edit the setting or aerial triangulation files. The name and location of the
setting or aerial triangulation files will be displayed in the Status Message Box of your
application. For data exports (FSM), Minification, ATE, DTM Feature Merge, Orthophoto,
Mosaic, and change Detection the setting file will have the extension (.set). For MST- Point
Measurement, and Solve, the aerial triangulation file will have the extension (.atf).
6. [Optional] View the log file for information about batch job completion. The log file name
is the same as the setting or aerial triangulation file‘s name with the extension .log and it is
located with the setting or aerial triangulation file in a subdirectory under the project
directory called batch_dir.
E.3.2 How to delete Batch Jobs on the Windows platform

Two ways to delete a batch job, using Modify Batch Queue or Command Prompt are described
below.
E.3.2.1 Using the Window’s Scheduler.

1. Check that the directory “Scheduled Tasks” is present in the Desktop/My Computer. If not,
contact with your System Administrator.
If the Scheduler is not available on your computer, you must

delete the job with a command prompt.
2. Double click My Computer on your computer’s Desktop.

3. Double click Scheduled Tasks and verify that the “Scheduled Tasks” window pops up.
4. Select the line that starts with At and has the same number as the “Job registration number”
of the batch job you want to delete.
5. Press the RMB.
6. Delete the selected At job.
7. If not needed, delete the setting file that was belong to the deleted job, from the batch_dir
directory in the project’s data directory.
SOCET SET Page E-7

E.3.2.2 Using Command Prompt
E.3.2.2.1 Using the registration number or execution time

1. Click Start > Programs > Command Prompt and verify that the DOS window pops up. Use
this window to type all the commands, described below.
2. Verify that the selected job is present in the At job list.
S:\>ATBLANK
SPACEBLANK
SPACE
BLANK
SPACE BLANK SPACE
STATUS ID DAY TIME COMMAND LINE
7 NEXT 05 10:20 S:<install_path>\data\ron_albis\batch_dir\b38be8f53.bat
3. Delete the At job (in this example At job number 7 and execution time is10:20 PM).
S:\>at 7 /delete
4. Verify that the deleted job is not present in the At job list.
S:\>at
There are no entries in the list.
5. Delete the setting file that was belong to the deleted job, if that file is not needed.
S:<install_path>\data\batch_dir>del b38be8f53.set
E.3.2.2.2 Using the application name
It may be a problem to delete a batch job using the application

name, in case you have several batch jobs created by the same
application.
Assumption: In this example the user only knows that the application name is minification and
wants to delete that batch job.
1. Verify which jobs are present in the At job list.
S:\>at
S:\>ATBLANK
SPACEBLANK
SPACE
BLANK
SPACE BLANK SPACE
3 NEXT 06 10:50 S:<install_path>\data\ron_albis\batch_dir\b38be8g55.bat
4 NEXT 06 10:50 S:<install_path>\data\ron_albis\batch_dir\b38ad8a5f.bat
Identify the ID number associated with the batch application. Display the contents of the
batch files in order to find the application name.
S:<install_path\bin\start_socet -single
<application_name>...
2. After identification, delete the batch job.
S:\>at 3 /delete
Page E-8 SOCET SET

3. Verify that the deleted job is not present in the list.
S:\>at
BLANK
S:\>AT SPACEBLANK
SPACE
BLANK
SPACE BLANK SPACE
4 NEXT 06 10:50 S:<install_path>\data\ron_albis\batch_dir\b38ad8a5f.bat
Delete the setting that was belong to the deleted job if that file is not needed.
S:<install_path>\data\ron_albis\batch_dir\b38be8f53.set
Optional: To delete all the batch jobs in the list use the following command >at /y /delete
E.3.3 Deleting Batch jobs on the UNIX platform.

It is possible to delete a batch job in two ways, described below.
E.3.3.1 Using the registration number or execution time.

1. Verify that the selected job is present in the At job list.
>atq
RANK EXECUTION DATE OWNER JOB QUEUE JOB NAME
1st Mar 13, 2000 22:20 vitaly 952978800.a a stdin
2. Delete the At job.
>atrm 952978800.a
3. Verify that the deleted job does not present in the At job list.
>at -l
4. Delete the setting file that was belong to the deleted job if that file is not needed.
>cd <install_path>/data/iec_utm_sdap/batch_dir
> ls kaa0_H5bK.set
kaa0_H5bK.set
> rm kaa0_H5bK.set
E.3.3.2 Using the application name and the setting file name.
1. Verify that the At jobs are present in the At job list.
>atq
SOCET SET Page E-9

RANK JOB
EXECUTION DATE OWNER JOB QUEUE
NAME
1st Mar 5, 2000 11:50 vitaly 952249800.a a stdin
2nd Mar 5, 2000 11:50 vitaly 952249801.a a stdin
Assumption: In this example the user only knows that the batch job was created by
minification with the setting file paa0vAr_P.set and wants to delete this job.
2. List all At jobs.
cd /var/spool/cron/atjobs
ls
952249800.a 952249801.a
3. Display 2 last lines of each batch job file until you find the required application name and
the setting file name.
tail -2 952249801.a
/prod1/socet_set/socet_v4.3.3/develop.SOLARIS26/bin/
start_socet -single data_convert -batch-afast_math-s
<install_path>/data/iec_utm_sdap/batch_dir/aaa0VdiU8.set >
<install_path>/data/iec_utm_sdap/batch_dir/aaa0VdiU8.log
2>&1
tail -2 952249800.a
/prod1/socet_set/socet_v4.3.3/develop.SOLARIS26/bin/
start_socet -single minifier
-batch -s <install_path>/data/iec_utm_sdap/batch_dir/
paa0vAr_P.set >
<install_path>/data/iec_utm_sdap/batch_dir/paa0vAr_P.log
2>&1
4. After identification, delete the batch job.
atrm 952249800.a
5. Verify the At job list.
at -l
952249801.a Sun Mar 5 11:50:01 2000
Page E-10 SOCET SET

6. Delete the setting file that was belong to the deleted At job, if this file is not needed.
cd <install_path>/data/iec_utm_sdap/batch_dir
rm paa0vAr_P.set
Optional: To delete all batch jobs in the list use the following format UNIX command:
atrm -a
E.3.4 Running Batch from Shell Scripts

An alternative to running batch applications from the shell command line is to run the application
from a shell script. A script will let you run multiple batch applications one after another; or you
can schedule your script to run at a certain time of the day using Unix commands like atq or
crontab.
A shell script is an ASCII text file containing Unix command lines. You use a separate input line
for each application you wish to invoke. The format of a shell script is shown below:
The back-slash (\) denotes the continuation of a long

command that requires more than one line of text.
# Comment line
% start_socet -single <application_executable_a> -batch -s

\
$PATH_NAME/setting_file1.set
# Comment line
% start_socet -single <application_executable_b> -batch -s

\
# Comment line
% start_socet -single <application_executable_c> -batch -s

\
# Comment line
% .
% .
% .
Note that comment lines in a shell script are optional.

To run a shell script, it must first be executable. To make it executable, use the command:
% chmod +x <shell_script_name>
SOCET SET Page E-11

Now the shell script can be treated like any other executable file. To run it, simply type the name
of the script. To create a separate log file that contains all the output messages of each application
being run, run the shell script as shown below:
% <shell_script_name> >& <log_file_name>
The log file need not exist beforehand. To run the job in the background, place an & at the end of
the above command; this will allow the job to continue running after you log off. When the shell
script file shell_script_name has finished its run, you can view the file log_file_name to verify
that the correct data sets were run and to see if any errors occurred during the run. Using log files
is highly recommended, as they are the only means of verifying the status of a background job
running on a machine you are not currently logged onto.
If the shell script and the setting files used in the script are all in the same directory, the script
does not need environment variables in front of the setting file names as long as it is executed in
that same directory.
A sample shell script program is shown below:
# This script runs ate on two polygons and creates two
# orthophotos
# Run ate on polygon 1
% start_socet-single ate -batch -s polygon1.set
# Run ate on polygon 2
start_socet -single ate -batch -s polygon2.set
# Run orthophoto on polygon 1
% start_socet -single orthophoto -batch -s polygon1.set
# Run orthophoto on polygon 2
% start_socet -single orthophoto -batch -s polygon2.set
## End of script file
E.3.5 Setting Files

You specify the input parameters to an application running in batch mode by way of a setting file.
The setting file is an ASCII text file that contains the input data needed by the application. You
must create a setting file before you can start the application in batch mode. The format of the
setting file is described below.
Page E-12 SOCET SET

You can specify the location of the setting file in one of three ways:
1. Without an explicit path, in which case the application will search the current directory for
the setting file.
2. With an explicit path, in which case the application will find the setting file at the location
you specified.
3. With an environment variable which specifies the directory that contains the setting file.
These methods are illustrated in the following examples:
% start_socet -single <appname> -batch -s file1.set
% start_socet -single <appname> -batch -s /home/smith/

file2.set
% start_socet -single <appname> -batch -s $SOMEPATH/

file3.set
You can specify more than one setting to the application by specifying multiple -s options. The
applications read the multiple setting files sequentially, extracting the application-specific
information from each file. The last setting file has the final say as to which data goes into the
application. Here is an example of starting an application with multiple setting files:
% start_socet -single <appname> -batch [-a options] -s

file1.set-s file2.set
E.3.6 Creating Setting Files

Create one with a text editor such as vi, xedit, textedit, etc. There are many examples you
can use as a starting template in internal_dbs/BATCH_SAMPLES. The next two sections of
this appendix contain detailed instructions on how to format the information in a setting file. You
must spell the keywords exactly as shown below or the application will not function correctly.
Note that each application expects a unique set of keywords, so be sure to specify the correct
keywords.
If your input file is a 4.1 Feature Database, you will need the .ftr extension (i.e. FDB.ftr); if your
input/output file is a 4.2 Feature Database, you will not need any extension (i.e. FDB), since the
new Feature Database is now a directory.
E.3.7 Format of Setting Files

A setting file contains two columns: the first column are the keywords, and the second column
are the values. Each keyword must have a corresponding value. The generic format of the setting
file is shown below:
setting_file 1.1
application_a.keyword_1 data_value_a1
application_b.keyword_1 data_value_b1
SOCET SET Page E-13

application_b.keyword_2 data_value_b2
application_c.keyword_1 data_value_c1
Do not embed spaces, tabs, or carriage returns within the

keyword and data values.
The first line of a setting file must always be setting_file 1.1 in order to be recognized
by the applications. As shown above, each setting file can contain data for several applications.
Each application will choose only the data intended for it. The keyword indicates what data value
you are specifying. For example:
KEYWORD DATA VALUE
setting_file 1.1
ate.project <install_path>/data/project_name.prj
ate.dtm dtm_file.dth
ate.strat strategy_file.strat
The above example shows the setting file for a simple Automatic Terrain Extraction. It contains
a project name, a DTM, and a strategy file.
It is best to only put one application’s settings into any given file. Many applications check the
settings files and will report an error if a setting for another application is present. If a particular
keyword is specified more than once in a setting file, the bottom-most specification is used.
You will not need to specify every possible input value to the application, since defaults already
exist in the application. To be sure, you can specify everything needed. Also, if certain key inputs
are missing, the application will abort its operation.
E.4 Batch Processing on the Windows Platform

There are some differences between UNIX batch operations and Windows batch operations. The
first difference is how the output is handled. The output generated from a batch application on
Windows is written to a log file. The default location of the log file is defined by the Home
environment variable. To change the default log file directory, specify a new LOGDIR in the
socet_config.bat file.The default name of the log file is the application name followed by
a “_log.txt”—for example, minifier_log.txt. The start_socet program has an optional “-l”
command line argument. This option allows the log file’s to be defined at execution time. The “-
l” option is only available on the Windows platform. This is an example of using the “-l” option:
% start_socet -l my_log_file -single

application_executable-batch
USAGE: (arguments must appear in the following order)
% start_socet [-l log_name] [-single app_name [app args]]
Page E-14 SOCET SET

The second difference between UNIX batch operations and Windows batch operations is the use
of the forward-slash (/) and the back-slash (\) in file names. When on the Windows platform, the
back-slash (\) is used to denote an Windows file system path, and a drive letter and colon must
precede the filename, e.g. c:<install_path>\data\abc.prj.
If you have more than one start_socet command in your batch file, it is necessary to include the
word start before the start_socet commands. In order to keep the command window open after
execution, prefix the start_socet command with start /B /wait
When installing the software to a directory that contains spaces (the

default for Microsoft Windows installations in SOCET SET 5.3.0 and
later), you must make sure any custom batch scripts that reference
this path now contain double quotes around the path names.
See http://www.microsoft.com/resources/documentation/windows/xp/
all/proddocs/en-us/batch.mspx and http://www.microsoft.com/
resources/documentation/windows/xp/all/proddocs/en-us/ntcmds.mspx
for additional information on batch commands for the Windows XP
operating system.
E.5 Applications
BATCH APPLICATIONS
Automatic Terrain Extraction See “Batch Processing - ATE” on page 37-9.
Automatically Populate See “Batch Processing - A Feature Database” on page 42-43.

Dimensional Attributes
Build Fast Sensor Model See “Batch Processing - Fast Sensor Model” on page 7-34.
Build Terrain Import (BIL) See “Batch Processing --- BIL Terrain Import” on page 17-31.
Dodger (Image Balancing) See “Batch Processing - Dodger” on page 22-12.
DTM Feature Merge See “Batch Processing - DTM Feature Merge” on page 44-12.
Elevation Assignment (EA) See “Batch Processing - A Feature Database” on page 42-43.
from DTM
Export ASCII ARC Grid See “Batch Processing - Export ASCII ARC Grid” on page 17-38.
Export ASCII DTM See “Batch Processing - Export ASCII DTM” on page 17-34.
Export ASCII Features See “Batch Processing - ASCII Features Export” on page 18-25.
Export DEM See “Batch Processing - Export DEM” on page 17-40.
Export DGN Features See “Batch Processing - DGN Features Export” on page 18-34.
Export DGN Posts See “Batch Processing - Export DGN Posts” on page 17-56.
Export DTED See “Batch Processing - Export DTED” on page 17-51.
Export DXF Features See “Batch Processing - DXF Features Export” on page 18-17.
SOCET SET Page E-15

BATCH APPLICATIONS
Export SDTS See “Batch Processing - Export SDTS” on page 17-53
Export Shapefile See “Batch Processing - Shapefile Export” on page 18-30.
Export Terrain Graphics See “Batch Processing - Terrain Graphics” on page 36-7.
Export USGS DOQ Image See “Batch Processing - USGS DOQ Export” on page 7-31.
Frame Import See “Batch Processing - Frame Import” on page 8-15.
Image Import/Export See “Batch Processing - Image Export/Reformat” on page 7-29.
Image Rectification See “Batch Processing - Image Rectification” on page 33-8.
Image Scaling See “Batch Processing - Image Rectification” on page 33-8.
Import ASCII ARC Grid See “Batch Processing - Import ASCII ARC Grid” on page 17-11.
Import ASCII DTM See “Batch Processing - Import ASCII DTM” on page 17-7.
Import ASCII Features See “Batch Processing - ASCII Features Import” on page 18-12.
Import ASCII Image Points See “Batch Processing - Import ASCII Image Points” on page 16-11.
Import DEM See “Batch Processing - Import DEM” on page 17-13.
Import DTED See “Batch Processing - Import DTED” on page 17-16.
Import DXF Features See “Batch Processing - DXF Features Import” on page 18-4.
Import QuickBird See “Batch Processing - QuickBird/WorldView Import” on page 9-3
Import SDTS See “Batch Processing - Import SDTS” on page 17-18
Import Shapefile See “Batch Processing - Shapefile Import” on page 18-15.
Import SPOT DIMAP See “Batch Processing - SPOT DIMAP Import” on page 11-8
Import USGS DOQ Image See “Batch Processing - USGS DOQ Export” on page 7-31.
Minification See “Batch Processing - Minification” on page 21-5.
Mosaic See “Batch Processing - Mosaic” on page 49-22.
Mosaic Sheet Cutter See “Batch Processing - Mosaic Sheet Cutter” on page 49-35
Multi-Sensor Triangulation See “Batch Processing - Multi-Sensor Triangulation” on page 25-9.
Orthophoto See “Batch Process - Orthophoto” on page 46-16.
Panoramic Import See “Execution - Panoramic Import/Edit” on page 8-24
Quality Statistics See “Batch Processing - Quality Statistics” on page 61-32.
E.6 Examples
E.6.1 Minifying Image Files

1. Create a setting file for the left image, left_image.set:
setting_file 1.1
Page E-16 SOCET SET

min.project <install_path>/data/sample_project.prj
min.input_sup left_image_support_file.sup
min.output_name left_image_support_file.
min.output_location sample_location
2. Create a setting file for the right image, right_image.set:
setting_file 1.1
min.project<install_path>/data/sample_project.prj
min.input_sup right_image_support_file.sup
min.output_nameright_image_support_file.
min.output_location sample_location
3. Set up an environment variable for the batch setting file directory:
% setenv BATCHDIR<install_path>/batch
4. Run the minifier twice, once for each image setting file.
% start_socet -single minifier -batch -s $BATCHDIR/

left_image.set

right_image.set
5. Alternatively, you can place these commands into a shell script called
minify_left_and_right:
# Minify left image

left_image.set
# Minify right image

right_image.set
6. To run the shell script, make it executable if it isn’t already:
% chmod +x minify_left_and_right
7. Run the script with a log file:
% minify_left_and_right >& minify_log
E.6.2 Automatic Terrain Extraction on a Single DTM

1. Create a setting file, single_dtm.set:
SOCET SET Page E-17

setting_file1.1
ate.project<install_path>/data/sample_project.prj
ate.dtm single_dtm_polygon
2. Run ate in batch mode on the command line, specifying the setting file you created.
% start_socet -single ate -batch -s $BATCHDIR/

single_dtm.set
3. Alternatively, you can place this command into a shell script called ate_single_dtm:
# Run ate on a single DTM
% start_socet -single ate -batch -s $BATCHDIR/

single_dtm.set
% ate_single_dtm >& ate_log
E.6.3 Creating an Orthophoto

The following steps will make an orthophoto from a DTM and a single image, include grid lines,
and automatically minify the result.
1. Create a setting file, called simple_ortho.set:
setting_file 1.1
ortho.project <install_path>/data/
sample_project.prj
ortho.dtm single_dtm_
polygon.dth
ortho.image image_support_
file.sup
ortho.use_dtm YES
ortho.auto_min YES
ortho.grid_btn YES
ortho.grid_int 100
ortho.grid_grey 200
ortho.gsd 1.0
ortho.output_fil output_ortho
e
ortho.interp NEAREST_NEIGHBOR
Page E-18 SOCET SET

ortho.output_loc sample_location
ation
2. Run orthophoto in batch mode, specifying the setting file you created:
% start_socet -single orthophoto -batch -s $BATCHDIR/

simple_ortho.set
3. Alternatively, you can place this command into a shell script called
ortho_single_image:
# Run orthophoto with a DTM and single image
% start_socet -single orthophoto -batch -s $BATCHDIR/

simple_ortho.set
% ortho_single_image >& ortho_log
E.6.4 Exporting an Image to TIFF Format

The following steps will execute data_convert to change an image file to TIFF format.
1. Create a setting file, called simple_data_convert.set:
setting_file 1.1
data_convert.project_ <install_path>/data/mayes.prj
file
data_convert.conversion_ convert_image_import_export
type
data_convert.input_file <install_path>/images/a.img
data_convert.min_level 0
data_convert.output_file <install_path>/images/b.img
data_convert.output_ img_type_tiff
format
data_convert.output_ <install_path>/data/mayes/
support_file
b.sup
2. Run data_convert in batch mode, specifying the setting file you created:
% start_socet -single data_convert -batch -s $BATCHDIR/

simple_data_convert.set
3. Alternatively, you can place this command into a shell script called convert_
generic_image:
# Run data_convert to change an image to TIFF
SOCET SET Page E-19

% start_socet -single data_convert -batch -s $BATCHDIR/

simple_data_convert.set
% data_convert_image >& data_convert_log
E.6.5 Importing a Frame Image

The following steps will execute frame import using an LHS support file and an image file in vitec
format.
1. Create an setting file, called simple_frame_import.set:
setting_file 1.1
frame.project <install_path>/data/
mikeg_escon.prj
frame.cam_calib_filename /home/phoenix.2/
vcurrent/develop/
internal_dbs/CAM/
default.cam
frame.atmos_ref NO
frame.auto_min NO
frame.create_files IMAGE_AND_SUPPORT
frame.input_image_type LHS
frame.input_image_ /home/ruby.1/images
filename escon10.dsup
frame.output_name sample_name
frame.output_location sample_location
frame.output_format img_type_tiff_tiled
frame.cam_loc_type UNKNOWN
2. Run frame import in batch mode, specifying the setting file you created. The “frame/pan”
flag determines which kind of sensor model Frame Import will create. The choices are
Frame and Panoramic types, respectively. See “Frame and Panoramic,” Chapter 8 for
details about these sensor models:
% start_socet -single frame_import -batch -a <frame/pan/

close_range> -s $BATCHDIR/simple_frame_import.set
3. Alternatively, you can place this command into a shell script called frame_import_image:
# Run frame_import with an LHS image as input
% start_socet -single frame_import -batch -a <frame/pan/

close_range> -s $BATCHDIR/simple_frame_import.set
Page E-20 SOCET SET

% frame_import_image >& frame_log
E.6.6 SDTS
IMPORT
The following steps will execute data_convert to import SDTS files.
1. Create a setting file, called sdts_to_dtm.set:
setting_file 1.1
data_convert.conversion_type import_sdts
data_convert.input_sdts_file <install_path>/data/
min_demo/sdts/
sdtsIDEN.DDF
data_convert.output_dtm_file <install_path>/data/
min_demo/test_sdts
data_convert.project_file <install_path>/data/
min_demo.prj
2. Run data_convert batch mode, specifying the setting file you created:
% start_socet – single data_convert –batch –s $BATCHDIR/

sdts_to_dtm.set
EXPORT
The following steps will execute data_convert to export SDTS files:
1. Create a setting file, called dtm_to_sdts.set:
setting_file 1.1
data_convert.conversion_type export_sdts
data_convert.input_dtm_file <install_path>/data/
min_demo/
save_demo_large.dth
data_convert.output_sdts_dir <install_path>/data/
min_demo/sdts
data_convert.project_file <install_path>/data/
min_demo.prj
data_convert.save_format Float
2. Run data_convert batch mode, specifying the setting file you created:
% start_socet – single data_convert –batch –s $BATCHDIR/

dtm_to_sdts.set
SOCET SET Page E-21

Appendix F
Figures Of Merit
Figures Of Merit is the correlator which provides definitions
for the Automatic Terrain Extraction.
F.1 Overview
FOM is a numerical value assigned by the terrain extraction process. It may indicate one of three
things for a given post measurement:
• It may be an error flag value, indicating that the automatic measurement was
questionable.
• It may indicate a successful or good measurement.
• It may be an edit flag value, indicating the type of editing that was used (lake-filled,
interpolated, etc.).
FOMs may be set by the Automatic Terrain Extraction, Interactive Terrain Editing, or Merge
processes, and are assigned for each post. For example, a particular post may have an elevation
of 374.1 and a FOM of 4, indicating that the elevation value was extrapolated.
Within the Interactive Terrain Editing program, FOMs may be displayed in the Post Editor and
edited with the Area Tool. They may also be displayed graphically (by color) using Terrain
Graphics Setup.
Values occurring in the “CODE” column in the following table are as follows:
A—Elevations with these FOMs are used to interpolate elevations when using the ITE tool
“Interpolate From Good Pts.”
B—Elevations with these FOMs are not changed during ATE.
Values occurring in the Rank column shows the order of precedence. Larger values indicate a
higher precedence than smaller values.
CODE VAL FOM TITLE DEFINITION RANK
0 SMALLEST_FOM Lowest numerical value for a FOM (set to 0

0).
B 1 OUTSIDE_BOUNDARY Outside the extraction boundary defined as a 1
polygon when the grid was created or
defined as a rectangle. The
OUTSIDE_BOUNDARY posts are not
processed by any SOCET SET applications.
SOCET SET Page F-1

Appendix F - Figures Of Merit
2 START_SUSPECT_FOM FOMs between this value and the 2

START_GOOD_FOMS were flagged by the
correlation process (ATE) and have
interpolated elevations from the surrounding
“good” FOM points. Points with FOMs in
this range (START_SUSPECT_FOM to
START_GOOD_FOMS) may have good
elevations since they were interpolated from
the surrounding elevation data
3 INSIDE_BOUNDARY After the DTM is created, all FOMs will 2
have either an INSIDE_BOUNDARY FOM
or an OUTSIDE_BOUNDARY FOM. The
INSIDE_BOUNDARY FOMs are assigned
to points before they have gone through the
correlation process (ATE) or interactive edit
process (ITE).
4 EXTRAPOLATED Points which are on the edge of the DTM 2
grid and have assigned elevations from
points with good FOMs internal to the grid.
5 INTER_OPER_BAD INTERest OPERator BAD indicates a point 2
failed the initial correlation process and a
subsequent interest operator correlation
process. Currently not used.
6 HIGH_SLOPE The elevation assigned to the point after 2
correlation failed an elevation slope
threshold check and has been subsequently
interpolated from surrounding data.
7 TEMPORARY_FLAG Used by software. 2
8 SPIKE_POST The elevation assigned to the point after 2

correlation failed an elevation spike or well
threshold check. The spike or well was
determined from the surrounding elevation
data. The elevation for the point has been
interpolated after it was identified as a spike
or well.
9 LOW_CORRELATION_ The elevation assigned to the point after 2
CURVATURE correlation failed an elevation spike or well
threshold check. The spike or well was
determined from the surrounding elevation
data. The elevation for the point has been
interpolated after it was identified as a spike
or well.
10 LARGE_DIFF_SIGNAL The signal power difference between the 2
_POWER right and left image patches used by the
correlator was lower than the threshold. The
elevation for the point has been interpolated
after it was identified as having a large
difference in signal power.
11 EXCESSIVE_SHIFT The maximum correlation was found on the 2
first or last sample in the correlation image
buffer. The elevation for the point has been
interpolated after it was identified as having
a secondary peak.
Page F-2 SOCET SET

12 EDGE_OF_IMAGE The image patch for correlation was too 2

close to the edge of the image and could not
be used by the correlator. The elevation for
the point has been interpolated or
extrapolated after it was identified as being
on the edge of the image.
13 LOW_SIGNAL_POWER The signal power computed for the right or 2
left image patch in the correlator did not
meet the signal power cutoff threshold. The
elevation for the point has been interpolated
after it was identified as having a low signal
power.
14 LARGE_ELEV_CHANGE The change in elevation during iterations 2
within the correlator exceeds a threshold.
15 LOW_CORRELATION The correlation coefficient computed for the 2
point was below the threshold. The elevation
for the point has been interpolated after it
was identified as having a low correlation.
16 EXCESSIVE_Y_ Not used. 2
PARALLAX
17 INVISIBLE The post/point is not used to generate terrain 2
graphics.
18 SECONDARY_ There was a secondary correlation peak 2
CORRELATION_PEAK identified by the correlator. The secondary
peak may be almost as large as the primary
correlation peak. Therefore, the point is
considered as suspect. The elevation for the
point has been interpolated after it was
identified as having a secondary peak.
19 EXCESSIVE_V_SHIFT The maximum correlation was found on the 2
first or last line in the correlation image
buffer. The elevation for the point has been
interpolated after it was identified as having
a secondary peak.
20 ELEVATED_POST The post is identified as a none bare earth 2
post such as on top of a tree or building. Its
elevation may have been lowered to the
ground by a bare earth tool.
21 START_GOOD_FOMS Points with FOMs greater than 4
START_GOOD_FOMS are considered
good. See START_SUSPECT_FOMS for
more information.
A, B 22 MANUALLY_MEASURED The point has been edited using the ITE 5
tools post editor or profile editor.
A>B 23 LAKE_FILLED The point has been edited using one of the 4
ITE area tools for setting a constant
elevation to a polygonal region of elevation
points.
A 24 PLANE_FILLED The point has been edited using the ITE area 4
tool for setting the elevations inside a
polygonal region to the best fit plane
defined by the polygon.
SOCET SET Page F-3

25 SMOOTHED The point has been edited using one of the 3

ITE area tools for smoothing a polygonal
region of points.
26 DWI The point has been edited using one of the 4
ITE area tools for weighted interpolation on
a polygonal region of points (Distance
Weighted Interpolation - first- or second-
order interpolation tools).
27 THINNED The point has been marked as redundant by 4
the ITE area edit tool so that it can be
thinned by the DTM Export function.
28 IMPORTED_DTED The point has been imported from DTED. 4
A, B 29 GEOMORPHIC The point has been edited using one of the 4

ITE geomorphic tools.
30 INTERPOLATED The point has been edited using an ITE tool 4
for clipping an area, or the point has been
imported from a DTM created outside the
workstation.
31 SEED_POINT The point is from a see point such as a 4
control point, or a tie point etc.
32 EDGE_POINT This post/point is matched by edge
matching.
33 CORNER_POINT This is a corner post identified by one of the
bare earth tools.
34 ONERETURNS LIDAR point/post from the first return.
35 TWORETURNS LIDAR point/post from the second return.
36 THREERETURNS LIDAR point/post from the third return.
37 FOURRETURNS LIDAR point/post from the fourth return.
38 FIVERETURNS LIDAR point/post from the fifth return.
39 LARGEST_FOM The largest possible numerical FOM value 3

for a post which did not automatically
correlate.
401 Above this value indicates a successful 3
automatic correlation.
1.Figure Of Merit numbers greater than 40 (LARGEST_FOM) indicate successful auto-
matic correlation. These large Figures Of Merit are proportional to the correlation coeffi-
cient, so in general, the larger the number, the better the measurement
Page F-4 SOCET SET

Appendix G
Interpolation and Resampling

Interpolation and Resampling gives the details on how
SOCET SET resamples image pixel values.
G.1 Overview
An image is resampled when it is changed in scale, rotation, or skew. For example, resampling is
used in epipolar rectification, image rotation, and orthorectification. The resampling methods are:
• Nearest Neighbor Interpolation
• Bilinear Interpolation
• Weighted Mean Interpolation
• Pixel Averaging
• Flemming (Cubic) Interpolation
Each output image pixel gets its gray level (or color) by mapping back into the input image. If the
location in the input image falls between pixels, the output pixel’s gray level is interpolated from
surrounding pixels.
INPUT IMAGE OUTPUT IMAGE
G.1.1 Nearest Neighbor Interpolation

Nearest neighbor interpolation is not really an interpolation at all. If the location of the output
pixel falls between pixels in the input image, the gray level of the closest input pixel is used. If
SOCET SET Page G-1

Appendix G - Interpolation and Resampling
the location falls exactly half way between input pixels, the gray level of one of the pixels is
selected (arbitrarily).
Nearest neighbor—gray level of closest input pixel is assigned to the output pixel
IINPUT IMAGE OUTPUT IMAGE
G.1.2 Bilinear Interpolation

In bilinear interpolation, one, two, or four input pixels are used to compute the output gray level.
Bilinear is linear interpolation in two directions. It can be thought of as a weighted average of
four neighboring pixels, where the pixel closest to the output pixel location gets greater weight
than the other pixels. The weights are computed by mapping the center of the output pixel back
into the input image. The output pixel center will generally fall somewhere between four input
pixel centers. The weights are inversely proportional to the linear distance between input and
output pixel centers. If the center of the output pixel maps back exactly onto the center of an input
pixel, then the weight on the other three neighboring pixels is 0, so the output gray level depends
only on the one input pixel. Bilinear tends to have a smoothing effect on edges.
Bilinear Interpolation—output gray level is interpolated from four

surrounding input pixels.
these two pixels have

less weight than the
two above
G.1.3 Weighted Mean Interpolation

“Weighted mean” interpolation is a bit of a misnomer. Selective mean might be a better name. In
this interpolation, the output gray level is the unweighted average of one, two, or up to several
neighboring pixels. The algorithm determines which pixels to use by effectively superimposing
Page G-2 SOCET SET

the output pixel on the input image, thus taking into account the relative pixels sizes of the two
images. This interpolation method is intended to give a sharper, less smoothed effect than
bilinear.
Example: average of two pixels:

Example: average of four pixels:
G.1.4 Pixel Averaging

Minification uses pixel averaging. Each output pixel is the average of four adjacent input pixels.
Minification starts at the upper left corner of the image. If the input image dimensions are odd,
the edges are padded with like pixels.
SOCET SET Page G-3

G.1.5 Flemming (Cubic) Interpolation

The Flemming interpolation algorithm is a cubic 4x4 interpolation. The Flemming interpolation
fits a cubic grey-level surface through a 4x4 patch of pixels in the input image. The output grey
shade is computed by mapping the center of the output pixel into the input patch and using the
cubic surface to calculate the output grey value.
Page G-4 SOCET SET

Appendix H
Limitations and Constraints

This section address Limitations and Constraints of various
applications within SOCET SET.
H.1 Overview
Below are known limitations and constraints associated with various applications and processes
within SOCET SET. You will find that the topics follow SOCET SET’s main menu. These know
limitations may or may not be upgraded in future releases.
H.1.1 System Administration

• Driver Installation
If you have Microsoft Windows Services for UNIX installed on the same PC as SOCET
SET, you will need to set the following variable in your <installation
dir>\socet_config.bat configuration file:
set EDITOR=C:\WINNT\System32\write.exe
You may substitute C:\WINNT\System32\write.exe with your favorite plain text editor.
• RT Display
All monitors utilizing the Full Roam display must be set to:
UNIX 24 bits
Windows 32 bits
If not set properly, images may not be displayed correctly.
H.1.2 Project
When deleting imagery on Windows, the image file will not be deleted if the image is
loaded into any of the viewports.
H.1.3 Preparation
• Import > Image > Frame
SOCET SET Page H-1

Appendix H - Limitations and Constraints
Image Import - In the Review/Edit Settings window, to enter a value in multiple

columns, first select multiple rows and then right-click on the column to change.
For TIES Import, do not use import “Support Only.” If you need to use the reimport
“Support Only” function, delete the support file from the project’s data directory and
then reimport images and support files, and reuse images.
• Import > Image > Landsat

Importing the two-band thermal image separately is not supported
• Import > Image > DOQ

The pre-1996 format is not supported.
• Import > Image > SPOT

If you import a 3-band merged (color) SPOT image, you cannot immediately import
another single-band SPOT image. Exit and restart SPOT Import to proceed.
If you import SPOT data with a file input, you may see a message, “Error: Could not find
volume directory file in this scene directory.” This message can be safely ignored.
• Import > Image > CIB & CADRG

CIB and CADRG Import consume a lot of memory if the output image size is larger than
2000 by 2000 pixels. To minimize the impact of this, close as many applications as
possible before running the import. You can also help by adding more memory to your
system.
• Image Dodge and Balance

Dodger does not produce exactly the same results when using a correction file versus
saving to a pixel file. You can use either method, but you should not mix the two methods
and expect matching images.
• Manual Interior Orientation

Double-click on the “Use” table cell to first select it, then click it On or Off.
• Resample > Rectification

Single Image or Pairwise Rectification only works properly in 1:1 image minification
level.
• Multi-Sensor Triangulation (MST)

Initialize/Solve > Adjustment Type -The Direct Linear Transform (DLT) polynomial
math model does not function correctly with geographic coordinate system projects. It
can be used with Grid and LSR projects only.
H.1.4 Extraction
• TIN Editing
General: For TIN format DTMs, when the x-step is greater than one, the software filters
out points in the TIN for display. As a result, only the points that are displayed are
affected by the editing tools.
Page H-2 SOCET SET

Geomorphic Editing with TIN: Pressing undo after inserting a new vertex in a TIN
breakline in ITE may corrupt the terrain file.
• Terrain > Automatic Extraction

You must not run ATE more than once for the same DTM, when the DTM format is TIN.
• Feature
Feature Extraction Generic 2D features functions have been disabled.
Mensuration button produces inconsistent and unreliable results in the text report.
Recommend using Auto Attribution.
Texture Patch display window only shows imagery as grayscale.
• Image Control Toolbar

Do not switch Graphics from Off to Limited, or Full on the Image Control Toolbar, when
there are a lot of feature graphics and RT is in Full Roam mode.
• ClearFlite
Hot-keys for this application have been disabled.
• Annotation & Counting

Sketch behaviors on Annotation may be different from Feature Extraction. For example,
Annotation does not support “Undo” or control points for Arc.
Grid lines are only drawn on the left image.
Annotation is currently limited to displaying about 30-100 images. To work around this
problem, you can split your fly file into smaller pieces and view each separately.
• Feature/Annotation > Sketch

RT may not display all the features after selecting edit shared vertices.
There is a four view limit when using the Online/Offline toggle in Sketch.
To enter a single line of text, do not press the Enter Key when complete, just press the
RMB to accept. To enter multiple-lines of text, press the Enter Key at the end of each
line entry. After the last entry, just press the RMB to accept.
To create a cylinder volumetric feature using the 3-Point Circle Collection, you should
use either the “Enter” or “DTM” Height Entry Mode to determine the height of the
building. The Measure Height Entry Mode is non-functioning.
H.1.5 Products
• Orthophoto
GeoTIFF output does not currently support rotated orthophotos, i.e. unequal upper-left
and upper-right latitude values.
• Mosaic
SOCET SET Page H-3

Mosaic Auto Range Adjust does not properly read enhancements you have saved with
the Image Enhancement “Save to File” option. To use saved enhancements you must use
the “Commit to Disk” option.
H.1.6 Outputs
• File Export > Terrain > DTED
DTED Export may issue an error message complaining about X & Y post spacing not
matching. This message can be safely ignored.
• Rendering Engines > OpenFlight

When running OpenFlight Export, ensure you select the Output File Path to be the
location where the rendering system will be executed. Do not move the files to another
directory after export. External references are currently exported with absolute
pathnames.
H.1.7 Preferences
• Correlation Weights
When using the Correlation Band Selector, do not remove image files from the list.
Doing so will result in inaccurate band weights for image files in the list. If this happens,
you will need to restart SOCET SET in order to get the correct band weights for the
selected images.
H.1.8 Tools
• Image Enhancement
You cannot save enhancements by overwriting the image if the image is NITF JPEG
compressed.
Saving enhancements by overwriting the currently loaded image is not supported on

Windows.
Applied enhancements may not take effect until the minification level is changed.
Filter does not work well with color imagery.
The Image and Auto Brightness/Contrast adjustments do not work for pseudo color
images (e.g. those produced by Image Map).
If you are using image enhancement zoom and rotate and commit the changes to disk
(rewrite the image), the new image will not have proper ground coordinate tracking. If
you want to zoom or rotate an image with proper ground coordinate tracking, use the
Zoom / Scale application under the Preparation pulldown.
• DOQ Edit
Extra files (doq header information) are saved as a .save file in the project directory
while quitting DOQ Editor. Even though you click Cancel after being asked “would you
like to save changes,” an extra file is created.
• Coordinate Measurement
Page H-4 SOCET SET

The image display parameters are not updated when you load a new image. The work-around
is to close and restart coordinate measurement.
If the project coordinate system is LSR (anchored to ground) and the vertical datum is
MSL, and you set the Coordinate Measurement display to Geographic or UTM, then the
Z value is displayed referenced to ellipsoid (should be MSL). As a work-around, use the
coordinate conversion subwindow instead.
In a project with a Geographic Coordinate System and a MSL vertical datum, if you
convert the real-time coordinates on Coordinate Measurement to UTM, the vertical
datum (elevation) is changed from MSL to Ellipsoid. The work-around is to use
CoordSys/Datum Conversion (from the Options menu of the Coordinate Measurement)
and explicitly select the vertical datum.
H.1.9 Other
• To drag a minimum bounding rectangle box within a Solaris system, do not use split-
screen.
• Middle Mouse Button
Due to a bug in the drag-and-drop functionality of the UNIX X-Window system, certain
conditions related to pressing the middle mouse button can cause erratic behavior up to
and including a system hang or crash. There is no problem with positioning the cursor
over these areas as long as the middle mouse button is not pressed. If you accidentally
press the middle mouse button, you may still be able to avoid a problem if you can drag
the cursor to the background area of the monitor and release the middle mouse button
there (not inside a SOCET SET window).
• Remote Tape Drive Access

Access to remote tape drives is supported only when the tape drive is on the same kind
of platform as your local computer.
• Triangular Terrain (TIN)

The following SOCET SET modules process triangular terrain files in a degraded mode
(interpolating the TIN as if it were a grid): Perspective Scene and Shaded Relief.
• Other > File Descriptors (Solaris ONLY)

If you experience problems with opening files you may have reached the maximum
number of file descriptors that can be opened for an application on your system. You can
check the maximum number of descriptors by typing “limit” at the command prompt. A
list of limit setting will appear. The number to the right of “descriptors” is the maximum
a program can have. You can alter this number by the command: limit descriptors
<max_number_desired>, for example limit descriptors 256.
• Other > Preference Files

When upgrading to a new version of SOCET SET. It is recommended to remove all
preference files (.mem****, .cur****) from project directories. Loading old preference
files may cause the Sketch GUI to display incorrectly (i.e not all buttons visible).
• XIL Warning
SOCET SET Page H-5

Loading JPEG images on Solaris may give you an XIL obsolescence warning. This
message may be safely ignored.
H.2 Windows Platform Specific
These Platform Specific notes are in addition to the limitations

above.
H.2.1 Extraction
• Output > Reports > Edit
Direct printing of reports from SOCET SET applications is not currently supported. To
print ASCII files generated by SOCET SET you can load them in the Windows Notepad
application and print them from there.
H.2.2 Preferences
• Keyboard/Trackball Accelerator Mapping
Although you can modify the Change Segment Direction mapping that defaults to
“--UnMapped--” the mapping will not actually be functional.
H.2.3 Other
• Real-Time Image Display
If you are moving the extraction cursor using a standard mouse and the toggling
technique (F3 or trackball button), you may occasionally encounter a problem where the
normal Windows cursor will reappear outside the image display during a move. This can
occur when Windows focus is in the Display a window that is not the image displayed,
AND there is another window overlapping the Image Display window at the time that
the cursor is toggled with the F3 key or the trackball button. Under this condition, the
cursor will change back to the Windows cursor whenever the overlapping window is
“hit” by the invisible cursor. If this occurs, toggle the cursor back to normal mode, put
focus an image display window, and re-toggle the cursor. Alternately, you could move
the window which is overlapping the Image Display and re-toggle.
Brightness and Contrast adjustments on SunRaster images that are produced by the
Image Map application do not work properly. However, the unadjusted image will
display properly.
Page H-6 SOCET SET

Appendix I
Internationalization
This section provides information on translating
SOCET SET.
I.1 Overview
SOCET SET GUI's can be translated into any language that your system supports. The following
procedure will guide you through the process.
In your installation directory under internal_dbs/TRANSLATION are two files named
socet_untranslated.ts and qt_untranslated.ts. Copy these files with the following naming
convention (where XX is the 2 letter code for your target language):
1. socet_XX.ts
2. qt_XX.ts
Note that qt has already been translated into several target languages and
these files are provided.
See http://xml.coverpages.org/iso639a.html for info on 2 letter language codes.

Next you will need to run Trolltech's translation tool called 'linguist' and open the newly created
socet_XX.ts. The 'linguist' application is in the bin directory where SOCET SET is installed.
There is information on how to use this tool at http://doc.trolltech.com/3.3/linguist-manual.html.
Click on the 'Translators' link. This tool will allow you to translate all of the visible text in
SOCET and will save it back to socet_XX.ts.
Once all of the translations have been completed you will need to run another utility called
'lrelease'. The usage is as follows:
1. Go to the internal_dbs/TRANSLATION directory
2. Run “lrelease socet_XX.ts -qm socet_XX.qm”
The last step is to set your environment variable LANG equal to the 2 letter code of your target
langue. For example if you have translated SOCET SET to German:
1. From a C Shell: setenv LANG de
2. From a Korn Shell: export 'LANG=de'
3. From Windows: Right click on My Computer > Properties, go to the Advanced tab, click
on Environment Variables…, and add a new variable called LANG. Set it to de.
Now just start SOCET_SET as you normally would and it will appear in the target language.
SOCET SET Page I-1

Appendix J
Accelerator Key Commands

Accelerator Key Commands are hot-keys for your
convenience.
J.1 Overview
The accelerator key commands are hot-keys to help you navigate or perform functions efficiently
within the application. A complete list of these accelerator key commands for the application you
are running is available by viewing the Accelerator Mapping window. From the Main
Workstation window, click Preferences > Keyboard/Trackball Accelerator Mapping.
See “Selecting Files By Footprint” on page 1-5 for details on how to interact with the Accelerator
Mapping window.
The following are guidelines when using accelerator key commands:
• The cursor must be in the window that contains the desired menu option or function in
order to be activated by key commands.
• For multi-key commands, keys are pressed simultaneously.
• Alphanumeric keys can be in either upper or lower case.
SOCET SET Page J-1

INDEX
Symbols window, 45-4
ARC
.netrc file, D-9 grid export, 17-37
.rhost file, D-9 grid import, 17-10
ARC_GEN
Numerics
export, 18-18
3rd, 60-1 import, 18-5
ArcSDE
A execution, 42-39
area editor
absolute orientation errors, triangulation, 28-9
posts display, 39-32
accelerator key commands, J-1
ASCII
accelerator mapping, 1-5, 61-18
ARC
accuracy, 2-7
grid import, 17-10
adding
DTM export, 17-32
control points, 27-25
DTM import, 17-1
control points by measuring, 23-6
feature export, 18-23
control points manually, 23-6
feature import, 18-7
advanced drawing tools, sketch, 58-11
ground point import, 16-3
AFE
ASCII ground point import, 16-3
single feature mode (sketch), 42-19
ASTER, 7-55
ALBANY, 8-14, 8-23
attribute query, 42-19
ALOS Import, 7-38
attribute validation report, 42-20
AMS export files, 18-8
auto loader, 4-12
anaglyph, 52-6
auto point measurement strategy files, triangu-
anchoring, annotation, 45-11
lation, 25-12
animation, perspective scenes, 50-34
autocreate parameters, 58-14
annotation, 45-1
automated population of attributes, 42-29
anchoring, 45-11
automatic
counting, 45-1
interior orientation (AIO), 24-3
execution, 45-11
point measurement, 27-2
grid lines & tick marks, 45-9
range adjustment, 49-14, 49-15
icon list, 45-10
terrain extraction, 37-4
sketch tools, 45-4
terrain extraction sample workflow, 3-12
ticks & gridlines, 45-7
terrain extraction strategies, 35-4
when to run, 45-1
automatic terrain extraction
SOCET SET Index-1

INDEX
(ATE), 37-1, 38-1 import GeoTIFF terrain, 17-26

execution, 37-7 import NED GridFloat, 17-9
minification, 21-5, 52-26, 52-27
B MST, 25-9
backing up data, triangulation, 25-17 operation, E-3
backup, restore & delete orthophoto, 46-16
backup, 6-2 panoramic import, 8-25
restore, 6-5 quickbird import, 9-3
when to use, 6-1 scheduling batch jobs, E-3
basic functions, vct, 20-3 stand-alone operation, E-3
batch processing, E-1 start at, E-2
AIO, 24-5 windows platform, E-14
applications, E-15 bilinear interpolation, G-2
batch applications, E-1 BINGO, 8-24
build fast sensor model, 7-34 blunder processing, triangulation, 28-9
dodger, 22-12 building an MC&G product, sample workflow,
DTM feature merge, 44-12 3-16
examples, E-16 building lean, orthophoto, 46-8
export C
ASCII ARC grid, 17-38
ASCII DTM, 17-34 CADRG import, 7-22
ASCII features, 18-25 camera calibration, 61-5
DEM, 17-40 distortion parameters, 61-12
DGN features, 18-34 execution, 61-13
DGN posts, 17-56 fiducial coordinates, 61-10
DXF features, 18-17 camera location window, panoramic, 8-21
GeoTIFF terrain, 17-59 change detection, 48-1, 48-2
NED GridFloat, 17-36 DTM input, 48-1
SDTS, 17-53 execution, 48-6
exporting USGS DOQ image, 7-31 output image, 48-2
feature db, 42-43 registration, 48-1
frame import, 8-15, 33-8 change elevation, 61-38
image balancing, 22-12 changing coordinates, 5-14
image export/reformat, 7-29 changing default cursor, 61-17
image scaling, 34-4 CIB Image Source, 54-22
import CIB import, 7-19
ASCII DTM, 17-7 CIB Registration, 54-1
ASCII features, 18-12 clearflite, 40-1
ASCII image points, 16-11 cursor tracking, 40-10
DEM, 17-13 data files, 40-21
DTED, 17-16 execution, 40-18
DXF features, 18-4 color balancing, 46-11, 52-13
SDTS, 17-18 color imagery, perspective scenes, 50-16
shapefile, 18-15 command line
Index-2 SOCET SET

INDEX
apmstats, 61-2 input, 23-3

conv_spec, 61-2 loading data, 23-7
copy_spot_disk, 61-2 saving data, 23-7
copy_spot_to_tape, 61-2 window, 23-3
dtm_compare, 61-2 control points, triangulation, 27-23
dump_screen, 61-2 converting, LSR, 5-9
flip_image, 61-2 coordinate measurement, 59-1
ftr_to_dst, 61-2 areas, 59-4
img_band_merge, 61-2 coordinate system, 59-5
img_cut, 61-2 datum conversions, 59-5
img_join, 61-2 execution, 59-4
make_arc, 61-2 execution of coordinate/datum conversion,
make_shortsup, 61-2 59-7
media_state, 61-2 lengths, 59-4
mp_asc_import, 61-2 window, 59-2
ortho_qa_file_read, 61-2 coordinate system, 5-2
ortho_qa_make_sup, 61-2 control points, 23-7
ortho_qa_merge_orthos, 61-2 geographic, 5-6
ortho_qa_stats, 61-2 grid, 5-10, D-2
pgmkill, 61-3 LSR, 5-7
platform_swap_grid_dtm, 61-3 state plane, 5-10
ss_hostid, 61-3 UTM, 5-11
start_socet, 61-3 coordinate system & datums, 2-8
tape_struct, 61-3 copy project, 5-16
tiffinfo, 61-3 copying data files between projects, 5-14, 5-16
tkbtest, 61-3 correlation band selector, 61-39
commands, accelerator key, J-1 creating a project
complex features, extracting, 42-41 execution, 5-13
Condor, 60-1 cursor
configuring internal database, D-9 customizing speed, 1-3
constraint files, 25-11, 28-16 editor, 61-15
contour line splining, 36-7 extraction cursor, 1-3
contour lines, 36-6 grounding, 1-4
contour lines, DTM, 52-12 mouse, 1-3
contrast, 49-15 moving, 1-3
control point editor, 23-1 toggling, 1-4
coordinate system, 23-7 two-handed controller, 1-4
datum, 23-7 customizing your S/W configuration, D-1
execution cd-roms, D-4
adding control points by measuring, grid coordinate systems, D-2
23-6 hot-keys, D-4
adding points manually, 23-6 image location, D-1
control point reviewing/editing, 23-6 internal database, D-9
create new file, 23-5 printers, D-4
SOCET SET Index-3

INDEX
tape drives, D-4 import, 17-13

text fonts, D-2 DTM
user interface, D-4 boundaries, 35-10
customizing your workflow, 3-1 change detection, 48-1
contour lines, 52-12
D creation, 35-2
data creation sample workflow, 3-10
ASCII ground point import, 16-3 export, 17-32
export, 16-1 geomorphic editor, 39-36
image point import, 16-5 graphics, 36-4
import, 16-1 image map, 52-12
import & export, 16-1 image sharpening, 47-1
import a ASCII ground point, 16-5 import, 17-1
scene content selection, 50-30 polygon strategy, 35-2
data files, triangulation, 25-10 populating with valid data, 35-4
data managers, vct, 20-10 registration, 29-1
database, internal configuring, D-9 execution, 29-3
datum, 2-8 user inputs, 29-2
control point editor, 23-7 shaded relief, 36-6
conversion, 59-5 terrain analysis, 51-1
converting, 5-9 DTM/feature merge, 44-1
entering control points, 27-26 batch processing, 44-12
degree/radian conversion, 61-15 boundary edit/view, 44-7
delete, 6-7 class algorithm edit, 44-10
DEM class algorithm settings, 44-7
export, 17-38 data flow, 44-3
import, 17-11 execution, 44-11
DGN information, 44-7
data format conversion, 18-30 DXF
display feature export, 18-16
overlay file, 36-5 feature import, 18-1
documentation, 2-3 E
dodger, 22-1
batch processing, 22-12 edit tools, sketch, 58-7
execution, 22-9 elevation change, 61-38
overview, 22-1 environment, 2-4
parameter file, 22-6 EROS B Import, 7-46
user interface, 22-3 ERS import, 12-6
DOQ establishing image location, D-1
edit, 61-40 export
export, USGS, 7-30 AMS, 18-8
drawing tools, sketch, 58-3 ARC, 17-37
DTED ARC_GEN, 18-18
export, 17-41 ASCII ARC grid, batch processing, 17-38
Index-4 SOCET SET

INDEX
ASCII DTM, 17-32 reserved classes & attributes, C-4

ASCII DTM, batch processing, 17-34 feature database merge, 43-1
ASCII feature, 18-23 attributes, 43-8
ASCII features, batch processing, 18-25 execution, 43-10
data, 16-1 features, 43-5
DEM, 17-38 preferences, 43-7
DEM, batch processing, 17-40 feature extraction
DGN features, batch processing, 18-34 area based editing, 42-43
DGN posts, batch processing, 17-56 attribute query, 42-19
DTED, 17-41 attribute validation report, 42-20
DXF feature, 18-16 autocreate parameters, 58-14
DXF features, batch processing, 18-17 automated population of attributes, 42-29
GeoTIFF terrain, batch processing, 17-59 changing an extraction specification, 42-40
image, 7-1, 7-24 clockwise/counterclockwise
Intergraph DGN feature, 18-30 orientation, 42-41
LIN files, 18-10 copying attribute values, 42-40
MP ASCII feature, 18-26 execution
NED FloatGrid, 17-35 ArcSDE db, 42-39
NED GridFloat, batch processing, 17-36 socet set db, 42-36
openflight, 57-1 extracting complex features, 42-41
SDTS, 17-51 feature & element attributes, 42-11
shapefile, 18-27 forcing features to lay on the ground, 42-40
terrain, 17-1 generic features, 42-35
to rendering system, 57-1 graphics attributes, 42-12
USGS DOQ, 7-30 mensuration, 42-21
export to rendering sys model placement, 42-27
openflight, 57-1 monotonic elevation increase/decrease,
extracting 42-41
complex features, 42-41 overview, 42-1
extraction cursor editor, 61-15 polygon topology, 42-7
extraction monitor, stereo, 2-4 retrieve/manipulate, 42-14
extraction specification, C-1, C-3 sample workflow, 3-13
replacing/editing, C-4 scale/rotate, 42-41
reserved classes & attributes, C-4 secondary feature classes, 42-33
eyepoint route editor, 50-18 secondary feature creation, 42-34
simultaneous collection, 42-31
F sketch tools, 42-4
fast sensor model, 7-32 texture patch, 42-24
feathering, 49-12 tips, 42-40
feature volume create tool, 42-22
retrieve/manipulate, 42-14 feature extraction preference options, 42-39
feature database and extraction specification, feature import & export, 18-1
C-1 AMS export files, 18-8
extraction specifications, C-3 ARC_GEN export, 18-18
SOCET SET Index-5

INDEX
ARC_GEN import, 18-5 frame, panoramic & close range import, 8-1
ASCII feature export, 18-23 orientation angles, 8-3
ASCII feature import, 18-7 support data, 8-20
DXF feature export, 18-16
DXF feature import, 18-1 G
Intergraph DGN feature export, 18-30 generic features, 42-35
LIN export files, 18-10 GeoEye-1 Import, 15-1
MP ASCII feature export, 18-26 geographic
shapefile export, 18-27 coordinate system, 5-2
shapefile import, 18-12 geoid, vertical datum, 5-11
feature registration, 30-1 geomorphic editor, 39-36
execution, 30-3 grid DTM format, 39-37
user input, 30-2 geo-position sample workflow, 3-10
window, 30-2 Geopositioning, 56-1
feature specification editor, 41-1 GeoTIFF, 46-12
attribute editor, 41-4, 41-5 GeoTIFF Import batch processing, 17-26
class editor, 41-3 glossary, A-1
features GPS
attribute query, 42-19 entering info manually, 26-18
attributes, 42-11 GPS information, triangulation, 26-18
clockwise/counterclockwise GPS, constraint files, 25-12
orientation, 42-41 graphical attributes, triangulation, 25-13
complex extracting, 42-41 graphics
create tool, 42-22 attributes, 42-12
graphics attributes, 42-12 projection, 61-37
mensuration, 42-21 graphics terrain settings
model placement, 42-27 footprints, 61-3
figures of merit, F-1 north arrow, 61-3
file scale fonts, 61-3
organization, B-1 terrain tracking, 61-3
establishing image location, B-6 grid, 5-10
image location, B-5 grid lines & tick marks, 45-9, 52-11
project data files, B-1 ground point files, triangulation, 25-11
restoring, 6-6 gui language, I-1
flemming (cubic) interpolation, G-4
FOM, F-1 H
font scaling, 61-3
fonts hardcopy products and image maps, 52-1
changing fonts, D-3 anaglyph, 52-6
choosing text fonts, D-2 calibration, 52-20
footprints, 61-3, 61-4 color balancing, 52-13
FORMOSAT 2 Import, 7-35 grid lines, 52-11
frame image enhancment, 52-13
import, 8-1, 8-8 image map, 52-7
Index-6 SOCET SET

INDEX
image previewing tools, 52-2 use image enhancement, 4-13

margin templates, 52-10 use image scaling, 34-1
print graphics, 52-24 use main triangulation window, 25-17
printing images, 52-4 use map accuracy assessment, 32-2
screen dumps, 52-3 use map registration, 31-1
tick marks, 52-11 use mosaic, 49-2
hosts.equiv, D-9 use orthophoto, 46-2
hot-keys, D-4 use perspective scenes, 50-2
control point editor, 19-1, J-1 use terrain analysis, 51-1
coordinate measurement, 19-1, J-1 use terrain graphics, 36-1
DTM registration, 19-1, J-1
feature registration, 19-1, J-1 I
how to icon list, annotation, 45-10
change default cursor, 61-17 IKONOS images, 7-8
change fonts, D-3 IKONOS, space imaging, 7-16
copy a project, 5-16 image
define DTM boundaries, 35-10 enhancement, 46-11
DTM registration, 29-1 export, 7-1
edit DTM using interactive terrain edit, export/reformat, 7-29
39-1 filters, 4-22
find images quickly, B-8 IKONOS, 7-8
group images into strips, 26-4 import, 7-1
rectify an image, 33-2 information, 61-35
remove location, establishing, B-6
automatic parallax, 27-24 minification, 21-1
manual parallax, 27-23 moving, B-7
remove parallax, 27-23 MrSid, 7-8
run annotation, 45-1 panoramic import/edit, 8-17
run camera calibration, 61-6 space, 7-8
run correlation band selector, 61-39 image balancing
run image map, 52-8 batch processing, 22-12
run line of sight (LOS), 53-2 dodger, 22-1
run quality statistics, 61-26 execution, 22-9
run setup, triangulation, 26-17 overview, 22-1
scan imagery imported in unknown mode, parameter file, 22-6
26-6 user interface, 22-3
scan strips of frame imagery, 26-6 image data, triangulation, 26-12
use change detection, 48-1 image enhancement, 52-13
use coordinate measurement, 59-1 filters, 4-22
use dodger, 22-2 orthophoto, 46-11
use DTM/feature merge, 44-1 image export/reformat, 7-24
use feature extraction, 42-2 image files, triangulation, 25-11
use feature registration, 30-1 image header update, 61-41
use graphical display window, 25-21 image import
SOCET SET Index-7

INDEX
IKONOS, 7-16 duplicate names, B-8

rapid positioning capability, 7-16 flicker, 61-36
space imaging, 7-16 import
image import & export, 7-1 ARC, 17-10
image import/export ARC_GEN, 18-5
data handling capabilities, 7-3 ASCII DTM, 17-1
image export/reformat, 7-24 ASCII DTM, batch processing, 17-7
image import/reformat, 7-9 ASCII feature, 18-7
USGS DOQ export, 7-30 ASCII features, batch processing, 18-12
image import/reformat, 7-9 ASCII image points, batch processing,
image loader, 4-10 16-11
image location, B-5, D-1 data, 16-1
image management, 2-5 DEM, 17-11
image map, 52-7 DEM, batch processing, 17-13
brightness, 52-13 DTED, 17-13
DTM contour lines, 52-12 DTED, batch processing, 17-16
execution, 52-22 DXF feature, 18-1
graphic clipping, 52-13 DXF features, batch processing, 18-4
production sample workflow, 3-14 ERS, 12-6
window, 52-15 frame, 8-1, 8-8
image minification, 21-1 GeoTIFF, 17-26
execution, 21-4 ground point, 16-3
image location, 21-2 image, 7-1
window, 21-3 image point, 16-5
image point IRS, 11-13
files, triangulation, 25-11 JERS, 11-9
import, 16-5 landsat, 10-1
image points NED GridFloat, 17-8
interactive point measurement, 27-23 panoramic image import/edit, 8-17
image previewing tools, 52-2 quickbird, 9-1
image RADARSAT import, 12-4 RADARSAT, 12-1
image rectification, 33-1 RADARSAT image, 12-4
define SDTS, 17-16
single image, 4-25, 33-3 shapefile, 18-12, 18-15
execution SPOT, 11-4
pairwise, 33-7 SPOT DIMAP, 11-7
single image, 4-26, 33-5 terrain, 17-1
rectification window, 33-3 input file bundle measurement, triangulation,
ways of performing, 33-2 25-13
image scaling, 34-1 interactive point measurement, 27-14
execution, 34-3 interactive terrain edit, 39-1
zoom/scale window, 34-2 area editor, 39-12
image support files, triangulation, 25-11 convolution matrix editor, 39-31
images posts display, 39-32
Index-8 SOCET SET

INDEX
posts-query editor, 39-28 sample workflow, 3-14

execution, 39-38 limitations and constraints, H-1
geomorphic editor, 39-36 LIN export files, 18-10
post editor - GRID DTM format, 39-11 line of sight (LOS), 53-1
post editor - TIN DTM format, 39-10 local devices, D-8
terrain shaded relief options, 39-4 locking cursor, triangulation, 27-23
user inputs, 39-2 LOS, 53-1
interactive terrain edit tools execution, 53-8
edit tools, 39-10 obstruction measurement annotation, 53-6
Intergraph DGN data format conversions, obstruction measurement information, 53-5
17-53 vector annotation, 53-5
Intergraph DGN feature export, 18-30 vector comparison, 53-7
interior orientation, 24-1 vector info, 53-4
automatic, 24-3 vector ring marker, 53-6
execution, 24-8 LSR
semi-auto measurement, 24-10 coordinate system, 5-7
internal
database configuring, D-9 M
internationalization, I-1 main workstation window, 4-1
interpolation and resampling, G-1 auto loader, 4-12
bilinear interpolation, G-2 monitors
flemming interpolation, G-4 console, 4-2
nearest neighbor interpolation, G-1 extraction, 4-2
overview, G-1 image loader, 4-10
pixel averaging, G-3 roaming, 4-2
weighted mean interpolation, G-2 primary view port, 4-7
IRS import, 11-13 pull-down menu, 4-3
J map accuracy assessment, 32-1
assessment, 32-11
JERS import, 11-9 execution, 32-11
job queue manager, 3-3 mensuration, 32-8
setup, 32-6
K start, 32-5
keyboard, 1-5 map registration, 31-1
keyboard & accelerator mapping, 61-18 execution, 31-5
keyboard commands, accelerator, J-1 window, 31-2
margin templates, 52-10
L mensuration, 42-21
menu pull-down, 4-3
LADAR import, 17-20 merge DTM/features, 44-1
landsat image import window, 10-3 minification
landsat import, 10-1 batch processing, 21-5, 52-26, 52-27
image, 10-3 image, 21-1
layer mosaic model placement, 42-27
SOCET SET Index-9

INDEX
monitors NED GridFloat export, 17-35

console, 4-2 NED GridFloat import, 17-8
extraction, 4-2 newlink limits, H-1
imagery loader, 4-10 NGATE, 38-1
roaming, 4-2 NGATE Batch Processing, 38-9
stereo extraction, 2-4 NGATE Properties, 38-3
mosaic, 49-1 NITF
auto range adjust, matching, 49-19 image export/reformat, 7-24
automatic range adjustment, 49-14, 49-15 north arrow, 61-3, 61-4
corner point, 49-11
DTM post spacing, 49-14 O
execution, 49-21 object coordinates, triangulation, 25-13
feathering, 49-12 openflight, 57-1
GeoTIFF output, 49-19 output window, 57-3
grid lines, 49-14, 49-19 openflite sample workflow, 3-15
image enhancement, 49-14 operating environment, 2-4
input DTM, 49-14, 49-19 OrbView-3 Import, 14-1
mosaic manager organizing data with projects, 5-1
input, 49-7 orientation
output, 49-8 angles, frame & etc., 8-3
mosaicing methods, 49-13 clockwise/counterclockwise, 42-41
overview, 49-1 orthophoto, 46-1, 46-11
seamline editor, 49-26 batch processing, 46-16
shape & orientation, 49-10 color balancing, 46-11
sheet cutter, 49-32 execution, 46-15
window, 49-3 generation and image mosaicking sample
mouse workflow, 3-14
recentering, 1-5 generation window, 46-3
moving image, B-7 GeoTIFF output, 46-12
MP ASCII feature export, 18-26 image enhancement, 46-11
mport, 17-26 overview, 46-1
MrSid, 7-8 rectifying, 46-2
MSL, 5-11 removing building lean, 46-8
multi-spectral grey merge, 47-1 shape & orientation, 46-9
multi-spectral imagery sharpening, 47-1 output
multi-spectral sharpening, 47-3 GeoTIFF, 46-12
data flow, 47-2 option window, 57-5
DTM input, 47-1 SPOT, 11-3
execution, 47-7
output image, 47-2 P
registration, 47-1
panoramic triangulation, 25-23
N PAT-B, 8-23
perspective scenes, 50-1
nearest neighbor interpolation, G-1
Index-10 SOCET SET

INDEX
aim point route setup, 50-17 changing coordinates, 5-14

aim route editor, 50-24 copying data files between projects, 5-14,
animation, 50-34 5-16
data flow, 50-2 organizing data, 5-1
edit way-point, 50-21 parameters, 5-2
eyepoint attribution, 50-27 reviewing and editing a project, 5-14
eyepoint route setup, 50-17 project parameters, 5-2
multiple scene mode, 50-10 projection,graphics, 61-37
multiple scene window, 50-7 pull-down menu, 4-3
overview
advanced features, 50-14 Q
color imagery, 50-16 quality statistics, 61-26
feature file prep., 50-14 quickbird import, 9-1
terrain file prep., 50-14 quickbird import batch processing, 9-3
sample workflow, 3-15
scene content selection, 50-30 R
scene parameter setup, 50-32
scene rendering, 50-34 RADARSAT & ERS import, 12-1
single scene mode, 50-5 ERS import, 12-6
single scene window, 50-4 RADARSAT import, 12-1
terminology, 50-2 radian/degree conversion, 61-15
window, 50-4 rapid positioning capability, 7-16
photo data, frame, pan, close range, 8-20 rectification, image, 33-1
pixel averaging, G-3 Reference, 42-37
point measurement, resetting, triangulation, reference backgrounds, vct, 20-17
25-17 reformat image, 7-24
polygon topology, 42-7 registration, DTM, 29-1
polynomial sensor model, 7-32 relative orientation, triangulation, 28-15
power-up workstation, 1-1 remote
preferences devices, D-8
preference files, D-6 login, D-8
primary view port window, 4-7 report editor, 61-13
print graphics, 52-24 reserved classes & attributes, C-4
execution, 52-25 resetting point measurement, triangulation,
printer 25-17
configuration restore archived data, 6-5
format, D-7 restoring files, 6-6
sample, D-7 reviewing and editing a project, 5-14
configuration file, D-7 S
printing images, 52-4
project data files, B-1 sample workflows, 3-7
project data files transfer, 5-18 save image load point, 4-3
project data review, 61-23 scheduling batch jobs, E-3
project management, 5-1 screen dumps
SOCET SET Index-11

INDEX
unix, 52-3 SPOT DIMAP

windows, 52-3 import, 11-7
SDTS export, 17-51 SPOT, JERS & IRS import
SDTS import, 17-16 IRS import, 11-13
seamline editor, 49-26 JERS import, 11-9
semi-auto. measurement, interior orientation, outputs, 11-3
24-10 SPOT DIMAP import, 11-7
sensor models, 2-6 SPOT import, 11-4
shaded relief, 36-6 start at, E-2, E-3
shape & orientation, mosaic, 49-10 stereo extraction monitor, 2-4
shapefile stereo imagery, 2-8
export, 18-27 controlling workflow, 3-9
import, 18-12 overlapping, 35-2
shapefile import, batch processing, 18-15 stereo model manager, 61-24
sharpening display list, 61-24
multi-spectral imagery, 47-1 model list, 61-24
sheet cutter, mosaic, 49-32 strategy
simultaneous collection, 42-31 ATE, 35-4
simultaneous solve, triangulation, 28-10 custom ATE, 35-5
sketch, 58-1 sup (file suffix), B-4
actions, 58-13 system administration, 1-1
advanced drawing tools, 58-11
AFE single feature mode, 42-19 T
annotation, 45-4 tape drives
drawing tools, 58-3 configuration file, D-4
edit tools, 58-7 terminology, perspective scenes, 50-2
examples, 58-19 terrain
feature extraction, 42-4 ASCII import ground points, 16-3
preferences, 58-14 automatic extraction, 37-1, 38-1
toolbox, 58-1 converting to feature vectors, 36-5
SOCET for ArcGIS, 19-1 display
basic workflow, 19-7 graphics, 36-4
software see ATE, 37-1, 38-1
description, 2-5 tracking, 1-4, 61-4
solution strategy file, triangulation, 28-16 terrain analysis, 51-1
solution type/setup files, triangulation, 26-14 execution, 51-3
solve strategy files, triangulation, 25-12 visibility analysis, 51-1
space imaging, 7-8 window, 51-1
space imaging, IKONOS, 7-16 terrain extraction in urban areas workflow,
special rules, triangulation, 26-5 3-13
SPOT terrain file creation, 35-1
import, 11-4 choosing an ATE method, 35-3
outputs, 11-3 create
triangulation, 25-23 DTM window, 35-6
Index-12 SOCET SET

INDEX
creating a DTM, 35-2 extraction, 42-40

define DTM boundaries, 35-10 changing an extraction spec, 42-40
polygon strategy, 35-2 copying attribute values, 42-40
user input, 35-6 forcing features to lay on the ground,
terrain graphics, 36-1 42-40
contour lines, 36-6 monotonic elevation +/-, 42-41
converting to feature vectors, 36-5 scale/rotate, 42-41
display overlay file, 36-5 triangulation, 25-23
displaying w/o imagery, 36-6 toolbox, sketch, 58-1
DTM, 36-1 tools
graphics, 36-4 apmstats, 61-2
range, 36-3 conv_spec, 61-2
setup, 36-1 copy_spot_disk, 61-2
execution, 36-4 copy_spot_to_tape, 61-2
overlay range, 36-3 dtm_compare, 61-2
overlay setup, 36-1 dump_screen, 61-2
shaded relief, 36-6 flicker images, 61-36
terrain import/export, 17-1 flip_image, 61-2
ARC grid export, 17-37 ftr_to_dst, 61-2
ASCII ARC grid import, 17-10 img_band_merge, 61-2
ASCII DTM export, 17-32 img_cut, 61-2
ASCII DTM import, 17-1 img_join, 61-2
DEM export, 17-38 make_arc, 61-2
DEM import, 17-11 make_shortsup, 61-2
DTED export, 17-41 media_state, 61-2
DTED import, 17-13 mp_asc_import, 61-2
Intergraph DGN data format conv., 17-53 ortho_qa_file_read, 61-2
NED GridFloat export, 17-35 ortho_qa_make_sup, 61-2
NED GridFloat import, 17-8 ortho_qa_merge_orthos, 61-2
SDTS export, 17-51 ortho_qa_stats, 61-2
SDTS import, 17-16 pgmkill, 61-3
terrain tracking, 61-3 platform_swap_grid_dtm, 61-3
TerraSAR-X, 7-52 ss_hostid, 61-3
text file start_socet, 61-3
editing, 61-14 tape_struct, 61-3
opening, 61-14 tiffinfo, 61-3
printing, 61-14 tkbtest, 61-3
texture patch, 42-24 topology, polygon, 42-7
tick marks, 52-11 trackball, 1-5
tie point trackball accelerator mapping, 61-18
pattern file, 27-9 tracking
pattern file, triangulation, 25-13 sensitivity
tips mouse, 61-20
blunder detection, 28-8 trackball, 61-20
SOCET SET Index-13

INDEX
transferring project data files, 5-18 automatic, 27-2

triangular DTM format, 39-36 control points, 27-23
triangulation entering control points, 27-26
geomorphic editor, 39-36 graphical display, 27-27
graphical display window, 25-18 ground point file, 27-15
stereo pair, 3-9 image point file, 27-15
triangulation overview & workflow, 25-1 image points, 27-23
automatic point measurement, 25-17 interactive point measurement, 27-14
backing up data, 25-17 locking the cursor, 27-23
batch processing - MST, 25-9 model check, 27-27
data files, 25-10 remove parallax, 27-23
auto point measurement strategy files tie point pattern file, 27-9
(.apm_strat), 25-12 triangulation setup & GPS, 26-1
constraint files (.cns), 25-11 entering info manually, 26-18
graphical attributes (.gra), 25-13 GPS file format, 26-18
ground point files (.gpf), 25-11 GPS information, 26-18
image files, 25-11 group images into strips, 26-4
image point files (.ipf), 25-11 image data, 26-12
image support files (.sup), 25-11 image parameter weights, 26-22
input file bundle measurement (imag- overview, 26-1
es.meas), 25-13 scan imagery imported in unknown mode,
object coordinates (object.ini), 25-13 26-6
solve strategy files (.solve), 25-12 scan strips of frame imagery, 26-6
tie point pattern file (.tpp), 25-13 setup tips, 26-17
triangulation files (.atf), 25-10 solution type/setup files, 26-14
GPS, constraint files, 25-12 special rules, 26-5
graphical display, 25-18 triangulation solve, 28-1
interactive point measurement, 25-17 absolute orientation errors, 28-9
large block images, 25-7 blunder
main triangulation window, 25-14 detect & solve, 28-1
multi-images, 25-5 detection tips, 28-8
multi-images blocked, 25-6 processing, 28-9
panoramic, 25-23 constraint files, 28-16
parallel processing, 25-8 initialize/solve, 28-1
recovering from errors, 25-17 relative orientation, 28-15
resetting point measurements, 25-17 simultaneous solve, 28-10
sample execution scenarios, 25-4 solution strategy file, 28-16
setup, 25-17 solution types, 28-1
single image, 25-5 troubleshooting unresponsive workstation, 1-2
SPOT, 25-23 true orthophoto, 46-8
tips, 25-23 two-handed controller, 1-4
triangulation point measurement, 27-1 typographic conventions, 2-3
adding control points, 27-25
auto measure all, 27-26
Index-14 SOCET SET

INDEX
U data managers, 20-10

getting started, 20-2
units reference backgrounds, 20-17
project, 5-11 vertical reference, 5-11
universal transverse mercator (UTM), 5-11 viewing window, 4-7
unresponsive workstation, 1-2 visibility analysis, DTM, 51-1
USGS DOQ visual coverage tool (vct), 20-1
export, 7-30 volume create tool, 42-22
USMSD generation, 26-15
utilities, 61-1 W
camera calibration, 61-5
w/s op. inst.
distortion parameters, 61-12
accelerator mapping, 1-5
execution, 61-13
overview, 1-1
fiducial coordinates, 61-10
power-up, 1-1
change elevation, 61-38
recenter the mouse, 1-5
changing default cursor, 61-17
weighted mean interpolation, G-2
correlation band selector, 61-39
windows
cursor editor, 61-15
absolute check point, 28-8
DOQ edit, 61-40
accelerator mapping, 1-5, 61-18
fast sensor model, 7-32
albany triangulation, 8-23
flicker images, 61-36
anaglyph, 52-6
footprints, 61-4
animation, 50-34
graphics projection, 61-37
annotation, 45-4
graphics/terrain settings, 61-3
ARC_GEN export, 18-18
image information, 61-35
ARC_GEN import, 18-5
keyboard & accelerator mapping, 61-18
area editor, 39-12
north arrow, 61-4
area to process, 57-4
project data review, 61-23
ASCII ARC grid export, 17-37
quality statistics, 61-26
ASCII ARC grid import, 17-10
quality statistics check point file vs. mea-
ASCII DTM assign code description, 17-5
sured point file, 61-28
ASCII DTM export, 17-19, 17-32
radian/degree conversion, 61-15
ASCII DTM import, 17-2
report editor, 61-13
ASCII feature export, 18-23
stereo model manager, 61-24
ASCII feature import, 18-7
terrain tracking, 61-4
ASCII ground point import, 16-3
trackball accelerator mapping, 61-18
ASCII image point import, 16-6
tracking sensitivity, 61-20
ATE statistics, 37-6
y parallax, 61-22
attribute editor, 41-4, 41-5
UTM
attribute query, 42-19
coordinate system, 5-11
auto loader, 4-12
V autocreate parameters, 58-14
automated triangulation/full block, 25-14
vct automatic interior orientation (AIO), 24-3
basic functions, 20-3 automatic point measurement (APM), 27-4
SOCET SET Index-15

INDEX
automatic terrain extraction, 37-4 DXF feature export, 18-16

backup, 6-2 DXF feature import, 18-1
backup log, 6-4 edit way-point, 50-21
bingo triangulation, 8-24 eyepoint attribution, 50-27
block transform failure report, 28-8 fast sensor model, 7-32, 61-39
blunder detection progress report, 28-4 feature and element attributes, 42-11
camera calibration editor, 61-8 feature extraction, 42-4
camera location, panoramic, 8-21 feature information, 42-11
change detection, 48-2 feature information, data review, 61-23
change elevation, 61-38 feature registration, 30-2
class algorithm edit, 44-10 feature retrieval, 42-15
class editor, 41-3 fiducial coordinates, 61-10
clearflite file location, moving image, B-7
extract obstructions-automatic, 40-13 file location, new, B-6
extract obstructions-edit, 40-14 find conjugate point in the right eye, 27-8
extract obstructions-manual, 40-12 find point in both the left and right eye,
feature retrieval, 40-15 27-8
highest above OIS feature, 40-17 frame import, 8-8
identification, 40-5 generic features, 42-35
report generation, 40-17 geomorphic editor, 39-36, 39-37
z bias actions, 40-16 graphical display, 25-18
clearfllite graphics attributes, 42-12
cursor tracking, 40-10 grid lines, 49-14, 49-19
control point editor, 23-3 icon list, 45-10
coordinate measurement, 59-2 image data, 26-12
coordsys/datum conversion, 59-5 image export/reformat, 7-24
copy project, 5-17 image information, 61-35
correlation band selector, 61-39 image loader, 4-10
create DTM, 35-6 image map, 52-15
create/edit project, 5-4 image map-show/edit device, 52-17
cursor editor, extraction, 61-15 interactive point measurement, 27-16
delete, 6-7 interactive terrain edit, 39-3
DEM export, 17-39 Intergraph DGN feature export, 18-30
DEM import, 17-11 kernel editor, 4-23
DGN post export, 17-54 LADAR import, 17-20
display parameters, 28-14 landsat image import, 10-3
distortion parameters, 61-12 line of sight, 53-2
DOQ edit, 61-40 LOS vector annotation, 53-5
DTED export, 17-42 LOS vector comparison, 53-7
DTM feature merge, 44-4 LOS vector information, 53-4
DTM information, 44-7 LOS vector ring marker, 53-6
DTM range, 36-3 main workstation, 4-1
DTM registration, 29-2 main workstation menu, 4-3
DTM setup, 36-1 map accuracy assessment
Index-16 SOCET SET

INDEX
assessment, 32-11 route editor - eyepoint, 50-18

mensuration, 32-8 save image load point, 4-3
setup, 32-6 scene parameter setup, 50-32
start, 32-5 secondary feature creation, 42-34
map registration, 31-2 select new description file (ASCII DTM),
margin setup, 52-16 17-5
mensuration, 42-21 set pivit point, 50-29
minification, 21-3 setup, triangulation, 26-3
model connection failure report, 28-7 shapefile export, 18-27
model placement, 42-27 shapefile import, 18-12
mosaic, 49-3 simultaneous collection, 42-31
mosaic manager sketch preferences, 58-14
input, 49-7 solution type/setup files, 26-14
output, 49-8 specification editor, 41-1
move to point display, 59-8 start at, E-3
MP ASCII feature export, 18-26 strip connection failure report, 28-8
multi-sensor triangulation residuals, 28-12 terrain analysis, 51-1
multi-spectral sharpening, 47-3 texture patch, 42-25
obstruction measurement annotation, 53-6 ticks and gridlines, 45-7
obstruction measurement information, 53-5 tie point pattern, 27-7
openflight output, 57-3 tracking sensitivity, 61-20
orthophoto generation, 46-3 visibility analysis generation, 51-1
output options, 57-5 volume create, 42-22
overlay range, 36-3 zoom/scale, 34-2
overlay setup, 36-1 workflow
panoramic import/edit, 8-17 customizing, 3-1
pat-b triangulation, 8-23 job queue manager, 3-3
perspective scene, 50-4 sample, 3-7
perspective scenes - multiple scenes, 50-7 automatic terrain extraction, 3-12
perspective scenes - single scene, 50-4 building an MC&G product, 3-16
photo data, 8-20 DTM creation, 3-10
point distribution check failure report, 28-5 feature extraction, 3-13
posts display, 39-32 geo-position, 3-10
print graphics, 52-24 getting started, 3-7
projection, 61-37 image map production, 3-14
quality statistics check point vs. measured importing an image, 3-7
point, 61-28 layer mosaicking, 3-14
quickbird import, 9-2 making S3 mosaics, 3-17
RADARSAT import, 12-4 merging features and DTMs, 3-12
radian/degree, 61-15 Openflite, 3-15
rectification, 33-3 orthophoto generation and image mosa-
relative orientation failure report, 28-6 icking, 3-14
restore, 6-5 perspective scenes, 3-15
route editor - aim point, 50-24 photo-interpretation, 3-8
SOCET SET Index-17

INDEX
single image data extraction, 3-9

terrain extraction in urban areas, 3-13
triangulate a stereo pair, 3-9
triangulating a single image, 3-8
wrapping up a project, 3-17
workstation
accuracy, 2-7
components, 2-3
coordinate system & datums, 2-8
description, 2-1
documentation, 2-3
image management, 2-5
operating environment, 2-4
operating instructions, 1-1
operator controls, 2-4
purpose, 2-1
sensor models, 2-6
software description, 2-5
stereo extraction monitor, 2-4
stereo imagery, 2-8
typographic conventions, 2-3
wrapping up a project, sample workflow, 3-17
X
X & Y directions, 1-3
Y
y parallax, 61-22
Z
Z direction, 1-3
zoom toggle, 1-5
zoom/scale, 34-1
Index-18 SOCET SET

®
1.2.6 Adjusting Brightness and 1.2.12 Displaying Current Cursor

Quick Reference Guide Contrast Coordinates
• Drag the slider bars to the right to increase; drag to • Select Tools > Coordinate Measurement
Version 5.5 the left to decrease
April 2009 1.2.13 Roaming in 3D Ground
1.2.7 Changing Elevation without Space
1.2 The Basics a Trackball
• Toggle to the extraction cursor
• Select Tools > Change Elevation • Move the mouse and/or trackball
1.2.1 Creating a Project • To re-center the image at the new extraction cursor
• Move slider to adjust elevation
location either: press the left button on the trackball,
• Select Project > Create/Edit Project • Change scale value to increase or decrease
-OR- press the F2 key on the keyboard
• Select File > New sensitivity
• Use Move To Point in Coordinate Measurement tool
• Enter project name to drive the cursor to a particular coordinate location
• Select coordinate system & datum
• Enter minimum & maximum elevations
1.2.8 Auto Brightness/Contrast • To raise or lower the extraction cursor height, roll the
trackball either forward or backward
• Select Auto Brightness/Contrast ON to have SOCET • To “snap” to ground level, press the right trackball,
1.2.2 Loading a Project SET automatically adjust the images -OR- button “F1” on the 3D mouse
• Select Image Brightness/Contrast to change the full • Note that the position of the extraction cursor
• Select File > Load Project range of image pixels for more precise, but slower changes as you change its height; the sensor model
• Select project name adjustment projects the cursor onto each image according to the
new height
• Click OK button
• You may need to recenter the imagery (with the left
1.2.9 Zooming In/Out trackball button, or the F2 key on the keyboard) to
1.2.3 Importing Imagery perceive stereo
• Select Preparation > Import >Image >image_type

• Select the tape device that the tape is mounted on • Select 1:1 to zoom in, select 2:1 or greater to zoom 1.3 Advanced Procedures
-OR- select the input image file out
• Enter the image file name • If only a 1:1 Zoom level is available, run Minification 1.3.1 Controlling Imagery
• Click the Start button • Press the F6 key for previous Zoom
• Import images
• <ALT>PageUP: Zoom In
• Run Interior Orientation, if film based images
1.2.4 Displaying Image(s) • <ALT>PageDown: Zoom Out
• Import ground control point file (if you don’t have
ground control data in a file yet, enter it during the
• Select File > Load Images
• Select left and/or right images to display
1.2.10 Toggling the Cursor Interactive Point Measurement phase of
Triangulation)
Mouse Extraction
• Click the OK button • Run Triangulation to measure the ground control
Cursor Cursor points in your imagery and perform simultaneous
adjustment
1.2.5 Image Enhancement • Press the middle button on the trackball -OR-
• Press the F3 key on the keyboard
• Select any or all of the tools needed from the Image 1.3.2 Extracting Terrain
Enhancement Toolbar
• Choose from: TTC, HISTOGRAM, ZOOM, FILTER, 1.2.11 Pull Cursor back to Center • Import and orient stereo images
RESET, INVERT, MAGNIFY, ROTATE, CHIP, and • Display the stereo image on main image display
SAVE • Press the Home key on the keyboard • Select View/Edit/New DTM File from Automatic
Extraction > File to create and extract a terrain file. 1.3.6 Creating a Mosaic to the hidden building sides
Two or more images are required • Select Products > Perspective Scenes
• Run Interactive Terrain Editing to review & revise • Select Products > Mosaic • Select File > Load to create a perspective scene
• Run DTM/Feature Merge to combine with other • Select a DTM with any number of images parameter file
DTMs (optional) • Select a Seam Polygon database that contains your • Specify the images and DTM. Input a feature
seam lines (optional - if you skip this, SOCET SET Database. Delineate the route for the imagery viewer
can automatically make the seams) • Determine the number of scenes to be generated
1.3.3 Displaying Terrain • Select a mosaic method, interpolation method, grid and generate
lines, etc. • Validate the quality of the scenes by reviewing them
• Load the imagery you extracted the terrain data from. with Animation
If you don’t have imagery, use the • Select Auto Range Adjust for balancing (optional)
GRAPHICS_ONLY.sup pseudo-image • Edit the four corners for the boundary
• Select Extraction >Terrain >Interactive Terrain Edit • Click the Start button to begin creating the 1.3.10 Some Common examples
orthophoto mosaic
• Select File > Load DTM and select a terrain file of Windows systems
• Click the DTM Setup button and select a drawing socet_config.bat entries:
mode (dots, contours, mesh, etc.) and a color source 1.3.7 Creating an Image Map
(monochrome, elevation, FOM, etc.) • To change the default directory for SOCET SET
• Click the Change Default Range Values button to set • Create an Orthophoto as described above projects and imagery to D:\my_data, add the
up the colors for rendering the terrain graphics • Extract a feature database of the region (optional) following: set DATA_DIR=d:\my_data
• Click the Done button to dismiss the Setup DTM • Use Interactive Terrain Editing to draw DTM contours • To change the behavior of SOCET SET to NOT
window (optional) produce JPEG compressed images from the
• Click the Draw button • Select Products > Image Map. Specify feature and minification process when a JPEG compressed
image files named above. Use margin setup window image is input, add the following:
to specify output margin border widths
1.3.4 Extracting Features • Select Extraction > Annotation & Counting and draw
set DONT_COMPRESS_OUTPUT=1
• To use an Immersion 3D mouse connected to COM2
the margin template, grid lines, tick marks, and other as the tracking device, add the following:
• Select Extraction > Feature
graphical overlays. Leave Annotation running set TRACKBALL_KIND_2=IBOX \
• Click Feature Database button
• Turn Interactive Graphic on set TRACKBALL_DEVICE_2=COM2
• Type in new filename or select an existing file • Select start and wait for Image Map to complete
• If new file select a spec file • To trap error and warning messages generated by
• Verify the Image Map: Exit Annotation, load the SOCET SET to the log file named messages.log in
• Click Current Class button Image Map (PREVIEW.sup) into the main
• Select from available class the HOME directory, add the following:
workstation window set LOGFILE=message.log
• Move cursor to desired position and press left mouse • Print or export the Image Map
button
• Continue defining vertices with left mouse button
• Right mouse button (RMB) to end 1.3.8 Improving Stereo
Visualization
1.3.5 Creating an Orthophoto • Select Pairwise Rectify from the Image
Enhancement Toolbar
• Select Products > Orthophoto Generation
• Select a DTM and one image
• Enter the name of the output orthophoto image 1.3.9 Generating Perspective
• Enter the ground sample distance of the output Scenes
orthophoto image
• Edit the four corners to change the footprint of the • Create and extract a DTM
output orthophoto • Extract feature database containing the buildings to
• Click the Start button to begin creating the be modelled in the Perspective Scene
orthophoto • If feature database extracted, attach image patches
1.4 Sketch Hotkeys <Ctrl> u
<Ctrl> z
Undo
Measure
<Ctrl> p Preferences
PgDn Next
1.4.1 Draw Tools: PgUp Previous
<Ctrl> PgDn Next Point
<Ctrl> F2 Curve <Ctrl> PgUp Previous Point
<Ctrl> F3 Arc LMB or / Sample
<Ctrl> F4 Stream MMB or
<Ctrl> F5 Rectangle <Alt>F7 Snap
<Ctrl> F6 Static RMB or * Accept/Reset
<Ctrl> F8 On-the-fly-square Esc Cancel
<Ctrl> F9 Square after accept
<Ctrl> F10 AFE Rooftop
<Ctrl> F11 AFE Lake
<Ctrl> F12 AFE Refine
<Alt> c Circle
1.4.2 Volumetric Draw Tools

<Alt> F7 Conical
<Alt> F8 Top-Bottom
1.4.3 Advance Draw Tools:

= Parallel
\ Monotonic
<Ctrl> g Share Segment
<Ctrl> d Change Direction
1.4.4 Edit Tools:

<Shift> F8 Delete
<Ctrl> q Select
<Ctrl> l Move Vertex
<Ctrl> f Move Feature
<Ctrl> c Copy
<Ctrl> r Rotate
<Ctrl> s Scale
<Ctrl> x Split
<Ctrl> n Insert Multiple Vertices
Insert Insert Vertex
Delete Delete Vertex
1.4.5 Toggles:
<Ctrl> v Display Vertices
<Ctrl> a Edit Shared Vertices
<Ctrl> e Edit Element
<Ctrl> b Rubberband
<Ctrl> t MBR
1.4.6 Action:

SOCETSET User Man

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

SOCETSET User Man

Transféré par

Droits d'auteur :

Formats disponibles

SOCET SET User’s Manual

Export Controlled Data

Italic New terminology, names of separate documents, command line argument

Typewriter Commands (followed by the manual section number in parentheses), Unix

Special warnings and other critical information for you to consider.

RMB click Will bring up a C o n t e x t M e n u dependent upon the area clicked.

See... on page... Hypertext to additional information.

Chapter 1 Workstation Operating Instructions - - - - - - - - - - - - - - - - - - - 1-1

Chapter 2 Workstation Description - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-1

Chapter 3 Workflow - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-1

Chapter 4 Main Workstation Window - Full Roam - - - - - - - - - - - - - - - - 4-1

Chapter 5 Project Management - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-1

Chapter 6 Backup, Restore and Delete - - - - - - - - - - - - - - - - - - - - - - - - - 6-1

Chapter 7 Image Import and Export - - - - - - - - - - - - - - - - - - - - - - - - - - 7-1

SOCET SET TOC-1

Chapter 8 Frame and Panoramic - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 8-1

Chapter 9 QuickBird WorldView Import - - - - - - - - - - - - - - - - - - - - - - - 9-1

Chapter 10 Landsat Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 10-1

Chapter 11 SPOT, JERS and IRS Import - - - - - - - - - - - - - - - - - - - - - - - 11-1

TOC-2 SOCET SET

JERS Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 11-9

Chapter 12 RADARSAT and ERS Import - - - - - - - - - - - - - - - - - - - - - - 12-1

Chapter 13 ADS40 Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 13-1

Chapter 14 OrbView-3 Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 14-1

Chapter 15 GeoEye-1 Import - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 15-1

Chapter 16 Data Import and Export- - - - - - - - - - - - - - - - - - - - - - - - - - - 16-1

Chapter 17 Terrain Import and Export - - - - - - - - - - - - - - - - - - - - - - - - 17-1

SOCET SET TOC-3

NED GridFloat Export - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17-35

Chapter 18 Feature Import and Export - - - - - - - - - - - - - - - - - - - - - - - - 18-1

Chapter 19 SOCET for ArcGIS® - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 19-1

Chapter 20 Visual Coverage Tool - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 20-1

Chapter 21 Image Minification- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 21-1

Chapter 22 Image Balancing: Dodger - - - - - - - - - - - - - - - - - - - - - - - - - - 22-1

TOC-4 SOCET SET

Chapter 23 Control Point Editor - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 23-1

Chapter 24 Interior Orientation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 24-1

Chapter 25 Multi-Sensor Triangulation - Overview and Workflow - - - - - 25-1

Chapter 26 Multi-Sensor Triangulation - Setup and GPS - - - - - - - - - - - - 26-1

Chapter 27 Multi-Sensor Triangulation - Point Measurement - - - - - - - - 27-1

Chapter 28 Multi-Sensor Triangulation - Solve - - - - - - - - - - - - - - - - - - - 28-1

Chapter 29 DTM Registration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 29-1

SOCET SET TOC-5

Chapter 30 Feature Registration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 30-1

Chapter 31 Map Registration- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 31-1

Chapter 32 Map Accuracy Assessment - - - - - - - - - - - - - - - - - - - - - - - - - 32-1

Chapter 33 Image Rectification - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33-1

Chapter 34 Image Scaling - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 34-1

Chapter 35 Terrain File Creation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 35-1

Chapter 36 Terrain Graphics- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 36-1

Chapter 37 Automatic Terrain Extraction - - - - - - - - - - - - - - - - - - - - - - 37-1

TOC-6 SOCET SET

Chapter 38 Next Generation Automatic Terrain Extraction - - - - - - - - - - 38-1

Chapter 39 Interactive Terrain Edit - - - - - - - - - - - - - - - - - - - - - - - - - - - 39-1

Chapter 40 ClearFlite - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 40-1

Chapter 41 Feature Specification Editor - - - - - - - - - - - - - - - - - - - - - - - - 41-1

Chapter 42 Feature Extraction- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-1

SOCET SET TOC-7

Simultaneous Collection - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42-31

Chapter 43 Feature Database Merge - - - - - - - - - - - - - - - - - - - - - - - - - - 43-1

Chapter 44 DTM/Feature Merge - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44-1

Chapter 45 Annotation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 45-1