Tabular Datasets contain data in a columnar format as in a database table. Each column (field) must have a name and each column may only contain data of one type. Tabular datasets are used in many different objects.

The dataset may contain any number of columns (fields), columns containing easting (X) and northing (Y) are always required. Although a column with elevation or depth (Z) is optional in the dataset it may be required in some objects.

Access Database Source of any format
CSV File Source. Any CSV file containing at least easting (X) and northing (Y)
Firebird Database Source of any format
ODBC Source

In most cases (see model database below) a tabular dataset is defined as a SQL query containing the three usual sections: SELECT, FROM, and WHERE. The configuration dialog reflects these three sections.

SELECT
X: Field or column name for X coordinates (required).
Y: Field or column name for Y coordinates (required).
Z: Field or column name for Z coordinates. Be sure to check the “Z = Elevation” and “Z = Depth” radio buttons. Note: If Z = Depth the Z values are converted to elevation using the designated scene terrain model surface. See Project Settings.
ID: Field or column name for ID.
Additional fields (Optional): List the names of the fields that should be included in the resulting dataset. The default “*” means that all fields will be included. Warning: In joins including multiple tables this may result in a large number of fields. If this box is left blank all fields are included.

FROM
List the tables that contain the fields listed above in the SELECT box. Note: For CSV File Sources this is always the filename.

WHERE
Fixed Extent: By default the dataset extent is identical to the current scene extent. However, this option makes it is possible to fix the extent to any area.

Horizontal Extent: Defines a rectangular area where data are extracted from the source. Note that the values uses the fields for X and Y entered in the SELECT box.

Additional conditions (optional): The dataset may be refined further using SQL. This makes it possible to use regular SQL to query the source database or CSV file within the extent. This is an advanced option that can be used for users that has an in depth knowledge of the source format.

Example: Join two tables (Table1 and Table2) in the dataset. Both tables has an ID Field.
Table1.ID = Table2.ID

Preview Buttons
Preview SQL…: Shows a preview of the resulting query. Advanced users can use this option to analyze the resulting query.
Preview Data…: Shows a preview of the data resulting from the query using the Dataset Viewer.

When the source for the tabular dataset is an Access database and is specified to be in Model Database format then the configuration of the dataset is simpler. Simply select a model and a digimodel to import. If you want to extract other data from a model database as a tabular dataset simply specify the source database format as unspecified.