Skip to content

Commit 74805fe

Browse files
committed
update OGC services
1 parent b99f6f0 commit 74805fe

2 files changed

Lines changed: 23 additions & 18 deletions

File tree

en/ogc/wcs_format.txt

Lines changed: 16 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@
1313
:Contact: nbarker at ittvis.com
1414
:Author: Jeff McKenna
1515
:Contact: jmckenna at gatewaygeomatics.com
16-
:Last Updated: 2026-04-13
16+
:Last Updated: 2026-04-16
1717

1818

1919
.. contents::
@@ -22,7 +22,7 @@
2222

2323
This document explains how to use MapServer to deliver Landsat, SPOT, DEM, and
2424
NetCDF temporal/banded data through the MapServer WCS interface. Thanks go to
25-
Steve Lime and Frank Warmerdam for their assistance with these projects
25+
Steve Lime and Frank Warmerdam for their assistance with these projects.
2626

2727
It also shows how to configure MapServer for GRIB2 output format.
2828

@@ -31,18 +31,19 @@ It also shows how to configure MapServer for GRIB2 output format.
3131
Landsat
3232
=======
3333

34-
To serve Landsat imagery through the MapServer Web Coverage Service specify
35-
the :ref:`OUTPUTFORMAT` object. For format support install the GDAL library
36-
and from the command prompt and cd to where GDAL is installed and use the
37-
command, gdalinfo --formats. A list of all supported formats will appear and
38-
will specify if the format is read only **<ro>** or read and write **<rw>**
34+
To serve Landsat imagery through the MapServer Web Coverage Service we must configure
35+
the :ref:`OUTPUTFORMAT` object. First, you should verify that your local `GDAL <https://gdal.org>`__
36+
library supports that raster format: from the command prompt, use the `gdalinfo <https://gdal.org/programs/gdalinfo.html>`__
37+
command to see what formats are supported, by executing *gdalinfo --formats*.
38+
A list of all supported formats will appear and will specify if the format is
39+
read-only **<ro>** or read and write **<rw>**;
3940
for WCS the format needs to be supported for read and write (except for
4041
*GDAL's* own WCS format, however).
4142

4243
For the example below the Landsat 7 15m resolution mosaic is in a Enhanced
43-
Compressed Wavelets format (ECW). By running the gdalinfo.exe program I could
44+
Compressed Wavelets format (ECW). By running the gdalinfo command we can
4445
verify that the ECW format has write permissions, therefore the format can be
45-
specified in the MapFile and requested using the GetCoverage request.
46+
specified in the mapfile and requested using the GetCoverage request.
4647

4748
.. code-block:: mapfile
4849

@@ -78,8 +79,8 @@ specified in the MapFile and requested using the GetCoverage request.
7879
END
7980

8081
A GetCoverage request can then be requested (using the parameters set in the
81-
MapFile) by creating a URL with the elements: - Your Server, MapServer
82-
Program, Location of MapFile, Type of Service (WCS), Request (GetCoverage),
82+
mapfile) by creating a URL with the elements: - Your Server, MapServer
83+
Program, Location of mapfile, Type of Service (WCS), Request (GetCoverage),
8384
Coverage (Landsat7), BBOX (0,0,700005,1050000), CRS (EPSG:27700), ResX (75)
8485
ResY (75), Format (ECW).
8586

@@ -90,7 +91,7 @@ SPOT imagery can be delivered through MapServer Web Coverage Service similarly
9091
to the Landsat example above. The main difference is that as SPOT is a
9192
greyscale image the wcs_bandcount = 1 rather than a Landsat image which
9293
consists of 3 bands. For this example the well known GeoTiff format will be
93-
used to demonstrate what to specify in a MapFile for SPOT data.
94+
used to demonstrate what to specify in a mapfile for SPOT data.
9495

9596
.. code-block:: mapfile
9697

@@ -123,7 +124,7 @@ used to demonstrate what to specify in a MapFile for SPOT data.
123124
END
124125
END
125126

126-
The key parameters to specify in the WCS MapFile for any data layer and format
127+
The key parameters to specify in the WCS mapfile for any data layer and format
127128
are::
128129

129130
- Layer Name = Create a short name for the data
@@ -174,8 +175,8 @@ and the corresponding layer
174175
END
175176
END
176177

177-
Performance gains can be made by using the gdaladdo utility described at
178-
https://gdal.org/programs/gdaladdo.html
178+
Performance gains can be made by using the `gdaladdo <https://gdal.org/programs/gdaladdo.html>`__
179+
utility.
179180

180181
NetCDF
181182
======

en/ogc/wcs_server.txt

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@
1313
:Contact: stephan.meissl at eox.at
1414
:Author: Fabian Schindler
1515
:Contact: fabian.schindler at eox.at
16-
:Last Updated: 2026-04-13
16+
:Last Updated: 2026-04-16
1717

1818
.. contents:: Table of Contents
1919
:depth: 2
@@ -238,8 +238,12 @@ utilizing the raw image modes::
238238
FORMATOPTION "FILENAME=result.grd"
239239
END
240240

241-
The FORMATOPTION FILENAME defines the preferred name of the result
242-
file when returned WCS GetCoverage results.
241+
The *FORMATOPTION FILENAME* defines the preferred name of the resulting
242+
file from WCS GetCoverage requests.
243+
244+
.. TIP::
245+
The :ref:`MapServer WCS Use Cases <wcs_format>` document has more examples
246+
of formats (for both input and output).
243247

244248
Spatio/Temporal Indexes
245249
-----------------------

0 commit comments

Comments
 (0)