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

[BUG] TABEL: Aantal schadegevallen per type schade: numbers of columns of arguments do not match #487

Open
SanderDevisscher opened this issue Sep 19, 2024 · 2 comments
Assignees

Comments

@SanderDevisscher
Copy link
Collaborator

Describe the bug
When looking at the TABEL: Aantal schadegevallen per type schade with Data bron == "E-loket (ANB)" I get a message displaying numbers of columns of arguments do not match.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'faunabeheer.inbo.be' or 'faunabeheer-dev.inbo.be'
  2. Click on 'wildschade'
  3. Select Wild zwijn with all types of schade
  4. Scroll down to 'TABEL: Aantal schadegevallen per type schade'
  5. See error
  6. Set 'Data bron != "E-loket (ANB)"' the error disappears
  7. Set 'Data bron == "E-loket (ANB)"' the error reappears

Expected behavior
Graph is displayed also when Data bron == "E-loket (ANB)"

Screenshots
image

image

Additional context
No similar errors exists with other graphs that allows setting data bron

Git SHA (after 0.3.1)
d6d14c6037ed6b3462988acbc0e282f4b8f0ae0f

@lcougnaud
Copy link
Collaborator

lcougnaud commented Nov 11, 2024

There is a (maybe) related issue: the current function assumes that the schade code are unique across schade basis code.
However, the 'WLSCHD' code seems to be available in the basis code: 'Andere' and 'Gewas', e.g. for 'Wild Zwijn':

         locatie schadeCode schadeBasisCode freq
1        Limburg     WLSCHD          ANDERE   18
2        Limburg     WLSCHD           GEWAS 1707
3 Vlaams Brabant     WLSCHD          ANDERE    4
4 Vlaams Brabant     WLSCHD           GEWAS  172

Is this expected? If so, the function should be updated to handle this scenario.

@SanderDevisscher
Copy link
Collaborator Author

This indeed is not expected ! W'll fix this in the backoffice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants