since the topic was solved, I’d assume @gab1one 's post was the solution - is your “Image Reader (Table) Remote” Node already from the OMERO integration from the nightly community update site from KNIME Image Processing | KNIME? Other than that I’m not aware of any news or updates, but will ask around and come back to you if I have news.
my experience with OMERO/Glencoe software products is that they are under constant development. That means the OMERO specific KNIME nodes tend to target specific versions of OMERO only. That seems to be the problem here, if I’m not mistaken…
Well, you could aim for the OMERO Python language bindings. They are much more stable and support reading and writing of all kinds of image metadata and even pixel data from images themselves. You can have a look at the raw data access section in particular.
Depending on your specific OMERO server installation, you might also want to look into directly querying the tile server for image tiles. Have a look at the OMERO Pixel Data Microservice which supports direct queries for image tiles. The URL-encoded queries have the following form:
Also, for completeness sake, I want to mention the JSON API as well. You can fetch some image metadata using this endpoints, although authentication is a bit tricky but well documented too. Here is an example from Glencoe how authentication against the JSON API can be done using a Python script.
With KNIMEs native support for Python scripts you could integrate OMERO into your KNIME workflows like this. The solution would be much less dependent on the specific OMERO version in use.
Thanks @karbon_kreature for the workaround. Was it implemented into a single node? If so I would also be interested
In fact it would be convenient to revive such an Omero Reader node being independent from the Omero server version.
Best,
m