Changes between Version 3 and Version 4 of rfc65_rfc7946_geojson


Ignore:
Timestamp:
Oct 29, 2016, 2:23:23 PM (8 years ago)
Author:
Even Rouault
Comment:

Add a note about M

Legend:

Unmodified
Added
Removed
Modified

  • rfc65_rfc7946_geojson

    v3 v4  
    1717
    1818The RFC 7946 standard is backwards compatible with the legacy definition of GeoJSON, but has a few differences (see https://tools.ietf.org/html/rfc7946#appendix-B). For OGR, the most significant are: removal of "crs" (CRS84 only), counter-clockwise winding of polygons, geometry splitting at the antimeridian, and representation of bounding boxes at the antimeridian and poles.
     19Note: RFC 7946 explicitly restricts to 2D and 3D coordinates, and forbid use of the M dimension for example. This was already the case in the existing driver for the GeoJSON 2008 output.
    1920
    2021Consensus on the gdal-dev list is that developers should be able to require RFC 7946 GeoJSON by configuring layer creation with an option and that it be an all-or-nothing switch.