Re: [GRASS-dev] R in winGRASS

[Paulo van Breugel]

Hi Anna,

You need to define the path to R. I wrote a short explanation here:
https://pvanb.wordpress.com/2014/12/17/access-r-from-grass-gis-on-windows/

Hope that helps,

Paulo

On Mon, Mar 16, 2015 at 11:12 PM, Anna Petrášová 
wrote:

>
>
> On Mon, Mar 16, 2015 at 6:05 PM, Anna Petrášová 
> wrote:
>
>> Hi,
>>
>> I am having troubles with running R in winGRASS. I installed R using this
>> tutorial:
>>
>> http://www.r-bloggers.com/installing-rcpp-on-windows-7-for-r-and-c-integration/
>>
>> In normal windows command line, it works. In GRASS session, I get this
>> when running R:
>>
>> C:\Users\akratoc>R
>> '"\R.exe"' is not recognized as an internal or external command,
>> operable program or batch file.
>>
>> Any idea?
>>
>
> I just read on the wiki, you have to install R first, then GRASS, so I
> reinstalled GRASS, but still no success.
>
>>
>> Thank you
>>
>> Anna
>>
>>
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] R in winGRASS

[Anna Petrášová]

On Mon, Mar 16, 2015 at 6:05 PM, Anna Petrášová 
wrote:

> Hi,
>
> I am having troubles with running R in winGRASS. I installed R using this
> tutorial:
>
> http://www.r-bloggers.com/installing-rcpp-on-windows-7-for-r-and-c-integration/
>
> In normal windows command line, it works. In GRASS session, I get this
> when running R:
>
> C:\Users\akratoc>R
> '"\R.exe"' is not recognized as an internal or external command,
> operable program or batch file.
>
> Any idea?
>

I just read on the wiki, you have to install R first, then GRASS, so I
reinstalled GRASS, but still no success.

>
> Thank you
>
> Anna
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] R in winGRASS

[Anna Petrášová]

Hi,

I am having troubles with running R in winGRASS. I installed R using this
tutorial:
http://www.r-bloggers.com/installing-rcpp-on-windows-7-for-r-and-c-integration/

In normal windows command line, it works. In GRASS session, I get this when
running R:

C:\Users\akratoc>R
'"\R.exe"' is not recognized as an internal or external command,
operable program or batch file.

Any idea?

Thank you

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

[GRASS-dev] Fwd: [OSGeo-Discuss] OSGeo Google Summer of Code 2015: Students application period opens today

[Markus Neteler]

FYI

-- Forwarded message --
From: Margherita Di Leo 
Date: Mon, Mar 16, 2015 at 11:52 AM
Subject: [OSGeo-Discuss] OSGeo Google Summer of Code 2015: Students
application period opens today
To: OSGeo-SoC , OSGeo Discussions <
disc...@lists.osgeo.org>, ica-osgeo-l...@lists.osgeo.org


Dear All,

This is a gentle reminder that *student application period opens today*
[1]!

If you are a *student*, you can now start drafting your application in
melange. Do contact the developers of your chosen software, to make sure
you will have strong mentor support! Be sure you have read the
recommendations for students [2]

If you are a *mentor*, please create your profile in melange, then connect
with your organization (OSGeo) *indicating in the message for the admins
your project and the name of the idea(s) you are mentoring, together with
an email address that you wish to use with communication with the mentoring
organization*. Such data will be kept private and only handled by GSoC
admins. A plus is a link to a mail on public mailing lists, that show that
communication with the prospective student has started. Before applying as
a mentor, however, we encourage you to familiarize yourself with the guide
for mentors [3].

The *deadline* to students applications is *27th March*. [1]
Mentor registration will remain open until student acceptance.

Please forward this email to all relevant mailing lists of your knowledge.

Looking forward to see the first applications in Melange!
As usual, contact soc mailing list with your general questions about
application with OSGeo.


Your OSGeo GSoC admins,
Madi and Anne
https://www.youtube.com/watch?v=x43JNRR2yZY
http://en.wikipedia.org/wiki/Falles#La_Masclet.C3.A0


[1] https://www.google-melange.com/gsoc/events/google/gsoc2015
[2]
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students
[3]
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2015_Administrative#A_Mentor.27s_Responsibilities


-- 
Best regards,

Dr. Margherita DI LEO
Scientific / technical project officer

