I am hoping to revitalise the QGIS Network API plugin project that I mentored for GSoC last year - it needs porting to QGIS3 and probably some more documentation.
For anyone who doesn't know it, it makes QGIS expose a network API service so that clients can call defined QGIS functions. So using the R client API you can get data from live QGIS layers, or send R spatial objects to QGIS as new layers. code: https://gitlab.com/qgisapi docs: https://qgisapi.gitlab.io/ bugs: plenty Barry On Fri, Apr 27, 2018 at 1:09 AM, Nyall Dawson <nyall.daw...@gmail.com> wrote: > On 26 April 2018 at 22:10, Barry Rowlingson > <b.rowling...@lancaster.ac.uk> wrote: > > As a long-time R spatial developer and QGIS user I'll be glad to help > out - > > but time-poor at work for now. "Helping out" may be more like "making > > unreasonable suggestions" and "finding annoying bugs". > > Don't undersell yourself... these would be very valuable contributions! > > > For example, can we find a more efficient way to transfer data from QGIS > to > > R? Can the new `sf` packages in R work with the data straight out of > QGIS' > > memory? I *think* the `sf` package stores vector data in GDALs native C++ > > objects, and if QGIS is doing that too then we *might* be able to get > access > > from QGIS and R if we write the R plugin as a C/C++ module that > dynamically > > links with the shareable libR.so. > > I've (very roughly) looked into this, and I also believe it should be > possible to directly create R data frames from QGIS layers. Then we'd > just need to add a "R console" to QGIS, and boom! Awesome spatial > statistical analysis tool directly within QGIS! > > Nyall > > > > > The current R processing plugin converts QGIS layers to shapefiles, > reads > > them into a new R process. On occasion I've hit problems with shapefile > > limitations (field name length, usually) that make my scripts fail. > Maybe it > > should go via geopackage instead. > > > > Should it create `sp` objects on the R side or `sf` objects? This could > be > > controllable in the R processing script headers, so it can be set on a > > per-script basis. > > > > I'll stop now... > > > > Barry > > > > > > > > > > > > > > On Thu, Apr 26, 2018 at 9:42 AM, Aurelio Pires <anvpi...@gmail.com> > wrote: > >> > >> +1 > >> > >> Thanks, > >> > >> > >> On 2018-04-26 07:40, Paolo Cavallini wrote: > >> > Hi all, > >> > > >> > Il 26/04/2018 05:08, Nyall Dawson ha scritto: > >> >> I'm VERY interested in seeing this resurrected. I'm available to > >> >> mentor this task if someone else wants to take ownership of the > plugin > >> >> and do the port, OR alternatively I'd be happy for North Road to do > >> >> the porting ourselves and take over maintenance if someone can fund > >> >> this work. > >> > that's good news. So starting a crowdfunding campaign seems a good way > >> > to go, unless there is a bigger sponsor; do you agree? > >> > All the best, and thanks. > >> > > >> > >> _______________________________________________ > >> QGIS-Developer mailing list > >> QGIS-Developer@lists.osgeo.org > >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > > > > > _______________________________________________ > > QGIS-Developer mailing list > > QGIS-Developer@lists.osgeo.org > > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer