Export to SHP, TAB, Excel and GeoTIFF (and import into your project)

Resource Manager

, and all vector data and metadata of the project are stored in a single file called database.fmp. Therefore, all resources stored in different formats must be imported and exported within this database. Once imported, it is no longer necessary to keep the source files in the device's storage. On the contrary**, raster image files must not be deleted**, since the application will always read directly from them when rendering the map, importing only their references. Importing and exporting are done using the Resource Manager.

This window is accessible by pressing the button at the bottom of the layer menu. The resource list is shown in a resizable grid. To change the column width, drag your finger over the headers; to change the row height, drag vertically from the header of the first column. If you tap a header, you can sort the rows by the corresponding attribute. These attributes are:

• Selection box: Allows selecting multiple resources to apply actions to them from the top button bar. (Some actions are only available when items are selected).
• Resource options: Pressing this button opens a pop-up menu with the following actions:
  • Export to a file: Opens the file selection window to export the resource.
  • Delete : Removes the resource from the project. This action cannot be undone.
  • Edit table: Available when a single table is selected. Opens the table editor to modify its structure: attributes, data types, and projection.
  • Empty table: Removes all the content of a table.
  • Duplicate: Opens the Duplicate table dialog, which asks for a name for the copy and, if the table has an assigned export filter, offers the option Apply export filter (checked by default) to copy only the tuples matching that filter; unchecked, the entire table is duplicated with all its content. The new table keeps the internal tuple identifiers, the coordinate system (SRID), the supported geometry type, and the dimensions.
  • Calculate fields: Performs mass updates (UPDATE) on the table. (see Field Calculators).
  • Export filter: Allows selecting a filter, which will remain permanently associated with the table: each time that table is exported, only the tuples that meet the filter will be saved. Tables with an assigned export filter are marked with a characteristic mark in the resource list .
• Resource type:
  • Table.
  • Raster.
  • WMS service.
• Name: Name assigned to the resource.
• Layers: List of layers where the resource has been added in the current activity. If it is also used in another activity, it will be indicated as “Activity: ”.
• Modified: Date and time of the last modification made to the structure or content of the resource. It may also coincide with the moment of its creation.
• Imported: Date and time of the last import of the resource.
• Exported: Date and time of the last export. If the modification date is later than this, the cell will be highlighted.

You can scroll vertically or horizontally over the grid by dragging your finger over the rows. Tapping a row adds the resource as a layer in the current activity and automatically returns to the activity's interface.

At the top of the window is the action button bar. Some buttons only appear when one or more resources are selected. The available actions are:

• Import: Opens the file browser to select one or more files. The supported formats for tables are: .tab, .mif, .shp, .kml, .kmz, .gdb, .xls, .xlsx, .xlsm. For raster: .tiff, .jpg, .png, .ex2 (up to 1 Gigapixel), .pj2, .pdf, .grd. Other resources such as .lyrx, .lpkx, or the native .fmr can also be imported. When importing Excel spreadsheets, the application automatically detects the data type of each column and respects columns formatted as text (for example, codes or identifiers with leading zeros are not converted into numbers).
• Export: Exports all selected resources. This action opens a dialog that indicates the destination folder and warns that the exported resources will replace previous versions. It also offers the following options:

- **Destination folder:** By default, exports are saved in the Export subfolder of the project folder; you can change it by tapping the icon ![Destination folder button](/docs/assets/export-and-import-data-icon-08.webp){.icon}.
- **Export format**: You can select one or more of the available formats - TAB, SHP, XLS/XLSX, MIF, KML, KMZ, and GDB (ESRI Geodatabase, checked by default). Each resource will be exported in each of the selected formats; with GDB, all selected tables are dumped together into a single exports/<project>.gdb folder (one layer per table). Also, if that layer has an assigned geocoder, in the XLS format the headers of the columns whose selector has a title color defined in the geocoder take on that same color.
- **Apply dynamic style**: Some formats allow preserving styles. If this option is enabled, the dynamic style of the first layer where the table is used will be applied. 
- Subsequent action:
    - **Export only**: Exports the resources in the selected formats to the indicated folder.
    - **Export and send as zip**: Compresses the exported files into a .zip and launches an action to send them through another application.
    - **Export and send as zip, include images**: Same as the previous option, but adds the images from the project's DCIM folder to the .zip file.
- **Do not show again**: If you check this box, the selected options will be set as default and will not be asked again. To change them later, hold down the export button.

• KML/KMZ and ESRI Geodatabase (.gdb) vector formats: in addition to TAB, SHP, XLS, and MIF, KML/KMZ and ESRI Geodatabase are imported and exported preserving styles. KML/KMZ supports points, lines, and polygons mixed in the same layer (styled Placemarks; KMZ is a compressed KML). An ESRI Geodatabase is a .gdb folder (it can also be shared as .zip): when importing a layer with mixed geometries, it is automatically split into _puntos, _lineas and _poligonos tables; when exporting, one layer is generated per geometry family, and if a .gdb already exists at the destination it is opened in update mode, replacing the layer with the same name (it supports multiple tables). When the import finishes, it is confirmed with “KML imported” or “Geodatabase imported” as appropriate.
• Delete: Deletes the selected resources. This action cannot be undone.
• Add to map: Adds the selected resources as layers in the current activity (either on the map or in the strip log).
• New table: Creates an empty table from scratch. Opens the table editor to define its name, its attributes, and the projection.

Table editor

The table editor lets you create a new table or modify the structure of an existing table from within the application itself. It opens with the New table or Edit table actions of the Resource Manager and organizes the information into two tabs: Properties and Attributes.

In the Properties tab, the general characteristics of the table are defined:

• Name: name of the table in the database.
• Description: free text to describe the table.
• Coordinate dimensions: number of dimensions of the geometry's coordinates (for example, XY or XYZ).
• Projection: coordinate reference system (SRID) of the table. It can be changed with the edit button; when changed, the existing geometries are transformed automatically.

In the Attributes tab, the table's data columns are managed:

• The add button adds a new column, named Column N until you assign it a name.
• Each column has a name and a data type: integer, text, real, boolean, date and time, or decimal. Columns of the real type are shown but cannot be modified.
• Columns can be reordered by dragging them. There must be at least one attribute.

When saving, the application warns about operations that involve loss or transformation of data: deleting a column permanently removes that column and all its data; changing a column's type discards incompatible values; and changing the projection transforms the geometries. If the table is already in use, modifying its structure unassigns filters, dynamic styles, or geocoders that become incompatible, and it warns when a geocoder changed its fields. If you try to exit without saving, confirmation is requested.

Field calculators

Sometimes it is necessary to obtain coordinate columns based on the tuple's point, or vice versa. Other times it is useful to recalculate one or more attributes of a group of tuples. This tool is designed for that.

These are defined and saved as a project resource, so they can later be applied to different compatible tables, repeatedly. They can be imported and exported as .fmr.

Each calculator has a name and a list of table attributes to update, each of which has an SQL (spatialite) expression that will define the value to assign. In addition, they have a condition, which is an SQL WHERE-type expression similar to filters.

The assignments editor offers recipes to build the most common calculations. When selecting one of them, you will be asked to select the appropriate attributes of the associated table, and in the case of geometric functions, you will be asked for the target coordinate system. The expression fields also have an assistant to generate expressions with a suggestions pop-up.

You can apply a calculator by selecting it in the manager's list. When doing so, the application validates the expressions, shows a preview with the number of affected tuples, and asks for confirmation before running the update in the background; the action cannot be undone.