Ticket #2254 (closed bug: duplicate)
Format.GML.v2 and v3 fail when there's no geometry but bounds. JS error.
|Reported by:||fvanderbiest||Owned by:||tschaub|
The case happens for instance with WFS getFeature when requesting attributes properties but no geometry, passing the propertyNames option to the WFST protocol's read method.
The error is caused by the GML format's base.js affecting bounds to feature.geometry, but feature.geometry is null. The proposed patch deals with that by affecting bounds to the feature instead of the inexistent geometry. I'm not sure crschmidt will agree with that ;-)
Tests are provided.