Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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
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
<Text> Hovering over the word or phrase will provide additional information.
File > Exit Execution commands done by clicking on menus or buttons with the
cursor.
ii SOCET SET
Table of Contents
TABLE OF CONTENTS
Important Notices - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -1
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
Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22-1
Image Dodge and Balance - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22-3
Execution - Dodger- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22-9
Batch Processing - Dodger - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22-12
The Next Step - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22-14
Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 29-1
DTM Registration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 29-2
Execution - DTM Registration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 29-3
Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37-1
Automatic Terrain Extraction - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37-4
Executions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37-7
Batch Processing - ATE - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37-9
Next Step - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37-13
Applications - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - E-15
Examples - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - E-16
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.
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.
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.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 .
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.
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.
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.
Workstation Description
Workstation Description explains the purpose, components,
and software description.
• Image enhancement
• Data export functions for softcopy databases (imagery, feature, and terrain data),
and hardcopy products (image maps)
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
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.
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.
Major component characteristics of the workstation are described in the following paragraphs.
Network Tape
Drive
Disk Drive Console
Monitor
Trackball
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.
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.
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)
Openflight (S)
Wrapping-Up a
Project (U)
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 > 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.
Options > Edit Options Invokes the Edit Options window described below.
SELECT TO
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.
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.
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.
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|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:
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.
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. [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.
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.
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.
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.
% cd <install_path>/internal_dbs/SPECS
% cp <install_path>/internal_dbs/ICONS/mcg/*
<install_path>/internal_dbs/ICONS
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.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.
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.
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.
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.
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.
To set up your monitor to view stereo in CDE environment, run the following script:
# UNIX: install/cde_setup.ksh
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.
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.
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 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.
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 > 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
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 > 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 > Terrain Analysis Terrain shaded relief and line-of-sight analysis.
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 > Line of Sight Tool for visual analysis of linear paths in a model.
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.
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 > Correlation Used to establish band weights for correlation activities performed in
Weights Automatic Terrain Extraction.
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 > 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
Standard Toolbar
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.
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.
SELECT TO
Zoom Out Zoom out of image incrementally. Click and hold for continuous zoom.
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.
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.
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.
SELECT TO
Refresh Graphics Redraw the current graphics. (Useful for clearing old graphics.)
Recenter All Viewports Center all viewport images around their respective extraction cursor
locations.
SELECT TO
Up/Down Arrows Select and load either the previous or next image in the scroll list.
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.
You can also zoom the imagery with Image Enhancement. See Rotation/Zoom for details.
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.
Histogram Rotation/Zoom
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...
SELECT TO
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.
<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.
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.
SELECT TO
Apply Sensor Default... Tell the software to automatically select a TTC for the imagery currently
displayed.
Recall Save the current TTC file before using the saved one.
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.
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.
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
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
SELECT TO
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.
Generate histogram using Collects and displays the histogram using the 1:1 image or a reduced
1:1 Image resolution of the image.
SELECT TO
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
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.
SELECT TO
SELECT TO
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.
SELECT TO
Select Sensor Default... Tell the software to automatically select a filter for the imagery currently
displayed.
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.
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.
Size > 3x3, 5x5, 7x7, 9x9, Changes the size of the kernel.
11x11
• 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.
• 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.
Options > Auto Minify Automatically creates a minified image pyramid after Image Chipping is
complete.
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.
BLANK SPACE BLANK SPACE
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.
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.
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.
chipping chipping
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.
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_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
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_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
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_2 Y value of the second ground point vertex of the image chip. Can specify
as geographic latitude 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_x_vertex_3 X value of the third 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_3 Y value of the third ground point vertex of the image chip. Can specify as
geographic latitude 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_x_vertex_4 X value of the fourth 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_4 Y value of the fourth ground point vertex of the image chip. Can specify as
geographic latitude 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.
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.
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)
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.
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.
Create/Edit
Project
Computer
UTM Zone
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.
Options > Set LSR Origin Prompts you to enter an LSR origin. Use only for LSR and LSR With
Curvature projects.
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).
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.
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.
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
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 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.
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.
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)
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).
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.
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.
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.
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.5.1 Save
Edit the project, change the coordinate system, units and/or datum), then use the Save operation.
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.
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.
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
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.
SELECT TO
Object Characteristics Display detailed information about the data file selected
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.
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
cd <install_path>/data
cd <install_path>/data
6.2 Backup
File > Load Project Allow you to select the project to backup from a popup menu.
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.
Start Start the backup. All the items displayed in the Backup List window will
be backed up.
EOF
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.
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.
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.
SELECT TO
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.
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.
SELECT TO
Project Name (Optional) Causes a popup menu to appear that allows you to select the project to
delete.
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.
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
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
The following are other Geo-Referenced Imports that utilize the Image Import/Reformat window.
TIFF-RPC Import (IKONOS Import the IKONOS GeoTIFF with RPC text file.
GeoTIFF with RPC text)
USGS DOQ Import Imports the United States Geological Survey’s digital orthophoto
quadrangle product. USGS DOQ Import is described below.
NITF Image Import Imports NITF Images which have georeferencing information in the image
header
NCDRD Import Import the NCDRD file. See “NCDRD Import” on page 7-17.
Panoramic Import/Edit Imports a digitized panoramic aerial photo. This uses Frame Import
running in a special mode.
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.
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
GEO-
FORMAT BATCH NAME IMPORT EXPORT DISPLAYABLE REF.
TIFF img_type_tiff_tiled Y Y Y N
JFIF img_type_jfif Y N Y N
GEO-
FORMAT BATCH NAME IMPORT EXPORT DISPLAYABLE REF.
MrSid n/a Y N4 Y N
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.
levels from the original file, set the variable "USE_J2K_RLEVELS" with the Configuration
Editor.
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.
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
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.
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
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.
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.
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.
BLANK SPACE BLANK SPACE
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.
BLANK SPACE BLANK SPACE
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.
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).
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.
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.
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.
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
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.
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.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.
COMMAND LINE:
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.
KEYWORD DESCRIPTION
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.
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.
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.
File > Load Project... Load the project to hold the output image.
SELECT TO
Draw Polygon Allow user to specify the area of interest by drawing a polygon.
7.5.1.2 Outputs
Outputs consist of an ASCII support file and a binary image file.
File > Open Prompts you to select the RPF directory which contains the CIB files you
want to display.
SELECT TO
Open File Prompts you to select the RPF directory which contains the CIB files you
want to display.
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.
SELECT TO
Click on Image Displays latitude and longitude of where you clicked on the window title
bar.
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.
SELECT TO
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.
Each CADRG chart type (based on scale) has its own code & series abbreviation associated with
it. For example:
7.7.2.1 Outputs
Outputs consist of an ASCII support file and a binary image file.
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.
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.
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
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.
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.
SELECT TO
Selected (Images) List of selected images chosen from the available 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 Options Create a support file for each of the exported images when checked.
Create Support File Default value is checked.
BLANK SPACE BLANK SPACE
Map-down to 8 bits Convert two-byte images to one-byte per pixel image when checked.
BLANK SPACE Default value is checked.
BLANK SPACE BLANK SPACE
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.
BLANK SPACE BLANK SPACE
Output Min Level Specified the output image Minification Level.
BLANK SPACE 1:1, 2:1, 4:1, … 2048:1. Default value is 1:1.
BLANK SPACE BLANK SPACE
Select Bands... Select the desired bands for exported files. Default is to export all bands
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.
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:
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.
data_convert data_convert
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_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.
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).
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.
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.
USGS DOQ
EXPORT
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
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.
data_convert data_convert
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.
File > Load Project Prompts you to pick the project that contains the support file that you wish
to build the fast sensor model for.
File > Input Support File Prompts you to pick the support file that you wish to build the fast sensor
model for.
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.
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:
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. 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.
data_convert data_convert
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)
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.
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.
Edit Names Change the name of the output image or support 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.
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".
<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.
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.)
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.
sat_import sat_import
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.
Interior Orientation is not required with ALOS AVNIR 2 images, since the sensor is a digital
camera, resulting in a known, fixed relationship between each image pixel and the sensor lens.
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.)
Options > Select Bands Brings up a window to allow custom selection of the bands to produce
output images for.
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.
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.
Text box Display band combinations chosen so far. To remove an entry, highlight it
and press the Delete or Backspace key.
sat_import sat_import
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.
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.
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)
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.
Options > Lens Aberration Resulting Sensor Model calculates lens aberration.
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.
Edit Names Change the name of the output image or support file.
sat_import sat_import
KEYWORD DESCRIPTION
project Project file name. Select from the .prj files in the Project Directory.
input_file PASS file(s) you want to import. Repeat for each image you want
to import.
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
auto_minify Set to YES to minify the output image.
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.
SELECT TO
RADARSAT 2 Files Identify the names of RADARSAT 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 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
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 product.xml file.
Edit Names Change the name of the output image or support file.
sat_import sat_import
KEYWORD DESCRIPTION
project Project file name. Select from the .prj files in the Project Directory.
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).
KEYWORD DESCRIPTION
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.
SELECT TO
TerraSAR-X Files Identify the names of TerraSAR-X 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 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
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 general
header found within the xml file.
Edit Names Change the name of the output image or support file.
sat_import sat_import
KEYWORD DESCRIPTION
project Project file name. Select from the .prj files in the Project Directory.
input_file TSX1_SAR----.xml file(s) you want to import. Repeat for each
image you want to import.
image_format Format of output image(s).
KEYWORD DESCRIPTION
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.
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
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 - Edit Names Bring up window for editing the names of output support and image files.
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.
SELECT TO
SWIR Nadir - Check Boxes Select SWIR bands to combine in one image.
TIR Nadir - Check Boxes Select TIR bands to combine in one image.
Text Box Display band combinations chosen so far. To remove an entry, highlight it
and press the Delete or Backspace key.
sat_import sat_import
KEYWORD DESCRIPTION
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_format The format you wish for the output images. See the table in the
Image Import/Export chapter for values.
output_location (Optional) Location from the list in internal_dbs/DEVICE/
location.list
auto_minify Set to YES to minify the output image.
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".
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.
Edit Names Change the name of the output image or support file.
sat_import sat_import
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.
KEYWORD DESCRIPTION
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
Ground
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.
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.
+x,-y
+x,+y
Positive Roll Angle
-x,-y
Heading
GROUND X
-x,+y
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.
Strip_Number Image_Number X Y Z
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.
File > Load Project Choose a project file (only if started in stand-alone).
Options > Auto Minify When toggled on, enables minification of the image after import.
SELECT TO
SELECT TO
Automatic Interior Starts Automatic Interior Orientation for the images that were imported.
Orientation
Start at... Create a batch settings file and starts creation of support files or support
and image files at specified time in batch mode.
SELECT TO
SELECT TO
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.
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.
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.
multi_frame multi_frame
KEYWORD DESCRIPTION
project Project filename (with full path prefix, select from the .prj files in
<install_path>/data).
create_files Specifies that only a support file will be created “SUPPORT” or image and
support files will be created “IMAGE_AND_SUPPORT”
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.
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.”
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.
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.
BLANK SPACE BLANK SPACE
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.
BLANK SPACE BLANK SPACE
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.
BLANK SPACE BLANK SPACE
Other... Specifies that input image is an unsupported format. The Review/Edit
Support window prompts you to enter the image support data.
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.
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.
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 BLANK SPACE
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.
BLANK SPACE BLANK SPACE
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.
BLANK SPACE BLANK SPACE
Calibration Choose the camera calibration file. The camera calibration file contains lens
distortion and fiducial coordinate information.
SELECT TO
Output Identify the name, location, and format of the output file.
You only need to enter this data when the image is of type
“Other.”
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.
(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:
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.
SELECT TO
Mounting Angle Identify the angle of the camera relative to the platform. See “Camera
Mounting Angle (Panoramic only)” on page 8-6.
SELECT TO
To gain access to this window click in the Camera Location field on the Panoramic Import/Edit
window.
SELECT TO
To gain access to this window click in the Camera Location field on the Panoramic Import/Edit
window.
SELECT TO
To gain access to this window click in the Camera Location field on the Panoramic Import/Edit
window.
frame_import frame
KEYWORD DESCRIPTION
project Project filename (with full path prefix, select from the .prj files in
<install_path>/data).
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”
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.”
cam_loc_ang_sys Camera location input angle system: Omega, Phi, Kappa: “OPK” or
Heading, Roll, Pitch: “HRP.”
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_filename The filename (with full path prefix) for the camera location: Albany
triangulation file or Patb file.
platform_gnd_spd (Airborne only) Ground speed of the platform in project vertical units per
second
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.
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.
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 data from the
DIMAP file, e.g.55542820206151826141J.sup
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.
setting_file
sat_import sat_import
KEYWORD DESCRIPTION
project Project file name. Select from the .prj files in the Project Directory.
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
auto_minify Set to YES to minify the output image.
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.
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.
SOCET SET also imports the U.S. Department of the Interior NLAPS format.
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
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
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.
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.
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.
SELECT TO
L7NNNN_NNNN_HTM.FST
L7NNNN_NNNN_HPN.FST
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.
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.
Ground
Track
Imagery is collected as
sensor moves forward
Pushbroom Sensor
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.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.
Options > Display Displays the Tape Parameters window to display the tape parameters.
Parameters
SELECT TO
Output Image Identify the name, format, and location of the output image.
% <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
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:
The input devices list in the Open Device Window are listed in
the Device Configuration File. See “Customizing Your
Software Configuration,” Appendix D for more information.
5. In the Output Image section of the SPOT, set the file name, location, and format to values
you want.
6. Click Start to begin importing the image.
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.
Options > Auto Minify Automatically creates a minified image pyramid from the resulting mosaic
after the processing completes.
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.
SELECT TO
Edit Names Change the name of the output image or support 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.
copy_images Set to “YES” to copy the images to an Image Location. Default is” NO.”
KEYWORD DESCRIPTION
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
auto_minify Set to YES to minify the output image.
atmospheric_refraction (Optional) Set to "YES" to include the effect of atmospheric refraction for
the sensor model. Default value is "NO".
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.
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.
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.
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.
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.
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.
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.
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.
6. Click Start to begin importing the image.
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.
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.
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.
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.
Active SAR
pulse
Reflective
return Ground
Track
Lake
12.2.0.1 SAR
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)
Wide 150X150 30
Standard 100X100 30
Fine 50X50 10
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.
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.
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.
The input devices list 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 file name and location to values you want.
6. Click Start to begin importing the image.
If you have difficulty importing, you can also try identifying the files in the above order with the
Disk Import interface.
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.
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.
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.
6. Set the Output Image file name and location to values you want.
7. Click Start to begin importing the image.
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.
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.
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
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.
File > Load Project Prompts you to select the project file.
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.
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.
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.
File > Load Project Prompts you to select the project file.
File > Open... Prompts you to select the .pvl file, e.g. 3V0223.pvl.
Options > Auto Minify Enable this to minify the imagery while importing.
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
sat_import sat_import
KEYWORD DESCRIPTION
project Project file name. Select from the .prj files in the Project Directory.
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.”
KEYWORD DESCRIPTION
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
auto_minify Set to YES to minify the output image.
atmospheric_refraction (Optional) Set to "YES" to include the effect of atmospheric refraction for
the sensor model. Default value is "NO".
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.
File > Load Project Prompts you to select the project file.
File > Open... Prompts you to select the .pvl file, e.g. 3V0223.pvl.
Options > Auto Minify Enable this to minify the imagery while importing.
SELECT TO
GEO-EYE-1 Files Identify the names of GEO-EYE-1 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 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.
sat_import sat_import
KEYWORD DESCRIPTION
project Project file name. Select from the .prj files in the Project Directory.
input_file Pvl file(s) you want to import. Repeat for each image.
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
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:
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.
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>.
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.
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 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.
1: ID 1: Y 1: Ignore
2: X 2: X 2: X
3: Y 3: Z 3: Y
4: Z 4: Illegal 4: Z
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.
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.”
File > Load Project Prompts you to pick the name of the project to import the ground points
into (only if started stand-alone).
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
imported. By default, this is the name of the project that is currently loaded
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.
SELECT TO
111070152106.000 0
-99
111.69152106 0
-99
...
-99
...
-99
...
-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:
-99
-99
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.
data_convert data_convert
KEYWORD DESCRIPTION
conversion_type import_asc_ip
project_file File name (with full path prefix) of project file.
input_file File name (with full path prefix) of input ASCII file.
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
LIDAR Import
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
main workstation window.
ASCII DTM
IMPORT
SOCET SET
DTM
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
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.
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
main workstation window.
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.
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.
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.
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:
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
data_convert data_convert
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.
code_file File name (with full path prefix) of input code description file.
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).
File > Load Project Prompts you to pick the name of the project to import the GridFloat into
(only if started stand-alone).
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.
Start Begin importing.
data_convert data_convert
KEYWORD DESCRIPTION
conversion_type import_gridfloat
output_dtm_file File name (with full path prefix) of output DTH file.
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.
ASCII ARC
GRID DATA FILE
ARC GRID
IMPORT
File > Load Project Prompts you to pick the name of the project to import the ARC Grid file
into (only if started stand-alone).
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
imported. By default, this is the name of the project that is currently loaded
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.
data_convert data_convert
KEYWORD DESCRIPTION
conversion_type import_asc_arc_grid
input_grid_file File name (with full path prefix) of input ARC Grid file.
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.
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 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.
File > Load Project Prompts you to pick the name of the project to import the DEM into (only
if started stand-alone).
SELECT TO
Output DTM Type in the name of the output DTM. Terminate your entry with a carriage
return.
DEM File Type Specify the input DEM file extent. (7.5 Minute & 1 Degree)
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.
data_convert data_convert
KEYWORD DESCRIPTION
conversion_type import_dem
input_dem_file File name (with full path prefix) of input DTH file.
output_dtm_file File name (with full path prefix) of output DTH file.
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 > 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.
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.
3. Type the name of the output DTM in the Output DTM field, followed by a carriage return.
4. Click Start to import the DTED.
data_convert data_convert
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.
output_dtm_file File name (with full path prefix) of output DTH 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.
File > Load Project Prompts you to pick the name of the project to import the SDTS into (only
if started stand alone).
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.
data_convert data_convert
KEYWORD DESCRIPTION
conversion_type import_sdts
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.
SELECT TO
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.
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
or remove file(s) by right-clicking and selecting Add or Remove.
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.
Start Begin the import process.
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.
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.
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.
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.
data_convert data_convert
KEYWORD DESCRIPTION
conversion_type import_lidar
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_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] 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.
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
(only if started stand-alone).
SELECT TO
Input GeoTIFF File Prompts you to pick a terrain GeoTIFF file to import.
Output DTM Type in the name of the output DTM. Terminate your entry with a carriage
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.
data_convert data_convert
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.
File > Load Project Prompts you to pick the name of the project toimport the NITF into (only if
started stand-alone).
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
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.
data_convert data_convert
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.
Possible values are “none”, “float”, “inverse”, and “non-inverse”.
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
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 “float” – where the format is
floating point with identity scaling factor (i.e., scaling factor is 1.0).
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.
File > Load Project Prompts you to pick the name of the project to import the BIL into (only if
started stand-alone).
SELECT TO
Input BIL File Prompts you to pick a BIL terrain file to import.
Output DTM Type in the name of the output DTM. Terminate your entry with a carriage
return.
data_convert data_convert
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
ASCII DTM
EXPORT
ASCII DTM
OUTPUT DATA FILE
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.
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.
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.
1. Start up ASCII DTM Export by clicking Output > Export > Terrain > ASCII DTM on the
main workstation window.
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
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.
data_convert data_convert
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
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).
File > Load Project Prompts you to pick the name of the project to export the DTM from (only
if started stand-alone).
SELECT TO
Output NED (FLT) File Type in the name of the output NEDGridFloat file. Terminate your entry
with a carriage return.
SELECT TO
data_convert data_convert
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.
SOCET SET
DTM
ARC GRID
EXPORT
ARC GRID
OUTPUT DATA FILE
File > Load Project Prompts you to pick the name of the project which contains the DTM to
export (only if started stand-alone).
SELECT TO
Output ASCII ARC Grid Name the output ASCII ARC Grid file, followed by a carriage return.
File
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.
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.
data_convert data_convert
KEYWORD DESCRIPTION
conversion_type export_asc_arc_grid
input_dtm_file File name (with full path prefix) of input DTH file.
output_asc_file File name (with full path prefix) of output ASCII file.
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 > Load Project Prompts you to pick the name of the project which contains the DTM to
export (only if started stand-alone).
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.
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)
data_convert data_convert
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.
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.
File > Load Project Prompts you to pick the name of the project from which the DTED will be
exported (only if started stand-alone).
SELECT TO
Input DTM Type the name of the input DTM, followed by a carriage return.
NOTE: Only grid format DTM is supported.
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
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
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
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:
Header Info Label This would be by default UHL to indicate which part of the
tab you are on.
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.
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
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.
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.
Partial Cell Indicator Indicates coverage of the DTED cell. 00 is complete, 01-99 is
% of data coverage.
Product Amendment/ Values are in between 00-99. First number indicates the
Charge Number Product Specification Amendment Number. Second digit
indicates change 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.
Security Handling Other types of security description. Can be free text or blank
filled.
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.
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.
Orientation Angle Clockwise orientation angle of the data with respect to true
North. (Usually all zeros.)
Nation Reserved Reserved for producing nation use. Free text or blank filled.
17.17.2.3 DSI-Reserved
Source Type Code Number of coordinates in the accuracy sub region outline.
Header Info Label This would be by default ACC to indicate which part of the
tab you are on
Relative Horizontal Provides the point to point horizontal accuracy of the product
Accuracy in meters.
Relative Vertical Provides the point to point vertical accuracy of the product in
Accuracy meters.
17.17.2.5 ACC-SubRegion
Relative Horizontal Provides the point to point horizontal accuracy of the sub-
Accuracy Sub-Region region in meters.
Coordinate Pairs There are 14 coordinate pairs each having a latitude and
longitude associated.
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.
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.
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.
data_convert data_convert
KEYWORD DESCRIPTION
conversion_type export_dted
input_dtm_file File name (with full path prefix) of input DTH file.
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.
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)
File > Load Project Prompts you to pick the name of the project to export the SDTS into (only
if started stand alone).
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.
data_convert data_convert
KEYWORD DESCRIPTION
conversion_type export_sdts
input_dtm_file File name (with full path prefix) of input DTH file.
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.
DGN POST
EXPORT
DGN FILE
File > Load Project Prompts you to pick the name of the project from which the DTM will be
exported (only if started stand-alone).
SELECT TO
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.
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.
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).
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.
data_convert data_convert
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.
File > Load Project Prompts you to pick the name of the project to export the GeoTIFF from
(only if started stand-alone).
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
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 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
data_convert data_convert
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.
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
characters with an inverse scaling factor. Setting this to “non-inverse” will
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
File > Load Project Prompts you to pick the name of the project to export the NITF from (only
if started in stand-alone).
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
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 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.
data_convert data_convert
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
characters with an inverse scaling factor. Setting this to “non-inverse” will
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).
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
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.
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.
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.
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.
Compatibility is as follows:
INT_TYPE Integer
ASCII_TYPE String
DOUBLE_TYPE Double
FLOAT_TYPE Float
ENUMER_TYPE Enum
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).
data_convert data_convert
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.)
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.
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.
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.
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.
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.
File > Load Project Prompts you to pick the name of the project to import the ASCII features
into (only if started stand-alone).
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.
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:
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:
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).
END
3 feature_id
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:
1 1 DITCH PERRENIAL 3
2 2 DITCH PERRENIAL 3
3 3 DITCH PERRENIAL 3
17 13 DITCH PERRENIAL 3
21 14 DITCH PERRENIAL 3
20 14 DITCH PERRENIAL 3
19 14 DITCH PERRENIAL 3
18 14 DITCH PERRENIAL 3
data_convert data_convert
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.
spec_file File name (with full path prefix) of the default extraction specification file
used to create the output feature database.
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
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.
SELECT TO
SELECT TO
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.
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:
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:
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.
data_convert data_convert
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.
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).
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).
data_convert data_convert
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.
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).
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.
Class Present a list of classes, based on the Input Feature File specified above,
from which you choose a single feature class to export.
features contained in these files are not delineated. The format of the file for complex and
primitive features is as follows:
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:
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:
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.
1 1 12 BUILDING ...
2 1 12 BUILDING ...
(additional records)
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
END
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
END
The coordinate file has a record for each point or text feature. The file has the following format:
END
Only use this mode if you have N G A feature code spec files
and want these specific filenames!
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.
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.
File > Load Project Prompts you to pick the name of the project which contains the feature
database to export (only if started stand-alone).
SELECT TO
Output ARC File Type the name of the output ASCII file.
END
ELEMENT_ATTRIBUTES END_OF_ELEMENT_ATTRIBUTES
text_or_icon_value
data_convert data_convert
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).
File > Load Project Prompts you to pick the name of the project which contains the feature
database to export (only if started stand-alone).
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:
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.
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).
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.
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.
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.
data_convert data_convert
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
project_file File name (with full path prefix) of project file.
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).
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.
class
class_name
class_code dgn_level line_style line_weight line_color elem_type
any other information desired (text is ignored)
end class
FIELDS DESCRIPTION
class_code Integer, class code assigned in the feature database specification file.
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.
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
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
data_convert data_convert
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.
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.
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.
The rest of the tool buttons are sketch tools. See “Sketch,” Chapter 58 for their usage.
After connection
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.
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.
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.
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.3 Execution
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.
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.
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.
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.
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.
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.
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.
• 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.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
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
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.
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.
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.
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.
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.
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.
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.
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.
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 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.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.
The CADRG Data Manager is divided up into a Source and Destination section as shown below.
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.
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.
The VPF Data Manager is displayed with Source location listed on the left and Destination on the
right.
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:
BP Black/White Photography
EO Electro-Optical
FL Forward-Looking Infrared
HR High-Resolution Radar
HS Hyperspectral
OP Optical
RD Radar
SL Side-Looking Radar
TI Thermal Infrared
IR Infrared
MS Multispectral
VD Video
SHP Shapefiles
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.
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%.
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.
level are VPF libraries. At the fourth level are VPF coverages, and at the fifth level are the VPF
feature tables.
vct_VisualCoverageTool2 GUI
vct_VisualCoverageTool3 GUI
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.
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
21.2 Minification
SELECT TO
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.
Start At... Display the Start Batch Job window and lets you initiate the batch job.
See “Start At Jobs” on page E-3
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.
minifier min
KEYWORD DESCRIPTION
project Full path and project filename (select from the .prj files in
<install_path>/data).
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.
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.
DODGER
File > Load Project... Prompts you to pick the name of the project.
Options > Auto Minify Automatically creates a minified image pyramid for each dodged image
after the dodge processing completes.
SELECT TO
(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.
BLANK SPACE BLANK SPACE
Report File Prompt you to select a report file or enter the name.
BLANK SPACE BLANK SPACE
View... Display the report file.
SELECT TO
Start At... Display the Start Batch Job window and lets you initiate the batch job.
See “Start At Jobs” on page E-3
SELECT TO
Parameter File Select a parameter file which controls the dodge and balance process.
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.
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.
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.
OK Close the window and uses the displayed values as the dodge parameters.
Cancel Close the widow ignoring any changes which were made.
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.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:
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
dodger dodger
KEYWORD DESCRIPTION
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.
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).
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”.
# NOTES:
BAND_INDEPENDENT FALSE
NUM_TILES 10
PERCENT_SKIP 2.000000
BALANCE_ACROSS_IMAGES TRUE
22.4.2.2 Sample parameter file for color imagery with given mean and deviation
DODGER_DATA_FILE 1.0
# NOTES:
# project.
BAND_INDEPENDENT True
NEW_MEAN 80 128 94
NEW_STD_DEV 22 33 30
MAX_GREY_SHIFT 30 30 30
MIN_GREY 0 0 0
NUM_TILES 6
PERCENT_SKIP 2.0
BALANCE_ACROSS_IMAGES TRUE
After running Dodger, you can display the output images on the main SOCET SET display, but
you should not save the Image Enhancement parameters.
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.
• 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.
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.
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.
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.
5. To save any changes you made to the data, click File > Save GPF on the Control Point
Editor window.
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.
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.
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
POINT
MEASUREMENT
ORIENTATION
SOLUTION
INTERIOR SUPPORT
ORIENTATION FILE
POINT FILE
To access AIO from within SOCET SET, click Preparation > Interior Orientation > Automatic
Interior Orientation on the main workstation window
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.
SELECT TO
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
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.
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.
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.
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.
SELECT TO
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.
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.
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.
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.
SELECT TO
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.
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.
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
Sensor
Images Sensor
Image Points
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
control points from one coordinate system or datum to another. See “Selecting the
Coordinate System or Datum” on page 23-7 for details.
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
STEPS DESCRIPTION
1. Setup Create a single artificial strip and put all the images into that strip.
STEPS DESCRIPTION
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.
6. Verify If the solution is bad (has high residuals) repeat steps 3, 4, and 5 as needed.
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
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.
POINT
DESCRIPTION
TYPE
0 Tie 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 .
internal_dbs/HATS directory and may be customized and stored under different names
based on the user’s preferences.
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.
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 > 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
Setup Execute Setup, which creates and populates the triangulation file. See
below for a detailed description of Setup.
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.
Solve Create a window for launching the three types of solutions available in
Triangulation.
SELECT TO
Solve Bingo
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.
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.
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
SELECT TO
SELECT TO
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.
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.
Image 2
Overlap
Area
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.
• 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.
CL0 CS0 Turn on CL0 and CS0 only for strip lengths to 50
km.
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.
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.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.
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_ID1 10 10 5000 0 0 0
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:
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.
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
SELECT TO
Images Identify the image IDs belonging to the current strip. Image IDs must be
Support File integers.
BLANK SPACE BLANK SPACE
Use Enable this image to be used.
BLANK SPACE BLANK SPACE
Sensor Identify the Sensor Model.
BLANK SPACE BLANK SPACE
Reverse Order Reverses the order of the images.
BLANK SPACE BLANK SPACE
Add Add additional images. A Right click on a Images Support File will also
BLANK SPACE provide Add/Remove/Image Data.
BLANK SPACE BLANK SPACE
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
Setup Block Starts the Block Setup window which you use to set up 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.
6
4_
Example of a cross strip.
5
4_
4
4_
3
4_
2
4_
1
4_
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.
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.
You should not run Block Setup if your imagery is not from a
frame camera.
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.
Apply Update your support files with the new strip locations.
SELECT TO
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.
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
SELECT TO
Solution Type Identify the options radio buttons. See “Solution Type” below.
• Rigorous Simultaneous
• Direct Linear Transformation (DLT)
• 3D Polynomial
USMSD See “USMSD Generation” on page 26-15 for details regarding USMSD.
OK Exit window.
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.
<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.
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.
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:
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 does not work well with JPEG images. You should
reformat JPEG images to TIFF tiled JPEG format before
importing them.
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.
SELECT TO
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).
Start At... Display the Start Batch Job window and lets you initiate the batch job.
See “Start At Jobs” on page E-3.
Close Close the Automatic Point Measurement window. The state of the
Automatic Point Measurement when you click Done determines what
happens next.
0, 0 100, 0
+x
+y
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.
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.
The Interactive Point Measurement for APM window’s selection are as follows:
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.
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.
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.
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.
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.
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
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:
Residual limit
Residual Diminishing benefit of adding more
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.
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.
The Interactive Point Measurement window is divided into two major sections, Ground Point, and
Image Point.
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.
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.
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.
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.
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
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.
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).
Left Image Right Image
Extraction cursor is
locked in the left
image; cursor
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.
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).
1. On the Display Utility window, set the Cursor control to Fixed Image.
Left Image Right 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 Image Right Image
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 Image Right Image
6. Measure the point by clicking Sample in the Interactive Point Measurement window.
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.
to drive to the last measured line/sample locations which do not depend on the state of the math
models.
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
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.
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 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:
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).
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.
SELECT TO
Current function and Show which function is running and the percentage in progress.
Percentage bar
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 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.
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.
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.
State Display On/Off, which can be toggled back and forth with the RMB.
Point Index Display the area of the Point Index map the point is located in.
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.
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.
SELECT TO
State Display On/Off, which can be toggled back and forth with the RBM.
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
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.
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.
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.
SELECT TO
Display Residuals Activate the Display Residuals window showing a list of all points and
their residuals (See description below).
Start Prompt you to save all the active files and restarts Simultaneous Solution.
Useful for removing remaining blunders.
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.
2nd
1st
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.
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
Re-measure Display the Activates the remeasure option on a highlight point ID.
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.
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.
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.
B = numerical partials
Z = image residuals
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.
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.8 Redundancy
A negative redundancy is acceptable for Satellite Sensor Models; however, for Frame Sensor
Models, a positive redundancy is expected.
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
DEM
ASCII DTM
DTED
} TERRAIN
IMPORT
ATE or
ITE
UNREGISTERED
DTM
DTM REGISTERED
REGISTRATION DTM
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.
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.
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.
Setup DTM Open the Input/Overlay DTM Setup Preference window. (See “Setup DTM and
Setup Overlay Preferences” on page 36-1).
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.
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
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.
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.
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.
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.
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.
FEATURE
IMPORT
FEATURE
EXTRACTION
FEATURE DATABASE
FEATURE
REGISTRATION
REGISTERED
FEATURES
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
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.
c. Press the RMB to accept the sample and toggle out of the extraction cursor.
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.
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.
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.
• Setup:
Select a candidate.
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.
• 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.
SELECT TO
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.
SELECT TO
File Click button to display the Select Candidate window. Select the support
file associated with 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
SELECT TO
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.
SELECT TO
(Point List)
Point Type Point type. It can be Tie / Z Control / XY Control / XYZ Control / Z Check
/ XY Check / XYZ Check.
SELECT TO
Coordinate Display Display the coordinates and the accuracy of the point.
Measure Status:
Measured Display the image is measured and the pixel coordinates are sampled if the
BLANK SPACE box checked.
BLANK SPACE BLANK SPACE
Load Click RMB, select Load to load an image from the control list.
BLANK SPACE BLANK SPACE
Delete Click RMB, select Delete to delete an image.
BLANK SPACE BLANK SPACE
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).
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:
SELECT TO
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.
INPUT OUTPUT
IMAGE(S) IMAGE(S)
RECTIFICATION
INPUT OUTPUT
SUPPORT SUPPORT
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.
File > Load Project Prompts you to pick the project file containing the desired support files
(only if started stand-alone).
File > Input Support file Prompts you to pick the image(s) to rectify.
Options > Auto Minify Automatically creates a minified image pyramid after Rectification is
complete.
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.
BLANK SPACE BLANK SPACE
Current Orientation Rectify with the rotation angle CW to the current orientation of the input
image.
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.
Output Image Identify the name and location of the output image files.
Start at... Display the Start Batch Job window and lets you initiate the batch job. See
“Start At Jobs” on page E-3.
a1 a2
(A) (B)
line line
Sample Sample
Epipolar plane
L2 L1 L2
L1
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.
The sum of the skip and process values must be less than the
original lines and samples of the image.
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
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.
The sum of the skip and process values must be less than the
original lines and samples of the image.
rectifier rectify
KEYWORD DESCRIPTION
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.
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.
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.
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.2 Zoom/Scale
To obtain this window, click Preparation > Resample > Zoom/Scale on the main workstation
window.
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...
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.
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 at... Display the Start Batch Job window and lets you initiate the batch job.
See “Start At Jobs” on page E-3.
b. Enter the Zoom Factor. The Map Scale will automatically be calculated.
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.
9. [Optional] Click Start at... to initiate a batch process job at a later time.
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.)
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:
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.
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.
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
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.
SELECT TO
DTM Name of the DTM currently selected. This field is not editable.
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.
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.
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 MBR Around Polygon Use the minimum bounding rectangle of the polygon as the DTM
boundaries.
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.
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.
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.
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 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.
SELECT TO
See “Create a DTM for NGATE - NGATE Properties” for more information.
35.4 Executions
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.
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.
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.
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.
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.
Cancel Close the DTM or Overlay Setup windows without saving changes.
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.
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.
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.
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:
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.
% setenv SPLINE no
Spline does not apply to editable contours; however, it does apply to both Grid and TIN DTMs.
The project, feature, and DTM names must include full path.
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
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.
Feature
Database
MERGE DTM
[OPTIONAL] IMPORT
AUTOMATIC
TERRAIN
EXTRACTION
INTERACTIVE TERRAIN
DTM(S) WITH GRAPHICS
TERRAIN ELEVATION POSTS
EDITING DISPLAY
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.
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.
obtain this window click Extraction > Terrain > Automatic Extraction on the main workstation
window.
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.
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
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.
SELECT TO
Posts per Second Display the number of posts processed per second
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 at... Display the Start Batch Job window and lets you initiate the batch job. See
“Start At Jobs” on page E-3.
Abort Abort ATE
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.
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).
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.
6. [Optional] Click Start at... to initiate a batch process job at a later time.
See “Execution - Start At” on page E-7
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.
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.
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.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.
KEYWORD DESCRIPTION
ate.feather For Multi-Processor Batch. Feathering setting for the DTM’s (YES or
NO). Default is YES.
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
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.strat The strategy to use, with the .strat extension. The default is no strategy.
KEYWORD DESCRIPTION
ate.images Images which ATE will use. Each support file needs its own line with the
“images” keyword.
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.polygon_verts 479867.0 3626407.0 16.5
ate.polygon_verts 482044.0 3626438.0 16.5
ate.polygon_verts 482076.0 3625118.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.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.polygon_verts -2.041985773 0.5585053606 0.000000
ate.polygon_verts -2.059488517 0.5585053606 0.000000
ate.polygon_verts -2.059488517 0.5760081041 485.000000
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
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.
Help > Contents... Starts the online documentation.
SELECT TO
SELECT TO
Start at... Display the Start Batch Job window and initiate the batch job. See “Start
At Jobs” .
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
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.
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.
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.
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:
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.
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
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.
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.
KEYWORD DESCRIPTION
ngate.project The full path of the project where your DTM will reside.
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,
LOW_SMOOTHING, MEDIUM_SMOOTHING, or
HIGH_SMOOTHING). Default is NONE_SMOOTHING.
ngate.precision Precision option for the DTM (HIGH_PRECISION, MEDIUM
PRECISION, or LOW_PRECISION). Default is HIGH_PRECISION.
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
“images” keyword.
ngate.post_spacing_unit Units that ATE uses (UNIT_SECONDS, UNIT_FEET,
UNIT_INTERNATIONAL_FEET, UNIT_US_SURVEY_FEET, or
UNIT_METERS). Default is UNIT_METERS.
ngate.seed_dtms Specifies seed DTM with full path and .dth extension. Each Seed DTM
needs its own line with the “seed_dtms” keyword.
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
elevation post. Default is 1.
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.project The full path of the project where your DTM will reside.
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
The difference between scenario #2 and scenario #3 is that there are no “ngate.num_verts” and
ngate.polygon_verts” keywords in scenario #3.
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
Area Editor
Geomorphic Editor
• 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.
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.
Interactive Terrain Edit organizes these windows into the following hierarchy:
Interactive
Terrain Edit
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.
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.
Help > Contents Starts the on-line documentation.
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.
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.
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.
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.
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.
Parallel For TIN Geomorphic editor, draw parallel break lines. See “Sketch,”
Chapter 58 for more details
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.
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.
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
3. With the Edit DTM Block window open, click Change Size to alter the block size (500 =
500 posts by 500 posts).
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.
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.
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.
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.
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.
SELECT TO
SELECT TO
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.
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
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.
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:
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.
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.
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
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.
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.
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.
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:
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.
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.
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.
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.
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.
SELECT TO
Algorithm Initially, this pull-down menu is the only sensitized control. You select an
algorithm to select posts.
SELECT TO
Matrix Window This menu pull-down is sensitized only when you select the Average Delta
BLANK SPACE Elevation algorithm.
BLANK SPACE BLANK SPACE
3x3 Execute the Average Delta Elevation algorithm on a 3x3 neighbor matrix.
BLANK SPACE (eight neighbors)
BLANK SPACE BLANK SPACE
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.
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).
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.
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.
SELECT TO
SELECT TO
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
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.
0 0 0
-5 -5 -5
SELECT TO
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.
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.
Ridgeline
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.
3. Click Setup DTM on ITE window. This prompts you to set the graphics display options.
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.
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.
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.
c. RBI (NGA)/FDB method: Which disables SML tracking and lets you load any Feature
Database for drawing.
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.
SELECT TO
Obstruction Surface... Prompt you to select an OIS FDB. If toggle button on the left toggles the
drawing of the OISFDB.
SELECT TO
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.
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.
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.
SELECT TO
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.
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.
SELECT TO
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
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
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.
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.
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.
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 Out: Distance “out” is from the runway end which is along the
extended runway centerline.
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.
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.
Closest xy-Δ: Display the xy distance from the closest feature to the
cursor position.
The following menu choices are for Manual and Automatic modes.
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.
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 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
• 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.
SELECT TO
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.
BLANK SPACE BLANK SPACE
Reset Z Bias Reset the height offset to 0.
BLANK SPACE BLANK SPACE
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.
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.
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.
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
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.
AIRPORT_CATEGORY AEM
INPUT_UNITS FEET
ARC_ANGLE_DEG 5.0
PRIMARY_WIDTH 2000
OUTER_HORIZONTAL_WIDTH 42532
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.
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.
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.
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.
KEYWORDS DESCRIPTION
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.
KEYWORDS DESCRIPTION
ARC_ANGLE_DEG ClearFlite simulates half circles that are used in construction of the outer
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.
KEYWORDS DESCRIPTION
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.
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).
KEYWORDS DESCRIPTION
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.
KEYWORDS DESCRIPTION
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
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.
SELECT TO
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.
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.
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.
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.
SELECT TO
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
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.
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.
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.
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.
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.
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 TO
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.
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.
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.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
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.
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.
Start:
MMB for MMB for Snap,
Snap RMB to accept edge
B
LMB
A
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.
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.
SELECT TO
SELECT TO
See “How to Change the Fonts” on page D-3 for more information on how to configure text
fonts.
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.
window. You can filter the Feature List to show only a subset of the available features.The
SELECT TO
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
Fence
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.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.
SELECT TO
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.
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.
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.
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.
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:
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.
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
feature. This value is only applicable to 3D generic features.
Length Min & Max Identify the minimum and maximum length that will be applied to a
feature. This value is only applicable to 3D generic features.
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.
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)
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.
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.
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.
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”
on page 57-7 for details.
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
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.
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.
SELECT TO
SELECT TO
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.
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.
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.
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.
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.
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.
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.
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.
Help > Contents... Starts the on-line documentation.
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.
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.
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.
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.
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.
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.
SELECT TO
SELECT TO
SELECT TO
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.
Close Close the window.
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.
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
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
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.
Ridge Feature
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.
DTM/FEATURE
MERGE
OUTPUT
DTM
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
DTM
Feature
Merge
Class
Select .cas Algorithm
Edit
SELECT TO
SELECT TO
SELECT TO
DTM
GEOMORPHIC EDIT ALGORITHM PARAMETER
FORMATS
DTM
GEOMORPHIC EDIT ALGORITHM PARAMETER
FORMATS
DTM
AREA EDIT ALGORITHM PARAMETER(S)
FORMAT
DTM
AREA EDIT ALGORITHM PARAMETER(S)
FORMAT
The following example Class Algorithm Settings file is for a SOCET SET feature file that
contains lake, road, and cover features:
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.
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.
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.
17. [Optional] Click Start at... to initiate a batch process job at a later time.
dtm_ftr merge
KEYWORD DESCRIPTION
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
KEYWORD DESCRIPTION
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”.
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.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.
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.
FEATURE
ANNOTATION
EXTRACTION
FEATURE
ANNOTATION
EXTRACTION
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
45.2 Annotation
Back to Sketch
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.
SELECTION DESCRIPTION
Options > Preferences Brings up the preference window for sketch options.
Options > Customize Allows customization of the sketch toolbars.
Help > Contents Starts the on-line documentation.
SELECT TO
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.
SELECT TO
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.
SELECT TO
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).
SELECT TO
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.
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.
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.
If you think you may have two or more duplicate grids, you should delete all the grids (as
described above) then start over.
40:45 40:45
Numerical labels are
drawn at every interval.
40:30 40:30
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.
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.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.
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
one created. The Margin
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.
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.
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.
FEATURE
DATABASE
IMAGE(S) DTM (optional)
ORTHOPHOTO
OUTPUT OUTPUT
IMAGE SUPPORT FILE
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.
Help > Contents Starts the on-line documentation.
SELECT TO
SELECT TO
SELECT TO
SELECT TO
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.
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.
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.
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.
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.
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
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.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:
PROJECTION_TYPE UTM_PROJECTION
ZONE 14
GEOTIFF 26914
The other TIFF characteristics of GeoTIFF images are the same as Tiled TIFF. See “Image Import
and Export,” Chapter 7 for details.
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:
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:
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.
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.
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)
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.
13. [Optional] Click Start at... to initiate a batch process job at a later time.
orthophoto ortho
KEYWORDS DESCRIPTION
KEYWORDS DESCRIPTION
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.
dtm Input DTM. (selected from the DTMs in your project directory).
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.
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).
KEYWORDS DESCRIPTION
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
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 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).
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”.
You can begin mosaicking the orthophotos you have produced thus far. See “Mosaic,”
Chapter 49 for more details.
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.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.
COLOR-GRAY
MERGE
OUTPUT OUTPUT
IMAGE SUPPORT FILE
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.
Help > Contents Starts the on-line documentation.
SELECT TO
SELECT TO
SELECT TO
SELECT TO
Project... Prompt you to select a project file. This choice is only available if you are
running Orthophoto in stand-alone mode.
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
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
sample distance.
NOTE: If you are building an orthophoto to input to Interactive
Mosaic, you must ensure that the GSD matches the mosaic layer
GSD, and that the orthophoto is not rotated from North.
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.
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.
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.
Start Start Orthophoto processing.
Start at... Display the Start Batch Job window and lets you initiate the batch job. See
“Start At Jobs” on page E-3.
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.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.
IMAGE(S) DTM
(optional)
CHANGE
DETECTION
OUTPUT OUTPUT
IMAGE SUPPORT FILE
File > Load Project... Select a project file. This choice is only available if you are running
Change Detection in stand-alone mode.
File > Save Settings Saves the current options of the GUI.
File > Exit Exits the Orthophoto window.
Help > Contents Starts the on-line documentation.
SELECT TO
SELECT TO
SELECT TO
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.
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
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”
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.
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
SELECT TO
49.2.2 Setup
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.
NOTE: This group only applies if you are creating multiple 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.
NOTE: This group only applies if you are creating multiple 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.
SELECT TO
Upper-Left
Lower-Left
49.2.3 Input
SELECT TO
49.2.4 Output
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.
49.3 Options
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.
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.
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.
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
Output Mosaic
Boundary
image 1 feather width
image 2
image 3
seams
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 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.
• 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.
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.
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.
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
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
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.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.
If voids are near seam lines, you might have to turn off Seam
Feathering and switch to Nearest Neighbor resampling for a
good result.
mosaicmanager mosaic
KEYWORD DESCRIPTION
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.
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.
lr_y Input MBR lower- right corner y coordinate (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.
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).
KEYWORD DESCRIPTION
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.
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”.
KEYWORD DESCRIPTION
dra_percent_skip Amount of the image edge to skip when calculating the image
statistics. Range: 0.0-20.0.
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.
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_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
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.
SELECT TO
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.
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.
Auto Draw Automatically draws the contents of the Seamline Database whenever you
re-center the image.
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.
SELECT TO
Set Image Allows you select the image to associate with the polygon.
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.
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 .
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.
image 1
seam polygon 1 seam polygon 2
image 3
image 4
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.
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.
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.
Help > Contents Starts the on-line documentation.
SELECT TO
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:
<sup> - 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.
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><sup>_ortho
pre<x>middle<y>more<sup>end
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.
cutter cutter
KEYWORD DESCRIPTION
input_ortho Input support filename (select from the .sup files in your project directory).
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].
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]
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].
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
the “Export” column says “Y” then the format can be used. Use the
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].
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.
50.1.2 Terminology
Eyepoint The location of the viewer’s eye for the perspective scene.
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)
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
SCENE
RENDERING
1 OR MORE
PERSPECTIVE SCENE
IMAGE FILES
ANIMATION
Tools > Automated Route Generates a series of aim and route points based on the location of the
input image file.
Help > Contents Starts the on-line documentation.
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.
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.
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
“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.
SELECT TO
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.”
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.
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
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.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 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.
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.
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
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
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.
Ground
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.
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.
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.
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.
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).
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.
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.
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.
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:
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.
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.
2. Enter number of the eyepoint in the Eyepoint Number input field. This displays the
parameters for the eyepoint.
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.
reflected in this window as well. The view volume is also based on the current eyepoint's
coordinates and yaw, pitch, and roll angles.
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.
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).
BLANK SPACE BLANK SPACE
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).
BLANK SPACE BLANK SPACE
Vertical Display the vertical size of the field of view (in degrees).
SELECT TO
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.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.
SELECT TO
Play Backward Play each scene in the flythrough starting with the last and ending with the
first.
Play Play each scene in the flythrough starting with the first and ending with the
last.
SELECT TO
/usr/geoset/images/my_project/anim1.img
/usr/geoset/images/my_project/anim2.img
/usr/geoset/images/my_project/anim3.img
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.
MERGE
(optional)
TERRAIN
ANALYSIS
VISIBILITY ANALYSIS
DTM
File > Open DTM... Prompts you to pick a DTM for the use by Visibility Analysis.
File > Exit Exits the Terrain Analysis window.
Help > Contents... Starts the on-line documentation.
SELECT TO
Open Input DTM Prompts you to pick a DTM for the use by Visibility Analysis.
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.
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.
10. You may repeat steps 7 through 9 to vary the location of the viewpoint
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.
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.
WORKSTATION
ANIMATION XV GHOSTVIEW
WINDOW
You use Animation to review one or more perspective scenes that you generated with Perspective
Scenes. See “Animation” on page 50-34 for details.
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.
Arrange Display on
the Screen
Print PostScript
file with 1pr
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.
% /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
% lp -d print_device postscript_file
If the image file is in X-dump format you can print it with the following command:
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.
ACTION PRINT
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.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.
SELECT TO
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.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.
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.
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.
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
POSTSCRIPT
LASER PRINTER
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.
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.
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.
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.
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 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.
Input
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.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.
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.
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.
Help > Contents Starts the on-line documentation.
SELECT TO
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.
BLANK SPACE BLANK SPACE
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.
BLANK SPACE BLANK SPACE
Show/Edit Device Bring up the PostScript Device Configuration window.
BLANK SPACE BLANK SPACE
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.
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.
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.
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.
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:
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.
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).
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.
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.
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.
SELECT TO
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.
BLANK SPACE BLANK SPACE
Polygon Toggle on to only gather graphics from the area of the polygon you draw.
BLANK SPACE BLANK SPACE
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.
BLANK SPACE BLANK SPACE
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.
hardcopy image_map
KEYWORD DESCRIPTION
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.
printer_resolution {Optional] Printer resolution for scaling text in the output. Default is
“300.”
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.
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
Line Of Sight
LOS Vector LOS Vector LOS Vector LOS Vector Obstruction Obstruction
Information Annotation Comparison Ring Marker Measurement Measurement
Information Annotation
File > Save; Save As Saves the LOS data that you are editing to a disk file.
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.
Help > Contents Starts the on-line documentation.
SELECT TO
SELECT TO
SELECT TO
SELECT TO
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.
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.
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.
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.
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.
The CIB Job Setup Window, shown below, is used to create a new SOCET SET project for CIB
Generation.
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.
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).
13 Automatic creation of a CIB working area, known as a Task Assignment Area (TAA).
SELECT TO
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.
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
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.
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.
File > Exit Closes the Import Imagery From D2C window.
Help Starts the on-line documentation.
SELECT TO
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.
The Stage CADRG Window includes the following selections for CIB:
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).
The Stage CADRG Window includes the following selections for CIB:
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.
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.
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.
The Assessment Mosaic Window contains the following selections for CIB:
SELECT TO
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.
SELECT TO
Submit Request Submit the job via the Batch Scheduler Window.
Done Exit the window.
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.
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.
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.
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.
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.
The Sheet Cutter Window contains the following selections for CIB:
SELECT TO
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.
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).
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.
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.
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.
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.”
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.
6. Select File > Exit to close the window.
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.
DPPDB Generation
Digital Point Positioning Database (DPPDB) is a product
composed of stereoscopic images stored on a DVD or 8mm
tape.
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.
SELECT TO
SELECT TO
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.
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.
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.
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
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
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.
SELECT TO
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
Footprint type. Use the Footprint Fill to color the inside of the selected
rectangle and IDs to display the name of the listed features.
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
selected rectangle and IDs to display the name of the listed features.
Footprint Fill Shades in a selected feature
IDs Displays the name of a selected feature.
SELECT TO
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
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
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.
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
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).
SELECT TO
GUI Needed
Segments that successfully validate are outlined in blue and segments that fail are identified by a
dashed brown line.
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.
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.
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.
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
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.
image segments. See the chapter on Brightness and Contrast Adjustment for detailed instructions
on adjusting the DRA for images.
SELECT TO
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.
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.
SELECT TO
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.
REJECT TO
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.
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.
CATEGORY DESCRIPTION
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.
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.
SELECT TO
CADRG Staging Location Direct the software to the location of the CADRG Staging Directory.
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.
SELECT TO
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.
A SOCET SET image location with sufficient disk space is required prior to creating a
geopositioning production job.
SELECT TO
SELECT TO
SELECT TO
Input File File selection window that enables you to browse to the storage location of
the support data and select the file.
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.
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).
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.
SELECT TO
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
Footprint type. Use the Footprint Fill to color the inside of the selected
rectangle and IDs to display the name of the listed features.
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
selected rectangle and IDs to display the name of the listed features.
Footprint Fill Shades in a selected feature
IDs Displays the name of a selected feature.
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
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.
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.
Help > Contents Starts the online documentation.
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.
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.
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.
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
SELECT TO
Merge > Available Displays ATF files stored in the project location.
Merge > Selected Builds the list of ATF files to be merged.
SELECT TO
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 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
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.
57.2.4 OpenFlight
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.
Help > Contents Starts the on-line documentation.
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.
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.
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.
SELECT TO
SELECT TO
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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-11 for details.
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.
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.
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.
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.
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.
Refer to Quick Reference Guide for a complete listing of Sketch Hot-keys.
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.
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.
SELECTION DESCRIPTION
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.
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
Sketch preferences are accessed though the application preference window. The Sketch
preference panels are as follows:
SELECT TO
SELECT TO
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.
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.
2. If the difference between the last point and the digitized point
is GREATER than the maximum distance then record the
digitized point.
3. If the difference between the last point and 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
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.
SELECT TO
SELECT TO
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.
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.
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.
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.
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.
Move to Point
}
Viewed only when
Options > Absolute
Accuracy is selected
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.
BLANK SPACE BLANK SPACE
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 BLANK SPACE
BLANK SPACE Display the slope between current and initial extraction cursor locations, as
Slope Percentage a percentage. Units specified by selected System.
BLANK SPACE BLANK SPACE
BLANK SPACE BLANK SPACE
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.
BLANK SPACE BLANK SPACE
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.
SELECT TO
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.
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
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.
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.
SELECT TO
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.
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).
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
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
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.
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
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
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.
• 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.
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.
Configuration Editor
TOOL FUNCTION
apmstats Prints out various statistics about gpf and ipf files.
dtm_compare Subtracts the elevation values of two DTMs and outputs the differences
into a third DTM
img_band_merge Converts RGB 24-bit color image to 8-bit grey level image
img_join Joins 3 separate band files into a single-3 band image file
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.
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
TOOL FUNCTION
tape_struct Reads a tape and reports record sizes of all files found
You can read additional information on some of these tools in the doc/readme_files
directory.
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.
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.
• 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.
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.
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.
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.
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.
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.
Help > Contents... Starts the on-line documentation.
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.
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.
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.
Cancel Close the window and ignores any changes you made.
Help Start the on-line documentation.
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.
SELECT TO
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.
Help Start the on-line documentation.
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.
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
main workstation window.
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:
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.
SELECT TO
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...).
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.
where "<cursor_file>" is the full path name to the file. For example, a common cursor that
could be used is shown below:
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.
<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)
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.
Film
Ground Oblique Oblique XY
(Object) Object Z
Ground
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.
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.
The footprint for each file type is drawn in a different color according to the following table:
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.
Help Starts the on-line documentation.
Close Exits the Stereo Model Manager 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.
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.
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.
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.
The Check Point File vs. Measured Point File window’s selections are as follows:
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.
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.
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.
3. Running in INTERACTIVE with a setting file as output, for preparing the setting file
interactively:
% cp orth1_check.gpf orth1_meas.gpf
8. Now invoke the Quality Statistics tool with the set of steps described in the section entitled
Invoking from the Main Workstation window.
qstat qstat
KEYWORD DESCRIPTION
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
qstat qstat
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_meas_point_file Point measured file, 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
KEYWORD DESCRIPTION
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_dtm_file Master DTM, selected from .dth files in your project directory
(include full path name)
input_dtm_slave_file Slave DTM, selected from .dth 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.
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
⎛ n ⎞
⎜ ⎟
⎜ ∑ d i⎟ ⁄ n
⎝i = 1 ⎠
outliers Differences that have absolute value greater than three times of std.
⎛ n ⎞
⎜ ⎟
⎜ ∑ d i⎟ ⁄ n + 3 σ
⎝i = 1 ⎠
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.
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.
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.
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.
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.
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.
SELECT TO
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.
Help Start the on-line documentation.
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”.
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.
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.
Help > Contents... Starts the on-line documentation.
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.
/<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.
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 > 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.
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.
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
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
Automatic Terrain Extraction.
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.
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
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
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.
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
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
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.
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
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
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.
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.
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.
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.
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.
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.
• 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.
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.
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.
% loc_a /export/home/tiger2/disk_a
% 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.
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
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.
have created the feature database, you can run “Save w/ New Spec” function in Feature
Extraction.
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
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.
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.
<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.
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.
<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.
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
SIZES 6
8 10 14 36 72 144
STYLES 4
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.
D.5.2 Hot-keys
You can change your hot-keys by clicking Preference > Keyboard/Trackball > Accelerator
Mapping on the main workstation window.
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.
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.
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.)
.projusernameset User username’s home directory Project Settings File — contains the
name of the last project you loaded.
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:
I Image
T Text
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
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
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.
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.
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.
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.
VITEC Don’t Touch. Contains data files needed for the VITec image
processing board.
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.
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.
• 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
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
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:
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.
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.
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.
SELECT TO
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.
S:\>ATBLANK
SPACEBLANK
SPACE
BLANK
SPACE BLANK SPACE
STATUS ID DAY TIME COMMAND LINE
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
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
STATUS ID DAY TIME COMMAND LINE
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
S:\>at
BLANK
S:\>AT SPACEBLANK
SPACE
BLANK
SPACE BLANK SPACE
STATUS ID DAY TIME COMMAND LINE
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
>atq
>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
RANK JOB
EXECUTION DATE OWNER JOB QUEUE
NAME
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.
cd /var/spool/cron/atjobs
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
cd /var/spool/cron/atjobs
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
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
# Comment line
# Comment line
# Comment line
# Comment line
% .
% .
% .
% chmod +x <shell_script_name>
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:
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:
# orthophotos
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:
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:
setting_file 1.1
application_a.keyword_1 data_value_a1
application_a.keyword_2 data_value_a2
application_a.keyword_3 data_value_a3
application_b.keyword_1 data_value_b1
application_b.keyword_2 data_value_b2
application_c.keyword_1 data_value_c1
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:
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.
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
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
Build Terrain Import (BIL) See “Batch Processing --- BIL Terrain Import” on page 17-31.
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 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 DXF Features See “Batch Processing - DXF Features Export” on page 18-17.
BATCH APPLICATIONS
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.
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 DXF Features See “Batch Processing - DXF Features Import” on page 18-4.
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.
Mosaic Sheet Cutter See “Batch Processing - Mosaic Sheet Cutter” on page 49-35
E.6 Examples
setting_file 1.1
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.
5. Alternatively, you can place these commands into a shell script called
minify_left_and_right:
% chmod +x minify_left_and_right
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.
3. Alternatively, you can place this command into a shell script called ate_single_dtm:
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
ortho.output_loc sample_location
ation
2. Run orthophoto in batch mode, specifying the setting file you created:
3. Alternatively, you can place this command into a shell script called
ortho_single_image:
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:
3. Alternatively, you can place this command into a shell script called convert_
generic_image:
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:
3. Alternatively, you can place this command into a shell script called frame_import_image:
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:
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:
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.
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.
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
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.
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.
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
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
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.
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.
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.
Geomorphic Editing with TIN: Pressing undo after inserting a new vertex in a TIN
breakline in ITE may corrupt the terrain file.
• 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.
• ClearFlite
Hot-keys for this application have been disabled.
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.
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
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.
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.
Applied enhancements may not take effect until the minification level is changed.
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
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).
• XIL Warning
Loading JPEG images on Solaris may give you an XIL obsolescence warning. This
message may be safely ignored.
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.
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.
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.
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
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: