search

landam / grass-gis-git-migration-test

0 stars 0 forks source link

quiet processing in v.net.path #36

Open landam opened 5 years ago

landam commented 5 years ago

Reported by 09091968 on 15 Dec 2009 19:00 UTC 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 ?

Thanks,

Luc

GRASS GIS version and provenance

6.4.2

Migrated-From: https://trac.osgeo.org/grass/ticket/836

landam commented 5 years ago

Comment by hamish on 16 Dec 2009 02:16 UTC 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.

Hamish

landam commented 5 years ago

Comment by neteler on 21 Aug 2012 17:52 UTC 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.

landam commented 5 years ago

Comment by mmetz on 21 Aug 2012 18:45 UTC 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.

Markus M

landam commented 5 years ago

Modified by @landam on 12 May 2016 06:44 UTC

landam commented 5 years ago

Modified by @landam on 25 Aug 2016 15:51 UTC

landam commented 5 years ago

Comment by @landam on 27 Aug 2016 13:42 UTC Milestone renamed

landam commented 5 years ago

Comment by neteler on 26 Jan 2018 11:40 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by neteler on 12 Jun 2018 20:48 UTC

landam commented 5 years ago

Comment by @landam on 25 Sep 2018 16:51 UTC All enhancement tickets should be assigned to 7.6 milestone.

landam commented 5 years ago

Comment by @landam on 25 Jan 2019 21:08 UTC Ticket retargeted after milestone closed