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 (
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
A detailed changelog is available here
Winning! Many thanks for the update.
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:
Hi @qqilihq , at the moment, the Service field can’t accept any String variable, either from Variable Creator or String Configuration node. Here’s what I got when attempting to do so:
The values I tried were:
that’s because we do not use the “human readable” text for the services, but a technical identifier. To figure out the identifier I suggest as follows:
Configure the node to output the value of
service as flow variable (that’s what the input field beside the drop down is used for, just enter sth. like
Open the output table and switch to the “Flow Variables” tab
Copy the value which is shown for
service (e.g. for Twitter this will be
You can then use this input for your variable.
Hope this helps!
Hi @qqilihq , it seems that even if I attempted to manually click on Twitter option in the dropdown menu, I still can’t get access via flow variables. Here’s how I set it up in a dummy component:
Here are the notifications:
- When leaving the fields empty:
- When writing a dummy data:
I think the issue is that the variables didn’t override the fields, whether the fields are empty or not.
Just to show that my tokens are correct, here’s the successful attempt without any variables:
Mhhhhhh, let me have another look at this. For simplicity would you mind attaching your workflow as shown above (just for the structure - please strip out your personal key, secret)
Sure, here’s the simple workflow as shown above:
KNIME_project2.knwf (11.3 KB)
Ahhh, now the coin has fallen (as ze Germans say).
This will indeed need some fixing in the code - currently it’s just not possible to do this via flow variables, sorry. I’ll try to have a look at it once there’s some spare time. Thanks!
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.
Related to this unsolved thread .
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.
This post was flagged by the community and is temporarily hidden.
That makes sense; probably in the form of an output port which provides an image? Let me see if this can be done. Thanks for the suggestions
I have found this component to solve my Excel Reader browse issue, so I can integrate the reader into my component, instead of keeping it outside. Only the OAuth Node is the odd one out at the moment
Hi @badger101 ,
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).
Any feedback or clarification welcome
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.
I’m just hoping there’ll be an update someday for the Palladian’s Map Viewer’s image output port as mentioned earlier
I’m sure there will be good news with an upcoming update. (not the 2.8 which we pushed today and about which I hadn’t even time yet to write about … well, tomorrow then).
+++++++ Palladian Nodes 2.7 is available +++++++
Here’s a brief overview of the new functionality:
- Geohash nodes to convert coordinate parts to geohashes and back:
- An improved ML model for the Location Extractor node
The full changelog is available here: Palladian — NodePit (and did you actually know that you can also subscribe to all changelogs on NodePit via RSS? Here’s the link: Changelog: All Products)