Dear list,
I hope you can help me to understand the behavior of GRASS for the
following: I need calculate the network-distances for intersections in
this network. What seemed easy, starts to get very tricky
My approach is shown below, but has following problems:
1.) As intersections need
On Tue, Mar 11, 2014 at 4:09 PM, Patrick S. wrote:
> Dear list,
>
> I hope you can help me to understand the behavior of GRASS for the
> following: I need calculate the network-distances for intersections in this
> network. What seemed easy, starts to get very tricky
>
> My approach is shown b
On Tue, Mar 11, 2014 at 9:01 PM, Markus Metz
wrote:
...
> v.net.allpairs does not work properly in GRASS 6.
Should we drop it from G6?
> You need to use GRASS 7 if you want to use this module.
(we'll hopefully package the tech preview release at the Vienna code
sprint but you can get it from he
Thanks, Markus.
In that case it would be of advantage to remove this function.
However, before I go for GRASS 7 (which will be harder to host on our
Server): The module v.net.allpairs in GRASS 7.0 demands to keep points
and lines on different layers, which did not work for me when using
Postgr
On Wed, Mar 12, 2014 at 10:40 AM, Patrick S. wrote:
...
> However, before I go for GRASS 7 (which will be harder to host on our
> Server):
Anything we can help with to facilitate the installation of GRASS 7?
Note that you can run both GRASS 6 and 7 in parallel.
best
markusN
_
On 03/12/2014 10:46 AM, Markus Neteler wrote:
On Wed, Mar 12, 2014 at 10:40 AM, Patrick S. wrote:
...
Anything we can help with to facilitate the installation of GRASS 7?
Note that you can run both GRASS 6 and 7 in parallel.
I am not a "poweruser" of the servers, so the admin will only run
inst
Markus Metz wrote:
>> v.net.allpairs does not work properly in GRASS 6.
Markus Neteler wrote:
> Should we drop it from G6?
the changes look contained and non-fatal, so good candidate for backport.
https://trac.osgeo.org/grass/changeset?new=55985%40grass%2Ftrunk%2Fvector%2Fv.net.allpairs&old=5
