Access
The Access extension reads exterior orientations from a Microsoft Access database table (.mdb or .accdb).
Aerial triangulation file
In Aerial triangulation file, select Microsoft Access database files (*.mdb;*.accdb). Reads only .mdb or .accdb files.
Digi3D.AI opens the database using OLE DB provider Microsoft.ACE.OLEDB.16.0, which must be installed.
The database does not contain camera calibration. Specify a camera file in the model or select one when prompted (see Camera).
The extension does not provide absolute orientation.
Table and fields
Access Orientation Importer in configuration specifies the table and fields used to read orientations:
| Option | Default value | Field contents |
|---|---|---|
| Table | EXTERIOR ORIENTATION |
Table containing orientations. |
| Image | FICHERO |
Image name. |
| X, Y, Z | XL, YL, ZL |
Projection center coordinates. |
| Omega, Phi, Kappa | OM, PHI, K |
Rotations. |
In the same category:
- Image name with extension: Yes searches for the image file name with extension (
107.tif); No, without it (107). Defaults to No. - Rotation units: Radians, Sexagesimal or Centesimal. Defaults to Sexagesimal.
- Order of rotations: order used to build the rotation matrix. Defaults to Omega-Phi-Kappa.
For each model image, Digi3D.AI runs SELECT [X], [Y], [Z], [Omega], [Phi], [Kappa] FROM [Tabla] WHERE [Imagen] LIKE 'nombre' with the configured field names and uses the first returned record.
Coordinate reference system
Reads the .prj with the same name as the database (vuelo.prj for vuelo.mdb). Without .prj, displays Would you like to assign one?. Does not ask for the vertical system.
Error messages
- “The following error was found: error”: database access fails, for example because the configured table or field does not exist.
- “Image orientation not found: image”: the query returns no record for the left or right model image.