When a geographic bounding box cannot be established for a layer, MapServer currently emits an empty WGS84BoundingBox element and a warning comment:
|
} else { |
|
xmlNewChild(psRootNode, psNsOws, BAD_CAST "WGS84BoundingBox", NULL); |
|
xmlAddSibling(psNode, |
|
xmlNewComment(BAD_CAST "WARNING: Optional WGS84BoundingBox could not be established for this layer. Consider setting the EXTENT in the LAYER object, or wfs_extent metadata. Also check that your data exists in the DATA statement")); |
|
} |
The output looks like this:
<ows:WGS84BoundingBox/>
<!--WARNING: Optional WGS84BoundingBox could not be established for this layer. Consider setting the EXTENT in the LAYER object, or wfs_extent metadata. Also check that your data exists in the DATA statement-->
This empty element violates the OWS schema — when this element is present, it must have LowerCorner and UpperCorner children. The standard-compliant thing to do would be to omit the empty <WGS84BoundingBox/> and to just emit the XML comment.
This issue was discovered while troubleshooting a user-reported compatibility problem between ArcGIS Runtime and MapServer. This XML quirk caused parsing to fail for the entire capabilities document.
Reactions are currently unavailable
When a geographic bounding box cannot be established for a layer, MapServer currently emits an empty WGS84BoundingBox element and a warning comment:
MapServer/mapwfs11.cpp
Lines 261 to 265 in f035f44
The output looks like this:
This empty element violates the OWS schema — when this element is present, it must have LowerCorner and UpperCorner children. The standard-compliant thing to do would be to omit the empty <WGS84BoundingBox/> and to just emit the XML comment.
This issue was discovered while troubleshooting a user-reported compatibility problem between ArcGIS Runtime and MapServer. This XML quirk caused parsing to fail for the entire capabilities document.