Dear Geoserver development team,
I contact you to ask you advice on the procedure to add code examples in the GeoServer online documentation on how to interact with the REST API by means of the R software.
Indeed i’ve been developing an R package called geosapi (https://github.com/eblondel/geosapi/wiki) that is used as R interface to the GeoServer REST API.
It is not robust as the equivalent Java geoserver-manager, but geosapi already offers a range of operations, including CRUD operations for workspaces, namespaces, datastores, featuretypes, layers and styles, as well as the methods to upload data to Geoserver. geosapi still miss the features to manipulate coverage stores, but I hope this will come soon. The R package also follows a clear testing procedure, with regular integration tests, and it is already under release lifecycle for the official CRAN packages repository (https://cran.r-project.org/package=geosapi).
Although there is extensive documentation on geosapi, both online and through the embedded R document, I believe it could be valuable to add some entry point through the Geoserver documentation here http://docs.geoserver.org/latest/en/user/rest/index.html
Looking forward to your advice,
Best regards,
Emmanuel
Hi,
happy to see more clients for the configuration REST API showing up 
I think examples based on geosapi could fit well in this page:
http://docs.geoserver.org/latest/en/user/rest/index.html#examples
Right now we have “Examples”, and they are all curl based… maybe the easiest thing is to rename those into “CURL Examples”
and add a new section with links to “geosapi” examples. Let’s hear if others have alternative proposals on where to place it.
About the mechanics of the contribution, the documentation is written using Sphinx and part of GeoServer sources, here:
https://github.com/geoserver/geoserver/tree/master/doc/en/user/source/rest
So, a PR would be the way to contribute changes to it.
Cheers
Andrea
···
Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.
Thank you Andrea for your answer. I will be waiting for more feedback from your others.
I had a look to the doc, but i’ve seen there is not yet documentation for Java code (aka geoserver-manager, i’m not aware of another library…).
The R geosapi works in a similar way as the Java geoserver-manager, it’s object-oriented and requires to instantiate a “manager” to work with it. Similarly, R geosapi has several “managers” depending on the resource you want to manage (workspace, datastore, style, etc), but wraps all manager functions into a single ‘GSManager’. This is the class to instantiate to access to all functions to manage the different kind of resources.
The point is how/where in the documentation we should give the piece of code to instantiate such manager… Somehow it sounds we miss a 1st section, on which then the other resource-specific sections could be based on … Any thought?
Having participated into the devs of geoserver-manager, i would also be keen to contribute to its documentation in the meantime I would do it for geosapi…
Cheers
Emmanuel
···
Le 04/10/2018 à 11:13, Andrea Aime a écrit :
Hi,
happy to see more clients for the configuration REST API showing up
I think examples based on geosapi could fit well in this page:
http://docs.geoserver.org/latest/en/user/rest/index.html#examples
Right now we have “Examples”, and they are all curl based… maybe the easiest thing is to rename those into “CURL Examples”
and add a new section with links to “geosapi” examples. Let’s hear if others have alternative proposals on where to place it.
About the mechanics of the contribution, the documentation is written using Sphinx and part of GeoServer sources, here:
https://github.com/geoserver/geoserver/tree/master/doc/en/user/source/rest
So, a PR would be the way to contribute changes to it.
Cheers
Andrea
On Thu, Oct 4, 2018 at 11:08 AM Emmanuel Blondel (GMAIL) <emmanuel.blondel1@anonymised.com> wrote:
Dear Geoserver development team,
I contact you to ask you advice on the procedure to add code examples in the GeoServer online documentation on how to interact with the REST API by means of the R software.
Indeed i’ve been developing an R package called geosapi (https://github.com/eblondel/geosapi/wiki) that is used as R interface to the GeoServer REST API.
It is not robust as the equivalent Java geoserver-manager, but geosapi already offers a range of operations, including CRUD operations for workspaces, namespaces, datastores, featuretypes, layers and styles, as well as the methods to upload data to Geoserver. geosapi still miss the features to manipulate coverage stores, but I hope this will come soon. The R package also follows a clear testing procedure, with regular integration tests, and it is already under release lifecycle for the official CRAN packages repository (https://cran.r-project.org/package=geosapi).
Although there is extensive documentation on geosapi, both online and through the embedded R document, I believe it could be valuable to add some entry point through the Geoserver documentation here http://docs.geoserver.org/latest/en/user/rest/index.html
Looking forward to your advice,
Best regards,
Emmanuel
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.