GeoJSON should serialize geometry.collection as GeometryCollection and vice-versa

[tschaub]

The GeoJSON spec describes GeometryCollection as a type of geometry, not a collection of geometries.

[tschaub]

parse GeometryCollection as geometry.collection

[crschmidt]

a rendered example, and another test

[crschmidt]

The patch looks good to me. I'm okay having this go into trunk. I don't want another RC just for this -- so the question then becomes if we can convince ourselves that we can put it in to the final release without another RC. I don't have a strong feeling against that, other than it being somewhat bad policy, especially since this is a rather invasive change.

I'd rather do a 2.5.1 to fix just GeoJSON after the spec is actually finished than try to chase it as part of a release. This could change again if the community fights against it.

[crschmidt]

(In [5435]) GeoJSON should parse and serialize GeometryCollections as a Geometry.Collection object. (Closes #1067)

[tschaub]

(In [5436]) non-functional change - just removing an extra comma from r5435 to appease IE (see #1067)

[tschaub]

Those extra two tests are broken. The format reads to an array of features by default. Clear cache before testing perhaps?

[tschaub]

(In [5437]) Fixed test for GeoJSON collections (closes #1067).