Re: [GRASS-user] v.isochrones : error message

[Markus Neteler]

On Dec 17, 2015 5:29 PM, "image93"  wrote:
>
> 

As you can see, it is from 2014.

Please update your installation.

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

Re: [GRASS-user] v.isochrones : error message

[image93]

 



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/v-isochrones-error-message-tp5241729p5241796.html
Sent from the Grass - Users mailing list archive at Nabble.com.
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] v.isochrones : error message

[Markus Neteler]

On Dec 17, 2015 4:48 PM, "image93"  wrote:
>
> My current version is GRASS GIS 7.1.svn

>From which date? It is too generic.
Please send the suggested output.

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

Re: [GRASS-user] v.isochrones : error message

[image93]

My current version is GRASS GIS 7.1.svn

Thanks. 



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/v-isochrones-error-message-tp5241729p5241785.html
Sent from the Grass - Users mailing list archive at Nabble.com.
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Average raster value of the upslope contributing area,

[Pierluigi De Rosa]

Hi Johannes, 


perhaps you procedure could be correct. 
Let'me try and I will notify my progress 
Pierluigi 


- Messaggio originale -

Da: "Johannes Radinger"  
A: "Ing. Pierluigi De Rosa"  
Cc: "grass-user"  
Inviato: Giovedì, 17 dicembre 2015 11:51:15 
Oggetto: Re: [GRASS-user] Average raster value of the upslope contributing 
area, 


Hi Pierluigi, 


