[OASIS Issue Tracker] (ODATA-594) Discrepancy between ATOM and JSON formats (GML, GeoJson) for Polygon information content

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://tools.oasis-open.org/issues/browse/ODATA-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36979#comment-36979 ] 

Stefan Drees commented on ODATA-594:
------------------------------------

For type "Polygon", the "coordinates" member must be an array of LinearRing coordinate arrays. For Polygons with multiple rings, the first must be the exterior ring and any others must be interior rings or holes. (GeoJSON)

With holes:

  { "type": "Polygon",
    "coordinates": [
      [ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ],
      [ [100.2, 0.2], [100.8, 0.2], [100.8, 0.8], [100.2, 0.8], [100.2, 0.2] ]
      ]
   }

from sample in spec.

> Discrepancy between ATOM and JSON formats (GML, GeoJson) for Polygon information content
> ----------------------------------------------------------------------------------------
>
>                 Key: ODATA-594
>                 URL: https://tools.oasis-open.org/issues/browse/ODATA-594
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format
>    Affects Versions: V4.0_OS
>            Reporter: Evan Ireland
>             Fix For: V4.0_ERRATA01
>
>
> GML seems to require that Polygons specify (usually) an exterior ring, but also permits the specification or zero or more interior rings.
> GeoJSON only seems to allow a single set of points (see example in http://geojson.org/geojson-spec.html#id4)
> For OData, one would hope that there is some kind of notion of the information content of Polygon coordinates which is independent of the format (ATOM or JSON) that we use. (Even if this information content is not formally documented, we could imagine that it exists).
> Unfortunately, this mismatch in Polygon coordinates between GML and GeoJSON seems hard to fit into a single information model.



--
This message was sent by Atlassian JIRA
(v6.1.1#6155)