Skip to main content

Django speaking WFS 2.0 (exposing GeoDjango model fields)

Project description

Travis PyPI MPL License Coverage

django-gisserver

Django speaking WFS 2.0 to expose geo data.

Features

  • WFS 2.0 simple implementation.
  • GML 3.2 output.
  • Standard and spatial filtering (FES 2.0)
  • GeoJSON export support.
  • Extensible view/operations.
  • Uses GeoDjango queries for filtering.
  • Streaming responses for large datasets.

Usage

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.geometries 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(),
            fields="__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:

By adding &OUTPUTFORMAT=geojson to the GetFeature request, the GeoJSON output is returned.

NOTE: by default, the minimum number of model fields are exposed as WFS attributes. Use FeatureType(..., fields=[...]) parameter to define which fields should be exposed.

Customization hooks

There are a few places that allow to customize the WFS logic:

  • Overriding methods from WFSView, such as get_feature_types() or dispatch() for authorization.
  • Subclassing the FeatureType class, to override it's get_queryset() method.
  • Registering new FES functions to gisserver.parsers.fes_function_registry.
  • Registering new stored procedures to gisserver.queries.stored_query_registry.

Debugging questions

  • The error "Operation on mixed SRID geometries" often indicates the table SRID differs from the GeometryField(srid=..) configuration in Django.

Standards compliance

Nearly all operations for the WFS simple conformance class are implemented. You should be able to view the WFS server QGis. The unit tests validate the output against WFS 2.0 XSD schema.

Some remaining parts for the "WFS simple" conformance level are not implemented yet:

  • KVP filters: propertyName, aliases, namespaces.
  • Remote resolving: resolve, resolveDepth, resolveTimeout.
  • Some GetCapabilities features: acceptFormats and sections.
  • Temporal filtering (high on todo)

Low-prio items:

Anything outside WFS simple could be implemented, but is very low on the todo-list:

  • The methods for the WFS 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.

Development

When you follow the source of the WFSView, WFSMethod and Parameter classes, 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.

A lot of the internal classes and object names are direct copies from the WFS spec. By following these type definitions, a lot of the logic and code structure follows naturally.

The Makefile gives you all you need to start working on the project. Typing make gives an overview of all possible shortcut commands.

The WFS specification and examples be found at:

Some deeplinks:

Other links:

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.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

django-gisserver-0.8.tar.gz (67.4 kB view hashes)

Uploaded Source

Built Distribution

django_gisserver-0.8-py2.py3-none-any.whl (84.0 kB view hashes)

Uploaded Python 2 Python 3

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page