Pattern Flag addition to v.patch

[3DTOPO]

Currently there is a limit to the number of vectors that can operated on with v.patch. Apparently adding a pattern flag to v.patch could allow a user to work around this limitation.

[wenzeslaus]

G7:r.colors and G7:r.series have option file which is an alternative to map and input options. It is a path to a text file with names of raster maps, one map per line. This is simple and solves the problem, although the naming could be more clear.

I'm not sure how this should work for vector. Particularly, what to with layers? Should the format be something like the following?

native_vect_name_a 1
native_vect_name_b 1
native_vect_name_c 5

Should the layer be optional? So for layer one (that's the usual default):

native_vect_name_a
native_vect_name_b
native_vect_name_c

It would be up to the module to define if the default layer is something else, same as with options.

The OGR direct access would require (as far as I understand):

file_path/file_name_a@OGR file_name_a
file_path/file_name_b@OGR file_name_b
file_path/file_name_c@OGR file_name_c

Does this sound reasonable? Will the formats work always?

Comparing to the proposed pattern solution, this should cover more cases and it should be better for programming. However, it requires G7:g.list call first in non-programming most cases. Anyway, if I remember correctly, this was discussed on mailing list and the result was usage of text file.

[neteler]

Milestone renamed

[neteler]

Ticket retargeted after milestone closed

[martinl]

All enhancement tickets should be assigned to 7.4 milestone.

[neteler]

Ticket retargeted after milestone closed

[martinl]

No activity 2 years, what is status of this issue?

[martinl]

All enhancement tickets should be assigned to 7.6 milestone.

[martinl]

Ticket retargeted after milestone closed

[martinl]

Ticket retargeted after milestone closed