Copy CoastWatch Navigation Offsets for Files Listed in Table

Copies navigation offsets from a source variable to destination variables in CoastWatch POES AVHRR CWF or HDF files listed in a table.

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 in the destination file, the entire navigation affine is reset by invoking the cwnavigate utility with the -R option.

Command line syntax

CoastWatchAVHRRCopyNavigationOffsetsArcGISTable_GeoEco <table> <coastWatchFileField> <sourceVariable> {destVariables;destVariables...} {where} {basePath}

Parameters

Expression	Explanation
<table>	Name of the table to query.
<coastWatchFileField>	Field containing the CoastWatch POES AVHRR CWF or HDF files. Navigation offsets will be extracted from the files in this field that contain the source variable and applied to the files that contain any of the destination variables, providing that the source file and destination file are for the same satellite image. If a file contains both the source variable and one or more destination variables, it will serve as both a source and destination file. To determine of two given files are for the same satellite image, this function compares the image time, satellite, sensor, center coordinates, cell size, number of rows and columns, projection, and spheroid. If all are the same, the files are assumed to be for the same satellite image. 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.
<sourceVariable>	CoastWatch variable in the source file from which navigation offsets should be copied.
{destVariables;destVariables...}	CoastWatch variables in the destination file to which the navigation offsets should be applied. In general, navigation offsets should only be applied to variables that are derived from sensor data. 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.
{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

CoastWatchAVHRRCopyNavigationOffsetsArcGISTable_GeoEco (table, coastWatchFileField, sourceVariable, destVariables, where, basePath)

Parameters

Expression	Explanation
Table (Required)	Name of the table to query.
CoastWatch file field (Required)	Field containing the CoastWatch POES AVHRR CWF or HDF files. Navigation offsets will be extracted from the files in this field that contain the source variable and applied to the files that contain any of the destination variables, providing that the source file and destination file are for the same satellite image. If a file contains both the source variable and one or more destination variables, it will serve as both a source and destination file. To determine of two given files are for the same satellite image, this function compares the image time, satellite, sensor, center coordinates, cell size, number of rows and columns, projection, and spheroid. If all are the same, the files are assumed to be for the same satellite image. 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.
Source variable for navigation (Required)	CoastWatch variable in the source file from which navigation offsets should be copied.
Destination variables to navigate (Optional)	CoastWatch variables in the destination file to which the navigation offsets should be applied. In general, navigation offsets should only be applied to variables that are derived from sensor data. 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.
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.