European Commission - DG JRC
Institute for Environment and Sustainability (IES)
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261

Tel. +39 0332 78 3600
margherita.di-...@jrc.ec.europa.eu

Disclaimer: The views expressed are purely those of the writer and may not
in any circumstance be regarded as stating an official position of the
European Commission.

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

Re: [GRASS-dev] [GRASS GIS] #2626: v.out.ogr does not suggest db.connect and db.login when not set

[GRASS GIS]

#2626: v.out.ogr does not suggest db.connect and db.login when not set
---+
 Reporter:  wenzeslaus |   Owner:  grass-dev@…  

 Type:  defect |  Status:  new  

 Priority:  normal |   Milestone:  7.1.0

Component:  Vector | Version:  svn-trunk

 Keywords:  PostgreSQL, postgres, PostGIS  |Platform:  Linux

  Cpu:  Unspecified|  
---+

Comment(by neteler):

 Small note: The error message comes from OGR, not GRASS GIS (here a random
 link to a similar problem: http://lists.osgeo.org/pipermail/gdal-
 dev/2012-November/034530.html).

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #2628: db.login does not ask for password as PostgreSQL database driver manual page says

[GRASS GIS]

#2628: db.login does not ask for password as PostgreSQL database driver manual
page says
+---
 Reporter:  wenzeslaus  |   Owner:  grass-dev@…  
 Type:  defect  |  Status:  new  
 Priority:  normal  |   Milestone:  7.1.0
Component:  Database| Version:  svn-trunk
 Keywords:  db.login, postgres  |Platform:  Linux
  Cpu:  Unspecified |  
+---

Comment(by neteler):

 Replying to [ticket:2628 wenzeslaus]:
 ...
 > I was not prompted for the password at any point. So it seems that
 either the manual page is wrong or `db.connect` does not work as expected.

 The interactive password prompting was removed in r32551. See also
 comment:6:ticket:1951

 > I think that I actually got the `db.tables` error message ("no password
 supplied") twice as presented above.
 >
 > Setting the password in command line works (but of course exposes the
 password in the bash history file).

 ... a major security flaw.

 > I don't think this is related to #2626 or #2627. I don't know if it is
 related to #1951.
 >
 > By the way, ''PostgreSQL DATABASE DRIVER'' title should be probably
 changed to ''PostgreSQL database driver'' (better typography, no reason
 for all uppercase).

 (Not sure where that is but please just fix it).

 BTW: see also #2147

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Compute mahalanobis distance using Scipy

[Paulo van Breugel]

Great, I'll do that



On Mon, Mar 16, 2015 at 9:56 PM, Pietro  wrote:

> Hi Paulo,
>
> On Mon, Mar 16, 2015 at 9:23 PM, Paulo van Breugel
>  wrote:
> >> Paulo van Breugel wrote:
> >> Alternatively, it might indicate an issue in the PyGrass library; that
> >> code is relatively new.
> >
> >
> > OK, hopefully the PyGrass gurus can have a look at it.
>
> Ofcourse I will look into it, but since I need two/three weeks, may be
> could a good idea to open a ticket on track, just to not forget this
> problem.
> Thank you for reporting this.
>
> Pietro
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Compute mahalanobis distance using Scipy

[Pietro]

Hi Paulo,

On Mon, Mar 16, 2015 at 9:23 PM, Paulo van Breugel
 wrote:
>> Paulo van Breugel wrote:
>> Alternatively, it might indicate an issue in the PyGrass library; that
>> code is relatively new.
>
>
> OK, hopefully the PyGrass gurus can have a look at it.

Ofcourse I will look into it, but since I need two/three weeks, may be
could a good idea to open a ticket on track, just to not forget this
problem.
Thank you for reporting this.

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

Re: [GRASS-dev] Compute mahalanobis distance using Scipy

[Paulo van Breugel]

On Mon, Mar 16, 2015 at 3:30 PM, Glynn Clements 
wrote:

>
> Paulo van Breugel wrote:
>
> > When running the tiled_function function you wrote [1] I am getting the
> > error below.
> >
> > {{{
> > tiled_function(raster_inputs=ref, raster_output="out_mah1",
> > func=mahalanobis_distances)
> > }}}
> >
> > ERROR: No null file for 
> >
> > Any idea what is wrong?
>
> That error message is from lib/raster, and indicates that the null
> file couldn't be created (Rast_open_new() should probably generate an
> error or warning if this happens; the fact that it doesn't suggests
> that it isn't a common occurrence).
>
> Were there any other warnings prior to that? Check the permissions on
> the mapset directory, the cell_misc subdirectory, and the
> cell_misc/out_mah1 subdirectory (if it exists).
>

No prior warnings, as far as I could see. Permissions on those folders are
OK. No cell_misc/out_mah1, but that makes sense I guess as that is the
raster file that should be created by the tiled_function.


>
> Alternatively, it might indicate an issue in the PyGrass library; that
> code is relatively new.
>

OK, hopefully the PyGrass gurus can have a look at it.

>
> --
> Glynn Clements 
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #2628: db.login does not ask for password as PostgreSQL database driver manual page says

[GRASS GIS]

#2628: db.login does not ask for password as PostgreSQL database driver manual
page says
+---
 Reporter:  wenzeslaus  |   Owner:  grass-dev@…  
 Type:  defect  |  Status:  new  
 Priority:  normal  |   Milestone:  7.1.0
Component:  Database| Version:  svn-trunk
 Keywords:  db.login, postgres  |Platform:  Linux
  Cpu:  Unspecified |  
+---
Changes (by martinl):

  * keywords:  postgres => db.login, postgres


-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] [GRASS GIS] #2628: db.login does not ask for password as PostgreSQL database driver manual page says

