Unexpected imported scalar boundary conditions from nek

[stgeke]

Each boundary ID (or tag) must be associated with a specific boundary type. When importing boundary conditions from Nek5000, boundary IDs are typically absent, except when the mesh is imported via one of the available mesh converters. In cases without boundary IDs, we use a heuristic approach to generate them by mapping each boundary type to an ID. While this approach is effective in most situations, it can occasionally result in wrong BCs in specific cases.

I cannot think of a good and robust fix for this.
Suggested workaround: define boundary IDs in nek and specify types in par

[fischer1]

THere is a simple work around that involves counting.
We should fix this to support Nek.