[GRASS-dev] [GRASS GIS] #2266: g.list and g.mlist should be able to handle strds, str3ds, stvds
#2266: g.list and g.mlist should be able to handle strds, str3ds, stvds -+-- Reporter: sbl | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: 7.0.0 Component: Default | Version: unspecified Keywords: g.list, g.mlist |Platform: Unspecified Cpu: Unspecified | -+-- g.list and g.mlist should be able to list space time dataset names (strds, str3ds, stvds) (not the single maps registered). -- Ticket URL: http://trac.osgeo.org/grass/ticket/2266 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] #2266: g.list and g.mlist should be able to handle strds, str3ds, stvds
#2266: g.list and g.mlist should be able to handle strds, str3ds, stvds -+-- Reporter: sbl | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: 7.0.0 Component: Temporal | Version: unspecified Keywords: g.list, g.mlist |Platform: Unspecified Cpu: Unspecified | -+-- Changes (by neteler): * component: Default = Temporal Comment: These new elements need to be added in lib/manage/element_list -- Ticket URL: http://trac.osgeo.org/grass/ticket/2266#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] #2266: g.list and g.mlist should be able to handle strds, str3ds, stvds
#2266: g.list and g.mlist should be able to handle strds, str3ds, stvds -+-- Reporter: sbl | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: 7.0.0 Component: Temporal | Version: unspecified Keywords: g.list, g.mlist |Platform: Unspecified Cpu: Unspecified | -+-- Comment(by neteler): Replying to [comment:1 neteler]: These new elements need to be added in lib/manage/element_list In fact no since these elements are in the SQL DB. So http://grass.osgeo.org/grass71/manuals/t.list.html -- Ticket URL: http://trac.osgeo.org/grass/ticket/2266#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] #2266: g.list and g.mlist should be able to handle strds, str3ds, stvds
#2266: g.list and g.mlist should be able to handle strds, str3ds, stvds --+- Reporter: sbl | Owner: grass-dev@… Type: enhancement | Status: closed Priority: normal | Milestone: 7.0.0 Component: Temporal | Version: unspecified Resolution: invalid |Keywords: g.list, g.mlist Platform: Unspecified | Cpu: Unspecified --+- Changes (by sbl): * status: new = closed * resolution: = invalid Comment: Sorry for the noise, I should read the manuals more carefully... Just found it natural to have it g.list since also imagery groups can be listed in g.list... -- Ticket URL: http://trac.osgeo.org/grass/ticket/2266#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] #2266: g.list and g.mlist should be able to handle strds, str3ds, stvds
#2266: g.list and g.mlist should be able to handle strds, str3ds, stvds --+- Reporter: sbl | Owner: grass-dev@… Type: enhancement | Status: reopened Priority: normal | Milestone: 7.0.0 Component: Temporal | Version: unspecified Resolution: |Keywords: g.list, g.mlist Platform: Unspecified | Cpu: Unspecified --+- Changes (by martinl): * status: closed = reopened * resolution: invalid = Comment: Replying to [comment:3 sbl]: Sorry for the noise, I should read the manuals more carefully... Just found it natural to have it g.list since also imagery groups can be listed in g.list... Manual of `g.list` should note that, reopening this ticket. -- Ticket URL: http://trac.osgeo.org/grass/ticket/2266#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] #2266: g.list and g.mlist should be able to handle strds, str3ds, stvds
#2266: g.list and g.mlist should be able to handle strds, str3ds, stvds --+- Reporter: sbl | Owner: grass-dev@… Type: enhancement | Status: reopened Priority: normal | Milestone: 7.0.0 Component: Temporal | Version: unspecified Resolution: |Keywords: g.list, g.mlist Platform: Unspecified | Cpu: Unspecified --+- Comment(by neteler): Replying to [comment:4 martinl]: Replying to [comment:3 sbl]: Sorry for the noise, I should read the manuals more carefully... Just found it natural to have it g.list since also imagery groups can be listed in g.list... Manual of `g.list` should note that, reopening this ticket. Crosslinks added in r59966 and r59967 -- Ticket URL: http://trac.osgeo.org/grass/ticket/2266#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] #1343: v.buffer2: difference between Linux 32bit and 64bit
#1343: v.buffer2: difference between Linux 32bit and 64bit ---+ Reporter: mmetz | Owner: grass-dev@… Type: defect| Status: reopened Priority: critical | Milestone: 7.0.0 Component: Default | Version: svn-develbranch6 Resolution:|Keywords: v.buffer Platform: Linux | Cpu: x86-64 ---+ Comment(by neteler): v.buffer has been rebased on GEOS in r59970 which you now need to compile the module. Please test the updated version of v.buffer in 6.4.svn. -- Ticket URL: http://trac.osgeo.org/grass/ticket/1343#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] 6.4.4 planning
Hi, On Sun, Apr 20, 2014 at 7:38 PM, Markus Neteler nete...@osgeo.org wrote: Hi devs, in order to prepare the 6.4.4RC1, please check: Important bugs concerning the next release https://trac.osgeo.org/grass/report/13 now v.buffer has been fixed by Markus Metz (using the GEOS library). Please test. I have updated to some extent the draft release notes (please add more): https://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS] #2268: t.list.rast where sensitivity
#2268: t.list.rast where sensitivity
-+--
Reporter: martinl | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Temporal | Version: svn-trunk
Keywords: t.list.rast |Platform: Unspecified
Cpu: Unspecified |
-+--
{{{
t.rast.list modis_m where=start_time 2002-03-01
}}}
gives no output, no warning - note missing quotes around date, ie.
{{{
t.rast.list modis_m where=start_time '2002-03-01'
}}}
--
Ticket URL: http://trac.osgeo.org/grass/ticket/2268
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] #2267: t.list doesn't respect search path
#2267: t.list doesn't respect search path -+-- Reporter: martinl | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.0.0 Component: Temporal | Version: svn-trunk Keywords: t.list, search path |Platform: Unspecified Cpu: Unspecified | -+-- Comment(by annakrat): In animation tool, when you don't provide the name without mapset, I try to guess the mapset and the first would be the `modis@landamar`. So I am not sure if this [http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/animation/utils.py#L58 function] is wrong or if the output of t.list is wrong. t.list just gives back the result of a SELECT in a database ordered alphabetically. Should t.list return the results based on the search path if user doesn't specify order? Or we perhaps need a function in the temporal API which would behave like g.findfile? How is this solved in the temporal modules? -- Ticket URL: http://trac.osgeo.org/grass/ticket/2267#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] #2267: t.list doesn't respect search path
#2267: t.list doesn't respect search path -+-- Reporter: martinl | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.0.0 Component: Temporal | Version: svn-trunk Keywords: t.list, search path |Platform: Unspecified Cpu: Unspecified | -+-- Comment(by martinl): Replying to [comment:1 annakrat]: In animation tool, when you don't provide the name without mapset, I try to guess the mapset and the first would be the `modis@landamar`. So I am not sure if this BTW, `g.gui.timeline` shows a dialog where the user can choose which dataset he/she wants to use. -- Ticket URL: http://trac.osgeo.org/grass/ticket/2267#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
[GRASS-dev] [GRASS GIS] #2269: r.univar silent instead of NaN
#2269: r.univar silent instead of NaN
-+--
Reporter: neteler | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.4
Component: Raster | Version: svn-releasebranch64
Keywords: r.univar |Platform: Unspecified
Cpu: Unspecified |
-+--
r.univar should not remain silent when the computational
region is only containing NULL cells. Instead NaN should be
printed as result for the individual min, max, etc values.
{{{
GRASS 6.4.4svn (nc_spm_08):~ g.region n=1 s=0 w=0 e=1 res=0.5 -p
projection: 99 (Lambert Conformal Conic)
zone: 0
datum: nad83
ellipsoid: a=6378137 es=0.006694380022900787
north: 1
south: 0
west: 0
east: 1
nsres: 0.5
ewres: 0.5
rows: 2
cols: 2
cells: 4
GRASS 6.4.4svn (nc_spm_08):~ r.univar elevation
100%
GRASS 6.4.4svn (nc_spm_08):~ r.univar elevation -g
GRASS 6.4.4svn (nc_spm_08):~
}}}
The issue is in r.univar, stats.c line 123. However, not
that easy to fix since sometimes zones are considered,
sometimes not.
--
Ticket URL: http://trac.osgeo.org/grass/ticket/2269
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] #2271: t.rast.mapcalc2 x t.rast.mapcalc
#2271: t.rast.mapcalc2 x t.rast.mapcalc -+-- Reporter: martinl | Owner: grass-dev@… Type: task | Status: new Priority: blocker | Milestone: 7.0.0 Component: Temporal | Version: unspecified Keywords: t.rast.mapcalc2 |Platform: Unspecified Cpu: Unspecified | -+-- Before releasing GRASS 7 the module `t.rast.mapcalc2` should be renamed or merged with `t.rast.mapcalc`. -- Ticket URL: http://trac.osgeo.org/grass/ticket/2271 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] #2270: t.list.rast where =/=
#2270: t.list.rast where =/= +--- Reporter: martinl | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.0.0 Component: Temporal| Version: unspecified Keywords: t.list.rast, where |Platform: Unspecified Cpu: Unspecified | +--- Comment(by martinl): Replying to [comment:1 huhabla]: This is the magic of sqlite and postgresql regarding dates that are defined without time. This is not related to the implementation of TGRASS but to the chosen backend database. Ah, so maybe big note about that in the manual? :-) -- Ticket URL: http://trac.osgeo.org/grass/ticket/2270#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] #2271: t.rast.mapcalc2 x t.rast.mapcalc
#2271: t.rast.mapcalc2 x t.rast.mapcalc -+-- Reporter: martinl | Owner: grass-dev@… Type: task | Status: new Priority: blocker | Milestone: 7.0.0 Component: Temporal | Version: unspecified Keywords: t.rast.mapcalc2 |Platform: Unspecified Cpu: Unspecified | -+-- Comment(by huhabla): t.rast.mapcalc and t.rast.mapcalc2 are implementing different of spatio- temporal algebra approaches and can't be merged. t.rast.mapcalc2 is using PLY to implement a new algebra (GSoC project). In case PLY is not available, t.rast.mapcalc can be used instead supporting only a very limited but still powerful spatio-temporal algebra. I strongly suggest to not include the temporal algebra classes, tests, the modules t.select, t.vect.mapcalc, t.rast.mapcalc2 and t.rast3d.mapcalc2 into the grass70 beta release. The temporal algebra implementation is still very experimental. -- Ticket URL: http://trac.osgeo.org/grass/ticket/2271#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] #2271: t.rast.mapcalc2 x t.rast.mapcalc
#2271: t.rast.mapcalc2 x t.rast.mapcalc -+-- Reporter: martinl | Owner: grass-dev@… Type: task | Status: new Priority: normal | Milestone: 7.0.0 Component: Temporal | Version: unspecified Keywords: t.rast.mapcalc2 |Platform: Unspecified Cpu: Unspecified | -+-- Changes (by martinl): * priority: blocker = normal -- Ticket URL: http://trac.osgeo.org/grass/ticket/2271#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
[GRASS-dev] sample dataset for temporal data
Hi, since more and more users are using temporal framework, we should consider creating a sample dataset for temporal data. This could be used in the manual pages of t.* modules. Some of them still don't have any example and the existing examples are based on tests with generated data which is not the best way. Some time ago I created a climate dataset for North Carolina from publicly available data, it has monthly temperature average and monthly precipitation from 2000 to 2012. You can download it from here: http://courses.ncsu.edu/mea592/common/media/02/nc_climate_spm_2000_2012.zip There are no temporal vector data, just the standard precip. stations vector from nc_spm_08. So I suggest to use this, because it's consistent with nc_spm_08 but feel free to suggest something else. Best, Anna ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
