Yes, you could extract the keys yourself.  I personally like having the 
keys ready to go, especially as iterating over the CoverageDescriptions 
is likely to be a very common action after doing a DescribeCoverage.

Taking them out would probably be fine (I've streamlined it a bit), but 
doing so would break the related GeoExt patches that I believe others 
are using.


On 2013-09-26 14:11, Bart van den Eijnden wrote:
>
> In lib/OpenLayers/Format/WCSDescribeCoverage/v1_1_0.js:
>
> > +     * Contains public functions, grouped by namespace prefix, that will
> > +     *     be applied when a namespaced node is found matching the function
> > +     *     name.  The function will be applied in the scope of this parser
> > +     *     with two arguments: the node being read and a context object passed
> > +     *     from the parent.
> > +     */
> > +    readers: {
> > +        "wcs": OpenLayers.Util.applyDefaults({
> > +            // Root object, contains one or more CoverageDecription entries
> > +            // In 1.0.0, this was CoverageDescription, in 1.1.0, it's
> > +            // CoverageDescriptions (plural)
> > +            "CoverageDescriptions": function(node, obj) {
> > +                obj.coverageDescriptions = {};
> > +                this.readChildNodes(node, obj.coverageDescriptions);
> > +
> > +                obj.coverageDescriptionKeys = [];
>
> So the structure that is created by the parser is an object with keys 
> (coverageDescriptions). Application code can easily extract the keys 
> from there, so I wonder why we need to do this in the parser 
> (coverageDescriptionKeys)?
>
> —
> Reply to this email directly or view it on GitHub 
> <https://github.com/openlayers/openlayers/pull/846/files#r6598187>.
>