#1747: v.rast.stats on dbf shapefile not enough precision even with DOUBLE
PRECISION
---+
Reporter: vesnikos | Owner: grass-dev@…
Type: defect| Status: closed
Prior
On Mon, May 5, 2014 at 8:52 PM, Markus Neteler wrote:
> On Tue, Apr 29, 2014 at 6:29 PM, Markus Neteler wrote:
>> On Sun, Apr 20, 2014 at 7:38 PM, Markus Neteler wrote:
>>> in order to prepare the 6.4.4RC1, please check:
Draft announcement to be updated:
http://trac.osgeo.org/grass/wiki/Release
#2120: wxgui: encoding errors
-+--
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.4
#1461: Broken Links in man page for r.random.surface in grass 6.5
--+-
Reporter: dnewcomb | Owner:
grass-dev@…
Type: defect|
On Wed, Apr 9, 2014 at 4:07 AM, Glynn Clements wrote:
> Packages which include command-line programs (e.g. compilers)
> typically either modify the environment variables (e.g. PATH) via the
> registry[1], or provide a .bat/.cmd file which must be run to set up
> the environment for a particular sh
#1438: g.remove cannot remove vector map because of space in DB layer name
--+-
Reporter: arencambre | Owner: grass-dev@…
Type: defect | Status: reopened
Priorit
1. We may need to break backward compatibility at some point to improve the
data structure. As long as we keep the same file format, we could provide a
tool to build old databases out of new ones.
2. Good point and right, even now, cell_misc has subdirectories, not files.
If we really want to have
Huidae Cho wrote:
> I think in the long term it would be better to change the raster directory
> structure such that raster and vector have the same mapset/(raster,
> vector)/mapname/element path. Then we would be able to move some useful
> element related functions from librast to libgis.
The m
With option 1) , would the tool also operate on externally linked datasets
( via v.external and r.external) ?
Doug
On Wed, May 14, 2014 at 4:06 PM, Matej Krejci wrote:
> Hi,
>
> I would like to discuss the metadata management in GRASS which is my topic
> for GSOC.
>
> My idea for GSOC term is
#2290: Grass not starting
--+-
Reporter: dnewcomb | Owner: grass-dev@…
Type: defect| Status: new
Priority: normal| Milestone: 7.0.0
Comp
Hi,
I would like to discuss the metadata management in GRASS which is my topic
for GSOC.
My idea for GSOC term is to Python library, command line modules and wxGUI
front-end.
The current plan has two parts, however the second one is optional.
1)
Main task is to make Python library that can crea
#2290: Grass not starting
--+-
Reporter: dnewcomb | Owner: grass-dev@…
Type: defect| Status: new
Priority: normal| Milestone: 7.0.0
Comp
Here is the error message. Any thoughts or does this need a ticket?
Errors in:
/Users/cmbarton/Dropbox/GRASS_dropbox/source/grass64_rb/imagery/i.pca
--
In case of errors please change into the directory with error and run 'make'.
If you get multiple errors, you need to deal with them in the order
Hi,
2014-05-14 15:32 GMT+02:00 Vaclav Petras :
> Hi, Trac wiki is the right choice, IMHO. There is somewhere an email
> explaining all the reasons for it. The student's GSoC page should be subpage
> of GSoC/2014, e.g. GSoC/2014/Metadata or GSoC/2014/MetadataForGRASS (the
> official name does not h
Hi,
2014-05-14 15:32 GMT+02:00 Vaclav Petras :
> Hi, Trac wiki is the right choice, IMHO. There is somewhere an email
> explaining all the reasons for it. The student's GSoC page should be subpage
> of GSoC/2014, e.g. GSoC/2014/Metadata or GSoC/2014/MetadataForGRASS (the
> official name does not h
#2291: Python not quitting on exit
---+
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Hi, Trac wiki is the right choice, IMHO. There is somewhere an email
explaining all the reasons for it. The student's GSoC page should be
subpage of GSoC/2014, e.g. GSoC/2014/Metadata or GSoC/2014/MetadataForGRASS
(the official name does not have to be in URL, it is enough if it is in the
main head
#2290: Grass not starting
--+-
Reporter: dnewcomb | Owner: grass-dev@…
Type: defect| Status: new
Priority: normal| Milestone: 7.0.0
Comp
fyi from the GDAL-dev ML
http://lists.osgeo.org/pipermail/gdal-dev/2014-May/039054.html
-
Even Rouault:
Hi,
I've followed the update process of the EPSG SRS database to latest v8.4,
and
just committed the updated files into libgeotiff, GDAL and PROJ trunk. Also
submitted t
On Tue, May 13, 2014 at 10:23 PM, Glynn Clements
wrote:
>
> Markus Neteler wrote:
>
>> I tried my current start-python-and-create-a-location script on Windows.
>> The location is generated but then a call of the scripting library fails
>> with a gettext error (I print the os.environment to underst
Hi,
I have a set of faults (lines made from 2 points only)
and my target is to calculate the distance from a city to all of the
faults in the region.
Ideally I would need the location (X,Y) of the mid-point of the line,
but if I can extract the two tipline nodes coordinates, then it is
half-way t
I somehow missed the v.to.db option:
start: line/boundary starting point coordinates, X,Y or X,Y,Z
end: line/boundary end point coordinates, X,Y or X,Y,Z
On 14/05/2014, Yann Chemin wrote:
> Hi,
>
> I have a set of faults (lines made from 2 points only)
> and my target is to calculate the dista
#1682: incorrect output from v.voronoi
---+
Reporter: MichaelP | Owner: grass-dev@…
Type: defect| Status: closed
Priority: major | Milestone: 6.4.4
#1682: incorrect output from v.voronoi
---+
Reporter: MichaelP | Owner: grass-dev@…
Type: defect | Status: new
Priority: major | Milestone: 6.4.4
#1397: Lat/lon compatibility for r.water.outlet
+---
Reporter: awickert| Owner: grass-dev@…
Type: defect | Status: new
Priority: major | Mi
#1452: wx location wizard doesn't ask for datum transform options because proj4
4.7.1's epsg file is broken
-+--
Reporter: hamish | Owner: hamish
Type: defect | S
#335: export floats and doubles with correct precision
---+
Reporter: hamish | Owner: grass-dev@…
Type: task | Status: new
Priority: critical | Milestone:
OK, thanks, that looks interesting. I really should get into Python.. would
be great if this could work with raster data as input, e.g., for species
distribution modelling. I can imagine that this might be a (faster)
alternative to modelling in R (especially the model projection part, which
can be
#2087: grass64 man page: missing words
+---
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: critical| Milestone: 6.4.4
#2087: grass64 man page: missing words
+---
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: critical| Milestone: 6.4.4
#2291: Python not quitting on exit
---+
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
#2253: WinGRASS doesn't allow to close console window
---+
Reporter: martinl| Owner: grass-dev@…
Type: defect | Status: new
Prior
#2291: Python not quitting on exit
---+
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
On 13/05/14 22:27, Paulo van Breugel wrote:
Does anybody have experience with the scikit-learn toolkit? It seems
like a very extensive tool set for machine learning in Python. I have no
experience in programming in Python, so I cannot really judge how
difficult it would be to call functions from
34 matches
Mail list logo
