Fix various typos found by 'make spelling'

alg/gdalproximity.cpp

@@ -103,7 +103,7 @@ the proximity output.
 
   FIXED_BUF_VAL=n
 
-If this option is set, all pixels within the MAXDIST threadhold are
+If this option is set, all pixels within the MAXDIST threshold are
 set to this fixed value instead of to a proximity distance.
 */
 

alg/gdaltransformer.cpp

@@ -1765,13 +1765,13 @@ static void GDALGCPAntimeridianUnwrap(int nGCPCount, GDAL_GCP *pasGCPList,
  * a PROJ or WKT string, used as an override over the normally computed
  * pipeline. The pipeline must take into account the axis order of the source
  * and target SRS. <li> COORDINATE_EPOCH: (GDAL &gt;= 3.0) Coordinate epoch,
- * expressed as a decimal year. Useful for time-dependant coordinate operations.
+ * expressed as a decimal year. Useful for time-dependent coordinate operations.
  * </li>
  * <li> SRC_COORDINATE_EPOCH: (GDAL &gt;= 3.4) Coordinate epoch of source CRS,
- * expressed as a decimal year. Useful for time-dependant coordinate operations.
+ * expressed as a decimal year. Useful for time-dependent coordinate operations.
  * </li>
  * <li> DST_COORDINATE_EPOCH: (GDAL &gt;= 3.4) Coordinate epoch of target CRS,
- * expressed as a decimal year. Useful for time-dependant coordinate operations.
+ * expressed as a decimal year. Useful for time-dependent coordinate operations.
  * </li>
  * <li> GCPS_OK: If false, GCPs will not be used, default is TRUE.
  * </li>
@@ -3366,11 +3366,11 @@ void *GDALCreateReprojectionTransformer(const char *pszSrcWKT,
  * <li>COORDINATE_OPERATION=string: PROJ or WKT string representing a
  * coordinate operation, overriding the default computed transformation.</li>
  * <li>COORDINATE_EPOCH=decimal_year: Coordinate epoch, expressed as a
- * decimal year. Useful for time-dependant coordinate operations.</li>
+ * decimal year. Useful for time-dependent coordinate operations.</li>
  * <li> SRC_COORDINATE_EPOCH: (GDAL &gt;= 3.4) Coordinate epoch of source CRS,
- * expressed as a decimal year. Useful for time-dependant coordinate
+ * expressed as a decimal year. Useful for time-dependent coordinate
  *operations.</li> <li> DST_COORDINATE_EPOCH: (GDAL &gt;= 3.4) Coordinate epoch
- *of target CRS, expressed as a decimal year. Useful for time-dependant
+ *of target CRS, expressed as a decimal year. Useful for time-dependent
  *coordinate operations.</li>
  * </ul>
  *

alg/gdalwarper.cpp

@@ -1221,7 +1221,7 @@ CPLErr GDALWarpDstAlphaMasker(void *pMaskFuncArg, int nBandCount,
  * is sufficient.  Depending on the transformation in effect, the source
  * window may be a bit too small, or even missing large areas.  Problem
  * situations are those where the transformation is very non-linear or
- * "inside out".  Examples are transforming from WGS84 to Polar Steregraphic
+ * "inside out".  Examples are transforming from WGS84 to Polar Stereographic
  * for areas around the pole, or transformations where some of the image is
  * untransformable.  The following options provide some additional control
  * to deal with errors in computing the source window:

doc/source/development/rfc/rfc19_safememalloc.rst

@@ -26,7 +26,7 @@ scanlines, whole image buffers, etc.. Currently no overflow checking is
 done, thus leading to potential allocation of not large enough buffers.
 Overflow can occur when raster dimensions are very large (this can be
 the case with a WMS raster source for example) or when a dataset is
-corrupted, intentionnaly or unintentionnaly. This can lead to latter
+corrupted, intentionally or unintentionally. This can lead to latter
 crash.
 
 This RFC introduces new API to allocate memory when the computation of

doc/source/development/rfc/rfc39_ogr_layer_algebra.rst

@@ -19,7 +19,7 @@ for commonly needed overlay analysis methods.
 The basic functionality for spatial analysis with GDAL is provided by
 GEOS. However, GEOS operates on geometries and typically people work
 with geospatial data layers. Vector data layers are represented in GDAL
-by OGRLayer objects. Thus, there is a need for spatial analaysis
+by OGRLayer objects. Thus, there is a need for spatial analysis
 operations that work on layers.
 
 Unfortunately there is no standard for spatial analysis operations API,

doc/source/development/rfc/rfc41_multiple_geometry_fields.rst

@@ -122,7 +122,7 @@ The OGRFeatureDefn class will be extended as the following :
            virtual void        AddGeomFieldDefn( OGRGeomFieldDefn * );
            virtual OGRErr      DeleteGeomFieldDefn( int iGeomField );
 
-           // Route OGRwkbGeometryType GetGeomType() and void SetGeomType() 
+           // Route OGRwkbGeometryType GetGeomType() and void SetGeomType()
            // on the first geometry field definition.
 
            // Same for IsGeometryIgnored() and SetGeometryIgnored()
@@ -179,7 +179,7 @@ The OGRFeature class will be extended as following :
            OGRErr              SetGeomFieldDirectly( int iField, OGRGeometry * );
            OGRErr              SetGeomField( int iField, OGRGeometry * );
 
-           // Route SetGeometryDirectly(), SetGeometry(), GetGeometryRef(), 
+           // Route SetGeometryDirectly(), SetGeometry(), GetGeometryRef(),
            // StealGeometry() on the first geometry field in the array
 
            // Modify implementation of SetFrom() to replicate all geometries
@@ -343,7 +343,7 @@ different in most use cases.
 
 (On the other side, if we introduce 64bit integer as a OGR type (this is
 an RFC that is waiting for implementation...), the above code would
-still produce a meaningful result. The string reprentation of a 64bit
+still produce a meaningful result. The string representation of a 64bit
 integer is not that bad as a default behavior.)
 
 GetFieldCount() would also take into account geometry fields, but in

doc/source/development/rfc/rfc46_gdal_ogr_unification.rst

@@ -264,7 +264,7 @@ Drivers and driver registration
      driver level because, in practice, layer creation options do not depend on the
      dataset instance.
      The value of this item is an XML snippet with a format similar to dataset creation
-     options. 
+     options.
      If specified, the passed creation options to CreateLayer() are validated
      against that authorized creation option list.
      Below an example of such an authorized open option list in the Shapefile driver.
@@ -305,17 +305,17 @@ Datasets / Datasources
 
        virtual int         TestCapability( const char * ) { return FALSE; }
 
-       virtual OGRLayer   *CreateLayer( const char *pszName, 
+       virtual OGRLayer   *CreateLayer( const char *pszName,
                                         OGRSpatialReference *poSpatialRef = NULL,
                                         OGRwkbGeometryType eGType = wkbUnknown,
                                         char ** papszOptions = NULL );
-       virtual OGRLayer   *CopyLayer( OGRLayer *poSrcLayer, 
-                                      const char *pszNewName, 
+       virtual OGRLayer   *CopyLayer( OGRLayer *poSrcLayer,
+                                      const char *pszNewName,
                                       char **papszOptions = NULL );
 
        virtual OGRStyleTable *GetStyleTable();
        virtual void        SetStyleTableDirectly( OGRStyleTable *poStyleTable );
-                               
+
        virtual void        SetStyleTable(OGRStyleTable *poStyleTable);
 
        virtual OGRLayer *  ExecuteSQL( const char *pszStatement,
@@ -337,7 +337,7 @@ Datasets / Datasources
    OGRLayerH CPL_DLL GDALDatasetGetLayer( GDALDatasetH, int );
    OGRLayerH CPL_DLL GDALDatasetGetLayerByName( GDALDatasetH, const char * );
    OGRErr    CPL_DLL GDALDatasetDeleteLayer( GDALDatasetH, int );
-   OGRLayerH CPL_DLL GDALDatasetCreateLayer( GDALDatasetH, const char *, 
+   OGRLayerH CPL_DLL GDALDatasetCreateLayer( GDALDatasetH, const char *,
                                          OGRSpatialReferenceH, OGRwkbGeometryType,
                                          char ** );
    OGRLayerH CPL_DLL GDALDatasetCopyLayer( GDALDatasetH, OGRLayerH, const char *,
@@ -383,7 +383,7 @@ Datasets / Datasources
 
 ::
 
-       virtual OGRLayer   *ICreateLayer( const char *pszName, 
+       virtual OGRLayer   *ICreateLayer( const char *pszName,
                                         OGRSpatialReference *poSpatialRef = NULL,
                                         OGRwkbGeometryType eGType = wkbUnknown,
                                         char ** papszOptions = NULL );
@@ -397,7 +397,7 @@ Datasets / Datasources
    creation option list (GDAL_DS_LAYER_CREATIONOPTIONLIST), before calling
    ICreateLayer() (this is similar to RasterIO() / IRasterIO() )
    A global pass on all in-tree OGR drivers has been made to rename CreateLayer()
-   as ICreateLayer(). 
+   as ICreateLayer().
 
 -  GDALOpenEx() is added to be able to open raster-only, vector-only, or
    raster-vector datasets. It accepts read-only/update mode,
@@ -533,7 +533,7 @@ Changes in drivers
    a file to determine if they recognize it. They have been converted to
    GDALDriver to accept a GDALOpenInfo argument and they now use its
    pabyHeader field to examine the first bytes of files. The number of
-   system calls realated to file access (open/stat), in order to
+   system calls related to file access (open/stat), in order to
    determine that a file is not recognized by any OGR driver, has now
    dropped from 46 in GDAL 1.11 to 1. The converted drivers are :
    AeronavFAA, ArcGEN, AVCBin, AVCE00, BNA, CSV, DGN, EDIGEO, ESRI

doc/source/development/rfc/rfc47_dataset_caching.rst

@@ -70,7 +70,7 @@ periods once the cache is full, and new memory is being initialized in
 GDALRasterBlock::Internalize().
 
 In order to remove the need for this LRU cache to be locked more often a
-new global config option is introducted "GDAL_DATASET_CACHING". This
+new global config option is added "GDAL_DATASET_CACHING". This
 causes the LRU cache to be per dataset when set to "YES", rather then a
 global cache ("NO" Default). Doing this will also allow threaded
 applications to flush only the cache for a single dataset, improving

doc/source/development/rfc/rfc52_strict_sql_quoting.rst

@@ -73,7 +73,7 @@ This change affects compatibility in the sense that users that relied on
 the current permissive behavior will have to adapt their SQL
 expressions. This might be quite tricky to detect as it will not always
 cause obvious runtime failures. For example " SELECT
-'i_thought_this_would_be_interpreted_as_a_column_name_but_now_it_is_a_string_litteral'
+'i_thought_this_would_be_interpreted_as_a_column_name_but_now_it_is_a_string_literal'
 FROM atable " will run without error but not produce the previously
 expected result. So applications will have to review how they build SQL
 filters ( SetAttributeFilter() ) and expressions ( ExecuteSQL() )

doc/source/development/rfc/rfc54_dataset_transactions.rst

@@ -96,7 +96,7 @@ MySQL
    other reading) because of the use of mysql_use_result() that can work
    with one single request at a time. mysql_store_result() would be a
    solution but requires ingesting the whole result set into memory,
-   which is inpractical for big layers.
+   which is impractical for big layers.
 -  step does not set row changes once the query has started (if done
    through another connection, because if done through ExecuteSQL() the
    long transaction is interrupted)
@@ -134,36 +134,36 @@ OGRDataSource which inherits from GDALDataset).
    /**
     \brief For datasources which support transactions, StartTransaction creates a transaction.
 
-    If starting the transaction fails, will return 
-    OGRERR_FAILURE. Datasources which do not support transactions will 
+    If starting the transaction fails, will return
+    OGRERR_FAILURE. Datasources which do not support transactions will
     always return OGRERR_UNSUPPORTED_OPERATION.
 
     Nested transactions are not supported.
-    
+
     All changes done after the start of the transaction are definitely applied in the
     datasource if CommitTransaction() is called. They may be canceled by calling
     RollbackTransaction() instead.
-    
+
     At the time of writing, transactions only apply on vector layers.
-    
+
     Datasets that support transactions will advertise the ODsCTransactions capability.
     Use of transactions at dataset level is generally preferred to transactions at
     layer level, whose scope is rarely limited to the layer from which it was started.
-    
+
     In case StartTransaction() fails, neither CommitTransaction() or RollbackTransaction()
     should be called.
-    
+
     If an error occurs after a successful StartTransaction(), the whole
     transaction may or may not be implicitly canceled, depending on drivers. (e.g.
     the PG driver will cancel it, SQLite/GPKG not). In any case, in the event of an
     error, an explicit call to RollbackTransaction() should be done to keep things balanced.
-    
+
     By default, when bForce is set to FALSE, only "efficient" transactions will be
     attempted. Some drivers may offer an emulation of transactions, but sometimes
     with significant overhead, in which case the user must explicitly allow for such
     an emulation by setting bForce to TRUE. Drivers that offer emulated transactions
     should advertise the ODsCEmulatedTransactions capability (and not ODsCTransactions).
-    
+
     This function is the same as the C function GDALDatasetStartTransaction().
 
     @param bForce can be set to TRUE if an emulation, possibly slow, of a transaction
@@ -182,10 +182,10 @@ OGRDataSource which inherits from GDALDataset).
    /**
     \brief For datasources which support transactions, CommitTransaction commits a transaction.
 
-    If no transaction is active, or the commit fails, will return 
-    OGRERR_FAILURE. Datasources which do not support transactions will 
-    always return OGRERR_UNSUPPORTED_OPERATION. 
-    
+    If no transaction is active, or the commit fails, will return
+    OGRERR_FAILURE. Datasources which do not support transactions will
+    always return OGRERR_UNSUPPORTED_OPERATION.
+
     Depending on drivers, this may or may not abort layer sequential readings that
     are active.
 
@@ -202,11 +202,11 @@ OGRDataSource which inherits from GDALDataset).
 
    /**
     \brief For datasources which support transactions, RollbackTransaction will roll
-    back a datasource to its state before the start of the current transaction. 
+    back a datasource to its state before the start of the current transaction.
 
-    If no transaction is active, or the rollback fails, will return  
+    If no transaction is active, or the rollback fails, will return
     OGRERR_FAILURE. Datasources which do not support transactions will
-    always return OGRERR_UNSUPPORTED_OPERATION. 
+    always return OGRERR_UNSUPPORTED_OPERATION.
 
     This function is the same as the C function GDALDatasetRollbackTransaction().
 
@@ -244,7 +244,7 @@ whose data is supported by files/directories.
 ::
 
    /** Returns a new datasource object that adds transactional behavior to an existing datasource.
-    * 
+    *
     * The provided poTransactionBehaviour object should implement driver-specific
     * behavior for transactions.
     *

doc/source/development/rfc/rfc59.1_utilities_as_a_library.rst

@@ -395,13 +395,13 @@ keywords. So various combinations are possible :
 ::
 
 
-   def WarpOptions(options = [], format = 'GTiff', 
+   def WarpOptions(options = [], format = 'GTiff',
             outputBounds = None,
             outputBoundsSRS = None,
             xRes = None, yRes = None, targetAlignedPixels = False,
             width = 0, height = 0,
             srcSRS = None, dstSRS = None,
-            srcAlpha = False, dstAlpha = False, 
+            srcAlpha = False, dstAlpha = False,
             warpOptions = None, errorThreshold = None,
             warpMemoryLimit = None, creationOptions = None, outputType = GDT_Unknown,
             workingType = GDT_Unknown, resampleAlg = None,
@@ -467,7 +467,7 @@ keywords. So various combinations are possible :
 ::
 
 
-   def VectorTranslateOptions(options = [], format = 'ESRI Shapefile', 
+   def VectorTranslateOptions(options = [], format = 'ESRI Shapefile',
             accessMode = None,
             srcSRS = None, dstSRS = None, reproject = True,
             SQLStatement = None, SQLDialect = None, where = None, selectFields = None, spatFilter = None,
@@ -553,7 +553,7 @@ keywords. So various combinations are possible :
 
 ::
 
-   def NearblackOptions(options = [], format = 'GTiff', 
+   def NearblackOptions(options = [], format = 'GTiff',
             creationOptions = None, white = False, colors = None,
             maxNonBlack = None, nearDist = None, setAlpha = False, setMask = False,
             callback = None, callback_data = None):
@@ -564,7 +564,7 @@ keywords. So various combinations are possible :
              creationOptions --- list of creation options
              white --- whether to search for nearly white (255) pixels instead of nearly black pixels.
              colors --- list of colors  to search for, e.g. ((0,0,0),(255,255,255)). The pixels that are considered as the collar are set to 0
-             maxNonBlack --- number of non-black (or other searched colors specified with white / colors) pixels that can be encountered before the giving up search inwards. Defaults to 2. 
+             maxNonBlack --- number of non-black (or other searched colors specified with white / colors) pixels that can be encountered before the giving up search inwards. Defaults to 2.
              nearDist --- select how far from black, white or custom colors the pixel values can be and still considered near black, white or custom color.  Defaults to 15.
              setAlpha --- adds an alpha band if the output file.
              setMask --- adds a mask band to the output file.
@@ -635,7 +635,7 @@ keywords. So various combinations are possible :
 
 ::
 
-   def RasterizeOptions(options = [], format = None, 
+   def RasterizeOptions(options = [], format = None,
             creationOptions = None, noData = None, initValues = None,
             outputBounds = None, outputSRS = None,
             width = None, height = None,
@@ -660,8 +660,8 @@ keywords. So various combinations are possible :
              bands --- list of output bands to burn values into
              inverse --- whether to invert rasterization, ie burn the fixed burn value, or the burn value associated  with the first feature into all parts of the image not inside the provided a polygon.
              allTouched -- whether to enable the ALL_TOUCHED rasterization option so that all pixels touched by lines or polygons will be updated, not just those on the line render path, or whose center point is within the polygon.
-             burnValues -- list of fixed values to burn into each band for all objects. Excusive with attribute.
-             attribute --- identifies an attribute field on the features to be used for a burn-in value. The value will be burned into all output bands. Excusive with burnValues.
+             burnValues -- list of fixed values to burn into each band for all objects. Exclusive with attribute.
+             attribute --- identifies an attribute field on the features to be used for a burn-in value. The value will be burned into all output bands. Exclusive with burnValues.
              useZ --- whether to indicate that a burn value should be extracted from the "Z" values of the feature. These values are added to the burn value given by burnValues or attribute if provided. As of now, only points and lines are drawn in 3D.
              layers --- list of layers from the datasource that will be used for input features.
              SQLStatement --- SQL statement to apply to the source dataset

doc/source/development/rfc/rfc5_unicode.rst

@@ -32,7 +32,7 @@ means we should convert user's input from the local encoding to UTF-8
 during interactive sessions. The opposite should be done for GDAL
 output. For example, when user passes a filename as a command-line
 parameter to GDAL utilities, that filename should be immediately
-converted to UTF-8 and only afetrwards passed to functions like
+converted to UTF-8 and only afterwards passed to functions like
 GDALOpen() or OGROpen(). All functions, which take character strings as
 parameters, assume UTF-8 (with except of several ones, which will do the
 conversion between different encodings, see Implementation). The same is