You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The sort order found in filter (a - filter list, b - drop down, c - metadata panel) is wrongly ordered by schema:identifier interpreted as xsd:string - while in LINDAS it has type xsd:integer. NB: Meanwhile the legend (preview & published) is fine 👍
See wrong sort order ("1":Zurich, "10":Fribourg, "11":Solothurn, ...)
Expected behavior
Identifier parsed according to the data in lindas as xsd:integer and thus ordered (1:Zurich, 2:Berne, 3:Lucerne ...)
xref: #937 (comment)
Environment (please complete the following information):
Visualize environment and version: [e.g. INT v3.19.5]
Additional information
required for the upcoming go live of forest fire warning.
The text was updated successfully, but these errors were encountered:
@Rdataflow Has this dataset changed ? I remember solving the integer interpretation bug, but now I cannot re-check since I cannot use a column chart due to the lack of number measure.
Describe the bug
The sort order found in filter (a - filter list, b - drop down, c - metadata panel) is wrongly ordered by schema:identifier interpreted as
xsd:string
- while in LINDAS it has typexsd:integer
. NB: Meanwhile the legend (preview & published) is fine 👍To Reproduce
a) Steps to reproduce the behavior:
edit filters
b) Steps to reproduce the behavior:
c) Steps to reproduce the behavior:
Expected behavior
Identifier parsed according to the data in lindas as
xsd:integer
and thus ordered (1:Zurich, 2:Berne, 3:Lucerne ...)xref: #937 (comment)
Environment (please complete the following information):
Additional information
required for the upcoming go live of forest fire warning.
The text was updated successfully, but these errors were encountered: