Re: [GRASS-dev] Managing the translations with Transifex

[Markus Neteler]

On Sun, May 7, 2017 at 7:14 PM, Markus Neteler  wrote:
> Hi,
>
> AFAIK we are still not feeding back the .po files updates from
> transifex into SVN.
> While this could become a cronjob on grass.osgeo.org, there are still
> some issues to be solved.
>
> I found that
> grass-addons/tools/transifex_merge.sh
>
> empties all "fuzzy" state messages. Good or bad?

... checking again it doesn't look so bad.

I have now
- renamed grass*_pt_br.po to grass*_pt_BR.po for transifex
compatibility (all G7 branches + trunk)
- updated grass-addons/tools/transifex_merge.sh to fix the headers of
newly arrived translations (r71124)
- added newly arrived translations in r71121 (came in from transifex)

TODO:
- upload many translations fetched through that transifex_merge.sh
script to SVN.

Objections?

Markus


-- 
Markus Neteler, PhD
http://www.mundialis.de - free data with free software
http://grass.osgeo.org
http://courses.neteler.org/blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Helmut Kudrnovsky]

Paul Schrum wrote
> I started off trying to build it in a directory under my home directory
> using the instructions here
> ;,
> but I could not get it to build.  The only part of those instructions that
> I was not following were the path.  So I started using the paths indicated
> in those instructions and then it would build.  That is why my copy of the
> source is where it is.
> 
> Based on yall's comments, I now think it was something other than the path
> where I was storing the source code, but I have no idea what.

please post here your steps and error (?)/warning(?) messages of compiling.




-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Gaining-write-privileges-to-usr-local-and-subdirectories-tp5321487p5321504.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Paul Schrum]

I started off trying to build it in a directory under my home directory
using the instructions here
,
but I could not get it to build.  The only part of those instructions that
I was not following were the path.  So I started using the paths indicated
in those instructions and then it would build.  That is why my copy of the
source is where it is.

Based on yall's comments, I now think it was something other than the path
where I was storing the source code, but I have no idea what.


On Tue, May 23, 2017 at 11:33 AM, Moritz Lennert <
mlenn...@club.worldonline.be> wrote:

> On 23/05/17 17:21, Martin Landa wrote:
>
>> Hi,
>>
>> 2017-05-23 17:12 GMT+02:00 Paul Schrum :
>>
>>> In following the directions to build grass7_trunk, I put the source under
>>> /usr/local/src/grass7_trunk, and now everything I do which modifies
>>> anything
>>> must be preceeded with sudo.  I would like to eliminate this requirement
>>> for
>>> day-to-day work.
>>>
>>
>> chown [1], chmod [2]. Martin
>>
>> [1] http://www.linfo.org/chown.html
>> [2] http://man.cat-v.org/plan_9/1/chmod
>>
>
> Even though these commands do the job, I would not recommend it. Just put
> your entire src tree somewhere into your $HOME directory. No need to have
> it in /usr/local.
>
> Moritz
>
>
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Helmut Kudrnovsky]

Paul Schrum wrote
> Is there a way I can give myself privileges in my own usr/local to write
> to
> it and its subdirectories?
> 
> In following the directions to build grass7_trunk, I put the source under
> /usr/local/src/grass7_trunk, and now everything I do which modifies
> anything must be preceeded with sudo.  I would like to eliminate this
> requirement for day-to-day work.

here on my debian, I put the grass source code in my /home/ directory [1]
and do there all my coding and compiling. maybe not the best practice, but
no chown/chmod needed.

[1] https://wiki.debian.org/FilesystemHierarchyStandard




-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Gaining-write-privileges-to-usr-local-and-subdirectories-tp5321487p5321498.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Moritz Lennert]

On 23/05/17 17:21, Martin Landa wrote:

Hi,

2017-05-23 17:12 GMT+02:00 Paul Schrum :

In following the directions to build grass7_trunk, I put the source under
/usr/local/src/grass7_trunk, and now everything I do which modifies anything
must be preceeded with sudo.  I would like to eliminate this requirement for
day-to-day work.


chown [1], chmod [2]. Martin

[1] http://www.linfo.org/chown.html
[2] http://man.cat-v.org/plan_9/1/chmod


