Set Navigation Offsets of CoastWatch Files Listed in Table

Sets the navigation offsets of the CoastWatch POES AVHRR CWF or HDF files listed in a table to the values specified by two fields.

The navigation offsets are the e and f coefficients of the navigation affine attribute of each variable (the HDF nav_affine attribute). Prior to setting the navigation offsets, the entire navigation affine is reset by invoking the cwnavigate utility with the -R option.

Command line syntax

CoastWatchAVHRRSetNavigationOffsetsArcGISTable_GeoEco <table> <coastWatchFileField> <navOffsetXField> <navOffsetYField> {variables;variables...} {where} {orderBy;orderBy...} {directions;directions...} {basePath}

Parameters

Expression	Explanation
<table>	Table to query.
<coastWatchFileField>	Field containing the paths of the CoastWatch POES AVHRR CWF or HDF files. Only CoastWatch POES AVHRR files are supported. Other CoastWatch files, such as those for the GOES satellite series, will be skipped and a warning will be reported. Compressed files in a supported compression format will be automatically decompressed. Archives (e.g. .zip or .tar) must contain exactly one file, which must not be in a subdirectory.
<navOffsetXField>	Field containing the horizontal offsets to apply to the images in the corresponding files, expressed as the number of pixels that the images should be shifted horizontally, where positive is east and negative is west. Because CWF files only support integer offsets, the fractional part of non-integer offsets will be truncated prior to applying them to CWF files. For example, the values 3.01, 3.5, and 3.99 will all be truncated to the value 3.
<navOffsetYField>	Field containing the vertical offsets to apply to the images in the corresponding files, expressed as the number of pixels that the images should be shifted vertically, where positive is north and negative is south. Because CWF files only support integer offsets, the fractional part of non-integer offsets will be truncated prior to applying them to CWF files. For example, the values 3.01, 3.5, and 3.99 will all be truncated to the value 3.
{variables;variables...}	CoastWatch variables to which the navigation offsets should be applied. In general, navigation offsets should only be applied to variables that are derived from sensor data, not variables that represent positional metadata. At the time of this writing, the variables derived from sensor data included: avhrr_ch1 avhrr_ch2 avhrr_ch3 avhrr_ch3a avhrr_ch4 avhrr_ch5 cloud cloudx sst Peter Hollemans, one of the lead CoastWatch researchers at NOAA, suggested that navigation offsets should not be applied to the graphics, rel_azimuth, sat_zenith, and sun_zenith variables. With respect to the last three, he said: "I've thought about it for a while and my inclination is to say don't correct the angle data. It's not a perfect solution -- ie: if we knew the satellite's position and orientation perfectly and recomputed the angle data, we would find very small discrepancies compared with the navigation-corrected version."
{where}	SQL WHERE clause expression that specifies the subset of rows to process. If this parameter is not provided, all of the rows will be processed. If this parameter is provided but the underlying database does not support WHERE clauses, an error will be raised. The exact syntax of this expression depends on the underlying database. ESRI recommends you reference fields using the following syntax: If you're querying ArcInfo coverages, shapefiles, INFO tables or dBASE tables (.dbf files), enclose field names in double quotes in the SQL expression: "MY_FIELD". If you're querying Microsoft Access tables or personal geodatabase tables, enclose field names in square brackets: [MY_FIELD]. If you're querying ArcSDE geodatabase tables, an ArcIMS feature class, or an ArcIMS image service sublayer, don't enclose field names: MY_FIELD.
{orderBy;orderBy...}	Fields that will be used to sort the rows (i.e., the columns specified in the ORDER BY clause of a SQL SELECT statement). If no fields are provided, the rows will be sorted in the default order determined by the underlying database. If this parameter is provided but this computer is not running ArcGIS 9.2 or later or the underlying database does not support ORDER BY clauses, an error will be raised. In addition to specifying the ORDER BY fields, you must also specify the sort direction for each field.
{directions;directions...}	List of strings, either 'Ascending' or 'Descending', that specify the sort directions for the ORDER BY fields. If this parameter is provided but this computer is not running ArcGIS 9.2 or later or the underlying database does not support ORDER BY clauses, an error will be raised.
{basePath}	Base path to prepend to relative paths. If a base path is provided, it will be prepended to any relative paths that are obtained from the fields that list the inputs (and outputs, if this tool has outputs). If a base path is not provided, the workspace containing the table will be prepended instead.

