Generate Feature Bounds Interactions

Known Issues

The following table describes the result of a query when various paramters are turned on/off when the feature type being queried already contains an attribute named "boundedBy" which is a geometry type.

gml:boundedBy refers to the generated bounding box of type gml:Box
app:boundedBy refers to the attribute bounding box of type gml:GeometryPropertyType

parameters

CITE	Strict cite conformance / GML prefixing
BBOX	Generate Feature Bounds option
PROP	boundedBy attribute included in query
Result	returned boundedBy result, one of (none,gml:boundedBy,app:boundedBy,both)

CITE	BBOX	PROP	Result
off	off	no	none
off	off	yes	app:boundedBy
off	on	no	gml:boundedBy
off	on	yes	both (gml:boundedBy includes app:boundedBy
on	off	no	none
on	off	on	gml:boundedBy (includes app:boundedBy)
on	on	no	gml:boundedBy
on	on	yes	gml:boundedBy

Returning both gml:boundedBy and app:boundedBy is valid according to GML, since they are in different namespaces. app:boundedBy is treated as a geometry attribute of the feature, and its bounds is also calculated. Though perhaps a bit unintuitive it makes the most sense to return both given our current assumptions, since putting a boundedBy attribute in to serve as the gml: attribute is a hack, and should only happen for the cite conformance. Doing both does not break any GML.

If the query being made does not contain a geometry attribute/property then a null bounding box is generated in cases 3 and 7. Returning a null is what GML is supposed to do if there are no geometries.