Choose the feature that matches the job.

Offline generation works without signing in. Synchronisation connects the QGIS project to the expedition records.

Offline map

Prepare the map for the field

Build a `.tairudb` with imagery, vectors, contour lines, a reference grid and elevation for Tairu Maps with no internet.

Synchronisation*

Exchange records with the expedition

Pull records as editable GeoPackage layers and push your features back as editable expedition records.

Automation

Repeat generation when needed

Run the same engine through the wizard, Processing, or the GeoPDF converter when the workflow needs a command line.

Which route should you use?

Start with the result your team needs.

The right TairuDB route depends on how the data will be used in the field.
When you need to…	TairuDB provides	In Tairu Maps
Take orthophotos, boundaries and terrain to a phone	A local `.tairudb`, with a size and time estimate before generation.	An offline map and read-only vectors.
Follow what was recorded in the field*	`Receber Registros` organises editable layers in the expedition GeoPackage.	The same records, with groups and identity retained.
Publish features the team can edit*	`Enviar camadas vetoriais` previews additions, updates and deletions.	Editable records in the `Registros` tab.
Repeat or automate an output	The `Tairu > TairuDB` Processing algorithm or GeoPDF converter.	A `.tairudb` file ready to import or share.

* Features that require a paid plan: Online or Realtime.

Project synchronisation*

The same information stays visible in QGIS and in the field.

QGIS with the Destoca layer selected and the Tairu Maps panel showing one update ready to synchronise — Layers received from the expedition stay organised in QGIS, and the panel shows what changed before the next push.

Destoca record in Tairu Maps with its map location and field photographs — The Destoca record keeps its position and photos in the same project used by the field team.

* Feature that requires a paid plan: Online or Realtime.

Before you install

The important limits are clear from the start.

Generation and sync are separate paths

The local wizard and Processing need no sign-in. Sign-in, expeditions, uploads and downloads require an Online or Realtime plan.

Vectors in a file are read-only

Vector layers in a `.tairudb` are not edited in the app, but chosen features can be incorporated as records, up to 500 at a time. Use layer push when the team needs to edit the whole layer in the field.

An online basemap is an explicit choice

It is included only when selected in `Parâmetros`; generation downloads tiles and the estimate shows how many first.

KML and layers opened inside ZIP files

Save the QGIS project after pushing. For persistent identity, extract the ZIP or convert the layer to GeoPackage.

GeoPDF is a command-line tool

The converter requires GDAL, pyproj and QGIS Python bindings; the input file needs usable spatial referencing.

The plugin interface is in Portuguese

Panel and button names remain in Portuguese even when QGIS uses another language.

Next step

Tutorials to follow once you choose the route.

QGIS · Portuguese

Create a `.tairudb` in QGIS

Install the plugin, choose the area, adjust layers and generate a file for offline use.

Open tutorial →

Tairu Maps · Portuguese

Import a `.tairudb`

Add the file to an expedition, check its content and test it before relying on it in the field.

Open tutorial →

Ready to open the panel in QGIS?

Install TairuDB from the official repository. Code, issues and suggestions are open on GitHub.

Install TairuDB