Doc: remove links to Trac wiki (or point to web.archive.org)

doc/source/api/csharp/csharp_compile_legacy.rst

@@ -84,7 +84,7 @@ To test the compiled binaries, you can use:
 
     nmake /f makefile.vc test`
 
-This command will invoke some of the sample applications. 
+This command will invoke some of the sample applications.
 
 .. note:: For the tests to work the location of the proj and gdal DLLs should be available in the PATH.
 
@@ -93,7 +93,7 @@ Using MONO on Windows
 
 If you have the Windows version of the MONO package installed you can compile the C# code using the MONO compiler. In this case uncomment the following entry in csharp.opt:
 
-:program:`MONO = YES` 
+:program:`MONO = YES`
 
 .. note:: mcs.exe must be in the PATH.
 
@@ -165,7 +165,7 @@ To test the compiled binaries, you can use:
 
     nmake test
 
-This command will invoke some of the sample applications. 
+This command will invoke some of the sample applications.
 
 .. note:: For the tests to work the location of the proj and gdal libraries should be available in the PATH.
 
@@ -179,8 +179,4 @@ To run one of the prebuilt executables - you can run them with Mono as follows :
 :program:`mono GDALInfo.exe`
 
 Both the managed libraries (i.e. the DLLs) and the unmanaged libraries must be available to Mono.
-This is in more detail in `the Mono documentation <https://www.mono-project.com/docs/advanced/pinvoke/>`__ 
-
-.. note:: This document was amended from the previous version at `https://trac.osgeo.org/gdal/wiki/GdalOgrCsharpCompile <https://trac.osgeo.org/gdal/wiki/GdalOgrCsharpCompile>`__
-
-
+This is in more detail in `the Mono documentation <https://www.mono-project.com/docs/advanced/pinvoke/>`__

doc/source/api/csharp/csharp_raster.rst

