Re: [GRASS-dev] How to calculate mean coordinates from big point datasets?
Glynn Clements wrote: Markus Metz wrote: Please try the new addon v.centerpoint [0]. It calculates various center points for point clouds, lines, and areas. Standard options are the geometric mean (center of gravity) That's the arithmetic mean. The geometric mean of a set of N values is the Nth root of the product of the values (i.e. the logarithm of the geometric mean is the arithmetic mean of the logarithms of the values). It wouldn't be meaningful to compute the geometric mean of coordinate data. Right, I fixed the documentation. Internally, the arithmetic mean has been used already to calculate centers of gravity. Markus M ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] compile error with v.in.ply
I am trying to compile GRASS GIS 7.0 (revision 57836) and I am getting an error when running make related to v.in.ply and v.out.ply. When running make in the vector folder, I am getting the following error message: make: *** v.in.ply: No such file or directory. Stop. make: *** v.out.ply: No such file or directory. Stop. I don't know if it is in any way related, but I did first update gdal from 1.9 to 1.10.1. And I just tried, and it seems in my previous install, r57757, there is no v.in.ply or v.out.ply? Best Paulo ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] compile error with v.in.ply
Paulo van Breugel wrote: I am trying to compile GRASS GIS 7.0 (revision 57836) and I am getting an error when running make related to v.in.ply and v.out.ply. When running make in the vector folder, I am getting the following error message: make: *** v.in.ply: No such file or directory. Stop. make: *** v.out.ply: No such file or directory. Stop. Oops, fixed in r57837. Markus M ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] compile error with v.in.ply
Woh.. that is quick, thanks! On Wed, Sep 25, 2013 at 12:28 PM, Markus Metz markus.metz.gisw...@gmail.com wrote: Paulo van Breugel wrote: I am trying to compile GRASS GIS 7.0 (revision 57836) and I am getting an error when running make related to v.in.ply and v.out.ply. When running make in the vector folder, I am getting the following error message: make: *** v.in.ply: No such file or directory. Stop. make: *** v.out.ply: No such file or directory. Stop. Oops, fixed in r57837. Markus M ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #957: v.voronoi has extra lines in output
#957: v.voronoi has extra lines in output ---+ Reporter: helena | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 6.4.4 Component: Vector | Version: svn-releasebranch64 Keywords: v.voronoi |Platform: All Cpu: All| ---+ Comment(by mmetz): Replying to [comment:28 mlennert]: In 64release, I'm still getting a subset of the holes reported by Helena in a raster resulting from v.voronoi polygons [...] although the vector polygons all look ok. That is a bug in v.to.rast, more specifically in G_plot_polygon() in lib/gis/plot.c. -- Ticket URL: https://trac.osgeo.org/grass/ticket/957#comment:30 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] #957: v.voronoi has extra lines in output
#957: v.voronoi has extra lines in output ---+ Reporter: helena | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 6.4.4 Component: Vector | Version: svn-releasebranch64 Keywords: v.voronoi |Platform: All Cpu: All| ---+ Comment(by mmetz): Replying to [comment:30 mmetz]: Replying to [comment:28 mlennert]: In 64release, I'm still getting a subset of the holes reported by Helena in a raster resulting from v.voronoi polygons [...] although the vector polygons all look ok. That is a bug in v.to.rast, more specifically in G_plot_polygon() in lib/gis/plot.c. Please try trunk r57839. -- Ticket URL: https://trac.osgeo.org/grass/ticket/957#comment:31 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] #957: v.voronoi has extra lines in output
#957: v.voronoi has extra lines in output ---+ Reporter: helena | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 6.4.4 Component: Vector | Version: svn-releasebranch64 Keywords: v.voronoi |Platform: All Cpu: All| ---+ Comment(by mlennert): Replying to [comment:31 mmetz]: Replying to [comment:30 mmetz]: Replying to [comment:28 mlennert]: In 64release, I'm still getting a subset of the holes reported by Helena in a raster resulting from v.voronoi polygons [...] although the vector polygons all look ok. That is a bug in v.to.rast, more specifically in G_plot_polygon() in lib/gis/plot.c. Please try trunk r57839. Solves it for me, thanks ! As this wasn't even a v.voronoi bug, I think this bug report can probably be closed, unless you want to keep it open as a reminder to erase the empty functions. Is there an agreement on erasing them ? If yes, I'm willing to do it. Moritz -- Ticket URL: https://trac.osgeo.org/grass/ticket/957#comment:32 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] #957: v.voronoi has extra lines in output
#957: v.voronoi has extra lines in output ---+ Reporter: helena | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 6.4.4 Component: Vector | Version: svn-releasebranch64 Keywords: v.voronoi |Platform: All Cpu: All| ---+ Comment(by mlennert): Replying to [comment:32 mlennert]: Replying to [comment:31 mmetz]: Replying to [comment:30 mmetz]: Replying to [comment:28 mlennert]: In 64release, I'm still getting a subset of the holes reported by Helena in a raster resulting from v.voronoi polygons [...] although the vector polygons all look ok. That is a bug in v.to.rast, more specifically in G_plot_polygon() in lib/gis/plot.c. Please try trunk r57839. Solves it for me, thanks ! Backport to release6 ? Moritz -- Ticket URL: https://trac.osgeo.org/grass/ticket/957#comment:33 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.in.ogr: how to force sqlite instead of dbf for output location ? SEG-Y input (Geology/Seismic Data)
Hi list, I'm using GRASS6.4.2 on a Suse-based HPC Cluster. When trying to ingest SEG-Y data (geology/seismics) into a new location via v.in.ogr (GDAL 1.9.0) this error is thrown since the new location is set by default (?) to dbf: GRASS 6.4.2 (startup_sqlite):~/geodata/petrel/SEG_Y_Demo v.in.ogr dsn=demo20071121142735_CH1_35P.seg output=seg_y_test location=segy_sqlite Layer: demo20071121142735_CH1_35P WARNING: Default driver / database set to: driver: dbf database: $GISDBASE/$LOCATION_NAME/$MAPSET/dbf/ WARNING: Column type not supported (SAMPLE_ARRAY) WARNING: DBMI-DBF driver: column name 'TRACE_NUMBER_WITHIN_LINE' truncated to 'TRACE_NUMB' WARNING: DBMI-DBF driver: column name 'TRACE_NUMBER_WITHIN_FILE' truncated to 'TRACE_NUMB' DBMI-DBF driver error: Column 'TRACE_NUMB' already exists (duplicate name) Cannot create table. Error in db_execute_immediate() ERROR: Unable to create table: 'create table seg_y_test_1 (cat integer, TRACE_NUMBER_WITHIN_LINE integer, TRACE_NUMBER_WITHIN_FILE integer, ORIGINAL_FIELD_RECORD_NUMBER integer, TRACE_NUMBER_WITHIN_ORIGINAL_FIELD_RECORD integer, TRACE_IDENTIFICATION_CODE integer, ENSEMBLE_NUMBER integer, TRACE_NUMBER_WITHIN_ENSEMBLE integer, NUMBER_VERTICAL_SUMMED_TRACES integer, NUMBER_HORIZONTAL_STACKED_TRACES integer, DATA_USE integer, DISTANCE_SOURCE_GROUP integer, RECEIVER_GROUP_ELEVATION integer, SURFACE_ELEVATION_AT_SOURCE integer, SOURCE_DEPTH_BELOW_SURFACE integer, DATUM_ELEVATION_AT_RECEIVER_GROUP integer, DATUM_ELEVATION_AT_SOURCE integer, WATER_DEPTH_AT_SOURCE integer, WATER_DEPTH_AT_GROUP integer, VERTICAL_SCALAR integer, HORIZONTAL_SCALAR integer, SOURCE_X integer, SOURCE_Y integer, GROUP_X integer, GROUP_Y integer, COORDINATE_UNITS integer, WEATHERING_VELOCITY integer, SUB_WEATHERING_VELOCITY integer, UPHOLE_TIME_AT_SOURCE integer, UPHOLE_TIME_AT_GROUP integer, SOURCE_STATIC_CORRECTION integer, GROUP_STATIC_CORRECTION integer, TOTAL_STATIC_CORRECTION integer, LAG_TIME_A integer, LAG_TIME_B integer, DELAY_RECORDING_TIME integer, MUTE_TIME_START integer, MUTE_TIME_END integer, SAMPLES integer, SAMPLE_INTERVAL integer, GAIN_TYPE integer, INSTRUMENT_GAIN_CONSTANT integer, INSTRUMENT_INITIAL_GAIN integer, CORRELATED integer, SWEEP_FREQUENCY_AT_START integer, SWEEP_FREQUENCY_AT_END integer, SWEEP_LENGTH integer, SWEEP_TYPE integer, SWEEP_TRACE_TAPER_LENGTH_AT_START integer, SWEEP_TRACE_TAPER_LENGTH_AT_END integer, TAPER_TYPE integer, ALIAS_FILTER_FREQUENCY integer, ALIAS_FILTER_SLOPE integer, NOTCH_FILTER_FREQUENCY integer, NOTCH_FILTER_SLOPE integer, LOW_CUT_FREQUENCY integer, HIGH_CUT_FREQUENCY integer, LOW_CUT_SLOPE integer, HIGH_CUT_SLOPE integer, YEAR integer, DAY_OF_YEAR integer, HOUR integer, MINUTE integer, SECOND integer, TIME_BASIC_CODE integer, TRACE_WEIGHTING_FACTOR integer, GEOPHONE_GROUP_NUMBER_OF_ROLL_SWITH integer, GEOPHONE_GROUP_NUMBER_OF_TRACE_NUMBER_ONE integer, GEOPHONE_GROUP_NUMBER_OF_LAST_TRACE integer, GAP_SIZE integer, OVER_TRAVEL integer)' The initial location from which v.in.ogr was invoked was already switched to a sqlite-backend. How can this issue be overcome ? - I'm no SEG Y guru, so having v.in.ogr infer the settings for the resulting target location would be required. Cheers, Peter peter.lo...@gmx.de ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2084: Combine r.water.outlet easting=, northing= into coordinates= (G_OPT_M_COORDS) for mouse interactivity in g.gui.
#2084: Combine r.water.outlet easting=, northing= into coordinates= (G_OPT_M_COORDS) for mouse interactivity in g.gui. -+-- Reporter: hcho | Owner: hcho Type: enhancement | Status: new Priority: major| Milestone: 7.0.0 Component: Raster | Version: svn-trunk Keywords: |Platform: All Cpu: All | -+-- Changes (by hcho): * owner: martinl = hcho * status: assigned = new -- Ticket URL: http://trac.osgeo.org/grass/ticket/2084#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] #2084: Combine r.water.outlet easting=, northing= into coordinates= (G_OPT_M_COORDS) for mouse interactivity in g.gui.
#2084: Combine r.water.outlet easting=, northing= into coordinates= (G_OPT_M_COORDS) for mouse interactivity in g.gui. --+- Reporter: hcho | Owner: hcho Type: enhancement | Status: closed Priority: major| Milestone: 7.0.0 Component: Raster | Version: svn-trunk Resolution: fixed|Keywords: Platform: All | Cpu: All --+- Changes (by hcho): * status: new = closed * resolution: = fixed -- Ticket URL: http://trac.osgeo.org/grass/ticket/2084#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] #2084: Combine r.water.outlet easting=, northing= into coordinates= (G_OPT_M_COORDS) for mouse interactivity in g.gui.
#2084: Combine r.water.outlet easting=, northing= into coordinates= (G_OPT_M_COORDS) for mouse interactivity in g.gui. --+- Reporter: hcho | Owner: hcho Type: enhancement | Status: closed Priority: major| Milestone: 7.0.0 Component: Raster | Version: svn-trunk Resolution: fixed|Keywords: Platform: All | Cpu: All --+- Comment(by hcho): Try r57841. -- Ticket URL: http://trac.osgeo.org/grass/ticket/2084#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
