MapProxy

from Wikipedia, the free encyclopedia
MapProxy

logo
Basic data

Maintainer Omniscale GmbH & Co. KG
Publishing year 2009
Current  version 1.12.0
( August 30, 2019 )
programming language python
category GIS
License Apache ( Free Software )
German speaking No
mapproxy.de

MapProxy is an open-source software , which by WMS - and Tile - proxies , allowing existing Geoservices to speed through pre-construction and caching the data.

use

MapProxy can be used as a standardization and acceleration element in a spatial data infrastructure . The software can summarize data from different servers with different standards and be addressed by both GIS and web clients. MapProxy can be used cascading (as a pure proxy for map services) and with the cache function.

Furthermore, the software can serve as a security layer in front of map services. In this way, entire map services or individual layers provided by a map service can be secured.

history

At the end of 2008, the Oldenburg company Omniscale GmbH & Co. KG , which specializes in geodata applications on an open source basis, began developing MapProxy. The program has been running since mid-2009. On March 22, 2010, Omniscale released the program with version 0.8.0 for the first time as open source software under the GNU AGPL License 3.0 . Since then it has been continuously developed by an active community . Version 1.0.0 was released on March 3, 2011. With version 1.1.0, they switched to the Apache Software License 2.0 in June 2011 .

safety

MapProxy is able to combine individual map levels of different WMS services. In this way, information can be specifically activated or blocked. The actual WMS servers are not visible to the end user and can, for example, be secured by firewall systems.

technology

MapProxy is mostly written in Python and is configured via YAML files. The software can be operated via WSGI as well as FastCGI with a web server or as an independent HTTP server.

MapProxy saves queries that have been answered once in its cache. In this way, the actual map service is not called up again for similar inquiries to the MapProxy. In order to also speed up initial inquiries, areas with a likely high demand can be pre-stored. The caching is tiled, i.e. H. the data requested by the map service are saved in rectangular image files. These are put together again according to the request before delivery. This enables the OGC WMS standard to be complied with.

With MapProxy it is possible to use only single functions like getFeatureInfoor of getLegenda map service and to combine several identical or different map services.

Example: MapProxy can combine an aerial WMTS server with a road data WMS server and the getFeatureInfofunctionality of a land use data WMS server in one layer. This layer can be integrated in a GI system. You get a layer in which street data is located above the aerial photo and metadata can be called up for certain areas.

The software can transform between different coordinate systems. For example, a WMS in WGS 84 can be delivered as a Gauß-Krüger coordinate system .

Standards

MapProxy can receive and deliver data from the following standards:

  • OGC WMS 1.0.0-1.3.0
  • OSGeo TMS
  • OGC WMTS
  • OGC KML 2.2

Individual evidence

  1. ↑ Release 1.12.0 . August 30, 2019 (accessed August 31, 2019).
  2. ↑ Dominik Helle; Oliver Tonnhofer: MapProxy. A practical introduction. (PDF; 908 kB) Workshop for the FOSSGIS conference on April 7, 2011 in Heidelberg
  3. ↑ a b c mapproxy: CHANGES.txt

Web links