Wow! We just published our 10th Just KNIME It! challenge this season! Time is really flying this year, huh?
This week, imagine that you work as a data analyst for a delivery company. Given a dataset with successful deliveries (due to no typos) and unsuccessful ones (due to typos), your goal is to automatically fix incorrect postal addresses by leveraging the correct ones.
Here is the challenge. Let’s use this thread to post our solutions to it, which should be uploaded to your public KNIME Hub spaces with tag JKISeason3-10.
Need help with tags? To add tag JKISeason3-10 to your workflow, go to the description panel in KNIME Analytics Platform, click the pencil to edit it, and you will see the option for adding tags right there. Let us know if you have any problems!
My solution to the 10th challenge. It’s a surprise even for me that I had the time to solve it this quick
This challenge was really enjoyable and required some thoughtful problem-solving and nodes that you do not use every day.
I’m excited to see how others approached it. Since this isn’t a visualization challenge, I’m sure the final solutions will showcase peak efficiency just as in the folder challenge!
Hello @ JKIers
Here is my take for the challenge using ‘KNIME Distance Matrix Extension’ nodes.
I also checked for typos in $full Address$ string key segments (street number, address text, postal district number); aiming to highlight that, a double typo may suggest to the delivery service company taking some audit actions.
In the results table, a typo warning in ‘street number’ could require only address text correction, as a wrong assigned street number can stand for an unhappy customer.
Yes, I agree with your point of view. Through everyone’s exploration, this string has a special structure, and the error occurred in the first paragraph of the address. Both methods can obtain the result.
Hello everyone,
My workflow is similar to others’, taking inspiration from their approaches. I highlighted the corrections, using @sryu 's ideas. Thanks.