Hi Radim and friends

What you have built sounds really cool! Is my understanding correct that with 
eventual read/write support the idea is that a user connecting via QGIS PostGIS 
connection would have equivalent permissions to a user created in Django auth, 
so could for example directly edit a feature in QGIS via PG connection, in QGIS 
via WFS-T connection or edit a feature in Django via e.g. OpenLayers WFS-T 
connect to QGIS or in Django via django forms?

If that is the goal that sounds really great! Or do some of the above use cases 
not apply?

Regards

Tim

> On 25 Oct 2018, at 09:26, Radim Blazek <[email protected]> wrote:
> 
> We (MPA Solutions, www.mpasolutions.it) wrote a Django provider for
> QGIS (read only, no editing for now)
> https://github.com/MPASolutions/django-provider. It is proof of
> concept but it works.
> 
> It contains a small test Django project with simple wms Django view
> based on QgsServer, so it should be easy for you to test it. The
> vector provider in Python requires QGIS master(?), I think.
> 
> Any contribution is welcome, especially the write access (i.e.
> AddFeatures, DeleteFeatures, ChangeGeometries, ChangeAttributeValues),
> which would enable the editing chain QGIS Desktop <-> WFS-T <-> QGIS
> Server <-> Django provider <-> Django (<-> PostGIS).
> 
> Radim
> On Wed, Oct 10, 2018 at 8:19 AM Pēteris Brūns <[email protected]> wrote:
>> 
>> 
>> ---- On Mon, 08 Oct 2018 22:27:42 +0300 Radim Blazek 
>> <[email protected]> wrote ----
>> 
>> On Mon, Oct 8, 2018 at 8:47 PM Pēteris Brūns <[email protected]> wrote:
>>> 
>>> Hi all,
>>> 
>>> Pretty long time ago in similar case we developed django app able to 
>>> replicate django user and group permissions to PostgreSQL roles and 
>>> permissions. So each user can use the same user name and passowrd in WEB 
>>> client and using QGIS/PostgreSQL, manage permissions in django auth app and 
>>> the same will be replicated in postgresql. Each model is table and django 
>>> permissions are translated to PostgreSQL role permissions - implementation 
>>> works also with m2m and related models.
>>> 
>>> In basic cases such model is OK, but ir more complex implementations we 
>>> loose logic build around model in django or need to repeat it in QGIS or 
>>> move to PostgreSQL.
>> 
>> This is exactly what we also end up with and what we would like to
>> liberate from for the reasons you mentioned. Thank you anyway, at
>> least we know that we are not crazy alone.
>> 
>> 
>> You are not alone! And if you come to some good idea let us know. We would 
>> be happy to hear and review opportunity to contribute or contribute with 
>> funding of such functionality.
>> 
>> BTW, contextually not exact but similar case is file/attachment upload from 
>> QGIS to server using, for example RESTful API. Year ago, in Nodebo, we 
>> discussed such functionality with Mathias and Marco.
>> 
>> Peteris
>> 
>> Radim
>> 
>> 
>>> If this sounds as suitable approach, I believe, we could try to review the 
>>> code and make open source.
>>> 
>>> Best,
>>> --
>>> Pēteris Brūns
>>> SunGIS
>>> +371 26336691
>>> [email protected]
>>> 
>>> 
>>> ---- On Fri, 05 Oct 2018 23:54:07 +0300 Olivier Dalang 
>>> <[email protected]> wrote ----
>>> 
>>> Hi Radim,
>>> 
>>> I didn't get this sorted in the end (ended just having the layer as read 
>>> only in QGIS from postgis and users would do any modification from django 
>>> admin).
>>> 
>>> About a Django provider for QGIS : it is now possible to create python 
>>> providers [1]. So creating a REST provider to consume a django rest 
>>> framework endpoint may not be that hard anymore ? That would certainly be a 
>>> great addition to QGIS !!
>>> 
>>> And about a WFS-T app for Django : I don't know of any other effort than 
>>> django-wfs, but I just saw there's an open PR with some a lot of changed 
>>> including python 3 support, so maybe django-wfs is not as dead as it looks 
>>> ? Still WFS-T would have to be added, and again not sure how hard this 
>>> would be...
>>> 
>>> Let us know how it goes !
>>> 
>>> Cheers,
>>> 
>>> Olivier
>>> 
>>> [1] https://github.com/qgis/QGIS/pull/7012
>>> 
>>> 
>>> 
>>> On Sat, Oct 6, 2018 at 4:24 AM Radim Blazek <[email protected]> wrote:
>>> 
>>> Hi,
>>> we need the same, to be precise, we need two things, to allow editing
>>> of data stored in Django/PostGIS in QGIS over the network and let QGIS
>>> Server (WMS) to read data from Django, both using Django filters etc.
>>> If we manage to get data to QGIS from Django (and back), we can use
>>> QGIS Server and WFS-T for editing. So I am looking for something like
>>> Django provider for QGIS or WFS-T application for Django. Are you
>>> aware of something like that?
>>> 
>>> Olivier, what have you used in the end? [1] is not maintained and it
>>> does not support WFS-T.
>>> 
>>> Alessandro, in [2] I am missing data reading from Django models. It
>>> seems like the server is launched from python, but data flow goes
>>> through standard QGIS providers?
>>> 
>>> Marco, if I got it looking briefly into GeoNode code, they just run
>>> QGIS server, but they don't read data directly from Django models,
>>> right?
>>> 
>>> [1] https://github.com/vascop/django-wfs
>>> [2] http://www.itopen.it/qgis-server-binding-news/lang-pref/en/
>>> 
>>> Radim
>>> 
>>> On Fri, Mar 24, 2017 at 1:56 PM Marco Bernasocchi <[email protected]> wrote:
>>>> 
>>>> Hi Olivier
>>>> Kartoza has been working on having geonode server running smoothly using
>>>> a qgis server in the background.
>>>> 
>>>> have a look at
>>>> https://www.youtube.com/watch?v=GzX4byPkV3E
>>>> http://osgeo-org.1560.x6.nabble.com/New-Geonode-GeoSAFE-and-QGIS-work-td5303864.html
>>>> 
>>>> cheers
>>>> Marco
>>>> 
>>>> On 24.03.2017 13:10, Olivier Dalang wrote:
>>>>> Dear List,
>>>>> 
>>>>> Does anybody here have some experience with making QGIS work with
>>>>> (Geo)Django ?
>>>>> 
>>>>> I would love to be able to make them communicate, as QGIS is the
>>>>> interface of choice to do complex work on geometries and Django is
>>>>> perfect to quickly setup a complete endpoint with user management, model
>>>>> logic and web administration interface.
>>>>> 
>>>>> I see two approches :
>>>>> - Using Django REST framework to create a REST endpoint - but is there a
>>>>> way to consume REST endpoints in QGIS ?
>>>>> - Developing a WFST module for Django, for which there seem to be some
>>>>> work done [1] for the non-transactionnal part.
>>>>> 
>>>>> I just wanted to ask before reinventing the wheel !
>>>>> 
>>>>> Bests,
>>>>> 
>>>>> Olivier
>>> 
>>> _______________________________________________
>>> QGIS-Developer mailing list
>>> [email protected]
>>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> 
>>> 
>>> 
>> 
>> 
>> 
> _______________________________________________
> QGIS-Developer mailing list
> [email protected]
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

—








Tim Sutton

Co-founder: Kartoza
Ex Project chair: QGIS.org

Visit http://kartoza.com <http://kartoza.com/> to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux 
IRC: timlinux on #qgis at freenode.net

_______________________________________________
QGIS-Developer mailing list
[email protected]
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Reply via email to