@@ -15,40 +15,40 @@ The :file:`Band` class contains the following :file:`ReadRaster`/:file:`WriteRas
 
 .. code-block:: C#
 
-    public CPLErr ReadRaster(int xOff, int yOff, int xSize, int ySize, byte[] buffer, 
+    public CPLErr ReadRaster(int xOff, int yOff, int xSize, int ySize, byte[] buffer,
         int buf_xSize, int buf_ySize, int pixelSpace, int lineSpace){}
-        
-    public CPLErr WriteRaster(int xOff, int yOff, int xSize, int ySize, byte[] buffer, 
+
+    public CPLErr WriteRaster(int xOff, int yOff, int xSize, int ySize, byte[] buffer,
         int buf_xSize, int buf_ySize, int pixelSpace, int lineSpace){}
-        
-    public CPLErr ReadRaster(int xOff, int yOff, int xSize, int ySize, short[] buffer, 
+
+    public CPLErr ReadRaster(int xOff, int yOff, int xSize, int ySize, short[] buffer,
         int buf_xSize, int buf_ySize, int pixelSpace, int lineSpace){}
-        
-    public CPLErr WriteRaster(int xOff, int yOff, int xSize, int ySize, short[] buffer, 
+
+    public CPLErr WriteRaster(int xOff, int yOff, int xSize, int ySize, short[] buffer,
         int buf_xSize, int buf_ySize, int pixelSpace, int lineSpace){}
-        
-    public CPLErr ReadRaster(int xOff, int yOff, int xSize, int ySize, int[] buffer, 
+
+    public CPLErr ReadRaster(int xOff, int yOff, int xSize, int ySize, int[] buffer,
         int buf_xSize, int buf_ySize, int pixelSpace, int lineSpace){}
-        
-    public CPLErr WriteRaster(int xOff, int yOff, int xSize, int ySize, int[] buffer, 
+
+    public CPLErr WriteRaster(int xOff, int yOff, int xSize, int ySize, int[] buffer,
         int buf_xSize, int buf_ySize, int pixelSpace, int lineSpace){}
-        
-    public CPLErr ReadRaster(int xOff, int yOff, int xSize, int ySize, float[] buffer, 
+
+    public CPLErr ReadRaster(int xOff, int yOff, int xSize, int ySize, float[] buffer,
         int buf_xSize, int buf_ySize, int pixelSpace, int lineSpace){}
-        
-    public CPLErr WriteRaster(int xOff, int yOff, int xSize, int ySize, float[] buffer, 
+
+    public CPLErr WriteRaster(int xOff, int yOff, int xSize, int ySize, float[] buffer,
         int buf_xSize, int buf_ySize, int pixelSpace, int lineSpace){}
-        
-    public CPLErr ReadRaster(int xOff, int yOff, int xSize, int ySize, double[] buffer, 
+
+    public CPLErr ReadRaster(int xOff, int yOff, int xSize, int ySize, double[] buffer,
         int buf_xSize, int buf_ySize, int pixelSpace, int lineSpace){}
-        
-    public CPLErr WriteRaster(int xOff, int yOff, int xSize, int ySize, double[] buffer, 
+
+    public CPLErr WriteRaster(int xOff, int yOff, int xSize, int ySize, double[] buffer,
         int buf_xSize, int buf_ySize, int pixelSpace, int lineSpace){}
-        
+
     public CPLErr ReadRaster(int xOff, int yOff, int xSize, int ySize, IntPtr buffer, i
         nt buf_xSize, int buf_ySize, DataType buf_type, int pixelSpace, int lineSpace){}
-  
-    public CPLErr WriteRaster(int xOff, int yOff, int xSize, int ySize, IntPtr buffer, 
+
+    public CPLErr WriteRaster(int xOff, int yOff, int xSize, int ySize, IntPtr buffer,
         int buf_xSize, int buf_ySize, DataType buf_type, int pixelSpace, int lineSpace){}
 
 The only difference between these functions is the actual type of the buffer parameter.
@@ -76,7 +76,7 @@ When reading the image this way the C# API will copy the image data between the
     band.ReadRaster(0, 0, width, height, r, width, height, 0, 0);
     // Copying the pixels into the C# bitmap
     int i, j;
-    for (i = 0; i< width; i++) 
+    for (i = 0; i< width; i++)
     {
         for (j=0; j<height; j++)
         {
@@ -113,13 +113,13 @@ Raster data can be read into the C# bitmap directly using the following approach
     Bitmap bitmap = new Bitmap(width, height, PixelFormat.Format8bppIndexed);
     // Obtaining the bitmap buffer
     BitmapData bitmapData = bitmap.LockBits(new Rectangle(0, 0, width, height), ImageLockMode.ReadWrite, PixelFormat.Format8bppIndexed);
-    try 
+    try
     {
         int stride = bitmapData.Stride;
         IntPtr buf = bitmapData.Scan0;
         band.ReadRaster(0, 0, width, height, buf, width, height, DataType.GDT_Byte, 1, stride);
     }
-    finally 
+    finally
     {
         bitmap.UnlockBits(bitmapData);
     }
@@ -167,7 +167,7 @@ When reading images with indexed color representations, the programmer might hav
     Bitmap bitmap = new Bitmap(width, height, PixelFormat.Format8bppIndexed);
     // Obtaining the bitmap buffer
     BitmapData bitmapData = bitmap.LockBits(new Rectangle(0, 0, width, height), ImageLockMode.ReadWrite, PixelFormat.Format8bppIndexed);
-    try 
+    try
         {
             int iCol = ct.GetCount();
             ColorPalette pal = bitmap.Palette;
@@ -177,13 +177,13 @@ When reading images with indexed color representations, the programmer might hav
                 pal.Entries[i] = Color.FromArgb(ce.c4, ce.c1, ce.c2, ce.c3);
             }
             bitmap.Palette = pal;
-                
+
             int stride = bitmapData.Stride;
             IntPtr buf = bitmapData.Scan0;
 
             band.ReadRaster(0, 0, width, height, buf, width, height, DataType.GDT_Byte, 1, stride);
             }
-            finally 
+            finally
             {
                 bitmap.UnlockBits(bitmapData);
             }
@@ -199,19 +199,19 @@ When reading grayscale images, the programmer should create a sufficient palette
     Bitmap bitmap = new Bitmap(width, height, PixelFormat.Format8bppIndexed);
     // Obtaining the bitmap buffer
     BitmapData bitmapData = bitmap.LockBits(new Rectangle(0, 0, width, height), ImageLockMode.ReadWrite, PixelFormat.Format8bppIndexed);
-    try 
+    try
         {
-            ColorPalette pal = bitmap.Palette; 
-            for(int i = 0; i < 256; i++) 
-                pal.Entries[i] = Color.FromArgb( 255, i, i, i ); 
+            ColorPalette pal = bitmap.Palette;
+            for(int i = 0; i < 256; i++)
+                pal.Entries[i] = Color.FromArgb( 255, i, i, i );
             bitmap.Palette = pal;
-                
+
             int stride = bitmapData.Stride;
             IntPtr buf = bitmapData.Scan0;
 
             band.ReadRaster(0, 0, width, height, buf, width, height, DataType.GDT_Byte, 1, stride);
         }
-        finally 
+        finally
         {
             bitmap.UnlockBits(bitmapData);
         }
@@ -224,5 +224,3 @@ The following examples demonstrate the usage of the GDAL raster operations menti
 * :source_file:`swig/csharp/apps/GDALRead.cs`
 * :source_file:`swig/csharp/apps/GDALReadDirect.cs`
 * :source_file:`swig/csharp/apps/GDALReadDirect.cs`
-
-.. note:: This document was amended from the previous version at `https://trac.osgeo.org/gdal/wiki/GdalOgrCsharpRaster <https://trac.osgeo.org/gdal/wiki/GdalOgrCsharpRaster>`__

