.. _impexp_xml_query_tiling: parameter ^^^^^^^^^^^^^^^^^^ The ```` parameter allows for exporting the requested top-level features in tiles. Every tile is exported to its own target file within a separate subfolder of the export directory. Like the bounding box settings of the simple GUI-based export filter (cf. chapter :numref:`impexp_export_bbox_filter`), the ```` parameter requires three mandatory inputs: the ```` of the geographic region that should be tiled and the number of ```` and ```` into which the region should be evenly split. The ```` must be provided as bounding box using a ```` and an ```` element. The example below exports all buildings within the provided ```` into 2x2 tiles. .. code-block:: xml bldg:Building 10.7005978 47.5707931 10.7093525 47.5767573 2 2 Besides the mandatory input, the optional ```` parameter can be used to control the names of the subfolders and tile files, and whether tile information should be stored as generic attribute. The following subelements are supported: .. list-table:: Tiling options of the parameter. :name: impexp_query_expression_table :widths: 30 70 * - | ```` - | Name of subfolder that is created for each tile (default: *tile*). * - | ```` - | Suffix to append to each . Allowed values are *row_column* (default), *xMin_yMin*, *xMax_yMin*, *xMin_yMax*, *xMax_yMax* and *xMin_yMin_xMax_yMax*. * - | ```` - | Suffix to append to each tile filename. Allowed values are *none* (default) and *sameAsPath*. * - | ```` - | Add a generic attribute named *TILE* to each city object. * - | ```` - | Value for the generic attribute. Allowed values are identical to those for (default: *xMin_yMin_xMax_yMax)*. If the ```` element is not present, then the settings defined in the export preferences (cf. :numref:`impexp_preferences_export_tiling_chapter`) are used instead.