{"name": "TairuDB", "package_name": "tairu_db", "version": "2.0.7", "experimental": false, "qgis_min": "3.20.0", "qgis_max": "4.99.0", "downloads": 60, "uploaded_by": "danielhsm", "upload_datetime": "2026-06-20T13:12:55.487307", "changelog": "2.0.7 - Raster wizard: added \"Use visible map area\" option to select the current map canvas extent as the generation area. Fix: canceling .tairudb generation no longer crashes with \"wrapped C/C++ object has been deleted\" (finished signal is now disconnected before jobs are canceled).\n2.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.\n2.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.\n2.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.\n2.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.\n2.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.\n2.0.1 - Security hardening: HTTPS enforced on all outbound requests; SQL table names validated against strict regex; static analysis suppressions documented\n2.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\n1.2.1 - Support for QGIS 4\n1.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\n1.1 - GeoPDF converter added; rendering performance improvements\n1.0 - Initial release: raster tile generation for Tairu Maps", "external_deps": null, "download_url": "https://plugins.qgis.org/plugins/tairu_db/version/2.0.7/download/"}