In response to GetMap, GetFeatureInfo with the `format_options=mapmlfeatures:true` parameter, add ability to recursively 'de-layer' a layergroup into a text/mapml document composed of its composite layers as features and tiles about geoserver HOT 3 OPEN

When mixing rasters and vectors in the same output, we need a TiledCRS to locate where the tiles are.
If we don't have a TiledCRS, then we need to skip the imagery layer. If we have a TiledCRS and the request is not tiled anyways, we'll have to generate enough map-tiles references to cover the entire area.

from geoserver.

It's going to be quite likely to have a mapmlfeatures and mapmlusefeatures be used by mistake in each other place.
How about a mapmlbody option with two possible values: layers and flat instead?

from geoserver.

How about a mapmlbody option with two possible values: layers and flat instead?

mapmlfeatures already exists, so I was / am hesitant about changing anything in how it works. Are you suggesting that mapmlbody would have the same meaning as mapmlusefeatures, OR would it replace both mapmlusefeatures and mapmlfeatures , or something else? I'm unsure how that would work, need to think about it more. Currently, mapmlfeatures only appears in templated URLs generated in the tref attribute. mapmlusefeatures is a flag controlling the 'inner node' document. If mapmlbody does something related to mapmlusefeatures, I will have to re-write the table in the first details over here

from geoserver.