Changes between Version 3 and Version 4 of rfc70_output_format_guess

Timestamp:

Nov 15, 2017, 7:06:45 AM (6 years ago)

Author:

Even Rouault

Comment:

A few precisions

rfc70_output_format_guess

@@ -9 +9 @@
 == Summary ==
 
-This proposal is to add syntaxic sugar to make GDAL and OGR command line utilities, so they take into account the extension of the output filename to guess which output driver to use, when it is not explicitly specified. 
+This proposal is to add syntaxic sugar to make GDAL and OGR command line utilities, so they take into account the extension of the output filename to guess which output driver to use, when it is not explicitly specified with -f / -of switch.
 
 == Motivation ==
@@ -31 +31 @@
 Similarly, for vector output, if doing something like "ogr2ogr PG:dbname=mydb out.shp", a PG:dbname=mydb directory is created with shapefiles, instead of ingesting the shapefile into PostgreSQL. A warning is emitted in that case since the PG driver declares the PG: prefix in its metadata. The new behaviour will be to imply the -update switch in such situation.
 
+When the utilities are available as library functions (GDALTranslate(), etc.), output format guessing will also be applied if the -f/-of switch is not specified
 
 == Changes in SWIG bindings ==
@@ -48 +49 @@
 This will break scripts that use an output filename whose extension is matched by a driver which is not the default one. This incompatibility is rather unlikely since previous GDAL versions already emit a warning in this situation (for C/C++ utilities only. for Python utilities default driver is silently used), so people have likely specified the output driver if they really want to do "gdal_translate in.tif out.png -of GTiff".
 
+MIGRATION_GUIDE.TXT will mention those potential caveats.
+
 == Testing ==