Skip to content

Instantly share code, notes, and snippets.

@signedav
signedav / baker_usabilityhub_exporter_final.md
Last active August 26, 2022 10:57
QGIS Model Baker - UsabILIty Hub Exporter Final Concept

UsabIlity Hub Exporter Final Concept

Final concept only containing things that will be implemented and addtional notes how the technical implementation could be.

1. Create UsabILIty Meta Data

New wizard with an own button / menu entry.

image

@signedav
signedav / changelog_710.md
Last active April 8, 2022 07:37
Changelog 7.1.0

With release 7.1. of the QGIS Model Baker the backend library is separated from the graphical components. As well there PostgreSQL services are supported (pg_service.conf) in the database selection as well as the SSL mode. Another nice thing is the new "Link Child Dialog" in the Relation Editor Widget provided by the new plugin Linking Relation Editor

Linking Relation Editor

With Qgis Model Baker the Linking Relation Editor plugin is loaded as dependency. When a project is generated this widget type is chosen as the Relation Editor Widget.

image

When linking child features there will be opened a much more comfortable dialog, than we are used to. image

@signedav
signedav / usabilityhub_id_and_layertree.md
Last active March 23, 2022 08:17
UsabILIty Hub Layertree concept

Note that those are only notes made by @signedav and not a clearly defined concept. See for the implemented part opengisch/QgisModelBaker#648

Layertree, internal Id and Relations

Super Layertree

First of all the layer tree file gets powerfull.

The layer tree file will contain in future:

  • Optional internal id's in the layers (and the groups) - not integrated
@signedav
signedav / baker_usabilityhub_exporter.md
Last active July 15, 2022 11:41
QGIS Model Baker - UsabILIty Hub Exporter

UsabIlity Hub Exporter

This is the original started concept, containing a lot of general thoughts. For the final concept see: https://gist.github.com/signedav/44b12b6667c707f646dc6177e026ac56

1. Create UsabILIty Meta Data

We will have a new wizard - and not to insert it into the existing workflow wizard, since it's kind of an operator functionality and the normal user should not be confronted to much with it - with an own button / menu entry.

image

@signedav
signedav / Intersection_ErrorLog.md
Created December 20, 2021 15:38
Intersection_ErrorLog.
<?xml version="1.0" encoding="UTF-8"?><TRANSFER xmlns="http://www.interlis.ch/INTERLIS2.3">
<HEADERSECTION SENDER="ili2pg-4.6.1-63db90def1260a503f0f2d4cb846686cd4851184" VERSION="2.3"><MODELS><MODEL NAME="IliVErrors" VERSION="2016-06-10" URI="mailto:ceis@localhost"></MODEL></MODELS></HEADERSECTION>
<DATASECTION>
<IliVErrors.ErrorLog BID="b1">
<IliVErrors.ErrorLog.Error TID="o1"><Message>ili2pg-4.6.1-63db90def1260a503f0f2d4cb846686cd4851184</Message><Type>Info</Type><TechDetails>logGeneralInfo():  (Ili2db.java:1458)</TechDetails></IliVErrors.ErrorLog.Error>
<IliVErrors.ErrorLog.Error TID="o2"><Message>ili2c-5.2.3-3ec7a10e9bacc87e149a14a7f11a6035e0481c69</Message><Type>Info</Type><TechDetails>logGeneralInfo():  (Ili2db.java:1459)</TechDetails></IliVErrors.ErrorLog.Error>
<IliVErrors.ErrorLog.Error TID="o3"><Message>iox-ili-1.21.8-a6aee68136447c0616995e56888fa9c7ef362a77</Message><Type>Info</Type><TechDetails>logGeneralInfo():  (Ili2db.java:1460)</TechDetails></IliVErrors.ErrorLog.Error>
<IliVErrors.ErrorLog
@signedav
signedav / QField_ReleaseManagerNotes.md
Last active October 21, 2021 06:57
QField Release Manager Notes

Labels on QField Repo

Top Level Labels (CATEGORIES) Usually an issue has only one of them

  • BUG
  • ENHANCEMENT
  • SUPPORT
  • INPUT
  • QUESTION
@signedav
signedav / qgis_modelbaker_redesign_v2.md
Last active July 8, 2021 08:10
Qgis Model Baker Redesign 0.2

Workflow

0 There might be a start dialog

welcome

  • On first selection, we come to 1 Choose the file
  • On second selectoin, we come to Export Workflow
  • On third selection, we come to 2 Choose the database

1 Choose the files

First page on opening the wizard asks you to load the files and the models you want to import:

Use case

Assets should have multiple region of interests (and back) what can be multiple geometries of every type

Inheritance

ILI

INTERLIS 2.3;

MODEL RegionOfInterest_Inheritance (en) 
@signedav
signedav / usabilityhub_tech_doc.md
Last active February 4, 2021 08:34
UsabILIty Hub Technisches Dokument

Zusammenfassung

Ein ilidata.xml basiert auf dem Model DatasetIdx16. Es enthält Elemente "DatasetMetadata" wo relative Pfade zu Files definiert sind. Die Files liegen auf demselben Server/Repo wie das ilidata.xml. Es gibt verschiedene Server/Repos. Die "DatasetMetadata" werden anhand einer Systemübergreifenden Id identifiziert. Es ist dem Benutzer überlassen, wie diese Id lautet (in den Beispielen werden UUIDs genommen).

Ein Meta-Konfigurationsfile ist eine INI-Datei, die Konfigurationen für ein oder mehrere Tools enthält. Dort kann auf andere Files referenziert werden - anhand der Systemübergreifenden DatasetMetadata-Id.

Die Tools können dies unterschiedlich handhaben. ZBs. wird ili2db das Meta-Konfigurationsfile übergeben. Dort ist dann auch das Modell spezifiziert. Im ModelBaker hingegen startet man (meistens) mit dem Modell. Wenn ein Modell importiert wird, soll auf allen relevanten Servern/Repos nach relevanten Meta-Konfigurationsfiles gesucht werden (und Katalogen - mehr dazu später). Die benötigte