doc/source/api/index.rst

@@ -117,7 +117,6 @@ API
 
        Go <https://github.com/lukeroth/gdal>
        Julia <https://github.com/JuliaGeo/GDAL.jl>
-       Lua <https://trac.osgeo.org/gdal/wiki/GdalOgrInLua>
        Original Node.js bindings <https://github.com/naturalatlas/node-gdal>
        Node.js fork with full Promise-based async and TypeScript support <https://www.npmjs.com/package/gdal-async>
        Perl <https://metacpan.org/release/Geo-GDAL-FFI>
@@ -126,10 +125,6 @@ API
        Ruby <https://github.com/telus-agcg/ffi-gdal>
        Rust <https://github.com/georust/gdal>
 
-    .. warning::
-        For Perl, since GDAL 3.5 the link `Perl <https://trac.osgeo.org/gdal/wiki/GdalOgrInPerl>`__ is deprecated, use above link instead.
-
-
 
     There are also more Pythonic ways of using the vector/OGR functions with
 

doc/source/development/building_from_source.rst

@@ -2546,5 +2546,5 @@ crashes will occur at runtime (often at process termination with a
 Autoconf/nmake (GDAL versions < 3.5.0)
 --------------------------------------------------------------------------------
 
-See https://trac.osgeo.org/gdal/wiki/BuildHints for hints for GDAL < 3.5
+See http://web.archive.org/https://trac.osgeo.org/gdal/wiki/BuildHints for hints for GDAL < 3.5
 autoconf and nmake build systems.

doc/source/development/rfc/rfc48_geographical_networks_support.rst

@@ -19,7 +19,7 @@ project “GDAL/OGR Geography Network support” into GDAL library. GNM
 create, manage and analyse networks built over spatial data in GDAL.
 
 GSoC project description:
-`http://trac.osgeo.org/gdal/wiki/geography_network_support <http://trac.osgeo.org/gdal/wiki/geography_network_support>`__
+`http://web.archive.org/web/20240812232429/https://trac.osgeo.org/gdal/wiki/geography_network_support <http://web.archive.org/web/20240812232429/https://trac.osgeo.org/gdal/wiki/geography_network_support>`__
 
 GDAL fork with all changes in trunk:
 `https://github.com/MikhanGusev/gdal <https://github.com/MikhanGusev/gdal>`__

doc/source/drivers/raster/cog.rst

@@ -53,9 +53,7 @@ General creation options
       * ``JPEG`` should generally only be used with
         Byte data (8 bit per channel). But if GDAL is built with internal libtiff and
         libjpeg, it is    possible to read and write TIFF files with 12bit JPEG compressed TIFF
-        files (seen as UInt16 bands with NBITS=12). See the `"8 and 12 bit
-        JPEG in TIFF" <http://trac.osgeo.org/gdal/wiki/TIFF12BitJPEG>`__ wiki
-        page for more details.
+        files (seen as UInt16 bands with NBITS=12).
         For the COG driver, JPEG compression for 3 or 4-band images automatically
         selects the PHOTOMETRIC=YCBCR colorspace with a 4:2:2 subsampling of the Y,Cb,Cr
         components.
@@ -612,8 +610,6 @@ See Also
 --------
 
 - :ref:`raster.gtiff` driver
--  `How to generate and read cloud optimized GeoTIFF
-   files <https://trac.osgeo.org/gdal/wiki/CloudOptimizedGeoTIFF>`__ (before GDAL 3.1)
 - If your source dataset is an internally tiled geotiff with the desired georeferencing and compression,
   using `cogger <https://github.com/airbusgeo/cogger>`__ (possibly along with gdaladdo to create overviews) will
   be much faster than the COG driver.

doc/source/drivers/raster/ecw.rst

@@ -327,4 +327,3 @@ See Also
    `Hexagon Geospatial public
    forum <https://supportsi.hexagon.com/help/s/erdas-apollo>`__
 -  Community contributed `patches <https://github.com/rouault/libecwj2-3.3-builds/blob/main/libecwj2-3.3.patch>`__ to apply to ECW SDK 3.3 sources
--  `GDAL ECW Build Hints <http://trac.osgeo.org/gdal/wiki/ECW>`__

doc/source/drivers/raster/gtiff.rst

@@ -384,9 +384,6 @@ The TIFF format only supports R,G,B components for palettes / color
 tables. Thus on writing the alpha information will be silently
 discarded.
 
-You may want to read hints to `generate and read cloud optimized GeoTIFF
-files <https://trac.osgeo.org/gdal/wiki/CloudOptimizedGeoTIFF>`__
-
 Creation Options
 ~~~~~~~~~~~~~~~~
 

doc/source/drivers/raster/jp2ecw.rst

@@ -379,4 +379,3 @@ See Also
 -  Support for non-GDAL specific issues should be directed to the
    `Hexagon Geospatial public
    forum <https://sgisupport.intergraph.com/infocenter/index?page=forums&forum=507301383c17ef4e013d8dfa30c2007ef1>`__
--  `GDAL ECW Build Hints <http://trac.osgeo.org/gdal/wiki/ECW>`__

doc/source/drivers/raster/msg.rst

@@ -35,37 +35,8 @@ Driver capabilities
 Build Instructions
 ------------------
 
-CMake builds
-++++++++++++
-
 See the ``GDAL_USE_PUBLICDECOMPWT`` option of :ref:`building_from_source`.
 
-Other build systems
-+++++++++++++++++++
-
-Clone the EUMETSAT library for wavelet decompression into ``frmts/msg``.
-
-If you are building with Visual Studio 6.0, extract the .vc makefiles
-for the PublicDecompWT from the file `PublicDecompWTMakefiles.zip`
-stored in that directory.
-
-If you build using the GNUMakefile, use *--with-msg* option to enable
-MSG driver:
-
-::
-
-   ./configure --with-msg
-
-If you find that some adjustments are needed in the makefile and/or the msg
-source files, please "commit" them. The EUMETSAT library promises to be
-"platform independent", but as we are working with Microsoft Windows and
-Visual Studio 6.0, we did not have the facilities to check if the rest
-of the msg driver is. Furthermore, apply steps 4 to 7 from the :ref:`raster_driver_tut`, section "Adding
-Driver to GDAL Tree".
-
-MSG Wiki page is available at http://trac.osgeo.org/gdal/wiki/MSG. It's
-dedicated to document building and usage hints
-
 Specification of Source Dataset
 -------------------------------
 

doc/source/drivers/raster/netcdf.rst

@@ -750,9 +750,6 @@ This driver is compiled with the UNIDATA NetCDF library.
 You need to download or compile the NetCDF library before configuring
 GDAL with NetCDF support.
 
-See `NetCDF GDAL wiki <http://trac.osgeo.org/gdal/wiki/NetCDF>`__ for
-build instructions and information regarding HDF4, NetCDF-4 and HDF5.
-
 See Also:
 ---------
 

doc/source/drivers/raster/pds4.rst

@@ -194,10 +194,7 @@ The following dataset creation options are available:
           and not creating from an existing PDS4 file, the
           data/pds4_template.xml file will be used. For GDAL utilities to
           find this default PDS4 template, GDAL's data directory should be
-          defined in your environment (typically on Windows builds). Consult
-          the
-          `wiki <https://trac.osgeo.org/gdal/wiki/FAQInstallationAndBuilding#HowtosetGDAL_DATAvariable>`__
-          for more information.
+          defined in your environment (typically on Windows builds).
 
    -  .. co:: LATITUDE_TYPE
          :choices: Planetocentric, Planetographic
@@ -537,12 +534,6 @@ Converting a shapefile to a PDS4 dataset with a CSV-delimited table
 
    $ ogr2ogr my_out_pds4.xml in.shp
 
-Limitations
------------
-
-As a new driver and new format, please report any issues to the bug
-tracker, as explained on the `wiki <https://trac.osgeo.org/gdal/wiki>`__
-
 See Also:
 ---------
 

doc/source/drivers/raster/postgisraster.rst

@@ -130,6 +130,6 @@ See Also
 --------
 
 -  `GDAL PostGISRaster driver
-   Wiki <https://trac.osgeo.org/gdal/wiki/frmts_wtkraster.html>`__
+   Wiki <http://web.archive.org/web/20240812045916/https://trac.osgeo.org/gdal/wiki/frmts_wtkraster.html>`__
 -  `PostGIS Raster
    documentation <https://postgis.net/docs/RT_reference.html>`__

doc/source/drivers/vector/pgeo.rst

@@ -104,8 +104,7 @@ How to use PGeo driver with unixODBC and MDB Tools (on Unix and Linux)
 
 This article gives step-by-step explanation of how to use OGR with
 unixODBC package and how to access Personal Geodatabase with PGeo
-driver. See also `GDAL wiki for other
-details <http://trac.osgeo.org/gdal/wiki/mdbtools>`__
+driver.
 
 Prerequisites
 ~~~~~~~~~~~~~

doc/source/drivers/vector/shapefile.rst

@@ -166,9 +166,7 @@ terminated with an error.
 Note that this can make it very difficult to translate a mixed geometry
 layer from another format into Shapefile format using ogr2ogr, since
 ogr2ogr has no support for separating out geometries from a source
-layer. See the
-`FAQ <http://trac.osgeo.org/gdal/wiki/FAQVector#HowdoItranslateamixedgeometryfiletoshapefileformat>`__
-for a solution.
+layer.
 
 Shapefile feature attributes are stored in an associated .dbf file, and
 so attributes suffer a number of limitations:
@@ -484,5 +482,3 @@ See Also
 --------
 
 -  `Shapelib Page <http://shapelib.maptools.org/>`__
--  `User Notes on OGR Shapefile
-   Driver <http://trac.osgeo.org/gdal/wiki/UserDocs/Shapefiles>`__

doc/source/faq.rst

@@ -4,7 +4,7 @@
 FAQ
 ================================================================================
 
-.. TODO maybe migrate the chapters 2 and following of https://trac.osgeo.org/gdal/wiki/FAQ
+.. TODO maybe migrate the chapters 2 and following of http://web.archive.org/web/https://trac.osgeo.org/gdal/wiki/FAQ
 
 .. only:: not latex