Seeking clarification of naming for GeographyCollection with GeoJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • V4.0_ERRATA01
    • Affects Version/s: V4.0_OS
    • Component/s: JSON Format
    • None
    • Environment:

      [Applied]

    • Hide

      I propose we don't introduce new properties/annotations at this point; that a geographyCollection is represented as a geometryCollection with "geometries" as the property name. Whether it is to be interpreted as geography or geometry is based on metadata.

      Accepted: https://www.oasis-open.org/committees/download.php/52767/odata-meeting-70_on-20140403-minutes.html#odata-597

      Show
      I propose we don't introduce new properties/annotations at this point; that a geographyCollection is represented as a geometryCollection with "geometries" as the property name. Whether it is to be interpreted as geography or geometry is based on metadata. Accepted: https://www.oasis-open.org/committees/download.php/52767/odata-meeting-70_on-20140403-minutes.html#odata-597

      GeoJSON section 2.1.8 states:

      A GeoJSON object with type "GeometryCollection" is a geometry object which represents a collection of geometry objects.

      A geometry collection must have a member with the name "geometries". The value corresponding to "geometries" is an array. Each element in this array is a GeoJSON geometry object.

      Can we assume that for OData, a GeographyCollection contains a member with the name "geographies", as opposed to "geometries", and that the "type" will be "GeographyCollection" rather than "GeometryCollection"?

      Or do we assume that the "geometry" naming is used in the GeoJSON format, even for "geography" types?

            Assignee:
            Michael Pizzo (Inactive)
            Reporter:
            evan.ireland.2
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: