Re: [GRASS-dev] Issue with db.execute: error altering a PostGIS table

Hi, 2017-05-25 7:37 GMT+02:00 Markus Neteler : > The situation is that user ${TARGETDB_USER_TEST_ADMIN} has the > permission to see schema "test". This user is the only one who may you need to have at least select permission on schema where PostGIS functions lives (usually

Re: [GRASS-dev] G7 helptext: replace Fig. 1: GRASS GIS 7 location structure with new figure

Hi, 2017-05-25 7:15 GMT+02:00 Markus Neteler : > often confuses users while > https://grasswiki.osgeo.org/wiki/File:Grass_database.png > > is so much better! Could we exchange that somehow? +1 Ma -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa

Re: [GRASS-dev] G7 helptext: replace Fig. 1: GRASS GIS 7 location structure with new figure

On 25 May 2017 at 07:15, Markus Neteler wrote: > Hi Vaclav, > Hi, > IMHO "Fig. 1: GRASS GIS 7 location structure" in > https://grass.osgeo.org/grass72/manuals/help_loc_struct.png > https://grass.osgeo.org/grass72/manuals/helptext.html > > (master: doc/help_loc_structure.odg)

Re: [GRASS-dev] Implement a REST API for GRASS

Hi Moritz, On Wed, May 24, 2017 at 3:31 PM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > - first of all: is build a REST API for GRASS a stupid idea? should we >> use/promote just the WPS? >> > > > Well, what is your argument agains WPS ? Why do you think a REST API is > necessary /

Re: [GRASS-dev] Implement a REST API for GRASS

I assume that both are equally dangerous. My opinion is that GRASS GIS should not be exposed to any non trustable users, as various smaller and larger bugs are too common. Unless, of course, it runs inside a throw-away VM. 2017-05-25 10:33 GMT+03:00 Pietro : > Dear Māris, >

Re: [GRASS-dev] Issue with db.execute: error altering a PostGIS table

2017-05-25 8:26 GMT+02:00 Martin Landa : >> The situation is that user ${TARGETDB_USER_TEST_ADMIN} has the >> permission to see schema "test". This user is the only one who may > > you need to have at least select permission on schema where PostGIS > functions lives

Re: [GRASS-dev] Implement a REST API for GRASS

Dear Māris, On Wed, May 24, 2017 at 8:52 PM, Maris Nartiss wrote: > GRASS GIS code has never been developed with security in mind. I would > not suggest to run it in a non-trustable environment. > Do you think that expose some GRASS modules through a REST API can be more

Re: [GRASS-dev] Gaining write privileges to usr/local and subdirectories

Paul Schrum wrote > Going by > https://grasswiki.osgeo.org/wiki/Compile_and_Install_Ubuntu#GRASS_GIS and > focusing on GRASS GIS 7 trunk: > > 1. Last week I did > > svn co https://svn.osgeo.org/grass/grass/trunk grass7_trunk > > On a directory under my ownership. > > 2. Today in that same

Re: [GRASS-dev] Implement a REST API for GRASS

Seen this: https://bitbucket.org/huhabla/open-graas? Cheers Stefan Von: grass-dev [grass-dev-boun...@lists.osgeo.org] im Auftrag von Maris Nartiss [maris@gmail.com] Gesendet: Donnerstag, 25. Mai 2017 09:42 An: Pietro Cc: GRASS developers list Betreff:

Re: [GRASS-dev] Implement a REST API for GRASS

2017-05-25 10:24 GMT+02:00 Blumentrath, Stefan : > Seen this: https://bitbucket.org/huhabla/open-graas? Sorry, that shouldn't be public available. Please ignore this implementation. Cheers Sören > Cheers > Stefan > > Von:

Re: [GRASS-dev] G7 helptext: replace Fig. 1: GRASS GIS 7 location structure with new figure

On Thu, May 25, 2017 at 1:15 AM, Markus Neteler wrote: > IMHO "Fig. 1: GRASS GIS 7 location structure" in > https://grass.osgeo.org/grass72/manuals/help_loc_struct.png > https://grass.osgeo.org/grass72/manuals/helptext.html > > (master: doc/help_loc_structure.odg) > > often