#836: quiet processing in v.net.path
-------------------------+--------------------------------------------------
Reporter: 09091968 | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: normal | Milestone: 6.4.0
Component: Vector | Version: 6.4.0 RCs
Keywords: v.net.path | Platform: MSWindows XP
Cpu: Unspecified |
-------------------------+--------------------------------------------------
Hello,
I am new to grass, but with the book and the web I am about to succeed in
calculating millions of paths using v.net.path, great stuff!!!
In my datasets a lot of "not reachable" messages pop up, slowing the
processing by a factor 5 to 10 (about 20 % of the from or to are within
pedestrian areas, with no car access or vice versa). Preselecting the
from/to is not easy to administer (5 different modes, a lot of scenario
stuff...)
The quiet option does not prohibits this message. Is it possible to modify
this ?
It uses G_warning(), which can not be surpressed at run-time.
if you run GRASS with a MSys terminal you could redirect the error
messages to a file or to the dustbin with something like:
{{{
v.net.path ... options ... 2> v.net.path.err
}}}
or from the dos prompt with something like
{{{
v.net.path ... > nul:
}}}
In general throwing away all warning and error messages can be quite
counter productive as you might miss the real ones.
I don't think there will be a way to shut them off from the GUI right now.
Q: are those messages (from v.net.path/path.c) informational (and so
should use G_message()) or actually quite important to know (so stay with
G_warning()) ?
I don't know enough about the module to answer that.
Replying to [comment:2 neteler]:
> The v.net modules have been massively improved, please try 6.4.svn
> (upcoming 6.4.3) or later. Closing, feel free to reopen if the
> problem persists.
The problem, if you will so, persists. The ticket was opened 3 years ago,
since then bugs in the GRASS routing library have been fixed and at the
moment there are no known bugs in this library.
But the description of the ticket lets suggest that the unreachable
warnings were correct in the sense that some nodes were indeed
unreachable. This is important information for the user since the user
wants to find the shortest path between nodes A and B, but there is no
path at all between these nodes. Since this is no bug in the module
itself, the warning could be converted to an important message, which can
be suppressed by setting GRASS_VERBOSE to 0 or -1. OTOH, it could be left
as a warning because it could indicate an error in the network
preparation.