Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Faulty extension handling on export #128

Closed
cymed opened this issue Jun 20, 2023 · 1 comment
Closed

Faulty extension handling on export #128

cymed opened this issue Jun 20, 2023 · 1 comment

Comments

@cymed
Copy link

cymed commented Jun 20, 2023

Describe the bug
When exporting a SIA405 from a DB with value list extensions, the value_de is matched directly from the primary key instead of the vsacode. This results in unexpected behaviour.
In the test case, the value 'Platzwasser' was inserted into the vl of channel_usage_current to conform with AG-96 ili here.

The vl addition was done using plain sql:

INSERT INTO qgep_vl.channel_usage_current (code,vsacode,value_de,value_en,active) VALUES (999993,4520,'Platzwasser','square_water',true) ON CONFLICT DO NOTHING;

In the export, the result is
[...]<Nutzungsart_Ist>Platzwasser</Nutzungsart_Ist>[...] instead of [...]<Nutzungsart_Ist>Regenabwasser</Nutzungsart_Ist>[...]

To Reproduce
Exact steps to reproduce the behavior:

  1. Add vl addition accordizbg to description
  2. Add a channel with usage_current='Platzwasser'
  3. Export Interlis
  4. Check output

Expected behavior
qgepqwat2ili should map the vl indirectly by accessing the vsacode (if distinct from code) and get the corresponding value_de

Screenshots / data
DB dump can be sent privately (live data), to be used for bug fixing only

Desktop (please complete the following information):

  • QGEP plugin version: 1.6.1
  • QGEP datamodel version: 1.6.0
  • QGEP project file version
  • QGIS Version: 3.28.5
  • OS: Windows

Additional context
See vsacode handling in #208

@sjib
Copy link
Contributor

sjib commented Apr 23, 2024

Solved with QGEP/datamodel#220

@sjib sjib closed this as completed Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants