When a WFS response is being serialized as MapML, when the output CRS is geodetic, it should be tagged in the MapML file as belonging to the "MapML:" CRS 'authority', because axis order in MapML is always x,y (horizontal, vertical), which should not lead to errors on the part of users, hopefully because it is not pretending to be lat,long.
Although https://osgeo-org.atlassian.net/browse/GEOS-9965#icft=GEOS-9965 Add support for MapML CRS authority in GetFeature responses was intended to address this originally, a bug was found after merging, for which tests had been commented out / not yet completed.
When a WFS response is being serialized as MapML, when the output CRS is geodetic, it should be tagged in the MapML file as belonging to the "MapML:" CRS 'authority', because axis order in MapML is always x,y (horizontal, vertical), which should not lead to errors on the part of users, hopefully because it is not pretending to be lat,long.
Although https://osgeo-org.atlassian.net/browse/GEOS-9965#icft=GEOS-9965 Add support for MapML CRS authority in GetFeature responses was intended to address this originally, a bug was found after merging, for which tests had been commented out / not yet completed.
This issue addresses the bug and tests required.