• Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • V4.01_CS02
    • Affects Version/s: V4.01_CS01
    • Component/s: ABNF
    • Hide

      GeoJSON only supports Three-Dimension with a third coordinate representing an altitude or elevation.

      GeoJSON notation in principle allows the two "Measured" variants, but RFC7946 strongly discourages its use.

      To not be overly restrictive we should extend the ABNF for Geo types and also allow two optional coordinates:

      positionLiteral = doubleValue SP doubleValue [ SP doubleValue ] [ SP doubleValue ] ; longitude, latitude, altitude/elevation (optional), linear referencing measure (optional)
      
      Show
      GeoJSON only supports Three-Dimension with a third coordinate representing an altitude or elevation. GeoJSON notation in principle allows the two "Measured" variants, but RFC7946 strongly discourages its use. To not be overly restrictive we should extend the ABNF for Geo types and also allow two optional coordinates: positionLiteral = doubleValue SP doubleValue [ SP doubleValue ] [ SP doubleValue ] ; longitude, latitude, altitude/elevation (optional), linear referencing measure (optional)
    • Show
      https://github.com/oasis-tcs/odata-abnf/pull/16  

      Geo literals in WKT (well-known text) representation as defined by the OpenGIS Simple Feature Access http://www.opengeospatial.org/standards/sfa require two dimensions (longitute, latitude) and allow two optional dimensions

      • Three-Dimension (x,y, z)
      • Two-Dimension Measured (x, y, m) with m being a linear referencing measure
      • Three-Dimension Measured (x, y, z, m)

            Assignee:
            Unassigned
            Reporter:
            handl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: