Re: [GRASS-dev] openMP support in GRASS GIS

Hi, yes I already changed the r.sim.sediment, so it is running there, I just wanted to check there is no theoretical issue since you haven't mentioned it in the paper. I kept the max number of walkers lower as it was, the problem if I remember correctly is that is uses static allocations, so if

Re: [GRASS-dev] openMP support in GRASS GIS

Hi Anna, many thanks! Please keep it in addons for a while, as it is referenced in the paper. Yes it is possible to use it in r.sim.sediment as well because actually we have parallelized the simulation library (simlib) used by r.sim.sediment as well. But it needs some modification of

Re: [GRASS-dev] openMP support in GRASS GIS

Dear Jaro and all, During recent code sprint in Boston I ported r.sim.water.mp to GRASS r.sim.water and r.sim.sediment. I tested it with r.sim.sediment and it seems to work, so let me know if there are any reasons parallelization shouldn't be used with r.sim.sediment. I removed all the commented

[GRASS-dev] python script utils encoding/decoding overriding unicode with python-future

Pietro, In r71394 [1] you changed the unicode handling in decode()/encode() in the python script library. However, this broke things on one of my machines [2] because I didn't have the python-future deb package installed, which is normally not supposed to be a compulsory dependency AFAIK.

Re: [GRASS-dev] [GRASS GIS] #3405: encoding issue when launching modules

#3405: encoding issue when launching modules --+--- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.4.0 Component: wxGUI|Version:

Re: [GRASS-dev] [GRASS GIS] #3405: encoding issue when launching modules

#3405: encoding issue when launching modules --+--- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.4.0 Component: wxGUI|Version:

[GRASS-dev] A big thank you to our two GSoC students !

A big thank you to our two GSoC students, Zechariah (GRASS GIS Locations from Public Data) and Ondrej (SOS tools in GRASS GIS), who have sent in their final report [1], [2] ! Great job, guys !!! I am looking forward to seeing your modules (v.in.sos, r.in.sos, t.vect.in.sos, t.rast.in.sos,

Re: [GRASS-dev] [GRASS GIS] #3405: encoding issue when launching modules

#3405: encoding issue when launching modules --+--- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.4.0 Component: wxGUI|Version:

Re: [GRASS-dev] [GRASS GIS] #3409: d.what.vect JSON issue with OSM data

#3409: d.what.vect JSON issue with OSM data --+- Reporter: neteler | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.2.2 Component: Display |Version: svn-releasebranch72

Re: [GRASS-dev] v.in.osm working?

On jeudi 24 août 2017 15:34:11 CEST Markus Metz wrote: > On Thu, Aug 24, 2017 at 11:15 AM, Even Rouault > > wrote: > > > You can use v.in.ogr directly for OSM PBF files ( > > > > > > http://gdal.org/drv_osm.html). > > > > > > > > > > > > BTW, with GDAL 2.2.1,

Re: [GRASS-dev] v.in.osm working?

On Thu, Aug 24, 2017 at 11:15 AM, Even Rouault wrote: > > > > > You can use v.in.ogr directly for OSM PBF files ( > > > http://gdal.org/drv_osm.html). > > > > > > BTW, with GDAL 2.2.1, using OGR_INTERLEAVED_READING=YES does not work for > > > me (empty vector). > > > >

Re: [GRASS-dev] v.in.osm working?

On Thu, Aug 24, 2017 at 10:40 AM, Markus Neteler wrote: > > On Thu, Aug 24, 2017 at 9:30 AM, Markus Metz > wrote: > > On Tue, Aug 22, 2017 at 8:37 PM, Markus Neteler wrote: > >> Hi, > >> > >> does v.in.osm actually work? I am

Re: [GRASS-dev] [GRASS GIS] #3405: encoding issue when launching modules

#3405: encoding issue when launching modules --+--- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.4.0 Component: wxGUI|Version:

Re: [GRASS-dev] [GRASS GIS] #3405: encoding issue when launching modules

#3405: encoding issue when launching modules --+--- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.4.0 Component: wxGUI|Version:

Re: [GRASS-dev] [GRASS GIS] #3405: encoding issue when launching modules

#3405: encoding issue when launching modules --+--- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.4.0 Component: wxGUI|Version:

Re: [GRASS-dev] v.in.osm working?

> You can use v.in.ogr directly for OSM PBF files ( > http://gdal.org/drv_osm.html). > > BTW, with GDAL 2.2.1, using OGR_INTERLEAVED_READING=YES does not work for > me (empty vector). Caution: you cannot just specify OGR_INTERLEAVED_READING=YES and loop over layers as usual. See the

Re: [GRASS-dev] v.in.osm working?

On Thu, Aug 24, 2017 at 9:30 AM, Markus Metz wrote: > On Tue, Aug 22, 2017 at 8:37 PM, Markus Neteler wrote: >> Hi, >> >> does v.in.osm actually work? I am trying to import from a OSM PBF >> file, for example: >> >>

Re: [GRASS-dev] [GRASS GIS] #3409: d.what.vect JSON issue with OSM data

#3409: d.what.vect JSON issue with OSM data --+- Reporter: neteler | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.2.2 Component: Display |Version: svn-releasebranch72

[GRASS-dev] [GRASS GIS] #3409: d.what.vect JSON issue with OSM data

#3409: d.what.vect JSON issue with OSM data -+- Reporter: neteler | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.2.2 Component: Display

Re: [GRASS-dev] v.in.osm working?

On Tue, Aug 22, 2017 at 8:37 PM, Markus Neteler wrote: > > Hi, > > does v.in.osm actually work? I am trying to import from a OSM PBF > file, for example: > > http://download.geofabrik.de/europe/germany/berlin.html > --> berlin-latest.osm.pbf (51MB) > > grass72