SNT-327 data layers UI improvements - #394
Merged
Merged
Conversation
This wizard streamlines the process of creating standard, OpenHexa, and composite data layers, guiding the user through type selection, details, legend configuration, and data input. It integrates the composite layer editor as a dedicated step, and allows for client-side legend previews and various data entry methods (CSV, manual grid).
Bewi
changed the title
michiwend
requested changes
Sep 23, 2026
Member
There was a problem hiding this comment.
Works pretty nicely for me, well done! I have some general findings from the testing and code comments down below:
- Blocking: A user can go back to change the layer type but that keeps the already entered meta data. E. g. I had an OH layer which auto fills all fields, I go back, select standard layer and then I'll have still all the values from the OH auto fill.
- Blocking: When importing multi-year data, proceed to the legend which imports the data, then go back to the data and delete a year, proceed again to the legend and the year is still there
- UI knit: Default colour for legend items is always black, can we generate different ones automatically or go straight for the auto-legend approach? At least we should change the black to something else 🫠
- UI knit: The legend item inputs look a bit unaligned because they keep the space for the delete action. Maybe we can show it permanently so it looks a bit more aligned?
- UI knit: I wonder if we can find an alternative to those blue and green status boxes for imports. To me they look a bit "out of design sytem"
- We mix error messages: Snack bar and custom side panel boxes. Maybe we should use the snack bar consistently?
- The loading/status icon for OH import layers is a bit misplaced in the main view
michiwend
approved these changes
Sep 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What problem is this PR solving?
Change flow when creating layer
Related JIRA tickets
SNT-327
Changes
Moved creation of DataLayer to a side Panel.
First choost type of data layer.
Then fill in details.
Then Load data and preview in a table.
Finally preview on a map with a legend editor.
How to test
Go to DataLayers and play around with creating layers (try three options).
Print screen / video
Basic layer
OH Data Layer
Composite Layer
Notes
Related to IASO PR: BLSQ/iaso#3341
Doc
Tell us where the doc can be found (docs folder, wiki, in the code...).