Skip to content

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

Closed
vincentsarago opened this issue Jun 4, 2020 · 4 comments
Closed

we need a better UI #27

vincentsarago opened this issue Jun 4, 2020 · 4 comments

Comments

@vincentsarago
Copy link
Member

No description provided.

@vincentsarago
Copy link
Member Author

vincentsarago commented Jun 29, 2021

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)

fetch(`${metadata_endpoint}?url=${scope.url}&max_size=256`)

I think we should make metadata fetching optional (and thus making the histogram optional too)

FYI: I've implemented some of this in developmentseed/rio-viz#38

Edit: ☝️ was done in 473c37d

@dchirst
Copy link
Contributor

dchirst commented Mar 31, 2023

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 rio-viz instead?

@vincentsarago
Copy link
Member Author

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 info for the dataset and then the user can fetch the statistics)

That's said, the viewers are pretty old and written in pure javascript/css. I'm sure we can do better!!! I'm not a frontend designer/developper so I prefer let other do this task 😂

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 😃

@dchirst
Copy link
Contributor

dchirst commented Mar 31, 2023

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.

@developmentseed developmentseed locked and limited conversation to collaborators Apr 4, 2023
@vincentsarago vincentsarago converted this issue into discussion #622 Apr 4, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants