# Filtering specific data

**URL:** <https://forum.knime.com/t/filtering-specific-data/16488>\
**Category:** KNIME Analytics Platform\
**Created:** [July 4, 2019, 2:53pm UTC](https://forum.knime.com/t/filtering-specific-data/16488 "2019-07-04T14:53:16Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Leviheichou](https://forum-cdn.knime.com/letter_avatar_proxy/v4/letter/l/aca169/32.png) [@Leviheichou](https://forum.knime.com/u/Leviheichou)\
**Post date:** [July 4, 2019, 2:53pm UTC](https://forum.knime.com/t/filtering-specific-data/16488/1 "2019-07-04T14:53:16Z")

</div>

Good afternoon everyone, comparing between 2 data (league index and total hours)

How do you categorise and filter a specific value? E.g i want to take out any number of league index that has spent a total of 800 hours and ABOVE, while letting people know that what the numbers are in league index that spent over 800 hours and above.(see photo for example)

 ![knime%20forum](https://forum-cdn.knime.com/uploads/default/original/2X/f/fca2a6cc3fdb3264a41f57ad6e184eb584ed332e.jpeg)

---

<div class="post-metadata">

**Author:** ![armingrudd](https://forum-cdn.knime.com/user_avatar/forum.knime.com/armingrudd/32/84633_2.png) [@armingrudd](https://forum.knime.com/u/armingrudd)\
**Post date:** [July 4, 2019, 3:06pm UTC](https://forum.knime.com/t/filtering-specific-data/16488/2 "2019-07-04T15:06:57Z")

</div>

Hi and welcome the community @Leviheichou,

If by total you mean sum of all the “TotalHours” values for each “LeagueIndex” value, then you have to use a [GroupBy](https://nodepit.com/node/org.knime.base.node.preproc.groupby.GroupByNodeFactory) node and group the rows based on “LeageueIndex” and use “Sum” aggregation on “TotalHours”. After that use a [Rule Engine](https://nodepit.com/node/org.knime.base.node.rules.engine.RuleEngineNodeFactory) node to label the records which exceeds 800 in sum of TotalHours.

But if by total you mean the current value in TotalHour column, then just use a Rule Engine node and label the rows with the value equal or higher than 800.

The expression for Rule Engine would be:

```auto
$TotalHours" >= 800 => "Over 800"
TRUE => "Below 800"

```

You can also use a Row Filter to exclude the rows based on this label if you want.

😊

---

<div class="post-metadata">

**Author:** ![Leviheichou](https://forum-cdn.knime.com/letter_avatar_proxy/v4/letter/l/aca169/32.png) [@Leviheichou](https://forum.knime.com/u/Leviheichou)\
**Post date:** [July 4, 2019, 3:15pm UTC](https://forum.knime.com/t/filtering-specific-data/16488/3 "2019-07-04T15:15:29Z")

</div>

Thank you so much for the prompt reply! I have tried it out and it worked. However, Is there a node i can visually display each “league index” comparing whether are they above 800 hours or below 800 hours?

Also , i have 3341 rows , but it’s only displaying 500. Issit adjustable in the settings?

---

<div class="post-metadata">

**Author:** ![armingrudd](https://forum-cdn.knime.com/user_avatar/forum.knime.com/armingrudd/32/84633_2.png) [@armingrudd](https://forum.knime.com/u/armingrudd)\
**Post date:** [July 4, 2019, 3:21pm UTC](https://forum.knime.com/t/filtering-specific-data/16488/4 "2019-07-04T15:21:18Z")

</div>

What exactly do you mean by “visually display each …”

Can you provide an example of what you want?

😊

---

<div class="post-metadata">

**Author:** ![Leviheichou](https://forum-cdn.knime.com/letter_avatar_proxy/v4/letter/l/aca169/32.png) [@Leviheichou](https://forum.knime.com/u/Leviheichou)\
**Post date:** [July 4, 2019, 3:22pm UTC](https://forum.knime.com/t/filtering-specific-data/16488/5 "2019-07-04T15:22:51Z")

</div>

Through a histogram would be good!

---

<div class="post-metadata">

**Author:** ![armingrudd](https://forum-cdn.knime.com/user_avatar/forum.knime.com/armingrudd/32/84633_2.png) [@armingrudd](https://forum.knime.com/u/armingrudd)\
**Post date:** [July 4, 2019, 3:25pm UTC](https://forum.knime.com/t/filtering-specific-data/16488/6 "2019-07-04T15:25:14Z")

</div>

So you mean you first want to group the indexes, right?

---

<div class="post-metadata">

**Author:** ![Leviheichou](https://forum-cdn.knime.com/letter_avatar_proxy/v4/letter/l/aca169/32.png) [@Leviheichou](https://forum.knime.com/u/Leviheichou)\
**Post date:** [July 4, 2019, 3:26pm UTC](https://forum.knime.com/t/filtering-specific-data/16488/7 "2019-07-04T15:26:44Z")

</div>

Yes!

---

<div class="post-metadata">

**Author:** ![armingrudd](https://forum-cdn.knime.com/user_avatar/forum.knime.com/armingrudd/32/84633_2.png) [@armingrudd](https://forum.knime.com/u/armingrudd)\
**Post date:** [July 4, 2019, 4:03pm UTC](https://forum.knime.com/t/filtering-specific-data/16488/8 "2019-07-04T16:03:18Z")

</div>

[bar-chart-over-800.knwf](https://forum-cdn.knime.com/uploads/default/original/2X/4/4bedea8fe05f0fadd5fce6ec52d19883fc9de224.knwf) (6.4 KB)

I hope this is what you want.

😊

---

<div class="post-metadata">

**Author:** ![Leviheichou](https://forum-cdn.knime.com/letter_avatar_proxy/v4/letter/l/aca169/32.png) [@Leviheichou](https://forum.knime.com/u/Leviheichou)\
**Post date:** [July 4, 2019, 4:07pm UTC](https://forum.knime.com/t/filtering-specific-data/16488/9 "2019-07-04T16:07:26Z")

</div>

Yes,kinda! But where do i import the data from excel ? Unlike file reader / CSV writer, the table creator has no options to import

---

<div class="post-metadata">

**Author:** ![armingrudd](https://forum-cdn.knime.com/user_avatar/forum.knime.com/armingrudd/32/84633_2.png) [@armingrudd](https://forum.knime.com/u/armingrudd)\
**Post date:** [July 4, 2019, 4:21pm UTC](https://forum.knime.com/t/filtering-specific-data/16488/10 "2019-07-04T16:21:00Z")

</div>

Replace the Table Creator in my workflow with one the readers.

😊

---

<div class="post-metadata">

**Author:** ![system](https://forum-cdn.knime.com/uploads/default/original/1X/ab3ccf34482a0329361734a18199390177204f15.png) [@system](https://forum.knime.com/u/system)\
**Post date:** [January 3, 2020, 4:21am UTC](https://forum.knime.com/t/filtering-specific-data/16488/11 "2020-01-03T04:21:03Z")

</div>

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