[GRASS-dev] doc 'upgrade' request for v.net.path

[Moritz Lennert]

On 16/11/07 16:04, Michael Barton wrote:
> 
> 
> On 11/16/07 5:48 AM, "Moritz Lennert" <mlennert at club.worldonline.be> wrote:
> 
>> On 15/11/07 16:30, Michael Barton wrote:
>>>It is still unclear to me what the
>>> "1" is for since it doesn't seem to apply to layer (i.e., the nodes in a
>>> network are normally in layer 2).
>>
>> 1 is the id you wish to give to the resulting line. v.net.path
>> automatically creates a category number, but it also creates an id
>> column which contains this number.
>>
>> This is linked to the fact that you are not limited to two points, i.e.
>> two paths, but you can feed as many start and end points as you want to
>> v.net.path.
> 
> Thanks very much for the clarification. This is far from clear in the docs.
> Are the entries for each path (cat,start,path) to be separated by spaces or
> a return in the text file?
>  
> 1 start end 2 start end 3 start end...
> 
> OR
> 
> 1 start end
> 2 start end
> 3 start end

Try it ;-)
I think only the second works, but am not 100% sure.


> ...
> 
>>> It would seem a lot easier to simply have a "startend=" option built
>>> into v.net.path that takes 2 cats separated by a comma.
>> This would then limit the use to one path, unless you actually allow
>> entry of multiples of 3 in the form id,start,end,id,start,end,...
> 
> Multiple entries of 3 separated by a comma or semicolon in a module option
> (e.g., "startend=1 start end,2 start end,3 start end,...") would be no more
> difficult to type and easier for non-unix types to understand than piping
> the same info to the command (i.e., 1 start end 2 start end | v.net.path...)

Yes, obviously, it should be space, not comma separated. If you want a 
comma between every path, then you will probably have to modify 
v.net.path even more, although I'm not sure that it would be an enormous 
effort.

Moritz