[GeoNode-devel] QGIS <-> GeoNode Integration

[Simone Dalmasso]

Thanks Tim for the summary and for the very cool work!

I have one comment about APIs, the current /layers /maps API are flat,
meaning they don't include data of other database tables then layers_layer
and maps_map, the reason of this was to keep (make) them fast to feed the
geonode search page. I agree that there should be more comprehensive API
even if maybe a bit slower so we can definitely add new ones like
*layer-full* and *maps-full*. Actually we have already something like this
for resource owners.

Ciao!

2017-04-26 17:20 GMT+02:00 Tim Sutton <tim at kartoza.com>:

> Hi All
>
> I just wanted to show you some of the work we have been doing to integrate
> QGIS Desktop and GeoNode. I made a little video which illustrates it here:
>
> https://www.youtube.com/watch?v=z0WYsEUNmg4
>
> This work was funded by WorldBank  / GFDRR. We expect to make a pull
> request against QGIS to merge this work next week some time.
>
> There have been previous attempts to integrate GeoNode support into QGIS
> but ours is a bit different as it is implemented in C++ and will be
> 'native' / baked in code that every QGIS user can make use of without
> needing to install any plugins etc. We will also create python bindings for
> the helper classes so that you can use the GeoNode backend logic in your
> own QGIS plugins if you want to without re-inventing the wheel.
>
> My colleague, Gavin, has previously written to this list to provide a
> broad outline of our work plans. One of the pain points we have had while
> working on this functionality is the GeoNode API. Our implementation
> basically consisted of hopping around between the GeoNode API and GeoNode's
> CSW instance. This diagram summarizes the process we follow:
>
> https://files.gitter.im/kartoza/kartoza/ucRq/GeoNodeArchitecture.png
>
> We had to do a lot of hoop jumping to get valid layer end points and we
> would like to implement some changes to the API to make it less of a pain.
> Our first tentative doodling on how the API can be improved are here:
>
> https://files.gitter.im/kartoza/kartoza/YxLa/GeoNodeArchitecture-API.png
>
> We would make any changes as non breaking changes (unless people are using
> really crapping parsing techniques to pull data out of the API responses) -
> adding to some existing responses, and adding new API end points to support
> pushing and pulling styles and so on. I expect we will add more to the
> above diagram, consider it a first draft only. Is anyone else working on
> things that might affect the API / planning changes to the API? If so could
> we collaborate with you so that we can see what is coming down the line?
> Our work will probably be split between:
>
> a) a few specific changes we need to execute our work.
> b) a proposal of what other things might be improved in the API for future
>
> I look forward to hearing from anyone else who is interested in QGIS /
> GeoNode integration and GeoNode API improvements.
>
> Regards
>
> Tim
>
>
>
> —
>
>
>
>
>
>
>
>
>
> *Tim Sutton*
>
> *Co-founder:* Kartoza
> *Project chair:* QGIS.org
>
> Visit 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
>
> Kartoza is a merger between Linfiniti and Afrispatial
>
>
> _______________________________________________
> geonode-devel mailing list
> geonode-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geonode-devel
>
>


-- 
Simone
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20170502/ebc0069d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: KartozaNewLogoThumbnail.jpg
Type: image/jpeg
Size: 6122 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20170502/ebc0069d/attachment-0001.jpg>