should we filter boolean MVT attributes to the ones that matter?

[nilsnolde]

What would you like to share?

I already enjoy the popups for Valhalla dev a lot! but it is a bit overwhelming bcs there's so many attributes..

I wonder if we shouldn't filter the false ones which are expected to be false, e.g. toll, deadend etc. most of the booleans are important to understand when they're true, hardly any false is valuable information.

wdyt @chrstnbwnkl ?

[nilsnolde]

I'd also love to filter out live traffic if it's not available. app-side it seems a bit weird when properties depend on each other. we could ask /status?json={"verbose": true} when loading the app, the problem with that is that it'll return the huge bbox geojson too. I then thought I'd change Valhalla to always return the tile info and only hide the graph extent behind verbose, but loading a graph tile is still required and kinda defeats the purpose of a low-latency /status endpoint.

I gave it a shot in #329 too.