Interplay with vscode remote development: no access to remote file system.

[heidekrueger]

Hi, I stumbled upon the extension randomly and absolutely love it, great work!

I've found the following limitation. I suspect that I may just be missing something or that it's a limitation of kepler itself and might not be fixable in the extension, but I wanted to let you know anyways.

I'm working on a remote server via vscode's remote development extension. The workspace contains a bunch of geojson data files. I vizualized one of them with geo-data-viewer and saved my configuration as a .kgl.json config file to the same (remote) workspace.

Now I would like to open a different geojson file with the same config, but I don't see a way to do this easily.

I can open the config file in geo-data-viewer (via the Geo: View Map command). However, the 'Add Data' GUI opens a local file browser, rather than allowing browsing of the (remote) vscode workspace files. Similarly, the drag-and-drop feature does not work with files from the workspace. Accessing these files via URL from the local client is also not possible.

Could it be possible, to e.g. add a Geo: Add Data command to the extension that would access the workspace data similar to the way Geo: View Map does ?

[hcoohb]

I would be interested in that too!

[RandomFractals]

We might add that in our new Geo Data Viewer Pro v. later this fall ...

See new Pro Data Tools docs repo for more info about our new Pro extensions for VS Code IDE in the works.

[RandomFractals]

@heidekrueger to answer your question, this geo data viewer doesn't support remote workspaces and files loaded from those workspaces. We'd need to extend current data and config file selection dialog to allow local and remote files selection in order to enable it, similar to how VS Code IDE does it for some file selections in GitHub CodeSpaces.

We'll keep this request open and will add this feature in the next Geo data viewer extension update. Most likely it will be a Pro v. feature and require monthly sponsorship to access and download that extension version.

It is a frequently requested feature and we had devs asking for similar functionality and support in our DuckDB SQL Tools and other extensions, as some projects require loading of large data files from remote workspaces. Thank you for bringing it up!

[heidekrueger]

Thanks for considering this! I agree that this would be a feature worth paying for.

[RandomFractals]

Great! We are wrapping up some updates to the new Pro Data Tools we started building this year centered around DuckDB, SQL Tools, SQL and markdown documents, and Jupyter notebooks in VS Code.

Those updates will be finalized and published this and next month. Currently working on adding broader support of integrated SQL Tools and drivers with new SQL code lenses for SQL code blocks in various markdown documents:

https://github.com/RandomFractals/pro-data-tools#markdown-sql-pro-tools

Later this year we plan to release new Data Notebook Pro Tools:

https://github.com/RandomFractals/pro-data-tools#data-notebook-pro-tools

We'll update Geo Data Viewer to use the latest version of keplergl per #141 and will create and publish new Pro version of this VS Code extension for our Pro sponsors on GithHub with support of remote workspaces and better data loading, map view and config restore options later this year.

Geo data viewer is one of our most popular VS Code extensions and has a large user base by now we'd like to support and provide new Premium features for those willing to pay for monthly updates and releases.

Thank you for trying it out and sticking with the current somewhat outdated keplergl version and other wrinkles in this extension!

Also, please review related open ticket for the local and remote workspaces support: https://github.com/RandomFractals/geo-data-viewer/issues/106