Decluttering the map for turn restrictions

Nobody has claimed this yet.

The data density of detected restrictions is starting to get high enough that the experience of interaction has come down. Its hard to identify missing data on OSM and verify existing data with imagery.

https://mapbox.github.io/osm-navigation-map/?days=990#17.3/37.77535/-122.41879

How can we improve the UX of the tool? The filter interface on [Mapillary](https://www.mapillary.com/app/?pKey=goIIxneArjlThoohYIS5CA&focus=map&lat=37.7719173666423&lng=-122.42339031044307&z=18.167244141994548&x=0.43280891782540554&y=0.3201623823545017&zoom=1.2374396202245241&signs=true&trafficSign%5B%5D=regulatory--no-left-turn--g1&trafficSign%5B%5D=regulatory--no-right-turn--g1&trafficSign%5B%5D=regulatory--no-left-turn--g2&trafficSign%5B%5D=regulatory--no-right-turn--g2&trafficSign%5B%5D=regulatory--no-straight-through--g1&trafficSign%5B%5D=regulatory--no-u-turn--g3&trafficSign%5B%5D=regulatory--no-u-turn--g1) has gotten much better in the meantime that makes it easier to browse through the data, but still far from ideal.

What are low hanging fruits here?

cc @rasagy @kepta @batpad

Start by running the linked osm-navigation-map view and comparing the dense turn-restriction display with the Mapillary filter example. The issue does not name files, tests, or a specific change; done would require an agreed UX improvement that makes missing and existing restriction data easier to identify and verify.

Written by the indexing model from the issue text.