-
Notifications
You must be signed in to change notification settings - Fork 131
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
Workflow to Support Lazy Loading of Dataset? #75
Comments
We have a branch working on a related feature: Add a new option that the dataset will not be loaded into front-end. In this case, the query task will be sent to a customized server to handle the computation and only return the view data (which is usually much smaller than the raw data). It can allow graphic-walker to handle much larger dataset than before. The feature is already in testing and will be published this week. |
Thanks for the reply. I will be waiting for the feature to try. |
Any update on that? |
@ObservedObserver Has the branch containing this feature been published? I'm very interested in this feature. |
I'm considering using the @kanaries/graphic-walker library for generic data visualisation, and I'm finding it extremely useful. However, I have a requirement where I need to handle large datasets efficiently. Currently, the library fetches the entire dataset upfront, which can be problematic when dealing with large amounts of data. I'm assuming that based on demos; please let me know if I'm wrong. We have a requirement to display spatial datasets which can go up to 50GB in size.
I wanted to inquire if it's possible to modify the workflow of the library to support the lazy loading of the dataset as a React Component. Here's the proposed workflow:
Please let me know if this is something that can be done using this library as an import without needing to customize the internals.
The text was updated successfully, but these errors were encountered: