MapProxy 3.1.2__tar.gz → 4.0.0__tar.gz

{MapProxy-3.1.2 → mapproxy-4.0.0}/CHANGES.txt

@@ -1,3 +1,49 @@
+4.0.0 2025-03-21
+~~~~~~~~~~~~~~~~
+
+Breaking:
+  - Removed legacy seed configuration.
+  - Removed Python 3.8 support.
+  - Removed riak support as the client library is not maintained anymore. If you rely on the riak support you have to
+    continue to use version 3.1.3 with Python 3.8.
+
+Improvements:
+
+  - The tile removal and refresh code is improved by simplifying the usage of `remove_timestamp` and `before_timestamp`
+    and complementing them by new `remove_all` and `refresh_all` parameters.
+  - Add a default logging config to the docker images.
+  - Add environment variables to the docker images to enable and configure multiapp support.
+  - Added a docker compose file to make it easy to run & build docker images and to use as reference.
+  - Updated and improved the documentation about usage of the docker images.
+
+Maintenance:
+
+  - Use python build instead of invoking setup.py.
+  - Removal of the six library.
+  - Removed array initializers in function signatures.
+
+Fixes:
+
+  - Added `AdminstrativeArea` to WMTS serviceprovider metadata.
+  - Fixed spelling & grammar in seed.rst.
+  - Fixed problem with combined usage of `coverage` and the `remove_all` cache config parameters.
+  - Fixed missing dimension parameters in the `remove_tile` functions of various caches.
+
+
+3.1.3 2024-11-26
+~~~~~~~~~~~~~~~~
+
+Maintenance:
+
+  - Several dependencies for the tests and GitHub actions have been updated
+  - Spelling and grammar mistakes in the documentation corrected
+
+Fixes:
+
+  - The chmod to update file permissions is now only called if the file was freshly created
+  - A bug with clipping polygons that become multi polygons due to the clipping is now fixed
+
+
 3.1.2 2024-11-20
 ~~~~~~~~~~~~~~~~
 

{MapProxy-3.1.2 → mapproxy-4.0.0}/MapProxy.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.4
 Name: MapProxy
-Version: 3.1.2
+Version: 4.0.0
 Summary: An accelerating proxy for tile and web map services
 Home-page: https://mapproxy.org
 Author: Oliver Tonnhofer
@@ -8,11 +8,9 @@ Author-email: olt@omniscale.de
 Maintainer: terrestris GmbH & Co. KG
 Maintainer-email: info@terrestris.de
 License: Apache Software License 2.0
-Platform: UNKNOWN
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: License :: OSI Approved :: Apache Software License
 Classifier: Operating System :: OS Independent
-Classifier: Programming Language :: Python :: 3.8
 Classifier: Programming Language :: Python :: 3.9
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
@@ -24,6 +22,24 @@ Description-Content-Type: text/x-rst
 License-File: LICENSE.txt
 License-File: COPYING.txt
 License-File: AUTHORS.txt
+Requires-Dist: PyYAML>=3.0
+Requires-Dist: future
+Requires-Dist: pyproj>=2
+Requires-Dist: jsonschema>=4
+Requires-Dist: werkzeug<4
+Requires-Dist: Pillow!=2.4.0,!=8.3.0,!=8.3.1
+Dynamic: author
+Dynamic: author-email
+Dynamic: classifier
+Dynamic: description
+Dynamic: description-content-type
+Dynamic: home-page
+Dynamic: license
+Dynamic: license-file
+Dynamic: maintainer
+Dynamic: maintainer-email
+Dynamic: requires-dist
+Dynamic: summary
 
 MapProxy is an open source proxy for geospatial data. It caches, accelerates and transforms data from existing map services and serves any desktop or web GIS client.
 
@@ -37,6 +53,52 @@ The documentation is available at: http://mapproxy.github.io/mapproxy/latest/
 
 Changes
 -------
+4.0.0 2025-03-21
+~~~~~~~~~~~~~~~~
+
+Breaking:
+  - Removed legacy seed configuration.
+  - Removed Python 3.8 support.
+  - Removed riak support as the client library is not maintained anymore. If you rely on the riak support you have to
+    continue to use version 3.1.3 with Python 3.8.
+
+Improvements:
+
+  - The tile removal and refresh code is improved by simplifying the usage of `remove_timestamp` and `before_timestamp`
+    and complementing them by new `remove_all` and `refresh_all` parameters.
+  - Add a default logging config to the docker images.
+  - Add environment variables to the docker images to enable and configure multiapp support.
+  - Added a docker compose file to make it easy to run & build docker images and to use as reference.
+  - Updated and improved the documentation about usage of the docker images.
+
+Maintenance:
+
+  - Use python build instead of invoking setup.py.
+  - Removal of the six library.
+  - Removed array initializers in function signatures.
+
+Fixes:
+
+  - Added `AdminstrativeArea` to WMTS serviceprovider metadata.
+  - Fixed spelling & grammar in seed.rst.
+  - Fixed problem with combined usage of `coverage` and the `remove_all` cache config parameters.
+  - Fixed missing dimension parameters in the `remove_tile` functions of various caches.
+
+
+3.1.3 2024-11-26
+~~~~~~~~~~~~~~~~
+
+Maintenance:
+
+  - Several dependencies for the tests and GitHub actions have been updated
+  - Spelling and grammar mistakes in the documentation corrected
+
+Fixes:
+
+  - The chmod to update file permissions is now only called if the file was freshly created
+  - A bug with clipping polygons that become multi polygons due to the clipping is now fixed
+
+
 3.1.2 2024-11-20
 ~~~~~~~~~~~~~~~~
 
@@ -113,40 +175,7 @@ Fixes:
   - Fix gh-pages workflow
 
 
-2.2.0 2024-07-24
-~~~~~~~~~~~~~~~~
-
-Improvements:
-
-  - Add timeout to SQLite connect for geopackages. This helps against locking exceptions
-  - Improvement of documentation, typos, wrong cli commands, old python2 stuff
-  - The WMTS capabilites will now advertise the WMS GetLegendGraphic as a LegendURL if both services are active
-  - It is possible now to configure LegendURLs that should be shown in the WMTS capabilities
-  - A new method for plugins to intercept and modify requests made to MapProxy was added.
-
-Maintenance:
-
-  - Removal of debian package information
-  - Fix docs workflow
-
-Fixes:
-
-  - Remove import of the packaging library that does not appear in the `install_requires`
-  - Only install and use `importlib_resources` in python 3.8
-
-
-2.1.1 2024-07-16
-~~~~~~~~~~~~~~~~
-Fixes:
-
-  - Fix version of jsonschema in setup.py
-  - Fix alpine docker build
-  - Fix doc generation workflow
-
-
 
 Older changes
 -------------
 See https://raw.github.com/mapproxy/mapproxy/master/CHANGES.txt
-
-

{MapProxy-3.1.2 → mapproxy-4.0.0}/MapProxy.egg-info/SOURCES.txt

@@ -4,6 +4,7 @@ COPYING.txt
 LICENSE.txt
 MANIFEST.in
 README.md
+pyproject.toml
 requirements-tests.txt
 setup.py
 MapProxy.egg-info/PKG-INFO
@@ -90,7 +91,6 @@ mapproxy/cache/meta.py
 mapproxy/cache/path.py
 mapproxy/cache/redis.py
 mapproxy/cache/renderd.py
-mapproxy/cache/riak.py
 mapproxy/cache/s3.py
 mapproxy/cache/tile.py
 mapproxy/client/__init__.py
@@ -400,7 +400,6 @@ mapproxy/test/system/fixture/renderd_client.yaml
 mapproxy/test/system/fixture/scalehints.yaml
 mapproxy/test/system/fixture/seed.yaml
 mapproxy/test/system/fixture/seed_mapproxy.yaml
-mapproxy/test/system/fixture/seed_old.yaml
 mapproxy/test/system/fixture/seed_timeouts.yaml
 mapproxy/test/system/fixture/seed_timeouts_mapproxy.yaml
 mapproxy/test/system/fixture/seedonly.yaml
@@ -438,7 +437,6 @@ mapproxy/test/unit/test_cache_couchdb.py
 mapproxy/test/unit/test_cache_geopackage.py
 mapproxy/test/unit/test_cache_mbtile.py
 mapproxy/test/unit/test_cache_redis.py
-mapproxy/test/unit/test_cache_riak.py
 mapproxy/test/unit/test_cache_s3.py
 mapproxy/test/unit/test_cache_tile.py
 mapproxy/test/unit/test_client.py

{MapProxy-3.1.2 → mapproxy-4.0.0}/MapProxy.egg-info/entry_points.txt

@@ -1,4 +1,3 @@
 [console_scripts]
 mapproxy-seed = mapproxy.seed.script:main
 mapproxy-util = mapproxy.script.util:main
-

{MapProxy-3.1.2 → mapproxy-4.0.0}/MapProxy.egg-info/requires.txt

@@ -1,9 +1,6 @@
-Pillow!=2.4.0,!=8.3.0,!=8.3.1
 PyYAML>=3.0
 future
-jsonschema>=4
 pyproj>=2
+jsonschema>=4
 werkzeug<4
-
-[:python_version <= "3.8"]
-importlib_resources
+Pillow!=2.4.0,!=8.3.0,!=8.3.1

{MapProxy-3.1.2 → mapproxy-4.0.0}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.4
 Name: MapProxy
-Version: 3.1.2
+Version: 4.0.0
 Summary: An accelerating proxy for tile and web map services
 Home-page: https://mapproxy.org
 Author: Oliver Tonnhofer
@@ -8,11 +8,9 @@ Author-email: olt@omniscale.de
 Maintainer: terrestris GmbH & Co. KG
 Maintainer-email: info@terrestris.de
 License: Apache Software License 2.0
-Platform: UNKNOWN
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: License :: OSI Approved :: Apache Software License
 Classifier: Operating System :: OS Independent
-Classifier: Programming Language :: Python :: 3.8
 Classifier: Programming Language :: Python :: 3.9
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
@@ -24,6 +22,24 @@ Description-Content-Type: text/x-rst
 License-File: LICENSE.txt
 License-File: COPYING.txt
 License-File: AUTHORS.txt
+Requires-Dist: PyYAML>=3.0
+Requires-Dist: future
+Requires-Dist: pyproj>=2
+Requires-Dist: jsonschema>=4
+Requires-Dist: werkzeug<4
+Requires-Dist: Pillow!=2.4.0,!=8.3.0,!=8.3.1
+Dynamic: author
+Dynamic: author-email
+Dynamic: classifier
+Dynamic: description
+Dynamic: description-content-type
+Dynamic: home-page
+Dynamic: license
+Dynamic: license-file
+Dynamic: maintainer
+Dynamic: maintainer-email
+Dynamic: requires-dist
+Dynamic: summary
 
 MapProxy is an open source proxy for geospatial data. It caches, accelerates and transforms data from existing map services and serves any desktop or web GIS client.
 
@@ -37,6 +53,52 @@ The documentation is available at: http://mapproxy.github.io/mapproxy/latest/
 
 Changes
 -------
+4.0.0 2025-03-21
+~~~~~~~~~~~~~~~~
+
+Breaking:
+  - Removed legacy seed configuration.
+  - Removed Python 3.8 support.
+  - Removed riak support as the client library is not maintained anymore. If you rely on the riak support you have to
+    continue to use version 3.1.3 with Python 3.8.
+
+Improvements:
+
+  - The tile removal and refresh code is improved by simplifying the usage of `remove_timestamp` and `before_timestamp`
+    and complementing them by new `remove_all` and `refresh_all` parameters.
+  - Add a default logging config to the docker images.
+  - Add environment variables to the docker images to enable and configure multiapp support.
+  - Added a docker compose file to make it easy to run & build docker images and to use as reference.
+  - Updated and improved the documentation about usage of the docker images.
+
+Maintenance:
+
+  - Use python build instead of invoking setup.py.
+  - Removal of the six library.
+  - Removed array initializers in function signatures.
+
+Fixes:
+
+  - Added `AdminstrativeArea` to WMTS serviceprovider metadata.
+  - Fixed spelling & grammar in seed.rst.
+  - Fixed problem with combined usage of `coverage` and the `remove_all` cache config parameters.
+  - Fixed missing dimension parameters in the `remove_tile` functions of various caches.
+
+
+3.1.3 2024-11-26
+~~~~~~~~~~~~~~~~
+
+Maintenance:
+
+  - Several dependencies for the tests and GitHub actions have been updated
+  - Spelling and grammar mistakes in the documentation corrected
+
+Fixes:
+
+  - The chmod to update file permissions is now only called if the file was freshly created
+  - A bug with clipping polygons that become multi polygons due to the clipping is now fixed
+
+
 3.1.2 2024-11-20
 ~~~~~~~~~~~~~~~~
 
@@ -113,40 +175,7 @@ Fixes:
   - Fix gh-pages workflow
 
 
-2.2.0 2024-07-24
-~~~~~~~~~~~~~~~~
-
-Improvements:
-
-  - Add timeout to SQLite connect for geopackages. This helps against locking exceptions
-  - Improvement of documentation, typos, wrong cli commands, old python2 stuff
-  - The WMTS capabilites will now advertise the WMS GetLegendGraphic as a LegendURL if both services are active
-  - It is possible now to configure LegendURLs that should be shown in the WMTS capabilities
-  - A new method for plugins to intercept and modify requests made to MapProxy was added.
-
-Maintenance:
-
-  - Removal of debian package information
-  - Fix docs workflow
-
-Fixes:
-
-  - Remove import of the packaging library that does not appear in the `install_requires`
-  - Only install and use `importlib_resources` in python 3.8
-
-
-2.1.1 2024-07-16
-~~~~~~~~~~~~~~~~
-Fixes:
-
-  - Fix version of jsonschema in setup.py
-  - Fix alpine docker build
-  - Fix doc generation workflow
-
-
 
 Older changes
 -------------
 See https://raw.github.com/mapproxy/mapproxy/master/CHANGES.txt
-
-

{MapProxy-3.1.2 → mapproxy-4.0.0}/doc/auth.rst

@@ -93,7 +93,8 @@ Here is a more elaborate example that denies requests to all layers that start w
           environ['mapproxy.authorize'] = self.authorize
           return self.app(environ, start_response)
 
-      def authorize(self, service, layers=[], environ=None, **kw):
+      def authorize(self, service, layers=None, environ=None, **kw):
+          layers = layers or None
           allowed = denied = False
           if service.startswith('wms.'):
               auth_layers = {}

{MapProxy-3.1.2 → mapproxy-4.0.0}/doc/caches.rst

@@ -317,61 +317,14 @@ MapProxy will place the JSON document for tile z=3, x=1, y=2 at ``http://localho
 
 The ``_attachments``-part is the internal structure of CouchDB where the tile itself is stored. You can access the tile directly at: ``http://localhost:9999/mywms_tiles/mygrid-3-1-2/tile``.
 
+
 .. _cache_riak:
 
 ``riak``
 ========
 
-.. versionadded:: 1.6.0
-
-Store tiles in a `Riak <http://basho.com/riak/>`_ cluster. MapProxy creates keys with binary data as value and timestamps as user defined metadata.
-This backend is good for very large caches which can be distributed over many nodes. Data can be distributed over multiple nodes providing a fault-tolernt and high-available storage. A Riak cluster is masterless and each node can handle read and write requests.
-
-Requirements
-------------
-
-You will need the `Python Riak client <https://pypi.org/project/riak>`_ version 2.4.2 or older. You can install it in the usual way, for example with ``pip install riak==2.4.2``. Environments with older version must be upgraded with ``pip install -U riak==2.4.2``. Python library depends on packages `python-dev`, `libffi-dev` and `libssl-dev`.
-
-Configuration
--------------
-
-Available options:
+Support dropped after version 3.1.3 of MapProxy.
 
-``nodes``:
-    A list of riak nodes. Each node needs a ``host`` and optionally a ``pb_port`` and an ``http_port`` if the ports differ from the default. Defaults to single localhost node.
-
-``protocol``:
-    Communication protocol. Allowed options is ``http``, ``https`` and ``pbc``. Defaults to ``pbc``.
-
-``bucket``:
-    The name of the bucket MapProxy uses for this cache. The bucket is the namespace for the tiles and must be unique for each cache. Defaults to cache name suffixed with grid name (e.g. ``mycache_webmercator``).
-
-``default_ports``:
-    Default ``pb`` and ``http`` ports for ``pbc`` and ``http`` protocols. Will be used as the default for each defined node.
-
-``secondary_index``:
-    If ``true`` enables secondary index for tiles. This improves seed cleanup performance but requires that Riak uses LevelDB as the backend. Refer to the Riak documentation. Defaults to ``false``.
-
-Example
--------
-
-.. code-block:: yaml
-
-  myriakcache:
-    sources: [mywms]
-    grids: [mygrid]
-    cache:
-      type: riak
-      nodes:
-        - host: 1.example.org
-          pb_port: 9999
-        - host: 1.example.org
-        - host: 1.example.org
-      protocol: pbc
-      bucket: myriakcachetiles
-      default_ports:
-        pb: 8087
-        http: 8098
 
 .. _cache_redis:
 

{MapProxy-3.1.2 → mapproxy-4.0.0}/doc/configuration.rst

@@ -238,7 +238,7 @@ The name of the layer. You can omit the name for group layers (e.g. layers with
 
 ``title``
 """""""""
-Readable name of the layer, e.g WMS layer title.
+Readable name of the layer, e.g. WMS layer title.
 
 
 .. _layers:
@@ -297,14 +297,14 @@ A list of caches for this layer. This list overrides ``sources`` for WMTS and TM
 
 Limit the layer to the given min and max resolution or scale. MapProxy will return a blank image for requests outside of these boundaries (``min_res`` is inclusive, ``max_res`` exclusive). You can use either the resolution or the scale values, missing values will be interpreted as `unlimited`. Resolutions should be in meters per pixel.
 
-The values will also apear in the capabilities documents (i.e. WMS ScaleHint and Min/MaxScaleDenominator).
+The values will also appear in the capabilities documents (i.e. WMS ScaleHint and Min/MaxScaleDenominator).
 
 Please read :ref:`scale vs. resolution <scale_resolution>` for some notes on `scale`.
 
 ``legendurl``
 """""""""""""
 
-Configure a URL to an image that should be returned as the legend for this layer. Local URLs (``file://``) are also supported. MapProxy ignores the legends from the sources of this layer if you configure a ``legendurl`` here. If WMS and WMTS are enabled the address to the WMS `GetLegendGraphic` endpoint will be included in the WMTS capabilities as the legend url.
+Configure a URL to an image that should be returned as the legend for this layer. Local URLs (``file://``) are also supported. MapProxy ignores the legends from the sources of this layer if you configure a ``legendurl`` here. If WMS and WMTS are enabled the address to the WMS `GetLegendGraphic` endpoint will be included in the WMTS capabilities as the legend URL.
 
 .. _layer_metadata:
 
@@ -397,7 +397,7 @@ Each dimension is another dictionary with a list of ``values`` and an optional `
 
 It is possible to configure which URLS the WMTS will advertise as LegendURLs through its capabilities. These will be
 inserted as a ``LegendURL`` tag into the capabilities document. These URLs support two template variables ``{base_url}``
-which is the base url of MapProxy and ``{layer_name}`` which is the name of the layer.
+which is the base URL of MapProxy and ``{layer_name}`` which is the name of the layer.
 
 .. code-block:: yaml
 
@@ -541,7 +541,7 @@ In practice this means that all the linked images will have the first such tile'
 """"""""""""""""""""""""""
 If set to ``true``, MapProxy will only issue a single request to the source. This option can reduce the request latency for uncached areas (on demand caching).
 
-By default MapProxy requests all uncached meta-tiles that intersect the requested bbox. With a typical configuration it is not uncommon that a requests will trigger four requests each larger than 2000x2000 pixel. With the ``minimize_meta_requests`` option enabled, each request will trigger only one request to the source. That request will be aligned to the next tile boundaries and the tiles will be cached.
+By default MapProxy requests all uncached meta-tiles that intersect the requested bbox. With a typical configuration it is not uncommon that a request will trigger four requests each larger than 2000x2000 pixel. With the ``minimize_meta_requests`` option enabled, each request will trigger only one request to the source. That request will be aligned to the next tile boundaries and the tiles will be cached.
 
 .. index:: watermark
 
@@ -616,9 +616,9 @@ MapProxy is able to create missing tiles by rescaling tiles from zoom levels bel
 
 MapProxy will scale up tiles from one or more zoom levels above (with lower resolutions) if you set ``upscale_tiles`` to 1 or higher. The value configures by how many zoom levels MapProxy can search for a proper tile. Higher values allow more blurry results.
 
-You can use ``upscale_tiles`` if you want to provide tiles or WMS responses in a higher resolution then your available cache. This also works with partially seeded caches, eg. where you have an aerial image cache of 20cm, with some areas also in 10cm resolution. ``upscale_tiles`` allows you to provide responses for 10cm requests in all areas, always returning the best available data.
+You can use ``upscale_tiles`` if you want to provide tiles or WMS responses in a higher resolution then your available cache. This also works with partially seeded caches, e.g. where you have an aerial image cache of 20cm, with some areas also in 10cm resolution. ``upscale_tiles`` allows you to provide responses for 10cm requests in all areas, always returning the best available data.
 
-MapProxy will scale down tiles from one or more zoom levels below (with higher resolutions) if you set ``downscale_tiles`` to 1 or higher. The value configures by how many zoom levels MapProxy can search for a proper tile. Note that the number of tiles growth exponentialy. Typically, a single tile can be downscaled from four tiles of the next zoom level. Downscaling from two levels below requires 16 tiles, three levels below requires 64, etc.. A larger WMS request can quickly accumulate thousands of tiles required for downscaling. It is therefore `not` recommended to use ``downscale_tiles`` values larger then one.
+MapProxy will scale down tiles from one or more zoom levels below (with higher resolutions) if you set ``downscale_tiles`` to 1 or higher. The value configures by how many zoom levels MapProxy can search for a proper tile. Note that the number of tiles growth exponentially. Typically, a single tile can be downscaled from four tiles of the next zoom level. Downscaling from two levels below requires 16 tiles, three levels below requires 64, etc.. A larger WMS request can quickly accumulate thousands of tiles required for downscaling. It is therefore `not` recommended to use ``downscale_tiles`` values larger than one.
 
 You can use ``downscale_tiles`` to fill a cache for a source that only provides data for higher resolutions.
 
@@ -677,7 +677,7 @@ Example:
 """"""""""""""""""""
 
 If set to ``true``, MapProxy will not store any tiles for this cache. MapProxy will re-request all required tiles for each incoming request,
-even if the there are matching tiles in the cache. See :ref:`seed_only <wms_seed_only>` if you need an *offline* mode.
+even if there are matching tiles in the cache. See :ref:`seed_only <wms_seed_only>` if you need an *offline* mode.
 
 .. note:: Be careful when using a cache with disabled storage in tile services when the cache uses WMS sources with metatiling.
 
@@ -841,7 +841,7 @@ The total number of cached resolution levels. Defaults to 20, except for grids w
 
 ``min_res`` and ``max_res``
 """""""""""""""""""""""""""
-The the resolutions of the first and the last level.
+The resolutions of the first and the last level.
 
 ``stretch_factor``
 """"""""""""""""""
@@ -849,7 +849,7 @@ MapProxy chooses the `optimal` cached level for requests that do not exactly
 match any cached resolution. MapProxy will stretch or shrink images to the
 requested resolution. The `stretch_factor` defines the maximum factor
 MapProxy is allowed to stretch images. Stretched images result in better
-performance but will look blurry when the value is to large (> 1.2).
+performance but will look blurry when the value is too large (> 1.2).
 
 Example: Your MapProxy caches 10m and 5m resolutions. Requests with 9m
 resolution will be generated from the 10m level, requests for 8m from the 5m
@@ -910,7 +910,7 @@ Example ``grids`` configuration
 sources
 -------
 
-A sources defines where MapProxy can request new data. Each source has a ``type`` and all other options are dependent to this type.
+A source defines where MapProxy can request new data. Each source has a ``type`` and all other options are dependent to this type.
 
 See :doc:`sources` for the documentation of all available sources.
 
@@ -1027,7 +1027,7 @@ The following options define how tiles are created and stored. Most options can
 .. _lock_dir:
 
 ``lock_dir``
-  MapProxy uses locking to limit multiple request to the same service. See ``concurrent_requests``.
+  MapProxy uses locking to limit multiple requests to the same service. See ``concurrent_requests``.
   This option defines where the temporary lock files will be stored. The path
   can either be absolute (e.g. ``/tmp/lock/mapproxy``) or relative to the
   mapproxy.yaml file. Defaults to ``./cache_data/tile_locks``.
@@ -1103,7 +1103,7 @@ The following options define how tiles are created and stored. Most options can
 
 ``axis_order_ne`` and ``axis_order_en``
   The axis ordering defines in which order coordinates are given, i.e. lon/lat or lat/lon.
-  The ordering is dependent to the SRS. Most clients and servers did not respected the
+  The ordering is dependent to the SRS. Most clients and servers did not respect the
   ordering and everyone used lon/lat ordering. With the WMS 1.3.0 specification the OGC
   emphasized that the axis ordering of the SRS should be used.
 
@@ -1212,7 +1212,7 @@ Sets the ``Access-control-allow-origin`` header to HTTP responses for `Cross-ori
 .. versionadded:: 1.14.0
 
 Enables MapProxy cookie management for HTTP sources. When enabled MapProxy will accept and store server cookies. Accepted cookies will be passed
-back to the source on subsequent requests. Usefull for sources which require to maintain an HTTP session to work efficiently, maybe in combination
+back to the source on subsequent requests. Useful for sources which require to maintain an HTTP session to work efficiently, maybe in combination
 with basic authentication. Depending on your deployment MapProxy will still start multiple sessions (e.g. one per MapProxy process).
 Cookie handling is based on Python `CookieJar <https://docs.python.org/3/library/http.cookiejar.html>`_. Disabled by default.
 
@@ -1386,7 +1386,7 @@ Notes
 Scale vs. resolution
 """"""""""""""""""""
 
-Scale is the ratio of a distance on a map and the corresponding distance on the ground. This implies that the map distance and the ground distance are measured in the same unit. For MapProxy a `map` is just a collection of pixels and the pixels do not have any size/dimension. They do correspond to a ground size but the size on the `map` is depended of the physical output format. MapProxy can thus only work with resolutions (pixel per ground unit) and not scales.
+Scale is the ratio of a distance on a map and the corresponding distance on the ground. This implies that the map distance and the ground distance are measured in the same unit. For MapProxy a `map` is just a collection of pixels and the pixels do not have any size/dimension. They do correspond to a ground size but the size on the `map` is depended on the physical output format. MapProxy can thus only work with resolutions (pixel per ground unit) and not scales.
 
 This applies to all servers and the OGC WMS standard as well. Some neglect this fact and assume a fixed pixel dimension (like 72dpi), the OCG WMS 1.3.0 standard uses a pixel size of 0.28 mm/px (around 91dpi). But you need to understand that a `scale` will differ if you print a map (200, 300 or more dpi) or if you show it on a computer display (typical 90-120 dpi, but there are mobile devices with more than 300 dpi).
 

{MapProxy-3.1.2 → mapproxy-4.0.0}/doc/deployment.rst

@@ -285,11 +285,11 @@ MultiMapProxy
 
 .. versionadded:: 1.2.0
 
-You can run multiple MapProxy instances (configurations) within one process with the MultiMapProxy application.
+You can run multiple MapProxy apps (configurations) within one process with MultiMapProxy.
 
 MultiMapProxy can dynamically load configurations. You can put all configurations into one directory and MapProxy maps each file to a URL: ``conf/proj1.yaml`` is available at ``http://hostname/proj1/``.
 
-Each configuration will be loaded on demand and MapProxy caches each loaded instance. The configuration will be reloaded if the file changes.
+Each configuration will be loaded on demand and MapProxy caches each loaded app. The configuration will be reloaded if the file changes.
 
 MultiMapProxy as the following options:
 
@@ -308,5 +308,5 @@ There is a ``make_wsgi_app`` function in the ``mapproxy.multiapp`` package that
 .. code-block:: python
 
   from mapproxy.multiapp import make_wsgi_app
-  application = make_wsgi_app('/path/to.projects', allow_listing=True)
+  application = make_wsgi_app('/path/to.configs', allow_listing=True)
 

{MapProxy-3.1.2 → mapproxy-4.0.0}/doc/install.rst

@@ -5,7 +5,7 @@ This tutorial guides you to the MapProxy installation process on Unix systems. F
 
 This tutorial was created and tested with Debian and Ubuntu, if you're installing MapProxy on a different system you might need to change some package names.
 
-MapProxy is `registered at the Python Package Index <https://pypi.org/project/MapProxy/>`_ (PyPI). If you have Python 3.8 or higher, you can install MapProxy with::
+MapProxy is `registered at the Python Package Index <https://pypi.org/project/MapProxy/>`_ (PyPI). If you have Python 3.9 or higher, you can install MapProxy with::
 
   python -m pip install MapProxy
 
@@ -39,7 +39,7 @@ This will change the ``PATH`` for your `current` session.
 Install Dependencies
 --------------------
 
-MapProxy is written in Python, thus you will need a working Python installation. MapProxy works with Python 3.8 or higher, which should already be installed with most Linux distributions.
+MapProxy is written in Python, thus you will need a working Python installation. MapProxy works with Python 3.9 or higher, which should already be installed with most Linux distributions.
 
 MapProxy requires a few third-party libraries that are required to run. There are different ways to install each dependency. Read :ref:`dependency_details` for a list of all required and optional dependencies.