Virtual Format

OGR Virtual Format is a driver that transforms features read from other drivers based on criteria specified in an XML control file. It is primarily used to derive spatial layers from flat tables with spatial information in attribute columns. It can also be used to associated coordinate system information with a datasource, merge layers from different datasources into a single data source, or even just to provide an anchor file for access to non-file oriented datasources.

The virtual files are currently normally prepared by hand.

Creation Issues

Currently the ODBC VRT driver is read-only, so new features, tables and datasources cannot normally be created by OGR applications. This limitation may be removed in the future.

Virtual File Format

The root element of the XML control file is OGRVRTDataSource. It has an OGRVRTLayer child for each layer in the virtual datasource. That element may have the following subelements:

SrcDataSource (manditory): The value is the name of the datasource that this layer will be derived from. The element may optionally have a relativeToVRT attribute which defaults to "0", but if "1" indicates that the source datasource should be interpreted as relative to the virtual file. This can be any OGR supported dataset, including ODBC, CSV, etc.
SrcLayer (optional): The value is the name of the layer on the source data source from which this virtual layer should be derived. If this element isn't provided, then the SrcSQL element must be provided.
SrcSQL (optional): An SQL statement to execute to generate the desired layer result. This should be provided instead of the SrcLayer for statement derived results. Some limitations may apply for SQL derived layers.
FID (optional): Name of the attribute column from which the FID of features should be derived. If not provided, the FID of the source features will be used directly.
GeometryType (optional): The geometry type to be assigned to the layer. If not provided it will be taken from the source layer. The value should be one of "wkbNone", "wkbUnknown", "wkbPoint", "wkbLineString", "wkbPolygon", "wkbMultiPoint", "wkbMultiLineString", "wkbMultiPolygon", or "wkbGeometryCollection". Optionally "25D" may be appended to mark it as including Z coordinates. Defaults to "wkbUnknown" indicating that any geometry type is allowed.
LayerSRS (optional): The value of this element is the spatial reference to use for the layer. If not provided, it is inherited from the source layer. The value may be WKT or any other input that is accepted by the OGRSpatialReference::SetUserInput() method.
GeometryField (optional): This element is used to define how the geometry for features should be derived. If not provided the geometry of the source feature is copied directly. The type of geometry encoding is indicated with the encoding attribute which may have the value "WKT", "WKB" or "PointFromColumns". If the encoding is "WKT" or "WKB" then the field attribute will have the name of the field containing the WKT or WKB geometry. If the encoding is "PointFromColumns" then the x, y and z attributes will have the names of the columns to be used for the X, Y and Z coordinates. The z attribute is optional.

Example: ODBC Point Layer

In the following example (disease.ovf) the worms table from the ODBC database DISEASE is used to form a spatial layer. The virtual file uses the "x" and "y" columns to get the spatial location. It also marks the layer as a point layer, and as being in the WGS84 coordinate system.

<OGRVRTDataSource>

    <OGRVRTLayer name="worms">
        <SrcDataSource>ODBC:DISEASE,worms</SrcDataSource> 
 	<SrcLayer>worms</SrcLayer> 
	<GeometryType>wkbPoint</GeometryType> 
        <LayerSRS>WGS84</LayerSRS>
	<GeometryField encoding="PointFromColumns" x="x" y="y"/> 
    </OGRVRTLayer>

</OGRVRTDataSource>

Other Notes

When the GeometryField is "WKT" spatial filtering is applied after extracting all rows from the source datasource. Essentially that means there is no fast spatial filtering on WKT derived geometries.
When the GeometryField is "PointFromColumns", and a SrcLayer (as opposed to SrcSQL) is used, and a spatial filter is in effect on the virtual layer then the spatial filter will be internally translated into an attribute filter on the X and Y columns in the SrcLayer. In cases where fast spatial filtering is important it can be helpful to index the X and Y columns in the source datastore, if that is possible. For instance if the source is an RDBMS.
Normally the SrcDataSource is a non-spatial tabular format (such as MySQL, SQLite, CSV, or ODBC) but it can also be a spatial database in which case the geometry can be directly copied over.