[OASIS Issue Tracker] (ODATA-1250) GeoJSON, SRID, and LineString

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

Ralf Handl created ODATA-1250:
---------------------------------

             Summary: GeoJSON, SRID, and LineString
                 Key: ODATA-1250
                 URL: https://issues.oasis-open.org/browse/ODATA-1250
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: JSON Format
    Affects Versions: V4.01_CS01
            Reporter: Ralf Handl
             Fix For: V4.01_CS02


Two issues with the JSON Format specification and GeoJSON:

1) The JSON Format specification states
{quote}Geography and geometry values are represented as geometry types as defined inÂ*[[RFC7946|https://tools.ietf.org/html/rfc7946]]*, with the following modifications:
 * Keys SHOULD be ordered with type first, then coordinates, then any other keys
 * TheÂcoordinatesÂmember of aÂLineStringÂcan have zero or more positions
 * If the optional CRS object is present, it MUST be of typeÂname, where the value of theÂnameÂmember of the containedÂpropertiesÂobject is an EPSG SRID legacy identifier.{quote}

The CRS object is not defined in RFC7946, it was defined in the now obsolete predecessor [GeoJSON-2008|http://geojson.org/geojson-spec.html], and RFC7946 has explicitly removed the concept of "coordinate reference systems" (CRS) and restricts GeoJSON to World Geodetic System 1984 (WGS 84), which (fortunately) is the default for the SRID facet in OData (EPSG 4326).
Â
2) RFC7946 and GeoJSON-2008 require a LineString to have at least two positions: why do we additionally allow zero or one position? And what does that mean?



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)