I think here you could use the tool r.watershed ( 
https://grass.osgeo.org/grass70/manuals/r.watershed.html ) 
with your underlying DEM as input. This tool will provide you an accumulation 
map with increasing values in 
downstream direction. 


I am not exactly sure if this is your task, but if you provide an input map for 
'flow' with values for each cell that represents 
the actual cell size than the output accumulation map output is your upslope 
contributing area. If you 
use another input map for 'flow' (e.g. sediment input per cell) than the output 
will be the accumulated sediment 
in downstream direction. Subsequently you can use r.mapcalc to divide both maps 
to get the ratio 
of sediment delivery per unit upslope contributing area. 


I hope that helps?! 


cheers, 
Johannes 




On Thu, Dec 17, 2015 at 11:29 AM, Ing. Pierluigi De Rosa < 
pierluigi.der...@gfosservices.it > wrote: 


Dear users, 

my deal is to calculate a raster of the sediment delivery ratio like 
explained here: 
http://data.naturalcapitalproject.org/nightly-build/invest-users-guide/html/sdr.html#sediment-delivery-ratio
 

moreover I need to calculate, for each cell, the average of a raster (C 
factor) of the upslope contributing area. 
take a look to these image to better explication: 
http://data.naturalcapitalproject.org/nightly-build/invest-users-guide/html/_images/connectivity_diagram.png
 

How can I do that? 
Thanks 
Pierluigi 


-- 


 
Ing. Pierluigi De Rosa (PhD) 
Studio Associato GFOSSERVICES 


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



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

[GRASS-user] Trouble with SQLite on NFS

[Blumentrath, Stefan]

Hi,

Recently I started having trouble with SQLite on NFS. SQLite databases appear 
to be always locked, even the very moment when they are created (e.g. through 
v.out.ogr). Not sure what the reason might be as several things were changed at 
once: OS / package update, changed mounting routine...

There are voices saying that SQLite should not be used on NFS at all: 
http://stackoverflow.com/questions/9907429/locking-sqlite-file-on-nfs-filesystem-possible
And it seems that many (if not all) operative systems (Ubuntu, RedHat, 
Windows...) are having trouble with file-locking on NFS, see: 
https://www.sqlite.org/faq.html#q5

Mounting the share with "nolock"-option makes it possible to create SQLite DBs 
on NFS, but I am afraid that this could have unpredictable side effects!?. It 
would be a pity if we could not use SQLite on NFS reliably...

I tried if I can work around this, by moving temporary files to the local file 
system (as described here: https://trac.osgeo.org/grass/ticket/2185). But that 
does not seem to have any effect. How can I check if TMPDIR and 
GRASS_TMPDIR_MAPSET are taken into account?

Thanks for helping in advance...

Kind regards,
Stefan


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

Re: [GRASS-user] wingrass daily buidls + addons temporary down

[Martin Landa]

Hi,

2015-12-16 21:56 GMT+01:00 Martin Landa :
> * GRASS Addons are still down (will work on them in the next days)

GRASS Addons now again back (you need to install the most fresh daily
build). Thanks for testing. Ma

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] v.isochrones : error message

[Markus Neteler]

Hi,

On Thu, Dec 17, 2015 at 11:24 AM, image93  wrote:
> Dear all,
>
> We just tried a test with v.isochrones on Grass 7 (windows 32 bits).

please post the version of your GRASS GIS installation because...

[...]

> Usage:
>  r.cost [-knri] input=name output=name [nearest=name]
> [outdir=name]
>[start_points=name] [stop_points=name] [start_rast=name]
>[start_coordinates=east,north[,east,north,...]]
>[stop_coordinates=east,north[,east,north,...]]
> [max_cost=value]
>[null_cost=value] [percent_memory=value] [--overwrite]

"percent_memory" no longer exists (changed to "memory" several 7 versions back:
https://grass.osgeo.org/grass70/manuals/r.cost.html

You get the version either from Help --> About system

or

g.version -g

You likely need to update your installation.

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

Re: [GRASS-user] Average raster value of the upslope contributing area,

[Johannes Radinger]

Hi Pierluigi,

I think here you could use the tool r.watershed (
https://grass.osgeo.org/grass70/manuals/r.watershed.html)
with your underlying DEM as input. This tool will provide you an
accumulation map with increasing values in
downstream direction.

I am not exactly sure if this is your task, but if you provide an input map
for 'flow' with values for each cell that represents
the actual cell size than the output accumulation map output is your
upslope contributing area. If you
use another input map for 'flow' (e.g. sediment input per cell) than the
output will be the accumulated sediment
in downstream direction. Subsequently you can use r.mapcalc to divide both
maps to get the ratio
of sediment delivery per unit upslope contributing area.

I hope that helps?!

cheers,
Johannes


On Thu, Dec 17, 2015 at 11:29 AM, Ing. Pierluigi De Rosa <
pierluigi.der...@gfosservices.it> wrote:

> Dear users,
>
> my deal is to calculate a raster of the sediment delivery ratio like
> explained here:
>
> http://data.naturalcapitalproject.org/nightly-build/invest-users-guide/html/sdr.html#sediment-delivery-ratio
>
> moreover I need to calculate, for each cell, the average of a raster (C
> factor) of the upslope contributing area.
> take a look to these image to better explication:
>
> http://data.naturalcapitalproject.org/nightly-build/invest-users-guide/html/_images/connectivity_diagram.png
>
> How can I do that?
> Thanks
> Pierluigi
>
>
> --
>
>
> 
> Ing. Pierluigi De Rosa (PhD)
> Studio Associato GFOSSERVICES
>
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Average raster value of the upslope contributing area,

[Ing. Pierluigi De Rosa]

Dear users,

my deal is to calculate a raster of the sediment delivery ratio like
explained here: 
http://data.naturalcapitalproject.org/nightly-build/invest-users-guide/html/sdr.html#sediment-delivery-ratio

moreover I need to calculate, for each cell, the average of a raster (C
factor) of the upslope contributing area.
take a look to these image to better explication:
http://data.naturalcapitalproject.org/nightly-build/invest-users-guide/html/_images/connectivity_diagram.png

How can I do that?
Thanks
Pierluigi


-- 



Ing. Pierluigi De Rosa (PhD)
Studio Associato GFOSSERVICES


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

[GRASS-user] v.isochrones : error message

[image93]

Dear all,

We just tried a test with v.isochrones on Grass 7 (windows 32 bits). 
We set the resolution 'ew' and 'ns' on 100. 
Our road network comes from OSM data. We edited the network and kept only
usefull roads for car isochrony. We erected  speed profile values. We chose
the r.cost method.
 
Below, i paste the error message. Could you throw light for me? 

Thanks.


-
(Thu Dec 17 10:55:58 2015)  
v.isochrones map=Road_IDF_iso_VOITURE_L93@Dataset_AD_iso roads_layer=1
cost_column=MS_profil start_points=Loc_GE_PS@Dataset_AD_iso
isochrones=ISO_Voit_GE_PS_15_min time_steps=15 timemap=raster_iso_voit_15
method=r.cost
Unknown module parameter "keyword" at line 18
Unknown module parameter "keyword" at line 19
Unknown module parameter "keyword" at line 20
Pass 1 of 15:
Reading features...
Writing raster map...
Pass 2 of 15:
Reading features...
Writing raster map...
Pass 3 of 15:
Reading features...
Writing raster map...
Pass 4 of 15:
Reading features...
Writing raster map...
Pass 5 of 15:
Reading features...
Writing raster map...
Pass 6 of 15:
Reading features...
Writing raster map...
Pass 7 of 15:
Reading features...
Writing raster map...
Pass 8 of 15:
Reading features...
Writing raster map...
Pass 9 of 15:
Reading features...
Writing raster map...
Pass 10 of 15:
Reading features...
Writing raster map...
Pass 11 of 15:
Reading features...
Writing raster map...
Pass 12 of 15:
Reading features...
Writing raster map...
Pass 13 of 15:
Reading features...
Writing raster map...
Pass 14 of 15:
Reading features...
Writing raster map...
Pass 15 of 15:
Reading features...
Writing raster map...
Converted points/lines: 253058 of 253058
v.to.rast terminé.
Description:
 Creates a raster map showing the cumulative cost of moving
between different geographic locations on an input raster
map whose cell category values represent cost.
Keywords:
 raster, cost surface, cumulative costs, cost allocation
Usage:
 r.cost [-knri] input=name output=name [nearest=name]
[outdir=name]
   [start_points=name] [stop_points=name] [start_rast=name]
   [start_coordinates=east,north[,east,north,...]]
   [stop_coordinates=east,north[,east,north,...]]
[max_cost=value]
   [null_cost=value] [percent_memory=value] [--overwrite]
[--help]
   [--verbose] [--quiet] [--ui]
Flags:
  -k   Utiliser le "mouvement du cavalier (aux échecs)";
plus lent, mais plus précis
  -n   Keep null values in output raster map
  -r   Démarrer avec les valeurs de la couche raster
  -i   Print info about disk space and memory requirements
and exit
 --o   Autoriser la sortie à écraser les fichiers existants
 --h   Print usage summary
 --v   Sortie du module en mode bavard
 --q   Sortie du module en mode silence
 --ui  Force launching GUI dialog
Parameters:
  input   Name of input raster map containing
grid cell cost information
 output   Nom de la couche matricielle en sortie
nearest   Name for output raster map with
nearest start point
 outdir   Name for output raster map to contain
movement directions
   start_points   Name of starting vector points map
   Or data source for direct OGR access
stop_points   Name of stopping vector points map
   Or data source for direct OGR access
 start_rast   Name of starting raster points map
  start_coordinates   Coordinates of starting point(s) (E,N)
   stop_coordinates   Coordinates of stopping point(s) (E,N)
   max_cost   Maximum cumulative cost
  par défaut: 0
  null_cost   Coût assigné aux cellules vides. Par
défaut, les cellules vides sont ignorées
 percent_memory   Pourcentage de la couche à garder en
mémoire
  options: 0-100
  par défaut: 40
ERROR: Sorry,  is not a valid parameter
Traceback (most recent call last):
  File "C:\Users\aderouen\AppData\Roaming\GRASS7\addons/scri
pts/v.isochrones.py", line 395, in 
main()
  File "C:\Users\aderouen\AppData\Roaming\GRASS7\addons/scri
pts/v.isochrones.py", line 304, in main
memory=memory)
  File "C:\Program Files\GRASS GIS
7.1.svn\etc\python\grass\script\core.py", line 373, in
run_command
return handle_errors(returncode, returncode, args,
kwargs)
  File "C:\Program Files\GRASS GIS
7.1.svn\etc\python\grass\script\core.py", line 308, in
handle_errors
returncode=returncode)
grass.exceptions.CalledModuleError: Module run None
['r.cost', 'input=cost_map_tmp_7012',
'start_points=Loc_GE_PS@Dataset_AD_iso',
'output=time_map_tmp_7012', 'max_cost=15', 'memory=300']
ended with error
Process ended with non-zero return code 1. See errors in the
(error) output.
(Thu Dec 17 10:57:57 2015) La commande s'est terminée (1 min 58 sec)
--





--
View this message in context: 
http://osgeo-org.1560.x6.nabble.c