Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Specification of multipolygon element #43

Closed
prushforth opened this issue Apr 3, 2019 · 4 comments
Closed

Specification of multipolygon element #43

prushforth opened this issue Apr 3, 2019 · 4 comments

Comments

@prushforth
Copy link
Member

prushforth commented Apr 3, 2019 •
edited

  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
Copy link
Member Author

prushforth commented Jun 28, 2019 •
edited

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

@jerstlouis
Copy link

jerstlouis commented Jun 30, 2019 •
edited

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

@prushforth
Copy link
Member Author

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

Agreed.

prushforth added a commit that referenced this issue Jul 2, 2019
@prushforth
Fix issues #43 and #44 with specification and schema for geometry names
513cc32 
and coordinates
@prushforth
Copy link
Member Author

Fixed by 513cc32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@prushforth @jerstlouis