Skip to content

Commit e3c9da7

Browse files
authored
Merge pull request #905 from jmckenna/spatialreference-links
point to spatialreference.org for EPSG references
2 parents 26e9705 + 1c078e3 commit e3c9da7

File tree

8 files changed

+16
-16
lines changed

8 files changed

+16
-16
lines changed

en/glossary.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -177,7 +177,7 @@
177177
(or more commonly known as the *Google Mercator*, or *Web Mercator*) is a
178178
term used to describe the default :ref:`PROJECTION` used by many commercial
179179
API providers for their resulting map tiles & services. The associated official
180-
EPSG code is `EPSG:3857 <https://epsg.io/3857>`__ (formerly "EPSG:900913").
180+
EPSG code is `EPSG:3857 <https://spatialreference.org/ref/epsg/3857/>`__ (formerly "EPSG:900913").
181181

182182
SVG
183183
`Scalable Vector Graphics <https://en.wikipedia.org/wiki/Scalable_Vector_Graphics>`__ is

en/input/vector/postgis.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -312,7 +312,7 @@ Next specify the *table* and *column*, with the *-nomd* switch, such as:
312312
gdalinfo PG:"host=127.0.0.1 port=5432 user=postgres password=postgres dbname=mydb table=lunenburg_colorhillshade column=rast" -nomd
313313

314314
which returns a summary of the raster, including its projection
315-
(`EPSG:2961 <https://epsg.io/2961>`__) :
315+
(`EPSG:2961 <https://spatialreference.org/ref/epsg/2961/>`__) :
316316

317317
::
318318

en/mapfile/projection.txt

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -81,8 +81,8 @@ NAD83), but use 2 different methods:
8181

8282
.. note::
8383

84-
See https://epsg.io/26915 for more information on
85-
this coordinate system.
84+
See `EPSG:26915 <https://spatialreference.org/ref/epsg/26915/>`__
85+
for more information on this coordinate system.
8686

8787
The next two examples both display how to possibly define unprojected
8888
lat/long ("geographic"):
@@ -109,10 +109,10 @@ lat/long ("geographic"):
109109
-----------------------------------
110110

111111
The EPSG code for the commonly used "Web" or "Google" mercator projection is
112-
'3857'. See https://epsg.io/3857 for more information on
113-
this coordinate system. This code was also unofficially referred to as
114-
`EPSG:900913`; you are recommended to use the official `EPSG:3857` code
115-
instead, such as:
112+
'3857'. See `EPSG:3857 <https://spatialreference.org/ref/epsg/3857/>`__
113+
for more information on this coordinate system. This code was also
114+
unofficially referred to as `EPSG:900913`; you are recommended to use the
115+
official `EPSG:3857` code instead, such as:
116116

117117
.. code-block:: mapfile
118118

en/ogc/wms_server.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2291,8 +2291,8 @@ FAQ / Common Problems
22912291
:Q: **How can I find the EPSG code for my data's projection?**
22922292

22932293
:A: If you know some of the parameters of your data's projection,
2294-
then you can use the search tool at https://epsg.io/ to find your data's
2295-
associated EPSG code. The EPSG official home now also allows
2294+
then you can use the search tool at https://spatialreference.org to find your data's
2295+
associated EPSG code. The EPSG official home also allows
22962296
you to perform a text or map search for a projection: https://epsg.org/
22972297

22982298
For `PROJ <https://proj.org/>`_ version >= 6: the EPSG codes are stored in a SpatiaLite

en/optimization/raster.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -162,7 +162,7 @@ MrSID raster: ::
162162
Upper Right values) to paste into your
163163
mapfile's EXTENT parameter. You can also notice in that summary
164164
the *PROJCS/AUTHORITY* line, which states that this data is currently
165-
in the `EPSG:26915 <http://epsg.io/26915>`__ projection.
165+
in the `EPSG:26915 <https://spatialreference.org/ref/epsg/26915/>`__ projection.
166166

167167
.. NOTE::
168168
For Windows users, `MS4W <https://ms4w.com>`__ includes the gdalinfo utility,

en/optimization/vector.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,7 @@ Then get a summary of the 'popplace' table through ogrinfo: ::
139139
You can use the extent values returned from ogrinfo, to paste into your
140140
mapfile's EXTENT parameter. You can also notice in that summary
141141
the *PROJCS/AUTHORITY* line, which states that this data is currently
142-
in the `EPSG:3978 <http://epsg.io/3978>`__ projection.
142+
in the `EPSG:3978 <https://spatialreference.org/ref/epsg/3978/>`__ projection.
143143

144144
Learn & Review the various OGR utilities to manage your vectors
145145
---------------------------------------------------------------
@@ -159,7 +159,7 @@ renames the new table to 'roadways') : ::
159159

160160
You might also import a spatial file, and reproject it to another EPSG
161161
projection, as the following (that takes a shapefile, reprojects it into
162-
the web mercator `EPSG:3857 <http://epsg.io/3857>`__, imports it into an
162+
the web mercator `EPSG:3857 <https://spatialreference.org/ref/epsg/3857/>`__, imports it into an
163163
existing PostGIS database, and renames the new table to 'roadways3857') :
164164
::
165165

en/output/tile_mode.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ you will have to ensure each LAYER has a valid PROJECTION block.
6262
.. note::
6363
The MAP-level projection in the mapfile is not required for *mode=tile*
6464
as the output projection will always be set to the Google
65-
Mercator projection `EPSG:3857 <http://epsg.io/3857>`__ and its extents,
65+
Mercator projection `EPSG:3857 <https://spatialreference.org/ref/epsg/3857/>`__ and its extents,
6666
for mode=tile (in other words, the Google Mercator projection is hard-coded in
6767
the underlying MapServer source code, always for the mode=tile case).
6868
If your mapfile is also serving through an OGC service,
@@ -157,7 +157,7 @@ About Spherical Mercator
157157
:term:`Spherical Mercator` (also called the "web mercator" or "google mercator")
158158
is a world projection that all the major tile-based map interfaces (Google Maps,
159159
Bing Maps [formerly "Virtual Earth"], Yahoo Maps, OpenLayers) use to address tiles.
160-
The associated official EPSG code is `EPSG:3857 <http://epsg.io/3857>`__.
160+
The associated official EPSG code is `EPSG:3857 <https://spatialreference.org/ref/epsg/3857/>`__.
161161

162162
A spherical mercator set of tiles has the following properties:
163163

en/tutorial/example1-6.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ you want to learn more about EPSG codes, have a look at
8484

8585
.. note::
8686

87-
You can search for EPSG codes and see MapServer usage examples at `<https://epsg.io/>`_
87+
You can search for EPSG codes and see MapServer usage examples at `<https://spatialreference.org/>`_
8888

8989
Also, check out the EPSG web site at `<https://epsg.org>`_.
9090

0 commit comments

Comments
 (0)