Scripting syntax

CoastWatchAVHRRSetNavigationOffsetsArcGISTable_GeoEco (table, coastWatchFileField, navOffsetXField, navOffsetYField, variables, where, orderBy, directions, basePath)

Parameters

Expression	Explanation
Table (Required)	Table to query.
CoastWatch file field (Required)	Field containing the paths of the CoastWatch POES AVHRR CWF or HDF files. Only CoastWatch POES AVHRR files are supported. Other CoastWatch files, such as those for the GOES satellite series, will be skipped and a warning will be reported. Compressed files in a supported compression format will be automatically decompressed. Archives (e.g. .zip or .tar) must contain exactly one file, which must not be in a subdirectory.
Horizontal navigation offset field (Required)	Field containing the horizontal offsets to apply to the images in the corresponding files, expressed as the number of pixels that the images should be shifted horizontally, where positive is east and negative is west. Because CWF files only support integer offsets, the fractional part of non-integer offsets will be truncated prior to applying them to CWF files. For example, the values 3.01, 3.5, and 3.99 will all be truncated to the value 3.
Vertical navigation offset field (Required)	Field containing the vertical offsets to apply to the images in the corresponding files, expressed as the number of pixels that the images should be shifted vertically, where positive is north and negative is south. Because CWF files only support integer offsets, the fractional part of non-integer offsets will be truncated prior to applying them to CWF files. For example, the values 3.01, 3.5, and 3.99 will all be truncated to the value 3.
Variables to navigate (Optional)	CoastWatch variables to which the navigation offsets should be applied. In general, navigation offsets should only be applied to variables that are derived from sensor data, not variables that represent positional metadata. At the time of this writing, the variables derived from sensor data included: avhrr_ch1 avhrr_ch2 avhrr_ch3 avhrr_ch3a avhrr_ch4 avhrr_ch5 cloud cloudx sst Peter Hollemans, one of the lead CoastWatch researchers at NOAA, suggested that navigation offsets should not be applied to the graphics, rel_azimuth, sat_zenith, and sun_zenith variables. With respect to the last three, he said: "I've thought about it for a while and my inclination is to say don't correct the angle data. It's not a perfect solution -- ie: if we knew the satellite's position and orientation perfectly and recomputed the angle data, we would find very small discrepancies compared with the navigation-corrected version."
Where clause (Optional)	SQL WHERE clause expression that specifies the subset of rows to process. If this parameter is not provided, all of the rows will be processed. If this parameter is provided but the underlying database does not support WHERE clauses, an error will be raised. The exact syntax of this expression depends on the underlying database. ESRI recommends you reference fields using the following syntax: If you're querying ArcInfo coverages, shapefiles, INFO tables or dBASE tables (.dbf files), enclose field names in double quotes in the SQL expression: "MY_FIELD". If you're querying Microsoft Access tables or personal geodatabase tables, enclose field names in square brackets: [MY_FIELD]. If you're querying ArcSDE geodatabase tables, an ArcIMS feature class, or an ArcIMS image service sublayer, don't enclose field names: MY_FIELD.
Order By fields (Optional)	Fields that will be used to sort the rows (i.e., the columns specified in the ORDER BY clause of a SQL SELECT statement). If no fields are provided, the rows will be sorted in the default order determined by the underlying database. If this parameter is provided but this computer is not running ArcGIS 9.2 or later or the underlying database does not support ORDER BY clauses, an error will be raised. In addition to specifying the ORDER BY fields, you must also specify the sort direction for each field.
Order By directions (Optional)	List of strings, either 'Ascending' or 'Descending', that specify the sort directions for the ORDER BY fields. If this parameter is provided but this computer is not running ArcGIS 9.2 or later or the underlying database does not support ORDER BY clauses, an error will be raised.
Base path (Optional)	Base path to prepend to relative paths. If a base path is provided, it will be prepended to any relative paths that are obtained from the fields that list the inputs (and outputs, if this tool has outputs). If a base path is not provided, the workspace containing the table will be prepended instead.