terracotta
terracotta copied to clipboard
DHI
Mutli-dataset Selection in Terracotta connect
In the Terracotta Preview App, terracotta connect, you can click and select individual datasets in the table search results. Would it be possible to add ctrl+click and shift+click support in order to view multiple datasets at the same time?
That is certainly possible and would be a nice feature. It should also only require a change to the preview app itself. Each dataset would just be another leaflet layer.
As @mrpgraae mentions, this is not a fundamental issue at all. However, this would require quite substantial changes to the preview app:
- Contrast sliders would have to be remodeled (or should the same contrast apply to all layers?)
- Mechanism to move layers up / down the stack?
- RGB and singleband not mutually exclusive anymore?
- Keep layers active across searches
I think in this case we would like a list of active layers that can be manipulated by the user (drag new layers in, press to toggle, remove, reorder).
Since my Javascript fu is limited, we will have to rely on volunteers for this one (inside DHI GRAS or from the outside).
Contrast sliders would have to be remodeled (or should the same contrast apply to all layers?)
Maybe as a first go it would be alright to have the same contrast applied to all layers. If you want to compare values from different layers, this is probably what you want anyways.
Mechanism to move layers up / down the stack?
and
Keep layers active across searches
Would be nice, but maybe not strictly necessary for a first implementation.
RGB and singleband not mutually exclusive anymore?
This is worse. Any ideas on what to do here would be appreciated.
@mrpgraae your suggestions would fit my use case! I have a simple dataset: non-overlapping layers, same datatype across layer, single band. Keeping the layers active across searches would be nice, but not critical for an initial implementation.
@dionhaefner My javascript fu is also limited, but I will take a look and see if I can get something working.
Sounds good @mccarthyryanc! I suffer from the same JS limitations as @dionhaefner, but I'll gladly help and give advice if needed.