Leapfrog View Export

We should find a way to export vtki scenes to Steno3D so that users can rapidly share interactive visualizations of their data over the web.

• https://github.com/seequent/steno3dpy

I think this would be really similar to the VTKjs export script I added in #57

Pinging @fwkoch: do you think we could collaborate on this? Would this be reasonable to “export” a scene to the Steno3D format and provide an API in vtki to send scenes directly to a users account?

[fwkoch]

Hey @lperozzi - I can’t speak to support within pyvista/omfvtk (i.e. vtki -> LFView or vtki -> omf - Bane needs to follow up on those). However, the case of omf -> LFView is supported by the View Python client:

pip install lfview-api-client

Get an API key (https://lfview.com/generate_api_key - you must already be logged in), then -

from lfview.client import convert, Session
session = Session('your-api-key')
view = convert.omf_to_view('your_file.omf')
session.upload(view)

Maybe that helps a little, at least for now? Let me know if you have any questions or issues.

[banesullivan]

Thanks for your swift feedback, @fwkoch!

I’d recommend moving over to LF View. This is a rebranded evolution of the same product. It is built on better technology and under active development

This looks like an awesome project - I’ll work towards building an export script for LF View instead!

it would be totally reasonable to export a scene from vtki … The omf/steno3d/lfview APIs all have fairly similar data structures, so I don’t see any major hurdles there. Especially since you’ve already worked through omf -> vtki conversion, this should mostly just be translating in the opposite direction.

From a few minutes of poking around the client library, it does indeed look similar to OMF - this should make my life a lot easier!

Actually, I notice that there is an OMF importer… this makes me wonder if I should focus on creating a way to go from vtki to omf over in https://github.com/OpenGeoVis/omfvtk and put the LF View exporter/uploader over there? I’m thinking OMF might be a bit more stable than lfview-resources-spatial and that most people using vtki+ LF View would be omfvtk users to begin.

I suppose my remaining question is - should I focus on building an exporter from vtki to lfview-resources-spatial or focus on building the link from vtki back to omf so that users can both upload data to LF View and save projects locally.