consider adding a datum to boundingAltitudes
bug added to split this issue from the another bug (#1019) which will be resolved. Possibly, boundingAltitudes should have a datum attached. Alternatively, this level of detail belongs in spatialReference, not geographicCoverage. Before this bug can be addressed, we need to determine who uses this element, and for what purpose.