2.0.6 - QGIS copy/paste on pulled record layers now treats duplicated
recordId features as new records, so edited copies are created
separately instead of overwriting the original record during push.
2.0.5 - New record types and subtypes (occurrence, trail, point of
interest, drawing, and related subtypes). Contour lines are now
classified as drawing/line: when pushing layers, the default
type/subtype becomes Drawing/Line for layers with an ELEV field; in
.tairudb export, the contourLine type is no longer written and these
layers are saved as regular lines.
2.0.4 - Vector export to .tairudb: color, transparency, and width are
read from per-feature symbology (graduated, categorized, and
rule-based renderers) instead of falling back to the default blue.
Contour lines follow the same logic as record conversion: index
contours are thicker and more opaque, intermediate contours are
thinner and translucent.
2.0.3 - .tairudb generation: Tairu record layers (sync GeoPackages)
are automatically skipped during vector export, with a warning. This
avoids duplicated "ghost" geometries on the map when a record layer is
included in a .tairudb file.
2.0.2 - Contour lines: fixed import color handling (resolves the
"_PROP_FILL_COLOR_ is not defined" error on layers with
graduated/rule-based symbology); elevation-based titles ("Curve
140m"); automatic styling distinguishes index contours (thicker and
more opaque - width 3, opacity 0.8) from regular contours (thinner and
translucent - width 2, opacity 0.5), with automatic vertical-interval
detection. Fix: pushing a record that had been deleted in the app now
restores it instead of silently updating a hidden record.
2.0.1 - Security hardening: HTTPS enforced on all outbound requests;
SQL table names validated against strict regex; static analysis
suppressions documented
2.0 - Tairu Maps: dock panel with Firebase login (e-mail, Google,
Apple); pull records as GeoPackage layers and tairudb files as raster
layers (MBTiles); push vector layers as records with change preview;
wizard to generate and upload .tairudb rasters directly to a map
1.2.1 - Support for QGIS 4
1.2 - Multi-region support (one polygon feature per region); vector
layer export with JSON attributes; automatic tile retry on failure;
WebP support; dry run mode for estimating tile count, file size and
processing time
1.1 - GeoPDF converter added; rendering performance improvements
1.0 - Initial release: raster tile generation for Tairu Maps
yes
danielhsm
2026-06-19T19:25:18.734173+00:00
3.20.0
4.99.0
None
no
Plugin Tags