[GRASS GIS]

#2628: db.login does not ask for password as PostgreSQL database driver manual
page says
-+--
 Reporter:  wenzeslaus   |   Owner:  grass-dev@…  
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  7.1.0
Component:  Database | Version:  svn-trunk
 Keywords:  postgres |Platform:  Linux
  Cpu:  Unspecified  |  
-+--
 The ''PostgreSQL DATABASE DRIVER'' manual page
 (http://grass.osgeo.org/grass70/manuals/grass-pg.html) says:

 {{{
 # example for connecting to a PostgreSQL server:
 db.connect driver=pg database="host=myserver.osgeo.org,dbname=mydb"
 # password is asked interactively if not specified:
 db.login user=myname [pass=secret]
 db.connect -p
 db.tables -p
 }}}

 I noticed:
 {{{
 # password is asked interactively if not specified:
 }}}

 So I tried:

 {{{
 db.login user=docker
 }}}

 But then I got:

 {{{
 > db.connect -p
 driver: pg
 database: host=localhost,port=25432,dbname=gis
 schema:
 group:
 > db.tables -p
 DBMI-PostgreSQL driver error:
 Connection failed.
 fe_sendauth: no password supplied

 DBMI-PostgreSQL driver error:
 Connection failed.
 fe_sendauth: no password supplied
 }}}

 I was not prompted for the password at any point. So it seems that either
 the manual page is wrong or `db.connect` does not work as expected.

 I think that I actually got the `db.tables` error message ("no password
 supplied") twice as presented above.

 Setting the password in command line works (but of course exposes the
 password in the bash history file).

 I don't think this is related to #2626 or #2627. I don't know if it is
 related to #1951.

 By the way, ''PostgreSQL DATABASE DRIVER'' title should be probably
 changed to ''PostgreSQL database driver'' (better typography, no reason
 for all uppercase).

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] [GRASS GIS] #2627: v.out.postgis uses wrong database name or port

[GRASS GIS]

#2627: v.out.postgis uses wrong database name or port
---+
 Reporter:  wenzeslaus |   Owner:  grass-dev@…  

 Type:  defect |  Status:  new  

 Priority:  normal |   Milestone:  7.1.0

Component:  Default| Version:  svn-trunk

 Keywords:  PostgreSQL, postgres, PostGIS  |Platform:  Unspecified  

  Cpu:  Unspecified|  
---+
 After using `db.connect` and `db.login`:

 {{{
 db.connect driver=pg database="host=0.0.0.0,port=25432,dbname=gis"
 db.login user=docker password=docker
 }}}

 v.out.postgis uses wrong database name or port (or both) and then fails to
 connect to the database and then crashes or hangs.

 In the following reports I used `g.gisenv set=DEBUG=5` but the behavior is
 the same for no debug. Note the name of database in debug messages is once
 "grass", then NULL and then "grass" plus some unknown/non-printable
 character. It also seems that it calls the `read_file()` function twice.
 Finally, it mentions 5432 before it ends.

 Hangs:

 {{{
 D2/5: V1_open_new_pg(): name = busroutesall with_z = 0
 D1/5: V1_open_new_pg(): conninfo='dbname=grass' table='busroutesall'
 D3/5: db_get_login(): drv=[pg] db=[grass]
 D3/5: read_file(): DB login file = 
 D3/5: ret = 4 : drv=[pg] db=[host=localhost,port=25432,dbname=gis]
 usr=[docker] pwd=[docker]
 D3/5: db_get_login(): drv=[pg] db=[(null)]
 D3/5: read_file(): DB login file = 
 D3/5: ret = 4 : drv=[pg] db=[host=localhost,port=25432,dbname=gis]
 usr=[docker] pwd=[docker]
 D1/5:PQconnectdb(): dbname=grass user=docker password=docker
 ERROR: Connection to PostgreSQL database failed. Try to set up
username/password by db.login.
could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.5432"?
 D1/5: Vect_close(): name = busroutesall, mapset = PERMANENT, format = 0,
 level = 2, is_tmp = 0
 D1/5: spatial index file closed
 D1/5: close history file
 D1/5: V1_close_nat(): name = busroutesall mapset= PERMANENT
 D1/5: file_handler: PG_27099
 D2/5: G_file_name(): path = /grassdata//nc_spm/postgis_test1/PG_27099
 }}}

 Aborted with "free(): invalid pointer":

 {{{
 D2/5: V1_open_new_pg(): name = busroutesall with_z = 0
 D1/5: V1_open_new_pg(): conninfo='dbname=grass' table='busroutesall'
 D3/5: db_get_login(): drv=[pg] db=[grass]
 D3/5: read_file(): DB login file = 
 D3/5: ret = 4 : drv=[pg] db=[host=localhost,port=25432,dbname=gis]
 usr=[docker] pwd=[docker]
 D3/5: db_get_login(): drv=[pg] db=[(null)]
 D3/5: read_file(): DB login file = 
 D3/5: ret = 4 : drv=[pg] db=[host=localhost,port=25432,dbname=gis]
 usr=[docker] pwd=[docker]
 D1/5:PQconnectdb(): dbname=grass user=docker password=docker
 ERROR: Connection to PostgreSQL database failed. Try to set up
username/password by db.login.
could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.5432"?
 D1/5: Vect_close(): name = busroutesall, mapset = PERMANENT, format = 0,
 level = 2, is_tmp = 0
 D1/5: spatial index file closed
 D1/5: close history file
 D1/5: V1_close_nat(): name = busroutesall mapset= PERMANENT
 D1/5: file_handler: PG_27257
 D2/5: G_file_name(): path = /grassdata//nc_spm/postgis_test1/PG_27257
 dbmi: Protocol error
 * Error in `v.out.postgis': free(): invalid pointer: 0x7f6fed3977e8 *
 Aborted (core dumped)
 }}}

 Segmentation fault:

 {{{
 D2/5: V1_open_new_pg(): name = busroutesall with_z = 0
 D1/5: V1_open_new_pg(): conninfo='dbname=grass' table='busroutesall'
 D3/5: db_get_login(): drv=[pg] db=[grass]
 D3/5: read_file(): DB login file = 
 D3/5: ret = 4 : drv=[pg] db=[host=localhost,port=25432,dbname=gis]
 usr=[docker] pwd=[docker]
 D3/5: db_get_login(): drv=[pg] db=[(null)]
 D3/5: read_file(): DB login file = 
 D3/5: ret = 4 : drv=[pg] db=[host=localhost,port=25432,dbname=gis]
 usr=[docker] pwd=[docker]
 D1/5:PQconnectdb(): dbname=grass user=docker password=docker
 ERROR: Connection to PostgreSQL database failed. Try to set up
username/password by db.login.
could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.5432"?
 D1/5: Vect_close(): name = busroutesall, mapset = PERMANENT, format = 0,
 level = 2, is_tmp = 0
 D1/5: spatial index file closed
 D1/5: close history file
 D1/5: V1_close_nat(): name = busroutesall mapset= PERMANENT
 D1/5: file_handler: PG_27267
 D2/5: G_file_name(): path = /grassd

[GRASS-dev] [GRASS GIS] #2626: v.out.ogr does not suggest db.connect and db.login when not set

[GRASS GIS]

#2626: v.out.ogr does not suggest db.connect and db.login when not set
---+
 Reporter:  wenzeslaus |   Owner:  grass-dev@…  

 Type:  defect |  Status:  new  

 Priority:  normal |   Milestone:  7.1.0

Component:  Vector | Version:  svn-trunk

 Keywords:  PostgreSQL, postgres, PostGIS  |Platform:  Linux

  Cpu:  Unspecified|  
---+
 When there is no connection set using `db.connect` or authentication using
 `db.login`, `v.out.ogr` does not say what's wrong. Instead a misleading
 (?) error about database creation is shown:

 {{{
 $ v.out.ogr in=lakes@PERMANENT output=PG:dbname=gis format=PostgreSQL
 type=area
 ERROR 1: PQconnectdb failed.
 could not connect to server: No such file or directory
 Is the server running locally and accepting
 connections on Unix domain socket
 "/var/run/postgresql/.s.PGSQL.5432"?

 ERROR 1: PostgreSQL driver doesn't currently support database creation.
 Please create database with the `createdb' command.
 ERROR: Unable to open OGR data source 'PG:dbname=gis'
 }}}

 Executing `db.connect` and `db.login` actually does not solve the problem
 for me: `db.tables -p` lists tables but `v.out.ogr` still says the same. I
 suppose this might be my problem, I might have misinterpreted the manual,
 but in any case the initial message is wrong.

 The special thing about my environment is that I'm using PostgreSQL
 database in a Docker container from
 [https://registry.hub.docker.com/u/kartoza/postgis/ kartoza/postgis]. I
 used their steps to run it and `psql` works for me (in GRASS session):

 {{{
 psql -h localhost -U docker -p 25432 -l
 }}}

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte

[Helmut Kudrnovsky]

>I tested winGRASS r64873, no problems with English locale, I switched to
German too, still no problems.

interesting:

_no_ problems with commands like e.g.:

g.region
g.mapset
g.access
g.gisenv
g.extension

problems with commands like e.g.:

r.slope.aspect
d.vect
r.watershed
r.neigbhours
v.parallel
...

any idea?





-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/utf8-codec-can-t-decode-byte-0xf6-in-position-8-invalid-start-byte-tp5193488p5193653.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #2625: r.stats's nsteps is not region-sensitive

[GRASS GIS]

#2625: r.stats's nsteps is not region-sensitive
-+--
 Reporter:  martinl  |   Owner:  grass-dev@…  
 Type:  defect   |  Status:  new  
 Priority:  major|   Milestone:  7.0.1
Component:  Raster   | Version:  svn-trunk
 Keywords:  r.stats, nsteps  |Platform:  Unspecified  
  Cpu:  Unspecified  |  
-+--
 `r.stat's nsteps` option is not region-sensitive, in other words ranges
 are calculated from original raster, not from current region. It can be
 very confusing for a user, I am not sure if it's a bug or just
 undocumented behaviour.

 OK, I get 5 classes:

 {{{
 g.region rast=elevation
 r.stats elevation nsteps=5 --q
 55.578793-75.729007
 75.729007-95.879221
 95.879221-116.029436
 116.029436-136.17965
 136.17965-156.329865
 }}}

 Smaller number of classes when using sub-region:

 {{{
 g.region n=219326.524155 s=218357.261131 w=635573.588429 e=637027.482965
 -a
 r.stats elevation nsteps=5 --q
 75.729007-95.879221
 95.879221-116.029436
 116.029436-136.17965
 }}}

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte

[Helmut Kudrnovsky]

> I tested winGRASS r64873, no problems with English locale, I switched to
German too, still no problems.

tested with

System Info 
GRASS Version: 7.1.svn  
GRASS SVN revision: 64873   
Build date: 2015-03-16  
Build platform: i686-pc-mingw32 
GDAL: 1.11.2
PROJ.4: 4.8.0   
GEOS: 3.4.2 
SQLite: 3.7.17  
Python: 2.7.4   
wxPython: 2.8.12.1  
Platform: Windows-7-6.1.7601-SP1 (OSGeo4W)  

'utf8' codec can't decode error still there.

also tested with 

System Info 
GRASS Version: 7.0.0
GRASS SVN Revision: 64706   
Erstellungsdatum: 2015-01-20  

in the same OSGeo4W-stack, no problem there.



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/utf8-codec-can-t-decode-byte-0xf6-in-position-8-invalid-start-byte-tp5193488p5193649.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte

[Anna Petrášová]

I tested winGRASS r64873, no problems with English locale, I switched to
German too, still no problems.

Anna

On Sun, Mar 15, 2015 at 6:33 PM, Helmut Kudrnovsky  wrote:

> hi,
>
> tested with
>
> GRASS Version: 7.1.svn
> GRASS SVN revision: 64858
> Build date: 2015-03-15
> Build platform: i686-pc-mingw32
> GDAL: 1.11.2
> PROJ.4: 4.8.0
> GEOS: 3.4.2
> SQLite: 3.7.17
> Python: 2.7.4
> wxPython: 2.8.12.1
> Platform: Windows-7-6.1.7601-SP1 (OSGeo4W)
>
> a ms windows error message window:
>
> 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte
>
> <
> http://osgeo-org.1560.x6.nabble.com/file/n5193488/utf_codec_error_15032015_232313.png
> >
>
> pops up when invoking e.g.
>
> d.vect
> r.slope.aspect
> ...
>
> and following error message:
>
> Traceback (most recent call last):
>   File "C:\OSGEO4~2\apps\grass\grass-7.1.svn\gui\wxpython\gu
> i_core\forms.py", line 2054, in OnUpdateDialog
>
> self.parent.updateValuesHook()
>   File "C:\OSGEO4~2\apps\grass\grass-7.1.svn\gui\wxpython\gu
> i_core\forms.py", line 628, in updateValuesHook
>
> self.SetStatusText('
> '.join(self.notebookpanel.createCmd(ignoreErrors = True)))
> TypeError
>
>
>
> -
> best regards
> Helmut
> --
> View this message in context:
> http://osgeo-org.1560.x6.nabble.com/utf8-codec-can-t-decode-byte-0xf6-in-position-8-invalid-start-byte-tp5193488.html
> Sent from the Grass - Dev mailing list archive at Nabble.com.
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Compute mahalanobis distance using Scipy

[Glynn Clements]

Paulo van Breugel wrote:

> When running the tiled_function function you wrote [1] I am getting the
> error below.
> 
> {{{
> tiled_function(raster_inputs=ref, raster_output="out_mah1",
> func=mahalanobis_distances)
> }}}
> 
> ERROR: No null file for 
> 
> Any idea what is wrong?

That error message is from lib/raster, and indicates that the null
file couldn't be created (Rast_open_new() should probably generate an
error or warning if this happens; the fact that it doesn't suggests
that it isn't a common occurrence).

Were there any other warnings prior to that? Check the permissions on
the mapset directory, the cell_misc subdirectory, and the
cell_misc/out_mah1 subdirectory (if it exists).

Alternatively, it might indicate an issue in the PyGrass library; that
code is relatively new.

-- 
Glynn Clements 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #2622: Text interface quits immediately when run from zsh shell

[GRASS GIS]

#2622: Text interface quits immediately when run from zsh shell
-+--
 Reporter:  zimmi|   Owner:  grass-dev@…  
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  7.0.1
Component:  Startup  | Version:  6.4.4
 Keywords:  zsh  |Platform:  Unspecified  
  Cpu:  x86-64   |  
-+--

Comment(by martinl):

 Replying to [comment:6 zimmicz]:
 > GRASS 7.1 comes from official repo? I'm using zsh 5.0.2 that might be
 the difference.

 well, it depends what you mean by "official", there are Launchpad builds
 (1) recommended on official project pages (2).

 (1) https://launchpad.net/~grass/+archive/ubuntu/grass-devel
 (2) http://grass.osgeo.org/download/software/linux/#g71x

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #2620: r.neighbours should offer to ignore centre value

[GRASS GIS]

#2620: r.neighbours should offer to ignore centre value
--+-
 Reporter:  marisn|   Owner:  grass-dev@…  
 Type:  enhancement   |  Status:  new  
 Priority:  minor |   Milestone:  7.0.1
Component:  Raster| Version:  7.0.0
 Keywords:  r.neighbours  |Platform:  Unspecified  
  Cpu:  Unspecified   |  
--+-

Comment(by glynn):

 Replying to [comment:3 marisn]:

 > Second - it is not possible to use weights and circular neighbourhood at
 the same time (documentation states: "The -c flag and the weights
 parameter are mutually exclusive.")

 More accurately, it is not possible to use weight= and an automatically-
 generated mask (either the circular mask generated by -c or the Gaussian
 mask generated by gauss= or the square mask generated in the absence of
 any other applicable option). Nothing prevents weight= from being used to
 supply a circular mask.

 However, any automatically-generated mask (whether square, circular or
 Gaussian) is simply a short-cut whose behaviour could also be obtained by
 passing the appropriate mask via weight=. So the question isn't about
 what's possible, but what's possible without providing an explicit weights
 file.

 There's no end to the set of masks which could be generated internally;
 the only question is which ones are common enough to warrant a short-cut.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #2622: Text interface quits immediately when run from zsh shell

[GRASS GIS]

#2622: Text interface quits immediately when run from zsh shell
-+--
 Reporter:  zimmi|   Owner:  grass-dev@…  
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  7.0.1
Component:  Startup  | Version:  6.4.4
 Keywords:  zsh  |Platform:  Unspecified  
  Cpu:  x86-64   |  
-+--

Comment(by zimmicz):

 GRASS 7.1 comes from official repo? I'm using zsh 5.0.2 that might be the
 difference.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS-user] v.out.ogr dialog ask for user to type entire output path

[Martin Landa]

Hi,

2015-03-16 13:47 GMT+01:00 Daniel Victoria :
> In the 'Name of output OGR datasource' field, the user has to type the
> entire path, which some times can be quite long. Of course I can copy/paste
> the output path but couldn't we have a directory or file chooser dialog
> there?

the problem with datasource is that it could be a file, database, ...
It's the main reason why the option has no hardcoded type. But I agree
with you, it should be improved. One option would be to write a
similar front-end as already exists for v.in.ogr or v.external.out (it
could be good starting point for v.out.ogr). But it requires some time
and programming (any volunteer here?) or to change option type to
G_OPT_F_OUTPUT (file). This option will still enables to type eg. PG
datasource (PostGIS). Another option which came to my mind is to
change form.py to use GDALSelect widget directly. It would be the best
option I would say.

Martin

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

Re: [GRASS-dev] [GRASS GIS] #2624: r.horizon problem in Windows (horizon_zud)

[GRASS GIS]

#2624: r.horizon problem in Windows (horizon_zud)
--+-
 Reporter:  rorschach |   Owner:  grass-dev@…   
   
 Type:  defect|  Status:  new   
   
 Priority:  normal|   Milestone:  7.0.1 
   
Component:  Raster| Version:  7.0.0 
   
 Keywords:  r.horizon, grass70, wingrass  |Platform:  MSWindows 8   
   
  Cpu:  Unspecified   |  
--+-
Changes (by rorschach):

  * keywords:  r.horizon, grass70, grass, windows => r.horizon, grass70,
   wingrass


-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] [GRASS GIS] #2624: r.horizon problem in Windows (horizon_zud)

[GRASS GIS]

#2624: r.horizon problem in Windows (horizon_zud)
+---
 Reporter:  rorschach   |   Owner:  grass-dev@… 
 
 Type:  defect  |  Status:  new 
 
 Priority:  normal  |   Milestone:  7.0.1   
 
Component:  Raster  | Version:  7.0.0   
 
 Keywords:  r.horizon, grass70, grass, windows  |Platform:  MSWindows 8 
 
  Cpu:  Unspecified |  
+---
 I think that r.horizon does not create multiple raster maps when used in
 raster mode in Windows.

 *Note: I am using a dual-booted PC (Ubuntu 14.04 and Windows 8.1)

 I ran r.horizon on Windows 8.1 using GRASS 7.0.0. During runtime, it kept
 on showing angle: X raster:  instead of the usual angle: X
 raster: horizon_X when being run on Ubuntu.

 When looking at the mapset, only 1 map named horizon_zud was added when
 running r.horizon on Windows compared to the multiple horizon_X maps when
 the command is ran on Ubuntu.

 Also, when using r.horizon as an input for r.sun, the results I got on
 Windows and Ubuntu where different. This should not have been the case
 considering I used the same dataset and input parameters for r.sun and
 r.horizon.

 Lastly, when I ran r.sun on Ubuntu using the location and mapset
 (including the r.horizon results) I created using GRASS 7.0.0 on Windows,
 it tells me that the horizon maps are not found.

 These things lead me to believe that r.horizon does not create multiple
 raster maps on Windows.

-- 
Ticket URL: 
GRASS GIS 

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