Is there a simple way to implement a wfs service based on the
geodjango models?
I want to serve information from the db as wfs and wfs-t to the user
agent. The reason why I am not using geoserver, mapserver or any other
of these is because I want to control the users right to some layers
and also control what information they see or modify from some
specific layer. As an example I want the user to be able to modify
only his or her own points on some layers.
Any ideas on how this can be done, or if there is already some
implementation for this?
regards
Kristoffer
The words "simple" and "WFS" probably shouldn't be used together in the
same sentence :)
To answer your question, while it's certainly possible to it, there's no
existing WFS application I know of. You could implement a subset of the
standard you need by using Django views and determining the appropriate
action based on the GET and POST parameters, but it would not be simple.
> I want to serve information from the db as wfs and wfs-t to the user
> agent. The reason why I am not using geoserver, mapserver or any other
> of these is because I want to control the users right to some layers
> and also control what information they see or modify from some
> specific layer. As an example I want the user to be able to modify
> only his or her own points on some layers.
>
> Any ideas on how this can be done, or if there is already some
> implementation for this?
>
While I'm not familiar with the gory details of the WFS standard, I do
know it's complicated. Moreover, GeoServer is _the_ reference
implementation for the WFS standard -- I'd look at a way of leveraging
its existing capabilities.
I'm just brainstorming here, but considering exploring options where
GeoServer and Django are used together on the same PostGIS DB. GeoServer
does the WFS lifting while Django could control authentication to
GeoServer services. If GeoServer creates tables in the database, it's
possible to introspect and use those within Django.
-Justin
A colleague of mine at GeoSolutions developed a hibernate based
catalog for geoserver, it's in trunk as a community module called
"hibernate", by default though, geoserver uses a xml based catalog. As
far as I know it has been tested with postgis and oracle as backends.
Plus, the OpenGeo guys also have done some django + geoserver stuff in
`Geonode <http://geonode.org>`_
Ariel Núñez // GeoSolutions S.A.S.
http://geo-solutions.it/