Specification of multipolygon element

[prushforth]

1. The table contains CamelCase element names, which it shouldn't.
2. The multipolygon content model says that it contains "Two or more <coordinates> elements" , but it should say "Two or more <polygon> elements"

Yes, this is inconsistent with the content models for multilinestring and multipoint. This was done to minimize markup, and adhere to GeoJSON content model to the extent possible in markup.

Opinions welcome in replies, but I think this is a bikeshed not worth painting.

[prushforth]

I believe this relates to the issue raised by OGC Testbed 15, requesting that MapML eliminate (redundant) <multipoint><coordinates>.

[jerstlouis]

A single "polygon" within a "multipolygon" should probably also be considered valid.
Same for a single "coordinates" within a "multilinestring".

[prushforth]

A single "polygon" within a "multipolygon" should probably also be considered valid.
Same for a single "coordinates" within a "multilinestring".

Agreed.

[prushforth]

Fixed by 513cc32