How can I save data-layer visibility settings between visits?

[jimerb]

Is there currently a supported way to save the visibility state of individual data layers?

For example, I don’t want commercial aircraft displayed, so I turn off the Commercial Flights layer. However, when I reopen Shadowbroker or return the next day, it is enabled again and I have to toggle it off manually.

There's a zillion layers causing information overload, and each day i have to tame them before things start to make sense.

Ideally it should look just like i left it the previous day or back to a default i set.

I’m hoping there is an existing setting, configuration option, or intended workflow that makes Shadowbroker remember these choices. I’m not looking to use a userscript or maintain a fork, just trying to find the normal way to preserve my layer preferences.

[Charlie284]

Short answer: there is no supported way to persist those layer choices in the current build.

The dashboard creates activeLayers from a hard-coded defaults object on every mount. A layer click only updates that React state. The subsequent POST /api/layers is not a saved profile: the endpoint only changes the backend's in-memory layer map, whose defaults are also defined in source. There is no corresponding read endpoint or browser-storage key for the full layer state.

Shadowbroker already persists some UI preferences, such as sidebar visibility, so this looks like a missing feature rather than an intentional workflow hidden elsewhere.

With the no-userscript/no-fork constraint, re-toggling is unfortunately the only normal option today. A native implementation should restore a validated, versioned layer-preference object from browser storage before the first /api/layers sync, merge it over current defaults so newly added layers still get sane defaults, and provide a “reset layers to defaults” action. That would preserve the exact per-browser layout without turning the backend's process-global state into a user-profile store.

[BigBodyCobain]

OK. Just got to it. It should work now if you update your docker container to pull the latest from the back and front end (follow instructions on main page.)

[BigBodyCobain]

Working on it

[jimerb]

wonderful!!!

[BigBodyCobain]

It should work if you update your docker container to pull the latest front and back end

[jimerb]

Thank you! Seems like it's sticking now!!