We removed the loss maps output in favor of the aggregate loss curves output in engine-3.11 (see https://github.com/gem/oq-engine/pull/6395
). The old loss maps output was simply an extract from the asset loss curves output, picking out the points from the asset loss curves corresponding to the return period of interest. In principle, it was not possible to obtain the loss corresponding to a given return period for an administrative division, for instance, by simply summing up the corresponding losses from all assets within that division listed in the loss maps output. Thus, the old loss maps output had limitations in its applicability.
Instead, now, by including the parameter aggregate_by = tag1, tag2, .. in your job file (eg., where tag1 could be province and tag2 could be occupancy), the engine will compute aggregate loss curves for each tag combination. We believe the aggregate loss curves output should cover most (if not all) of the use cases of the old loss maps output. We'd be curious to hear from you if there's a case that you think is not covered by the aggregate loss curves output.