Unfortunately I cannot post this into the existing Ka-Boom thread, so we’re just starting a new one in order to keep up with the traditions!
There’s Palladian 2.5 on the update site with three new nodes:
Thanks to @wisemanleo we have improved the existing OAuth node to allow more signature methods (HMAC-SHA1, HMAC-SHA256, HMAC-SHA512, PLAINTEXT) and to allow settings additional headers. The new node replaces the previous one and is now called “OAuth 1 Signer”:
Beside that, there’s two new nodes in the “Geo” category for formatting and parsing DMS coordinates:
More Geo-related features will come soon. Stay tuned.
Palladian freely available for free KNIME versions and exclusively distributed through NodePit: Palladian — NodePit
Palladian for KNIME, version 2.6 is already available for a few days. So, high time to update this thread! There’s plenty of improvements, especially for the Geo/Location extraction nodes and the OAuth Connector node.
The old beta version of the OAuth Connector has been replaced by a new version with many fixes and detail improvements, based on the numerous of feedback we received from the community – thank you for that:
The Palladian Location Extractor received an internal overhaul, includes an improved extraction model, and allows different output modes:
We include two options for gazetteers/location databases now: GeoNames and a local one. These can be connected through the green input port:
Contact us for details if you’re interested in using the local location source.
For all changes have a look at the changelog here on NodePit:
At the moment I’ll leave it outside of my component then. Thanks for considering to take a look into the matter.
Meanwhile, if anyone knows how can I incorporate the Excel Reader into my component, that’ll be appreciated. I’m leaving the Excel Reader outside too, since I don’t know how to make a ‘Browse’ button as a configuration function. I don’t want to make a string configuration that asks the users to type in the directory of the file.
On another topic, @qqilihq , I hope one day you can develop an equivalent node of the OSM Map to Image for the Palladian Map Viewer, because I’m having the same issue mentioned here where I can’t integrate the image produced by Map Viewer into my component’s interactive view.
I had a quick stab at the “flow variable support”. While adding support to properly supply the values at configuration time (i.e. service, api key, secret, and scope), I’m not too sure if this will be sufficient for your scenario – at the end, the user will need to click the “Authorize Access” button to run through the flow, innit? Would this be possible when wrapping the OAuth node into a meta node at all? (I’m no expert in that field).
Hi @qqilihq , you’re right on that matter. Due to the Authorize button, the OAuth node still needs to be left outside. I guess it’s okay then I wish I could give some pointers from the technical side of things, but sadly I’m not a coder.
An option might be to start the authentication flow when executing the node, but I’m not sure I like this flow UX wise. I will see if we can come up with a better solution to that, but leaving the node outside of metanodes is my suggestion for now
Thank you @qqilihq , I have learned that I didn’t need the OAuth node if the users key in their access tokens manually. I was able to use Twitter’s V2 API via the Palladian HTTP Retriever as long as I provide all the necessary tokens including bearer.