Opened 8 years ago

Last modified 3 years ago

#2571 new enhancement

Pattern Flag addition to v.patch

Reported by: 3DTOPO Owned by: grass-dev@…
Priority: normal Milestone: 7.6.2
Component: Vector Version: unspecified
Keywords: v.patch, file option, multiple input Cc:
CPU: Unspecified Platform: Unspecified

Description

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.

Change History (11)

comment:1 by wenzeslaus, 7 years ago

Keywords: file option multiple input added
Milestone: 7.0.07.1.0

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.

comment:2 by neteler, 6 years ago

Milestone: 7.1.07.2.0

Milestone renamed

comment:3 by neteler, 6 years ago

Milestone: 7.2.07.2.1

Ticket retargeted after milestone closed

comment:4 by martinl, 5 years ago

Milestone: 7.2.17.2.2

comment:5 by martinl, 5 years ago

Milestone: 7.2.27.4.0

All enhancement tickets should be assigned to 7.4 milestone.

comment:6 by neteler, 5 years ago

Milestone: 7.4.07.4.1

Ticket retargeted after milestone closed

comment:7 by martinl, 5 years ago

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

comment:8 by neteler, 4 years ago

Milestone: 7.4.17.4.2

comment:9 by martinl, 4 years ago

Milestone: 7.4.27.6.0

All enhancement tickets should be assigned to 7.6 milestone.

comment:10 by martinl, 4 years ago

Milestone: 7.6.07.6.1

Ticket retargeted after milestone closed

comment:11 by martinl, 3 years ago

Milestone: 7.6.17.6.2

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.