You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also, as discussed with @dleadbetter, we would like to make it possible to populate the layer picker per-place. So the search mode would have the layers available which are configured per-deploy; in place mode, the place itself will provide the layers to be loaded into the picker, as an array of links to compatible map layers.
Let's discuss tomorrow (Thu, 1/18)!
The text was updated successfully, but these errors were encountered:
I have some basic layer switching functionality implemented. It's been tricky though, because vector maps just work in such a different way. (More about this in our meeting today.) I'll still have to refine this a bit today. But after that, we should have the basics in place.
FWIW: the original wireframes had "place-specific layers" in the site details sidebar. I believe this might be preferable over dynamically swapping the contents of the main layer switcher. But let's chat about it later today.
Hey @rsimon! the GCA client has requested that we use this basemap, which we may as well do even though we're only in prototype mode: https://cloud.maptiler.com/maps/dataviz/
Also, as discussed with @dleadbetter, we would like to make it possible to populate the layer picker per-place. So the search mode would have the layers available which are configured per-deploy; in place mode, the place itself will provide the layers to be loaded into the picker, as an array of links to compatible map layers.
Let's discuss tomorrow (Thu, 1/18)!
The text was updated successfully, but these errors were encountered: