Django WMS Framework
The Django WMS Framework is a toolkit that makes it easy to build a Web Map Service (WMS) or a x-y-z Tile Map Service. Rendering of both vector and raster data formats are supported.
For complete documentation please go to http://django-wms.readthedocs.org
Requirements
The processing of spatial data in django-wms relies on MapServer and its python bindings MapScript. Raster data integration depends on the django-raster package. The use of PostGIS as the database backend is required as well, for raster ntegration PostGIS >= 2.0 is required (see also django-raster package).
Installation
Install package with pip install django-wms
Add “wms” to your INSTALLED_APPS setting like this:
INSTALLED_APPS = ( ... 'wms', )
Example
To create a mapping service, subclass the django-wms layer, map and view classes and connect them to an existing model in django that has a spatial field (such as Point, Polygon or MultiPolygon). An example wms_config.py module could be specified as follows
### wms_config.py
# Load django-wms classes
from wms import maps, layers, views
# Load model with spatial field (Point, Polygon or MultiPolygon)
from myapp.models import MySpatialModel
# Subclass the WmsVectorLayer class and point it to a spatial model.
# Use WmsRasterLayer for rasters
class MyWmsLayer(layers.WmsVectorLayer):
model = MySpatialModel
# Subclass the WmsMap class and add the layer to it
class MyWmsMap(maps.WmsMap):
layer_classes = [ MyWmsLayer ]
# Subclass the WmsView to create a view for the map
class MyWmsView(views.WmsView):
map_class = MyWmsMap
With the WmsView subclass in place, the only thing left to do to create a functional map service is to hook the view into a url. An example url configuration urls.py could be
### urls.py
# Import the wms view
from myproject.wms_config import MyWmsView
# Add url patterns to setup map services from the view
urlpatterns = patterns('',
# This creates a WMS endpoint
url(r'^wms/$', MyWmsView.as_view(), name='wms'),
# This creates a TMS endpoint
url(r'^tile/(?P<layers>[^/]+)/(?P<z>[0-9]+)/(?P<x>[0-9]+)/(?P<y>[0-9]+)(?P<format>\.jpg|\.png)$',
MyWmsView.as_view(), name='tms'),
)
The django-wms package will automatically detect the first spatial field it can find in MySpatialModel and create a WMS endpoint from the class based view. If the three arguments x, y and z are found in the urlpattern, the view functions as TMS endpoint.
Metadata
Release files for django-wms 0.1.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django-wms-0.1.12.tar.gz | 9.3 kB | Without provenance | Details for django-wms-0.1.12.tar.gz |
Release files / django-wms-0.1.12.tar.gz
| Download URL | django-wms-0.1.12.tar.gz |
|---|---|
| Size | 9.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
94825dbe6e934b4da98063cb3be2f29cf2242bd70f2e091f0e80cf3d41d81bc5
|
|
BLAKE2b-256 checksum How to use checksums |
c359e0b78a875879171ba9edd29b41fb3d18e07092ac972fe5619cd8d1099f17
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-wms 0.1.12
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.