-
Notifications
You must be signed in to change notification settings - Fork 10
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
Supply your own 3D coordinates? #3
Comments
Thank you for checking out this project! The quick answer is no, the interface currently ships with 4 visualizations/layouts (random, map, timeline, timeline tracks). To your second question, it is possible (though I can't say "reasonable" for sure) to modify the codebase to support this. I'd look at three key files to start with:
There will likely need to be other files touched, but I think those are the ones to start with! And a quick note: the development phase (and funding) of this project has ended as of April 2021, so unfortunately we can't guarantee continued support or PR reviews, but I'd love to know if you were able to get it working! |
@beefoo thanks for this! I was thinking about writing my own data file(s) directly, according to the same format/convention of the other layout files. (Was thinking about looking at the sphere layout, and then matching my space into that.) Either way: thanks for this, I'll definitely try this out when our project advances that far. (We'll start in march and will first look into clustering & projection of the collection, and only into visualization later this year.) |
I just came across this project, and it looks absolutely fantastic!
Just a quick question I could not figure out from the Readme: is it possible to supply your own 3D coordinates in the CSV for each record? (We are about to start a project where we'll perform our own clustering based on various different criteria.)
Or, if not: is that something we could possibly (and reasonably...) modify ourselves (and - if there's interest - feed back as a PR)?
The text was updated successfully, but these errors were encountered: