search

landam / grass-gis-git-migration-test

0 stars 0 forks source link

Pattern Flag addition to v.patch #151

Open landam opened 5 years ago

landam commented 5 years ago

Reported by 3DTOPO on 31 Jan 2015 19:39 UTC 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.

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

landam commented 5 years ago

Comment by wenzeslaus on 12 Nov 2015 01:55 UTC https://grass.osgeo.org/grass77/manuals/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. .htmlI'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 https://grass.osgeo.org/grass77/manuals/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..html

landam commented 5 years ago

Comment by neteler on 5 May 2016 14:08 UTC Milestone renamed

landam commented 5 years ago

Comment by neteler on 28 Dec 2016 15:04 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by @landam on 5 May 2017 20:40 UTC

landam commented 5 years ago

Comment by @landam on 1 Sep 2017 20:28 UTC All enhancement tickets should be assigned to 7.4 milestone.

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

Comment by @landam on 28 Jan 2018 11:00 UTC No activity 2 years, what is status of this issue?

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:52 UTC All enhancement tickets should be assigned to 7.6 milestone.

landam commented 5 years ago

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