Re: [GRASS-dev] convert 3D polygons or Tins to a DEM?

Hamish wrote: For a long time it has been unclear to me, do kernels live in the middle of each face like an area centroid with 3D coordinates, or is it for true 3D topology like a single point somewhere within a closed volume defined by many faces. ie would a cube get a single kernel in

Re: [GRASS-dev] lib fn to convert int color number to RGB values?

Hi, Color change for d.grid -c,-f is now working. http://trac.osgeo.org/grass/changeset/29944 Please review. Hamish Looking for last minute shopping deals? Find them fast with Yahoo! Search.

Re: [GRASS-dev] patch for v.voronoi/v.delaunay

So maybe the thing to do for now is to mention all these issues in the HTML man page. The BUGS section is silent about them right now. Does the v.voronoi part suffer from the same problems? Benjamin Maris Nartiss wrote: Hi Benjamin, I'm sorry to disappoint You - Your patch does not fix bogous

Re: [GRASS-dev] patch for v.voronoi/v.delaunay

I understand Your (and others) unwillingness to fix this code, still shipping broken code is also not a good thing. It MUST be fixed (patch/rewrite) or there must be some additional checks like if(npointsMAX_INT) G_error(Blah! Decrease input vector size) to avoid producing bogous results

Re: [GRASS-dev] Autoconf 2.13

Hamish wrote: There were also a lot of improvements and tidying recently with regard to making parallel builds work and stopping needless regeneration of HTML documentation on every compile. re. stopping needless regeneration of HTML documentation on every compile: I am still not

[GRASS-dev] Re: [GRASS GIS] #29: moving of vector object by mouse

#29: moving of vector object by mouse --+- Reporter: zanollim | Owner: martinl Type: enhancement | Status: assigned Priority: major| Milestone: 6.4.0

[GRASS-dev] Re: [GRASS GIS] #29: moving of vector object by mouse

#29: moving of vector object by mouse --+- Reporter: zanollim | Owner: martinl Type: enhancement | Status: assigned Priority: major| Milestone: 6.4.0

[GRASS-dev] Re: [GRASS GIS] #29: moving of vector object by mouse

#29: moving of vector object by mouse --+- Reporter: zanollim | Owner: martinl Type: enhancement | Status: assigned Priority: major| Milestone: 6.4.0

Re: [GRASS-dev] module -label versus -description

Hi, 2008/2/4, Hamish [EMAIL PROTECTED]: Hamish wrote: I notice these two changes: (are there more?) http://trac.osgeo.org/grass/changeset/25463 http://trac.osgeo.org/grass/changeset/29533 They are good candidates to use both module-label and module-description. Using both

Re: [GRASS-dev] convert 3D polygons or Tins to a DEM?

Hi, 2008/2/4, Hamish [EMAIL PROTECTED]: Benjamin Ducke: If we have 3D input points for the TIN construction, then the resulting triangles should be 3D face primitives not areas (of which I assumed they were 2D primitives in the GRASS vector model), shouldn't they? Martin Landa

[GRASS-dev] Re: [GRASS GIS] #24: Zoom in / Zoom out enhancement

#24: Zoom in / Zoom out enhancement --+- Reporter: zanollim | Owner: martinl Type: enhancement | Status: closed Priority: trivial | Milestone: 6.4.0 Component: Python |

Re: [GRASS-dev] What Tcl/Tk version?

was scrubbed... URL: http://lists.osgeo.org/pipermail/grass-dev/attachments/ 20080204/7dc65dfc/attachment-0001.html -- There have been problems reported using 8.5 on Windows and Mac. These are probably solvable, but I don't think they've been solved. Depending on how

[GRASS-dev] d.where -w problem

Hi, I'm having issues with projections in GRASS. I have two co-located projects, one in UTM projection, the other in an Oblique Mercator (omerc). The problem I'm having is when I query the rotated Hotine projection with d.where -w, the returned Lat, Lon is nonsensical. However, geotiffs

Re: R: [GRASS-dev] What Tcl/Tk version?

; is this version still suggested? would be 8.4.17 (last before 8.5) good? Thanks Marco -- next part -- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/grass-dev/attachments/ 20080204/7dc65dfc/attachment-0001.html -- There have

Re: [GRASS-dev] erratic behavior of v.in.ascii with WinGRASS

Michael Barton wrote: I've run into a problem running v.in.ascii for WinGRASS importing an ASCII points file. Sometimes it works OK. Other times, it causes a Windows dbf.exe error but still gets the job done. In most cases, it causes a dbf.exe error and only imports the first point--with a

Re: [GRASS-dev] erratic behavior of v.in.ascii with WinGRASS

On Feb 4, 2008, at 7:23 PM, Hamish wrote: Michael Barton wrote: I've run into a problem running v.in.ascii for WinGRASS importing an ASCII points file. Sometimes it works OK. Other times, it causes a Windows dbf.exe error but still gets the job done. In most cases, it causes a dbf.exe error

Re: [GRASS-dev] erratic behavior of v.in.ascii with WinGRASS

I just emailed you the response - it is the fs=| try to skip it to see what happens. It does not seem to have anything with the data in the file Helena Helena Mitasova Associate Professor Department of Marine, Earth and Atmospheric Sciences 1125 Jordan Hall, Campus Box 8208 North Carolina

Re: [GRASS-dev] erratic behavior of v.in.ascii with WinGRASS

I did few more experiments (with a different file, but still generated by GRASS - this time using v.out.ascii) and it indeed looks like the fs=| is responsible for the truly erratic behavior - I think that without quotes it is represented as pipe(?) so depending on where you put it you get