top/base information often lacking for zones

[tnatt]

There is no structuring or information to tell that an element is a zone or a horizon in the stratigraphy block in the global config.
Without this we can’t make pydantic logic to ensure all zones have a top and base defined.

The top and base goes into the metadata but it is optional (since it is not required for horizons) and hence becomes unreliable since many users don’t specify the top and base horizon for their zones.

We could potentially structure the stratigraphy different so that the keys are zones and each zone has a top/base horizon defined under it.

We could also look into splitting out the stratigraphy mapping in a separate block/file. And then when we do a look-up and convert the name and set stratigraphic=True for the user if it is present in this mapping.

current	potential change

This could be exported by RMS, and might be even more smooth once roxar supports accessing the stratigraphic column (RMS14.5)