Provide backend route to "find data" #3524
Assignees
Labels
Comments
youri-k
pushed a commit
that referenced
this issue
Jan 24, 2019
youri-k
pushed a commit
that referenced
this issue
Jan 24, 2019
fm3
pushed a commit
that referenced
this issue
Feb 21, 2019
* Working inefficient solution to find data in dataset #3524 * make requesting more efficient #3524 * check if all data is zero to locate empty bucket * respond with null if no position was found #3682 * integrate find-my-data route into UI * directly check if positions contain data #3682 * [WIP] simplify backend code #3682 * revert to old working version with some improvements #3682 * improve find data service and fix frontend #3682 * fix import error #3682 * changelog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It can be quite frustrating to open a dataset but not being able to find the actual data. Often the bounding box is not set correctly. We could certainly improve the guessing of the bbox (i.e., inspect the data within the cubes and not only look which cubes exist). However, this won't automatically help with existing datasets. That's why I suggest a simple backend route to "find your data". If the front-end notices, that there's no data at the current position, we could show a toast which says "There does not seem to exist data at the current position. Do you want to jump to a position which contains data?".
The back-end could do some sort of 3D binary (? the center should probably be favored) search across all cubes to find a good position. To avoid reading multiple GB of data, a cube could be spot checked by only reading some center buckets. For these center buckets, the logic would be something like "is there at least one voxel in that bucket which is not black?".
The text was updated successfully, but these errors were encountered: