Django speaking WFS 2.0 (exposing GeoDjango model fields)
Django speaking WFS 2.0 to expose geo data.
- WFS 2.0 simple implementation.
- GML 3.2 output.
- GeoJSON export support.
- Extensible view/operations.
- Uses GeoDjango queries for filtering.
- Uses Django template engine for rendering XML (might become streaming lxml later).
Create a model that exposes a GeoDjango field:
from django.contrib.gis.db.models import PointField from django.db import models class Restaurant(models.Model): name = models.CharField(max_length=200) location = PointField(null=True) def __str__(self): return self.name
Write a view that exposes this model as a WFS feature:
from gisserver.features import FeatureType, ServiceDescription from gisserver.types import CRS, WGS84 from gisserver.views import WFSView from .models import Restaurant RD_NEW = CRS.from_string("urn:ogc:def:crs:EPSG::28992") class PlacesWFSView(WFSView): """An simple view that uses the WFSView against our test model.""" xml_namespace = "http://example.org/gisserver" # The service metadata service_description = ServiceDescription( title="Places", abstract="Unittesting", keywords=["django-gisserver"], provider_name="Django", provider_site="https://www.example.com/", contact_person="django-gisserver", ) # Each Django model is listed here as a feature. feature_types = [ FeatureType(Restaurant.objects.all(), other_crs=[RD_NEW]), ]
Use that view in the URLConf:
from django.urls import path from . import views urlpatterns = [ path("/wfs/places/", views.PlacesWFSView.as_view()), ]
You can now use http://localhost:8000/wfs/places/ in your GIS application. It will perform requests such as:
&OUTPUTFORMAT=geojson to the
GetFeature request, the GeoJSON output is returned.
Currently, the following 3 methods are implemented:
GetFeaturewith bbox and pagination support.
This is sufficient to show results in QGis. The unit tests validate the output against WFS 2.0 XSD schema.
Some parts for conformance to the "WFS simple" level are not implemented yet:
- Certain parameters:
- Remote resolving:
- Output rewriting:
GetFeaturewith only the
Filtering is high on the TO-DO list.
Anything outside WFS simple could be implemented, but is very low on the todo-list:
- The methods for the WFS basic, transactional, locking and inheritance conformance classes.
- HTTP POST requests.
- SOAP requests.
- Other protocols (WMS, WMTS, WCS)
- Other output formats (shapefile, CSV, KML, GML 3.1) - but easy to add.
When you follow the source of the
you'll find that it's written with extensibility in mind. Extra parameters and operations
can easily be added there. You could even do that within your own projects and implementations.
Makefile gives you all you need to start working on the project.
make gives an overview of all possible shortcut commands.
The WFS specification and examples be found at:
- https://www.opengeospatial.org/standards/ (all OGC standards)
- https://docs.opengeospatial.org/ (HTML versions)
- https://www.opengeospatial.org/standards/common (OGC Web Service Common)
- https://www.opengeospatial.org/standards/wfs#downloads (OGC WFS)
- https://portal.opengeospatial.org/files/09-025r2 (WFS 2.0 spec, PDF)
- https://portal.opengeospatial.org/files/09-026r1 (OpenGIS Filter Encoding 2.0, PDF)
- https://portal.opengeospatial.org/files/?artifact_id=20509 (GML 3.2.1)
- http://schemas.opengis.net/wfs/2.0/ (XSD and examples)
- https://cite.opengeospatial.org/teamengine/ (test suite)
- https://mapserver.org/development/rfc/ms-rfc-105.html (more examples)
Why this code is shared
The "datapunt" team of the Municipality of Amsterdam develops software for the municipality. Much of this software is then published as Open Source so that other municipalities, organizations and citizens can use the software as a basis and inspiration to develop similar software themselves. The Municipality of Amsterdam considers it important that software developed with public money is also publicly available.
This package is initially developed by the City of Amsterdam, but the tools and concepts created in this project can be used in any city.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size django_gisserver-0.2-py2.py3-none-any.whl (31.8 kB)||File type Wheel||Python version py2.py3||Upload date||Hashes View hashes|
|Filename, size django-gisserver-0.2.tar.gz (33.8 kB)||File type Source||Python version None||Upload date||Hashes View hashes|
Hashes for django_gisserver-0.2-py2.py3-none-any.whl