cnetextract
Extracts portions of an existing Control Network
Extracts Control Points into a new Control Network from a specified Control Network in accordance to specified filters.
Currently, the filters are divided into four categories: Exclusive Filters, Inclusive Filters, Cube Filters, and Lat/Lon Filters.
Exclusive Filters prevent extraction. They are taken into consideration last and have the highest priority. This means that if any other filter creates a selected Exclusive Filter condition during processing, that Exclusive Filter will prevent the extraction. For example, if the Cube Filters CUBES, CUBELIST, and CUBEMEASURES are used along with the Exclusive Filter NOSINGLEMEASURES, then an input Control Point which contains only one cube in the CUBELIST will not be extracted, regardless of the number of Control Measures it had on input. This is because NOSINGLEMEASURES will see it as a Control Point with exactly one Control Measure and prevent its extraction. If only Exclusive Filters are used, all Control Points/Measures that do not have an exclusive property will be extracted.
Inclusive Filters allow extraction. They only extract Control Points and/or Measures that are included in the Inclusive Filter. In addition, each Inclusive Filter is associated with an explicit property of the Control Point/Measure. If more than one Inclusive Filter is selected, only Control Points/Measures that contain all inclusive properties will be extracted.
Cube Filters also allow extraction, however, they pertain to the cubes contained within the Control Points/Measures. Option RETAIN_REFERENCE will extract the Reference even if not in the Cube List.
Lat/Lon Filters allow extraction as well, however, they only extract Control Points/Measures that lie in the lat/lon bounding box.
A summary of the Control Points not extracted, listed by the filter which prevented them from being extracted, can be included in optional report files. See the PREFIX and filter keywords for more details. The following table lists the output file names, the corresponding filter for the output file, and a description of the contents of the output file. These output files will only be generated if PREFIX has been defined.
OutputReport | Filter | Reason for not extracting the points/measures in this report |
---|---|---|
[PREFIX]IgnoredPoints.txt |
NOIGNORE |
These points are set to ignored. |
[PREFIX]IgnoredMeasures.txt |
NOIGNORE |
These measures are set to ignored. Ignored reference measures are
always extracted, however they are still listed in this report
with the note: Ignored measure but extracted since it is Reference.
|
[PREFIX]SingleMeasurePoints.txt |
NOSINGLEMEASURES |
These points have only one measure. |
[PREFIX]MeasurelessPoints.txt |
NOMEASURELESS and REFERENCE |
These points have no measures. |
[PREFIX]NonReferenceMeasures.txt |
REFERENCE |
These measures are not reference measures. |
[PREFIX]NonFixedPoints.txt |
FIXED |
These points are not fixed. |
[PREFIX]NonConstrainedPoints.txt |
CONSTRAINED |
These points are not constrained. |
[PREFIX]NonEditLockedPoints.txt |
EDITLOCKED |
These points are not editlocked. |
[PREFIX]TolerancePoints.txt |
TOLERANCE |
These points have line and/or sample less than the given
PIXELTOLERANCE.
|
[PREFIX]NonListedPoints.txt |
POINTSLIST |
These points are not in the given POINTLIST.
|
[PREFIX]NonCubePoints.txt |
CUBES |
These points have no measures corresponding to the given CUBELIST.
|
[PREFIX]NonCubeMeasures.txt |
CUBES, CUBEMEASURES, and RETAIN_REFERENCE |
These are measures for extracted points that do not correspond to
cubes in the given CUBELIST. If RETAIN_REFERENCE is true,
all reference measures for extracted points will be extracted,
however any reference measure that does not correspond to cubes
in the cubelist will still be listed in this report with the note:
Reference not in the cubelist but extracted since RETAIN_REFERENCE=true.
|
[PREFIX]LatLonOutOfRange.txt |
LATLON |
These points have a latitude and/or longitude that is not in the given MINLAT/MAXLAT or MINLON/MAXLON range. |
[PREFIX]NoLatLonPoints.txt |
LATLON |
These points do not have a determineable latitude and/or longitude value. |
Categories
History
Christopher Austin | 2009-07-22 | Original version |
Christopher Austin | 2009-07-31 | Refactored for readability, added parameter defaults, and added detail to the application log. |
Christopher Austin | 2009-08-11 | Added an additional output progress bar. |
Christopher Austin | 2009-08-21 | Added the points kept to the print file. |
Christopher Austin | 2009-08-28 | Fixed TOLIST blank lines, added the POINTLIST option, and changed the CUBEPOINTS parameter to take a filename instead of a boolean. |
Christopher Austin | 2009-09-29 | Added the TOLERANCE parameter. |
Christopher Austin | 2009-10-02 | Changed the TOLERANCE keyword to extract points with an error greater than or equal to the TOLERANCE, instead of less than or eqaul to. |
Christopher Austin | 2009-10-15 | Fixed the TOLERANCE code. |
Christopher Austin | 2009-11-02 | Fixed the interface to be more clear. |
Christopher Austin | 2009-11-09 | Added the GROUND parameter. |
Christopher Austin | 2010-01-20 | Added the USENETWORK parameter to avoid the need for spiceinit prior to knowing which cubes are necessary for the extracted control network. |
Christopher Austin | 2010-02-01 | FROMLIST is now an option parameter, however, to be able to generate a TOLIST, the FROMLIST must be provided. Also did some code cleanup. |
Christopher Austin | 2010-03-01 | Changed NOSINGLEMEASURES to NOMEASURELESS and fixed a simple progress bug. |
Christopher Austin | 2010-03-03 | Fixed min/max lat/lon bounding issues. |
Christopher Austin | 2010-03-08 | Brought back NOSINGLEMEASURES while leaving NOMEASURELESS as is. |
Christopher Austin | 2010-06-18 | Added PREFIX and moved all detailed output from the print.prt to the PREFIX files for each filter parameter. |
Christopher Austin | 2010-06-30 | Rewrote documentation and reorganized keywords into groups. |
Christopher Austin | 2010-11-08 | Fixed for binary cnet conversion. |
Christopher Austin | 2011-01-18 | Altered to compile with the new Control redesign. |
Jai Rideout | 2011-04-12 | Changed OUTNET to ONET for consistency. |
Sharmila Prasad | 2011-05-27 | Added an option RETAIN_REFERENCE to extract the Reference measure even if it is not in the CUBELIST |
Debbie A. Cook and Tracie Sucharski | 2011-06-07 | Change point types "Ground" to "Fixed" and "Tie" to "Free". |
Stuart Sides | 2011-10-07 | Added documentation with Annie Howington-Kraus and Ella Lee. |
Jeannie Backer | 2012-06-22 | Added and modified documentation for filters and PREFIX report files to better reflect how the program filters work. References #927. |
Jeannie Backer | 2012-07-11 | Modified application to not create empty output files. If a file is not created, a comment will be printed in the results log. Fixes #253. Fixed bug in NOMEASURELESS and POINTLIST filters. These were not being properly handled by the program. Replaced summary keyword NoCubeMeasure with NonCubeMeasures for consitency with NonCubePoints. Modified and added new appTests to reflect changes. Fixes #955. Added webpage example. Added documentation to Makefiles. Updated xml documentation and clarified output reports for [PREFIX]IgnoredMeasures.txt and [PREFIX]NonCubeMeasures.txt Fixes #927. |
Debbie A. Cook | 2012-11-30 | Changed to use TProjection instead of Projection. References #775. |
Moses P. Milazzo | 2014-11-13 | Added EditLocked and Constrained filters. References #255. |
Kelvin Rodriguez | 2016-08-16 | removed redundant boolean statement (len == 0) which caused warnings in clang. Part of porting to OS X 10.11. |
Ian Humphrey | 2016-09-29 | When using LATLON=true, control points that are out of the specified latitude and longitude ranges will now be properly recorded into the approriate output text files. See the internal history for cnetextract.cpp's ExtractLatLonRange() for more detailed change information. |