Geospatial nodes development priorities

I’m finally exploring the new geospatial nodes, with a mixture of excitement and caution.

It’s very exciting to finally have some serious geospatial capability in KNIME, but it’s also apparent that these new nodes are still developing, and in many ways are not production-ready.

Many suggestions for improvement have already been discussed in other threads. My personal wishlist is:

  1. Integration with KNIME’s file handling framework
  2. The ability to write visual outputs as images (unless I’m missing something, the visualisation nodes have no outputs at all)
  3. The ability to select features in a visualisation and have them filter other visualisation elements, or at least save a ‘row selected’ flag akin to the Table Editor.
  4. The ability to input new data, such as by placing pins or drawing a polygon.

Until the file handling framework is upgraded, it’s hard to see how these nodes can be deployed in a productionised environment. Similarly, if all of the visualisation outputs are purely interactive, with no graphical or selection output, there is only so much we can do with these nodes. (I’m not even sure yet if the outputs are supposed to work in the WebPortal, as I have not succeeded in achieving this yet.)

I gather that these limitations stem from the underlying python integration framework, which I understand is also in its infancy. But it would be really good to have some idea of what improvements we can expect to see over the coming releases. Has a roadmap of this kind been made available, or could it be?

Hello @AngusVeitch ,
thanks a lot for the feedback and good suggestions. Your improvements are pretty high on our list :slight_smile:
The only exception is the last one which we haven’t thought about so far. But I have created a ticket for it. Most of the node related issues are listed in the Geospatial Github repository. Framework related tickets are also tracked in the KNIME internal ticket system and might not appear in Github.
Regarding a roadmap, in Github we use Milestones to plan the next releases. Milestones have a rough date assigned to give you an idea when to expect the releases. However the dates and content might change as long as they haven’t been finished. Feel free to add comments or issues to the repository.
Bye
Tobias

1 Like

Thanks for pointing me to the GitHub page, @tobias.koetter - that’s very helpful! And for creating the tickets. I’ll watch with interest as the features develop.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.