-
Notifications
You must be signed in to change notification settings - Fork 174
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
we need a better UI #27
Comments
right now the default UI fetch the dataset metadata (info + stats) when openning a new dataset. This helps when we are dealing with non-byte data (rescaling the value from min/max found in the stats)
I think we should make FYI: I've implemented some of this in developmentseed/rio-viz#38 Edit: ☝️ was done in 473c37d |
Hey @vincentsarago. This issue is pretty old, but I'd be interested in taking it on. Do you have any other ideas on how you'd like to improve the UI, or has most of the work for this been done already? Also, I'm not sure I fully understand how the UI here interfaces with rio-viz - should it be all one codebase (in titiler.local like this issue says), or should development be done in |
titiler and rio-viz are two different project but they share a lot (well now rio-viz depends on titiler.core 😅) titiler.extensions's viewers are really close to the one in rio-viz and I usually experiment first in rio-viz before changing the UI in titiler. About my last comment, I already made the change in titiler's viewer (we now only fetch the That's said, the viewers are pretty old and written in Note: Designing a frontend for titiler client is going to be quite complex so if we really want to do this I should also check internally if some of our designers want to help (👋 @LanesGood @ricardoduplos) but I feel you have a great knowledge of titiler already so I'm eager to ear what you have in mind 😃 |
Perhaps this would be better suited in Discussions, rather than Issues? I'll draft up a few possibilities that might work - there are lots of options ranging from small UI tweaks to large overhauls. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
No description provided.
The text was updated successfully, but these errors were encountered: