Re: [GRASS-dev] [GRASS GIS] #1318: DebCheck QA: Memory leaks
#1318: DebCheck QA: Memory leaks +--- Reporter: hamish | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 6.4.3 Component: Compiling | Version: 6.4.0 Keywords: gem, lib/bitmap, shapelib, lib/iostream, dglib, r.li, nviz | Platform: Linux Cpu: Unspecified | +--- Changes (by hamish): * milestone: 6.4.2 = 6.4.3 Comment: visualization/nviz/src/togl.c fixed in devbr6 r55837. lib/external/shapelib/shpopen.c fixed in trunk and devbr6 with r55838,9. Hamish -- Ticket URL: https://trac.osgeo.org/grass/ticket/1318#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] #1323: DebCheck QA: Resource leaks
#1323: DebCheck QA: Resource leaks ---+ Reporter: hamish | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 6.4.4 Component: Compiling | Version: 6.4.0 Keywords: gem, i.ortho.photo, i.points, i.vpoints, lib/cairodriver, lib/gis/copy_file.c, lib/gis/error.c, lib/gis/ls.c, r.li, r.mfilter, r.mfilter.fp, r.out.gridatb, r.statistics, r.terraflow, r3.in.v5d, r3.out.v5d, r3.showdspf |Platform: Linux Cpu: Unspecified | ---+ Changes (by hamish): * milestone: 6.4.2 = 6.4.4 Comment: d.profile done in devbr6 with r55840. -- Ticket URL: https://trac.osgeo.org/grass/ticket/1323#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] #1326: DebCheck QA: fflush() called on input stream stdin may result in undefined behaviour
#1326: DebCheck QA: fflush() called on input stream stdin may result in
undefined behaviour
+---
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.3
Component: Compiling | Version: 6.4.0
Keywords: lib/edit, lib/vask |Platform: Linux
Cpu: Unspecified |
+---
Changes (by hamish):
* milestone: 6.4.2 = 6.4.3
Comment:
{{{
fflush(stdin);
}}}
-
{{{
#include stdio.h
scanf(%*[^\n]%*c);
}}}
?,
Hamish
--
Ticket URL: https://trac.osgeo.org/grass/ticket/1326#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] #767: g.copy only issues warning when destination exists
#767: g.copy only issues warning when destination exists --+- Reporter: ferrouswheel | Owner: grass-dev@… Type: enhancement | Status: new Priority: major | Milestone: 6.4.4 Component: Default | Version: svn-develbranch6 Keywords: g.copy, g.rename |Platform: Unspecified Cpu: Unspecified | --+- Comment(by hamish): see also #1658 -- Ticket URL: https://trac.osgeo.org/grass/ticket/767#comment:7 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] #1695: WinGRASS does not launch (was: GRASSGIS does not launch)
#1695: WinGRASS does not launch --+- Reporter: TheloniusMonk | Owner: grass-dev@… Type: defect| Status: new Priority: major | Milestone: 6.4.3 Component: Startup | Version: 6.4.2 Keywords: launch, wingrass |Platform: MSWindows 7 Cpu: x86-64| --+- Changes (by hamish): * component: Default = Startup -- Ticket URL: https://trac.osgeo.org/grass/ticket/1695#comment:8 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] #731: Warning message after removing layer confusing (was: Warming message after removing layer confusing)
#731: Warning message after removing layer confusing
-+--
Reporter: pvanbosgeo | Owner: grass-dev@…
Type: defect | Status: closed
Priority: normal | Milestone: 6.4.0
Component: Default | Version: svn-develbranch6
Resolution: fixed |Keywords: g.remove, delete, message
Platform: Linux | Cpu: x86-64
-+--
Changes (by hamish):
* keywords: remove, delete, message = g.remove, delete, message
* status: new = closed
* resolution: = fixed
Comment:
current behaviour in 6.4.3svn:
{{{
GRASS g.copy geology,geology
Copy raster geology@PERMANENT to current mapset as geology
GRASS g.remove geology
Removing raster geology
WARNING: 'cell/geology' was found in more mapsets (also found in
PERMANENT)
WARNING: Using geology@user1
}}}
seems like it got fixed.
note only maps from the current mapset can be written to (or deleted).
Hamish
--
Ticket URL: https://trac.osgeo.org/grass/ticket/731#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] #891: add a command g.move
#891: add a command g.move --+- Reporter: timmie | Owner: grass-dev@… Type: enhancement | Status: closed Priority: normal | Milestone: 6.5.0 Component: Default | Version: unspecified Resolution: wontfix |Keywords: g.move Platform: Unspecified | Cpu: Unspecified --+- Changes (by hamish): * keywords: = g.move * status: new = closed * resolution: = wontfix Comment: It's not really about other users on the system (you can't write to directories you don't own either, and grass enforces that for mapset access even if there is filesystem group write permissions set), it's more about safe concurrent use. If you had two GRASS sessions running in parallel, it wouldn't be very nice if the other one suddenly overwrote a map in the one you were working in. The same is true for why starting two GRASSes running in the same mapset is disallowed (also in that case a change by g.region by the twin session could be damaging). so it's about keeping the paperwork in order and goes pull, not push. see also the r.pack, r.unpack modules if you need to transfer maps between different systems/locations, and g.laptop.sh from Addons: http://grasswiki.osgeo.org/wiki/AddOns/GRASS_6#g.laptop.sh Hamish -- Ticket URL: https://trac.osgeo.org/grass/ticket/891#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] #953: module help information in machine-readable format
#953: module help information in machine-readable format +--- Reporter: cmbarton| Owner: glynn Type: enhancement | Status: new Priority: normal | Milestone: 6.5.0 Component: Default | Version: unspecified Keywords: help, metadata |Platform: All Cpu: All | +--- Comment(by hamish): can we consider the wish completed? -- Ticket URL: https://trac.osgeo.org/grass/ticket/953#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] #1371: Error on saving a named region which was saved previously
#1371: Error on saving a named region which was saved previously --+- Reporter: MilenaN | Owner: grass-dev@… Type: defect| Status: new Priority: normal| Milestone: 6.4.3 Component: Default | Version: svn-develbranch6 Keywords: g.region |Platform: MSWindows 7 Cpu: x86-64| --+- Changes (by hamish): * keywords: region = g.region * version: svn-trunk = svn-develbranch6 * milestone: = 6.4.3 Comment: `g.region save=test123@current_mapset` now works in trunk, but not 6.x. support for stripping away @current_mapset added to devbr6 in r55841. please test. Hamish -- Ticket URL: https://trac.osgeo.org/grass/ticket/1371#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-user] Using r.quantile result with r.recode
Hi Glynn, - Original Message - From: Glynn Clements r.recode will treat boundary values as belonging to the upper range, e.g. in the above example, 6.0 will get recoded to 2. So we can not use directly the result of r.quantile with -r flag in r.recode, right? In the example, 6 should be recoded to 1, right? Thank you very much! Best regards, Pedro Pedro Venâncio wrote: Thank you very much for your answer! My question lies precisely in the need to know if a quantile value which falls as the upper limit for one range and the lower limit of the next, should belong to the class anterior or posterior. For example, assuming that r.quantile (with -r flag) gives this result: 2:6:1 6:8:2 8:12:3 12:20:4 20:873:5 the value 6 should belong to the first class or second? r.recode will treat boundary values as belonging to the upper range, e.g. in the above example, 6.0 will get recoded to 2. This behaviour stems from Rast_fpreclass_get_cell_value() in lib/raster/fpreclass.c, and isn't configurable (i.e. there's no way that r.recode's behaviour could be modified without modifying the fpreclass functions). -- Glynn Clements gl...@gclements.plus.com ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #1530: g.region shrink / expand parameter
#1530: g.region shrink / expand parameter --+- Reporter: alf | Owner: grass-dev@… Type: enhancement | Status: closed Priority: normal | Milestone: 6.4.3 Component: Default | Version: 6.4.1 Resolution: fixed|Keywords: g.region, expand Platform: Unspecified | Cpu: Unspecified --+- Changes (by hamish): * status: reopened = closed * resolution: = fixed Comment: g.region.grow module added to grass6 addons in r55843. http://grasswiki.osgeo.org/wiki/AddOns/GRASS_6#g.region.grow Instead of `rows=rows+2*n cols=cols+2*n` (or `rows=rows-2*n cols=cols-2*n`) I took the easy way and made use of the g.region -a flag, which rounds outwards to the nearest whole-cell. Feel free to reopen the wish if you'd like to see a -c flag added to make the expand= (should it be called amount= or extent=?) refer to cells not map units. Hamish -- Ticket URL: https://trac.osgeo.org/grass/ticket/1530#comment:7 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] #131: Tool to assist creation (design) of simple scripts within from the wxpython-GUI
#131: Tool to assist creation (design) of simple scripts within from the wxpython-GUI --+- Reporter: nikos | Owner: grass-dev@… Type: enhancement | Status: new Priority: minor | Milestone: 6.5.0 Component: Default | Version: unspecified Keywords: GUI, script creation |Platform: Unspecified Cpu: Unspecified | --+- Comment(by hamish): done by the now-developed modeler? -- Ticket URL: https://trac.osgeo.org/grass/ticket/131#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] #131: Tool to assist creation (design) of simple scripts within from the wxpython-GUI
#131: Tool to assist creation (design) of simple scripts within from the wxpython-GUI --+- Reporter: nikos | Owner: grass-dev@… Type: enhancement | Status: new Priority: minor | Milestone: 6.5.0 Component: Python| Version: unspecified Keywords: GUI, script creation |Platform: Unspecified Cpu: Unspecified | --+- Changes (by hamish): * component: Default = Python -- Ticket URL: https://trac.osgeo.org/grass/ticket/131#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] wiki pages buttons for G+ FB
Hi, 2013/4/17 Yann Chemin yann.che...@gmail.com: some of the wiki pages would be useful to some students/friends hanging around the FB and G+ spheres, would it be possible to add such social media buttons on the wiki pages? generally speaking, it's possible [1,2] and others. If you think that it's useful, I can install this extension to our mediawiki. Martin [1] http://www.mediawiki.org/wiki/Extension:AddThis [2] http://www.mediawiki.org/wiki/Extension:TwitterFBLike ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #1068: unnecessary error information at GRASS startup
#1068: unnecessary error information at GRASS startup
--+-
Reporter: msieczka | Owner: grass-dev@…
Type: defect| Status: new
Priority: minor | Milestone: 6.4.0
Component: Startup | Version: svn-releasebranch64
Keywords:|Platform: All
Cpu: All |
--+-
Changes (by hamish):
* component: Default = Startup
Comment:
If the last-known mapset or location isn't found any more, an error saying
it isn't found seems entirely appropriate. The expected behaviour (load up
the last mapset) is not possible, and any time that the expected thing
isn't going to happen there should be warning bells sounding.
The thing to worry about, I think, is how well it recovers from that
situation..
the current 6.x wxGUI gives this in the terminal if the mapset went away:
{{{
...
ERROR: MAPSET user1 not found
ERROR: Mapset user1 not found
}}}
but loads up the loc'n with the list of existing mapsets.
If the loc'n is no longer there the wxGUI startup gives you:
{{{
Cleaning up temporary files ...
Starting GRASS ...
access: No such file or directory
ERROR: LOCATION /path/to/old/name not available
}}}
then loads up the GISDBASE dir and selects the first loc'n there.
The -text version gives this after esc-enter, then asks if you want to
create it.
{{{
Mapset user1 is not available
}}}
For an invalid loc'n it is similar: asks if you wish to create a new loc'n
by that name.
it all seems ok to me.
Hamish
--
Ticket URL: https://trac.osgeo.org/grass/ticket/1068#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] #1880: change color field to text for d.vect.chart
#1880: change color field to text for d.vect.chart +--- Reporter: cmbarton | Owner: grass-dev@… Type: defect | Status: closed Priority: major | Milestone: 6.4.3 Component: Display| Version: 6.4.2 RCs Resolution: duplicate |Keywords: d.vect.chart, d.thematic.area, color arguments Platform: All| Cpu: All +--- Changes (by annakrat): * status: new = closed * resolution: = duplicate Comment: This is a duplicate of #1774 which has been fixed in 6.4 and 7 and now also in 6.5 (r55845). -- Ticket URL: https://trac.osgeo.org/grass/ticket/1880#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] #1109: g.mlist functionality extension: return e.g. $prefix.001 to $prefix.031 out of $prefix.365 maps
#1109: g.mlist functionality extension: return e.g. $prefix.001 to $prefix.031 out of $prefix.365 maps ---+ Reporter: nikos | Owner: grass-dev@… Type: enhancement| Status: new Priority: minor | Milestone: Component: Default| Version: unspecified Keywords: g.mlist, pattern, |Platform: Unspecified Cpu: Unspecified| ---+ Comment(by hamish): How about a `g.name.sequence` wrapper module with mandatory min= max= basename= options and an optional padding(?)= option (default=3) for this? g.sequence min=32 max=59 pad=4 base=day. would print to stdout `day.0032,day.0033,...,day.0059`. ? then you wouldn't have to be a UNIX power tools or python expert to make it happen. Hamish -- Ticket URL: https://trac.osgeo.org/grass/ticket/1109#comment:11 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] #1109: g.mlist functionality extension: return e.g. $prefix.001 to $prefix.031 out of $prefix.365 maps
#1109: g.mlist functionality extension: return e.g. $prefix.001 to $prefix.031 out of $prefix.365 maps --+- Reporter: nikos| Owner: grass-dev@… Type: enhancement | Status: closed Priority: minor| Milestone: Component: Default | Version: unspecified Resolution: fixed|Keywords: g.mlist, pattern, Platform: Unspecified | Cpu: Unspecified --+- Changes (by hamish): * status: new = closed * resolution: = fixed Comment: Replying to [comment:11 hamish]: How about a `g.name.sequence` wrapper module done for g6 addons in r55850. http://grasswiki.osgeo.org/wiki/AddOns/GRASS_6#g.name.sequence enjoy, Hamish -- Ticket URL: https://trac.osgeo.org/grass/ticket/1109#comment:12 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] v.generalize smoothing loop support
On Wed, Apr 17, 2013 at 10:54 AM, Miroslav Talasek miroslav.tala...@seznam.cz wrote: hi all i try make contours from DEM ASTER and i was successfull but contorus is ugly i try use v.generalze but this function cant change firt and las point , but some contrours is like loop (first and last point is the same) so after smoothing with sliging_averaging algo part around start point look_ahead wide was unchanged iwas so ugly , so i write patch which implementing loop line support , check if line is loop (start and endpoint is same ) and smooting correctly, is it usabel for others ? Yes, I think this is usuable for others. Do you mind sending the patch? Markus M attachment: black is war contours, blue is orig algo and red is with my patch -- MSc. Miroslav Talasek Developer, Team leader Seznam.cz, a.s. Prague Czech Republic tel.:+420 234 694 722 fax: +420 234 694 115 gsm: +420 608 934 724 jabber: mire...@jabber.cz work-email: miroslav.tala...@firma.seznam.cz email: miroslav.tala...@seznam.cz web:http://photo.talasek.sk ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS] #1932: r.univar segfault on map with massive values
#1932: r.univar segfault on map with massive values
--+-
Reporter: hamish| Owner: grass-dev@…
Type: defect| Status: new
Priority: normal| Milestone: 6.4.3
Component: Raster| Version: svn-develbranch6
Keywords: r.univar |Platform: Linux
Cpu: x86-64|
--+-
as seen on the ML:
http://lists.osgeo.org/pipermail/grass-user/2013-April/067810.html
r.univar's stack gets smashed if the values in the map are huge:
{{{
G65 g.region -d# spearfish
G65 r.mapcalc bigvals = 1.0e200 * elevation.10m
G65 r.info -r bigvals
min=1.06206e+203
max=1.846390747e+203
G65 r.univar bigvals
100%
Segmentation fault
G65 g.gisenv set=DEBUG=5
G65 r.univar bigvals
...
D2/5: G__read_Cell_head
D2/5: G__read_Cell_head_array
D3/5: region item: proj: 1
D3/5: region item: zone: 13
D3/5: region item: north: 4928010
D3/5: region item: south: 4913700
D3/5: region item: east: 609000
D3/5: region item: west: 589980
D3/5: region item: cols: 634
D3/5: region item: rows: 477
D3/5: region item: e-w resol: 30
D3/5: region item: n-s resol: 30
D3/5: region item: format: -1
D3/5: region item: compressed: 1
D3/5: create window mapping (634 columns)
100%
Segmentation fault
G65 g.gisenv set=DEBUG=0
G65 gdb `which r.univar`
(gdb) run bigvals
[...]
Program received signal SIGSEGV, Segmentation fault.
0x004036e0 in print_stats (stats=0x608490) at stats.c:141
141 fprintf(stdout, total null and non-null cells: %d\n,
stats[z].size);
}}}
Hamish
--
Ticket URL: https://trac.osgeo.org/grass/ticket/1932
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] #1932: r.univar segfault on map with massive values
#1932: r.univar segfault on map with massive values --+- Reporter: hamish| Owner: grass-dev@… Type: defect| Status: new Priority: normal| Milestone: 6.4.3 Component: Raster| Version: svn-develbranch6 Keywords: r.univar |Platform: Linux Cpu: x86-64| --+- Comment(by hamish): kdbg tells me z=960050486, (*stats).size=302418 stats[1195].size is the biggest array element I can get to before it tells me I can't access the memory address. Hamish -- Ticket URL: https://trac.osgeo.org/grass/ticket/1932#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] v.overlay in grass 7.0 trunk segfault
we can cut contours by polygon but sigsegv is result :(
here is some debug
GRASS 7.0.svn (ncontours_magic):~/grassgis/grass-svn gdb v.overlay
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/local/grass-7.0.svn/bin/v.overlay...done.
(gdb) run ainput=cnt_sm atype=line binput=orez output=cnt_cut_test
operator=and --verbose --overwrite
Starting program: /usr/local/grass-7.0.svn/bin/v.overlay ainput=cnt_sm
atype=line binput=orez output=cnt_cut_test operator=and --verbose
--overwrite
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
WARNING: Vector map cnt_cut_test already exists and will be overwritten
Copying vector features from cnt_sm@miro...
100%
Collecting input attributes...
Copying vector features from orez@miro...
100%
Collecting input attributes...
Breaking lines...
26%
Program received signal SIGSEGV, Segmentation fault.
0x77b7e4b9 in break_lines (Map=0x7fffc020, List_break=0x0,
List_ref=0x61ec60, type=6, Err=0x0, check=0) at break_lines.c:356
356 !touch1_e nodex == BBox-W) ||
(gdb) info local
APoints = 0x4df2a20
BPoints = 0x4df2a50
Points = 0x4df2a80
AXLines = 0x0
BXLines = 0x0
ACats = 0x4df2ab0
BCats = 0x4df2ad0
Cats = 0x4df2af0
i = 0
j = -1
k = 32767
l = -20720
ret = -138628762
atype = 4
btype = 4
aline = 136717
bline = 136717
found = 0
iline = 128
nlines = 461
nlines_org = 137049
naxlines = 0
nbxlines = 0
nx = 0
xx = 0x0
yx = 0x0
zx = 0x0
ABox = {N = 5546310, S = 5414331, E = 399947.402, W =
300473.402, T = 0, B = 0}
BBox = 0x7fffe6f49fe0
List = 0x4df2b10
nbreaks = 0
touch1_n = 1
touch1_s = 1
touch1_e = 0
touch1_w = 1
touch2_n = 0
touch2_s = 1
touch2_e = 1
touch2_w = 1
is3d = 0
node = 136740
anode1 = 136740
anode2 = 136626
bnode1 = 136740
bnode2 = 136626
nodex = 399947.402
nodey = 5414331
a_is_ref = 1
b_is_ref = 1
break_a = 1
break_b = 0
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] v.overlay in grass 7.0 trunk segfault
Hi, 2013/4/17 Miroslav Talasek miroslav.tala...@seznam.cz: we can cut contours by polygon but sigsegv is result :( here is some debug please could you fill a new ticket [1] and to attach sample data for which `v.overlay` crashes? Martin [1] http://trac.osgeo.org/grass/wiki/WikiStart#BugTracking ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] v.generalize smoothing loop support
is it ok ?
it add new parameter loop_support which would be 1 or 0 for loop line
support in
sliging_averaging algo
On 04/17/2013 12:46 PM, Markus Metz wrote:
On Wed, Apr 17, 2013 at 10:54 AM, Miroslav Talasek
miroslav.tala...@seznam.cz wrote:
hi all
i try make contours from DEM ASTER and i was successfull but contorus is
ugly i try use v.generalze but this function cant change firt and las point
, but some contrours is like loop (first and last point is the same) so
after smoothing with sliging_averaging algo part around start point
look_ahead wide was unchanged iwas so ugly , so i write patch which
implementing loop line support , check if line is loop (start and endpoint
is same ) and smooting correctly, is it usabel for others ?
Yes, I think this is usuable for others. Do you mind sending the patch?
Markus M
attachment:
black is war contours, blue is orig algo and red is with my patch
--
MSc. Miroslav Talasek
Developer, Team leader
Seznam.cz, a.s.
Prague
Czech Republic
tel.:+420 234 694 722
fax: +420 234 694 115
gsm: +420 608 934 724
jabber: mire...@jabber.cz
work-email: miroslav.tala...@firma.seznam.cz
email: miroslav.tala...@seznam.cz
web:http://photo.talasek.sk
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Index: vector/v.generalize/point.h
===
--- vector/v.generalize/point.h (revision 55852)
+++ vector/v.generalize/point.h (working copy)
@@ -50,6 +50,12 @@
*/
extern inline void point_assign(struct line_pnts *Points, int index,
int with_z, POINT * res);
+/* assign point Points[index] to the res
+ * if with z = 0 then res.z = 0
+ * loop to infinite
+ */
+extern inline void point_assign_loop(struct line_pnts *Points, int index,
+int with_z, POINT * res);
/* res = k * a */
extern inline void point_scalar(POINT a, double k, POINT * res);
Index: vector/v.generalize/smoothing.c
===
--- vector/v.generalize/smoothing.c (revision 55852)
+++ vector/v.generalize/smoothing.c (working copy)
@@ -70,7 +70,8 @@
/* mcmaster's sliding averaging algorithm. Return the number of points
* in the output line. This equals to the number of points in the
* input line */
-int sliding_averaging(struct line_pnts *Points, double slide, int look_ahead,
+
+int sliding_averaging(struct line_pnts *Points, double slide, int look_ahead, int loop_support,
int with_z)
{
@@ -78,10 +79,23 @@
double sc;
POINT p, tmp, s;
POINT *res;
+int is_loop,count;
+is_loop=0;
n = Points-n_points;
half = look_ahead / 2;
+
+count = n - half;
+/* is it loop ?*/
+if (Points-x[0] == Points-x[n-1]
+ Points-y[0] == Points-y[n-1]
+ (Points-z[0] == Points-z[n-1] || with_z == 0) loop_support){
+is_loop = 1;
+count = n + half;
+
+}
+
if (look_ahead % 2 == 0) {
G_fatal_error(_(Look ahead parameter must be odd));
return n;
@@ -90,7 +104,7 @@
if (look_ahead = n || look_ahead == 1)
return n;
-res = G_malloc(sizeof(POINT) * n);
+res = G_malloc(sizeof(POINT) * (n + half));
if (!res) {
G_fatal_error(_(Out of memory));
return n;
@@ -104,27 +118,38 @@
point_add(p, tmp, p);
}
+
/* and calculate the average of remaining points */
-for (i = half; i + half n; i++) {
- point_assign(Points, i, with_z, s);
+for (i = half; i count; i++) {
+ point_assign_loop(Points, i, with_z, s);
point_scalar(s, 1.0 - slide, s);
point_scalar(p, sc * slide, tmp);
point_add(tmp, s, res[i]);
- if (i + half + 1 n) {
- point_assign(Points, i - half, with_z, tmp);
+ if ((i + half + 1 n) || is_loop ) {
+ point_assign_loop(Points, i - half, with_z, tmp);
point_subtract(p, tmp, p);
- point_assign(Points, i + half + 1, with_z, tmp);
+ point_assign_loop(Points, i + half + 1, with_z, tmp);
point_add(p, tmp, p);
}
}
-for (i = half; i + half n; i++) {
+for (i = half; i count; i++) {
Points-x[i] = res[i].x;
Points-y[i] = res[i].y;
Points-z[i] = res[i].z;
}
+if (is_loop) {
+for (i = 0; i half; i++) {
+Points-x[i] = res[n + i - 1].x;
+Points-y[i] = res[n + i - 1].y;
+Points-z[i] = res[n + i - 1].z;
+}
+}
+
+
+
G_free(res);
return Points-n_points;
Index: vector/v.generalize/operators.h
===
--- vector/v.generalize/operators.h (revision 55852)
+++ vector/v.generalize/operators.h (working copy)
@@ -12,7 +12,7 @@
/* smoothing.c */
int boyle(struct line_pnts *Points, int look_ahead, int with_z);
int sliding_averaging(struct line_pnts *Points, double slide, int look_ahead,
- int with_z);
+ int loop_support, int with_z);
int distance_weighting(struct line_pnts *Points, double
Re: [GRASS-dev] [GRASS GIS] #1929: make r.report CSV/spreadsheet ready
#1929: make r.report CSV/spreadsheet ready ---+ Reporter: timmie | Owner: grass-dev@… Type: enhancement| Status: new Priority: normal | Milestone: 7.0.0 Component: Raster | Version: unspecified Keywords: r.report, r.stats |Platform: All Cpu: Unspecified| ---+ Changes (by hamish): * keywords: = r.report, r.stats * type: defect = enhancement Comment: Hi, Perhaps r.stats has what you want? (r.report is largely a wrapper which prints the computer-friendly results of r.stats in a human-friendly way) Hamish -- Ticket URL: https://trac.osgeo.org/grass/ticket/1929#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] #1930: Quote column names when creating tables via sqlite
#1930: Quote column names when creating tables via sqlite -+-- Reporter: scw | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.0.0 Component: Database | Version: unspecified Keywords: sqlite |Platform: Unspecified Cpu: Unspecified | -+-- Changes (by hamish): * keywords: = sqlite * component: Default = Database -- Ticket URL: https://trac.osgeo.org/grass/ticket/1930#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] #953: module help information in machine-readable format
#953: module help information in machine-readable format +--- Reporter: cmbarton| Owner: glynn Type: enhancement | Status: new Priority: normal | Milestone: 6.5.0 Component: Default | Version: unspecified Keywords: help, metadata |Platform: All Cpu: All | +--- Comment(by cmbarton): Replying to [comment:5 hamish]: can we consider the wish completed? Probably. -- Ticket URL: https://trac.osgeo.org/grass/ticket/953#comment:6 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] #953: module help information in machine-readable format
#953: module help information in machine-readable format --+- Reporter: cmbarton | Owner: glynn Type: enhancement | Status: closed Priority: normal | Milestone: 6.5.0 Component: Default | Version: unspecified Resolution: fixed|Keywords: help, metadata Platform: All | Cpu: All --+- Changes (by cmbarton): * status: new = closed * resolution: = fixed -- Ticket URL: https://trac.osgeo.org/grass/ticket/953#comment:7 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-user] Using r.quantile result with r.recode
Pedro Venâncio wrote: r.recode will treat boundary values as belonging to the upper range, e.g. in the above example, 6.0 will get recoded to 2. So we can not use directly the result of r.quantile with -r flag in r.recode, right? In the example, 6 should be recoded to 1, right? For real data, most of the boundary values won't be actual values from the input data, but values derived from interpolating two adjacent values. In that situation, it doesn't matter how r.recode handles boundary values. -- Glynn Clements gl...@gclements.plus.com ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS] #1933: v.overlay ends with sigsegv in cut lines by polygon
#1933: v.overlay ends with sigsegv in cut lines by polygon
---+
Reporter: mapycz | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker| Milestone: 7.0.0
Component: Vector | Version: unspecified
Keywords: v.overlay |Platform: Unspecified
Cpu: x86-64 |
---+
we tried cut contours by polygon but v.overaly crashed
our training dta consist of contour lines and polygon
these data is in tar.bz2 archive in this location:
http://work.talasek.sk:/download/grass_error.tar.bz2
here is some debug
GRASS 7.0.svn (test1):~/grassgis/grass-svn gdb v.overlay
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/local/grass-7.0.svn/bin/v.overlay...done.
(gdb) run ainput=cnt_sm atype=line binput=cut_poly operator=and
output=cnt_cut1 --overwrite
Starting program: /usr/local/grass-7.0.svn/bin/v.overlay ainput=cnt_sm
atype=line binput=cut_poly operator=and output=cnt_cut1 --overwrite
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
WARNING: Vector map cnt_cut1 already exists and will be overwritten
WARNING: Table cnt_cut1 linked to vector map cnt_cut1 does not exist
Copying vector features from cnt_sm@miro...
100%
Copying vector features from cut_poly@miro...
100%
Breaking lines...
0%
Program received signal SIGSEGV, Segmentation fault.
0x77b7e55b in break_lines (Map=0x7fffc040, List_break=0x0,
List_ref=0x61f8d0, type=6, Err=0x0, check=0) at break_lines.c:360
360 !touch1_w nodex == BBox-E) ||
(gdb) info local
APoints = 0x1276530
BPoints = 0x1276560
Points = 0x1276590
AXLines = 0x7753328c
BXLines = 0x7fffa9b0
ACats = 0x12765c0
BCats = 0x12765e0
Cats = 0x1276600
i = 0
j = -1
k = 32767
l = -20688
ret = -138628762
atype = 4
btype = 4
aline = 17849
bline = 17849
found = 0
iline = 0
nlines = 13
nlines_org = 17861
naxlines = 32767
nbxlines = -7760
nx = 32767
xx = 0x0
yx = 0x0
zx = 0x0
ABox = {N = 5557464.4957634434, S = 5506178.6524737561, E =
790483.12121040502, W = 725733.38919512555, T = 0, B = 0}
BBox = 0x7fffe7415fe0
List = 0x1276620
nbreaks = 0
touch1_n = 1
touch1_s = 1
touch1_e = 1
touch1_w = 0
touch2_n = 1
touch2_s = 1
touch2_e = 1
touch2_w = 1
is3d = 0
node = 17862
anode1 = 17862
anode2 = 17863
bnode1 = 17862
bnode2 = 17863
nodex = 725733.38919512555
nodey = 5556926.5740271173
a_is_ref = 1
b_is_ref = 1
break_a = 1
break_b = 0
(gdb)
--
Ticket URL: http://trac.osgeo.org/grass/ticket/1933
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] #640: setup.py may use different Python than configured for GRASS
#640: setup.py may use different Python than configured for GRASS -+-- Reporter: kyngchaos| Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 6.5.0 Component: Compiling| Version: 6.4.0 RCs Keywords: python |Platform: Unspecified Cpu: Unspecified | -+-- Comment(by kyngchaos): Ah, right. Looks like in python.make it's just a compile command. Not an issue for the OS X 32bit vs. 64bit problem, but important to compile for the right version of python. I also found $(PYTHON) in the wx gui makefile. There it's just running python scripts to generate some files, doesn't look to me like the python version is important. Configuring a PYTHON could also be useful if some wx stuff is run at compile time, to get around the 32bit OS X problem with old wxpython versions, and on OS X wxpython python scripts need to run in pythonw... hmm, there might already be some of those - wx-based modules that are run to generate the help files. -- Ticket URL: https://trac.osgeo.org/grass/ticket/640#comment:7 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] #1933: v.overlay ends with sigsegv in cut lines by polygon
#1933: v.overlay ends with sigsegv in cut lines by polygon --+- Reporter: mapycz | Owner: grass-dev@… Type: defect | Status: closed Priority: blocker | Milestone: 7.0.0 Component: Vector | Version: unspecified Resolution: invalid |Keywords: v.overlay Platform: Unspecified | Cpu: x86-64 --+- Changes (by mapycz): * status: new = closed * resolution: = invalid -- Ticket URL: http://trac.osgeo.org/grass/ticket/1933#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] #1934: v.overlay ends with sigsegv in cut lines by polygon
#1934: v.overlay ends with sigsegv in cut lines by polygon
-+--
Reporter: mapycz | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 7.0.0
Component: Vector | Version: svn-trunk
Keywords: |Platform: Linux
Cpu: x86-64 |
-+--
we tried cut contours by polygon but v.overaly crashed
our training dta consist of contour lines and polygon
these data is in tar.bz2 archive in this location:
http://work.talasek.sk:/download/grass_error.tar.bz2
here is some debug
{{{
GRASS 7.0.svn (test1):~/grassgis/grass-svn gdb v.overlay
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/local/grass-7.0.svn/bin/v.overlay...done.
(gdb) run ainput=cnt_sm atype=line binput=cut_poly operator=and
output=cnt_cut1 --overwrite
Starting program: /usr/local/grass-7.0.svn/bin/v.overlay ainput=cnt_sm
atype=line binput=cut_poly operator=and output=cnt_cut1 --overwrite
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
WARNING: Vector map cnt_cut1 already exists and will be overwritten
WARNING: Table cnt_cut1 linked to vector map cnt_cut1 does not exist
Copying vector features from cnt_sm@miro...
100%
Copying vector features from cut_poly@miro...
100%
Breaking lines...
0%
Program received signal SIGSEGV, Segmentation fault.
0x77b7e55b in break_lines (Map=0x7fffc040, List_break=0x0,
List_ref=0x61f8d0, type=6, Err=0x0, check=0) at break_lines.c:360
360 !touch1_w nodex == BBox-E) ||
(gdb) info local
APoints = 0x1276530
BPoints = 0x1276560
Points = 0x1276590
AXLines = 0x7753328c
BXLines = 0x7fffa9b0
ACats = 0x12765c0
BCats = 0x12765e0
Cats = 0x1276600
i = 0
j = -1
k = 32767
l = -20688
ret = -138628762
atype = 4
btype = 4
aline = 17849
bline = 17849
found = 0
iline = 0
nlines = 13
nlines_org = 17861
naxlines = 32767
nbxlines = -7760
nx = 32767
xx = 0x0
yx = 0x0
zx = 0x0
ABox = {N = 5557464.4957634434, S = 5506178.6524737561, E =
790483.12121040502, W = 725733.38919512555, T = 0, B = 0}
BBox = 0x7fffe7415fe0
List = 0x1276620
nbreaks = 0
touch1_n = 1
touch1_s = 1
touch1_e = 1
touch1_w = 0
touch2_n = 1
touch2_s = 1
touch2_e = 1
touch2_w = 1
is3d = 0
node = 17862
anode1 = 17862
anode2 = 17863
bnode1 = 17862
bnode2 = 17863
nodex = 725733.38919512555
nodey = 5556926.5740271173
a_is_ref = 1
b_is_ref = 1
break_a = 1
break_b = 0
(gdb) }}}
--
Ticket URL: http://trac.osgeo.org/grass/ticket/1934
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] #1934: v.overlay ends with sigsegv in cut lines by polygon
#1934: v.overlay ends with sigsegv in cut lines by polygon ---+ Reporter: mapycz | Owner: grass-dev@… Type: defect | Status: new Priority: blocker| Milestone: 7.0.0 Component: Vector | Version: svn-trunk Keywords: v.overlay |Platform: Linux Cpu: x86-64 | ---+ Changes (by martinl): * keywords: = v.overlay -- Ticket URL: http://trac.osgeo.org/grass/ticket/1934#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] #1933: v.overlay ends with sigsegv in cut lines by polygon
#1933: v.overlay ends with sigsegv in cut lines by polygon --+- Reporter: mapycz | Owner: grass-dev@… Type: defect | Status: reopened Priority: blocker | Milestone: 7.0.0 Component: Vector | Version: unspecified Resolution: |Keywords: v.overlay Platform: Unspecified | Cpu: x86-64 --+- Changes (by mapycz): * status: closed = reopened * resolution: invalid = Comment: hmm big fixed but can u see for result ? some lines disappear and result is nod good, computataion is abnormally fast i feel it is something similar #55854 -- Ticket URL: http://trac.osgeo.org/grass/ticket/1933#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] #1933: v.overlay ends with sigsegv in cut lines by polygon
#1933: v.overlay ends with sigsegv in cut lines by polygon --+- Reporter: mapycz | Owner: grass-dev@… Type: defect | Status: reopened Priority: blocker | Milestone: 7.0.0 Component: Vector | Version: unspecified Resolution: |Keywords: v.overlay Platform: Unspecified | Cpu: x86-64 --+- Comment(by mapycz): sry similar ticket is #1875 -- Ticket URL: http://trac.osgeo.org/grass/ticket/1933#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] #1934: v.overlay ends with sigsegv in cut lines by polygon
#1934: v.overlay ends with sigsegv in cut lines by polygon +--- Reporter: mapycz | Owner: grass-dev@… Type: defect | Status: closed Priority: blocker| Milestone: 7.0.0 Component: Vector | Version: svn-trunk Resolution: duplicate |Keywords: v.overlay Platform: Linux | Cpu: x86-64 +--- Changes (by mapycz): * status: new = closed * resolution: = duplicate -- Ticket URL: http://trac.osgeo.org/grass/ticket/1934#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] #1933: v.overlay ends with sigsegv in cut lines by polygon
#1933: v.overlay ends with sigsegv in cut lines by polygon --+- Reporter: mapycz | Owner: grass-dev@… Type: defect | Status: reopened Priority: blocker | Milestone: 7.0.0 Component: Vector | Version: svn-trunk Resolution: |Keywords: v.overlay Platform: Linux| Cpu: x86-64 --+- Changes (by mapycz): * platform: Unspecified = Linux * version: unspecified = svn-trunk -- Ticket URL: http://trac.osgeo.org/grass/ticket/1933#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] #1318: DebCheck QA: Memory leaks
#1318: DebCheck QA: Memory leaks +--- Reporter: hamish | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 6.4.3 Component: Compiling | Version: 6.4.0 Keywords: gem, lib/bitmap, shapelib, lib/iostream, dglib, r.li, nviz | Platform: Linux Cpu: Unspecified | +--- Comment(by neteler): Replying to [comment:1 hamish]: lib/external/shapelib/shpopen.c fixed in trunk and devbr6 with r55838,9. Please also let this get fixed upstream (or open a ticket): http://svn.osgeo.org/gdal/trunk/gdal/ogr/ogrsf_frmts/shape/shpopen.c Note that we use a potentially outdated copy of this and related files. -- Ticket URL: http://trac.osgeo.org/grass/ticket/1318#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] #1827: Measure Distance - Bearing
#1827: Measure Distance - Bearing ---+ Reporter: voncasec | Owner: grass-dev@… Type: defect| Status: closed Priority: normal| Milestone: 6.4.3 Component: wxGUI | Version: svn-releasebranch64 Resolution: fixed |Keywords: Bearing tool, MapFrame.MeasureDist() Platform: Linux | Cpu: x86-64 ---+ Comment(by voncasec): Thanks for applying this fix to the wxGUI Display Hamish. I love being able to click a couple points on the map without having to think about the angle heading. Casey -- Ticket URL: http://trac.osgeo.org/grass/ticket/1827#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] #1933: v.overlay ends with sigsegv in cut lines by polygon
#1933: v.overlay ends with sigsegv in cut lines by polygon --+- Reporter: mapycz | Owner: grass-dev@… Type: defect | Status: reopened Priority: blocker | Milestone: 7.0.0 Component: Vector | Version: svn-trunk Resolution: |Keywords: v.overlay Platform: Linux| Cpu: x86-64 --+- Comment(by mmetz): Replying to [comment:2 mapycz]: hmm big fixed but can u see for result ? some lines disappear and result is nod good I checked with r55797, no disappearing lines, result seems good. Can you provide a screenshot and coordinates where lines disappear? -- Ticket URL: http://trac.osgeo.org/grass/ticket/1933#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
[GRASS-dev] [GRASS GIS] #1935: v.out.ogr removed export directory when dsn= is incorrectly specified.
#1935: v.out.ogr removed export directory when dsn= is incorrectly specified.
-+--
Reporter: cgsbob | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Vector | Version: svn-trunk
Keywords: |Platform: Linux
Cpu: Unspecified |
-+--
I can't believe I specified a dsn without escaping the space character.
So, when I saw the error below, I figured that the dsn caused this
problem. So, I tested my theory by setting the dsn to /tmp/hydro.shp
without any errors. When I went to see if any files were written in
/media/STORE N GO/Sac, I discovered that this directory was gone!
{{{
(Wed Apr 17 11:36:43 2013)
v.out.ogr -c -e --verbose input=sac_course@Data dsn=/media/STORE N
GO/Sac/hydro.shp format=ESRI_Shapefile
Exporting 118696 features...
ERROR 1: Error in psSHP-sHooks.Fwrite() while writing
object to .shp file.
ERROR 1: Error in psSHP-sHooks.Fwrite() while writing
object to .shp file.
ERROR 1: Error in psSHP-sHooks.Fwrite() while writing
object to .shp file.
ERROR 1: Error in psSHP-sHooks.Fwrite() while writing
object to .shp file.
ERROR 1: Error in psSHP-sHooks.Fwrite() while writing
object to .shp file.
ERROR 1: Error in psSHP-sHooks.Fwrite() while writing
object to .shp file.
ERROR 1: Error in psSHP-sHooks.Fwrite() while writing
object to .shp file.
ERROR 1: Error in psSHP-sHooks.Fwrite() while writing
object to .shp file.
ERROR 1: Error in psSHP-sHooks.Fwrite() while writing
object to .shp file.
ERROR 1: Error in psSHP-sHooks.Fwrite() while writing
object to .shp file.
ERROR 1: Error in psSHP-sHooks.Fwrite() while writing
object to .shp file.
ERROR 1: Error in psSHP-sHooks.Fwrite() while writing
object to .shp file.
ERROR 1: Error in psSHP-sHooks.Fwrite() while writing
object to .shp file.
ERROR 1: Failure writing DBF record 1555.
ERROR 1: Error in psSHP-sHooks.Fwrite() while writing
object to .shp file.
}}}
'''I hit CTRL-C'''
{{{
Please note that the data are left in inconsistent state and may be
corrupted
(Wed Apr 17 11:37:41 2013) Command aborted (57 sec)
}}}
Export vector to /tmp works fine
{{{
(Wed Apr 17 11:38:05 2013)
v.out.ogr -c -e --verbose input=sac_course@Data dsn=/tmp/hydro.shp
format=ESRI_Shapefile
Exporting 118696 features...
v.out.ogr complete. 118696 features written to sac_course
(ESRI_Shapefile).
(Wed Apr 17 11:39:05 2013) Command finished (59 sec)
}}}
--
Ticket URL: http://trac.osgeo.org/grass/ticket/1935
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] #1932: r.univar segfault on map with massive values
#1932: r.univar segfault on map with massive values --+- Reporter: hamish| Owner: grass-dev@… Type: defect| Status: new Priority: normal| Milestone: 6.4.3 Component: Raster| Version: svn-develbranch6 Keywords: r.univar |Platform: Linux Cpu: x86-64| --+- Changes (by jradinger): * cc: jradinger (added) -- Ticket URL: http://trac.osgeo.org/grass/ticket/1932#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] #1428: WinGRASS + how to deliver Microsoft Visual C++ Redistributable Package (vcredist)?
#1428: WinGRASS + how to deliver Microsoft Visual C++ Redistributable Package (vcredist)? --+- Reporter: dhastings | Owner: grass-dev@… Type: defect| Status: new Priority: blocker | Milestone: 6.4.3 Component: Installation | Version: 6.4.3 RCs Keywords: wingrass |Platform: MSWindows 7 Cpu: x86-64| --+- Comment(by neteler): Tested ok on Win8. Please backport to relbranch64. Question: Is there a potential race condition during installation of DLL package while the winGRASS package already offers the Next button? Could winGRASS wait for the DLL redistribuition package installation to complete? -- Ticket URL: http://trac.osgeo.org/grass/ticket/1428#comment:61 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
