Boundary layer would be an interesting part to see visualized.

You could make it premium, label it experimental and stash it in some weird container where it can live even if it was buggy or otherwise non perfect, and subject to change or removal later on.

Then it'd be a matter of defining a scale and creating & serving tiles for a specific parameter of a model right? You could also add more parameters for experimentation without perhaps committing to them fully. Might even generate the tiles runtime, even if that was slower, just to make it easier to experiment with parameters and see what would finally make it's way to the actual list of layers

I know the official reason for not being able to choose a default layer is cache fragmentation. And the secondary reason is that "this is windy and not radary etc" which likely is more of a joke, but anyway 😛

I'd suggest adding a setting "remember last open layer"

Think of it this way, if a lot of people from a certain geographical area are looking at radar (or any other layer) instead of wind, the caches would actually adapt to that behavior and (could) make the experience better for all.

Label the setting as "experimental" and kill it if it causes trouble. Or make it available to premium users only.

Also, I would not mind if the app still preloaded wind layer data on background, or if the caches were configured or set up in a way that gave preference to the wind layer if you think this is needed to preserve decent initial load speeds for most users.

Two things to balance and I'm sure you've thought of these: initial load speed vs getting to what you want to see speed

@korina I see something like this was added. Thank you :)

Boundary layer would be an interesting part to see visualized.

You could make it premium, label it experimental and stash it in some weird container where it can live even if it was buggy or otherwise non perfect, and subject to change or removal later on.

Then it'd be a matter of defining a scale and creating & serving tiles for a specific parameter of a model right? You could also add more parameters for experimentation without perhaps committing to them fully. Might even generate the tiles runtime, even if that was slower, just to make it easier to experiment with parameters and see what would finally make it's way to the actual list of layers

@korina I see something like this was added. Thank you :)

I know the official reason for not being able to choose a default layer is cache fragmentation. And the secondary reason is that "this is windy and not radary etc" which likely is more of a joke, but anyway 😛

I'd suggest adding a setting "remember last open layer"

Think of it this way, if a lot of people from a certain geographical area are looking at radar (or any other layer) instead of wind, the caches would actually adapt to that behavior and (could) make the experience better for all.

Label the setting as "experimental" and kill it if it causes trouble. Or make it available to premium users only.

Also, I would not mind if the app still preloaded wind layer data on background, or if the caches were configured or set up in a way that gave preference to the wind layer if you think this is needed to preserve decent initial load speeds for most users.

Two things to balance and I'm sure you've thought of these: initial load speed vs getting to what you want to see speed