The filtering didn't work at 55:30 because there are two bridges listed with OVERALL_LENGTH set to 998001 metres. This seems to be the result of maths done on "no-data" values. Normally the histogram is drawn on filter interface, but it's squashed up into the first pixel on the left. If you filter the dataset itself you can locate these two spurious rows and amend them. The real longest OVERALL_LENGTH is 1850 metres, for the feeder bridges to the West Gate Freeway. But the West Gate Bridge itself is listed with an OVERALL_LENGTH of 0, although it's really 2.6 km long.
![Conquering PL-300: Power BI Data Analyst Certification 📈 [Full Course]](http://i.ytimg.com/vi/BDGzVpt1xCg/mqdefault.jpg)
The filtering didn't work at 55:30 because there are two bridges listed with OVERALL_LENGTH set to 998001 metres. This seems to be the result of maths done on "no-data" values. Normally the histogram is drawn on filter interface, but it's squashed up into the first pixel on the left.
If you filter the dataset itself you can locate these two spurious rows and amend them. The real longest OVERALL_LENGTH is 1850 metres, for the feeder bridges to the West Gate Freeway. But the West Gate Bridge itself is listed with an OVERALL_LENGTH of 0, although it's really 2.6 km long.