[GRASS-dev] [GRASS GIS] #381: wxgui: Show attribute data depends on global db connection, not file db connection parameter

2008-11-25 Thread GRASS GIS 
#381: wxgui: Show attribute data depends on global db connection, not file db
connection parameter
-+--
 Reporter:  mlennert |   Owner:  grass-dev@lists.osgeo.org
 Type:  defect   |  Status:  new  
 Priority:  major|   Milestone:  6.4.0
Component:  wxGUI| Version:  unspecified  
 Keywords:   |Platform:  Unspecified  
  Cpu:  Unspecified  |  
-+--
 When trying to access the attribute table in the wxgui, I get an error
 when the map is connected to a table which is not in the default database
 of the mapset, in other words v.db.connect gives other information for
 database than db.connect. This is because db.tables is called.

 Probably attribute management of a single map and table management for the
 default database need to be decoupled somehow...

-- 
Ticket URL: http://trac.osgeo.org/grass/ticket/381
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] #382: r.texture NULL or negative value ERROR (possible r.null problem)

2008-11-25 Thread GRASS GIS 
#382: r.texture NULL or negative value ERROR (possible r.null problem)
-+--
 Reporter:  khufkens |   Owner:  
grass-dev@lists.osgeo.org
 Type:  defect   |  Status:  new
  
 Priority:  minor|   Milestone:  6.3.1  
  
Component:  Raster   | Version:  6.3.0  
  
 Keywords:  r.texture r.null ERROR null negative values  |Platform:  Linux  
  
  Cpu:  Unspecified  |  
-+--
 Concerning r.texture in GRASS 6.3:

 Running r.texture on a map after r.null (should have) replaced all NULL
 values still produces an error indicating a persistent NULL or negative
 value in the map.

 r.category shows no NULL values or negative values but yet they are there
 for r.texture...

 Adding a fixed value to the map with the map calculator or running a
 running window analysis removes these hidden values and also removes the
 error.

 This traces back to either an error in r.texture or r.null, not sure...

-- 
Ticket URL: http://trac.osgeo.org/grass/ticket/382
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] Re: [GRASS GIS] #382: r.texture NULL or negative value ERROR (possible r.null problem)

2008-11-25 Thread GRASS GIS 
#382: r.texture NULL or negative value ERROR (possible r.null problem)
---+
  Reporter:  khufkens  |   Owner:  grass-dev@lists.osgeo.org
  
  Type:  defect|  Status:  new  
  
  Priority:  minor |   Milestone:  6.3.1
  
 Component:  Raster| Version:  6.3.0
  
Resolution:|Keywords:  r.texture r.null ERROR null negative 
values
  Platform:  Linux | Cpu:  Unspecified  
  
---+
Comment (by neteler):

 for the record:

 On Tue, Nov 25, 2008 at 2:29 AM, Hamish:
  maybe something like this:
 
 
http://trac.osgeo.org/grass/changeset?new=grass%2Ftrunk%2Fraster%2Fr.los%2Fpts_elim.c%4025104old=grass%2Ftrunk%2Fraster%2Fr.los%2Fpts_elim.c%4018934

-- 
Ticket URL: http://trac.osgeo.org/grass/ticket/382#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] [GRASS GIS] #383: change fprintf to G_debug in do_proj.c

2008-11-25 Thread GRASS GIS 
#383: change fprintf to G_debug in do_proj.c
-+--
 Reporter:  quinn|   Owner:  grass-dev@lists.osgeo.org
 Type:  defect   |  Status:  new  
 Priority:  trivial  |   Milestone:   
Component:  Raster   | Version:  6.2.3
 Keywords:   |Platform:  All  
  Cpu:  All  |  
-+--
 If you use r.proj to project between coordinate systems that don't
 share all points, you get many errors to STDERR, for each projection
 failure.  I'm not sure that's necessarily an error, and I suggest the
 notice be sent to G_debug.

 {{{
  --- grass-6.2.3.orig/lib/proj/do_proj.c
  +++ grass-6.2.3/lib/proj/do_proj.c
  @@ -104,8 +104,7 @@
}
 } if (ok  0) {
  -   fprintf(stderr, pj_transform() failed\ncause: );
  -   fprintf(stderr, %s\n, pj_strerrno(ok));
  +  G_debug(5,pj_transform() failed in pj_do_proj\ncause: %s\n,
 pj_strerrno(ok));
 }
 return ok;
  }
  @@ -178,8 +177,7 @@
G_free(h);
  if (ok  0) {
  -   fprintf(stderr, pj_transform() failed\ncause: );
  -   fprintf(stderr, %s\n, pj_strerrno(ok));
  +  G_debug(5,pj_transform() failed in pj_do_transform\ncause:
 %s\n,pj_strerrno(ok));
 }
 return ok;
  }
 }}}

-- 
Ticket URL: http://trac.osgeo.org/grass/ticket/383
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] Re: [GRASS GIS] #382: r.texture NULL or negative value ERROR (possible r.null problem)

2008-11-25 Thread GRASS GIS 
#382: r.texture NULL or negative value ERROR (possible r.null problem)
---+
  Reporter:  khufkens  |   Owner:  grass-dev@lists.osgeo.org
  
  Type:  defect|  Status:  new  
  
  Priority:  minor |   Milestone:  6.3.1
  
 Component:  Raster| Version:  6.3.0
  
Resolution:|Keywords:  r.texture r.null ERROR null negative 
values
  Platform:  Linux | Cpu:  Unspecified  
  
---+
Comment (by hamish):

 what does r.univar say, before and after r.null?

 (run 'g.region rast=yourmap' first)

 Hamish

-- 
Ticket URL: https://trac.osgeo.org/grass/ticket/382#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