Even though these commands do the job, I would not recommend it. Just 
put your entire src tree somewhere into your $HOME directory. No need to 
have it in /usr/local.


Moritz



___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Martin Landa]

Hi,

2017-05-23 17:12 GMT+02:00 Paul Schrum :
> In following the directions to build grass7_trunk, I put the source under
> /usr/local/src/grass7_trunk, and now everything I do which modifies anything
> must be preceeded with sudo.  I would like to eliminate this requirement for
> day-to-day work.

chown [1], chmod [2]. Martin

[1] http://www.linfo.org/chown.html
[2] http://man.cat-v.org/plan_9/1/chmod

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Paul Schrum]

Is there a way I can give myself privileges in my own usr/local to write to
it and its subdirectories?

In following the directions to build grass7_trunk, I put the source under
/usr/local/src/grass7_trunk, and now everything I do which modifies
anything must be preceeded with sudo.  I would like to eliminate this
requirement for day-to-day work.

Thanks.

- Paul
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Need help in writing a program in Grass GIS

[pablo zader]

Hi CM,
You can use:
http://grasswiki.osgeo.org/wiki/GRASS_Python_Scripting_Library

Or,

https://grass.osgeo.org/grass70/manuals/libpython/pygrass_index.html





El 23/5/2017 11:12 a. m., "Luca Delucchi"  escribió:

On 21 May 2017 at 20:03, CM Reddy  wrote:
> Hi All,

Hi,

> I am new to GIS and GRASS also. We would like to use the GRASS source and
> implement the following features.
>
> Import a shape file.
> Select a start location and end location in the map. Connect start and end
> locations with some intermediate points. Each point or location should
> uniquely identified with lat and long.
> Associate predefined properties for each identified point.
> Store the each location and it's properties in a data base.
>
> We would like to implement the above feature as additional menu in the
> existing toolbar. We would like to implement required dialog boxes or UI
> panel to display lat and long assocaited with identified locations. GUI
> should has the provision to enter properties for each location. Finally,
we
> need to store them in DB after clicking a SAVE button.
>
> I request your help in building the above application. I have already
> downloaded and compiled the GRASS 7.2 on ubuntu successfully.
>
> How to extend the current GRASS application ?

GRASS is composed by singular modules, so it is quiet simple to extent

> How to build the supporting the GUI ?

https://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/README
https://trac.osgeo.org/grass/browser/grass/trunk/gui/
wxpython/xml/menudata.README

> Can I write a python script to build the above application ?

yes

> What are the modules to be written ?
>

probably none, I think all modules you need are already in GRASS

> - Thanks
>
> CM
>


--
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Need help in writing a program in Grass GIS

[Luca Delucchi]

On 21 May 2017 at 20:03, CM Reddy  wrote:
> Hi All,

Hi,

> I am new to GIS and GRASS also. We would like to use the GRASS source and
> implement the following features.
>
> Import a shape file.
> Select a start location and end location in the map. Connect start and end
> locations with some intermediate points. Each point or location should
> uniquely identified with lat and long.
> Associate predefined properties for each identified point.
> Store the each location and it's properties in a data base.
>
> We would like to implement the above feature as additional menu in the
> existing toolbar. We would like to implement required dialog boxes or UI
> panel to display lat and long assocaited with identified locations. GUI
> should has the provision to enter properties for each location. Finally, we
> need to store them in DB after clicking a SAVE button.
>
> I request your help in building the above application. I have already
> downloaded and compiled the GRASS 7.2 on ubuntu successfully.
>
> How to extend the current GRASS application ?

GRASS is composed by singular modules, so it is quiet simple to extent

> How to build the supporting the GUI ?

https://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/README
https://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/xml/menudata.README

> Can I write a python script to build the above application ?

yes

> What are the modules to be written ?
>

probably none, I think all modules you need are already in GRASS

> - Thanks
>
> CM
>


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [OSGeo-Discuss] FOSS4G 2017 Boston Code Sprint

[Vaclav Petras]

[forwarded from osgeo-discuss]

Code Sprint in Boston, August 19th:

https://wiki.osgeo.org/wiki/FOSS4G_2017_Code_Sprint

Add yourself and topics if you are coming.

Best,
Vaclav

-- Forwarded message --
From: Regina Obe 
Date: Sun, May 21, 2017 at 3:23 AM
Subject: [OSGeo-Discuss] FOSS4G 2017 Boston Code Sprint
To: [...]


As with all FOSS4G conferences, we'll be having a code sprint the day after
the conference.

The code sprint is free of charge, though you will need to arrange your own
accommodations.

The code sprint will be held Saturday August 19th 2017 right after the 2017
FOSS4G Boston Conference.

If you'd like to attend, please add your name to the list below so we can
plan accordingly.  Also feel free to spread the word.


https://wiki.osgeo.org/wiki/FOSS4G_2017_Code_Sprint#Code_Sprint


Thanks,
Regina Obe
Boston LOC Committee member







___
Discuss mailing list
disc...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] PostGIS layer import

[Markus Neteler]

On Tue, May 23, 2017 at 11:34 AM, Moritz Lennert
 wrote:
> On 19/05/17 22:31, Markus Metz wrote:
>> On Thu, May 18, 2017 at 12:59 PM, Markus Neteler >> On Wed, May 17, 2017 at 3:03 PM, Markus Metz
>>> > On Wed, May 17, 2017 at 9:31 AM, Moritz Lennert
...
>>> Just a side-note: I would be very happy to not store the password in
>>> the cmd line history. PG itself supports a password file
>>> (https://www.postgresql.org/docs/9.6/static/libpq-pgpass.html).
>>>
>>> Please keep any password hiding option(s) in mind when working on the
>>> design.
>>
>> Apparently such a password file is recognized by the PostgreSQL client
>> library, therefore no special mechanism should be needed for OGR or
>> GRASS, but a hint in the manuals of db.login and v.in.ogr might be
>> helpful.
>
> Just as a feedback: I just tried v.in.ogr with
>
> v.in.ogr "PG:host=thehost dbname=thedb user=theuser"  layer=thetable
> out=mymap
>
> and a .pgpass file entry as such:
>
> thehost:5432:thedb:theuser:thepasswd
>
> and it works like a charm.

Cool!
Likely also valid for v.out.ogr when writing to PG (?).

> Is login info really useful for other drivers than pg and mysql ? Maybe we
> should look into deprecating db.login and telling people to use the .pgpass
> / .mylogin.cnf files ?

I'd be quite in favor since db.login writes a central file (rather
than mapset specific files) only which prevents the user from
connecting to several databases.

> If we want to keep a tool such as db.login it should probably work with a
> password prompt that doesn't show the password on the command line.

strong +1.

Apparently it would be sufficient to add text/example snippets in the
manual pages about the .pgpass and  .mylogin.cnf files ?

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] PostGIS layer import

[Moritz Lennert]

On 19/05/17 22:31, Markus Metz wrote:



On Thu, May 18, 2017 at 12:59 PM, Markus Neteler mailto:nete...@osgeo.org>> wrote:


On Wed, May 17, 2017 at 3:03 PM, Markus Metz
mailto:markus.metz.gisw...@gmail.com>>

wrote:

> On Wed, May 17, 2017 at 9:31 AM, Moritz Lennert
...
>> I would, therefore, expect to just be able to do this:
>>
>> v.in.ogr "PG:host=myhost user=theuser password=thepassword
>> dbname=thedatabase" layer=theschema.thetable out=mygrassmap
>
> I agree

Just a side-note: I would be very happy to not store the password in
the cmd line history.
PG itself supports a password file
(https://www.postgresql.org/docs/9.6/static/libpq-pgpass.html).

Please keep any password hiding option(s) in mind when working on the

design.

Apparently such a password file is recognized by the PostgreSQL client
library, therefore no special mechanism should be needed for OGR or
GRASS, but a hint in the manuals of db.login and v.in.ogr might be helpful.


Just as a feedback: I just tried v.in.ogr with

v.in.ogr "PG:host=thehost dbname=thedb user=theuser"  layer=thetable 
out=mymap


and a .pgpass file entry as such:

thehost:5432:thedb:theuser:thepasswd

and it works like a charm.

Is login info really useful for other drivers than pg and mysql ? Maybe 
we should look into deprecating db.login and telling people to use the 
.pgpass / .mylogin.cnf files ?


If we want to keep a tool such as db.login it should probably work with 
a password prompt that doesn't show the password on the command line.


Moritz
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev