Re: [GRASS-dev] [GRASS GIS] #2618: v.category option=transfer does not copy multiple cat values
#2618: v.category option=transfer does not copy multiple cat values -+- Reporter: ulf | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.0.1 Component: Vector |Version: 7.0.0 Resolution: | Keywords: v.category transfer CPU: x86-64 | Platform: Linux -+- Comment (by wenzeslaus): I added the commands as a Bash test case in r65485 but I actually don't understand what the output means here (why it is the same for `layer=1` and `layer=2`?) and what `option=transfer` does. It would be good if somebody can review it and/or comment in the test. Side note: The Bash script tests (test cases, test files) are really easy to create. Just look at r65485. They have a lot of problems and the solution is not scalable but it is better than no test! -- Ticket URL: https://trac.osgeo.org/grass/ticket/2618#comment:4 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Fwd: Re: [GRASS GIS] #2692: v.in.ascii does not handle text in qoutes
Glynn,
Could you just take a look at the patch and say whether this is an
acceptable hack ?
Moritz
Forwarded Message
Subject: Re: [GRASS GIS] #2692: v.in.ascii does not handle text in qoutes
Date: Sun, 14 Jun 2015 12:18:09 -
From: GRASS GIS t...@osgeo.org
Reply-To: grass-dev@lists.osgeo.org
To: undisclosed-recipients:;
#2692: v.in.ascii does not handle text in qoutes
-+-
Reporter: wenzeslaus | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.1
Component: Default |Version: svn-trunk
Resolution: | Keywords: CSV, doublequote, singlequote, text
CPU: | delimiter
Unspecified| Platform: Unspecified
-+-
Comment (by mlennert):
Replying to [comment:1 mlennert]:
Replying to [ticket:2692 wenzeslaus]:
Since r63581 G7:v.in.ascii should be able to handle CSV with quoted
text fields (`text` option) but the quotes are stored to the database.
This is the result from `v.db.select` (same thing in `sqliteman`):
{{{
100|437343.6704|4061363.41525|High Erosion|Low Deposition
}}}
IIUC, this comes from
[https://trac.osgeo.org/grass/browser/grass/trunk/lib/gis/token.c#L107
this part of lib/gis/token.c]. The p++ just advances the pointer like for
any other character. I guess that in order to skip it, one would have to
create a second pointer which takes a copy of the first, but advances only
when the first one is not equal to the character you want to eliminate. Or
something like that. But my pointer foo is much too low to handle this
directly. Anyone more C-savy who could do this in 5 minutes ?
The attached patch seems to solve the problem for me, but it feels like a
quick fix and there probably is a better way...
Moritz
--
Ticket URL: https://trac.osgeo.org/grass/ticket/2692#comment:2
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2692: v.in.ascii does not handle text in qoutes
#2692: v.in.ascii does not handle text in qoutes
-+-
Reporter: wenzeslaus | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.1
Component: Default |Version: svn-trunk
Resolution: | Keywords: CSV, doublequote, singlequote, text
CPU: | delimiter
Unspecified| Platform: Unspecified
-+-
Comment (by glynn):
Replying to [comment:2 mlennert]:
The attached patch seems to solve the problem for me, but it feels like
a quick fix and there probably is a better way...
Simply removing the quotes isn't sufficient to support CSV. It's necessary
to treat the field separator as a normal character when it occurs within a
quoted field (that's the point of using quotes), and also to replace two
consecutive quotes with a single quote (so that the quote character itself
can occur within a field).
For that, an explicit state machine is likely to be more legible than ad-
hoc logic.
Off the top of my head:
{{{
classes: delimiter, separator, newline, other
states: start, in_quote, after_quote, error
actions: no_op, add_char, new_field, end_record, error
start,delimiter - in_quote,no_op
start,separator - start,new_field
start,newline - start,end_record
start,other - start,add_char
in_quote,delimiter - after_quote,no_op
in_quote,separator - in_quote,add_char
in_quote,newline - error,error
in_quote,other - in_quote,add_char
after_quote,delimiter - in_quote,add_char
after_quote,separator - start,new_field
after_quote,newline - start,end_record
after_quote,other - error,error
}}}
--
Ticket URL: https://trac.osgeo.org/grass/ticket/2692#comment:3
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2309: Add a select all flag to v.edit
#2309: Add a select all flag to v.edit --+--- Reporter: wenzeslaus | Owner: grass-dev@… Type: enhancement | Status: new Priority: trivial | Milestone: 7.1.0 Component: Vector |Version: svn-trunk Resolution: | Keywords: v.edit, feature selection CPU: Unspecified | Platform: All --+--- Comment (by wenzeslaus): Replying to [comment:1 mlennert]: I've attached a patch that provides a very simplistic approach to a select all flag. Thanks. However, reflection is needed on the following questions: * Should the flag select all features, regardless of whether they have a category number of not ? * If not should the flag select only features that have category numbers in a given layer ? In the example in the original report, the `layer` option is used to specify the layer to write the categories to, so it cannot be used for selection, so there is no given layer. And since there is no given layer, there is no way to determine if the features have category or not. So for me the answer for both questions is select regardless of existing category. This will do well for simple cases, I'm not sure if there are any complicated cases when a more sophisticated approach would be appropriate. -- Ticket URL: https://trac.osgeo.org/grass/ticket/2309#comment:3 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Debugging QGIS with GRASS provider on Windows
Hi, I need to debug QGIS GRASS provider on Windows. I have successfully compiled GRASS 7 using MinGW [1] and QGIS using MSVC [2]. The problem is that MSVC does not support GCC debugging symbols and vice versa. Do you have any idea how to debug both QGIS and GRASS code at the same time, preferably in MSVC or Qt Creator? Is there any recent effort to compile GRASS with MSVC? I have only found quite an old mail about MSVC port [3]. Radim [1] https://trac.osgeo.org/grass/wiki/CompileOnWindows [2] https://htmlpreview.github.io/?https://github.com/qgis/QGIS/blob/master/doc/INSTALL.html#toc12 [3] http://lists.osgeo.org/pipermail/grass-dev/2007-November/034108.html ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Debugging QGIS with GRASS provider on Windows
On Tue, Jun 16, 2015 at 2:01 PM, Radim Blazek radim.bla...@gmail.com wrote: Hi, I need to debug QGIS GRASS provider on Windows. I have successfully compiled GRASS 7 using MinGW [1] and QGIS using MSVC [2]. The problem is that MSVC does not support GCC debugging symbols and vice versa. Do you have any idea how to debug both QGIS and GRASS code at the same time, preferably in MSVC or Qt Creator? Is there any recent effort to compile GRASS with MSVC? I have only found quite an old mail about MSVC port [3]. There is an exploratory effort to use CMake for GRASS GIS [1] but there is a lack of CMake experts with free time. In theory this is one of the steps to compile GRASS with MSVC. Isn't it possible to easily compile QGIS with MinGW thanks to CMake (since GCC is used on other platforms)? Vaclav [1] https://github.com/starseeker/grass Radim [1] https://trac.osgeo.org/grass/wiki/CompileOnWindows [2] https://htmlpreview.github.io/?https://github.com/qgis/QGIS/blob/master/doc/INSTALL.html#toc12 [3] http://lists.osgeo.org/pipermail/grass-dev/2007-November/034108.html ___ 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] [GRASS GIS] #2648: v.concave.hull fails with small number of points
#2648: v.concave.hull fails with small number of points
--+--
Reporter: annakrat | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.1
Component: Addons |Version: unspecified
Resolution: | Keywords: concave hull
CPU: Unspecified | Platform: All
--+--
Comment (by annakrat):
Replying to [comment:1 mlennert]:
Could you provide a reproducible test case ?
{{{
echo 638597|220531
638838|220526
638757|220237
638695.0|220410.0 | v.in.ascii in=- out=points
v.concave.hull input=points out=hull
}}}
--
Ticket URL: https://trac.osgeo.org/grass/ticket/2648#comment:2
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2349: CELL raster format: make ZLIB level 3 standard compression instead of RLE
#2349: CELL raster format: make ZLIB level 3 standard compression instead of RLE --+--- Reporter: neteler | Owner: grass-dev@… Type: enhancement | Status: new Priority: critical | Milestone: 7.1.0 Component: Raster |Version: svn-trunk Resolution: | Keywords: compression, r.compress, null CPU: Unspecified | Platform: All --+--- Comment (by glynn): Replying to [comment:34 glynn]: I added some support for the improved r.null/r.compress functionality to lib/raster With r65489, r65490, and r65491, r.null and r.support should work with compressed nulls. r.null now has a -z flag to re-create the null file using the current compression setting (i.e. compress/decompress). -- Ticket URL: https://trac.osgeo.org/grass/ticket/2349#comment:38 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS] #2696: Set language in GRASS-7.0.0
#2696: Set language in GRASS-7.0.0 --+- Reporter: Biz | Owner: grass-dev@… Type: defect| Status: new Priority: normal| Milestone: 7.0.1 Component: Default |Version: 7.0.0 Keywords: Set language |CPU: Unspecified Platform: MSWindows 7 | --+- Hi, I have not reported software difficulties before so apologies if I am doing it wrong. I did see this issue reported following a normal google search, but I could not see how to plus one the report. I have pasted the message here in case it helps too. -- Hi, 2015-02-25 15:49 GMT+01:00 Venkatesh Raghavan raghavan at media.osaka- cu.ac.jp: GException Traceback (most recent call last): File C:\Program Files (x86)\GRASS GIS 7.0.0\gui\wxpython\gui_core\preferences.py, line 178, in OnSave self.settings.SaveToFile() File C:\Program Files (x86)\GRASS GIS 7.0.0\gui\wxpython\core\settings.py, line 1032, in SaveToFile 'detail' : e }) core.gcmd . GException Any suggestions for fixing this? hm, I cannot reproduce this error on Czech Windows (switching from Czech to English). So probably it could be related to JP environment (?) ... Martin -- Martin Landa --- I too have the issue on my Japanese work computer. I have most programs/desktop set to English, but the system itself is still Japanese. I installed WinGRASS-7.0.0-1-Setup (was not able to install the example data with it though), and opened the program from the desktop shortcut. Some parts of the opening windows were in Japanese, I clicked the button to open the program proper (using the default locations etc), found the setting to change the language and saved as en. I closed the windows but when I reopened the program, the language was still Japanese (system). I have included the error below and the system info. Unfortunately I can't read much Japanese so navigating a program I am also unfamiliar with is a bit beyond my capabilities. I would really appreciate any help with this, and please let me know if I can provide more useful information. --- Traceback (most recent call last): File C:\Program Files\GRASS GIS 7.0.0\gui\wxpython\gui_core\preferences.py, line 178, in OnSave self.settings.SaveToFile() File C:\Program Files\GRASS GIS 7.0.0\gui\wxpython\core\settings.py, line 1032, in SaveToFile 'detail' : e }) core.gcmd . GException System Info GRASS version: 7.0.0 GRASS SVN Revision: 64706 Build Date: 2015-01-20 Build Platform: i686-pc-mingw32 GDAL/OGR: 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 --- -- Ticket URL: http://trac.osgeo.org/grass/ticket/2696 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2634: 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte
#2634: 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte ---+- Reporter: hellik| Owner: grass-dev@… Type: defect| Status: new Priority: critical | Milestone: 7.0.1 Component: Default |Version: svn-trunk Resolution:| Keywords: utf, wxgui CPU: x86-32| Platform: MSWindows 7 ---+- Changes (by hellik): * milestone: 7.1.0 = 7.0.1 -- Ticket URL: https://trac.osgeo.org/grass/ticket/2634#comment:4 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2634: 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte
#2634: 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte
---+-
Reporter: hellik| Owner: grass-dev@…
Type: defect| Status: new
Priority: critical | Milestone: 7.0.1
Component: Default |Version: svn-trunk
Resolution:| Keywords: utf, wxgui
CPU: x86-32| Platform: MSWindows 7
---+-
Comment (by hellik):
it's also now in the 7.0.1RC1, tested in the NC sample dataset
{{{
System Info
GRASS Version: 7.0.1RC1
GRASS SVN Revision: 65472
Erstellungsdatum: 2015-06-15
Build Platform: i686-pc-mingw32
GDAL/OGR: 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)
}}}
choosing d.rast from the wxgui
a MS error box pops up with
{{{
'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte
}}}
followed by this message in the wxgui
{{{
Traceback (most recent call last):
File C:\OSGEO4~2\apps\grass\grass-7.0.1RC1\gui\wxpython\g
ui_core\forms.py, line 2023, in OnUpdateDialog
self.parent.updateValuesHook()
File C:\OSGEO4~2\apps\grass\grass-7.0.1RC1\gui\wxpython\g
ui_core\forms.py, line 628, in updateValuesHook
self.SetStatusText('
'.join(self.notebookpanel.createCmd(ignoreErrors = True)))
TypeError
}}}
as mentioned in the original ticket above, e.g. g.region works without any
problem
any ideas?
--
Ticket URL: https://trac.osgeo.org/grass/ticket/2634#comment:5
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] wingrass build not available
Martin Landa wrote 2015-06-16 10:13 GMT+02:00 Helmut Kudrnovsky lt; hellik@ gt;: oh, https://trac.osgeo.org/grass/ticket/2634 is now also in the 7.0.1.RC1. so, it's blocker now? Ma I would say yes. any idea what to test before change to blocker? - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/wingrass-build-not-available-tp5208115p5211171.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] [GRASS GIS] #2634: 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte
#2634: 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte
---+-
Reporter: hellik| Owner: grass-dev@…
Type: defect| Status: new
Priority: critical | Milestone: 7.0.1
Component: Default |Version: svn-trunk
Resolution:| Keywords: utf, wxgui
CPU: x86-32| Platform: MSWindows 7
---+-
Comment (by marisn):
Replying to [comment:7 hellik]:
Replying to [comment:6 hellik]:
language is set following:
GUI preferences - language - system
ok, I switched the language to englisch:
{{{
GUI preferences - language - en
}}}
this error disappears.
maybe some error in the translation?
Haven't tested, but it seems like the opposite. A string is translated but
some python code expects it to be an ascii string. There have been similar
issues already reported (see #2617 for longer discussion). Traceback
indicates use of str method on unicode object in 'gui_core\forms.py' file.
wxgui is full of such issues and in many places it is unknown if adding
just a u' ' would not introduce problems elsewhere :( Backporting r64834
could help in some cases but an overhaul of any string processing in wxgui
is required with strict rules (that need to be created).
--
Ticket URL: https://trac.osgeo.org/grass/ticket/2634#comment:9
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] wingrass build not available
Martin Landa wrote 2015-06-16 10:13 GMT+02:00 Helmut Kudrnovsky lt; hellik@ gt;: oh, https://trac.osgeo.org/grass/ticket/2634 is now also in the 7.0.1.RC1. so, it's blocker now? Ma see https://trac.osgeo.org/grass/ticket/2634#comment:7 I've switched GUI language to english, the error disappears. maybe a translation error? - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/wingrass-build-not-available-tp5208115p5211180.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] [GRASS GIS] #2634: 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte
#2634: 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte
---+-
Reporter: hellik| Owner: grass-dev@…
Type: defect| Status: new
Priority: critical | Milestone: 7.0.1
Component: Default |Version: svn-trunk
Resolution:| Keywords: utf, wxgui
CPU: x86-32| Platform: MSWindows 7
---+-
Comment (by hellik):
Replying to [comment:7 hellik]:
Replying to [comment:6 hellik]:
language is set following:
GUI preferences - language - system
ok, I switched the language to englisch:
{{{
GUI preferences - language - en
}}}
this error disappears.
maybe some error in the translation?
system language is german
--
Ticket URL: https://trac.osgeo.org/grass/ticket/2634#comment:8
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2696: Set language in GRASS-7.0.0
#2696: Set language in GRASS-7.0.0
--+--
Reporter: Biz | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.1
Component: Default |Version: 7.0.0
Resolution: | Keywords: Set language
CPU: Unspecified | Platform: MSWindows 7
--+--
Comment (by marisn):
In meantime you could try to edit manually wx settings file. It should be
located in your user home folder, appdata/grass version/wx (those are
hidden folders - just search around for proper folder name, file is called
wx).
Open that wx file with an text editor (notepad), find line starting with
language and replace it with:
{{{
language;locale;lc_all;C
}}}
Report back success or failure.
--
Ticket URL: https://trac.osgeo.org/grass/ticket/2696#comment:1
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2634: 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte
#2634: 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte ---+- Reporter: hellik| Owner: grass-dev@… Type: defect| Status: new Priority: critical | Milestone: 7.0.1 Component: Default |Version: svn-trunk Resolution:| Keywords: utf, wxgui CPU: x86-32| Platform: MSWindows 7 ---+- Comment (by martinl): Replying to [comment:9 marisn]: adding just a u' ' would not introduce problems elsewhere :( Backporting r64834 could help in some cases but an overhaul of any string processing in wxgui is required with strict rules (that need to be created). it's already done in r65462 -- Ticket URL: https://trac.osgeo.org/grass/ticket/2634#comment:10 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2695: Error loading extension. File is not zip file
#2695: Error loading extension. File is not zip file
---+-
Reporter: dnewcomb | Owner: grass-dev@…
Type: defect| Status: new
Priority: major | Milestone: 7.0.1
Component: Default |Version: svn-releasebranch70
Resolution:| Keywords:
CPU: x86-64| Platform: MSWindows 7
---+-
Description changed by martinl:
Old description:
Had GRASS 7.0 installed on Windows 7.0 computer .
Installed r.geomorphon Addon successfully .
Saw GRASS 7.0.1 RC was out.
Uninstalled GRASS 7.0.
Installed 7.0.1 RC1.
Tried to install more Addons.
With each addon get the following error ( r.gradient as example):
(Mon Jun 15 17:45:32 2015)
g.extension extension=r.gradient svnurl=http://svn.osgeo.org/grass/grass-
addons/grass7
Downloading precompiled GRASS Addons r.gradient...
ERROR: File is not a zip file:
http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1RC1/r.gradient.zip
(Mon Jun 15 17:45:34 2015) Command finished (1 sec)
New description:
Had GRASS 7.0 installed on Windows 7.0 computer .
Installed r.geomorphon Addon successfully .
Saw GRASS 7.0.1 RC was out.
Uninstalled GRASS 7.0.
Installed 7.0.1 RC1.
Tried to install more Addons.
With each addon get the following error ( r.gradient as example):
{{{
(Mon Jun 15 17:45:32 2015)
g.extension extension=r.gradient svnurl=http://svn.osgeo.org/grass/grass-
addons/grass7
Downloading precompiled GRASS Addons r.gradient...
ERROR: File is not a zip file:
http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1RC1/r.gradient.zip
(Mon Jun 15 17:45:34 2015) Command finished (1 sec)
}}}
--
--
Ticket URL: https://trac.osgeo.org/grass/ticket/2695#comment:1
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2634: 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte
#2634: 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte
---+-
Reporter: hellik| Owner: grass-dev@…
Type: defect| Status: new
Priority: critical | Milestone: 7.0.1
Component: Default |Version: svn-trunk
Resolution:| Keywords: utf, wxgui
CPU: x86-32| Platform: MSWindows 7
---+-
Comment (by hellik):
Replying to [comment:5 hellik]:
it's also now in the 7.0.1RC1, tested in the NC sample dataset
{{{
System Info
GRASS Version: 7.0.1RC1
GRASS SVN Revision: 65472
Erstellungsdatum: 2015-06-15
Build Platform: i686-pc-mingw32
GDAL/OGR: 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)
}}}
choosing d.rast from the wxgui
a MS error box pops up with
{{{
'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte
}}}
followed by this message in the wxgui
{{{
Traceback (most recent call last):
File C:\OSGEO4~2\apps\grass\grass-7.0.1RC1\gui\wxpython\g
ui_core\forms.py, line 2023, in OnUpdateDialog
self.parent.updateValuesHook()
File C:\OSGEO4~2\apps\grass\grass-7.0.1RC1\gui\wxpython\g
ui_core\forms.py, line 628, in updateValuesHook
self.SetStatusText('
'.join(self.notebookpanel.createCmd(ignoreErrors = True)))
TypeError
}}}
as mentioned in the original ticket above, e.g. g.region works without
any problem
any ideas?
language is set following:
GUI preferences - language - system
--
Ticket URL: https://trac.osgeo.org/grass/ticket/2634#comment:6
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2634: 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte
#2634: 'utf8' codec can't decode byte 0xf6 in position 8: invalid start byte
---+-
Reporter: hellik| Owner: grass-dev@…
Type: defect| Status: new
Priority: critical | Milestone: 7.0.1
Component: Default |Version: svn-trunk
Resolution:| Keywords: utf, wxgui
CPU: x86-32| Platform: MSWindows 7
---+-
Comment (by hellik):
Replying to [comment:6 hellik]:
language is set following:
GUI preferences - language - system
ok, I switched the language to englisch:
{{{
GUI preferences - language - en
}}}
this error disappears.
maybe some error in the translation?
--
Ticket URL: https://trac.osgeo.org/grass/ticket/2634#comment:7
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2618: v.category option=transfer does not copy multiple cat values
#2618: v.category option=transfer does not copy multiple cat values -+- Reporter: ulf | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.0.1 Component: Vector |Version: 7.0.0 Resolution: | Keywords: v.category transfer CPU: x86-64 | Platform: Linux -+- Comment (by mlennert): Can this be closed ? -- Ticket URL: http://trac.osgeo.org/grass/ticket/2618#comment:3 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2695: Error loading extension. File is not zip file
#2695: Error loading extension. File is not zip file ---+- Reporter: dnewcomb | Owner: grass-dev@… Type: defect| Status: closed Priority: major | Milestone: 7.0.1 Component: Default |Version: svn-releasebranch70 Resolution: fixed | Keywords: CPU: x86-64| Platform: MSWindows 7 ---+- Changes (by martinl): * status: new = closed * resolution: = fixed Comment: Fixed in r65482 -- Ticket URL: https://trac.osgeo.org/grass/ticket/2695#comment:2 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] r.sample.category
I am having a look at the new r.sample.category addon. Great idea. I would like to make a suggestion; to allow the user to define the number of points as a percentage, similar to r.random. Rgds, Paulo ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2649: r.to.vect diagonals defect fixed
#2649: r.to.vect diagonals defect fixed +- Reporter: byronbest | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.0.1 Component: Raster |Version: unspecified Resolution: | Keywords: r.to.vect CPU: x86-64 | Platform: All +- Comment (by mlennert): Has anyone been able to take a closer look at this patch ? -- Ticket URL: http://trac.osgeo.org/grass/ticket/2649#comment:5 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2648: v.concave.hull fails with small number of points
#2648: v.concave.hull fails with small number of points --+-- Reporter: annakrat | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.0.1 Component: Addons |Version: unspecified Resolution: | Keywords: concave hull CPU: Unspecified | Platform: All --+-- Comment (by mlennert): Could you provide a reproducible test case ? -- Ticket URL: http://trac.osgeo.org/grass/ticket/2648#comment:1 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] maps not showing in Data catalog
In one of my mapsets, raster layers are not showing in the Data catalog (vector layers are). They do also not show in the metadata editor (g.gui.metadata), which I guess is a related problem. The list of raster layers do show in d.rast and in the layer selection window opened with Ctrl+L. Any hint where to look for the problem. Is there a place where the layers are registered per mapset? Paulo ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] maps not showing in Data catalog
Hi, 2015-06-16 12:09 GMT+02:00 Paulo van Breugel p.vanbreu...@gmail.com: In one of my mapsets, raster layers are not showing in the Data catalog (vector layers are). They do also not show in the metadata editor (g.gui.metadata), which I guess is a related problem. I don't know, but I can see raster maps in data catalog. 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] #2304: Problems with add category to all features workflow
#2304: Problems with add category to all features workflow --+ Reporter: wenzeslaus | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.1.0 Component: Default |Version: unspecified Resolution: | Keywords: v.edit, v.category CPU: Unspecified | Platform: Unspecified --+ Comment (by mlennert): Replying to [comment:5 wenzeslaus]: Unresolved: * `v.category` has a parameter/option option while `v.edit` has a parameter tool The two modules do different things and I don't really see it as a problem that the parameters have different names. * `v.category` builds topology when there was no change v.category only does this when there is an output map and for any new map topology has to be built, so again, I don't see this as a problem. * `v.category` does nothing for `option=step`; using `option=sum` under the same conditions gives a result if there is something else to add, it is not in the example in manual There is no option=step. step is a separate parameter which allows to change the default step of 1 when v.category creates new cat values. * v.category says 0 features modified. when it finished report or print but it seems redundant I wouldn't expect something else when using report or print and not providing output I cannot reproduce this. * in GUI query tool, you will see that it shows only one layer and one category * now I see that layers are there but they are represented as separate maps which is not what I would expect since (layers are inside the map); I missed that before because I was querying more than one map and I considered the other (folded) row as one of the other maps * this needs separate ticket IMHO this behavior is debatable, but definitely not a bug. I again suggest closing this bug, as there is no actual bug report in here. -- Ticket URL: http://trac.osgeo.org/grass/ticket/2304#comment:6 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2309: Add a select all flag to v.edit
#2309: Add a select all flag to v.edit --+--- Reporter: wenzeslaus | Owner: grass-dev@… Type: enhancement | Status: new Priority: trivial | Milestone: 7.1.0 Component: Vector |Version: svn-trunk Resolution: | Keywords: v.edit, feature selection CPU: Unspecified | Platform: All --+--- Changes (by mlennert): * Attachment v_edit_select_all.diff added. -- Ticket URL: http://trac.osgeo.org/grass/ticket/2309 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2309: Add a select all flag to v.edit
#2309: Add a select all flag to v.edit --+--- Reporter: wenzeslaus | Owner: grass-dev@… Type: enhancement | Status: new Priority: trivial | Milestone: 7.1.0 Component: Vector |Version: svn-trunk Resolution: | Keywords: v.edit, feature selection CPU: Unspecified | Platform: All --+--- Comment (by mlennert): I've attached a patch that provides a very simplistic approach to a select all flag. However, reflection is needed on the following questions: * Should the flag select all features, regardless of whether they have a category number of not ? * If not should the flag select only features that have category numbers in a given layer ? I'm sure there are other questions like that that I haven't even thought about... -- Ticket URL: http://trac.osgeo.org/grass/ticket/2309#comment:1 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
