This is a list of recognized and supported fields for the frames table of the frame camera raster type. This table enables specification of parameters that control exterior orientation (EO). For more details about the Esri frame camera raster type, and frame and camera schemas, please refer to the description document.
The frames table can be stored in several formats: a geodatabase table, a feature class table, or a .csv file. Listed below are all of the supported fields. After this list is an example of a frames table.
A parameter definition in the frames table takes precedence over any duplicate definitions within the cameras table.
List of fields supported in the frames table
|Field name||Field type||Data type||Description|
The path to the image file.
A unique field within the cameras table from where the orientation parameters are loaded.
The x-coordinate of the perspective center in the ground coordinate system. The units are in the coordinate system units.
The geographic coordinate system units are not currently supported. Specify the PerspectiveX value in projected coordinate system units.
The y-coordinate of the perspective center in the ground coordinate system. The units are in the coordinate system units.
The geographic coordinate system units are not currently supported. Specify the PerspectiveY value in projected coordinate system units.
The z-coordinate value of the perspective center in the ground coordinate system. The z-coordinate units should be consistent with the x- and y-coordinate units.
The z-coordinates are typically expressed as orthometric heights, which means elevation above sea level. This is appropriate if you will be inputting a DEM that is also using orthometric heights. If you have z-coordinates that are using ellipsoidal heights, your DEM should also be in ellipsoidal heights.
For the case where z-units are ellipsoidal and the DEM is orthometric, the Geoid flag can be used to enable an approximate correction.
The rotational angle of the camera's x-axis in degrees. The units are in decimal degrees.
The rotational angle of the camera's y-axis in degrees. The units are in decimal degrees.
The rotational angle of the camera's z-axis in degrees. The units are in decimal degrees.
The matrix describing the transformation from image space to map space.
The matrix is specified as nine floating-point values, which are delimited by spaces or semicolons.
The polygon identifying the region containing valid image data. This polygon becomes the footprint of the corresponding mosaic dataset item.
An alias name to identify the image. If this is left blank, the image file name is used.
A tag that enables the image to participate in a function template.
An optional categorization for images. All images with the same group name participate together in a function template.
The name of the strip (run).
Coordinate system associated with the perspective point as WKT-PRJ string or file path or EPSG code. Defaults to data-specified or mosaic dataset SR. The spatial reference can be defined for each image item in the mosaic dataset as well. If SRS field is defined both in the cameras table and the frames table, the value in the frames table will take precedence.
Required*—The frames table must have either the Omega, Phi, and Kappa fields or the Matrix field in order for the data to be added to the mosaic dataset. If both types of EO exist in the table, the transformation matrix value will be used.
Example of a frames table
Below is an example of a frames table stored as a geodatabase table, and where only a selection of the available fields are being used. Since only four frames (images) are used in this example, there are only four rows in the table.
Example of a frames table