when a M_CSCL feature is coincident with the boundary of the M_COVR of a cell, then when it is converted it can lead to self-intersecting DataCoverage features as in the diagram below (from a US cell). This came up in the S-101PT meeting as conversion can lead to a number of inconsistent geometries.
It would make sense, maybe, to encode coincident M_COVR with M_CSCL features in S-57 in order to ensure this does not happen. The root of the issue is the mapping of M_COVR->DataCoverage and M_CSCL->DataCoverage
when a M_CSCL feature is coincident with the boundary of the M_COVR of a cell, then when it is converted it can lead to self-intersecting DataCoverage features as in the diagram below (from a US cell). This came up in the S-101PT meeting as conversion can lead to a number of inconsistent geometries.
It would make sense, maybe, to encode coincident M_COVR with M_CSCL features in S-57 in order to ensure this does not happen. The root of the issue is the mapping of M_COVR->DataCoverage and M_CSCL->DataCoverage