Re: [GRASS-dev] [GRASS GIS] #1241: Change default calculation in r.sun to include topographic shadowing
#1241: Change default calculation in r.sun to include topographic shadowing --+- Reporter: newcombttg | Owner: hamish Type: enhancement | Status: closed Priority: normal | Milestone: 7.0.0 Component: Raster | Version: svn-trunk Resolution: fixed|Keywords: r.sun Platform: All | Cpu: All --+- Changes (by hamish): * status: assigned = closed * resolution: = fixed Comment: Yann and MarkusN like it too; done in r55187. There is now a '-p' planar flag. (if you like a better non-s letter, by all means change it..) Also I expanded some option names to take advantage of the new grass7 underscore option name parsing. Hamish -- Ticket URL: https://trac.osgeo.org/grass/ticket/1241#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] #1693: v.colors placeholder raster map naming option
#1693: v.colors placeholder raster map naming option ---+ Reporter: alf| Owner: hamish Type: enhancement| Status: assigned Priority: normal | Milestone: 6.4.4 Component: Shell Scripts | Version: svn-develbranch6 Keywords: v.colors |Platform: All Cpu: All| ---+ Changes (by hamish): * milestone: 6.5.0 = 6.4.4 Comment: Done in devbr6 with r55191. To be backported to 6.4.4 for further testing after the freeze. Hamish -- Ticket URL: https://trac.osgeo.org/grass/ticket/1693#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] #1606: WXGUI regression - attribute query tool reports nothing found when clicking on a vector object
#1606: WXGUI regression - attribute query tool reports nothing found when clicking on a vector object --+- Reporter: marisn | Owner: grass-dev@… Type: defect | Status: reopened Priority: blocker | Milestone: 6.4.3 Component: wxGUI| Version: 6.4.3 RCs Resolution: |Keywords: query Platform: Unspecified | Cpu: Unspecified --+- Comment(by mlennert): Replying to [comment:11 annakrat]: In case there exist layers of vector map which are not connected to db, the query output is redirected in command console (r55184). This is the easiest solution, other solutions would need more changes which means more possible errors. Thanks ! It would be great, however, to be able to copy directly from the display, instead of having to copy everything to the clipboard, copy that to a text editor and then pick out the elements you want. As an example: sometimes I just want to identify the coordinates of a place. It would be nice to be able to click on it and then directly copy the values for easting and northing from the query results window. Moritz -- Ticket URL: http://trac.osgeo.org/grass/ticket/1606#comment:12 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] #1893: d.vect on re-opening switches to default layer
#1893: d.vect on re-opening switches to default layer -+-- Reporter: marisn | Owner: grass-dev@… Type: defect | Status: new Priority: major| Milestone: 6.4.3 Component: wxGUI| Version: svn-releasebranch64 Keywords: |Platform: Unspecified Cpu: Unspecified | -+-- Comment(by mlennert): Replying to [comment:1 annakrat]: Please try r55181. Works great for me. Thanks ! Moritz -- Ticket URL: http://trac.osgeo.org/grass/ticket/1893#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] #1889: wxPy loc'n wiz: don't auto-launch into PERMANENT
#1889: wxPy loc'n wiz: don't auto-launch into PERMANENT -+-- Reporter: hamish | Owner: grass-dev@… Type: defect | Status: new Priority: blocker | Milestone: 6.4.3 Component: wxGUI| Version: 6.4.3 RCs Keywords: location wizard |Platform: Unspecified Cpu: x86-64 | -+-- Comment(by mlennert): Replying to [comment:7 annakrat]: Please try r55185. It asks for new mapset after creating location and goes back to startup window. This looks good to me, now. We might want to think about a tooltip that explains why creating a mapset (other than PERMANENT) is a good idea, but that's cosmetics. I noticed that startup window gui accepts non-ascii mapset and location name but later, the gui complains about it. See #1293. I suggest to check the input and do not allow diacritic. +1 Is there a possibility to call a Python equivalent of G_legal_name() ? Moritz -- Ticket URL: http://trac.osgeo.org/grass/ticket/1889#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] #1241: Change default calculation in r.sun to include topographic shadowing
#1241: Change default calculation in r.sun to include topographic shadowing --+- Reporter: newcombttg | Owner: hamish Type: enhancement | Status: closed Priority: normal | Milestone: 7.0.0 Component: Raster | Version: svn-trunk Resolution: fixed|Keywords: r.sun Platform: All | Cpu: All --+- Comment(by neteler): Updated also: http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures#Rastermodules -- Ticket URL: https://trac.osgeo.org/grass/ticket/1241#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] #1241: Change default calculation in r.sun to include topographic shadowing
#1241: Change default calculation in r.sun to include topographic shadowing --+- Reporter: newcombttg | Owner: hamish Type: enhancement | Status: closed Priority: normal | Milestone: 7.0.0 Component: Raster | Version: svn-trunk Resolution: fixed|Keywords: r.sun Platform: All | Cpu: All --+- Comment(by hamish): see also the Renamed options section further down the page, already done. :) https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures?action=diffversion=143 H -- Ticket URL: https://trac.osgeo.org/grass/ticket/1241#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] #1891: wingrass: background dosbox from regular wxgui startup
#1891: wingrass: background dosbox from regular wxgui startup --+- Reporter: hamish| Owner: grass-dev@… Type: defect| Status: new Priority: major | Milestone: 6.4.3 Component: Default | Version: svn-releasebranch64 Keywords: wingrass |Platform: MSWindows 7 Cpu: x86-64| --+- Changes (by hamish): * priority: blocker = major Comment: this is unsightly, but not a really a blocker. -- Ticket URL: https://trac.osgeo.org/grass/ticket/1891#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] #1270: wingrass: Error in Attribute Table Manager
#1270: wingrass: Error in Attribute Table Manager ---+ Reporter: antonioall | Owner: grass-dev@… Type: defect | Status: new Priority: blocker| Milestone: 6.4.3 Component: wxGUI | Version: svn-develbranch6 Keywords: wingrass, attribute table manager |Platform: MSWindows Vista Cpu: x86-32 | ---+ Comment(by neteler): Replying to [comment:16 hamish]: Replying to [comment:12 neteler]: I guess that http://trac.osgeo.org/grass/changeset/55106 will now block any testing. not really, just use devbr6 for testing ... as per previous discussions (see ML archive) I doubt that devbr6 receives reasonable testing. -- Ticket URL: https://trac.osgeo.org/grass/ticket/1270#comment:17 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] #1803: GRASS 6.4.3RC1 on Win 7: grass64.bat fails due to UNIX line endings in Init.bat
#1803: GRASS 6.4.3RC1 on Win 7: grass64.bat fails due to UNIX line endings in Init.bat --+- Reporter: msieczka | Owner: grass-dev@… Type: defect| Status: new Priority: critical | Milestone: 6.4.3 Component: Startup | Version: 6.4.3 RCs Keywords: Init.bat, CRLF, wingrass |Platform: MSWindows 7 Cpu: x86-64| --+- Comment(by hamish): Retesting with the 6.4.3svn r55185 nightly build; the svn prop change didn't help. I assume that's because the Init.bat script is not copied, it is made from init.bat(?). note that msys nicely provides unix2dos.exe, if we need it at build or install time. Once resaving Init.bat with DOS newlines, GRASS Command Line in the cmd.exe window starts, but after esc-enter an error message pops up saying set_data.exe has stopped working (segfault afaict APPCRASH) do you want to check for an online solution or close the program?. If you press cancel you get the usual GRASS welcome text but no ascii art, and g.gisenv all seems to be ok. not sure where to go from here, but the nightly build scripts? Hamish -- Ticket URL: https://trac.osgeo.org/grass/ticket/1803#comment:12 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] #1893: d.vect on re-opening switches to default layer
#1893: d.vect on re-opening switches to default layer
-+--
Reporter: marisn | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone: 6.4.3
Component: wxGUI| Version: svn-releasebranch64
Keywords: |Platform: Unspecified
Cpu: Unspecified |
-+--
Comment(by mmetz):
Replying to [comment:2 mlennert]:
Replying to [comment:1 annakrat]:
Please try r55181.
Works great for me.
Does not work for me in all branches with a network generated with v.net.
1. Add a table to layer 2
2. Display layer 2 with attributes (just cats for testing), click OK: ok
3. Double-click on the layer in the lmgr, do nothing just click OK:
KABOOM! Vectors are gone, error:
{{{
Details: attrcol not specified, cannot display attributes
}}}
It might be easier to just hide the dialog and show it again (like for
decorations) on double-click or clock on Properties. The dialog then needs
to be destroyed when the layer is removed. Makes sense?
Markus M
--
Ticket URL: http://trac.osgeo.org/grass/ticket/1893#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] #1893: d.vect on re-opening switches to default layer
#1893: d.vect on re-opening switches to default layer
-+--
Reporter: marisn | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone: 6.4.3
Component: wxGUI| Version: svn-releasebranch64
Keywords: |Platform: Unspecified
Cpu: Unspecified |
-+--
Comment(by mlennert):
Replying to [comment:3 mmetz]:
Replying to [comment:2 mlennert]:
Replying to [comment:1 annakrat]:
Please try r55181.
Works great for me.
Does not work for me in all branches with a network generated with
v.net.
1. Add a table to layer 2
2. Display layer 2 with attributes (just cats for testing), click OK: ok
3. Double-click on the layer in the lmgr, do nothing just click OK:
KABOOM! Vectors are gone, error:
{{{
Details: attrcol not specified, cannot display attributes
}}}
It might be easier to just hide the dialog and show it again (like for
decorations) on double-click or clock on Properties. The dialog then needs
to be destroyed when the layer is removed. Makes sense?
I see the issue. IIUC, it's due to llayer. But wouldn't it be enough to
apply a similar fix to llayer ?
Moritz
--
Ticket URL: http://trac.osgeo.org/grass/ticket/1893#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] #1893: d.vect on re-opening switches to default layer
#1893: d.vect on re-opening switches to default layer
-+--
Reporter: marisn | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone: 6.4.3
Component: wxGUI| Version: svn-releasebranch64
Keywords: |Platform: Unspecified
Cpu: Unspecified |
-+--
Comment(by mmetz):
Replying to [comment:4 mlennert]:
Replying to [comment:3 mmetz]:
Replying to [comment:2 mlennert]:
Replying to [comment:1 annakrat]:
Please try r55181.
Works great for me.
Does not work for me in all branches with a network generated with
v.net.
1. Add a table to layer 2
2. Display layer 2 with attributes (just cats for testing), click OK:
ok
3. Double-click on the layer in the lmgr, do nothing just click OK:
KABOOM! Vectors are gone, error:
{{{
Details: attrcol not specified, cannot display attributes
}}}
It might be easier to just hide the dialog and show it again (like for
decorations) on double-click or clock on Properties. The dialog then needs
to be destroyed when the layer is removed. Makes sense?
I see the issue. IIUC, it's due to llayer. But wouldn't it be enough to
apply a similar fix to llayer ?
No. You would need similar fixes for all column options as well. The
dialog should IMHO not be updated when showing properties because the user
did not update anything. IOW, the dialog and its options should only be
updated when they are really updated (changed by the user). Thus my
show/hide suggestion, which is already used for other dialogs.
Markus M
--
Ticket URL: http://trac.osgeo.org/grass/ticket/1893#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] #1606: WXGUI regression - attribute query tool reports nothing found when clicking on a vector object
#1606: WXGUI regression - attribute query tool reports nothing found when clicking on a vector object --+- Reporter: marisn | Owner: grass-dev@… Type: defect | Status: reopened Priority: blocker | Milestone: 6.4.3 Component: wxGUI| Version: 6.4.3 RCs Resolution: |Keywords: query Platform: Unspecified | Cpu: Unspecified --+- Comment(by annakrat): Replying to [comment:12 mlennert]: Replying to [comment:11 annakrat]: In case there exist layers of vector map which are not connected to db, the query output is redirected in command console (r55184). This is the easiest solution, other solutions would need more changes which means more possible errors. Thanks ! It would be great, however, to be able to copy directly from the display, instead of having to copy everything to the clipboard, copy that to a text editor and then pick out the elements you want. As an example: sometimes I just want to identify the coordinates of a place. It would be nice to be able to click on it and then directly copy the values for easting and northing from the query results window. You are talking about new querying in grass7? It is different than in grass 64, it is more consistent. But needs some improvemnets. Could you create a ticket for this? As for the coordinates, you can get them by right click on the map display. Anna -- Ticket URL: http://trac.osgeo.org/grass/ticket/1606#comment:13 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] #1606: WXGUI regression - attribute query tool reports nothing found when clicking on a vector object
#1606: WXGUI regression - attribute query tool reports nothing found when clicking on a vector object --+- Reporter: marisn | Owner: grass-dev@… Type: defect | Status: reopened Priority: blocker | Milestone: 6.4.3 Component: wxGUI| Version: 6.4.3 RCs Resolution: |Keywords: query Platform: Unspecified | Cpu: Unspecified --+- Comment(by mlennert): Replying to [comment:13 annakrat]: Replying to [comment:12 mlennert]: Replying to [comment:11 annakrat]: In case there exist layers of vector map which are not connected to db, the query output is redirected in command console (r55184). This is the easiest solution, other solutions would need more changes which means more possible errors. Thanks ! It would be great, however, to be able to copy directly from the display, instead of having to copy everything to the clipboard, copy that to a text editor and then pick out the elements you want. As an example: sometimes I just want to identify the coordinates of a place. It would be nice to be able to click on it and then directly copy the values for easting and northing from the query results window. You are talking about new querying in grass7? Yes, sorry. I got confused between versions here. The grass6 solution also works well, by the way. I'm just afraid that it will be a bit confusing for users to see two different reactions to the same action (either editable attributes or output to console). It is different than in grass 64, it is more consistent. But needs some improvemnets. Could you create a ticket for this? As for the coordinates, you can get them by right click on the map display. Thanks for the tip on coordinates (hadn't noticed this, yet, it's very practical !), but my remark was more general. I'll file a ticket. Moritz -- Ticket URL: http://trac.osgeo.org/grass/ticket/1606#comment:14 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] #1897: grass7 wxgui query: allow copying individual elements from query results
#1897: grass7 wxgui query: allow copying individual elements from query results -+-- Reporter: mlennert | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: 7.0.0 Component: wxGUI| Version: svn-trunk Keywords: query|Platform: Unspecified Cpu: Unspecified | -+-- In the current implementation of map querying in the grass7 wxgui, when you click on the display a dedicated window (Query results) opens with the r/v.what results. One can copy the complete window contents to the clipboard, but not individual elements. This makes working with these results a bit tedious as if you need a specific element you have to copy the entire contents of the window to a text editor to then be able to copy just what you need. It would be much more practical IMHO to be able to directly select and copy individual elements. Linked to that one might also question the need of the dedicated display window. Why not simply continue to use the console output ? Moritz -- Ticket URL: http://trac.osgeo.org/grass/ticket/1897 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] #1893: d.vect on re-opening switches to default layer
#1893: d.vect on re-opening switches to default layer
-+--
Reporter: marisn | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone: 6.4.3
Component: wxGUI| Version: svn-releasebranch64
Keywords: |Platform: Unspecified
Cpu: Unspecified |
-+--
Comment(by annakrat):
Replying to [comment:5 mmetz]:
Replying to [comment:4 mlennert]:
Replying to [comment:3 mmetz]:
Replying to [comment:2 mlennert]:
Replying to [comment:1 annakrat]:
Please try r55181.
Works great for me.
Does not work for me in all branches with a network generated with
v.net.
1. Add a table to layer 2
2. Display layer 2 with attributes (just cats for testing), click
OK: ok
3. Double-click on the layer in the lmgr, do nothing just click OK:
KABOOM! Vectors are gone, error:
{{{
Details: attrcol not specified, cannot display attributes
}}}
It might be easier to just hide the dialog and show it again (like
for decorations) on double-click or clock on Properties. The dialog then
needs to be destroyed when the layer is removed. Makes sense?
I see the issue. IIUC, it's due to llayer. But wouldn't it be enough
to apply a similar fix to llayer ?
No. You would need similar fixes for all column options as well. The
dialog should IMHO not be updated when showing properties because the user
did not update anything. IOW, the dialog and its options should only be
updated when they are really updated (changed by the user). Thus my
show/hide suggestion, which is already used for other dialogs.
Actually, the show/hide is already there. I just removed the line which
updated the dialog.
The llayer option seems to be a different problem which I don't fully
understand. Only layer 1 is in the list.
Anna
--
Ticket URL: http://trac.osgeo.org/grass/ticket/1893#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] #1897: grass7 wxgui query: allow copying individual elements from query results
#1897: grass7 wxgui query: allow copying individual elements from query results -+-- Reporter: mlennert | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: 7.0.0 Component: wxGUI| Version: svn-trunk Keywords: query|Platform: Unspecified Cpu: Unspecified | -+-- Comment(by annakrat): Replying to [ticket:1897 mlennert]: In the current implementation of map querying in the grass7 wxgui, when you click on the display a dedicated window (Query results) opens with the r/v.what results. One can copy the complete window contents to the clipboard, but not individual elements. This is a limitation of wxPython. There are a few possibilities what to do: * on right click show context menu with 'copy selected value' * add checkbox 'show query results also in command console' * let the user choose in preferences if to use the dialog or not (use command console) Linked to that one might also question the need of the dedicated display window. Why not simply continue to use the console output ? The dialog has some advantages: * dialog is more natural for new and not advanced users * the results are better organized, for example the output of raster querying for more maps is a mess (but I understand that this argument is more about the formatting than using dialog) * dialog uses tree structure, so you can hide some results Regards, Anna -- Ticket URL: http://trac.osgeo.org/grass/ticket/1897#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] dead links in references for GRASS LiDAR processing
On Sun, Feb 24, 2013 at 11:39 PM, Michael Barton michael.bar...@asu.eduwrote: The first two of the links for references on the GRASS LiDAR tools are dead links. http://grasswiki.osgeo.org/wiki/LIDAR Can the relevant documents be found and put onto the GRASS server where they can be archived and maintained? It depends - if they have the proper license. The third link is still live, but slow. Perhaps it would be good to also archive that PDF where it is more easily accessible. Michael *References:* - Detailed description: herehttp://www.foss4g2006.org/getFile.py/access?contribId=48sessionId=59resId=7materialId=slidesconfId=1 (FOSS4G 2006) [DEAD LINK] -- which title? - Summarised version: herehttp://geomatica.como.polimi.it/corsi/remote_sensing/LiDAR_filtering_with_GRASS-lab4.pdf (2010) [DEAD LINK] found with google: http://geomatica.como.polimi.it/corsi/remote_sensing/LiDAR.pdf - Calibration of the filtering parameters (around 20 parameters) by integrating the USGS UCODE and GRASS, see herehttp://www.isprs.org/proceedings/XXXVIII/1_4_7-W5/paper/Brovelli-126.pdf [LIVE BUT SLOW LINK] so nothing to do. I have update the one link and also the titles in the Wiki page. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #1270: wingrass: Error in Attribute Table Manager
#1270: wingrass: Error in Attribute Table Manager
---+
Reporter: antonioall | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker| Milestone: 6.4.3
Component: wxGUI | Version: svn-develbranch6
Keywords: wingrass, attribute table manager |Platform: MSWindows Vista
Cpu: x86-32 |
---+
Comment(by hellik):
Replying to [comment:3 hamish]:
suspect the attribute manager is holding the temp file open..
tested with
{{{
System Info
GRASS version: 6.5.svn
GRASS SVN Revision: 55167
GIS Library Revision: 50936 (2012-02-25)
GDAL/OGR: 1.9.2
PROJ4: Rel. 4.8.0, 6 March 2012
Python: 2.7.2
wxPython: 2.8.12.1
Platform: Windows-7-6.1.7601-SP1 (OSGeo4W)
}}}
yes, it seems so.
the temp file is in C:\Users\xxx\AppData\Local\Temp, the file's
content is the sql update command, e.g.
{{{
UPDATE myhosp SET testc=2 WHERE cat=1;
}}}
any idea how to close the temp file?
Helmut
--
Ticket URL: https://trac.osgeo.org/grass/ticket/1270#comment:18
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] #1270: wingrass: Error in Attribute Table Manager
#1270: wingrass: Error in Attribute Table Manager
---+
Reporter: antonioall | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker| Milestone: 6.4.3
Component: wxGUI | Version: svn-develbranch6
Keywords: wingrass, attribute table manager |Platform: MSWindows Vista
Cpu: x86-32 |
---+
Comment(by hellik):
Replying to [comment:16 hamish]:
[...]
moreover, using v.db.addcol from the main db - vect db conns menu to
add a column had this error:
{{{
v.db.addcol --verbose map=copyofbugs2@user1 columns=someint2 integer
DBMI-DBF driver error:
ERROR: Unable to open database C:/Program Files (x86)/GRASS GIS
6.4.3svn/msys/Users/Hamish/Documents/GIS DataBase/spearfish60/user1/dbf/
ERROR: Cannot continue (problem adding column).
}}}
tested with
{{{
GRASS version: 6.4.3svn
GRASS SVN Revision: 55185
GIS Library Revision: 50937 (2012-02-25)
GDAL/OGR: 1.9.2
PROJ4: Rel. 4.8.0, 6 March 2012
Python: 2.7.2
wxPython: 2.8.12.1
Platform: Windows-7-6.1.7601-SP1 (OSGeo4W)
}}}
{{{
v.db.addcol map=myfires@user1 columns=someint2 integer
(Mon Feb 25 21:05:23 2013) Command finished (2 sec)
}}}
Helmut
--
Ticket URL: https://trac.osgeo.org/grass/ticket/1270#comment:19
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] #1270: wingrass: Error in Attribute Table Manager
#1270: wingrass: Error in Attribute Table Manager
---+
Reporter: antonioall | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker| Milestone: 6.4.3
Component: wxGUI | Version: svn-develbranch6
Keywords: wingrass, attribute table manager |Platform: MSWindows Vista
Cpu: x86-32 |
---+
Comment(by hellik):
Replying to [comment:16 hamish]:
moreover, using v.db.addcol from the main db - vect db conns menu to
add a column had this error:
{{{
v.db.addcol --verbose map=copyofbugs2@user1 columns=someint2 integer
DBMI-DBF driver error:
ERROR: Unable to open database C:/Program Files (x86)/GRASS GIS
6.4.3svn/msys/Users/Hamish/Documents/GIS DataBase/spearfish60/user1/dbf/
ERROR: Cannot continue (problem adding column).
}}}
and now tested with the wingrass-standalone installer
{{{
GRASS version: 6.4.3svn
GRASS SVN Revision: 55185
GIS Library Revision: 50937 (2012-02-25)
GDAL/OGR: GDAL 1.9.2, released 2012/10/08
PROJ4: Rel. 4.8.0, 6 March 2012
Python: 2.7.2
wxPython: 2.8.12.1
Platform: Windows-7-6.1.7601-SP1
}}}
{{{
v.db.addcol map=myhosp@user1 columns=someint3 integer
(Mon Feb 25 21:28:45 2013) Command finished (2 sec)
}}}
Helmut
--
Ticket URL: https://trac.osgeo.org/grass/ticket/1270#comment:20
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] #1270: wingrass: Error in Attribute Table Manager
#1270: wingrass: Error in Attribute Table Manager
---+
Reporter: antonioall | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker| Milestone: 6.4.3
Component: wxGUI | Version: svn-develbranch6
Keywords: wingrass, attribute table manager |Platform: MSWindows Vista
Cpu: x86-32 |
---+
Comment(by hellik):
Replying to [comment:16 hamish]:
[...]
with the r55185-512 6.4.3svn nightly build on Windows7 64bit running the
desktop icon wxGUI, I still get an error. Actually it froze with an
endless spinning circle hourglass thing when I tried to add a column in
the show attribute data manage tables tab, with the cursor over any of
the open grass windows. I had to kill it by clicking on the X in the
window, which took out all of grass except a zombie dbf.exe in the task
manager + the empty cmd.exe dosbox.
tested with
{{{
GRASS version: 6.4.3svn
GRASS SVN Revision: 55185
GIS Library Revision: 50937 (2012-02-25)
GDAL/OGR: GDAL 1.9.2, released 2012/10/08
PROJ4: Rel. 4.8.0, 6 March 2012
Python: 2.7.2
wxPython: 2.8.12.1
Platform: Windows-7-6.1.7601-SP1
}}}
can't reproduce this ...
Helmut
--
Ticket URL: https://trac.osgeo.org/grass/ticket/1270#comment:21
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] #1683: error message v.db.addcol
#1683: error message v.db.addcol ---+ Reporter: jradinger | Owner: hamish Type: defect | Status: assigned Priority: major | Milestone: 6.4.3 Component: Shell Scripts | Version: svn-develbranch6 Keywords: v.db.addcol|Platform: All Cpu: Unspecified| ---+ Comment(by hamish): Hi, scripts in devbr6 now updated with r55194:55226, but need testing before backport to the stable branch. AFAICT the only ones which will actually trigger run-time processing errors (instead of just the occasional harmless message) on WinGrass w/ spaces in GISDBASE, are: * r.pack/unpack (already backported) * r.in.srtm * db.droptable * d.rast.leg (bug? try erode.index@spearfish) * r.in.wms * i.image.mosaic * v.in.garmin (doesn't need to be fixed for wingrass as dep req's UNIX) so those should be tested then backported for 6.4.3. the rest can wait until after the freeze and go in for 6.4.4. Hamish -- Ticket URL: https://trac.osgeo.org/grass/ticket/1683#comment:16 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
