In some data models (i.e. LandCoverVector), elements with a multiplicity > 1 are used to nest child features within the main feature (in LandCoverVector Units are added by aggregation under the member element). This can be utilized to provide xlinks referencing these features instead of providing all the data inline (causes size issues, i.e. 180MB for 1 feature). Unfortunately, GeoServer App Schema only supports this type of multiplicity at a deeper level within the featureType.
In some data models (i.e. LandCoverVector), elements with a multiplicity > 1 are used to nest child features within the main feature (in LandCoverVector Units are added by aggregation under the member element). This can be utilized to provide xlinks referencing these features instead of providing all the data inline (causes size issues, i.e. 180MB for 1 feature). Unfortunately, GeoServer App Schema only supports this type of multiplicity at a deeper level within the featureType.
Workaround Use Deegree