ISIS Application Documentation
|Standard View | TOC | Home|
Integrated Photogrammetric Control Environment
The quality of digital image mosaics (DIM) and digital elevation models (DEM) - and geologic maps using such products as basemaps - depends greatly upon accurate sensor position and pointing parameters. Spacecraft ephemeris and attitude data provide initial estimates for these parameters. Uncertainty in these data propagate to errors in mapping products. To minimize errors, images are controlled photogrammetrically. Overlapping images are registered to one another by measuring common features (tie points). Images may be tied to the ground by measuring features identifiable on base maps or DEMs (control points). Image measurements are input to the least-squares bundle adjustment which generates improved sensor position and pointing parameters plus the triangulated coordinates of tie and control points.
The objective of the Integrated Photogrammetric Control Environment (IPCE) is to incorporate all aspects of the photogrammetric control process within a single interactive and user friendly environment. A project oriented design simplifies data management with the ability to save and restore project data and settings. Multiple, integrated views of data and processing output help to streamline the control workflow.
IPCE currently includes functionality from the standalone isis applications jigsaw, qview, qnet, qmos, and cneteditor. Control networks can be visualized in a table view (e.g. cneteditor), or overlaid on an image view (e.g. qview, qnet) or an image footprint view (e.g. qmos). Control networks can be edited from these views as well. Editing includes adding, deleting, and refining control points and measures or modifying metadata associated with them. The bundle adjustment (e.g. jigsaw) can be performed any number of times within IPCE. Results can be analyzed, compared against other bundle adjustment runs, and saved/restored as part of the IPCE project.
A link to the IPCE User's Manual (PDF format) is given below under Related Objects and Documents. It contains example workflows as well as details on using the application.
|Ken Edmundson||2012-04-03||Original version|
|Ian Humphrey||2016-11-09||The main window state is now saved properly when running ipce. If running ipce without opening a project, the config files are saved as ipce_Project.config (Project is the default project name). Otherwise, when a project is loaded, config files are saved as ipce_ProjectName.config, where ProjectName is the name of the loaded project. Fixes #4358.|
|Tyler Wilson||2016-11-10||Changed the alias reference for the data_management.png icon from 'data' to 'data-management'. Annoying errors were showing up on the command line when the application was launched due to a naming conflict. Fixes #3982.|
|Tracie Sucharski||2017-06-22||Changed name of application from cnetsuite to ipce.|
|Summer Stapleton||2017-08-14||Updated ipce to only include licensed or open source images and icons. Fixes #5105.|
|Ken Edmundson, et al.||2018-07-30||Added ability to specify bundle observation solve settings on a per image basis. Added control net health monitor. Changed interface to allow views to be dockable.|