Re: [GRASS-dev] Fwd: FOSDEM 2015

2014-11-18 Thread Margherita Di Leo
Hi,

On Mon, Nov 17, 2014 at 3:45 PM, Moritz Lennert 
mlenn...@club.worldonline.be wrote:

 Hello,

 As you can see below, Margherita contacted me concerning a GRASS
 presentation at the geospatial devromm foreseen for the first time at the
 upcoming FOSDEM.

 I can present something, but would like to know

 1) if other devs are planning to attend and if yes, if they were planning
 to present anything
 2) which themes you think would be the most interesting to present from a
 GRASS perspective

 Currently, I've been thinking about two themes:

 - The obvious what's new in GRASS 7, but I'm not sure that this is the
 most appropriate for the mostly developper crowd present at a FOSDEM.

 - A focus on the different APIs in GRASS from C to pygrass to
 grass.script, explaining structure and use cases of each.

 Any other ideas ?

 Moritz



Thank you Moritz for bringing the discussion in ML. Just to put it in
context, see at:
http://geofemengineering.blogspot.it/2014/10/call-for-papers-geospatial-devroom.html

Hope to see many of you there!!

cheers,
madi


-- 
Best regards,

Dr. Margherita DI LEO
Scientific / technical project officer

European Commission - DG JRC
Institute for Environment and Sustainability (IES)
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261

Tel. +39 0332 78 3600
margherita.di-...@jrc.ec.europa.eu

Disclaimer: The views expressed are purely those of the writer and may not
in any circumstance be regarded as stating an official position of the
European Commission.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #2492: v.generalize: incorrect handling of wrap at 180 meridian

2014-11-18 Thread GRASS GIS
#2492: v.generalize: incorrect handling of wrap at 180 meridian
--+-
 Reporter:  jkaplan   |   Owner:  grass-dev@…  
 Type:  defect|  Status:  new  
 Priority:  normal|   Milestone:   
Component:  Vector| Version:  svn-trunk
 Keywords:  v.generalize  |Platform:  All  
  Cpu:  OSX/Intel |  
--+-
 I am running GRASS 7.1.svn on Mac OS X.

 {{{
 GRASS 7.1.svn (global_lonlat):~  g.version -g
 version=7.1.svn
 date=2014
 revision=62762
 build_date=2014-11-17
 build_platform=x86_64-apple-darwin10.8.0
 }}}

 I am having a problem with the behavior of v.generalize when attempting to
 generalize a vector feature - lines or polygons it does not seem to matter
 - that crosses the 180 meridian, using a location that is EPSG:4326 with
 global extents.

 The problem is probably best illustrated with a picture, which I have
 attached to this ticket, but can also be viewed here:

 http://arve.unil.ch/pub/GRASS_wrap_problem.png

 In the picture two line vector features are displayed. The black-lined
 feature is the original vector line feature (test1). The red-lined feature
 is produced from test1 using the following command:

 {{{
 v.generalize input=test1 output=test2 method=sliding_averaging
 look_ahead=5 slide=1 threshold=1
 }}}

 It appears that v.generalize, when smoothing between vertices that are
 very close to the 180 meridian, results in the incorrect identification of
 the “next point, hence the long horizontal lines connecting points “the
 wrong way around” the earth. The behavior is the same when using any of
 the generalization or smoothing tools.

 I have tested this with a simpler vector containing points farther away
 from the 180 meridian and it doesn’t appear to show the same behavior.

 I would very much appreciate any help anyone could give me to solve this
 problem.

 Thank you in advance!

 Best regards,

 Jed Kaplan

 --

 If you would like to download the original lines file and try my procedure
 yourself, I have also attached a test vector file to this ticket. It can
 also be downloaded here:

 http://arve.unil.ch/pub/GRASS_wrap_problem_samplevector.gmt

 Assuming you have OGR support for GMT in your version of GRASS, you can
 import the vector using this command:

 {{{
 v.in.ogr dsn=GRASS_wrap_problem_samplevector.gmt output=test1
 }}}

-- 
Ticket URL: http://trac.osgeo.org/grass/ticket/2492
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] winGRASS 71 binaries missing

2014-11-18 Thread Anna Petrášová
Martin,

I realized the last grass 71 binary is from November 13, but the last log
doesn't show any error?

Anna
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Tests down to 65% (from 86%)

2014-11-18 Thread Vaclav Petras
Thanks, tests are back to 86%.

http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2014-11-18-08-00/report_for_nc_spm_08_grass7_nc/testsuites.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #2493: wxgui file import wizards: all files should be defined as '*', not '*.*'

2014-11-18 Thread GRASS GIS
#2493: wxgui file import wizards: all files should be defined as '*', not '*.*'
+---
 Reporter:  mlennert|   Owner:  grass-dev@…  
 Type:  defect  |  Status:  new  
 Priority:  normal  |   Milestone:  7.0.0
Component:  wxGUI   | Version:  unspecified  
 Keywords:  wxgui file import glob  |Platform:  Unspecified  
  Cpu:  Unspecified |  
+---
 The wxgui file import wizards define all files as '*.*' which means that
 if you have total legal tif files which do not have the .tif extension you
 cannot see them in the file selector.

 In r.in.gdal this was replaced by '*' a long time ago, but in the import
 wizards it is still a nuisance.

 Classifying this as a bug since for some users this means they don't know
 how to import these files.

-- 
Ticket URL: https://trac.osgeo.org/grass/ticket/2493
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] How to calculate log() in v.db.update with SQLite backend?

2014-11-18 Thread Markus Neteler
Hi,

playing around with the Meuse dataset about soil contamination I
attempted to calculate that right away but...:

v.db.update meuse_voronoi column=logzinc qcolumn=log(zinc)
DBMI-SQLite driver error:
Error in sqlite3_prepare():
no such function: log

DBMI-SQLite driver error:
Error in sqlite3_prepare():
no such function: log

ERROR: Error while executing: 'UPDATE meuse_voronoi SET logzinc=log(zinc)'

After some online research I found that I would need to tune my local
SQLite installation with

https://sqlite.org/contrib/download/extension-functions.c
extension-functions.c (50.96 KB) contributed by Liam Healy on
2010-02-06 15:45:07
Provide mathematical and string extension functions for SQL queries
using the loadable extensions mechanism. Math: acos, asin, atan, atn2,
atan2, acosh, asinh, atanh, difference, degrees, radians, cos, sin,
tan, cot, cosh, sinh, tanh, coth, exp, log, log10, power, sign, sqrt,
square, ceil, floor, pi. String: replicate, charindex, leftstr,
rightstr, ltrim, rtrim, trim, replace, reverse, proper, padl, padr,
padc, strfilter. Aggregate: stdev, variance, mode, median,
lower_quartile, upper_quartile.


Alternative: use pysqlite and define an own function.

Which way to go?

thanks
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev


Re: [GRASS-dev] [GRASS GIS] #2491: configure: error: *** Unable to locate FreeType includes.

2014-11-18 Thread GRASS GIS
#2491: configure: error: *** Unable to locate FreeType includes.
-+--
 Reporter:  strk |   Owner:  grass-dev@…  
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  7.0.0
Component:  Compiling| Version:  unspecified  
 Keywords:   |Platform:  Unspecified  
  Cpu:  Unspecified  |  
-+--

Comment(by glynn):

 Replying to [comment:2 strk]:
  $ freetype-config --cflags
  -I/usr/include/freetype2
 
  Is that acceptable by policy then ?

 Yes. But the configure script doesn't currently use freetype-config.

 Before making that change, we should decide whether to use freetype-config
 or pkg-config.

 Also, we don't currently have a macro for *-config scripts; each package
 which uses them has the same boilerplate.

-- 
Ticket URL: https://trac.osgeo.org/grass/ticket/2491#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] #2495: Java runtime error

2014-11-18 Thread GRASS GIS
#2495: Java runtime error
---+
  Reporter:  ragola|   Owner:  grass-dev@…   
  Type:  defect|  Status:  closed
  Priority:  normal|   Milestone:  6.4.5 
 Component:  Installation  | Version:  unspecified   
Resolution:  invalid   |Keywords:  java, runtime, gui startup
  Platform:  MacOSX| Cpu:  OSX/Intel 
---+
Changes (by kyngchaos):

  * status:  new = closed
  * resolution:  = invalid


Comment:

 This is not a GRASS bug.  This comes from the GDAL framework 1.11.0, where
 Java ''6'', not Java 8, is required for the MDB driver.  I have removed
 the MDB driver in GDAL 1.11.1, and will eventually make it an optional
 GDAL plugin.

 Update GDAL.

-- 
Ticket URL: https://trac.osgeo.org/grass/ticket/2495#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