Changes between Version 1 and Version 2 of rfc65_rfc7946_geojson

Timestamp:

Sep 28, 2016, 1:42:41 AM (8 years ago)

Author:

sgillies

Comment:

layer creation, not global config, option

rfc65_rfc7946_geojson

@@ -18 +18 @@
 The 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.
 
-Consensus on the gdal-dev list is that developers should be able to require RFC 7946 GeoJSON by configuring GDAL with an option or environment variable and that it be an all-or-nothing switch.
+Consensus 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.
 
 == Changes ==
 
-A configuration option will be added for the GeoJSON driver, e.g., {{{OGR_GEOJSON_RFC7946=TRUE}}}. When "on", OGR will write GeoJSON with CRS84 coordinates (reprojecting as needed) with 7 places of precision by default, polygons wound properly, and geometries split at the antimeridian.
+A layer creation option will be added for the GeoJSON driver, e.g., {{{RFC7946=TRUE}}}. When "on", OGR will write GeoJSON with CRS84 coordinates (reprojecting as needed) with 7 places of precision by default, polygons wound properly, and geometries split at the antimeridian.
 
 === Updated drivers ===
@@ -34 +34 @@
 == Utilities ==
 
-Utilities will implement RFC 7946 by using the configuration option.
+Utilities will implement RFC 7946 by using the layer creation option.
 
 == Documentation ==