v.patch: Continuous cats with -e

[HuidaeCho]

This PR makes patched categories continuous. Without this PR:

v.random tmp100 npoints=100 seed=100
v.db.addtable tmp100 col="id varchar(20)"
v.db.update tmp100 col=id qcol="'tmp100_' || cat"

v.random tmp10 npoints=10 seed=10
v.db.addtable tmp10 col="id varchar(20)"
v.db.update tmp10 col=id qcol="'tmp10_' || cat"

v.patch tmp100,tmp10 out=tmp110 -e

v.category tmp110 op=report
Layer/table: 1/tmp110
type       count        min        max
point        110          2        112
line           0          0          0
boundary       0          0          0
centroid       0          0          0
area           0          0          0
face           0          0          0
kernel         0          0          0
all          110          2        112 # 2-101, 103-112

With this PR:

v.category tmp110 op=report
Layer/table: 1/tmp110
type       count        min        max
point        110          1        110
line           0          0          0
boundary       0          0          0
centroid       0          0          0
area           0          0          0
face           0          0          0
kernel         0          0          0
all          110          1        110 # 1-110

[HuidaeCho]

This PR partly addresses https://lists.osgeo.org/pipermail/grass-dev/2024-March/096233.html. In my test, all features were linked to cats.

[cmbarton]

This PR partly addresses https://lists.osgeo.org/pipermail/grass-dev/2024-March/096233.html. In my test, all features were linked to cats.

This looks like it solves a major part of my issues. Thanks much. I'll try to compile and test very soon.

[cmbarton]

This improves v.patch and works fine. So I recommend merging. However, there remain additional issues to solve.

[HuidaeCho]

This improves v.patch and works fine. So I recommend merging. However, there remain additional issues to solve.

@wenzeslaus Is this a GitHub bug? With @cmbarton's approval, I should be able to merge it, but it still says Review required. Weird...

[cmbarton]

I think it’s because I no longer have 'official' review to merge authorization.  Michael Barton...Sent from my iPadOn Mar 16, 2024, at 10:05 AM, Huidae Cho ***@***.***> wrote: This improves v.patch and works fine. So I recommend merging. However, there remain additional issues to solve. @wenzeslaus Is this a GitHub bug? With @cmbarton's approval, I should be able to merge it, but it still says Review required. Weird... —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[echoix]

I think it’s because I no longer have 'official' review to merge authorization.

Yes it is because of that. In these simple cases, when an external expert approves a PR but doesn't have the right permissions, someone else just comes in an approve afterwards, no big deal.