Krzysztof Findeisen added a comment - 31/May/22 4:58 PM - edited I had a conversation about this with Jim Bosch this morning. The most important points: ExposureInfo development is stalled pending other priorities, but it is a priority. In particular, Jim Bosch believes that we cannot stick to the current persistence format (FITS tables, as implemented by afw.table.io ) in operations – we need something the community can read without using the Stack. He is contemplating a large project to replace our use of table.io with something else (with DM-26746 as a precursor), and would like my help for at least the early stages. GenericMap is not specifically a priority. In particular, it has no built-in persistence support or assumptions, so it would be left untouched by the persistence rewrite described above. Jim Bosch floated the idea of using GenericMap as a C++ intermediate representation for YAML, but I think that would make things harder compared to an off-the-shelf YAML library. On the other hand, we are not planning to replace ExposureInfo wholesale, so any work that makes GenericMap work better in ExposureInfo won't be wasted. Some newer tasks are using alternatives to Exposure , but existing code will continue using it indefinitely.