Re: [GRASS-dev] [GRASS GIS] #1800: v.kernel crashes after long execution

[GRASS GIS]

#1800: v.kernel crashes after long execution
+---
 Reporter:  arencambre  |   Owner:  grass-dev@…  
 Type:  defect  |  Status:  new  
 Priority:  normal  |   Milestone:  6.4.3
Component:  Vector  | Version:  6.4.2
 Keywords:  |Platform:  MSWindows 7  
  Cpu:  x86-64  |  
+---

Comment(by arencambre):

 Sorry, the formatting got messed up. Trying again:

 {{{
 v.kernel input=geocoding_after_highway_name_fix@PERMANENT
 output=mockingbird_and_central_high_resolution stddeviation=100
 STDDEV: 100.00
 RES: 11.176766  ROWS: 4710  COLS: 4495

 Writing output raster map using smooth parameter=100.00.

 Normalising factor=64826.350188.
 closecell: can't move C:\temp/dallascounty/PERMANENT/.tmp/7128.0
 to cell file
 C:\temp/dallascounty/PERMANENT/fcell/mockingbird_and_central_high_resolution
 Maximum value in output: 2.703527e-002.
 (Fri Nov 16 14:26:46 2012) Command finished (59981 sec)
 }}}

-- 
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] #1800: v.kernel crashes after long execution

[GRASS GIS]

#1800: v.kernel crashes after long execution
+---
 Reporter:  arencambre  |   Owner:  grass-dev@…  
 Type:  defect  |  Status:  new  
 Priority:  normal  |   Milestone:  6.4.3
Component:  Vector  | Version:  6.4.2
 Keywords:  |Platform:  MSWindows 7  
  Cpu:  x86-64  |  
+---
 A v.kernel run on a dataset with over 700,000 points abruptly crashes
 after several hours of processing:
 '''v.kernel input=geocoding_after_highway_name_fix@PERMANENT
 output=mockingbird_and_central_high_resolution stddeviation=100
 STDDEV: 100.00
 RES: 11.176766  ROWS: 4710  COLS: 4495

 Writing output raster map using smooth parameter=100.00.

 Normalising factor=64826.350188.
 closecell: can't move C:\temp/dallascounty/PERMANENT/.tmp/7128.0
 to cell file
 C:\temp/dallascounty/PERMANENT/fcell/mockingbird_and_central_high_resolution
 Maximum value in output: 2.703527e-002.
 (Fri Nov 16 14:26:46 2012) Command finished (59981 sec)'''

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] osgeo4w-wingrass (all versions) are not starting

[Jürgen E . Fischer]

Hi Helmut,

On Fri, 16. Nov 2012 at 09:59:25 -0800, Helmut Kudrnovsky wrote:
> >and an windows error message box (attached) pops up
 
> libeay32.dll is in C:\OSGeo4W\bin. 

OpenSSL was updated to 1.0.1 recently in OSGeo4W - might be related, although
other things like curl or QGIS didn't need changes for that.


JÃrgen

-- 
Jürgen E. Fischer norBIT GmbH   Tel. +49-4931-918175-31
Dipl.-Inf. (FH)   Rheinstraße 13Fax. +49-4931-918175-50
Software Engineer D-26506 Norden   http://www.norbit.de
committ(ed|ing) to Quantum GIS IRC: jef on FreeNode 


-- 
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502

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

Re: [GRASS-dev] osgeo4w-wingrass (all versions) are not starting

[Helmut Kudrnovsky]

>and an windows error message box (attached) pops up

libeay32.dll is in C:\OSGeo4W\bin. 

maybe a dll-mismatch?



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.n6.nabble.com/osgeo4w-wingrass-all-versions-are-not-starting-tp5016979p5016982.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] osgeo4w-wingrass (all versions) are not starting

[Helmut Kudrnovsky]

hi,

tested with all osgeo4w-wingrass-nightly builds from yesterday and today
(all versions).

the welcome screen starts, the selection of location and mapset is possible,
but then the wxgui disappears and following error in the command line is
shown:

Launching  GUI in the background, please wait...
GRASS 7.0.svn> GRASS module 'g.proj' not found. Unable to start map display
window.

g.proj is in (C:\OSGeo4W\apps\grass\grass-7.0.svn\bin,
C:\OSGeo4W\apps\grass\grass-6.4.3svn\bin,
C:\OSGeo4W\apps\grass\grass-6.5.svn\bin).

and an windows error message box (attached) pops up

 





-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.n6.nabble.com/osgeo4w-wingrass-all-versions-are-not-starting-tp5016979.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] #1799: Selecting multiple columns in v.db.select window does not work

[GRASS GIS]

#1799: Selecting multiple columns in v.db.select window does not work
-+--
 Reporter:  pvanbosgeo   |   Owner:  grass-dev@…  
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  7.0.0
Component:  wxGUI| Version:  svn-trunk
 Keywords:  v.db.select  |Platform:  Unspecified  
  Cpu:  x86-64   |  
-+--
Changes (by martinl):

  * keywords:  => v.db.select
  * component:  Default => wxGUI


-- 
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] #1799: Selecting multiple columns in v.db.select window does not work

[GRASS GIS]

#1799: Selecting multiple columns in v.db.select window does not work
+---
 Reporter:  pvanbosgeo  |   Owner:  grass-dev@…  
 Type:  defect  |  Status:  new  
 Priority:  normal  |   Milestone:  7.0.0
Component:  Default | Version:  svn-trunk
 Keywords:  |Platform:  Unspecified  
  Cpu:  x86-64  |  
+---
 Running v.db.select using the GUI: it is not possible to select more then
 one column in the dropdown menu

 GRASS version: 7.0.svn
 GRASS SVN Revision: 53783
 GIS Library Revision: 52468 (2012-07-27)
 GDAL/OGR: 1.9.2
 PROJ.4: 4.7.0
 GEOS: 3.3.3
 Python: 2.7.3
 wxPython: 2.8.12.1
 Platform: Linux-3.5.0-18-generic-x86_64-with-Ubuntu-12.10-quantal

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] could r.stream.* become part of GRASS core?

[Moritz Lennert]

On 16/11/12 09:10, Rainer M Krug wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 15/11/12 23:41, Helmut Kudrnovsky wrote:

I agree that the quality of the r.stream.* modules is out of question.


these are very nice and useful modules with high quality.


For what concerns including it into the core, I would like to point you out the 
discussion
[1] about the concept of toolboxes. The general orientation is not to include 
field specific
groups of modules into the core and make them available in an easy way when 
required.


Please also note the discussion in this thread [1], where most 
developpers rather seem to plead for integrating more modules directly 
into trunk.


Toolboxes would then rather be menu blocks that you can activate or not, 
organising your GUI access to the relevant modules.


Moritz

[1] http://lists.osgeo.org/pipermail/grass-dev/2012-October/060565.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] could r.stream.* become part of GRASS core?

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 15/11/12 23:41, Helmut Kudrnovsky wrote:
>> I agree that the quality of the r.stream.* modules is out of question.
> 
> these are very nice and useful modules with high quality.
> 
>> For what concerns including it into the core, I would like to point you out 
>> the discussion
>> [1] about the concept of toolboxes. The general orientation is not to 
>> include field specific
>> groups of modules into the core and make them available in an easy way when 
>> required.
> 
> but how can we guide "normal" users that such interesting tools are in the 
> addons?

That is an interesting and important question. One way would be to have one sub 
menu named
"Available Add-Ons" which is updated automatically from the official Add-On 
repository.
When one entry is selected, the extension manager could be opened to make 
installation easy.
And in the menu, it could be reflected which ones are already installed.

Just an idea,

Cheers

Rainer

> 
> 
> 
> - best regards Helmut -- View this message in context:
> http://osgeo-org.1560.n6.nabble.com/could-r-stream-become-part-of-GRASS-core-tp5000607p5016768.html
>
> 
Sent from the Grass - Dev mailing list archive at Nabble.com.
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCl9OMACgkQoYgNqgF2egr+ZQCfRo+coiU2QhmR8ty3bVyVMqjx
vx4An2PDm84nsCM5wZegeH27kaxo9uGu
=66J1
-END PGP SIGNATURE-
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev