Apply Active Floor Filter to All Buildings

[ChristopherJStrong]

Currently, when using floor-aware data/maps, you filter by selecting a facility then a level.  That filter only applies to the selected facility, and not the other visible facilities nearby.

There is no way to indicate this mismatch of levels (unless you identify another building unit/feature), and this is very confusing to those expecting to see a consistent level across multiple facilities (certainly it is not intuitive to expect one structure at one level and the rest at the default ground level).

I suggest applying the chosen level filter to all facilities in the dataset, or alternatively,   so as to minimize confusion (this is an existing Idea).

It would also be great to choose a level filter without needing to specify a specific facility (this is great for users who are trying to view multiple facilities at the same time).

Here's another somewhat related idea

[MollyEhrenberger]

This would be an awesome feature.

My projects have some campuses with multiple buildings all attached to each other, so it is confusing for public users. A lot of the time they don't even realize they are in a different "building."
We tried messing around with alt level IDs but still couldn't get anything very intuitive to work. 

The "intuitiveness" of switching floors has been a common critique for us.

[LarisaKruger]

The ability to have all buildings filter by the same floor is critical for us to be able to roll this out for wayfinding for our students and patients. This is particularly important in the med center where many buildings are "attached" and the user doesn't even realize they have entered another building. I built a simple  filter in our web app builders that already does this and wanted to explore moving to indoors so we could utilize the simpler floor slider widget, but this makes it an absolute no-go for us. In addition, our users frequently do not even know the building names and the extra time it takes for them to find or think of the facility name is also a no-go.  Please explain why this was the chosen method?  What were the benefits to this over filtering across all facilities?  It feels like it required a lot more complexity in terms of table attribution as well.  We'll continue to just use the filter widget which still does the same thing for many layer.

[MollyE]

We have a similar issue with our organization as well. We ended up making a separate "ALT" levels and facilities layers which works well enough for us but isn't perfect. So rather than having a level IDs such as HLC_1000.LV1, HLC_1000.LV2, HLC_2000.LV1, HLC_2000.LV2, HLC_3000.LV1, etc.. we have HLC_ALL.LV1, HLC_ALL.LV2, etc..  It ends up being just more layers we need to manage because depending on the map purpose, we may need one over the other.

I agree it would be a very helpful feature to not need to choose a facility before choosing a level, or just be able to change the level across all facilities even if one has been chosen.